LTE; Universal Mobile Telecommunications System (UMTS); Diameter data management applications (3GPP TS 29.283 version 14.4.0 Release 14)

RTS/TSGC-0429283ve40

General Information

Status
Published
Publication Date
02-Oct-2019
Current Stage
12 - Completion
Completion Date
03-Oct-2019
Ref Project

Buy Standard

Standard
ETSI TS 129 283 V14.4.0 (2019-10) - LTE; Universal Mobile Telecommunications System (UMTS); Diameter data management applications (3GPP TS 29.283 version 14.4.0 Release 14)
English language
41 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

ETSI TS 129 283 V14.4.0 (2019-10)






TECHNICAL SPECIFICATION
LTE;
Universal Mobile Telecommunications System (UMTS);
Diameter data management applications
(3GPP TS 29.283 version 14.4.0 Release 14)

---------------------- Page: 1 ----------------------
3GPP TS 29.283 version 14.4.0 Release 14 1 ETSI TS 129 283 V14.4.0 (2019-10)



Reference
RTS/TSGC-0429283ve40
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 enregistrée à la
Sous-Préfecture 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 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 prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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 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 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.

© ETSI 2019.
All rights reserved.

DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3GPP TS 29.283 version 14.4.0 Release 14 2 ETSI TS 129 283 V14.4.0 (2019-10)
Intellectual 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: "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, 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 include 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 present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
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. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 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 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

---------------------- Page: 3 ----------------------
3GPP TS 29.283 version 14.4.0 Release 14 3 ETSI TS 129 283 V14.4.0 (2019-10)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions, symbols and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Main Concept . 8
4.1 Introduction . 8
5 MC Service General Architecture . 9
5.1 Introduction . 9
5.2 Functional requirements of network entities . 9
5.2.1 Functional Requirements of the MC Service Server . 9
5.2.2 Functional Requirements of the Configuration Management Server . 9
5.2.3 Functional requirements of MCPTT User Database . 9
5.3 Functional classification of MC Service Server to MC Service User Database related interface
procedures . 10
5.4 Functional classification of CSC-13 interface procedures . 10
6 Procedure Descriptions for MC Services . 11
6.1 Introduction . 11
6.2 MC Service User data handling procedures . 11
6.2.1 Data Pull . 11
6.2.1.1 General . 11
6.2.1.2 Detailed behaviour of the requesting entity . 12
6.2.1.3 Detailed behaviour of the MC Service User Database . 12
6.2.2 Data Update . 13
6.2.2.1 General . 13
6.2.2.2 Detailed behaviour of the Configuration Management Server . 14
6.2.2.3 Detailed behaviour of the MC Service User Database . 15
6.2.3 Data Notification . 16
6.2.3.1 General . 16
6.2.3.2 Detailed behaviour of the MCPTT User Database . 17
6.2.3.3 Detailed behaviour of the receiving entity . 17
6.3 Requesting entity permissions list . 18
6.3.1 General . 18
7 Protocol Specification and Implementation for MC Service. 19
7.1 General . 19
7.1.1 Use of Diameter base protocol . 19
7.1.2 Securing Diameter Messages . 19
7.1.3 Accounting functionality . 19
7.1.4 Use of sessions . 20
7.1.5 Transport protocol . 20
7.1.6 Routing considerations . 20
7.1.7 Advertising Application Support . 21
7.1.8 Diameter Application Identifier . 21
7.1.9 Use of the Supported-Features AVP . 21
7.1.10 MC Service ID to MC Service User Database resolution . 21
7.2 Commands . 23
7.2.1 Introduction. 23
7.2.2 Command-Code values . 23
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 29.283 version 14.4.0 Release 14 4 ETSI TS 129 283 V14.4.0 (2019-10)
7.2.3 Data-Pull-Request (DPR) Command . 23
7.2.4 Data-Pull-Answer (DPA) Command . 24
7.2.5 Data-Update-Request (DUR) Command . 24
7.2.6 Data-Update-Answer (DUA) Command . 24
7.2.7 Notification-Data-Request (PDR) Command . 25
7.2.8 Notification-Data-Answer (PDA) Command . 25
7.3 AVPs . 26
7.3.1 General . 26
7.3.2 MCPTT-ID . 27
7.3.3 Requested-Data . 27
7.3.4 DRMP . 27
7.3.5 OC-OLR . 27
7.3.6 OC-Supported-Features . 27
7.3.7 User-Data . 27
7.3.8 User-Identifier . 28
7.3.9 Feature-List-ID AVP . 28
7.3.10 Feature-List AVP . 28
7.3.11 Data-Identification-Prefix . 28
7.3.12 Data-Identification-Flags . 28
7.3.13 DPR-Flags. 29
7.3.14 DPA-Flags . 29
7.3.15 DUR-Flags . 29
7.3.16 DUA-Flags . 30
7.3.17 NDR-Flags . 30
7.3.18 NDA-Flags . 30
7.3.19 User-Data-Id . 30
7.3.20 MC-Service-User-Profile-Data . 30
7.3.21 Sequence-Number . 31
7.3.22 Data . 31
7.3.23 Load . 31
7.3.24 MCVideo-ID . 31
7.3.25 MCData-ID . 31
7.4 Result-Code and Experimental-Result-Code Values . 31
7.4.1 Introduction. 31
7.4.2 Success . 31
7.4.2.1 General . 31
7.4.3 Permanent Failures . 32
7.4.3.1 General . 32
7.4.3.2 DIAMETER_ERROR_USER_UNKNOWN (5001) . 32
7.4.3.3 DIAMETER_ERROR_USER_DATA_NOT_RECOGNIZED (5100) . 32
7.4.3.4 DIAMETER_ERROR_OPERATION_NOT_ALLOWED (5101) . 32
7.4.3.5 DIAMETER_ERROR_USER_DATA_CANNOT_BE_READ (5102) . 32
7.4.3.6 DIAMETER_ERROR_USER_DATA_CANNOT_BE_MODIFIED (5103) . 32
7.4.3.7 DIAMETER_ERROR_USER_DATA_CANNOT_BE_NOTIFIED (5104) . 32
7.4.3.8 DIAMETER_ERROR_TOO_MUCH_DATA (5008) . 32
7.4.3.9 DIAMETER_ERROR_DATA OUT_OF_SYNC (5105) . 32
7.4.3.10 DIAMETER_ERROR_FEATURE_UNSUPPORTED (5011) . 32
7.4.3.11 DIAMETER_ERROR_NO_SUBSCRIPTION_TO_DATA (5107) . 32
7.4.3.12 DIAMETER_ERROR_ UNKNOWN _DATA (5670) . 33
7.4.3.13 DIAMETER_ERROR_REQUIRED_KEY_NOT_PROVIDED (5671) . 33
7.4.4 Transient Failures . 33
7.4.4.1 General . 33
7.4.4.2 DIAMETER_USER_DATA_NOT_AVAILABLE (4100) . 33
7.4.4.3 DIAMETER_PRIOR_UPDATE_IN_PROGRESS (4101) . 33
Annex A (normative): Diameter overload control mechanism . 34
A.1 General . 34
A.2 MC Service User Database behaviour . 34
A.3 MC Service Server and Configuration Management Server behaviour . 34
Annex B (Informative): Diameter overload node behaviour . 35
B.1 Message prioritization . 35
ETSI

