hash
stringlengths
32
32
doc_id
stringlengths
5
12
section
stringlengths
5
1.47k
content
stringlengths
0
6.67M
0f43309e2e94684398565057f4cf8c2e
28.885
5.4.4.1 Description
Within the 3GPP 5GS, seven standard SSTs have been defined in TS 23.501 [8] to support key scenarios such as eMBB, URLLC, and MIoT, among others. The standardization of SST values facilitates global interoperability for network slicing, enabling PLMNs to support roaming more efficiently for the most commonly deployed s...
0f43309e2e94684398565057f4cf8c2e
28.885
5.4.4.2 Potential requirements
PREQ-Energy_Efficiency_HDLLC-1: The 3GPP management system should be able to estimate the energy efficiency for HDLLC.
0f43309e2e94684398565057f4cf8c2e
28.885
5.4.4.3 Potential solutions
None.
0f43309e2e94684398565057f4cf8c2e
28.885
5.4.4.4 Evaluation of potential solutions
There were no potential solutions studied for this use case.
0f43309e2e94684398565057f4cf8c2e
28.885
5.4.5 Use case #5: Enhancements to gNB Energy Consumption
0f43309e2e94684398565057f4cf8c2e
28.885
5.4.5.1 Description
gNB Energy Consumption KPI is used by operators to monitor the energy consumed by a gNB, and used by 5GC network function EIF for internal processing, hence the correctness of the KPI is important. gNB EC KPI is defined in clause 6.7.3.4 of TS 28.554 [4], and specified that it is obtained by summing up the Energy Con...
0f43309e2e94684398565057f4cf8c2e
28.885
5.4.5.2 Potential requirements
PREQ-Energy_Consumption_gNB-1: The 3GPP management system should be able to measure and report the energy consumption of a gNB designed to run on dedicated hardware.
0f43309e2e94684398565057f4cf8c2e
28.885
5.4.5.3 Potential solutions
0f43309e2e94684398565057f4cf8c2e
28.885
5.4.5.3.1 Potential solution #1: gNB EC KPI using PNF Energy consumption measurement
0f43309e2e94684398565057f4cf8c2e
28.885
5.4.5.3.1.1 Introduction
This potential solution describes the enhancements to the gNB EC KPI is defined in clause 6.7.3.4 of TS 28.554 [4].
0f43309e2e94684398565057f4cf8c2e
28.885
5.4.5.3.1.2 Description
gNB EC KPI is proposed to be based on PNF Energy consumption measurement (PEE.Energy) defined in clause 5.1.1.19.3 of TS 28.552 [10] when the gNB is designed to run on dedicated hardware. This potential solution proposes the gNB EC KPI to be updated and defined as follows: a) ECgNB b) This KPI describes the Energy C...
0f43309e2e94684398565057f4cf8c2e
28.885
5.4.5.4 Evaluation of potential solutions
The potential solution #1 gNB EC KPI using PNF Energy consumption measurement (described in clause 5.4.5.3.1), provides the enhancements to the gNB EC KPI is defined in clause 6.7.3.4 of TS 28.554 [4]. This potential solution utilizes measurement PNF Energy consumption defined in clause 5.1.1.19.3 of TS 28.552 [10]. ...
0f43309e2e94684398565057f4cf8c2e
28.885
6 Conclusions and recommendations
0f43309e2e94684398565057f4cf8c2e
28.885
6.1 Enhancements to support energy efficiency as a service criteria
0f43309e2e94684398565057f4cf8c2e
28.885
6.1.1 Use case #1: Enhancements to support the energy-related characteristics for Network Elements and Network Functions
The use case, requirements (PREQ-Energy_Related_Characteristics-2 and PREQ-Energy_Related_Characteristics-3) and potential solutions for the Enhancements to support the energy-related characteristics for Network Elements and Network Functions are described in clause 5.1.1. The evaluation and feasibility of the potentia...
0f43309e2e94684398565057f4cf8c2e
28.885
6.1.2 Use case #2: Management mechanisms to support service adjustments to adapt to energy-related characteristics and energy rationing
The use case and potential requirement for Management mechanisms to support service adjustments to adapt to energy-related characteristics and energy rationing are described in clause 5.1.2. There is no potential solution for this use case, hence no impacts identified for the normative phase.
0f43309e2e94684398565057f4cf8c2e
28.885
6.1.3 Use case #3: Energy Rationing Information Management
The use case, requirement (REQ-Energy_Rationing-CON-1) and potential solution for the Energy Rationing Information Management are described in clause 5.1.3. The evaluation and feasibility of the potential solution is described in clause 5.1.3.4. It is proposed to define the solution in TS 28.310 [3], as input to the no...
0f43309e2e94684398565057f4cf8c2e
28.885
6.2 Enhancements to support the information required by Energy Information Function (EIF)
0f43309e2e94684398565057f4cf8c2e
28.885
6.2.1 Use case #1: Energy consumption and Energy Efficiency estimation and reporting at per network slice granularity
The use case, requirements (PREQ-Energy_Consumption_Network_Sharing-1) and potential solutions for Energy consumption and Energy Efficiency estimation and reporting at per network slice granularity are described in clause 5.2.1. The evaluation and feasibility of the potential solution is described in clause 5.2.1.4. Fo...
0f43309e2e94684398565057f4cf8c2e
28.885
6.2.2 Use case #2: Enhancements to 5GC NF Profile to support energy saving and energy efficiency
The use case, requirements (PREQ-NFProfile_Energy_Conf-1) and potential solutions enhancements to introduce new attributes to ManagedNFProfile data type (defined in clause 5.3.54 of TS 28.541 [7]) are described in clause 5.2.2. The evaluation and feasibility of the potential solution is described in clause 5.2.2.4. It ...
0f43309e2e94684398565057f4cf8c2e
28.885
6.3 Improve energy saving, energy efficiency and reducing carbon footprint of 5G network
There are no use-cases studied to improve energy saving, energy efficiency and reducing carbon footprint of 5G network, hence no impacts identified for the normative phase.
0f43309e2e94684398565057f4cf8c2e
28.885
6.4 Enhancements to Energy Consumption and Energy Efficiency measurements and KPIs
0f43309e2e94684398565057f4cf8c2e
28.885
6.4.1 Use case #1: Renewable energy consumption
The use case and potential requirement for Renewable energy consumption are described in clause 5.4.1. There is no potential solution for this use case, hence no impacts identified for the normative phase.
0f43309e2e94684398565057f4cf8c2e
28.885
6.4.2 Use case #2: Support EC measurement of NE at per Energy Supply granularity
The use case, requirements (PREQ-Energy_Consumption-1) and potential solutions to support EC measurement of NE at per Energy Supply granularity are described in clause 5.4.2. The evaluation and feasibility of the potential solution is described in clause 5.4.2.4. It is proposed to enhance ManagedFunction IOC (defined i...
0f43309e2e94684398565057f4cf8c2e
28.885
6.4.3 Use case #3: Support estimation of EC and EE KPIs at per PLMN-ID granularity in Network sharing scenario
The use case, requirements (PREQ-Energy_Consumption_Network_Sharing-1) and potential solutions to support estimation of EC and EE KPIs at per PLMN-ID granularity in Network sharing scenario are described in clause 5.4.3. The evaluation and feasibility of the potential solution is described in clause 5.4.3.4. It is prop...
0f43309e2e94684398565057f4cf8c2e
28.885
6.4.4 Use case #4: Support estimation of EE KPI of HDLLC slice
The use case and potential requirement for Support estimation of EE KPI of HDLLC slice are described in clause 5.4.4. There is no potential solution for this use case, hence no impacts identified for the normative phase.
0f43309e2e94684398565057f4cf8c2e
28.885
6.4.5 Use case #5: Enhancements to gNB Energy Consumption
The use case, requirements (PREQ-Energy_Consumption_gNB-1) and potential solutions for enhancements to gNB Energy Consumption gNB EC KPI using PNF Energy consumption measurement are described in clause 5.4.5. The evaluation and feasibility of the potential solution is described in clause 5.4.5.4. It is proposed to enha...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
1 Scope
The present document investigates and discusses use cases along with the corresponding potential requirements and solutions for improvements to interoperability, improvements to MDA framework, new analytics related capabilities and enhanced analytics related capabilities.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific. - For a specific reference, subsequent revisions do not apply. -...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
3 Definitions of terms, symbols and abbreviations
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
3.1 Terms
For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
3.2 Symbols
Void.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. CPA Conditional PSCell Addition CPC Conditional PSCell Change NSA Non-st...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
4 Concept and background
Management Data Analytics (MDA) is defined in TS 28.104 [2]. MDA provides a capability of processing and analysing data related to network and service events and status to provide analytics output, and may also provide recommendations to enable necessary actions for network and service operations.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5 Use cases
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.1 Improvements to interoperability
No content was identified for this aspect of the study.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.2 Improvements to MDA framework
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.2.1 Use case 1: Integration of analytics with a network operator’s management system
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.2.1.1 Description
A Network Operator (NOP) wishes to integrate Management Data Analytics Service with the NOP’s automated network management system. To be able to successfully perform this integration, the NOP needs to know which management facilities are provided by MDAS. The NOP also needs to know if MDAS depends on other 3GPP manage...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.2.1.2 Potential requirements
None.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.2.1.3 Potential solutions
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.2.1.3.1 Update description of MDA scope for closed loop control management
TS 28.104 [2] clause 6.1 states that only analytics are in scope. Other aspects of a management loop (Observation, Decision, Execution) are therefore not in scope. This is in conflict with TS 28.567 [4] figures 5.1.2.2-1 and 5.1.2.2-2, which show that the MDA MnS producer may perform data collection, analytics, and dec...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.2.1.4 Evaluation of solutions
The solution proposed in clause 5.2.1.3 is feasible for normative work.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.2.2 Use case 2: Indicating supported domain information in MDAFunction
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.2.2.1 Description
The IOC MDAFunction represents the MDA function which supports one or more MDA capabilities as described in TS 28.104 [2]. It also describes that an MDA function can act as 3GPP domain-specific (e.g. RAN or CN) or as 3GPP cross-domain MDA MnS producer. From MnS consumer perspective, it is reasonable to know not only th...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.2.2.2 Potential requirements
REQ-MDA_Fun-01: The MDA MnS producer should have the capability to allow authorized MDA MnS consumer to request the supported analysis of domain information.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.2.3.3 Potential solutions
It is proposed to make the following changes to TS 28.104 [2] clause 9.3.1.2: - update the MDAFunction IOC attribute to add a new attribute supportedMDADomains, which can be used to indicate the domain(s) supported by the MDAFunction.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.2.2.4 Evaluation of solutions
The solution proposed in clause 5.2.2.3 satisfies the requirements and this solution is feasible for normative work.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3 Investigate new and enhanced analytics related capabilities
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.1 Use case 1: Enhance the Mobility performance analysis use case
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.1.1 Description
This use case is to enhance the existing MDA capability for mobility performance analysis. The enhancements to the existing mobility performance analysis are targeted towards to solve the mobility problems in NSA deployment architecture and to recommend optimization or repair actions. The existing use case for mobilit...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.1.2 Potential requirements
REQ-MRO_MDA-01: MDA capability for mobility performance issue analysis should provide the NSA mobility issue including too-early PSCell change, too-late PSCell change, too Late CPC Execution and too Early CPC/CPA Execution. REQ-MRO_MDA-02: MDA capability for mobility performance issue analysis should include providing...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.1.3 Potential solutions
Reuse the performanceThresholdInfo attribute in the MDARequest IOC with the threshold of mobility related performance measurements for this MDA type, including: - Thresholds of mobility related performance measurements. The enabling data for this MDA type would introduce the additional NSA mobility measurements as fo...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.1.4 Evaluation of solutions
The solution proposed in clause 5.3.1.3 satisfies the requirements and this solution is feasible for normative work.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.2 Use case 2: MDA assisted failure resolution
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.2.1 Description
As networks become more complex, it becomes more difficult to quickly resolve network failures, where network performance becomes degraded or lost completely. By looking only at the alarm list, it can be difficult to identify the most serious network failures. Network automation is essential to speed up the identificat...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.2.2 Potential requirements
REQ-FAILURE_RESOLUTION_MDA-01: MDA capability for network failure resolution should be able to provide the analytics output including the probable impact of the network failure. REQ-FAILURE_RESOLUTION_MDA-02: MDA capability for network failure resolution should be able to provide the analytics output including recomme...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.2.3 Potential solutions
Update TS 28.104 [2] to add a new MDA type MDAAssistedFaultManagement.FailureAnalysis to allow an MnS consumer to request analytics related to a network failure. Update TS 28.104 [2] to add a new analytics output for network failure analysis, including (but not limited to) information related to: - related alarm(s) w...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.2.4 Evaluation of solutions
The solution proposed in clause 5.3.2.3 satisfies the requirements and this solution is feasible for normative work.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.3 Use case 3: Radio resource optimization based on per SSB usage
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.3.1 Description
5G NR adopts massive MIMO technology, where the base station employs directional beams for both UE initial access on common channels and subsequent connection during the RRC_CONNECTED state. Common signals/channels for initial access are transmitted within the Synchronization Signal Block (SSB). SSBs are designed with ...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.3.2 Potential requirements
REQ-RRO-FUN-01: MDA should have capability for radio resource optimization analysis. REQ-RRO-FUN-02: MDA capability for radio resource optimization analysis should include the capability of the beam-level radio resource utilisation assessment to indicate if coverage shape configuration of gNodeB is proper based on bea...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.3.3 Potential solutions
Update TS 28.104 [2] to add a new MDA type RadioResourceAnalytics.SSBUsageAnalysis. MnS consumer could request MDAS to acquire beam-level management data and recommend coverage shape based on analysis. The enabling data for RadioResourceAnalytics.SSBUsageAnalysis would include as follows: - Timing Advance distributio...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.3.4 Evaluation of solutions
The solution proposed in clause 5.3.3.3 satisfies the requirements and this solution is feasible for normative work.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.4 Use case 4: Remote Electrical Tilt (RET) and Transmission Power analytics (TP)
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.4.1 Description
Operators establish their own guidelines for deploying antenna RET, both mechanical and electrical, in cells, primarily based on LTE/NR layers and traffic management strategies. Initial RET and power configurations may not be optimal for all cells, necessitating ongoing fine-tuning. The initial RET may not account for ...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.4.2 Potential requirements
REQ-RET-DATA-1: MDA capability for RET analysis shall include providing analytics for indicating the recommended change in RET and TP for a specific cell.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.4.3 Possible solutions
It is proposed to add a new MDA capability for RET and TP analysis. The MDAS Consumer submits an MDARequest, specifying the target cell(s) and the periodic interval at which data should be collected. MDAS Consumer receives the MDA Report for the RET_TPAnalytics. MDAS Producer collects the enabling data and generates th...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.4.4 Evaluation of solutions
The solution proposed in clause 5.3.4.3 satisfies the requirements and this solution is feasible for normative work.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.5 Use case 5: Interference Cell grouping analytics
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.5.1 Description
For several RAN automation capabilities, it is typically not possible to analyse the entire network with one instance of the automation function. The automation functions need to be configured with the scope of the RAN (the group of cells) for which the automation function should undertake its automation actions. E.g. ...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.5.2 Potential requirements
REQ-CellGRP-1: The MnS producer for MDA should include capability to provide analytics output on cell grouping for interference minimization.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.5.3 Potential solutions
To support analytics output on cell grouping: - Introduce a capability for "interference minimization cell grouping analytics" under the "Correlation analytics" MDA capabilities. The MDA type is: CorrelationAnalytics.InterferenceCellGroupingAnalysis: - The enabling data for CorrelationAnalytics. InterferenceCellGroup...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.5.4 Evaluation of solutions
The solution proposed in clause 5.3.5.3 satisfies the requirements and it is feasible for normative work.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.6 Use case 6: Consumer indication of preference requirements
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.6.1 Description
Multiple consumers of an MDA MnS may have differing requirements on the accuracy/goal/priority of analysis to be performed by MDA. Some consumers may require highly-accurate analysis reports and will accept if MDA expends time and energy to achieve the best results. Other consumers may require analysis to be performed ...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.6.2 Potential requirements
REQ-PREF_MDA-01: The MDA MnS producer should have the capability to allow authorized MDA MnS consumer to indicate preference requirements (e.g., time or constraints on resources) during the analysis.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.6.3 Potential solutions
It is proposed to add a new analysisRequirements attribute in the MDARequest IOC to indicate the preference requirements e.g. time or constraints on resources will be consumed for MDAS producer to create the MDAReport. While performing analysis, the MDA MnS producer may terminate the analysis early if the analysis res...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
5.3.6.4 Evaluation of solutions
The solution proposed in clause 5.3.6.3 satisfies the requirements and this solution is feasible for normative work.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
6 Conclusions and recommendations
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
6.1 Improvements to interoperability
No content was identified for this aspect of the study.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
6.2 Improvements to MDA framework
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
6.2.1 Integration of analytics with a network operator’s management system
The use case and solution for integration of analytics with a network operator’s management system are described in clause 5.2.1. It is recommended to update TS 28.567 [4] to clarify that only analytics are in scope of the MDA MnS producer. The detailed solution is described in clause 5.2.1.3.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
6.2.2 Indicating supported domain information in MDAFunction
The use case, requirements and solution for indicating supported domain information in MDAFunction are described in clause 5.2.2. It is recommended to update the MDAFunction IOC in TS 28.104 [2] to indicate the domain(s) supported by the MDAFunction. The detailed solution is described in clause 5.2.2.3.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
6.3 New and enhanced analytics capabilities
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
6.3.1 Enhance the Mobility performance analysis use case
The use case, requirements and solution for Enhance the Mobility performance analysis are described in clause 5.3.1. It is recommended to enhance the existing Mobility performance analysis capability in TS 28.104 [2] to analyse mobility issues in NSA deployments and to recommend optimization or repair actions. The deta...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
6.3.2 MDA assisted failure resolution
The use case, requirements and solution for MDA assisted failure resolution are described in clause 5.3.2. It is recommended to update TS 28.104 [2] to add a new MDA capability for network failure resolution. The detailed solution is described in clause 5.3.2.3.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
6.3.3 Radio resource optimization based on per SSB usage
The use case, requirements and solution for radio resource optimization based on per SSB usage are described in clause 5.3.3. It is recommended to update TS 28.104 [2] to add a new MDA capability for radio resource optimization analysis. The detailed solution is described in clause 5.3.3.3.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
6.3.4 Remote Electrical Tilt (RET) and Transmission Power analytics (TP)
The use case, requirements and solution for Remote Electrical Tilt and Transmission Power analytics are described in clause 5.3.4. It is recommended to update TS 28.104 [2] to add a new MDA capability for RET and TP analysis. The detailed solution is described in clause 5.3.4.3.
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
6.3.5 Interference Cell grouping analytics
The use case, requirements and solution for Interference Cell grouping analytics is described in clause 5.3.5. It is recommended for the normative work to enhance the existing correlation analytics capability in TS 28.104 [2] to support MDA analytics for Interference Cell grouping. The detailed solution is described in...
1d806e9df5fec2f4a64ca34ba2a402ee
28.886
6.3.6 Consumer indication of preference requirements
The use case, requirements and solution for consumer indication of required preference requirements are described in clause 5.3.6. It is recommended to enhance the existing MDARequest IOC in TS 28.104 [2] to allow the MDA MnS consumer to indicate preference requirements (e.g., time or constraints on resources). The det...
4f0bf3de05c8f2635add4d0daab5ffd7
28.889
1 Scope
The present document …
4f0bf3de05c8f2635add4d0daab5ffd7
28.889
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific. - For a specific reference, subsequent revisions do not apply. -...
4f0bf3de05c8f2635add4d0daab5ffd7
28.889
3 Definitions of terms, symbols and abbreviations
4f0bf3de05c8f2635add4d0daab5ffd7
28.889
3.1 Terms
For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. None.
4f0bf3de05c8f2635add4d0daab5ffd7
28.889
3.2 Symbols
For the purposes of the present document, the following symbols apply: None.
4f0bf3de05c8f2635add4d0daab5ffd7
28.889
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. None. 4. Use Cases
4f0bf3de05c8f2635add4d0daab5ffd7
28.889
4.1 Closed Control Loop for Network Maintenance
4f0bf3de05c8f2635add4d0daab5ffd7
28.889
4.1.1 Description
Network maintenance operations (e.g., software upgrades, downgrades, patching of network functions, license renewals, certificate renewals etc.) can significantly affect service continuity, performance, and user experience. Because of this, they need to be planned, validated, executed, and monitored with minimal disrup...
4f0bf3de05c8f2635add4d0daab5ffd7
28.889
4.1.2 Potential requirements
REQ-MaintenanceCCL -1: The 3GPP management system should have the capability to allow MnS consumer to instantiate a closed control loop for network maintenance delivering software updates REQ-MaintenanceCCL-2: The 3GPP management system should have the capability to allow MnS consumer to get a report from the closed c...