Invigo Role of Device Mngt

10
The Role of Device Management in in RCS Roll-Out RCS, VoLTE, and Beyond Slovenia, Oct 2012 Ibtissam HAJJAR INVIGO 1 Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - Confidential

description

Paper from Device Manager

Transcript of Invigo Role of Device Mngt

The Role of Device Management in in RCS Roll-OutRCS, VoLTE, and BeyondSlovenia, Oct 2012Ibtissam HAJJARINVIGO1 Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - ConfidentialAgenda The need for Over-The-Air provisioning Standards and specifications (OMA, GSMA) Auto-configuration mechanisms (3G, WiFi, secondary device access) g ( , , y ) The Impact of Evolving Specifications Conclusion2 Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - ConfidentialThe Need for Over-The-Air Provisioning More than 100 parameters to configure p g Dynamic username/password generated by IMS system upon provisioning provisioning Possibility to configure an RCSe only APN for roaming considerations - a l d t OTT tit real advantage over OTT competitors Aim is to give the user the impression that the RCS service is working out of the box Device Management systemshall trigger Device Management system shall trigger subscriber provisioning (get susbcribers IMS credentials) device configuration3 Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - ConfidentialThe Need for Over-The-Air ProvisioningDiff t U C f O Th Ai fi tiDifferent Use Cases for Over The Air configuration : First registration of a new subscriber Existingsubscriber changing device Existingsubscriber changing swappingSIM Single or Mass configuration update (RCSe parameter change) Deactivationof the client (deprovisioned subscriber) RCS should offer similar or better features than OTT competitors U i h ll b i l f ll l fi tiUser experience shall be as simple fully seamless configuration process. Unlike OTT competitor, no need for any manual setup, Its just there. It just works Service availability over Wifi and 3G both 3G and Wifi Over The Air provisioningshall be supported4 Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - ConfidentialStandards and Specifications (OMA, GSMA) Two standardized auto-configuration mechanisms: g Basedon Hypertext Transfer Protocol (HTTP/HTTPS) Basedon OMA-DM management object OMA-CP not adapted to large number of parameters Parameters independent of provisioningprotocol Autoconfigurationmechanismaccording to the latest RCS specifications g g pRCS 5.1 published in Aug 2012 (includes Provisioning over WiFi)5 Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - ConfidentialStandards and Specifications (OMA, GSMA) HTTP/HTTPS auto-configuration protocol (GSMA) HTTP/HTTPS auto configuration protocol (GSMA) A completely transparent configuration procedure to the RCS user Client initiated connection only (pre-defined URL mcc.mnc etc.) Simple autodetection mechanismSimple autodetection mechanism 3G and WiFi supported OMA-DM protocol (Open Mobile Alliance) Requires a factory bootstrap (pre-loaded at factory phase) Network and client initiated connection 3G only6 Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - ConfidentialAuto-configuration over 3G 7 Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - ConfidentialAuto-configuration over WiFiSecondary Device y Configuration over WiFi is essential to compete with OTT players Requires authentication (no MSISDN enrichment, no RADIUS) Requires authentication (no MSISDN enrichment, no RADIUS) Subscriber authenticated with a token/OneTimePassword mechanism Might require user intervention (client dependent)8 Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - ConfidentialThe Impact of the Evolving Specifications Changing RCS/RCSe specifications is leading to delays in service launch High reactivity and cooperation required from OEMs, and operators to implement changes Device Management platform shall handle various client versions (different configuration files based on supported RCS specifications version)RCS5.0 RCS5.1RCS 4.0 RCS 3.0 RCS 2.0 RCS 1.0g pp p )2011Aug 20122010 2009 2008Apr 2012RCSe1.1 RCSe1.2.1 RCSe1.2.2 RCSe1.29 Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - ConfidentialConclusion Many players in the IP communications world, but many reasons to believe in RCS: believe in RCS: Interoperability (across devices and networks) Reach (embedded for many OEMs + downladable Android and iPhone client) Ease of Use (no need to install seamless configuration)Ease of Use (no need to install, seamless configuration) Quality of Service (More adapted to QoS vs Best Effort for other applications) RCS is very device dependent with many parameters to be configured on the deviceRole of MDM is essential for a smooth launch10smooth launchRef : IGO.PRE.2066.IH.V3.0 (10.2012) - Confidential