|
TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
Telecommunication management;
Generic Network Resource Model (NRM)
Integration Reference Point (IRP);
Solution Set (SS) definitions
(3GPP TS 28.623 version 15.1.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 28.623 version 15.1.0 Release 15 1 ETSI TS 128 623 V15.1.0 (2019-04)
Reference
RTS/TSGS-0528623vf10
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.623 version 15.1.0 Release 15 2 ETSI TS 128 623 V15.1.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.623 version 15.1.0 Release 15 3 ETSI TS 128 623 V15.1.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 Solution Set definitions . 8
Annex A (normative): CORBA Solution Set . 9
A.0 General . 9
A.1 Architectural features . 9
A.1.1 Syntax for Distinguished Names . 9
A.1.2 Rules for NRM extensions . 9
A.1.2.0 Introduction. 9
A.1.2.1 Allowed extensions . 9
A.1.2.2 Extensions not allowed . 9
A.2 Mapping . 10
A.2.1 General mapping . 10
A.2.2 Information Object Class (IOC) mapping . 10
A.2.2.1 IOC SubNetwork . 10
A.2.2.2 IOC ManagedElement . 10
A.2.2.3 IOC MeContext . 10
A.2.2.4 IOC ManagementNode . 11
A.2.2.5 IOC VsDataContainer . 11
A.2.2.6 IOC ManagedFunction . 11
A.2.2.7 IOC IRPAgent . 11
A.2.2.8 IOC Top . 11
A.2.2.9 IOC Link . 12
A.2.2.10 IOC EP_RP . 12
A.3 Solution Set definitions . 13
A.3.1 IDL definition structure . 13
A.3.2 IDL specification "GenericNetworkResourcesIRPSystem.idl" . 13
A.3.3 IDL specification "GenericNetworkResourcesNRMDefs.idl" . 15
Annex B (normative): XML Definitions . 18
B.0 General . 18
B.1 Architectural features . 18
B.1.0 Introduction . 18
B.1.1 Syntax for Distinguished Names . 18
B.2 Mapping . 18
B.2.1 General mapping . 18
B.2.2 Information Object Class (IOC) mapping . 18
B.3 Solution Set definitions . 19
B.3.1 XML definition structure . 19
B.3.2 Graphical Representation . 19
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 28.623 version 15.1.0 Release 15 4 ETSI TS 128 623 V15.1.0 (2019-04)
B.3.3 XML schema "genericNrm.xsd" . 20
Annex C (informative): Change history . 25
History . 26
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 28.623 version 15.1.0 Release 15 5 ETSI TS 128 623 V15.1.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.
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 28.623 version 15.1.0 Release 15 6 ETSI TS 128 623 V15.1.0 (2019-04)
1 Scope
The TS 28.62x-series (Generic Network Resources IRP) define an Integration Reference Point (IRP) through which an
"IRPAgent" (typically an Element Manager or Network Element) can communicate Network Management related
information to one or several "IRPManagers" (typically Network Managers).
This TS-family specifies a generic Network Resource Model, NRM (also referred to as a Management Information
Model - MIM) with definitions of Information Object Classes (IOCs) and Managed Object Classes (MOCs).
The present document specifies the Solution Set definition for the Generic NRM IRP.
The Solution Set definition is related to 3GPP TS 28.622 V14.1.X [4].
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.600: "Telecommunication management; Configuration Management (CM); Concept
and high-level requirements".
[4] 3GPP TS 28.622: “Generic Network Resource Model (NRM) Integration Reference Point (IRP);
Information Service (IS)”.
[5] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name
convention for Managed Objects".
[6] 3GPP TS 32.306: "Telecommunication management; Configuration Management (CM);
Notification Integration Reference Point (IRP); Solution Set (SS) definitions".
[7] 3GPP TS 32.616: "Telecommunication management; Configuration Management (CM); Bulk CM
Integration Reference Point (IRP); Solution Set (SS) definitions".
[8] W3C REC-xml11-20060816: "Extensible Markup Language (XML) 1.1 (Second Edition)".
[9] Void.
[10] W3C XML Schema Definition Language (XSD) 1.1 Part 1: Structures.
[11] W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes.
[12] W3C REC-xml-names-20060816: "Namespaces in XML 1.1 (Second Edition)".
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 28.623 version 15.1.0 Release 15 7 ETSI TS 128 623 V15.1.0 (2019-04)
3 Definitions and abbreviations
3.1 Definitions
For terms and definitions please refer to 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], 3GPP TS 32.600 [3] and
3GPP TS 28.622 [4].
XML file: file containing an XML document
XML document: composed of the succession of an optional XML declaration followed by a root XML element
NOTE: See [8]; in the scope of the present document.
XML declaration: it specifies the version of XML being used
NOTE: See [8].
XML element: has a type, is identified by a name, may have a set of XML attribute specifications and is either
composed of the succession of an XML start-tag followed by the XML content of the XML element followed by an
XML end-tag, or composed simply of an XML empty-element tag; each XML element may contain other XML
elements
NOTE: See [8].
empty XML element: having an empty XML content; an empty XML element still possibly has a set of XML attribute
specifications; an empty XML element is either composed of the succession of an XML start-tag directly followed by
an XML end-tag, or composed simply of an XML empty-element tag
NOTE: See [8].
XML content (of an XML element): empty if the XML element is simply composed of an XML empty-element tag;
otherwise the part, possibly empty, of the XML element between its XML start-tag and its XML end-tag
XML start-tag: the beginning of a non-empty XML element is marked by an XML start-tag containing the name and
the set of XML attribute specifications of the XML element
NOTE: See [8].
XML end-tag: the end of a non-empty XML element is marked by an XML end-tag containing the name of the XML
element
NOTE: See [8].
XML empty-element tag: composed simply of an empty-element tag containing the name and the set of XML attribute
specifications of the XML element.
NOTE: See [8].
XML attribute specification: has a name and a value
NOTE: See [8].
DTD: defines structure and content constraints to be respected by an XML document to be valid with regard to this
DTD
NOTE: See [8].
XML schema: more powerful than a DTD, an XML schema defines structure and content constraints to be respected
by an XML document to conform with this XML schema; through the use of XML namespaces several XML schemas
can be used together by a single XML document; an XML schema is itself also an XML document that shall conform
with the XML schema for XML schemas
NOTE: See [9], [10] and [11].
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 28.623 version 15.1.0 Release 15 8 ETSI TS 128 623 V15.1.0 (2019-04)
XML namespace: enables qualifying element and attribute names used in XML documents by associating them with
namespaces identified by different XML schemas
NOTE: See [12], in the scope of the present document.
XML complex type: defined in an XML schema; cannot be directly used in an XML document; can be the concrete
type or the derivation base type for an XML element type or for another XML complex type; ultimately defines
constraints for an XML element on its XML attribute specifications and/or its XML content
NOTE: See [9], [10] and [11].
XML element type: declared by an XML schema; can be directly used in an XML document; as the concrete type of
an XML element, directly or indirectly defines constraints on its XML attribute specifications and/or its XML content;
can also be the concrete type or the derivation base type for another XML element type
NOTE: See [9], [10] and [11].
For additional terms and definitions please refer to 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], 3GPP TS 32.600 [3] and
3GPP TS 28.622 [4].
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
CM Configuration Management
CORBA Common Object Request Broker Architecture
DN Distinguished Name
DTD Document Type Definition
EDGE Enhanced Data for GSM Evolution
GERAN GSM/EDGE Radio Access Network
GSM Global System for Mobile communication
IS Information Service
IDL Interface Definition Language (OMG)
IRP Integration Reference Point
IS Information Service
MO Managed Object
MOC Managed Object Class
NRM Network Resource Model
OMG Object Management Group
SS Solution Set
UMTS Universal Mobile Telecommunications System
UTRAN Universal Terrestrial Radio Access Network
XML eXtensible Markup Language
4 Solution Set definitions
This specification defines the following 3GPP Generic NRM IRP Solution Set Definitions:
- 3GPP Generic NRM IRP CORBA SS (Annex A)
- 3GPP Generic NRM IRP XML Definitions (Annex B)
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 28.623 version 15.1.0 Release 15 9 ETSI TS 128 623 V15.1.0 (2019-04)
Annex A (normative):
CORBA Solution Set
A.0 General
This annex contains the CORBA Solution Set for the IRP whose semantics is specified in Generic NRM IRP:
Information Service (TS 28.622 [4]).
A.1 Architectural features
The overall architectural feature of Generic Network Resources IRP is specified in 3GPP TS 28.622 [4].
This clause specifies features that are specific to the CORBA SS.
A.1.1 Syntax for Distinguished Names
The syntax of a Distinguished Name is defined in 3GPP TS 32.300 [5].
A.1.2 Rules for NRM extensions
A.1.2.0 Introduction
This clause discusses how the models and IDL definitions provided in the present document can be extended for a
particular implementation and still remain compliant with 3GPP SA5's specifications.
A.1.2.1 Allowed extensions
Vendor-specific MOCs may be supported. The vendor-specific MOCs may support new types of attributes.
The 3GPP SA5-specified notifications may be issued referring to the vendor-specific MOCs and vendor-specific
attributes. New MOCs shall be distinguishable from 3GPP SA5 MOCs by name. 3GPP SA5-specified and vendor-
specific attributes may be used in vendor-specific MOCs. Vendor-specific attribute names shall be distinguishable from
existing attribute names.
NRM MOCs may be subclassed. Subclassed MOCs shall maintain the specified behaviour of the 3GPP SA5's superior
classes. They may add vendor-specific behaviour with vendor-specific attributes. When subclassing, naming attributes
cannot be changed. The subclassed MOC shall support all attributes of its superior class. Vendor-specific attributes
cannot be added to 3GPP SA5 NRM MOCs without subclassing.
When subclassing, the 3GPP SA5-specified containment rules and their specified cardinality shall still be followed.
As an example, ManagementNode (or its subclasses) shall be contained under SubNetwork (or its subclasses).
Managed Object Instances may be instantiated as CORBA objects. This requires that the MOCs be represented in IDL.
3GPP SA5's NRM MOCs are not currently specified in IDL, but may be specified in IDL for instantiation or
subclassing purposes. However, management information models should not require that IRPManagers access the
instantiated managed objects other than through supported methods in the present document.
Extension rules related to notifications (Notification categories, Event Types, Extended Event Types etc.) are for further
study.
A.1.2.2 Extensions not allowed
The IDL specifications in the present document cannot be edited or altered. Any additional IDL specifications shall be
specified in separate IDL files.
IDL interfaces (note: not MOCs) specified in the present document may not be subclassed or extended. New interfaces
may be defined with vendor-specific methods.
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 28.623 version 15.1.0 Release 15 10 ETSI TS 128 623 V15.1.0 (2019-04)
A.2 Mapping
A.2.1 General mapping
Attributes modelling associations as defined in the NRM (here also called "reference attributes") are in this SS mapped
to attributes. The names of the reference attributes in the NRM are mapped to the corresponding attribute names in the
MOC. When the cardinality for an association is 0.1 or 1.1 the datatype for the reference attribute is defined as an
MOReference. The value of an MO reference contains the distinguished name of the associated MO. When the
cardinality for an association allows more than one referred MO, the reference attribute will be of type
MOReferenceSet, which contains a sequence of MO references.
A.2.2 Information Object Class (IOC) mapping
This Solution Set supports reference attributes for relations other than containment relations between objects. Reference
attributes are therefore introduced in each MOC where needed.
A.2.2.1 IOC SubNetwork
Mapping from NRM IOC SubNetwork attributes to SS equivalent MOC SubNetwork attributes
IS Attributes SS Attributes SS Type
id id string
dnPrefix dnPrefix string
userLabel userLabel string
userDefinedNetworkType userDefinedNetworkType string
setOfMcc setOfMcc GenericNetworkResourcesIRPSystem::AttributeTyp
es::StringSet
A.2.2.2 IOC ManagedElement
Mapping from NRM IOC ManagedElement attributes and association roles to SS equivalent MOC
ManagedElement attributes
IS Attributes SS Attributes SS Type
id id string
dnPrefix dnPrefix string
userLabel userLabel string
locationName locationName string
vendorName vendorName string
userDefinedState userDefinedState string
managedElementType managedElementType GenericNetworkResourcesIRPSystem::AttributeTyp
es::StringSet
managedBy managedBy GenericNetworkResourcesIRPSystem::AttributeTyp
es::MOReferenceSet
swVersion swVersion string
A.2.2.3 IOC MeContext
Mapping from NRM IOC MeContext attributes to SS equivalent MOC MeContext attributes
IS Attributes SS Attributes SS Type
id id string
dnPrefix dnPrefix string
ETSI
---------------------- Page: 11 ----------------------
3GPP TS 28.623 version 15.1.0 Release 15 11 ETSI TS 128 623 V15.1.0 (2019-04)
A.2.2.4 IOC ManagementNode
Mapping from NRM IOC ManagementNode attributes and association roles to SS equivalent MOC
ManagementNode attributes
IS Attributes SS Attributes SS Type
id id string
userLabel userLabel string
locationName locationName string
vendorName vendorName string
userDefinedState userDefinedState string
managedElements managedElements GenericNetworkResourcesIRPSystem::Attr
ibuteTypes::MOReferenceSet
swVersion swVersion string
A.2.2.5 IOC VsDataContainer
Mapping from NRM IOC VsDataContainer attributes and association roles to SS equivalent MOC
VsDataContainer attributes
IS Attributes SS Attributes SS Type
id id string
vsDataType vsDataType string
vsData vsData any
vsDataFormatVersion vsDataFormatVersion string
A.2.2.6 IOC ManagedFunction
Mapping from NRM IOC ManagedFunction attributes and association roles to SS equivalent MOC
ManagedFunction attributes
IS Attributes SS Attributes SS Type
id id string
peeParametersList peeParametersList GenericNetworkResourcesIRPSystem::AttributeTypes::
PEEParametersListType
userLabel userLabel string
vnfParametersList vnfParametersList GenericNetworkResourcesIRPSystem::AttributeTypes::
VNFParametersListType
A.2.2.7 IOC IRPAgent
Mapping from NRM IOC IRPAgent attributes to SS equivalent MOC IRPAgent attributes
IS Attributes SS Attributes SS Type
id id string
systemDN systemDN string
A.2.2.8 IOC Top
Mapping from NRM IOC Top attributes to SS equivalent attributes in all MOCs
IS Attributes SS Attributes SS Type
objectClass CLASS string
objectInstance No direct mapping
ETSI
---------------------- Page: 12 ----------------------
3GPP TS 28.623 version 15.1.0 Release 15 12 ETSI TS 128 623 V15.1.0 (2019-04)
A.2.2.9 IOC Link
Mapping from NRM IOC Link attributes to SS equivalent MOC IRPAgent attributes
IS Attributes SS Attributes SS Type
id id string
userLabel (see note 2) userLabel string
aEnd aEnd GenericNetworkResourcesIRPSystem::Att
ributeTypes::MOReference
zEnd zEnd GenericNetworkResourcesIRPSystem::Att
ributeTypes::MOReference
linkType linkType LinkTypeType
protocolName protocolName string
protocolVersion protocolVersion string
NOTE 1: Void.
NOTE 2: Void.
A.2.2.10 IOC EP_RP
Mapping from NRM IOC EP_RP attributes to SS equivalent MOC EP_RP attributes
IS Attributes SS Attributes SS Type
id id string
userLabel userLabel string
farEndEntity farEndEntity GenericNetworkResourcesIRPSystem::Att
ributeTypes::MOReference
ETSI
---------------------- Page: 13 ----------------------
3GPP TS 28.623 version 15.1.0 Release 15 13 ETSI TS 128 623 V15.1.0 (2019-04)
A.3 Solution Set definitions
A.3.1 IDL definition structure
Clause A.3.2 defines the types which are used by the Generic NRM IRP.
Clause
...