LAUNCHING RCS THINGS TO CONSIDER KOBUS SMIT, STRATEGIC ENGAGEMENT - PowerPoint PPT Presentation

LAUNCHING RCS – THINGS TO CONSIDER KOBUS SMIT, STRATEGIC ENGAGEMENT DIRECTOR – GSMA

RCS Deployment Options Operators face a number of choices in deploying RCS: • RCS Infrastructure: on premises or hosted? • Which vendor? • Which RBM server? The following slides outline the alternatives

Operator Owned Solution ADVANTAGES DISADVANTAGES   More flexibility Requires more expertise to set up and operate  More options for differentiation from other  Deployment timeline will normally be longer operators  E.g. integration with legacy messaging  Requires the establishment of specific connections with other networks  Infrastructure can be partly shared with VoLTE  Most networks can be covered with connections  Allows to use joint registration through hubs  More efficient on client-side (e.g. battery  Some may need dedicated connections (e.g. other consumption) major operators in country)  Need for joint project with other network  Provides more visibility of the traffic and user behaviour  Makes it easier to provide customer support  No need to provide authentication options to 3 rd parties 3 CONFIDENTIAL

Hosted Solution ADVANTAGES DISADVANTAGES   Easy to deploy Separate infrastructure  Only requires providing access from cellular network  Requires dual registration and enabling authentication  Somewhat less efficient on client side  Access may even be straightforward if using the  Little control over feature roadmap of network internet APN as HOS APN   More difficult to connect to legacy messaging infrastructure Almost no in-house experience is required  Fall-back to SMS on the client is probably most viable  Easy interconnect approach  Almost instant connectivity to other networks hosted Requires providing 3 rd parties with options to authenticate user  by same party and all networks that party connected  Limits authentication options to already  Somewhat mitigated from UP 2.0 onwards with OpenID  No technical expertise required for further connect authentication that can be performed against endpoint connections provided by operator  Quicker to deploy  Less visibility of traffic  Customer support and general monitoring (e.g. fraud prevention) will be harder 4 CONFIDENTIAL

Business Model for Hosted RCS  Hosted RCS solutions are a low-Capex, faster way to introduce RCS A2P services  Service provider may seek to monetise provision of the RCS service through revenue-sharing on A2P revenue  Operators considering hosted services should:  Be aware of the WA.09 ecosystem principles  Be aware of the short, medium and long term financial pros and cons  Ensure they maintain control of the directory of chatbots reachable from the device  Ensure that they contractually maintain the right and technical ability to connect to aggregators and chatbots, regardless of whether the chatbots are enabled by the hosted solution provider or another party 5 CONFIDENTIAL

LEGAL INTERCEPT Operator services are obliged to support legal intercept Approaches differ by country and by vendor  Operators should request details of how Legal Intercept is satisfied from all potential vendors One of 3 Models for Legal Intercept usually applies  1) Regulator says RCS is not a regulated service  2) Regulator Legal Intercept performed by 3 rd pary service provider  3) Regulator requires Operator to provide Legal Intercept in their network Both 2) and 3) above can be subject to a temporary derogation by the Regulator

RCS Interconnect Interconnect is necessary to achieve reach and market coverage Operators can choose point to point interconnect or interconnecting via hubs

RCS INTERCONNECTION DIFFERS FROM SMS IN SEVERAL REGARDS  Specification enables different approaches for person-to- person interconnect traffic and Business interconnect traffic  Traffic type tag in traffic header  Different SIP address format for originator  Emphasis on hubs (join once / connect to multiple networks) approach to deliver scale  Ability for MNOs to interconnect for A2P traffic in a commercially viable – currently no MNO is exploiting this capacity but it is achievable

RCS INTERCONNECTION ARCHITECTURE AGGREGATOR MAAP PLATFORM MAAP API Gateway MAAP API Gateway MAAP Platform MAAP Platform Session Session Border Border RCS Core RCS Core Controller Controller RCS HUB MNO 1 MNO 2..n

P2P INTERCONNECTION HUBS  Currently 2 hubs supporting active networks  Vodafone Group hub  Google hub(s) Europe, Americas and Asia  Multiple additional providers of hubs entering the market (see below)  MNO hub initiative announced at MWC 2018  P2P hubs will be governed by Live Hubs Live Hubs Live Hubs Live Hubs  GSMA document on Europe Europe N. America China definition of hub-as-a- N. America S.E Asia service  Hub interconnect MoU encouraging hubs to interconnect

P2P INTERCONNECTION HUBS DT Albania TODAY DT Hungary DT Cosmote DT Slovakia DT Romania Orange Romania Orange Slovakia VF Albania VF Italy Telenor Norway VF Czech Republic VF Portugal Telenor Denmark VF Germany Telia Norway VF Romania Vodafone VF Greece Vodafone Rogers Bell Mobility VF Spain 12 VF Hungary VF Turkey VF Ireland VF UK Google (Belgium) Sprint Tracphone China Mobile ZTE (China) Google (San Fran) AMX Mex Reliance Jio Globe Singtel ZTE Google Hosted AMX Brazil (Singapore) Vodafone Hosted ZTE Hosted WIT Platform MNO Platform Launched and interconnected Launched Launching this FY Forecast to go from one to multiple launches in 2018