7.2.5 Solutions for generic MnS requirements
28.1003GPPLevels of autonomous networkManagement and orchestrationRelease 17TS
Table 7.2.5-1: Solutions for generic MnS requirements of autonomous network level for RAN NE deployment
|
Autonomous Network Level |
Requirements (Defined in Clause 7.1.4) |
Corresponding solutions |
|
Level 1 |
REQ-ANL-RanNeDeploy-Level_1-MnS-1 |
This is implemented by provisioning MnS defined in TS 28.532 [4] with 5G Network Resource model defined in TS 28.541 [5]. |
|
REQ-ANL-RanNeDeploy-Level_1-MnS-2 |
This is implemented by provisioning MnS defined in TS 28.532 [4] with 5G Network Resource model defined in TS 28.541 [5]. |
|
|
Level2 |
REQ-ANL-RanNeDeploy-Level_2-MnS-1 |
This can be implemented by provisioning MnS (e.g. createMOI) defined in TS 28.532 [4] to specify the network configuration data generation control information. |
|
Level3 |
REQ-ANL-RanNeDeploy-Level_3-MnS-1 |
This can be implemented by using generic provisioning MnS defined in TS 28.532 [4] to specify the network configuration data generation control information. |
|
REQ-ANL-RanNeDeploy-Level_3-MnS-2 |
This can be implemented by using generic provisioning MnS defined in TS 28.532 [4] to specify the commissioning test control information. |
|
|
REQ-ANL-RanNeDeploy-Level_3-MnS-3 |
This can be implemented by using generic provisioning MnS defined in TS 28.5326 [4] to specify the dialing test control information. |