1、 ETSI TS 133 203 V5.6.0 (2003-06)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);3G security;Access security for IP-based services(3GPP TS 33.203 version 5.6.0 Release 5)GLOBAL SYSTEM FOR MOBILE COMMUNICATIONSRETSI ETSI
2、TS 133 203 V5.6.0 (2003-06) 1 3GPP TS 33.203 version 5.6.0 Release 5 Reference RTS/TSGS-0333203v560 Keywords GSM, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif
3、 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in
4、contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the do
5、cument may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: editoretsi.org Copyright Notification No part may be
6、reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2003. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its
7、Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 133 203 V5.6.0 (2003-06) 2 3GPP TS 33.203 version 5.6
8、.0 Release 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellec
9、tual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investiga
10、tion, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specificat
11、ion (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
12、The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp . ETSI ETSI TS 133 203 V5.6.0 (2003-06) 3 3GPP TS 33.203 version 5.6.0 Release 5 Contents Intellectual Property Rights2 Foreword.2 Foreword.5 1 Scope 6 2 References 6 3 Definiti
13、ons, symbols and abbreviations .7 3.1 Definitions7 3.3 Abbreviations .7 4 Overview of the security architecture.8 5 Security features.10 5.1 Secure access to IMS10 5.1.1 Authentication of the subscriber and the network.10 5.1.2 Re-Authentication of the subscriber .11 5.1.3 Confidentiality protection
14、 .11 5.1.4 Integrity protection .11 5.2 Network topology hiding11 6 Security mechanisms12 6.1 Authentication and key agreement .12 6.1.1 Authentication of an IM-subscriber12 6.1.2 Authentication failures14 6.1.2.1 User authentication failure 14 6.1.2.2 Network authentication failure15 6.1.2.3 Incomp
15、lete authentication .16 6.1.3 Synchronization failure.16 6.1.4 Network Initiated authentications .17 6.1.5 Integrity protection indicator 17 6.2 Confidentiality mechanisms .17 6.3 Integrity mechanisms .18 6.4 Hiding mechanisms 18 7 Security association set-up procedure 18 7.1 Security association pa
16、rameters .19 7.2 Set-up of security associations (successful case)21 7.3 Error cases in the set-up of security associations .23 7.3.1 Error cases related to IMS AKA.23 7.3.1.1 User authentication failure 23 7.3.1.2 Network authentication failure23 7.3.1.3 Synchronisation failure .23 7.3.1.4 Incomple
17、te authentication .23 7.3.2 Error cases related to the Security-Set-up.23 7.3.2.1 Proposal unacceptable to P-CSCF.23 7.3.2.2 Proposal unacceptable to UE.23 7.3.2.3 Failed consistency check of Security-Set-up lines at the P-CSCF 24 7.4 Authenticated re-registration24 7.4.1 Void 24 7.4.1a Management o
18、f security associations in the UE .24 7.4.2 Void 25 7.4.2a Management of security associations in the P-CSCF .25 7.5 Rules for security association handling when the UE changes IP address .26 8 ISIM .26 8.1 Requirements on the ISIM application.26 8.2 Sharing security functions and data with the USIM
19、.26 ETSI ETSI TS 133 203 V5.6.0 (2003-06) 4 3GPP TS 33.203 version 5.6.0 Release 5 Annex A: Void 28 Annex B: Void 29 Annex C: Void 30 Annex D: Void 31 Annex E: Void 32 Annex F: Void 33 Annex G (informative): Management of sequence numbers 34 Annex H (normative): The use of “Security Mechanism Agreem
20、ent for SIP Sessions“ 21 for security mode set-up35 Annex I (normative): Key expansion functions for IPsec ESP .37 Annex J (informative): Recommendations to protect the IMS from UEs bypassing the P-CSCF .38 Annex J (informative): Change history .39 History 41 ETSI ETSI TS 133 203 V5.6.0 (2003-06) 5
21、3GPP TS 33.203 version 5.6.0 Release 5 Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the c
22、ontents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved
23、 document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 133 203 V5.6.0 (2003-06) 6 3GPP TS
24、 33.203 version 5.6.0 Release 5 1 Scope The scope for this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system. The IMS in UMTS will support IP Multimedia applications such as video, audio a
25、nd multimedia conferences. 3GPP has chosen SIP, Session Initiation Protocol, as the signaling protocol for creating and terminating Multimedia sessions, cf. 6. This specification only deals with how the SIP signaling is protected between the subscriber and the IMS, how the subscriber is authenticate
26、d and how the subscriber authenticates the IMS. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) or no
27、n-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same R
28、elease as the present document. 1 3GPP TS 33.102: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Security Architecture“. 2 3GPP TS 22.228: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Ser
29、vice Requirements for the IP Multimedia Core Network“. 3 3GPP TS 23.228: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia (IM) Subsystem“. 4 3GPP TS 21.133: “3rd Generation Partnership Project; T Technical Specification Group Services and
30、System Aspects; Security Threats and Requirements “. 5 3GPP TS 33.210: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Network domain security; IP network layer security“. 6 IETF RFC 3261 “SIP: Session Initiation Protocol“. 7 3GPP TS 21.90
31、5: “3rd Generation Partnership Project: Technical Specification Group Services and System Aspects; Vocabulary for 3GPP specifications“. 8 3GPP TS 24.229: “3rd Generation Partnership Project: Technical Specification Group Core Network; IP Multimedia Call Control Protocol based on SIP and SDP“. 9 3GPP
32、 TS 23.002: “3rd Generation Partnership Project: Technical Specification Group Services and System Aspects, Network Architecture“. 10 3GPP TS 23.060: “3rd Generation Partnership Project: Technical Specification Group Services and System Aspects, General Packet Radio Service (GPRS); Service Descripti
33、on“. 11 3GPP TS 24.228: “3rd Generation Partnership Project: Technical Specification Group Core Network; Signalling flows for the IP multimedia call control based on SIP and SDP“. 12 IETF RFC 2617 (1999) “HTTP Authentication: Basic and Digest Access Authentication“. 13 IETF RFC 2406 (1998) “IP Encap
34、sulating Security Payload (ESP)“. 14 IETF RFC 2401 (1998) “Security Architecture for the Internet Protocol“. ETSI ETSI TS 133 203 V5.6.0 (2003-06) 7 3GPP TS 33.203 version 5.6.0 Release 5 15 IETF RFC 2403 (1998) “The Use of HMAC-MD5-96 within ESP and AH“. 16 IETF RFC 2404 (1998) “The Use of HMAC-SHA
35、-1-96 within ESP and AH“. 17 IETF RFC 3310 (2002): “HTTP Digest Authentication Using AKA“. April, 2002. 18 IETF RFC 3041 (2001): “Privacy Extensions for Stateless Address Autoconfiguration in IPv6“. 19 IETF RFC 2402 (1998): “IP Authentication Header“. 20 IETF RFC 2451 (1998): “The ESP CBC-Mode Ciphe
36、r Algorithms “. 21 IETF RFC 3329 (2002): “Security Mechanism Agreement for the Session Initiation Protocol (SIP)“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply. Authenticated (re-) registration: A registr
37、ation i.e. a SIP register is sent towards the Home Network which will trigger a authentication of the IMS subscriber i.e. a challenge is generated and sent to the UE. Confidentiality: The property that information is not made available or disclosed to unauthorised individuals, entities or processes.
38、 Data integrity: The property that data has not been altered in an unauthorised manner. Data origin authentication: The corroboration that the source of data received is as claimed. Entity authentication: The provision of assurance of the claimed identity of an entity. Key freshness: A key is fresh
39、if it can be guaranteed to be new, as opposed to an old key being reused through actions of either an adversary or authorised party. ISIM IM Subscriber Identity Module: For the purposes of this document the ISIM is a term that indicates the collection of IMS security data and functions on a UICC. Th
40、e ISIM may be a distinct application on the UICC. 3.3 Abbreviations For the purposes of the present document, the following abbreviations apply, 7 contains additional applicable abbreviations: AAA Authentication Authorisation Accounting AKA Authentication and key agreement CSCF Call Session Control
41、Function HSS Home Subscriber Server IM IP Multimedia IMPI IM Private Identity IMPU IM Public Identity IMS IP Multimedia Core Network Subsystem ISIM IM Services Identity Module MAC Message Authentication CodeME Mobile Equipment SA Security Association SEG Security GatewaySDP Session Description Proto
42、col SIP Session Initiation Protocol UA User Agent ETSI ETSI TS 133 203 V5.6.0 (2003-06) 8 3GPP TS 33.203 version 5.6.0 Release 5 4 Overview of the security architecture In the PS domain, the service is not provided until a security association is established between the mobile equipment and the netw
43、ork. IMS is essentially an overlay to the PS-Domain and has a low dependency of the PS-domain. Consequently a separate security association is required between the multimedia client and the IMS before access is granted to multimedia services. The IMS Security Architecture is shown in the following f
44、igure. IMS authentication keys and functions at the user side shall be stored on a UICC. It shall be possible for the IMS authentication keys and functions to be logically independent to the keys and functions used for PS domain authentication. However, this does not preclude common authentication k
45、eys and functions from being used for IMS and PS domain authentication according to the guidelines given in section 8. For the purposes of this document the ISIM is a term that indicates the collection of IMS security data and functions on a UICC. Further information on the ISIM is given in section
46、8. Figure 1: The IMS security architecture There are five different security associations and different needs for security protection for IMS and they are numbered 1,2, 3, 4 and 5 in figure 1 where: 1. Provides mutual authentication. The HSS delegates the performance of subscriber authentication to
47、the S-CSCF. However the HSS is responsible for generating keys and challenges. The long-term key in the ISIM and the HSS is associated with the IMPI. The subscriber will have one (network internal) user private identity (IMPI) and at least one external user public identity (IMPU). 2. Provides a secu
48、re link and a security association between the UE and a P-CSCF for protection of the Gm reference point. Data origin authentication is provided i.e. the corroboration that the source of data received is as claimed. For the definition of the Gm reference point cf. TS23.002 9. 3. Provides security wit
49、hin the network domain internally for the Cx-interface. This security association is covered by TS 33.210 5. For the definition of the Cx-interface cf. TS23.002 9. 4. Provides security between different networks for SIP capable nodes. This security association is covered by TS 33.210 5. This security association is only applicable when the P-CSCF resides in the VN and if the P-CSCF resides in the HN then bullet point number five below applies, cf. also Figure 2 and Figure 3. 5. Provides security within the network
