1、 TIA DOCUMENT All-IP Core Network Multimedia Domain Cx Interface Based on the Diameter Protocol; Protocol Details TIA-873.006 DECEMBER 2003 TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Industry Association represents the communications sector of Copyright Telecommunications Industr
2、y 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 and purchaser
3、s, 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 from manufactur
4、ing 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 industry, and are
5、 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 TIA Engineer
6、ing 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 subject. Sug
7、gestions for revision should be directed to: Standards 2 Protocol Details 3 Contents 4 5 1 Scope . 1 6 2 References . 1 7 3 Definitions, symbols and abbreviations 1 8 3.1 Definitions. 1 9 3.2 Abbreviations 2 10 4 General. 2 11 5 Use of the Diameter base protocol. 2 12 5.1 Securing Diameter Messages
8、2 13 5.2 Accounting functionality . 2 14 5.3 Use of sessions 3 15 5.4 Transport protocol 3 16 5.5 Routing considerations. 3 17 5.6 Advertising Application Support . 3 18 6 Diameter application for Cx interface . 3 19 6.1 Command-Code values . 4 20 6.1.1 User-Authorization-Request (UAR) Command . 4 2
9、1 6.1.2 User-Authorization-Answer (UAA) Command 5 22 6.1.3 Server-Assignment-Request (SAR) Command 5 23 6.1.4 Server-Assignment-Answer (SAA) Command. 6 24 6.1.5 Location-Info-Request (LIR) Command 6 25 6.1.6 Location-Info-Answer (LIA) Command. 7 26 6.1.7 Multimedia-Auth-Request (MAR) Command 7 27 6.
10、1.8 Multimedia-Auth-Answer (MAA) Command 7 28 6.1.9 Registration-Termination-Request (RTR) Command. 8 29 6.1.10 Registration-Termination-Answer (RTA) Command. 8 30 6.1.11 Push-Profile-Request (PPR) Command 8 31 6.1.12 Push-Profile-Answer (PPA) Command 9 32 6.2 Experimental-Result-Code AVP values . 9
11、 33 6.2.1 Success . 9 34 6.2.1.1 DIAMETER_FIRST_REGISTRATION (2001) 9 35 6.2.1.2 DIAMETER_SUBSEQUENT_REGISTRATION (2002). 10 36 6.2.1.3 DIAMETER_UNREGISTERED_SERVICE (2003). 10 37 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or
12、 networking permitted without license from IHS-,-,-TIA-873-006 ii 6.2.1.4 DIAMETER_SUCCESS_SERVER_NAME_NOT_STORED (2004) 10 1 6.2.1.5 DIAMETER_SERVER_SELECTION (2005) 10 2 6.2.2 Permanent Failures . 10 3 6.2.2.1 DIAMETER_ERROR_USER_UNKNOWN (5001). 10 4 6.2.2.2 DIAMETER_ERROR_IDENTITIES_DONT_MATCH (5
13、002) . 10 5 6.2.2.3 DIAMETER_ERROR_IDENTITY_NOT_REGISTERED (5003) . 10 6 6.2.2.4 DIAMETER_ERROR_ROAMING_NOT_ALLOWED (5004) . 10 7 6.2.2.5 DIAMETER_ERROR_IDENTITY_ALREADY_REGISTERED (5005) 11 8 6.2.2.6 DIAMETER_ERROR_AUTH_SCHEME_NOT_SUPPORTED (5006) 11 9 6.2.2.7 DIAMETER_ERROR_IN_ASSIGNMENT_TYPE (500
14、7) 11 10 6.2.2.8 DIAMETER_ERROR_TOO_MUCH_DATA (5008). 11 11 6.2.2.9 DIAMETER_ERROR_NOT_SUPPORTED_USER_DATA (5009) 11 12 6.3 AVPs 11 13 6.3.1 Visited-Network-Identifier AVP 12 14 6.3.2 Public-Identity AVP .12 15 6.3.3 Server-Name AVP 12 16 6.3.4 Server-Capabilities AVP 13 17 6.3.5 Mandatory-Capabilit
15、y AVP 13 18 6.3.6 Optional-Capability AVP . 13 19 6.3.7 User-Data AVP. 13 20 6.3.8 SIP-Number-Auth-Items AVP 13 21 6.3.9 SIP-Authentication-Scheme AVP. 13 22 6.3.10 SIP-Authenticate AVP 13 23 6.3.11 SIP-Authorization AVP 13 24 6.3.12 SIP-Authentication-Context AVP. 14 25 6.3.13 SIP-Auth-Data-Item AV
16、P. 14 26 6.3.14 SIP-Item-Number AVP 14 27 6.3.15 Server-Assignment-Type AVP. 14 28 6.3.16 Deregistration-Reason AVP . 15 29 6.3.17 Reason-Code AVP. 15 30 6.3.18 Reason-Info AVP 16 31 6.3.19 Charging-Information AVP 16 32 6.3.20 Primary-Event-Charging-Function-Name AVP . 16 33 6.3.21 Secondary-Event-
17、Charging-Function-Name AVP . 16 34 6.3.22 Primary-Charging-Collection-Function-Name AVP 16 35 6.3.23 Secondary-Charging-Collection-Function-Name AVP 16 36 6.3.24 User-Authorization-Type AVP. 16 37 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleN
18、o reproduction or networking permitted without license from IHS-,-,-TIA-873-006 iii 6.3.25 User-Data-Request-Type AVP . 17 1 6.3.26 User-Data-Already-Available AVP 17 2 6.3.27 Confidentiality-Key AVP . 17 3 6.3.28 Integrity-Key AVP .17 4 6.4 Use of namespaces . 17 5 6.4.1 AVP codes 17 6 6.4.2 Experi
19、mental-Result-Code AVP values . 18 7 6.4.3 Command Code values. 18 8 6.4.4 Application-ID value 18 9 7 Special Requirements 18 10 7.1 Version Control. 18 11 12 13 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permi
20、tted without license from IHS-,-,-TIA-873-006 iv Foreword 1 This document contains portions of material copied from 3GPP document number 29.229. The copyright 2 on the 3GPP document is owned by the Organizational Partners of 3GPP (ARIB - Association of Radio 3 Industries and Businesses, Japan; CWTS
21、- China Wireless Telecommunications Standards group, China; 4 ETSI - European Telecommunications Standards Institute; ATIS; TTA - Telecommunications Technology 5 Association, Korea; and TTC Telecommunication Technology Committee, Japan), which have granted 6 license for reproduction and for use by 3
22、GPP2 and its Organizational Partners. 7 8 Revision History 9 10 Revision Changes Date 1.0 Initial Publication December 2003 11 12 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,
23、-TIA-873-006 v 1 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-006 1 1 Scope 1 The present document defines a transport protocol for use in the IP multimedia (IM) Core
24、 Network (CN) 2 subsystem based on Diameter. 3 The present document is applicable to: The Cx interface between the I-CSCF/S-CSCF and the HSS. 4 Whenever it is possible this document specifies the requirements for this protocol by reference to 5 specifications produced by the IETF within the scope of
25、 Diameter. Where this is not possible, extensions to 6 Diameter are defined within this document. 7 2 References 8 The following documents contain provisions, which through reference in this text constitute provisions of 9 the present document. 10 References are either specific (identified by date o
26、f publication, edition number, version number, 11 etc.) or non-specific. 12 For a specific reference, subsequent revisions do not apply. 13 For a non-specific reference, the latest version applies. 14 1 3GPP2 X.S0013-005, “IP Multimedia (IM) Subsystem Cx interface; signalling flows and message 15 co
27、ntents” 16 TIA-873-005 “IP Multimedia (IM) Subsystem Cx interface; signalling flows and message contents” 17 2 3GPP2 S.S0086, “IMS Security Framework” 18 3 IETF RFC 3261, “SIP: Session Initiation Protocol“ 19 4 IETF RFC 2396, “Uniform Resource Identifiers (URI): generic syntax” 20 5 IETF RFC 2960, “
28、Stream Control Transmission Protocol” 21 6 IETF RFC 3588, “Diameter Base Protocol” 22 7 IETF RFC 2234, “Augmented BNF for syntax specifications” 23 8 IETF RFC 2806, “URLs for Telephone Calls” 24 9 void 25 10 IETF RFC 3309, “SCTP Checksum Change” 26 11 3GPP2 X.S0013-011, “Sh Interface based on the Di
29、ameter protocol; protocol details” 27 TIA-873-011, “Sh Interface based on the Diameter protocol; protocol details” 28 12 IETF RFC 3589, “Diameter Command Codes for Third Generation Partnership Project (3GPP) 29 Release 5” 30 31 3 Definitions, symbols and abbreviations 32 3.1 Definitions 33 Refer to
30、6 for the definitions of some terms used in this document. 34 For the purposes of the present document, the following terms and definitions apply. 35 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without
31、license from IHS-,-,-TIA-873-006 2 Attribute-Value Pair: see 6, it corresponds to an Information Element in a Diameter message. 1 Diameter Multimedia client: The client is one of the communicating Diameter peers that usually initiate 2 transactions 3 Diameter Multimedia server: A Diameter Multimedia
32、 server that also supported the NASREQ and 4 MobileIP applications would be referred to as a Diameter server. 5 Registration: SIP-registration. 6 Server: SIP-server. 7 User data: user profile data. 8 3.2 Abbreviations 9 For the purposes of the present document, the following abbreviations apply: 10
33、AAA Authentication, Authorization and Accounting 11 ABNF Augmented Backus-Naur Form12 AVP Attribute-Value Pair 13 CN Core Network 14 CSCF Call Session Control Function 15 HSS Home Subscriber Server 16 IANA Internet Assigned Numbers Authority 17 I-CSCF Interrogating CSCF 18 IETF Internet Engineering
34、Task Force 19 IMS IP Multimedia Subsystem 20 RFC Request For Comments 21 S-CSCF Serving CSCF 22 SCTP Stream Control Transport Protocol 23 SIP Session Initiation Protocol 24 UCS Universal Character Set 25 URL Uniform Resource Locator 26 UTF UCS Transformation Formats 27 4 General 28 The Diameter Base
35、 Protocol as specified in 6 shall apply except as modified by the defined support of the 29 methods and the defined support of the commands and AVPs, result and event codes specified in clause 6 30 of this specification. Unless otherwise specified, the procedures (including error handling and unreco
36、gnised 31 information handling) are unmodified. 32 5 Use of the Diameter base protocol 33 With the clarifications listed in the following subclauses, the Diameter Base Protocol defined by IETF 6 34 shall apply. 35 5.1 Securing Diameter Messages 36 For secure transport of Diameter messages, see 2. 37
37、 5.2 Accounting functionality 38 Accounting functionality (Accounting Session State Machine, related command codes and AVPs) is not 39 used on the Cx interface. 40 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking perm
38、itted without license from IHS-,-,-TIA-873-006 3 5.3 Use of sessions 1 Both between the I-CSCF and the HSS and between the S-CSCF and the HSS Diameter sessions are 2 implicitly terminated. An implicitly terminated session is one for which the server does not maintain state 3 information. The client
39、does not need to send any re-authorization or session termination requests to the 4 server. 5 The Diameter base protocol includes the Auth-Session-State AVP as the mechanism for the implementation 6 of implicitly terminated sessions. 7 The client (server) shall include in its requests (responses) th
40、e Auth-Session-State AVP set to the value 8 NO_STATE_MAINTAINED (1), as described in 6. As a consequence, the server does not maintain any 9 state information about this session and the client does not need to send any session termination request. 10 Neither the Authorization-Lifetime AVP nor the Se
41、ssion-Timeout AVP shall be present in requests or 11 responses. 12 5.4 Transport protocol 13 Diameter messages over the Cx interface shall make use of SCTP 5 and shall utilise the new SCTP 14 checksum method specified in RFC 3309 10. 15 5.5 Routing considerations 16 This clause specifies the use of
42、the Diameter routing AVPs Destination-Realm and Destination-Host. 17 If an I-CSCF or S-CSCF knows the address/name of the HSS for a certain user, both the Destination-Realm 18 and Destination-Host AVPs shall be present in the request. Otherwise, only the Destination-Realm AVP 19 shall be present and
43、 the command shall be routed to the next Diameter node based on the Diameter routing 20 table in the client. Consequently, the Destination-Host AVP is declared as optional in the ABNF for all 21 requests initiated by an I-CSCF or an S-CSCF. The S-CSCF shall store the address of the HSS for each 22 u
44、ser, after a first request sent to the redirector function. 23 Requests initiated by the HSS towards an S-CSCF shall include both Destination-Host and Destination-24 Realm AVPs. The HSS obtains the Destination-Host AVP to use in requests towards an S-CSCF, from the 25 Origin-Host AVP received in pre
45、vious requests from the S-CSCF. Consequently, the Destination-Host AVP 26 is declared as mandatory in the ABNF for all requests initiated by the HSS. 27 Destination-Realm AVP is declared as mandatory in the ABNF for all requests. 28 5.6 Advertising Application Support 29 The HSS, S-CSCF and I-CSCF s
46、hall advertise support of the Diameter Multimedia Application by 30 including the value of 3GPP (10415) in the Supported-Vendor-Id AVP of the Capabilities-Exchange-31 Request and Capabilities-Exchange-Answer commands, and by including the value of 3GPP (10415) in the 32 Vendor-Id AVP and the value o
47、f the application identifier (see chapter 6) in the Auth-Application-Id AVP, 33 both in the Vendor-Specific-Application-Id AVP of the Capabilities-Exchange-Request and Capabilities-34 Exchange-Answer command. 35 6 Diameter application for Cx interface 36 This clause specifies a Diameter application
48、that allows a Diameter Multimedia server and a Diameter 37 Multimedia client: 38 - to exchange location information 39 - to authorize a user to access the IMS 40 - to exchange authentication information 41 - to download and handle changes in the user data stored in the server 42 Copyright Telecommun
49、ications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-006 4 The Cx interface protocol is defined as an IETF vendor specific Diameter application, where the vendor is 1 3GPP. The vendor identifier assigned by IANA to 3GPP ( http:/www.iana.org/assignme
