hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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 network management system (e.g., real-time analytics, network optimization engines, visualization dashboards, and audit services).
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].
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. For the case of multiple consumers requesting the same performance data, it causes the producer to retrieve and duplicate the relevant performance data from its cache for each connection individually.
By adopting a message bus architecture, the producer establishes connection(s) with the message bus and publishes the performance data only once. Consumers retrieve the data whenever they want (i.e., the consumer either pulls the data from the message bus or subscribes and receives messages pushed by the bus) - hence the principle of loose coupling. No additional connections are initiated by the producer, and no duplicate data reporting occurs on its side for the case that multiple consumers request the same performance data. As a comparison example between WebSocket and Message Bus for the case that multiple consumers request the same performance data as an assumption:
• for the WebSocket option, duplicate data reporting occurs N times on the producer's side for sending the data to the N consumers who request the same performance data.
• for the Message Bus option, depending on the collection job, no duplicate data reporting occurs on the producer's side for sending the data to the N consumers who request the same performance data because the only one copy of data buffered on the message bus broker (i.e., a middleware that facilitates communication between different participants by acting as an intermediary for messages) can be polled by all the consumers.
While the message bus architecture introduces certain operational considerations, such as the need for proper message category segmentation and consumer coordination management to avoid throughput bottlenecks. These aspects are addressed through established internal mechanisms and configuration practices. Such implementation details are outside the scope of this document. The message bus interface is not used on ManagedElement/NF level but only on management function level.
|
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 is meant for use at the management level and not at the managedElement/NF level. This solution also does not impact existing MnS services and can coexist beside such services as an additional option.
Figure 5.2.3.1-1: Potential solution for multipoint-to-multipoint management data streaming based on message bus
As shown in Figure 5.2.3.1-1, in this solution, Message bus data reporting MnS producers send management data to Message broking MnF using the message bus data reporting service based on message bus publishing protocol. Message bus data retrieval MnS consumers receive the management data using the message bus data retrieval service based on message bus retrieval protocol. This approach allows the same copy of management data produced by the Message bus data reporting MnS producer(s) to be shared across multiple Message bus data retrieval MnS consumers thus enabling multipoint-to-multipoint communication and a publishing-and-subscribing based communication pattern.
Editor’s note: The following aspects are FFS
1. What types of management data (e.g. PM) to be supported.
2. What specific message bus-based communication protocol to be supported (e.g. Kafka) and why?
3. How to do data access control.
4. How the information related to the message bus (e.g., end-point URIs) is conveyed or configured to the MnS producers and MnS consumers needs to be clarified.
5. Whether new MnSs is needed is to be studied
|
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 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.
|
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 should have the capability allowing to retrieve alarms that were active during a certain time window in the past.
REQ-4: The 3GPP Management system should have the capability allowing to retrieve the dates and times when the perceived severity of an alarm changed
REQ-5 The 3GPP management system should have the capability allowing to retrieve the periods when the retrieved historical alarms may not fully represent the real situation in the network at that point in time.
Editor’s Note: The size of the log should not be set by the standard, leaving it to be a vendor decision..
Open issues:
1. Which other parameters have to be stored if it changes during the alarm's active lifetime (beside severity)?
2. What kind of filter shall be available when retrieving the alarms (beside a timewindow in REQ-3)
• filter based on some(?) alarmRecord parameters
• filter for one subnet as source
• filter for a specific IOC as source
• filter for a given percievedSeverity or
• full JEX filter on all parameters
3. How can the consumer retrieve the historical alarms
• as a file
• some other method
|
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 the time dimension in the operation input parameters. The easiest case is to add a "time" parameter to the operation input parameters that specifies a time in the past for which the active alarms (as represented by their alarm records) shall be retrieved. Filtering capabilities of the retrieval operation may be used to scope the response to specific managed object instances. The target object of the retrieval operation is the already specified "AlarmList" object. Variations of this approach are possible, for example a time window may be specified in the request (for some managed objects), the response then returns the alarm records for all alarms that were active in this time window.
- The NRM is extended to allow for the representation of historical alarms and their alarm records. For retrieving these historical alarm record instances, the normal "getMOIAttributes" operation can be used.
The capability to retrieve historical alarms is expected to be available in a typical deployment only on Management Functions and not on Network Functions.
|
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 category called alarms. The historical alarms are then managed together with other kinds of management data.
|
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 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.
Based on 4G definitions in [11], when describing SW management in this document we use the following terminology:
Activation: Activation of software makes it ready to be used and the software starts providing service
Installation: Installation of software puts it into a form suitable for activation or use. (Activation may include steps like unpacking, unzipping, checks, but does not include starting to provide service.)
Fallback: The process of activating a previous SW version. (Fallback may involve moving to a previous configuration content of NRM).
Cancellation: Is the process where a consumer stops an ongoing operation (e.g. download, activation). If the process is stopped by the producer, it is considered a failure of the process not a cancellation.
Use cases for PNF SW management
The following are examples of possible/typical use-cases. (They are presented here as informative examples)
• UC1: Download software on MnS producer: In preparation for a software upgrade, relevant software artefacts are downloaded by suitable means to the MnS producer. After download, other preparatory steps (a.k.a. software installation) may be performed (such as unzipping, integrity validation) to make sure the software artefacts are suitable and ready for subsequent activation. This download/installation activity is typically not traffic-impacting and may happen some time before the software is activated. The activity might be triggered by an MnS consumer, or might be triggered by some other event (perhaps the installation of new hardware on the PNF, requiring a software upgrade). The download/installation is typically long-running, and its progress can be externally observed. At the end of this use case, the software is ready to be activated. In exceptional error situations (such as unsuitable software being installed; checksum errors), activation of this software will not be possible.
• UC2: Activate software: Previously downloaded/installed software is activated. The activation of the software brings the software into service, effectively replacing the previously running software. As part of the software activation, the PNF’s configuration may be automatically updated. Software activation may or may not be traffic-impacting, depending on the particulars of the PNF implementation. The activation activity is usually triggered by an MnS consumer; but may be triggered by an event or a scheduler. The software activation is typically long-running, and its progress can be externally observed. At the end of this use case, the activated software has been brought into service. In exceptional error situations, the software activation procedure is aborted, the previous software brought (back) into service, and any automated updates to the PNFs configuration undone.
• UC3: Cancellation: The software installation and activation are typically long-running operations. In some scenarios (e.g., ongoing emergency, slow/faulty O&M network, a mistake having been made), the ongoing operation is cancelled. A cancellation is typically triggered by an MnS consumer. After the cancellation, the MnS producer will be in the same state as it was before the operation started. It is possible to re-start the same operation.
• UC4: Fallback to previous software: After the PNF’s software has been successfully upgraded, after observing the system's behaviour for some time, a decision may be made that the upgraded software is unsatisfactory (perhaps it is functionally or performance-wise inferior to the previously installed software). In this case, a software fallback may be triggered. The software fallback will re-activate previously activated software and effectively repeat the steps of the software activation (see UC2) for the previously activated software.
• UC5: Remove inactive software (house cleaning): Software residing on the producer may become unneeded. Unneeded and in-active software is removed from the producer. This operation is typically triggered by the MnS consumer. At the end of this use case the in-active software has been removed from the PNF and therefore is not available anymore for fallback or activation. One typical case when software becomes unneeded is when a PNF’s software is successfully activated, and found to be operating satisfactorily (perhaps after having been observed for a while), other software still present on the PNF, but not in service, may be removed in order to free resources on the PNF.
Implementation considerations for further study
The producer should check the SW intended to be activated. Whether these checks are executed immediately after download, in a separate step, or at the beginning of activation is implementation dependent.
The producer may take additional preparatory steps before activation (e.g. unpacking the SW). Whether these are executed immediately after download, in a separate installation step or at the beginning of activation is implementation dependent.
Open issues for further study:
-Whether fallback shall be initiated by the consumer or by the producer or potentially both
- Whether activation shall be triggered explicitly by the consumer or automatically in the producer (e.g. by a scheduler) or both
Two modes shall be considered:
- a single step activation that includes download, any checks and activation. Activation may be immediate or delayed, triggered by a scheduler or some other condition.
- a multi-step activation, where after download, activation is executed as a separate step within the producer. The separate activation step shall be initiated by a consumer operation.
|
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 support the capability to monitor the progress and the result of software download, activation and fallback and any other vendor specific steps e.g. installation
REQ-SBMA-PNFSWM-4: The 3GPP management system should support the capability to allow the consumer to cancel all SW management operations e.g. download.
REQ-SBMA-PNFSWM-5: The 3GPP management system shall support the capability to allow the consumer to retrieve information about the SW on the producer, including its state.
Editor's note: The relation between this requirement and the inventory information is FFS.
REQ-SBMA-PNFSWM-6: The 3GPP management system shall support the capability to remove inactive SW from the producer.
REQ-SBMA-PNFSWM-7: The 3GPP management system shall support the capability to fallback to a previous SW version. Fallback may include returning to the previous configuration.
Editor's note: Unless the consumer or the producer is explicitly mentioned, the requirements do not imply whether the consumer or the producer initiates an activity. Unless explicitly specified the requirements do not imply whether an activity is executed as a separate step or potentially together with other activities. These issues are FFS.
|
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 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.
|
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 to:
- Define the Inventory NRMs, which are static for read only, for 5G which are communicated between MnS consumer and MnS producer;
- Reuse the content of 4G Inventory NRMs (i.e., InventoryUnit, InventoryUnitNE and InventoryUnitHw defined in TS 28.632 [15]) as a basis to model 5G inventory NRMs.
|
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 attributes or updating a single attribute (or attribute field).
A common use-case is updating a multiple attributes of multiple MOIs while leaving other attributes of the same MOIs unchanged. This is not properly handle and documented.
5.6.1.1 Problem when updating multiple MOIs
The changeMOIs operation should be used, as using individual createMOI, deleteMOI and modifyMOIAttributes operations would require using multiple operations requiring more processing and network resources. See TS 28.532 clause 11.1.1.4a.
Lets look at the following example where an immediate heartbeat is ordered in one ManagedElement and multiple attributes of a PerfMetricJob are updated in another ManagedElement.
5.6.1.1-1 Example configuration, modifying two separate objects
As multiple MOIs are to be modified by changeMOIs the
- baseObjectInstance shall identify a common ancestor MOI for all MOIs to-be-modified or to-be-reported, this could potentially be the root ManagedElement or the SubNetwork. As the ManagedElements may belong to different SubNetworks the baseObjectInstance can only be set to a common ancestor Subnetwork:
"baseObjectInstance": "SubNetwork=Buda-1"
The rest of the path to each argument must be defined in the "path" element using long multi-segment strings. Each "path" element needs to specify the path from the baseObjectInstance to the individual attribute or attribute field. E.g. for updating 5 attributes the following 5 "paths" have to be created and parsed:
"path": "/SubNetwork=Lagymanyos/ManagedElement=BudaME1/NtfSubscriptionControl=sub1/HeartbeatControl=hb1/triggerHeartbeatNtf"
"path": "/SubNetwork=Obuda/ManagedElement=BudaME17/PerfMetricJob=pmJob1/administrativeState"
"path": "/SubNetwork=Obuda/ManagedElement=BudaME17/PerfMetricJob=pmJob1/granularityPeriod"
"path": "/SubNetwork=Obuda/ManagedElement=BudaME17/PerfMetricJob=pmJob1/objectInstances"
"path": "/SubNetwork=Obuda/ManagedElement=BudaME17/ PerfMetricJob=pmJob1/scheduler"
- "node Value" shall contain the new value of each attribute(element) e.g. true, UNLOCKED ,30, SubNetwork=SubNetwork=Buda-1,Scheduler=Sched-1
This means that for each updated attribute(element) the consumer has to produce a long "path" element which the consumer has to read/parse.
A computationally cheaper solution would be to use the "path" element to address each modified MOI, and let the "nodeValue" element contain all attribute changes; to have an operation that allows modifying multiple attributes of an MOI while leaving other attributes of the same MOI unchanged. That would allow the consumer to address each MOI only once. In the example above that would mean creating/parsing only 2 "path" elements instead of 5.
In Netconf, JSON Merge patch or the 3GPP JSON Merge patch this is possible using the "merge" operation. While this is describe both for the Netconf_YANG and for the OpenAPI solution sets, it is not described on stage-2.
Note: While the above example is about a SubNetwork level producer, the same problem is valid for ManagedElement level producers as even inside a single ManagedElement there are IOCs that are embedded in the ManagedElement 5 levels deep.
5.6.1.2 Problem use-case when notifying the update of multiple MOIs
When reporting the changes made in the example of the previous clause the notification notifyMOIChanges should be used. The alternative, using some of the notifications notifyMOICreation, NotifyMOIDeletion, notifyMOIAttributeValueChanges, would mean sending multiple notifications instead of one, which requires more processing and network resources.
When using notifyMOIChanges just as described above we will need to set
"objectInstance": "SubNetwork=Buda-1"
5 separate moiChanges values will be needed, where the "path" element will specify the path to each attribute separately. (The replace operation towards the PerfMetricJob=pmJob1 MOI cannot be used as that would delete all not listed attributes.)
It would be good if we could collect all the attribute changes for a single MOI into one moiChanges value, thereby requiring only a single "path" element for each MOI to be created/parsed even if multiple attributes are updated.
An operation similar to "merge" would help. However, for notifyMOIChanges there is no such operation defined on stage-2 or stage-3.
With a proposed "merge" operation only 2 paths would need to be handled:
"path": "/SubNetwork=Lagymanyos/ManagedElement=BudaME1/NtfSubscriptionControl=sub1/HeartbeatControl=hb1"
"path": "/SubNetwork=Obuda/ManagedElement=BudaME17/PerfMetricJob=pmJob1"
|
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] and in 3GPP TS 32.158[18].
b) Add a new "merge" value to the "moiChanges.op" parameter of the notifyMOIChanges notification. This will allow
- the (base)ObjectInstance to identify a common ancestor MOI for all MOIs to-be-modified or to-be-reported.
- the use of a single "moiChanges" value for each MOI thus avoiding the need to create/read a separate "path" element for each attribute. Within the single moiChanges value
- the "path" shall to the individual MOI
- the "value" element shall contain all modified attribute values (created, deleted, updated)
Editor’s note: How to report a deleted attribute within merge for YANG based schemas is FFS. Maybe null as a value can be used, although that’s not part of RFC 7951..
As attribute (elements) can have a complex structure too, the merge operation shall be applicable for any kind of target: MOI, attribute, attribute field, or attribute element.
The "value" element shall not contain any child MOIs, thereby ensuring that changes to separate MOIs are reported as separate "moiChange" items.
|
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.101[20], figure 1 shows the discovery mechanism of MnS. MnS producer registers service to MnS registry. MnS consumer retrieves service from MnS registry. Then MnS consumer invokes service from MnS producer.
Figure 1. Discovery mechanism of MnS
In distributed deployment scenarios, MnS consumers may get multiple MnSs returned when retrieving MnSs from the MnS registry. MnS consumer has to decide which MnS to invoke. Figure 2 depicts the discovery mechanism in the distributed scenario. The current challenge is how an MnS consumer can select the most appropriate MnS from a set of discovered MnS(s) from the MnS registry.
Figure 2. Discovery mechanism in the distributed scenario
|
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
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.
|
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
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
2025-11
SA5#164
S5-255534
pCR TR 28.884 Update use case on management data streaming based on message bus
v0.2.0
2025-11
SA5#164
S5-255535
pCR TR 28.884 Message Bus principles integrated in SBMA
v0.2.0
2025-11
SA5#164
S5-255537
pCR TR 28.884 Management data streaming based on message bus potential solution 2
v0.2.0
2025-11
SA5#164
S5-255541
pCR TR 28.884 Add new use case on wide-area distributed deployment scenarios for SBMA
v0.2.0
2025-11
SA5#164
S5-255542
pCR TR 28.884 SW Management additions
v0.2.0
2025-11
SA5#164
S5-255544
pCR TR 28.884 Solution for inventory management
v0.2.0
2025-11
SA5#164
S5-255545
pCR TR 28.884 Historical alarm list requirements
v0.2.0
2025-11
SA5#164
S5-255546
Rel-20 pCR 28.884 Add NRM based solution for historical alarms
v0.2.0
2025-11
SA5#164
S5-255580
pCR TR 28.884 Merge operation
v0.2.0
2025-11
SA5#164
S5-255581
Rel-20 pCR 28.884 Add Management data based solution for historical alarms
v0.2.0
|
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.
- 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".
|
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: 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].
|
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 Function
S-NSSAI Single Network Slice Selection Assistance Information
|
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 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.
|
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 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.
|
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 made.
|
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 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.
|
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 should enable the network to adjust communication services adapting to energy-related characteristics.
|
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 made.
|
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 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.
|
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 made.
|
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 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.
|
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 consumption KPI at network slice (as defined in TS 23.501 [8]) granularity is missing in TS 28.554 [4]. This use case is to study the inconsistencies and enhance or introduce KPIs to enable the 5GC NF requirements.
Further, the requirements for energy consumption monitoring at per network slice granularity is specified in clause 6.15a.4.2 of TS 22.261 [2]. Several solutions identified for the key issues in TR 23.700-67 [9] include 5GC NFs to collect slice level energy consumption and energy efficiency from 3GPP management system.
The network slice identifiers in the 3GPP network are defined in clause TS 23.501 [8] as: "An S-NSSAI identifies a Network Slice.". Further the standardized and non-standardized values of S-NSSAI are defined as " An S-NSSAI can have standard values (i.e. such S-NSSAI is only comprised of an SST with a standardised SST value, see clause 5.15.2.2 of TS 23.501 [8] and no SD) or non-standard values (i.e. such S-NSSAI is comprised of either both an SST and an SD or only an SST without a standardised SST value and no SD). An S-NSSAI with a non-standard value identifies a single Network Slice within the PLMN with which it is associated.".
The problem with the existing Network Slice related EC and EE KPIs are described below:
- Network Slice Energy Consumption (EC) KPI is specified in clause 6.7.3.3 of TS 28.554 [4]. This is reported at KPI object NetworkSlice IOC (defined in clause 6.2.1 of TS 28.541 [7]), while “network slice” in TS 23.501 [8] are identified using S-NSSAI and PLMN ID as described above.
- Network slice Energy Efficiency (EE) KPIs are specified in clause 6.7.2 of TS 28.554 [4]. This is reported at KPI object NetworkSlice IOC (defined in clause 6.2.1 of TS 28.541 [7]), while “network slice” in TS 23.501 [8] are identified using S-NSSAI and PLMN ID as described above.
- The NetworkSlice IOC is defined in clause 6.3.1 of TS 28.541 [7], with attribute serviceProfileList that holds a list of ServiceProfile (defined in clause 6.3.3 of TS 28.541 [7]) supported by the NetworkSlice MOI. ServiceProfile is a data type with attribute pLMNInfoList (a list of data type PLMNInfo defined in clause 4.3.41 of TS 28.541 [7]) that defines which PLMN and S-NSSAI combinations that are assigned for the service to satisfy service requirements represented by the ServiceProfile in case of network slicing feature is supported. A NetworkSlice MOI can be configured, in attribute serviceProfileList, with a list of ServiceProfile value, where the list can hold one or more than one element. Each element in the list attribute serviceProfileList can be configured with a list PLMN and S-NSSAI combinations in attribute pLMNInfoList. Hence a NetworkSlice MOI can be configured with a list of PLMN and S-NSSAI combinations.
This use case is to study the enhancements to support for energy consumption and energy efficiency monitoring, estimation and reporting at per network slice (as defined in TS 23.501 [8]) granularity.
Editor’s note: This use case could be updated subject to conclusions of SA2 study (FS_EnergySys_Ph2) in TR 23.700-67 [9].
|
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.
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.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 be enhanced to report the following:
- Estimated ECns_SNSSAI: The KPI defined in clause 6.7.3.3 of TS 28.554 [4] is applicable for the estimated EC of an S-NSSAI.
- Estimated ECns KPI: The combined estimated EC for the NetworkSlice can be obtained by adding the Estimated ECns_SNSSAI of each SNSSAI that is configured in the NetworkSlice MOI.
Editor's Note: This clause needs to be updated for the KPI definition as per the KPI template in TS 28.554 [4].
5.2.1.3.i Potential solution #<i>: <Potential Solution i Title>
5.2.1.3.i.1 Introduction
Editor's Note: This clause describes briefly the potential solution at a high-level.
5.2.1.3.i.2 Description
Editor's Note: This clause further details the potential solution, including all of its aspects and any assumptions made.
|
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 identify the enhancements to ManagedNFProfile data type to support the energy saving and energy efficiency in the 5GC.
Editor’s note: This use case could be updated subject to conclusions of SA2 study (FS_EnergySys_Ph2) in TR 23.700-67 [9].
Editor’s note: The proposals for enhancements to 5GC NF Profile in 5GC NRM should be based on the conclusions of SA2 study (FS_EnergySys_Ph2) in TR 23.700-67 [9].
|
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 made.
|
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 use case.
5.2.X.3 Potential solutions
5.2.X.3.i Potential solution #<i>: <Potential Solution i Title>
5.2.X.3.i.1 Introduction
Editor's Note: This clause describes briefly the potential solution at a high-level.
5.2.X.3.i.2 Description
Editor's Note: This clause further details the potential solution, including all of its aspects and any assumptions made.
5.2.X.4 Evaluation of potential solutions
Editor's Note: This clause provides the evaluation of potential solutions listed in 5.2.X.3.
|
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 Solution i Title>
5.3.X.3.i.1 Introduction
Editor's Note: This clause describes briefly the potential solution at a high-level.
5.3.X.3.i.2 Description
Editor's Note: This clause further details the potential solution, including all of its aspects and any assumptions made.
5.3.X.4 Evaluation of potential solutions
Editor's Note: This clause provides the evaluation of potential solutions listed in 5.3.X.3.
|
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 supply of renewable energy varies substantially by time and location. There is a need for the 3GPP management system to support to report of renewable energy consumption on different granularities (e.g., NF, NE, Sub-network), and the total energy consumption considering energy consumption from energy supplies with renewable and non-renewable sources in order to estimate of renewable energy consumption, and to report the renewable energy consumption for different granularities.
Therefore, the 3GPP management system need to support to provide the renewable energy consumption based on energy related information obtained from various sources, or to provide the renewable energy consumption for different granularities, and support to report this information to authorized consumers, e.g., EIF.
|
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 made.
|
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 energy consumption separately for each energy supply to calculate accurate carbon emissions. The operator configures the system to associate each energy supply. The operator and the internal optimization need the 3GPP management system to collect EC data per energy supply and report them.
The existing energy consumption measurements are based on PEE measurements and assume a single energy supply for the NE (represented by ManagedElement) and do not provide energy consumption related information at the energy supply granularity. This use case identifies the existing measurements and studies the enhancements that need to be supported.
Energy supply information can be associated with the Managed Elements (representing the Network Elements) using EnergyInfoGroup IOC (see clause 8.3.3. of TS 28.310 [3]). Energy-related information for each energy source (see EnergySourceInfo defined in clause 8.3.2 of TS 28.310 [3]) of the energy supply (see EnergySupplyInfo defined in clause 8.3.1 of TS 28.310 [3]) includes information of different energy source, with source type, carbon emission factor, renewable and non-renewable energy information.
Power, Energy and Environmental (PEE) measurements are defined in clause 5.1.1.19 of TS 28.552 [10], and PNF Energy consumption for ManagedElement is defined in clause 5.1.1.19.3 of TS 28.552 [10].
Energy consumption related KPIs are defined in clause 6.7.3 of TS 28.554 [4]. gNB Estimated Carbon Emission and NG-RAN Estimated Carbon Emission KPIs are defined in clause 6.7.7 of TS 28.554 [4]. A Network Element (represented by Managed Element) can be powered by one or more energy supplies (see TS 28.310 [3]). The Carbon Emission related KPIs defined in TS 28.554 [4] are currently restricted to the scenarios when a Network Element is powered by a single energy supply. This limitation is due to the lack of EC measurements at a per energy supply granularity for a Network Element.
Energy consumption of a Network Element is essential for monitoring and reporting of carbon emissions, carbon intensity, and network energy optimization use cases considering energy supply mix, and energy-related characteristics (defined in TS 22.261 [2]).
This use case is to study the enhancements to enable measurements and reporting of EC of a Network Element at a per energy supply granularity.
|
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 made.
|
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 scenarios. The existing EE and EC KPIs do not consider network sharing scenarios, and do not provide KPIs at operator-specific (i.e., PLMN-ID) granularity.
Following are the currently supported measurements and KPIs related to energy consumption and energy efficiency:
• Power, Energy and Environmental (PEE) measurements are defined in clause 5.1.1.19 of TS 28.552 [10], and PNF Energy consumption for ManagedElement is defined in clause 5.1.1.19.3 of TS 28.552 [10].
• Energy consumption and energy efficiency related KPIs are defined in clause 6.7 of TS 28.554 [4].
This use case is to study the enhancements to enable monitoring and/or estimation of energy consumption and energy efficiency KPIs and reporting of a NG-RAN at operator-specific (i.e., at a per PLMN-ID) granularity in network sharing scenarios.
|
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 made.
|
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 slice types.
In particular, SST with value 6 - High Data-rate & Low-Latency Communication (HDLLC)—has been introduced to handle Extended Reality Media (XRM) referred to Table 5.15.2.2-1 in TS 23.501 [8]. This service type is characterized by stringent requirements for high data throughput and low latency.
This use case is to study the estimation of EE KPI of HDLLC slice.
|
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 made.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 5.4.4.4 Evaluation of potential solutions
| Editor's Note: This clause provides the evaluation of potential solutions listed in 5.4.4.3.
5.4.X Use case #<X>: <Use case title>
5.4.X.1 Description
Editor’s note: This clause provides a description of the use case.
5.4.X.2 Potential requirements
Editor’s note: This clause captures potential requirements for the use case.
5.4.X.3 Potential solutions
5.4.X.3.i Potential solution #<i>: <Potential Solution i Title>
5.4.X.3.i.1 Introduction
Editor's Note: This clause describes briefly the potential solution at a high-level.
5.4.X.3.i.2 Description
Editor's Note: This clause further details the potential solution, including all of its aspects and any assumptions made.
5.4.X.4 Evaluation of potential solutions
Editor's Note: This clause provides the evaluation of potential solutions listed in 5.4.X.3.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 6 Conclusions and recommendations
| |
a0af2a6390198051f207bb132b271100 | 28.885 | 6.1 Enhancements to support energy efficiency as a service criteria
| Editor’s Note: This clause is to summarize the identified use cases and to add conclusions and recommendations for a potential Work Item.
6.1.x Use case #<X>: <Use case title>
Editor’s note: This clause captures conclusions and recommendations for the use case.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 6.2 Enhancements to support the information required by Energy Information Function (EIF)
| 6.2.x Use case #<X>: <Use case title>
Editor’s note: This clause captures conclusions and recommendations for the use case.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 6.3 Improve energy saving, energy efficiency and reducing carbon footprint of 5G network
| 6.3.x Use case #<X>: <Use case title>
Editor’s note: This clause captures conclusions and recommendations for the use case.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 6.4 Enhancements to Energy Consumption and Energy Efficiency measurements and KPIs
| 6.4.x Use case #<X>: <Use case title>
Editor’s note: This clause captures conclusions and recommendations for the use case.
Annex A:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
-
N/A
-
-
-
TR skeleton
0.0.0
2025-10
SA5#163
S5-254683
pCR
-
-
pCR on Rel-20 TR 28.885 Add TR structure
0.1.0
2025-10
SA5#163
S5-254698
pCR
-
-
pCR on Rel-20 TR 28.885 Add new use case support of energy-related characteristics
0.1.0
2025-10
SA5#163
S5-254699
pCR
-
-
pCR on Rel-20 TR 28.885 Add new use case related to service adjustments to adapt to energy-related characteristics
0.1.0
2025-10
SA5#163
S5-254700
pCR
-
-
Rel-20 pCR TR 28.885 Add New Use Case on Energy Rationing management
0.1.0
2025-10
SA5#163
S5-254736
pCR
-
-
pCR TR 28.885 Add use case and requirements for renewable energy consumption
0.1.0
2025-10
SA5#163
S5-254738
pCR
-
-
pCR on Rel-20 TR 28.885 Add new use case for enhancements to reporting EC and EE at per network slice granularity
0.1.0
2025-10
SA5#163
S5-254739
pCR
-
-
pCR on Rel-20 TR 28.885 Add new use case to study Enhancements to NF Profile to support energy saving and energy efficiency
0.1.0
2025-10
SA5#163
S5-254740
pCR
-
-
pCR on Rel-20 TR 28.885 Add new use case to study measuring of EC of NE at per Energy Supply granularity
0.1.0
2025-10
SA5#163
S5-254741
pCR
-
-
pCR on Rel-20 TR 28.885 Add new use case to study EC and EE per PLMNID in Network sharing scenario
0.1.0
2025-11
SA5#164
S5-255553
pCR
-
-
pCR on Rel-20 TR 28.885 Add potential solution for Enhancements to network slice EC KPIs
0.2.0
2025-11
SA5#164
S5-255670
pCR
-
-
pCR on Rel-20 TR 28.885 Add new use case for supporting estimation of EE KPI of HDLLC slice
0.2.0
2025-11
SA5#164
-
-
-
-
v0.2.0 published in S5-255474 was incomplete and required v0.3.0 in S5-255708
0.3.0
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 1 Scope
| The present document …
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.