Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 28.104  Word version:  18.3.0

Top   Top   Up   Prev   Next
1…   5…   6…   7…   7.2.2…   7.2.3…   7.2.4…   7.2.5…   7.2.6…   7.2.7…   7.2.8…   7.3…   8…   9…   10…   A…

 

7.2.2  SLS analysisp. 25

7.2.2.1  Service experience analysisp. 25

7.2.2.1.1  Descriptionp. 25
This MDA capability is for the service experience analysis.
7.2.2.1.2  Use casep. 25
Service experience of end user is key indicator that directly reflects the user satisfaction degree. In 5G system, the diversity of network services is expanding all the time and the requirements of different services especially from vertical users are being standardized. Considering these diverse requirements and expectation from end user perspective (e.g. priorities of SLA related attributes such as latency, throughput, maximum number of users or different required values of these attributes), the service experience as a comprehensive indicator need to be extensively analysed.
Up
7.2.2.1.3  Requirementsp. 26
Requirement label Description Related use case(s)
REQ-SER_EXP_MDA-01MDA capability for service experience analysis shall include identifying the source of service experience issue, e.g. RAN issue, CN issue, TN issue, UE issue, service provider issue.Service experience analysis.
REQ-SER_EXP_MDA-02MDA capability for service experience analysis shall include providing the analytics output with following information describing the current service experience aspects and potentially future prediction:
  • The predicted future service experience and/or observed service experience statistics.
  • Service experience degradation root cause analysis.
Service experience analysis.
REQ-SER_EXP_MDA-03MDA capability for service experience analysis shall include providing the level of service experience.Service experience analysis.
REQ-SER_EXP_MDA-04MDA capability for service experience analysis shall include providing the recommendation for improving service experience.Service experience analysis.
REQ-SER_EXP_MDA-05MDA capability for service analysis should include the ability to provide service experience analysis across or within domains.Service experience analysis.
Up

7.2.2.2  Network slice throughput analysisp. 26

7.2.2.2.1  Descriptionp. 26
This MDA capability is for the network slice throughput analysis.
7.2.2.2.2  Use casep. 26
Throughput is of great importance which represents the end users' experiences and also reflects the network problems, e.g. low UE throughput may be caused by resource shortage. In order to satisfy the requirements of dL/ulThptPerSlice in the ServiceProfile, MDAS may be utilized for throughput related analysis/predictions for network slice instance.
MDAS producer allows the consumer to request analytics of network slice throughput related issues and identify the corresponding root cause(s) to assist throughput assurance. Network slice throughput analysis can be for a specific domain and/or for cross-domain. Domain-specific MDAS producer analyses the network slice subnet throughput, while the cross-domain MDAS producer analyses the network slice throughput. The two level MDAS producers, i.e. domain-specific and cross-domain may work in coordination to assure the optimum throughput performance.
Up
7.2.2.2.3  Requirementsp. 26
Requirement label Description Related use case(s)
REQ-THR_MDA-1MDA capability for network slice throughput analysis shall include identifying the network slice throughput issues, including those RAN-related and CN-related issues.Network slice throughput analysis.
REQ-THR_MDA -2MDA capability for network slice throughput analysis shall include providing the root cause analysis of the network slice throughput issue(s).Network slice throughput analysis.
REQ-THR_MDA -3MDA capability for network slice throughput analysis shall include providing the analytics output of the network slice throughput which contain the following information:
  • Network slice throughput statistics.
  • Network slice throughput predictions.
Network slice throughput analysis.
REQ-THR_MDA-04MDA capability for network slice throughput analysis shall include providing the prompt when the network slice throughput exceeds or falls below a certain threshold.Network slice throughput analysis.
Up

7.2.2.3  Network slice traffic predictionp. 27

