ETSI TS 128 622 V15.4.0 (2020-01)

TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
Telecommunication management;
Generic Network Resource Model (NRM)
Integration Reference Point (IRP);
Information Service (IS)
(3GPP TS 28.622 version 15.4.0 Release 15)

3GPP TS 28.622 version 15.4.0 Release 15 1 ETSI TS 128 622 V15.4.0 (2020-01)

Reference
RTS/TSGS-0528622vf40
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 2020.
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
3GPP TS 28.622 version 15.4.0 Release 15 2 ETSI TS 128 622 V15.4.0 (2020-01)
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
3GPP TS 28.622 version 15.4.0 Release 15 3 ETSI TS 128 622 V15.4.0 (2020-01)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 8
4 Model . 9
4.1 Imported information entities and local labels . 9
4.2 Class diagrams . 9
4.2.1 Relationships. 9
4.2.2 Inheritance . 11
4.3 Class definitions . 12
4.3.1 Any . 12
4.3.1.1 Definition . 12
4.3.1.2 Attributes . 12
4.3.1.3 Attribute constraints . 12
4.3.1.4 Notifications . 12
4.3.2 IRPAgent . 12
4.3.2.1 Definition . 12
4.3.2.2 Attributes . 12
4.3.2.3 Attribute constraints . 12
4.3.2.4 Notifications . 12
4.3.3 ManagedElement . 13
4.3.3.1 Definition . 13
4.3.3.2 Attributes . 13
4.3.3.3 Attribute constraints . 13
4.3.3.4 Notifications . 13
4.3.4 ManagedFunction . 14
4.3.4.1 Definition . 14
4.3.4.2 Attributes . 14
4.3.4.3 Attribute constraints . 14
4.3.4.4 Notifications . 14
4.3.5 ManagementNode . 14
4.3.5.1 Definition . 14
4.3.5.2 Attributes . 15
4.3.5.3 Attribute constraints . 15
4.3.5.4 Notifications . 15
4.3.6 MeContext . 15
4.3.6.1 Definition . 15
4.3.6.2 Attributes . 15
4.3.6.3 Attribute constraints . 15
4.3.6.4 Notifications . 16
4.3.7 SubNetwork . 16
4.3.7.1 Definition . 16
4.3.7.2 Attributes . 16
4.3.7.3 Attribute constraints . 16
4.3.7.4 Notifications . 16
4.3.8 Top . 16
ETSI
3GPP TS 28.622 version 15.4.0 Release 15 4 ETSI TS 128 622 V15.4.0 (2020-01)
4.3.8.1 Definition . 16
4.3.8.2 Attributes . 16
4.3.8.3 Attribute constraints . 17
4.3.8.4 Notifications . 17
4.3.9 VsDataContainer . 17
4.3.9.1 Definition . 17
4.3.9.2 Attributes . 17
4.3.9.3 Attribute constraints . 17
4.3.9.4 Notifications . 17
4.3.10 Link . 17
4.3.10.1 Definition . 17
4.3.10.2 Attributes . 17
4.3.10.3 Attribute constraints . 18
4.3.10.4 Notifications . 18
4.3.11 EP_RP . 18
4.3.11.1 Definition . 18
4.3.11.2 Attributes . 18
4.3.11.3 Attribute constraints . 18
4.3.11.4 Notifications . 18
4.3.12 MeasurementControl . 18
4.3.12.1 Definition . 18
4.3.12.2 Attributes . 19
4.3.12.3 Attribute constraints . 19
4.3.12.4 Notifications . 19
4.3.13 MeasurementReader . 19
4.3.13.1 Definition . 19
4.3.13.2 Attributes . 19
4.3.13.3 Attribute constraints . 20
4.3.13.4 Notifications . 20
4.3.14 Measurements <> . 20
4.3.14.1 Definition . 20
4.3.14.2 Attributes . 20
4.3.14.3 Attribute constraints . 20
4.3.14.4 Notifications . 20
4.3.15 ManagedEntity <> . 20
4.3.15.1 Definition . 20
4.3.15.2 Attributes . 20
4.3.15.3 Attribute constraints . 21
4.3.15.4 Notifications . 21
4.4 Attribute definitions . 22
4.4.1 Attribute properties . 22
4.4.2 Constraints . 31
4.5 Common notifications . 31
4.5.1 Alarm notifications . 31
4.5.2 Configuration notifications . 31
Annex A (informative): Alternate class diagram . 32
Annex B (informative): Change history . 33
History . 34

