|
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.2.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 28.622 version 15.2.0 Release 15 1 ETSI TS 128 622 V15.2.0 (2019-04)
Reference
RTS/TSGS-0528622vf20
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:
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
If you find errors in the present document, please send your comment to one of the following services:
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 2019.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
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
---------------------- Page: 2 ----------------------
3GPP TS 28.622 version 15.2.0 Release 15 2 ETSI TS 128 622 V15.2.0 (2019-04)
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.
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 as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
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
---------------------- Page: 3 ----------------------
3GPP TS 28.622 version 15.2.0 Release 15 3 ETSI TS 128 622 V15.2.0 (2019-04)
Contents
Intellectual Property Rights . 2
Foreword . 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 . 13
4.3.4.1 Definition . 13
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 . 14
4.3.5.3 Attribute constraints . 14
4.3.5.4 Notifications . 14
4.3.6 MeContext . 14
4.3.6.1 Definition . 14
4.3.6.2 Attributes . 15
4.3.6.3 Attribute constraints . 15
4.3.6.4 Notifications . 15
4.3.7 SubNetwork . 15
4.3.7.1 Definition . 15
4.3.7.2 Attributes . 15
4.3.7.3 Attribute constraints . 15
4.3.7.4 Notifications . 16
4.3.8 Top . 16
4.3.8.1 Definition . 16
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 28.622 version 15.2.0 Release 15 4 ETSI TS 128 622 V15.2.0 (2019-04)
4.3.8.2 Attributes . 16
4.3.8.3 Attribute constraints . 16
4.3.8.4 Notifications . 16
4.3.9 VsDataContainer . 16
4.3.9.1 Definition . 16
4.3.9.2 Attributes . 16
4.3.9.3 Attribute constraints . 16
4.3.9.4 Notifications . 16
4.3.10 Link . 16
4.3.10.1 Definition . 16
4.3.10.2 Attributes . 17
4.3.10.3 Attribute constraints . 17
4.3.10.4 Notifications . 17
4.3.11 EP_RP . 17
4.3.11.1 Definition . 17
4.3.11.2 Attributes . 17
4.3.11.3 Attribute constraints . 17
4.3.11.4 Notifications . 17
4.3.12 MeasurementControl . 17
4.3.12.1 Definition . 17
4.3.12.2 Attributes . 18
4.3.12.3 Attribute constraints . 18
4.3.12.4 Notifications . 18
4.3.13 MeasurementReader . 18
4.3.13.1 Definition . 18
4.3.13.2 Attributes . 18
4.3.13.3 Attribute constraints . 18
4.3.13.4 Notifications . 19
4.3.14 Measurements<> . 19
4.3.14.1 Definition . 19
4.3.14.2 Attributes . 19
4.3.14.3 Attribute constraints . 19
4.3.14.4 Notifications . 19
4.4 Attribute definitions . 20
4.4.1 Attribute properties . 20
4.4.2 Constraints . 26
4.5 Common notifications . 27
4.5.1 Alarm notifications . 27
4.5.2 Configuration notifications . 27
Annex A (informative): Alternate class diagram . 28
Annex B (informative): Change history . 29
History . 30
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 28.622 version 15.2.0 Release 15 5 ETSI TS 128 622 V15.2.0 (2019-04)
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
---------------------- Page: 6 ----------------------
3GPP TS 28.622 version 15.2.0 Release 15 6 ETSI TS 128 622 V15.2.0 (2019-04)
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
---------------------- Page: 7 ----------------------
3GPP TS 28.622 version 15.2.0 Release 15 7 ETSI TS 128 622 V15.2.0 (2019-04)
[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) ".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the 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 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.
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
(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.
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 28.622 version 15.2.0 Release 15 8 ETSI TS 128 622 V15.2.0 (2019-04)
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 thei
...