8 Data definitions for MDA capabilities
28.1043GPPManagement and orchestrationManagement Data Analytics (MDA)Release 17TS
8.1 Introduction
8.1.1 MDA Types
The output of MDA can be related to a particular capability as described in clause 7, where an MDA type can indicate a specific MDA capability corresponding to a predefined use case(s).
The MDA capabilities may also support analytics of a set of data or analytics for certain PMs, KPIs, trace data, QoE or other type of data. Analytics related to the set of data relies on multiple raw, or already processed input data enabling an MDA MnS producer to provide more complex MDA output. Analytics related to certain set of data including PMs, KPIs, trace or QoE data may rely on these specific categories of data.
MDA MnS consumers may request and obtain output for MDA types related to analytics of a set of data or analytics for certain PMs, KPIs, trace or QoE data.
8.2 About analytics
8.2.1 About enabling data
Analytics are capability-specific, and the present document provides the enabling data for each MDA capability in the respective tables. It is not restrictive or mandatory to use the analytics inputs exactly the same as the provided enabling data for implementation, and other (additional or different) data are also allowed in order to facilitate the production of analytics outputs.
8.2.2 About analytics outputs
For analytics outputs, there are:
1) common information elements that can be generated by MDA and be applicable for all MDA capabilities;
2) capability-specific information elements; and
3) optionally, vendor specific extensions.
The common information elements are provided in clause 8.3, and the capability-specific information elements are provided per MDA capability in clause 8.4 of the present document.
8.3 Common information elements of analytics outputs
8.3.0 General
There are some information elements that are common for all analytics outputs and MDA capabilities, i.e. these common information elements form a subset of all analytics outputs of all MDA capabilities.
8.3.1 Common information element definitions
The common information elements of the analytics outputs are defined in Table 8.3.1-1.
Table 8.3.1-1: Common information elements of analytics outputs
Information element |
Definition |
Support qualifier |
Properties |
mDAType |
It indicates the MDA type. The allowed values are the MDA type names defined for each MDA capability respectively in clause 8.4. |
M |
type: string multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
analyticsId |
The identifier of the analytics output. |
M |
type: string multiplicity: 1 isOrdered: N/A isUnique: True defaultValue: None isNullable: False |
analyticsOutputGenerationTime |
It indicates the time when the analytics output is generated. |
M |
type: DateTime multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
8.4 Data definitions per MDA capability
8.4.1 Coverage related analytics
8.4.1.1 Coverage problem analysis
8.4.1.1.1 MDA type
The MDA type for coverage problem analysis is: CoverageAnalytics.CoverageProblemAnalysis.
8.4.1.1.2 Enabling data
The enabling data for CoverageAnalytics.CoverageProblemAnalysis MDA type are provided in table 8.4.1.1.2-1.
For general information about enabling data, see clause 8.2.1.
Table 8.4.1.1.2-1: Enabling data for coverage problem analysis
Data category |
Description |
References |
---|---|---|
Performance measurements |
SS-RSRP distribution per SSB (beam) of serving NR cell |
SS-RSRP distribution per SSB (clause 5.1.1.22.1 of TS 28.552 [4]). |
SS-RSRP distribution per SSB (beam) of neighbor NR cell |
SS-RSRP distribution per SSB of neighbor NR cell (clause 5.1.1.22.2 of TS 28.552 [4]) |
|
RSRP distribution of neighbor E-UTRA cell for an NR cell |
RSRP distribution per neighbor E‑UTRAN cell (clause 5.1.1.22.3 of TS 28.552 [4]) |
|
Power headroom distribution for NR cell |
Type 1 power headroom distribution (clause 5.1.1.26.1 of TS 28.552 [4]). |
|
Wideband CQI distribution for NR cell |
Wideband CQI distribution (clause 5.1.1.11.1 of TS 28.552 [4]). |
|
Timing Advance distribution for NR cell |
Timing Advance distribution for NR Cell (clause 5.1.1.33.1 of TS 28.552 [4]) |
|
Number of UE Context Release Request (gNB-DU initiated) |
Number of UE Context Release Request (gNB-DU initiated) (clause 5.1.3.5.1 of TS 28.552 [4]). |
|
Number of UE Context Release Request per SSB (gNB-DU initiated) |
Number of UE Context Release Request (gNB-DU initiated) (clause 5.1.3.5.1 of TS 28.552 [4]). |
|
Number of UE Context Release Requests (gNB-CU initiated) |
Number of UE Context Release Request (gNB-CU initiated) (clause 5.1.3.5.2 of TS 28.552 [4]). |
|
Number of UE Context Release Requests per SSB (gNB-CU initiated) |
Number of UE Context Release Request (gNB-CU initiated) (clause 5.1.3.5.2 of TS 28.552 [4]). |
|
RSRP related measurements for ng-eNB |
RSRP related measurements (clause 6.1 of TS 32.425 [12]). |
|
UE power headroom related measurements for ng-eNB |
UE power headroom related measurements (clause 6.3 of TS 32.425 [12]). |
|
Wideband CQI distribution for ng-eNB |
Wideband CQI distribution (clause 4.10.1.1 of TS 32.425 [12]). |
|
Average sub-band CQI for ng-eNB |
Average sub-band CQI (clause 4.10.1.2 of TS 32.425 [12]). |
|
UE Rx – Tx time difference related measurements for ng-eNB |
UE Rx – Tx time difference related measurements (clause 6.4 of TS 32.425 [12]). |
|
AOA related measurements for ng-eNB |
AOA related measurements (clause 6.5 of TS 32.425 [12]). |
|
Timing Advance distribution for ng-eNB |
Timing Advance Distribution (clause 4.10.2 of TS 32.425 [12]). |
|
Number of UE CONTEXT Release Request initiated by ng-eNodeB |
Number of UE CONTEXT Release Request initiated by eNodeB/RN (clause 4.1.5.1 of TS 32.425 [12]). |
|
MDT reports |
MDT reports containing RSRPs of the serving cell and neighbour cells, and UE location. |
RSRPs and UE location of M1 measurements for NR in TS 32.422 [6] and TS 32.423 [7]. |
RLF reports |
RLF reports containing RSRPs of the last serving cell and neighbour cells, and UE location. |
RLF data collection and RLF reporting in TS 32.422 [6], and rlf-Report-r16 in TS 38.331 [13]. |
RCEF reports |
RCEF reports containing RSRPs of NR cell where the RRC connection establishment failed and neighbour cells, and UE location. |
RCEF data collection and RCEF reporting in TS 32.422 [6], and ConnEstFailReport-r16 in TS 38.331 [13]. |
UE location reports |
UE location information provided by the LMF services which can be used to correlate with the MDT reports. |
The UE location information provided by LMF via service-based interface (see TS 23.273 [14]). |
Geographical data |
The geographical information (longitude, latitude, altitude) of the deployed RAN (NG-RAN and E-UTRAN). |
The geographical information (longitude, latitude, altitude) information (see the peeParametersList attribute of the ManagedFunction IOC in TS 28.622 [19]). |
Configuration data |
The NRMs containing the attributes affecting the coverage for (NG-RAN and E-UTRAN). |
NRCellDU IOC, NRSectorCarrier IOC, BWP IOC, CommonBeamformingFunction IOC, and Beam IOC in TS 28.541 [15]; EUtranGenericCell IOC in TS 28.658 [16]; SectorEquipmentFunction IOC, AntennaFunction IOC, and TMAFunction IOC in TS 28.662 [17]. |
8.4.1.1.3 Analytics output
The specific information elements of the analytics output for coverage problem analysis, in addition to the common information elements of the analytics outputs (see clause 8.3), are provided in table 8.4.1.1.3-1.
Table 8.4.1.1.3-1: Analytics output for coverage problem analysis
Information element |
Definition |
Support qualifier |
Properties |
---|---|---|---|
coverageProblemId |
The identifier of the coverage problem. |
M |
type: string multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
coverageProblemType |
Indication of type of the coverage Problem. The allowed value is one of the enumerated values: WeakCoverage, CoverageHole, PilotPollution, Overshoot coverage, DlUlChannelCoverageMismatch, Other. |
M |
type: enumeration multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
coverageProblemAreas |
Geographical location areas where the coverage problem occurred. |
O |
type: GeoArea (see TS 28.622 [19]) multiplicity: * isOrdered: False isUnique: True defaultValue: None isNullable: False |
problematicCells |
The CGIs of cells where the coverage problem occurred. |
M |
type: Integer multiplicity: * isOrdered: False isUnique: True defaultValue: None isNullable: False |
recommendedActions |
The recommended actions to solve the coverage problem. The recommended action may be (but not limited to): – creation of new beam(s), or cell(s); – change the transmission power of the NR sector carrier; – delete some unwanted beam(s) or cell(s). |
M |
type: RecommendedAction multiplicity: * isOrdered: False isUnique: True defaultValue: None isNullable: False |
radioEnvironmentMap |
The graphical description of the observed radio coverage characteristics. The graphic may be for the RSRP or SINR of the selected cluster of cells mapped against the physical geographical information (longitude, latitude, altitude) of the area where the RAN (NG-RAN and E-UTRAN) cells are deployed. It is a list of paired tuples of geographical information (longitude, latitude, altitude) and coverage (RSRP or SINR) values. |
O |
type: List multiplicity: * isOrdered: False isUnique: True defaultValue: None isNullable: False |
cellConfigurations |
The cell configurations for a new cell or reconfigurations of existing cells derived based on the characteristics in the radioEnvironmentMap. The cell configurations are the changes to the NRMs attributes affecting the cell coverage (NG-RAN and E-UTRAN). |
O |
type: may differ as defined in NRCellDU IOC, NRSectorCarrier IOC, BWP IOC, CommonBeamformingFunction IOC, and Beam IOC in TS 28.541 [15]; multiplicity: * isOrdered: False isUnique: True defaultValue: None isNullable: False |
8.4.1.2 Paging Optimization
8.4.1.2.1 MDA type
The MDA type for Capability-Paging Optimization: SLSAnalysis.PagingOptimization.
8.4.1.2.2 Enabling data
The enabling data for paging optimization are provided in table 8.4.1.2.2-1.
Table 8.4.1.2.2-1: Enabling data for Paging Optimization Analysis
Data category |
Description |
References |
MDT Data |
MDT reports indicating UE location information |
MDT measurements defined in TS 32.423 [7]. |
Performance measurements |
Measurement for 5G Paging from AMF |
See clause 5.2.5.2 in TS 28.552 [4]. |
8.4.1.2.3 Analytics output
The specific information elements of the analytics output for paging optimization, in addition to the common information elements of the analytics outputs (see clause 8.3), are provided in table 8.4.1.2.3-1.
Table 8.4.1.2.3-1: Analytics output for paging optimization analysis
Information element |
Definition |
Support qualifier |
Properties |
oOCDuration |
This specify the time window during which UE is out-of-coverage. |
M |
type: ProjectionDuration multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
oOCLocation |
This specifies the last known location of the UEs before it goes out-of-coverage. This would be within the area indicated by the "areaScope" of the MDA request. |
CM |
type: GeoCoordinate multiplicity: 1..* isOrdered: False isUnique: True defaultValue: None isNullable: False |
oOCMap |
This specifies the geographical region within which the paging issues are experienced by a group of UEs. This would be within the area indicated by the "areaScope" of the MDA request. |
CM |
type: GeoArea (see TS 28.622 [19]) multiplicity: 1..* isOrdered: False isUnique: True defaultValue: None isNullable: False |
8.4.2 SLS analysis
8.4.2.1 Service experience analysis
8.4.2.1.1 MDA type
The MDA type for Capability-Service experience analysis is: SLSAnalysis.ServiceExperienceAnalysis.
8.4.2.1.2 Enabling data
The enabling data for SLSAnalysis.ServiceExperienceAnalysis MDA type are provided in table 8.4.2.1.2-1.
Table 8.4.2.1.2-1: Enabling data for service experience analysis
Data category |
Description |
References |
Performance measurements |
Average e2e uplink/downlink delay for a network slice |
Average e2e uplink/downlink delay for a network slice (in clause 6.3.1.8 in TS 28.554 [5]). |
Integrated uplink/downlink delay in RAN |
Integrated downlink delay in RAN (clause 6.3.1.2 in TS 28.554 [5]); Integrated uplink delay in RAN (clause 6.3.1.7 in TS 28.554 [5]). |
|
Round-trip packet delay |
Round-trip packet delay between PSA UPF and NG‑RAN (clause 5.4.8 in TS 28.552 [4]). |
|
UL/DL throughput for network and Network Slice Instance |
Upstream throughput for network and Network Slice Instance (clause 6.3.2 in TS 28.554 [5]); Downstream throughput for Single Network Slice Instance (clause 6.3.3 in TS 28.554 [5]). |
|
RAN UE Throughput |
RAN UE Throughput (clause 6.3.6 in TS 28.554 [5]) |
|
Throughput at N3 interface |
Upstream Throughput at N3 interface (clause 6.3.4 in TS28.554 [5]); Downstream Throughput at N3 interface (clause 6.3.5 in TS28.554 [5]). |
|
QoE Data |
The QoE data of the different services |
QoE data (TS 26.247 [22] and TS 26.114 [23] can be acquired through the procedures defined in TS 28.405 [8]). |
8.4.2.1.3 Analytics output
The specific information elements of the analytics output for service experience analysis, in addition to the common information elements of the analytics outputs (see clause 8.3), are provided in table 8.4.2.1.3-1.
Table 8.4.2.1.3-1: Analytics output for Service experience analysis
Information element |
Definition |
Support qualifier |
Properties |
serviceExperienceId |
The identifier indicates the analytics report is related with service experience analysis. |
M |
type: string multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
serviceExperienceIssueType |
Indication of the service experience issue type. The allowed value is one of the enumerated values: – RAN issue; – CN issue; – both |
M |
type: ENUM multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
affectedObjects |
The managed object instances where the service experience is applicable, e.g. SubNetwork Instance, NetworkSlice Instance. |
O |
type: DN multiplicity: 1..* isOrdered: False isUnique: True defaultValue: None isNullable: False |
serviceExperienceStatistics |
The statistics of the level of service experience for a service in a certain time period, e.g. there are five levels which are represented by 1, 2, 3, 4, 5 where level 1 represents the users are enduring bad experience while level 5 represents the users’ requirements are perfectly satisfied. |
O |
type: ENUM multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
serviceExperiencePredictions |
The predictions of the level of service experience for a service in a certain time period. |
O |
type: ENUM multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
8.4.2.2 Network slice throughput analysis
8.4.2.2.1 MDA type
The MDA type for Capability-Network slice throughput analysis is: SLSAnalysis.NetworkSliceThroughputAnalysis.
8.4.2.2.2 Enabling data
The enabling data for SLSAnalysis.NetworkSliceThroughputAnalysis MDA type are provided in table 8.4.2.2.2-1.
Table 8.4.2.2.2-1: Enabling data for network slice throughput analysis
Data category |
Description |
References |
Performance measurements |
UL/DL throughput for network and Network Slice Instance |
Upstream throughput for network and Network Slice Instance as defined in clause 6.3.2 in TS 28.554 [5]; Downstream throughput for Single Network Slice Instance as defined in clause 6.3.3 in TS 28.554 [5]. |
RAN UE Throughput |
RAN UE Throughput as defined in clause 6.3.6 in TS 28.554 [5]. |
|
Throughput at N3 interface |
Upstream Throughput at N3 interface as defined in clause 6.3.4 in TS 28.554 [5]; Downstream Throughput at N3 interface as defined in clause 6.3.5 in TS 28.554 [5]. |
8.4.2.2.3 Analytics output
The specific information elements of the analytics output for network slice throughput analysis, in addition to the common information elements of the analytics outputs (see clause 8.3), are provided in table 8.4.2.2.3-1.
Table 8.4.2.2.3-1: Analytics output for network slice throughput analysis
Information element |
Definition |
Support qualifier |
Properties |
networkSliceThroughputIssueId |
Network slice throughput issue identifier |
M |
type: string multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
networkSliceThroughputIssueType |
Indication of the network slice throughput issue type The allowed value is one of the enumerated values: RAN issue, CN issue, both |
M |
type: ENUM multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
networkSliceThroughputUserStatistics |
The statistics of the UL and/or DL network slice throughput in a certain time period. The value indicates the average percentage of users, for which the required SLS throughput satisfies |
O |
type: integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
networkSliceThroughputTimeStatistics |
The statistics of the UL and/or DL network slice throughput in a certain time period. The value indicates the average percentage of time, during which the required SLS throughput satisfies |
O |
type: integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
networkSliceThroughputUserPredictions |
The predictions of the UL and/or DL network slice throughput in a certain time period. The value indicates the average percentage of users, for which the required SLS throughput could be met |
O |
type: integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
networkSliceThroughputTimePredictions |
The predictions of the UL and/or DL network slice throughput in a certain time period. The value indicates the average percentage of time, during which the required SLS throughput could be met. |
O |
type: integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
8.4.2.3 Network slice traffic prediction
8.4.2.3.1 MDA type
The MDA type for capability Network slice traffic prediction is: SLSAnalysis.NetworkSliceTrafficAnalysis.
8.4.2.3.2 Enabling data
The enabling data for SLSAnalysis.NetworkSliceTrafficAnalysis MDA type are provided in table 8.4.2.3.2-1.
Table 8.4.2.3.2-1: Enabling data for network slice traffic prediction analysis
Data category |
Description |
References |
Performance measurements |
UL/DL throughput for network slice. |
Upstream throughput for network and Network Slice Instance (clause 6.3.3 in TS 28.554 [5]); Downstream throughput for Single Network Slice Instance (clause 6.3.4 in TS 28.554 [5]). |
Number of incoming and outgoing octets of GTP packet on N3 |
See clauses 5.4.1.4 and 5.4.1.3 in TS 28.541 [5]). |
|
UL/DL UE throughput for network slice |
RAN UE Throughput (clause 6.3.6 in TS 28.554 [5]). |
|
Number of PDU sessions of network slice |
Mean number of PDU sessions of network and network Slice Instance (clause 6.4.1 in TS 28.554 [5]). |
|
Number of registered subscribers of a network slice instance |
Mean registered subscribers of network and network slice through AMF (see clause 6.2.1 in TS 28.554 [5]). |
|
Maximum packet size for a network slice |
Maximum packet size for a network slice subnet (see clause 6.3.11 of TS 28.541 [5]). |
8.4.2.3.3 Analytics output
The specific information elements of the analytics output for network slice traffic prediction analysis, in addition to the common information elements of the analytics outputs (see clause 8.3), are provided in table 8.4.2.3.3-1.
Table 8.4.2.3.3-1: Analytics output for network slice traffic prediction analysis
Information element |
Definition |
Support qualifier |
Properties |
trafficProjections |
This specifies the traffic projections for a slice. |
M |
type: TrafficProjections multiplicity: * isOrdered: False isUnique: True defaultValue: None isNullable: False |
8.4.2.4 E2E latency analysis
8.4.2.4.1 MDA type
The MDA type for Capability-E2E latency analysis is: SLSAnalysis.E2ElatencyAnalysis.
8.4.2.4.2 Enabling data
The enabling data for SLSAnalysis.E2ElatencyAnalysis MDA type are provided in table 8.4.2.4.2-1.
Table 8.4.2.4.2-1: Enabling data for E2E latency analysis
Data category |
Description |
References |
Performance measurements |
Average e2e UL/DL delay for a network slice |
Average e2e uplink delay for a network (clause 6.3.1.8.1 in TS 28.554 [5]); Average e2e downlink delay for a network slice (clause 6.3.1.8.2 in TS 28.554 [5]). |
Integrated uplink/downlink delay in RAN |
Integrated downlink delay in RAN (clause 6.3.1.2 in TS 28.554 [5]); Integrated uplink delay in RAN (clause 6.3.1.7 in TS 28.554 [5]). |
|
Round-trip Packet Delay |
Round-trip packet delay between PSA UPF and NG-RAN (clause 5.4.8 TS 28.552 [4]). |
8.4.2.4.3 Analytics output
The specific information elements of the analytics output for E2E latency analysis, in addition to the common information elements of the analytics outputs (see clause 8.3), are provided in table 8.4.2.4.3-1.
Table 8.4.2.4.3-1: Analytics output for E2E latency analysis
Information element |
Definition |
Support qualifier |
Properties |
e2ELatencyIssueId |
The identifier indicates the output is for E2E latency issue analysis |
M |
type: String multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
e2ELatencyIssueType |
Indication the type of the E2E latency issue. The allowed value is one of the enumerated values: RAN latency issue, CN latency issue |
M |
type: ENUM multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
affectedObjects |
The managed object instances of subnetwork, managed elements or network slices where the latency issue happens |
O |
type: DN multiplicity: 1..* isOrdered: False isUnique: True defaultValue: None isNullable: False |
8.4.2.5 Network slice load analysis
8.4.2.5.1 MDA type
The MDA type for Capability- Network slice load analysis is: SLSAnalysis.NetworkSliceLoadAnalysis.
8.4.2.5.2 Enabling data
The enabling data for SLSAnalysis.NetworkSliceLoadAnalysis MDA type are provided in table 8.4.2.5.2-1.
Table 8.4.2.5.2-1: Enabling data for network slice load analysis
Data category |
Description |
References |
Performance measurements |
Number of PDU sessions of network slice |
Mean number of PDU sessions of network and network Slice Instance (clause 6.4.1 in TS 28.554 [5]). |
Number of PDU Sessions successfully setup |
Number of PDU Sessions successfully setup (clause 5.1.1.5 in TS28.552 [4]). |
|
Mean Number of PDU sessions |
Number of PDU sessions(Mean) (clause 5.3.1.1 in TS 28.552 [4]). |
|
Network Data Analytics |
Analysis results from the control plane produced by NWDAF |
Analytics data from NWDAF in TS 23.288 [10] including e.g. Slice load level related network data analytics clause 6.3, and the analytics for user plane performance (i.e. average/maximum traffic rate, average/maximum packet delay, average packet loss rate in clause 6.14. |
Configuration data |
MOIs of the cells, NW slice/NW slice subnet, 5GC NFs |
NRM information TS 28.541 [15]. |
8.4.2.5.3 Analytics output
The specific information elements of the analytics output for network slice load analysis, in addition to the common information elements of the analytics outputs (see clause 8.3), are provided in table 8.4.2.5.3-1.
Table 8.4.2.5.3-1: Analytics output for network slice load analysis
Information element |
Definition |
Support qualifier |
Properties |
networkSliceLoadIssueId |
The identifier indicates the output is for Network slice instance load analysis |
M |
type: string multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
networkSliceLoadIssueDomain |
Indicates the domain of the network slice instance load issue The allowed value is one of the enumerated values: – RAN issue; – CN issue |
M |
type: ENUM multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
networkSliceLoadIssuePhase |
Indicates the phase of the network slice instance load issue The allowed value is one of the enumerated values: historic network slice load issue, ongoing network slice load issue, potential network slice load issue |
M |
type: ENUM multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
networkSliceLoadIssueType |
Indicates the type of the network slice instance load issue The allowed value is one of the enumerated values: overload network slice load issue, underutilized network slice load issue |
M |
type: ENUM multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
affectedObjects |
The managed object instances involved in the network slice instance load problem |
O |
type: DN multiplicity: 1..* isOrdered: False isUnique: True defaultValue: None isNullable: False |
networkSliceLoadDistribution |
Describes the detailed load distribution or predictive distribution, e.g. load distribution for a network slice instance at a certain location or in a certain time period |
O |
type: Integer multiplicity: * isOrdered: True isUnique: False defaultValue: None isNullable: False |
8.4.3 MDA assisted fault management
8.4.3.1 MDA assisted failure prediction
8.4.3.1.1 MDA type
The MDA type for failure prediction analysis is: MDAAssistedFaultManagement.FailurePrediction.
8.4.3.1.2 Enabling data
The enabling data for MDAAssistedFaultManagement.FailurePrediction MDA type are provided in table 8.4.3.1.2-1.
For general information about enabling data, see clause 8.2.1.
Table 8.4.3.1.2-1: Enabling data for fault predication analysis
Data category |
Description |
References |
Performance measurements |
The deteriorated performance or the abnormal performance measurements based on certain performance monitoring threshold. 3GPP management system may monitor a set of performance measurements and their thresholds, so as to support the analytics of prediction of a network service failure. |
The performance measurements as defined in TS 28.552 [4] |
Alarm notifications |
Alarm information, e.g. the alarm notification of network functions. |
Alarm information and notifications as per TS 28.532 [11] |
Configuration data |
MOIs of the cells, UPFs and SMFs. |
TS 28.541 [15] |
Network analytics data |
The control plane analysis result from the NWDAF, e.g. observed service experience related network data analytics. |
TS 23.288 [10] |
8.4.3.1.3 Analytics output
The specific information elements of the analytics output for failure prediction analysis, in addition to the common information elements of the analytics outputs (see clause 8.3), are provided in table 8.4.3.1.3-1.
Table 8.4.3.1.3-1: Analytics output for fault prediction analysis
Information element |
Definition |
Support qualifier |
Properties |
failurePredictionObject |
Indication of NR cells or NFs where the failure related issues occurred or potentially occur. |
M |
type: DN multiplicity: 1..* isOrdered: False isUnique: True defaultValue: None isNullable: False |
potentialFailureType |
Indication of type of issues that can cause the failures. NOTE 1: The values can be defined as a list of example values: "Operational Violation", "Physical Violation" and "Time Domain Violation". See alarmType described in TS 28.532 [11]. |
M |
type: string multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
eventTime |
This field holds the time of potential failure predicted. Examples: "20:15:00", "20:15:00-08:00" (for 8 hours behind UTC). |
M |
type: DateTime multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
issueID |
This filed holds the ID of this failure prediction which is reported. When reports, this identifier can be used to provide the information to management system to maintain. |
M |
type: string multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
perceivedSeverity |
This field holds the value to indicate relative level of urgency for operator attention. NOTE 2: The value can be Critical, Major, Minor, Warning, Indeterminate, Cleared, see Recommendation ITU-T X.733 [27]. |
M |
type: ENUM multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
8.4.4 MDA assisted energy saving
8.4.4.1 Energy saving analysis
8.4.4.1.1 MDA type
The MDA type for energy saving analysis is: MDAAssistedEnergySaving.EnergySavingAnalysis.
8.4.4.1.2 Enabling data
The enabling data for MDAAssistedEnergySaving.EnergySavingAnalysis MDA type are provided in table 8.4.4.1.2-1.
For general information about enabling data, see clause 8.2.1.
Table 8.4.4.1.2-1: Enabling data for energy saving analysis
Data category |
Description |
References |
Performance measurements |
PNF Power Consumption: power consumed over the measurement period |
Clause 5.1.1.19.2 of TS 28.552 [4]. |
PNF Energy consumption: energy consumed |
Clause 5.1.1.19.3 of TS 28.552 [4]. |
|
SS-RSRP distribution per SSB (beam) of serving NR cell |
Clause 5.1.1.22.1 of TS 28.552 [4]. |
|
SS-RSRP distribution per SSB (beam) of neighbor NR cell |
Clause 5.1.1.22.1 of TS 28.552 [4]. |
|
PDCP Data Volume of NR cells: PDCP data volume delivered in the downlink and uplink |
Clause 5.1.2.1 and 5.1.3.6 of TS 28.552 [4] |
|
Traffic load variation: – PRB utilization rate; – RRC connection number; – etc. |
Clause 5.1.1.2 and 5.1.1.4 of TS 28.552 [4]. |
|
UE throughput: – UE throughput in downlink and uplink |
Clause 5.1.1.3 of TS 28.552 [4]. |
|
Delay related measurements of UPF |
Clause 5.4 of TS 28.552 [4]. |
|
Data volume of UPF |
Clause 5.4 of TS 28.552 [4]. |
|
Virtual resource usage of NF: The virtual CPU usage, virtual memory usage, virtual disk usage of virtual network functions |
Clause 5.7.1 of TS 28.552 [4]. |
|
MDT reports |
The RSRPs of UE measurements |
RSRPs of M1 measurements in TS 32.422 [6] and TS 32.423 [7]. |
The RSRQs of UE measurements |
RSRQs of M1 measurements in TS 32.422 [6] and TS 32.423 [7]. |
|
The UE location information |
UE location of M1 measurements in TS 32.422 [6] and TS 32.423 [7]. |
|
QoE Data |
The measurements that are collected are DASH and MTSI measurements |
TS 28.406 [9]. |
Configuration data |
MOIs of the cells, UPFs and SMFs |
TS 28.541 [15]. |
Network analytics data |
The control plane analysis result from the NWDAF, e.g. observed service experience related network data analytics |
TS 23.288 [10]. |
8.4.4.1.3 Analytics output
The specific information elements of the analytics output for energy saving analysis, in addition to the common information elements of the analytics outputs (see clause 8.3), are provided in table 8.4.4.1.3-1.
Table 8.4.4.1.3-1: Analytics output for energy saving analysis
Information element |
Definition |
Support qualifier |
Properties |
---|---|---|---|
energyEfficiencyProblematicObject |
Indication of NR cells or NFs where the energy efficiency issues occurred or potentially occur. |
M |
type: DN multiplicity: 1..* isOrdered: False isUnique: True defaultValue: None isNullable: False |
energyEfficiencyProblemType |
Indication of type of the energy efficiency issues. The allowed value is one of the enumerated values: HighEnergyConsumption, LowEenergyEfficiency, Other, Unknown. |
M |
type: enumeration multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
trafficLoadTrends |
The predictions of the trends of traffic load in a certain time period. The predictions include the traffic load of the issue cell(s) and neighboring cell(s). |
M |
type:TrafficLoadTrend multiplicity: 1..* isOrdered: False isUnique: True defaultValue: None isNullable: False |
rANenergySavingRecommendations |
For ES on NR cells. It may contain a set of: – Recommended NR Cell (ES-Cell) to enter energySaving state. – Recommended candidate cells with precedence for taking over the traffic of the ES-Cell. – The time to enter and terminate the energy saving state. – The load threshold to enter and terminate the energy saving state for the ES-Cell. This exist only in case of RAN energy saving is supported. |
CM |
type: EsRecommendationOnNRcell multiplicity: 1..* isOrdered: False isUnique: True defaultValue: None isNullable: False |
cNenergySavingRecommendations |
For ES on UPFs. It contains a set of: – Recommended UPF (ES-UPF) to conduct energy saving. – Recommended candidate UPFs with precedence for taking over the traffic of the ES-UPF. – The time to conduct energy saving for the ES-UPF. This exist only in case of CN energy saving is supported.. |
CM |
type: EsRecommendationOnUPF multiplicity: 1..* isOrdered: False isUnique: True defaultValue: None isNullable: False |
statisticsOfCellsEsState |
The statistic result of current energy saving state of the cells at a certain time, which can be used by consumers to make analysis (e.g. observed service experience analysis made by NWDAF) or to make decision (e.g. enter/exit the energy saving state based on the current energy saving state). |
O |
type: StatisticOfCellEsState multiplicity: 1..* isOrdered: False isUnique: True defaultValue: None isNullable: False |
8.4.5 MDA assisted mobility management
8.4.5.1 Mobility performance analysis
8.4.5.1.1 MDA type
The MDA type for mobility performance analysis is: MobilityManagementAnalytics.MobilityPerformanceAnalysis.
8.4.5.1.2 Enabling data
The enabling data for MobilityManagementAnalytics.MobilityPerformanceAnalysis MDA type are provided in table 8.4.5.1.2-1.
For general information about enabling data, see clause 8.2.1.
Table 8.4.5.1.2-1: Enabling data for mobility performance analysis
Data category |
Description |
References |
Performance measurements |
Inter-gNB handovers |
Inter-gNB handovers (clause 5.1.1.6.1 of TS 28.552 [4]). |
Intra-gNB handovers |
Inter-gNB handovers (clause 5.1.1.6.4 of TS 28.552 [4]). |
|
Inter-gNB DAPS handovers |
Inter-gNB handovers (clause 5.1.1.6.2 of TS 28.552 [4]). |
|
Intra-gNB DAPS handovers |
Inter-gNB handovers (clause 5.1.1.6.3 of TS 28.552 [4]). |
|
Inter-gNB conditional handovers |
Inter-gNB handovers (clause 5.1.1.6.6 of TS 28.552 [4]). |
|
Intra-gNB conditional handovers |
Inter-gNB handovers (clause 5.1.1.6.7 of TS 28.552 [4]). |
8.4.5.1.3 Analytics output
The specific information elements of the analytics output (MDA report) for mobility performance analysis, in addition to the common information elements of the analytics outputs (see clause 8.3), are provided in table 8.4.5.1.3‑1.
Table 8.4.5.1.3-1: Analytics output for Mobility Performance analysis
Information element |
Definition |
Support qualifier |
Properties |
mobilityPerformance IssueIdentifier |
The identifier of the mobility performance issue analysis; |
M |
type: integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
mobilityPerformance IssueRootCause |
The root cause of mobility performance issues. The allowed value is one of the enumerated values: too long mobility interruption time, poor coverage of the cell-edge, inappropriate handover parameters, other. |
M |
type: ENUM multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
mobilityPerformance IssueLocation |
Geographical location areas where the mobility performance issue occurred. |
O |
type: GeoArea (see TS 28.622 [19]) multiplicity: * isOrdered: False isUnique: True defaultValue: None isNullable: False |
8.4.5.2 Handover Optimization analysis
8.4.5.2.1 MDA type
The MDA type for handover optimization is: MobilityManagementAnalytics.HandoverOptimization.
8.4.5.2.2 Enabling data
The enabling data for handover optimization analysis are provided in table 8.4.5.2-1.
For general information about enabling data, see clause 8.2.1.
Table 8.4.5.2.2-1: Enabling data for handover optimization analysis
Data category |
Description |
References |
Performance Measurements |
Consumed virtual resources of target gNB |
Virtualised resource usage measurement (clause 6.2 of TS 28.552 [4]) |
The physical radio resource utilization of each target cells |
Physical radio resource utilization of the target gNB, see clause 5.1.1.2 of TS 28.552 [4]; |
|
PDCP Data Volume of NR cells |
Clause 5.1.2.1 and 5.1.3.6 of TS 28.552 [4]. |
|
MDT Data |
UE measurements related to RSRP, RSRQ, SINR (serving cell and neighbour cells) and UE location information |
RSRPs, RSRQs and UE location of M1 measurements for NR in TS 32.422 [6] and TS 32.423 [7]. |
8.4.5.2.3 Analytics output
The specific information elements of the analytics output for handover optimization analysis, in addition to the common information elements of the analytics outputs (see clause 8.3), are provided in table 8.4.5.2.3-1.
Table 8.4.5.2.3-1: Analytics output for handover optimization analysis
Information element |
Definition |
Support qualifier |
Properties |
hOTarget |
This provides analytics report for each target cell, of a target gNB, for handover optimization. |
M |
type: HOTargetType multiplicity: 1..* isOrdered: False isUnique: True defaultValue: None isNullable: False |
8.4.6 Maintenance management related analytics
8.4.6.1 Maintenance management analysis
8.4.6.1.1 MDA type
The MDA type for maintenance management is: Maintenance.MaintenanceAnalytics.
8.4.6.1.2 Enabling data
The enabling data for Maintenance.MaintenanceAnalytics MDA type are provided in table 8.4.6.1.2-1.
For general information about enabling data, see clause 8.2.1.
Table 8.4.6.1.2-1: Enabling data for maintenance analysis
Data category |
Description |
References |
Performance Measurements |
Number of Active DRB |
Mean number of DRBs being allocated (clause 5.1.1.10.9 of TS 28.552 [4]). |
Number of bearers undergoing handover |
Number of requested preparations for handovers from 5GS to EPS (clause 5.1.1.6.3.1 of TS 28.552 [4]). Number of requested resource allocations for handovers from EPS to 5GS (clause 5.1.1.6.3.4 of TS 28.552 [4]) Number of requested preparations for EPS fallback handovers (clause 5.1.1.6.3.10 of TS 28.552 [4]) Number of successful executions for EPS fallback handovers (clause 5.1.1.6.3.13 of TS 28.552 [4]) |
|
Number of bearers being recovered from the error state |
Editors Note: to be defined in TS 28.552. |
|
Number of successful bearer modification |
Number of QoS flows attempted to modify (clause 5.1.1.13.4.1 of TS 28.552 [4]) |
8.4.6.1.3 Analytics output
The specific information elements of the analytics output for maintenance management analysis, in addition to the common information elements of the analytics outputs (see clause 8.3), are provided in table 8.4.6.1.3-1.
Table 8.4.6.1.3-1: Analytics output for maintenance analysis
Information element |
Definition |
Support qualifier |
Properties |
currentUpgradeOptimal |
This data type defines whether gNB can be upgrade at present |
M |
type: CurrentUpgrade multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: none isNullable: False |
futureUpgradeOptimal |
This data type defines whether the gNB can be upgrade in future and when |
M |
type: FutureUpgrade multiplicity: * isOrdered: False isUnique: True defaultValue: none isNullable: False |
gNBID |
This identifies the gNB |
type: String multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: none isNullable: False |
8.5 Data type definitions
8.5.1 RecommendedAction <<dataType>>
8.5.1.1 Definition
This data type specifies the type of recommended action in the analytics output.
8.5.1.2 Information elements
Table 8.5.1.2-1
Name |
Definition |
Support qualifier |
Properties |
recommended3GPPActions |
It contains the recommendations actions concerning 3GPP defined operations on MOIs. |
O |
type: Recommended3GPPAction multiplicity: * isOrdered: False isUnique: True defaultValue: None isNullable: False |
recommendedHumanReadableActions |
It contains the recommendations on human readable actions. NOTE: Further details of recommended human readable actions are not specified. |
O |
type: string multiplicity: * isOrdered: False isUnique: True defaultValue: None isNullable: False |
8.5.2 Recommended3GPPAction <<dataType>>
8.5.2.1 Definition
This data type specifies the data type of recommended 3GPP action.
8.5.2.2 Information elements
Table 8.5.2.2-1
Name |
Definition |
Support qualifier |
Properties |
---|---|---|---|
mOInstance |
Identifies the instance of a common ancestor object of the objects for which changes are recommended. |
M |
type: string multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
path |
The "path" and "mOInstance" identify the object, attribute, attribute field or multi-value attribute element, that are recommended for creation, deletion or modification. |
M |
type: string multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
op |
It specifies the type of operation that is recommended for the MOI specified by the path. Allowed values: "add", "remove" and "replace". The operation describes what is recommended to do to the NRM. "add" shall be used for recommending the creation of an object, attribute, attribute field or multi-value attribute element. "remove" shall be used for recommending the deletion of an object, attribute, attribute field or multi-value attribute element. "replace" shall be used for recommending the replacement of an existing attribute value, attribute field value or multi-value attribute element. |
M |
type: enumeration multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
value |
If an object creation is recommended with "add", the "value" shall carry a complete representation of the created object. If an object deletion is recommended with "remove", the "value" shall be absent. It may optionally carry a complete representation of the deleted object. If an attribute, attribute field or multi-value attribute element creation is recommended with "add", the "value" shall carry the value of the recommended attribute, attribute field or multi-value attribute element. If an attribute, attribute field or multi-value attribute element deletion is recommended with "remove", the "value" shall be absent. If the replacement of an attribute, attribute field or multi-value attribute element value is recommended with "replace", the "value" shall carry the new value of the attribute, attribute field or multi-value attribute element. If multiple objects are recommended for creation, the creation of parent objects shall be recommended before the child objects. |
CM |
type: AttributeValuePair (see TS 32.156 [18]) multiplicity: * isOrdered: False isUnique: True defaultValue: None isNullable: False |
additionalText |
It provides the additional text for the recommended change. |
O |
type: string multiplicity: * isOrdered: False isUnique: False defaultValue: None isNullable: False |
8.5.2.3 Constraints
Table 8.5.2.3-1
Name |
Definition |
value Support Qualifier |
Condition: value of op attribute is "add", or "replace". |
8.5.3 TrafficLoadTrend <<dataType>>
8.5.3.1 Definition
This data type specifies the type of TrafficLoadTrend.
8.5.3.2 Information elements
Table 8.5.3.2-1
Name |
Definition |
Support qualifier |
Properties |
cellId |
It indicates the cell for which the traffic load prediction is performed. |
M |
type: DN multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
startTime |
It indicates the start time that are used for traffic load prediction. |
M |
type: DateTime multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
endTime |
It indicates the end time that are used for traffic load prediction. |
M |
type: DateTime multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
trafficLoadList |
It provides a list of PRB usage based on a specific granularity. |
M |
type: Integer multiplicity: 1..* isOrdered: True isUnique: False defaultValue: None isNullable: False |
8.5.4 Void
8.5.5 EsRecommendationsOnNRcell <<dataType>>
8.5.5.1 Definition
This data type specifies the type of energy saving recommendations on NR cells.
8.5.5.2 Information elements
Table 8.5.5.2-1
Name |
Definition |
Support qualifier |
Properties |
esNRcell |
It provides the DN of NR cell (ES-Cell) which is recommended to enter energySaving state. |
M |
type: DN multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
candidateNRcells |
It provides the DN of candidate NR cells which are recommended with precedence for taking over the traffic of ES-Cell. |
M |
type: DN multiplicity: * isOrdered: False isUnique: True defaultValue: None isNullable: False |
enterTime |
It provides the recommended time to enter the energy saving state for the ES-Cell. |
M |
type: DateTime multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
endTime |
It provides the recommended time to terminate the energy saving state for the ES-Cell. |
M |
type: DateTime multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
trafficThresholds |
It provides the recommended traffic threshold information. The ES-Cell can enter the energy saving state when the traffic is below the threshold value defined in the thresholdValue. |
M |
type: ThresholdInfo multiplicity: * isOrdered: False isUnique: False defaultValue: None isNullable: False |
8.5.6 EsRecommendationsOnUPF <<dataType>>
8.5.6.1 Definition
This data type specifies the type of energy saving recommendations on UPFs.
8.5.6.2 Information elements
Table 8.5.6.2-1
Name |
Definition |
Support qualifier |
Properties |
esUPF |
It provides the DN of UPF (ES-UPF) which is recommended to conduct energy saving. |
M |
type: DN multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
candidateUPFs |
It provides the DN of candidate UPFs which are recommended with precedence for taking over the traffic of ES-UPF. |
O |
type: DN multiplicity: * isOrdered: False isUnique: True defaultValue: None isNullable: False |
conductTime |
It indicates the recommended time period to conduct energy saving for the ES-UPF. |
M |
type: TimeWindow multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
8.5.7 StatisticOfCellEsState <<dataType>>
8.5.7.1 Definition
This data type specifies the type of statistics of cells energy saving state in the analytics output.
8.5.7.2 Information elements
Table 8.5.7.2-1
Name |
Definition |
Support qualifier |
Properties |
cellId |
It indicates the cell for which the statistics is performed. |
M |
type: DN multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
startTime |
It indicates the start time that are used for statistics. |
M |
type: DateTime multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
endTime |
It indicates the end time that are used for statistics. |
M |
type: DateTime multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
ratioOfEsStateTime |
It provides the ratio of the time when the cell is in the energy saving state to the total time between StartTime and EndTime. |
M |
type: Real multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
8.5.8 CurrentUpgrade <<dataType>>
8.5.8.1 Definition
This data type specifies whether it is optimal to upgrade the gNB at present.
8.5.8.2 Information elements
Table 8.5.8.2-1
Name |
Definition |
Support qualifier |
Properties |
currentUpgradeOptimal |
Boolean attribute indicating whether RAN Node can be upgrade at present. |
type: Boolean multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
|
numberOfGBRDRB |
This specifies the total number of GBR bearer at present. |
type: Integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
|
numberOfNonGBRDRB |
This specifies the total number of non-GBR bearer at present. |
type: Integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
8.5.9 FutureUpgrade <<dataType>>
8.5.9.1 Definition
This data type specifies whether it is optimal to upgrade the gNB at a future point of time.
8.5.9.2 Information elements
Table 8.5.9.2-1
Name |
Definition |
Support qualifier |
Properties |
---|---|---|---|
futureUpgradeOptimal |
Boolean attribute indicating whether RAN Node can be upgrade at a future point of time. |
M |
type: Boolean multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
optimalTime |
This specifies the future time period during which the gNB can be upgraded optimally. This shall be present only if the FutureUpgradeOptimal is TRUE. |
CM |
type: TimeWindow multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
numberOfGBRDRB |
This specifies the total number of GBR bearer which will be present at the time stamp provided by the attribute OptimalTime. This shall be present only if the FutureUpgradeOptimal is TRUE. |
CM |
type: Integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
numberOfNonGBRDRB |
This specifies the total number of non-GBR bearer which will be present at the time stamp provided by the attribute OptimalTime. This shall be present only if the FutureUpgradeOptimal is TRUE. |
CM |
type: Integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
8.5.10 TrafficProjections <<dataType>>
8.5.10.1 Definition
This data type specifies the traffic projection for a slice.
8.5.10.2 Information elements
Table 8.5.10.2-1
Name |
Definition |
Support qualifier |
Properties |
projectionTime |
The time duration for which the projections are made. |
M |
type: ProjectionDuration multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
uPFProjections |
This specifies the traffic projection of a UPF in the slice. It shall be present only if the analysis target contains CN part. |
CM |
type: UPFProj multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
gNBProjections |
This specifies the traffic projection of a gNB in the slice. It shall be present only if the analysis target contains AN part. |
CM |
type: gNBProj multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
sMFProjections |
This specifies the projected number of PDU session of a SMF in the slice. It shall be present only if the analysis target contains CN part. |
CM |
type: Integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
aMFProjections |
This specifies the projected number of registered subscriber of an AMF in the slice. It shall be present only if the analysis target contains CN part. |
CM |
type: Integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
8.5.11 UPFProj <<dataType>>
8.5.11.1 Definition
This data type specifies the traffic projection for a UPF.
8.5.11.2 Information elements
Table 8.5.11.2-1
Name |
Definition |
Support qualifier |
Properties |
uLThroughput |
The projected average UL throughput for a single UPF in the slice, over the time duration indicated by projectionTime attribute. The unit is kbit/s. This is the projection of the Upstream Throughput at N3 interface KPI defined in TS 28.554 [5] |
M |
type: Integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
dLThroughput |
The projected average DL throughput for a single UPF in the slice, over the time duration indicated by projectionTime attribute. The unit is kbit/s. This is the projection of the Downstream Throughput at N3 interface KPI defined in TS 28.554 [5]. |
M |
type: Integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
maxPktSize |
The projected average maximum packet size for a single UPF in the slice, over the time duration indicated by projectionTime attribute. |
O |
type: Integer multiplicity: 1 isOrdered: N/A isUnique: True defaultValue: None isNullable: False |
8.5.12 gNBProj <<dataType>>
8.5.12.1 Definition
This data type specifies the traffic projection for a gNB.
8.5.12.2 Information elements
Table 8.5.12.2-1
Name |
Definition |
Support qualifier |
Properties |
uLUEThroughput |
The projected average UL UE throughput in the slice, over the time duration indicated by projectionTime attribute. The unit is kbit/s. This is the projection of the UL RAN UE throughput KPI defined in TS 28.554 [5]. |
M |
type: Integer multiplicity: 1 isOrdered: N/A isUnique: True defaultValue: None isNullable: False |
dLUEThroughput |
The projected average DL throughput in the slice, over the time duration indicated by projectionTime attribute. The unit is kbit/s. This is the projection of the DL RAN UE throughput KPI defined in TS 28.554 [5]. |
M |
type: Integer multiplicity: 1 isOrdered: N/A isUnique: True defaultValue: None isNullable: False |
8.5.13 HOTargetType <<dataType>>
8.5.13.1 Definition
This data type specifies the information about the target cell and gNB for handover.
The attribute isOptimal specify if the cell (served by gNB) is optimal for handover considering the current virtual, physical and radio resource consumption by the gNB and/or the cell. The value TRUE imply that the target is not resource deprived at present and can be selected for handover.
The attribute futureOptimalInfo specify if the cell (served by the gNB) will be optimal for handover at a future point of time considering the future virtual and radio resource consumption by the gNB and/or the cell . This will also provide projection of future virtual, and radio resource consumptions.
8.5.13.2 Information elements
Table 8.5.13.2-1
Name |
Definition |
Support qualifier |
Properties |
gNBId |
See clause 4.4.1 of TS 28.541 [15]. |
M |
type: Integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
cellLocalId |
See clause 4.4.1 of TS 28.541 [15]. |
M |
type: Integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: NULL isNullable: False |
isOptimal |
This specifies if the cell (served by the gNB) is optimal for handover with respect to the virtual and physical resource consumption of its gNB and its own radio resource consumption. The value TRUE indicates that the gNB is optimal at present. Allowed Values: TRUE and FALSE. |
M |
type: Boolean multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: TRUE isNullable: False |
futureOptimalInfo |
This specifies related information when the cell is optimal for handover in future. |
O |
type: FutureOptimal multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
8.5.14 FutureOptimal <<dataType>>
8.5.14.1 Definition
This data type specifies the time duration for which the gNB is optimal for upgrade. This also provide virtual, physical and radio resource projections.
8.5.14.2 Information elements
Table 8.5.14.2-1
Name |
Definition |
Support qualifier |
Properties |
futureOptimalTime |
This specifies the time duration during which the cell is optimal for handover. |
M |
type: ProjectionDuration multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
projectedVResCon |
This specifies the projected virtual resource consumption of the gNB. This exist only in case of virtual gNB. |
CM |
type: VirRes multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
projectedRResCon |
This specifies the projected radio resource consumption of the cell. |
M |
type: RadRes multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
8.5.15 VirRes <<dataType>>
8.5.15.1 Definition
This data type specifies the virtual resource consumption.
8.5.15.2 Information elements
Table 8.5.15.2-1
Name |
Definition |
Support qualifier |
Properties |
virtualCPU |
It indicates the average number of virtual CPU (see definition of numVirtualCpu in clause 7.1.9.2.3.2 of ETSI GS NFV‑IFA 011 [26]) usage over the time duration indicated by FutureOptimalTime attribute. |
M |
type: Integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
virtualMemory |
It indicates the average virtual memory size (see definition of virtualMemSize in clause 7.1.9.2.3.2 of ETSI GS NFV‑IFA 011 [26]) usage over the time duration indicated by FutureOptimalTime attribute. |
M |
type: Integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
virtualDisk |
It indicates the average virtual storage size (see definition of sizeOfStorage in clause 7.1.9.2.3.2 of ETSI GS NFV‑IFA 011 [26]) usage over the time duration indicated by FutureOptimalTime attribute. |
M |
type: Integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
8.5.16 RadRes <<dataType>>
8.5.16.1 Definition
This data type specifies the radio resource consumption.
8.5.16.2 Information elements
Table 8.5.16.2-1
Name |
Definition |
Support qualifier |
Properties |
dLPRBUsage |
This specifies the average total usage (in percentage) of Physical Resource Blocks (PRBs) on the downlink for any purpose, over the time duration indicated by projectionTime attribute. |
M |
type: Real multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
uLPRBUsage |
This specifies the average total usage (in percentage) of Physical Resource Blocks (PRBs) on the uplink for any purpose, over the time duration indicated by projectionTime attribute. |
M |
type: Real multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
8.5.17 ProjectionDuration <<dataType>>
8.5.17.1 Definition
This data type specifies the time duration for which the projections are made.
8.5.17.2 Information elements
Table 8.5.17.2-1
Name |
Definition |
Support qualifier |
Properties |
fromTime |
This specifies the timestamp from when the projection are made |
M |
type: DateTime multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |
toTime |
This specifies the timestamp till when the projection are made |
M |
type: DateTime multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False |