hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 4.3 Message Bus principles integrated in SBMA
| Message Bus principles
A Message Bus is a middleware architecture that enables different systems or services to communicate through a shared messaging infrastructure in a decoupled way. Key principles include the following:
• Loose Coupling: Services interact without knowing each other’s internal details. Enhance... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5 Use cases and potential solutions
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.1 Use case #1: Integration of SBMA with 5GC and 5G Access Network architecture
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.1.1 Description
| In a 5G Advanced network deployment, a mobile operator adopts an SBMA that leverages a modular reference model as defined in annex A.11 of TS 28.533 [YY]. This model abstracts Management Functions (MnFs) as logical entities, independent of their physical implementation, and enables them to interact exclusively through ... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.1.2 Potential requirements
| REQ-SBMA-ARM-1: SBMA should provide a consolidated view of management architecture.
|
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.1.3 Potential solutions
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.1.4 Evaluation of potential solutions
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.2 Use case #2: Management data streaming based on Message Bus
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.2.1 Description
| The 5G network employs a distributed, service-oriented architecture, leading to scenarios where multiple consumers request the same management data for multiple uses. In a typical network performance data reporting scenario, an MnS producer collects and transmits performance data to multiple MnS consumers within the ne... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.2.2 Potential requirements
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.2.3 Potential solutions
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.2.3.1 Solution #1: Multipoint-to-Multipoint management data streaming based on message broking MnF
| This potential solution proposes introduction of a new MnF implementing the message broker(s) that mediates data with the help of new MnS services, namely, message bus data reporting MnS and message bus data retrieval MnS (for data subscribers) to enable multipoint-to-multipoint streaming data reporting. This solution ... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.2.4 Evaluation of potential solutions
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.3 Use case #3: Historical alarms
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.3.1 Description
| The "AlarmList" defined in TS 28.111 [10] contains "AlarmRecords" that represent currently active alarms. Alarms, that are cleared and acknowledged (inactive alarms) are removed from the alarm list and cannot be retrieved any more by MnS consumers.
However, old inactive alarms (historical alarms) are a valuable source... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.3.2 Potential requirements
| REQ-1: The 3GPP Management system should have the capability allowing to retrieve alarms that were active in the past (historical alarms).
REQ-2: The 3GPP Management system should have the capability allowing to retrieve alarms that were active at a certain point in time in the past.
REQ-3: The 3GPP Management system... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.3.3 Potential solutions
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.3.3.1 NRM based approach
| The NRMs defined by SA5 are a representation of the current state of the managed system. They do not represent states before the current time. Reading the data node tree always returns its current state.
For retrieving historical alarms two methods can be envisaged:
- A new retrieval operation can be introduced with ... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.3.3.2 Management data based approach
| The alarm records are handled as a specific kind of management data, like performance metrics or Trace and MDT data. The MnS allowing to retrieve active alarms (based on the "AlarmList" object) is not modified.
More specifically, the schema of the alarm record is used to specify the value of a new management data cate... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.4 Use case#4 on software management for 5G
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.4.1 Description
| 3GPP TS 32.531 [11], TS 32.532 [12], and TS 32.533 [13] define the concepts, requirements, Information Service, and CORBA solution set for the software management of NEs for 4G, encompassing both automated and non-automated software management approaches.
Software management for 5G enhances 5G network operational effi... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.4.2 Potential requirements
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.4.2.1 Potential general requirements
| REQ-SBMA-SWM-1: The 3GPP management system should support software management.
|
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.4.2.2 Potential requirements for PNF
| REQ-SBMA-PNFSWM-1: The 3GPP management system shall support the capability to download SW to the MnS producer.
REQ-SBMA-PNFSWM-2 The 3GPP management system shall support the capability to activate the new SW, that is to start running it by bringing it into service
REQ-SBMA-PNFSWM-3: The 3GPP management system shall s... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.4.2.3 Potential requirements for VNF
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.4.3 Potential solutions
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.4.4 Evaluation of potential solutions
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.5 Use case#5 on inventory management for 5G
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.5.1 Description
| 3GPP TS 28.631 [14], TS 28.632 [15], and TS 28.633 [16] define the requirements, Information Service definitions, and XML solution set for inventory management. These specifications cover inventory information of NEs, including hardware, software, licences, Tower Mounted Amplifiers (TMAs) and antennas.
The benefits of... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.5.2 Potential requirements
| REQ-SBMA-IM-1: The 3GPP management system should support inventory management.
REQ-SBMA-IM-2: The 3GPP management system should support inventory management for hardware.
|
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.5.3 Potential solutions
| Though the scope of TS 28.631 [14]/TS 28.632 [15] is limited to the communication between IRPAgent and IRPManager, the content of the inventory NRMs defined in TS 28.632 [15] can be reused to support inventory management for hardware. This solution addresses REQ-SBMA-IM-1 and REQ-SBMA-IM-2 in clause 5.5.2 and proposes ... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.5.4 Evaluation of potential solutions
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.6 Use case #6: Merge operation
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.6.1 Description
| The changeMOIs operation and the notifyMOIChanges notification (as described in TS 28.532[12]) both support multiple operation types, defined by the "modifyOperator" in changeMOIs and as "op" in notifyMOIChanges. These operations are optimized for handling individual data nodes e.g. replacing a full object with all its... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.6.2 Potential requirements
| REQ-MERGE-1: Add a simple solution for indicating the update of multiple attributes of multiple MOIs with a single notification while minimizing the need for parsing long "path" parameters.
|
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.6.3 Potential solutions
| Two separate solutions are proposed for the problems described in clause 5.6.1.1 and 5.6.1.2.
a) Describe the merge operation for the changeMOIs operation on stage-2 in 28.532[12].
Note: Exact details of merge shall not be described on stage-2 as they are solution set specific and already described in RFC 6241[19] ... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.6.4 Evaluation of potential solutions
| TBD
|
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.7 Use case#7: MnS selection in distributed deployment scenarios for SBMA
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.7.1 Description
| 3GPP management system introduce Service-Based Management Architecture in 5G which has improved system flexibility to adapt to different types of deployment scenarios. In SBMA, MnS producer and MnS consumer are two fundamental entities as defined in TS 28.533[2]. According to definitions in and TS 28.537[4] and TS 32.1... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.7.2 Potential requirements
| REQ-Distributed-FUN-1: The 3GPP management system should have capability to assist the MnS consumer to select the appropriate MnS(s) from multiple discovered MnS(s).
5.X Use case #<X>: <use case title>
5.X.1 Description
Editor's note: This clause provides a description of use case.
5.X.2 Potential requirements
E... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 6 Conclusions and recommendations
| 6.X Use case #<X>: <use case title>
Editor's note: This clause provides conclusions and recommendations for the corresponding use case.
Annex A: Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
SA5#162
Initial skeleton
V0.0.0
2025-10
SA5#163... |
a0af2a6390198051f207bb132b271100 | 28.885 | 1 Scope
| The present document …
|
a0af2a6390198051f207bb132b271100 | 28.885 | 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.
-... |
a0af2a6390198051f207bb132b271100 | 28.885 | 3 Definitions of terms, symbols and abbreviations
| |
a0af2a6390198051f207bb132b271100 | 28.885 | 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].
carbon emission: quantity of equivalent carbon dioxide emitted (e.g. kg of CO2 equivalent).
NOTE 1... |
a0af2a6390198051f207bb132b271100 | 28.885 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
a0af2a6390198051f207bb132b271100 | 28.885 | 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].
EC Energy Consumption
EE Energy Efficiency
EIF Energy Information Functi... |
a0af2a6390198051f207bb132b271100 | 28.885 | 4 Concepts and Background
| Editor’s note: This clause captures the concepts and background related to the studies performed in this TR
|
a0af2a6390198051f207bb132b271100 | 28.885 | 5 Use Cases
| |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.1 Enhancements to support energy efficiency as a service criteria
| |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.1.1 Use case #1: Enhancements to support the energy-related characteristics for Network Elements and Network Functions
| |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.1.1.1 Description
| Energy-related characteristics, energy availability, energy capacity, energy supply mix, carbon emission and carbon intensity are defined in TS 22.261 [2]. Several new use cases and requirements have been introduced in clause 6.15a of TS 22.261 [2] that utilize this energy-related characteristics such as adjustments to... |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.1.1.2 Potential requirements
| PREQ-Energy_Related_Characteristics-1: The 3GPP management system should be able to estimate and report the carbon emission information Network Element and Network Function.
PREQ-Energy_Related_Characteristics-2: The 3GPP management system should enable an authorized consumer to retrieve energy capacity information of... |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.1.1.3 Potential solutions
| 5.1.1.3.i Potential solution #<i>: <Potential Solution i Title>
5.1.1.3.i.1 Introduction
Editor's Note: This clause describes briefly the potential solution at a high-level.
5.1.1.3.i.2 Description
Editor's Note: This clause further details the potential solution, including all of its aspects and any assumptions m... |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.1.1.4 Evaluation of potential solutions
| Editor's Note: This clause provides the evaluation of potential solutions listed in 5.1.X.3.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 5.1.2 Use case #2: Management mechanisms to support service adjustments to adapt to energy-related characteristics and energy rationing
| |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.1.2.1 Description
| Under energy rationing constraints (i.e., when energy availability is limited or restricted), there is a potential risk for the entire network to shut-down causing service disruption. During such unavoidable hard constraints, the operators would like the network to provide services to their consumers to extend the time... |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.1.2.2 Potential requirements
| PREQ-Energy_Related_Service_Adjustment-1: The 3GPP management system should enable the operator to adapt the network performance of existing communication services to meet energy rationing control utilizing the available energy rationing information.
PREQ-Energy_Related_Service_Adjustment-2: The 3GPP management system... |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.1.2.3 Potential solutions
| 5.1.2.3.i Potential solution #<i>: <Potential Solution i Title>
5.1.2.3.i.1 Introduction
Editor's Note: This clause describes briefly the potential solution at a high-level.
5.1.2.3.i.2 Description
Editor's Note: This clause further details the potential solution, including all of its aspects and any assumptions m... |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.1.2.4 Evaluation of potential solutions
| Editor's Note: This clause provides the evaluation of potential solutions listed in 5.1.2.3.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 5.1.3 Use case #3: Energy Rationing Information Management
| |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.1.3.1 Description
| Clause 3.1 in TS 22.261 [2] defines energy rationing as a situation in which the availability of energy either across the network or at a particular network element or function is limited or reduced. This use case is for enabling management of energy rationing and energy saving in a network. The configuration of energy... |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.1.3.2 Potential requirements
| REQ-Energy_Rationing-CON-1: The 3GPP management system should enable its authorised consumers to provide energy rationing related information in an operator’s network.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 5.1.3.3 Potential solutions
| 5.1.3.3.A Potential solution #<A>: <Potential Solution A Title>
5.1.3.3.A.1 Introduction
Editor's Note: This clause introduces briefly the potential solution at a high-level.
5.1.3.3.A.2 Description
Editor's Note: This clause further details the potential solution, including all of its aspects and any assumptions ... |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.1.3.4 Evaluation of potential solutions
| Editor's Note: This clause provides the evaluation of all potential solutions listed in 5.1.3.3
5.1.X Use case #<X>: <Use case title>
5.1.X.1 Description
Editor’s note: This clause provides a description of the use case.
5.1.X.2 Potential requirements
Editor’s note: This clause captures potential requirements for ... |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.2 Enhancements to support the information required by Energy Information Function (EIF)
| Editor’s note: The use cases in this clause are subject to be updated based on the conclusion of SA2 study (FS_EnergySys_Ph2) in TR 23.700-67.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 5.2.1 Use case #1: Energy consumption and Energy Efficiency estimation and reporting at per network slice granularity
| |
a0af2a6390198051f207bb132b271100 | 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 consumpt... |
a0af2a6390198051f207bb132b271100 | 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... |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.2.1.3 Potential solutions
| |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.2.1.3.1 Potential solution #1: Enhancements to estimation of network slice EC KPIs
| |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.2.1.3.1.1 Introduction
| This potential solution defines enhancements estimation of network slice energy consumption KPI.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 5.2.1.3.1.2 Description
| The existing network slice EC KPI specified in clause 6.7.3.3 of TS 28.554 [4] can be enhanced to report support reporting for each SNSSAI. The KPI description in clause 6.7.3.3 of TS 28.554 [4] already describes how to estimate the energy consumption of gNB and 5GC NFs that are part of the NetworkSlice.
This KPI can... |
a0af2a6390198051f207bb132b271100 | 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.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 5.2.2 Use case #2: Enhancements to 5GC NF Profile to support energy saving and energy efficiency
| |
a0af2a6390198051f207bb132b271100 | 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 identi... |
a0af2a6390198051f207bb132b271100 | 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].
|
a0af2a6390198051f207bb132b271100 | 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 m... |
a0af2a6390198051f207bb132b271100 | 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... |
a0af2a6390198051f207bb132b271100 | 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 Solutio... |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.4 Enhancements to Energy Consumption and Energy Efficiency measurements and KPIs
| |
a0af2a6390198051f207bb132b271100 | 28.885 | 5.4.1 Use case #1: Renewable energy consumption
| |
a0af2a6390198051f207bb132b271100 | 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 s... |
a0af2a6390198051f207bb132b271100 | 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.
|
a0af2a6390198051f207bb132b271100 | 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 m... |
a0af2a6390198051f207bb132b271100 | 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.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 5.4.2 Use case #2: Support EC measurement of NE at per Energy Supply granularity
| |
a0af2a6390198051f207bb132b271100 | 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 ... |
a0af2a6390198051f207bb132b271100 | 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.
|
a0af2a6390198051f207bb132b271100 | 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 m... |
a0af2a6390198051f207bb132b271100 | 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.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 5.4.3 Use case #3: Support estimation of EC and EE KPIs at per PLMN-ID granularity in Network sharing scenario
| |
a0af2a6390198051f207bb132b271100 | 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 ... |
a0af2a6390198051f207bb132b271100 | 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.
|
a0af2a6390198051f207bb132b271100 | 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 m... |
a0af2a6390198051f207bb132b271100 | 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.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 5.4.4 Use case #4: Support estimation of EE KPI of HDLLC slice
| |
a0af2a6390198051f207bb132b271100 | 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... |
a0af2a6390198051f207bb132b271100 | 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.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 5.4.4.3 Potential solutions
| 5.4.4.3.i Potential solution #<i>: <Potential Solution i Title>
5.4.4.3.i.1 Introduction
Editor's Note: This clause describes briefly the potential solution at a high-level.
5.4.4.3.i.2 Description
Editor's Note: This clause further details the potential solution, including all of its aspects and any assumptions ma... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.