hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.11.3 Solution evaluation
| The solution addresses KI#1 the study aspect on "Whether enhancements to existing application enablement layer services or a new application enabler service is required to support energy savings operations in the application enablement layer." New functional architecture is proposed with SEAL Energy Saving Enablement (... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.12.1 Solution Description
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.12.1.0 General
| The following clauses specify the procedure and information flow of SEAL service on energy data collection for support energy saving.
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.12.1.1 Procedure
| Pre-condition:
• The VAL UEs, VAL server, VAL service, and consumer in the procedure belong to the same party.
Figure 6.12.1.1-1: Energy data collection and processing
1. A consumer (e.g., VAL server, SEAL server/client) sends energy data collection and processing subscription request to ESE server. The re... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.12.1.2 Information Flows
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.12.1.2.1 General
| The following information flows are specified for energy data collection and processing.
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.12.1.2.2 Energy data collection and processing subscription request
| Table 6.12.1.2.2-1 shows the request sent by a SEAL service consumer to a ESE server for energy data collection and processing procedure.
Table 6.12.1.2.2-1: Energy data collection and processing subscription request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.12.1.2.3 Energy data collection and processing subscription response
| Table 6.12.1.2.3-1 shows the response sent by the ESE server to the consumer for energy data collection and processing procedure.
Table 6.12.1.2.3-1: Energy data collection and processing subscription response
Information element
Status
Description
Result
M
The result of the request (positive or negative acknowl... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.12.1.2.4 Energy data collection and processing notify
| Table 6.12.1.2.4-1 shows the notification sent by the ESE server to the consumer for energy data collection and processing procedure.
Table 6.12.1.2.4-1: Energy data collection and processing notify
Information element
Status
Description
Success status
O
(NOTE)
Indicates that data collection was successful.
>D... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.12.2 Architecture impacts
| A new ESE server service is introduced with the corresponding service API:
- ESE Energy Data Collection and Processing API (subscribe / notify model; API provider: ESE server; known consumer: VAL server, SEAL server/client; corresponding to steps 1, 3, and 6 of clause 6.12.1.1).
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.12.3 Solution evaluation
| The solution addresses KI #1 on enhancements to functional architecture by proposing a new ESE service on energy data collection and processing. The ESE server collects and processes energy data and provides processed energy data to the consumer based on request, to support energy saving for the consumer application op... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.13.1 Solution Description
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.13.1.0 General
| According to key issue #2, there is a need for a service that can monitor and expose the energy information/status (e.g. energy source type change, anomaly energy consumption, etc.). This solution provides energy saving monitoring service, that can be used by the consumer (e.g., VAL server, SEAL client (Energy Saving),... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.13.1.1 Energy monitoring procedure
| Figure 6.13.1.1-1 illustrates the procedure for a consumer (e.g., VAL server, ESE client, other SEAL server) to monitor energy information/status.
Figure 6.13.1.1-1: Energy monitoring subscription and notification
1. The consumer (e.g., VAL server, ESE client, other SEAL server) sends an Energy Monitoring Subscript... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 5 The ESE server receives notifications about energy information from the subscribed data source(s), for example, energy consumption per UE from EIF via NEF, energy consumption at the VAL UE (via ESE client).
| 6. The ESE server determines whether to send a notification to the consumer based on the reporting requirements in step 1. The reporting can be periodic, or event triggered (e.g. the energy consumption at the VAL UE exceeds the threshold provided in step 1, which triggers server to send notification to the consumer).
... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.13.1.2 Energy monitoring Information elements
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.13.1.2.1 Energy monitoring subscription request
| Table 6.13.1.2.1-1 shows request sent by the consumer (e.g. VAL server, ESE client, other SEAL server) to the ESE server for the energy monitoring subscription.
Table 6.13.1.2.1-1: Energy monitoring subscription request
Information element
Status
Description
Consumer ID
M
The identifier of the consumer (e.g. VAL... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.13.1.2.2 Energy monitoring subscription response
| Table 6.13.1.2.2-1 shows response sent by the SEAL server (Energy Saving) to the consumer (e.g. VAL server, SEAL client (Energy Saving), other SEAL server) for the energy monitoring subscription procedure.
Table 6.13.1.2.2-1: Energy monitoring subscription response
Information element
Status
Description
Subscripti... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.13.1.2.3 Energy monitoring notification
| Table 6.13.1.2.3-1 shows the notification sent by the SEAL server (Energy Saving) to the consumer (e.g. VAL server, SEAL client (Energy Saving), other SEAL server) for the energy monitoring procedure.
Table 6.13.1.2.3-1: Energy monitoring notification
Information element
Status
Description
Subscription ID
M
Repr... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.13.2 Architecture impacts
| The impact to architecture is as introduced in clause 6.13.1, on monitoring energy information.
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.13.3 Solution evaluation
| This solution addresses KI #2 by providing a method to monitor the energy information/status upon receiving energy monitoring subscriptions from the consumer and send notifying to the consumer.
6.14 Solution #14: Updating QoS according to renewable energy to improve user experience in EDGEAPP
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.14.1 Solution Description
| This paper proposes the solution to solve the problem listed in KI #3 and proposes to improve the user experience if UE or QoS flow consumes renewable energy.
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.14.1.1 General
| According to the section 5.51.2.2.1 of 3GPP TS 23.501 [3], the Energy Information Function (EIF) collects the UE related Energy Consumption information including Node-level energy consumption information, Node-level data volume from OAM and data volume of the required granularities (i.e. S-NSSAI, PDU Session and/or Ser... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.14.1.2 Solution description
| In order to save the energy consumption and reduce the carbon emission, the operators may consider using renewable energy or green energy to replace traditional energy. For example, some servers of operators can be powered by electricity converted from renewable energy to reduce the carbon emission. Considering the ren... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.14.1.3 Procedure of QoS update related to renewable energy consumption
| The procedure listed here are based on the procedure defined in section 8.6.6.2.3 of 3GPP TS 23.558 [8].
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 8.6.6.2.3 Update a session
| Figure 8.6.6.2.3-1 illustrates the session with QoS update request operation between the EAS and the EES. It is used to request a modification of the QoS of the data session between AC and EAS
Figure 8.6.6.2.3-1: Session with QoS API: update operation
0. The EAS act as AF to subscribe and receive the energy consump... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.14.2 Architecture impacts
| In this solution, it doesn’t change the overall architecture of enabling edge applications defined in section 6.2 of 3GPP TS 23.558 [8]. But the following enhancements are added:
- The EAS can act as AF to subscribe the energy consumption information of certain UE or certain QoS from 5GC. And if renewable energy is co... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.14.3 Solution evaluation
| This solution addresses Key Issue #3 – open issue #1 and #2 on how to enhance EDGE application enabler to support energy saving and energy efficiency in QoS updating.
This solution enables edge application enablement enhance to support for QoS updating according to energy related information triggered by EAS. The solu... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.15.1 Solution Description
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.15.1.0 General
| According to the key issue #4, there is a need for AIMLE enhancements for AIML services such as AI/ML task transfer. This solution enables the AIMLE Server to select the target AI/ML member(s) for the AI/ML task transfer, based on energy consumption related information of the target AI/ML member(s) and the energy savin... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.15.1.1 Energy saving in AI/ML task transfer procedure
| Pre-condition:
• The source and target AI/ML members belong to the same operator
Figure 6.15.1.1-1: Support energy saving in AI/ML task transfer
Figure 6.15.1.1-1 illustrates the procedure for support energy saving in AI/ML task transfer. The detailed corresponding procedure is detailed as follows:
1. The sou... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.15.1.2 Enhance the information flow for AI/ML task transfer procedure
| The information flow for AI/ML task transfer as specified in clause 8.6.3 of 3GPP TS 23.482 [10] is enhanced as follows (new text in bold italics):
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 8.6.3.2 AI/ML task transfer assist request
| Table 8.6.3.2-1 describes information elements for the AI/ML task transfer assist request from the source AI/ML member to the AIMLE Server.
Table 8.6.3.2-1: AI/ML task transfer assist request
Information element
Status
Description
Requestor identity
M
The identifier of the source AI/ML member (e.g. identifier of... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 8.6.3.3 AI/ML task transfer assist response
| Table 8.6.3.3-1 describes information elements for the AI/ML task transfer assist response from the AIMLE Server to the source AI/ML member.
Table 8.6.3.3-1: AI/ML task transfer assist response
Information element
Status
Description
Transfer Mode
O
Indication the transfer mode (e.g. direct transfer).
Target AI/... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.15.2 Architecture impacts
| The architecture impact is introduced in the clauses 6.15.1.1 and 6.15.1.2.
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.15.3 Solution evaluation
| This solution addresses KI #4 by providing a method to support energy saving in AI/ML task transfer including the selection of a target AI/ML member(s) for the AI/ML task transfer, based on the energy consumption related information of the target AI/ML member(s) collected by the ESE server.
6.16 Solution #16: Support ... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.16.1 Solution Description
| This solution addresses Key Issue #4.
Stage 1 has introduced the notion of ‘energy credit’ as per 3GPP TR 22.882 and 3GPP TS 22.261 [2], which is a quantity of credit associated with the subscriber (end user, ASP) that can be used for credit control by the 5G system. Energy credit in the 3GPP context refers to a polic... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.16.2 Architecture impacts
| This solution requires that a new SEAL server, aka ESE server, has the role of detecting and triggering an energy related event associated with the AIML split operation pipeline.
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.16.3 Solution evaluation
| This solution addresses Key Issue #4, and in particular the use of energy criteria for update an AIML split operation pipeline. This solution enhances the split AI/ML operation update procedure which has been specified in 3GPP TS 23.482 [10] clause 8.14.2.6. Such procedure doesn’t have any energy criterion for determin... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.17.1 Solution Description
| This solution addresses Key Issue #4.
Stage 1 has introduced the notion of ‘energy credit’ as per 3GPP TR 22.882 and 3GPP TS 22.261 [2], which is a quantity of credit associated with the subscriber (end user, ASP) that can be used for credit control by the 5G system. Energy credit in the 3GPP context refers to a polic... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.17.2 Architecture impacts
| This solution requires that a new SEAL server, aka ESE server, has the role of detecting and triggering an energy related event associated with the FL member.
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.17.3 Solution evaluation
| This solution addresses Key Issue #4, and in particular the use of energy criteria for monitoring the FL member availability. This solution enhances the FL related event notification AIMLE capability as provided in clause 8.5.3 of 3GPP TS 23.482 [10].
The solution is feasible, well aligned with the AIMLE functional ar... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.18.1 Solution Description
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.18.1.1 General
| This solution proposes to enhance the NSCE service on VAL server-triggered and network-based network slice adaptation for VAL application (in clause 9.11 of 3GPP TS 23.435 [13]). The enhancement enables NSCE to guide UEs to use different slices to improve energy efficiency and promote the use of renewable energy.
The ... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.18.1.2 Procedure
| The procedure on VAL server-triggered and network-based network slice adaptation for VAL application in clause 9.11.2 of 3GPP TS 23.435 [13] is enhanced as follows (new text in bold italics):
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 9.11.2 Procedures
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 9.11.2.1 Procedure for VAL server-triggered and network-based network slice adaptation for VAL application - request and response model
| Figure 9.11.2.1-1 illustrates the VAL server-triggered and network-based procedure where the NSCE server supports the network slice adaptation with the underlying 3GPP system for the VAL UEs of the VAL application.
Figure 9.11.2.1-1: Network slice adaptation for VAL application
1. The VAL server sends a network sli... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.18.1.3 Information flows
| The information flows on network slice adaptation request in clause 9.11.3 of 3GPP TS 23.435 [13] is enhanced as follows (new text in bold italics):
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 9.11.3.1 Network slice adaptation request
| Table 9.11.3.1-1 describes the information flow network slice adaptation request from the VAL server to the NSCE server.
Table 9.11.3.1-1: Network slice adaptation request
Information element
Status
Description
VAL service ID
M
The VAL service ID of the VAL application for which the network slice adaptation may ... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.18.2 Architecture impacts
| Architecture impact has been identified in clause 6.18.1.
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.18.3 Solution evaluation
| This solution addresses the open issue #2 in Key Issue #5, on whether and how to use energy consumption information to fulfill network slice selection, modification, adaptation, by proposing enhancements to Network Slice Adaptation Considering Energy Information for VAL Application. The enhancements enable the NSCE to ... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.19.1 Solution Description
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.19.1.1 General
| This solution proposes enhancing multiple slices coordinated resource optimization (clause 9.10 of 3GPP TS 23.435 [13]) to consider slice energy related information, enable slice modification between multiple network slices for energy saving and promotion of the use of renewable energy.
The high-level principles are a... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.19.1.2 Procedures
| The procedure and information flows on multiple slices coordinated resource optimization in clause 9.10 of 3GPP TS 23.435 [13] is enhanced as follows (new text in bold italics):
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 9.10.2 Procedure
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 9.10.2.1 Procedure on multiple slices coordinated resource optimization
| Figure 9.10.2.1-1 illustrates the procedure of multiple slices coordinated resource optimization service from VAL server to NSCE server.
Pre-conditions:
1. The network slice enabler layer is capable to interact with PLMN 5GC or OAM system to handle slices of PLMN and its PNI-NPNs.
2. PNI-NPNs are deployed as network... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 9.10.3 Information flows
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 9.10.3.1 General
| The following information flows are specified:
- Multiple slices coordinated resource optimization request and response.
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 9.10.3.2 Multiple slices coordinated resource optimization request
| Table 9.10.3.2-1 describes information elements for the multiple slices coordinated resource optimization request from the VAL server to the NSCE server.
Table 9.10.3.2-1: Multiple slices coordinated resource optimization request
Information element
Status
Description
Requestor Identifier
M
Unique identifier of... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 9.10.3.3 Multiple slices coordinated resource optimization response
| Table 9.10.3.3-1 describes the information elements for the multiple slices coordinated resource optimization response from the NSCE server to the VAL server.
Table 9.10.3.3-1: Multiple slices coordinated resource optimization response
Information element
Status
Description
Result
M
Indicates the success or fail... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.19.2 Architecture impacts
| Architecture impact has been identified in clause 6.19.1.
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.19.3 Solution evaluation
| This solution addresses the open issue #2 in Key Issue #5, on whether and how to use energy consumption information to fulfill network slice selection, modification, adaptation, by proposing enhancements to Multiple Slices Coordinated Optimization according to energy information. The enhanced NSCE service enables NSCE ... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.20.1 Solution Description
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.20.1.1 General
| Definition of energy saving level: each energy saving level indicate a distinguishing energy consumption performance. Some examples like:
- Economy level: an energy level when the service provider (e.g., SEAL Server, etc.) minimizes energy consumption prioritized over performance.
- Balanced level: an energy level wh... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.20.1.2 Enhance location reporting procedures
| The procedure for Location reporting as specified in clause 9.3.3.3 of 3GPP TS 23.434 [14] is enhanced as follows (new text in bold italics):
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 9.3.3.3 Location reporting
| Figure 9.3.3.3-1 illustrates the procedure for location reporting.
Figure 9.3.3.3-1: Location reporting procedure
1. The location management client sends a location information report to the location management server, containing location information identified by the location management server and available to the... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 9.3.5 Client-triggered or VAL server-triggered location reporting procedure
| Figure 9.3.5-1 illustrates the high level procedure of client-triggered or VAL server-triggered location reporting.
Figure 9.3.5-1: Client-triggered location reporting procedure
1. Location management client 2 (authorized VAL user or VAL UE) or VAL server sends a location reporting trigger to the location managemen... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.20.1.3 Enhancements to information flows
| The information flow for Location reporting trigger as specified in clause 9.3.2.4 of 3GPP TS 23.434 [14] is enhanced as follows (new text in bold italics):
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 9.3.2.4 Location reporting trigger
| Table 9.3.2.4-1 describes the information flow from the location management client or VAL server to the location management server for triggering a location reporting procedure.
Table 9.3.2.4-1: Location reporting trigger
Information element
Status
Description
Requestor Identity
M
(see NOTE 1)
Identity of the r... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 9.3.2.2 Location information report
| Table 9.3.2.2-1 describes the information flow from the location management client to the location management server for the location information reporting or from the location management server to the requesting location management client or VAL server to report location information.
Table 9.3.2.2-1: Location informa... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.20.2 Architecture impacts
| The architecture impacts are as identified in clause 6.20.1.
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.20.3 Solution evaluation
| This solution addresses the open issue in Key Issue #3, on enhancing existing LM service to support energy savings. The location reporting procedure, Client-triggered location reporting procedure, and their corresponding information flows are enhanced to support trigger switch location reporting between LMC and network... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.21.1 Solution Description
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.21.1.1 General
| The existing location reporting optimization for different devices sharing the same location is not based on the energy saving criteria. Consider the example scenario where a user with different devices sharing the same location needs to report the location. In this case, a device can be selected as the location report... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.21.1.2 Procedure for optimized location reporting based on energy saving
| Pre-conditions:
1. The LMS has the information that all UEs share the same location.
2. The UEs can be aware of each other's location.
Figure 6.21.1.2-1: Optimized location reporting based on energy saving
1. The Location Management Server (LMS) sends track energy information subscription request to ESE server fo... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.21.1.3 Information Flows
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.21.1.3.1 Inform Location reporter VAL UE
| Table 6.21.1.3.1-1: Inform Location Reporter VAL UE
Information element
Status
Description
Requestor Identity
M
Indicates the requestor’s identity (i.e., identifier of LMS).
VAL service ID
O
Identity of the VAL service for which the location service is registered.
Identity of VAL UE(s)
M
Indicates the ident... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.21.1.3.2 Terminate Location reporter VAL UE
| Table 6.21.1.3.2-1: Terminate Location reporter VAL UE
Information element
Status
Description
Requestor Identity
M
Indicates the requestor’s identity (i.e., identifier of LMS).
VAL service ID
O
Identity of the VAL service for which the location service is registered.
Stop location report
M
Indicates to stop... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.21.2 Architecture impacts
| This architecture impact is introduced in the clauses 6.21.1.2 and 6.21.1.3.
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.21.3 Solution evaluation
| This solution addresses KI#6 by providing a method for optimized location reporting by a single device for a group of devices sharing the same location. A location reporting device is selected by LMS based on collected energy status of the devices. This solution can be used to support energy saving for group of UE loca... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 7 Overall Evaluation
| 7.1 Overall Evaluation of Key issue #1: Enhance Application Enablement Layer Architecture and Services to Support Energy Saving
The open issues studied in the Key Issue #1 are as follows:
- Whether enhancements to existing application enablement layer services or a new application enabler service is required to suppo... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 8 Conclusions
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 8.1 General conclusions
| The present technical report described the energy enabler capabilities for supporting vertical use cases. This technical report fulfils the objectives of the study on application enabler architecture for enabling energy saving services. The report includes the following:
1. Definition of terms, symbols and abbreviatio... |
7c4ff880bd6ea05413a74ff675872fec | 23.700-56 | 1 Scope
| The present document investigates further enhancements to the capabilities of IMS data channel (DC), specifically in the areas of ADC establishment in alerting phase, IMS capability exposure and dynamic configuration of MDC2 endpoints.
|
7c4ff880bd6ea05413a74ff675872fec | 23.700-56 | 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.
-... |
7c4ff880bd6ea05413a74ff675872fec | 23.700-56 | 3 Definitions of terms and abbreviations
| |
7c4ff880bd6ea05413a74ff675872fec | 23.700-56 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
|
7c4ff880bd6ea05413a74ff675872fec | 23.700-56 | 3.2 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
A2P Application to Person
ADC Application Data Channel
API Application P... |
7c4ff880bd6ea05413a74ff675872fec | 23.700-56 | 4 Architectural Assumptions and Requirements
| |
7c4ff880bd6ea05413a74ff675872fec | 23.700-56 | 4.1 Architectural Assumptions
| The following Architectural Assumptions are applicable to this Study:
- The IMS and IMS DC architecture defined in TS 23.228 [2] is used as the basis for any enhancements.
- An AS may be trusted or untrusted.
- The functionality of existing standardized APIs (e.g. OMA APIs) exposing MMTEL services may be used where ... |
7c4ff880bd6ea05413a74ff675872fec | 23.700-56 | 5 Key Issues
| |
7c4ff880bd6ea05413a74ff675872fec | 23.700-56 | 5.1 Key Issue #1: ADC establishment in alerting phase for early media
| This key issue will investigate how to support IMS application data channel establishment in alerting phase to provide early media for a normal IMS DC session.
This Key Issue will study:
- Whether and how the capability of supporting ADC establishment in alerting phase is exchanged between UE and IMS network.
- How ... |
7c4ff880bd6ea05413a74ff675872fec | 23.700-56 | 5.2 Key Issue #2: Enhancements to capability exposure framework for eMMTel services
| This Key Issue will investigate how to enhance IMS capability exposure framework to expose IMS capability for eMMTel services (voice/video) and related events besides Data Channel, supporting IMS session establishment, modification and release to enable eMMTel services that may require enhancing audio/video services wi... |
7c4ff880bd6ea05413a74ff675872fec | 23.700-56 | 5.3 Key Issue #3: Supporting dynamic configuration of MDC2 endpoints
| This Key Issue will investigate whether and how to define interfaces between DCSF and NEF/AF to complete existing P2A/P2A2P Data Channel procedures by specifying DC3/DC4 interfaces to enable dynamic configuration of MDC2 endpoints.
This Key Issue will study:
- the services and information elements that are exposed vi... |
7c4ff880bd6ea05413a74ff675872fec | 23.700-56 | 6 Solutions
| |
7c4ff880bd6ea05413a74ff675872fec | 23.700-56 | 6.0 Mapping of Solutions to Key Issues
| Table 6.0-1: Mapping of Solutions to Key Issues
Key Issues
Solutions
KI#1
KI#2
KI#3
#1
X
#2
X
#3
X
#4
X
#5
X
#6
X
#7
X
#8
X
#9
X
10
X
11
X
12
X
13
X
14
X
15
X
16
X
17
X
|
7c4ff880bd6ea05413a74ff675872fec | 23.700-56 | 6.1 Solution #1: ADC establishment in alerting phase initiated by the UE
| |
7c4ff880bd6ea05413a74ff675872fec | 23.700-56 | 6.1.0 High-level solution Principles
| This solution addresses Key Issue #1: DC establishment in alerting phase for early media.
The solution reuses Rel-19 TS 23.228 [2] with the addition that
- Based on the UE request (via a specific root URL) , the DSCF sends to the UE(s) an application list related with the alerting phase- The calling party receive BD... |
7c4ff880bd6ea05413a74ff675872fec | 23.700-56 | 6.1.1 Description
| This solution provides a procedure on how to establish a P2A ADC in alerting phase.
Editor's note: Current version of the solution supports P2A ADC establishment in alerting phase. it is FFS whether it can support other forms of ADC, i.e. P2A2P and P2P.
|
7c4ff880bd6ea05413a74ff675872fec | 23.700-56 | 6.1.2 Procedure
| The pre-condition of ADC establishment in alerting phase is the capability negotiation during the IMS registration phase on whether the UE supports the DC in alerting phase.
Based on the IMS DC capability negotiation defined in clause AC.7.0 of TS 23.228 [2], when the UE supporting DC in alerting phase and the UE is a... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.