TIA-873 010-2003 All-IP Core Network Multimedia Domain IP Multimedia Subsystem Sh Interface Signaling Flows and Message Contents Stage-2《CDMA2000扩频系统的IP网－IP多媒体子系统Sh接口 信令流和消息内容》.pdf

1、 TIA DOCUMENT All-IP Core Network Multimedia Domain IP Multimedia Subsystem Sh Interface; Signaling Flows and Message Contents Stage-2 TIA-873.010 DECEMBER 2003 TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Industry Association represents the communications sector of Copyright Telec

2、ommunications 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 manufa

3、cturers and 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 o

4、f TIA from 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

5、the industry, 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 availabl

6、e in the 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

7、 on this subject. Suggestions for revision should be directed to: Standards 3 Signaling flows and message contents Stage 2 4 5 Contents 6 7 1 Scope . 1 8 2 References . 1 9 3 Definitions, symbols and abbreviations 2 10 3.1 Definitions . 2 11 3.2 Abbreviations 2 12 4 Main Concept . 2 13 5 General Arc

8、hitecture 2 14 5.1 Functional requirements of network entities . 2 15 5.1.1 Functional Requirements of the Application Server. 2 16 5.1.2 Functional requirements of HSS. 2 17 5.2 Functional classification of Sh interface procedures. 3 18 6 Procedure Descriptions 3 19 6.1 User data handling procedure

9、s. 3 20 6.1.1 Data read (Sh-Pull) . 3 21 6.1.1.1 Detailed behaviour.4 22 6.1.2 Data Update (Sh-Update) . 5 23 6.1.2.1 Detailed behaviour6 24 6.1.3 Subscription to notifications (Sh-Subs-Notif) 7 25 6.1.3.1 Detailed behaviour8 26 6.1.4 Notifications (Sh-Notif) 9 27 6.1.4.1 Detailed behaviour9 28 6.2

10、AS permissions list 9 29 7 Information element contents. 10 30 7.1 User Identity 10 31 7.2 Requested Domain . 10 32 7.3 Requested Data 10 33 7.4 Service Indication 10 34 7.5 Result 10 35 7.6 Data. 10 36 7.6.1 Repository Data 11 37 Copyright Telecommunications Industry Association Provided by IHS und

11、er license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-010 7.6.2 PublicIdentifiers 11 1 7.6.3 IMSUser State. 11 2 7.6.4 S-CSCF Name 11 3 7.6.5 Initial Filter Criteria 11 4 7.6.6 void. 11 5 7.6.6.1 void. 11 6 7.6.6.2 void. 11 7 7.6.7 Void 11 8 7.

12、6.8 Charging information 11 9 7.7 Subscription request type . 12 10 7.8 Current Location 12 11 7.9 Application Server Identity 12 12 7.10 Application Server Name. 12 13 8 Protocol version identification.12 14 9 Operational Aspects . 12 15 Annex A (normative): Mapping of Sh operations and terminology

13、 to Diameter 13 16 A.1 Introduction . 13 17 A.2 Sh message to Diameter command mapping. 13 18 A.3 Sh message parameters to Diameter AVP mapping 13 19 Annex B (informative): Message flow 14 20 B.1 Message flows 14 21 B.1.1 Data Update, Registration, Notification Subscription. . 14 22 Annex C (informa

14、tive): UML model of the data downloaded over Sh i/f . 16 23 C.1 General description. 16 24 C.2 PublicIdentifiers.16 25 C.3 Sh-IMS-Data . 17 26 Annex D (normative): XML schema for the Sh interface user profile 19 27 Annex E (ShDataType.xsd): 26 28 29 30 Copyright Telecommunications Industry Associati

15、on Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-010 Foreword 1 2 “This document contains portions of material copied from 3GPP document number(s) TS 29.328. The 3 copyright on the 3GPP document is owned by the Organi

16、zational Partners of 3GPP (ARIB - Association of 4 Radio Industries and Businesses, Japan; CWTS China Wireless Telecommunications Standards group, 5 China; ETSI European Telecommunications Standards Institute; ATIS, USA; TTA - Telecommunications 6 Technology Association, Korea; and TTC Telecommunica

17、tion Technology Committee, Japan), which 7 have granted license for reproduction and for use by 3GPP2 and its Organizational Partners.” 8 9 Revision History 10 11 Revision Changes Date 0 Initial Publication December 2003 12 13 14 Copyright Telecommunications Industry Association Provided by IHS unde

