Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 28.622  Word version:  19.0.0

Top   Top   None   None   Next
0…   4… 
0 Introduction  1 Scope  2 References  3 Definitions and abbreviations  3.1 Definitions  3.2 Abbreviations 
...

 

0  Introduction  p. 9

The present document is part of a TS-family covering the 3rd 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 TS 32.102, 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 TS 32.150.
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.
Up

1  Scope  p. 10

The present document specifies the Generic network resource information that can be communicated between an MnS producer and MnS consumer 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 TS 28.620.
Note that the present document is applicable to deployment scenarios using the Service Based Management Architecture (SBMA) as defined in TS 28.533. For deployment scenarios using the IRP framework as defined in TS 32.102 the latest Rel-14 version of TS 28.622 is applicable.
Up

2  References  p. 10

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]
TS 32.101: "Telecommunication management; Principles and high level requirements".
[2]
TS 32.102: "Telecommunication management; Architecture".
[3]
TS 32.302: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)".
[4]
TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and Definitions".
[5]
TS 23.003: "Technical Specification Group Core Network and Terminals; Numbering, addressing and identification"
[6]  Void
[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]  Void
[12]  Void
[13]
TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects".
[14]
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]
TS 28.552: "Management and orchestration; 5G performance measurements".
[21]
TS 28.625: "State Management Data Definition Integration Reference Point (IRP); Information Service (IS) ".
[22]
TS 23.501: "System Architecture for the 5G System".
[23]
TS 23.502: "Procedures for the 5G System; Stage 2".
[24]
RFC 791:  "Internet Protocol".
[25]
RFC 2373:  "IP Version 6 Addressing Architecture".
[26]
TR 21.905: "Vocabulary for 3GPP Specifications".
[27]
TS 28.532: "Management and orchestration; Generic management services".
[28]
TS 28.554: "Management and orchestration; 5G end to end Key Performance Indicators (KPI)".
[29]
TS 32.421: "Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements".
[30]  Void.
[31]
ITU-T Recommendation X.733 (02/92): "Information technology - Open Systems Interconnection - Systems Management: Alarm reporting function".
[32]
TS 28.533: "Management and orchestration; Architecture framework".
[33]
TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2".
[34]
TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[35]
TS 38.104: "NR; Base Station (BS) radio transmission and reception".
[36]
TS 38.321: "NR; Medium Access Control (MAC) protocol specification".
[37]
TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification".
[38]
TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification".
[39]
TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[40]
TS 25.321: "Medium Access Control (MAC) protocol specification".
[41]
TS 25.331: "Radio Resource Control (RRC); Protocol specification".
[42]
TS 38.304: "NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state".
[43]
TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2".
[44]
TS 28.705: "Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[45]
TS 28.702: "Telecommunication management; Core Network (CN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[46]
TS 28.652: "Telecommunication management; Universal Terrestrial Radio Access Network (UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[47]
TS 28.708: "Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[48]
TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3".
[49]
RFC 8089:  "The "file" URI Scheme".
[50]
TS 28.405: "Telecommunication management; Quality of Experience (QoE) measurement collection; Control and configuration".
[51]
TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)".
[52]
TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction".
[53]
TS 26.118: "Virtual Reality (VR) profiles for streaming applications".
[54]
RFC 3339:  "Date and Time on the Internet: Timestamps".
[55]
RFC 6991:  "Common YANG Data Types".
[56]
TS 28.658: "Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[57]
TS 28.558: "Management and orchestration; UE level measurements for 5G system".
[58]
TS 28.111: "Fault management"
[59]
TS 32.404: "Performance Management (PM); Performance measurements; Definitions and template".
[60]
RFC 1166:  "Internet Numbers".
[61]
RFC 5952:  "A recommendation for IPv6 address text representation".
[62]
RFC 3986:  "Uniform Resource Identifier (URI): Generic Syntax".
[63]
OpenAPI: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0.
Up

3  Definitions and abbreviations  p. 12

3.1  Definitions  p. 12

For the purposes of the present document, the following terms and definitions apply. For terms and definitions not found here, please refer to TS 32.101, TS 32.102, TS 32.150 and TS 32.600.
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 TS 32.156. 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 for additional information on IOC.
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)
Reproduction of 3GPP TS 28.622, Fig. 3.1: Relationships between a Name space and a number of participating MOs
Figure 3.1: Relationships between a Name space and a number of participating MOs
Up
Name space:
A name space is a collection of names. The IRP name convention (see TS 32.300) 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.
Network Resource Model (NRM):
A collection of IOCs, inclusive of their associations, attributes and operations, representing a set of network resources under management.
Data node:
This term is defined in TS 32.156.
Up

3.2  Abbreviations  p. 14

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
CAG
Closed Access Group
DN
Distinguished Name (see TS 32.300)
IOC
Information Object Class
MO
Managed Object
MOC
Managed Object Class
MOI
Managed Object Instance
MnS
Management Service (see TS 28.533)
NID
Network ID
NFVI
Network Functions Virtualisation Infrastructure (NFVI): Defined in ETSI GS NFV 003 [15].
NPN
Non-Public Network
PNI-NPN
Public Network Integrated Non-Public Network
RDN
Relative Distinguished Name (see TS 32.300)
SNPN
Standalone Non-Public Network
SS
Solution Set
VNF
Virtualised Network Function
Up

Up   Top   ToC