1、 ETSI TS 124 105 V15.0.0 (2018-06) Universal Mobile Telecommunications System (UMTS); LTE; Application specific Congestion control for Data Communication (ACDC) Management Object (MO) (3GPP TS 24.105 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 124 105 V15.0.0 (2018-06)13GPP TS 24
2、.105 version 15.0.0 Release 15Reference RTS/TSGC-0124105vf00 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
3、(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 withou
4、t 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 network drive within ETSI Secretariat. Users of the
5、 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 com
6、ment 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.
7、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 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the bene
8、fit of its Members. 3GPPTM and LTETMare trademarks of ETSI 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 124 105
9、V15.0.0 (2018-06)23GPP TS 24.105 version 15.0.0 Release 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 member
10、s 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.o
11、rg/). 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 p
12、resent 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 a
13、nd/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. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The
14、 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, UMTS, 3GPP and ETSI identities can be found unde
15、r 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 express
16、ion of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 124 105 V15.0.0 (2018-06)33GPP TS 24.105 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5
17、g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 ACDC MO . 6g35 ACDC MO parameters . 6g35.1 General . 6g35.2 Node: . 6g35.3 /Name . 6g35.4 ACDC . 7g35.4.1 /ACDC 7g35.4.2 /ACDC/ . 7g35.4.3 /ACDC/ACDCConf . 7 g35.4.4 /ACDC/ACDCConf/ . 7g35.4.5 /ACDC/AC
18、DCConf/ApplicationInfo . 7g35.4.6 /ACDC/ACDCConf/ApplicationInfo/ . 8g35.4.7 /ACDC/ACDCConf/ApplicationInfo/App-ID . 8g35.4.8 /ACDC/ACDCConf/ApplicationInfo/App-ID/ . 8g35.4.9 /ACDC/ACDCConf/ApplicationInfo/App-ID/OSId 8g35.4.10 /ACDC/ACDCConf/ApplicationInfo/App-ID/OSApps . 8g35.4.11 /ACDC/ACDCConf
19、/ApplicationInfo/App-ID/OSApps/ . 9g35.4.12 /ACDC/ACDCConf/ApplicationInfo/App-ID/OSApps/OSAppId. 9g35.4.13 /ACDC/ACDCConf/ACDCCategory . 9g35.5 /Ext . 10g3Annex A (informative): ACDC MO DDF . 11g3Annex B (informative): Change history . 16g3History 17g3ETSI ETSI TS 124 105 V15.0.0 (2018-06)43GPP TS
20、24.105 version 15.0.0 Release 15Foreword This Technical Specification 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
21、 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 docume
22、nt 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 ETSI TS 124 105 V15.0.0 (2018-06)53GPP TS 24.105
23、version 15.0.0 Release 151 Scope The present document defines Management Object (MO) that is used to configure the UE with parameters related to Application specific Congestion control for Data Communication (ACDC) functionality. The MO is compatible with the OMA Device Management (DM) protocol spec
24、ifications, version 1.2 and upwards, and is defined using the OMA DM Device Description Framework (DDF) as described in the Enabler Release Definition OMA-ERELD-DM-V1_2 3. The MO consists of relevant parameters for provisioning of ACDC at a UE. 2 References The following documents contain provisions
25、 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 refer
26、ence, 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 3GPP TS
27、 22.011: “Service accessibility“. 3 OMA-ERELD-DM-V1_2: “Enabler Release Definition for OMA Device Management“. 4 3GPP TS 23.003: “Numbering, addressing and identification“. 5 3GPP TS 31.102: “Characteristics of the USIM Application“. 6 IETF RFC 3629 (November 2003): “UTF-8, a transformation format o
28、f ISO 10646“. 7 IETF RFC 4122 (July 2005): “A Universally Unique IDentifier (UUID) URN Namespace“. 8 “Unicode 5.1.0, Unicode Standard Annex #15; Unicode Normalization Forms“, March 2008. http:/www.unicode.org 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, t
29、he terms and definitions given in 3GPP TR 21.905 1 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 1. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905
30、 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 1. ACDC Application specific Congestion control for Data Communication ETSI ETSI TS 124 105 V15.0.0 (2018-06)63GPP TS 24.105 version 15
31、.0.0 Release 154 ACDC MO The ACDC MO is used to manage configuration parameters related to ACDC functionality for a UE supporting provisioning of such information. The presence and format of the ACDC configuration file on the USIM is specified in 3GPP TS 31.102 5. The MO identifier is: urn:oma:mo:ex
32、t-3gpp-ACDC-config:1.0. The OMA DM Access Control List (ACL) property mechanism (see OMA-ERELD-DM-V1_2 3) may be used to grant or deny access rights to OMA DM servers in order to modify nodes and leaf objects of the ACDC MO. The following nodes and leaf objects are possible in the ACDC MO as describ
33、ed in figure 4.1.1 through figure 4.1.2: Figure 4.1.1: The ACDC Management Object Figure 4.1.2: The ACDC Configuration 5 ACDC MO parameters 5.1 General This clause describes the parameters for the ACDC MO. 5.2 Node: This interior node acts as a placeholder for zero or one accounts for a fixed node.
34、- Occurrence: ZeroOrOne - Format: node - Access Types: Get - Values: 5.3 /Name The Name leaf is a name for the ACDC MO settings. ETSI ETSI TS 124 105 V15.0.0 (2018-06)73GPP TS 24.105 version 15.0.0 Release 15- Occurrence: ZeroOrOne - Format: chr - Access Types: Get - Values: The User displayable nam
35、e shall be represented by Unicode characters encoded as UTF-8 as specified in IETF RFC 3629 6 and formatted using Normalization Form KC (NFKC) as specified in Unicode Standard Annex #15; Unicode Normalization Forms 8. 5.4 ACDC 5.4.1 /ACDC The ACDC node acts as a placeholder for ACDC information. - O
36、ccurrence: ZeroOrOne - Format: node - Access Types: Get, Replace - Values: 5.4.2 /ACDC/ This interior node acts as a placeholder for one or more ACDC policies. - Occurrence: OneOrMore - Format: node - Access Types: Get, Replace - Values: 5.4.3 /ACDC/ACDCConf The ACDCConf node indicates a particular
37、ACDC configuration parameter. - Occurrence: One - Format: node - Access Types: Get, Replace - Values: 5.4.4 /ACDC/ACDCConf/ This interior node acts as a placeholder for one or more ACDC configuration parameter. - Occurrence: OneOrMore - Format: node - Access Types: Get, Replace - Values: 5.4.5 /ACDC
38、/ACDCConf/ApplicationInfo The ApplicationInfo node indicates a particular application information. ETSI ETSI TS 124 105 V15.0.0 (2018-06)83GPP TS 24.105 version 15.0.0 Release 15- Occurrence: One - Format: node - Access Types: Get, Replace - Values: 5.4.6 /ACDC/ACDCConf/ApplicationInfo/ This interio
39、r node acts as a placeholder for one or more ApplicationInfo. - Occurrence: OneOrMore - Format: node - Access Types: Get, Replace - Values: 5.4.7 /ACDC/ACDCConf/ApplicationInfo/App-ID This interior node acts as a placeholder for an ApplicationInfo based on an applicationID. - Occurrence: ZeroOrOne -
40、 Format: node - Access Types: Get, Replace - Values: N/A 5.4.8 /ACDC/ACDCConf/ApplicationInfo/App-ID/ This interior node acts as a placeholder for one or more combinations of OSId and OSAppId values. - Occurrence: OneOrMore - Format: node - Access Types: Get, Replace - Values: 5.4.9 /ACDC/ACDCConf/A
41、pplicationInfo/App-ID/OSId The OSId leaf indicates an operating system identifier. - Occurrence: One - Format: chr - Access Types: Get, Replace - Values: The format of the operating system identifier is a Universally Unique IDentifier (UUID) as specified in IETF RFC 4122 7. 5.4.10 /ACDC/ACDCConf/App
42、licationInfo/App-ID/OSApps This interior node acts as a placeholder for the list of OS specific application identifiers. - Occurrence: One ETSI ETSI TS 124 105 V15.0.0 (2018-06)93GPP TS 24.105 version 15.0.0 Release 15- Format: node - Access Types: Get, Replace - Values: 5.4.11 /ACDC/ACDCConf/Applic
43、ationInfo/App-ID/OSApps/ This interior node acts as a placeholder for an OS specific application identifiers. - Occurrence: OneOrMore - Format: node - Access Types: Get, Replace - Values: 5.4.12 /ACDC/ACDCConf/ApplicationInfo/App-ID/OSApps/OSAppId The OSAppId leaf indicates an OS specific applicatio
44、n identifier. - Occurrence: One - Format: chr - Access Types: Get, Replace - Values: Further definition of the format of the OS specific application identifier is beyond the scope of this specification. 5.4.13 /ACDC/ACDCConf/ACDCCategory The ACDCCategory leaf represents indicates the ACDC category f
45、or which applications matching the ApplicationInfo belongs. - Occurrence: One - Format: int - Access Types: Get, Replace - Values: The ACDC category indicates the category to which the identified application belongs. Table 5.4.13 gives the decode of the ACDC category. The highest ranked ACDC categor
46、y means the ACDC category with the lowest value and a UE treats applications assigned to the highest ranked ACDC category as the least restriction to access attempts. The lowest ranked ACDC category means the ACDC category with the highest value and a UE treats applications assigned to the lowest ra
47、nked ACDC category as the most restriction to access attempts. Table 5.4.13: Values of ACDC category Value Description 0 Reserved 1 Highest ranked ACDC category value 2-15 ACDC category value indicating descending order of ranking 16 Lowest ranked ACDC category value ETSI ETSI TS 124 105 V15.0.0 (20
48、18-06)103GPP TS 24.105 version 15.0.0 Release 155.5 /Ext The Ext is an interior node for where the vendor specific information about the NAS configuration MO is being placed (vendor meaning application vendor, device vendor etc.). Usually the vendor extension is identified by vendor specific name un
49、der the ext node. The tree structure under the vendor identifier is not defined and can therefore include one or more un-standardized sub-trees. - Occurrence: ZeroOrOne - Format: node - Access Types: Get - Values: N/A ETSI ETSI TS 124 105 V15.0.0 (2018-06)113GPP TS 24.105 version 15.0.0 Release 15Annex A (informative): ACDC MO DDF This DDF is the standardized minimal set. A vendor can define its own DDF for the complete device. This DDF can include more features than this minimal