18、r license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-010 1 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-010 1

19、Scope 1 This document specifies the interactions between the HSS (Home Subscriber Server) and the SIP AS 2 (Application Server) and between the HSS and the OSA SCS (Service Capability Server). This interface is 3 referred to as the Sh reference point. 4 The IP Multimedia (IM) Core Network Subsystem

20、stage 2 is specified in 1 and the protocol for the IP 5 multimedia call control based on SIP and SDP are specified in 2. 6 The IP Multimedia (IM) Session Handling with the IP Multimedia (IM) call model is specified in 4. 7 This document addresses the signalling flows and message contents for the pro

21、tocol at the Sh interface. 8 2 References 9 1 TIA-873-002: “IP Multimedia (IM) Subsystem Stage 2”. 10 3GPP2 X.S0013-002: “IP Multimedia (IM) Subsystem Stage 2. 11 2 TIA-873-004: “IP Multimedia Call Control Protocol based on SIP and SDP”. 12 3GPP2 X.S0013-004: “IP Multimedia Call Control Protocol bas

22、ed on SIP and SDP”. 13 3 TIA/TSB-151: IP Network Reference Model (NRM) for cdma20001Spread Spectrum Systems, 14 December 2003. 15 3GPP2 S.R0037-0, “3GPP2 All-IP Network Architecture Model Version 2.0, May 14, 2002”. 16 4 TIA-873-003: “IP Multimedia (IM) session handling; IM call model”. 17 3GPP2 X.S

23、0013-003: “IP Multimedia (IM) session handling; IM call model”. 18 5 TIA-873-011: “Sh Interface based on Diameter Protocol details”. 19 3GPP2 X.S0013-011: “Sh Interface based on Diameter Protocol details”. 20 6 TIA-873-005: “IP Multimedia (IM) Subsystem Cx Interface; Signalling flows and Message 21

24、Elements”. 22 3GPP2 X.S0013-005: “IP Multimedia (IM) Subsystem Cx Interface; Signalling flows and Message 23 Elements”. 24 7 TIA-873-006: “Cx Interface based on the Diameter protocol ; Protocol details”. 25 3GPP2 X.S0013-006: “Cx Interface based on the Diameter protocol ; Protocol details”. 26 8 IET

25、F RFC 3588, “Diameter Base Protocol”, September 2003. 27 9 IETF RFC 3261: “SIP: Session Initiation Protocol“. 28 10 IETF RFC 2806: “URLs for Telephone Calls“. 29 1cdma2000 is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of

26、 3GPP2. When applied to goods and services, the cdma2000mark certifies their compliance with cdma2000standards. Geographically (and as of the date of publication), cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States. Copyright Telecommunic

27、ations Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-010 3 Definitions, symbols and abbreviations 1 3.1 Definitions 2 For the purposes of the present document, the following terms and definitions

28、apply. 3 IP Multimedia session: IP Multimedia session and IP Multimedia call are treated as equivalent in this 4 specification. 5 Transparent data: Data that is understood syntactically but not semantically by the HSS. It is data that an 6 AS may store in the HSS to support its service logic. One ex

29、ample is data that an AS stores in the HSS, 7 using it as a repository. 8 Non-transparent data: Data that is understood both syntactically and semantically by the HSS. 9 AS (Application Server): a term used to denote either of a SIP Application Server or an OSA Service 10 Capability Server. 11 3.2 A

30、bbreviations 12 For the purposes of the present document, the following abbreviations apply: 13 AS Application Server 14 CSCF Call Session Control Function 15 HSS Home Subscriber Server 16 IE Information Element 17 IP Internet Protocol 18 IM IP Multimedia 19 IMS IP Multimedia Subsystem 20 SIP Sessio

31、n Initiation Protocol 21 S-CSCF Serving CSCF 22 4 Main Concept 23 This document presents the Sh interface related functional requirements of the communicating entities. 24 It gives a functional classification of the procedures and describes the procedures and message parameters. 25 Error handling fl

32、ows, protocol version identification, etc. procedures are also included. 26 5 General Architecture 27 This clause further specifies the architectural assumptions associated with the Sh reference point, building 28 on 1 and 4. 29 5.1 Functional requirements of network entities 30 5.1.1 Functional Req

