ETSI TS 129 283-2018 LTE Universal Mobile Telecommunications System (UMTS) Diameter data management applications (V15 0 0 3GPP TS 29 283 version 15 0 0 Release 15).pdf

1、 ETSI TS 129 283 V15.0.0 (2018-07) LTE; Universal Mobile Telecommunications System (UMTS); Diameter data management applications (3GPP TS 29.283 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 129 283 V15.0.0 (2018-07)13GPP TS 29.283 version 15.0.0 Release 15Reference RTS/TSGC-042928

2、3vf00 Keywords 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 non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document ca

3、n 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 of the present document shall not be modified without the prior written authorization of ETSI. In case of a

4、ny 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 network drive within ETSI Secretariat. Users of the present document should be aware that the document may

5、 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 errors in the present document, please send your comment to one of the following services: https:/portal.et

6、si.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 except as authorized by written permission of ETSI. The content of the PDF version shall not be modified wi

7、thout the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of E

8、TSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 129 283 V15.0.0 (2018-07)23GPP TS 29.283 version 15.0.0 Release

9、 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314:

10、 “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 server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation

11、, 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 become, essential to the present document. Trademarks The present document may in

12、clude trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the pre

13、sent document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications

14、 or reports using their 3GPP identities, UMTS identities or GSM identities. These should be 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

15、terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need 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 allow

16、ed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 129 283 V15.0.0 (2018-07)33GPP TS 29.283 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 6g31 Scope 7g32 References 7g33 Definitions, symbols and abbreviati

17、ons . 8g33.1 Definitions 8g33.2 Abbreviations . 8g34 Main Concept . 8g34.1 Introduction 8g35 MC Service General Architecture 9g35.1 Introduction 9g35.2 Functional requirements of network entities 9g35.2.1 Functional Requirements of the MC Service Server . 9g35.2.2 Functional Requirements of the Conf

18、iguration Management Server 9g35.2.3 Functional requirements of MCPTT User Database . 9g35.3 Functional classification of MC Service Server to MC Service User Database related interface procedures 10g35.4 Functional classification of CSC-13 interface procedures . 10g36 Procedure Descriptions for MC

19、Services . 10g36.1 Introduction 10g36.2 MC Service User data handling procedures . 11g36.2.1 Data Pull . 11g36.2.1.1 General 11g36.2.1.2 Detailed behaviour of the requesting entity 12g36.2.1.3 Detailed behaviour of the MC Service User Database 12g36.2.2 Data Update 13g36.2.2.1 General 13g36.2.2.2 De

20、tailed behaviour of the Configuration Management Server 14g36.2.2.3 Detailed behaviour of the MC Service User Database 15g36.2.3 Data Notification 16g36.2.3.1 General 16g36.2.3.2 Detailed behaviour of the MCPTT User Database 17g36.2.3.3 Detailed behaviour of the receiving entity 17g36.3 Requesting e

21、ntity permissions list 18g36.3.1 General 18g37 Protocol Specification and Implementation for MC Service 19g37.1 General . 19g37.1.1 Use of Diameter base protocol 19g37.1.2 Securing Diameter Messages 19g37.1.3 Accounting functionality 19g37.1.4 Use of sessions 19g37.1.5 Transport protocol 20g37.1.6 R

22、outing considerations . 20g37.1.7 Advertising Application Support 20g37.1.8 Diameter Application Identifier 21g37.1.9 Use of the Supported-Features AVP . 21g37.1.10 MC Service ID to MC Service User Database resolution . 21g37.2 Commands 23g37.2.1 Introduction. 23g37.2.2 Command-Code values . 23g3ETS

23、I ETSI TS 129 283 V15.0.0 (2018-07)43GPP TS 29.283 version 15.0.0 Release 157.2.3 Data-Pull-Request (DPR) Command 23g37.2.4 Data-Pull-Answer (DPA) Command 24g37.2.5 Data-Update-Request (DUR) Command 24g37.2.6 Data-Update-Answer (DUA) Command 24g37.2.7 Notification-Data-Request (PDR) Command . 25g37.

24、2.8 Notification-Data-Answer (PDA) Command . 25g37.3 AVPs 26g37.3.1 General 26g37.3.2 MCPTT-ID . 27g37.3.3 Requested-Data . 27g37.3.4 DRMP . 27g37.3.5 OC-OLR . 27g37.3.6 OC-Supported-Features 27g37.3.7 User-Data 27g37.3.8 User-Identifier . 28g37.3.9 Feature-List-ID AVP 28g37.3.10 Feature-List AVP 28

25、g37.3.11 Data-Identification-Prefix . 28g37.3.12 Data-Identification-Flags 28g37.3.13 DPR-Flags. 29g37.3.14 DPA-Flags 29g37.3.15 DUR-Flags 29g37.3.16 DUA-Flags 29g37.3.17 NDR-Flags 30g37.3.18 NDA-Flags 30g37.3.19 User-Data-Id . 30g37.3.20 MC-Service-User-Profile-Data . 30g37.3.21 Sequence-Number . 3

26、1g37.3.22 Data . 31g37.3.23 Load 31g37.3.24 MCVideo-ID . 31g37.3.25 MCData-ID . 31g37.4 Result-Code and Experimental-Result-Code Values 31g37.4.1 Introduction. 31g37.4.2 Success 31g37.4.2.1 General 31g37.4.3 Permanent Failures . 31g37.4.3.1 General 31g37.4.3.2 DIAMETER_ERROR_USER_UNKNOWN (5001) 31g3

27、7.4.3.3 DIAMETER_ERROR_USER_DATA_NOT_RECOGNIZED (5100) . 32g37.4.3.4 DIAMETER_ERROR_OPERATION_NOT_ALLOWED (5101) . 32g37.4.3.5 DIAMETER_ERROR_USER_DATA_CANNOT_BE_READ (5102) 32g37.4.3.6 DIAMETER_ERROR_USER_DATA_CANNOT_BE_MODIFIED (5103) . 32g37.4.3.7 DIAMETER_ERROR_USER_DATA_CANNOT_BE_NOTIFIED (5104

28、) 32g37.4.3.8 DIAMETER_ERROR_TOO_MUCH_DATA (5008) 32g37.4.3.9 DIAMETER_ERROR_DATA OUT_OF_SYNC (5105) . 32g37.4.3.10 DIAMETER_ERROR_FEATURE_UNSUPPORTED (5011) . 32g37.4.3.11 DIAMETER_ERROR_NO_SUBSCRIPTION_TO_DATA (5107) . 32g37.4.3.12 DIAMETER_ERROR_ UNKNOWN _DATA (5670) . 32g37.4.3.13 DIAMETER_ERROR

29、_REQUIRED_KEY_NOT_PROVIDED (5671) . 32g37.4.4 Transient Failures . 32g37.4.4.1 General 32g37.4.4.2 DIAMETER_USER_DATA_NOT_AVAILABLE (4100) 32g37.4.4.3 DIAMETER_PRIOR_UPDATE_IN_PROGRESS (4101) . 33g3Annex A (normative): Diameter overload control mechanism 34g3A.1 General . 34g3A.2 MC Service User Dat

30、abase behaviour 34g3A.3 MC Service Server and Configuration Management Server behaviour . 34g3Annex B (Informative): Diameter overload node behaviour 35g3B.1 Message prioritization 35g3ETSI ETSI TS 129 283 V15.0.0 (2018-07)53GPP TS 29.283 version 15.0.0 Release 15Annex C (normative): Diameter messag

31、e priority mechanism 36g3C.1 General . 36g3C.2 MCPTT-2, MCVideo-2, MCData-2 and CSC-13 interfaces 36g3C.2.1 General 36g3C.2.2 MC Service Server and Configuration Management Server behaviour 36g3C.2.3 MC Service User Database behaviour 37g3Annex D (normative): Diameter load control mechanism 38g3D.1

32、General . 38g3D.2 MC Service User Database behaviour 38g3D.3 MC Service Server and Configuration Management Server behaviour . 38g3Annex E (informative): Change history . 39g3History 40g3ETSI ETSI TS 129 283 V15.0.0 (2018-07)63GPP TS 29.283 version 15.0.0 Release 15Foreword This Technical Specificat

33、ion has been produced by the 3rdGeneration 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 a

34、n identifying change of release date and 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

35、 changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 129 283 V15.0.0 (2018-07)73GPP TS 29.283 version 15.0.0 Release 151 Scope The common functional architectur

36、e for support of Mission Critical (MC) services is specified in 3GPP TS 23.280 21. The functional architecture for support of Mission Critical Push To Talk (MCPTT) services is specified in 3GPP TS 23.379 18. The functional architecture for support of Mission Critical Video (MCVideo) services is spec

37、ified in 3GPP TS 23.281 19. The functional architecture for support of Mission Critical Data (MCData) services is specified in 3GPP TS 23.282 20. This 3GPP Technical Specification (TS) specifies: 1. The interactions between the MC Service User Database and the MC Service Server: - This interface bet

38、ween the MCPTT User Database and the MCPTT Server is referred to as the MCPTT-2 reference point, as specified in 3GPP TS 23.379 18. - This interface between the MCVideo User Database and the MCVideo Server is referred to as the MCVideo-2 reference point, as specified in 3GPP TS 23.281 19. - This int

39、erface between the MCData User Database and the MCData Server is referred to as the MCData-2 reference point, as specified in 3GPP TS 23.282 20. - This interface between the MCData User Database and the MCData Server is referred to as the MCVideo-2 reference point, as specified in 3GPP TS 23.282 20.

40、 2. The interactions between the MC Service User Database and the Configuration Management Server. This interface is referred to as the CSC-13 reference point. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document

41、. - References are either 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 (incl

42、uding a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 Void. 3 Void. 4 3GPP TS 33.210: “3G security; Network Domain Security (NDS); IP network laye

43、r security“. 5 IETF RFC 4960: “Stream Control Transmission Protocol“. 6 3GPP TS 29.229: “Cx and Dx interfaces based on the Diameter protocol; Protocol details“. 7 IETF RFC 5234:“Augmented BNF for Syntax Specifications: ABNF“. 8 IETF RFC 7944: “Diameter Routing Message Priority“. 9 3GPP TS 29.329: “S

44、h interface based on the Diameter protocol; Protocol details“. ETSI ETSI TS 129 283 V15.0.0 (2018-07)83GPP TS 29.283 version 15.0.0 Release 1510 3GPP TS 29.336: “Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications“. 11 IETF RFC 7683: “Diameter

45、 Overload Indication Conveyance“. 12 3GPP TS 23.003: “Numbering, addressing and identification“. 13 3GPP TS 24.229: “IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3“. 14 3GPP TS 29.228: “IP Multimedia (IM) Subsystem Cx an

46、d Dx Interfaces; Signalling flows and message contents“. 15 IETF RFC 3986:“Uniform Resource Identifier (URI): Generic Syntax“. 16 Void. 17 IETF draft-ietf-dime-load-07: “Diameter Load Information Conveyance“. Editors note: The above document cannot be formally referenced until it is published as an

47、RFC. 18 3GPP TS 23.379: “Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2“. 19 3GPP TS 23.281: “Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2“. 20 3GPP TS 23.282: “Functional architecture and

48、information flows to support Mission Critical Data (MCData); Stage 2“. 21 3GPP TS 23.280: “Common functional architecture to support mission critical services; Stage 2“. 22 3GPP TS 24.484: “Mission Critical Services (MCS) configuration management; Protocol specification“. 23 IETF RFC 6733: “Diameter

49、 Base Protocol“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 1, in 3GPP TS 23.281 19, in 3GPP TS 23.282 20, in 3GPP TS 23.280 21, in 3GPP TS 23.379 18 and the following apply, if any. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 1, in 3GPP TS 23.281 19, in 3GPP TS 23.282 20, in 3GPP TS 23.280 21, in 3GPP TS 23.379 18 and the following a