1、 ETSI TS 1Universal Mobile TelDiameter dat(3GPP TS 29.2TECHNICAL SPECIFICATION129 283 V13.0.0 (2016LTE; elecommunications System (ata management applications.283 version 13.0.0 Release 1316-05) (UMTS); ns 13) ETSI ETSI TS 129 283 V13.0.0 (2016-05)13GPP TS 29.283 version 13.0.0 Release 13Reference DT
2、S/TSGC-0429283vd00 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 presen
3、t 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 of the present document shall not be modified without the prior written authorization of ETSI.
4、 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 network drive within ETSI Secretariat. Users of the present document should be aware that the
5、 document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: https:/portal
6、.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 except as authorized by written permission of ETSI. The content of the PDF version shall not be modified
7、 without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of i
8、ts 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 the GSM Association. ETSI ETSI TS 129 283 V13.0.0 (2016-05)23GPP TS 29.283 version 13.0.0 Release 13Intel
9、lectual 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 available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Righ
10、ts (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, including IPR searches, ha
11、s 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. Foreword This Technical Specification (TS) has been produced by ET
12、SI 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 interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM,
13、 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“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the
14、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 283 V13.0.0 (2016-05)33GPP TS 29.283 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3M
15、odal verbs terminology 2g3Foreword . 6g31 Scope 7g32 References 7g33 Definitions, symbols and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 8g34 Main Concept . 8g34.1 Introduction 8g35 MCPTT General Architecture 8g35.1 Introduction 8g35.2 Functional requirements of network entities 8g35.
16、2.1 Functional Requirements of the MCPTT Server 8g35.2.2 Functional Requirements of the Configuration Management Server 8g35.2.3 Functional requirements of MCPTT User Database . 9g35.3 Functional classification of MCPTT-2 interface procedures 9g35.4 Functional classification of CSC-13 interface proc
17、edures . 9g36 Procedure Descriptions for MCPTT . 9g36.1 Introduction 9g36.2 MCPTT User data handling procedures . 10g36.2.1 Data Pull . 10g36.2.1.1 General 10g36.2.1.2 Detailed behaviour of the requesting entity 11g36.2.1.3 Detailed behaviour of the MCPTT User Database 11g36.2.2 Data Update 12g36.2.
18、2.1 General 12g36.2.2.2 Detailed behaviour of the Configuration Management Server 13g36.2.2.3 Detailed behaviour of the MCPTT User Database 14g36.2.3 Data Notification 15g36.2.3.1 General 15g36.2.3.2 Detailed behaviour of the MCPTT User Database 16g36.2.3.3 Detailed behaviour of the receiving entity
19、 17g36.3 Requesting entity permissions list 17g36.3.1 General 17g37 Protocol Specification and Implementation for MCPTT . 18g37.1 General . 18g37.1.1 Use of Diameter base protocol 18g37.1.2 Securing Diameter Messages 18g37.1.3 Accounting functionality 18g37.1.4 Use of sessions 18g37.1.5 Transport pr
20、otocol 19g37.1.6 Routing considerations . 19g37.1.7 Advertising Application Support 19g37.1.8 Diameter Application Identifier 20g37.1.9 Use of the Supported-Features AVP . 20g37.1.10 MCPTT ID to MCPTT User Database resolution. 20g37.2 Commands 22g37.2.1 Introduction. 22g37.2.2 Command-Code values .
21、22g3ETSI ETSI TS 129 283 V13.0.0 (2016-05)43GPP TS 29.283 version 13.0.0 Release 137.2.3 Data-Pull-Request (DPR) Command 22g37.2.4 Data-Pull-Answer (DPA) Command 23g37.2.5 Data-Update-Request (DUR) Command 23g37.2.6 Data-Update-Answer (DUA) Command 23g37.2.7 Notification-Data-Request (PDR) Command .
22、 24g37.2.8 Notification-Data-Answer (PDA) Command . 24g37.3 Information Elements . 25g37.3.1 General 25g37.3.2 MCPTT-ID . 26g37.3.3 Requested-Data . 26g37.3.4 DRMP . 26g37.3.5 OC-OLR . 26g37.3.6 OC-Supported-Features 26g37.3.7 User-Data 27g37.3.8 User-Identifier . 27g37.3.9 Feature-List-ID AVP 27g37
23、.3.10 Feature-List AVP 27g37.3.11 Requested-Data-Index 27g37.3.12 Requested-Data-Flags . 27g37.3.13 DPR-Flags. 28g37.3.14 DPA-Flags 28g37.3.15 DUR-Flags 28g37.3.16 DUA-Flags 28g37.3.17 NDR-Flags 29g37.3.18 NDA-Flags 29g37.3.19 Data-Index 29g37.3.20 MCPTT-User-Profile-Data . 29g37.3.21 Sequence-Numbe
24、r . 29g37.4 Result-Code and Experimental-Result-Code Values 30g37.4.1 Introduction. 30g37.4.2 Success 30g37.4.2.1 General 30g37.4.3 Permanent Failures . 30g37.4.3.1 General 30g37.4.3.2 DIAMETER_ERROR_USER_UNKNOWN (5001) 30g37.4.3.3 DIAMETER_ERROR_USER_DATA_NOT_RECOGNIZED (5100) . 30g37.4.3.4 DIAMETE
25、R_ERROR_OPERATION_NOT_ALLOWED (5101) . 30g37.4.3.5 DIAMETER_ERROR_USER_DATA_CANNOT_BE_READ (5102) 30g37.4.3.6 DIAMETER_ERROR_USER_DATA_CANNOT_BE_MODIFIED (5103) . 30g37.4.3.7 DIAMETER_ERROR_USER_DATA_CANNOT_BE_NOTIFIED (5104) 30g37.4.3.8 DIAMETER_ERROR_TOO_MUCH_DATA (5008) 30g37.4.3.9 DIAMETER_ERROR
26、_DATA OUT_OF_SYNC (5105) . 31g37.4.3.10 DIAMETER_ERROR_FEATURE_UNSUPPORTED (5011) . 31g37.4.2.11 DIAMETER_ERROR_NO_SUBSCRIPTION_TO_DATA (5107) . 31g37.4.3.12 DIAMETER_ERROR_UNKNKOWN_DATA (51x1) 31g37.4.3.13 DIAMETER_ERROR_REQUIRED_KEY_NOT_PROVIDED (51x2) . 31g37.4.4 Transient Failures . 31g37.4.4.1
27、General 31g37.4.3.2 DIAMETER_USER_DATA_NOT_AVAILABLE (4100) 31g37.4.3.3 DIAMETER_PRIOR_UPDATE_IN_PROGRESS (4101) . 31g3Annex A (normative): Diameter overload control mechanism 32g3A.1 General . 32g3A.2 MCPTT User Database behaviour 32g3A.3 MCPTT Server and Configuration Management Server behaviour .
28、 32g3Annex B (Informative): Diameter overload node behaviour 33g3B.1 Message prioritization 33g3Annex C (normative): Diameter message priority mechanism 34g3C.1 General . 34g3C.2 MCPTT-2 and CSC-13 interfaces 34g3ETSI ETSI TS 129 283 V13.0.0 (2016-05)53GPP TS 29.283 version 13.0.0 Release 13C.2.1 Ge
29、neral 34g3C.2.2 MCPTT Server and Configuration Management Server behaviour 34g3C.2.3 MCPTT User Database behaviour 34g3Annex D (informative): Change history . 35g3History 36g3ETSI ETSI TS 129 283 V13.0.0 (2016-05)63GPP TS 29.283 version 13.0.0 Release 13Foreword This Technical Specification has been
30、 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 an identifyin
31、g 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 changes of
32、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 V13.0.0 (2016-05)73GPP TS 29.283 version 13.0.0 Release 131 Scope This 3GPP Technical Specification (TS) specif
33、ies: 1. The interactions between the MCPTT User Database and the MCPTT Server. This interface is referred to as the MCPTT-2 reference point. 2. The interactions between the MCPTT User Database and the Configuration Management Server. This interface is referred to as the CSC-13 reference point. The f
34、unctional architecture for support of mission critical communication services is specified in 3GPP TS 23.179 2. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified b
35、y 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), a non-specific reference
36、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 3GPP TS 23.179: “Functional architecture and information flows to support mission critical communication services; Stage 2“. 3 IETF RFC 3588
37、: “Diameter Base Protocol“. 4 3GPP TS 33.210: “3G security; Network Domain Security (NDS); IP network layer 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 fo
38、r Syntax Specifications: ABNF“. 8 IETF draft-ietf-dime-drmp-03: “Diameter Routing Message Priority“. Editors note: The above document cannot be formally referenced until it is published as an RFC. 9 3GPP TS 29.329: “Sh interface based on the Diameter protocol; Protocol details“. 10 3GPP TS 29.336: “
39、Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications“. 11 IETF RFC 7683: “Diameter Overload Indication Conveyance“. 12 3GPP TS 23.003: “Numbering, addressing and identification“. 13 3GPP TS 24.229: “IP multimedia call control protocol based on
40、Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3“. 14 3GPP TS 29.228: “IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents“. 15 IETF RFC 3986:“Uniform Resource Identifier (URI): Generic Syntax“. ETSI ETSI TS 129 283 V13.0.0 (2016-
41、05)83GPP TS 29.283 version 13.0.0 Release 1316 3GPP TS 24.384: “Mission Critical Push To Talk (MCPTT) configuration management; Protocol specification“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR 21.90
42、5 1 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.179 2 and the following apply, if any. An abbreviation defined in the present document takes precedence over the definition of the same abbrevia
43、tion, if any, in 3GPP TR 21.905 1. 4 Main Concept 4.1 Introduction The MCPTT-2 reference point (between the MCPTT Server and the MCPTT User Database) and the CSC-13 reference (between the Configuration Management and the MCPTT User Database) are defined in the 3GPP TS 23.179 2. This document describ
44、es the Diameter-based MCPTT-2 and CSC-13 related procedures, message parameters and protocol specification. This document specifies the Diameter Management Application used as protocol over the MCPTT-2 and CSC-13 reference points. 5 MCPTT General Architecture 5.1 Introduction This section further sp
45、ecifies the architectural assumptions associated with the MCPTT-2 and CSC-13 reference points, building on 3GPP TS 23.179 2. 5.2 Functional requirements of network entities 5.2.1 Functional Requirements of the MCPTT Server The MCPTT Server may communicate with the MCPTT User Database over the MCPTT-
46、2 interface. For more details on the functionality of the MCPTT Server, refer to 3GPP TS 23.179 2. 5.2.2 Functional Requirements of the Configuration Management Server The Configuration Management Server may communicate with the MCPTT User Database over the CSC-13 interface. For more details on the
47、functionality of the Configuration Management Server, refer to 3GPP TS 23.179 2. ETSI ETSI TS 129 283 V13.0.0 (2016-05)93GPP TS 29.283 version 13.0.0 Release 135.2.3 Functional requirements of MCPTT User Database The MCPTT User Database may communicate with the MCPTT Server over the MCPTT-2 interfac
48、e. The MCPTT User Database may communicate with the Configuration Management Server over the CSC-13 interface. For more details on the functionality of the MCPTT User Database, refer to 3GPP TS 23.179 2. 5.3 Functional classification of MCPTT-2 interface procedures Operations on the MCPTT-2 interfac
49、e are classified in functional groups: 1. Data handling procedures - The download of data from the MCPTT User Database to an MCPTT Server. - The subscription to notifications from the MCPTT User Database when particular information about a specific MCPTT User is updated. - The MCPTT User Database can notify an MCPTT Server of changes in data for which the MCPTT Server previously had subscribed. 5.4 Functional classification of CSC-13 interface procedures Operations on the CSC-13 interface are classified in functional groups
