IP Comms DEVICE CONFIGURATION SOLUTION

GSMA.N2020.DSD V1 – 22.02.2017

Welcome

Open Market devices > 60% of devices shipped. MNO-specific SKUs no longer solve the problem.

VoLTE / ViLTE launches are increasing making device configuration a major MNO and OEM issue and driving up OPEX / CAPEX costs due to non-centralised individual approaches.

Differences in MNO implementations of ‘standard’ services causes device-network interoperability issues.

VIRTUE / IR.92 v10 and regional profiles:

Reduce fragmentationAlign operators to facilitate interoperabilityReduce optionalityBut late customisation of devices required to provide flexibility

31 Jan 2017, GSMA

Issues

LTE Launched by Reaching

580 189 60%In

Operators Of PopulationCountries

voice andvideo over

Operatorlaunches

Countries

Devices

LTE102 55 842

RCS Voice over WiFi HD VoiceOPERATOR LAUNCHESCOUNTRIESDEVICESHOSTED SOLUTIONPROVIDERS

5037

15619

OPERATOR LAUNCHESCOUNTRIES

52

31

OPERATOR LAUNCHESCOUNTRIES

164

88

IP comms device configuration ecosystem

3rd PARTY

MNO

MNO

MVNO

MVNO

GSMA - HOSTEDDATABASE

OEM

CHIPSETPROVIDER

Settings

MNO #1

MNO #2

MNO #3

MNO #N

Common configurationparameters

TSG TAD and OEM settings

TS.36 specifications and the database implementation

N2020.05specifications

TS.32specifications

Device configuration solution diagram

LocalDB

pull / pushmechanisms

OEMparameters

OEM /Chipset Man. /

3rd party

Device Configuration

Servers

TSG TAD TSG DSD DCS

GSMA Hosted

Database

The common solution is to configure the common parameters and their default values via late customisation. Any subscriber / device differentiation can be subsequently covered by the operator provisioning if necessary. Note that RCS configuration is done solely via operator provisioning.

OEMs recognise that individual bilateral agreements with all MNOs over a large number of technical features and settings is not feasible and therefore support the GSMA’s initiative.

OEMs see collating MNO technical settings in a central database as crucial for allowing the telecoms industry to move forward to the rapid and efficient deployment of new services.

OEMs support the Device Configuration Database

Project initial launch

OEM-XOEM-Z

OEM-XOEM-Y

MNO-BSettings

MNO-ASettings

MNO-CSettings

IC2 interfaces for MNOs to upload settings

IC2 interfaces for OEMs to download settings

Every MNO and every OEM will have fully isolated libraries

MNOs will define which OEMs to access their settings

MNOs will submit the settings file and OEM access preferences by Friday 01:00 GMT

A weekly automated process will deliver settings files into the OEM libraries that has access permission

OEMs receive notification email

MNO-A

OEM-XOEM-YOEM-Z

MNO-B

MNO-C

OEM-X

OEM-Y

OEM-Z

8

Project initial launch

MNO responsibilities:Fill the TS.32 settings Excel sheet with the settings data ready for production environment and upload the file to the MNO’s own library in InfoCentre2

Determine the OEMs list which will be granted access to the settings data and upload to the MNO’s own library

Update the settings Excel sheet when there is a change in the TS.32 settings

OEM responsibilities:Follow up the email notifications and visit InfoCentre2 library weekly basis

Download the up to date operator settings data Excel

Test and implement the settings data into the device configuration servers and devices

Q. Which settings are included in the scope?A. All device settings including VoLTE, ViLTE, VoWiFi and radio parameters.

Please refer to TS.32 v1 document for further details.

Q. Can operators see each others settings?A. No, settings are isolated between the operators.

Q. Can all OEMs see all operator settings?A. No, operators a list of OEMs that their setting can be provide to. Ideal the setting should be

available for all OEMs.

Q. How can operators and OEMs join the project?A. To find out more and to participate in this initiative visit

gsma.com/network2020/digest/dsd

Key questions

Where to discover more?

NETWORK 2020The GSMA’s Network 2020 programme working with the mobile industry speeding up the development of all-IP communications.

