7 Management services for SON
28.3133GPPManagement and orchestrationRelease 17Self-Organizing Networks (SON) for 5G networksTS
7.1 Management services for D-SON management
7.1.1 RACH Optimization (Random Access Optimisation)
7.1.1.1 MnS component type A
Table 7.1.1.1-1: RACH optimization type A
|
MnS Component Type A |
Note |
|
Operations and notifications defined in clause 11.1.1of TS 28.532 [3]: – createMOI operation – getMOIAttributes operation – modifyMOIAttributes operation – deleteMOI operation – notifyMOIAttributeValueChanges operation – notifyMOICreation – notifyMOIDeletion – notifyMOIChanges |
It is supported by Provisioning MnS for NF, as defined in 28.531 [11]. |
|
Operations defined in clause 11.3.1.1.1 in TS 28.532 [3] and clause 6.2.3 of TS 28.550 [12]: – notifyFileReady operation – reportStreamData operation |
It is supported by Performance Assurance MnS for NFs, as defined in 28.550 [12]. |
7.1.1.2 MnS Component Type B definition
7.1.1.2.1 Targets information
The targets of RACH optimization are shown in Table 7.1.2.1.1-1.
Table 7.1.1.1.2-1: RACH optimization targets
|
Targets |
Definition |
Legal Values |
|---|---|---|
|
UE access delay probability |
The probability distribution of UE access delay per cell. |
CDF of access delay |
|
Number of preambles sent probability |
The probability of the number of preambles sent per cell. |
CDF of access probability |
7.1.1.2.2 Control information
The parameter is used to control the RACH optimization function.
Table 7.1.1.2.2-1: RACH optimization control
|
Control parameter |
Definition |
Legal Values |
|---|---|---|
|
RACH optimization control |
This attribute allows authorized consumer to enable/disable the RACH optimization functionality. See attribute rachOptimizationControl in TS 28.541 [13]. |
Boolean On, off |
7.1.1.2.3 Parameters to be updated
Void.
7.1.1.3 MnS Component Type C definition
7.1.1.3.1 Performance measurements
Performance measurements related to the RACH optimization are captured in Table 7.1.1.3.1-1:
Table 7.1.1.3.1-1: RACH optimization related performance measurements
|
Performance measurements |
Description |
Related targets |
|
Distribution of RACH preambles sent |
Distribution of the number of preambles UEs sent to achieve synchronization per SSB, where the number of preambles sent corresponds to PREAMBLE_TRANSMISSION_COUNTER (see clause 5.1.1 in TS 38.321 [4]) in UE. |
UE access delay probability per SSB |
|
Distribution of UEs access delay per SSB |
Distribution of the time needed for UEs to successfully attach to the network per SSB. |
Number of preambles send per SSB probability |
7.1.2 MRO (Mobility Robustness Optimisation)
7.1.2.1 MnS component type A
Table 7.1.2.1-1: MRO type A
|
MnS Component Type A |
Note |
|
Operations and notifications defined in clause 11.1.1 of TS 28.532 [3]: createMOI operation – getMOIAttributes operation – modifyMOIAttributes operation – deleteMOI operation – notifyMOIAttributeValueChanges operation – notifyMOICreation – notifyMOIDeletion – notifyMOIChanges |
It is supported by Provisioning MnS for NF, as defined in TS 28.531 [11]. |
|
Operations defined in clause 11.3.1.1.1 in TS 28.532 [3] and clause 6.2.3 of TS 28.550 [12]: – notifyFileReady operation – reportStreamData operation |
It is supported by Performance Assurance MnS for NFs, as defined in TS 28.550 [12]. |
7.1.2.2 MnS Component Type B definition
7.1.2.2.1 Targets information
The targets of MRO are shown in the Table 7.1.2.2.1-1.
Table 7.1.2.2.1-1: MRO targets
|
Target Name |
Definition |
Legal Values |
|---|---|---|
|
Total handover failure rate |
(the number of failure events related to handover) / (the total number of handover events) |
[0..100] in unit percentage |
|
Total intra-RAT handover failure rate |
(the number of failure events related to intra-RAT handover) / (the total number of handover events) |
[0..100] in unit percentage |
|
Total inter-RAT handover failure rate |
(the number of failure events related to inter-RAT handover) / (the total number of handover events) |
[0..100] in unit percentage |
7.1.2.2.2 Control information
The parameter is used to control the MRO function.
Table 7.1.2.2.2-1: MRO control
|
Control parameter |
Definition |
Legal Values |
|---|---|---|
|
MRO function control |
This attribute allows the operator to enable/disable the MRO functionality. See attribute mroControl in TS 28.541 [13]. |
Boolean On, off |
7.1.2.2.3 Parameters to be updated
Table 7.1.2.2.3-1: Ranges of handover parameters
|
Control parameters |
Definition |
Legal Values |
|---|---|---|
|
Maximum deviation of Handover Trigger |
This parameter defines the maximum allowed deviation of the Handover Trigger from the default point of operation (see clause 15.5.2.5 in TS 38.300 [7] and clause 9.2.2.61 in TS 38.423 [17]). See attribute maximumDeviationHoTrigger in TS 28.541 [13]. The upper and lower bounds of this parameter are configured separately. |
[-20..20] in unit 0.5 dB |
|
Minimum time between Handover Trigger changes |
This parameter defines the minimum allowed time interval between two Handover Trigger change performed by MRO. This is used to control the stability and convergence of the algorithm (see clause 15.5.2.5 in TS 38.300 [7]). See attribute minimumTimeBetweenHoTriggerChange in TS 28.541 [13]. |
[0.. 604800] in unit Seconds |
|
Tstore_UE_cntxt |
The timer used for detection of too early HO, too late HO and HO to wrong cell. Corresponds to Tstore_UE_cntxt timer described in clause 15.5.2.5 in TS 38.300 [7]. See attribute tstoreUEcntxt in TS 28.541 [13]. |
[0..1023] in unit 100 milliseconds |
7.1.2.3 MnS Component Type C definition
7.1.2.3.1 Performance measurements
Performance measurements related MRO are captured in Table 7.1.2.3.1.-1:
Table 7.1.2.3.1-1. MRO related performance measurements
|
Performance measurements |
Description |
Related targets |
|---|---|---|
|
Number of handover events |
Includes all successful and unsuccessful handover events (see clause 5.1.1.6 in TS 28.552 [5]). |
Total handover failure rate |
|
Number of handover failures |
Includes unsuccessful handover events with failure causes (see clause 5.1.1.6 in TS 28.552 [5]). |
Total handover failure rate |
|
Number of intra-RAT handover events |
Includes all successful and unsuccessful intra-RAT handover events (see clauses 5.1.1.6.1 and 5.1.1.6.2 in TS 28.552 [5]). |
Total intra-RAT handover failure rate |
|
Number of intra-RAT handover failures |
Includes unsuccessful intra-RAT handover events with failure causes (see clauses 5.1.1.6.1 and 5.1.1.6.2 in TS 28.552 [5]). |
Total intra-RAT handover failure rate |
|
Number of inter-RAT handover events |
Includes all successful and unsuccessful inter-RAT handover events (see clause 5.1.1.6.3 in TS 28.552 [5]). |
Total inter-RAT handover failure rate |
|
Number of inter-RAT handover failures |
Includes unsuccessful inter-RAT handover events with failure causes (see clause 5.1.1.6.3 in TS 28.552 [5]). |
Total inter-RAT handover failure rate |
|
Number of intra-RAT too late handover failures |
Detected when an RLF occurs after the UE has stayed for a long period of time in the source cell; the UE attempts to re-establish the radio link connection in the target cell (see clause 5.1.1.25.1 in TS 28.552 [5]). |
|
|
Number of intra-RAT too early handover failures |
Detected when an RLF occurs shortly after a successful handover from a source cell to a target cell or a handover failure occurs during the handover procedure; the UE attempts to re-establish the radio link connection in the source cell (see clause 5.1.1.25.1 in TS 28.552 [5]). |
|
|
Number of intra-RAT handover failures to wrong cell |
Detected when an RLF occurs shortly after a successful handover from a source cell to a target cell or a handover failure occurs during the handover procedure; the UE attempts to re-establish the radio link connection in a cell other than the source cell or the target cell (see clause 5.1.1.25.1 in TS 28.552 [5]). |
|
|
Number of intra-RAT too late handover failures per source beam |
Detected when an RLF occurs after the UE has stayed for a long period of time in the source cell; the UE attempts to re-establish the radio link connection in the target cell (see clause 5.1.1.25.5 in TS 28.552 [5]). |
|
|
Number of intra-RAT too early handover failures per source beam |
Detected when an RLF occurs shortly after a successful handover from a source cell to a target cell or a handover failure occurs during the handover procedure; the UE attempts to re-establish the radio link connection in the source cell (see clause 5.1.1.25.5 in TS 28.552 [5]). |
|
|
Number of intra-RAT handover failures to wrong cell per source beam |
Detected when an RLF occurs shortly after a successful handover from a source cell to a target cell or a handover failure occurs during the handover procedure; the UE attempts to re-establish the radio link connection in a cell other than the source cell or the target cell (see clause 5.1.1.25.5 in TS 28.552 [5]). |
|
|
Number of inter-RAT too late handover failures |
Detected when an RLF occurs after the UE has stayed in anNG-RAN cell for a long period of time; the UE attempts to reconnect to a cell belonging to an E-UTRAN node (see clause 5.1.1.25.2 in TS 28.552 [5]). |
|
|
Number of inter-RAT too early handover failures |
Detected when an RLF occurs shortly after a successful handover from an E-UTRAN cell to a target cell in a NG-RAN node (see clause 5.1.1.25.2 in TS 28.552 [5]). |
|
|
Number of unnecessary handover to another RAT |
Detected when a UE is handed over from NG-RAN to other system (e.g. UTRAN) even though quality of the NG-RAN coverage was sufficient for the service used by the UE (see clause 5.1.1.25.3 in TS 28.552 [5]). |
|
|
Number of inter-RAT handover ping pong |
Detected when an UE is handed over from a cell in a source system (e.g. NG-RAN) to a cell in a target system different from the source system (e.g. E-UTRAN), then within a predefined limited time the UE is handed over back to a cell in the source system, while the coverage of the source system was sufficient for the service used by the UE (see clause 5.1.1.25.4 in TS 28.552 [5]). |
7.1.3 PCI configuration
7.1.3.1 MnS component type A
Table 7.1.3.1-1: PCI type A
|
MnS Component Type A |
Note |
|
Operations and notifications defined in clause 11.1.1 of TS 28.532 [3]: – createMOI operation – getMOIAttributes operation – modifyMOIAttributes operation – deleteMOI operation – notifyMOIAttributeValueChanges operation – notifyMOICreation – notifyMOIDeletion – notifyMOIChanges |
It is supported by Provisioning MnS for NF, as defined in 28.531 [11]. |
7.1.3.2 MnS Component Type B definition
7.1.3.2.1 Control information
The parameter is used to control the D-SON PCI configuration function.
Table 7.1.3.2.1-1: PCI contol
|
Control parameter |
Definition |
Legal Values |
|---|---|---|
|
PCI configuration control |
This attribute allows authorized consumer to enable/disable the D-SON PCI configuration functionality. See attribute pciConfigurationControl in TS 28.541 [13]. |
enable, disable |
7.1.3.2.2 Parameters to be updated
The table below lists the parameter related to the D-SON PCI configuration function.
Table 7.1.3.2.2-1: PCI update
|
Parameters |
Definition |
Legal Values |
|---|---|---|
|
PCI list |
The list of PCI values to be used by D-SON PCI configuration function to assign the PCI for NR cells. (See attribute pciList in TS 28.541 [13]). |
List of integers |
7.1.3.3 MnS Component Type C definition
7.1.3.3.1 Notification information
The table below lists the notifications related to D-SON PCI configuration.
Table 7.1.3.3-1: PCI notifications
|
Notifications |
Description |
Note |
|
PCI change notification |
When the PCI configuration function changes the PCI of a cell, this change is notified using a notifyMOIAttributeValueChanges notification. See attribute nRPCI in TS 28.541 [13]. |
7.1.3.3.2 Alarm notification information
The table below lists the alarm notifications related to D-SON PCI configuration.
Table 7.1.3.3.2-1: PCI alarm notifications
|
Alarm notifications |
Description |
Note |
|
PCI configuration function failure |
This alarm notification indicates that the PCI configuration function has failed to resolve PCI collision or PCI confusion problems. |
7.1.4 ANR management
This management service is used for management of ANR, and ANR is specified in TS 38.300 [7], clauses 15.3.3.
Stage 2 for ANR management is located in TS 28.541 [13], clauses 4.3.2.2, 4.3.2.3, 4.3.32.2 and 4.3.32.3.
Stage 3 for ANR management is located in TS 28.541 [13], clauses C.4.3, D.4.3, and E.5.
7.1.5 LBO (Load Balancing Optimisation)
7.1.5.1 MnS component type A
Table 7.1.5.1-1: D-LBO type A
|
MnS Component Type A |
Note |
|
Operations and notifications defined in clause 5 of TS 28.532 [3]: – createMOI operation – getMOIAttributes operation – modifyMOIAttributes operation – deleteMOI operation – notifyMOIAttributeValueChanges – notifyMOICreation – notifyMOIDeletion – notifyMOIChanges |
It is supported by Provisioning MnS for NF, as defined in TS 28.531 [11]. |
|
Operations defined in clause 11.3.1.1.1 in TS 28.532 [3] and clause 6.2.3 of TS 28.550 [12]: – establishStreamingConnection operation – notifyFileReady operation – reportStreamData operation |
It is supported by Performance Assurance MnS for NFs, as defined in TS 28.550 [12]. |
7.1.5.2 MnS Component Type B definition
7.1.5.2.1 Control information
The parameter is used to control the LBO function.
Table 7.1.5.2.1-1: D-LBO control information
|
Control parameter |
Definition |
Legal Values |
|---|---|---|
|
D-LBO function control |
This attribute allows the operator to enable/disable the LBO functionality. |
Boolean On, off |
7.1.5.2.2 Parameters to be updated
Table 7.1.5.2.2-1: Ranges of HO and cell selection parameters
|
Control parameters |
Definition |
Legal Values |
|---|---|---|
|
Maximum deviation of Handover Trigger |
This parameter defines the maximum allowed absolute deviation of the Handover Trigger, from the default point of operation (see clause 15.5.1.4 in TS 38.300 [7] and clause 9.2.2.61 in TS 38.423 [17]). See attribute maximumDeviationHoTrigger in TS 28.541 [13]. |
[-20 .. 20] in unit 0.5 dB |
|
Minimum time between Handover Trigger changes |
This parameter defines the minimum allowed time interval between two Handover Trigger change performed by MRO. This is used to control the stability and convergence of the algorithm (see clause 15.5.1.4 in TS 38.300 [7]). See attribute minimumTimeBetweenHoTriggerChange in TS 28.541 [13]. |
[0 .. 604800] in unit Seconds |
7.1.5.3 MnS Component Type C definition
7.1.5.3.1 Performance measurements
Performance measurements related LBO are captured in Table 7.1.x.3.1-1:
Table 7.1.5.3.1-1. D-LBO related performance measurements
|
Performance measurements |
Description |
Note |
|---|---|---|
|
DL Total PRB Usage |
This measurement provides the total usage (in percentage) of physical resource blocks (PRBs) on the downlink (see clause 5.1.1.2.1 in TS 28.552 [5]). |
|
|
UL Total PRB Usage |
This measurement provides the total usage (in percentage) of physical resource blocks (PRBs) on the uplink (see clause 5.1.1.2.2 in TS 28.552 [5]). |
|
|
Distribution of DL Total PRB Usage |
This distribution measurement is to monitor when a cell may experience overload situation in the downlink (see clause 5.1.1.2.3 in TS 28.552 [5]). |
|
|
Distribution of UL Total PRB Usage |
This distribution measurement is to monitor when a cell may experience overload situation in the uplink (see clause 5.1.1.2.4 in TS 28.552 [5]). |
|
|
DL PRB used for data traffic |
This measurement provides the number of physical resource blocks (PRBs) in average used in downlink for data traffic (see clause 5.1.1.2.5 in TS 28.552 [5]). |
|
|
UL PRB used for data traffic |
This measurement provides the number of physical resource blocks (PRBs) in average used in uplink for data traffic (see clause 5.1.1.2.7 in TS 28.552 [5]). |
|
|
Mean number of RRC Connections |
This measurement provides the mean number of users in RRC connected mode during the granularity period (see clause 5.1.1.4.1 in TS 28.552 [5]). |
|
|
Max number of RRC Connections |
This measurement provides the maximum number of users in RRC connected mode during the granularity period (see clause 5.1.1.4.2 in TS 28.552 [5]). |
|
|
Mean number of stored inactive RRC Connections |
This measurement provides the mean number of users in RRC inactive mode during each granularity period (see clause 5.1.1.4.3 in TS 28.552 [5]). |
|
|
Max number of stored inactive RRC Connections |
This measurement provides the maximum number of users in RRC inactive mode during each granularity period (see clause 5.1.1.4.3 in TS 28.552 [5]). |
7.1.6 MRO for Conditional Handover (CHO)
7.1.6.1 MnS component type A
MRO for CHO re-uses the component A for MRO, see clause 7.1.2.1.
7.1.6.2 MnS Component Type B definition
7.1.6.2.1 Control information
These parameters are used to control the CHO function.
Table 7.1.6.2.1-1: MRO fro CHO control
|
Control parameter |
Definition |
Legal Values |
|---|---|---|
|
CHO function control |
This attribute allows the operator to enable/disable the CHO functionality. See attribute choControl in TS 28.541 [13]. |
Boolean On, off |
7.1.6.2.2 Parameters to be updated
MRO for CHO re-uses the same parameters to be updated as MRO, see clause 7.1.2.2.3.
7.1.6.3 MnS Component Type C definition
7.1.6.3.1 Performance measurements
Performance measurements related to MRO for CHO are captured in Table 7.1.6.3.1.-1:
Table 7.1.6.3.1-1. MRO for CHO related performance measurements
|
Performance measurements |
Description |
Note |
|---|---|---|
|
Number of requested conditional handover preparations |
Counts the number of successful and unsuccessful inter-gNB conditional handover preparations sent (see TS 28.552 clause 5.1.1.6.x.1) |
|
|
Number of successful conditional handover preparations |
Counts the number of unsuccessful inter-gNB conditional handover preparations sent (see TS 28.552 clause 5.1.1.6.x.2) |
|
|
Number of failed conditional handover preparations |
Counts the number of unsuccessful inter-gNB conditional handover preparations sent (see TS 28.552 clause 5.1.1.6.x.3) |
|
|
Number of requested conditional handover resource allocations |
Counts the number of successful and unsuccessful inter-gNB conditional handover preparations (see TS 28.552 clause 5.1.1.6.x.4) |
|
|
Number of successful conditional handover resource allocations |
Counts the number of successful inter-gNB conditional handover preparations (see TS 28.552 clause 5.1.1.6.x.5) |
|
|
Number of failed conditional handover resource allocations |
Counts the number of unsuccessful inter-gNB conditional handover preparations (see TS 28.552 clause 5.1.1.6.x.6) |
|
|
Number of configured conditional handover candidates |
Counts the number of outgoing inter-gNB conditional handover candidates requested (see TS 28.552 clause 5.1.1.6.x.7) |
|
|
Number of UEs configured with conditional handover. |
Counts the number of UEs that has been configured with inter-gNB conditional handover (see TS 28.552 clause 5.1.1.6.x.8) |
|
|
Number of successful conditional handover executions |
Counts the number of successful inter-gNB conditional handover executions received (see TS 28.552 clause 5.1.1.6.x.9) |
|
|
Number of failed conditional handover executions |
Counts the the number of failed inter-gNB conditional handover executions received (see TS 28.552 clause 5.1.1.6.x.10) |
|
|
Mean Time of requested conditional handover executions |
Counts the mean time of inter-gNB conditional handover executions (see TS 28.552 clause 5.1.1.6.x.11) |
|
|
Max Time of requested conditional handover executions |
Counts the max time of inter-gNB conditional handover executions (see TS 28.552 clause 5.1.1.6.x.12) |
|
|
Number of configured conditional handover candidates |
Counts the number of outgoing intra-gNB conditional handover candidates requested (see TS 28.552 clause 5.1.1.6.y.1) |
|
|
Number of UEs configured with conditional handover |
Countes the the number of UEs that has been configured with conditional handover (see TS 28.552 clause 5.1.1.6.y.2) |
|
|
Number of successful conditional handover executions |
Counts the number of successful intra-gNB conditional handover executions received (see TS 28.552 clause 5.1.1.6.y.3) |
|
|
Number of requested conditional handover preparations |
Counts the number of outgoing intra-gNB conditional handover preparations requested, for a split gNB deployment (see TS 28.552 clause 5.1.3.7.1.a) |
|
|
Number of successful conditional handover preparations |
Countes the number of successful intra-gNB conditional handover preparations, for a split gNB deployment (see TS 28.552 clause 5.1.3.7.1.b) |
7.1.7 MRO for DAPS handover
7.1.7.1 MnS component type A
MRO for DAPS handover re-uses the component A for MRO, see clause 7.1.2.1.
7.1.7.2 MnS Component Type B definition
7.1.7.2.1 Control information
The parameter is used to control the DAPS handover function.
Table 7.1.7.2.1-1: MRO for DAPS handover control
|
Control parameter |
Definition |
Legal Values |
|---|---|---|
|
DAPS HO function control |
This attribute allows the operator to enable/disable the DAPS HO functionality. See attribute dapsHoControl in TS 28.541 [13]. |
Boolean On, off |
7.1.7.2.2 Parameters to be updated
MRO for DAPS handover re-uses the same parameters to be updated as MRO, see clause 7.1.2.2.3.
7.1.7.3 MnS Component Type C definition
7.1.7.3.1 Performance measurements
Performance measurements related to MRO for DAPS handover are captured in Table 7.1.7.3.1.-1:
Table 7.1.7.3.1-1. MRO for DAPS handover related performance measurements
|
Performance measurements |
Description |
Note |
|---|---|---|
|
Number of requested DAPS handover preparations |
Counts the number of successful and unsuccessful inter-gNB DAPS handover preparations sent (see TS 28.552 clause 5.1.1.6.x.1) |
|
|
Number of successful DAPS handover preparations |
Counts the number of unsuccessful inter-gNB DAPS handover preparations sent (see TS 28.552 clause 5.1.1.6.x.2) |
|
|
Number of failed DAPS handover preparations |
Counts the number of unsuccessful inter-gNB DAPS handover preparations sent (see TS 28.552 clause 5.1.1.6.x.3) |
|
|
Number of requested DAPS handover resource allocations |
Counts the number of successful and unsuccessful inter-gNB DAPS handover preparations (see TS 28.552 clause 5.1.1.6.x.4) |
|
|
Number of successful DAPS handover resource allocations |
Counts the number of successful inter-gNB DAPS handover preparations (see TS 28.552 clause 5.1.1.6.x.5) |
|
|
Number of failed DAPS handover resource allocations |
Counts the number of unsuccessful inter-gNB DAPS handover preparations (see TS 28.552 clause 5.1.1.6.x.6) |
|
|
Number of requested DAPS handover executions |
Counts the number of outgoing inter-gNB DAPS handover candidates requested (see TS 28.552 clause 5.1.1.6.x.7) |
|
|
Number of successful DAPS handover executions |
Counts the number of successful inter-gNB DAPS handover executions received (see TS 28.552 clause 5.1.1.6.x.8) |
|
|
Number of failed DAPS handover executions |
Counts the the number of failed inter-gNB DAPS handover executions received (see TS 28.552 clause 5.1.1.6.x.9) |
|
|
Number of DAPS handover requested |
Counts the number of outgoing intra-gNB DAPS handovers requested (see TS 28.552 clause 5.1.1.6.y.1) |
|
|
Number of successful DAPS handovers |
Counts the number of successful intra-gNB DAPS handovers (see TS 28.552 clause 5.1.1.6.y.2) |
|
|
Number of requested DAPS handover preparations |
Counts the number of outgoing intra-gNB DAPS handover preparations requested, for a split gNB deployment (see TS 28.552 clause 5.1.3.7.1.a) |
|
|
Number of successful DAPS handover preparations |
Countes the number of successful intra-gNB DAPS handover preparations, for a split gNB deployment (see TS 28.552 clause 5.1.3.7.1.b) |
7.2 Management services for C-SON
7.2.1 PCI configuration
7.2.1.1 MnS component type A
Table 7.2.1.1-1: PCI type A
|
MnS Component Type A |
Note |
|
Operations and notifications defined in clause 11.1.1 of TS 28.532 [3]: – createMOI operation – getMOIAttributes operation — modifyMOIAttributes operation – – deleteMOI operation – – notifyMOIAttributeValueChanges operation – notifyMOICreation – notifyMOIDeletion – notifyMOIChanges |
It is supported by Provisioning MnS for NF, as defined in 28.531 [11]. |
|
Operations and notifications defined in clause 11.5.1 of TS 28.532 [3]: – establishStreamingConnection operation – terminateStreamingConnection operation – reportStreamData operation – addStream operation – deleteStream operation – getConnectionInfo operation – getStreamInfo operation |
|
|
Operations defined in clauses 11.3.1.1.1 and 11.6.1 in TS 28.532 [3] and clause 6.2.3 of TS 28.550 [12]: notifyFileReady operation – reportStreamData operation – notifyFilePreparationError notification – subscribe operation – unsubscribe operation – istAvailableFiles operation |
It is supported by Performance Assurance MnS for NFs, as defined in 28.550 [12]. |
7.2.1.2 MnS Component Type B definition
7.2.1.2.1 Control information
The parameter is used to control the C-SON PCI configuration function.
Table 7.2.1.2.1-1: PCI control
|
Control parameter |
Definition |
Legal Values |
|---|---|---|
|
PCI configuration control |
This attribute allows authorized consumer to enable/disable the C-SON PCI configuration functionality. |
disable, enable |
|
PCI list |
The list of PCI values to be used by domain centralized SON PCI configuration function to assign the PCI for NR cells. (See attribute cSonPciList in TS 28.541 [13]). |
Integer |
7.2.1.2.2 Parameters to be updated
The table below lists the parameter related to the C-SON PCI configuration function.
Table 7.2.1.2.2-1: PCI update
|
Updated parameters |
Definition |
Legal Values |
|---|---|---|
|
NR PCI |
This parameter contains the PCI of the NR cell. |
Integer |
7.2.1.3 MnS Component Type C definition
7.2.1.3.1 Notifications information
The table below lists the notifications related to PCI configuration are generated from the NR cells.
Table 7.2.1.3.1-1: PCI notification
|
Notification information |
Description |
Note |
|
PCI collision notification |
The collision notification is used to indicate two neighbouring cells are using the same PCIs. |
|
|
PCI Confusion notification |
The confusion notification is used to indicate that a serving cell has 2 neighbouring cells that are using the same PCI value. |
7.2.1.3.2 Performance measurements
Performance measurements related to the PCI configuration are collected from the NR cells.
Table 7.2.1.3.2-1. PCI related performance measurements
|
Performance measurements |
Description |
Note |
|
PCI of candidate cellsExcessive Radio Link Failure |
The measurement contains cumulative counter with subcounters that is identified by the PCI value(s) of the candidate cells, and is derived from MeasResultListNR (see clause 6.3.2 in TS 38.331 [9]) where it contains PCI in PhysCellId, and RSRP/RSRQ in MeasQuantityResults of candidate cells. It is generated when the RSRP received from the candidate cells exceeds certain thresholds. The measurements can be used to discover cells with excessive Radio Link Failures (see TS 28.552 [5] clauses 5.1.1.6.1.8, 5.1.1.6.1.9, 5.1.1.6.2.1 and 5.1.1.6.2.2) |
7.2.1.3.3 Trace Reporting
Trace information related to the PCI configuration are collected from NR cells.
|
Trace Report |
Description |
Note |
|
RLF messages |
Radio Link Failure messages are generated by UEs experiencing Radio Link Failures, which may be caused by a PCI collision or a PCI confusion (see TS 32.423 [18] clause 4.30 and TS 38.423 [19] clause 8.4.7) |
7.2.2 RRM resources optimization for network slice instance(s)
7.2.2.1 MnS component type A
Table 7.2.2.1-1: RRM resources optimization type A
|
MnS Component Type A |
Note |
|
Operations and notifications defined in clause 5 of TS 28.532 [3]: – createMOI operation – getMOIAttributes operation – modifyMOIAttributes operation – deleteMOI operation – notifyMOIAttributeValueChanges operation – notifyMOICreation – notifyMOIDeletion – notifyMOIChanges |
It is supported by Provisioning MnS for NF, as defined in TS 28.531 [11]. |
|
Operations defined in clause 11.3.1.1.1 in TS 28.532 [3] and clause 6.2.3 of TS 28.550 [12]: – notifyFileReady operation – reportStreamData operation |
It is supported by Performance Assurance MnS for NFs, as defined in TS 28.550 [12]. |
7.2.2.2 MnS Component Type B definition
7.2.2.2.1 Parameters to be updated
Table 7.2.2.2.1-1 defines the RRM related parameters to be updated by C-SON function.
Table 7.2.x.2.1-1: RRM related parameters
|
Control parameters |
Definition |
Legal Values |
|---|---|---|
|
Maximum RRM policy ratio |
This parameter specifies the maximum percentage of RRM resources used by the network slice instance(s). See attribute rRMPolicyMaxRatio in TS 28.541 [13]. |
0..100 |
|
Minimum RRM policy ratio |
This parameter specifies the minimum percentage of RRM resources used by the network slice instance(s). See attribute rRMPolicyMinRatio in TS 28.541 [13]. |
0..100 |
|
Dedicated RRM policy ratio |
This parameter specifies the maximum percentage of RRM resources that are dedicated to the network slice instance(s). See attribute rRMPolicyDedicatedRatio in TS 28.541 [13]. |
0..100 |
7.2.2.3 MnS Component Type C definition
7.2.2.3.1 Performance measurements
RRM related performance measurements are captured in Table 7.2.2.3.1-1:
Table 7.2.2.3.1-1. RRM related performance measurements
|
Performance measurements |
Description |
Note |
|---|---|---|
|
Mean DL PRB used for data traffic |
Provides the mean number of PRBs used in downlink for data traffic in the NRCellDU, with subcounters per sNSSAI (see clause 5.1.1.2.5 in TS 28.552 [5]). |
|
|
Peak DL PRB used for data traffic |
Provides the peak number of PRBs used in downlink for data traffic in the NRCellDU, with subcounters per sNSSAI (see clause 5.1.1.2.9 in TS 28.552 [5]).. |
|
|
Mean UL PRB used for data traffic |
Provides the mean number of PRBs used in uplink for data traffic in the NRCellDU, with subcounters per sNSSAI (see clause 5.1.1.2.7 in TS 28.552 [5]). |
|
|
Peak UL PRB used for data traffic |
Provides the peak number of PRBs used in uplink for data traffic in the NRCellDU, with subcounters per sNSSAI (see clause 5.1.1.2.10 in TS 28.552 [5]).. |
|
|
Average DL UE throughput in gNB |
Provides the average UE throughput in downlink in the NRCellDU, with subcounters per sNSSAI (see clause 5.1.1.3.1 in TS 28.552 [5]). |
|
|
Distribution of DL UE throughput in gNB |
Provides the distribution of the UE throughput in downlink in the NRCellDU, with subcounters per sNSSAI (see clause 5.1.1.3.2 in TS 28.552 [5]). |
|
|
Average UL UE throughput in gNB |
Provides the average UE throughput in uplink in the NRCellDU, with subcounters per sNSSAI (see clause 5.1.1.3.3 in TS 28.552 [5]). |
|
|
Distribution of UL UE throughput in gNB |
Provides the average UE throughput in uplink in the NRCellDU, with subcounters per sNSSAI (see clause 5.1.1.3.4 in TS 28.552 [5]). |
|
|
Mean number of Active UEs in the DL per cell |
Provides the mean number of active UEs in downlink in an NRCellDU, with subcounters per sNSSAI (see clause 5.1.1.23.1 in TS 28.552 [5]). |
|
|
Maximum number of Active UEs in the DL per cell |
Provides the maximum number of active UEs in downlink in an NRCellDU, with subcounters per sNSSAI (see clause 5.1.1.23.2 in TS 28.552 [5]). |
|
|
Mean number of Active UEs in the UL per cell |
Provides the mean number of active UEs in uplink in an NRCellDU, with subcounters per sNSSAI (see clause 5.1.1.23.3 in TS 28.552 [5]). |
|
|
Maximum number of Active UEs in the UL per cell |
Provides the maximum number of active UEs in uplink in an NRCellDU, with subcounters per sNSSAI (see clause 5.1.1.23.4 in TS 28.552 [5]). |
|
|
Mean number of DRBs being allocated |
Provides the mean number of DRBs being allocated in the PDU sessions in the NRCellCU, with subcounters per sNSSAI (see clause 5.1.1.10.9 in TS 28.552 [5]). |
|
|
Peak number of DRBs being allocated |
Provides the peak number of DRBs being allocated in the PDU sessions in the NRCellCU, with subcounters per sNSSAI (see clause 5.1.1.10.10 in TS 28.552 [5]).. |
|
|
Peak number of PDU Sessions being allocated |
Provides the peak number of PDU Sessions being allocated in the NRCellCU, with subcounters per sNSSAI (see clause 5.1.1.5.4 in TS 28.552 [5]). |
|
|
Peak number of PDU Sessions being allocated |
Provides the peak number of PDU Sessions being allocated in the NRCellCU, with subcounters per sNSSAI(see clause 5.1.1.5.5 in TS 28.552 [5]). |
|
|
Mean number of RRC connections |
Provides the mean number of RRC connections in the NRCellCU, with subcounters per sNSSAI (see clause 5.1.1.4.1 in TS 28.552 [5]). |
|
|
Maximum number of RRC connections |
Provides the maximum number of RRC connections in the NRCellCU, with subcounters per sNSSAI (see clause 5.1.1.4.2 in TS 28.552 [5]). |
7.2.3 Centralized Capacity and Coverage Optimization
7.2.3.1 MnS component type A
Table 7.2.x.1-1: CCO type A
|
MnS Component Type A |
Note |
|
Operations and notifications defined in clause 5 of TS 28.532 [3]: – createMOI operation – getMOIAttributes operation – modifyMOIAttributes operation – deleteMOI operation – notifyMOIAttributeValueChanges operation – notifyMOICreation – notifyMOIDeletion – notifyMOIChanges |
It is supported by Provisioning MnS for NF, as defined in TS 28.531 [11]. |
|
Operations defined in clause 11.3.1.1.1 in TS 28.532 [3] and clause 6.2.3 of TS 28.550 [12]: – notifyFileReady operation – reportStreamData operation |
It is supported by Performance Assurance MnS for NFs, as defined in TS 28.550 [12]. |
7.2.3.2 MnS Component Type B definition
7.2.3.2.1 Parameters to be updated
Table 7.2.3.2.1-1 defines the CCO control parameters to be updated by C-SON function.
Table 7.2.3.2.1-1: CCO control parameters
|
Control parameters |
Definition |
Note |
|---|---|---|
|
Configured max Tx power |
Represents the maximum transmission power in milliwatts (mW) at the antenna port for all downlink channels, used simultaneously in a cell, added together. See attribute configuredMaxTxPower in TS 28.541 [13]. |
|
|
Configured Max Tx EIRP |
Represents the maximum emitted isotroptic radiated power (EIRP) in dBm for all downlink channels, used simultaneously in a cell, added together. See attribute configuredMaxTxEIRP in TS 28.541 [13]. |
|
|
Coverage shape |
Identifies the sector carrier coverage shape described by the envelope of the contained SSB beams. See attribute coverageShape in TS 28.541 [13]. |
|
|
Digital tilt |
Represents the vertical pointing direction of the antenna relative to the antenna bore sight, representing the total non-mechanical vertical tilt of the selected coverageShape. See attribute digitalTilt in TS 28.541 [13]. |
|
|
Digital azimuth |
Represents the horizontal pointing direction of the antenna relative to the antenna bore sight, representing the total non-mechanical horizontal pan of the selected coverageShape. See attribute digitalAzimuth in TS 28.541 [13]. |
7.2.3.2.2 Control information
The parameter is used to control the C-SON CCO function.
Table 7.2.3.2.2-1: CCO control
|
Control parameter |
Definition |
Note |
|---|---|---|
|
CCO switch |
This attribute allows authorized consumer to enable/disable the CCO functionality. See attribute cCOControl in TS 28.541 [13]. |
This parameter is used when domain centralized SON CCO is supported. |
|
CCO policy |
It indicates the range of the parameters which can be adjusted to optimize radio coverage. See attributes of the abstract class CCOParameters in TS 28.541 [13]. |
This parameter is used when domain centralized SON CCO is supported. |
7.2.3.3 MnS Component Type C definition
7.2.3.3.1 Performance measurements
CCO related performance measurements are captured in Table 7.2.x.3.1-1:
Table 7.2.3.3.1-1. CCO related performance measurements
|
Performance measurements |
Description |
Note |
|---|---|---|
|
Distribution of SS-RSRP per SSB |
Provides the distribution of SS_RSRP per SSB (see clause 5.1.1.22.1 in TS 28.552 [5]). |
|
|
Distribution of SS-RSRQ |
Provides the distribution of SS_RSRQ (see clause 5.1.1.31.1 in TS 28.552 [5]). |
|
|
Distribution of the number of active UE per SSB |
Provides the distribution of the number of active UE per SSB. |
|
|
Number of requested handover executions |
Provides the number of requested handover executions (see clause 5.1.1.6.1.7 in TS 28.552 [5]). |
|
|
Number of failed handover executions |
Provides the number of failed handover executions (see clause 5.1.1.6.1.9 in TS 28.552 [5]). |
|
|
Distribution of DL Total PRB Usage |
Provides the distribution of samples with total usage (in percentage) of PRBs on the downlink in different ranges (see clause 5.1.1.2.3 in TS 28.552 [5]). |
|
|
Distribution of UL Total PRB Usage |
Provides the distribution of samples with total usage (in percentage) of PRBs on the uplink in different ranges (see clause 5.1.1.2.4 in TS 28.552 [5]). |
|
|
DL PRB used for data traffic |
Provides the number of PRBs in average used in downlink for data traffic (see clause 5.1.1.2.5 in TS 28.552 [5]). |
|
|
DL total available PRB |
provides the total number of PRBs in average available downlink (see clause 5.1.1.2.6 in TS 28.552 [5]). |
|
|
UL PRB used for data traffic |
Provides the number of PRBs in average used in uplink for data traffic (see clause 5.1.1.2.7 in TS 28.552 [5]). |
|
|
UL total available PRB |
Provides the total number of PRBs in average available uplink (see clause 5.1.1.2.8 in TS 28.552 [5]). |
|
|
Average DL UE throughput in gNB |
Provides the average UE throughput in downlink (see clause 5.1.1.3.1 in TS 28.552 [5]). |
|
|
Distribution of DL UE throughput in gNB |
Provides the distribution of the UE throughput in downlink (see clause 5.1.1.3.1 in TS 28.552 [5]). |
|
|
Average UL UE throughput in gNB |
Provides the average UE throughput in uplink (see clause 5.1.1.3.3 in TS 28.552 [5]). |
|
|
Distribution of UL UE throughput in gNB |
Provides the distribution of the UE throughput in uplink (see clause 5.1.1.3.4 in TS 28.552 [5]). |
|
|
Mean number of RRC Connections |
Provides the mean number of users in RRC connected mode (see clause 5.1.1.4.1 in TS 28.552 [5]). |
|
|
Max number of RRC Connections |
Provides the maximum number of users in RRC connected mode (see clause 5.1.1.4.2 in TS 28.552 [5]). |
|
|
Number of PDU Sessions requested to setup |
Provides the number of PDU Sessions by the gNB (see clause 5.1.1.5.1 in TS 28.552 [5]). |
|
|
Number of PDU Sessions successfully setup |
Provides the number of PDU Sessions successfully setup by the gNB from AMF (see clause 5.1.1.5.2 in TS 28.552 [5]). |
|
|
Number of PDU Sessions failed to setup |
Provides the number of PDU Sessions failed to setup by the gNB (see clause 5.1.1.5.3 in TS 28.552 [5]). |
7.2.3.3.2 MDT and Trace reports
CCO related MDT and trace reports are captured in Table 7.2.3.3.1-2:
Table 7.2.3.3.1-2. CCO related MDT and trace reports
|
Performance measurements |
Description |
Note |
|---|---|---|
|
MDT reports |
Provides RSRPs of the serving cell and neighbour cells, and UE location (see TS 32.422 [20]). |
|
|
RLF reports |
Provides RSRPs of the of the last serving cell and neighbour cells, and UE location (see TS 32.422 [20]). |
|
|
RCEF reports |
Provides RSRPs of the NR cell where the RRC connection establishment failed and neighbour cells, and UE location (see TS 32.422 [20]). |
7.2.4 LBO (Load Balancing Optimisation)
7.2.4.1 MnS component type A
Table 7.2.4.1-1: C-LBO type A
|
MnS Component Type A |
Note |
|
Operations and notifications defined in clause 11.1.1 of TS 28.532 [3]: – createMOI operation – getMOIAttributes operation — modifyMOIAttributes operation – – deleteMOI operation – – notifyMOIAttributeValueChanges – notifyMOICreation – notifyMOIDeletion – notifyMOIChanges |
It is supported by Provisioning MnS for NF, as defined in 28.531 [11]. |
|
Operations defined in clause 11.3.1.1.1 in TS 28.532 [3] and clause 6.2.3 of TS 28.550 [12]: – establishStreamingConnection operation – notifyFileReady operation – reportStreamData operation |
It is supported by Performance Assurance MnS for NFs, as defined in 28.550 [12]. |
7.2.4.2 MnS Component Type B definition
7.2.4.2.1 Parameters to be updated
Table 7.2.4.2.1-1: Ranges of HO and cell selection parameters
|
Control parameters |
Definition |
Legal Values |
|---|---|---|
|
Maximum deviation of Handover Trigger |
This parameter defines the maximum allowed absolute deviation of the Handover Trigger, from the default point of operation (see clause 15.5.2.5 in TS 38.300 [7] and clause 9.2.2.61 in TS 38.423 [17]). See attribute maximumDeviationHoTrigger in TS 28.541 [13]. |
[-20 .. 20] in unit 0.5 dB |
|
Minimum time between Handover Trigger changes |
This parameter defines the minimum allowed time interval between two Handover Trigger change performed by MRO. This is used to control the stability and convergence of the algorithm (see clause 15.5.2.5 in TS 38.300 [7]). See attribute minimumTimeBetweenHoTriggerChange in TS 28.541 [13]. |
[0 .. 604800] in unit Seconds |
7.2.4.3 MnS Component Type C definition
7.2.4.3.1 Performance measurements
Table 7.2.4.3.1-1. lists the performance measurements that are used to monitor the load of NR cells (see clause 15.5.1.2 in TS 38.300 [7]).
Table 7.2.4.3.1-1. C-LBO load performance measurements
|
Performance measurements |
Description |
Note |
|
DL Total PRB Usage |
This measurement provides the total usage (in percentage) of physical resource blocks (PRBs) on the downlink (see clause 5.1.1.2.1 in TS 28.552 [5]). |
|
|
UL Total PRB Usage |
This measurement provides the total usage (in percentage) of physical resource blocks (PRBs) on the uplink (see clause 5.1.1.2.2 in TS 28.552 [5]). |
|
|
Distribution of DL Total PRB Usage |
This distribution measurement is to monitor when a cell may experience overload situation in the downlink (see clause 5.1.1.2.3 in TS 28.552 [5]). |
|
|
Distribution of UL Total PRB Usage |
This distribution measurement is to monitor when a cell may experience overload situation in the uplink (see clause 5.1.1.2.4 in TS 28.552 [5]). |
|
|
DL PRB used for data traffic |
This measurement provides the number of physical resource blocks (PRBs) in average used in downlink for data traffic (see clause 5.1.1.2.5 in TS 28.552 [5]). |
|
|
UL PRB used for data traffic |
This measurement provides the number of physical resource blocks (PRBs) in average used in uplink for data traffic (see clause 5.1.1.2.7 in TS 28.552 [5]). |
|
|
Mean number of RRC Connections |
This measurement provides the mean number of users in RRC connected mode during the granularity period (see clause 5.1.1.4.1 in TS 28.552 [5]). |
|
|
Max number of RRC Connections |
This measurement provides the maximum number of users in RRC connected mode during the granularity period (see clause 5.1.1.4.2 in TS 28.552 [5]). |
|
|
Mean number of stored inactive RRC Connections |
This measurement provides the mean number of users in RRC inactive mode during each granularity period (see clause 5.1.1.4.3 in TS 28.552 [5]). |
|
|
Max number of stored inactive RRC Connections |
This measurement provides the maximum number of users in RRC inactive mode during each granularity period (see clause 5.1.1.4.3 in TS 28.552 [5]). |
Table 7.2.4.3.1-2 lists the performance measurements used to monitor the LBO performance:
Table 7.2.4.3.1-2. C-LBO related performance measurements
|
Performance measurements |
Description |
Note |
|---|---|---|
|
Attempted RRC connection establishments |
Includes the number of RRC connection establishment attempts (see clause 5.1.1.15.1 in TS 28.552 [5]). |
|
|
Successful RRC connection establishments |
Includes the number of successful RRC establishments (see clause 5.1.1.15.2 in TS 28.552 [5]). |
|
|
Number of RRC connection re-establishment attempts |
Includes the number of RRC connection re-establishment attempts (see clauses 5.1.1.17.1 in TS 28.552 [5]). |
|
|
Successful RRC connection re-establishment |
Includes the number of successful RRC connection re-establishment (see clauses 5.1.1.17.2 and 5.1.1.17.3 in TS 28.552 [5]). |
|
|
Number of RRC connection resuming attempts |
Includes Number of RRC connection resuming attempts (see clause 5.1.1.18.1 in TS 28.552 [5]). |
|
|
Successful RRC connection resuming |
Includes the number of successful RRC connection resuming (see clause 5.1.1.18.2 in TS 28.552 [5]). |