33、uirements of the Application Server 31 The Application Server may communicate with the HSS over the Sh interface. 32 For functionality of the Application Server refer to 1, 3 and 4. 33 5.1.2 Functional requirements of HSS 34 The HSS may communicate with the Application Server over the Sh interface.

34、35 For functionality of the HSS refer to 1, 3 and 4. 36 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-010 5.2 Functional classification of Sh interface procedures 1 Op

35、erations on the Sh interface are classified in functional groups: 2 1. Data handling procedures 3 - The download of data from the HSS to an AS. 4 - The update of data in the HSS. 5 2. Subscription/notification procedures 6 - An AS can subscribe to receive notifications from the HSS of changes in dat

36、a. 7 - The HSS can notify an AS of changes in data for which the AS previously had subscribed. 8 6 Procedure Descriptions 9 6.1 User data handling procedures 10 6.1.1 Data read (Sh-Pull) 11 This procedure is used between an AS the HSS. The procedure is invoked by the AS and is used: 12 To read trans

37、parent and/or non-transparent data for a specified user from the HSS. This procedure is 13 mapped to the commands User-Data-Request/Answer in the Diameter application specified in 5. Tables 14 6.1.1.1 and 6.1.1.2 detail the involved information elements. 15 This release of the specification does not

38、 support location retrieval 16 This release of the specification does not support retrieval of the CS and PS User State data. 17 18 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,

39、TIA-873-010 Table 6.1.1.1: Sh-Pull 1 Information element name Mapping to Diameter AVP Cat. Description User Identity (See 7.1) User-Identity M Identity of the user for whom the data is required. Requested data (See 7.3) Data-Reference M This information element indicates the reference to the requ

40、ested information. The set of valid reference values are defined in 7.6. Requested domain (See 7.2) Requested-Domain C This information element indicates the domains to which the operation is applicable. Check table 7.6.1 to see when it is applicable. Current Location (See 7.8) Current-Location C Th

41、is information element indicates whether an active location retrieval has to be initiated or not. It shall be present if Location Information is requested. If this information element takes the value InitiateActiveLocationRetrieval (1) the HSS shall indicate the need to initiate an active location r

42、etrieval. Service Indication (See 7.4) Service-Indication C IE that identifies, together with the User-Identity and Data-Reference, the set of service related transparent data that is being requested Application Server Identity (See 7.9) Origin-Host M IE that identifies the AS originator of the requ

43、est and that is used to check the AS permission list. Application Server Name (See 7.10) Server-Name C IE that is used, together with the User -Identity and Data-Reference, as key to identify the filter criteria. This element shall be present when the Data-Reference value is InitialFilterCriteria (1

44、3). 2 Table 6.1.1.2: Sh-Pull Resp 3 Information element name Mapping to Diameter AVP Cat. Description Result (See 7.5) Result-Code / Experimental-Result M Result of the request. Result-Code AVP shall be used for errors defined in the Diameter Base Protocol. Experimental-Result AVP shall be used for

45、Sh 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. Data (See 7.6) User-Data O Requested data. 4 6.1.1.1 Detailed behaviour 5 The conditions for the inclusion of Requested-Domain as an additional key to the

46、requested data are 6 described in table 7.6.1. If repository data is requested, Service-Indication shall be present in the request. If 7 initial filter criteria are requested, the Server-Name AVP shall contain the SIP URL of the AS that initiates 8 the request; requests for initial filter criteria a

47、re limited to those initial filter criteria which are relevant to 9 the requesting AS. 10 Upon reception of the Sh-Pull request, the HSS shall, in the following order: 11 1. Check that the AS sending the request (identified by the Origin-Host AVP) has Sh-Pull permission 12 in the AS Permissions List

48、 (See 6.2). If not, Experimental-Result-Code shall be set to 13 DIAMETER_ERROR_OPERATION_NOT_ALLOWED in the Sh-Pull Response. 14 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-

49、TIA-873-010 2. Check that the user for whom data is asked exists in HSS. If not, Experimental-Result-Code shall be 1 set to DIAMETER_ERROR_USER_UNKNOWN in the Sh-Pull Response. 2 3. Check that the requested user data is allowed to be read by the AS. 3 - If the data referenced in the request is not allowed to be read, Experimental