1、 ETSI TS 1Universal Mobile TelTelecommGeneric NetwIntegratioInfor(3GPP TS 28.6TECHNICAL SPECIFICATION128 622 V12.1.0 (2016elecommunications System (LTE; munication management; ork Resource Model (NRM)tion Reference Point (IRP); ormation Service (IS) .622 version 12.1.0 Release 1216-01) (UMTS); M) 12
2、) ETSI ETSI TS 128 622 V12.1.0 (2016-01)13GPP TS 28.622 version 12.1.0 Release 12Reference RTS/TSGS-0528622vc10 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 n
3、on 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/or print versions o
4、f 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 kept on a specific
5、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/status/status.asp If you find errors in t
6、he 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 a
7、uthorized 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 Institute 2016. All rights reserved. DECTTM,
8、 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 Marks registered and owned by the GSM Asso
9、ciation. ETSI ETSI TS 128 622 V12.1.0 (2016-01)23GPP TS 28.622 version 12.1.0 Release 12Intellectual 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 E
10、TSI 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:/
11、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, essentia
12、l 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 identities. These should be interpreted
13、 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“, “should not“, “may“, “need not“, “w
14、ill“, “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 ETSI TS 128 622 V12.1.0 (2016-01)33GP
15、P TS 28.622 version 12.1.0 Release 12Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Model . 9g34.1 Imported information entitie
16、s and local labels . 9g34.2 Class diagrams 9g34.2.1 Relationships. 9g34.2.2 Inheritance 11g34.3 Class definitions . 11g34.3.1 Any . 11g34.3.1.1 Definition 11g34.3.1.2 Attributes . 11g34.3.1.3 Attribute constraints 11g34.3.1.4 Notifications 11g34.3.2 IRPAgent 11g34.3.2.1 Definition 11g34.3.2.2 Attrib
17、utes . 12g34.3.2.3 Attribute constraints 12g34.3.2.4 Notifications 12g34.3.3 ManagedElement 12g34.3.3.1 Definition 12g34.3.3.2 Attributes . 12g34.3.3.3 Attribute constraints 12g34.3.3.4 Notifications 12g34.3.4 ManagedFunction . 13g34.3.4.1 Definition 13g34.3.4.2 Attributes . 13g34.3.4.3 Attribute co
18、nstraints 13g34.3.4.4 Notifications 13g34.3.5 ManagementNode . 13g34.3.5.1 Definition 13g34.3.5.2 Attributes . 13g34.3.5.3 Attribute constraints 13g34.3.5.4 Notifications 13g34.3.6 MeContext 14g34.3.6.1 Definition 14g34.3.6.2 Attributes . 14g34.3.6.3 Attribute constraints 14g34.3.6.4 Notifications 1
19、4g34.3.7 SubNetwork 14g34.3.7.1 Definition 14g34.3.7.2 Attributes . 15g34.3.7.3 Attribute constraints 15g34.3.7.4 Notifications 15g34.3.8 Top 15g3ETSI ETSI TS 128 622 V12.1.0 (2016-01)43GPP TS 28.622 version 12.1.0 Release 124.3.8.1 Definition 15g34.3.8.2 Attributes . 15g34.3.8.3 Attribute constrain
20、ts 15g34.3.8.4 Notifications 15g34.3.9 VsDataContainer . 15g34.3.9.1 Definition 15g34.3.9.2 Attributes . 16g34.3.9.3 Attribute constraints 16g34.3.9.4 Notifications 16g34.3.10 Link . 16g34.3.10.1 Definition 16g34.3.10.2 Attributes . 16g34.3.10.3 Attribute constraints 16g34.3.10.4 Notifications 16g34
21、.3.11 EP_RP 16g34.3.11.1 Definition 16g34.3.11.2 Attributes . 17g34.3.11.3 Attribute constraints 17g34.3.11.4 Notifications 17g34.4 Attribute definitions . 18g34.4.1 Attribute properties . 18g34.4.2 Constraints 20g34.5 Common notifications 20g34.5.1 Alarm notifications . 20g34.5.2 Configuration noti
22、fications . 20g3Annex A (informative): Alternate class diagram . 21g3Annex B (informative): Change history . 22g3History 23g3ETSI ETSI TS 128 622 V12.1.0 (2016-01)53GPP TS 28.622 version 12.1.0 Release 12Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project
23、 (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 versio
24、n 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, correction
25、s, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part of a TS-family covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication
26、management; as identified below: 28.621 Generic Network Resource Model (NRM) Integration Reference Point (IRP); Requirements; 28.622 Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) ; 28.623 Generic Network Resource Model (NRM) Integration Reference Po
27、int (IRP); Solution Set (SS) definitions. The interface Itf-N, defined in 3GPP TS 32.102 2, is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP
28、TS 32.150 4. This specification is part of a set that has been developed for converged management solutions. ETSI ETSI TS 128 622 V12.1.0 (2016-01)63GPP TS 28.622 version 12.1.0 Release 121 Scope The present document specifies the Generic network resource information that can be communicated between
29、 an IRPAgent and an IRPManager for telecommunication network management purposes, including management of converged networks. This document specifies the semantics of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It doe
30、s not define their syntax and encoding. This document supports the Federated Network Information Model (FNIM) concept described in 8 in that the relevant Information Object Class (IOC)s defined in this specification are directly or indirectly inherited from those specified in the Umbrella Informatio
31、n Model (UIM) of 9. 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 r
32、eference, 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 docume
33、nt. 1 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Se
34、rvice (IS)“. 4 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Concept and Definitions“. 5 3GPP TS 23.003: “Technical Specification Group Core Network and Terminals; Numbering, addressing and identification“ 6 3GPP TS 32.532: “ Telecommunication management; Software
35、Management Integration Reference Point (IRP); Information Service (IS) “ 7 ITU-T Recommendation X.710 (1991): “Common Management Information Service Definition for CCITT Applications“. 8 TS 32.107: “Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNI
36、M)“ 9 TS 28.620: “Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model (UIM)“ 10 TS 32.156: “Telecommunication management; Fixed Mobile Convergence (FMC) Model Repertoire“ 11 3GPP TS 32.111-2: “Telecommunication management
37、; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)“. 12 3GPP TS 32.662: “Telecommunication management; Configuration Management (CM); Kernel CM Information Service (IS)“. ETSI ETSI TS 128 622 V12.1.0 (2016-01)73GPP TS 28.622 version 12.1.0 Release 1213 3GPP
38、 TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 14 3GPP TS 32.600: “Telecommunication management; Configuration Management (CM); Concept and high-level requirements“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of t
39、he present document, the following terms and definitions apply. For terms and definitions not found here, please refer to 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.150 4 and 3GPP TS 32.600 14. Association: In general it is used to model relationships between Managed Objects. Associations can be
40、 implemented in several ways, such as: 1) name bindings, 2) reference attributes, and 3) association objects. This IRP stipulates that name containment associations shall be expressed through name bindings, but it does not stipulate the implementation for other types of associations as a general rul
41、e. These are specified as separate entities in the object models (UML diagrams). Currently however, all (non-containment) associations are modelled by means of reference attributes of the participating MOs. Information Object Class (IOC): An IOC represents the management aspect of a Network Resource
42、. It describes the information that can be passed/used in management interfaces. Their representations are technology agnostic software objects. IOC has attributes that represents the various properties of the class of objects. See the term “attribute“ defined in 10. Furthermore, IOC can support ope
43、rations providing network management services invocable on demand for that class of objects. An IOC may support notifications that report event occurrences relevant for that class of objects. It is modelled using the stereotype “Class“ in the UML meta-model. See TS 32.156 10 for additional informati
44、on on IOC. Managed Element (ME): An instance of the IOC ManagedElement. Managed Object (MO): A MO is an instance of a Managed Object Class (MOC) representing the management aspects of a Network Resource. Its representation is a technology specific software object. It is sometimes called MO instance
45、(MOI). The MOC is a class of such technology specific software objects. An MOC is the same as an IOC except that the former is defined in technology specific terms and the latter is defined in technology agnostic terms. MOCs are used/defined in SS level specifications. IOCs are used/defined in IS le
46、vel specifications. Management Information Base (MIB): A MIB is an instance of an NRM and has some values on the defined attributes and associations specific for that instance. In the context of the present document, an MIB consists of: 1) a Name space (describing the MO containment hierarchy in the
47、 MIB through Distinguished Names), 2) a number of Managed Objects with their attributes and 3) a number of Associations between these MOs. Also note that TMN (ITU-T Recommendation X.710 7) defines a concept of a Management Information Tree (also known as a Naming Tree) that corresponds to the name s
48、pace (containment hierarchy) portion of this MIB definition. Figure 3.1 depicts the relationships between a Name space and a number of participating MOs (the shown association is of a non-containment type) ETSI ETSI TS 128 622 V12.1.0 (2016-01)83GPP TS 28.622 version 12.1.0 Release 12MO Name contain
49、ment Associ at ion MIB Figure 3.1: Relationships between a Name space and a number of participating MOs Name space: A name space is a collection of names. The IRP name convention (see 3GPP TS 32.300 13) restricts the name space to a hierarchical containment structure, including its simplest form - the one-level, flat name space. All Managed Objects in a MIB shall be included in the corresponding name space and the MIB/name space shall only support a strict hierarchical containment structure (with one root object). A M
