Content for TS 23.558 Word version: 18.1.0
8 Procedures and information flows
8.1 General
8.2 Common Information Elements
8.3 ECS Discovery and Service provisioning
8.3.1 General
8.3.2 ECS Discovery
8.3.3 Service provisioning
...
...
8 Procedures and information flows p. 36
8.1 General p. 36
This clause provides procedures and information flows necessary for enabling edge application including information elements used in the procedures.
8.2 Common Information Elements p. 36
8.2.1 General p. 36
This clause provides descriptions for Information Elements which are commonly used in several procedures.
8.2.2 AC Profile p. 36
An AC Profile includes information about AC used to determine services and service characteristics required.
| Information element | Status | Description |
|---|---|---|
| ACID | M | Identity of the AC. |
| AC Type | O | The category or type of AC (e.g. V2X). This is an implementation specific value. |
| Preferred ECSP list | O | When used in a service provisioning request, this IE indicates to the ECS which ECSPs are preferred for the AC. The ECS may use this information in the selection of EESs. |
| AC Schedule | O | The expected operation schedule of the AC (e.g. time windows) |
| Expected AC Geographical Service Area | O | The expected location(s) (e.g. route) of the hosting UE during the AC's operation schedule. This geographic information can express a geographic point, polygon, route, signalling map, or waypoint set. |
| AC Service Continuity Support | O | Indicates if service continuity support is required or not for the application. The IE also indicates which ACR scenarios are supported by the AC and which of these are preferred by the AC. |
| Simultaneous EAS connectivity information in service continuity | O | Indicates if simultaneous EAS connectivity is needed and the inactive time guidance for keeping connectivity towards the S-EAS. |
| List of EASs | O | List of EAS that serve the AC along with the service KPIs required by the AC |
| > EASID | M | Identifier of the EAS |
| > Expected AC Service KPIs | O | KPIs expected in order for ACs to receive currently required services from the EAS, as described in Table 8.2.3-1 |
| > Minimum required AC Service KPIs | O | Minimum KPIs required in order for ACs to receive meaningful services from the EAS, as described in Table 8.2.3-1 |
8.2.3 AC Service KPIs p. 37
AC Service KPIs provide information about service characteristics required by the ACs.
| Information element | Status | Description |
|---|---|---|
| Connection bandwidth | O | The required connection bandwidth in Kbit/s for the application. |
| Request rate | O | The request rate to be generated by the AC. |
| Response time | O | Response time (NOTE) required for the server servicing the requests. |
| Availability | O | Percentage of time the server is required to be available for the AC's use. |
| Compute | O | The compute resources required by the AC. |
| Graphical Compute | O | The graphical compute resources required by the AC. |
| Memory | O | The memory resources required by the AC. |
| Storage | O | The storage resources required by the AC. |
|
NOTE:
The response time includes the round-trip time of the request and response packet, the processing time at the server and the time required by the server to consume 3GPP Core Network capabilities, if any.
|
||
8.2.4 EAS Profile p. 38
| 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. |
| 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. |
| EAS Type | O | The category or type of EAS (e.g. V2X) |
| 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 Service continuity support | O | Indicates if the EAS supports service continuity or not. This IE also indicates which ACR scenarios are supported by the EAS. |
| General context holding time duration (NOTE) | 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 TS 23.501. 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, etc.) |
|
NOTE:
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).
|
||
8.2.5 EAS Service KPIs p. 38
EAS Service KPIs provide information about service characteristics provided by the EAS
| Information element | Status | Description |
|---|---|---|
| Maximum Request rate | O | Maximum request rate from the AC supported by the server. |
| Maximum Response time | O | The maximum response time advertised for the AC's service requests. |
| Availability | O | Advertised percentage of time the server is available for the AC's use. |
| Available Compute | O | The maximum compute resource available for the AC. |
| Available Graphical Compute | O | The maximum graphical compute resource available for the AC. |
| Available Memory | O | The maximum memory resource available for the AC. |
| Available Storage | O | The maximum storage resource available for the AC. |
| Connection Bandwidth | O | The connection bandwidth in Kbit/s advertised for the AC's use. |
|
NOTE:
The maximum response time includes the round-trip time of the request and response packet, the processing time at the server and the time required by the server to consume 3GPP Core Network capabilities, if any.
|
||
8.2.6 EES Profile p. 39
The EES profile includes information about the EES and the services it provides.
| Information element | Status | Description |
|---|---|---|
| EESID | M | The identifier of the EES |
| EES Endpoint | M | Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the EES. This information is provided to the EEC to connect to the EES. |
| EASIDs | M | List of EASIDs registered with the EES. |
| instantiable EAS information | O | The EAS instantiation status per EASID (e.g. instantiated, instantiable but not be instantiated yet) |
| EEC registration configuration | M | Indicates whether the EEC is required to register on the EES to use edge services or not. |
| EES Provider Identifier | O | The identifier of the ECSP that provides the EES Provider. |
| EES Topological Service Area | O | The EES serves UEs that are connected to the Core Network from one of the cells included in this service area. EECs in UEs that are located outside this area shall not be served. See possible formats in Table 8.2.7-1. |
| EES Geographical Service Area | O | The area being served by the EES in Geographical values (as specified in clause 7.3.3.3) |
| List of EES DNAI(s) | O | DNAI(s) associated with the EES. This IE is used as Potential Locations of Applications in clause 5.6.7 of TS 23.501. It is a subset of the DNAI(s) associated with the EDN, where the EES resides. |
| EES Service continuity support | O | Indicates if the EES supports service continuity or not. This IE also indicates which ACR scenarios are supported by the EES. |
8.2.7 Topological Service Area p. 39
The following formats may be used for expressing a Topological Service Area:
| Information element | Status | Description |
|---|---|---|
| Cell IDs (NOTE) | O | The list of cell IDs defining the Topological Service Area |
| TAIs (NOTE) | O | The list of Tracking Area IDs defining the Topological Service Area |
| PLMN IDs (NOTE) | O | The list of PLMN IDs defining the Topological Service Area |
|
NOTE:
A combination of these information elements can be used to define the Topological Service Area. Combinations should not have duplicate or overlapping information for the same Topological Service Area.
|
||
8.2.8 EEC Context p. 40
The EEC Context includes information about an EEC for receiving edge enabler services.
| Information element | Status | Description |
|---|---|---|
| EEC ID | M | Unique identifier of the EEC. |
| EEC Context ID | M | Identifier assigned to the EEC Context |
| Source EES Endpoint | M | The endpoint address (e.g., URI, IP address) of the EES that provided EEC context ID. |
| UE Identifier | O | The identifier of the hosting UE (i.e., GPSI or identity token) |
| List of EDGE-1 subscriptions | O | List of subscriptions IDs for capability exposure to the EEC ID (NOTE). |
| UE location | O | Latest UE location of the UE hosting the EEC which was available at the EES. |
| List of AC Profiles | O | Information about the ACs as described in Table 8.2.2-1. |
| List of Service Session Contexts | O | List of associated Service Session Context IEs. Each Service Session Context includes information maintained by the EES for the services (involving UE related resources) received from an EAS registered to the EES. |
| > Service Session Context | M | Service Session Context is described in Table 8.2.8-2 |
|
NOTE:
The corresponding EDGE-1 subscription information may include 3GPP CN subscription information such as subscription correlation ID
|
||
| Information element | Status | Description |
|---|---|---|
| EAS ID | M | Identifier of the EAS providing the application services |
| EAS Endpoint | M | Endpoint information of the EAS. |
| AC ID | O | Identifier of the AC ID for which the service session is provided, if determined. |
8.2.9 Geographical Service Area p. 40
The following formats may be used for expressing a Geographical Service Area:
| Information element | Status | Description |
|---|---|---|
| Geographical Area Description | O | A shape defined in TS 23.032 |
| Civic Location | O | An area identified by a civic location element, e.g. building, park, arena, civic address or ZIP code. |
8.3 ECS Discovery and Service provisioning p. 41
8.3.1 General p. 41
Service provisioning allows configuring the EEC with information about available Edge Computing services, based on the hosting UEs location, service requirements, service preferences and connectivity. This configuration includes the necessary address information for the EEC to establish connection with the EES(s).
If the ECS deployed by MNO is contracted with one or more ECSP(s), the ECS provides EES configuration information of MNO owned and ECSP owned EESs via MNO ECS as described in clause 8.3.3.3.3.
If the ECS is deployed by a non-MNO ECSP, the ECS endpoint address may be configured with the EEC. An EEC that is aware of multiple ECSP's ECS endpoint addresses may perform the service provisioning procedure per ECS of each ECSP multiple times.
Figure 8.3.1-1 illustrates an overview of service provisioning. Service provisioning procedures support the following models:
- Request/Response model; and
- Subscribe/Notify model.
The UE is initially provisioned from the ECS with the configurations required to connect to the EDN. Once provisioned, the EEC of the UE registers with the selected EES(s) from the list of provisioned EES(s) it received from the ECS(s) ), if the EEC registration configuration in EES profile indicates that EEC registration is required. The UE further consumes the edge computing services and performs various operations such as EAS discovery, Edge application communications, ACR, etc. While the UE is consuming the edge computing services, there may be several triggers which may cause service provisioning to be triggered by the UE or by the ECS.
The triggers for service provisioning are classified as:
-
Triggers at UE - Some examples are:
- AC related updates available at the EEC due to AC installation/re-installation, AC requesting application server access (e.g. via internet browser);
- EEC supporting one or more ACs may be updated due to EEC re-installation; and
- Lifetime of EDN Configuration Information is expired or the EEC detects that the UE moves out of EDN Service Area in the EDN Configuration Information.
-
Triggers at ECS - Some examples are:
- EES updates received due to EAS installation/re-installation/re-location; and
- ECS receives the EDN/DNAI change notification of the UE from 5GC when the ECS subscribes to the user plane path management events as specified in clause 8.10.2.
8.3.2 ECS Discovery p. 43
8.3.2.1 General p. 43
ECS configuration information consists of one or more endpoint information (e.g. URI(s), FQDN(s), IP address(es)) of ECS(s), and optionally the corresponding ECS Provider Identifier. ECS configuration information can be
- pre-configured with the EEC;
- configured by an edge-aware AC;
- configured by the user;
- provisioned by MNO through 5GC procedure if the UE has the capability to deliver the ECS configuration information to the EEC on the UE (see TS 23.548, clause 6.5.2); or
- derived from HPLMN identifier for non-roaming scenario or from VPLMN identifier for roaming scenario.
| Information element | Status | Description |
|---|---|---|
| ECS address | M | Endpoint information of ECS (e.g. URI, FQDN, IP address) |
| ECSP Identifier | O | The identifier of the ECSP (e.g., the MNO or a 3rd party service provider) that provides the ECS. |
| Spatial Validity Conditions | O | Spatial validity condition, as described in TS 23.548. |
|
NOTE:
This IE shall be included when the ECS configuration information is provisioned by the MNO through the 5GC procedure.
|
||
8.3.2.2 Procedures p. 43
8.3.2.2.1 General p. 43
There is no additional information about procedures for ECS Discovery.
8.3.2.3 Information flows p. 43
8.3.2.3.1 General p. 43
There is no additional information about information flows for ECS Discovery
8.3.2.4 APIs p. 44
8.3.2.4.1 General p. 44
There is no additional information about APIs for ECS Discovery
8.3.3 Service provisioning p. 44
8.3.3.1 General p. 44
The following clauses specify procedures, information flows and APIs for service provisioning.
8.3.3.2 Procedures p. 44
8.3.3.2.1 General p. 44
Following procedures are supported for service provisioning:
- Request-response procedure;
-
Subscribe-notify procedures, including:
- Subscription procedure;
- Notification procedure;
- Subscription update procedure; and
- Unsubscribe procedure.
8.3.3.2.2 Request-response model p. 44
Figure 8.3.3.2.2-1 illustrates service provisioning procedure based on request/response model.
Pre-conditions:
- The EEC has been pre-configured or has discovered the address (e.g. URI) of the ECS;
- The EEC has been authorized to communicate with the ECS;
- The UE Identifier is either preconfigured or resulted from a successful authorization; and
- The ECS is configured with ECSP's policy for service provisioning.
Step 1.
If the EDN configuration information includes an LADN DNN as an identifier for the EDN, the EEC considers the LADN as the EDN. Therefore, the service area of EDN is the LADN Service Area which can be discovered using the UE Registration Procedure.
The EEC may cache the service provisioning information (e.g. EES endpoint) for subsequent use and avoid the need to repeat step 1. If the Lifetime IE is included in the Service provisioning response, then the EEC may cache and reuse the Service provisioning information only for the duration specified by the Lifetime IE, without the need to repeat step 1.
If the ECS provided information regarding the service continuity support of individual EESs, the EEC may take this information into account when selecting an EES for EEC registration, EAS discovery or T-EAS discovery, respectively.
When the EES profile(s) include instantiable EAS information, the EEC can select one EES for EAS discovery to mitigate the waste of EDN resources considering the instantiable EAS information, if the EAS instantiation status corresponding to the EASID requested by AC/EEC is instantiable but not yet instantiated.
The EEC sends a service provisioning request to the ECS. The service provisioning request includes the security credentials of the EEC received during EEC authorization procedure and may include the UE identifier such as GPSI, connectivity information, UE location and AC profile(s) information.
Step 2.
Upon receiving the request, the ECS performs an authorization check to verify whether the EEC has authorization to perform the operation. The ECS may utilize the capabilities (e.g. UE location) of the 3GPP core network as specified in clause 8.10.2. If AC profile(s) are provided by the EEC, the ECS identifies the EES(s) based on the provided AC profile(s) and the UE location. When AC profiles(s) are not provided, then:
Step 3.
- if available, the ECS identifies the EES(s) based on the UE-specific service information at the ECS and the UE location;
- ECS identifies the EES(s) by applying the ECSP policy (e.g. based only on the UE location);
If the processing of the request was successful, the ECS responds to the EEC's request with a service provisioning response which includes a list of EDN configuration information, e.g. identification of the EDN, EDN service area, and the required information (e.g. URI, IP address) for establishing a connection to the EES.
If the ECS is not provisioned with any EDN configuration information or is unable to determine the EES information using the inputs in service provisioning request, UE-specific service information at the ECS or the ECSP's policy, the ECS shall reject the service provisioning request and respond with an appropriate failure cause.
8.3.3.2.3 Subscribe-notify model p. 44
8.3.3.2.3.1 General p. 46
Clause 8.3.3.2.3.2 and clause 8.3.3.2.3.3 together illustrate the service provisioning procedure based on Subscribe/Notify model.
Clause 8.3.3.2.3.4 illustrates the service provisioning update procedure.
Clause 8.3.3.2.3.5 illustrates the service provisioning unsubscribe procedure.
8.3.3.2.3.2 Subscribe p. 46
Figure 8.3.3.2.3.2-1 illustrates the service provisioning subscription procedure between the EEC and the ECS.
Pre-conditions:
- The EEC has been pre-configured or has discovered the address (e.g. URI) of the ECS;
- The EEC has been authorized to communicate with the ECS as specified in clause 8.11;
- The UE Identifier is either preconfigured or resulted from a successful authorization;
- The ECS is configured with ECSP's policy for service provisioning; and
- The EEC has optionally acquired a Notification Target Address to be used in its subscriptions to notifications.
Step 1.
The EEC sends a service provisioning subscription request to the ECS. The service provisioning subscription request includes the security credentials of the EEC received during EEC authorization procedure and Notification Target Address (e.g. URL) and may include the UE identifier such as GPSI, connectivity information, proposed expiration time and AC Profile information.
Step 2.
Upon receiving the request, the ECS performs an authorization check to verify whether the EEC has authorization to perform the operation. If required, the ECS may utilize the capabilities (e.g. UE location or user plane management event notification service if available) of the 3GPP core network as specified in clause 8.10.2. If the request is authorized, the ECS creates and stores the subscription for provisioning.
Step 3.
If the processing of the request was successful, the ECS responds with a service provisioning subscription response, which includes the subscription identifier and may include the expiration time, indicating when the subscription will automatically expire. To maintain the subscription, the EEC shall send a Service provisioning subscription update request prior to the expiration time. If a Service provisioning subscription update request is not received prior to the expiration time, the ECS shall treat the EEC as implicitly unsubscribed.
If the ECS is unable to determine the EES information using the inputs in service provisioning subscription request, UE-specific service information at the ECS or the ECSP policy, the ECS shall reject the service provisioning subscription request and respond with an appropriate failure cause.
8.3.3.2.3.3 Notify p. 47
Figure 8.3.3.2.3.3-1 illustrates the service provisioning notification procedure between the EEC and the ECS.
Pre-conditions:
- The EEC has subscribed with the ECS for the provisioning information as specified in clause 8.3.3.2.3.2.
Step 1.
If the EDN configuration information in the service provisioning notification includes an LADN DNN as an identifier for the EDN, the EEC considers the LADN as the EDN. Therefore, the service area of EDN is the LADN Service Area, which can be discovered using the UE Registration Procedure.
If the ECS provided information regarding the service continuity support of individual EESs, the EEC may take this information into account when selecting an EES for EEC registration, EAS discovery or T-EAS discovery, respectively.
An event occurs at the ECS that satisfies trigger conditions for updating service provisioning of a subscribed EEC. If UE's location information is not available, the ECS may obtain the UE location by utilizing the capabilities of the 3GPP core network as specified in clause 8.10.2. If AC profile(s) were provided by the EEC during subscription creation, the ECS identifies the EES(s) based on the provided AC profile(s) and the UE location. If AC profiles(s) were not provided, then:
Step 2.
- if available, the ECS identifies the EES(s) based on the UE-specific service information at the ECS and the UE location;
- ECS identifies the EES(s) by applying the ECSP policy (e.g. based only on the UE location);
The ECS sends a provisioning notification to the EEC with the list of EDN configuration information determined in step 1.
8.3.3.2.3.4 Subscription update p. 48
Figure 8.3.3.2.3.4-1 illustrates the service provisioning subscription update procedure between the EEC and the ECS.
Pre-conditions:
- The EEC has subscribed with the ECS for the provisioning information as specified in clause 8.3.3.2.3.2.
Step 1.
The EEC sends a service provisioning subscription update request to the ECS. The service provisioning subscription update request includes the security credentials of the EEC received during EEC authorization procedure along with the subscription identifier and may include the UE identifier such as GPSI, connectivity information, proposed expiration time for the updated subscription and AC profile(s).
Step 2.
Upon receiving the request, the ECS performs an authorization check to verify whether the EEC has authorization to perform the operation. If required, the ECS may utilize the capabilities (e.g. UE location) of the 3GPP core network as specified in clause 8.10.2. If authorized, the ECS updates the stored subscription for provisioning as requested in step 1.
Step 3.
The ECS responds with a service provisioning subscription update response, which may include the expiration time, indicating when the updated subscription will automatically expire. To maintain the subscription, the EEC shall send a Service provisioning subscription update request prior to the expiration time. If a Service provisioning subscription update request is not received prior to the expiration time, the ECS shall treat the EEC as implicitly unsubscribed.
8.3.3.2.3.5 Unsubscribe p. 49
Figure 8.3.3.2.3.5-1 illustrates the service provisioning unsubscribe procedure between the EEC and the ECS.
Pre-conditions:
- The EEC has subscribed with the ECS for the provisioning information as specified in clause 8.3.3.2.3.2.
Step 1.
The EEC sends a service provisioning unsubscribe request to the ECS. The service provisioning unsubscribe request includes the security credentials of the EEC received during EEC authorization procedure along with the subscription identifier.
Step 2.
Upon receiving the request, the ECS performs an authorization check to verify whether the EEC has authorization to perform the operation. If authorized, the ECS cancels the subscription for provisioning as requested in step 1.
Step 3.
The ECS responds with a service provisioning unsubscribe response.
8.3.3.3 Information flows p. 50
8.3.3.3.1 General p. 50
The following information flows are specified for service provisioning:
- Service provisioning request and response;
- Service provisioning subscription request and response;
- Service provisioning notification;
- Service provisioning update request and response; and
- Service provisioning unsubscribe request and response.
8.3.3.3.2 Service provisioning request p. 50
Table 8.3.3.3.2-1 describes the information elements for service provisioning request from the EEC to the ECS.
| Information element | Status | Description |
|---|---|---|
| EECID | M | Unique identifier of the EEC. |
| Security credentials | M | Security credentials resulting from a successful authorization for the edge computing service. |
| AC Profile(s) | O | Information about services the EEC wants to connect to, as described in Table 8.2.2-1. |
| 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. |
| UE Identifier | O | The identifier of the UE (i.e. GPSI or identity token) |
| Connectivity information | O | List of connectivity information for the UE, e.g. PLMN ID, SSID. |
| UE location | O | The location information of the UE. The UE location is described in clause 7.3.2. |
8.3.3.3.3 Service provisioning response p. 51
Table 8.3.3.3.3-1 describes the information elements for service provisioning response from the ECS to the EEC.
| Information element | Status | Description |
|---|---|---|
| Successful response | O | Indicates that the service provisioning request was successful. |
| > List of EDN configuration information | M | List of EDN configuration information as defined in Table 8.3.3.3.3-2. |
| Failure response | O | Indicates that the service provisioning request failed. |
| > Cause | O | Indicates the cause of service provisioning request failure. |
| Information element | Status | Description |
|---|---|---|
| EDN connection information (NOTE 1) | M | Information required by the UE to establish connection with the EDN. |
| > DNN/APN | M | Data Network Name/Access Point Name |
| > S-NSSAI | O | Network Slice information |
| > EDN Topological Service Area | O | The EDN serves UEs that are connected to the Core Network from one of the cells included in this service area. See possible formats in Table 8.2.7-1. |
| List of EESs | M | List of EESs of the EDN. |
| > EESID | M | The identifier of the EES |
| > EES Endpoint | M | The endpoint address (e.g. URI, IP address) of the EES |
| > EASIDs (NOTE 2) | O | List of EASIDs registered with the EES. |
| > instantiable EAS information | O | The EAS instantiation status per EASID (e.g. instantiated, instantiable but not be instantiated yet) |
| > EES Provider identifier | O | The identifier of the EES Provider (such as ECSP) |
| > EES Topological Service Area | O | The EES serves UEs that are connected to the Core Network from one of the cells included in this service area. EECs in UEs that are located outside this area shall not be served. See possible formats in Table 8.2.7-1. |
| > EES Geographical Service Area | O | The area being served by the EES in Geographical values (as specified in clause 7.3.3.3) |
| > List of EES DNAI(s) | O | DNAI(s) associated with the EES/EAS. This IE is used as Potential Locations of Applications in clause 5.6.7 of TS 23.501. |
| > EES Service continuity support | O | Indicates if the EES supports service continuity or not. This IE also indicates which ACR scenarios are supported by the EES. |
| > EEC registration configuration | M | Indicates whether the EEC is required to register on the EES to use edge services or not. |
| > Security Credential | O | Indicates the security credential sent by the ECS. The security credential is used by EEC to communicate with the EES as specified in TS 33.558, clause 6.2. |
| Lifetime | O | Time duration for which the EDN configuration information is valid and supposed to be cached in the EEC. |
|
NOTE 1:
If the UE is provisioned or pre-configured with URSP rules by the HPLMN, the UE handles the precedence between EDN connection info and URSP rules as defined in TS 23.503, clause 6.1.2.2.1. EDN connection info is considered to be part of UE Local Configurations.
NOTE 2:
EAS information is limited to the EEC requested applications. If no AC profiles were present in the service provisioning request, the EAS information is subject to the ECSP policy (e.g. no EAS information or a subset of EAS information related to the EES).
|
||
8.3.3.3.4 Service provisioning subscription request p. 52
Table 8.3.3.3.4-1 describes the information elements for service provisioning subscription request from the EEC to the ECS.
| Information element | Status | Description |
|---|---|---|
| EECID | M | Unique identifier of the EEC. |
| Security credentials | M | Security credentials resulting from a successful authorization for the edge computing service. |
| Notification Target Address (see NOTE) | O | The Notification Target Address (e.g. URL) where the notifications destined for the EEC should be sent to. |
| AC profile(s) | O | Information about services the EEC wants to connect to, as described in Table 8.2.2-1. |
| 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. |
| UE Identifier | O | The identifier of the UE (i.e. GPSI or identity token) |
| Connectivity information | O | List of connectivity information for the UE, e.g. PLMN ID, SSID. |
| Proposed expiration time | O | Proposed expiration time for the subscription |
|
NOTE:
When SEAL NMS is used this IE is same as Callback URL in SEAL notification management service.
|
||
8.3.3.3.5 Service provisioning subscription response p. 53
Table 8.3.3.3.5-1 describes the information elements for service provisioning subscription response from the ECS to the EEC.
| Information element | Status | Description |
|---|---|---|
| Successful response | O | Indicates that the subscription request was successful. |
| > Subscription ID | M | Subscription identifier corresponding to the subscription. |
| > Expiration time | O | Indicates the expiration time of the subscription. To maintain an active subscription, a subscription update is required before the expiration time. |
| Failure response | O | Indicates that the subscription request failed. |
| > Cause | O | Indicates the cause of subscription request failure |
8.3.3.3.6 Service provisioning notification p. 53
Table 8.3.3.3.6-1 describes the information elements for service provisioning notification from the ECS to the EEC.
| Information element | Status | Description |
|---|---|---|
| Subscription ID | M | Subscription identifier corresponding to the subscription stored in the ECS for the request |
| List of EDN configuration information | M | List of EDN configuration information as defined in Table 8.3.3.3.3-2. |
8.3.3.3.7 Service provisioning subscription update request p. 53
Table 8.3.3.3.7-1 describes the information elements for service provisioning subscription update request from the EEC to the ECS.
| Information element | Status | Description |
|---|---|---|
| Subscription ID | M | Subscription identifier corresponding to the subscription to be updated |
| Security credentials | M | Security credentials resulting from a successful authorization for the edge computing service. |
| Connectivity information | O | List of connectivity information for the UE, e.g. PLMN ID, SSID. |
| Proposed expiration time | O | Proposed expiration time for the subscription |
| AC profile(s) | O | Information about services the EEC wants to connect to, as described in Table 8.2.2-1. |
| 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. |
8.3.3.3.8 Service provisioning subscription update response p. 54
Table 8.3.3.3.8-1 describes the information elements for service provisioning subscription update response from the ECS to the EEC.
| Information element | Status | Description |
|---|---|---|
| Successful response | O | Indicates that the subscription update request was successful. |
| > Expiration time | O | Indicates the expiration time of the updated subscription. To maintain an active subscription, a subscription update is required before the expiration time. |
| Failure response | O | Indicates that the subscription update request failed. |
| > Cause | O | Indicates the cause of subscription update request failure |
8.3.3.3.9 Service provisioning unsubscribe request p. 54
Table 8.3.3.3.9-1 describes the information elements for service provisioning unsubscribe request from the EEC to the ECS.
| Information element | Status | Description |
|---|---|---|
| Subscription ID | M | Subscription identifier corresponding to the subscription stored in the ECS |
| Security credentials | M | Security credentials of the EEC |
8.3.3.3.10 Service provisioning unsubscribe response p. 54
Table 8.3.3.3.10-1 describes the information elements for service provisioning unsubscribe response from the ECS to the EEC.
| Information element | Status | Description |
|---|---|---|
| Successful response | O | Indicates that the unsubscribe request was successful. |
| Failure response | O | Indicates that the unsubscribe request failed. |
| > Cause | O | Indicates the cause of unsubscribe request failure |
8.3.3.4 APIs p. 55
8.3.3.4.1 General p. 55
Table 8.3.3.4.1-1 illustrates the API for service provisioning.
| API Name | API Operations | Operation Semantics | Consumer(s) |
|---|---|---|---|
| Eecs_ | Request | Request/Response | EEC |
| Subscribe | Subscribe/Notify | EEC | |
| Notify | |||
| UpdateSubscription | |||
| Unsubscribe |
8.3.3.4.2 Eecs_ServiceProvisioning_Request operation p. 55
API operation name:
Eecs_ServiceProvisioning_Request
Description:
The consumer requests for one time service provisioning information.
Inputs:
See clause 8.3.3.3.2.
Outputs:
See clause 8.3.3.3.3.
See clause 8.3.3.2.2 for details of usage of this operation.
8.3.3.4.3 Eecs_ServiceProvisioning_Subscribe operation p. 55
API operation name:
Eecs_ServiceProvisioning_Subscribe
Description:
The consumer subscribes for service provisioning information.
Inputs:
See clause 8.3.3.3.4.
Outputs:
See clause 8.3.3.3.5.
See clause 8.3.3.2.3.2 for details of usage of this operation.
8.3.3.4.4 Eecs_ServiceProvisioning_Notify operation p. 55
API operation name:
Eecs_ServiceProvisioning_Notify
Description:
The consumer is notified with service provisioning information.
Inputs:
See clause 8.3.3.3.6.
Outputs:
None.
See clause 8.3.3.2.3.3 for details of usage of this operation.
8.3.3.4.5 Eecs_ServiceProvisioning_UpdateSubscription operation p. 55
API operation name:
Eecs_ServiceProvisioning_UpdateSubscription
Description:
The consumer updates an existing subscription for service provisioning information.
Inputs:
See clause 8.3.3.3.7.
Outputs:
See clause 8.3.3.3.8.
See clause 8.3.3.2.3.4 for details of usage of this operation.
8.3.3.4.6 Eecs_ServiceProvisioning_Unsubscribe operation p. 56
API operation name:
Eecs_ServiceProvisioning_Unsubscribe
Description:
The consumer cancels an existing subscription for service provisioning information.
Inputs:
See clause 8.3.3.3.9.
Outputs:
See clause 8.3.3.3.10.
See clause 8.3.3.2.3.5 for details of usage of this operation.
