hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 4.2.2 Open issues
| To support the enhancements to API administrator role, the following aspects need to be studied:
- What are the key types of API analytics that would be useful for an API provider administrator?
- How to provide API analytics for the CAPIF entities in the API provider domain?
- whether and what are the key types of... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 4.3.1 Description
| As described in clause 6.1 of 3GPP TS 33.122 [3], a prerequisite to onboarding an API invoker to CAPIF, an API invoker is required to obtain onboarding enrolment information from the API provider domain (see step 1 of the referenced clause). This information is necessary to enable the API invoker to authenticate with t... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 4.3.2 Open issues
| 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 to API Invokers and API resources pu... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 4.4.1 Description
| Currently, the CCF obtains the service API status (e.g., active, inactive) via the API management function as described in clause 6.3.6 and 6.4.8 of 3GPP TS 23.222, or via the APF publish and publish updated procedure.
However, in some scenarios the API Provider Domain is unable to provide the status of Service APIs a... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 4.4.2 Open issues
| - This key issue will study approaches to address scenarios in which the API Provider Domain is unable to provide the status of its AEFs with associated Service APIs and whether and how to enhance the architecture and related functions to handle the scenarios in which the connection between the CAPIF core function and ... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 4.5.1 Description
| One existing gap in current deployments, detected by field experiences, is how to avoid in a controlled way that a service API invocation is served when, e.g., the UE is roaming and no exposure related roaming agreements with the visiting network exists in the home network or indicates that the service should not be de... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 4.5.2 Open issues
| To support the control of service API invocations when the UE is roaming, the following aspects need to be studied:
- How to determine and ensure correct handling on Service API invocations, based on:
- whether roaming agreements and policies between CSPs needed for exposure; and
- whether application preferences re... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 4.6.1 Description
| One existing challenge is how to ensure that a service API is only invoked when the UE is within a designated service area aligned e.g. with the application preferences. Some services are only valid or cost-effective when the UE is physically inside a predefined service area or meets application-specific location prefe... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 4.6.2 Open issues
| To support the control of service API invocations when the UE is within or outside a designated service area, the following aspects need to be studied:
- How to determine and ensure correct handling on Service API invocations based on location of API invoker.
4.x Key issue #x: <title>
4.x.1 Description
This secti... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 5 Architecture enhancements
| 5.x Option #x: <title>
5.x.1 Description
This section provides details about the proposed architecture enhancements.
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6 Solutions
| |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.1 Mapping of solutions to key issues
| Table 6.1-1 Mapping of solutions to key issues
KI #1
KI #2
KI #3
KI #4
KI #5
KI #6
…
Sol #1
Sol #2
Sol #1
X
Sol #2
X
Sol #3
X
Sol #4
X
Sol #5
X
X
Sol #6
X
Sol #...
6.2 Solution #1:... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.2.1 General
| This solution relates to KI #1.
KI#1 identifies several use cases where the API invoker may have changed its status in the API provider domain after onboarding in the CAPIF provider domain. E.g., the API invoker decides to terminate the service agreement with the API provider, or the API Provider decides to terminate... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.2.2 Architecture Impacts
| There are no architecture impacts.
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.2.3 Solution description
| |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.2.3.0 General
| The following changes are proposed to 3GPP TS 23.222 [2]:
- Update of Annex E to include the CAPIF administrator provisioning of per API provider domain and API Invoker service API enrollement information.
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.2.3.0.1 Updates to TS 23.222 Annex E
| 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... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.2.3.1 Information flows
| Not applicable.
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.2.4 Solution evaluation
| This section provides solution evaluation based on the open issues specified in the related key issue(s).
6.3 Solution #2: API invoker enrolled Service API notification
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.3.1 General
| This solution relates to KI #1.
KI#1 identifies several use cases where the API invoker may have changed its status in the API provider domain after onboarding in the CAPIF provider domain. E.g., the API invoker decides to terminate the service agreement with the API provider, or the API Provider decides to terminate... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.3.2 Architecture Impacts
| This solution proposes an enhancement to the CAPIF_Events API, with the definition of a new subscription filter for the Service API of interest event, and a new subscription indication to include the Identifier of the API Invoker that successfully enrolls the reported service API in the event report of enrolled service... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.3.3 Solution description
| |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.3.3.0 General
| Figure 6.x.3.0-1 illustrates the procedure for the API provider domain subscribing with the CCF to notification of API Invoker API Invoker enrolled service API event, and the notification from the CCF to API provider domain about changes in the list of service APIs the API invoker successfully enrolled for.
Figure 6... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.3.3.1 Information flows
| |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 8.8.6 List of CAPIF events
| Table 8.8.6-1 provides a non-exhaustive list of CAPIF events.
Table 8.8.6-1: List of CAPIF events
Events
Events Description
Availability of service APIs
Availability events of service APIs (e.g. active, inactive)
Service API updated
Events related to change in service API information
Monitoring service API invo... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.3.4 Solution evaluation
| This section provides solution evaluation based on the open issues specified in the related key issue(s).
6.4 Solution #3: API provider domain remove enrolled APIs for API invoker
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.4.1 General
| The API invoker receives onboarding enrolment information from the API provider domain, which is used by the API invoker to onboard to CCF. If the API invoker has unsubscribed to the services provided by the API provider domain, then the it is required remove enrolled APIs for the APIs provided by API provider domain.
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.4.2 Architecture Impacts
| This solution does not impact existing CAPIF architecture.
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.4.3 Solution description
|
Figure 6.4.3.1 illustrates the procedure for offboarding API invoker from the CCF initiated by the AEF.
Pre-conditions:
1. The API invoker had received the onboarding enrolment information from the API provider domain and successfully onboarded to the CCF..
2. The API provider domain function (i.e. AMF) decides to... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.4.3.1 Information Flows
| The Offboard API invoker request and Offboard API invoker response messages are same as specified in clause 8.2.2.1 and clause 8.2.2.2 respectively. Table 6.x.3.1-1 describes the information flow offboard API invoker notify from the CAPIF core function to the API invoker.
Table 6.4.3.1-1: Offboard API invoker notify
... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.4.4 Solution evaluation
| This section provides solution evaluation based on the open issues specified in the related key issue(s).
6.5 Solution #4: Enhanced CAPIF events for AEF status
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.5.1 General
| This solution is related to key issue#4, specifically on introducing new CAPIF events to handle the scenarios in which the connection between the CAPIF core function and the API provider domain functions is disrupted due to network issues.
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.5.2 Architecture Impacts
| It is based on existing CAPIF architecture specified in 3GPP TS 23.222 [2].
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.5.3 Solution description
| In the existing CAPIF framework, introducing a heartbeat mechanism similar to the EAS Availability Reporting Period would enable CCF (CAPIF core function) to detect whether the connection between the CAPIF core function and an AEF is disrupted or not.
Editor's note: Whether there may be other mechanism than heartbeat... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.5.3.1 Information flows
| The following updates (in bold) to clause 8.8.6 of 3GPP TS 23.222 [2] are proposed for supporting new events for AEF status change if option 1 is adopted.
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.5.4 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
6.6 Solution #5: AEF status and error reporting
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.6.1 General
| This solution relates to KI #2 and KI #4. As per KI #2, CCF can collect data required for error tracking. This solution proposes API invoker to share the error reports to the CCF, Further, as per KI #4, CCF needs to know when AEF is unavailable. As stated in the key issue - the API Provider Domain is unable to provide ... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.6.2 Architecture Impacts
| This solution does not impact existing CAPIF architecture.
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.6.3 Solution description
| In this solution, if CCF requires the status report from the API invoker, the CCF provides the indication about the same in the discovery response (as spececified in clause 6.x6.3.1.
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.6.3.1 Enhancements to Service API discover response
| The service API discovery response is enhanced with new information element as described below:
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 8.7.2.2 Service API discover response
| Table 8.7.2.2-1 describes the information flow service API discover response from the CAPIF core function to the API invoker.
Table 8.7.2.2-1: Service API discover response
Information element
Status
Description
Result
M
Indicates the success or failure of the discovery of the service API information
Service AP... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.6.3.2 AEF Status reporting
| |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.6.3.2.1 General
| The procedure API invoker to report AEF status. The procedure may be invoked when service API invocation towards the AEF fails.
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.6.3.2.2 Information flows
| |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.6.3.2.2.1 AEF status reporting request
| Table 6.6.3.2.2.1-1 describes the information flow AEF status reporting request from the API invoker to the CAPIF core function.
Table 6.6.3.2.2.1-1: AEF status reporting request
Information element
Status
Description
API invoker identity information
M
Identity information of the API invoker
Service API inform... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.6.3.2.2.2 AEF status reporting response
| Table 6.6.3.2.2.2-1 describes the information flow AEF status reporting response from the CAPIF core function to the API invoker.
Table 6.6.3.2.2.2-1: AEF status reporting response
Information element
Status
Description
Result
M
Indicates the availability check is in-progress and result will be notified later, s... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.6.3.2.3 Procedure
| Figure 6.6.3.2.3-1 illustrates the procedure for AEF status reporting.
Pre-conditions:
1. The API invoker is onboarded, discovered the service APIs and received service authorization to invoke the service APIs.
Figure 6.6.3.2.3-1: AEF Status reporting
1. The API invoker (on the UE) sends the AEF status reporting ... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.6.4 Solution evaluation
| This section provides solution evaluation based on the open issues specified in the related key issue(s).
6.7 Solution #6: Support of API provider administrator in CAPIF
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.7.0 General description
| Here are some key types of API analytics that would be useful for an API provider administrator and their applications:
1. Usage Metrics
- Requests per Second (RPS): Monitor the number of API requests to identify peak usage times and ensure the system can handle the load.
- Total Requests: Track the overall numbe... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.7.1 Solution description
| Figure 6.7.1-1 illustrates the procedure for support of API provider administrator in CAPIF.
Pre-conditions:
1. Authorization details of the API analytics consumer e.g. AMF are available with the CAPIF core function.
Figure 6.7.1-1: Procedure for support of API provider administrator in CAPIF
1. For querying serv... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.7.2 Architecture Impacts
| Supporting API analytics functionality is required.
The API analytics function has the following capabilities:
1. Requests per Second (RPS), Total Requests, Response Times
2. Error Rates, Error Types
3. Most Used Endpoints, User Segmentation, User feedback
4. Unauthorized Access Attempts, Rate Limiting Violati... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.7.3 Corresponding APIs
| Editor's Note: APIs are FFS.
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 6.7.4 Solution evaluation
| Editor's Note: Solution evaluation is FFS.
6.x Solution #x: <Solution Title>
6.x.1 General
This solution relates to KI #N.
This section describes the high level principle of the solution.
6.x.2 Architecture Impacts
This section describes any architectural impacts based on the proposed solution.
6.x.3 Solution... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 7 Deployment scenarios
| |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 7.1 General
| This section describes the general information about deployment scenarios.
7.x Deployment model #x: <title>
This section describes the specific deployment scenario based on agreed solutions.
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 8 Business Relationships
| |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 8.1 General
| This section describes the general information about business relationships.
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 9 Overall evaluation
| |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 9.1 Evaluation of architecture enhancements
| 9.1.x Evaluation of architecture option #x
This section evaluates architecture option #x.
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 9.2 Evaluation of key issues
| 9.2.x Evaluation of key issue #x
This section evaluates all solutions related to key issue #x.
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 10 Conclusions
| |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 10.1 Architectural conclusions
| This section provides conclusion and suggestion for normative work for the architecture options studied in this TR.
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 10.2 Key issues conclusions
| 10.2.x Conclusions of key issue #x
This section provides conclusion and suggestion for normative work for the solutions related to key issue #x.
Annex A (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
SA6#68
S6-253193
Skeleton
0.0.... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 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... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 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.
-... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 3 Definitions of terms, symbols and abbreviations
| |
eb1343f2cdb3d270d65fac7ddb0d0638 | 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... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
eb1343f2cdb3d270d65fac7ddb0d0638 | 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>
|
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 4 Architectural Requirements and Assumptions
| |
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 4.1 Architectural requirements
| This clause will document any architectural requirements for FS_EnergySys_APP.
|
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 4.2 Architectural assumptions
| This clause will document any architectural assumptions for FS_EnergySys_APP.
|
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 5 Key Issues
| 5.1 Key issue #1: Enhance Application Enablement Layer Architecture and Services to Support Energy Saving
|
eb1343f2cdb3d270d65fac7ddb0d0638 | 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 enhanceme... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 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... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 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... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 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 applic... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 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... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 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... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 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 m... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 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... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6 Solutions
| |
eb1343f2cdb3d270d65fac7ddb0d0638 | 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
X
Sol #A3
X
Sol #4
Sol #x5
X
X
Sol #6
Sol #7
Sol #Y18
X
Sol #Y9
X
Sol #10
6.X21 Solution... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.1.1 Solution Description
| |
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.1.1.0 General
| The following clauses specify the procedure and information flow on energy saving assistance provisioning.
|
eb1343f2cdb3d270d65fac7ddb0d0638 | 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 assistance request to SEAL server. The request includes information as described in Table 6.1.1.2.2-1.2. The SEAL server authenticates and authorizes the request. If authorized, the SEAL server determ... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.1.1.2 Information Flows
| |
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.1.1.2.1 General
| The following information flows are specified for energy saving assistance.
|
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.1.1.2.2 Energy saving assistance request
| Table 6.1.1.2.2-1 shows the request sent by a SEAL service consumer to a SEAL server for energy saving assistance procedure.
Table 6.1.1.2.2-1: Energy saving assistance request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
VAL service ID
M
The identity of the... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.1.1.2.3 Energy saving assistance response
| Table 6.1.1.2.3-1 shows the response sent by the SEAL server to the consumer for energy saving assistance procedure.
Table 6.1.1.2.3-1: Energy saving assistance response
Information element
Status
Description
Result
M
The result of the request (positive or negative acknowledgement).
Subscription ID
O
Identifi... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.1.1.2.4 Energy saving assistance notify
| Table 6.1.1.2.4-1 shows the notification sent by the SEAL server to the consumer for energy saving assistance procedure.
Table 6.1.1.2.4-1: Energy saving assistance notify
Information element
Status
Description
Success status
O
(NOTE)
Indicates that energy saving assistance was successful.
>Assistance informat... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.1.2 Architecture impacts
| Editor’s Note: The architecture impacts of the solution is FFS.
|
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.1.3 Solution evaluation
| Editor’s Note: The evaluation of the solution is FFS.
6.2 Solution #2: Edge Application Server Discovery by Considering Renewable energy
|
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.2.1 Solution Description
| The proposed solution solves the problem listed in KI#1 and KI#3 and proposes to consider Renewable energy in edge computing.
In Edge Computing deployment, an application service may be served by multiple Edge Application Servers typically deployed in different sites. These multiple Edge Application Servers that host ... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.2.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 EES can subscribe to EAS whether renewable is consumed by EAS. If the EAS consumes the renewable energy, for example in the morning ti... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.2.3 Procedure
| |
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.2.3.1 Procedure of subscription Energy information from EAS
|
Figure 6.2.3.1-1: EAS energy information subscription
1. The EES sends an EAS energy information subscription request to the EAS. The EAS energy information subscription request includes the EES ID along with the security credentials, Event ID and time period to subscribe to information about energy information of E... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.2.3.2 Procedure of EAS discovery considering renewable energy information
| The procedure listed here are based on the procedure defined in section 8.5.2.2 of 3GPP TS 23.558 [8].
|
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 8.5.2.2 Request-response model
| Pre-conditions:
1. The EEC has received information (e.g. URI, IP address) related to the EES;
2. The EEC has received appropriate security credentials authorizing it to communicate with the EES as specified in clause 8.11; and
3. The EES is configured with ECSP's policy for EAS discovery.
NOTE 1: Details of ECSP's... |
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.2.4 Solution evaluation
| Editor’s Note: This part is for further update.
6.3 Solution #3: Enhance Edge Services for Support Energy Saving
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.