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

TS 28.707
Evolved Packet Core (EPC) NRM IRP –
Requirements

3GPP‑Page   ETSI‑search   CONTENT↓
V17.0.0 (PDF)  2022/03  10 p.
V16.0.0  2020/06  10 p.
V15.0.0  2018/06  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.
Rapporteur:
Mr. Heskin, Eamon
Deutsche Telekom AG

Content for  TS 28.707  Word version:  17.0.0

Here   Top

0  Introduction  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; as identified below:
28.707:
"Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements".
28.708:
"Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
28.709:
"Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions".
Up

1  Scope  p. 5

The present document defines, in addition to the requirements defined in [1], [2] and [3], the Requirements for the EPC Network Resource Model (NRM) IRP.

2  References  p. 5

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.600: "Telecommunication management; Configuration Management (CM); Concept and high-level requirements".
[4]
TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
[5]
TS 32.107: "Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM)".
[6]
TS 28.620: "Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model (UIM)".
[7]
TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service".
[8]
TS 37.340: "NR; Multi-connectivity; Overall description; Stage 2".
Up

3  Definitions and abbreviations  p. 5

3.1  Definitions  p. 5

For the purposes of the present document, the following terms and definitions apply.
Data:
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):
see http://www.omg.org.
Operations System (OS):
indicates a generic management system, independent of its location level within the management hierarchy.
Up

3.2  Abbreviations  p. 6

For the purposes of the present document, the following abbreviations apply:
5GS
5G System
CM
Configuration Management
EDGE
Enhanced Data Rate for GSM Evolution
E-MBMS
Evolved Multimedia Broadcast Multicast Service
EN-DC
E-UTRA-NR Dual Connectivity
EPC
Evolved Packet Core
EPS
Evolved Packet System
E-UTRAN
Evolved Universal Terrestrial Radio Access Network
GERAN
GSM/EDGE Radio Access Network
IOC
Information Object Class
IRP
Integration Reference Point
IS
Information Service (see [1])
MME
Mobility Management Entity
MOC
Managed Object Class
NE
Network Element
NR
New Radio
NRM
Network Resource Model
OS
Operations System
UTRAN
Universal Terrestrial Radio Access Network
Up

4  Requirements  p. 7

4.1  General Requirement  p. 7

The following general requirements apply for the present IRP:
a)
IRP-related requirements in TS 32.101.
b)
IRP-related requirements in TS 32.102.
c)
IRP-related requirements in TS 32.600.
The NRM defined by this IRP:
d)
Shall support communications for telecommunication network management purposes, including management of converged networks.
e)
Is a member of the Federated Network Information Model (FNIM) [5] and its information is derived from FNIM Umbrella Information Model (UIM) [6].
Up

4.2  Business Level Requirement  p. 7

In addition to the general requirement, the following more specific requirements apply:
  1. The Network Resource Model defined by this IRP shall contain EPC specific IOCs and related definitions, supporting EPC Network entities in the 3GPP Release.
  2. The Network Resource Model defined by this IRP shall contain MME pool management specific IOCs and related definitions.
  3. The Network Resource Model defined by this IRP shall contain E-MBMS specific IOCs and related definitions.
  4. The Network Resource Model defined by this IRP shall contain EPC specific IOCs and related interaction relation definition, supporting the management of communication between EPC and 3GPP access (including E-UTRAN and EN-DC (see TS 37.340)), trusted non-3GPP access and untrusted non-3GPP access.
  5. The Network Resource Model defined by this IRP shall contain EPC specific IOCs and related interaction relation definition, supporting the EPS/5GS interworking management in EPC side.
Up

$  Change History  p. 8

Up   Top