hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 7.3.3 Service Flows | 1. Alice’s vehicle wants to know the complete situation of the accident vehicle. So, her car sends the request to 5G system to select the vehicles located in different positions /direction and a certain distance to the accident vehicle
2. Based on the candidate UE list located in different position to the accident vehicle, the Alice’s vehicle starts to establish direction device connection to each of the selected vehicles and transmit the 3D object detection model to them via direct device connection.
3. Alice’s vehicle receives the inference result the 3D object detection model made by the selected vehicles and further aggregate the results to acquire a highly accurate 3D object reconstruction of the accident vehicles.
4. Alice’s vehicle may also share the aggregated result to other vehicles or the application server so that they can use it to assist their own intelligent driving as well. |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 7.3.4 Post-conditions | Thanks to candidate UE list provided by the 5G system and inference results provided by other vehicles, Alice’s vehicle can get the situation of the accident scene accurately and make a path planning to avoid road congestion effectively. |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 7.3.5 Existing features partly or fully covering the use case functionality | In TS 22.261 clause 6.40.2, there is a requirement for FL scenario, i.e. the 5GS to assist 3rd party to determine FL members. But it is between the 5GS NF and the 3rd party. For the distributed joint inference use case, the communication is between the 3rd party UE and the UE1 or other UEs. The existing 5G system cannot support to help find the suitable UEs request by the 3rd party UE via direct device connection.
Subject to user consent, operator policy and regulatory requirements, the 5G system shall be able to expose information (e.g. candidate UEs) to an authorized 3rd party to assist the 3rd party to determine member(s) of a group of UEs (e.g. UEs of a FL group). |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 7.3.6 Potential New Requirements needed to support the use case | |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 7.3.6.1 Potential Functionality Requirements | [P.R.7.3-001] Subject to user consent, operator policy, and 3rd party’s request, 5GS shall be able to provide and configure the QoS applied to a group of UEs communicating via direct device connection (e.g. part of a joint AIML inference task).
NOTE: the above requirement assumes unicast type of communication.
[P.R.7.3-002] Subject to user consent, operator policy and 3rd party’s request, the 5G system shall be able to provide information of certain UEs (e.g. located in a specific location) to an authorized 3rd party (e.g. to assist a joint AIML task using direct device communication). |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 7.3.6.2 Potential KPI Requirements | According to [24], some typical 3D objection model size and transmission KPI are listed in the table below
Model Type
Max allowed DL end-to-end latency
Experienced data rate
(PC5)
Model size
Communication service availability
PointPillar
1s
0.14 Gbit/s
18 MByte
99.99 %
SECOND
1s
0.16 Gbit/s
20 MByte
99.99 %
PV-RCNN
1s
0.4 Gbit/s
50 MByte
99.99 %
Voxel R-CNN (Car)
1s
0.22 Gbit/s
28 MByte
99.99 % |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 8 Consolidated potential requirements and KPIs | |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 8.1 Consolidated potential requirements | |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 8.1.1 Authorization | Table 8.1.1 –Authorization Consolidated Requirements
CPR #
Consolidated Potential Requirement
Original PR #
Comment
CPR 8.1.1-1
Based on user consent, operator policy and trusted 3rd party request, the 5G system shall support a means to authorize specific UEs to transmit data (e.g. AI-ML model data for a specific application,) via direct divice connection in a certain location and time.
P.R.5.2.6-001
P.R.6.2-001
CPR 8.1.1-2
Based on user consent, operator policy, and trusted 3rd party’s request, the 5G system shall be able to provide means for an operator to authorize specific UEs who participate in the same service (e.g. for the same AI-ML FL task) to exchange data with each other via direct device connection, e.g. when direct network connection cannot fulfil the required QoS.
P.R.6.1-002
P.R.7.1-001
CPR 8.1.2-3
Based on user consent, operator policy and trusted 3rd party request, the 5G system shall be able to dynamically add or remove specific UEs to/from the same service (e.g. a AI-ML federated learning task) when communicating via direct device connection.
P.R.7.1-002 |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 8.1.2 QoS control | Table 8.1.2 – QoS control Consolidated Requirements
CPR #
Consolidated Potential Requirement
Original PR #
Comment
CPR 8.1.2-1
Based on user consent and operator policy, the 5G system shall be able to provide means for the network to configure and modify remote UEs’ communication QoS , when a relay UE is involved, e.g., to satisfy end to end latency for proximity-based work task offloading.
NOTE 1: for proximity-based work task offloading, the data packet size transmitted over the sidelink and Uu parts of the UE indirect network connection can be different.
P.R.5.1.6-001
P.R.5.2.6-005
CPR 8.1.2-2
Subject to user consent and operator policy, the 5G system shall be able to support configuration of the QoS (e.g., latency, reliability, data rate) of a communication path using direct device connection, e.g., for AI-ML data transfer.
P.R.5.2.6-004
CPR 8.1.2-3
Based on user consent, operator policy and trusted 3rd party request, the 5G system shall be able to support means to monitor the QoS characteristics (e.g. data rate, latency) of traffic transmitted via direct device connection or relayed by a UE, and 5G network expose the monitored information to the 3rd party.
NOTE: The monitoring information doesn’t include user position-related data.
P.R.6.1-001
CPR 8.1.2-4
Subject to user consent, operator policy and trusted 3rd party request, the 5G system shall be able to provide means the network to predict and expose QoS information changes for UEs’ traffic using direct or indirect network connection (e.g., bitrate, latency, reliability).
P.R.5.2.6-002
CPR 8.1.2-5
The 5G system shall be able to support a mechanism for a trusted third-party to negotiate with the 5G system for a suitable QoS for direct device connections of multiple UEs exchanging data with each other (e.g. a group of UEs using the same AI-ML service)
P.R.6.1-003
CPR 8.1.2-6
Based on user consent, operator policy and trusted 3rd party’s request, the 5G system shall be able to support and provision an aggregated QoS for multiple remote UEs served by a relay UE.
P.R. 7.2-001
P.R. 7.2-002
CPR 8.1.2-7
Based on user consent, operator policy and trusted 3rd party’s request, the 5G system shall be able to support configuring specific QoS limitations applied to multiple UEs communicating via direct device connection (e.g. part of a joint AI-ML inference task).
NOTE: the above requirement assumes unicast type of communication.
P.R.7.3-001 |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 8.1.3 Information Exposure | Table 8.1.3 – Member selection Consolidated Requirements
CPR #
Consolidated Potential Requirement
Original PR #
Comment
CPR 8.1.3-1
Subject to user consent, regulation, trusted 3rd party’s request and operator policy, the 5G network shall be able to expose information to assist the 3rd party to determine candidate UEs for data transmission via direct device connection (e.g. for AIML model transfer for a specific application).
NOTE: the information does not include user’s specific positioning and can include QoS information
P.R.6.2-002
CPR 8.1.3-2
Subject to user consent, operator policy, regulation and trusted 3rd party’s request, the 5G network shall be able to expose information of certain UEs using the same service to the 3rd party (e.g. to assist a joint AIML task of UEs in a specific area using direct device communication)
NOTE: the information does not include user’s exact positioning information.
P.R.7.3-002 |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 8.1.4 Charging | Table 8.1.4 – Charging Consolidated Requirements
CPR #
Consolidated Potential Requirement
Original PR #
Comment
CPR 8.1.4-1
The 5G system shall be able to support charging mechanisms for multiple UEs exchanging data for the same service using the direct device connection (e.g. for AI-ML applications).
PR.5.1.6-003 |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 8.2 Consolidated potential KPIs | |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 8.2.1 Split AI/ML operation between AI/ML endpoints | Table 8.1-1 KPI Table of Split AI/ML operation between AI/ML endpoints for AI inference by leveraging direct device connection
Max allowed end-to-end latency (NOTE 1)
UL Payload size (Intermediate data size)
(NOTE 1)
UL Experienced data rate
(NOTE 1)
Service area dimension
Communication service availability
(NOTE 1)
Reliability
(NOTE 1)
Remarks
2–100 ms
≤1.5 Mbyte for each frame
≤720 Mbps
Proximity-based work task offloading for Remote driving, AR displaying/gaming, remote-controlled robotics, video recognition and One-shot object recognition
10 ms
≤ 1.6 MByte
(8 bits data format)
≤1.28 Gbps
900 m2
(30 m x 30 m)
99.999 %
99.99 %
Local AI/ML model split on factory robots
10 ms
≤ 6.4 Mbyte
(32 bits data format)
≤1.5 Gbps
Local AI/ML model split on factory robots
NOTE 1: The KPIs in the table apply to UL data transmission in case of indirect network connection.. |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 8.2.2 AI/ML model/data distribution and sharing by leveraging direct device connection | Table 8.1-1 KPI Table of AI/ML model/data distribution and sharing by leveraging direct device connection
Max allowed end-to-end latency
(NOTE 1)
Experienced data rate
(NOTE 1)
Payload size
(NOTE 1)
Communication service availability
(NOTE 1)
Remark
1s
≤1.92 Gbit/s
≤240 MByte
99.9 %
AI Model Transfer Management through Direct Device Connection
3s
≤81.33 Mbyte/s
≤244 MByte
-
transfer learning for trajectory prediction
NOTE 1: The KPIs in the table apply to data transmission using direct device connection.
NOTE 2: The AI/ML model data distribution is for a specific application service |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 8.2.3 Distributed/Federated Learning by leveraging direct device connection | Table 8.1-1 KPI Table of Distributed/Federated Learning by leveraging direct device connection
Payload size
(NOTE 1)
Maximum latency
Experienced data rate
Reliability
Remark
132 MByte
2-3 s
≤528 Mbit/s
Direct device connection assisted Federated Learning (Uncompressed model)
Asynchronous Federated Learning via direct device connection
≤50 MByte
1 s
≤220 Mbit/s
99.99%
NOTE 1: The KPIs in the table apply to both UL and DL data transmission in case of indirect network connection. |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 9 Conclusion and recommendations | Regarding the Feasibility Study on traffic characteristics and performance requirements for AI/ML Model Transfer via direct device connection, the TR analyses use cases of AIML-Ph2 as follows: • Use cases on split AI/ML operation between AI/ML endpoints for AI inference by leveraging direct device connection: ◦ Proximity based work task offloading for AI/ML inference ◦ Local AI/ML model split on factory robots. • Use cases on AI/ML model/data distribution and sharing by leveraging direct device connection: ◦ AI Model Transfer Management through Direct Device Connection; ◦ 5GS assisted transfer learning for trajectory prediction. • Use cases on Distributed/Federated Learning by leveraging direct device connection: ◦ Direct device connection assisted Federated Learning; ◦ Asynchronous FL via direct device connection; ◦ 5GS assisted distributed joint inference for 3D object detection; It is recommended to proceed with normative work including the potential new requirements identified by this TR. The consolidated potential requirements in Clause 8 are the baseline for the subsequent normative work. Annex A: Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2022.05 SA1#98e S1-221010 - - - Initial Skeleton 0.0.0 2022.09 SA1#99e - - - Inclusion of pCRs agreed at SA1#99: S1-222397; S1-222158; S1-222398; S1-222399; S1-222400; S1-222401 0.1.0 2022.11 SA1#100 Inclusion of pCRs agreed at SA1#100: S1-223629; S1-223630; S1-223713; S1-223732 0.2.0 2023.02 SA1#101 Inclusion of pCRs agreed at SA1#101: S1-230783; S1-230393; S1-230394; S1-230087; S1-230396; S1-230784; S1-230744 0.3.0 2023-03 SA#99 SP-230224 MCC clean-up for presentation to SA#99 1.0.0 2023-05 SA1#102 Inclusion of pCR agreed at SA1#102： S1-231104, S1-231509, S1-231797, S1-231741, S1-231512 1.1.0 2023-06 SA#100 SP-230513 MCC clean-up for approval by SA#10 2.0.0 2023-06 SA#100 SP-230513 Raised to v.19.0.0 by MCC following approval by SA#10 19.0.0 2023-09 SA#101 SP-231023 0002 1 F Updating of KPI consolidated requirements 19.1.0 2023-09 SA#101 SP-231023 0001 3 F Updating of functional consolidated requirements 19.1.0 |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 1 Scope | The present document describes use cases related to the following three Roaming Value-Added Services (RVAS) that are enabled by the PLMN for 5GS roaming:
• Welcome SMS
• Steering of Roaming (SoR) during the registration procedure
• Subscription-based routing to a particular core network (e.g., in a different country)
Potential requirements are derived for these three services and consolidated in a dedicated chapter. The report ends with recommendation regarding the continuation of the work.
NOTE: This document is not expected to introduce any changes to the security mechanisms between operators, and responsible groups will verify that 5GS security mechanisms are not negatively impacted by these requirements. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 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 33.501: "Security architecture and procedures for 5G System"
[3] 3GPP TR 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)".
[4] 3GPP TS 22.011: "Service Accessibility". |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 3 Definitions of terms, symbols and abbreviations | |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 3.1 Terms | For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
RVAS Roaming Value-Added Services |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 4 Overview | Roaming Value-Added Services (RVAS) form part of the roaming services ecosystem and have traditionally been provided by either the PLMN or outsourced to a fully trusted entity. The RVAS provider acting on behalf of the PLMN could be any trusted 3rd party. The focus of this work is on RVAS enabled by the PLMN for 5GS roaming.
With the introduction of e2e encryption for roaming in 5GS [2], it is in some cases not possible for the trusted entities to provide RVAS in a proprietary way and they therefore need to be standardized in order to work in a multi-vendor environment.
This report describes the following three RVAS that are enabled by the PLMN for 5GS roaming:
• Welcome SMS
• Steering of Roaming (SoR) during the registration procedure
• Subscription-based routing to a particular core network (e.g. in a different country) |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5 Use cases | |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.1 Use case on welcome SMS | |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.1.1 Description | A welcome SMS is a SMS sent to a roaming subscriber’s UE when the UE is registered in a new network for the first time. The SMS typically follows a predefined template and is sent on behalf of the home operator and may contain relevant information related to the visited country e.g., the cost to call home, how to reach the operator’s customer service etc.
The use case describes how the home operator identifies that a user is registered in a new network and trigger sending a welcome SMS to the UE. The formatting and sending of the welcome SMS are done by an application server in the same way as many other SMS applications and is not described further in the use case. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.1.2 Pre-conditions | A user X has a subscription with operator MNO1.
User X is going to a country for trip and brings the phone.
One of the operators in the country is MNO2. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.1.3 Service Flows | User X arrives to the countries capital airport and turns off airplane mode on the UE at arrival.
The UE register to MNO2’s network.
MNO2 forwards the registration to user X’s HPLMN (i.e., MNO1).
MNO1 identifies that User X is registered in a new network and initiates a welcome SMS using a northbound API including the information about MNO2’s network and the needed subscriber information.
Either the HPLMN or a trusted 3rd party will trigger a welcome SMS to user X’s UE. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.1.4 Post-conditions | Shortly an SMS is delivered to the UE with a welcome SMS containing useful information related to the new country. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.1.5 Existing features partly or fully covering the use case functionality | The functionality to send MT SMS to the UE is “old as a rock” and is defined in a normative annex in 3GPP TS 22.003 [3]. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.1.6 Potential New Requirements needed to support the use case | [PR 5.1.6-001] The 5G system shall be able to support mechanisms for the HPLMN to provide a notification, including equipment and subscription identifiers, to a trusted application server when a UE successfully registers in a VPLMN. In response to the notification, the trusted application server can indicate specific actions to the HPLMN (e.g., send an SMS to the UE).
NOTE: The trusted application server can be hosted by the home operator or a trusted 3rd party and is out of 3GPP scope. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.2 Use case on Steering of Roaming (SoR) during the registration procedure | |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.2.1 Description | HPLMNs can steer their subscribers to preferred partner networks in case of roaming by means of issuing commands and updating the Operator Controlled PLMN Selector list on the USIM, either by using SMS or via signalling, as defined in TS 22.011 [2].
Additionally, for more short-term balancing of distribution across VPLMNs, operators use mechanisms to reject registration attempts from some share of UEs to certain VPLMNs to make them select a different VPLMN.
Both mechanisms – SoR as defined in 3GPP and the here described SoR during the registration procedure – can be applied in parallel by a HPLMN.
This use case describes how the home operator identifies that a roaming user attempts to register in a new network and triggers the sending of reject messages to the UE, resulting in the UE attempting to register to another VPLMN. The details of how often a reject is sent to a particular UE to achieve the desired result and to prevent the UE from being without a network, are left to the application server and not described here. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.2.2 Pre-conditions | Users X and Y have a subscription with operator HPLMN1.
Both users X and Y are travelling to another country, where two networks are available – VPLMN1 and VPLMN2. Both networks have a roaming agreement with HPLMN1.
VPLMN1 has a higher priority for both users. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.2.3 Service Flows | Users X and Y arrive at the country and switch on their phones. According to existing procedures both UEs select VPLMN1 as their first choice for registration and try to register on that network.
VPLMN1 forwards the registration request messages of the UEs of users X and Y to the HPLMN1.
HPLMN1 recognises the registration attempts and invokes the steering service via a northbound API. The steering service, hosted by the HPLMN or some trusted 3rd party, decides if some steering action is needed for any of the UEs.
In this use case it decides to allow the UE of user X to register on VPLMN1 whereas user Y’s UE should not use VPLMN1.
The steering service triggers the steering action using the northbound API for user Y’s UE, which results in a reject message being sent to this UE, including an appropriate reason for the rejection. The registration process for user X’s UE is not affected. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.2.4 Post-conditions | While the UE of user X successfully registered to VPLMN1 the UE of user Y selects VPLMN2 as the only other available network and registers there.
If more than one remaining VPLMN is available, the UE picks one of them according to network selection procedures. The process of rejecting could be repeated as needed. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.2.5 Existing features partly or fully covering the use case functionality | Registration to networks and rejecting registration attempts with different information corresponding to the reason for rejection, causing the UE to search for other networks. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.2.6 Potential New Requirements needed to support the use case | [PR 5.2.6-001] The 5G system shall be able to support mechanisms enabling the HPLMN to:
- provide a notification, including subscription and equipment identifiers, to a trusted application server when a UE tries to register in a VPLMN
- receive a notification reply from the trusted application server indicating specific actions to the HPLMN e.g., reject UE registration (with a specific cause), trigger a SoR command.
NOTE: The trusted application server can be hosted by the home operator or a trusted 3rd party and is out of 3GPP scope. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.3 Use case on Subscription-based routing to a particular core network | |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.3.1 Description | Some operators use more than one PLMN ID, e.g., multi-national operators. Due to certain business and operational demands, it might be necessary to route signalling traffic of a certain customer segment, typically from a certain IMSI range of USIMs, of a PLMN to another PLMN and to further handle the subscriber there. This means the signalling is not handled by the "real" HPLMN (according to MNC and MCC) but by some alternative PLMN.
This e.g. enables the case where several national subsidiaries of a multi-national operator offer various services for different customer segments but for operational efficiency the actual service for a certain group is provided by only one dedicated network.
This mechanism is not visible for the UE and it therefore do not need any additional features to support this RVAS. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.3.2 Pre-conditions | Subscriptions a, b, c and d are with operator MNO1.
Subscriptions b and c are part of a certain customer segment X and this information is part of the subscription.
MNO1 has an agreement with MNO2 that MNO2 shall handle the signalling of subscriptions of all UEs belonging to the customer segment X. For this purpose, there is a connection between the networks of MNO1 and MNO2. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.3.3 Service Flows | |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.3.3.1 Non roaming case | The UEs of subscribers a, b, c and d attach to the PLMN of MNO1.
The network recognizes subscriptions b and c to be part of customer segment X and forwards the signalling to the PLMN of MNO2 via the pre-established connection.
Subscriptions a and d are not affected.
Later, subscription c is removed from customer segment X by customer care. This results in removal of the corresponding information in the subscription. From now on signalling related to subscription c will be handled by the network of MNO1 again.
Further on, subscription a is added to the customer segment X by customer care and subscription data are updated accordingly. So, signalling related to subscription a will be handled by the network of MNO2.
The UEs of subscribers c and a are not aware of these updates. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.3.3.2 Roaming case | Subscribers a, b, c and d attach to a VPLMN. The corresponding signalling is routed to their HPLMN (network of MNO1).
The further procedure is the same as in the non-roaming case: The HPLMN recognizes subscriptions b and c to be part of customer group X and forwards the signalling to the PLMN of MNO2 via the pre-established connection. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.3.4 Post-conditions | Subscriptions of customer group X are handled by the network of MNO2, all other subscriptions by the regular HPLMN MNO1. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.3.5 Existing features partly or fully covering the use case functionality | Subscriptions can contain a routing indicator which might be re-used for assigning a subscription to a certain customer group which requires routing to a different network. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 5.3.6 Potential New Requirements needed to support the use case | [PR 5.3.6-001] The 5G system shall be able to support a mechanism for forwarding signalling traffic pertaining to UEs of specific subscribers from their HPLMN to a target PLMN, e.g., to enable further handling of those UEs by the target PLMN. The forwarding mechanism shall minimize signalling traffic in the HPLMN, e.g., by using efficient means to forward traffic from selected UEs.
NOTE 1: The above requirement assumes that the HPLMN has an agreement with the target PLMN and routing policies are in place.
NOTE 2: In case of UEs connected via a VPLMN, it is assumed that signalling traffic is forwarded to the target PLMN by the HPLMN. |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 6 Consolidated potential requirements | Table 6-1 –Consolidated Potential Requirements
CPR #
Consolidated Potential Requirement
Original PR #
Comment
CPR 6-001
The 5G system shall be able to support mechanisms for the HPLMN to provide a notification, including equipment and subscription identifiers, to a trusted application server when a UE successfully registers in a VPLMN. In response to the notification, the trusted application server can indicate specific actions to the HPLMN (e.g., send an SMS to the UE).
NOTE: The trusted application server can be hosted by the home operator or a trusted 3rd party and is out of 3GPP scope.
PR 5.1.6-001
CPR 6-002
The 5G system shall be able to support mechanisms enabling the HPLMN to:
- provide a notification, including subscription and equipment identifiers, to a trusted application server when a UE tries to register in a VPLMN
- receive a notification reply from the trusted application server indicating specific actions to the HPLMN e.g., reject UE registration (with a specific cause), trigger a SoR command.
NOTE: The trusted application server can be hosted by the home operator or a trusted 3rd party and is out of 3GPP scope.
PR 5.2.6-001
CPR 6-003
The 5G system shall be able to support a mechanism for forwarding signalling traffic pertaining to UEs of specific subscribers from their HPLMN to a target PLMN, e.g., to enable further handling of those UEs by the target PLMN. The forwarding mechanism shall minimize signalling traffic in the HPLMN, e.g., by using efficient means to forward traffic from selected UEs.
NOTE 1: The above requirement assumes that the HPLMN has an agreement with the target PLMN, and routing policies are in place.
NOTE 2: In case of UEs connected via a VPLMN, it is assumed that signalling traffic is forwarded to the target PLMN by the HPLMN.
PR 5.3.6-001 |
46022d2d65fd68fe9fd8662086a95712 | 22.877 | 7 Conclusion and recommendations | This technical report provides use cases and potential new requirements for the three RVAS: • Welcome SMS • Steering of Roaming (SoR) during the registration procedure • Subscription-based routing to a particular core network (e.g., in a different country) The resulting service requirements have been consolidated and can be found in chapter 6. It is recommended to consider the consolidated requirements identified in this TR as the baseline for subsequent normative work. Annex A (informative): Change history Change history Date Meeting Tdoc CR Rev Cat Subject/Comment New version 2022-08 SA1#99-e S1-202010 TR skeleton 0.0.0 2022-09 SA1#99-e S1-222407, S1-222408, S1-222409, S1-222410, S1-222411 Scope, Overview Welcome SMS Use case SoR during registration IMSI based routing 0.1.0 2022-11 SA1#100 S1-223375 S1-223376 S1-223388 S1-223378 Editorial clean-up Update of use case 3 Consolidation Conclusion 0.2.0 2022-12 SA#98e SP-221265 MCC clean-up for presentation for one-step approval to TSG SA 1.0.0 2022-12 SA#98e SP-221265 Raised to v.19.0.0 following SA#98e one-step approval 19.0.0 |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 1 Scope | The present document provides stage 1 use cases and potential 5G requirements on the following aspects regarding enhancements to Energy Efficiency of 5G network and application service enabler aspects:
- Defining and supporting energy efficiency criteria as part of communication service to user and application services;
- Supporting information exposure of systematic energy consumption or level of energy efficiency to vertical customers;
- Gap analysis between the identified potential requirements and existing 5GS requirements or functionalities;
- Potential requirements on security, charging and privacy aspects. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 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] ETSI ES 201 554: "Environmental Engineering (EE); Measurement method for Energy efficiency of Mobile Core network and Radio Access Control equipment".
[3] ETSI ES 203 228: "Environmental Engineering (EE); Assessment of mobile network energy efficiency".
[4] GSMA Intelligence: "Going green: benchmarking the energy efficiency of mobile", June 2021.
[5] 3GPP TR 21.866: "Study on Energy Efficiency Aspects of 3GPP Standards".
[6] 3GPP TS 28.310: "Management and orchestration; Energy efficiency of 5G".
[7] 3GPP TR 28.813: "Management and orchestration; Study on new aspects of Energy Efficiency (EE) for 5G".
[8] 3GPP TR 38.864: "Study on network energy savings for NR ".
[9] ETSI ES 202 336‑1: "Environmental Engineering (EE); Monitoring and control interface for infrastructure equipment (power, cooling and building environment systems used in telecommunication networks); Part 1: Generic Interface".
[10] ETSI ES 202 336‑12: "Environmental Engineering (EE); Monitoring and control interface for infrastructure equipment (power, cooling and building environment systems used in telecommunication networks); Part 12: ICT equipment power, energy and environmental parameters monitoring information model".
[11] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements".
[12] 3GPP TS 28.554: "Management and orchestration; 5G end to end Key Performance Indicators (KPI)".
[13] 3GPP TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[14] Void
[15] 3GPP TS 22.261: "Service requirements for the 5G system".
[16] 3GPP TS 22.115: "Service aspects; Charging and billing"
[17] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2"
[18] 3GPP TS 32.299: " Telecommunication management; Charging management; Diameter charging applications".
[19] NGMN: "NGMN Energy Efficiency White Paper, Phase 2", Dec 2022.
[20] GSMA: "5G energy efficiencies: green is the new black, Nov 2020".
[21] Renewable Energy Certificates (RECs): https://www.epa.gov/green-power-markets/renewable-energy-certificates-recs
[22] ETSI EN 303 472: "Environmental Engineering (EE); Energy Efficiency measurement methodology and metrics for RAN equipment".
[23] 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".
[24] Methodological standard for the environmental assessment for Internet Service Provision (ISP), February 2023, https://librairie.ademe.fr/cadic/7695/pcr_internet_services_provision__english_version.pdf. Accessed April 29th, 2023
[25] 3GPP TR 28.829: "Study on network and service operations for energy utilities"
[26] 3GPP TR 28.913: "Study on new aspects of EE for 5G networks phase 2" |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 3 Definitions of terms, symbols and abbreviations | |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 3.1 Terms | For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
energy state: state of a cell, a network element and/or a network function with respect to energy, e.g. (not) energy saving states, which are defined in TS 28.310 [6].
energy charging rate: a means of determining the energy consumption consequence (use of energy credit) associated with charging events.
energy credit: a quantity of credit associated with the subscriber that can be used for credit control by the 5G system.
maximum energy consumption: a policy establishing an upper bound on the quantity of energy consumption by the 5G system in a specific period of time or space, e.g. energy consumption inside a given service area.
maximum energy credit limit: a policy establishing an upper bound on the aggregate quantity of energy consumption by the 5G system to provide services to a specific subscriber, e.g. in kilowatt hours.
NOTE 1: The term maximum energy credit limit is distinct from 'maximum energy consumption' because the credit limit is a total amount of energy consumed, where maximum energy consumption is a limit to the consumption in a given interval of time.
carbon emissions: kilograms of equivalent carbon dioxide emitted (kg of CO2 equivalent)
carbon intensity: quantity of CO2 equivalent emission per unit of final energy consumption for an operational period of use [23]
communication service pooling: refers to an operator serving subscribers from other operators traditionally providing communication service over the same geographical area, but which temporarily stop providing their service over their own network infrastructure for energy saving, e.g. via cell switch-off.
NOTE 2: Communication service pooling can be achieved, e.g. via NG-RAN sharing techniques or national roaming agreements wherever applicable, and apply to coverage and/or capacity layers.
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 3: This definition was taken from [22]. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
AS Application Server
DV Data Volume
EC Energy Consumption
EE Energy Efficiency |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 4 Overview | Climate change and global energy shortage are issues that requires international cooperation and coordinated solutions at all levels, many regions and countries have published related policies and requirements to control carbon release and promote energy efficiency. These policies have made energy efficiency a strategic priority for many telecom operators around the world. Energy efficiency has been considered in many standard groups and specifications.
The existing studies concentrate more on how to satisfy user experience and try to achieve energy efficiency at the same time and achieve energy efficiency within the network, so the requirements, use cases and solutions are basically within the network itself. Verticals and customers have no approach for energy efficiency related information from the network.
Introducing energy efficiency as a service will allow users to have the choice to select proper energy efficiency criteria as well as other network performance parameters when they need them, which may include:
- Define and support energy efficiency criteria as part of communication service to user and application services.
- Provide information exposure on systematic energy consumption or level of energy efficiency to vertical customers.
Such as in satellite and terrestrial convenience scenario, for some regions where both satellite and terrestrial coverage exist, energy saving could be taken as a dimension while providing the communication service, users or operators could have the choice to find out a best way in satisfying both user experience and energy efficiency. From another perspective, the network could also react to different energy consumption modes of applications or adjust network resources.
Both aspects above need more interactions between applications and networks on energy consumption status. It is worth considering how to deliver services with energy efficiency as service criteria, associated with verticals’ preferences, and how to support the policy of handling energy as part of a subscription. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5 Use cases | |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.1 Use case on energy consumption as a performance criteria for best effort communication | |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.1.1 Description | Currently energy consumption and efficiency can be monitored and considered through O&M and network operation, but not as a service performance criterion, as for example bit rate, latency or availability. Guidance from SA to all working groups states:
"The EE-specific efforts so far undertaken e.g., in SA5 have aimed mostly at improving the energy efficiency by impacting the operations of the system. As we now are starting to specify the 5G-Advanced features, TSG SA kindly requests the recipient WGs and TSGs to consider EE even more as a guiding principle when developing new solutions and evolving the 3GPP systems specification, in addition to the other established principles of 3GPP system design.
TSG SA clarifies that in addition to EE, other system level criteria shall continue to be met (i.e. the energy efficiency aspects of a solution defined in 3GPP is not to be interpreted to take priority or to be alternative to security, privacy, complexity etc. and to meeting the requirements and performance targets of the specific feature(s) the solution addresses)."
There is an important type of traffic where energy efficiency policy, for example a maximum amount of energy to be utilized could be applied without conflict with this guidance. Best effort traffic is a type of traffic that is provided as a service to customers everything else being equal. Of course, security, privacy and complexity principles will not be sacrificed, but there is no conflict between a service policy that constrains performance (e.g. latency, throughput, even availability) on the basis of energy consumption and a best effort service, since there are no guarantees in the case of best effort traffic. We can say that best effort traffic is not associated with QoS policy service performance level criteria.
Today the 5G system works to support services efficiently, though does not take into account energy consumption at the service level. The use case explores a particular opportunity to identify this information and use it to make more efficient use of all network resources without sacrificing service quality. In particular, information gathered through O&M, and in the future possibly from the network (see 5.1.5 which identifies a gap and opportunity), can be leveraged to make it possible to employ energy consumption information as part of service delivery.
In the following use case, the possibility of using energy consumption as a new service criterion for this less constrained type of mobile telecommunication service is explored.
A large-scale logistics company L has deployed a large number of communicating components. These are integrated into vehicles, palettes, facilities, etc. Essentially, IoT terminals enable remote tracking and monitoring functions. The information gathered is relevant, but not constrained with respect to latency. In fact, eventual delivery (e.g. after hours or even a full day) of communication is entirely acceptable for L. The MNO M offers a 'green service' which limits the rate of energy consumed for communication over a particular time interval (e.g. per day) and this service is appropriate for L, whose overall corporate goals are also served by 'green service,' as they strive to operate with energy efficiency. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.1.2 Pre-conditions | L deploys many UEs with associated 'green service' subscriptions from M. These subscriptions policies include the following criteria:
- Best Effort Service (service that is not associated with QoS policy service performance level criteria)
- Energy Constraints applied to service delivery |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.1.3 Service flows | 1. The fleet of trucks belonging to L leave the logistic center located in the middle of the uninhabited region hundreds of kilometers northeast of the major city Erehwon. There are many devices located in this fleet. The trucks and their contents comprise a physically dense group of UEs, all communicating periodically with the network. This 'massive IoT' group leaves the coverage of the logistics center. The network coverage over the road through the uninhabited region is very sparse.
2. As the trucks proceed into extreme low coverage, the energy consumed to communicate with the IoT devices increases. This energy consumption increase is monitored by the 5G network and can be aggregated, e.g. at the slice level.
3. The 'green service' policy for the service provided to L includes a maximum energy consumption rate. At a certain point the IoT communication of the fleet exceeds this maximum energy consumption rate.
4. The policy indicates that latency can be traded off with energy consumption for service to L; the communication service is delay tolerant in this condition. As the energy consumption rate has exceeded the maximum, the latency is increased to enforce this policy. In effect, L's fleet receives very limited service, with high latency, even for a limited period of time, no service at all.
NOTE: This use case does not describe how latency is increased, but does assume that this increase will result in a reduction of energy consumption. It is possible to reduce energy consumption by offering less service.
The use case description does not define how operator M offers the 'green service'. One possibility is that the maximum energy consumption policy applies to all services for the subscription of a device deployed by L with operator M. This simple policy may not be appropriate if the UEs deployed by L use different kinds of services at different times. In this case, the policy would apply to specific services (service flows, etc.) A requirement at the service flow level is not pursued in this use case.
A further option is that specific network slices apply a 'green service' policy to all services communicating by means of that slice.
The use case does not describe how energy consumption is determined. There is related work in SA5 and RAN3 to determine energy consumption. If energy consumption cannot be determined at the granularity, e.g. of a specific service or network slice or even the aggregate energy consumption of a subscriber, it is still possible to identify the total energy consumption of different elements in the 5G network. It is therefore possible, at least in principle, to divide the total energy by the number of served sessions, subscribers, etc. 'Average consumption' of a node or cell or network slice, etc. is a course unit of measurement, and does not reflect the true energy consumption at the finer granularity, though it still can be a useful metric.
Though an averaging approach could be useful to count the total amount of energy used to attribute to each subscriber, this approach is not enough to measure the rate of energy consumption as described in this use case. For this, there would have to be finer granularity energy reporting than 'per node' or 'per cell.' Though this is not yet supported in the 5G network. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.1.4 Post-conditions | The IoT devices in the fleet belonging to L are able to communicate with varying latency, depending on the energy consumption required to serve the devices. When the UEs are in poor coverage, they communicate seldom, when under good coverage, they can communicate more frequently.
The total energy consumption of M's network has reduced while still providing adequate service to customer L.
It is important to emphasize that there has been no trade-off between 'energy efficiency' and 'service quality.' Customer L received what was necessary while using less energy precisely because the energy consumption was taken into account in the service delivery. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.1.5 Existing feature partly or fully covering use case functionality | The 5G network can monitor energy consumption. The existing energy consumption monitoring is done at an O&M level, per network node, per cell and per network slice. The number of UEs per network node, cell and network slice are also known. Please see Annex A for an overview of existing energy efficiency standardization, which includes the determining energy consumption for use in calculating energy efficiency.
The 5G network can enforce performance criteria, as described in TS 22.261, 6.7 [15]. Most of the enforcement requirements refer to prioritization, but policies that result in other enforcement are possible too, e.g. gating, charging, credit control, restrictions with respect to maximum allowed resources, etc.
Gap: there is currently no means for the 5G network to determine the per subscriber or per network slice service flow energy consumption. This information is not included in network data analytic services. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.1.6 Potential new requirements needed to support the use case | [PR.5.1.6-1] Subject to operator’s policy, the 5G network shall support subscription policies that define a maximum energy consumption rate for services without QoS criteria (also termed "best effort" services.)
NOTE 1: The granularity of the subscription policies can either apply to the subscriber (all services), or to particular services. This requirement's applicability is limited to UEs that only support services without QoS criteria.
[PR.5.1.6-2] Subject to operator’s policy, the 5G network shall support enforcement of subscription policies that define a maximum energy consumption rate for services without associated QoS criteria (also termed "best effort" services.)
[PR.5.1.6-3] The 5G network shall support a means to define maximum energy consumption rate with specific granularities:
a) subscriber granularity (considering all services of the 5G network for the subscriber);
b) network slice granularity.
NOTE 2: The energy consumption of the UE is out of scope of this requirement.
[PR.5.1.6-4] Subject to operator's policy, the 5G network shall support energy consumption monitoring at per network slice and per subscriber granularity.
NOTE 3: Energy consumption monitoring as described in the preceding requirement is done by means of averaging or applying a statistical model. The requirement does not imply that some form of 'real time' monitoring is required. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.2 Use case on supporting different energy-related SLAs in industrial campus | |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.2.1 Description | Industrial campuses are very typical scenarios of edge computing and local traffic offload. Dedicated network facilities are usually deployed near the campus for lower latency and local data protection. This brings a problem that these network facilities are used only for the campus, so while the manufacturing load is light or during vacation, these network facilities will be in very light load or even no load. Under this scenario, the energy consumption of these network facilities will be unnecessary. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.2.2 Pre-conditions | Factory F, a smart manufacturing factory locates in a remote area outside the city. Factory F requires low latency in AGV transporting services and local data processing using computing vision to support image comparison for fault detection in circuit boards. Factory F has an agreement with Operator T on the communication service with certain SLA. As the manufacturing activity is not consistent, Operator T provides a replaceable SLA which can be used during off-peak time. This replaceable SLA can reduce energy consumption by changing the energy state of network functions used locally (e.g. to “energy saving” state), and the action can be activated either by pre-configured policy or by notification from Factory F. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.2.3 Service flows | 1. Operator T provides a dedicate set of UPF and MEC platform for factory F. Factory F is an environmental conscious enterprise that cares about energy saving (and efficiency) along its whole industrial chain.
2. When the manufacturing load of Factory F reaches a certain threshold (lower or higher), which is evaluated by Factory F, a notification will be sent to Operator T.
3. Operator T will change the energy state of the dedicated network functions accordingly to energy saving, based on the pre-agreed policy with Factory F.
4. After one year of this kind of usage, the charging information of the communication service will consider the actual usage time of the different energy states. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.2.4 Post-conditions | Manufacturing of Factory F will be not affected, while energy consumption of the communication service could be saved by dynamically changing energy states of network functions, and the expenses of the communication service will be lower to encourage this kind of environmental-friendly action. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.2.5 Existing features partly or fully covering the use case functionality | In TS 28.310 [6], there are existing requirements to switch off edge UPFs during off-peak hours:
REQ-SOUPF-FUN-1: The management service producer responsible for energy saving should have the capability allowing its authorized consumer to collect the traffic load performance measurements of its edge UPFs.
REQ-SOUPF-FUN-2: The management service producer responsible for energy saving should have the capability allowing its authorized consumer to administratively prohibit selected edge UPFs from performing services for its users, either with immediate effect or only when no more users are using these UPFs. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.2.6 Potential new requirements needed to support the use case | [PR.5.2.6-1] The 5G system shall support different energy states of network elements and network functions.
[PR.5.2.6-2] The 5G system shall support dynamic changes of energy states of network elements and network functions, based on pre-configured policy with authorised 3rd party.
NOTE 1: Pre-configured policy may include: the time of changing energy states, which energy state map to which level of load, etc.
[PR.5.2.6-3] The 5G system shall support different charging mechanisms based on the different energy states of network elements and network functions. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.3 Use case on energy consumption exposure considering possible deployment scenarios | |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.3.1 Description | When considering Energy as a service or network performance criteria, it is necessary to consider different 5G network deployment scenarios, e.g. for RAN network with dual connectivity, RAN network with CU-DU deployment, RAN sharing, etc. That means whatever the deployment scenario, the energy consumption of the 5G network which relates to the industry customer is expected to be acquired and exposed to the authorized third parties. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.3.2 Pre-conditions | The network operator A deploys 5G network “N” to serve industry customers C and D.
In the 5G network “N”, some of the gNBs can support dual-connectivity. In order to achieve more flexible deployment and reduce the cost, operator A also deploys a large number of DUs in some hotspot area, each DU is for covering a certain area. For customer C, dual-connectivity is utilized, while for customer D, multiple DUs have been configured.
Industry customers C and D have also subscribed the “Green Energy Moni” value-added service from network operator A, thus they can access energy consumption information corresponding to their respective network functions from a web application provided by Operator A. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.3.3 Service flows | 1. The 5G network “N” of operator A acquires the energy consumption information of related 5G network functions serving customers C and D.
2. Customer C asks the “Green Energy Moni” of Operator A to provide the network energy consumption information associated with the 5G network functions serving it via dual-connectivity deployment.
3. Operator A provides the network energy consumption information to customer C.
4. Customer D asks the “Green Energy Moni” of Operator A to provide the network energy consumption information associated with the 5G network functions serving it via DU deployment.
5. Operator A provides the network energy consumption information to customer D. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.3.4 Post-conditions | Customers C and D can get the energy consumption information of the network functions serving them, independently from NG-RAN deployment scenarios. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.3.5 Existing features partly or fully covering the use case functionality | None. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.3.6 Potential new requirements needed to support the use case | [PR.5.3.6-1] Subject to operator’s policy and consent by the vertical customer, the 5G system shall be able to acquire energy consumption information of the network functions serving the customer, independently from NG-RAN deployment scenarios, and expose this information to the customer and authorized third parties. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.4 Use case on energy efficiency information exposure under NPN RAN sharing | |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.4.1 Description | In the practice of 5G NPN deployment, in order to save time and cost, RAN sharing (i.e. NG-RAN is shared by any combination of PLMNs and NPNs) is a common deployment scenario for vertical industries. The customers will concern about the energy efficiency of their communication service especially in RAN sharing cases. Thus, it is reasonable for 5G system to acquire and expose the energy efficiency information of the customer including when it is served by RAN sharing network. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.4.2 Pre-conditions | The 5G network operator A deploys local NPN “N1” network in factories for customer C which is sharing resource of operator A’s PLMN “R”.
Customer C has subscribed the “Green energy Moni” value-added service for its NPN “N1” from network operator A, thus it can access energy efficiency information corresponding to the “N1” network from a web application provided by Operator A. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.4.3 Service flows | 1. The 5G network of operator A acquires the energy efficiency information of the NPN ”N1” and PLMN “R”.
2. Customer C asks the “Green Energy Moni” of Operator A to provide the energy efficiency information of its network “N1”.
3. The operator A acquires and provides energy efficiency information of the network “N1” to customer C. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.4.4 Post-conditions | Customer C can get the energy efficiency information of its network “N1”. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.4.5 Existing features partly or fully covering the use case functionality | TS 28.554 [12] already defines EE, EC and DV-related KPIs and use cases to acquire and calculate energy-efficiency at various levels within the 5G system. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.4.6 Potential new requirements needed to support the use case | [PR.5.4.6-1] Subject to operator’s policy and consent by the customer of NPN, the 5G system shall be able to acquire energy efficiency information of the NPN, including the shared network function(s) which is (are) serving the NPN, and expose this information to the NPN customer and authorized third parties. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.5 Use case on service energy monitoring by an application server | |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.5.1 Description | In this scenario, a service provider monitors events resulting from energy consumption policy triggers in the 5G system. These triggers correspond to monitoring policy in the 5G system as well as energy enforcement policies.
Figure 5.5-1: Monitoring of Energy Events by the 5G network for an AS
In Figure 5.5.1, the application server AS obtains information corresponding to the energy consequences of a UE 'A' served by the 5G network.
This use case will provide a description of a scenario in which the service provider (who operates an application server) cares about energy consumption in the 5G system as a result of the service to UE A. This could be for 3 reasons:
- the service provider needs to show they are saving energy;
- the service has an associated energy cost, and the service provider wants to reduce it. This is analogous to the use of industrial or consumer electronics when energy rates are lower, and also as an incentive to operate more efficiently;
- the service provider recognizes that there are policies that limit energy use (such as aggregate energy use of a network slice) and controls the overall use of the service to operate within those constraints.
The use case introduces five new concepts related to new energy events and energy event monitoring:
a) the ability for the network operator to create a 'maximum energy credit' policy, after which services are gated;
b) the ability for the network operator to inform an AS of the 'maximum energy credit expired' event;
c) the ability for the 5G system to calculate 'energy credit' use;
d) the ability to monitor and provide to the AS the use of 'energy credits' (or other energy 'quantum');
e) the support a new policy that establishes the energy consequence for charging control - either charging for use of energy or establishing an 'energy credit limit' for enforcement by the 5G system. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.5.2 Pre-conditions | The UE "A" has a subscription that enables it to make use of 'best effort communication subject to energy constraints' policy for communication. This class of communication was introduced in clause 5.1.
The application service provider of "AS" is capable monitoring service aspects of the 3GPP system, e.g. through network exposure of information as described in TS 22.261 [15] for QoS monitoring or TS 22.115 [16] related to credit limit policy and control. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.5.3 Service flows | 1. The application service provider of AS has an energy policy related to the service for the subscription related to UE "A". As a result, AS requests to monitor 'Energy Use', which is a kind of usage monitoring supported by the 5G system. The monitoring policy has an established 'threshold' for the 5G system to notify the AS.
In addition, the AS requests to monitor 'Out of Energy Credit' events.
2. The 5G system provides service to UE A according to a 'best effort communication subject to energy constraints' policy, where the policy charges for energy use and also imposes an 'energy credit' limit, after which the UE A subscription is 'gated' (receives no further services from the 5G system until more 'energy credit is available).
3. UE A proceeds to use services of the 5G system, especially data communication. As it does so, the charging system is triggered and generates records. The 3GPP charging system uses a means to identify how much credit is used and whether a credit limit is exceeded. The 3GPP charging system in this use case also uses a means of calculating energy credits on the basis of charging events. That is, there is a 'rating policy' used to multiply a 'charging event' by an 'energy consumption' unit.
NOTE 1: The actual amount of energy corresponding to an 'energy unit' used in energy credit control is out of scope of this use case. A mobile network operator can develop a model by which they analyze the total energy needed to provide services and assign fractions of these to each event triggered in the charging system.
4. When the total 'energy units' exceed the reporting threshold according to the energy monitoring policy, the 5G system exposes this energy consumption information to AS.
NOTE 2: Monitoring of energy consumption could be done by other means than 'energy units' corresponding to the same units as the credit limit. This could be useful for the third party. However, only by exposing units that result in charging or gating enforcement by the network operator can the third party determine the consequences of their use of services and potentially change their use of those services, e.g. to communicate sparingly, to communicate more efficiently (e.g. at times in less energy use is reported per 'byte', etc. of communication, as calculated by the third party based on their own measurements and the monitoring reports of the 5G system.)
5. When the total 'energy units' exceed the energy credit limit, this results in the 5G system exposing this event to the AS. The AS could take some action to restore energy credit, but this is out of scope of the use case. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.5.4 Post-conditions | The UE A's energy consumption can be monitored by AS. The AS can alter their activity (e.g. communicate less intensely or less frequently) to remain within their expectation - be it to keep the charging per energy consumption to their expectation, or to avoid exhausting A's energy credit limit.
The MNO is able to create and enforce policies that attach consequences to energy consumption. This can lead to energy efficient behaviour on the part of service providers which is both in their interest and the interest of the MNO. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.5.5 Existing feature partly or fully covering use case functionality | The 5G system provides support for credit limits [16, clause 8.2] and for performance monitoring [15]. There are a number of other events that are exposed by the 5G system to third parties by the Policy and charging control framework by the 5G System [17]. These events and their triggers, which are not detailed in stage 1, allow for usage monitoring to be exposed to a third party in specific circumstances, e.g. sponsored connectivity. The scenario in this use case is similar to sponsored connectivity, as the application service provider is a directly concerned party that seeks to operate successfully in an efficient manner, as there are charging and even gating consequences as the UE communicates with AS.
Note that the existing usage monitoring and reporting for sponsored connectivity is not sufficient to support this use case because these do not in any way take into account the energy consequence of the service. Only traffic volume and time-based monitoring are supported today. Other chargeable events (and therefore significant from an energy perspective) are not captured by usage monitoring as supported in the 5G system. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.5.6 Potential new requirements needed to support the use case | [PR.5.5.6-1] Subject to operator’s policy, the 5G system shall support subscription policies that define a maximum energy credit limit for services.
[PR.5.5.6-2] Subject to operator’s policy, the 5G system shall support subscription policies that support a means to associate energy consumption units with charging records.
[PR.5.5.6-3] Subject to operator’s policy, the 5G system shall support a means to expose energy consumption to authorized third parties for services, such that the energy consumption information clearly identifies the 'approaching' enforcement of an energy credit limit.
[PR.5.5.6-4] Subject to operator’s policy, the 5G system shall support a mechanism to perform energy consumption credit limit control for services.
NOTE 1: The result of the credit control is not specified by this requirement. Examples include gating, increased charging rates, etc.
NOTE 2: Credit control [18] compares against a credit control limit. In this use case, charging events are assigned a corresponding energy consumption and this is compared against a policy of energy credit limit. The use case assumes it is possible that there is a new policy to limit energy consumption allowed. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.6 Use case on supporting service-level energy efficiency analysis for verticals | |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.6.1 Description | Company A is located in an industrial campus. There are three internal applications used by employees for daily work which are based on two network slices. App A is for internal communication. App B is for production control. App C is for office automation. A and C are running on one slice, while B running on a separate slice. The data of these three applications are all dealt with a locally deployed UPF in this campus. The operator provides the additional service of exposing energy consumption of locally deployed UPF. Company A find that energy consumption of the UPF become higher recently, but cannot find out the cause, hope that 5G system can help to analysis which users or application are abnormal.
5G system analysis the data volume on this UPF and energy consumption of each app periodically.
Figure 5.6-1: Supporting service-level energy efficiency analysis for verticals |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.6.2 Pre-conditions | 5G system support energy consumption analysis based on data volume and energy consumption of network functions, which can be done by UPF. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.6.3 Service flows | 1.Company A finds abnormal energy consumption on the local network entity and request 5G system to report data usage of app A, B and C in past 3 days.
2.5G system analyses data volume and energy consumption of each app in every 2 hours.
3.5G system report shows that app B has a large data usage during 3am-5am every day.
4.Company A finds that app B has an abnormal setting which lead to system update repeatedly and large energy consumption. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.6.4 Post-conditions | Company A located the abnormal app and machine. They reset the setting and fix the problem. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.6.5 Existing features partly or fully covering the use case functionality | Requirements for DV measurement control and Power, Energy and Environmental (PEE) measurement has been defined to support for 5G NF measurement control.
In SA5 TS 28.554 [12], clause 6.7.3.3 Network Slice Energy Consumption are introduced.
In SA2, quota for PDU sessions per network slice and user numbers are already defined. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.6.6 Potential new requirements needed to support the use case | [PR.5.6.6-1] The 5G system shall support energy consumption measurement of network functions and exposure to authorised 3rd party.
NOTE: The granularity of energy consumption measurement could vary according to different situations, for example, when several services share a same network slice, etc. Energy consumption monitoring as described in the preceding requirement is done by means of averaging or applying a statistical model. The requirement does not imply that some form of 'real time' monitoring is required. |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.7 Use case on energy consumption information exposure considering QoS | |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.7.1 Description | Quality of service (QoS) refer to the network measurement of the overall performance about a communication service for the user. This network performance statistic can be e.g, packet loss, data rate, transmission delay, jitter, etc. When provide the energy as a service or a network performance criteria, e.g. in clause 5.2, the industrial park customer can be provided different energy-related SLAs under different energy states of network by operator, it is reasonable that not only the energy consumption information of the network or network functions but also the associated network performance statistic information are collected and exposed together to the customers or authorized third parties which will help customers to achieve more visible network service under different energy states of network functions.
The network performance statistic information can be pre-configured by the customer, authorized third parties or by Operator to be associated with the network functions energy consumption information. The network performance statistic information can be packet loss, data rate, transmission delay, jitter, etc. which can be collected and calculated the average value based on 5QI refer TS28.554. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.