hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.8.3.0.1 Introduction
| This solution proposes two CAPIF enhancements:
1. Enhancements on Service API Publish to enable the APF can indicate the API Provider domain preferences about the service API information that can be disseminated using the Open Discovery API (see clause 6.8.3.0.2 and 6.8.3.1)
2. Enhancements on the Configuration data ... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.8.3.0.2 Service API Publish with API Provider domain preferences for Open Discovery
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 8.3.3 Procedure
| Figure 8.3.3-1 illustrates the procedure for publishing the service APIs. The service API publish mechanism is supported by the CAPIF core function.
Pre-conditions:
1. Authorization details of the APF are available with the CAPIF core function.
2. API invokers may have subscribed with the CAPIF core function to obt... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.8.3.0.3 CCF configuration with CAPIF Administrator preferences for Open Discovery
| Annex E (normative):
Configuration data for CAPIF
The configuration data is stored in the CAPIF core function and provided by the CAPIF administrator.
The configuration data for CAPIF is specified in table E-1.
Table E-1: Configuration data for CAPIF
Reference
Parameter description
Subclause 4.2.2
List of pub... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.8.3.0.4 Updated procedure for Open Discovery considering API Provider Domain and CAPIF administrator preferences
| NOTE: The security aspects of the Open Discovery procedure for the dissemination of service API information depend on the SA3 study on Open Discovery security and will be incorporated in the normative phase once they are concluded in SA3.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 8.38 Open Discover service APIs
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 8.38.1 General
| The following procedure in this subclause corresponds to supporting open discover service APIs. Such open discovery operation allows requestor to discover service API information (e.g., API name, API category) about the available set of APIs offered by CCF before onboarding.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 8.38.2 Information flows
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 8.38.2.1 Open Service API discover request
| Table 8.38.2.1-1 describes the information flow open service API discover request from the requestor to the CAPIF core function.
Table 8.38.2.1-1: Open Service API discover request
Information element
Status
Description
Query information
O
(see NOTE)
Criteria for discovering matching service APIs. It may contai... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 8.38.2.2 Open Service API discover response
| Table 8.38.2.2-1 describes the information flow open service API discover response from the CAPIF core function to the requestor.
Table 8.38.2.2-1: Open Service API discover response
Information element
Status
Description
Result
M
Indicates the success or failure of the open discovery of the service API informat... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 8.38.3 Procedure
| Figure 8.38.3-1 illustrates the procedure for open discover service APIs.
The open service API discovery mechanism is supported by the CAPIF core function.
Pre-conditions:
1. The requestor is not a recognized user of the CAPIF.
2. The CAPIF core function is aware of the Service API information that can be dissemina... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.8.3.1 Information flows
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 8.3.2.1 Service API publish request
| Table 8.3.2.1-1 describes the information flow service API publish request from the API publishing function to the CAPIF core function.
Table 8.3.2.1-1: Service API publish request
Information element
Status
Description
API publisher information
M
The information of the API publisher may include identity, authen... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.8.4 Solution evaluation
| Solution#7 is a feasible solution for KI#7, and proposes that the CCF is aware of the policies for service API dissemination based on:
1. the update of the Publish API, to indicate per Service API, whether the Service API can be diseminated using the Open Discovery.
2- the update of the CAPIF Configuration table, to... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.9.1 General
| This solution relates to KI #2. In this solution, the CCF is acting as data source to ADAES as already defined in clause 8.6 of 3GPP TS 23.436 [7], and provides more data (like API Usage Info (Total Requests, Response Times), Error Tracking logs (Error Types)).
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.9.2 Architecture Impacts
| This solution does not impact CAPIF architecture.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.9.3 Solution description
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.9.3.1 Enhancements to Procedure for supporting service API analytics
| The clause 8.6 of 3GPP TS 23.436 [7] is already defined to get Service API analytics. The solution proposes to reuse clause 8.6 of 3GPP TS 23.436 [7] to provide API analytics for API administration, with following enhancements:
1) The CAPIF administration and/of API provider domain administration are the consumer for ... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 8.6.3.6 Service API analytics notification
| Table 8.6.3.6-1 describes information elements for the service API analytics notification to the subscriber/consumer from the ADAE server.
Table 8.6.3.6-1: Service API analytics notification
Information element
Status
Description
Service API information
M
The service API name or type for which analytics apply.
... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.9.3.2 Enhancements to Auditing service API invocation
| In order to enable ADAES to get service API logs, the clause 8.22.3 of 3GPP TS 23.222 [2] is enhanced as follows.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 8.22.3 Procedure
| Figure 8.22.3-1 illustrates the procedure for auditing service API invocation.
Pre-conditions:
1. Service API invocation logs are available at the CAPIF core function.
2. Authorization details of the AMF are available with the CAPIF core function.
Figure 8.22.3-1: Procedure for auditing service API invocation
1... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.9.3.3 Information flows
| The solution is not defining any new information flows, and the enhancements to existing information flows is captured in clause 6.x.3.1 and clause 6.x.3.2.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.9.4 Solution evaluation
| The solution is related to KI#2 and proposes to reuse the existing procedure defined in clause 8.6 from 3GPP TS 23.436 [7]. The solution further enhances the existing procedure defined in clause 8.22 of 3GPP TS 23.222 [2]. The solution enhances the information flow to add API usage information and Error tracking inform... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.10.1 General
| This solution relates to KI #2.
KI#2 identifies the use case of controlling the usage of an API provider domain’s service API information such as Service API invocation logs, for analytics services to application entities outside of API provider domain. The open issue is captured on how the API provider permits the us... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.10.2 Architecture Impacts
| This solution enhances the existing Publish Service API procedure. There are no new functional elements or reference points introduced in this solution. There are no architecture impacts.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.10.3 Solution description
| This solution enhances the existing Publish Service API procedure with permission information. The enhancements proposed to Publish service APIs procedure in clause 8.3 of 3GPP TS 23.222 [2] are shown in below (indicated in bold).
Figure 8.3.3-1 illustrates the procedure for publishing the service APIs. The service A... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.10.3.1 Information flows
| This solution proposes the update to Service API publish request in clause 8.3.2.1 of 3GPP TS 23.222 [2], with permission information. The updates are shown below (in bold).
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.10.4 Solution evaluation
| This solution addresses the KI #2 and addresses the issue on how the API provider permits the usage of service API information. This solution proposes to reuse the existing procedure defined in clause 8.3 of 3GPP TS 23.222 [2]. The solution enhances the CAPIF service API publish service with permission information from... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.11.1 General
| This solution relates to KI #3.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.11.2 Architecture Impacts
| This solution does not impacts CAPIF architecture.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.11.3 Solution description
| The KI#3 has following open issue: “This key issue will study approaches to managing entities (i.e., API Invoker or API Provider) without a valid CCF issued and signed certificate, specifically how such entities can be deleted from the CCF including associated resources to the entities like Security_Context associated... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.11.3.1 Information flows
| NOTE: The impact on the information flows of procedures in 3GPP TS 23.222 [2] depends on the outcome of KI#4 of 3GPP TR 33.700-23 [6] in SA3.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.11.4 Solution evaluation
| The solution is related to KI#3. Certificate management is within the scope of SA3, and any further action in SA6 depends on the progress of the KI#4 of 3GPP TR 33.700-23 [6].
NOTE: SA6 impacts due to the SA3 outcome of the study on security aspects of credentials unavailability will be determined during normative p... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.12 Solution #11: Heartbeat of the AEF
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.12.1 General
| This solution is addressing key issue #4. It introduces the heartbeat mechanism between the AEF and the CAPIF core network.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.12.2 Architecture Impacts
| There are no architecture impacts.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.12.3 Solution description
| The AEF maintains the heartbeat with the CAPIF core function via a implementation specific heartbeat timer.
Currently, the API invoker is involved in the service API discovery and the service API invocation procedures, which may need the AEF status.
The CAPIF core function may determine the AEF status (i.e., connect... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.12.4 Solution evaluation
| This solution is proposed to use the heatbeat mechanism as an example and implementation specific option to make the CCF aware of the AEF status (connectivity with the AEF).
6.13 Solution #12: Determination of Service API and AEF unavailability
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.13.1 General
| This solution relates to KI #4.
KI#4 describes one existing gap in current deployments, about how to get awareness of API status (AEF/Service API) when the connection between the CAPIF core function and the AMF and/or APF, entities in charge of indicating AEF/Service API status, is disrupted due to e.g., network issu... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.13.2 Architecture Impacts
| There are no architecture impacts.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.13.3 Solution description
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.13.3.0 General
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.13.3.0.1 Introduction
| This clause describes the optional procedure that may be supported by the CCF to detect unavailability of the AEF, APF and AMF.
In the current level of the specification of 3GPP TS 23.222 [2]:
- The AMF manages the registration of the AEF, APF and AMF functions in the CCF using the CAPIF_API_Provider_Management_API a... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.13.3.0.2 Detection of AEF/Service API availability
| This clause describes the optional procedure that may be supported by the CCF to detect AEF/Service API unavailability.
Figure 6.13.3.0.2-1 describes the detection of AEF/Service API availability.
Preconditions:
- The AMF supports the detection of AEF/Service API availability by implementation specific means.
- The... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.3.5 API publishing function
| The API publishing function enables the API provider to publish the service APIs information in order to enable the discovery of service APIs by the API invoker. The API publishing function consists of the following capability:
- Publishing the service API information of the API provider to the CAPIF core function;
... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.13.3.1 Information flows
| This solution does not impact the existing Information flows.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.13.4 Solution evaluation
| This section provides solution evaluation based on the open issues specified in the related key issue(s).
6.14 Solution #13: CCF support of Roaming Considerations for Service API invocation
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.14.1 General
| This solution relates to KI #5.
KI#5 describes one existing gap in current deployments, experienced in live deployments, about how to avoid in a controlled way that a service API call is progressed towards the VPLMN when e.g. no exposure related roaming agreements with the visiting network exists in the home network.... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.14.2 Architecture Impacts
| The CAPIF architecture is impacted by the definition of the N33 reference point, that enables the CCF to interact, when necessary, with the CSP to retrieve UE roaming information via CSP exposed service APIs.
Figure 6.14.2-1 shows the updated reference point based functional model for the CAPIF.
Figure 6.14.2-1: Fu... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.14.3 Solution description
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.14.3.0 General
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.14.3.0.1 Roaming Considerations during Service API invocation
| Figure 6.14.3.0.1-1 illustrates the procedure to determine and handle the roaming information during service API invocation, showing the interaction between the different CAPIF functions when Roaming policies for exposure need to be applied.
Pre-conditions:
1. The API Invoker is onboarded and has received an API Invo... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.14.3.0.2 Roaming Authorization changes
| Figure 6.14.3.0.2-1 illustrates the procedure where either the UE roaming information changes or the roaming policies change while the service delivered by the service API is running, showing the interaction between the different CAPIF functions when roaming policies for exposure need to be applied.
Pre-conditions:
1... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.14.3.0.3 Apply Roaming Unsubscribe
| Figure 6.14.3.0.3-1 illustrates the procedure where the service API invocation is terminated, showing the interaction between the different CAPIF functions when Roaming Control policies need to be applied.
Pre-conditions:
1. The API Invoker is getting service from the authorized service API as described in Figure 6.1... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.14.3.1 Information flows
| Editor's Note: It is FFS the analysis of a solution based on access control policies.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.14.3.1.1 Apply Roaming Policy subscription request
| Table 6.14.3.1.1-1 describes the information flows for Apply Roaming Policy subscription request from the AEF to the CAPIF core function.
Table 6.14.3.1.1-1: Apply Roaming Policy subscription request
Information element
Status
Description
API invoker identity information
M
The information that determines the ide... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.14.3.1.2 Apply Roaming Policy subscription response
| Table 6.14.3.1.2-1 describes the information flows for Apply Roaming Policy subscription response from the CAPIF Core Function to the AEF.
Table 6.14.3.1.2-1: Apply Roaming Policy subscription response
Information element
Status
Description
Result
M
Indicates the success or failure of service API invocation.
Su... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.14.3.1.3 Apply Roaming Policy Notify request
| Table 6.14.3.1.3-1 describes the information flows for Apply Roaming Policy notify request from the CAPIF Core Function to the AEF.
Table 6.14.3.1.3-1: Apply Roaming Policy Notify request
Information element
Status
Description
Subscription identifier
M
The unique identifier of the apply roaming policy subscripti... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.14.3.1.4 Apply Roaming Policy unsubscription request
| Table 6.14.3.1.4-1 describes the information flows for Apply Roaming Policy unsubscription request from the AEF to the CAPIF core function.
Table 6.14.3.1.4-1: Apply Roaming Policy unsubscription request
Information element
Status
Description
Subscription identifier
M
The unique identifier of the apply roaming p... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.14.3.2 Updates in Configuration Data for CAPIF
| The configuration data for CAPIF is specified in 3GPP TS 23.222 [2] table E-1. The updates in Configuration Data for CAPIF to support UE roaming information to authorize API invoker request are highlighted in Italic and Bold format.
Table E-1: Configuration data for CAPIF
Reference
Parameter description
Subclause ... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.14.4 Solution evaluation
| Solution#13 is a feasible solution for KI#5 and is based on the definition of the Apply Exposure Policy API, exposed by the CCF and consumed by the AEF.
The AEF invokes the Apply Exposure Policy API when it needs to validate whether the service API invocation is according to configured policies. The CCF stores the ex... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.15.1 General
| This solution relates to KI #5 and KI #6.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.15.2 Architecture Impacts
| This solution requires CCF to interact with NEF via N33 interface which supports the subscription or retrieval of UE location information. The architecture figure update is shown in clause 6.14.2.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.15.3 Solution description
| Clause 8.11 of 3GPP TS 23.222 [2] has been modified as follows:
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 8.11.3 Procedure
| Figure 8.11.3-1 illustrates the procedure for obtaining authorization to access the service API.
Pre-condition:
1. The API invoker is onboarded and has received an API invoker identity.
Figure 8.11.3-1: Procedure for the API invoker obtaining authorization for service API access
1. The API invoker sends an obtain... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.15.3.1 Information flows
| The solution does not need any new information flows.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.15.4 Solution evaluation
| The solution is related to KI #5. The solution proposes for CCF to obtain location of API invoker (on the UE) and determine whether the API invoker (on the UE) is within the API service area or not, and issues the token only if the API invoker (on the UE) is wihtin the service area. For KI#5 and KI#6, if the API invok... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 7 Deployment scenarios
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 7.1 General
| No new deployment scenarios were studied in this report.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 8 Business Relationships
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 8.1 General
| No new business relationships were studied in this report.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 9 Overall evaluation
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 9.1 Evaluation of architecture enhancements
| 9.1.x Evaluation of architecture option #x
This section evaluates architecture option #x.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 9.2 Evaluation of key issues
| 9.2.1 Evaluation of key issue #1
The key issue #1 is about enhancements to API provider function to handle API invoker status change. Specifically, the key issue studied following open issue:
1) whether and how to handle the scenario where API invoker whose status has changed in the API provider domain, e.g. the API ... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 10 Conclusions
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 10.1 Architectural conclusions
| This section provides conclusion and suggestion for normative work for the architecture options studied in this TR.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 10.2 Key issues conclusions
|
10.2.1 Conclusions of key issue #1
Solution #1 and Solution #3 can be considered for normative work. For solution#2, The specific changes (if required) to the event definition will be discussed during normative phase.
10.2.2 Conclusions of key issue #2
Following solution considerations will be considered for the n... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 1 Scope
| The present document is a technical report which identifies the application enabling layer architecture, capabilities, and services to support energy saving services at the application layer.
The aspects of the study continue the investigation of application enablement impacts, cover the application enablement layer a... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 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.
-... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 3 Definitions of terms, symbols and abbreviations
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 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].
example: text used to clarify abstract rules by applying them literally.
Renewable Energ... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 3.3 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].
<ABBREVIATION> <Expansion>
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 4 Architectural Requirements and Assumptions
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 4.1 Architectural requirements
| [AR-4.1-a] The SEAL enabler layer (Energy Saving) shall support the provisioning of energy saving related assistance information to the application layer consumer.
[AR-4.1-b] The SEAL enabler layer (Energy Saving) shall support energy saving service event report from the SEAL enabler layer to the application layer.
[... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 4.2 Architectural assumptions
| [AA-4.2-a] The architecture for the energy saving services in the application enablement layer shall support consumption of the energy consumption information collection and exposure services as specified in clause 4.29 of 3GPP TS 23.502 [7].
[AA-4.2-b] The architecture for the energy saving services in the applicatio... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 5 Key Issues
| 5.1 Key issue #1: Enhance Application Enablement Layer Architecture and Services to Support Energy Saving
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 5.1.1 Description
| The new SID "study on Application Enablement to support Energy Saving Phase 2" lists the objective of the study that include:
- Potential enhancements to the application enablement layer (e.g. SEALDD, AIMLE, LM, ADAE) to support energy saving for the network resources used by the applications.
Potential enhancements ... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 5.1.2 Open issues
| To enhance application enablement layer architecture and services to support energy saving, the key issue will study:
- 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.
NOTE... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 5.2.1 Description
| Use cases and service requirements for energy saving have been specified in 3GPP TS 22.261 [2], including use cases and requirements requiring application enablement layer support.
In 3GPP TS 23.501 [3], 5GS enhancements for energy saving include framework for data volume information collection, network energy consump... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 5.2.2 Open issues
| This key issue will study the following aspects:
1. Whether and how the application enablement layer can obtain and use data related to energy consumption for energy consumption monitoring.
2. Whether and how to support the monitoring of energy consumption measurements associated with the usage of the application ena... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 5.4.1 Description
| SA1 identified use cases and requirements for energy efficiency and energy saving in Release-19 and Release-20 (in 3GPP TS 22.261 [2]). Energy efficiency and energy saving is a critical feature in 5G. Such use cases and requirements have application layer impacts. AI/ML requires more energy consumption at the device si... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 5.4.2 Open issues
| The key issue aims to study:
1. How to collect and utilize energy consumption data (and which data) from the UE side to support an application layer ML task (or ML model lifecycle / workflow operation).
2. How to enhance functionality and architecture of AIMLE to support energy saving.
3. Whether and how to use ener... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 5.6.1 Description
| The new SID "study on Application Enablement to support Energy Saving Phase 2" lists the objective of the study include:
- Potential enhancements to the application enablement layer (e.g. SEALDD, AIMLE, LM, ADAE) to support energy saving for the network resources used by applications.
SA6 defines services which may b... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 5.6.2 Open issues
| To enhance existing application enablement layer services to support energy saving, the key issue will study:
- Identify whether and how existing application enablement layer services (e.g. SEALDD, LM, ADAE) need be enhanced to support energy savings.
NOTE 1: The existing application enablement layer services conside... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6 Solutions
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.0 Mapping of solutions to key issues
| Table 6.0-1 Mapping of solutions to key issues
KI #1
KI #2
KI #3
KI #4
KI#5
KI#6
Sol #1
X
Sol #2
X
Sol #3
X
Sol #4
X
Sol #5
X
Sol #6
X
X
Sol #7
X
X
Sol #8
X
Sol #9
X
Sol #10
X
Sol #11
X
... |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.1.1 Solution Description
| |
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.1.1.0 General
| The following clauses specify the procedure and information flow on energy saving assistance provisioning.
|
6db04542c7aa154f5a7f619c9ea52b71 | 23.700-44 | 6.1.1.1 Procedure
|
Figure 6.1.1.1-1: Energy saving assistance
1. A consumer (e.g., VAL server, SEAL server/client) sends energy saving candidate entity request to ESE server. The request includes information as described in Table 6.1.1.2.2-1.
2. The ESE server authenticates and authorizes the request. If authorized, the ESE server... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.