Top   in Index   Prev   Next

TS 28.701
Core Network (CN) NRM IRP –

Use "3GPP‑Page" to get the Word version, and "ETSI‑search" to get the PDF version
V16.0.0 (PDF)  2020/06  10 p.
V15.1.0  2018/09  10 p.
V14.0.0  2017/03  10 p.
V13.0.0  2016/01  10 p.
V12.0.0  2014/10  10 p.
V11.1.0  2014/06  10 p.
Mr. Heskin, Eamon

Content for  TS 28.701  Word version:  16.0.0

Here   Top

0  IntroductionWord‑p. 4
The present document is part of a TS-family covering the 3rd Generation Partnership Project Technical Specification Group Services and System Aspects, Telecommunication management; Configuration Management (CM); as identified below:
"Core Network (CN) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements".
"Core Network (CN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
"Core Network CN) Network Resource Model (NRM)Integration Reference Point (IRP); Solution Set (SS) definitions".
Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of the 3GPP network as it evolves. CM actions have the objective to control and monitor the actual configuration on the Network Elements (NEs) and Network Resources (NRs), and they may be initiated by the operator or by functions in the Operations Systems (OSs) or NEs.
CM actions may be requested as part of an implementation programme (e.g. additions and deletions), as part of an optimisation programme (e.g. modifications), and to maintain the overall Quality of Service (QoS). The CM actions are initiated either as single actions on single NEs of the 3GPP network, or as part of a complex procedure involving actions on many resources/objects in one or several NEs.

1  ScopeWord‑p. 5
The present document defines, in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Core Network Network Resource Model IRP.

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.
TS 32.101: "Telecommunication management; Principles and high level requirements".
TS 32.102: "Telecommunication management; Architecture".
TS 32.600: "Telecommunication management; Configuration Management (CM); Concept and high-level requirements".
TS 32.602: "Telecommunication management; Configuration Management (CM); Basic Configuration Management Integration Reference Point (IRP): Information Service (IS)".
TS 28.704: " Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements".
TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
TS 28.620: "Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model (UIM)".
TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service".

3  Definitions and abbreviations

3.1  Definitions

For the purposes of the present document, the following terms and definitions apply.
is any information or set of information required to give software or equipment or combinations thereof a specific state of functionality.
Element Manager (EM):
provides a package of end-user functions for management of a set of closely related types of Network Elements (NEs). These functions can be divided into two main categories:
  • Element Management Functions for management of NEs on an individual basis. These are basically the same functions as supported by the corresponding local terminals.
  • Sub-Network Management Functions that are related to a network model for a set of NEs constituting a clearly defined sub-network, which may include relations between the NEs. This model enables additional functions on the sub-network level (typically in the areas of network topology presentation, alarm correlation, service impact analysis and circuit provisioning).
Information Object Class (IOC):
See definition in TS 28.622.
Integration Reference Point (IRP):
See TS 32.150.
Information Service (IS):
See TS 32.150.
Solution Set (SS):
See TS 32.150.
IRP Solution Set:
See TS 32.101.
Managed Object (MO):
an abstract entity, which may be accessed through an open interface between two or more systems, and representing a Network Resource (NR) for the purpose of management. The Managed Object (MO) is an instance of a Managed Object Class (MOC) as defined in a Management Information Model (MIM). The MIM does not define how the MO or NR is implemented; only what can be seen in the interface.
Managed Object Class (MOC):
a description of all the common characteristics for a number of MOs, such as their attributes, operations, notifications and behaviour.
Management Information Model (MIM):
also referred to as NRM - see the definition below. There is a slight difference between the meaning of MIM and NRM - the term MIM is generic and can be used to denote any type of management model, while NRM denotes the model of the actual managed telecommunications Network Resources (NRs).
Network Element (NE):
is a discrete telecommunications entity, which can be, managed over a specific interface e.g. the RNC.
Network Manager (NM):
provides a package of end-user functions with the responsibility for the management of a network, mainly as supported by the EM(s) but it may also involve direct access to the NEs. All communication with the network is based on open and well-standardised interfaces supporting management of multi-vendor and multi-technology NEs.
Network Resource (NR):
is a component of a NE, which can be identified as a discrete separate entity and is in an object oriented environment for the purpose of management represented by an abstract entity called Managed Object (MO).
Network Resource Model (NRM):
See definition in TS 28.622.
Object Management Group (OMG):
Operations System (OS):
indicates a generic management system, independent of its location level within the management hierarchy.

3.2  AbbreviationsWord‑p. 6
For the purposes of the present document, the following abbreviations apply:
Configuration Management
Core Network
Element Manager
Fault Management
Global System for Mobile communication
IP Multimedia Subsystem
Information Object Class
Integration Reference Point
Information Service (see [1])
Management Information Base
Management Information Model
Managed Object Class
Managed Object Instance
Network Element
Network Manager
Network Resource
Network Resource Model
Object Management Group
Operations System
Performance Management
Telecom Management
Unified Modelling Language (OMG)

4  RequirementsWord‑p. 7
The following general and high-level requirements apply for the present IRP:
  1. IRP-related requirements in TS 32.101.
  2. IRP-related requirements in TS 32.102.
  3. IRP-related requirements in TS 32.600.
In addition to the above, the following more specific requirements apply:
  1. The Network Resource Model defined by this IRP shall contain CN specific IOCs and related definitions, supporting Core Network entities in the current 3GPP Release, except for the IMS parts of CN (for the IMS parts, refer to the IMS NRM IRP Requirements in TS 28.704).
  2. The Network Resource Model defined by this IRP shall provide support for enabling consistency between UTRAN/GERAN and CN parameters, e.g. by defining relevant attributes.
The NRM defined by this IRP:
  1. Shall support communications for telecommunication network management purposes, including management of converged networks.
  2. Is a member of the Federated Network Information Model (FNIM) [5] and its information is derived from FNIM Umbrella Information Model (UIM) [7].

$  Change HistoryWord‑p. 8

Up   Top