Scribd
Upload
122 views

Invigo Role of Device MNGT

The document discusses the role of device management in the rollout of Rich Communication Services (RCS). It notes that RCS requires configuring over 100 parameters on devices and supports auto-configuration over both 3G and WiFi networks according to standards from GSMA and OMA. Device management systems must support various client versions to handle evolving RCS specifications and provide seamless provisioning of subscribers to enable an experience comparable to over-the-top messaging applications.

Uploaded by

elcorino
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
122 views

Invigo Role of Device MNGT

The document discusses the role of device management in the rollout of Rich Communication Services (RCS). It notes that RCS requires configuring over 100 parameters on devices and supports auto-configuration over both 3G and WiFi networks according to standards from GSMA and OMA. Device management systems must support various client versions to handle evolving RCS specifications and provide seamless provisioning of subscribers to enable an experience comparable to over-the-top messaging applications.

Uploaded by

elcorino
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

The Role of Device Management

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

Agenda

The need for Over-The-Air provisioning


Standards and specifications (OMA, GSMA)
Auto-configuration
g
mechanisms ((3G,, WiFi,, secondaryy device access))
The Impact of Evolving Specifications
Conclusion

Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - Confidential

The Need for Over-The-Air Provisioning

More than 100 p


parameters to configure
g
Dynamic username/password generated by IMS system upon
provisioning
Possibility to configure an RCSe only APN for roaming considerations - a
reall advantage
d
t
over OTT competitors
tit
Aim is to give the user the impression that the RCS service is working out
of the box
Device Management system shall trigger
9 subscriber provisioning (get susbcribers IMS credentials)
9 device configuration

Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - Confidential

The Need for Over-The-Air Provisioning

Different
Diff
t Use
U C
Cases ffor O
Over Th
The Ai
Air configuration
fi
ti :
9
9
9
9
9

First registration of a new subscriber


Existing subscriber changing device
Existing subscriber changing swapping SIM
Single or Mass configuration update (RCSe parameter change)
Deactivation of the client (deprovisioned subscriber)

RCS should offer similar or better features than OTT competitors


9 User
U
experience
i
shall
h ll b
be as simple
i l fully
f ll seamless
l
configuration
fi
ti process.
Unlike OTT competitor, no need for any manual setup, Its just there. It just
works
9 Service availability over Wifi and 3G both 3G and Wifi Over The Air
provisioning shall be supported

Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - Confidential

Standards and Specifications (OMA, GSMA)

Two standardized auto-configuration


g
mechanisms:
9 Based on Hypertext Transfer Protocol (HTTP/HTTPS)
9 Based on OMA-DM management object

OMA-CP not adapted to large number of parameters

Parameters independent of provisioning protocol

Autoconfiguration
g
mechanism according
g to the latest RCS specifications
p
RCS 5.1 published in Aug 2012 (includes Provisioning over WiFi)

Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - Confidential

Standards and Specifications (OMA, GSMA)

HTTP/HTTPS auto
auto-configuration
configuration protocol (GSMA)
9
9
9
9

A completely transparent configuration procedure to the RCS user


Client initiated connection only (pre-defined URL mcc.mnc etc.)
Simple autodetection mechanism
3G and WiFi supported

OMA-DM protocol (Open Mobile Alliance)


9 Requires a factory bootstrap (pre-loaded at factory phase)
9 Network and client initiated connection
9 3G only

Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - Confidential

Auto-configuration over 3G

Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - Confidential

Auto-configuration over WiFi


Secondary
y Device

Configuration over WiFi is essential to compete with OTT players


Requires authentication (no MSISDN enrichment, no RADIUS)
Subscriber authenticated with a token/OneTimePassword mechanism
Might require user intervention (client dependent)

Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - Confidential

The 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
g
files based on supported
pp
RCS specifications
p
version))
RCS 1.0

RCS 2.0

RCS 3.0

RCS5.0

RCS 4.0

RCS5.1

Apr 2012
Aug 2012
2008

2009

2010

2011

RCSe1.1 RCSe1.2 RCSe1.2.1 RCSe1.2.2

Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - Confidential

Conclusion
Many players in the IP communications world, but many reasons to
believe in RCS:
9
9
9
9

Interoperability (across devices and networks)


Reach (embedded for many OEMs + downladable Android and iPhone client)
Ease of Use (no need to install,
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 device

Role of MDM is essential for a


smooth launch
Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - Confidential

10

You might also like