5.1 Management reference model and interfaces

32.1013GPPPrinciples and high level requirementsRelease 17Telecommunication managementTS

5.1.1 Overview

Figure 1 illustrates the management reference model. It shows the Operations Systems interfacing with other systems.

The present document (and the rest of the 3GPP management detailed specifications) addresses the Operations System (function and architecture wise) and the interfaces to the other systems (information and protocol wise).

The present document does not address the definition of any of the systems, which the Operations System may interface to. The rest of the 3GPP specifications regarding management will not cover them either.

It is not the approach (nor it is possible) to re-define the complete management of all the technologies that might be used in the provision of a PLMN. However, it is the intention to identify and define what will be needed from the perspective of management.

An Operations System supports management interfaces to other systems. In each Operations System, a number of functions are present. The function(s) in execution would effectuate how the Operations System would interface to other systems.  

Examples of functions and entities included at the Network Management layer in an Operations System may include but are not limited to:

– Management and Orchestration, of network services.

– On-line network support for 3GPP services.

– Network planning including Radio Planning.

– Network Configuration Management.

– SON automation Management and Orchestration.

– Alarm correlation.

– Network event correlation.

– Network Supervision.

– Network Performance Monitoring.

– Operator terminal.

– LSA Controller (LC).

– IRP Manager.

Examples of functions and entities included at the Domain/Element Management layer in an Operations System may include but are not limited to:

– Network Configuration Management.

– Alarm correlation.

– Network Performance Monitoring.

– SON automation Management and Orchestration.

– Operator terminal.

– IRP Agent.

A number of management interfaces in a PLMN are identified in figure 1, namely:

1) between the Network Elements (NEs) and the Element Manager (EM) of a single PLMN Organisation;

2) between the Element Manager (EM) and the Network Manager (NM) of a single PLMN Organisation;

NOTE: In certain cases the Element Manager functionality may reside in the NE in which case this interface is directly from NE to Network Manager). These management interfaces are given the reference name Itf-N and are the primary target for standardization.

3) between the Network Managers and the Enterprise Systems of a single PLMN Organisation;

4) between the Network Managers (NMs) of a single PLMN Organisation;

4a) between the Domain Managers (DMs) of a single PLMN Organisation.

5) between Enterprise Systems & Network Managers of different PLMN Organisations;

5a) between the Domain Managers (DMs) of different PLMN Organisations.

6) between Network Elements (NEs).

7) between the Network Management Layer Service (NMLS) and the Network Manager (NM).

IRPs may be implemented at interfaces 2, 3, 4, 5 and 7.

The present document identifies Type 1, Type 2 and Type 4 management interfaces. The rest of the 3GPP management specifications focus on Type 2 and to a lesser extent on Type 1 management interfaces. In addition, the rest of the 3GPP management specifications will not refer to Type 4 management interface. Specific Type 2 protocols and information model that are applicable for use in Type 4 management interface are listed in Annex E.

The present document identifies Types 3, 5 & 5a management interfaces. Detailed specification of these interfaces is For Further Study (FFS).

The present document identifies as well a Type 7 management interface.

The specification of the management interfaces of type 4 & 6 is beyond the scope of standardisation.

Figure 1: Management reference model

5.1.2 Interfaces from Operations Systems to NEs (Type 1 & 2)

In some cases, the management interfaces to NEs have been defined bottom-up, trying to standardise the complete OAM&P functionality of the various NEs.

For PLMN management, a top-down approach will be followed to streamline the requirements from the perspective of Operators top priority management processes.

It is assumed that this will not fully cover the OAM&P functionality of all NE types at once; therefore a part of the functionality will be phased for further work and consideration. Some proprietary solutions (local and/or remote) will be needed in the interim. The rationale of this approach is not only the best use of resources, but also to follow a pragmatic step-wise approach that takes into account the market forces (the manufacturers and operators capabilities). A further rationale is to define clear and easy-to-agree steps that allow management functionality to be implemented in the same time frame as the telecom functionality in the network (i.e. to synchronise the management and network releases).

5.1.2.1 Interfaces from EM Operations Systems to NEs (Type 1)

The approach for NE management interfaces of Type 1 will be to allow the use of certain management application layer protocols (Management-application-layer-protocols). See Annex A for the list of Management-application-layer-protocols.

