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
1
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
2
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 susbcriber’s IMS credentials)
9 device configuration
Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - Confidential
3
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, “It’s 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
4
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
5
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
6
Auto-configuration over 3G
Ref : IGO.PRE.2066.IH.V3.0 (10.2012) - Confidential
7
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
8
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
9
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