hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.2.1.1 Description
| Energy Consumption at network slice (as defined in TS 23.501 [8]) granularity is an essential information that 5GC NFs uses for further optimization. Energy consumption of a NetworkSlice is defined in TS 28.554 [4]. But NetworkSlice IOC is not equivalent to the network slice as defined in TS 23.501 [8]. Energy consumption KPI at network slice (as defined in TS 23.501 [8]) granularity is missing in TS 28.554 [4]. This use case is to study the inconsistencies and enhance or introduce KPIs to enable the 5GC NF requirements.
Further, the requirements for energy consumption monitoring at per network slice granularity is specified in clause 6.15a.4.2 of TS 22.261 [2]. Several solutions identified for the key issues in TR 23.700-67 [9] include 5GC NFs to collect slice level energy consumption and energy efficiency from 3GPP management system.
The network slice identifiers in the 3GPP network are defined in clause TS 23.501 [8] as: "An S-NSSAI identifies a Network Slice.". Further the standardized and non-standardized values of S-NSSAI are defined as " An S-NSSAI can have standard values (i.e. such S-NSSAI is only comprised of an SST with a standardised SST value, see clause 5.15.2.2 of TS 23.501 [8] and no SD) or non-standard values (i.e. such S-NSSAI is comprised of either both an SST and an SD or only an SST without a standardised SST value and no SD). An S-NSSAI with a non-standard value identifies a single Network Slice within the PLMN with which it is associated.".
The problem with the existing Network Slice related EC and EE KPIs are described below:
- Network Slice Energy Consumption (EC) KPI is specified in clause 6.7.3.3 of TS 28.554 [4]. This is reported at KPI object NetworkSlice IOC (defined in clause 6.2.1 of TS 28.541 [7]), while “network slice” in TS 23.501 [8] are identified using S-NSSAI and PLMN ID as described above.
- Network slice Energy Efficiency (EE) KPIs are specified in clause 6.7.2 of TS 28.554 [4]. This is reported at KPI object NetworkSlice IOC (defined in clause 6.2.1 of TS 28.541 [7]), while “network slice” in TS 23.501 [8] are identified using S-NSSAI and PLMN ID as described above.
- The NetworkSlice IOC is defined in clause 6.3.1 of TS 28.541 [7], with attribute serviceProfileList that holds a list of ServiceProfile (defined in clause 6.3.3 of TS 28.541 [7]) supported by the NetworkSlice MOI. ServiceProfile is a data type with attribute pLMNInfoList (a list of data type PLMNInfo defined in clause 4.3.41 of TS 28.541 [7]) that defines which PLMN and S-NSSAI combinations that are assigned for the service to satisfy service requirements represented by the ServiceProfile in case of network slicing feature is supported. A NetworkSlice MOI can be configured, in attribute serviceProfileList, with a list of ServiceProfile value, where the list can hold one or more than one element. Each element in the list attribute serviceProfileList can be configured with a list PLMN and S-NSSAI combinations in attribute pLMNInfoList. Hence a NetworkSlice MOI can be configured with a list of PLMN and S-NSSAI combinations.
This use case is to study the enhancements to support for energy consumption and energy efficiency monitoring, estimation and reporting at per network slice (as defined in TS 23.501 [8]) granularity.
Editor’s note: This use case could be updated subject to conclusions of SA2 study (FS_EnergySys_Ph2) in TR 23.700-67 [9].
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.2.1.2 Potential requirements
| PREQ-Energy_Reporting_Network_Slice-1: The 3GPP management system should be able to estimate and report the energy consumption at per network slice granularity.
PREQ-Energy_Reporting_Network_Slice-2: The 3GPP management system should be able to estimate and report the energy efficiency at per network slice granularity.
Editor’s note: The potential requirements in this clause could be updated subject to conclusions of SA2 study (FS_EnergySys_Ph2) in TR 23.700-67 [9].
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.2.1.3 Potential solutions
| 5.2.1.3.i Potential solution #<i>: <Potential Solution i Title>
5.2.1.3.i.1 Introduction
Editor's Note: This clause describes briefly the potential solution at a high-level.
5.2.1.3.i.2 Description
Editor's Note: This clause further details the potential solution, including all of its aspects and any assumptions made.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.2.1.4 Evaluation of potential solutions
| Editor's Note: This clause provides the evaluation of potential solutions listed in 5.2.1.3.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.2.2 Use case #<2>: Enhancements to 5GC NF Profile to support energy saving and energy efficiency
| |
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.2.2.1 Description
| Several solutions identified for the key issues in TR 23.700-67 [9] include enhancements to 5GC NF Profile (see TS 23.501 [8]) to support energy saving and energy efficiency.
5GC NF Profile related attributes are modelled in ManagedNFProfile data type (see clause 5.3.54 of TS 28.541 [7]).
This use case is to identify the enhancements to ManagedNFProfile data type to support the energy saving and energy efficiency in the 5GC.
Editor’s note: This use case could be updated subject to conclusions of SA2 study (FS_EnergySys_Ph2) in TR 23.700-67 [9].
Editor’s note: The proposals for enhancements to 5GC NF Profile in 5GC NRM should be based on the conclusions of SA2 study (FS_EnergySys_Ph2) in TR 23.700-67 [9].
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.2.2.2 Potential requirements
| PREQ-NFProfile_Energy_Conf-1: The 3GPP management system should be able to support energy saving and energy related configurations in the managed 5GC NF Profile.
Editor’s note: The potential requirements in this clause could be updated subject to conclusions of SA2 study (FS_EnergySys_Ph2) in TR 23.700-67 [9].
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.2.2.3 Potential solutions
| 5.2.2.3.i Potential solution #<i>: <Potential Solution i Title>
5.2.2.3.i.1 Introduction
Editor's Note: This clause describes briefly the potential solution at a high-level.
5.2.2.3.i.2 Description
Editor's Note: This clause further details the potential solution, including all of its aspects and any assumptions made.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.2.2.4 Evaluation of potential solutions
| Editor's Note: This clause provides the evaluation of potential solutions listed in 5.2.2.3.
5.2.X Use case #<X>: <Use case title>
5.2.X.1 Description
Editor’s note: This clause provides a description of the use case.
5.2.X.2 Potential requirements
Editor’s note: This clause captures potential requirements for the use case.
5.2.X.3 Potential solutions
5.2.X.3.i Potential solution #<i>: <Potential Solution i Title>
5.2.X.3.i.1 Introduction
Editor's Note: This clause describes briefly the potential solution at a high-level.
5.2.X.3.i.2 Description
Editor's Note: This clause further details the potential solution, including all of its aspects and any assumptions made.
5.2.X.4 Evaluation of potential solutions
Editor's Note: This clause provides the evaluation of potential solutions listed in 5.2.X.3.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.3 Improve energy saving, energy efficiency and reducing carbon footprint of 5G network
| 5.3.X Use case #<X>: <Use case title>
5.3.X.1 Description
Editor’s note: This clause provides a description of the use case.
5.3.X.2 Potential requirements
Editor’s note: This clause captures potential requirements for the use case.
5.3.X.3 Potential solutions
5.3.X.3.i Potential solution #<i>: <Potential Solution i Title>
5.3.X.3.i.1 Introduction
Editor's Note: This clause describes briefly the potential solution at a high-level.
5.3.X.3.i.2 Description
Editor's Note: This clause further details the potential solution, including all of its aspects and any assumptions made.
5.3.X.4 Evaluation of potential solutions
Editor's Note: This clause provides the evaluation of potential solutions listed in 5.3.X.3.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4 Enhancements to Energy Consumption and Energy Efficiency measurements and KPIs
| |
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.1 Use case #<1>: Renewable energy consumption
| |
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.1.1 Description
| The operators are interested in using renewable energy sources to reduce emissions and boost network efficiency. Therefore, it’s important to track and report the share of energy consumption from renewable sources in their networks.
Due to the highly variable and unpredictable nature of renewable energy sources, the supply of renewable energy varies substantially by time and location. There is a need for the 3GPP management system to support to report of renewable energy consumption on different granularities (e.g., NF, NE, Sub-network), and the total energy consumption considering energy consumption from energy supplies with renewable and non-renewable sources in order to estimate of renewable energy consumption, and to report the renewable energy consumption for different granularities.
Therefore, the 3GPP management system need to support to provide the renewable energy consumption based on energy related information obtained from various sources, or to provide the renewable energy consumption for different granularities, and support to report this information to authorized consumers, e.g., EIF.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.1.2 Potential requirements
| REQ-RECM-CON-1: The 3GPP management system shall be able to allow its authorized consumers to request reporting about renewable energy consumption at different granularities.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.1.3 Potential solutions
| 5.4.1.3.i Potential solution #<i>: <Potential Solution i Title>
5.4.1.3.i.1 Introduction
Editor's Note: This clause describes briefly the potential solution at a high-level.
5.4.1.3.i.2 Description
Editor's Note: This clause further details the potential solution, including all of its aspects and any assumptions made.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.1.4 Evaluation of potential solutions
| Editor's Note: This clause provides the evaluation of potential solutions listed in 5.4.1.3.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.2 Use case #<2>: Support EC measurement of NE at per Energy Supply granularity
| |
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.2.1 Description
| Network Elements can be powered using multiple energy supplies (grid, backup energy, locally generated energy). The Network Element consumes energy from different energy supplies during different periods of time based on various conditions in the operator network. The 3GPP management system needs to measure and report energy consumption separately for each energy supply to calculate accurate carbon emissions. The operator configures the system to associate each energy supply. The operator and the internal optimization need the 3GPP management system to collect EC data per energy supply and report them.
The existing energy consumption measurements are based on PEE measurements and assume a single energy supply for the NE (represented by ManagedElement) and do not provide energy consumption related information at the energy supply granularity. This use case identifies the existing measurements and studies the enhancements that need to be supported.
Energy supply information can be associated with the Managed Elements (representing the Network Elements) using EnergyInfoGroup IOC (see clause 8.3.3. of TS 28.310 [3]). Energy-related information for each energy source (see EnergySourceInfo defined in clause 8.3.2 of TS 28.310 [3]) of the energy supply (see EnergySupplyInfo defined in clause 8.3.1 of TS 28.310 [3]) includes information of different energy source, with source type, carbon emission factor, renewable and non-renewable energy information.
Power, Energy and Environmental (PEE) measurements are defined in clause 5.1.1.19 of TS 28.552 [10], and PNF Energy consumption for ManagedElement is defined in clause 5.1.1.19.3 of TS 28.552 [10].
Energy consumption related KPIs are defined in clause 6.7.3 of TS 28.554 [4]. gNB Estimated Carbon Emission and NG-RAN Estimated Carbon Emission KPIs are defined in clause 6.7.7 of TS 28.554 [4]. A Network Element (represented by Managed Element) can be powered by one or more energy supplies (see TS 28.310 [3]). The Carbon Emission related KPIs defined in TS 28.554 [4] are currently restricted to the scenarios when a Network Element is powered by a single energy supply. This limitation is due to the lack of EC measurements at a per energy supply granularity for a Network Element.
Energy consumption of a Network Element is essential for monitoring and reporting of carbon emissions, carbon intensity, and network energy optimization use cases considering energy supply mix, and energy-related characteristics (defined in TS 22.261 [2]).
This use case is to study the enhancements to enable measurements and reporting of EC of a Network Element at a per energy supply granularity.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.2.2 Potential requirements
| PREQ-Energy_Consumption-1: The 3GPP management system should be able to measure and report the energy consumption of a Network Element at a per energy supply granularity.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.2.3 Potential solutions
| 5.4.2.3.i Potential solution #<i>: <Potential Solution i Title>
5.4.2.3.i.1 Introduction
Editor's Note: This clause describes briefly the potential solution at a high-level.
5.4.2.3.i.2 Description
Editor's Note: This clause further details the potential solution, including all of its aspects and any assumptions made.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.2.4 Evaluation of potential solutions
| Editor's Note: This clause provides the evaluation of potential solutions listed in 5.4.2.3.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.3 Use case #<3>: Support estimation of EC and EE KPIs at per PLMN-ID granularity in Network sharing scenario
| |
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.3.1 Description
| When a NG-RAN is shared between multiple operators in the network sharing (see TS 32.130 [11]), the participating operators are interested in the operator-specific energy consumption (EC) and energy efficiency (EE) of the NG-RAN.
The NG-RAN can support and serve multiple operators (i.e., PLMN-IDs) in Network sharing scenarios. The existing EE and EC KPIs do not consider network sharing scenarios, and do not provide KPIs at operator-specific (i.e., PLMN-ID) granularity.
Following are the currently supported measurements and KPIs related to energy consumption and energy efficiency:
• Power, Energy and Environmental (PEE) measurements are defined in clause 5.1.1.19 of TS 28.552 [10], and PNF Energy consumption for ManagedElement is defined in clause 5.1.1.19.3 of TS 28.552 [10].
• Energy consumption and energy efficiency related KPIs are defined in clause 6.7 of TS 28.554 [4].
This use case is to study the enhancements to enable monitoring and/or estimation of energy consumption and energy efficiency KPIs and reporting of a NG-RAN at operator-specific (i.e., at a per PLMN-ID) granularity in network sharing scenarios.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.3.2 Potential requirements
| PREQ-Energy_Consumption_Network_Sharing-1: The 3GPP management system should be able to report the energy consumption and energy efficiency of a NG-RAN at operator-specific, i.e., at a per PLMN-ID granularity.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.3.3 Potential solutions
| 5.4.3.3.i Potential solution #<i>: <Potential Solution i Title>
5.4.3.3.i.1 Introduction
Editor's Note: This clause describes briefly the potential solution at a high-level.
5.4.3.3.i.2 Description
Editor's Note: This clause further details the potential solution, including all of its aspects and any assumptions made.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.3.4 Evaluation of potential solutions
| Editor's Note: This clause provides the evaluation of potential solutions listed in 5.4.3.3.
5.4.X Use case #<X>: <Use case title>
5.4.X.1 Description
Editor’s note: This clause provides a description of the use case.
5.4.X.2 Potential requirements
Editor’s note: This clause captures potential requirements for the use case.
5.4.X.3 Potential solutions
5.4.X.3.i Potential solution #<i>: <Potential Solution i Title>
5.4.X.3.i.1 Introduction
Editor's Note: This clause describes briefly the potential solution at a high-level.
5.4.X.3.i.2 Description
Editor's Note: This clause further details the potential solution, including all of its aspects and any assumptions made.
5.4.X.4 Evaluation of potential solutions
Editor's Note: This clause provides the evaluation of potential solutions listed in 5.4.X.3.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 6 Conclusions and recommendations
| |
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 6.1 Enhancements to support energy efficiency as a service criteria
| Editor’s Note: This clause is to summarize the identified use cases and to add conclusions and recommendations for a potential Work Item.
6.1.x Use case #<X>: <Use case title>
Editor’s note: This clause captures conclusions and recommendations for the use case.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 6.2 Enhancements to support the information required by Energy Information Function (EIF)
| 6.2.x Use case #<X>: <Use case title>
Editor’s note: This clause captures conclusions and recommendations for the use case.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 6.3 Improve energy saving, energy efficiency and reducing carbon footprint of 5G network
| 6.3.x Use case #<X>: <Use case title>
Editor’s note: This clause captures conclusions and recommendations for the use case.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 6.4 Enhancements to Energy Consumption and Energy Efficiency measurements and KPIs
| 6.4.x Use case #<X>: <Use case title>
Editor’s note: This clause captures conclusions and recommendations for the use case.
Annex A:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
-
N/A
-
-
-
TR skeleton
0.0.0
2025-10
SA5#163
S5-254683
pCR
-
-
pCR on Rel-20 TR 28.885 Add TR structure
0.1.0
2025-10
SA5#163
S5-254698
pCR
-
-
pCR on Rel-20 TR 28.885 Add new use case support of energy-related characteristics
0.1.0
2025-10
SA5#163
S5-254699
pCR
-
-
pCR on Rel-20 TR 28.885 Add new use case related to service adjustments to adapt to energy-related characteristics
0.1.0
2025-10
SA5#163
S5-254700
pCR
-
-
Rel-20 pCR TR 28.885 Add New Use Case on Energy Rationing management
0.1.0
2025-10
SA5#163
S5-254736
pCR
-
-
pCR TR 28.885 Add use case and requirements for renewable energy consumption
0.1.0
2025-10
SA5#163
S5-254738
pCR
-
-
pCR on Rel-20 TR 28.885 Add new use case for enhancements to reporting EC and EE at per network slice granularity
0.1.0
2025-10
SA5#163
S5-254739
pCR
-
-
pCR on Rel-20 TR 28.885 Add new use case to study Enhancements to NF Profile to support energy saving and energy efficiency
0.1.0
2025-10
SA5#163
S5-254740
pCR
-
-
pCR on Rel-20 TR 28.885 Add new use case to study measuring of EC of NE at per Energy Supply granularity
0.1.0
2025-10
SA5#163
S5-254741
pCR
-
-
pCR on Rel-20 TR 28.885 Add new use case to study EC and EE per PLMNID in Network sharing scenario
0.1.0
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.1.1 Use case #1: Enhancements to support the energy-related characteristics for Network Elements and Network Functions
| |
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.1.2 Use case #2: Management mechanisms to support service adjustments to adapt to energy-related characteristics and energy rationing
| |
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.1.3 Use case #3: Energy Rationing Information Management
| |
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.2.1 Use case #1: Energy consumption and Energy Efficiency estimation and reporting at per network slice granularity
| |
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.2.2 Use case #2: Enhancements to 5GC NF Profile to support energy saving and energy efficiency
| |
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.1 Use case #1: Renewable energy consumption
| |
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.2 Use case #2: Support EC measurement of NE at per Energy Supply granularity
| |
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.4.3 Use case #3: Support estimation of EC and EE KPIs at per PLMN-ID granularity in Network sharing scenario
| |
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 1 Scope
| The present document …
|
17e7b95120f7e2c9a95a2c397fc59767 | 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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 28.104: "Management Data Analytics (MDA)".
[3] 3GPP TS 28.541: "5G Network Resource Model (NRM); Stage 2 and stage 3".
[4] 3GPP TS 28.567: "Management aspects of closed control loops".
|
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 3 Definitions of terms, symbols and abbreviations
| |
17e7b95120f7e2c9a95a2c397fc59767 | 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].
example: text used to clarify abstract rules by applying them literally.
|
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
17e7b95120f7e2c9a95a2c397fc59767 | 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
SN Secondary Node
NSA Non-standalone
|
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 4 Concept and background
| |
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5 Use cases
| |
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.1 Improvements to interoperability
| 5.1.X Use case X: Use case title
5.1.X.1 Description
5.1.X.2 Potential requirements
5.1.X.3 Potential solutions
5.1.X.4 Evaluation of solutions
|
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.2 Improvements to MDA framework
| |
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.2.1 Use case 1: Integration of analytics with a network operator’s management system
| |
17e7b95120f7e2c9a95a2c397fc59767 | 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 management functions and/or management services, and if these dependencies are mandatory or optional.
The operator uses TS 28.104 [2] to learn the required information about MDAS. Clause 5 of TS 28.104 [2] describes the management facilities which are provided by MDAS. Clause 5 of TS 28.104 [2] describes how MDAS may be combined with other 3GPP management functions and/or management services to satisfy NOP requirements.
Currently, clause 5 of TS 28.104 [2] is lacking description on how MDAS relates to some 3GPP management functions and/or management services (e.g. CCL, NDT). The current description is very abstract and may benefit from adding examples. The current description may also conflict with the content of other technical specifications.
|
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.2.1.2 Potential requirements
| None.
|
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.2.1.3 Potential solutions
| |
17e7b95120f7e2c9a95a2c397fc59767 | 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 decision making.
It is proposed to update TS 28.567 [4] figure 5.1.2.2-1, figure 5.1.2.2-2 and associated text to clarify that only analytics are in scope of the MDA MnS producer.
|
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.2.1.4 Evaluation of solutions
| |
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.2.2 Use case 2: Indicating supported domain information in MDAFunction
| |
17e7b95120f7e2c9a95a2c397fc59767 | 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 the support MDA capabilities but also to identify in which domains the MDA Function is supported for corresponding analysis. For example, an MnS consumer may wish to perform analytic for CN, while the MDA producer is only capable to provide report for RAN. There is no way to identify the capability of the MDA producer in advance, and no way to report why the producer cannot satisfy the request.
Currently, in clause 9.3.1.2 in 28.104 [2] the definition of MDAFunction IOC, only contains supportedMDACapabilities attribute without domain information. This makes a MnS consumer difficult to know the actual analysis scope of a MDAFunction.
|
17e7b95120f7e2c9a95a2c397fc59767 | 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.
|
17e7b95120f7e2c9a95a2c397fc59767 | 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.
|
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.2.2.4 Evaluation of solutions
| |
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.3 Investigate new and enhanced analytics related capabilities
| |
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.3.1 Use case 1: Enhance the Mobility performance analysis use case
| |
17e7b95120f7e2c9a95a2c397fc59767 | 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 mobility performance analysis is described in TS 28.104 [2]. This analysis output includes information such as mobility issue root cause, mobility issue location. The descriptions and requirements in the existing use cases also mention performance analysis under NSA deployment scenarios. However, the current solution does not provide additional information (e.g. mobility issue type such as NSA mobility issue and SA mobility issue, or the root cause of NSA mobility issue, or the recommended actions) which may enable the consumer to anticipate the impacts to the network more effectively.
The mobility performance related problems in NSA deployment scenarios may result from too-early/too-late PSCell change or too-early/too-late conditional PSCell addition or change due to inappropriate handover parameters as defined in TS 38.300 [x]. Performance measurements related to NSA need to be defined and used as enabling data for MDA analysis. MDAS can be used to analyse network performance during handover period in different mobility scenarios. The MDAS producer may also be capable to provide the recommendations of optimal handover parameters to MDAS consumer.
Correspondingly, the root cause of mobility issue in NSA deployment scenarios may be of interest to the consumer and can be provided in the analytics report. The root cause can be high interference in both uplink and downlink, wireless resource issues (such as high utilization of uplink and downlink PRBs), transport layer reasons (including insufficient transport resources leading to SN addition failure, such as S1 interface transport, X2 interface transport), and UE capability issues.
|
17e7b95120f7e2c9a95a2c397fc59767 | 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 recommended actions to solve the mobility performance issue.
|
17e7b95120f7e2c9a95a2c397fc59767 | 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 following:
- SN addition related performance measurements.
- SN change related performance measurements.
- Conditional SN addition related performance measurements
- Conditional SN change related performance measurements
The analytics output for this MDA type would include the following:
- The mobility performance issue type including NSA mobility issue and SA mobility issue
- The mobility performance issue including too-early handovers, too-late handovers and ping-pong handovers, too-early PSCell change, too-late PSCell change, too late CPC Execution and too early CPC/CPA execution.
- The mobility performance issue root case can be such as high interference, insufficient transport resources, UE capability issues etc.;
- The recommended actions to resolve the mobility issue (e.g. change the mobility parameters (e.g. CIO) or antenna RF parameters such as downtilt and azimuth etc.).
NOTE: The NSA mobility measurements are subject to be defined in TS 28.552 (FFS).
|
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.3.1.4 Evaluation of solutions
| TBD
|
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.3.2 Use case 2: MDA assisted failure resolution
| |
17e7b95120f7e2c9a95a2c397fc59767 | 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 identification and resolution of network failures, thereby increasing the stability of the network. This use case enables an MDAS consumer (e.g. an automated trouble ticketing system) to automatically perform the steps needed to resolve a network failure.
The MDAS consumer requests the MDAS producer to identify alarms which may relate to network failures. The MDAS producer analyses alarm data and network data to correlate alarms with deteriorating performance in the network. The MDAS producer analyses the cause of deteriorating performance. The MDAS producer reports possible network failures and the possible cause to the MDAS consumer.
The MDAS consumer requests the MDAS producer to diagnose the cause of a network failure. The MDAS producer performs analysis to locate the likely cause of the network failure (e.g. network function, virtualized resource, physical resource). The MDAS producer reports the possible cause of the network failure to the MDAS consumer.
The MDAS consumer requests the MDAS producer to recommend how to resolve a network failure. The MDAS producer performs analysis to identify which domain is causing the network failure. The MDAS producer calculates possible methods (e.g. re-configurations) to resolve the network failure. The MDAS producer simulates or emulates the effect of the possible methods (e.g. by using NDT) to evaluate if the network failure is resolved. The MDAS producer reports the possible methods to the MDAS consumer.
|
17e7b95120f7e2c9a95a2c397fc59767 | 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 recommended actions to resolve the network failure.
|
17e7b95120f7e2c9a95a2c397fc59767 | 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) which are likely to be correlated to the network failure
- managed objects (e.g. NFs, cells) that are impacted by the network failure
- metrics or KPIs that are impacted by the network failure
- probable impacted domain and cause of the network failure
- recommended actions to resolve the network failure
- estimated time to resolve the network failure
|
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.3.2.4 Evaluation of solutions
| |
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.3.3 Use case 3: Radio resource optimization based on per SSB usage
| |
17e7b95120f7e2c9a95a2c397fc59767 | 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 different patterns, corresponding to the number of SSB beams and their distinct directions.
In Clause 4.3.39 of TS 28.541[3], <<IOC>>CommonBeamformingFunction is defined to represents common beamforming functionality (eg: SSB beams). The CommonBeamformingFunction provides capability to configure the advanced antenna for a sector carrier. The configuration capability is provided by selection of coverageShape, digitalTilt and digitalAzimuth. These attributes represent the wanted coverage area and radiation pattern on a sector carrier related to an antenna transmission point.
For example, the area where a large outdoor stadium holds some competitions is characterized by a high number of users which is challenging to guarantee enough radio resource in this scenario. It is necessary to consider using MDAS to improve radio resource usage. MnS consumer could request MDAS to acquire beam-level management data and recommend coverage shape based on analysis. The beam-level data includes Number of UE related the SSB beam Index (mean), DL PRB Usage per SSB, etc. The recommendation could be used for 3GPP Management System to update the configuration of the target cell's coverage shape on gNodeB.
Figure 5.3.3.1-1 depicts SSB beams covering full cell coverage area. Figure 5.3.3.1-2 depicts SSB beams modifying to meet the UE centralized coverage after updating the coverage shape for target cell of gNodeB using the recommendation by MDAS.
It is anticipated that MDAS can be used to obtain an analysis of the usage of each SSB. This information can then be used to adjust the coverage shape.
Figure 5.3.3.1-1: Illustration of SSB beams covering full cell coverage area
Figure 5.3.3.1-2: Illustration of SSB beams modifying to meet the UE centralized coverage with MDAS recommendation
|
17e7b95120f7e2c9a95a2c397fc59767 | 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 beam-level management data analytics.
REQ-RRO-FUN-03: MDA capability for radio resource optimization analysis should include the capability to recommend coverage shape configuration for target cell of gNodeB.
5.3.3.3 Potential solutions
TBD
|
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.3.3.4 Evaluation of solutions
| TBD
|
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.3.4 Use case 4: Remote Electrical Tilt (RET) and Transmission Power analytics (TP)
| |
17e7b95120f7e2c9a95a2c397fc59767 | 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 changes in subscriber movement or infrastructure developments. Factors influencing optimal RET and power can evolve over time, including:
Subscriber Movement: Dynamic changes in user behavior, such as daily commutes from office to home or weekend outings to recreational areas, can impact network performance requiring the modification in the RET.
Infrastructure Growth: The addition of new cell sites can introduce interference with neighboring cells. Interference arises when signals from the new site overlap with or disrupt existing signals. This would affect performance and can be mitigated with modification in the RET.
Weather Conditions: Atmospheric phenomena like rain, snow, and fog can affect radio wave propagation, leading to signal attenuation or distortion. Tilt modification may minimize the impact.
It is desirable to use MDA analytics to generate optimal RET and power configuration over time. It is essential to follow initial antenna RET deployment with subsequent fine-tuning using MDA analytics. The producer employs a machine learning-based model that leverages strong correlations between performance, fault and configuration data of the network. This ML model analyzes the impacts of coverage and interference in relation to user traffic behavior, including mobility and weather conditions. It generates recommendations for fine-tuning RET and optimizing transmission power per cell.
|
17e7b95120f7e2c9a95a2c397fc59767 | 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.
|
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.3.4.3 Possible solutions
| TBD
|
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 5.3.4.4 Evaluation of solutions
| TBD
|
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 6 Conclusions and recommendations
| |
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 6.1 Improvements to interoperability
| |
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 6.2 Improvements to MDA framework
| |
17e7b95120f7e2c9a95a2c397fc59767 | 28.886 | 6.3 New and enhanced analytics capabilities
| Annex A (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
Initial skeleton
0.0.0
2025-08
SA5#162
S5‑253605
pCR
Pseudo-CR on TR 28.886 Add clause structure
0.1.0
2025-08
SA5#162
S5‑254044
pCR
Pseudo-CR on TR 28.886 Enhance the mobility performance analysis use case
0.1.0
2025-08
SA5#162
S5‑254045
pCR
Pseudo-CR on TR 28.886 Add MDA integration use case
0.1.0
2025-08
SA5#162
S5‑254046
pCR
Pseudo-CR on TR 28.886 Add failure resolution use case
0.1.0
2025-10
SA5#163
S5‑254687
pCR
Pseudo-CR on TR 28.886 Add solution for enhance the mobility performance analysis use case
0.2.0
2025-10
SA5#163
S5‑254684
pCR
Pseudo-CR on TR 28.886 Add new use case on domain information for MDAFunction
0.2.0
2025-10
SA5#163
S5‑254685
pCR
Rel-20 pCR TR 28.886 Add new use case on radio resource optimization based on per SSB usage
0.2.0
2025-10
SA5#163
S5‑254686
pCR
Rel-20 pCR 28.886 RET Analytics
0.2.0
2025-10
SA5#163
S5‑254688
pCR
Pseudo-CR on TR 28.886 Add requirements and solution for failure resolution
0.2.0
2025-10
SA5#163
S5‑254782
pCR
Pseudo-CR on TR 28.886 Add solution for MDA scope
0.2.0
|
8d2f6f763f71e88f74e01c5dff104898 | 28.889 | 1 Scope
| The present document …
|
8d2f6f763f71e88f74e01c5dff104898 | 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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
…
[x] <doctype> <#>[ ([up to and including]{yyyy[-mm]|V<a[.b[.c]]>}[onwards])]: "<Title>".
[X2] 3GPP TS 28.567: "Management and orchestration; Management aspects of closed control loops"
[Y3] 3GPP TS 28.312: "Management and orchestration; Intent driven management services for mobile networks"
[Z] 3GPP TS 28.104: "Management and orchestration; Management Data Analytics (MDA) "
|
8d2f6f763f71e88f74e01c5dff104898 | 28.889 | 3 Definitions of terms, symbols and abbreviations
| |
8d2f6f763f71e88f74e01c5dff104898 | 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].
example: text used to clarify abstract rules by applying them literally.
|
8d2f6f763f71e88f74e01c5dff104898 | 28.889 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
8d2f6f763f71e88f74e01c5dff104898 | 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].
<ABBREVIATION> <Expansion>
4. Use Cases
4.X1 Use case#X1: Closed Control Loop for Network Maintenance
4.X1.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 disruption. CCLs can help in assisting and automating the maintenance operations, in particular when maintenance needs to be performed in complex scenarios with multiple network functions with dependencies among them, in a large-scale network deployment.
This use case describes a scenario in which an MnS consumer requests a CCL for network maintenance, for example, a software upgrade, to achieve automation for network maintenance. The request may include the type of maintenance required ( e.g., software upgrade, software downgrade), target version for maintenance, any constraints for maintenance (e.g., time-window when the maintenance should take place), as well as any policies required for network maintenance the order of NFs for maintenance, whether isolation of NFs is required for network maintenance work, etc.
The intent-driven MnS producer may be MnS consumer of a Network Maintenance CCL MnS producer if the intent-driven MnS producer handles a Network Maintenance Expectation as specified in 3GPP TS 28.312 [3Y], clause 6.2.2.1.6.
A CCL for network maintenance may also use MDA reports in 3GPP TS 28.104 [Z4], for example, for the maintenance use-cases described in clause 7.2.6, to decide and execute necessary actions for network maintenance. A CCL for network maintenance may also analyse the impact of requested software update, for example, the impact of upgrading an NF software version. CCL for network maintenance delivering software updates may also coordinate with Conflict Management Aand Coordination Entity as specified in TS 28.567 [2X], clause 6.3.6 whether requested network maintenance cause any conflicts to existing operations. Based on the analysis, CCL may execute required actions to deliver software updates or execute a rollback in case software updates negatively impact operations.
The CCL for network maintenance MnS producer reports the result of network maintenance, including the resultant maintenance and any other relevant information.
4.X1.2 Potential requirements
REQ-MaintenanceCCL -1: The 3GPP management system should have the capability to allow MnS consumer to request 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 control loop regarding the network maintenance delivering software updates.
4.X1.3 Potential solutions
TBD
4.x2 CCL for network capacity optimization
4.x2.1 Description Use cases
Celllular networks have multiple managed objects (existing in RAN, CN and OAM) running together to fulfill the required services. This group of managed objects (MO) need to be monitored to check if the existing capacity of the object is enough for the current or near future demands. Network monitoring mechanisms are used to monitor the network and then manage the availiable capacity of the network. For example, if the current trends suggest the increase of traffic at a UPF in near future, an additional instance of the UPF is created to cater for the increasing traffic demand. CCL can be used to automate this process and optimize the available capacity of the network.
4.x2.2 Potential requirements
REQ-NET-CAP-1: The 3GPP management system should support a capability allowing an authorized MnS Consumer to request for optimization of available network capacity.
4.x2.3 Possible solutions
TBD
X4.Y3 Use case Y: Automated status monitoring
X4.Y3.1 Description
This use case describes a scenario in which an MnS consumer may request a CCL for continuous monitoring of the network status and resolution of any detected issues. The MnS consumer may request to monitor the status of a complete network or a specific subset of the network.
Based on the request, the MnS producer creates a CCL instance. At regular intervals, the CCL instance collects alarm data and performance data from the network. The CCL instance analyses the collected data for indications of possible faults or possible performance problems.
If the analysis indicates a possible fault or a possible performance problem, the CCL instance may decide on a solution for the issue and execute the solution. The MnS producer may provide a report on issues that have been detected and the actions that were executed to resolve the issues.
X4.3Y.2 Potential requirements
X4.Y3.3 Potential solutions
X4.Y3.4 Evaluation of solutions
Annex <X>:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
-
n/a
-
-
-
Initial skeleton
0.0.0
2025-10
SA5#163
S5‑254702
S5‑254885
S5‑254704
pCR
-
-
pCR on Rel-20 TR 28.889 Add use case description and requirement for Network Maintenance CCL
Rel-20 pCR 28.889 CCL for LCM
Pseudo-CR on TR 28.889 Add status monitoring use case
0.1.0
|
8d2f6f763f71e88f74e01c5dff104898 | 28.889 | 4.1 Use case1: Closed Control Loop for Network Maintenance
| |
8d2f6f763f71e88f74e01c5dff104898 | 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 disruption. CCLs can help in assisting and automating the maintenance operations, in particular when maintenance needs to be performed in complex scenarios with multiple network functions with dependencies among them, in a large-scale network deployment.
This use case describes a scenario in which an MnS consumer requests a CCL for network maintenance, for example, a software upgrade, to achieve automation for network maintenance. The request may include the type of maintenance required ( e.g., software upgrade, software downgrade), target version for maintenance, any constraints for maintenance (e.g., time-window when the maintenance should take place), as well as any policies required for network maintenance the order of NFs for maintenance, whether isolation of NFs is required for network maintenance work, etc.
The intent-driven MnS producer may be MnS consumer of a Network Maintenance CCL MnS producer if the intent-driven MnS producer handles a Network Maintenance Expectation as specified in 3GPP TS 28.312 [3], clause 6.2.2.1.6.
A CCL for network maintenance may also use MDA reports in 3GPP TS 28.104 [4], for example, for the maintenance use-cases described in clause 7.2.6, to decide and execute necessary actions for network maintenance. A CCL for network maintenance may also analyse the impact of requested software update, for example, the impact of upgrading an NF software version. CCL for network maintenance delivering software updates may also coordinate with Conflict Management and Coordination Entity as specified in TS 28.567 [2], clause 6.3.6 whether requested network maintenance cause any conflicts to existing operations. Based on the analysis, CCL may execute required actions to deliver software updates or execute a rollback in case software updates negatively impact operations.
The CCL for network maintenance MnS producer reports the result of network maintenance, including the resultant maintenance and any other relevant information.
|
8d2f6f763f71e88f74e01c5dff104898 | 28.889 | 4.1.2 Potential requirements
| REQ-MaintenanceCCL -1: The 3GPP management system should have the capability to allow MnS consumer to request 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 control loop regarding the network maintenance delivering software updates.
|
8d2f6f763f71e88f74e01c5dff104898 | 28.889 | 4.1.3 Potential solutions
| TBD
|
8d2f6f763f71e88f74e01c5dff104898 | 28.889 | 4.2 CCL for network capacity optimization
| |
8d2f6f763f71e88f74e01c5dff104898 | 28.889 | 4.2.1 Description
| Cellular networks have multiple managed objects (existing in RAN, CN and OAM) running together to fulfill the required services. This group of managed objects (MO) need to be monitored to check if the existing capacity of the object is enough for the current or near future demands. Network monitoring mechanisms are used to monitor the network and then manage the available capacity of the network. For example, if the current trends suggest the increase of traffic at a UPF in near future, an additional instance of the UPF is created to cater for the increasing traffic demand. CCL can be used to automate this process and optimize the available capacity of the network.
|
8d2f6f763f71e88f74e01c5dff104898 | 28.889 | 4.2.2 Potential requirements
| REQ-NET-CAP-1: The 3GPP management system should support a capability allowing an authorized MnS Consumer to request for optimization of available network capacity.
|
8d2f6f763f71e88f74e01c5dff104898 | 28.889 | 4.2.3 Possible solutions
| TBD
|
8d2f6f763f71e88f74e01c5dff104898 | 28.889 | 4.3 Use case Y: Automated status monitoring
| |
8d2f6f763f71e88f74e01c5dff104898 | 28.889 | 4.3.1 Description
| This use case describes a scenario in which an MnS consumer may request a CCL for continuous monitoring of the network status and resolution of any detected issues. The MnS consumer may request to monitor the status of a complete network or a specific subset of the network.
Based on the request, the MnS producer creates a CCL instance. At regular intervals, the CCL instance collects alarm data and performance data from the network. The CCL instance analyses the collected data for indications of possible faults or possible performance problems.
If the analysis indicates a possible fault or a possible performance problem, the CCL instance may decide on a solution for the issue and execute the solution. The MnS producer may provide a report on issues that have been detected and the actions that were executed to resolve the issues.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.