1、 ETSI TS 1Digital cellular telecommUniversal Mobile TelTelecommConfiguraName conve(3GPP TS 32.3TECHNICAL SPECIFICATION132 300 V13.1.0 (2016mmunications system (Phase elecommunications System (LTE; munication management; ration Management (CM); ention for Managed Objects .300 version 13.1.0 Release 1
2、316-04) e 2+) (GSM); (UMTS); ts 13) ETSI ETSI TS 132 300 V13.1.0 (2016-04)13GPP TS 32.300 version 13.1.0 Release 13Reference RTS/TSGS-0532300vd10 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 5
3、62 00017 - NAF 742 C 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
4、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 only prevailing document is the print of the Portable Document Fo
5、rmat (PDF) version kept 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 http:/portal.etsi.org/tb/sta
6、tus/status.asp 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
7、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. European Telecommunications Standards Instit
8、ute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its 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 Mark
9、s registered and owned by the GSM Association. ETSI ETSI TS 132 300 V13.1.0 (2016-04)23GPP TS 32.300 version 13.1.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPR
10、s, 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 ava
11、ilable 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 a
12、re, or may be, or may become, essential to the present document. Foreword 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, UMTS identities or GSM i
13、dentities. 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 terminology In the present document “shall“, “shall not“, “should
14、“, “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
15、 ETSI TS 132 300 V13.1.0 (2016-04)33GPP TS 32.300 version 13.1.0 Release 13Contents Intellectual Property Rights 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.
16、1.3 Managed Object and Network Resource 8g33.1.4 Name . 8g33.1.5 Name space . 8g33.1.6 Global Root and Local Root . 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 Repre
17、sentations of Distinguished Name (DN) . 11g37 String Representation of DN 12g37.A Overview 12g37.B Allowed character 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
18、Converting AttributeTypeAndValue . 13g37.1.2 Rule for multi-string DN . 13g37.1.2.1 Converting RDNSequence . 13g37.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
19、 DN string . 17g38 Examples of DN in string representation . 18g39 Usage Scenario . 19g39.1 DN prefix usage . 19g3Annex A (normative): Mapping of RDN AttributeType to Strings 20g3Annex B (normative): Rule for MO Designers regarding AttributeType interpretation . 21g3Annex C (informative): DN Prefix
20、and Local Distinguished Name (LDN) . 23g3Annex D (informative): Interpreting EBNF 13 . 25g3Annex E (informative): IOC/MOC name recommendation . 27g3ETSI ETSI TS 132 300 V13.1.0 (2016-04)43GPP TS 32.300 version 13.1.0 Release 13Annex F (informative): Change history . 28g3History 29g3ETSI ETSI TS 132
21、300 V13.1.0 (2016-04)53GPP TS 32.300 version 13.1.0 Release 13Foreword 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. Shou
22、ld 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
23、 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. Introduction Configurati
24、on Management (CM), in general, provides the operator with the ability to assure correct and effective operation of 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 i
25、nitiated by the operator or by functions in the Operations Systems (OSs) or NEs. CM actions may be requested as part 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
26、actions are initiated either as single actions on single NEs of the 3G network, or as part of a complex procedure involving 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 ve
27、ndor, to name network resources. The following problems have thus arisen: - Different classes of NE have used different name conventions. Network Management applications, when interfacing with these NEs, have been required to understand multiple name conventions to manage the NEs. - Network manageme
28、nt applications (e.g. Fault Management application), when interfacing with other applications (e.g. Configuration Management 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
29、vendors, the customer was confronted with multiple name conventions. - Without a name convention, it is difficult to integrate IRP conformant vendors resource name space (see subclause 3.1.5 for definition of name space) into the customers Enterprise name space. ETSI ETSI TS 132 300 V13.1.0 (2016-04
30、)63GPP TS 32.300 version 13.1.0 Release 13Benefits The benefits of using the subject name convention to name 3G network resources for network management purposes are as follows: - A resource name is guaranteed to be unambiguous in that it refers to, at most, one network resource. Unambiguous naming
31、of managed network resources is necessary for interoperability among managing applications and systems. - The resource 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 ben
32、efit only if the subject name convention is widely accepted. The root and upper portions of the name hierarchy are 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 namin
33、g systems, such as ITU-T Recommendation X.500 2. ETSI ETSI TS 132 300 V13.1.0 (2016-04)73GPP TS 32.300 version 13.1.0 Release 131 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
34、 identical interpretation of names assigned to network resources under management. Such names are required to be unambiguous as well. The present document recommends one name convention for network resources under management in the IRP context. To facilitate integration of network management informa
35、tion obtained via multiple IRPs based on different IRP Solution Set technologies, identical network resource name semantics 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 orde
36、r to avoid potential problems with valid characters in some programming languages. In this document, the name convention 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
37、Support IOC (SupportIOC). 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 spec
38、ific 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
39、document. 1 Void. 2 ITU-T Recommendation X.500 (1993): “Information technology - Open Systems Interconnection - 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 Requir
40、ements for Uniform Resource Names“. 5 IETF RFC 2247 (1998): “Using Domains in LDAP/X.500 Distinguished Names“. 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
41、Names“. 8 3GPP TS 32.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)“. 9 3GPP TS 32.622: “ Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Netwo
42、rk Resource Model (NRM)“. 10 Void. 11 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 12 3GPP TS 32.102: “Telecommunication management; Architecture“. ETSI ETSI TS 132 300 V13.1.0 (2016-04)83GPP TS 32.300 version 13.1.0 Release 1313 ISO/IEC 14977: “Information
43、 technology Syntactic metalanguage Extended BNF“. 14 ISO/IEC 646: “Information technology ISO 7-bit coded character 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) C
44、oncept and definitions“. 17 3GPP2 S.S0028-E “OAM, U+003B), - reverse solidus character (, U+005C), - quotation 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“
45、. This full stop character shall not be used in AttributeType. 3. The asterisk character (*, U+002A) is reserved 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
46、.3), the client can use wildcard to represent one or more characters which are legal in that field. The asterisk 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 na
47、me, DN prefix, local DN, domain component type, class names starting with upper case characters, attribute names 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 EBN
48、F 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 (*
49、 DN prefix and local DN *) , LocalDN ; (* are defined in annex C *) ETSI ETSI TS 132 300 V13.1.0 (2016-04)153GPP TS 32.300 version 13.1.0 Release 13DNPrefixPlusRDNSeparator = ( NullDNPrefix , NullRDNSeparator ) | ( DNPrefixWithDomainComponent , RDNSeparator ) | ( DNPrefixWithoutDomainComponent , RDNSeparator ) ; NullDNPrefix = ; (* empty string *) NullRDNSeparator = ; (* empty string *) DNPrefixWithDomainComponent = DomainComponentRDN , RDNSepar
