1、 ETSI TS 1Digital cellular telecommUniversal Mobile TelSh interface baP(3GPP TS 29.3TECHNICAL SPECIFICATION129 329 V13.1.0 (2017mmunications system (Phase elecommunications System (LTE; based on the Diameter protocoProtocol details .329 version 13.1.0 Release 1317-01) e 2+) (GSM); (UMTS); col; 13) E
2、TSI ETSI TS 129 329 V13.1.0 (2017-01)13GPP TS 29.329 version 13.1.0 Release 13Reference RTS/TSGC-0429329vd10 Keywords GSM,LTE,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
3、non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions
4、of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific
5、 network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find
6、errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm
7、except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserv
8、ed. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by t
9、he GSM Association. ETSI ETSI TS 129 329 V13.1.0 (2017-01)23GPP TS 29.329 version 13.1.0 Release 13Intellectual 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 avai
10、lable for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual 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 serv
11、er (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, 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 becom
12、e, essential to the present document. Foreword This Technical Specification (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
13、interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “ne
14、ed not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 129 329 V13.1.0 (2
15、017-01)33GPP TS 29.329 version 13.1.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 General . 7g35 Use of the Diameter base
16、 protocol . 7g36 Diameter application for Sh interface 7g36.1 Command-Code values 8g36.1.1 User-Data-Request (UDR) Command 8g36.1.2 User-Data-Answer (UDA) Command 9g36.1.3 Profile-Update-Request (PUR) Command 9g36.1.4 Profile-Update-Answer (PUA) Command 10g36.1.5 Subscribe-Notifications-Request (SNR
17、) Command . 10g36.1.6 Subscribe-Notifications-Answer (SNA) Command 11g36.1.7 Push-Notification-Request (PNR) Command . 11g36.1.8 Push-Notifications-Answer (PNA) Command 12g36.2 Result-Code AVP values 13g36.2.1 Success 13g36.2.2 Permanent Failures . 13g36.2.2.1 DIAMETER_ERROR_USER_DATA_NOT_RECOGNIZED
18、 (5100) . 13g36.2.2.2 DIAMETER_ERROR_OPERATION_NOT_ALLOWED (5101) . 13g36.2.2.3 DIAMETER_ERROR_USER_DATA_CANNOT_BE_READ (5102) 13g36.2.2.4 DIAMETER_ERROR_USER_DATA_CANNOT_BE_MODIFIED (5103) . 13g36.2.2.5 DIAMETER_ERROR_USER_DATA_CANNOT_BE_NOTIFIED (5104) 13g36.2.2.6 DIAMETER_ERROR_TOO_MUCH_DATA (500
19、8) 13g36.2.2.7 DIAMETER_ERROR_TRANSPARENT_DATA OUT_OF_SYNC (5105) . 13g36.2.2.8 DIAMETER_ERROR_FEATURE_UNSUPPORTED (5011) . 13g36.2.2.9 DIAMETER_ERROR_SUBS_DATA_ABSENT (5106) . 13g36.2.2.10 DIAMETER_ERROR_NO_SUBSCRIPTION_TO_DATA (5107) . 14g36.2.2.11 DIAMETER_ERROR_DSAI_NOT_AVAILABLE (5108) . 14g36.
20、2.2.12 DIAMETER_ERROR_IDENTITIES_DONT_MATCH (5002) 14g36.2.3 Transient Failures . 14g36.2.3.1 DIAMETER_USER_DATA_NOT_AVAILABLE (4100) 14g36.2.3.2 DIAMETER_PRIOR_UPDATE_IN_PROGRESS (4101) . 14g36.3 AVPs 15g36.3.1 User-Identity AVP 16g36.3.2 MSISDN AVP 16g36.3.3 User-Data AVP . 16g36.3.4 Data-Referenc
21、e AVP 16g36.3.5 Service-Indication AVP 17g36.3.6 Subs-Req-Type AVP 17g36.3.7 Requested-Domain AVP . 17g36.3.7A Requested-Nodes AVP . 17g36.3.8 Current-Location AVP 18g36.3.9 Server-Name AVP 18g36.3.10 Identity-Set AVP 18g3ETSI ETSI TS 129 329 V13.1.0 (2017-01)43GPP TS 29.329 version 13.1.0 Release 1
22、36.3.11 Supported-Features AVP 18g36.3.12 Feature-List-ID AVP 18g36.3.13 Feature-List AVP 18g36.3.14 Supported-Applications AVP . 18g36.3.15 Public-Identity AVP . 18g36.3.16 Expiry-Time AVP . 19g36.3.17 Send-Data-Indication AVP . 19g36.3.18 DSAI-Tag AVP 19g36.3.19 Wildcarded-Public-Identity AVP 19g3
23、6.3.20 Wildcarded-IMPU AVP . 19g36.3.21 Session-Priority AVP 19g36.3.22 One-Time-Notification AVP 19g36.3.23 Serving-Node-Indication AVP 19g36.3.24 Repository-Data-ID AVP . 19g36.3.25 Sequence-Number AVP 20g36.3.26 Pre-paging-Supported AVP 20g36.3.27 Local-Time-Zone-Indication AVP 20g36.3.28 UDR-Fla
24、gs 20g36.3.29 Call-Reference-Info AVP . 20g36.3.30 Call-Reference-Number AVP . 21g36.3.31 AS-Number AVP 21g36.3.32 OC-Supported-Features 21g36.3.33 OC-OLR . 21g36.3.34 DRMP AVP 21g36.4 Use of namespaces . 21g36.4.1 AVP codes 21g36.4.2 Experimental-Result-Code AVP values 21g36.4.3 Command Code values
25、 . 21g36.4.4 Application-ID value 21g37 Special Requirements . 22g37.1 Version Control 22g3Annex A (informative): Change history . 23g3History 25g3ETSI ETSI TS 129 329 V13.1.0 (2017-01)53GPP TS 29.329 version 13.1.0 Release 13Foreword This Technical Specification has been produced by the 3rdGenerati
26、on 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 contents of the present document, it will be re-released by the TSG with an identifying change of release date and
27、 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 document under change control. y the second digit is incremented for all changes of substance, i.e. technical en
28、hancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 129 329 V13.1.0 (2017-01)63GPP TS 29.329 version 13.1.0 Release 131 Scope The present document defines a transport protocol for use in the IP multi
29、media (IM) Core Network (CN) subsystem based on Diameter. The present document is applicable to: - The Sh interface between an AS and the HSS. - The Sh interface between an SCS and the HSS. Whenever it is possible this document specifies the requirements for this protocol by reference to specificati
30、ons produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within this document. 2 References The following documents contain provisions, which through reference in this text constitute provisions of the present document. - References are ei
31、ther specific (identified by date of publication, edition number, version number, etc.) or non-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)
32、, a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TS 29.328 “IP Multimedia (IM) Subsystem Sh interface; signalling flows and message contents“. 2 3GPP TS 33.210 “3G Security; Network Domain Security; IP Network Lay
33、er Security“. 3 IETF RFC 2960 “Stream Control Transmission Protocol“. 4 IETF RFC 3588 “Diameter Base Protocol“. 5 IETF RFC 2234 “Augmented BNF for syntax specifications“. 6 3GPP TS 29.229 “Cx and Dx Interfaces based on the Diameter protocol; protocol details“. 7 IETF RFC 3589 “Diameter Command Codes
34、 for Third Generation Partnership Project (3GPP) Release 5“. 8 ITU-T Recommendation E.164: “The international public telecommunication numbering plan“. 9 3GPP TR 33.978 “Security aspects of early IP Multimedia Subsystem (IMS) (Release 6)“. 10 3GPP TS 29.364 “IMS Application Server Service Data Descr
35、iptions for AS interoperability“. 11 3GPP TS 29.002 “Mobile Application Part (MAP) specification“. 12 IETF RFC 7683: “Diameter Overload Indication Conveyance“. 13 IETF RFC 7944: “Diameter Routing Message Priority“. ETSI ETSI TS 129 329 V13.1.0 (2017-01)73GPP TS 29.329 version 13.1.0 Release 133 Defi
36、nitions, symbols and abbreviations 3.1 Definitions Refer to IETF RFC 3588 4 for the definitions of some terms used in this document. For the purposes of the present document, the following terms and definitions apply. Attribute-Value Pair: see IETF RFC 3588 4, it corresponds to an Information Elemen
37、t in a Diameter message. Server: SIP-server. User data: user profile data. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AAA Authentication, Authorization and Accounting AS Application Server ABNF Augmented Backus-Naur Form AVP Attribute-Value Pair CN
38、 Core Network DRMP Diameter Routing Message Priority HSS Home Subscriber Server IANA Internet Assigned Numbers Authority IETF Internet Engineering Task Force IMS IP Multimedia Subsystem NDS Network Domain Security RFC Request For CommentSCTP Stream Control Transport Protocol UCS Universal Character
39、Set URL Uniform Resource Locator UTF UCS Transformation Formats 4 General The Diameter Base Protocol as specified in IETF RFC 3588 4 shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and event codes specified in clause 6 of
40、this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) are unmodified. 5 Use of the Diameter base protocol The same clarifications of section 5 of 3GPP TS 29.229 6 shall apply to the Sh interface. An exception is that the appli
41、cation identifier for this application is defined in chapter 6. 6 Diameter application for Sh interface This clause specifies a Diameter application that allows a Diameter server and a Diameter client: - to download and update transparent and non-transparent user data - to request and send notificat
42、ions on changes on user data ETSI ETSI TS 129 329 V13.1.0 (2017-01)83GPP TS 29.329 version 13.1.0 Release 13The Sh interface protocol is defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP ( http:/www.iana.org/assignments/
43、enterprise-numbers) is 10415. The Diameter application identifier assigned to the Sh interface application is 16777217 (allocated by IANA). 6.1 Command-Code values This section defines Command-Code values for this Diameter application. Every command is defined by means of the ABNF syntax (as defined
44、 in RFC 2234 5), according to the rules in IETF RFC 3588 4. Whenever the definition and use of an AVP is not specified in this document, what is stated in 3GPP TS 29.229 6 shall apply. The command codes for the Sh interface application are taken from the range allocated by IANA in IETF RFC 3589 7 as
45、 assigned in this specification. For these commands, the Application-ID field shall be set to 16777217 (application identifier of the Sh interface application, allocated by IANA). The following Command Codes are defined in this specification: Table 6.1.1: Command-Code values Command-Name Abbreviatio
46、n Code Section User-Data-Request UDR 306 6.1.1User-Data-Answer UDA 306 6.1.2Profile-Update-Request PUR 307 6.1.3 Profile-Update-Answer PUA 307 6.1.4Subscribe-Notifications-Request SNR 308 6.1.5 Subscribe-Notifications-Answer SNA 308 6.1.6 Push-Notification-Request PNR 309 6.1.7Push-Notification-Answ
47、er PNA 309 6.1.8 6.1.1 User-Data-Request (UDR) Command The User-Data-Request (UDR) command, indicated by the Command-Code field set to 306 and the “R“ bit set in the Command Flags field, is sent by a Diameter client to a Diameter server in order to request user data. Message Format := DRMP Vendor-Sp
48、ecific-Application-Id Auth-Session-State Origin-Host Origin-Realm Destination-Host Destination-Realm * Supported-Features User-Identity Wildcarded-Public-Identity Wildcarded-IMPU Server-Name * Service-Indication * Data-Reference * Identity-Set Requested-Domain Current-Location * DSAI-Tag Session-Pri
49、ority User-Name Requested-Nodes ETSI ETSI TS 129 329 V13.1.0 (2017-01)93GPP TS 29.329 version 13.1.0 Release 13 Serving-Node-Indication Pre-paging-Supported Local-Time-Zone-Indication UDR-Flags Call-Reference-Info OC-Supported-Features * AVP * Proxy-Info * Route-Record 6.1.2 User-Data-Answer (UDA) Command The User-Data-Answer (UDA) command, indicated by the Command-Code field set to 306 and the “R“ bit cleared in the Comman
