Mobile Connect: RCS and Blockchain...The Mobile Connect logo is a trade mark registered and owned by the GSMA. Sharing or verifying information for sensitive use cases where there

Mobile Connect: RCS and BlockchainDavid Pollington, Head of Service Access Technology

Enhancing RCS with identity

Copyright © 2018 GSMA. The Mobile Connect logo is a trade mark registered and owned by the GSMA.

• SMS A2P business messaging

volumes still growing (projected

to grow worldwide to $60-70bn

by 2020)

• … but already overtaken by

OTTs able to provide a richer

UX leading to higher

conversion rates and lower

costs

Identity – Mobile Connect3

SP need for richer UX accelerating adoption of OTT alternatives

0

500

1,000

1,500

2,000

2,500

3,000

3,500

4,000

4,500

5,000

5,500

6,000

6,500

7,000

2012 2013 2014 2015 2016 2017 2018 2019 2020 2021

OTT

SMS

GSMAi, Portio research

Volume, bn A2P Message Volume Forecast: SMS versus OTT

Copyright © 2018 GSMA. The Mobile Connect logo is a trade mark registered and owned by the GSMA.4

Importance of rich media and personalised experiences…

Identity – Mobile Connect

OpenMarket survey


… and deep integration (browser -> chat app)



• Enhanced customer engagement (reduced

churn)

• Interactive dialogue (low latency)

• Location awareness & customisation

• Rich media (images etc.)

• Rich Card UI (actions, carousels etc.)

• Self-serve content (usability)

• Message delivery robustness + read receipts

& analytics (click-through, performance etc.)

• Reduced operational costs

• 24/7/365 availability

(through automation)


SP requirements


Growing interest in using RCS for A2P business messaging…


MobileSquared survey

When would you want to start using RCS?RCS’ impact on your communications strategy?


RCS can support P2P and business messaging (P2A/A2P)

via a single app embedded natively in every phone…


OpenMarket survey


MNOs well placed to build on their existing SMS

A2P business relationships to offer a fully-

featured chat platform to SPs using RCS MaaP:

1. Ability to provide coverage equivalent to the

big 4 chat services combined

2. Ability to match other chat platforms in terms

of functionality through support for Rich

Cards

3. Intrinsic ability to step up to voice, or fallback

to SMS

4. Consumer preference for a more seamless

experience


MNO opportunity to build on existing A2P business with an

enhanced proposition built on RCS => MaaP [Messaging as a Platform]

OpenMarket survey


5. Arguably more trustworthy than some of the

competition:

• 64% of SPs have indicated that they would

trust a telco-based service more than chat

apps (such as Facebook Messenger)

• Users likely to be reticent in engaging SPs on

sensitive/personal subjects over a Facebook

platform, for example

6. Contextual insights about the user and their

device which can be used for service

personalisation or flagging potentially

fraudulent behaviour

7. Robust 'carrier grade' infrastructure including

end-to-end encryption and enhanced security


MNO opportunity to build on existing A2P business with an

enhanced proposition built on RCS => MaaP [Messaging as a Platform]

Copyright © 2018 GSMA. The Mobile Connect logo is a trade mark registered and owned by the GSMA.Identity – Mobile Connect11

Number of areas where MNOs can play a role in the value chain

RCS Infrastructure

RCS chat Platform

Direct-sell to brands

Digital Enablement

1 2 3 4

Which role do MNOs wish to play in the value chain?

Chatbot/SP

Authentication,

authorisation

and/or attributes

RCS

Chat

session

Authentication,

authorisation

and/or attribute

consent

SP/chatbot invokes

functionality separately

via RCS and MC APIs

✔︎

? ?


• Providing the means for businesses and end-

users to establish trust between one-another

via inclusion of an identity layer

• => leverage identity

capabilities of

Mobile Connect

• Three areas currently targeted:

1. Step-up authentication/authorisation

2. Sharing/verifying user information

3. Providing network attributes


Opportunities for MNOs to enhance/complement their RCS

propositions with identity


1. Explicit authentication of the

individual involved in an RCS chat

session

2. Requesting authorisation of an

action where explicit confirmation

(and an auditable trail) is required

Example use cases:

• Account administration

• High value transactions

• Charging purchases to mobile account

13

1. Step-up authentication/authorisation


RCS chat

ChatbotService request1

MC Authenticate

request (MC API)2

Service

authorisation

RCS Client

SIM applet


Sharing or verifying

information for sensitive use

cases where there is a risk of

fraud and/or the SP is

obligated to verify who they're

dealing with

Example use cases:

• Sale of age-restricted goods

• Verifying shipping address etc.

14

2. Sharing/verifying user information


RCS chat

Chatbot/

SPExpose MSISDN1

MC attribute

request (MC API)2

Personal

information

Locker

Fetch attributes

(MC resource API)4

RCS Client

Service

authorisation

RCS chat

or


Provision of unique insights relating

to the device through which a user is

accessing a chat (or other online)

service and the context of that

device to help mitigate fraud

Example use cases:

• Mitigating fraudulent purchases,

bot attacks etc.

15

3. Providing network attributes


RCS chat

Chatbot/

SPExpose MSISDN1

MC attribute

request (MC API)2

Network

attributes

Fetch attributes

(MC resource API)3

RCS Client

Service

authorisation


Candidate use cases


OpenMarket survey

Documents

Mobile Connect: RCS and Blockchain...The Mobile Connect logo is a trade mark registered and owned by the GSMA. Sharing or verifying information for sensitive use cases where there