Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 28.708  Word version:  18.0.0

Top   Top   None   None   Next
0…   4…

 

0  Introductionp. 6

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";
Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of the 3G 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 optimization 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 3G network, or as part of a complex procedure involving actions on many resources/objects in one or several NEs.
Up

1  Scopep. 7

The present document specifies Evolved Packet Core (EPC) network resource information that can be communicated between an IRPAgent and an IRPManager for telecommunication network management purposes, including management of converged networks. . It reuses relevant parts of the Generic NRM in TS 28.622, either by direct reuse or sub-classing, and in addition to that defines EPC specific Information Object Classes.
This document specifies the semantics and behaviour 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.
In order to access the information defined by this NRM, an Interface IRP such as the "Basic CM IRP" is needed (TS 32.602). However, which Interface IRP is applicable is outside the scope of the present document.
Up

2  Referencesp. 7

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.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
[4]
TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects".
[5]
TS 32.600: "Telecommunication management; Configuration Management (CM); Concept and high-level requirements".
[6]
TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[7]
TS 32.602: "Telecommunication management; Configuration Management (CM); Basic Configuration Management Integration Reference Point (IRP): Information Service (IS)".
[8]
TS 28.702: " Telecommunication management; Core Network (CN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[9]
TS 23.401: "GPRS enhancements for E-UTRAN access".
[10]
TS 28.705: "Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)".
[11]
TS 28.658: "Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[12]
TS 23.402: "Architecture Enhancements for non-3GPP accesses".
[13]
TS 32.662: "Telecommunication management; Configuration Management (CM); Kernel CM; Information service (IS)".
[14]
TS 23.003: " Technical Specification Group Core Network and Terminals; Numbering, addressing and identification".
[15]
TR 32.816: "Telecommunication management; Study on management of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and Evolved Packet Core (EPC) ".
[16]
TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[17]
TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[18]
TS 36.331: " Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
[19]
TS 23.203: "Policy and charging control architecture".
[20]
TS 32.302: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)".
[21]
TS 28.541: "Management and orchestration of networks and network slicing; NR and NG-RAN Network Resource Model (NRM); Stage 2 and stage 3".
[22]
3GPP TS 28.543: "Management and orchestration of networks and network slicing; 5G Core Network (5GC) Network Resource Model (NRM); Stage 2 and stage 3".
[23]
TS 23.214: "Architecture enhancements for control and user plane separation of EPC nodes".
Up

3  Definitions and abbreviationsp. 8

3.1  Definitionsp. 8

For the purposes of the present document, the terms and definitions given in TS 32.101, TS 32.102, TS 32.600 and the following apply:
Association:
See definition in TS 28.622.
Managed Element (ME):
See definition in TS 28.622.
Managed Object (MO):
See definition in TS 28.622.
Management Information Model (MIM):
also referred to as NRM - see the definition below.
Network Resource Model (NRM):
See definition in TS 28.622.

3.2  Abbreviationsp. 8

For the purposes of the present document, the following abbreviations apply:
CIM
Common Information Model
CUPS
Control and User Plane Separation
EM
Element Manager
eNodeB
evolved NodeB
EPC
Evolved Packet Core
ePDG
evolved Packet Data Gateway
E-UTRAN
Evolved Universal Terrestrial Radio Access Network
GPRS
General Packet Radio System
IOC
Information Object Class
IRP
Integration Reference Point
IS
Information Service
ME
Managed Element
MIM
Management Information Model
MME
Mobility Management Entity
MO
Managed Object
NE
Network Element
NR
Network Resource
NRM
Network Resource Model
PCRF
Policy and Charging Rules Function
P GW
PDN Gateway
PGW-C
PDN Gateway Control plane function
PGW-U
PDN Gateway User plane function
RDN
Relative Distinguished Name (see TS 32.300)
S GW
Serving Gateway
SGW-C
Serving Gateway Control plane function
SGW-U
Serving Gateway User plane function
TMN
Telecom Management Network
UML
Unified Modelling Language
Up

Up   Top   ToC