6 Edge Enabler Server API Definitions
24.5583GPPEnabling Edge ApplicationsProtocol specificationRelease 17TS
6.1 Void
6.2 Eees_EECRegistration API
6.2.1 API URI
The request URI used in each HTTP request from the EEC towards the EES shall have the structure as defined in clause 6.1 with the following clarifications:
– The <apiName> shall be "eees-eecregistration".
– The <apiVersion> shall be "v1".
– The <apiSpecificResourceUriPart> shall be set as described in clause 6.2.2.
6.2.2 Resources
6.2.2.1 Overview
Figure 6.2.2.1-1: Resource URI structure of the Eees_EECRegistration API
Table 6.2.2.1-1 provides an overview of the resources and applicable HTTP methods.
Table 6.2.2.1-1: Resources and methods overview
Resource name |
Resource URI |
HTTP method or custom operation |
Description |
EEC Registrations |
/registrations |
POST |
Create a new EEC registration at the EES |
Individual EEC registration |
/registrations/{registrationId} |
PUT |
Update an existing EEC registration a the EES |
DELETE |
Remove an existing ECC registration at EES |
||
PATCH |
Partially update an existing EEC registration a the EES |
6.2.2.2 Resource: EEC Registrations
6.2.2.2.1 Description
This resource represents a collection of EEC registrations with an EES.
6.2.2.2.2 Resource Definition
Resource URI: {apiRoot}/eees-eecregistration/<apiVersion>/registrations
This resource shall support the resource URI variables defined in table 6.2.2.2.2-1.
Table 6.2.2.2.2-1: Resource URI variables for this resource
Name |
Data Type |
Definition |
apiRoot |
string |
See clause 6.1 |
6.2.2.2.3 Resource Standard Methods
6.2.2.2.3.1 POST
This method creates a new registration. This method shall support the URI query parameters specified in table 6.22.2.3.1-
Table 6.2.2.2.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 6.2.2.2.3.1-2 and the response data structures and response codes specified in table 6.2.2.2.3.1-3
Table 6.2.2.2.3.1-2: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
EECRegistration |
M |
1 |
EEC registration request information |
Table 6.2.2.2.3.1-3: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
EECRegistration |
M |
1 |
201 Created |
EEC information is registered successfully at EES. EEC information registered with EES is provided in the response body. The URI of the created resource shall be returned in the "Location" HTTP header |
NOTE: The manadatory HTTP error status code for the POST method listed in Table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |
Table 6.2.2.2.3.1-4: Headers supported by the POST method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.2.2.2.3.1-5: 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}/eees-eecregistration/<apiVersion>/registrations/{registrationId} |
6.2.2.2.4 Resource Custom Operations
None.
6.2.2.3 Resource: Individual EEC registration
6.2.2.3.1 Description
This resource represents an individual registration of an EEC.
6.2.2.3.2 Resource Definition
Resource URI: {apiRoot}/eees-eecregistration//<apiVersion>/registrations/{registrationId}
This resource shall support the resource URI variables defined in table 6.2.2.3.2-1.
Table 6.2.2.3.2-1: Resource URI variables for this resource
Name |
Data Type |
Definition |
apiRoot |
string |
See clause 6.1 |
registrationId |
string |
The Identifier of a specific EEC registration. |
6.2.2.3.3 Resource Standard Methods
6.2.2.3.3.1 PUT
This method updates the EEC registration data by completely replacing the existing registration data. This method shall support the URI query parameters specified in table 6.2.2.3.3.1-1.
Table 6.2.2.3.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 6.2.2.3.3.1-2 and the response data structures and response codes specified in table 6.2.2.3.3.1-3.
Table 6.2.2.3.3.1-2: Data structures supported by the PUT Request Body on this resource
Data type |
P |
Cardinality |
Description |
EECRegistration |
M |
1 |
An Individual registration resource to be updated. |
Table 6.2.2.3.3.1-3: Data structures supported by the PUT Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
EECRegistration |
M |
1 |
200 OK |
An individual EEC registration resource updated successfully and the EECRegistration data shall be included in the response. |
n/a |
204 No Content |
An individual EEC registration resource updated 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 EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that the SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
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 EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that the SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
NOTE: The manadatory HTTP error status code for the PUT method listed in Table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |
Table 6.2.2.3.3.1-4: Headers supported by the PUT method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.2.2.3.3.1-5: Headers supported by the 200 response code on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.2.2.3.3.1-6: Links supported by the 200 Response Code on this endpoint
Name |
Resource name |
HTTP method or custom operation |
Link parameter(s) |
Description |
n/a |
Table 6.2.2.3.3.1-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 EES. |
Table 6.2.2.3.3.1-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 EES. |
6.2.2.3.3.2 DELETE
This method deregisters (removes) an existing EEC registration. This method shall support the URI query parameters specified in table 6.2.2.3.3.2-1.
Table 6.2.2.3.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 6.2.2.3.3.2-2 and the response data structures and response codes specified in table 6.2.2.3.3.2-3.
Table 6.2.2.3.3.1-2: Data structures supported by the DELETE Request Body on this resource
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.2.2.3.3.1-3: Data structures supported by the DELETE Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
204 No Content |
An individual EEC registration resource deleted successfully. |
||
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 EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that the SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
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 EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
NOTE: The manadatory HTTP error status code for the DELETE method listed in Table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |
Table 6.2.2.3.3.3-4: Headers supported by the DELETE method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.2.2.3.3.3-5: Headers supported by the 204 response code on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.2.2.3.3.3-6: Links supported by the 200 Response Code on this endpoint
Name |
Resource name |
HTTP method or custom operation |
Link parameter(s) |
Description |
n/a |
Table 6.2.2.3.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 EES. |
Table 6.2.2.3.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 EES. |
6.2.2.3.3.3 PATCH
This method partially updates the EEC registration at EES. This method shall support the URI query parameters specified in table 6.2.2.3.3.3-1.
Table 6.2.2.3.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 6.2.2.3.3.3-2 and the response data structures and response codes specified in table 6.2.2.3.3.3-3.
Table 6.2.2.3.3.3-2: Data structures supported by the PATCH Request Body on this resource
Data type |
P |
Cardinality |
Description |
EECRegistrationPatch |
M |
1 |
An Individual registration resource to be updated. |
Table 6.2.2.3.3.3-3: Data structures supported by the PATCH Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
EECRegistration |
M |
1 |
200 OK |
An individual EEC registration resource updated successfully and the EECRegistration data shall be included in the response. |
n/a |
204 No Content |
An individual EEC registration resource updated 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 EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that the SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
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 EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that the SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
NOTE: The manadatory HTTP error status code for the PATCH method listed in Table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |
Table 6.2.2.3.3.3-4: Headers supported by the PATCH method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.2.2.3.3.3-5: Headers supported by the 200 response code on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.2.2.3.3.3-6: Links supported by the 200 Response Code on this endpoint
Name |
Resource name |
HTTP method or custom operation |
Link parameter(s) |
Description |
n/a |
Table 6.2.2.3.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 EES. |
Table 6.2.2.3.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 EES. |
6.2.2.3.4 Resource Custom Operations
None.
6.2.3 Custom Operations without associated resources
None.
6.2.4 Notifications
None.
6.2.5 Data Model
6.2.5.1 General
This clause specifies the application data model supported by the Eees_EECRegistration API.
Table 6.2.5.1-1 specifies the data types defined specifically for the Eees_EECRegistration API service.
Table 6.2.5.1-1: Eees_EECRegistration API specific Data Types
Data type |
Section defined |
Description |
Applicability |
EECRegistration |
6.2.5.2.2 |
Describes the parameters to perform EEC Registration related operations |
|
acProfile |
6.2.5.2.3 |
Describes information about AC used to determine services and service characteristics required |
|
EASDetail |
6.2.5.2.4 |
Describes EAS along with service KPIs that serves the AC |
|
acServiceKPIs |
6.2.5.2.5 |
Describes the KPIs required by the AC in order to receive required services |
Table 6.2.5.1-2 specifies data types re-used by the Eees_EECRegistration API service.
Table 6.2.5.1-2: Re-used Data Types
Data type |
Reference |
Comments |
Applicability |
BitRate |
3GPP TS 29.571 [5] |
||
DateTime |
3GPP TS 29.122 [3] |
||
EndPoint |
3GPP TS 29.558 [4] |
||
ScheduledCommunicationTime |
3GPP TS 29.122 [3] |
||
LocationArea5G |
3GPP TS 29.122 [3] |
||
Uinteger |
3GPP TS 29.571 [5] |
||
DurationSec |
3GPP TS 29.122 [3] |
||
SupportedFeatures |
3GPP TS 29.571 [5] |
||
Gpsi |
3GPP TS 29.571 [5] |
||
ACRScenario |
3GPP TS 29.558 [4] |
6.2.5.2 Structured data types
6.2.5.2.1 Introduction
6.2.5.2.2 Type: EecRegistration
Table 6.2.5.2.2-1: Definition of type EecRegistration
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 |
Profiles of ACs for which the EEC provides edge enabling services. |
|
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. |
|
expTime |
DateTime |
O |
0..1 |
Represents an expiration time for the registration. This attribute shall be present in the response of the HTTP POST message from EEC to create a new registration or in the response of the HTTP PUT message from EEC to update a specific registration. If abesent, then it indicates that the registration of EEC never expires. |
|
eecCntxId |
string |
O |
0..1 |
Identifier of the EEC context obtained from a previous registration. |
|
srcEesId |
string |
O |
0..1 |
Identifier of the EES that provided EEC context ID. |
|
srcEesEndpoint |
EndPoint |
O |
0..1 |
The endpoint address of the EES that provided EEC context ID. |
|
unfulfilledAcProfs |
array(UnfulfilledAcProfile) |
O |
1..N |
Represents the list of ACIDs of the AC Profile(s) sent from EES, for which the requirements indicated in the AC profile(s) cannot be fulfilled as shared in reason |
6.2.5.2.3 Type: ACProfile
Table 6.2.5.2.3-1: Definition of type ACProfile
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
acId |
string |
M |
1 |
Identity of the AC. |
|
acType |
string |
O |
0..1 |
The category or type of AC. |
|
prefEcsps |
array(string) |
O |
1..N |
Indicates to the ECS which ECSPs are preferred for the AC. The ECS may use this information in the selection of EESs. |
|
acSchedule |
ScheduledCommunicationTime |
O |
0..1 |
Indicates the expected operation schedule of the AC (e.g. time windows) |
|
expAcGeoServArea |
LocationArea5G |
O |
0..1 |
Indicates the expected location(s) (e.g. route) of the hosting UE during the AC’s operation schedule. |
|
acSvcContSupp |
array(ACRScenario) |
O |
0..1 |
Indicates if service continuity support is required or not for the application. The ACR scenarios supported by the AC for service continuity. If this attribute is not present, then the AC does not support service continuity. |
|
eass |
Array(EasDetail) |
O |
1..N |
Provides the list of EAS that serve the AC along with the service KPIs required by the AC |
6.2.5.2.4 Type: EasDetail
Table 6.2.5.2.4-1: Definition of type EasDetail
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
easId |
string |
M |
1 |
The application identifier of the EAS, e.g. FQDN, URI. |
|
expectedSvcKPIs |
ACServiceKPIs |
O |
0..1 |
Describes the KPIs expected in order for ACs to receive currently required services from the EAS |
|
minimumReqSvcKPIs |
ACServiceKPIs |
O |
0..1 |
Describes the minimum KPIs required in order for ACs to receive meaningful services from the EAS |
6.2.5.2.5 Type: ACServiceKPIs
Table 6.2.5.2.5-1: Definition of type ACServiceKPIs
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
connBand |
BitRate |
O |
0..1 |
The required connection bandwidth in Kbit/s for the application. |
|
reqRate |
Uinteger |
O |
0..1 |
The request rate to be generated by the AC. |
|
respTime |
DurationSec |
O |
0..1 |
Response time required for the server servicing the requests. |
|
avail |
Uinteger |
O |
0..1 |
Percentage of time the server is required to be available for the AC’s use. |
|
reqComp |
string |
O |
0..1 |
The compute resources required by the AC. |
|
reqGrapComp |
string |
O |
0..1 |
The graphical compute resources required by the AC. |
|
reqMem |
string |
O |
0..1 |
The memory resources required by the AC. |
|
reqStrg |
string |
O |
0..1 |
The storage resources required by the AC. |
6.2.5.2.6 Type: EecRegistrationPatch
Table 6.2.5.2.6-1: Definition of type EecRegistrationPatch
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
acProfs |
array(ACProfile) |
O |
1..N |
Profiles of ACs for which the EEC provides edge enabling services. |
|
expTime |
DateTime |
O |
0..1 |
Represents an expiration time for the registration. |
|
unfulfilledAcProfs |
array(UnfulfilledAcProfile) |
O |
1..N |
Represents the list of ACIDs of the AC Profile(s) sent from EES, for which the requirements indicated in the AC profile(s) cannot be fulfilled as shared in reason |
6.2.5.2.7 Type: UnfulfilledAcProfile
Table 6.2.5.2.7-1: Definition of type UnfulfilledAcProfile
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
acId |
string |
M |
0..1 |
The list of identifier of the AC profile |
|
reason |
UnfulfillACProfRsn |
O |
0..1 |
Reason indicating the cause (e.g. EAS not available, requirements cannot be fulfilled) |
6.2.5.3 Simple data types and enumerations
6.2.5.3.1 Introduction
This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.
6.2.5.3.2 Simple data types
The simple data types defined in table 6.2.5.3.2-1 shall be supported.
Table 6.2.5.3.2-1: Simple data types
Type Name |
Type Definition |
Description |
Applicability |
6.2.5.3.3 Enumeration: UnfulfillACProfRsn
The enumeration UnfulfillACProfRsn represents the reasons for AC profile failure during EEC Registration. It shall comply with the provisions defined in table 6.2.5.3.3-1.
Table 6.2.5.3.3-1: Enumeration UnfulfillACProfRsn
Enumeration value |
Description |
Applicability |
EAS_NOT_AVAILABLE |
EAS not available |
|
REQ_UNFULFILLED |
Requirements cannot be fulfilled |
6.2.6 Error Handling
General error handling are described in clause 6.1.
6.2.6.1 Application Errors
The application errors defined for the Eees_EECRegistration service are listed in Table 6.2.6.1-1. The EES shall include in the HTTP status code a "ProblemDetails" data structure with the "cause" attribute indicating the application error as listed in table 6.2.6.1-1.
Table 6.2.6.1-1: Application errors
Application Error |
HTTP status code |
Description |
RESOURCE_NOT_FOUND |
404 Not Found |
Indicates that the requirements included in the EEC registration request e.g., the AC Profile(s) cannot be fulfilled. |
6.2.7 Feature negotiation
General feature negotiation procedures are described in clause 6.1. Table 6.2.7-1 lists the supported features for Eees_EECRegistration API.
Table 6.2.7-1: Supported Features
Feature number |
Feature Name |
Description |
6.3 Eees_EASDiscovery API
6.3.1 API URI
The Eees_EASDiscovery service shall use the Eees_EASDiscovery API.
The request URIs used in HTTP requests shall have the Resource URI structure defined in clause 6.1 with the following clarifications:
– The {apiRoot} shall be set as described in clause 6.1.
– The <apiName> shall be "eees-easdiscovery".
– The <apiVersion> shall be "v1".
– The <apiSpecificResourceUriPart> shall be set as described in clause 6.3.2.
6.3.2 Resources
6.3.2.1 Overview
Figure 6.3.2.1-1: Resource URI structure of the Eees_EASDiscovery API
Table 6.3.2.1-1 provides an overview of the resources and applicable HTTP methods.
Table 6.3.2.1-1: Resources and methods overview
Resource name |
Resource URI |
HTTP method or custom operation |
Description |
EAS Discovery Subscriptions |
/subscriptions |
POST |
Creates a new individual EAS discovery subscription. |
Individual EAS Discovery Subscription |
/subscriptions/{subscriptionId} |
PUT |
Updates an existing individual EAS discovery subscription identified by the subscriptionId. |
DELETE |
Deletes an existing individual EAS discovery subscription identified by the subscriptionId. |
||
PATCH |
Partial update an existing EAS Discovery Subscription resource identified by a subscriptionId. |
||
EAS Profiles |
/eas-profiles/request-discovery |
request-discovery (POST) |
Request EAS discovery. |
NOTE 1: Based on SA3 specified security mechanisms for EDGE-1, EDGE-3 and EDGE-9 interfaces, the EES can identify the initiator of the API (i.e. EEC, EAS or EES) and apply the appropriate security procedures as specified in 3GPP TS 33.558 [20].
NOTE 2: The same service API can be implemented on different interfaces, i.e. EDGE-1, EDGE-3 and EDGE-9, which are for separate endpoints, i.e. EEC, EAS and EES.
6.3.2.2 Resource: EAS Discovery Subscriptions
6.3.2.2.1 Description
This resource represents the collection of EAS Discovery Subscriptions managed by the EES.
6.3.2.2.2 Resource Definition
Resource URI: {apiRoot}/eees-easdiscovery/<apiVersion>/subscriptions
This resource shall support the resource URI variables defined in table 6.3.2.2.2-1.
Table 6.3.2.2.2-1: Resource URI variables for this resource
Name |
Data Type |
Definition |
apiRoot |
string |
See clause 6.1. |
6.3.2.2.3 Resource Standard Methods
6.3.2.2.3.1 POST
This method shall support the URI query parameters specified in table 6.3.2.2.3.1-1.
Table 6.3.2.2.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 6.3.2.2.3.1-2 and the response data structures and response codes specified in table 6.3.2.2.3.1-3.
Table 6.3.2.2.3.1-2: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
EASDiscoverySubscription |
M |
1 |
Create an Individual EAS Discovery Subscription resource. |
Table 6.3.2.2.3.1-3: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
EASDiscoverySubscription |
M |
1 |
201 Created |
Successful case. An Individual EAS Discovery Subscription resource was successfully created and a representation of the created resource is returned in the response body. The URI of the created resource shall be returned in an HTTP "Location" 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 6.3.2.2.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}/eees-easdiscovery/<apiVersion>/subscriptions/{subscriptionId} |
6.3.2.2.4 Resource Custom Operations
None.
6.3.2.3 Resource: Individual EAS Discovery Subscription
6.3.2.3.1 Description
This resource represents of an Individual EAS Discovery Subscription resource managed by the EES.
6.3.2.3.2 Resource Definition
Resource URI: {apiRoot}/eees-easdiscovery/<apiVersion>/subscriptions/{subscriptionId}
This resource shall support the resource URI variables defined in table 6.3.2.3.2-1.
Table 6.3.2.3.2-1: Resource URI variables for this resource
Name |
Data Type |
Definition |
apiRoot |
string |
See clause 6.1. |
subscriptionId |
string |
The identifier of the individual EAS discovery subscription. |
6.3.2.3.3 Resource Standard Methods
6.3.2.3.3.1 PUT
This method shall support the URI query parameters specified in table 6.3.2.3.3.1-1.
Table 6.3.2.3.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 6.3.2.3.3.1-2 and the response data structures and response codes specified in table 6.3.2.3.3.1-3.
Table 6.3.2.3.3.1-2: Data structures supported by the PUT Request Body on this resource
Data type |
P |
Cardinality |
Description |
EASDiscoverySubscription |
M |
1 |
An individual EAS discovery subscription resource to be updated. |
Table 6.3.2.3.3.1-3: Data structures supported by the PUT Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
EASDiscoverySubscription |
M |
1 |
200 OK |
The Individual EAS Discovery Subscription resource was successfully updated and a representation of the updated resource is returned in the response body. |
n/a |
204 No Content |
The Individual EAS Discovery Subscription resource was successfully updated and no content is returned in the response body. |
||
n/a |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that the SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
n/a |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that the SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
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 6.3.2.3.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 EES. |
Table 6.3.2.3.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 EES. |
6.3.2.3.3.2 DELETE
This method shall support the URI query parameters specified in table 6.3.2.3.3.2-1.
Table 6.3.2.3.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 6.3.2.3.3.2-2 and the response data structures and response codes specified in table 6.3.2.3.3.2-3.
Table 6.3.2.3.3.2-2: Data structures supported by the DELETE Request Body on this resource
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.3.2.3.3.2-3: Data structures supported by the DELETE Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
204 No Content |
The targeted Individual EAS Discovery Subscription resource was successfully deleted. |
||
n/a |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that the SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
n/a |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that the SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
NOTE: The manadatory HTTP error status code for the DELETE method listed in Table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |
Table 6.3.2.3.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 EES. |
Table 6.3.2.3.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 EES. |
6.3.2.3.3.3 PATCH
This method shall support the URI query parameters specified in the table 6.3.2.3.3.3-1.
Table 6.3.2.3.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 6.3.2.3.3.3-2 and the response data structures and response codes specified in table 6.3.2.3.3.3-3.
Table 6.3.2.3.3.3-2: Data structures supported by the PATCH Request Body on this resource
Data type |
P |
Cardinality |
Description |
EasDiscoverySubscriptionPatch |
M |
1 |
Contains the parameters to request the modification of an existing Individual EAS Discovery Subscription resource. |
Table 6.3.2.3.3.3-3: Data structures supported by the PATCH Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
EasDiscoverySubscription |
M |
1 |
200 OK |
The Individual EAS Discovery Subscription resource was successfully modified and a representation of the modified resource is returned in the response body. |
n/a |
204 No Content |
The Individual EAS Discovery Subscription resource was successfully modified and no content is returned in the response body. |
||
n/a |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that the SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
n/a |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that the SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
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 6.3.2.3.3.3-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 EES. |
Table 6.3.2.3.3.3-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 EES. |
6.3.2.3.4 Resource Custom Operations
None.
6.3.2.4 Resource: EAS Profiles
6.3.2.4.1 Description
This resource represents the collection of EAS Profiles managed by the EES.
6.3.2.4.2 Resource Definition
Resource URI: {apiRoot}/eees-easdiscovery/<apiVersion>/eas-profiles
This resource shall support the resource URI variables defined in table 6.3.2.2.2-1.
Table 6.3.2.2.2-1: Resource URI variables for this resource
Name |
Data Type |
Definition |
apiRoot |
string |
See clause 6.1 |
6.3.2.4.3 Resource Standard Methods
None.
6.3.2.4.4 Resource Custom Operations
6.3.2.4.4.1 Overview
Resource custom operations defined for this resource are summarized in table 6.3.2.4.4.1-1.
Table 6.3.2.4.4.1-1: Custom operations
Operation name |
Custom operaration URI |
Mapped HTTP method |
Description |
Request-Discovery |
eees-easdiscovery/<apiVersion>/eas-profile /request-discovery |
POST |
Request EAS discovery information |
6.3.2.4.4.2 Operation: RequestDiscovery
6.3.2.4.4.2.1 Description
The custom operation allows a service consumer (e.g. EEC, EAS, EES) to request EAS discovery, as specified in 3GPP TS 23.558 [2], from the EES.
6.3.2.4.4.2.2 Operation Definition
This operation shall support the request of data structures specified in table 6.3.2.4.4.2.2-1 and the response data structure and response codes specified in table 6.3.2.4.4.2.2-2.
Table 6.3.2.4.4.2.2-1: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
EASDiscoveryReq |
M |
1 |
Contains the necessary information to request EAS discovery. |
Table 6.3.2.4.4.2.2-2: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
EASDiscoveryResp |
M |
1 |
200 OK |
The requested EAS discovery information was successfully returned. |
n/a |
204 No Content |
The processing of the request is successful but no matching EAS was found. |
||
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. |
6.3.3 Custom operations without associated resources
There are no custom operations without associated resources defined for this API in this release of the specification.
6.3.4 Notifications
6.3.4.1 General
Table 6.3.4.1-1: Notifications overview
Notification |
Callback URI |
HTTP method or custom operation |
Description (service operation) |
EAS Discovery Notification |
{notificationDestination} |
POST |
Notifies a subscribed EEC about EAS discovery information.. |
6.3.4.2 EAS Discovery Notification
6.3.4.2.1 Description
EAS Discovery notification is used by the EES to notify an EEC on EAS discovery information. The EEC may subscribe to the EAS discovery information as a pre-condition for receiving notification.
6.3.4.2.2 Target URI
The Callback URI "{notificationDestination}" shall be used with the callback URI variables defined in table 8.6.4.2.2-1.
Table 6.3.4.2.2-1: Callback URI variables
Name |
Definition |
notificationDestination |
String formatted as URI with the Callback Uri. |
6.3.4.2.3 Standard Methods
6.3.4.2.3.1 POST
This method shall support the request data structures specified in table 6.3.4.2.3.1-1 and the response data structures and response codes specified in table 6.3.4.2.3.1-2.
Table 6.3.4.2.3.1-1: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
EasDiscoveryNotification |
M |
1 |
Notification of EAS discovery information. |
Table 6.3.4.2.3.1-2: 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 [6]. |
||
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 [6]. |
||
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 6.3.4.2.3.1-3: 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 EAS towards which the notification should be redirected. |
Table 6.3.4.2.3.1-4: 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 EAS towards which the notification should be redirected. |
6.3.5 Data Model
6.3.5.1 General
This clause specifies the application data model supported by the Eees_EASDiscovery API.
Table 6.3.5.1-1 specifies the data types defined specifically for the Eees_EASDiscovery API service.
Table 6.3.5.1-1: Eees_EASDiscovery API specific Data Types
Data type |
Section defined |
Description |
Applicability |
EasDiscoveryReq |
6.3.5.2.2 |
||
EasDiscoveryResp |
6.3.5.2.3 |
||
EasDiscoverySubscription |
6.3.5.2.4 |
||
EasDiscoveryNotification |
6.3.5.2.5 |
||
EasDiscoveryFilter |
6.3.5.2.6 |
||
EasCharacteristics |
6.3.5.2.7 |
||
DiscoveredEas |
6.3.5.2.8 |
||
EasDynamicInfoFilter |
6.3.5.2.9 |
Table 6.3.5.1-2 specifies data types re-used by the Eees_EASDiscovery API service.
Table 6.3.5.1-2: Re-used Data Types
Data type |
Reference |
Comments |
Applicability |
TimeWindow |
3GPP TS 29.122 [3] |
||
DurationSec |
3GPP TS 29.122 [3] |
||
LocationArea5G |
3GPP TS 29.122 [3] |
||
ACProfile |
clause 6.2.5.2.3 |
||
LocationInfo |
3GPP TS 29.122 [3] |
||
EndPoint |
3GPP TS 29.558 [4] |
||
EASProfile |
3GPP TS 29.558 [4] |
||
Dnai |
3GPP TS 29.571 [5] |
||
RouteToLocation |
3GPP TS 29.571 [5] |
||
Gpsi |
3GPP TS 29.571 [5] |
Used to identify a UE. |
|
Uri |
3GPP TS 29.122 [3] |
6.3.5.2 Structured data types
6.3.5.2.1 Introduction
This clause defines the structures to be used in resource representations.
6.3.5.2.2 Type: EasDiscoveryReq
Table 6.3.5.2.2-1: Definition of type EasDiscoveryReq
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
requestorId |
RequestorId |
M |
1 |
Represents a unique identifier of the requestor (e.g. EEC, EAS, EES). |
|
ueId |
string |
O |
0..1 |
Represents the identifier of the UE. |
|
easDiscoveryFilter |
EasDiscoveryFilter |
O |
0..1 |
Contains EAS characteristics |
|
eecSvcContinuity |
string |
O |
0..1 |
Contains service continuity support; indicates EEC supported ACR scenarios |
|
eesSvcContinuity |
String |
O |
0..1 |
Contains service continuity support; indicates EES supported ACR scenarios |
|
easSvcContinuity |
string |
O |
0..1 |
Contains service continuity support; indicates EAS supported ACR scenarios |
|
locInf |
LocationInfo |
O |
0..1 |
Represents location information of the UE. |
|
easTDnais |
array(Dnai) |
O |
1..N |
Contains the target DNAI information which can be associated with potential target-EAS(s) |
6.3.5.2.3 Type: EasDiscoveryResp
Table 6.3.5.2.3-1: Definition of type EasDiscoveryResp
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
discoveredEas |
array(DiscoveredEas) |
M |
1..N |
List of EAS discovery information |
6.3.5.2.4 Type: EasDiscoverySubscription
Table 6.3.5.2.4-1: Definition of type EasDiscoverySubscription
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
eecId |
string |
M |
1 |
Represents a unique identifier of the EEC. |
|
ueId |
Gpsi |
O |
0..1 |
Represents the identifier of the UE. |
|
easEventType |
EASDiscEventIDs |
M |
1 |
Event type for which the EEC should be notified; |
|
easDiscoveryFilter |
EasDiscoveryFilter |
O |
0..1 |
EAS characteristics filter; Applicable when easEventType is set to "EAS_AVAILABILITY_CHANGE" event |
|
easDynInfoFilter |
EasDynamicInfoFilter |
O |
0..1 |
EAS dynamic information changes filter; Applicable when easEventType is set to "EAS_DYNAMIC_INFO_CHANGE" event |
|
eecSvcContinuity |
array(ACRScenario) |
O |
0..1 |
Service continuity support; indicates EEC supported ACR scenarios |
|
notificationDestination |
Uri |
M |
1 |
URI where the EAS discovery notification should be delivered to. This attribute shall be present in HTTP POST message to EES. |
|
expTime |
DateTime |
O |
0..1 |
Expiration time of the subscription. If the expiration time is not present, then it indicates that the EEC subscription never expires. |
|
requestTestNotification |
boolean |
O |
0..1 |
Set to true by Subscriber to request the EES to send a test notification as defined in clause 6.1. 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. |
Notification_websocket |
suppFeat |
SupportedFeatures |
C |
0..1 |
Represents a list of Supported features used as described in clause 6.3.7. Shall be present in the HTTP POST request/response; |
6.3.5.2.5 Type: EasDiscoveryNotification
Table 6.3.5.2.5-1: Definition of type EasDiscoveryNotification
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
subId |
string |
M |
1 |
String identifying the individual subscription for which the service provisioning notification is delivered. |
|
eventType |
EASDiscEventIDs |
M |
1 |
Event type for which the notification is delivered; |
|
discoveredEas |
array(DiscoveredEas) |
M |
1..N |
List of EAS discovery information |
6.3.5.2.6 Type: EasDiscoveryFilter
Table 6.3.5.2.6-1: Definition of type EasDiscoveryFilter
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
acChars |
array(ACCharacteristics) |
O |
1..N |
AC description for which an EAS is needed |
|
easChars |
array(EasCharacteristics) |
O |
1..N |
Required EAS characteristics |
|
NOTE 1: Either acChars or easChars shall be present. NOTE 2: prefEcsps from the ACProfile shall not be present. |
6.3.5.2.7 Type: EasCharacteristics
Table 6.3.5.2.7-1: Definition of type EasCharacteristics
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
easId |
string |
O |
0..1 |
The application identifier of the EAS, e.g. FQDN, URI. |
|
easProvId |
string |
O |
0..1 |
EAS provider identifier |
|
easType |
string |
O |
0..1 |
EAS type |
|
easSched |
TimeWindow |
O |
0..1 |
EAS availability schedule |
|
svcArea |
LocationArea5G |
O |
0..1 |
Service availability area (geographical and topological) |
|
easSvcContinuity |
array(ACRScenario) |
O |
0..1 |
The ACR scenarios required by the EAS for service continuity. If this attribute is not present, then the EAS does not require to support service continuity. |
|
svcPermLevel |
string |
O |
0..1 |
Service permissions level |
|
svcFeats |
array(string) |
O |
1..N |
Service features |
|
NOTE: Must include at least one optional IE |
6.3.5.2.8 Type: DiscoveredEas
Table 6.3.5.2.8-1: Definition of type DiscoveredEas
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
eas |
EASProfile |
M |
1 |
Contains an EAS matching the discovery request filters |
|
lifeTime |
DateTime |
O |
0..1 |
Indicates the time duration for which the EAS information is valid and supposed to be cached in the EEC. |
6.3.5.2.9 Type: EasDynamicInfoFilter
Table 6.3.5.2.9-1: Definition of type EasDynamicInfoFilter
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
dynInfoFilter |
array(EasDynamicInfoFilterData) |
M |
1 |
List of EAS dynamic information required by the EEC per EAS |
6.3.5.2.10 Type: EasDynamicInfoFilterData
Table 6.3.5.2.10-1: Definition of type EasDynamicInfoFilterData
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
easId |
string |
M |
1 |
The application identifier of the EAS, e.g. FQDN, URI. |
|
easStatus |
boolean |
O |
0..1 |
Notify if EAS status changed |
|
easAcIds |
boolean |
O |
0..1 |
Notify if list of AC identifiers changed |
|
easDesc |
boolean |
O |
0..1 |
Notify if EAS description changed |
|
easPt |
boolean |
O |
0..1 |
Notify if EAS endpoint changed |
|
easFeature |
boolean |
O |
0..1 |
Notify if EAS feature changed |
|
easSchedule |
boolean |
O |
0..1 |
Notify if EAS schedule changed |
|
svcArea |
boolean |
O |
0..1 |
Notify if EAS service area changed |
|
svcKpi |
boolean |
O |
0..1 |
Notify if EAS KPIs changed |
|
svcCont |
boolean |
O |
0..1 |
Notify if EAS supported ACR changed |
6.3.5.2.11 Type: ACCharacteristics
Table 6.3.5.2.11-1: Definition of type ACCharacteristics
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
acProf |
ACProfile |
M |
1 |
Profiles of ACs for which the EEC provides edge enabling services. |
6.3.5.2.12 Type: EasDiscoverySubscriptionPatch
Table 6.3.5.2.12-1: Definition of type EasDiscoverySubscriptionPatch
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
easDiscoveryFilter |
EasDiscoveryFilter |
O |
0..1 |
EAS characteristics filter; Applicable when easEventType is set to "EAS_AVAILABILITY_CHANGE" event |
|
easDynInfoFilter |
EasDynamicInfoFilter |
O |
0..1 |
EAS dynamic information changes filter; Applicable when easEventType is set to "EAS_DYNAMIC_INFO_CHANGE" event |
|
eecSvcContinuity |
array(ACRScenario) |
O |
0..1 |
Service continuity support; indicates EEC supported ACR scenarios |
|
expTime |
DateTime |
O |
0..1 |
Expiration time of the subscription. If the expiration time is not present, then it indicates that the EEC subscription never expires. |
|
easEventType |
EASDiscEventIDs |
O |
0..1 |
Event type for which the EEC should be notified; |
6.3.5.2.13 Type: RequestorId
Table 8.6.5.2.13-1: Definition of type RequestorId
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
EesId |
string |
C |
0..1 |
The identifier of the EES (e.g. S-EES). |
|
EasId |
string |
C |
0..1 |
The application identifier of the EAS (e.g. S-EAS), e.g. FQDN, URI. |
|
eecId |
string |
C |
0..1 |
The identifier of the EEC. |
|
NOTE: Either the "eecId" attribute, the "EesId" attribute or the "EasId" attribute shall be provided, they are mutually exclusive. |
6.3.5.3 Simple data types and enumerations
6.3.5.3.1 Introduction
This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.
6.3.5.3.2 Simple data types
The simple data types defined in table 6.3.5.3.2-1 shall be supported.
Table 6.3.5.3.2-1: Simple data types
Type Name |
Type Definition |
Description |
Applicability |
6.3.5.3.3 Enumeration: EASDiscEventIDs
The enumeration ACREventIDs represents the ACR events supported. It shall comply with the provisions defined in table 6.3.5.3.3-1.
Table 6.3.5.3.3-1: Enumeration ACREventIDs
Enumeration value |
Description |
Applicability |
EAS_AVAILABILITY_CHANGE |
Represents the EAS availability change event |
|
EAS_DYNAMIC_INFO_CHANGE |
Represents the EAS dynamic information change event |
6.3.6 Error Handling
6.3.6.1 General
For the Eees_EASDiscovery API, HTTP error responses shall be supported as specified in clause 5.2.6 of 3GPP TS 29.122 [3]. Protocol errors and application errors specified in clause 5.2.6 of 3GPP TS 29.122 [3] shall be supported for the HTTP status codes specified in table 5.2.6-1 of 3GPP TS 29.122 [3].
In addition, the requirements in the following clauses are applicable for the Eees_EASDiscovery API.
6.3.6.2 Protocol Errors
No specific protocol errors for the Eees_EASDiscovery API are specified.
6.3.6.3 Application Errors
The application errors defined for the Eees_EASDiscovery service are listed in Table 6.3.6.3-1.
Table 6.3.6.1-1: Application errors
Application Error |
HTTP status code |
Description |
REGISTRATION_REQUIRED |
403 Forbidden |
Indicates that the registration is required for the EEC to perform the operation. |
6.3.7 Feature negotiation
General feature negotiation procedures are described in clause 6.1. Table 6.3.7-1 lists the supported features for Eees_EASDiscovery API.
Table 6.3.7-1: Supported Features
Feature number |
Feature Name |
Description |
1 |
Notification_test_event |
Testing of notification connection is supported according to clause 6.1. |
2 |
Notification_websocket |
The delivery of notifications over Websocket is supported according to clause 6.1. This feature requires that the Notification_test_event feature is also supported. |
6.4 Eees_ACREvents API
6.4.1 API URI
The request URI used in each HTTP request from the EEC towards the EES shall have the structure as defined in clause 6.1 with the following clarifications:
– The <apiName> shall be "eees-acrevents".
– The <apiVersion> shall be "v1".
– The <apiSpecificResourceUriPart> shall be set as described in clause 6.4.2.
6.4.2 Resources
6.4.2.1 Overview
Figure 6.4.2.1-1: Resource URI structure of the Eees_ACREvents API
Table 6.4.2.1-1 provides an overview of the resources and applicable HTTP methods.
Table 6.4.2.1-1: Resources and methods overview
Resource name |
Resource URI |
HTTP method or custom operation |
Description |
ACR events subscriptions |
/subscriptions |
POST |
Creates a new individual ACR events subscription. |
Individual ACR events subscription |
/subscriptions/{subscriptionId} |
PUT |
Updates an existing individual ACR events subscription identified by the subscriptionId. |
DELETE |
Deletes an existing individual ACR events subscription identified by the subscriptionId. |
||
PATCH |
Partially updates an existing individual ACR events subscription identified by the subscriptionId. |
6.4.2.2 Resource: ACR events subscriptions
6.4.2.2.1 Description
This resource represents a collection of ACR related events subscriptions with an EES.
6.4.2.2.2 Resource Definition
Resource URI: {apiRoot}/eees-acrevents/<apiVersion>/subscriptions
This resource shall support the resource URI variables defined in table 6.4.2.2.2-1.
Table 6.4.2.2.2-1: Resource URI variables for this resource
Name |
Data Type |
Definition |
apiRoot |
string |
See clause 6.4.1. |
6.4.2.2.3 Resource Standard Methods
6.4.2.2.3.1 POST
This method creates a new subscription. This method shall support the URI query parameters specified in table 6.4.2.2.3.1-1.
Table 6.4.2.2.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 6.4.2.2.3.1-2 and the response data structures and response codes specified in table 6.4.2.2.3.1-3.
Table 6.4.2.2.3.1-2: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
ACREventsSubscription |
M |
1 |
Create an Individual ACR events subscription resource. |
Table 6.4.2.2.3.1-3: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
ACREventsSubscription |
M |
1 |
201 Created |
Individual ACR events subscription resource created successfully. The URI of the created resource shall be returned in the "Location" HTTP header |
NOTE: The manadatory HTTP error status code for the POST method listed in Table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |
Table 6.4.2.2.3.1-4: Headers supported by the POST method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.4.2.2.3.1-5: 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}/eees-acrevents/<apiVersion>/subscriptions/{subscriptionId} |
6.4.2.2.4 Resource Custom Operations
None.
6.4.2.3 Resource: Individual ACR events subscription
6.4.2.3.1 Description
This resource represents modification or deletion of an Individual ACR events subscription resource.
6.4.2.3.2 Resource Definition
Resource URI: {apiRoot}/eees-acrevents/<apiVersion>/subscriptions/{subscriptionId}
This resource shall support the resource URI variables defined in table 6.4.2.3.2-1.
Table 6.4.2.3.2-1: Resource URI variables for this resource
Name |
Data Type |
Definition |
apiRoot |
string |
See clause 6.4.1. |
subscriptionId |
string |
The identifier of a specific individual ACR events subscription. |
6.4.2.3.3 Resource Standard Methods
6.4.2.3.3.1 PUT
This method updates the individual ACR events subscription resource by completely replacing the existing subscription data (except subscriptionId). This method shall support the URI query parameters specified in table 6.4.2.3.3.1-1.
Table 6.4.2.3.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 6.4.2.3.3.1-2 and the response data structures and response codes specified in table 6.4.2.3.3.1-3.
Table 6.4.2.3.3.1-2: Data structures supported by the PUT Request Body on this resource
Data type |
P |
Cardinality |
Description |
ACREventsSubscription |
M |
1 |
An individual ACR events subscription resource to be updated. |
Table 6.4.2.3.3.1-3: Data structures supported by the PUT Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
ACREventsSubscription |
M |
1 |
200 OK |
An individual ACR events subscription resource updated successfully and the ACREventsSubscription data shall be included in the response. |
n/a |
204 No Content |
An individual ACE events subscription resource updated 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 EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that the SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
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 EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that the SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
NOTE: The manadatory HTTP error status code for the PUT method listed in Table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |
Table 6.4.2.3.3.1-4: Headers supported by the PUT method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.4.2.3.3.1-5: Headers supported by the 200 response code on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.4.2.3.3.1-6: Links supported by the 200 Response Code on this endpoint
Name |
Resource name |
HTTP method or custom operation |
Link parameter(s) |
Description |
n/a |
Table 6.4.2.3.3.1-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 EES. |
Table 6.4.2.3.3.1-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 EES. |
6.4.2.3.3.2 DELETE
This method terminates an existing individual ACR events subscription. This method shall support the URI query parameters specified in table 6.4.2.3.3.2-1.
Table 6.4.2.3.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 6.4.2.3.3.2-2 and the response data structures and response codes specified in table 6.4.2.3.3.2-3.
Table 6.4.2.3.3.2-2: Data structures supported by the DELETE Request Body on this resource
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.4.2.3.3.2-3: Data structures supported by the DELETE Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
204 No Content |
An individual individual ACR events subscription resource deleted successfully. |
||
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 EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that the SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
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 EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that the SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
NOTE: The manadatory HTTP error status code for the DELETE method listed in Table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |
Table 6.4.2.3.3.2-4: Headers supported by the DELETE method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.4.2.3.3.2-5: Headers supported by the 204 response code on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.4.2.3.3.2-6: 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 EES. |
Table 6.4.2.3.3.2-7: 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 EES. |
6.4.2.3.3.3 PATCH
This method partially updates the individual ACR events subscription resource. This method shall support the URI query parameters specified in table 6.4.2.3.3.3-1.
Table 6.4.2.3.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 6.4.2.3.3.3-2 and the response data structures and response codes specified in table 6.4.2.3.3.3-3.
Table 6.4.2.3.3.3-2: Data structures supported by the PATCH Request Body on this resource
Data type |
P |
Cardinality |
Description |
ACREventsSubscriptionPatch |
M |
1 |
An individual ACR events subscription resource to be updated. |
Table 6.4.2.3.3.3-3: Data structures supported by the PATCH Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
ACREventsSubscription |
M |
1 |
200 OK |
An individual ACR events subscription resource updated successfully and the ACREventsSubscription data shall be included in the response. |
n/a |
204 No Content |
An individual ACE events subscription resource updated 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 EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that the SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
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 EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [3] with the difference that the SCEF is replaced by the EES and the SCS/AS is replaced by the EEC. |
||
NOTE: The manadatory HTTP error status code for the PATCH method listed in Table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |
Table 6.4.2.3.3.3-4: Headers supported by the PATCH method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.4.2.3.3.3-5: Headers supported by the 200 response code on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.4.2.3.3.3-6: Links supported by the 200 Response Code on this endpoint
Name |
Resource name |
HTTP method or custom operation |
Link parameter(s) |
Description |
n/a |
Table 6.4.2.3.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 EES. |
Table 6.4.2.3.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 EES. |
6.4.2.3.4 Resource Custom Operations
None.
6.4.3 Custom operations without associated resources
None.
6.4.4 Notifications
6.4.4.1 General
Table 6.4.4.1-1: Notifications overview
Notification |
Callback URI |
HTTP method or custom operation |
Description (service operation) |
ACR Information Notification |
{notificationDestination} |
POST |
Notifies EEC for the ACR information notification. |
6.4.4.2 ACR Information Notification
6.4.4.2.1 Description
ACR Information Notification is used by the EES to notify an EEC for the following ACR information:
– target information, i.e. the details of the selected T-EAS, if required, the selected T-EES, during the ACR procedures and, if required, the identifier of the AC;
– ACR complete events.
6.4.4.2.2 Notification definition
The POST method shall be used by the EES for sending notifications and the notification destination shall be the callback URI as provided by the EEC during the ACR events subscription.
Callback URI: {notificationDestination}
This method shall support the URI query parameters specified in table 6.4.4.2.2-1.
Table 6.4.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 6.4.4.2.2-2 and the response data structures and response codes specified in table 6.4.4.2.2-3.
Table 6.4.4.2.2-2: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
ACRInfoNotification |
M |
1 |
Notification of ACR information. |
Table 6.4.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. |
||
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. |
6.4.5 Data Model
6.4.5.1 General
This clause specifies the application data model supported by the Eees_ACREvents API.
Table 6.4.5.1-1 specifies the data types defined specifically for the Eees_ACREvents API service.
Table 6.4.5.1-1: Eees_ACREvents API specific Data Types
Data type |
Section defined |
Description |
Applicability |
ACREventsSubscription |
6.4.5.2.2 |
||
ACRInfoNotification |
6.4.5.2.3 |
||
ACREventIDs |
6.4.5.3.3 |
Table 6.4.5.1-2 specifies data types re-used by the Eees_ACREvents API service.
Table 6.4.5.1-2: Re-used Data Types
Data type |
Reference |
Comments |
Applicability |
DateTime |
3GPP TS 29.122 [3] |
||
Uri |
3GPP TS 29.122 [3] |
||
WebsockNotifConfig |
3GPP TS 29.122 [3] |
||
SupportedFeatures |
3GPP TS 29.571 [5] |
||
EDNConfigInfo |
Clause 8.1.5.2.7 |
||
DiscoveredEas |
Clause 6.3.5.2.8 |
||
ImplicitRegDetail |
3GPP TS 29.558 [4] |
6.4.5.2 Structured data types
6.4.5.2.1 Introduction
6.4.5.2.2 Type: ACREventsSubscription
Table 6.4.5.2.2-1: ACREventsSubscription
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. |
|
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. |
|
easIds |
array(string) |
M |
1..N |
The list of application identifiers of the EASs, e.g. FQDN, URI. |
|
acIds |
array(string) |
O |
1..N |
The list of identifier of the AC(s) (NOTE) |
|
eventIds |
ACREventIDs |
M |
1 |
Specifies the events for which EEC is subscribing. |
|
notificationDestination |
Uri |
M |
1 |
URI where the ACR Information Notification should be delivered to. |
|
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. |
|
NOTE: If acIds attribute is not included, it implies that the subscription corresponds to all ACs that can be served by the EAS(s) included this message. |
6.4.5.2.3 Type: ACRInfoNotification
Table 6.4.5.2.3-1: ACRInfoNotification
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
subId |
string |
M |
1 |
String identifying the Individual ACR events subscription for which the ACT Information notification is delivered. |
|
easId |
string |
M |
1 |
The application identifier of the EAS, e.g. FQDN, URI. |
|
eventId |
ACREventIDs |
M |
1 |
Specifies the events for which notification is sent |
|
acId |
string |
O |
0..1 |
Contains the identifier of the AC. |
|
trgtInfo (NOTE 1) |
TargetInfo |
O |
0..1 |
Details of the selected T-EAS and the T-EES. |
|
acrStatus |
ACRCompleteEventInfo |
C |
0..1 |
Details of a completed ACR and its result. This attribute shall be included when Event ID indicates ‘ACR_COMPLETE’ event |
|
eecCtxtReloc (NOTE 3) |
EecCtxtRelocStatus |
O |
0..1 |
Specifies the registration id and expiry time of the registration. |
|
NOTE 1: This attribute shall be included when Event ID indicates ‘TARGET_INFORMATION’ event NOTE 2: This attribute shall be included when the ACRRes attribute indicates failure. NOTE 3: This attribute shall be included when eventId indicates ‘ACR_COMPLETE’ event and EEC context relocation was attempted. |
6.4.5.2.4 Type: TargetInfo
Table 6.4.5.2.4-1: TargetInfo
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
trgetEASInfo |
DiscoveredEas |
M |
1 |
EAS discovery information. |
|
trgetEESInfo |
EDNConfigInfo |
O |
0..1 |
Provides EDN configuration information. This attribute shall be included only if the selected T-EES is different from the S-EES. |
6.4.5.2.5 Type: ACREventsSubscriptionPatch
Table 6.4.5.2.5-1: ACREventsSubscriptionPatch
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
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. |
|
easIds |
array(string) |
O |
1..N |
The list of application identifiers of the EASs, e.g. FQDN, URI. |
|
eventIds |
ACREventIDs |
O |
0..1 |
Specifies the events for which EEC is subscribing. |
|
notificationDestination |
Uri |
O |
0..1 |
URI where the ACR Information Notification should be delivered to. This attribute shall be present in HTTP POST message to EES. |
6.4.5.2.6 Type: EecCtxtRelocStatus
Table 6.4.5.2.6-1: EecCtxtRelocStatus
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
implReg |
ImplicitRegDetails |
O |
0..1 |
Provides implicit registration details (NOTE) |
|
NOTE 1: This attribute shall be included when the S-EES has received it in EEC Context Push response. |
6.4.5.2.7 Type: ACRCompleteEventInfo
Table 6.4.5.2.7-1: ACRCompleteEventInfo
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
acrRes |
boolean |
M |
1 |
Indicates whether the ACR is successful or failure |
|
tEasEndpoint |
EndPoint |
M |
1 |
Contains the endpoint address of the T-EAS to which an ACR has been performed. |
|
failReason |
string |
C |
0..1 |
Indicates the cause information for the failure This attribute shall be included when the acrRes attribute indicates failure |
6.4.5.3 Simple data types and enumerations
6.4.5.3.1 Introduction
This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.
6.4.5.3.2 Simple data types
The simple data types defined in table 6.4.5.3.2-1 shall be supported.
Table 6.4.5.3.2-1: Simple data types
Type Name |
Type Definition |
Description |
Applicability |
6.4.5.3.3 Enumeration: ACREventIDs
The enumeration ACREventIDs represents the ACR events supported. It shall comply with the provisions defined in table 6.4.5.3.3-1.
Table 6.4.5.3.3-1: Enumeration ACREventIDs
Enumeration value |
Description |
Applicability |
TARGET_INFORMATION |
||
ACR_COMPLETE |
6.4.6 Error Handling
General error handling are described in clause 6.1.
6.4.7 Feature negotiation
General feature negotiation procedures are described in clause 6.1. Table 6.4.7-1 lists the supported features for Eees_ACREvents API.
Table 6.4.7-1: Supported Features
Feature number |
Feature Name |
Description |
6.5 Eees_AppContextRelocation API
6.5.1 Introduction
The Eees_AppContextRelocation service shall use the Eees_AppContextRelocation API.
The API URI of the Eees_AppContextRelocation API shall be:
{apiRoot}/<apiName>/<apiVersion>
The request URI used in HTTP requests shall have the Resource URI structure defined in clause 6.1, i.e:
apiRoot}/<apiName>/<apiVersion>/<apiSpecificResourceUriPart>
with the following components:
– The {apiRoot} shall be set as described in clause 6.1.
– The <apiName> shall be "eees-appctxtreloc".
– The <apiVersion> shall be "v1".
– The <apiSpecificResourceUriPart> shall be set as described in clause 6.1.
6.5.2 Resources
There are no resources defined for this API in this release of the specification.
6.5.3 Custom Operations without associated resources
6.5.3.1 Overview
The structure of the custom operation URIs of the Eees_AppContextRelocation API is shown in Figure 6.5.3.1-1.
Figure 6.5.3.1-1: Resource URI structure of the Eees_AppContextRelocation API
Table 6.5.3.1-1 provides an overview of the custom operations and applicable HTTP methods defined for the Eees_AppContextRelocation API.
Table 6.5.3.1-1: Custom operations without associated resources
Operation name |
Custom operation URI |
Mapped HTTP method |
Description |
Determine |
/determine |
POST |
EES or EAS determines if ACR is needed and may initiate the procedure |
Initiate |
/initiate |
POST |
EES initiates the requested ACR procedure |
Declare |
/declare |
POST |
EAS declares the selected target EAS and the associated information. |
NOTE 1: Based on SA3 specified security mechanisms for EDGE-1 and EDGE-3 interfaces, the EES can identify the initiator of the API (EEC or EAS) and apply the appropriate security procedures as specified in 3GPP TS 33.558 [7].
NOTE 2: The same service API can be implemented on two different interfaces, i.e. EDGE-1 and EDGE-3, which are for separate endpoints, i.e. EEC and EAS.
6.5.3.2 Operation: Determine
6.5.3.2.1 Description
This custom operation allows the EEC or the EAS to request that the EES evaluates if ACR is needed and subsequently initiate the ACR procedure if required.
6.5.3.2.2 Operation Definition
This operation shall support the request data structures, the response data structures and response codes specified in tables 6.5.3.2.2-1 and 6.5.3.2.2-2.
Table 6.5.3.2.2-1: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
AcrDeterReq |
M |
1 |
Information about the requestor and requested ACR operation |
Table 6.5.3.2.2-2: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
204 No Content |
Successful case. The ACR request is successfully received and processed. |
||
n/a |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing an alternative target URI located in an alternative EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [2]. |
||
n/a |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing an alternative target URI located in an alternative EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [2] |
||
NOTE: The manadatory HTTP error status code for the POST method listed in Table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |
Table 6.5.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 EES. |
Table 6.5.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 EES. |
6.5.3.3 Operation: Initiate
6.5.3.3.1 Description
This custom operation allows the EEC to request initiation of an ACR procedure.
6.5.3.3.2 Operation Definition
This operation shall support the request data structures and the response data structures and response codes specified in tables 6.5.3.3.2-1 and 6.5.3.3.2-2.
Table 6.5.3.3.2-1: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
AcrInitReq |
M |
1 |
Information about the requestor and requested ACR operation |
Table 6.5.3.3.2-2: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
204 No Content |
Successful case. The ACR request is successfully received and processed. |
||
n/a |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing an alternative target URI located in an alternative EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [2]. |
||
n/a |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing an alternative target URI located in an alternative EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [2] |
||
NOTE: The manadatory HTTP error status code for the POST method listed in Table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |
Table 6.5.3.3.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 EES. |
Table 6.5.3.3.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 EES. |
6.5.3.4 Operation: Declare
6.5.3.4.1 Description
This custom operation allows an S-EAS to declare the selected target EAS and the associated information.
6.5.3.4.2 Operation Definition
This operation shall support the request data structures and the response data structures and response codes specified in tables 6.5.3.4.2-1 and 6.5.3.4.2-2.
Table 6.5.3.4.2-1: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
AcrDecReq |
M |
1 |
Contains the selected target EAS information. |
Table 6.5.3.4.2-2: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
204 No Content |
Successful case. The selected target EAS information is successfully received. |
||
n/a |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing an alternative target URI located in an alternative EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [2]. |
||
n/a |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing an alternative target URI located in an alternative EES. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [2] |
||
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 6.5.3.4.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 EES. |
Table 6.5.3.4.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 EES. |
6.5.4 Notifications
None
6.5.5 Data Model
6.5.5.1 General
This clause specifies the application data model supported by the Eees_AppContextRelocation API.
Table 6.5.5.1-1 specifies the data types defined specifically for the Eees_AppContextRelocation API service.
Table 6.5.5.1-1: Eees_AppContextRelocation API specific Data Types
Data type |
Section defined |
Description |
Applicability |
AcrDecReq |
6.5.5.2.4 |
||
AcrDetermReq |
6.5.5.2.2 |
||
AcrInitReq |
6.5.5.2.3 |
||
EecCtxtReloc |
6.5.5.2.5 |
Table 6.5.5.1-2 specifies data types re-used by the Eees_AppContextRelocation API service from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Eees_AppContextRelocation.
Table 6.5.5.1-2: Re-used Data Types
Data type |
Reference |
Comments |
Applicability |
RouteToLocation |
3GPP TS 29.571 [5] |
Represent the N6 traffic routing information and/or routing profile ID for a DNAI. |
|
EndPoint |
3GPP TS 29.558 [4] |
Represents the endpoint information of an EAS. |
|
Gpsi |
3GPP TS 29.571 [5] |
Represents a GPSI. |
6.5.5.2 Structured data types
6.5.5.2.1 Introduction
This clause defines the data structures to be used in resource representations.
6.5.5.2.2 Type: AcrDetermReq
Table 6.5.5.2.2-1: Definition of type AcrDetermReq
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
requestorId |
string |
M |
1 |
Contains the identifier of the EEC or the EAS that is sending the request. |
|
easId |
string |
O |
0..1 |
Contains the application identifier of the EAS, e.g. FQDN, URI.. |
|
sEasEndpoint |
EndPoint |
M |
1 |
Contains the endpoint information of the selected S-EAS. |
|
ueId |
Gpsi |
M |
1 |
Contains the identifier of the concerned UE. |
|
acId |
string |
O |
0..1 |
Contains the identifier of the AC. |
6.5.5.2.3 Type: AcrInitReq
Table 6.5.5.2.3-1: Definition of type AcrInitReq
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
requestorId |
string |
M |
1 |
Contains the identifier of the EEC that is sending the request. |
|
easId |
string |
O |
0..1 |
Contains the application identifier of the EAS, e.g. FQDN, URI. |
|
ueId |
Gpsi |
M |
1 |
Contains the identifier of the concerned UE. |
|
acId |
string |
O |
0..1 |
Contains the identifier of the AC. |
|
tEasEndpoint |
EndPoint |
M |
1 |
Contains the endpoint information of the T-EAS. |
|
sEasEndpoint |
EndPoint |
C |
0..1 |
Contains the endpoint information of the S-EAS. This attribute shall be provided when the "easNotifInd" attribute is set to "true" or when the "prevEasNotifInd" attribute is present and set to "true". |
|
prevTEasEndpoint |
EndPoint |
C |
0..1 |
Contains the endpoint information of the previous T-EAS. This attribute shall be provided when the EEC re-sends the ACR request to indicate that a previous ACR is to be cancelled. |
|
routeReq |
RouteToLocation |
O |
0..1 |
Contains the T-EAS’s DNAI information and the corresponding N6 traffic routing information and/or routing profile ID. |
|
easNotifInd |
boolean |
M |
1 |
Indicates whether the EAS should be notified about the need for ACR or ACR cancellation. "true": Notification required. "false" (default): Notification not required. |
|
prevEasNotifInd |
boolean |
C |
0..1 |
Indicates whether the EAS should be notified about ACR cancellation. "true": Notification required. "false" (default): Notification not required. This attribute shall be provided when the EEC re-sends the ACR request to indicate that a previous ACR is to be cancelled. |
|
eecCtxtReloc |
EecCtxtReloc |
O |
0..1 |
Contains EEC context relocation information. |
6.5.5.2.4 Type: AcrDecReq
Table 6.5.5.2.4-1: Definition of type AcrDecReq
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
requestorId |
string |
M |
1 |
Contains the identifier of the EAS that is sending the request. |
|
ueId |
Gpsi |
M |
1 |
Contains the identifier of the concerned UE. |
|
acId |
string |
O |
0..1 |
Contains the identifier of the AC. |
|
tEasId |
string |
M |
1 |
Contains the application identifier of the selected target EAS, e.g. FQDN, URI. |
|
tEasEndpoint |
EndPoint |
M |
1 |
Contains the endpoint information of the selected target EAS. |
6.5.5.2.5 Type: EecCtxtReloc
Table 6.5.5.2.5-1: Definition of type EecCtxtReloc
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
eecCtxtId |
string |
M |
1 |
Contains the identifier of the concerned EEC context. |
|
sEesId |
string |
O |
0..1 |
Contains the identifier of the S-EES. This attribute may be provided only if the ACR request is from the EEC to the T-EES. |
|
sEesEndpoint |
EndPoint |
O |
0..1 |
Contains the endpoint information of the selected S-EES. This attribute may be provided only if the ACR request is from the EEC to the T-EES. |
|
tEesId |
string |
O |
0..1 |
Contains the identifier of the T-EES. This attribute may be provided only if the ACR request is from the EEC to the S-EES. |
|
tEesEndpoint |
EndPoint |
O |
0..1 |
Contains the endpoint information of the selected T-EES. This attribute may be provided only if the ACR request is from the EEC to the S-EES. |
6.5.6 Error Handling
General error handling are described in clause 6.1.
6.5.7 Feature negotiation
General feature negotiation procedures are defined in clause 6.1. Table 6.5.7-1 lists the supported features for Eees_AppContextRelocation API.
Table 6.5.7-1: Supported Features
Feature number |
Feature Name |
Description |