---------------------- Page: 5 ----------------------
3GPP TS 29.283 version 14.4.0 Release 14 5 ETSI TS 129 283 V14.4.0 (2019-10)
Annex C (normative): Diameter message priority mechanism . 36
C.1 General . 36
C.2 MCPTT-2, MCVideo-2, MCData-2 and CSC-13 interfaces . 36
C.2.1 General . 36
C.2.2 MC Service Server and Configuration Management Server behaviour . 36
C.2.3 MC Service User Database behaviour . 37
Annex D (normative): Diameter load control mechanism . 38
D.1 General . 38
D.2 MC Service User Database behaviour . 38
D.3 MC Service Server and Configuration Management Server behaviour . 38
Annex E (informative): Change history . 39
History . 40


ETSI

---------------------- Page: 6 ----------------------
3GPP TS 29.283 version 14.4.0 Release 14 6 ETSI TS 129 283 V14.4.0 (2019-10)
Foreword
rd
This Technical Specification has been produced by the 3 Generation 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 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 enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 29.283 version 14.4.0 Release 14 7 ETSI TS 129 283 V14.4.0 (2019-10)
1 Scope
The common functional architecture 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 specified 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 between 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 interface 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].
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.
- 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 (including
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 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 for Syntax Specifications: ABNF".
[8] IETF RFC 7944: "Diameter Routing Message Priority".
[9] 3GPP TS 29.329: "Sh interface based on the Diameter protocol; Protocol details".
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 29.283 version 14.4.0 Release 14 8 ETSI TS 129 283 V14.4.0 (2019-10)
[10] 3GPP TS 29.336: "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 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".
[16] Void.
[17] IETF RFC 8583: "Diameter Load Information Conveyance".
Editor's note: The above document cannot be formally referenced until it is published as an 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 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 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 apply, if any. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
4 Main C
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.