8 Edge Configuration Server API Definitions
24.5583GPPEnabling Edge ApplicationsProtocol specificationRelease 17TS
8.1 Eecs_ServiceProvisioning API
8.1.1 API URI
The Eecs_ServiceProvisioning service shall use the Eecs_ServiceProvisioning API.
The request URI used in each HTTP request from the EEC towards the ECS shall have the structure as defined in clause 6.1 with the following clarifications:
– The <apiName> shall be "eecs-serviceprovisioning".
– The <apiVersion> shall be "v1".
– The <apiSpecificResourceUriPart> shall be set as described in clause 8.1.2.
8.1.2 Resources
8.1.2.1 Overview
Figure 8.1.2.1-1: Resource URI structure of the Eecs_ServiceProvisioning API
Table 8.1.2.1-1 provides an overview of the resources and applicable HTTP methods.
Table 8.1.2.1-1: Resources and methods overview
Resource name |
Resource URI |
HTTP method or custom operation |
Description |
Service Provisioning Subscriptions |
/subscriptions |
POST |
Creates a new subscription in ECS in order to be notified of provisioning data changes of interest. |
Individual Service Provisioning Subscription |
/subscriptions/{subscriptionId} |
PUT |
Updates an existing individual service provisioning subscription identified by the subscriptionId |
DELETE |
Deletes an existing individual service provisioning subscription identified by the subscriptionId. |
||
PATCH |
Partial update an existing individual service provisioning subscription identified by the subscriptionId. |
8.1.2.3 Resource: Service Provisioning Subscriptions
8.1.2.3.1 Description
This resource represents a collection of service provisioning subscriptions of EECs interested in receiving provisioning data related notifications from ECS.
8.1.2.3.2 Resource Definition
Resource URI: {apiRoot}/eecs-serviceprovisioning/<apiVersion>/subscriptions
This resource shall support the resource URI variables defined in table 8.1.2.3.2-1.
Table 8.1.2.3.2-1: Resource URI variables for this resource
Name |
Data Type |
Definition |
apiRoot |
String |
See clause 7.5 of 3GPP TS 29.558 [4] |
8.1.2.3.3 Resource Standard Methods
8.1.2.3.3.1 POST
This method creates a new subscription. This method shall support the URI query parameters specified in table 8.1.2.3.3.1-1.
Table 8.1.2.3.3.1-1: URI query parameters supported by the POST method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
This method shall support the request data structures specified in table 8.1.2.3.3.1-2 and the response data structures and response codes specified in table 8.1.2.3.3.1-3.
Table 8.1.2.3.3.1-2: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
ECSServProvSubscription |
M |
1 |
Create a new service provisioning subscription. |
Table 8.1.2.3.3.1-3: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
ECSServProvSubscription |
M |
1 |
201 Created |
Individual ECS Service Provisioning Subscription resource created successfully. The URI of the created resource shall be returned in the "Location" HTTP header |
NOTE: The mandatory HTTP error status code for the POST method listed in Table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |
Table 8.1.2.3.3.1-4: Headers supported by the 201 response code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
String |
M |
1 |
Contains the URI of the newly created resource, according to the structure: {apiRoot}/eecs-serviceprovisioning/<apiVersion>/subscriptions/{subscriptionId} |
8.1.2.3.4 Resource Custom Operations
None.
8.1.2.4 Resource: Individual Service Provisioning Subscription
8.1.2.4.1 Description
This resource represents the individual service provisioning subscription of an EEC at a given ECS.
8.1.2.4.2 Resource Definition
Resource URI: {apiRoot}/eecs-serviceprovisioning/<apiVersion>/subscriptions/{subscriptionId}
This resource shall support the resource URI variables defined in the table 8.1.2.4.2-1.
Table 8.1.2.4.2-1: Resource URI variables for this resource
Name |
Data Type |
Definition |
apiRoot |
string |
See clause 7.5 of 3GPP TS 29.558 [4] |
subscriptionId |
string |
Identifies an individual service provisioning subscription. |
8.1.2.4.3 Resource Standard Methods
8.1.2.4.3.1 PUT
This method updates the individual service provisioning subscription information at the ECS by completely replacing the existing subscription data (except eecId, suppFeat, requestTestNotification and websockNotifConfig). This method shall support the URI query parameters specified in the table 8.1.2.4.3.1-1.
Table 8.1.2.4.3.1-1: URI query parameters supported by the PUT method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
This method shall support the request data structures specified in table 8.1.2.4.3.1-2 and the response data structures and response codes specified in table 8.1.2.4.3.1-3.
Table 8.1.2.4.3.1-2: Data structures supported by the PUT Request Body on this resource
Data type |
P |
Cardinality |
Description |
ECSServProvSubscription |
M |
1 |
Details of individual service provisioning subscription matching the subscriptionId to be updated at the ECS. |
Table 8.1.2.4.3.1-3: Data structures supported by the PUT Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
ECSServProvSubscription |
M |
1 |
200 OK |
The individual service provisioning subscription matching the subscriptionId was modified successfully and the updated information is returned in the response. |
n/a |
204 No Content |
The individual service provisioning subscription matching the subscriptionId was modified successfully. |
||
n/a |
307 Temporary Redirect |
Temporary redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative ECS. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3]. |
||
n/a |
308 Permanent Redirect |
Permanent redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative ECS. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3]. |
||
NOTE: The mandatory HTTP error status code for the PUT method listed in Table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |
Table 8.1.2.4.3.1-4: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located in an alternative ECS. |
Table 8.1.2.4.3.1-5: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located in an alternative ECS. |
8.1.2.4.3.2 DELETE
This method removes the subscription information from the ECS. This method shall support the URI query parameters specified in the table 8.1.2.4.3.2-1.
Table 8.1.2.4.3.2-1: URI query parameters supported by the DELETE method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
This method shall support the request data structures specified in table 8.1.2.4.3.2-2 and the response data structures and response codes specified in table 8.1.2.4.3.2-3.
Table 8.1.2.4.3.2-2: Data structures supported by the DELETE Request Body on this resource
Data type |
P |
Cardinality |
Description |
n/a |
Table 8.1.2.4.3.2-3: Data structures supported by the DELETE Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
M |
1 |
204 No Content |
The individual service provisioning subscription matching the subscriptionId is deleted. |
n/a |
307 Temporary Redirect |
Temporary redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative ECS. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3]. |
||
n/a |
308 Permanent Redirect |
Permanent redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative ECS. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3]. |
||
NOTE: The mandatory HTTP error status code for the DELETE method listed in Table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |
Table 8.1.2.4.3.2-4: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located in an alternative ECS. |
Table 8.1.2.4.3.2-5: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located in an alternative ECS. |
8.1.2.4.3.3 PATCH
This method partially updates the individual service provisioning subscription. This method shall support the URI query parameters specified in the table 8.1.2.4.3.3-1.
Table 8.1.2.4.3.3-1: URI query parameters supported by the PATCH method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
This method shall support the request data structures specified in table 8.1.2.4.3.3-2 and the response data structures and response codes specified in table 8.1.2.4.3.3-3.
Table 8.1.2.4.3.3-2: Data structures supported by the PATCH Request Body on this resource
Data type |
P |
Cardinality |
Description |
ECSServProvSubscriptionPatch |
M |
1 |
Details of individual service provisioning subscription matching the subscriptionId to be updated at the ECS. |
Table 8.1.2.4.3.3-3: Data structures supported by the PATCH Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
ECSServProvSubscription |
M |
1 |
200 OK |
The individual service provisioning subscription matching the subscriptionId was modified successfully and the updated information is returned in the response. |
n/a |
204 No Content |
The individual service provisioning subscription matching the subscriptionId was modified successfully. |
||
n/a |
307 Temporary Redirect |
Temporary redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative ECS. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3]. |
||
n/a |
308 Permanent Redirect |
Permanent redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative ECS. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3]. |
||
NOTE: The mandatory HTTP error status code for the PATCH method listed in Table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |
Table 8.1.2.4.3.3-7: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located in an alternative ECS. |
Table 8.1.2.4.3.3-8: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located in an alternative ECS. |
8.1.3 Custom Operations without associated resources
8.1.3.1 Overview
The structure of the custom operation URIs of the Eecs_ServiceProvisioning API is shown in Figure 8.1.3.1-1.
Figure 8.1.3.1-1: Custom operation URI structure of the Eecs_ServiceProvisioning API
Table 8.1.3.1-1 provides an overview of the custom operations and applicable HTTP methods defined for the Eecs_ServiceProvisioning API.
Table 8.1.3.1-1: Custom operations without associated resources
Operation name |
Custom operation URI |
Mapped HTTP method |
Description |
Request |
/request |
POST |
Enables an EEC to request service provisioning information to the ECS. |
8.1.3.2 Operation: Request
8.1.3.2.1 Description
The custom operation enables an EEC to request service provisioning information to the ECS.
8.1.3.2.2 Operation Definition
This operation shall support the request data structures and the response data structures and response codes specified in tables 8.1.3.2.2-1 and 8.1.3.2.2-2.
Table 8.1.3.2.2-1: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
ECSServProvReq |
M |
1 |
Contains the parameters to request service provisioning information. |
Table 8.1.3.2.2-2: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
ECSServProvResp |
M |
1 |
200 OK |
The requested service provisioning information is returned successfully. |
n/a |
204 No Content |
The requested service provisioning information does not exist. |
||
n/a |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing an alternative target URI located in an alternative ECS. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3]. |
||
n/a |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing an alternative target URI located in an alternative ECS. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] |
||
NOTE: The manadatory HTTP error status code for the HTTP POST method listed in Table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |
Table 8.1.3.2.2-3: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative target URI located in an alternative ECS. |
Table 8.1.3.2.2-4: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative target URI located in an alternative ECS. |
8.1.4 Notifications
8.1.4.1 General
Table 8.1.4.1-1: Notifications overview
Notification |
Callback URI |
HTTP method or custom operation |
Description (service operation) |
Service Provisioning Notification |
{notificationDestination} |
POST |
Notifies EEC of the service provisioning information of interest. |
8.1.4.2 Service Provisioning Notification
8.1.4.2.1 Description
Service Provisioning Notification is used by the ECS to notify an EEC with service provisioning information.
8.1.4.2.2 Notification definition
The POST method shall be used by the ECS for sending notifications and the notification destination shall be the callback URI as provided by the EEC during the service provisioning subscription.
Callback URI: {notificationDestination}
This method shall support the URI query parameters specified in table 8.1.4.2.2-1.
Table 8.1.4.2.2-1: URI query parameters supported by the POST method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
This method shall support the request data structures specified in table 8.1.4.2.2-2 and the response data structures and response codes specified in table 8.1.4.2.2-3.
Table 8.1.4.2.2-2: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
ServProvNotification |
M |
1 |
Notification of service provisioning information. |
Table 8.1.4.2.2-3: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
204 No Content |
The receipt of the Notification is acknowledged. |
||
n/a |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing an alternative URI representing the end point of an alternative EEC where the notification should be sent. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3]. |
||
n/a |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing an alternative URI representing the end point of an alternative EEC where the notification should be sent. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3]. |
||
NOTE: The mandatory HTTP error status code for the POST method listed in Table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |
Table 8.1.4.2.2-4: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI representing the end point of an alternative EEC towards which the notification should be redirected. |
Table 8.1.4.2.2-5: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI representing the end point of an alternative EEC towards which the notification should be redirected. |
8.1.5 Data Model
8.1.5.1 General
This clause specifies the application data model supported by the API. Data types listed in clause 7.2 of 3GPP TS 29.558 [4] apply to this API.
Table 8.1.5.1-1 specifies the data types defined specifically for the Eecs_ServiceProvisioning API service.
Table 8.1.5.1-1: Eecs_ServiceProvisioning API specific Data Types
Data type |
Section defined |
Description |
Applicability |
ECSServProvReq |
8.1.5.2.2 |
||
ECSServProvResp |
8.1.5.2.3 |
||
ECSServProvSubscription |
8.1.5.2.4 |
Represents the service provisioning subscription. |
|
ConnectivityInfo |
8.1.5.2.5 |
||
ServProvNotification |
8.1.5.2.6 |
Service provisioning information notification from ECS to EEC. |
|
EDNConfigInfo |
8.1.5.2.7 |
||
EDNConInfo |
8.1.5.2.8 |
||
EESInfo |
8.1.5.2.9 |
Table 8.1.5.1-2 specifies data types re-used by the Eecs_ServiceProvisioning API service.
Table 8.1.5.1-2: Re-used Data Types
Data type |
Reference |
Comments |
Applicability |
PlmnId |
3GPP TS 29.571 [5] |
||
ACProfile |
clause 6.2.5.2.3 |
||
DateTime |
3GPP TS 29.122 [3] |
||
Uri |
3GPP TS 29.122 [3] |
||
SupportedFeatures |
3GPP TS 29.571 [5] |
Used to negotiate the applicability of optional features. |
|
Snssai |
3GPP TS 29.571 [5] |
||
LocationArea5G |
3GPP TS 29.122 [3] |
||
EndPoint |
3GPP TS 29.558 [4] |
||
Dnai |
3GPP TS 29.571 [5] |
||
LocationInfo |
3GPP TS 29.122 [3] |
The location information related to the UE. |
|
Dnn |
3GPP TS 29.571 [5] |
||
Gpsi |
3GPP TS 29.571 [5] |
Used to identify the UE. |
|
ACRScenario |
3GPP TS 29.558 [4] |
8.1.5.2 Structured data types
8.1.5.2.1 Introduction
8.1.5.2.2 Type: ECSServProvReq
Table 8.1.5.2.2-1: Definition of type ECSServProvReq
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
eecId |
string |
M |
0..1 |
Represents a unique identifier of the EEC. |
|
ueId |
Gpsi |
O |
0..1 |
Represents the identifier of the UE. |
|
acProfs |
array(ACProfile) |
O |
1..N |
Information about services the EEC wants to connect to. |
|
eecSvcContSupp |
array(ACRScenario) |
O |
0..1 |
The ACR scenarios supported by the EEC for service continuity. If this attribute is not present, then the EEC does not support service continuity. |
|
connInfo |
array(ConnectivityInfo) |
O |
0..N |
List of connectivity information for the UE. |
|
locInf |
LocationInfo |
O |
0..1 |
Represents location information of the UE. |
8.1.5.2.3 Type: ECSServProvResp
Table 8.1.5.2.3-1: Definition of type ECSServProvResp
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
ednCnfgInfo |
array(EDNConfigInfo) |
M |
1..N |
List of EDN configuration information. |
8.1.5.2.4 Type: ECSServProvSubscription
Table 8.1.5.2.4-1: Definition of type ECSServProvSubscription
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
eecId |
string |
M |
0..1 |
Represents a unique identifier of the EEC. |
|
ueId |
Gpsi |
O |
0..1 |
Represents the identifier of the UE. |
|
acProfs |
array(ACProfile) |
O |
1..N |
Information about services the EEC wants to connect to. |
|
expTime |
DateTime |
O |
0..1 |
Indicates the expiration time of the subscription. If the expiration time is not present, then it indicates that the EEC subscription never expires. |
|
eecSvcContSupp |
array(ACRScenario) |
O |
0..1 |
The ACR scenarios supported by the EEC for service continuity. If this attribute is not present, then the EEC does not support service continuity. |
|
connInfo |
array(ConnectivityInfo) |
O |
0..N |
List of connectivity information for the UE. |
|
notificationDestination |
Uri |
O |
1 |
The notification target address containing the URI where the service provisioning notification should be delivered to. This attribute shall be present in HTTP POST message to ECS. (NOTE 1) |
|
requestTestNotification |
boolean |
O |
0..1 |
Set to true by Subscriber to request the ECS to send a test notification as defined in clause 7.6 of 3GPP TS 29.558 [4]. Set to false or omitted otherwise. |
Notification_test_event |
websockNotifConfig |
WebsockNotifConfig |
O |
0..1 |
Configuration parameters to set up notification delivery over Websocket protocol as defined in clause 7.6 of 3GPP TS 29.558 [4]. |
Notification_websocket |
suppFeat |
SupportedFeatures |
O |
0..1 |
Used to negotiate the supported optional features of the API as described in clause 7.8 of 3GPP TS 29.558 [4]. This attribute shall be provided in the HTTP POST request and in the response of successful resource creation. This attribute also shall be provided in the HTTP PUT request and in the response of successful resource modification. |
|
NOTE 1: 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. |
8.1.5.2.5 Type: ConnectivityInfo
Table 8.1.5.2.5-1: Definition of type ConnectivityInfo
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
plmnId |
PlmnId |
O |
0..1 |
Represents PLMN identity |
|
ssId |
string |
O |
0..1 |
This IE shall be present if the UE is accessing the 5GC via a trusted WLAN access network. When present, it shall contain the SSID of the access point to which the UE is attached. |
8.1.5.2.6 Type: ServProvNotification
Table 8.1.5.2.6-1: Definition of type ServProvNotification
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
subId |
string |
M |
1 |
String identifying the individual service provisioning subscription for which the service provisioning notification is delivered. |
|
ednCnfgInfo |
array(EDNConfigInfo) |
M |
1..N |
List of EDN configuration information. |
8.1.5.2.7 Type: EDNConfigInfo
Table 8.1.5.2.7-1: Definition of type EDNConfigInfo
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
ednConInfo |
EDNConInfo |
M |
1 |
Contains EDN connection information required by the UE to establish connection with the EDN |
|
eess |
array(EESInfo) |
M |
1..N |
Contains the list of EESs of the EDN |
|
lifeTime |
DateTime |
O |
0..1 |
Indicates the time duration for which the EDN configuration information is valid and supposed to be cached in the EEC. |
8.1.5.2.8 Type: EDNConInfo
Table 8.1.5.2.8-1: Definition of type EDNConInfo
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
dnn |
Dnn |
O |
0..1 |
String representing a Data Network or an APN |
|
snssai |
Snssai |
O |
0..1 |
Represents network slice information |
|
ednTopoSrvArea |
LocationArea5G |
O |
0..1 |
The list of geographical and topological areas that the ECS serves. ACs in the UE that are outside the area shall not be served. |
8.1.5.2.9 Type: EESInfo
Table 8.1.5.2.9-1: Definition of type EESInfo
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
eesId |
string |
M |
1 |
The identifier of the EES |
|
endPt |
EndPoint |
M |
1 |
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 |
array(string) |
O |
1..N |
The list of application identifiers of the Edge Application Servers registered with the EES, e.g. FQDN, URI. |
|
ecspInfo |
string |
O |
0..1 |
String representing the EES Provider (such as ECSP Information) |
|
svcArea |
LocationArea5G |
O |
0..1 |
The list of geographical and topological areas that the EES serves. EECs in the UE that are outside the area shall not be served. |
|
dnais |
array(Dnai) |
O |
0..1 |
Represents list of Data network access identifier |
|
eesSvcContSupp |
array(ACRScenario) |
O |
0..1 |
The ACR scenarios supported by the EES for service continuity. If this attribute is not present, then the EEC does not support service continuity. |
|
eecRegConf |
boolean |
M |
1 |
Indicates whether the EEC is required to register on the EES to use edge services or not |
8.1.5.2.10 Type: ECSServProvSubscriptionPatch
Table 8.1.5.2.10-1: Definition of type ECSServProvSubscriptionPatch
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
acProfs |
array(ACProfile) |
O |
1..N |
Information about services the EEC wants to connect to. |
|
expTime |
DateTime |
O |
0..1 |
Indicates the expiration time of the subscription. If the expiration time is not present, then it indicates that the EEC subscription never expires. |
|
eecSvcContSupp |
array(ACRScenario) |
O |
0..1 |
The ACR scenarios supported by the EEC for service continuity. If this attribute is not present, then the EEC does not support service continuity. |
|
connInfo |
array(ConnectivityInfo) |
O |
0..N |
List of connectivity information for the UE. |
8.1.5.3 Simple data types and enumerations
None.
8.1.6 Error Handling
General error handling are described in clause 7.7 of 3GPP TS 29.558 [4].
8.1.7 Feature negotiation
General feature negotiation procedures are described in clause 7.8 of 3GPP TS 29.558 [4]. Table 8.1.7-1 lists the supported features for Eecs_ServiceProvisioning API.
Table 8.1.7-1: Supported Features
Feature number |
Feature Name |
Description |
1 |
Notification_test_event |
Testing of notification connection is supported according to clause 7.6 of 3GPP TS 29.558 [4]. |
2 |
Notification_websocket |
The delivery of notifications over Websocket is supported according to clause 7.6 of 3GPP TS 29.558 [4]. This feature requires that the Notification_test_event feature is also supported. |