1. Technical Support Report
IP Comms DEVICE CONFIGURATION SOLUTION

3. Issues
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 fragmentation
Align operators to facilitate interoperability
Reduce optionality
But late customisation of devices required to provide flexibility
LTE Launched by
194
Reaching
606 In 69 %
Operators
Countries
Of Population
105 56
voice and
video over
Devices
902
LTE
Operator
launches
Countries
RCS
Voice over WiFi
HD Voice
OPERATOR LAUNCHES
COUNTRIES
DEVICES
HOSTED SOLUTION
PROVIDERS 50 40
390 19
OPERATOR LAUNCHES
COUNTRIES 54 31
OPERATOR LAUNCHES
COUNTRIES
164 88
5 May 2017, GSMA

4. IP comms device configuration ecosystem
OEM
MVNO
MNO
Settings
GSMA - HOSTED
DATABASE
CHIPSET
PROVIDER
MNO
MVNO
3rd PARTY

5. Device configuration solution diagram
TSG TAD
000
000
000
000
TSG DSD
000
DCS
000
Common configuration parameters
pull / push
mechanisms
MNO #1
OEM / Chipset Man. / 3rd party
MNO #2
GSMA Hosted Database
Device Configuration Servers
MNO #3
Local DB
MNO #N
TS.32 specifications
TS.36 specifications and the database implementation
OEM parameters N
specifications
TSG TAD and OEM settings
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.

6. OEMs support the Device Configuration Database
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.

7. Project initial launch
OEM-X
MNO-A
Settings
MNO-A
OEM-X
OEM-Y
OEM-Z
OEM-Y
MNO-B
Settings
IC2 interfaces for MNOs to upload settings
IC2 interfaces for OEMs to download settings
Every MNO and every OEM will have fully isolated private libraries
MNOs will define which OEMs to access their settings
GSMA will manage the distribution of the settings to the OEMs
Notifications will be sent after new settings or setting updates
MNO-B
OEM-X
OEM-Z
OEM-Z
MNO-C
Settings
MNO-C
OEM-X
OEM-Y

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 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

9. Key questions 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

10. Where to discover more? FUTURE Networks End-user research
Why Advanced Communications?
Accreditation and certification
The GSMA’s Future Networks programme working with the mobile industry speeding up the development of all-IP communications.
Interoperability and Testing (IOT) enables a company to verify the maturity of their implementation prior to commercial launch or operator’s acceptance testing.
We asked users what they thought of Advanced Communications and the results show it has strong appeal:
Rich communications
Service (RCS)
Universal Profile
Advanced communications documents
A global initiative to provide the mobile industry with a common universal profile that enables mobile operators to deploy an interoperable RCS service.
Modernises voice/text experience provide a richer, simpler, and more fluid mobile experience.
Regularly updated, specifications.

11. Future Networks Programme
Questions and Answers
Future Networks Programme
Shaping the next generation in mobile

12. Appendix – TSG TERMINAL STEERING GROUP
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

13. 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

14. 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

15. Appendix – DCS FUTURE NETWORKS
The GSMA’s Future Networks 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
DEVICE CONFIGURATION SERVER
Project group under Future Networks programme, being run in conjunction with TSG work groups
Published N 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