ETSI TS 128 622 V11.5.0 (2023-04)

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 11.5.0 Release 11)

RTS/TSGS-0528622vb50

General Information

• Status: Not Published
• Technical Committee: 3GPP SA 5 - Telecom Management
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Completion Date: 21-Apr-2023

Standards Content (Sample)

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 11.5.0 Release 11)

3GPP TS 28.622 version 11.5.0 Release 11 1 ETSI TS 128 622 V11.5.0 (2023-04)

Reference
RTS/TSGS-0528622vb50
Keywords
5G,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from:
https://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
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
and/or governmental
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
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 2023.
All rights reserved.
ETSI
3GPP TS 28.622 version 11.5.0 Release 11 2 ETSI TS 128 622 V11.5.0 (2023-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
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.
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.
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 https://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 11.5.0 Release 11 3 ETSI TS 128 622 V11.5.0 (2023-04)
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 . 11
4.3.1 Any . 11
4.3.1.1 Definition . 11
4.3.1.2 Attributes . 11
4.3.1.3 Attribute constraints . 11
4.3.1.4 Notifications . 11
4.3.2 IRPAgent . 11
4.3.2.1 Definition . 11
4.3.2.2 Attributes . 12
4.3.2.3 Attribute constraints . 12
4.3.2.4 Notifications . 12
4.3.3 ManagedElement . 12
4.3.3.1 Definition . 12
4.3.3.2 Attributes . 12
4.3.3.3 Attribute constraints . 12
4.3.3.4 Notifications . 13
4.3.4 ManagedFunction . 13
4.3.4.1 Definition . 13
4.3.4.2 Attributes . 13
4.3.4.3 Attribute constraints . 13
4.3.4.4 Notifications . 13
4.3.5 ManagementNode . 13
4.3.5.1 Definition . 13
4.3.5.2 Attributes . 13
4.3.5.3 Attribute constraints . 13
4.3.5.4 Notifications . 13
4.3.6 MeContext . 14
4.3.6.1 Definition . 14
4.3.6.2 Attributes . 14
4.3.6.3 Attribute constraints . 14
4.3.6.4 Notifications . 14
4.3.7 SubNetwork . 14
4.3.7.1 Definition . 14
4.3.7.2 Attributes . 15
4.3.7.3 Attribute constraints . 15
4.3.7.4 Notifications . 15
4.3.8 Top . 15
ETSI
3GPP TS 28.622 version 11.5.0 Release 11 4 ETSI TS 128 622 V11.5.0 (2023-04)
4.3.8.1 Definition . 15
4.3.8.2 Attributes . 15
4.3.8.3 Attribute constraints . 15
4.3.8.4 Notifications . 15
4.3.9 VsDataContainer . 15
4.3.9.1 Definition . 15
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 . 16
4.3.10.3 Attribute constraints . 16
4.3.10.4 Notifications . 16
4.3.11 EP_RP . 16
4.3.11.1 Definition . 16
4.3.11.2 Attributes . 17
4.3.11.3 Attribute constraints . 17
4.3.11.4 Notifications . 17
4.4 Attribute definitions . 18
4.4.1 Attribute properties . 18
4.4.2 Constraints . 21
4.5 Common notifications . 21
4.5.1 Alarm notifications . 21
4.5.2 Configuration notifications . 21
Annex A (informative): Alternate class diagram . 22
Annex B (informative): Change history . 23
History . 24

ETSI
3GPP TS 28.622 version 11.5.0 Release 11 5 ETSI TS 128 622 V11.5.0 (2023-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].
This specification is part of a set that has been developed for converged management solutions.
ETSI
3GPP TS 28.622 version 11.5.0 Release 11 6 ETSI TS 128 622 V11.5.0 (2023-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.
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 11.5.0 Release 11 7 ETSI TS 128 622 V11.5.0 (2023-04)
[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 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.
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 betw
...