Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.558  Word version:  17.4.0

Top   Top   Up   Prev   Next
0…   5…   6…   7…   8…   8.4…   8.5…   8.6…   8.6.3…   8.6.6…   8.7…   8.8…   8.8.3…   8.8.4…   8.9…   A…   B…   C…   D…

 

8  Procedures and information flowsp. 34

8.1  Generalp. 34

This clause provides procedures and information flows necessary for enabling edge application including information elements used in the procedures.

8.2  Common Information Elementsp. 34

8.2.1  Generalp. 34

This clause provides descriptions for Information Elements which are commonly used in several procedures.

8.2.2  AC Profilep. 34

An AC Profile includes information about AC used to determine services and service characteristics required.
Information element Status Description
ACIDMIdentity of the AC.
AC TypeOThe category or type of AC (e.g. V2X). This is an implementation specific value.
Preferred ECSP listOWhen 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 ScheduleOThe expected operation schedule of the AC (e.g. time windows)
Expected AC Geographical Service AreaOThe 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 SupportOIndicates 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.
List of EASsOList of EAS that serve the AC along with the service KPIs required by the AC
> EASIDMIdentifier of the EAS
> Expected AC Service KPIsO 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 KPIsO Minimum KPIs required in order for ACs to receive meaningful services from the EAS, as described in Table 8.2.3-1
Up

8.2.3  AC Service KPIsp. 34

AC Service KPIs provide information about service characteristics required by the ACs.
Information element Status Description
Connection bandwidthOThe required connection bandwidth in Kbit/s for the application.
Request rateOThe request rate to be generated by the AC.
Response timeOResponse time (NOTE) required for the server servicing the requests.
AvailabilityOPercentage of time the server is required to be available for the AC's use.
ComputeOThe compute resources required by the AC.
Graphical ComputeOThe graphical compute resources required by the AC.
MemoryOThe memory resources required by the AC.
StorageOThe 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.
Up

8.2.4  EAS Profilep. 35

