hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.2.2 Potential requirements
| REQ-NDTDG-01: The 3GPP management system should support a capability to allow an authorized MnS consumer to express data generation preferences on data source object, data type, and data quantity.
|
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.2.3 Potential solutions
| |
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.2.4 Evaluation of potential solutions
| |
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.3 Use case #3: Collaborate with ML training Producer to generate data
| |
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.3.1 Description
| In 3GPP TS 28.561 [3], the existing use case and requirements for using NDT to generate ML training data is described in clause 5.4.2.2. However, using NDT alone to generate data may be insufficient to support the following scenarios:
- Due to the coverage limitations of the physical network simulated by NDT, some extreme scenario data (such as sudden traffic peaks or unforeseen equipment failures) may not be generated.
- NDT-based data generation depends on complex procedures such as simulating network topology and device interactions, making it time-consuming when generating large volumes of data.
Therefore, for scenarios requiring extreme data generation or large-scale data generation, it is considered to introduce AI-based data generation models, generated by the ML training Producer, into NDT to enable rapid, batch, and comprehensive data generation.
As shown in the Figure 5.3.1-1, the MnS Consumer can request the MnS producer to create an NDT instance for generating data with an indication of simulation object, data type, and data requirements, etc. Data requirements may specify large-scale data, extreme data requirements. The MnS producer creates an NDT instance based on the request and sends a response to the MnS consumer. The MnS producer can act as an ML training consumer to send a request to the ML training producer for generating a data generation model. Subsequently, the MnS producer executes simulation based on the NDT instance to obtain simulation data (e.g.,the generated UE throughput data), which is then sent to the ML training producer. This simulation data is used as training data to update and train the data generation model. The MnS producer can act as an ML inference function to receive the updated model from the ML training producer, execute it to obtain the final generated data, and send this data to the MnS consumer.
Figure 5.3.1-1 Collaborate with ML training Producer to generate data
Through this method, after the ML training producer completes ML model training and updates based on the initial NDT simulation data, it only needs to perform AI inference for subsequent data generation, which can reduce certain resource consumption.
|
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.3.2 Potential requirements
| 5.3.3 Potential solutions
5.3.4 Evaluation of potential solutions
|
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.4 Use Case #4: Enhancement for multiple NDT collaborations
| |
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.4.1 Description
| In 3GPP TS 28.561 [3], the existing use case and requirements for collaboration between NDTs are described in clause 5.5.2.1 and the requirement in clause 5.5.3. The 3GPP management system should support a capability enabling an authorized MnS consumer to configure the relationship between NDTs during simulation/emulation. However, there are no specific solutions to support this scenario, and there are no further details regarding the collaboration of multiple NDTs.
Therefore, the scenario needs the further investigate, a single NDT Function might not be able to fulfil a task by itself and may depend on or need to use the service or outputs of another NDT Function during the simulation/emulation activity. This require the 3GPP management to support the capabilities and report the relationships between NDTs regarding the collaboration of multiple NDTs.
|
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.4.2 Potential requirements
| REQ-NDT-Colla-1: The 3GPP management system should support a capability that enables an authorized MnS consumer to request a report on the relationships between NDTs regarding the collaboration of multiple NDTs.
|
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.4.3 Potential solutions
| |
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.4.4 Evaluation of potential solutions
| |
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.5 Use Case #5: Enhancement on NDT reporting method
| |
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.5.1 Description
| In TS 28.561 [3], the reporting method of NDT output is notification based reporting. The NDT MnS consumer receives an NDT report from NDT producer by invoking generic provisioning management service operations and notifications in TS 28.532 [4]. However, different NDT job may have different requirement on reporting method. For example, in the scenario of signalling storm, it is more appropriate to use streaming data reporting service to timely report the simulation/emulation information on potential network impact.
It is proposed to enable the NDT MnS consumer to select the reporting method of simulation/emulation output based on different requirement. In addition to notification based reporting, streaming data reporting service also need to be supported for NDT output reporting.
|
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.5.2 Potential requirements
| REQ-NDTRM-01: The 3GPP management system should support a capability to allow an authorized MnS consumer to request NDT report to be provided by streaming data reporting service.
REQ-NDTRM-02: The 3GPP management system should support a capability for NDT MnS producer to support delivery of NDT report by streaming data reporting service.
|
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.5.3 Potential solutions
| |
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.5.4 Evaluation of potential solutions
| |
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.6 Use Case #6: Capability Discovery of NDT in NDT Collaboration
| |
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.6.1 Description
| NDT collaboration among different NDTFunctions located in different domain is critical to enable end to end use cases, In Rel-19 the supported domain of NDT is represented by NDTFunctionScope attribute. Then, the NDTFunction that triggers the collaboration can involve NDT(s) that supports modelling of different domain.
When simulating end-to-end user experience data generation, the consumer may want to specify diverse traffic model and UE distribution for different scenarios. For example, major event such as sporting events, the UE distribution and user’s communication behaviour is quite different, in which the uplink traffic will increase significantly. Therefore, if consumers want to trigger NDT collaboration for E2E user experience data generation, they should know which candidate NDT supports the simulation of different traffic. Therefore, NDTFunction needs further enhancement to expose more detailed capability information (e.g., capability of supporting UE distribution model and traffic model). Then, the consumers can accurately identify and select appropriate collaboration participants as NDT component, ensure cross-domain traffic consistency, and effectively validate end-to-end scenario continuity.
|
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.6.2 Potential requirements
| REQ- NDTAUT-01
The 3GPP management system should support a capability enabling authorized MnS Consumer to discover detailed capability of candidate NDT components for NDT collaboration.
|
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.6.3 Potential solutions
| TBD
|
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.6.4 Evaluation of potential solutions
| TBD
|
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.7 Use Case #7 Defining the Lifecycle and Runtime Behaviour of NDT Jobs
| |
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.7.1 Description
| The NDTJob lifecycle is not clear, there are some items open to interpretation and some items missing which are described below.
Issue#1: The MnS Consumer should have a method to know which configuration of NDTJob has produced a given report. In the current specification NDTReport refer to the NDT job (i.e NDTJobRef). In the existing specification, it is possible to modify the NDTJob which may result in the different NDTReport. This will result in loosing the link between produced NDT Report and the original NDT Job. The MnS Consumer would benefit from understanding the implications of reconfiguring the NDTJob. At the moment, the NDTReports refer to the DN of the NDTJob – if a NDTJob is reconfigured, this means the same DN is applied to each report, even if the simulation has changed. Likewise, there is no clear procedure described in Clause 6.4, despite the “Modify” use-case being possible for the NDTJob Instances.
Excerpt: Table 6.2.1.3.8.2-1 describes the attributes associated with the NDTReport <<IOC>>
Excerpt: From 6.3 Attribute definitions, the explanation of the ndtJobRef of the NDTReport <<IOC>> refers to
|
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.7.2 Potential requirements
| |
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.7.3 Potential solutions
| |
042d302ca200c9423b759396ac85b7c9 | 28.883 | 5.7.4 Evaluation of potential solutions
| |
042d302ca200c9423b759396ac85b7c9 | 28.883 | 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 <X> (informative):
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
1. S5-254290
2. S5-254670
3. S5-254842
4. S5-254672
5. S5-254843
6. S5-254396
7. S5-254674
8. S5-254733
1. Rel-20 pCR TR 28.883 Add structure proposal
2. Rel-20 pCR TR 28.883 Use case on NDT support intent pre-evaluation
3. Rel-20 pCR TR 28.883 Improvement of data generation
4. pCR TR 28.883 Add a use case of NDT data generation
5. pCR TR 28.883 Add use case and requirements on enhancement for multiple NDT collaborations
6. Rel-20 pCR TR 28.883 Enhancement on NDT reporting method
7. Pseudo-CR on TR 28.883 Add New Use Case on Capability Discovery of NDT in NDT Collaboration
8. Rel-20 pCR TR 28.883 Defining the Lifecycle and Runtime Behaviour of NDT Jobs
V0.1.0
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 1 Scope
| The present document … describes use cases, potential requirements, and potentialproposed solutions aimed at enhancing the Service Based Management Architecture (SBMA) in the context of 5G Advanced (5GA). It also presents conclusions and recommendations regarding the next steps in the standardization process.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 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.533: "Management and orchestration; Architecture framework".
[a][3] 3GPP TS 28.532: " Management and orchestration; Generic management services".
[b][4] 3GPP TS 28.537: " Management and orchestration; Management capabilities".
[c][5] 3GPP TS 28.552: " Management and orchestration; 5G performance measurements".
[d][6] 3GPP TS 28.554: " Management and orchestration; 5G end to end Key Performance Indicators (KPIs)".
[e][7] 3GPP TS 32.423: " Telecommunication management; Subscriber and equipment trace: Trace data definition and management".
[f][8] https://datatracker.ietf.org/doc/html/rfc6455
[g][9] https://websocket.org/guides/websocket-protocol/
[102] 3GPP TS 28.111: "Management and orchestration; Fault management (FM)".
[a][11] 3GPP TS 32.531: "Telecommunication management; Software management (SwM); Concepts and Integration Reference Point (IRP) Requirements".
[b][12] 3GPP TS 32.532: "Telecommunication management; Software management (SwM); Integration Reference Point (IRP); Information Service (IS)".
[c][13] 3GPP TS 32.533: "Telecommunication management; Software management (SwM); Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)".
[a][14] 3GPP TS 28.631: "Telecommunication management; Inventory Management (IM) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements".
[b][15] 3GPP TS 28.632: "Telecommunication management; Inventory Management (IM) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[c][16] 3GPP TS 28.633: "Telecommunication management; Inventory Management (IM) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions".
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 3 Definitions of terms, symbols and abbreviations
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 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.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 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].
<ABBREVIATION> <Expansion>
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 4 Concepts and background
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 4.1 Introduction
| The Service Based Management Architecture (SBMA) is specified in 3GPP TS 28.533 [X] and represents a foundational shift in how management and orchestration capabilities are defined and delivered across 3GPP networks. SBMA adopts a modular, service-oriented approach that enables flexible, scalable, and interoperable management solutions.
The fundamental building block of the SBMA is the Management Service (MnS). An MnS is a set of offered capabilities for management and orchestration of network and services. Each MnS is produced by a logical entity known as an MnS Producer, and consumed by another logical entity referred to as an MnS Consumer. These interactions occur exclusively through standardized service interfaces, ensuring implementation-agnostic communication and consistent behaviour across deployments.
The architecture for the present study builds upon the SBMA framework in TS 28.533 [X][2]. All proposed potential enhancements and solutions are expected to comply with the principles outlined in TS 28.533 [X][2], including service abstraction, interface standardization, and functional decoupling.
The present study aims to preserve architectural continuity with the SBMA baseline model while expanding its applicability to address emerging requirements in 5G Advanced networks. These include support for distributed management function deployments, integration with message bus technologies, enhanced service discovery and registry mechanisms, and alignment with 5GC and RAN architecture. The goal is to maintain a unified, service based management framework that can evolve to support increasing levels of intelligence, autonomy, and cross-domain orchestration, while remaining aligned with other 3GPP Working Groups and external Standards Development Organizations (SDOs).
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 4.2 Management data streaming based on Message Bus technologies
| 3GPP TS 28.532 [3] defines Stage 2 and Stage 3 of the streaming data reporting service. Currently, the 3GPP management system supports WebSocket-based data streaming for PM, tracing, and analytics, establishing a point-to-point transport connection between the streaming data reporting MnS consumer and MnS producer. The producer initiates the connection with the consumer and exchanges metadata (informing the consumer about its identity and the nature of the data to be reported, i.e., streamInfo). After this phase, the producer reports streaming data to the consumer via the established connection.
Using point-to-point WebSocket communication protocol, which operates over a single TCP connection between a client and a server, a separate connection would be established between each consumer and the producer, causing the producer to generate and transmit multiple copies of the same data. The WebSocket protocol is standardized by the IETF in RFC 6455 [8]. It defines WebSocket as a protocol that enables ongoing, full-duplex, bidirectional communication between web servers and web clients over an underlying TCP connection, see [9]. Though a server can maintain multiple WebSocket connections simultaneously and broadcast messages to all connected clients. However, this is not a protocol-level feature, it is an application-level point-to-multipoint behaviour.
Editor's note: It is FFS to investigates the integration and compatibility with the message bus industry solutions by providing a general scope which covers management data types defined in 3GPP TS 28.537 [4] (e.g. performance data, trace data, etc.). This does not imply that the message bus investigated in the present document are intended to replace the currently used WebSocket.
NOTE: The management data includes performance measurements or KPIs defined in TS 28.552 [5] and TS 28.554 [6], trace reporting data defined in TS 32.423 [7] and analytic reporting data defined in TS 28.532 [3].
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5 Use cases and potential solutions
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.1 Use case #1: Integration of SBMA with 5GC and 5G Access Network architecture
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 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 An illustrative architecture reference model for management and orchestration, which defines management functions as logical, implementation-agnostic entities, is captured 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 These functions produce and/or consume Management Services (MnSs) exclusively via standardized service interfaces, enabling consistent, service-based interactions across the management domain.
Each MnF registers its MnSs with a service registry, enabling dynamic discovery and selection of services across domains and vendors.This baseline reference architecture model provides a consistent, modular foundation that can evolve to support increasing intelligence, autonomy, and cross-domain orchestration. Accordingly, it is needed to continue evolving the architecture, to support emerging requirements such as AI/ML integration, autonomous operations, and cross-domain orchestration.
For example:
• A fault management function in the RAN management domain autonomously detects faults using AI/ML models and triggers a healing workflow.
• This MnF can thenworkflow orchestrates actions across both RAN and Core domains, invoking MnSs such as performance analytics, configuration updates, and resource scaling.
• The orchestration logic is implementation-agnostic, which means it does not rely on where or how the functions are deployed, only on the standardized MnS interfaces.
• The SBMA framework ensures that each MnF clearly declares its role as a producer or consumer of MnSs, supporting modularity and reusability.
In Release-19, a modular reference model has been defined in annex A.11 of TS 28.533 [YY]. Continue evolving the architecture reference model for management and orchestration, to support new requirements such as AI/ML integration, autonomy, and cross-domain orchestration.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.1.2 Potential requirements
| REQ-SBMA-ARM-1: SBMA should support autonomous management operations.
REQ-SBMA-ARM-12: SBMA should enable cross-domain management and orchestration across RAN and Core domains, with provideing a consolidated view of management architecture.
REQ-SBMA-ARM-23: SBMA should be agnostic of implementation, allowing flexible deployment models (e.g., centralized, distributed, hybrid).
REQ-SBMA-ARM-4: SBMA should define clear roles and responsibilities for MnS producers and consumers, ensuring modularity and service reusability.
REQ-SBMA-ARM-345: SBMA should provide support on MnSs discovery, registration, and selection acrossin multi-domains /and multi-vendors environments.
Editor's note: "MnSs selection" of REQ-SBMA-ARM-4 will be revisited.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.1.3 Potential solutions
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.1.4 Evaluation of potential solutions
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.2 Use case #2: Management data streaming based on Message Bus
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 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. Using point-to-point WebSocket communication protocol, which operates over a single TCP connection between a client and a server, a separate connection would be established between each consumer and the producer, causing the producer to generate and transmit multiple copies of the same data. The WebSocket protocol is standardized by the IETF in RFC 6455 [f]. It defines WebSocket as a protocol that enables ongoing, full-duplex, bidirectional communication between web servers and web clients over an underlying TCP connection, see [g].
Though a server can maintain multiple WebSocket connections simultaneously and broadcast messages to all connected clients. However, this is not a protocol-level feature, it is an application-level point-to-multipoint behaviour.
Editor's note: It is FFS to investigates how the producer generates the data and send it to the message bus for the case that multiple consumers request the same management data.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.2.2 Potential requirements
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.2.3 Potential solutions
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.2.4 Evaluation of potential solutions
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.3 Use case #3: Historical alarms
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 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 of information in many use cases:
- AI/ML training: Historical alarms provide context information for AI/ML training.
- Security auditing: Historical security alarms provide information for security monitoring and auditing.
• Fault Repair: By analyzing historical alarms associated with previous faults, operators can identify recurring issues, understand root causes more effectively, and accelerate troubleshooting. This reduces mean time to repair (MTTR) and improves network and service reliability.
• Predictive Maintenance: Historical alarm can be used to forecast potential future failures. For example, repeated alarms from a specific network element may indicate impending hardware degradation. Predictive analytics based on alarm history enables proactive maintenance, minimizing service disruption.
• Enhanced analytics: Multiple MDA capabilities utilize alarm information as enabling data (see TS 28.104, clause 8). Currently the enabling data is defined as “Alarm information and notifications as per TS 28.111”, but the MDA capabilities would be more valuable if historical alarm data is also considered.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.3.2 Potential requirements
| Req-1: The 3GPP Management system should have the capability allowing to retrieve historical alarms.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.4 Use case#4 on software management for 5G
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 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 efficiency. The benefits of software management retain for 5G network management:
- One benefit of software management is interoperability: standardized procedures make it possible for operators to manage software on heterogeneous network elements in a multi-vendor environment and reduces operational complexity.
- Another benefit is network service continuity. By supporting mechanisms such as staged upgrades, version control, and fallback strategies, software management capability minimizes downtime and protects user experience.
Currently, TS 28.533 [2] does not include support for software management. As 5G networks evolve in scale and complexity, it is essential to introduce software management capabilities into SBMA. These capabilities will enable operators to maintain software of NEs and NFs.
Editor's note: To enable software management within SBMA, the associated potential requirements and potential solutions are FFS, building upon the legacy of software management of NEs for LTE while adapting to the principles of SBMA.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.4.2 Potential requirements
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.4.2.1 Potential general requirements
| REQ-SBMA-SWM-1: The 3GPP management system should support software management.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.4.2.2 Potential requirements for PNF
| REQ-SBMA-PNFSWM-1: The 3GPP management system should support the capability to monitor software download, and activation.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.4.2.3 Potential requirements for VNF
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.4.3 Potential solutions
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.4.4 Evaluation of potential solutions
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.5 Use case#5 on inventory management for 5G
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 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 inventory management retain for 5G network management:
Inventory management enables operators to track equipment status, plan capacity expansions, schedule upgrades, and manage decommissioning more effectively, which improves consistency across large, geographically distributed networks
Inventory management shows the links/topology among network elements, network functions and physical network resources, which helps operators for faster fault localization and root-cause analysis when problems occur. The insight into these dependencies also help operators minimize risks during maintenance or upgrades.
Currently, TS 28.533 [2] does not include support for Inventory Management (IM). As 5G networks evolve in scale and complexity, it is essential to introduce IM capabilities into SBMA. These capabilities will enable operators to maintain accurate and dynamic records of static network resources, supporting planning, assurance, and operational efficiency.
Editor's note 1: To enable inventory management in SBMA, the associated potential requirements, and potential solutions are FFS, building upon the legacy of inventory management for LTE while adapting to the principles of SBMA.
Editor's note 2: For topology or the relationship among different inventory objects, the difference between IM and CM for 5G is FFS.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.5.2 Potential requirements
| REQ-SBMA-IM-1: The 3GPP management system should support inventory management.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.5.3 Potential solutions
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.5.4 Evaluation of potential solutions
|
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
Editor's note: This clause provides potential requirements for the corresponding use case.
5.X.3 Potential solutions
Editor's note: This clause provides one or more solutions. Further (sub-)clause(s) may be added to capture details.
5.X.4 Evaluation of potential solutions
Editor's note: This clause provides evaluation of potential solutions.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 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
S5-254454
pCR TR 28.884 Add structure for SBMA study report
V0.1.0
2025-10
SA5#163
S5-254676
pCR TR 28.884 Add introduction for SBMA study report
V0.1.0
2025-10
SA5#163
S5-254677
pCR TR 28.884 Add scope for SBMA study report
V0.1.0
2025-10
SA5#163
S5-254678
pCR TR 28.884 Add concepts and background
V0.1.0
2025-10
SA5#163
S5-254681
pCR TR 28.884 Use case on integration of SBMA with 5GC and 5G Access Network architecture
V0.1.0
2025-10
SA5#163
S5-254682
pCR TR 28.884 Management data streaming based on message bus
V0.1.0
2025-10
SA5#163
S5-254732
New KI on Historical alarms
V0.1.0
2025-10
SA5#163
S5-254844
pCR TR 28.884 Use case on software management
V0.1.0
2025-10
SA5#163
S5-254845
pCR TR 28.884 Use case on inventory management
V0.1.0
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 4.2 Architectural enhancement views
| This clause provides a structured analysis of the architectural enhancements proposed for the SBMA. The enhancements are categorized into three complementary views: Logical View, Deployment View, and Service Interaction View. These views are intended to facilitate a comprehensive understanding of the SBMA evolution, while maintaining alignment with the foundational principles defined in TS 28.533 [X].
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 4.2.1 Logical View
| The Logical View describes the functional composition and abstraction of SBMA entities and their relationships. In the present study, the logical architecture is enhanced to support improved modularity, semantic clarity, and extensibility of MnS. These enhancements aim to facilitate cross-domain reuse, model decoupling, and improved resource representation.
Key enhancements include:
• Definition of management model and network resource model to enable aggregation and harmonization across domains.
• Introduction of model abstraction mechanisms to decouple management logic from resource-specific implementations.
• Enablement of inventory management capabilities within SBMA, including modelling of static resources.
• Refinement of mnsAgent usage and clarification of its associated IOC definitions.
• Introduction of merge operation semantics to support partial MOI updates and efficient change notification handling.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 4.2.2 Deployment view
| The Deployment View addresses the instantiation and distribution of SBMA components across physical and virtual environments. In the present study, the architecture is extended to support flexible deployment models, including distributed management function placement, cloud-native implementations and inter-domain interoperability.
Key enhancements include:
• Integration of message bus technologies to enable scalable, asynchronous communication between MnS entities.
• Support for federated MnS Registries to facilitate cross-domain service registration and discovery.
• Mapping of SBMA components to 5GC and RAN functional entities to ensure seamless interoperability.
• Enablement of software lifecycle management capabilities within SBMA, including download, upgrade, and rollback operations.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 4.2.3 Service interaction view
| The Service Interaction View defines the dynamic behaviour and communication mechanisms among SBMA entities. In the present study, it focuses on the invocation, subscription, and notification flows between MnS producers and consumers, and the mechanisms that enable service exposure, discovery, and selection.
Key enhancements include:
• Advanced management service discovery, registry, and selection mechanisms, including attribute-based filtering and contextual selection.
• Extension of fault management capabilities to support retrieval of historical alarms (i.e., stored inactive alarms), enabling improved operational visibility and troubleshooting.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 4.21 Management data streaming based on Message Bus technologies
| 3GPP TS 28.532 [a][3] defines Stage 2 and Stage 3 of the streaming data reporting service. Currently, the 3GPP management system supports WebSocket-based data streaming for PM, tracing, and analytics, establishing a point-to-point transport connection between the streaming data reporting MnS consumer and MnS producer. The producer initiates the connection with the consumer and exchanges metadata (informing the consumer about its identity and the nature of the data to be reported, i.e., streamInfo). After this phase, the producer reports streaming data to the consumer via the established connection.
As 5G networks scale in complexity and distribution, traditional point-to-point communication models for management services face limitations in scalability, resiliency, and flexibility, highlighting the advantages of introducing message bus solution. Using point-to-point WebSocket communication protocol, which operates over a single TCP connection between a client and a server, a separate connection would be established between each consumer and the producer, causing the producer to generate and transmit multiple copies of the same data. This results in redundant data production and inefficient use of transmission resources, hindering effective data management. The WebSocket protocol is standardized by the IETF in RFC 6455 [f][8]. It defines WebSocket as a protocol that enables ongoing, full-duplex, bidirectional communication between web servers and web clients over an underlying TCP connection, see [g][9]. Though a server can maintain multiple WebSocket connections simultaneously and broadcast messages to all connected clients. However, this is not a protocol-level feature, it is an application-level point-to-multipoint behaviour.
Editor's note: It is FFS to investigates the integration and compatibility with the message bus industry solutions by providing a general scope which covers management data types defined in 3GPP TS 28.537 [b][4] (e.g. performance data, trace data, etc.). This does not imply that the message bus investigated in the present document are intended to replace the currently used WebSocket.
Message bus architectures employ a publish-subscribe (pub-sub) model, offering multipoint-to-multipoint transport protocol communication, asynchronous delivery, and decoupled service interactions, which are well-suited for distributed management deployments. A message bus may offers the following key advantages, which address the weaknesses of conventional WebSocket-based connections:
High Performance: A message bus offers multipoint-to-multipoint transport protocol communication, which is suitable for handling large-scale, real-time data with high throughput and low latency.
Robustness and Resilience: A message bus may supports message storage and can be deployed in a distributed manner, therefore minimizes downtime and data loss, ensuring consistent and reliable service experiences.
Data Management Efficiency: A message bus provides asynchronous delivery and decoupled service interactions. It avoids redundant data collection, simplifies data pipelines and reduces operational costs.
There are industry solutions that can realize message bus functionalities. The present document investigates 3GPP management system should evolve to consider the integration and compatibility with these existing message bus industry solutions by providing a general scope which covers management data types defined in 3GPP TS 28.537 [b] (e.g. performance data, trace data, etc.). This does not imply that the message bus investigated in the present document are intended to replace the currently used WebSocket.
NOTE: The management data includes performance measurements or KPIs defined in TS 28.552 [c][5] and TS 28.554 [d][6], trace reporting data defined in TS 32.423 [e][7] and analytic reporting data defined in TS 28.532 [a][3].
Architectural Considerations:
- Logical View: MnFs remain implementation-agnostic and interact via MnSs; the message bus acts as a transport abstraction layer.
- Deployment View: Message bus clusters may be deployed per management domain (e.g., RAN management domain, CN management domain) or globally, depending on latency and fault domain requirements.
- Service Interaction View: MnS Producers publish events or data streams to message queues; MnS Consumers subscribe based on service type, management domain, or operational context. The message bus handles delivery, buffering, and replay. Message queue names are exchanged by the MnS producer and consumer.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.15.2 Use case #12: Management data streaming based on Message Bus
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.15.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. Using traditional point-to-point WebSocket communication protocol, which operates over a single TCP connection between a client and a server, a separate connection would be established between each consumer and the producer, causing the producer to generate and transmit multiple copies of the same data. This results in redundant data production and inefficient use of transmission resources, hindering effective data management. The WebSocket protocol is standardized by the IETF in RFC 6455 [f]. It defines WebSocket as a protocol that enables ongoing, full-duplex, bidirectional communication between web servers and web clients over an underlying TCP connection, see [g].
Though a server can maintain multiple WebSocket connections simultaneously and broadcast messages to all connected clients. However, this is not a protocol-level feature, it is an application-level point-to-multipoint behaviour.
Editor's note: It is FFS to investigates how the producer generates the data and send it to the message bus for the case that multiple consumers request the same management data.
By introducing a transport protocol level message bus mechanism, mMultiple consumers can subscribe to the same data. The producer only needs to generate a single copy of the data and send it to the message bus. The message bus then automatically replicates and efficiently distributes the data to all subscribed consumers, significantly improving data production, distribution, and management efficiency.
Operations for streaming data report defined in [a] are:
• establishStreamingConnection operation (M)
• terminateStreamingConnection operation (M)
• reportStreamData operation (M)
• addStream operation (M)
• deleteStream operation (M)
• getConnectionInfo operation (M)
• getStreamInfo operation (M)
These operations are defined from the producer's perspective. In the point-to-point WebSocket connection method, the producer initiates a stream connection to the consumer and sends the stream data. However, with the introduction of the message bus architecture, the interaction is no longer limited to between the producer and consumer. Instead, it is decoupled into separate interactions between each of them and the message bus.
Therefore, to support management stream data reporting services based on the message bus, enhancements are needed. in the following areas:
Producer side: Enhance the existing APIs to support the producer to report stream data to specific message queues based on the message bus protocol.
Consumer side: Add a set of new APIs to support the consumer to retrieve stream data from specific message queues based on the message bus protocol.
Interaction aspect: Study the mechanism to support the exchange of the endpoint information and message queues between the producer and the consumer.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.15.2.2 Potential requirements
| REQ-SBMA-MBUS-1: The 3GPP management system should provide capabilities allowing the producer to report stream data to specific message queues based on the message bus protocol.
REQ-SBMA-MBUS-2: The 3GPP management system should provide capabilities allowing MnS consumers to retrieve stream data from specific message queues based on the message bus protocol.
REQ-SBMA-MBUS-3: The 3GPP management system should provide capabilities to support the exchange of the information of the message bus endpoint and message queues between the MnS producer and the MnS consumer.
|
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.15.2.3 Potential solutions
| |
6b8b46b5fdff6eb6d629a669998ec3ca | 28.884 | 5.15.2.4 Evaluation of potential solutions
| 5.x5.3 Use case #3X: Historical alarms
5.x5.3.1 Description
The "AlarmList" defined in TS 28.111 [a10] 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 of information in many use cases:
- AI/ML training: Historical alarms provide context information for AI/ML training.
- Security auditing: Historical security alarms provide information for security monitoring and auditing.
• Fault Repair: By analyzing historical alarms associated with previous faults, operators can identify recurring issues, understand root causes more effectively, and accelerate troubleshooting. This reduces mean time to repair (MTTR) and improves network and service reliability.
• Predictive Maintenance: Historical alarm can be used to forecast potential future failures. For example, repeated alarms from a specific network element may indicate impending hardware degradation. Predictive analytics based on alarm history enables proactive maintenance, minimizing service disruption.
• Enhanced analytics: Multiple MDA capabilities utilize alarm information as enabling data (see TS 28.104, clause 8). Currently the enabling data is defined as “Alarm information and notifications as per TS 28.111”, but the MDA capabilities would be more valuable if historical alarm data is also considered.
5.x5.3.2 Potential requirements
Req-1: The 3GPP Management system should have the capability allowing to retrieve historical alarms.
5.X5.4 Use case#4 on software management for 5G
5.X5.4.1 Description
3GPP TS 32.531 [a][11], TS 32.532 [b][12], and TS 32.533 [c][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 enables network operators with network management capabilities including software download, activation, upgrade, fallback, software information query and monitoring, pre-check, etc, allowing operators to maintain continuous service availability while introducing new patches across multi-vendor environments.
Software management for 5G enhances 5G network operational efficiency and reduces costs. The benefits of software management retain for 5G network management:
- One benefit of software management is interoperability: standardized procedures make it possible for operators to manage software on heterogeneous network elements in a multi-vendor environment and reduces operational complexity.
- Another benefit is network service continuity. By supporting mechanisms such as staged upgrades, version control, and fallback strategies, software management capability minimizes downtime and protects user experience.
Currently, TS 28.533 [XX2] does not include support for software management functions. As 5G networks evolve in scale and complexity, it is essential to introduce software management capabilities into SBMA. These capabilities will enable operators to maintain software of NEs and NFs. To enable software management of NEs within SBMA, the potential requirements and potential solutions need to be studied.
Editor's note: To enable software management within SBMA, the associated potential requirements and potential solutions are FFS, building upon the legacy of software management of NEs for LTE while adapting to the principles of SBMA.
5.X5.4.2 Potential requirements
5.X5.4.2.1 Potential general requirements
REQ-SBMA-SWM-1: The 3GPP management system should support software management.
5.X5.4.2.21 Potential requirements for PNF
REQ-SBMA-PNFSWM-1: The 3GPP management system should support software download software downloadto one or more NEs and NFs.
REQ-SBMA-PNFSWM-2: The 3GPP management system should support active software activation activation for one or more NEs and NFs.
REQ-SBMA-PNFSWM-3: The 3GPP management system should support software fallback in one or more NEs and NFs.
REQ-SBMA-PNFSWM-14: The 3GPP management system should support the capability to monitor states of software download, installation and activation.
REQ-SBMA-SWM-5: The 3GPP management system should support the capability to retrievequery the information of a the software which is present in one or more NEs and NFs.
REQ-SBMA-SWM-6: The 3GPP management system should support the capability to pre-check the software to check whether the software can be successfully activated or not.
REQ-SBMA-SWM-7: The 3GPP management system should support the capability to pre-activate the software to check whether the software can be successfully activated or not.
5.X5.4.2.31 Potential requirements for VNF
5.X5.4.3 Potential solutions
5.X5.4.4 Evaluation of potential solutions
5.X5.5 Use case#5 on inventory management for 5G
5.X5.5.1 Description
3GPP TS 28.631 [a][14], TS 28.632 [b][15], and TS 28.633 [c][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 inventory management retain for 5G network management:
Inventory management enables operators to track equipment status, plan capacity expansions, schedule upgrades, and manage decommissioning more effectively, which improves consistency across large, geographically distributed networks
Inventory management shows the links/topology among network elements, network functions and physical/virtualized network resources, which helps operators for faster fault localization and root-cause analysis when problems occur. The insight into these dependencies also help operators minimize risks during maintenance or upgrades.
Currently, TS 28.533 [XX][2] does not include support for Inventory Management (IM) functions. As 5G networks evolve in scale and complexity, it is essential to introduce IM capabilities into SBMA. These capabilities will enable operators to maintain accurate and dynamic records of static network resources, supporting planning, assurance, and operational efficiency.
Editor's note 1: To enable inventory management in SBMA, the associated potential requirements, and potential solutions are FFS, building upon the legacy of inventory management for LTE while adapting to the principles of SBMA.
Editor's note 2: For topology or the relationship among different inventory objects, Tthe difference between IM and CM for 5G is FFS.
5.X5.5.2 Potential requirements
REQ-SBMA-IM-1: The 3GPP management system should support inventory management for NE, NF, hardware, software, licence, Tower Mounted Amplifier and Antenna.
REQ-SBMA-IM-2: The 3GPP management system should support inventory management for NE, NF, hardware, software, licence, Tower Mounted Amplifier and Antenna.
Editor's note: "NE, NF, hardware, software, licence, Tower Mounted Amplifier and Antenna" of REQ-SBMA-IM-2 will be revisited.
REQ-SBMA-IM-2: The 3GPP management system should support the capability to provide the relationships among different inventory objects.
5.X5.5.3 Potential solutions
5.X5.5.4 Evaluation of potential solutions
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
Editor's note: This clause provides potential requirements for the corresponding use case.
5.X.3 Potential solutions
Editor's note: This clause provides one or more solutions. Further (sub-)clause(s) may be added to capture details.
5.X.4 Evaluation of potential solutions
Editor's note: This clause provides evaluation of potential solutions.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 1 Scope
| The present document …
|
ef58d30e4030b2362bf35c2b280da85f | 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.
- 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 22.261: "Service requirements for the 5G system".
[3] 3GPP TS 28.310: "Management and orchestration; Energy efficiency of 5G".
[4] 3GPP TS 28.554: "Management and orchestration; 5G end to end Key Performance Indicators (KPI)".
[5] ETSI GS OEU 020 (v1.1.1): "Operational energy Efficiency for Users (OEU); Carbon equivalent Intensity measurement; Operational infrastructures; Global KPIs; Global KPIs for ICT Sites".
[6] ETSI ES 202 706-1 V1.7.1 (2022-08): "Environmental Engineering (EE); Metrics and measurement method for energy efficiency of wireless access network equipment; Part 1: Power consumption - static measurement method".
[7] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3".
[8] 3GPP TS 23.501: "System architecture for the 5G System (5GS)".
[9] 3GPP TR 23.700-67: "Study on Energy Efficiency and Energy Saving; Phase 2".
[10] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements".
[11] 3GPP TS 32.130: " Telecommunication management; Network sharing; Concepts and requirements".
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 3 Definitions of terms, symbols and abbreviations
| |
ef58d30e4030b2362bf35c2b280da85f | 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: This definition is taken from 3GPP TS 22.261 [2].
energy availability: the remaining amount of energy (e.g. in kWh) locally available for consumption. For devices, network elements and functions, energy availability may be limited and/or intermittent, in particular when relying on batteries and/or renewable energy sources (e.g. off-grid base stations, satellites etc) or during power grid heavy load or disruptions.
NOTE 2: This definition is taken from 3GPP TS 22.261 [2].
energy capacity: the maximum amount of energy (e.g. in kWh) that can be locally available for consumption (either locally produced and/or stored) by a device or a network element or function.
NOTE 3: This definition is taken from 3GPP TS 22.261 [2].
Energy Consumption (EC): integral of power consumption over time.
NOTE 4: This definition is taken from TS 28.310 [3]
Energy Efficiency (EE): ratio between performance and energy consumption.
NOTE 5: The performance may be measured based on e.g. data volume, latency, number of active users, etc.
NOTE 6: This definition is taken from 3GPP TS 28.310 [3].
energy rationing: A situation in which the availability of energy either across the network or at a particular network element or function is limited or reduced.
NOTE 7: This definition is taken from 3GPP TS 22.261 [2].
energy-related characteristics: information which characterize the energy to power the operator’s network in terms of energy consumption, energy supply mix, carbon footprint, energy capacity and availability conditions.
NOTE 8: Which energy-related characteristics are relevant depends on the scenario.
Network Slice: A logical network that provides specific network capabilities and network characteristics.
NOTE 90: This definition is taken from 3GPP TS 23.501 [8].
renewable energy: energy from renewable sources as energy from renewable non-fossil sources, namely wind, solar, aerothermal, geothermal, hydrothermal and ocean energy, hydropower, biomass, landfill gas, sewage treatment plant gas and biogases
NOTE 10: This definition is taken from TS 22.261 [2].
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
ef58d30e4030b2362bf35c2b280da85f | 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 Function
S-NSSAI Single Network Slice Selection Assistance Information
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 4 Concepts and Background
| Editor’s note: This clause captures the concepts and background related to the studies performed in this TR
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5 Use Cases
| |
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.1 Enhancements to support energy efficiency as a service criteria
| |
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.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 communication service, information exposure, performance requirements related to the exposure of network energy-related characteristics, network internal optimization as part of Rel-20 enhancements.
Energy-related characteristics are not reported by the network to the 3GPP management system and are required to be obtained by the operator from external sources and associated into the 3GPP management system for the 3GPP network to utilize this information. 3GPP management system currently support parts of energy-related characteristics. This use case identifies the energy-related characteristics that are currently supported by 3GPP management system.
Energy supply information can be associated with the Managed Elements (representing the Network Elements) or SubNetwork 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.
Energy consumption related KPIs are defined in clause 6.7.3 of TS 28.554 [4] and gNB Estimated Carbon Emission and NG-RAN Estimated Carbon Emission KPIs are defined in clause 6.7.7. of TS 28.554 [4]. Currently, the gNB Estimated Carbon Emission and NG-RAN Estimated Carbon Emission KPIs are limited to the scenario when they are powered using a single energy supply only. This use case is to study the gaps and enhancements to the energy-related characteristics associated with Managed Elements to satisfy the requirements in TS 22.261 [2]. This includes the following aspects for Network Elements and/or Network Functions:
1) Carbon emission: Enhancements (if necessary) for the carbon emission information Network Element and Network Function that can be made available and/or estimated in 3GPP management system.
2) Energy capacity: How energy capacity information of each energy supply of the Network Element can be made available and/or estimated in 3GPP management system.
3) Energy availability: How energy availability information of each energy supply of the Network Element can be made available and/or estimated in 3GPP management system.
|
ef58d30e4030b2362bf35c2b280da85f | 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 each energy supply of the Network Element.
PREQ-Energy_Related_Characteristics-3: The 3GPP management system should enable an authorized consumer to retrieve energy availability information of each energy supply of the Network Element.
|
ef58d30e4030b2362bf35c2b280da85f | 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 made.
|
ef58d30e4030b2362bf35c2b280da85f | 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.
|
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.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 duration for which the services are available, and this could be by degrading the network service performance. For example, the operators might want to prioritize the voice and emergency services (e.g. eMBB) over some data services (e.g., URLLC or Gaming service or Video service). The 3GPP management system can utilize the information related to energy rationing and other energy-related characteristics (such as energy capacity and energy availability), and provide mechanisms to the operator to prevent their network from going out of service and extend the duration for which the services are available.
Energy rationing and energy-related characteristics are defined in TS 22.261 [2].
The requirement specified in clause 6.15a.2.2 of TS 22.261 [2] includes providing means to enable the operator to degrade service performance to meet energy rationing constraints.
Another requirement specified in clause 6.15a.2.2 of TS 22.261 [2] include providing mechanisms to adjust communication service considering change of energy supply mix of the network as one of the factors. For example, adjustments based on the carbon emissions of different network functions.
This use case is to study
- management mechanisms to enable the operator to provide means to adapt the services provided by the network (e.g., by modifying the QoS requirements) to meet energy rationing control.
- management mechanisms to enable the network to adjust communication service (e.g., activate or deactivate communication services) adapting to energy-related characteristics.
|
ef58d30e4030b2362bf35c2b280da85f | 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 should enable the network to adjust communication services adapting to energy-related characteristics.
|
ef58d30e4030b2362bf35c2b280da85f | 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 made.
|
ef58d30e4030b2362bf35c2b280da85f | 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.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.1.3 Use case #<3>: Energy Rationing Information Management
| |
ef58d30e4030b2362bf35c2b280da85f | 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 rationing information in a network can be used to apply controlled energy usage and energy-saving in an operator’s network. This information could be crucial for maintaining network performance and achieving energy saving objectives. This information can help a consumer to know which services can be modified if a node which has energy rationing applied on it is used.
The energy rationing-related information in the network can assist in prioritizing a node for selection over others in a given scenario. The cause due to which the energy rationing is applied in an operator’s network can be related to regulatory requirements, economic reasons, electricity brownouts, or energy blackouts (full outage of energy supplier). Economic reason refers to raising the price of power (energy units) by an energy supplier during certain periods or locations to force operators to use less energy. In such cases, the MNO might need to reduce energy usage to keep its services economical. Electricity brownout refers to partial power reduction, energy blackout refers to a total energy outage at the energy supplier’s end (e.g., due to faults), requiring the MNO to rely on local power backup sources (battery banks, generators, etc.) and potentially reduce energy consumption to continue providing services until power from the energy supplier resumes.
|
ef58d30e4030b2362bf35c2b280da85f | 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.
|
ef58d30e4030b2362bf35c2b280da85f | 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 made.
|
ef58d30e4030b2362bf35c2b280da85f | 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 the use case.
5.1.X.3 Potential solutions
5.1.X.3.i Potential solution #<i>: <Potential Solution i Title>
5.1.X.3.i.1 Introduction
Editor's Note: This clause describes briefly the potential solution at a high-level.
5.1.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.1.X.4 Evaluation of potential solutions
Editor's Note: This clause provides the evaluation of potential solutions listed in 5.1.X.3.
|
ef58d30e4030b2362bf35c2b280da85f | 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.
|
ef58d30e4030b2362bf35c2b280da85f | 28.885 | 5.2.1 Use case #<1>: Energy consumption and Energy Efficiency estimation and reporting at per network slice granularity
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.