hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 7.2.6 Potential New Requirements needed to support the use case | [P.R. 7.2-001] 5GS shall be able to support an aggregated QoS for a group UEs served by a relay UE.
[P.R. 7.2-002] 5GS shall be able to provision an aggregated QoS to a relay UE for a group-based service.
[P.E. 7.2-003] Based on 3rd party request and user consent, the 5G system shall be able to expose information (e.g.... |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 7.3 5GS assisted distributed joint inference for 3D object detection | |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 7.3.1 Description | Distributed joint inference is to leverage multiple nodes (e.g. UEs) to provide inference results so that an aggregation of those inference results can lead to a better performance.
When a 3rd party vehicle wants to obtain relevant information of a certain vehicle 1 (e.g. position, width, length, height, profile, orien... |
3b008e4f4eb4734158412e812ecd3c39 | 22.876 | 7.3.2 Pre-conditions | As shown in figure-7.3.2-1, when a vehicle accident occurs somewhere and the road is congested. Alice's auto-driving vehicle wants to know the complete situation of the accident (i.e. the exact location and shape of the accident vehicle including the length, width and height of the vehicle), so as to use the inference ... |
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 vehi... |
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 canno... |
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... |
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
... |
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 appli... |
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.... |
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 ... |
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)
Re... |
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... |
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 d... |
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: ◦ Proximi... |
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)
P... |
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.
- Fo... |
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 ro... |
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... |
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 ... |
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 a... |
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 VPL... |
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 registrat... |
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 specifi... |
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. ... |
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, th... |
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 segmen... |
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-establ... |
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.... |
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 regi... |
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 c... |
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... |
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.
- Fo... |
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... |
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 Ene... |
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 strategi... |
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 m... |
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... |
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 net... |
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... |
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 t... |
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 ... |
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 communicat... |
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 ... |
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... |
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 inc... |
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 net... |
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 certai... |
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-connectiv... |
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. T... |
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 “... |
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... |
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 appl... |
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 netwo... |
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... |
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 creat... |
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 stag... |
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 recor... |
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 separat... |
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... |
17e8174f94d72a34a3d8a81dbfebc7a5 | 22.882 | 5.6.4 Post-conditions | Company A located the abnormal app and machine. They reset the setting and fix the problem. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.