7.2.2.3.1  Descriptionp. 27
This MDA capability is for the prediction of network slice traffic patterns.
7.2.2.3.2  Use casep. 27
It is desirable to use MDAS to get the network slice traffic predictions including individual traffic load predictions on each of the constituent network function instance present in the network slice. The traffic load predictions per constituent network function instances can be used for better resource provisioning of the network slice. For example, resources can be pre-configured considering the predicted traffic on the network slice.
7.2.2.3.3  Requirementsp. 27
Requirement label Description Related use case(s)
REQ-TRA_MDA-01MDA capability for network slice traffic prediction shall include providing analytics output describing traffic load prediction of the network slice including traffic load prediction for each of its constituent network function instances.Network slice traffic prediction.
REQ-TRA_MDA-02MDA capability for network slice traffic prediction shall include providing analytics output describing traffic load prediction for the network slice which include the following information:
  • Predicted uplink and downlink throughput on each User Plane Function instance (UPF) in the network slice.
  • Predicted number of Packet Data Unit (PDU) session for each Session Management Function (SMF) instance in the network slice.
  • Predicted number of UE or Registered subscriptions for each AMF instance in the network slice.
  • Predicted maximum packet size for each UPF instance in the network slice.
  • Predicted UE uplink and downlink throughput on each gNodeB (gNB) instance in the network slice.
  • Predicted number of UE for each gNB/NR cell instance in the network slice.
Network slice traffic prediction.
Up

7.2.2.4  E2E latency analysisp. 27

7.2.2.4.1  Descriptionp. 27
This MDA capability is for E2E latency related issue analysis.
7.2.2.4.2  Use casep. 27
E2E latency is an important parameter for URLLC services. User data packets should be successfully delivered within certain time constraints to satisfy the end users requirements. Latency could be impacted by the network capability and network configurations. These factors may be the root cause if the latency requirements cannot be achieved. Packet transmission latency may dynamically change if these factors change. The latency requirement should be assured even if some of the network conditions may degrade. It is important for the MDAS producer to analyze the latency related issues to support SLS assurance.
Up
7.2.2.4.3  Requirementsp. 28
Requirement label Description Related use case(s)
REQ-LAT_MDA-01MDA capability for E2E latency analytics shall include identifying the type of the E2E latency issue, including, RAN- related latency issue, CN-related latency issue, TN-related latency issue, UE-related latency issue and service provider originated latency issue.E2E latency analytics.
REQ-LAT_MDA-02MDA capability for E2E latency analytics shall include providing the root cause analysis of the E2E latency issue.E2E latency analytics.
REQ-LAT_MDA-03MDA capability for E2E latency analytics shall include providing the recommended actions to solve the E2E latency issue.E2E latency analytics.
Up

7.2.2.5  Network slice load analysisp. 28

7.2.2.5.1  Descriptionp. 28
This MDA capability is for network slice load analysis.
7.2.2.5.2  Use casesp. 28
Network slice load may vary during different time periods. Therefore, network resources allocated initially could not always satisfy the traffic requirements, for example, the network slice may be overloaded or underutilized. Overload of signalling in control plane and/or user data congestion in user plane will lead to underperforming network. Besides, allocating excessive resources for network slice with light load will decrease resource efficiency.
The analysis of network slice load should consider the load of services with different characteristics (e.g. QoS information, service priority), load distribution to derive the corresponding resource requirements. Load distribution analytic result may be provided, e.g. load distribution for network slices, different locations and/or time periods etc.
Traffics and resources related performance measurements and UE measurements can be utilized by MDAS producer to identify degradation of the performance measurements and KPI documented in an SLS due to load issues, e.g. radio resource utilization. MDAS producer may further provide recommendations to the network slice load issue. This analytics results can be considered as an input to support SLA assurance to perform further evaluation.
Up
7.2.2.5.3  Requirementsp. 28
Requirement label Description Related use case(s)
REQ-NS_LOAD_MDA-01MDA capability for network slice load analytics shall include identifying the domain of the network slice load issue, including, RAN issue, CN issue and TN-related issues.network slice load analytics.
REQ-NS_LOAD_MDA-02MDA capability for network slice load analytics shall include identifying the phase of the network slice load issue, e.g. historic/ongoing/potential network slice load issue.network slice load analytics.
REQ-NS_LOAD_MDA-03MDA capability for network slice load analytics shall include identifying the state of the network slice load issue, e.g. overload/underutilized network slice load issue.network slice load analytics.
REQ-NS_LOAD_MDA-04MDA capability for network slice load analytics shall include identifying the list of the network entities which are involved in the network slice load issue.network slice load analytics
REQ-NS_LOAD_MDA-05MDA capability for network slice load analytics shall include providing analytics related to network slice load within specified time schedules and geographic locations or target objects.network slice load analytics.
REQ-NS_LOAD_MDA-06MDA capability for network slice load analytics shall include providing the root cause and recommended actions to the network slice load issue.network slice load analytics.
Up

Up   Top   ToC