8.3 ECS Discovery and Service provisioning

23.5583GPPArchitecture for enabling Edge ApplicationsRelease 18TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

8.3.1 General

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.

Figure 8.3.1-1: Overview of Service provisioning

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:

a. 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.

b. 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

8.3.2.1 General

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 3GPP TS 23.548 [20], clause 6.5.2); or

– derived from HPLMN identifier for non-roaming scenario or from VPLMN identifier for roaming scenario.

NOTE: How the ECS configuration information is configured to the EEC user, or pre-configuration is out of scope of the present specification.

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.

It may be possible to provide the ECS configuration information to the EEC from an edge-ware AC via EDGE-5 reference point within the UE if the AC is configured with the ECS configuration information and can communicate with the EEC. When the ECS configuration information is provided from an AC, the EEC uses the ECS configuration information for the initial service provisioning for the AC if there is no ECS configuration information is provided from the 5GC.

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.

NOTE: The ECS configuration information configured by an edge-aware AC is considered to be part of pre-configured ECS configuration information with the EEC for the AC.

Table 8.3.2.1-1 describes the information elements of ECS configuration information for an ECS.

Table 8.3.2.1-1: ECS configuration information per ECS

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 3GPP TS 23.548 [20]
NOTE: This IE shall be included when the ECS configuration information is provisioned by the MNO through the 5GC procedure.

Editor’s Note: Information Elements of ECS configuration information are FFS.

8.3.2.2 Procedures

8.3.2.2.1 General

There is no additional information about procedures for ECS Discovery.

8.3.2.3 Information flows

8.3.2.3.1 General

There is no additional information about information flows for ECS Discovery

8.3.2.4 APIs

8.3.2.4.1 General

There is no additional information about APIs for ECS Discovery

8.3.3 Service provisioning

8.3.3.1 General

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

8.3.3.2 Procedures

8.3.3.2.1 General

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

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.

NOTE 1: Details of ECSP’s policy are out of scope.

Figure 8.3.3.2.2-1: Service provisioning – Request/Response

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.

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);

NOTE 2: Details of the UE-specific service information and how it is available at the ECS is out of scope.

NOTE 3: Both steps are evaluated prior to sending a response.

The ECS also determines other information that needs to be provisioned, e.g. identification of the EDN, EDN service area, EES endpoints.

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.

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.

NOTE 4: If the service provisioning request fails, the EEC can resend the service provisioning request again, taking into account the received failure cause.

NOTE 5: Even after the EEC establishes a connection to the EES using information received in step 3, the EES can issue AF request to influence traffic routing from EEC to EES as specified in 3GPP TS 23.501 [2] clause 5.6.7.

NOTE 6: If the EAS instantiation fails based on the selected EES, the EEC may retry the EAS discovery request to another EES.8.3.3.2.3 Subscribe-notify model

8.3.3.2.3.1 General

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

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.

NOTE 1: Details of ECSP’s policy are out of scope.

NOTE 2: How the EEC acquires the notification target address or a notification channel URI to receive the notifications is out of scope of this release. The notification target address can terminate at the EEC (e.g. in an IoT device) if the deployment supports EEC reachability, or it can terminate at a push notification service. Details of the push notification service are out of scope of this release.

Figure 8.3.3.2.3.2-1: Service provisioning subscription

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.

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.

NOTE 3: The ECS can monitor the user plane path change for EDGE-1 traffic toward EES(s) by utilizing the user plane management event notification service specified in 3GPP TS 23.501 [2]. Based on target DNAI reported from 5GC the ECS can notify more suitable EES(s) to the EEC.

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.

NOTE 4: If the service provisioning subscription request fails, the EEC can resend the service provisioning subscription request again, taking into account the received failure cause.

8.3.3.2.3.3 Notify

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.

Figure 8.3.3.2.3.3-1: Service provisioning notification

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);

NOTE 1: Details of the UE-specific service information and how it is available at the ECS is out of scope.

NOTE 2: Both steps are evaluated prior to sending a response.

The ECS also determines other information that needs to be provisioned, e.g. identification of the EDN, EDN service area, EES endpoints.

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.

NOTE 3: Even after the EEC establishes a connection to the EES using information received in step 2, the EES can issue AF request to influence traffic routing from EEC to EES as specified in 3GPP TS 23.501 [2] clause 5.6.7.

8.3.3.2.3.4 Subscription update

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.

Figure 8.3.3.2.3.4-1: Service provisioning subscription update

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).

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.

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

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.

Figure 8.3.3.2.3.5-1: Service provisioning unsubscribe

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.

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.

3. The ECS responds with a service provisioning unsubscribe response.

8.3.3.3 Information flows

8.3.3.3.1 General

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

Table 8.3.3.3.2-1 describes the information elements for service provisioning request from the EEC to the ECS.

Table 8.3.3.3.2-1: Service provisioning request

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.

Editor’s Note: [SA3] Whether the EECID and the UE ID included in request of EDGE-1 & 4 interactions is part of the security credential is SA3’s responsibility.

8.3.3.3.3 Service provisioning response

Table 8.3.3.3.3-1 describes the information elements for service provisioning response from the ECS to the EEC.

Table 8.3.3.3.3-1: Service provisioning response

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.

Table 8.3.3.3.3-2: EDN configuration information

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 3GPP TS 23.501 [2].
> 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 3GPP TS 33.558 [23], 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 3GPP TS 23.503 [12] 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

Table 8.3.3.3.4-1 describes the information elements for service provisioning subscription request from the EEC to the ECS.

Table 8.3.3.3.4-1: Service provisioning subscription request

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

Table 8.3.3.3.5-1 describes the information elements for service provisioning subscription response from the ECS to the EEC.

Table 8.3.3.3.5-1: Service provisioning subscription response

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

Table 8.3.3.3.6-1 describes the information elements for service provisioning notification from the ECS to the EEC.

Table 8.3.3.3.6-1: Service provisioning notification

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.

NOTE: When SEAL NMS is used, Service provisioning notification is the Notification data in SEAL Notification message of clause 17.3.2.4 in 3GPP TS 23.434 [13].

Editor’s note: Similar updates to other Subscription and Notification messages is FFS.

8.3.3.3.7 Service provisioning subscription update request

Table 8.3.3.3.7-1 describes the information elements for service provisioning subscription update request from the EEC to the ECS.

Table 8.3.3.3.7-1: Service provisioning subscription update request

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

Table 8.3.3.3.8-1 describes the information elements for service provisioning subscription update response from the ECS to the EEC.

Table 8.3.3.3.8-1: Service provisioning subscription update response

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

Table 8.3.3.3.9-1 describes the information elements for service provisioning unsubscribe request from the EEC to the ECS.

Table 8.3.3.3.9-1: Service provisioning unsubscribe request

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

Table 8.3.3.3.10-1 describes the information elements for service provisioning unsubscribe response from the ECS to the EEC.

Table 8.3.3.3.10-1: Service provisioning unsubscribe response

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

8.3.3.4.1 General

Table 8.3.3.4.1-1 illustrates the API for service provisioning.

Table 8.3.3.4.1-1: Eecs_ServiceProvisioning API

API Name	API Operations	Operation Semantics	Consumer(s)
Eecs_ServiceProvisioning	Request	Request/Response	EEC
	Subscribe	Subscribe/Notify	EEC
	Notify
	UpdateSubscription
	Unsubscribe

8.3.3.4.2 Eecs_ServiceProvisioning_Request operation

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

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

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

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

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.