TS 28.540
★
Management and Orchestration –
5G Network Resource Model (NRM) – Stage 1
Use "3GPP‑Page" to get the Word version,
and "ETSI‑search" to get the PDF version
V17.0.0 (Wzip)
2020/09 10 p.
V16.2.0 (PDF)
2020/03 12 p.
V15.1.0
2018/12 11 p.
- Rapporteur:
- Miss Ping, Jing
Content for TS 28.540 Word version: 17.0.0
1 Scope Word‑p. 5
The present document specifies the requirements for the Network Resource Model (NRM) definition of NR, NG-RAN, 5G Core Network (5GC) and network slice, to support the management for:
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.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.501: "System Architecture for the 5G System".
[3]
TS 38.300: "NR; Overall description; Stage-2".
[4]
TS 38.401: "NG-RAN; Architecture description".
[5]
TS 37.340: "NR; Multi-connectivity; Overall description; Stage 2".
[6]
TS 28.531: "Management and orchestration of 5G networks; Provisioning".
[7]
TS 23.502: "Procedures for the 5G System; Stage 2".
[8]
GSMA NG.116: "Generic Network Slice Template" v1.0 (2019-05-23).
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
5G Core Network:
Defined in TS 23.501.
AMF Region:
Defined in TS 23.501.
AMF Set:
Defined in TS 23.501.
en-gNB:
Defined in TS 37.340.
gNB:
Defined in TS 38.300.
gNB Central Unit (gNB-CU):
Defined in TS 38.401.
gNB-CU-Control Plane (gNB-CU-CP):
Defined in TS 38.401.
gNB-CU-User Plane (gNB-CU-UP):
Defined in TS 38.401.
gNB Distributed Unit (gNB-DU):
Defined in TS 38.401.
ng-eNB:
Defined in TS 38.300.
NG-RAN:
Defined in TS 23.501.
3.2 Abbreviations Word‑p. 6
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.
5GC
5G Core network
5GS
5G System
AMF
Access and Mobility Management Function
EN-DC
E-UTRA-NR Dual Connectivity
EPS
Evolved Packet System
MR-DC
Multi-RAT Dual Connectivity
NG-RAN
NG Radio Access Network
NR
New Radio
PCF
Policy Controle Function
UDM
Unified Data Management
UDR
Unified Data Repository
UDSF
Unstructured Data Storage Function
4 Concepts and background
4.1 NR and NG-RAN deployment scenarios
According to NG-RAN architecture defined in TS 38.300, An NG-RAN node is either a gNB or an ng-eNB connected to 5GC.
A gNB may consist of a gNB-CU and one or more gNB-DU(s), and a gNB-CU may consist of a gNB-CU-CP and one or more gNB-CU-UP. From functional split point of view, there have following gNB deployment scenarios which are specified in TS 38.401:
-
gNB which does not consist split function.
-
gNB which consists of gNB-CU and gNB-DU(s).
-
gNB which consists of gNB-CU-CP, gNB-CU-UP(s) and gNB-DU(s).
Abovementioned deployment scenarios apply to en-gNB also.
Part of gNB (e.g. gNB-CU) can be deployed as virtualized network function.
4.2 MR-DC
Besides single connectivity operation, E-UTRAN, NR and NG-RAN support Multi-RAT Dual Connectivity (MR-DC) operation defined in TS 37.340, which can be further divided into following two categories based on connected core network types.
-
MR-DC with the EPC via EN-DC, the NR node in EN-DC is called en-gNB.
-
MR-DC with the 5GC via either NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC) or NR-E-UTRA Dual Connectivity (NE-DC).
There are different user plane connectivity options of the master node and secondary node involved in MR-DC (see detail in TS 37.340).
4.3 5GC architecture Word‑p. 7
The 5G architecture is defined as service-based and the interaction between network functions is represented in the following two ways:
-
Service-based representation
-
Reference point representation
The network functions composed 5GC is specified in TS 23.501, network functions within the 5GC control plane shall only use service-based interfaces for their interactions.
4.4 Data storage architecture
5G system architecture allows UDM, PCF and NEF to store their data in the Unified Data Repository (UDR), and allows any NF to store and retrieve its unstructured data (e.g. UE context) into/from a UDSF.
4.5 AMF load balancing insides AMF Region/AMF Set
When deploying AMF Region or AMF Set, AMF load balancing insides AMF Region/AMF Set is achieved by setting a weight factor for each AMF according to its relative capacity compared to other AMFs, see detail in clause 5.19.3 of TS 23.501.
4.6 5GC NFs supporting edge computing
Edge computing enables operator and 3rd party services to be hosted close to the UE's access point of attachment, so as to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network, see details in clause 5.13 of TS 23.501.
4.7 General information for network slice instance and network slice subnet instance
The general information used to describe network slice instance and network slice subnet instance are specified in TS 28.531.
4.8 Remote Interference Management
A remote interference scenario may involve a number of victim and aggressor cells, where the gNBs execute Remote Interference Management (RIM) coordination on behalf of their respective cells. Aggressor and victim gNBs or cells can be grouped into semi-static sets, where each cell is asigned a set ID, and is configured with a RIM Reference Signal (RIM-RS) and the radio resources associated with the set ID. As defined in TS 38.300.
5 Requirements
5.1 Requirements for management of NG-RAN
The following specific requirements apply to NG-RAN:
REQ-NGRAN_NRM-CON-001:
The NRM definitions shall support management of NG-RAN, containing gNB or/and ng-eNB.
REQ-NGRAN_NRM-CON-002:
The NRM definitions shall support management of either gNB without split function or gNB with split functions defined in TS 38.401.
REQ-NGRAN_NRM-CON-003:
The NRM definitions shall support management of virtualized network functions that are part of gNB, e.g. virtualized gNB-CU.
REQ-NGRAN_NRM-CON-004:
The NRM definitions shall support management of intra-NG-RAN handover between any combinations of gNB and ng-eNB.
REQ-NGRAN_NRM-CON-005:
The NRM definitions shall support management of inter-system handover between 5GS and EPS.
REQ-NGRAN_NRM-CON-006:
The NRM definitions shall support management of network slicing feature in NG-RAN.
REQ-NGRAN_NRM-CON-007:
The NRM definitions shall have a read-only representation of NR beam properties in NG-RAN.
REQ-NGRAN_NRM-CON-008:
The NRM definitions shall support configuration of sector carrier coverage properties in NG-RAN.
REQ-NGRAN_NRM-CON-009:
The NRM definitions shall support management of radio access network sharing feature in NG-RAN.
5.2 Requirements for management of MR-DC Word‑p. 8
The following specific requirements apply to MR-DC management, including management of NR in EN-DC and other MR-DC operations.
REQ-MRDC_NRM-CON-001:
The NRM definitions shall support management of NR node in EN-DC operation (en-gNB).
REQ-MRDC_NRM-CON-002:
The NRM definitions shall support management of en-gNB with different user plane connectivity options defined in TS 37.340.
REQ-MRDC_NRM-CON-003:
The NRM definitions shall support management of NG-RAN nodes in NGEN-DC operation.
REQ-MRDC_NRM-CON-004:
The NRM definitions shall support management different user plane connectivity options in NGEN-DC operation defined in TS 37.340.
REQ-MRDC_NRM-CON-005:
The NRM definitions shall support management of NG-RAN nodes in EN-DC operation.
REQ-MRDC_NRM-CON-006:
The NRM definitions shall support management different user plane connectivity options in NE-DC operation defined in TS 37.340.
5.3 Requirements for management of 5GC NFs
The following specific requirements apply to management of 5GC NFs:
REQ-5GC_NRM-CON-001:
The NRM definitions shall support management of 5GC containing variety of network functions defined in TS 23.501.
REQ-5GC_NRM-CON-002:
The NRM definitions should support management of all the relationships between network functions and corresponding data storage functions where the network functions store/retrieve their data.
REQ-5GC_NRM-CON-003:
The NRM definitions shall support management of interworking between 5GC and EPC.
REQ-5GC_NRM-CON-004:
The NRM definitions shall support management of network slicing feature in 5GC.
REQ-5GC_NRM-CON-005:
The NRM definitions shall support management of 5GC network function services independently to align with requirements of TS 23.501.
REQ-5GC_NRM-CON-006:
The NRM definitions shall support NF service instance registration, deregistration, update, etc., with NRF during NF service instance lifecycle to align with requirements of TS 23.501 and TS 23.502.
REQ-5GC_NRM-CON-007:
5.4 Requirements for management of AMF Set Word‑p. 9
REQ-AMFSET_NRM-CON-001:
The NRM definitions shall support management of AMF Region and AMF Set, including AMF load balancing management.
5.5 Requirements for management of edge computing
REQ-ECM_NRM-CON-001:
The NRM definitions shall support management of 5GC NFs supporting edge computing.
5.6 Requirements for management of network slice and network slice subnet
The following requirements apply to network slice and network slice subnet:
REQ-NS_NRM-CON-001:
The NRM definitions shall support management of network slice.
REQ-NS_NRM-CON-002:
The NRM definitions shall support management of network slice subnet.
REQ-NS_NRM-CON-003:
The NRM definitions shall support the attributes of the Generic network Slice Template (GST) defined by GSMA [8].
5.7 Requirements Remote Interference Management
REQ-NGRAN_NRM-CON-001:
The NRM definitions should support Remote Interference Management.
$ Change history Word‑p. 10
- 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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.501: "System Architecture for the 5G System".
[3]
TS 38.300: "NR; Overall description; Stage-2".
[4]
TS 38.401: "NG-RAN; Architecture description".
[5]
TS 37.340: "NR; Multi-connectivity; Overall description; Stage 2".
[6]
TS 28.531: "Management and orchestration of 5G networks; Provisioning".
[7]
TS 23.502: "Procedures for the 5G System; Stage 2".
[8]
GSMA NG.116: "Generic Network Slice Template" v1.0 (2019-05-23).
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
5G Core Network:
Defined in TS 23.501.
AMF Region:
Defined in TS 23.501.
AMF Set:
Defined in TS 23.501.
en-gNB:
Defined in TS 37.340.
gNB:
Defined in TS 38.300.
gNB Central Unit (gNB-CU):
Defined in TS 38.401.
gNB-CU-Control Plane (gNB-CU-CP):
Defined in TS 38.401.
gNB-CU-User Plane (gNB-CU-UP):
Defined in TS 38.401.
gNB Distributed Unit (gNB-DU):
Defined in TS 38.401.
ng-eNB:
Defined in TS 38.300.
NG-RAN:
Defined in TS 23.501.
3.2 Abbreviations Word‑p. 6
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.
5GC
5G Core network
5GS
5G System
AMF
Access and Mobility Management Function
EN-DC
E-UTRA-NR Dual Connectivity
EPS
Evolved Packet System
MR-DC
Multi-RAT Dual Connectivity
NG-RAN
NG Radio Access Network
NR
New Radio
PCF
Policy Controle Function
UDM
Unified Data Management
UDR
Unified Data Repository
UDSF
Unstructured Data Storage Function
5G Core network
5GS
5G System
AMF
Access and Mobility Management Function
EN-DC
E-UTRA-NR Dual Connectivity
EPS
Evolved Packet System
MR-DC
Multi-RAT Dual Connectivity
NG-RAN
NG Radio Access Network
NR
New Radio
PCF
Policy Controle Function
UDM
Unified Data Management
UDR
Unified Data Repository
UDSF
Unstructured Data Storage Function
4.1 NR and NG-RAN deployment scenarios
According to NG-RAN architecture defined in TS 38.300, An NG-RAN node is either a gNB or an ng-eNB connected to 5GC.
A gNB may consist of a gNB-CU and one or more gNB-DU(s), and a gNB-CU may consist of a gNB-CU-CP and one or more gNB-CU-UP. From functional split point of view, there have following gNB deployment scenarios which are specified in TS 38.401:
- gNB which does not consist split function.
- gNB which consists of gNB-CU and gNB-DU(s).
- gNB which consists of gNB-CU-CP, gNB-CU-UP(s) and gNB-DU(s).
4.2 MR-DC
Besides single connectivity operation, E-UTRAN, NR and NG-RAN support Multi-RAT Dual Connectivity (MR-DC) operation defined in TS 37.340, which can be further divided into following two categories based on connected core network types.
- MR-DC with the EPC via EN-DC, the NR node in EN-DC is called en-gNB.
- MR-DC with the 5GC via either NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC) or NR-E-UTRA Dual Connectivity (NE-DC).
4.3 5GC architecture Word‑p. 7
The 5G architecture is defined as service-based and the interaction between network functions is represented in the following two ways:
-
Service-based representation
-
Reference point representation
The network functions composed 5GC is specified in TS 23.501, network functions within the 5GC control plane shall only use service-based interfaces for their interactions.
4.4 Data storage architecture
5G system architecture allows UDM, PCF and NEF to store their data in the Unified Data Repository (UDR), and allows any NF to store and retrieve its unstructured data (e.g. UE context) into/from a UDSF.
4.5 AMF load balancing insides AMF Region/AMF Set
When deploying AMF Region or AMF Set, AMF load balancing insides AMF Region/AMF Set is achieved by setting a weight factor for each AMF according to its relative capacity compared to other AMFs, see detail in clause 5.19.3 of TS 23.501.
4.6 5GC NFs supporting edge computing
Edge computing enables operator and 3rd party services to be hosted close to the UE's access point of attachment, so as to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network, see details in clause 5.13 of TS 23.501.
4.7 General information for network slice instance and network slice subnet instance
The general information used to describe network slice instance and network slice subnet instance are specified in TS 28.531.
4.8 Remote Interference Management
A remote interference scenario may involve a number of victim and aggressor cells, where the gNBs execute Remote Interference Management (RIM) coordination on behalf of their respective cells. Aggressor and victim gNBs or cells can be grouped into semi-static sets, where each cell is asigned a set ID, and is configured with a RIM Reference Signal (RIM-RS) and the radio resources associated with the set ID. As defined in TS 38.300.
- Service-based representation
- Reference point representation
5.1 Requirements for management of NG-RAN
The following specific requirements apply to NG-RAN:
REQ-NGRAN_NRM-CON-001:
The NRM definitions shall support management of NG-RAN, containing gNB or/and ng-eNB.
REQ-NGRAN_NRM-CON-002:
The NRM definitions shall support management of either gNB without split function or gNB with split functions defined in TS 38.401.
REQ-NGRAN_NRM-CON-003:
The NRM definitions shall support management of virtualized network functions that are part of gNB, e.g. virtualized gNB-CU.
REQ-NGRAN_NRM-CON-004:
The NRM definitions shall support management of intra-NG-RAN handover between any combinations of gNB and ng-eNB.
REQ-NGRAN_NRM-CON-005:
The NRM definitions shall support management of inter-system handover between 5GS and EPS.
REQ-NGRAN_NRM-CON-006:
The NRM definitions shall support management of network slicing feature in NG-RAN.
REQ-NGRAN_NRM-CON-007:
The NRM definitions shall have a read-only representation of NR beam properties in NG-RAN.
REQ-NGRAN_NRM-CON-008:
The NRM definitions shall support configuration of sector carrier coverage properties in NG-RAN.
REQ-NGRAN_NRM-CON-009:
The NRM definitions shall support management of radio access network sharing feature in NG-RAN.
5.2 Requirements for management of MR-DC Word‑p. 8
The following specific requirements apply to MR-DC management, including management of NR in EN-DC and other MR-DC operations.
REQ-MRDC_NRM-CON-001:
The NRM definitions shall support management of NR node in EN-DC operation (en-gNB).
REQ-MRDC_NRM-CON-002:
The NRM definitions shall support management of en-gNB with different user plane connectivity options defined in TS 37.340.
REQ-MRDC_NRM-CON-003:
The NRM definitions shall support management of NG-RAN nodes in NGEN-DC operation.
REQ-MRDC_NRM-CON-004:
The NRM definitions shall support management different user plane connectivity options in NGEN-DC operation defined in TS 37.340.
REQ-MRDC_NRM-CON-005:
The NRM definitions shall support management of NG-RAN nodes in EN-DC operation.
REQ-MRDC_NRM-CON-006:
The NRM definitions shall support management different user plane connectivity options in NE-DC operation defined in TS 37.340.
5.3 Requirements for management of 5GC NFs
The following specific requirements apply to management of 5GC NFs:
REQ-5GC_NRM-CON-001:
The NRM definitions shall support management of 5GC containing variety of network functions defined in TS 23.501.
REQ-5GC_NRM-CON-002:
The NRM definitions should support management of all the relationships between network functions and corresponding data storage functions where the network functions store/retrieve their data.
REQ-5GC_NRM-CON-003:
The NRM definitions shall support management of interworking between 5GC and EPC.
REQ-5GC_NRM-CON-004:
The NRM definitions shall support management of network slicing feature in 5GC.
REQ-5GC_NRM-CON-005:
The NRM definitions shall support management of 5GC network function services independently to align with requirements of TS 23.501.
REQ-5GC_NRM-CON-006:
The NRM definitions shall support NF service instance registration, deregistration, update, etc., with NRF during NF service instance lifecycle to align with requirements of TS 23.501 and TS 23.502.
REQ-5GC_NRM-CON-007:
5.4 Requirements for management of AMF Set Word‑p. 9
REQ-AMFSET_NRM-CON-001:
The NRM definitions shall support management of AMF Region and AMF Set, including AMF load balancing management.
5.5 Requirements for management of edge computing
REQ-ECM_NRM-CON-001:
The NRM definitions shall support management of 5GC NFs supporting edge computing.
5.6 Requirements for management of network slice and network slice subnet
The following requirements apply to network slice and network slice subnet:
REQ-NS_NRM-CON-001:
The NRM definitions shall support management of network slice.
REQ-NS_NRM-CON-002:
The NRM definitions shall support management of network slice subnet.
REQ-NS_NRM-CON-003:
The NRM definitions shall support the attributes of the Generic network Slice Template (GST) defined by GSMA [8].
5.7 Requirements Remote Interference Management
REQ-NGRAN_NRM-CON-001:
The NRM definitions should support Remote Interference Management.
The NRM definitions shall support management of NR node in EN-DC operation (en-gNB).
REQ-MRDC_NRM-CON-002:
The NRM definitions shall support management of en-gNB with different user plane connectivity options defined in TS 37.340.
REQ-MRDC_NRM-CON-003:
The NRM definitions shall support management of NG-RAN nodes in NGEN-DC operation.
REQ-MRDC_NRM-CON-004:
The NRM definitions shall support management different user plane connectivity options in NGEN-DC operation defined in TS 37.340.
REQ-MRDC_NRM-CON-005:
The NRM definitions shall support management of NG-RAN nodes in EN-DC operation.
REQ-MRDC_NRM-CON-006:
The NRM definitions shall support management different user plane connectivity options in NE-DC operation defined in TS 37.340.
The NRM definitions shall support management of 5GC containing variety of network functions defined in TS 23.501.
REQ-5GC_NRM-CON-002:
The NRM definitions should support management of all the relationships between network functions and corresponding data storage functions where the network functions store/retrieve their data.
REQ-5GC_NRM-CON-003:
The NRM definitions shall support management of interworking between 5GC and EPC.
REQ-5GC_NRM-CON-004:
The NRM definitions shall support management of network slicing feature in 5GC.
REQ-5GC_NRM-CON-005:
The NRM definitions shall support management of 5GC network function services independently to align with requirements of TS 23.501.
REQ-5GC_NRM-CON-006:
The NRM definitions shall support NF service instance registration, deregistration, update, etc., with NRF during NF service instance lifecycle to align with requirements of TS 23.501 and TS 23.502.
REQ-5GC_NRM-CON-007:
REQ-AMFSET_NRM-CON-001:
The NRM definitions shall support management of AMF Region and AMF Set, including AMF load balancing management.
5.5 Requirements for management of edge computing
REQ-ECM_NRM-CON-001:
The NRM definitions shall support management of 5GC NFs supporting edge computing.
5.6 Requirements for management of network slice and network slice subnet
The following requirements apply to network slice and network slice subnet:
REQ-NS_NRM-CON-001:
The NRM definitions shall support management of network slice.
REQ-NS_NRM-CON-002:
The NRM definitions shall support management of network slice subnet.
REQ-NS_NRM-CON-003:
The NRM definitions shall support the attributes of the Generic network Slice Template (GST) defined by GSMA [8].
5.7 Requirements Remote Interference Management
REQ-NGRAN_NRM-CON-001:
The NRM definitions should support Remote Interference Management.