A.3 Management support for EN-DC overall architecture
28.5303GPPConcepts, use cases and requirementsManagement and orchestrationRelease 17TS
NG-RAN supports Multi-Radio Dual Connectivity (MR-DC) operation whereby a UE in RRC_CONNECTED is connected to two different nodes, one providing NR access and the other one providing either E-UTRA or NR access. One node acts as the MN and the other as the SN. The MN and SN are connected via a network interface and at least the MN is connected to the core network (e.g. EPC).
The following figure illustrates the MR-DC with EPC (i.e. EN-DC) architecture in TS 37.340 [10].
Figure A.3-1: EN-DC Overall Architecture
NOTE 1: the en-gNB node provides NR user plane and control plane protocol terminations towards the UE, and acts as Secondary Node in EN-DC.
In order to provide management support for EN-DC, 3GPP management system needs to provide the management for en-gNB, eNB and EPC. There are also potential 2 management options to support, as follows.
EN-DC management Option#1
Figure Y.3-2: EN-DC management option#1
NOTE 2: The consumer behaves as IRPManager in IPR management mechanism of LTE and MnS consumer in service-based management mechanism of 5G.
In EN-DC management option#1,
– The en-gNB management domain provides MnS (including component type A, B and C) for management of en-gNB.
– The eNB management domain provides IRP (including interface IRP and NRM IRP) for the management of eNB.
– The EPC management domain provides IRP (including interface IRP and NRM IRP) for the management of EPC.
Figure Y.3-3: EN-DC management Option#2
NOTE 3: The consumer behaves as IRPManager in IPR management mechanism of LTE and MnS consumer in service-based management mechanism of 5G.
EN-DC management Option#2
In EN-DC management option#2,
– The en-gNB management domain provides MnS (including component type A, B and C) for management of en-gNB.
– The eNB management domain provides MnS (including component type A, B and C) for management of eNB. In this case, eNB NRM used as MnS component type B, which means the YAML/YANG solution set for eNB NRM needs to be provided.
– The EPC management domain provides MnS (including component type A, B and C) for management of EPC. In this case, EPC NRM used as MnS component type B, which means the YAML/YANG solution set for EPC NRM needs to be provided
Annex B (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2018-12 |
SA#82 |
SP-181041 |
0001 |
– |
F |
Align title with TS database |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181042 |
0002 |
1 |
F |
Fix gap of requirement for Network Slicing priority |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181043 |
0003 |
1 |
F |
Replace MF with managed function |
15.1.0 |
|
2019-09 |
SA#85 |
SP-190742 |
0009 |
1 |
F |
Fix inconsistencies related to service requirements |
15.2.0 |
|
2019-09 |
SA#85 |
SP-190753 |
0007 |
2 |
B |
Add MnS query related requirement |
16.0.0 |
|
2019-12 |
SA#86 |
SP-191159 |
0010 |
1 |
F |
Clean up for incosistence |
16.1.0 |
|
2019-12 |
SA#86 |
SP-191171 |
0011 |
1 |
B |
Add description for tenant information |
16.1.0 |
|
2019-12 |
SA#86 |
SP-191173 |
0013 |
1 |
A |
Fix inconsistencies in the usage of word instance |
16.1.0 |
|
2020-07 |
SA#88E |
SP-200497 |
0022 |
3 |
B |
Extend roles related to 5G networks and network slicing management |
16.2.0 |
|
2020-07 |
SA#88E |
SP-200485 |
0025 |
2 |
F |
Cleanup Network Slice related definitions in OAM space |
16.2.0 |
|
2020-07 |
SA#88E |
SP-200485 |
0027 |
1 |
F |
update slice NRM to align with refined slice definitions |
16.2.0 |
|
2020-09 |
SA#89e |
SP-200724 |
0028 |
1 |
F |
Replacement of instance of the term MF/managed function with network function |
16.3.0 |
|
2020-09 |
SA#89e |
SP-200724 |
0029 |
1 |
F |
Corrections |
16.3.0 |
|
2020-12 |
SA#90e |
SP-201050 |
0032 |
– |
F |
Add abbreviation |
16.4.0 |
|
2020-12 |
SA#90e |
SP-201053 |
0033 |
1 |
F |
Decouple communication service and network slice |
16.4.0 |
|
2020-12 |
SA#90e |
SP-201053 |
0034 |
1 |
F |
Move service profile definition from 28531 |
16.4.0 |
|
2020-12 |
SA#90e |
SP-201050 |
0035 |
– |
F |
Correction of missing Figure 4.1.7.1 Examples of network slice as NOP internals |
16.4.0 |
|
2020-12 |
SA#90e |
SP-201088 |
0036 |
– |
F |
Add the chapter of high level features |
16.4.0 |
|
2020-12 |
SA#90e |
SP-201046 |
0031 |
1 |
F |
Refine tenant information concept |
17.0.0 |
|
2021-03 |
SA#91e |
SP-210144 |
0044 |
– |
C |
Handling of slice input data |
17.1.0 |
|
2021-12 |
SA#94e |
SP-211463 |
0048 |
1 |
F |
Remove not used terms from abbreviations list |
17.2.0 |
|
2021-12 |
SA#94e |
SP-211464 |
0050 |
– |
A |
Correct tenant phrasing |
17.2.0 |
|
2021-12 |
SA#94e |
SP-211465 |
0051 |
1 |
B |
Add description for SBMA supporting manangement of 5G SA and NSA scenarios |
17.2.0 |
|
2022-09 |
SA#97e |
SP-220850 |
0053 |
1 |
F |
Clarify 3GPP management system capability requirement |
17.3.0 |