Information element Status Description
EASIDMThe identifier of the EAS
EAS EndpointMEndpoint 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)OIdentifies the AC(s) that can be served by the EAS
EAS Provider IdentifierOThe identifier of the ASP that provides the EAS.
EAS TypeOThe category or type of EAS (e.g. V2X)
EAS descriptionOHuman-readable description of the EAS
EAS ScheduleOThe availability schedule of the EAS (e.g. time windows)
EAS Geographical Service AreaOThe geographical service area that the EAS serves. ACs in UEs that are located outside that area shall not be served.
EAS Topological Service AreaO 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 KPIsO Service characteristics provided by EAS, detailed in Table 8.2.5-1
EAS service permission levelOLevel of service permissions e.g. trial, gold-class supported by the EAS
EAS Feature(s)OService features e.g. single vs. multi-player gaming service supported by the EAS
EAS Service continuity supportOIndicates if the EAS supports service continuity or not. This IE also indicates which ACR scenarios are supported by the EAS.
List of EAS DNAI(s)ODNAI(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 requirementsOThe N6 traffic routing information and/or routing profile ID corresponding to each EAS DNAI.
EAS Availability Reporting PeriodOThe 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 StatusOThe status of the EAS (e.g. enabled, disabled, etc.)
Up

8.2.5  EAS Service KPIsp. 35

EAS Service KPIs provide information about service characteristics provided by the EAS
Information element Status Description
Maximum Request rateOMaximum request rate from the AC supported by the server.
Maximum Response timeOThe maximum response time advertised for the AC's service requests.
AvailabilityOAdvertised percentage of time the server is available for the AC's use.
Available ComputeOThe maximum compute resource available for the AC.
Available Graphical ComputeOThe maximum graphical compute resource available for the AC.
Available MemoryOThe maximum memory resource available for the AC.
Available StorageOThe maximum storage resource available for the AC.
Connection BandwidthOThe 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.
Up

8.2.6  EES Profilep. 36

The EES profile includes information about the EES and the services it provides.
Information element Status Description
EESIDMThe identifier of the EES
EES EndpointMEndpoint 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.
EASIDsMList of EASIDs registered with the EES.
EEC registration configurationMIndicates whether the EEC is required to register on the EES to use edge services or not.
EES Provider IdentifierOThe identifier of the ECSP that provides the EES Provider.
EES Topological Service AreaO 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 AreaOThe area being served by the EES in Geographical values (as specified in clause 7.3.3.3)
List of EES DNAI(s)ODNAI(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 supportOIndicates if the EES supports service continuity or not. This IE also indicates which ACR scenarios are supported by the EES.
Up

8.2.7  Topological Service Areap. 36

The following formats may be used for expressing a Topological Service Area:
Information element Status Description
Cell IDs (NOTE)OThe list of cell IDs defining the Topological Service Area
TAIs (NOTE)OThe list of Tracking Area IDs defining the Topological Service Area
PLMN IDs (NOTE)OThe 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.
Up

8.2.8  EEC Contextp. 37

The EEC Context includes information about an EEC for receiving edge enabler services.
Information element Status Description
EEC IDMUnique identifier of the EEC.
EEC Context IDMIdentifier assigned to the EEC Context
Source EES EndpointMThe endpoint address (e.g., URI, IP address) of the EES that provided EEC context ID.
UE IdentifierOThe identifier of the hosting UE (i.e., GPSI or identity token)
List of EDGE-1 subscriptionsOList of subscriptions IDs for capability exposure to the EEC ID (NOTE).
UE locationOLatest UE location of the UE hosting the EEC which was available at the EES.
List of AC ProfilesO Information about the ACs as described in Table 8.2.2-1.
List of Service Session ContextsOList 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 ContextM 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 IDMIdentifier of the EAS providing the application services
EAS EndpointMEndpoint information of the EAS.
AC IDOIdentifier of the AC ID for which the service session is provided, if determined.
Up

8.2.9  Geographical Service Areap. 37

The following formats may be used for expressing a Geographical Service Area:
Information element Status Description
Geographical Area DescriptionOA shape defined in TS 23.032
Civic LocationOAn area identified by a civic location element, e.g. building, park, arena, civic address or ZIP code.
Up

8.3  ECS Discovery and Service provisioningp. 38

8.3.1  Generalp. 38

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.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.3.1-1: Overview of Service provisioning
Figure 8.3.1-1: Overview of Service provisioning
(⇒ copy of original 3GPP image)
Up
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:
  1. 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.
  2. 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.
Up

8.3.2  ECS Discoveryp. 40

8.3.2.1  Generalp. 40

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.
It may be possible to provide the ECS configuration information to the EEC from the 5GC if the UE has the capability to deliver the ECS configuration information to the EEC on the UE.
If the ECS configuration information is provided by 5GC and available at the EEC, the EEC shall use the information for the initial provisioning request. Otherwise, the EEC shall use pre-configured ECS address for the initial provisioning if ECS configuration information is preconfigured with the EEC.
Table 8.3.2.1-1 describes the information elements of ECS configuration information for an ECS.
Information element Status Description
ECS addressMEndpoint information of ECS (e.g. URI, FQDN, IP address)
ECSP IdentifierOThe identifier of the ECSP (e.g., the MNO or a 3rd party service provider) that provides the ECS.
Spatial Validity ConditionsOSpatial 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.
Up

8.3.2.2  Proceduresp. 40

8.3.2.2.1  Generalp. 40
There is no additional information about procedures for ECS Discovery.

8.3.2.3  Information flowsp. 40

8.3.2.3.1  Generalp. 40
There is no additional information about information flows for ECS Discovery

8.3.2.4  APIsp. 40

8.3.2.4.1  Generalp. 40
There is no additional information about APIs for ECS Discovery

8.3.3  Service provisioningp. 41

8.3.3.1  Generalp. 41

The following clauses specify procedures, information flows and APIs for service provisioning.

8.3.3.2  Proceduresp. 41

8.3.3.2.1  Generalp. 41
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 modelp. 41
Figure 8.3.3.2.2-1 illustrates service provisioning procedure based on request/response model.
Pre-conditions:
  1. The EEC has been pre-configured or has discovered the address (e.g. URI) of the ECS;
  2. The EEC has been authorized to communicate with the ECS;
  3. The UE Identifier is either preconfigured or resulted from a successful authorization; and
  4. The ECS is configured with ECSP's policy for service provisioning.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.3.3.2.2-1: Service provisioning - Request/Response
Up
Step 1.
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:
  • 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 also determines other information that needs to be provisioned, e.g. identification of the EDN, EDN service area, EES endpoints.
Step 3.
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.
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.
Up
8.3.3.2.3  Subscribe-notify modelp. 42
8.3.3.2.3.1  Generalp. 42
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.
Up
8.3.3.2.3.2  Subscribep. 42
Figure 8.3.3.2.3.2-1 illustrates the service provisioning subscription procedure between the EEC and the ECS.
Pre-conditions:
  1. The EEC has been pre-configured or has discovered the address (e.g. URI) of the ECS;
  2. The EEC has been authorized to communicate with the ECS as specified in clause 8.11;
  3. The UE Identifier is either preconfigured or resulted from a successful authorization;
  4. The ECS is configured with ECSP's policy for service provisioning; and
  5. The EEC has optionally acquired a Notification Target Address to be used in its subscriptions to notifications.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.3.3.2.3.2-1: Service provisioning subscription
Up
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.
Up
8.3.3.2.3.3  Notifyp. 44
Figure 8.3.3.2.3.3-1 illustrates the service provisioning notification procedure between the EEC and the ECS.
Pre-conditions:
  1. The EEC has subscribed with the ECS for the provisioning information as specified in clause 8.3.3.2.3.2.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.3.3.2.3.3-1: Service provisioning notification
Up
Step 1.
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:
  • 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 also determines other information that needs to be provisioned, e.g. identification of the EDN, EDN service area, EES endpoints.
Step 2.
The ECS sends a provisioning notification to the EEC with the list of EDN configuration information determined in 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.
Up
8.3.3.2.3.4  Subscription updatep. 44
Figure 8.3.3.2.3.4-1 illustrates the service provisioning subscription update procedure between the EEC and the ECS.
Pre-conditions:
  1. The EEC has subscribed with the ECS for the provisioning information as specified in clause 8.3.3.2.3.2.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.3.3.2.3.4-1: Service provisioning subscription update
Up
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.
Up
8.3.3.2.3.5  Unsubscribep. 45
Figure 8.3.3.2.3.5-1 illustrates the service provisioning unsubscribe procedure between the EEC and the ECS.
Pre-conditions:
  1. The EEC has subscribed with the ECS for the provisioning information as specified in clause 8.3.3.2.3.2.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.3.3.2.3.5-1: Service provisioning unsubscribe
Up
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.
Up

8.3.3.3  Information flowsp. 46

8.3.3.3.1  Generalp. 46
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 requestp. 46
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
EECIDMUnique identifier of the EEC.
Security credentialsMSecurity 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 SupportOIndicates if the EEC supports service continuity or not. The IE also indicates which ACR scenarios are supported by the EEC.
UE IdentifierOThe identifier of the UE (i.e. GPSI or identity token)
Connectivity informationOList of connectivity information for the UE, e.g. PLMN ID, SSID.
UE locationOThe location information of the UE. The UE location is described in clause 7.3.2.
Up
8.3.3.3.3  Service provisioning responsep. 47
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 responseOIndicates that the service provisioning request was successful.
> List of EDN configuration informationM List of EDN configuration information as defined in Table 8.3.3.3.3-2.
Failure responseOIndicates that the service provisioning request failed.
> CauseOIndicates the cause of service provisioning request failure.
Information element Status Description
EDN connection information (NOTE 1)MInformation required by the UE to establish connection with the EDN.
> DNN/APNMData Network Name/Access Point Name
> S-NSSAIONetwork Slice information
> EDN Topological Service AreaO 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 EESsMList of EESs of the EDN.
> EESIDMThe identifier of the EES
> EES EndpointMThe endpoint address (e.g. URI, IP address) of the EES
> EASIDs (NOTE 2)OList of EASIDs registered with the EES.
> EES Provider identifierOThe identifier of the EES Provider (such as ECSP)
> EES Topological Service AreaO 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 AreaOThe area being served by the EES in Geographical values (as specified in clause 7.3.3.3)
> List of EES DNAI(s)ODNAI(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 supportOIndicates if the EES supports service continuity or not. This IE also indicates which ACR scenarios are supported by the EES.
> EEC registration configurationMIndicates whether the EEC is required to register on the EES to use edge services or not.
LifetimeOTime 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).
Up
8.3.3.3.4  Service provisioning subscription requestp. 48
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
EECIDMUnique identifier of the EEC.
Security credentialsMSecurity credentials resulting from a successful authorization for the edge computing service.
Notification Target AddressOThe 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 SupportOIndicates if the EEC supports service continuity or not. The IE also indicates which ACR scenarios are supported by the EEC.
UE IdentifierOThe identifier of the UE (i.e. GPSI or identity token)
Connectivity informationOList of connectivity information for the UE, e.g. PLMN ID, SSID.
Proposed expiration timeOProposed expiration time for the subscription
Up
8.3.3.3.5  Service provisioning subscription responsep. 49
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 responseOIndicates that the subscription request was successful.
> Subscription IDMSubscription identifier corresponding to the subscription.
> Expiration timeOIndicates the expiration time of the subscription. To maintain an active subscription, a subscription update is required before the expiration time.
Failure responseOIndicates that the subscription request failed.
> CauseOIndicates the cause of subscription request failure
Up
8.3.3.3.6  Service provisioning notificationp. 49
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 IDMSubscription identifier corresponding to the subscription stored in the ECS for the request
List of EDN configuration informationM List of EDN configuration information as defined in Table 8.3.3.3.3-2.
Up
8.3.3.3.7  Service provisioning subscription update requestp. 49
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 IDMSubscription identifier corresponding to the subscription to be updated
Security credentialsMSecurity credentials resulting from a successful authorization for the edge computing service.
Connectivity informationOList of connectivity information for the UE, e.g. PLMN ID, SSID.
Proposed expiration timeOProposed 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 SupportOIndicates if the EEC supports service continuity or not. The IE also indicates which ACR scenarios are supported by the EEC.
Up
8.3.3.3.8  Service provisioning subscription update responsep. 50
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 responseOIndicates that the subscription update request was successful.
> Expiration timeOIndicates the expiration time of the updated subscription. To maintain an active subscription, a subscription update is required before the expiration time.
Failure responseOIndicates that the subscription update request failed.
> CauseOIndicates the cause of subscription update request failure
Up
8.3.3.3.9  Service provisioning unsubscribe requestp. 50
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 IDMSubscription identifier corresponding to the subscription stored in the ECS
Security credentialsMSecurity credentials of the EEC
Up
8.3.3.3.10  Service provisioning unsubscribe responsep. 50
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 responseOIndicates that the unsubscribe request was successful.
Failure responseOIndicates that the unsubscribe request failed.
> CauseOIndicates the cause of unsubscribe request failure
Up

8.3.3.4  APIsp. 51

8.3.3.4.1  Generalp. 51
Table 8.3.3.4.1-1 illustrates the API for service provisioning.
API Name API Operations Operation Semantics Consumer(s)
Eecs_ServiceProvisioningRequestRequest/ResponseEEC
SubscribeSubscribe/NotifyEEC
Notify
UpdateSubscription
Unsubscribe
Up
8.3.3.4.2  Eecs_ServiceProvisioning_Request operationp. 51
API operation name:
Eecs_ServiceProvisioning_Request
Description:
The consumer requests for one time service provisioning information.
Inputs:
Outputs:
See clause 8.3.3.2.2 for details of usage of this operation.
8.3.3.4.3  Eecs_ServiceProvisioning_Subscribe operationp. 51
API operation name:
Eecs_ServiceProvisioning_Subscribe
Description:
The consumer subscribes for service provisioning information.
Inputs:
Outputs:
See clause 8.3.3.2.3.2 for details of usage of this operation.
8.3.3.4.4  Eecs_ServiceProvisioning_Notify operationp. 51
API operation name:
Eecs_ServiceProvisioning_Notify
Description:
The consumer is notified with service provisioning information.
Inputs:
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 operationp. 51
API operation name:
Eecs_ServiceProvisioning_UpdateSubscription
Description:
The consumer updates an existing subscription for service provisioning information.
Inputs:
Outputs:
See clause 8.3.3.2.3.4 for details of usage of this operation.
8.3.3.4.6  Eecs_ServiceProvisioning_Unsubscribe operationp. 52
API operation name:
Eecs_ServiceProvisioning_Unsubscribe
Description:
The consumer cancels an existing subscription for service provisioning information.
Inputs:
Outputs:
See clause 8.3.3.2.3.5 for details of usage of this operation.

Up   Top   ToC