ETSI
3GPP TS 28.622 version 15.4.0 Release 15 5 ETSI TS 128 622 V15.4.0 (2020-01)
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.

Introduction
rd
The present document is part of a TS-family covering the 3 Generation Partnership Project; Technical Specification
Group Services and System Aspects; Telecommunication 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 Point (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 TS 32.150 [4].
The present document is part of a set that has been developed for converged management solutions.
The present document is part of a set that is used for management and orchestration of 5G networks and network
slicing.
ETSI
3GPP TS 28.622 version 15.4.0 Release 15 6 ETSI TS 128 622 V15.4.0 (2020-01)
1 Scope
The present document specifies the Generic network resource information that can be communicated between an
IRPAgent and an IRPManager for telecommunication network management purposes, including management of
converged networks and networks that include virtualized network functions.
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 does 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 Information 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 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 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 Service (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 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 (FNIM)"
[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; 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)".
[13] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name
convention for Managed Objects".
ETSI
3GPP TS 28.622 version 15.4.0 Release 15 7 ETSI TS 128 622 V15.4.0 (2020-01)
[14] 3GPP TS 32.600: "Telecommunication management; Configuration Management (CM); Concept
and high-level requirements".
[15] ETSI GS NFV 003 V1.1.1: "Network Functions Virtualisation (NFV); Terminology for Main
Concepts in NFV".
[16] ETSI GS NFV-IFA 008 v2.1.1: "Network Functions Virtualisation (NFV); Management and
Orchestration; Ve-Vnfm reference point - Interface and Information Model Specification".
[17] ETSI GS NFV-IFA 015 v2.1.2: "Network Functions Virtualisation (NFV); Management and
Orchestration; Report on NFV Information Model".
[18] ETSI ES 202 336-12 V1.1.1: "Environmental Engineering (EE); Monitoring and control interface
for infrastructure equipment (power, cooling and building environment systems used in
telecommunication networks); Part 12: ICT equipment power, energy and environmental
parameters monitoring information model".
[19] ITU-T Recommendation X.731: "Information technology - Open Systems Interconnection -
Systems Management: State management function".
[20] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements".
[21] 3GPP TS 28.625: "State Management Data Definition Integration Reference Point (IRP);
Information Service (IS) ".
[22] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [22], 3GPP TS 32.101 [1],
3GPP TS 32.102 [2], 3GPP TS 32.150 [4] and 3GPP TS 32.600 [14] 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 [22],
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 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 rule. 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. 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 operations 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 information on IOC.

ETSI
3GPP TS 28.622 version 15.4.0 Release 15 8 ETSI TS 128 622 V15.4.0 (2020-01)
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
(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 level 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 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 space
(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)

Name containment
MIB
MO
Associ at ion
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 are included in the corresponding name space and the MIB/name space shall only
support a strict hierarchical containment structure (with one root object). A Managed Object that contains another is
said to be the superior (parent); the contained Managed Object is referred to as the subordinate (child). The parent of all
MOs in a single name space is called a Local Root. The ultimate parent of all MOs of all managed systems is called the
Global Root.
Network resource: discrete entity represented by an Information Object Class (IOC) for the purpose of network and
service management.
NOTE: A network resource could represent intelligence, information, hardware and software of a
telecommunication network.
Network Resource Model (NRM): A collection of IOCs, inclusive of their associations, attributes and
operations, representing a set of network resources under management.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [22] 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 [22].
DN Distinguished Name (see 3GPP TS 32.300 [13])

IOC Information Object Class
MO Managed Object
MOC Managed Object Class
MOI Managed Object Instance
NFVI Network Functions Virtualisation Infrastructure (NFVI): Defined in ETSI GS NFV 003 [15].
RDN Relative Distinguished Name (see 3GPP TS 32.300 [13])

ETSI
3GPP TS 28.622 version 15.4.0 Release 15 9 ETSI TS 128 622 V15.4.0 (2020-01)
SS Solution Set
VNF Virtualised Network Function
4 Model
4.1 Imported information entities and local labels
Label reference Local label
notifyAckStateChanged
3GPP TS 32.111-2 [11], notification, notifyAckStateChanged
notifyAttributeValueChanged
3GPP TS 32.662 [12], notification, notifyAttributeValueChanged
notifyChangedAlarm
3GPP TS 32.111-2 [11], notification, notifyChangedAlarm
notifyClearedAlarm
3GPP TS 32.111-2 [11], notification, notifyClearedAlarm
notifyComments
3GPP TS 32.111-2 [11], notification, notifyComments
notifyNewAlarm
3GPP TS 32.111-2 [11], notification, notifyNewAlarm
notifyObjectCreation
3GPP TS 32.662 [12], notification, notifyObjectCreation
notifyObjectDeletion
3GPP TS 32.662 [12], notification, notifyObjectDeletion
notifyAlarmListRebuilt
3GPP TS 32.111-2 [11], notification, notifyAlarmListRebuilt
3GPP TS 32.111-2 [11], notification, notifyPotentialFaultyAlarmList
notifyPotentialFaultyAlarmList
notifyDownloadNESwStatusChanged
3GPP TS 32.532 [6], notification, notifyDownloadNESwStatusChanged
3GPP TS 32.532 [6], notification, notifyInstallNESwStatusChanged notifyInstallNESwStatusChanged
notifyActivateNESwStatusChanged
3GPP TS 32.532 [6], notification, notifyActivateNESwStatusChanged
3GPP TS 28.620 [9], IOC, Domain_ Domain_
3GPP TS 28.620 [9], IOC, ManagedElement_ ManagedElement_
3GPP TS 28.620 [9], IOC, Function_ Function_
3GPP TS 28.620 [9], IOC, ManagementSystem_ ManagementSystem_
3GPP TS 28.620 [9], IOC, TopologicalLink_ TopologicalLink_
Top_
3GPP TS 28.620 [9], IOC, Top_
4.2 Class diagrams
4.2.1 Relationships
This clause depicts the set of classes (e.g. IOCs) that encapsulates the information relevant for this IRP. This clause
provides the overview of the relationships of relevant classes in UML. Subsequent clauses provide more detailed
specification of various aspects of these classes.
The following figure shows the containment/naming hierarchy and the associations of the classes defined in the present
document. See Annex A of a class diagram that combines this figure with Figure 1 of [2], the class diagram of UIM.
ETSI
3GPP TS 28.622 version 15.4.0 Release 15 10 ETSI TS 128 622 V15.4.0 (2020-01)

NOTE 1: ManagedElement may be contained either
- in a SubNetwork (since SubNetwork inherits from Domain_ and ManagedElement inherits from ManagedElement_
and Domain_ name-contained ManagedElement_ as observed in the figure of Annex A) or
- in a MeContext instance as observed by the above figure or in the figure of Annex A.
This either-or relation cannot be shown by using an {xor} constraint in the above figure.
ManagedElement may also have no parent instance at all.
NOTE 2: Each instance of the VsDataContainer shall only be contained under one IOC. The VsDataContainer can be
contained under IOCs defined in other NRMs.
NOTE 3: If the configuration contains several instances of SubNetwork, exactly one SubNetwork instance shall directly or
indirectly contain all the other SubNetwork instances.
NOTE 4: The SubNetwork instance not contained in any other instance of SubNetwork is referred to as "the root
SubNetwork instance".
NOTE 5: ManagementNode shall be contained in the root SubNetwork instance.
NOTE 6: If contained in a SubNetwork instance, IRPAgent shall be contained in the root SubNetwork instance.
NOTE 7: For a clarification on the choice of containment of the IRPAgent (since it has three possible parents), see the def. of
IRPAgent.
Figure 4.2.1-1: Containment/Naming and Association NRM fragment
Each Managed Object is identified with a Distinguished Name (DN) according to 3GPP TS 32.300 [13] that expresses
its containment hierarchy. As an example, the DN of a ManagedElement instance could have a format like:
SubNetwork=Sweden,MeContext =MEC-Gbg-1, ManagedElement=RNC-Gbg-1.

ETSI
3GPP TS 28.622 version 15.4.0 Release 15 11 ETSI TS 128 622 V15.4.0 (2020-01)
NOTE 8: Each instance of the VsDataContainer shall only be contained under one IOC. The VsDataContainer can be
contained under IOCs defined in other NRMs by virtue of inheritance from the GENERIC NRM.
NOTE 9: The VsDataContainer is only used for the Bulk CM IRP.

Figure 4.2.1-2: VsDataContainer Containment/Naming and Association in GENERIC NRM diagram

Figure 4.2.1-3: PM NRM fragment

4.2.2 Inheritance
This clause depicts the inheritance relationships.

Figure 4.2.2-1: Inheritance Hierarchy NRM fragment

Figure 4.2.2-2: Inheritance PM NRM fragment

ETSI
3GPP TS 28.622 version 15.4.0 Release 15 12 ETSI TS 128 622 V15.4.0 (2020-01)
4.3 Class definitions
4.3.1 Any
4.3.1.1 Definition
This class represents the classes (e.g. IOC) that are not defined in this specification but are or will be defined in other
IRP specification(s).
4.3.1.2 Attributes
None
4.3.1.3 Attribute constraints
None
4.3.1.4 Notifications
This class does not support any notification.
4.3.2 IRPAgent
4.3.2.1 Definition
This IOC represents the functionality of an IRPAgent. It shall be present. For a definition of IRPAgent, see 3GPP
TS 32.102 [2].
The IRPAgent will be contained under an IOC as follows (only one of the options shall be used):
1) ManagementNode, if the configuration contains a ManagementNode;
2) SubNetwork, if the configuration contains a SubNetwork and no ManagementNode;
3) ManagedElement, if the configuration contains no ManagementNode or SubNetwork.
4.3.2.2 Attributes
The IRPAgent IOC includes the attributes inherited from Top_ IOC (defined in TS 28.620 [9]), attributes inherited from
Top IOC (defined in clause 4.3.8) and the following attributes:
Attribute Name Support Qualifier isReadable isWritable isInvariant isNotifyable
systemDN
M MT -F -F MT
4.3.2.3 Attribute constraints
None
4.3.2.4 Notifications
The common notifications defined in clause 4.5 are valid for this IOC, without exceptions or additions
ETSI
3GPP TS 28.622 version 15.4.0 Release 15 13 ETSI TS 128 622 V15.4.0 (2020-01)
4.3.3 ManagedElement
4.3.3.1 Definition
This IOC represents telecommunications equipment or TMN entities within the telecommunications network providing
support and/or service to the subscriber.
An ME communicates with a manager (directly or indirectly) over one or more management interfaces for the purpose
of being monitored and/or controlled. MEs may or may not additionally perform element management functionality.
An ME contains equipment that may or may not be geographically distributed. An ME is often referred to as a
"Network Element".
A telecommunication equipment has software and hardware components. The IOC described above represents the case
when the software component is designed to run on dedicated hardware component. In the case when the software is
designed to run on ETSI NFV defined NFVI [15], the IOC description would exclude the NFVI component supporting
the above mentioned subject software. A ManagedElement may be contained in either a SubNetwork or in a
MeContext instance. A single ManagedElement may also exist stand-alone with no parent at all.
The ManagedElement IOC may be used to represent combined ME functionality (as indicated by the
managedElementType attribute and the contained instances of different functional IOCs).
Single function ManagedElement IOC instances will have a 1.1 containment relationship to a function IOC instance
(in this context a function IOC instance is an instance of an IOC derived from the ManagedFunction IOC). Multiple
function ManagedElement instances will have a 1.N containment relationship to function IOC instances.
NOTE: For some specific functional IOCs a 1.N containment relationship is permitted. The specific functional
entities are identified in the NRMs that define subclasses of ManagedFunction.
4.3.3.2 Attributes
The ManagedElement IOC includes the attributes inherited from ManagedElement_IOC (defined in TS 28.620 [9]),
attributes inherited from Top IOC (defined in clause 4.3.8) and the following attributes:
Attribute Name Support Qualifier isReadable isWritable isInvariant isNotifyable
vendorName M T F F T
userDefinedState M T T F T
swVersion
M T F F T
priorityLabel
O T F T F
measurementsList
M T F F T
4.3.3.3 Attribute constraints
Name Definition
dnPrefix (inherited) Support Condition: The ManagedElement instance is the local root instance of
Qualifier the MIB; otherwise, the attribute shall be absent or carry no
information.
4.3.3.4 Notifications
The common notifications defined in clause 4.5 are valid for this IOC. In addition, the following set of notifications is
also valid.
ETSI
3GPP TS 28.622 version 15.4.0 Release 15 14 ETSI TS 128 622 V15.4.0 (2020-01)
Name Qualifier Notes
notifyDownloadNESwStatusChanged
See Software Management IRP (3GPP TS 32.532 [6])
notifyInstallNESwStatusChanged
See Software Management IRP (3GPP TS 32.532 [6])
notifyActivateNESwStatusChanged
See Software Management IRP (3GPP TS 32.532 [6])
4.3.4 ManagedFunction
4.3.4.1 Definition
This IOC is provided for sub-classing only. It provides attribute(s) that are common to functional IOCs. Note that a
ManagedElement may contain several managed functions. The ManagedFunction may be extended in the future
if more common characteristics to functional objects are identified.
This IOC can represent a telecommunication function either realized by software running on dedicated hardware or
realized by software running on NFVI. Each ManagedFunction instance communicates with a manager (directly or
indirectly) over one or more management interfaces exposed via its containing ME instance.
4.3.4.2 Attributes
The ManagedFunction IOC includes the attributes inherited from Function_IOC (defined in TS 28.620 [9]), attributes
inherited from Top IOC (defined in clause 4.3.8) and the following attributes:
Attribute Name Support Qualifier isReadable isWritable isInvariant isNotifyable
vnfParametersList
CM T T F T
peeParametersList
CM T T F T
priorityLabel T F T F
O
measurementsList M T F F T
4.3.4.3 Attribute constraints
Name Definition
vnfParametersList
Condition: The ManagedFunction instance is realized by one or more VNF
Support Qualifier
instance(s). Otherwise this attribute shall be absent.
peeParametersList
Condition:The control and monitoring of PEE parameters is supported by the
ManagedFunction or sub-class instance.
Support Qualifier
4.3.4.4 Notifications
There is no notification defined.
4.3.5 ManagementNode
4.3.5.1 Definition
This IOC represents a telecommunications management system (EM) within the TMN that contains functionality for
managing a number of ManagedElements (MEs). The management system communicates with the MEs directly or
indirectly over one or more interfaces for the purpose of monitoring and/or controlling these MEs.
This class has similar characteristics as the ManagedElement. The main difference between these two classes is that
the ManagementNode has a special association to the managed elements that it is responsible for managing.
ETSI
3GPP TS 28.622 version 15.4.0 Release 15 15 ETSI TS 128 622 V15.4.0 (2020-01)
4.3.5.2 Attributes
The ManagementNode IOC includes the attributes inherited from ManagementSystem_ IOC (defined in TS 28.620 [9])
...