hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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 preferences. Today, API invokers must monitor UE presence and prevent service API invocations when the UE is outside the service area, which increases complexity and slows time-to-market for application developers.
The key objective of this Key Issue would be to develop an efficient way to determine the UE’s presence within this service area to prevent unnecesary or unsupported service API invocations.
|
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 section provides details about the key issue – by providing possible gaps.
4.x.2 Open issues
This section lists open issues to be studied.
|
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: CAPIF Administrator revocation of API Invoker enrollment information
|
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 the service agreement with the API Invoker because e.g., unpaid bills.
With the current level of specification, the termination of the service agreement between an API Invoker and an API Provider is communicated to the CAPIF Provider (e.g. CSP) via off-line mechanisms out of CAPIF procedures (e.g. BSS specific procedures), and it is not further specified how this termination is provisioned into the CAPIF Provider.
This solution proposes that the CAPIF Administrator can update the API Invoker profile according to the API Provider domain provided information to the CAPIF provider, e.g., to update the set of enrolled APIs and to remove the API Invoker authorization information from the CCF, as necessary.
|
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 published service API discovery restrictions
> Service API identification
> API invoker identity information
> Service API category
Subclause 4.3.2
List of service API authorization restrictions per API invoker
> API Invoker identity information
> Service API identification
> Per resource, operation authorization information.
(see NOTE 2)
> Network slice identification
Subclause 4.7.2
List of service API log storage durations
> Service API identification
> Service API log storage duration (in hours) (see NOTE 1)
Subclause 4.7.4
List of API invoker interactions log storage durations
> Service API identification
API invoker interactions log storage duration (in hours) (see NOTE 1)
Subclause 4.10
List of access control policy (for an API provider domain) per API invoker and optionally per network slice
> Volume limit on service API invocations (total number of invocations allowed)
> Time limit on service API invocations (The time range of the day during which the service API invocations are allowed)
> Rate limit on service API invocations (allowed service API invocations per second)
> Service API identification
> API invoker identity information
> Network Slice Info
Subclause 8.1
Onboarding information per API provider domain and API invoker.
> API Invoker Identification
> List of service APIs allowed for enrollment
(see NOTE 3)
Subclause 8.34.3
Group context information
> Group identifier
> List of UE IDs (group members)
> UE identifier of the Group Resource Owner
> Authorization information related to the list of supported applications
>> Application identifier
>> Purpose
>> Scope
NOTE 1: If no value is set for the duration, the duration is assumed to be unlimited.
NOTE 2: The API invoker request for access authorization to specific resources or operations of a Service API is specified in 3GPP TS 33.122 [12].
NOTE 3: When the CAPIF administrator removes a service API from the list of authorized service APIs for enrollment for an API invoker, the authorization to access service API corresponding to the API invoker and the removed service API is revoked from CAPIF.
Editor's note: The complete set of information the CAPIF administrator provides to disenroll a set of service APIs for an API invoker is FFS.
|
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 the service agreement with the API Invoker because e.g., unpaid bills.
When the API invoker is in the onboarded status, the enrollment information for the list of enrolled APIs may change. The CAPIF API events API, using the event for Service API of interest, is able to notify about the service APIs that are enrolled, but currently does not indicate the API invoker that enrolled the service API, which could be useful for the API Provider domain, in case of revocation of API Invoker’s enrolled service APIs by CAPIF Administrator, and in case of API Invoker is modifying the list of enrolled service APIs.
This solution proposes that the subscription to Service API of interest event is updated to indicate whether the subscription is for a specific API invoker or for any API invoker and whether the notification, in case of report of enrolled service APIs, needs to include the identity of the API Invoker that successfully enrolled the service API.
|
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 API.
|
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.3.3.0-1: Procedure for API invoker enrolled Service API notification
1. The API Provider domain subscribes with the CCF to notifications about API Invoker enrolled service APIs event (Service API of interest events). The API Provider domain may provide the API Invoker information to identify the API invokers to be notified of and may provide as notification filter the service API(s) the API Invoker may be including for enrollment within the onboarding operation.
2. The CCF determines the already onboarded API invokers.
3. The CCF returns the response to the API provider subscription request to API Invoker enrolled service APIs event (Service API of interest events). If the API Provider requested immediate notification, the CCF returns the information available for the currently onboarded API Invokers, including the list of enrolled service APIs per API Invoker.
4. API Invoker X requests onboarding in the CCF and includes a set of service APIs for enrollment.
5. The CCF returns a successful API Invoker response, including the successfully enrolled APIs.
6. The CCF notifies the API Provider domain about a new API invoker enrolled service APIs event (Service API of interest events), including the successfully enrolled Service APIs for the API Invoker.
7. The API Provider domain acknowledges the notification.
8. API Invoker X requests to update the set of enrolled service APIs (disenroll and/or enroll).
9. The CCF acknowledges the request and returns the successfully enrolled service APIs.
10. The CCF triggers a notification to the API Provider domain indicating the updated list of service APIs the API invoker successfully enrolled for.
11. The API Provider domain returns a notification request acknowledgement to the CCF.
12. API invoker X offboards.
13. CCF acknowledges the offboarding request.
14. CCF notifies the API provider domain to indicate that there is no service API enrolled for the API Invoker.
|
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 invocations
Events corresponding to service API invocations
API invoker status
Events related to API invoker status in CAPIF (onboarded, offboarded, onboarding criteria not met status along with the criteria information that is not met.)
API topology hiding status
Events related to API topology hiding status in CAPIF (created, revoked)
System related events
Alarm events providing fault information
Performance related events
Events related to system load conditions
CAPIF-1/1e interaction events
Events related to CAPIF-1/1e interactions for a service API (e.g. onboarded API invokers)
AEF status
Events related to AEF status (e.g. unreachable, reachable) in CAPIF
|
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 remove enrolled APIs for the API invoker based on certain condition (e.g. the API invoker has unsubscribed to the services provided by the API provider domain functions).
Figure 6.4.3.1: Procedure for removing enrolled APIs for API invoker
1. The AMF triggers the remove enrolled APIs for the API invoker.
2. The AMF sends remove enrolled APIs request for the API invoker to the CAPIF core function with the details of the API invoker. The request message may include the reason for the removing enrolled APIs.
3. Upon receiving the request, the CAPIF core function invalidates the API invoker authorization corresponding to the service APIs. The CCF may decide to offboard the API invoker if all enrolled APIs are removed from the API invoker profile.
4. If CCF has decided to offboard the API invoker, the CCF sends an offboard API invoker notify to the API invoker. The notification message may include the reason for the offboarding.
4. The CAPIF core function sends a remove enrolled APIs response to the AMF.
|
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
Information element
Status
Description
API invoker identity information
M
The information that determines the identity of the API invoker whose has been Offboard.
List of APIs
M
List of APIs to be removed for enrolment for the API invoker
Cause
M
The cause for revoking the API invoker.
|
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 and how the heartbeat mechanism can be enabled to detect AEF availability is FFS.
When such connectivity problems arise, the AEF associated APIs may become unavailable. The consequence is that an ongoing service API invocation may terminate abruptly or time out, leading to transactions incomplete. Without timely notifications, API invoker may repeatedly attempt reconnections which may lead to unnecessary resource waste and heighten network congestion.
The following scenario is considered for this solution: when the CAPIF core function and a API provider domain functions are not co-located, CCF detects the AEF is disconnected due to network issue and there are multiple service APIs are accessible through this AEF by API invoker(s). Though AEF availability could be reported through service API availability and service API update events, in order to reduce the number of Service API updated event notification, the CCF may consider following options:
Option 1: CCF sends a new CAPIF event (i.e., AEF status in CAPIF) without sending Service API updated event notification if the CCF consider Service API information is changed due to AEF status changing.
Option 2: CCF sends AEF status in existing CAPIF event.
Editor's Note: ：Whether the AEF identity information should be provided to the API invoker or should be hidden is FFS.
Editor's Note: ：Which option is selected is FFS.
AEF status can be defined as the follows:
- Unreachable: Unable to communicate with the CCF (e.g., due to network issues), though the AEF itself may remain functional.
- Reachable: The connection between the AEF and CCF is restored to normal after network issues.
Regarding this new CAPIF event, as an example, once the CCF detects the connection between the CAPIF core function and an AEF is disrupted, it generates event of AEF status and sends the event notification including AEF Identity information and the AEF status (i.e., unreachable) to the subscribing entity (e.g., the API invoker), then the API invoker may stop invoking the AEF associated APIs. After that, once the connection between the AEF and CCF is restored to normal, the CCF generates event of AEF status and sends the event notification including AEF Identity information and the AEF status (i.e., reachable) to the subscribing entity (e.g., the API invoker), then the API invoker may resume invoking the AEF associated APIs.
|
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 the status of its AEFs.
|
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 API information
(see NOTE 2)
O
(see NOTE 1, NOTE 3)
The service API information as specified in Table 8.3.2.1-1, except for the service API status (e.g. active, inactive).
Interface information
O
(NOTE 3)
The interface details (e.g. IP address, port number, URI) of the requested service API(s)
CAPIF core function identity information
O
(see NOTE 1, NOTE 3)
Indicates the CAPIF core function serving the service API category provided in the query criteria
AEF status reporting
O
Indicates to report AEF status towards the CCF if the service API invocation fails. Possible values are true or false. That means the API invoker sends report to CCF for reachability failure, e.g. service unavailable,.
> frequency
O
Indicates after number of failures or time after which the AEF status needs to be reported
NOTE 1: The service API information or the CAPIF core function identity information or both shall be present if the Result information element indicates that the service API discover operation is successful. Otherwise, both shall not be present.
NOTE 2: If topology hiding is enabled for the service API, the interface details shall be the interface details of AEF acting as service communication entry point for the service API.
NOTE 3: "Interface information" IE shall not be present when "Service API information" or "CAPIF core function identity information" is present.
|
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 information
M
The service API information includes the service API name, API provider name, and other information as present in Table 8.3.2.1-1 of 3GPP TS 23.222 [2].
Interface information
O
The interface details (e.g. IP address) of the requested service API(s)
Status information
O
Indicates status of the interface (e.g. unauthorized or bad response, etc.) - Mapped to server side HTTP errors that are generated when API invoker requests are received by AEF and may indicate AEF unavailability.
|
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, success availability check or failure of the request
Interface information
O
(NOTE 1)
The updated interface details (e.g. IP address of the requested and failed service API(s)) if the service API is available
Failure cause
O (NOTE 2)
Indicates reason for failure
NOTE 1: These IEs are included for success response.
NOTE 2: This IE is included for failure response.
Editor's nNote: Notification of AEF status reporting to be notified when the AEF status reporting response is “in-progress” is FFS.
Editor's nNote: Whether more information than Interface Information is needed in the sucessful AEF status reporting response is FFS.
|
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 request message to the CCF. The request message includes the parameters as specified in Table 6.6.3.2.2.1-1.
2. Upon receiving the request, the CCF checks the registration status and published API status of the AEF (i.e. interface details). If the registration is active and published APIs status is also active, the CCF sends the in-progress response to the API invoker. The CCF may proceed with step-3 to check whether the information about the AEF in AMF indicates the AEF active or not, because e.g. the internal CCF information about registration and status is obsolete. For application or protocol errors, the response indicates success, and further steps will not be executed.
3. The CCF sends AEF status check request to AMF including end point details of the AEF(s) whose status is required to check. The AMF checks whether the AEF is active or not. The AMF sends the response message back to CCF. The response includes the AEF status (either active or in-active).
NOTE 1: For application or protocol errors, the CCF should not check with AMF for AEF inactivity.
NOTE 2: If connectivity between CCF and AMF is not present, the response from AMF may not be received by the CCF.
4. If no response received from the AMF (i.e. request timeout occurred) or the AEF is in-active (as informed by AMF), the CCF updates the registration status of the API provider domain function and also updates the status of the published service APIs.
Editor's Note: AMF action when AEF is inactive is FFS.
5. The CCF sends the final response to the API invoker with updated service API list.
6. If the AMF subscribed with the CCF to notifications about AEF/Service API status changes (availability/unavailability or service API information update), the CCF also sends the monitoring service API event notification to the AMF which indicates the change of registration status of the AEF and list of APIs marked as inactive.
|
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 number of API calls to understand user engagement and growth trends.
- Response Times: Measure the time taken to process requests, helping to identify performance bottlenecks.
2. Error Tracking
- Error Rates: Monitor the frequency of errors (e.g., 4xx client errors, 5xx server errors) to quickly address issues and improve reliability.
- Error Types: Categorize errors to understand common problems and prioritize fixes.
3. User pattern
- Most Used Endpoints: Identify which API endpoints are most frequently accessed to optimize resources and focus on high-demand features.
- User Segmentation: Analyse usage patterns by different user groups (e.g., developers, internal teams) to tailor support and documentation.
- User feedback: User feedback and usage patterns to improve API offerings and enhance user experience.
4. Security Monitoring
- Unauthorized Access Attempts: Detect and log attempts to access unauthorized endpoints or resources.
- Rate Limiting Violations: Track instances where users exceed rate limits to prevent abuse and ensure fair usage.
- Anomaly behaviour: Detect of anomalies in the usage of service APIs.
5. Performance Optimization
- Latency Analysis: Identify slow endpoints and optimize them for faster response times.
- Throughput Analysis: Measure the system's ability to handle concurrent requests and scale accordingly.
6. Compliance and Auditing
- Data Usage Reports: Ensure compliance with data protection regulations by monitoring how data is accessed and used.
- Audit Logs: Maintain detailed logs of API activity for auditing purposes and to investigate potential security incidents.
Examples of how these Analytics are leveraged:
- Proactive Problem Solving: Early detection of issues allows for quick resolution, minimizing downtime and user frustration.
- Resource Allocation: Insights into usage patterns help allocate resources efficiently, ensuring high availability and performance.
- Security Enhancement: Monitoring for suspicious activities helps in identifying potential threats and implementing necessary security measures.
- Usage pattern: Understanding user pattern and preferences aids in developing new features and services.
- Efficient Management: Optimizing API performance reduces operational efficiency by minimizing resource wastage and improving efficiency.
Editor's nNote: Which analytics can be within scope of CCF is FFS.
|
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 service API analytics, the API analytics consumer e.g. AMF triggers Query service API analytics request to the CAPIF core function. Table 6.7.1-1 describes the information flow Query service API analytics request from the API analytics consumer to the CAPIF core function.
Table 6.7.1-1: Query service API analytics request
Information element
Status
Description
Identity information
M
Identity information of the entity querying service API analytics request
Analytics Query information
M
List of query filters related to the required analytics, such as Usage Metrics, Error Tracking, User pattern, Security Monitoring, Performance Optimization, Compliance and Auditing
2. Upon receiving the query service API analytics request, the CAPIF core function accesses and/or generates the necessary analytics information.
3. The CAPIF core function returns the API analytics information to the API analytics consumer in the query service API analytics response. Table 6.7.1-2 describes the information flow Query service API analytics response from the CAPIF core function to the API management function.
Table 6.7.1-2: Query service API analytics response
Information element
Status
Description
Result
M
Indicates the success or failure of query service API analytics request
API invocation analytics information
O
(see NOTE)
API analytics information such as Usage Metrics (Requests per Second, Total Requests, Response Times), Error Tracking (Error Rates, Error Types),
User pattern (Most Used Endpoints, User Segmentation, User feedback), Security Monitoring (Unauthorized Access Attempts, Rate Limiting Violations, Anomaly detection), Performance Optimization (Latency Analysis, Throughput Analysis), Compliance and Auditing (Data Usage Reports, Audit Logs)
NOTE: Information element shall be present when result indicates success.
|
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 Violations, Anomaly detection
5. Latency Analysis, Throughput Analysis
6. Data Usage Reports, Audit Logs
If the analytics functionality is internal to the CAPIF core function, the CAPIF-5 reference point as specified in 3GPP TS 23.222, between the AMF and the CAPIF core function is used for AMF as an API analytics consumer fetching API analytics from the CCF.
Editor's Note: Performing analytics inside or outside of CCF (e.g. ADAES) is FFS and outside is based on data available with CCF (i.e. CCF being data source) is FFS.
|
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 description
This section describes the solution in detail.
6.x.3.1 Information flows
This section describes the information flow tables required for this solution.
6.x.4 Solution evaluation
This section provides solution evaluation based on the open issues specified in the related key issue(s).
|
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.0
2025-09
SA6#68
S6-253504
Scope for the TR
0.1.0
2025-09
SA6#68
S6-253505
Introduction for the TR
0.1.0
2025-09
SA6#68
S6-253500
CAPIF_Ph4 Key Issue Certificate unavailability
0.1.0
2025-09
SA6#68
S6-253501
CAPIF_Ph4 Key Issue AEF operational status
0.1.0
2025-09
SA6#68
S6-253721
Enhancements to API invoker offboarding
0.1.0
2025-09
SA6#68
S6-253775
CAPIF_Ph4-KI on enhancements to CAPIF Admin
0.1.0
2025-10
SA6#69
S6-254500
Clause 3
0.2.0
2025-10
SA6#69
S6-254501
Pseudo-CR on solution for KI#1, CAPIF Administrator revocation of API Invoker enrollment information.
0.2.0
2025-10
SA6#69
S6-254502
Pseudo-CR on solution for KI#1, API invoker enrolled Service API notification
0.2.0
2025-10
SA6#69
S6-254503
Pseudo-CR on solution for KI#1 – API invoker status change
0.2.0
2025-10
SA6#69
S6-254507
Pseudo-CR on Update key issue#4
0.2.0
2025-10
SA6#69
S6-254508
Solution for KI# 4 on support for AEF operational status
0.2.0
2025-10
SA6#69
S6-254730
Pseudo-CR on Update key issue#2
0.2.0
2025-10
SA6#69
S6-254759
Pseudo-CR on solution for AEF status reporting
0.2.0
2025-10
SA6#69
S6-254764
Pseudo-CR Solution for enhancing CAPIF Administrator
0.2.0
2025-10
SA6#69
S6-254778
Pseudo-CR on new KIs on Roaming Considerations for Service API Invocation
0.2.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 architecture potential enhancements/new design and solutions needed, to support energy saving operations at the application enablement layer and provide assistance to energy saving operations at the VAL layer.
|
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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.261: "Service requirements for the 5G system; Stage 1".
[3] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[4] 3GPP TS 28.310: "Management and orchestration; Energy efficiency of 5G".
[5] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements".
[6] 3GPP TS 28.554: "Management and orchestration; 5G end to end Key Performance Indicators (KPI)".
[x7] 3GPP TS 23.502: "Procedures for the 5G system, Stage 2".
[y8] 3GPP TS 23.558: "Architecture for enabling Edge Applications".
[z9] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS)".
[aa] 3GPP TS 23.558: "Architecture for enabling Edge Applications".[r2348210] 3GPP TS 23.482: "Functional architecture and information flows for AIML Enablement Service".
[x] 3GPP TS 23.482: " Functional architecture and information flows for AIML Enablement Service".[r2343611] 3GPP TS 23.436: "Functional architecture and information flows for Application Data Analytics Enablement Service".
[r2653112] 3GPP TS 26.531: "Data Collection and Reporting; General Description and Architecture".
[zz13] 3GPP TS 23.435: "Procedures for Network Slice Capability Exposure for Application Layer Enablement Service".[yy] 3GPP TS 23.436: "Functional architecture and information flows for Application Data Analytics Enablement Service".
[2343414] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL)".[23501] 3GPP TS 23501: "System architecture for the 5G System".
|
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 Energy: As defined by the TS 28.310 [4].
Renewable energy factor: As defined by the TS 28.310 [4].
|
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 enhancements to the exisiting application enablement layer services or introduction of a new application enabler may be required to support energy saving of the resources used by the applications. Therefore, whether there is need on common functionalities from application enablemebt layer services for supporting energy saving operations need to be studied.
|
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: The study will consider the underlying 3GPP system’s existing capabilities such as leveraging the capabilities provided by core network and management system.
5.2 Key issue #2: Key Issue on monitoring and exposure of energy consumption
|
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 consumption collection, calculation, and exposure.
Measurement of the energy efficiency of NG-RAN, 5G Core and network slicing and the optimization of the energy saving have been defined in 3GPP TS 28.310 [4], 3GPP TS 28.552 [5], and 3GPP TS 28.554 [6].
Energy consumption used by application enablement services may vary based on the services’ performance level, usage level and localization. Furthermore, the energy consumption associated with application enablement services may fluctuate over time due to different conditions (e.g., varying traffic load) and hence may need to be monitored.
Consumers of application enablement services may need exposure of the energy consumption information associated to consumed application enablement services and may need to be informed about energy consumption. For example, a consumer of application enablement services may be informed about energy consumption related to its usage of the services and may reduce its interactions to lower energy consumption.
This key issue proposes to study support monitoring of energy consumption measurements and exposure of energy consumption information associated with usage of the application enablement layer.
|
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 application enablement layer.
3. Whether and how the application enablement layer can support exposing energy consumption results related to monitoring energy consumption.
5.3 Key issue #3: EDGE application enablement enhancement for energy efficiency
Energy efficiency and energy saving is a critical feature in 5G. As use case studied in 3GPP TR 22.882, clause 5.14, use case on reducing GHG footprint of Application Services, green services could be provided.
The related requirements defined in 3GPP TS 22.261 [2] including:
- Subject to operator policy and agreement with 3rd party, the 5G system shall provide a mechanism to support the selection of an application server based on energy consumption information associated with a set of application servers.
As for now, EDGE service as defined in 3GPP TS 23.558 [8], is provided mostly based on service KPI, without fully considering the energy efficiency and energy saving, therefore, this key issue will study:
1. Whether and how the EDGE application enablement layer needs to be enhanced to support energy saving and energy efficiency?
2. How EDGE application enablement service could be enhanced to support energy saving and energy efficiency, including how to support the selection of an edge application server based on energy consumption information.
5.4 Key issue #4: Support AIMLE enhancements for AIML services energy saving
|
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 side as well as the network side. 3GPP TS 22.261 [2] has defined energy related information as a service criterion for multiple service including AIML.
3GPP SA6 in Rel-18 specified an application data analytics enablement functionality (ADAES, 3GPP TS 23.436 [11]). ADAES is a SEAL functionality for providing end to end performance analytics (e.g. VAL server performance). One analytics service of ADAES, as introduced in Rel-19, is the Support for DN energy Analytics. This feature supports a logical functionality at the ADAES to provide analytics on the energy consumption /efficiency of an edge platform (including the EESs / EASs). The DN energy analytics is performed per DNN/ DNAI and may be used to trigger the application server migration to different cloud. The analytics are based on NWDAF analytics and UPF/DN measurements on user plane load as well as edge/app side measurements on the energy consumption.
In addition, in Rel-19 AIML Enablement (AIMLE) service is described in 3GPP TS 23.482 [10]. AIMLE server is a SEAL server which includes of a common set of services for comprehensive enablement of AIML functionality. AIMLE server defines the following group of capabilities:
• Support for application-layer ML model related aspects, including model retrieval, model training, model monitoring, model selection, model update and model storage / discovery.
• Assistance in AI/ML task transfer and split AI/ML operations.
• Support HFL/VFL operations, including FL member registration, FL grouping and FL-related events notification, VFL feature alignment, HFL training.
• Support for AIMLE client registration, discovery, participation and selection.
Given the fact that ADAES supports ML-enabled analytics using AIMLE service (as defined in 3GPP TS 23.482 [10]), and in particular the requirement for an ADAE/AIMLE Client undertaking part of an ML task, such as ML model training in an FL operation, the energy consumption / efficiency analytics would help selecting the most appropriate UE as ML/FL member in the application layer ML task (e.g. training, inference).
|
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 to use energy consumption information to fulfill FL member selection, AIMLE client selection, split AI/ML operation, etc.
5.5 Key issue #5: NSCE enhancement for energy efficiency
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.
3GPP TS 22.261 [2] has defined that network slice support for alternative service for energy saving reasons, energy consumption monitoring at per network slice and per subscriber granularity, expose information on energy consumption. These requirements may have effect on NSCE.
3GPP TS 23.501 [3] has defined following information of energy consumption information which can exposure to AF:
- For UE level energy exposure, the consumer NF provides UE ID (SUPI/GPSI).
- For S-NSSAI of the UE level exposure, the consumer NF provides UE ID (SUPI/GPSI), S-NSSAI.
- For PDU session level exposure, the consumer NF provides UE ID (SUPI/GPSI), DNN/S-NSSAI.
- For Service Data Flow level exposure (e.g. per UE per application), the consumer NF provides UE ID (SUPI/GPSI), DNN/S-NSSAI and application information, e.g. Application Identifier, or Flow description(s).
Based on information above, this key issue will study:
1. Whether and how to enhance functionalities of NSCE to support for energy efficiency and energy saving.
2. Whether and how to use energy consumption information to fulfill network slice selection, modification, adaptation, etc.
5.6 Key issue #6: Application Enablement Layer Services for Energy Saving
|
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 may be enhanced to support energy saving capabilities in order to satisfy the request from consumer (e.g. VAL server). Examples include (but not limited to):
- Data delivery via SEALDD server and client consumes energy. For example, enhancements to the SEALDD server on adjustment of data delivery configuration with consideration of energy contains is needed.
- LM client reports location information consumes energy. LM service on location information collection can be adjusted, for example, adjustment of LCS QoS to reduce energy consumption and/or switch LM client location reporting to network location reporting to saving energy at the UE side.
- There are existing ADAE analytics on energy efficiency, for example, DN Energy Efficiency analytics, can be used for supporting energy saving of the network resources in some applications. To support wider range of applications, potential enhancements to the ADAE services may needed, e.g., enhance existing ADAE analytics and/or introduce new analytics.
Therefore, whether existing application enablement layer services including SEALDD, LM, ADAE, etc., can be enhanced to support energy saving of the resources used by applications need to be studied.
|
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 considered in this Key Issue are the ones which are not covered in the other Key Issues.
NOTE 2: The study will consider the underlying 3GPP system’s existing capabilities such as leveraging the capabilities provided by core network and management system.
|
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 #X21: New Service on Energy Saving Assistance
6.X21.1 Solution Description
6.X21.1.0 General
The following clauses specify the procedure and information flow on energy saving assistance provisioning.
6.X21.1.1 Procedure
Figure 6.X21.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.X21.1.2.2-1.
2. The SEAL server authenticates and authorizes the request. If authorized, the SEAL server determines the next actions (e.g. collect energy-related data, monitor energy-related information/status) for assisting energy saving. The ESE server can consolidate similar requests from Consumers (e.g., data collection from same source into single southbound requests, avoid re-fetching data that it already has if the request parameters allow it such as time frame matches, etc.).
3. The SEAL server sends energy-related data collection response to the consumer. The response includes information as described in Table 6.X21.1.2.3-1.
4. The SEAL server collects energy consumption information, monitor energy status, and generates assistance information for energy saving based on the data/information obtained in step 4.
5. The SEAL server sends energy saving assistance notify to the consumer with the assistance information. The notify includes information as described in Table 6.X21.1.2.4-1.
Editor’s Note: The update of the solution is FFS.
6.X21.1.2 Information Flows
6.X21.1.2.1 General
The following information flows are specified for energy saving assistance.
6.X21.1.2.2 Energy saving assistance request
Table 6.X21.1.2.2-1 shows the request sent by a SEAL service consumer to a SEAL server for energy saving assistance procedure.
Table 6.X21.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 VAL service for which the request applies.
Target energy saving entity(ies)
M
The identity(ies) of the target energy saving entity(ies) (e.g. VAL UE ID(s), SEAL server ID(s))
Assistance requirements
M
Identifies the requirement for the assistance on energy saving.
>Assistance information type
M
Identifies the assistance information type required for energy saving (e.g. information on entity which consume the most/least energy, assistance information for selection of entity(ies)).
6.X21.1.2.3 Energy saving assistance response
Table 6.X21.1.2.3-1 shows the response sent by the SEAL server to the consumer for energy saving assistance procedure.
Table 6.X21.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
Identifier of the subscription. It shall be provided if the request if the Result is positive acknowledgement.
6.X21.1.2.4 Energy saving assistance notify
Table 6.X21.1.2.4-1 shows the notification sent by the SEAL server to the consumer for energy saving assistance procedure.
Table 6.X21.1.2.4-1: Energy saving assistance notify
Information element
Status
Description
Success status
O
(NOTE)
Indicates that energy saving assistance was successful.
>Assistance information
M
Provides energy saving assistance information corresponding to the request.
Failure response
O
(NOTE)
Indicates that energy saving assistance was failure.
>Cause
M
Reason for the failure.
NOTE: One of the information elements shall be provided in the output.
6.X21.2 Architecture impacts
Editor’s Note: The architecture impacts of the solution is FFS.
6.X21.3 Solution evaluation
Editor’s Note: The evaluation of the solution is FFS.
6.x2 Solution #x2: Edge Application Server Discovery by Considering Renewable energy
6.x2.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 service may use a single IP address (anycast address) or different IP addresses. To start such a service, the UE needs to know the IP address(es) of the Application Server(s) serving the service. The UE may do a discovery to get the IP address(es) of a suitable Edge Application Server (e.g. the closest one), so that the traffic can be locally routed to the Edge Application Server and service latency, traffic routing path and user service experience can be optimized.
During the EAS discovery procedure, that the renewable energy of EAS is not considered. 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.
6.x2.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 [y8]. 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 time that solar energy can be consumed, the EES may select this EAS to save the energy.
6.x2.3 Procedure
6.x2.3.1 Procedure of subscription Energy information from EAS
Figure 6.x2.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 EAS.
The energy information includes Renewable energy of EAS. The Renewable energy of EAS includes that either the indication of the EAS consumes renewable energy or not, or the Renewable energy factor of EAS.
The time period indicates the EAS to notify the Energy information of EAS in the certain time period in the future.
2. Upon receiving the request from the EES, the EAS checks if the EEC is authorized to subscribe for information of the requested EAS(s).
3. If the processing of the request was successful, the EAS sends an EAS energy information subscription response to the EES, which includes the subscription identifier and may include the expiration time, indicating when the subscription will automatically expire.
4. The EAS sends an EAS renewable energy utilization notification to the EES.
Editor’s nNote: How EAS know the capability of renewable energy supporting is FFS.
6.x2.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 [y8].
|
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 determines the next actions (e.g. collect energy-related data, monitor energy-related information/status) for assisting energy saving. The ESE server can consolidate similar requests from Consumers (e.g., data collection from same source into single southbound requests, avoid re-fetching data that it already has if the request parameters allow it such as time frame matches, etc.).
3. The SEAL server sends energy-related data collection response to the consumer. The response includes information as described in Table 6.1.1.2.3-1.4. The SEAL server collects energy consumption information, monitor energy status, and generates assistance information for energy saving based on the data/information obtained in step 4.
5. The SEAL server sends energy saving assistance notify to the consumer with the assistance information. The notify includes information as described in Table 6.1.1.2.4-1.
Editor’s Note: The update of the solution is FFS.
|
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 VAL service for which the request applies.
Target energy saving entity(ies)
M
The identity(ies) of the target energy saving entity(ies) (e.g. VAL UE ID(s), SEAL server ID(s))
Assistance requirements
M
Identifies the requirement for the assistance on energy saving.
>Assistance information type
M
Identifies the assistance information type required for energy saving (e.g. information on entity which consume the most/least energy, assistance information for selection of entity(ies)).
|
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
Identifier of the subscription. It shall be provided if the request if the Result is positive acknowledgement.
|
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 information
M
Provides energy saving assistance information corresponding to the request.
Failure response
O
(NOTE)
Indicates that energy saving assistance was failure.
>Cause
M
Reason for the failure.
NOTE: One of the information elements shall be provided in the output.
|
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 service may use a single IP address (anycast address) or different IP addresses. To start such a service, the UE needs to know the IP address(es) of the Application Server(s) serving the service. The UE may do a discovery to get the IP address(es) of a suitable Edge Application Server (e.g. the closest one), so that the traffic can be locally routed to the Edge Application Server and service latency, traffic routing path and user service experience can be optimized.
During the EAS discovery procedure, that the renewable energy of EAS is not considered. 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.
|
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 time that solar energy can be consumed, the EES may select this EAS to save the energy.
|
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 EAS.
The energy information includes Renewable energy of EAS. The Renewable energy of EAS includes that either the indication of the EAS consumes renewable energy or not, or the Renewable energy factor of EAS.
The time period indicates the EAS to notify the Energy information of EAS in the certain time period in the future.
2. Upon receiving the request from the EES, the EAS checks if the EEC is authorized to subscribe for information of the requested EAS(s).
3. If the processing of the request was successful, the EAS sends an EAS energy information subscription response to the EES, which includes the subscription identifier and may include the expiration time, indicating when the subscription will automatically expire.
4. The EAS sends an EAS renewable energy utilization notification to the EES.
Editor’s Note: How EAS know the capability of renewable energy supporting is FFS.
|
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 policy are out of scope.
Figure 8.5.2.2-1: EAS Discovery procedure
1. The EEC sends an EAS discovery request to the EES. The EAS discovery request includes the requestor identifier [EECID] along with the security credentials and may include EAS discovery filters, EEC service continuity support, and may also include UE location to retrieve information about particular EAS(s) or a category of EASs, e.g. gaming applications, or Edge Applications Server(s) available in certain service areas, e.g. available on a UE's predicted or expected route. The request may include an EAS selection request indicator. If an e2e tunnel is used in the UE for applications (e.g. user configured tunnel service), and if the tunnel service provider and the ECSP are from the same organization and only if user grants the permission, then the EEC provides the tunnel information for the associated applications in the request to the EES considering user consent. The EAS discovery filter may include energy requirements to the EAS, e.g., Energy mode, Energy type supports. The Energy type is about requirement to the EAS on its supported energy type (e.g. non-renewable energy and/or renewable energy).
NOTE 2: The e2e tunnel case is limited to case where the tunnel service is deployed in home domain in the present release.
2. Upon receiving the request from the EEC, the EES checks if the EEC is authorized to discover the requested EAS(s). The authorization check may apply to an individual EAS, a category of EASs or to the EDN, i.e. to all the EASs. If EAS discovery filters contain energy requirements, the EES checks whether the EAS satisfy the requirements on Energy type supports in the EAS discovery requests. If the EAS fulfil the energy requirements, then EES adds the identified EAS(s) into the list of discovered EAS(s). If UE's location information is not already available, the EES obtains the UE location by utilizing the capabilities of the 3GPP core network as specified in clause 8.10.3. If EAS discovery filters are provided by the EEC, but it does not contain Application group profile, the EES identifies the EAS(s) based on the provided EAS discovery filters and the UE location. For the identified EAS(s) if EAS profile indicates the list of associated devices required in order to serve the UE, then EES checks whether the UE has required associated devices with it or not based on AC profile received in EAS discovery request. If the UE has the required associated devices then EES adds the identified EAS(s) into the list of discovered EAS(s).
When the bundle EAS information is provided, then
- If bundle EAS information includes EAS bundle identifier, the EES identifies all or part of the EAS(s) associated with the same EAS bundle identifier.
- If bundle EAS information includes a list of EASIDs, the EES identifies the EASs which are all or part of the EAS bundle.
If the EEC indicates that service continuity support is required, when identifying the EAS, the EES shall take the indication which ACR scenarios are supported by the AC, the EEC, the EES and the EAS and which of these are preferred by the AC into consideration. The EES may select one EAS and determine whether to perform application traffic influence for this EAS in advance based on AC's service KPI or EAS’s service KPI in desired response time, when the EAS does not perform traffic influence in advance. If the EES determines to perform application traffic influence for this EAS in advance, then the EES will applies the AF traffic influence of the EAS in the 3GPP Core Network before sending EAS discovery response.
If the Prediction expiration time is provided then the EES may determine whether to identify the instantiable but not instantiated EAS as T-EAS based on Prediction expiration time and the predicted EAS deployment time information obtained from ADAES as specified in clause 8.11 of TS 23.436 [28] or from local configured maximum EAS deployment time. The EES determines remaining EAS instantiation time or EAS instantiation completion time based on the timing receiving EAS instantiation is in progress from ECSP management system and the predicted EAS deployment time. Furthermore, if EES received the indication which the EAS instantiation is in progress, then the EES determines whether to identify the EAS which instantiation in progress as T-EAS based on Prediction expiration time and remaining EAS instantiation time information.
When EAS discovery filters are not provided, then:
- if available, the EES identifies the EAS(s) based on the UE-specific service information at the EES and the UE location;
- EES identifies the EAS(s) by applying the ECSP policy (e.g. based only on the UE location),
When EAS discovery filters contain Application group profile, the EES checks whether information about common EAS and related Application Group ID is available or not. If the common EAS information related to the Application Group ID is:
- not available at the EES, then based on the policy if EES needs to select the common EAS, the EES identifies an EAS for the Application Group ID based on the provided EAS discovery filters such as KPIs, UE-specific service information or the ECSP policy. Furthermore, the EES stores the common EAS information and related Application Group ID. The EES may also subscribe and get the notifications of candidate DNAIs for the UEs of the group as described in 3GPP TS 23.548 [20], 3GPP TS 23.501 [2], the EES identifies the EAS(s) taking the candidate DNAIs into account, e.g., an EAS where its DNAI in the EAS profile is common to all UEs in the group.
- available at the EES, then the EES provides information of that EAS as result for EAS discovery, or the EES identifies the EAS based on the provided EAS discovery filters and the UE location when E2E response time is received, furthermore:
- when the UE in the overlapping area between the EDNs of common EAS and EAS registered to this EES (e.g. UE can connect either common EAS or EAS registered to this EES which is UE is in the common EAS service area), the EES identifies either common EAS or EAS registered to this EES for the UE based on the UE location, EAS discovery filters, application group profile, common EAS KPI as specified in table 8.2.5 and EDN information, registered EAS KPI as specified in table 8.2.5 and EDN information, and inter-EAS communication performance of these EASs and checks whether the common EAS or EAS registered to this EES can provide better E2E response time.
- When the UE is not in the overlapping area between the EDNs of common EAS and EAS registered to this EES (e.g. UE is not in the common EAS service area), then the EES identifies candidate EAS(s) for the group from its registered EASs based on UE location, EAS discovery filters and application group profile and checks if the candidate EAS(s) can satisfy the E2E response time considering the response time of the candidate EAS(s), the response time of available common EASs in other EDNs and the inter-EAS communication latency. If the E2E response time cannot be satisfied, the EES will respond the EEC in step 3 indicating such a rejection reason; otherwise, the EES selects a candidate EAS and interacts with the ECS-ER to store it as common EAS as described in clause 8.20.2.3.
NOTE 3: The EES can use ADAE analytics service in 3GPP TS 23.436 [28] or local configuration to obtain application performance (e.g. latency) for inter-EAS communication.
NOTE 4: If the current EDN has overlapping area (where UE resides) with other EDN and both EDNs has available common EAS which can satisfy E2E response time, which EAS to select can take number of UEs in the group connected to available common EAS into consideration.
NOTE 5: The EES may have previously determined and stored the common EAS for Application group ID, or the EES may have received the common EAS selection information for Application group ID during the common EAS announcement procedure.
When the ECS-ER is not available and the EES selects the common EAS, the selected common EAS shall be announced to other EES(s) as per procedure specified in clause 8.19.
When the ECS-ER is available, if the common EAS information related to the Application Group ID is:
- not available at the ECS-ER, the EES identifies one EAS for the group and interacts with the ECS-ER to store the common EAS information as described in clause 8.20.2.3. The EES may also subscribe and get the notifications of candidate DNAIs for the UEs of the group as described in 3GPP TS 23.548 [20], 3GPP TS 23.501 [2], the EES identifies the EAS(s) taking the candidate DNAIs into account, e.g., an EAS where DNAI in the EAS profile is common to all UEs in the group.
- available at the ECS-ER, then the ECS-ER returns the common EAS information to the EES as described in clause 8.20.2.3, or the EES identifies the EAS based on the provided EAS discovery filters and the UE location when E2E response time is received, furthermore:
- When the UE is in the overlapping area between the EDNs of common EAS and EAS registered to this EES (e.g. UE can connect either common EAS or EAS registered to this EES, which is UE is in the common EAS service area), the EES identifies either common EAS or EAS registered to this EES for the UE based on the UE location, EAS discovery filters, application group profile, common EAS KPI as specified in table 8.2.5 and EDN information, registered EAS KPI as specified in table 8.2.5 and EDN information, and inter-EAS communication performance of these EASs and checks whether the common EAS or EAS registered to this EES can provide better E2E response time.
- When the UE is not in the overlapping area between the EDNs of common EAS and EAS registered to this EES (e.g. UE is not in the common EAS service area), the EES checks with the ECS-ER about all available common EASs and their corresponding EDNs by using procedure defined in clause 8.20.2.2. If no common EAS is available for the group, EES identifies one EAS for the group and interacts with the ECS-ER to store the common EAS information as described in clause 8.20.2.3. If current EDN already has available common EAS, the EES selects such common EAS considering UE location, EAS discovery filters, application group profile and the required E2E response time. If there are available common EASs in other EDNs, the EES identifies candidate EAS(s) for the group from its registered EASs and checks if the candidate EAS(s) can satisfy the E2E response time considering UE location, EAS discovery filters, application group profile, and the response time of the candidate EAS(s), the response time of available common EASs in other EDNs and the inter-EAS communication latency. If the E2E response time cannot be satisfied, the EES will respond the EEC in step 3 indicating such a rejection reason; otherwise, the EES selects a candidate EAS and interacts with the ECS-ER to store it as common EAS as described in clause 8.20.2.3.
NOTE 6: The EES can use ADAE analytics service in 3GPP TS 23.436 [28] or local configuration to obtain application performance (e.g. latency) for inter-EAS communication.
NOTE 7: Details of the UE-specific service information and how it is available at the EES is out of scope.
NOTE 8: Both steps are evaluated prior to sending a response.
Upon receiving the request from the EEC, the EES may also collect edge load analytics from ADAES (as specified in clause 8.8.2 of TS 23.436 [28]) or performance data from OAM to find whether the EAS(s) satisfies the Expected AC service KPIs or the Minimum required AC Service KPIs.
Upon receiving the request from the EEC, if the EEC does not indicate EAS Instantiation Triggering Suppress in the EAS Discovery request, the EES may trigger the ECSP management system to instantiate the EAS that matches with EAS discovery filter IEs (e.g. ACID) as in clause 8.12.
Otherwise, upon receiving the request from the EEC, if the EEC indicates EAS Instantiation Triggering Suppress in the EAS Discovery request and the EES supports such capability, the EES determines not triggering the ECSP management system to instantiate the EAS and may determine Instantiable EAS Information for EAS(s) that are instantiable but not yet instantiated and match the EAS discovery filter IEs. Instantiable EAS Information is provided in the EAS Discovery response and includes the EASID(s) and, for each EASID, the status indicating whether the EAS is instantiated or instantiable but not yet instantiated.
If the EEC provides in the EAS discovery request the EAS selection request indicator, the EES selects EAS satisfying the EAS discovery filter or based on other information (e.g. ECSP policy) as described above (if no EAS discovery filter received), and then provides the selected EAS information to the EEC in the discovered EAS list of EAS discovery response.
NOTE 9: Without EAS selection request indication, the EES handling is as per R17 procedure.
If the tunnel information is received, the EES additionally takes it into consideration in identifying EAS(s). If no tunnel information is received, the EES additionally takes the N6 tunnel (e.g. L2TP) information from 3GPP core network (via NEF user plane path management service as described in 3GPP TS 23.501 [2], clause 5.6.7) or NATed UE IP address (e.g. by local UPF based on local configuration) and EAS IP address information into consideration in identifying EAS(s). For instance, the IP address(es) of identified EAS(s) needs to be topologically close to the IP address of the tunnel server, local UPF (based on NATed UE IP address) or NATed UE for optimal N6 route.
3. If the processing of the request was successful, the EES sends an EAS discovery response to the EEC, which includes information about the discovered EASs and Instantiable EAS Information. For discovered EASs, this includes endpoint information. If the EES perform traffic influence for EAS(s) in step 2, then the discovered EAS(s) is with optimized traffic route. Depending on the EAS discovery filters received in the EAS discovery request, the response may include additional information regarding matched capabilities, e.g. service permissions levels, KPIs, AC locations(s) that the EASs can support, ACR scenarios supported by the EAS, etc., and regarding satisfied energy requirements, e.g., supported energy type. The EAS discovery response may contain a list of EASs and Instantiable EAS Information with EAS instantiation completion time. This list may be based on EAS discovery filters containing a Geographical or Topological Service Area, e.g. a route, included in the EAS discovery request by the EEC. When the discovered EAS is for a certain application group, then the Application Group ID is also included in the response message. If the discovered EAS is registered to another EES, then the EES endpoint of the EES where the discovered EAS is registered is also included in the response message.
When the EES accepts the request and determines to trigger the EAS instantiation, then the response may indicate that the EAS instantiation is in progress so that the detailed EAS profile information will be available later. Then the EES determines the remaining EAS instantiation time or EAS instantiation completion time based on the timing receiving EAS instantiation in progress ECSP management system and the predicted EAS deployment time. When EEC receives the EAS instantiation in progress indication, the EEC may send EAS discovery subscription request message if not subscribed yet or send EAS discovery request message later to the EES for obtaining updated EAS information.
If the EES is unable to determine the EAS information using the inputs in the EAS discovery request, UE-specific service information at the EES or the ECSP policy, the EES shall reject the EAS discovery request and respond with an appropriate failure cause.
If the EEC is not registered with the EES, and ECSP policy requires the EEC to perform EEC registration prior to EAS discovery, the EES shall include an appropriate failure cause in the EAS discovery response indicating that EEC registration is required.
If the UE location and predicted/expected UE locations, provided in the EAS discovery request, are outside the Geographical or Topological Service Area of an EAS, then the EES shall not include that EAS in the discovery response. The discovery response may include EAS(s) that cannot serve the UE at its current location if a predicted/expected UE location was provided in the EAS discovery request.
Upon receiving the EAS discovery response, if the EEC selects an EAS which is instantiated (i.e., an EAS profile was provided), the EEC uses the endpoint information for routing of the outgoing application data traffic to EAS(s), as needed, and may provide necessary notifications to the AC(s). The EEC may use the border or overlap between EAS Geographical Service Areas for service continuity purposes. The EEC may cache the EAS information (e.g. EAS endpoint) for subsequent use and avoid the need to repeat step 1. If the Lifetime IE is included in the response, the EEC may cache the EAS information only for the duration specified by the Lifetime IE.
Upon receiving the EAS discovery response, if the EEC selects an EAS which is instantiable but not yet instantiated (i.e. an EAS profile is not provided), the EEC sends the EAS information provisioning request indicating the selected EASID as in clause 8.15. If the EAS discovery response message contains the EAS(s) information along with r EAS instantiation completion time which the EAS instantiation in progress, then the EEC determines whether to identify the EAS which instantiation in progress as T-EAS based on Prediction expiration time and remaining EAS instantiation time/EAS instantiation completion time. If the EEC determines to identify the EAS for which instantiation is in-progress, the EEC may retry to discover the EAS and send the EAS discovery request again after waiting for the time as included in the response message, otherwise, the EAS discovery may fail.
NOTE 10: Within the duration specified by the Lifetime IE, the cached EAS Profile can be updated (e.g. according to notifications from the EES for changes of EAS information due to EAS status change) or the cached EAS Profile can be invalidated due to new EAS information discovery (e.g. due to UE mobility). The EEC can update or invalidate the cached EAS information (e.g. on PDU Session Release or Modification Command).
NOTE 11: The AC can cache the EAS information (e.g. EAS endpoint) for subsequent use. In the case of the cached information needing to be updated or invalidated, the mechanisms for the EEC to notify the AC is up to implementation and is not specified in the current release of the present document.
NOTE 12: The EEC can use the EAS information provided by the discovery procedure to perform service continuity planning, for example when ultra-low latency ACR is required.
If the EAS discovery request fails, the EEC may resend the EAS discovery request, taking into account the received failure cause. If the failure cause indicated that EEC registration is required, the EEC shall perform an EEC registration before resending the EAS discovery request.
NOTE 13: As long as a proper EAS (e.g. considering expected AC service KPIs included in EAS discovery request) is discovered and selected by the EES, EEC of a constraint UE can stop sending EAS discovery to rest candidate EES(s), and provide the selected EAS information to AC.
The information flow for EAS discovery as specified in clause 8.5.3.2 of 3GPP TS 23.558 [aa8] is enhanced as follows (new text in bold italics):
|
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
|
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.3.1 Solution Description
| According to the key issue #3, there is a need for EDGE application enablement layer enhance to support energy saving. The services procedures and information flows introduced in 3GPP TS 23.558 [8] for edge services, can be enhanced to support the energy saving requirements.
The procedure for EAS discovery as specified in clause 8.5.2.2 of 3GPP TS 23.558 [8] is enhanced as follows (new text in bold italics):
|
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 8.5.3.2 EAS discovery request
| Table 8.5.3.2-1 describes information elements for the EAS discovery request. Table 8.5.3.2-2 provides further detail about the EAS Discovery Filter information element.
Table 8.5.3.2-1: EAS discovery request
Information element
Status
Description
Requestor identifier
M
The ID of the requestor (e.g. EECID)
UE Identifier
O
The identifier of the UE (i.e., GPSI)
Security credentials
M
Security credentials resulting from a successful authorization for the edge computing service.
EAS discovery filters
O
Set of characteristics to determine required EASs, as detailed in Table 8.5.3.2-2.
UE location
O
The location information of the UE. The UE location is described in clause 7.3.2.
List of UE IDs
O
List of UE IDs in an Application Group, applicable for S-EAS or S-EES triggered EAS discovery request.
Serving MNO information (NOTE 2)
O
The serving MNO information (e.g. MNO name, PLMN ID) which is serving the subscriber.
Target DNAI (NOTE 1)
O
Target DNAI information which can be associated with potential T-EAS(s)
EEC Service Continuity Support
O
Indicates if the EEC supports service continuity or not. The IE also indicates which ACR scenarios are supported by the EEC or, if this message is sent by the EEC to discover a T‑EAS, which ACR scenario(s) are intended to be used for the ACR.
EES Service Continuity Support (NOTE 1)
O
The IE indicates if the S-EES supports service continuity or not. The IE also indicates which ACR scenarios are supported by the S-EES or, if the EAS discovery is used for an S‑EES executed ACR according to clause 8.8.2.5, which ACR scenario is to be used for the ACR.
EAS Service Continuity Support (NOTE 1)
O
The IE indicates if the S-EAS supports service continuity or not. The IE also indicates which ACR scenarios are supported by the S-EAS or, if the EAS discovery is used for an S‑EAS decided ACR according to clause 8.8.2.4, which ACR scenario is to be used for the ACR.
EAS Instantiation Triggering Suppress
O
Indicates to the EES that EAS instantiation triggering should not be performed for the current request, and Instantiable EAS Information (e.g. instantiated, instantiable but not be instantiated yet) is to be provided in response.
EAS selection request indicator
O
Indicates the request for EAS selection support from the EES (e.g., for constrained device).
Indication of service continuity planning
O
Indicates that this EAS discovery request is triggered for service continuity planning.
Prediction expiration time
O
The estimated time the UE may reach the Predicted/Expected UE location or EAS service area at the latest. This IE is used by EES as analytics input to get edge load analytics information from ADAES service as described in clause 8.8 of TS 23.436 [28].
Tunnel information
O
It includes service provider ID, the endpoint address (e.g. IP address) of the tunnel server associated with application(s).
NOTE 1: This IE shall not be included when the request originates from the EEC.
NOTE 2: This IE shall be included if edge node sharing is used.
Table 8.5.3.2-2: EAS discovery filters
Information element
Status
Description
List of AC characteristics (NOTE 1)
O
Describes the ACs for which a matching EAS is needed.
> AC profile (NOTE 2)
M
AC profile containing parameters used to determine matching EAS. AC profiles are further described in Table 8.2.2-1.
> Application group profile (NOTE 6)
O
Application group profile associated with the AC Profile, as defined in Table 8.2.11-1.
List of EAS characteristics (NOTE 1, NOTE 3)
O
Describes the characteristic of required EASs.
> EASID
O
Identifier of the required EAS.
> Application Group ID
O
Application group identifier as defined in 7.2.11.
> EAS content synchronization support
O
Indicates if the EAS content synchronization support is required or not.
> Bundle ID (NOTE 5)
O
A list of EASIDs or a bundle ID as described in clause 7.2.10.
> List of EASIDs (NOTE 5)
O
A list of EASIDs specific to a particular EAS bundle.
> Bundle type (NOTE 4)
O
Type of the EAS bundle as described in clause 7.2.10
> EAS bundle requirements (NOTE 4)
O
Requirements associated with the EAS bundle as described in clause 8.2.10.
> EAS provider identifier
O
Identifier of the required EAS provider
> EAS type
O
The category or type of required EAS (e.g. V2X, UAV, application enabler)
> EAS schedule
O
Required availability schedule of the EAS (e.g. time windows)
> EAS Geographical Service Area (NOTE 6)
O
Location(s) (e.g. geographical area, route) where the EAS service should be available.
> EAS Topological Service Area (NOTE 6)
O
Topological area (e.g. cell ID, TAI) for which the EAS service should be available. See possible formats in Table 8.2.7-1.
> Service continuity support
O
Indicates if the service continuity support is required or not.
> Service permission level
O
Required level of service permissions e.g. trial, gold-class
> Service feature(s)
O
Required service features e.g. single vs. multi-player gaming service
> Energy type
O
Indicates what energy type support is required, e.g. non-renewable energy, renewable energy.
NOTE 1: Either "List of AC characteristics" or "List of EAS characteristics" shall be present.
NOTE 2: "Preferred ECSP list" IE shall not be present.
NOTE 3: The "List of EAS characteristics" IE must include at least one optional IE, if used as an EAS discovery filter.
NOTE 4: When EAS discovery request is sent by the EEC, this IE shall not be included.
NOTE 5: “Bundle ID" and "List of EASIDs" shall not both be present.
NOTE 6: If application group profile IE is present, the expected group geographic service area IE present in the application group profile is preferentially used. If there is no EAS satisfied the expected group geographic service area or EAS does not provide better E2E response time, then the UE location and other service area IEs are considered.
The information flow of EAS Profile for EAS registration and discovery as specified in clause 8.2.4 of 3GPP TS 23.558 [aa8] is enhanced as follows (new text in bold italics):
|
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 8.2.4 EAS Profile
| An EAS Profile includes information about an EAS used to describe services and service characteristics offered.
NOTE: Information elements in the EAS Profile are provided by the ASP.
Table 8.2.4-1: EAS Profile
Information element
Status
Description
EASID
M
The identifier of the EAS
EAS Endpoint
M
Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the EAS. This information maybe discovered by EEC and exposed to ACs so that ACs can establish contact with the EAS.
List of EAS bundle information
O
List of EAS bundles to which the EAS belongs and related bundling requirements.
> Bundle ID
(NOTE 3)
O
Bundle ID as described in clause 7.2.10.
> List of EAS IDs
(NOTE 2, NOTE 3)
O
List of the EAS IDs of the EASs to be invoked by the EAS for an EAS driven association of EASs.
> Bundle type
M
Type of the EAS bundle as described in clause 7.2.10
> Main EASID
O
Indicate which EAS in a bundle takes the main EAS service role.
> EAS bundle requirements
O
Requirements associated with the EAS bundle as described in clause 8.2.10.
ACID(s)
O
Identifies the AC(s) that can be served by the EAS
EAS Provider Identifier
O
The identifier of the ASP that provides the EAS.
Allowed MNO information (NOTE 4)
O
Information of the allowed operator (e.g. MNO name, PLMN ID) from which its subscriber can consume the EAS services
EAS Type
O
The category or type of EAS (e.g. V2X, UAV, application enabler)
EAS description
O
Human-readable description of the EAS
EAS Schedule
O
The availability schedule of the EAS (e.g. time windows)
EAS Geographical Service Area
O
The geographical service area that the EAS serves. ACs in UEs that are located outside that area shall not be served.
EAS Topological Service Area
O
The EAS serves UEs that are connected to the Core Network from one of the cells included in this service area. ACs in UEs that are located outside this area shall not be served. See possible formats in Table 8.2.7-1.
EAS Service KPIs
O
Service characteristics provided by EAS, detailed in Table 8.2.5-1
EAS service permission level
O
Level of service permissions e.g. trial, gold-class supported by the EAS
EAS Feature(s)
O
Service features e.g. single vs. multi-player gaming service supported by the EAS
EAS content synchronization support
O
Indicates if the EAS supports content synchronization between EASs.
EAS Service continuity support
O
Indicates if the EAS supports service continuity or not. This IE indicates which ACR scenarios are supported by the EAS, also indicates the EAS ability (e.g. EAS bundle information) of handling bundled EAS coordinate ACR.
EAS Transport layer service continuity support
O
This IE indicates the EAS service continuity support for seamless transport layer (e.g. TCP/TLS/QUIC) relocation
General context holding time duration (NOTE 1)
O
The time duration that the EAS holds the context before the AC connects to the EAS in case of ACR for service continuity planning. It is an indication of the time the EAS holds the application context for a UE to move to its service area after receiving an ACR notification from the EES following an ACR request from the EEC.
List of EAS DNAI(s)
O
DNAI(s) associated with the EAS. This IE is used as Potential Locations of Applications in clause 5.6.7 of 3GPP TS 23.501 [2].
It is a subset of the DNAI(s) associated with the EDN where the EAS resides.
List of N6 Traffic Routing requirements
O
The N6 traffic routing information and/or routing profile ID corresponding to each EAS DNAI.
EAS Availability Reporting Period
O
The availability reporting period (i.e. heartbeat period) that indicates to the EES how often it needs to check the EAS's availability after a successful registration.
EAS Status
O
The status of the EAS (e.g. enabled, disabled, overload warning etc.)
List of associated devices
O
List of associated devices (e.g. haptic device, joy stick) required along with UE in order to provide service to the user. It includes device type.
Energy type
O
Indicates what energy type is supported by the EAS, e.g. non-renewable energy, renewable energy.
NOTE 1: Since the EASID of the EAS identifies the type of the application (e.g. SA6Video, SA6Game etc) as described in clause 7.2.4, "General context holding time duration" determined by EAS can depend on the EASID (type of the application).
NOTE 2: This IE may be provided when only bundle ID is provided, and the bundle type indicates the proxy bundle.
NOTE 3: At least one of the IEs shall be present if EAS bundle information is provided.
NOTE 4: For edge node sharing scenario, in order to restrict the access to the subscriber of the partner operator, this IE should only include MNO information of the leading operator.
NOTE: The EAS Transport layer service continuity support can be used in EAS discovery, e.g. as described in 3GPP TS 23.433 [26] for SEALDD server acting as EAS, which can further support the EAS IP replacement function.
Editor’s Note: How EES gets the information of energy type supported by an EAS is FFS.
6.A3.2 Architecture impacts
Editor’s Note: The architecture impacts of the solution is FFS.
6.A3.3 Solution evaluation
Editor’s Note: The evaluation of the solution is FFS.
6.x4 Solution #x4: Support of AIMLE client selection based on energy consumption
6.x4.1 Solution Description
This solution addresses Key Issue #4 – open issue #3 on how to use energy consumption information for AIMLE client selection. The solution proposes enhancements to the ML model information management procedure, and to procedures involving AIMLE client selection, to enable the storage and use of energy consumption information for AIMLE client selection.
The enhancements enable an AIMLE client to provide energy consumption capabilities during registration. Energy consumption capabilities include the maximum energy budget for performing AIML operations, and the VAL UE’s power profile. The VAL UE power profile indicates the degree of energy consumption of a VAL UE for performing AI/ML operations.
The enhancements also enable an ML model provider to include energy consumption information during ML model storage. The energy consumption information includes expected energy consumption values for performing AIML operations using an ML model. The expected energy consumption values are provided per power profile.
Both the AIMLE energy budget and the ML model energy consumption information are used for AIMLE client selection (e.g., request or subscription). During AIMLE client selection, the AIMLE server receives energy consumption requirements from a requestor. The energy consumption requirements include an indication to consider energy consumption during AIMLE client selection, and the maximum total energy consumption that is acceptable to the requestor. The AIMLE server uses the energy budget and energy consumption information to identify and select the ML models and AIMLE clients that meet the energy consumption requirements of the requestor.
6.x4.1.1 Impact to ML model information management
The ML model information management procedure and information flows in 3GPP TS 23.482 [r2348210] are enhanced (highlighted in bold italics) as follows.
|
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.3.2 Architecture impacts
| Editor’s Note: The architecture impacts of the solution is FFS.
|
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.3.3 Solution evaluation
| Editor’s Note: The evaluation of the solution is FFS.
6.4 Solution #4: Support of AIMLE client selection based on energy consumption
|
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.4.1 Solution Description
| This solution addresses Key Issue #4 – open issue #3 on how to use energy consumption information for AIMLE client selection. The solution proposes enhancements to the ML model information management procedure, and to procedures involving AIMLE client selection, to enable the storage and use of energy consumption information for AIMLE client selection.
The enhancements enable an AIMLE client to provide energy consumption capabilities during registration. Energy consumption capabilities include the maximum energy budget for performing AIML operations, and the VAL UE’s power profile. The VAL UE power profile indicates the degree of energy consumption of a VAL UE for performing AI/ML operations.
The enhancements also enable an ML model provider to include energy consumption information during ML model storage. The energy consumption information includes expected energy consumption values for performing AIML operations using an ML model. The expected energy consumption values are provided per power profile.
Both the AIMLE energy budget and the ML model energy consumption information are used for AIMLE client selection (e.g., request or subscription). During AIMLE client selection, the AIMLE server receives energy consumption requirements from a requestor. The energy consumption requirements include an indication to consider energy consumption during AIMLE client selection, and the maximum total energy consumption that is acceptable to the requestor. The AIMLE server uses the energy budget and energy consumption information to identify and select the ML models and AIMLE clients that meet the energy consumption requirements of the requestor.
|
eb1343f2cdb3d270d65fac7ddb0d0638 | 23.700-44 | 6.4.1.1 Impact to ML model information management
| The ML model information management procedure and information flows in 3GPP TS 23.482 [10] are enhanced (highlighted in bold italics) as follows.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.