Download RCS Common Core 1.1 Service Description Document

GSM Association
Non-confidential
Official Document RCC.61 - RCS Common Core 1.1 Service Description Document
R14-1-4 OM Devices containing a SIM which is associated with the user’s RCS identity
shall use any available SIM-based authentication mechanism in preference of
a non-SIM based authentication mechanism.
R14-1-5 User interaction to ensure security solutions shall be minimized.
R14-1-6 If manual user interaction is required, this interaction shall be limited to a single
one time experience and not be repeated, in case – but not limited to – device
re-provisioning.
R14-1-7 If manual user interaction is required, for native implementations any user
interaction shall be performed on one single screen (or an intuitive flow of
screens).
US14-2 As an operator, I want to customize the enhanced security function.
R14-2-1 The security solution shall offer the option for the operator to enable or disable
the function with appropriate security control.
R14-2-1-1 Enable or disable over the air.
R14-2-1-2 Enable or disable for selected devices.
R14-2-2 If user interaction is required, the user shall be guided to accomplish the
interaction in a way that RCS use of the primary identity is enabled in a secure
way after the set-up process.
US14-3 As an operator, I want to ensure that traffic and content generated by an RCS
identity is generated by that identity’s true user.
R14-3-1 Second Party and Third Party applications shall inherit the identity of the stack
therefore whilst API access may be controlled (not addressed here) no
additional RCS authentication shall be required from second and third party
applications.
R14-3-2 All traffic generated by an identity shall be identifiable as such.
14.3 Technical Information
The technical implementation of RCS involves a number of technologies on the user network
interface. Encryption, user authentication and access authorization is applied by the client
and the network on a per protocol basis (e.g. SIP, HTTP, IMAP). The level of security for the
individual technologies depend on the selection of the mean of authentication applied in the
technical specification.
14.3.1
User Authentication
The following main user authentication and methods are used in RCS.
R14-4-1 User Authentication via the UICC based Authentication and Key Agreement
protocol (AKA). This authentication protocol comes with a high level of security
based on shared secrets exchanged between the UICC and the network
authentication centre. As a result of the initial authentication session keys are
agreed which are used to secure the UNI signalling flow.
V2.0
Page 145 of 166