5.1.2.2 Interfaces from NM Operations Systems to NEs (Type 2)

The approach for NE management interfaces of Type 2 will be to concentrate on Management-application-layer-protocol independent information models (see 5.2.2 Information Model Level), allowing a mapping to several Management-application-layer-protocols (see 5.2.3 Solution Set Level). The rational is:

– Due to the convergence of Information and Telecommunication technologies, it is required to work on a more open approach (acknowledging the market status and foreseen evolutions);

– The life cycle of information flows, characterised by information models, is 10 to 20 years, while that of Management-application-layer-protocols is 5 to 10 years;

– Developments in automatic conversion from information models to various Management-application-layer-protocols will allow a more pragmatic and open approach (e.g. UML to IDL).

However, it is the intention to at least recommend one mapping for each information model defined.

Figure 2 shows the management interfaces of one part of the 3GPP System (the Radio Network), by way of illustration of interfaces of types 1 and 2.

Figure 2: Radio Network management interfaces

Figure 2 identifies the following management interfaces:

– Itf-B – between Node B & its Manager (physically, this may be a direct connection or via the RNC) (type 1).

– Itf-R – between RNC & its Manager (type 1).

– Itf-N – between the Network (Element Manager or NEs with an embedded EM) & Network Manager (type 2).

5.1.3 Interfaces to Enterprise Systems (Type 3)

The approach is to define a management structure that fully fits into the enterprise process needs of the PLMN Organisations. One of the essential issues of today’s way of running telecommunications businesses is integral operation (e.g. customer care, from service subscription to billing, from order fulfilment to complaint management).

Enterprise Systems are those Information Systems that are used in the telecommunication organisation but are not directly or essentially related to the telecommunications aspects (Call Centres, Fraud Detection and Prevention Systems, Invoicing etc.).

Standardising Enterprise Systems is out of the scope of 3GPP work, since it involves many operator choices (organisational, etc.) and even regulatory. Also Enterprise Systems are often viewed as a competitive tool. However, it is essential that the requirements of such systems are taken into account and interfaces to the Operations Systems are defined, to allow for easy interconnection and functional support.

5.1.3a Interface between Network Managers (Type 4)

Interface type 4 (where Itf-P2P is between Domain Managers of different PLMN Organisations) could have additional requirements over interface type 4a (see clause 5.1.3b) and therefore is FFS.

5.1.3b Interface between Domain Managers (Type 4a) – the Itf-P2P Interface

The approach for Interfaces of type 4a (the Itf-P2P interface) is the same as for interfaces of type 2 (the Itf-N interface – see clause 5.1.2.2).

The Itf-P2P should as much as possible re-use the interface definitions of the Itf-N interface.

Further details on the Itf-P2P interface are available in 3GPP TR 32.806 [107].

5.1.4 Interfaces to Operations Systems in other organisations (Type 5)

PLMN management considers integrally the interaction with the Operations Systems of other legal entities for the purpose of providing Mobile services.

There are two major types of interfaces to other management systems:

1) To the Operations Systems of another PLMN Organisation;

2) To the Operations Systems of a non-PLMN Organisation.

The first type deals with co-operation to provide Mobile services across a number of PLMN networks (e.g. roaming related interactions). The second type deals with client-server relationship to other operators (e.g. to leased lines providers, to added value service providers, etc.).

The approach that will be followed is to identify and define integral processes, not taking into account in the first step, how many operators or operations systems might be involved, but rather concentrating on the interactions between them (i.e. assuming an operator encompasses all functionalities). A further step will be to consider and define extra requirements (security, confidentiality etc.) when part of the process involves interactions with other operators Operations Systems (OSs).

5.1.5 Inter-NE interfaces (Type 6)

Interfaces between Network Elements are sometimes used to carry management information even though this may not be the primary purpose of the interface. An example in an UMTS network is the I_ub interface between Node-B and RNC (see figure 2 above). This type of interface is not within the scope of this specification, though potential impacts upon it should be considered.

5.1.6 Interface between NMLS and NM (Type 7)

The Type 7 interface is between the NMLS and the NM. The NMLS is the Service Provider (SP, see clause 5.4) and the NM the Service Consumer (SC, see clause 5.4).