UNIVERSAL PROFILEA global initiative to provide the mobile industry with a common universal profile that enables mobile operators to deploy an interoperable RCS service.

ADVANCED COMMUNICATIONS DOCUMENTSRegularly updated, specifications.

ACCREDITATION AND CERTIFICATION

RICH COMMUNICATIONSSERVICE (RCS)Modernises voice/text experience provide a richer, simpler, and more fluid mobile experience.

END-USER RESEARCHWHY ADVANCED COMMUNICATIONS?We asked users what they thought of Advanced Communications and the results show it has strong appeal:

Interoperability and Testing (IOT) enables a company to verify the maturity of their implementation prior to commercial launch or operator’s acceptance testing.

http://www.gsma.com/network2020/ http://www.gsma.com/network2020/accreditation-and-certification//

http://www.gsma.com/network2020/resources/end-user-research/

http://www.gsma.com/network2020/enriched-calling-with-rcs/

http://www.gsma.com/network2020/specs-and-product-docs/

http://www.gsma.com/network2020/universal-profile/

Questions and Answers

Network 2020 ProgrammeShaping the next generation in mobile

BACKUP SLIDES

TERMINAL STEERING GROUP:

TSG is a members only GSMA working group that facilitates operator and vendor alignment to drive terminal related matters for the benefit of the entire mobile ecosystem. It manages/coordinates terminal capability requirements activities within GSMA and beyond. TSG also provides a first contact point for operators or vendors or industry organisations who would like to:

Update on and discuss terminal related matters

Start a new terminal capability requirements activity

Update one of the published terminal capability requirements activities

Update one of the testing specifications TSG provides a coordinated activity for operators and vendors to

Review GSMA project and WGs proposals & outputs on terminal capability requirements

Ensure feasibility, consistency, vendor engagement, no overlap with other industry bodies activities

Align work between terminal capability requirements and terminal testing activities

Appendix - TSG

Appendix – TSG TAD

TECHNICAL ADAPTATION OF DEVICES

Task Force under TSG that defined a set of configuration parameters for Late Customisation for open

market devices

Covered all aspects of late configuration (e.g. LTE RAN aspects, 2G/3G RAN, IMS aspects and

others)

The IMS aspects were defined in co-operation with RILTE and were also reflected in updates to latest

versions of RILTE PRDs (IR.92 etc.) via addition of annexes with parameters and default values and

(continuing) interaction with 3GPP to maintain alignment

Published PRD TS.32 v1 Technical Adaptation of Devices through Late Customization in August 2016

Please see https://infocentre2.gsma.com/gp/wg/TS/WI/TAD/Pages/Default.aspx

Appendix – TSG DSD

DEVICE SETTINGS DATABASE

Task Force under TSG that provides a central repository for operator -specific settings,

These settings will be made available to device manufacturers, to bring improved ease -of-use to end

customers and improved performance of devices, while reducing the need for bilateral

communications between OEMs and carriers.

Published PRD TS.36 v1 Devices Settings Database in August 2016

The PRD specifies the “requirements for a database enabling the efficient transfer of settings from

mobile network operators (including mobile virtual network operators) to device manufacturers in order

to allow for the appropriate customization of devices “.

Please see https://infocentre2.gsma.com/gp/wg/TS/WI/SET/Pages/Default.aspx

Appendix – N2020 DCS

NETWORK 2020:The GSMA’s Network 2020 programme works with the mobile industry to deliver a collaborative and coordinated way of speeding up the development of all-IP communications. The programme aims to produce a world in which all-IP global networks let mobile users enjoy seamless, secure and enriched communications on any device. Please visit web site for more information: www.gsma.com/network2020

DEVICE CONFIGURATION SERVERProject group under N2020 IP Comms Leadership Team, being run in conjunction with TSG work groups

Published N2020.05 v1 Device Configuration Server Mechanisms in January 2017

The PRD summarizes the common solution for the late customization of the devices and focuses on the best practice methods of implementing a device config server.

Please see https://infocentre2.gsma.com/gp/pr/V2020/N2020/RCSLT/DCS/Pages/Default.aspx