1、 TIA DOCUMENT All-IP Core Network Multimedia Domain Sh Interface Based on Diameter Protocols Protocol Details Stage-3 TIA-873.011 DECEMBER 2003 TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Industry Association represents the communications sector of Copyright Telecommunications Ind
2、ustry 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 purch
3、asers, 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 manufa
4、cturing 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
5、 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 TIA Engi
6、neering 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.
7、 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 Committee, Japan
8、), which 6 have granted license for reproduction and for use by 3GPP2 and its Organizational Partners.” 7 8 9 Revision History 10 11 Revision Changes Date 0 Initial Publication December 2003 12 13 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleN
9、o reproduction or networking permitted without license from IHS-,-,-TIA-873-011 iv 1 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-011 1 1 Scope 1 The present document
10、 defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) 2 subsystem based on Diameter. 3 The present document is applicable to: 4 - The Sh interface between an SIP AS and the AAA. 5 - The Sh interface between an SCS and the AAA. 6 Whenever it is possible this document speci
11、fies the requirements for this protocol by reference to 7 specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to 8 Diameter are defined within this document. 9 2 References 10 The following documents contain provisions, which through reference in
12、this text constitute provisions of 11 the present document. 12 References are either specific (identified by date of publication, edition number, version number, 13 etc.) or non-specific. 14 For a specific reference, subsequent revisions do not apply. 15 For a non-specific reference, the latest vers
13、ion applies. In the case of a reference to a 3GPP2 16 document, a non-specific reference implicitly refers to the latest version of that document in the 17 same Release as the present document. 18 1 TIA-873-010: “IP Multimedia (IM) Subsystem Sh interface; signalling flows and message 19 contents”. 2
14、0 3GPP2 X.S0013-010: “IP Multimedia (IM) Subsystem Sh interface; signalling flows and message 21 contents”. 22 2 void 23 3 IETF RFC 2960 “Stream Control Transmission Protocol” 24 4 IETF RFC 3588, “Diameter Base Protocol”, September 2003. 25 5 IETF RFC 2234 “Augmented BNF for syntax specifications” 2
15、6 6 TIA-873-006: “Cx Interface based on Diameter protocol; protocol details”. 27 3GPP2 X.S0013-006: “Cx Interface based on Diameter protocol; protocol details”. 28 7 IETF RFC 3589, “Diameter Command Codes for 3GPP Release 5”, September 2003. 29 8 3GPP TS 23.003 V5.6.0 (2003-06): 3GPP Technical Speci
16、fication Group Core Network; 30 Numbering, addressing and identification (Release 5) 31 3 Definitions, symbols and abbreviations 32 3.1 Definitions 33 Refer to 4 for the definitions of some terms used in this document. 34 For the purposes of the present document, the following terms and definitions
17、apply. 35 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-011 2 Attribute-Value Pair: see 4, it corresponds to an Information Element in a Diameter message. 1 Server: SI
18、P-server. 2 User data: user profile data. 3 3.2 Abbreviations 4 For the purposes of the present document, the following abbreviations apply: 5 AAA Authentication, Authorization and Accounting 6 AS Application Server 7 ABNF Augmented Backus-Naur Form 8 AVP Attribute-Value Pair 9 CN Core Network 10 HS
19、S Home Subscriber Server 11 IANA Internet Assigned Numbers Authority 12 IETF Internet Engineering Task Force 13 IMS IP Multimedia Subsystem 14 RFC Request For Comment15 SCS Service Capability Server 16 SCTP Stream Control Transport Protocol 17 UCS Universal Character Set 18 URL Uniform Resource Loca
20、tor 19 UTF UCS Transformation Formats 20 4 General 21 The Diameter Base Protocol as specified in 4 shall apply except as modified by the defined support of the 22 methods and the defined support of the commands and AVPs, result and event codes specified in clause 65 23 of this specification. Unless
21、otherwise specified, the procedures (including error handling and unrecognised 24 information handling) are unmodified. 25 Note: The MSISDN represented in this document is similar to the MDN in 3GPP2. 26 5 Use of the Diameter base protocol 27 The same clarifications of section 5 of 6 shall apply to
22、the Sh interface. An exception is that the 28 application identifier for this application is defined in chapter 6. 29 6 Diameter application for Sh interface 30 This clause specifies a Diameter application that allows a Diameter server and a Diameter client: 31 - to download and update transparent a
23、nd non-transparent user data 32 - to request and send notifications on changes on user data 33 The Sh interface protocol is defined as an IETF vendor specific Diameter application, where the vendor is 34 3GPP. The vendor identifier assigned by IANA to 3GPP ( http:/www.iana.org/assignments/enterprise
24、-35 numbers) is 10415. 36 The Diameter application identifier assigned to the Sh interface application is 167772152 . 37 6.1 Command-Code values 38 This section defines Command-Code values for this Diameter application. 39 Copyright Telecommunications Industry Association Provided by IHS under licen
25、se with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-011 3 Every command is defined by means of the ABNF syntax 5, according to the rules in 4. Whenever the 1 definition and use of an AVP is not specified in this document, what is stated in 4 or 6 sha
26、ll apply. 2 The command codes for the Sh interface application are taken from the range allocated by IANA in 7 as 3 assigned in this specification. For these commands, the Application-ID field shall be set to 167772152 4 (application identifier of the Sh interface application). 5 The following Comma
27、nd Codes are defined in this specification: 6 Table 6.1.1: Command-Code values 7 Command-Name Abbreviation Code Section User-Data-Request UDR 306 6.1.1 User-Data-Answer UDA 306 6.1.2 Profile-Update-Request PUR 307 6.1.3 Profile-Update-Answer PUA 307 6.1.4 Subscribe-Notifications-Request SNR 308 6.1.
28、5 Subscribe-Notifications-Answer SNA 308 6.1.6 Push-Notification-Request PNR 309 6.1.7 Push-Notification-Answer PNA 309 6.1.8 8 6.1.1 User-Data-Request (UDR) Command 9 The User-Data-Request (UDR) command, indicated by the Command-Code field set to 306 and the R bit 10 set in the Command Flags field,
29、 is sent by a Diameter client to a Diameter server in order to request user 11 data. 12 Message Format 13 := 14 15 Vendor-Specific-Application-Id 16 Auth-Session-State 17 Origin-Host 18 Origin-Realm 19 Destination-Host 20 Destination-Realm 21 User-Identity 22 Service-Indication 23 Server-Name 24 1*
30、Data-Reference 25 * Requested-Domain 26 Current-Location 27 * AVP 28 * Proxy-Info 29 RuteRecrd 30 6.1.2 User-Data-Answer (UDA) Command 31 The User-Data-Answer (UDA) command, indicated by the Command-Code field set to 306 and the R bit 32 cleared in the Command Flags field, is sent by a server in res
31、ponse to the User-Data-Request command. 33 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-011 4 The Result-Code or Experimental-Result AVP may contain one of the values
32、 defined in section 6.2 in 1 addition to the values defined in 6. 2 Message Format 3 := 4 5 Vendor-Specific-Application-Id 6 Result-Cde 7 Experimental-Result 8 Auth-Session-State 9 Origin-Host 10 Origin-Realm 11 User-Data 12 * AVP 13 * Proxy-Info 14 * Route-Recrd 15 6.1.3 Profile-Update-Request (PUR
33、) Command 16 The Profile-Update-Request (PUR) command, indicated by the Command-Code field set to 307 and the R 17 bit set in the Command Flags field, is sent by a Diameter client to a Diameter server in order to update user 18 data in the server. 19 Message Format 20 := 21 22 Vendor-Specific-Applic
34、ation-Id 23 Auth-Session-State 24 Origin-Host 25 Origin-Realm 26 Destination-Host 27 Destination-Realm 28 User-Identity 29 User-Data 30 * AVP 31 * Proxy-Info 32 * Route-Record 33 6.1.4 Profile-Update-Answer (PUA) Command 34 The Profile-Update-Answer (PUA) command, indicated by the Command-Code field
35、 set to 307 and the R 35 bit cleared in the Command Flags field, is sent by a client in response to the Profile-Update-Request 36 command. The Result-Code or Experimental-Result AVP may contain one of the values defined in section 37 6.2 in addition to the values defined in 6. 38 Message Format 39 :
36、= 40 41 Vendor-Specific-Application-Id 42 Result-Code 43 Experimental-Result 44 Auth-Session-State 45 Origin-Host 46 Origin-Realm 47 * AVP 48 * Proxy-Info 49 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted
37、without license from IHS-,-,-TIA-873-011 5 * Route-Record 1 6.1.5 Subscribe-Notifications-Request (SNR) Command 2 The Subscribe-Notifications-Request (SNR) command, indicated by the Command-Code field set to 308 3 and the R bit set in the Command Flags field, is sent by a Diameter client to a Diamet
38、er server in order to 4 request notifications of changes in user data. 5 Message Format 6 := 7 8 Vendor-Specific-Application-Id 9 Auth-Session-State 10 Origin-Host 11 Origin-Realm 12 Destination-Host 13 Destination-Realm 14 User-Identity 15 Service-Indication 16 Server-Name 17 Subs-Req-Type 18 1* Da
39、ta-Reference 19 * AVP 20 *Proxy-Info 21 RuteRecrd 22 6.1.6 Subscribe-Notifications-Answer (SNA) Command 23 The Subscribe-Notifications-Answer (SNA) command, indicated by the Command-Code field set to 308 24 and the R bit cleared in the Command Flags field, is sent by a client in response to the Subs
40、cribe-25 Notifications-Request command. The Result-Code or Experimental-Result AVP may contain one of the 26 values defined in section 6.2 in addition to the values defined in 6. 27 Message Format 28 := 29 30 Vendor-Specific-Application-Id 31 Auth-Session-State 32 Result-Cde 33 Experimental-Result 3
41、4 Origin-Host 35 Origin-Realm 36 * Data-Reference 37 * AVP 38 * Proxy-Info 39 * Route-Recrd 40 6.1.7 Push-Notification-Request (PNR) Command 41 The Push-Notification-Request (PNR) command, indicated by the Command-Code field set to 309 and the 42 R bit set in the Command Flags field, is sent by a Di
42、ameter server to a Diameter client in order to notify 43 changes in the user data in the server. 44 Message Format 45 := 46 47 Vendor-Specific-Application-Id 48 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitt
43、ed without license from IHS-,-,-TIA-873-011 6 Auth-Session-State 1 Origin-Host 2 Origin-Realm 3 Destination-Host 4 Destination-Realm 5 User-Identity 6 User-Data 7 * AVP 8 * Proxy-Info 9 * Route-Record 10 6.1.8 Push-Notifications-Answer (PNA) Command 11 The Push-Notifications-Answer (PNA) command, in
44、dicated by the Command-Code field set to 309 and the 12 R bit cleared in the Command Flags field, is sent by a client in response to the Push-Notification-Request 13 command. The Result-Code or Experimental-Result AVP may contain one of the values defined in section 14 6.2 in addition to the values
45、defined in 6. 15 Message Format 16 := 17 18 Vendor-Specific-Application-Id 19 Result-Code 20 Experimental-Result 21 Auth-Session-State 22 Origin-Host 23 Origin-Realm 24 * AVP 25 * Proxy-Info 26 * Route-Record 27 6.2 Experimental-Result-Code AVP values 28 This section defines new result code values t
46、hat must be supported by all Diameter implementations that 29 conform to this specification. The result codes defined in 6 are also applicable. When one of the result 30 codes defined here is included in a response, it shall be inside a Experimental-Result AVP and Result-Code 31 AVP shall be absent.
47、 32 6.2.1 Success 33 The Result codes within the success category are used to inform a peer that a request has been successfully 34 completed. 35 6.2.2 Permanent Failures 36 Errors that fall within the Permanent Failures category are used to inform the peer that the request failed, 37 and should not
48、 be attempted again. 38 DIAMETER_ERROR_USER_DATA_NOT_RECOGNIZED (5100) 39 The data required, in the XML schema, does not match that which is specified within the HSS. 40 DIAMETER_ERROR_OPERATION_NOT_ALLOWED (5101) 41 The requested operation is not allowed for the user 42 DIAMETER_ERROR_USER_DATA_CANNOT_BE_READ (5102) 43 The r
