1、 TIA DOCUMENT All-IP Core Network Multimedia Domain IP Multimedia Subsystem Cx Interface Signaling Flows and Message Contents TIA-873.005 DECEMBER 2003 TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Industry Association represents the communications sector of Copyright Telecommunicat
2、ions Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers a
3、nd purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Publications shall not in any respect preclude any member or non-member of TIA fro
4、m manufacturing or selling products not conforming to such Publications. Neither shall the existence of such Documents preclude their voluntary use by non-TIA members, either domestically or internationally. TIA DOCUMENTS TIA Documents contain information deemed to be of technical value to the indus
5、try, and are published at the request of the originating Committee without necessarily following the rigorous public review and resolution of comments which is a procedural part of the development of a American National Standard (ANS). Further details of the development process are available in the
6、TIA Engineering Manual, located at http:/www.tiaonline.org/standards/sfg/engineering_manual.cfm TIA Documents shall be reviewed on a five year cycle by the formulating Committee and a decision made on whether to reaffirm, revise, withdraw, or proceed to develop an American National Standard on this
7、subject. Suggestions for revision should be directed to: Standards CWTS China Wireless Telecommunications Standards group, 4 China; ETSI European Telecommunications Standards Institute; ATIS, USA; TTA - Telecommunications 5 Technology Association, Korea; and TTC Telecommunication Technology Committe
8、e, Japan), which 6 have granted license for reproduction and for use by 3GPP2 and its Organizational Partners.” 7 8 Revision History 9 10 Revision Changes Date 0 Initial Publication December 2003 11 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for Resal
9、eNo reproduction or networking permitted without license from IHS-,-,-TIA-873-005 1 1 Scope 1 This Specification specifies the interactions between the HSS (Home Subscriber Server) and the CSCF 2 (Call Session Control Functions), referred to as the Cx interface. 3 This document addresses the signall
10、ing flows for the Cx interface. 4 The IP Multimedia (IM) Subsystem stage 2 is specified in 1 and the protocol for the IP multimedia call 5 control based on SIP and SDP are specified in 8. 6 2 References 7 1 TIA-873-002: “IP Multimedia (IM) Subsystem Stage 2”. 8 3GPP2 X.S0013-002: “IP Multimedia (IM)
11、 Subsystem Stage 2”. 9 2 Void 10 3 3GPP2 S.S0086-0: “3GPP2 IMS Security Framework”. 11 4 TIA/TSB-151: IP Network Reference Model (NRM) for cdma20001Spread Spectrum Systems, 12 December 2003. 13 3GPP2 S.R0037-0, “3GPP2 All-IP Network Architecture Model Version 2.0, May 14, 2002”. 14 5 TIA-873-006: “C
12、x Interface based on Diameter Protocol; Protocol details”. 15 3GPP2 X.S0013-006: “Cx Interface based on Diameter Protocol; Protocol details”. 16 6 TIA-873-003: “IP Multimedia Subsystem IP Multimedia Call Model; Stage 2”. 17 3GPP2 X.S0013-003: “IP Multimedia Subsystem IP Multimedia Call Model; Stage
13、2”. 18 7 IETF RFC 2045, “Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet 19 Message Bodies”, November 1996. 20 8 TIA-873-004: “IP Multimedia Call Control Protocol Based on SIP and SDP Stage 3”. 21 3GPP2 X.S0013-004: “IP Multimedia Call Control Protocol Based on SIP and SDP
14、Stage 3”. 22 9 IETF RFC 3588, “Diameter Base Protocol”, September 2003. 23 3 Definitions, symbols and abbreviations 24 3.1 Definitions 25 For the purposes of the present document, the following terms and definitions apply. 26 IP Multimedia session: IP Multimedia session and IP Multimedia call are tr
15、eated as equivalent in this 27 specification. 28 1cdma2000 is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. When applied to goods and services, the cdma2000mark certifies their compliance with cdma2000standards. G
16、eographically (and as of the date of publication), cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States. Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking per
17、mitted without license from IHS-,-,-TIA-873-005 2 3.2 Abbreviations 1 For the purposes of the present document, the following abbreviations apply: 2 AVP Attribute Value Pair 3 CSCF Call Session Control Function 4 HSS Home Subscriber Server 5 IE Information Element 6 IP Internet Protocol 7 I-CSCF Int
18、errogating CSCF 8 IM IP Multimedia 9 IMS IP Multimedia Subsystem 10 LIA Location Information Answer 11 LIR Location Information Request 12 MAA Multimedia Authentication Answer 13 MAR Multimedia Authentication Request 14 MO Mobile Originating 15 MT Mobile Terminating16 P-CSCF Proxy CSCF 17 PPA Push P
19、rofile Answer 18 PPR Push Profile Request 19 RTA Registration Termination Answer 20 RTR Registration Termination Request 21 SAA Server Assignment Answer 22 SAR Server Assignment Request23 SIP Session Initiation Protocol 24 S-CSCF Serving CSCF 25 UAA User Authorization Answer 26 UAR User Authorizatio
20、n Request 27 4 Main Concept 28 This document presents the Cx interface related functional requirements of the communicating entities. 29 It gives a functional classification of the procedures and describes the procedures and message parameters. 30 Error handling flows, protocol version identificatio
21、n and procedures are also included. 31 5 General Architecture 32 This clause further specifies the architectural assumptions associated with the Cx reference point, building 33 on 1. 34 5.1 Functional requirements of network entities 35 5.1.1 Functional requirements of P-CSCF 36 There is no requirem
22、ent for the interaction between the P-CSCF and the HSS. 37 5.1.2 Functional requirements of I-CSCF 38 The I-CSCF communicates with the HSS over the Cx interface. 39 For functionality of the I-CSCF refer to 4. 40 Copyright Telecommunications Industry Association Provided by IHS under license with EIA
23、Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-005 3 5.1.3 Functional requirements of S-CSCF 1 The S-CSCF communicates with the HSS over the Cx interface. 2 For functionality of the S-CSCF refer to 4. 3 5.1.4 Functional requirements of HSS 4 The HSS commun
24、icates with the I-CSCF and the S-CSCF over the Cx interface. 5 5.1.5 Functional classification of Cx interface procedures 6 Operations on the Cx interface are classified in functional groups: 7 1. Location management procedures 8 - The operations regarding registration and de-registration. 9 - Locat
25、ion retrieval operation. 10 2. User data handling procedures 11 - The download of user information during registration and to support recovery mechanisms. 12 - Operations to support the updating of user data. 13 3. User authentication procedures 14 6 Procedure Descriptions 15 In the tables that desc
26、ribe the information elements transported by each command, each Information 16 Element is marked as (M) Mandatory, (C) Conditional or (O) Optional. A mandatory information element 17 shall always be present. A conditional information shall be present if certain conditions are fulfilled; if 18 those
27、conditions are not fulfilled it shall be absent. An optional information element may be present or 19 absent in the command, at the discretion of the application at the sending entity. 20 6.1 Location management procedures 21 6.1.1 User registration status query 22 This procedure is used between the
28、 I-CSCF and the HSS during SIP registrations. The procedure is invoked 23 by the I-CSCF, corresponds to the combination of the functional level operations Cx-Query and Cx-Select-24 Pull (see 1) and is used: 25 - To authorize the registration of the user, checking multimedia subsystem access permissi
29、ons and 26 roaming agreements. 27 - To perform a first security check, determining whether the public and private identities sent in the 28 message belong to the same user. 29 - To obtain either the S-CSCF where the user is registered or unregistered (i.e. registered as a 30 consequence of a termina
30、ting call or there is a S-CSCF keeping the user profile stored), or the list of 31 capabilities that the S-CSCF has to support. 32 This procedure is mapped to the commands User-Authorization-Request/Answer in the Diameter 33 application specified in 5. Tables 6.1.1.1 and 6.1.1.2 detail the involved
31、information elements. 34 Table 6.1.1.1 : User registration status query 35 Information Mapping to Cat. Description Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-005 4
32、element name Diameter AVP Public User Identity (See 7.2) Public-Identity M User public identity to be registered Visited Network Identifier (See 7.1) Visited-Network-Identifier M Identifier that allows the home network to identify the visited network Type of Authorization (See 7.14) User-Authorizati
33、on-Type C Type of authorization requested by the I-CSCF. If the request corresponds to a de-registration, i.e. Expires field in the REGISTER method is equal to zero, this AVP shall be present in the command and the value shall be set to DE_REGISTRATION. If the request corresponds to an initial regis
34、tration or a re-registration, i.e. Expires field in the REGISTER method is not equal to zero then this AVP may be absent from the command. If present its value shall be set to REGISTRATION. If the request corresponds to an initial registration or a re-registration, and the I-CSCF explicitly queries
35、the S-CSCF capabilities, then this AVP shall be present in the command and the value shall be set to REGISTRATION_AND_CAPABILITIES. The I-CSCF shall use this value when the users current S-CSCF, which is stored in the HSS, cannot be contacted and a new S-CSCF needs to be selected. Private User Ident
36、ity (See 7.3) User-Name M User private identity Routing Information (See 7.13) Destination-Host, Destination-Realm C If the I-CSCF knows HSS name Destination-Host AVP shall be present in the command. Otherwise, only Destination-Realm AVP shall be present and the command shall be routed to the next D
37、iameter node. 1 Table 6.1.1.2 : User registration status response 2 Information element name Mapping to Diameter AVP Cat. Description Result (See 7.6) Result-Code / Experimental-Result M Result of the operation Result-Code AVP shall be used for errors defined in the Diameter Base Protocol. Experimen
38、tal-Result AVP shall be used for Cx errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. S-CSCF capabilities (See 7.5) Server-Capabilities O Required capabilities of the S-CSCF to be assigned to the user. S-CSCF
39、 Name (See 7.4) Server-Name C Name of the assigned S-CSCF. 3 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-005 5 6.1.1.1 Detailed behaviour 1 The HSS shall, in the fol
40、lowing order (if there is an error in any of the following steps the HSS shall stop 2 processing and return the corresponding error code, see 5): 3 1. Check that the user exists in the HSS. If not, Experimental-Result-Code shall be set to 4 DIAMETER_ERROR_USER_UNKNOWN. 5 2. Check that the private an
41、d public identities received in the request belong to the same user. If not, 6 Experimental-Result-Code shall be set to DIAMETER_ERROR _IDENTITIES_DONT_MATCH. 7 3. Check whether the public identity received in the request is barred for the establishment of multimedia 8 sessions. 9 + If it is, the HS
42、S shall check whether there are other non-barred public identities to be implicitly 10 registered with that one. 11 - If so, continue to step 4. 12 - If not, Result-Code shall be set to DIAMETER_AUTHORIZATION_REJECTED. 13 4. Check the User-Authorization-Type received in the request: 14 + If it is RE
43、GISTRATION or if User-Authorization-Type is absent from the request, the HSS shall 15 check that the user is allowed to roam in the visited network (if not, Experimental-Result-Code shall 16 be set to DIAMETER_ERROR _ROAMING_NOT_ALLOWED and processing should stop) and 17 authorized to register (if n
44、ot, Result-Code shall be set to 18 DIAMETER_AUTHORIZATION_REJECTED and processing should stop). Continue to step 5. 19 + If it is DE_REGISTRATION, the HSS may not perform any check regarding roaming. Continue to 20 step 5. 21 + If it is REGISTRATION_AND_CAPABILITIES, the HSS shall check that the use
45、r is allowed to 22 roam in the visited network (if not, Experimental-Result-Code shall be set to DIAMETER_ERROR 23 _ROAMING_NOT_ALLOWED) and authorized to register (if not Result-Code shall be set to 24 DIAMETER_AUTHORIZATION_REJECTED). The HSS shall return the list of S-CSCF 25 capabilities, which
46、enables the I-CSCF to select an S-CSCF. The returned capabilities must satisfy 26 the most restrictive service profile of the user. The list of capabilities may be empty, to indicate to 27 the I-CSCF that it can select any available S-CSCF. Result-Code shall be set to 28 DIAMETER_SUCCESS. The HSS sh
47、all not return any S-CSCF name. Stop processing. 29 5. Check the state of the public identity received in the request: 30 + If it is registered, the HSS shall return the stored S-CSCF name. No S-CSCF capabilities shall be 31 present in the response. In case the User-Authorization-Type is equal to RE
48、GISTRATION, 32 Experimental-Result-Code shall be set to DIAMETER_SUBSEQUENT_REGISTRATION. If User-33 Authorization-Type is equal to DE_REGISTRATION, Result-Code shall be set to 34 DIAMETER_SUCCESS. 35 +If it is unregistered (i.e registered as a consequence of a terminating call or there is a S-CSCF
49、keeping 36 the user profile stored) and User-Authorization-Type is equal to DE_REGISTRATION, Result-Code 37 shall be set to DIAMETER_SUCCESS. If the User-Authorization-Type is equal to REGISTRATION, 38 then: 39 o If the selection of a new S-CSCF is not necessary, the HSS shall return the stored S-CSCF 40 name and the Experimental-Result-Code set to 41 DIAMETER_SUBSEQUENT_REGISTRA
