7 Management workflows for requirements for the management of the shared NG-RAN NE(s) in MOCN network sharing scenario
32.1303GPPConcepts and requirementsNetwork sharingRelease 17Telecommunication managementTS
7.1 Management of the shared NG-RAN NE(s) in MOCN network sharing scenario with the same cell Identity broadcast
The NG-RAN MOCN Network Sharing with same cell identity broadcast scenario is illustrated in Figure 4.1-2 and corresponding requirements is defined in clause 5.1.4. This clause describes the workflows for the management of the shared NG-RAN NE(s) in MOCN network sharing scenario with the same cell identity broadcast.
In this workflow, the radio access network (i.e. one or multiple shared NG-RAN NE(s)) is shared between two POPs (POP A identified by PLMN#1and POP B identified by PLMN#2). Both MnS consumer and MnS producer for the management of shared NG-RAN NE(s) belong to MOP.For the Req-MOCN_SameCellId_Cfg-CON-1:
MnS consumer determines the individual EP_NgC MOI and EP_NgU MOI (see the attributes of NgC and NgU in TS 28.541[X]) for each POP (POP A and POP B), and requests MnS producer to create and configure EP_NgC MOI and EP_NgU MOI for each POP.
MnS producer creates and configures the EP_NgC MOI and EP_NgU MOI for each POP based on the requests from MnS consumer. The EP_NgC MOI and EP_NgU MOI are name containe by same GNBCUCPFunction MOI and GNBCUUPFunction MOI which is shared for different POPs.
For the Req- MOCN_SameCellId_Cfg-CON-2:
MnS consumer determines the attribute "PLMNInfoList" in NRCellDU MOI and NRCellCU MOI (see the attribute definition in TS 28.541[X]), which includes the PLMN#1 and PLMN#2, and requests MnS producer to configure NRCellDU MOI and NRCellCU MOI with attribute "PLMNInfoList".
MnS producer configures the NG-RAN NE(s) (i.e. subtree of ManagedElement MOI) based on the requests from MnS consumer, including configuring the NRCellDU MOI and NRCellCU MOIwith attribute "PLMNInfoList" to include PLMN#1 and PLMN#2.
For the Req- MOCN_SameCellId_Per-CON-3:
MnS producer collects the individual measurements for POP A and POP B in PLMN granularity by utilizing PLMN granularity subcounter. For the concrete PLMN granularity measurements, see TS 28.552[9].
MnS producer sends the individual measurements for POP A and POP B in PLMN granularity to MnS consumer.
7.2 Management of the shared NG-RAN NE(s) in MOCN network sharing scenario with the multiple cell Identity broadcast
The NG-RAN MOCN Network Sharing with multiple cell identity broadcast scenario is illustrated in Figure 4.1-3 and corresponding requirements is defined in clause 5.1.5. This clause describes the workflows for the management of the shared NG-RAN NE(s) in MOCN network sharing scenario with the muliple cell identity broadcast.
In this workflow, the radio access network (i.e. one or multiple shared NG-RAN NE(s)) is shared between two POPs (POP A identified by PLMN#1and POP B identified by PLMN#2). Both MnS consumer and MnS producer for the management of shared NG-RAN NE(s) belong to MOP.
For the Req-MOCN-MultiCellId-Cfg-CON-1:
MnS consumer determines the individual EP_NgC MOI and EP_NgU MOI (see the attributes of NgC and NgU in TS 28.541[8]) for each POP (POP A and POP B), and requests MnS producer to create and configure EP_NgC MOI and EP_NgU MOI for each POP.
MnS producer creates and configures the EP_NgC MOI and EP_NgU MOI for each POP based on the requests from MnS consumer. The EP_NgC MOI and EP_NgU MOI are name containe by corresponding POP’s GNBCUCPFunction MOI and GNBCUUPFunction MOI.
For the Req-MOCN-MultiCellId-Cfg-CON-2
MnS consumer determines the individual OperatorDU MOI and NROperatorCellDU MOI (see the attributes of OperatorDU and NROperatorCellDU in TS 28.541[8]) for each POP (POP A and POP B), and requests MnS producer to create and configure OperatorDU MOI and NROperatorCellDU MOI for each POP.
MnS producer configures the NG-RAN NE(s) (i.e. subtree of ManagedElement) based on the requests from MnS consumer, including creates and configures OperatorDU and NROperatorCellDU MOI for each POP.
MnS consumer determines the individual NRCellCU MOI (see the attributes of NRCellCU in TS 28.541[8]) for each POP (POP A and POP B), and requests MnS producer to create and configure NRCellCU MOI for each POP.
MnS producer configures the NG-RAN NE(s) (i.e. subtree of ManagedElement) based on the requests from MnS consumer, including creates and configures NRCellCU MOI for each POP.
For the Req-MOCN-MultiCellId-Cfg-CON-3
MnS producer collects the individual measurements for POP A and POP B in PLMN granularity by utilizing PLMN granularity subcounter or associated with OperatorDU and NROperatorCellDU. For the concrete PLMN granularity measurements, see TS 28.552[9].
MnS producer sends the individual measurements for POP A and POP B in PLMN granularity to MnS consumer.
For the Req-MOCN-MultiCellId-Cfg-CON-4 and Req-MOCN-MultiCellId-Cfg-CON-5
MnS consumer determines the individual EP_F1C MOI and EP_F1U MOI (see corresponding attributes in TS 28.541[8]) for each POP (POP A and POP B), and requests MnS producer to create and configure these MOIs for each POP. In case of common F1 intertface configuration, the values of the EP_F1C MOI and EP_F1U MOI attributes (including localAddress and remoteAddress) contained by different POP’s OperatorDU MOI of the same GNBDUFunction MOI should be same.
MnS producer creates and configures the individual EP_F1C MOI and EP_F1U MOI for each POP based on the requests from MnS consumer. The EP_F1C MOI and EP_F1U MOI are name contained by corresponding POP’s OperatorDU and associated to it’s own GNBCUCPFunction MOI and GNBCUUPFunction MOI.
For the Req-MOCN-MultiCellId-Cfg-CON-6
MnS consumer determines the NRCellRelation MOI(s) (see corresponding attributes in TS 28.541[8]) for each POP (POP A and POP B), and requests MnS producer to create and configure NRCellRelation MOI(s) for each POP.
MnS producer configures the NG-RAN NE(s) (i.e. subtree of ManagedElement) based on the requests from MnS consumer, including creates and configures the individual NRCellRelation MOI for each POP.
Annex A (informative):
Network sharing agreement
Prior to any network sharing deployment, the MOP and the POPs have to agree on legal, financial, technical and operational aspects. Among operational aspects, the network sharing agreement captures the following (non-exhaustive list):
– Organizations involved (i.e. Operators) and their roles in the network sharing deployment.
– Exhaustive list of shared and unshared resources in the shared network.
– Rights attached to each role (e.g. rights to configure network resources, rights to receive alarms, etc.).
– Duties attached to each role (e.g. obligation for the MOP to provide POPs with monthly KPIs, etc.).
– Delegations (if any) given by any organization to another organization.
– Service Level Agreements (SLAs).
Annex B (informative):
Change history
|
Change history |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
2014-12 |
SA#66 |
SP-140795 |
Presented for approval |
1.2.0 |
2.0.0 |
||
|
2014-12 |
Version after approval |
2.0.0 |
12.0.0 |
||||
|
2016-01 |
– |
– |
– |
– |
Update to Rel-13 version (MCC) |
12.0.0 |
13.0.0 |
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2016-12 |
SA#74 |
SP-160856 |
0001 |
2 |
B |
Add use cases and requirements for Management of measurements for cross-operator accounting based on data volume and QoS |
14.0.0 |
|
2018-01 |
SA#78 |
SP-170964 |
0002 |
– |
F |
Correcting requirements tags |
14.1.0 |
|
2018-06 |
– |
– |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
|
2020-07 |
– |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
2021-03 |
SA#91e |
SP-210141 |
0003 |
1 |
B |
Update the scope and background of network sharing scenarios |
17.0.0 |
|
2021-03 |
SA#91e |
SP-210141 |
0006 |
1 |
B |
Update the business requirements to support NG-RAN sharing |
17.0.0 |
|
2021-03 |
SA#91e |
SP-210141 |
0009 |
1 |
B |
Update business requirements to applicable for SBMA |
17.0.0 |
|
2021-06 |
SA#92e |
SP-210415 |
0011 |
– |
B |
Add requirememts for management support for 5G MOCN network sharing scenario with same Cell Identity |
17.1.0 |
|
2021-06 |
SA#92e |
SP-210415 |
0012 |
1 |
B |
Add requirememts for management support for 5G MOCN network sharing scenario with multiple Cell Identity |
17.1.0 |
|
2021-06 |
SA#92e |
SP-210415 |
0013 |
1 |
B |
Add mixed NG-RAN sharing use case and requirements |
17.1.0 |
|
2021-09 |
SA#93e |
SP-210877 |
0014 |
2 |
B |
Add NG-RAN sharing individual management use case and requirements |
17.2.0 |
|
2021-12 |
SA#94e |
SP-211471 |
0015 |
– |
B |
Update RAN sharing scenarios to cover 5G RAN sharing |
17.3.0 |
|
2021-12 |
SA#94e |
SP-211471 |
0016 |
– |
B |
Update RAN sharing scenarios to cover 5G RAN sharing |
17.3.0 |
|
2022-03 |
SA#95e |
SP-220184 |
0017 |
– |
F |
Clean up on concept and business level requirements |
17.4.0 |
|
2022-03 |
SA#95e |
SP-220184 |
0018 |
– |
B |
Add missing use case and requirements for radio resources partitioning between POPs |
17.4.0 |
|
2022-03 |
SA#95e |
SP-220184 |
0019 |
1 |
B |
Solution description for the requirements for the management of the shared NG-RAN NE(s) in MOCN network sharing scenario |
17.4.0 |
|
2022-03 |
SA#95e |
SP-220184 |
0020 |
– |
B |
Add requirement about administrative management capability for operator specific cell |
17.4.0 |
|
2022-12 |
SA#98e |
SP-221168 |
0022 |
– |
F |
Rel-17 CR for TS32.130 delete redundant figure |
17.5.0 |