1、 ETSI TS 132 300 V15.0.0 (2018-07) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Configuration Management (CM); Name convention for Managed Objects (3GPP TS 32.300 version 15.0.0 Release 15) TECHNICA
2、L SPECIFICATION ETSI ETSI TS 132 300 V15.0.0 (2018-07)13GPP TS 32.300 version 15.0.0 Release 15Reference RTS/TSGS-0532300vf00 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
3、 Association but 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/o
4、r 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 only prevailing document is the print of the Portable Document Format (PDF) version k
5、ept on a specific 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.
6、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 photocopyi
7、ng 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 2018. All rights reserved. DECTTM, PLUGTESTSTM, U
8、MTSTMand the ETSI logo are trademarks of ETSI registered for the benefit 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 trademar
9、ks registered and owned by the GSM Association. ETSI ETSI TS 132 300 V15.0.0 (2018-07)23GPP TS 32.300 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 t
10、o 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. L
11、atest 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 ETS
12、I 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 prope
13、rty 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. Foreword This Technical Specification (TS) has
14、 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 interpreted as being references to the corresponding ETSI deliverables. The cross re
15、ference 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“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described i
16、n 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 132 300 V15.0.0 (2018-07)33GPP TS 32.300 version 15.0.0 Release 15Contents Intellectual Property Right
17、s 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 7g32 References 7g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.1.1 Void 8g33.1.2 Void 8g33.1.3 Managed Object and Network Resource 8g33.1.4 Name . 8g33.1.5 Name space . 8g33.1.6 Global Root and Local Ro
18、ot . 9g33.1.7 Distinguished Name and Relative Distinguished Name . 9g33.2 Abbreviations . 9g34 System overview 10g34.1 System context . 10g35 Name Convention for Managed Objects 10g36 Representations of Distinguished Name (DN) . 11g37 String Representation of DN 12g37.A Overview 12g37.B Allowed char
19、acter sets 12g37.1 Converting DN from ASN.1 to String 12g37.1.1 Rule for one-string DN . 12g37.1.1.1 Converting RDNSequence . 12g37.1.1.2 Converting RelativeDistinguishedName . 13g37.1.1.3 Converting AttributeTypeAndValue . 13g37.1.2 Rule for multi-string DN . 13g37.1.2.1 Converting RDNSequence . 13
20、g37.1.2.2 Converting RelativeDistinguishedName 13g37.1.2.3 Converting AttributeTypeAndValue 13g37.2 Character syntax . 14g37.3 EBNF of DN String Representation . 14g37.4 Maximum size of DN string . 17g38 Examples of DN in string representation . 18g39 Usage Scenario . 19g39.1 DN prefix usage . 19g3A
21、nnex A (normative): Mapping of RDN AttributeType to Strings 20g3Annex B (normative): Rule for MO Designers regarding AttributeType interpretation . 21g3Annex C (informative): DN Prefix and Local Distinguished Name (LDN) . 23g3Annex D (informative): Interpreting EBNF 13 . 25g3Annex E (informative): I
22、OC/MOC name recommendation . 27g3Annex F (informative): Change history . 28g3ETSI ETSI TS 132 300 V15.0.0 (2018-07)43GPP TS 32.300 version 15.0.0 Release 15History 29g3ETSI ETSI TS 132 300 V15.0.0 (2018-07)53GPP TS 32.300 version 15.0.0 Release 15Foreword This Technical Specification has been produc
23、ed 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 identifying chang
24、e 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 substan
25、ce, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of
26、 the 3G network as it evolves. CM actions have the objective to control and monitor the actual configuration on the Network Elements (NEs) and Network Resources (NRs), and they may be initiated by the operator or by functions in the Operations Systems (OSs) or NEs. CM actions may be requested as par
27、t of an implementation programme (e.g. additions and deletions), as part of an optimisation programme (e.g. modifications), and to maintain the overall Quality of Service (QoS). The CM actions are initiated either as single actions on single NEs of the 3G network, or as part of a complex procedure i
28、nvolving actions on many resources/objects in one or several NEs. Background Traditionally, multiple name conventions have been used by different vendors NEs, or even within the same vendor, to name network resources. The following problems have thus arisen: - Different classes of NE have used diffe
29、rent name conventions. Network Management applications, when interfacing with these NEs, have been required to understand multiple name conventions to manage the NEs. - Network management applications (e.g. Fault Management application), when interfacing with other applications (e.g. Configuration M
30、anagement application, trouble ticket system) have been required to understand multiple name conventions. - When a customer purchased multiple classes of NEs from the same or different vendors, the customer was confronted with multiple name conventions. - Without a name convention, it is difficult t
31、o integrate IRP conformant vendors resource name space (see subclause 3.1.5 for definition of name space) into the customers Enterprise name space. Benefits The benefits of using the subject name convention to name 3G network resources for network management purposes are as follows: - A resource nam
32、e is guaranteed to be unambiguous in that it refers to, at most, one network resource. Unambiguous naming of managed network resources is necessary for interoperability among managing applications and systems. ETSI ETSI TS 132 300 V15.0.0 (2018-07)63GPP TS 32.300 version 15.0.0 Release 15- The resou
33、rce name syntax is specified such that management applications can be designed with assurance that its name-parsing algorithm needs not be modified in the future. We can derive this benefit only if the subject name convention is widely accepted. The root and upper portions of the name hierarchy are
34、based on name infrastructure of Domain Name System (DNS) (see IETF RFC 2247 5). The subject name convention can naturally fit in DNS and can integrate well with other hierarchical naming systems, such as ITU-T Recommendation X.500 2. ETSI ETSI TS 132 300 V15.0.0 (2018-07)73GPP TS 32.300 version 15.0
35、.0 Release 151 Scope A more detailed background and introduction of the IRP concept is given in 3GPP TS 32.150 16. To perform network management tasks, co-operating applications require identical interpretation of names assigned to network resources under management. Such names are required to be un
36、ambiguous as well. The present document recommends one name convention for network resources under management in the IRP context. To facilitate integration of network management information obtained via multiple IRPs based on different IRP Solution Set technologies, identical network resource name s
37、emantics shall be conveyed in all IRPs. The present document specifies one such name convention. The present document also specifies an IOC/MOC name recommendation (see annex E) in order to avoid potential problems with valid characters in some programming languages. In this document, the name conve
38、ntion and name recommendation (see annex E) are specified for MO instances whose MO class stereotype is IOC. These specifications are also for MO instances whose MO class stereotype is Support IOC (SupportIOC). 2 References The following documents contain provisions which, through reference in this
39、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.
40、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 Void. 2 ITU-T Recommendation X.500 (1993): “Information technology - Open Systems Interconnection
41、 - The Directory: Overview of concepts, models and services“. 3 T. Howes, ISBN 1-57870-070-1: “Understanding and Deploying LDAP Directory Services“. 4 IETF RFC 1737 (1994): “Functional Requirements for Uniform Resource Names“. 5 IETF RFC 2247 (1998): “Using Domains in LDAP/X.500 Distinguished Names“
42、. 6 IETF RFC 1035 (1987): “Domain names - implementation and specification“. 7 IETF RFC 2253 (1997): “Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names“. 8 3GPP TS 32.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integration Refere
43、nce Point (IRP): Information Service (IS)“. 9 3GPP TS 32.622: “ Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 10 Void. 11 3GPP TS 32.101: “Telecommunication management; Principles and high leve
44、l requirements“. 12 3GPP TS 32.102: “Telecommunication management; Architecture“. 13 ISO/IEC 14977: “Information technology Syntactic metalanguage Extended BNF“. ETSI ETSI TS 132 300 V15.0.0 (2018-07)83GPP TS 32.300 version 15.0.0 Release 1514 ISO/IEC 646: “Information technology ISO 7-bit coded cha
45、racter set for information interchange“. 15 ISO/IEC 10646: “Information technology Universal multiple-octet Coded Character Set (UCS)“. 16 3GPP TS 32.150: “Integration Reference Point (IRP) Concept and definitions“. 17 3GPP2 S.S0028-E “OAM, U+003B), - reverse solidus character (, U+005C), - quotatio
46、n mark character (“, U+0022). 2. The full stop character (., U+002E). This character may be used in the AttributeValue whose AttributeType is “DC“. An example is “DC=marketing.CompanyXYZ.com“. This full stop character shall not be used in AttributeType. 3. The asterisk character (*, U+002A) is reser
47、ved to denote wildcard. Wildcard can be used as input to search or filter capabilities based on DN. For example, a client is not sure of the exact spelling of the AttributeValue (see clause 7.3), the client can use wildcard to represent one or more characters which are legal in that field. The aster
48、isk character shall not be used in DN. 7.3 EBNF of DN String Representation The formal definitions provided within this subclause consolidate several rules and concepts (null distinguished name, DN prefix, local DN, domain component type, class names starting with upper case characters, attribute na
49、mes starting with lower case characters, classes with or without an “Id“ naming attribute, attribute type and attribute value allowed characters, wildcard character). The following is the EBNF for DN in string representation (Extended Backus-Naur Form; see ISO/IEC 14977 13 for more information): DistinguishedName =NullDN| RegularDN ; (*See size consideration in subclause 7.4 *) NullDN = ; (* empty string; null DN is specified in subclause 7.1.1 *) RegularDN = DNPrefixPlusRDNSeparator
