8.4 Registration
23.5583GPPArchitecture for enabling Edge ApplicationsRelease 18TS
8.4.1 General
Registration procedures allow entities in the edge deployment to deliver information to other entities.
The following registrations are supported:
– EEC registration with EES;
– EAS registration with EES; and
– EES registration with ECS.
8.4.2 EEC Registration
8.4.2.1 General
An EEC performs registration with an EES in order to provide information that can be used by the EES in Edge Computing services. The procedure also enables initialization, update and removal of the EEC context information at the EES. The context may be further used for edge-specific operations or processing, e.g. analytics.
An EEC may be registered with one or more EESs on behalf of one or more ACs simultaneously.
8.4.2.2 Procedures
8.4.2.2.1 General
Following are supported for EEC registration:
– EEC registration procedure;
– EEC registration update procedure;
– EEC de-registration procedure; and
– EEC Context relocation procedure.
NOTE: In this version of specification, each registration procedure provides for registering a single EEC per UE.
8.4.2.2.2 EEC registration
Figure 8.4.2.2.2-1 illustrates EEC registration procedure.
Pre-conditions:
1. The EEC is authorized to access the EES for the purpose of performing registration and has received relevant security credentials as specified in clause 8.11; and
2. The EEC has received service provisioning information from the ECS, including information for accessing the EES.
Figure 8.4.2.2.2-1: EEC registration procedure
1. The EEC sends EEC registration request to the EES. The request from the client includes the security credentials received after successful authorization for edge computing services and may include a proposed expiration time. The request also optionally includes information indicating to the EES how the EEC expects to use the services of the EES.
If the EEC is moving to this EES from the purview of another EES, called S-EES, the request from the EEC may include the identity and endpoint of the S-EES and an EEC context ID that was provided by the S-EES to maintain continuity of the EEC context and to authorize EEC context relocation. If the EEC registration is being performed as part of ACR, the EEC shall not include the S-EES endpoint and the EEC context ID.
2. Upon receiving the request from the EEC, the EES validates the registration request and verifies the security credentials. The EES further determines whether the requirements that were indicated in the AC Profile(s) can be fulfilled e.g., without failing to meet the requirements of the already registered EECs, and reserves corresponding resources (e.g., for EASs).
NOTE 1: Resource reservation at EEC registration ensures that the EES provides services for the duration of the registration.
If the EEC provides in the registration request the EAS selection request indicator and based on EES local policies, the EES selects EASs providing the capabilities required by the AC Profile(s), reserves the corresponding resources, and provides the information to the EEC in the registration response.
If the EEC provides in the registration request a UE type, the EES may use this information to apply UE-type-specific local policies.
NOTE 2: Without any indication from UE (either EAS selection request indication or UE type), the EES handling is as per R17 procedure
Editor’s Note: This functionality is to be aligned with how a “constrained device” is identified by the EES.
3. Upon successful validation of the request, if the received EEC registration request contains an EEC context ID and a S-EES Endpoint, the EES performs an EEC Context Pull relocation (clause 8.9.2.2) from the S-EES. The source and target EES perform EEC Context handling as detailed in clause 8.9.1.
NOTE 3: Only a single EEC Context ID may be provided in the EEC registration request.
NOTE 4: In this version of specification, each registration procedure relocates a single EEC context.
NOTE 5: Step 3 is executed when EEC determines to change its connection from S-EES to T-EES and ACR is not required.
If the EEC registration request fails after the EEC Context Pull relocation, e.g., the EES cannot reserve the necessary resources while meeting the capability requirements of the existing registered EECs, the EES shall determine the EEC Context information stale and send a failure response with a corresponding cause.
4. The EES sends a successful EEC registration response, which includes the registration ID and may include a newly assigned EEC context ID. If the EEC registration request contains AC Profile(s), and the EES determines that the requirements indicated in the AC profile(s) cannot be fulfilled for some of the AC profile(s), the EES shall include the list of ACIDs of such AC Profile(s) and may include appropriate reasons. If step 3 was executed, the EEC registration response also includes EEC context retrieval result. The EEC stores the new EEC context ID and uses it if and when it registers with another EES. The EES may also provide an expiration time to indicate to the EEC when the registration will automatically expire. To maintain the registration, the EEC shall send a registration update request prior to the expiration. If a registration update request is not received prior to the expiration time, the EES shall treat the EEC as implicitly de-registered.
If the EEC context relocation status indicates that the EEC context relocation was not successful, then the EEC performs the required EDGE-1 subscriptions at the T-EES.
8.4.2.2.3 EEC registration update
Figure 8.4.2.2.3-1 illustrates EEC registration update procedure.
Pre-conditions:
1. EEC has already registered with the EES.
Figure 8.4.2.2.3-1: EEC registration update procedure
1. The EEC sends EEC registration update request to the EES. The request from the client includes the security credentials received after successful authorization for edge computing services and may include a proposed expiration time and AC profile(s) parameters, including new or updated selected EAS information.
2. Upon receiving the request from the EEC, the EES validates the registration update request and verifies the security credentials.
3. Upon successful validation of the request, the EES sends a successful registration update response, which may include updated expiration time to indicate to the EEC when the updated registration will automatically expire. If the EEC registration update request contains AC Profile(s), and the EES determines that the requirements indicated in the AC profile(s) cannot be fulfilled for some of the AC profile(s), the EES shall include the list of ACIDs of such AC Profile(s) and may include appropriate reasons. To maintain the registration, the EEC shall send a registration update request prior to the expiration time. If a registration update request is not received prior to the expiration time, the EES shall treat the EEC as implicitly de-registered.
8.4.2.2.4 EEC de-registration
Figure 8.4.2.2.4-1 illustrates EEC de-registration procedure.
Pre-conditions:
1. EEC has already registered with the EES.
Figure 8.4.2.2.4-1: EEC de-registration procedure
1. The EEC sends EEC de-registration request to the EES. The request from the client includes the security credentials received after successful authorization for edge computing services.
2. Upon receiving the request from the EEC, the EES validates the de-registration request and verifies the security credentials.
3. Upon successful authorization, the EES sends a successful de-registration response.
8.4.2.3 Information flows
8.4.2.3.1 General
The following information flows are specified for EEC registration:
– EEC registration request and response;
– EEC registration update request and response; and
– EEC registration de-registration request and response.
8.4.2.3.2 EEC registration request
Table 8.4.2.3.2-1 describes information elements in the EEC registration request from the EEC to the EES.
Table 8.4.2.3.2-1: EEC registration request
|
Information element |
Status |
Description |
|
EECID |
M |
Unique identifier of the EEC. |
|
UE Identifier |
O |
The identifier of the hosting UE (i.e. GPSI or identity token) |
|
Security credentials |
M |
Security credentials resulting from a successful authorization for the edge computing service. |
|
AC Profile(s) |
O |
Profiles of ACs for which the EEC provides edge enabling services. AC Profiles are further described in Table 8.2.2-1. |
|
EEC Service Continuity Support |
O |
Indicates if the EEC supports service continuity or not. The IE also indicates which ACR scenarios are supported by the EEC. |
|
EAS selection request indicator |
O |
Indicates the request for EAS selection support from the EES (e.g., for constrained device). |
|
UE type |
O |
Indicates UE or device type (e.g. constrained device) |
|
Proposed expiration time |
O |
Proposed expiration time for the registration. |
|
EEC context ID (NOTE) |
O |
Identifier of the EEC context obtained from a previous registration. |
|
Source EESID (NOTE) |
O |
Identifier of the EES that provided EEC context ID. |
|
Source EES Endpoint (NOTE) |
O |
The endpoint address (e.g. URI, IP address) of the EES that provided EEC context ID. |
|
NOTE: This IE shall not be present when EEC registration is performed as part of ACR. |
||
8.4.2.3.3 EEC registration response
Table 8.4.2.3.3-1 describes information elements in the EEC registration response from the EES to the EEC.
Table 8.4.2.3.3-1: EEC registration response
|
Information element |
Status |
Description |
|
Successful response |
O |
Indicates that the registration request was successful. |
|
> Registration ID |
M |
Identifier of the EEC registration. |
|
> Expiration time |
M |
Indicates the expiration time of the registration. To maintain an active registration status, a registration update is required before the expiration time. |
|
> EEC context ID |
O |
Identifier of the EEC Context information available at the EES that performed the registration. |
|
> EEC Context Relocation status |
O |
Indicates whether the EEC context retrieval from the S-EES was successful or not. |
|
> Discovered EAS list |
O |
List of EASs discovered to provide the capabilities required by the AC Profiles. If the request includes the EAS selection request indicator, then Discovered EAS list shall contain only one selected EAS. If the EES selects no EASs, the list may be empty. |
|
>> EAS profile |
M |
Profile of the EAS. Each element is described in clause 8.2.4. |
|
> list of unfulfilled AC information |
O |
List of ACIDs of the AC Profile(s) for which the requirements indicated in the AC profile(s) cannot be fulfilled |
|
>> ACID |
M |
Application Identifier |
|
>> reason |
O |
Reason indicating the cause (e.g. EAS not available, requirements cannot be fulfilled) |
|
Failure response |
O |
Indicates that the registration request failed. |
|
> Cause |
M |
Provides the cause for registration request failure. |
8.4.2.3.4 EEC registration update request
Table 8.4.2.3.4-1 describes information elements in the EEC registration update request from the EEC to the EES.
Table 8.4.2.3.4-1: EEC registration update request
|
Information element |
Status |
Description |
|
Registration ID |
M |
Identifier of the EEC registration. |
|
Security credentials |
M |
Security credentials resulting from a successful authorization for the edge computing service. |
|
AC profile(s) |
O |
AC Profile as described in Table 8.2.2-1 |
|
Proposed expiration time |
O |
Proposed expiration time for the updated registration. |
8.4.2.3.5 EEC registration update response
Table 8.4.2.3.5-1 describes information elements in the EEC registration update response from the EES to the EEC.
Table 8.4.2.3.5-1: EEC registration update response
|
Information element |
Status |
Description |
|
Successful response |
O |
Indicates that the registration update request was successful. |
|
> Expiration time |
M |
Indicates the expiration time of the registration. To maintain an active registration status, a registration update is required before the expiration time. |
|
> list of unfulfilled AC information |
O |
List of ACIDs of the AC Profile(s) for which the requirements indicated in the AC profile(s) cannot be fulfilled |
|
>> ACID |
M |
Application Identifier |
|
>> reason |
O |
Reson indicating the cause (e.g. EAS not available, requirements cannot be fulfilled) |
|
Failure response |
O |
Indicates that the registration update request failed. |
8.4.2.3.6 EEC de-registration request
Table 8.4.2.3.6-1 describes information elements in the EEC de-registration request from the EEC to the EES.
Table 8.4.2.3.6-1: EEC de-registration request
|
Information element |
Status |
Description |
|
Registration ID |
M |
Identifier of the EEC registration. |
|
Security credentials |
M |
Security credentials resulting from a successful authorization for the edge computing service. |
8.4.2.3.7 EEC de-registration response
Table 8.4.2.3.7-1 describes information elements in the EEC de-registration response from the EES to the EEC.
Table 8.4.2.3.7-1: EEC registration update response
|
Information element |
Status |
Description |
|
Successful response |
O |
Indicates that the de-registration request was successful. |
|
Failure response |
O |
Indicates that the de-registration request failed. |
|
> Cause |
M |
Provide the cause for de-registration request failure. |
8.4.2.4 APIs
8.4.2.4.1 General
Table 8.4.2.4.1-1 illustrates the API for EEC registration.
Table 8.4.2.4.1-1: Eees_EECRegistration API
|
API Name |
API Operations |
Operation Semantics |
Consumer(s) |
|
Eees_EECRegistration |
Request |
Request/Response |
EEC |
|
Update |
|||
|
Deregister |
8.4.2.4.2 Eees_EECRegistration_Request operation
API operation name: Eees_EECRegistration_Request
Description: The consumer requests to register the EEC on the EES.
Inputs: See clause 8.4.2.3.2.
Outputs: See clause 8.4.2.3.3.
See clause 8.4.2.2.2 for details of usage of this operation.
8.4.2.4.3 Eees_EECRegistration_Update operation
API operation name: Eees_EECRegistration_Update
Description: The consumer requests to update the registered information of the EEC on the EES.
Inputs: See clause 8.4.2.3.4.
Outputs: See clause 8.4.2.3.5.
See clause 8.4.2.2.3 for details of usage of this operation.
8.4.2.4.4 Eees_EECRegistration_Deregister operation
API operation name: Eees_EECRegistration_Deregister
Description: The consumer requests to de-register the EEC from the EES.
Inputs: See clause 8.4.2.3.6.
Outputs: See clause 8.4.2.3.7.
See clause 8.4.2.2.4 for details of usage of this operation.
8.4.3 EAS Registration
8.4.3.1 General
The EAS Registration procedure allows an EAS to provide its information to an EES in order to enable its discovery.
If there is a change in the requirements or the information of an EAS, it uses the EAS registration update procedure to update the EES.
The EAS uses the EAS de-registration procedure to remove its information from the EES.
EAS registration at the EES can be time bound. So, to maintain the registration, the EAS needs to send a registration update request prior to the registration expiration time. If a registration update request is not received prior to the registration expiration time, the EES treats the EAS as implicitly de-registered.
NOTE: For registered EAS(s), the EES can request AF traffic influence for any UE, which is implementation specific.
8.4.3.2 Procedures
8.4.3.2.1 General
Following are supported for EAS registration:
– EAS registration procedure;
– EAS registration update procedure; and
– EAS de-registration procedure.
8.4.3.2.2 EAS registration
Pre-conditions:
1. The EAS has been configured with an EASID;
2. The EAS has been configured with the address (e.g. URI) of the EES; and
3. Both the EAS and EES have the necessary credentials to enable communications.
Figure 8.4.3.2.2-1: EAS Registration procedure
1. The EAS determines that registration to the EES is needed (e.g. the EAS is instantiated and started up).
2. The EAS sends an EAS registration request to the EES. The request shall include the EAS profile and may include proposed expiration time for the registration.
3. The EES performs an authorization check to verify whether the EAS has the authorization to register on the EES.
4. Upon successful authorization, the EES stores the EAS Profile for later use (e.g. for serving EAS discovery requests received from EECs, etc.) and replies to the EAS with an EAS registration response. The EES may provide an expiration time to indicate to the EAS when the registration will automatically expire. To maintain the registration, the EAS shall send a registration update request prior to the expiration time. If a registration update request is not received prior to the expiration time, the EES shall treat the EAS as implicitly de-registered.
8.4.3.2.3 EAS registration update
Pre-conditions:
1. The EAS has already registered with the EES.
Figure 8.4.3.2.3-1: EAS registration update procedure
1. The EAS determines that its existing registration needs to be updated (e.g. because the EAS’s status or availability schedule has changed, or EAS’s registration is about to expire).
2. The EAS sends an EAS registration update request to the EES. The request shall include the registration ID and may include the EAS profile and proposed expiration time for the updated registration.
3. The EES performs an authorization check to verify whether the EAS has the authorization to update the registration on the EES.
4. Upon successful authorization, the EES updates the registered EAS Profile and replies to the EAS with an EAS registration update response. The EES may provide an updated expiration time to indicate to the EAS when the updated registration will automatically expire. To maintain the registration, the EAS shall send a registration update request prior to the expiration time. If a registration update request is not received prior to the expiration time, the EES shall treat the EAS as implicitly de-registered.
8.4.3.2.4 EAS de-registration
Pre-conditions:
1. The EAS has already registered with the EES.
Figure 8.4.3.2.4-1: EAS de-registration procedure
1. The EAS determines that its existing registration needs to be terminated (e.g. because the services of the EAS are not needed anymore).
2. The EAS sends an EAS de-registration request to the EES. The request shall include the registration ID.
3. The EES performs an authorization check to verify whether the EAS has the authorization to de-register explicitly.
4. Upon successful authorization, the EES removes the registered EAS Profile and replies to the EAS with an EAS de-registration response.
8.4.3.3 Information flows
8.4.3.3.1 General
The following information flows are specified for EAS registration:
– EAS registration request and response;
– EAS registration update request and response; and
– EAS registration de-registration request and response.
8.4.3.3.2 EAS registration request
Table 8.4.3.3.1-2 describes information elements in the EAS registration request from the EAS to the EES.
Table 8.4.3.3.2-1: EAS registration request
|
Information element |
Status |
Description |
|
EAS Profile |
M |
EAS Profile as described in Table 8.2.4-1 |
|
Security credentials |
M |
Security credentials of the EAS. |
|
Proposed expiration time |
O |
Proposed expiration time for the registration |
8.4.3.3.3 EAS registration response
Table 8.4.3.3.3-1 describes information elements in the EAS registration response from the EES to the EAS.
Table 8.4.3.3.3-1: EAS registration response
|
Information element |
Status |
Description |
|
Successful response |
O |
Indicates that the registration request was successful. |
|
> Registration ID |
M |
Identifier of the registration. |
|
> Expiration time |
O |
Indicates the expiration time of the registration. To maintain an active registration status, a registration update is required before the expiration time. If the Expiration time IE is not included, it indicates that the registration never expires. |
|
Failure response |
O |
Indicates that the registration request failed. |
|
> Cause |
O |
Indicates the cause of registration request failure |
8.4.3.3.4 EAS registration update request
Table 8.4.3.3.4-1 describes information elements in the EAS registration update request from the EAS to the EES.
Table 8.4.3.3.4-1: EAS registration update request
|
Information element |
Status |
Description |
|
Registration ID |
M |
Identifier of the registration. |
|
Security credentials |
M |
Security credentials of the EAS |
|
Updated EAS Profile (NOTE) |
O |
EAS Profile as described in Table 8.2.4-1 with updated information. Included only if there is an update in EAS information. |
|
Proposed expiration time (NOTE) |
O |
Proposed expiration time for the registration |
|
NOTE: At least one of the IEs is included. |
||
8.4.3.3.5 EAS registration update response
Table 8.4.3.3.5-1 describes information elements in the EAS registration update response from the EES to the EAS.
Table 8.4.3.3.5-1: EAS registration update response
|
Information element |
Status |
Description |
|
Successful response |
O |
Indicates that the registration update request was successful. |
|
> Expiration time |
O |
Indicates the expiration time of the updated registration. To maintain an active registration status, a registration update is required before the expiration time. If the Expiration time IE is not included, it indicates that the updated registration never expires. |
|
Failure response |
O |
Indicates that the registration update request failed. |
|
> Cause |
O |
Indicates the cause of registration update request failure |
8.4.3.3.6 EAS de-registration request
Table 8.4.3.3.6-1 describes information elements in the EAS de-registration request from the EAS to the EES.
Table 8.4.3.3.6-1: EAS de-registration request
|
Information element |
Status |
Description |
|
Registration ID |
M |
Identifier of the registration. |
|
Security credentials |
M |
Security credentials of the EAS |
8.4.3.3.7 EAS de-registration response
Table 8.4.3.3.7-1 describes information elements in the EAS de-registration response from the EES to the EAS.
Table 8.4.3.3.7-1: EAS de-registration response
|
Information element |
Status |
Description |
|
Successful response |
O |
Indicates that the de-registration request was successful. |
|
Failure response |
O |
Indicates that the de-registration request failed. |
|
> Cause |
O |
Indicates the cause of de-registration request failure |
8.4.3.4 APIs
8.4.3.4.1 General
Table 8.4.3.4.1-1 illustrates the API for EAS registration.
Table 8.4.3.4.1-1: Eees_EASRegistration API
|
API Name |
API Operations |
Operation Semantics |
Consumer(s) |
|
Eees_EASRegistration |
Request |
Request/Response |
EAS |
|
Update |
|||
|
Deregister |
8.4.3.4.2 Eees_EASRegistration_Request operation
API operation name: Eees_EASRegistration_Request
Description: The consumer requests to register the EAS on the EES.
Inputs: See clause 8.4.3.3.2.
Outputs: See clause 8.4.3.3.3.
See clause 8.4.3.2.2 for details of usage of this operation.
8.4.3.4.3 Eees_EASRegistration_Update operation
API operation name: Eees_EASRegistration_Update
Description: The consumer requests to update the registered information of the EAS on the EES.
Inputs: See clause 8.4.3.3.4.
Outputs: See clause 8.4.3.3.5.
See clause 8.4.3.2.3 for details of usage of this operation.
8.4.3.4.4 Eees_EASRegistration_Deregister operation
API operation name: Eees_EASRegistration_Deregister
Description: The consumer requests to deregister the EAS from the EES.
Inputs: See clause 8.4.3.3.6.
Outputs: See clause 8.4.3.3.7.
See clause 8.4.3.2.4 for details of usage of this operation.
8.4.4 EES Registration
8.4.4.1 General
The EES Registration procedure allows an EES to provide information to an ECS in order to enable provisioning EES(s) to an EEC.
The EES registration update procedure allows an EES to update the ECS, if there is a change in the information at the EES.
The EES uses the EES de-registration procedure to remove its information from the ECS.
8.4.4.2 Procedures
8.4.4.2.1 General
8.4.4.2.2 EES registration
Pre-conditions:
1. The EES has the address (e.g. URI) of the ECS;
2. Both, the EES and ECS, have the necessary credentials to enable communications.
Figure 8.4.4.2.2-1: EES Registration procedure
1. The EES sends the EES registration request to the ECS. The request from the EES includes the EES profile and EES security credentials. The request may include a proposed expiration time for the registration.
2. Upon receiving the request from the EES, the ECS verifies the security credentials of the EES and stores the EES registration information obtained in step 1.
3. The ECS sends an EES registration response indicating success or failure of the registration operation. The ECS may provide an updated expiration time to indicate to the EES when the registration will automatically expire. To maintain the registration, the EES shall send a registration update request prior to the expiration time. If a registration update request is not received prior to the expiration time, the ECS shall treat the EES as implicitly de-registered.
8.4.4.2.3 EES registration update
Pre-conditions:
1. The EES has already registered on the ECS.
Figure 8.4.4.2.3-1: EES registration update procedure
1. The EES sends the EES registration update request to the ECS. The request from the EES includes the registration identity and EES security credentials, and may include proposed expiration time and updated EES profile.
2. Upon receiving the request from the EES, the ECS verifies the security credentials of the EES and stores the updated EES registration information obtained in step 1.
3. The ECS sends an EES registration update response indicating success or failure of the registration update operation. The ECS may provide an updated expiration time to indicate to the EES when the updated registration will automatically expire. To maintain the registration, the EES shall send a registration update request prior to the expiration time. If a registration update request is not received prior to the expiration time, the ECS shall treat the EES as implicitly de-registered.
8.4.4.2.4 EES de-registration
Figure 8.4.4.2.4-1: EES de-registration procedure
1. The EES sends the EES de-registration request to the ECS. The request from the EES includes the registration identity and EES security credentials.
2. Upon receiving the request from the EES, the ECS verifies the security credentials of the EES and removes the corresponding EES registration information.
3. The ECS sends an EES de-registration response indicating success or failure of the de-registration operation.
8.4.4.3 Information elements
8.4.4.3.1 General
The following information flows are specified for EES registration:
– EES registration request and response;
– EES registration update request and response; and
– EES registration de-registration request and response.
8.4.4.3.2 EES registration request
Table 8.4.4.3.2-1 describes information elements for an EES registration request from the EES to the ECS.
Table 8.4.4.3.2-1: EES registration request
|
Information element |
Status |
Description |
|
EES Profile |
M |
Profile information as specified in Table 8.2.6-1 |
|
Security credentials |
M |
Security credentials of the EES. |
|
Proposed expiration time |
O |
Proposed expiration time for the registration |
8.4.4.3.3 EES registration response
Table 8.4.4.3.3-1 describes information elements for an EES registration response from the ECS to the EES.
Table 8.4.4.3.3-1: EES registration response
|
Information element |
Status |
Description |
|
Successful response |
O |
Indicates that the registration request was successful. |
|
> Registration ID |
M |
Identifier of the registration. |
|
> Expiration time |
O |
Indicates the expiration time of the registration. To maintain an active registration status, a registration update is required before the expiration time. If the Expiration time IE is not included, it indicates that the registration never expires. |
|
Failure response |
O |
Indicates that the registration request failed. |
|
> Cause |
O |
Indicates the cause of registration request failure |
8.4.4.3.4 EES registration update request
Table 8.4.4.3.4-1 describes information elements for an EES registration update request from the EES to the ECS.
Table 8.4.4.3.4-1: EES registration update request
|
Information element |
Status |
Description |
|
Updated EES Profile (NOTE) |
O |
Profile information as specified in Table 8.2.6-1 |
|
Security credentials |
M |
Security credentials of the EES. |
|
Registration ID |
M |
Identifier of the registration. |
|
Proposed expiration time (NOTE) |
O |
Proposed expiration time for the registration |
|
NOTE: At least one of the IEs is included. |
||
8.4.4.3.5 EES registration update response
Table 8.4.4.3.5-1 describes information elements for an EES registration update response from the ECS to the EES.
Table 8.4.4.3.5-1: EES registration update response
|
Information element |
Status |
Description |
|
Successful response |
O |
Indicates that the registration update request was successful. |
|
> Expiration time |
O |
Indicates the expiration time of the updated registration. To maintain an active registration status, a registration update is required before the expiration time. If the Expiration time IE is not included, it indicates that the updated registration never expires. |
|
Failure response |
O |
Indicates that the registration update request failed. |
|
> Cause |
O |
Indicates the cause of registration update request failure |
8.4.4.3.6 EES de-registration request
Table 8.4.4.3.6-1 describes information elements for an EES de-registration request from the EES to the ECS.
Table 8.4.4.3.6-1: EES de-registration request
|
Information element |
Status |
Description |
|
Registration ID |
M |
Identifier of the registration. |
|
Security credentials |
M |
Security credentials of the EES |
8.4.4.3.7 EES de-registration response
Table 8.4.4.3.7-1 describes information elements for an EES de-registration response from the ECS to the EES.
Table 8.4.4.3.7-1: EES de-registration response
|
Information element |
Status |
Description |
|
Successful response |
O |
Indicates that the de-registration request was successful. |
|
Failure response |
O |
Indicates that the de-registration request failed. |
|
> Cause |
O |
Indicates the cause of de-registration request failure |
8.4.4.4 APIs
8.4.4.4.1 General
Table 8.4.4.4.1-1 illustrates the API for EES registration.
Table 8.4.4.4.1-1: Eecs_EESRegistration API
|
API Name |
API Operations |
Operation Semantics |
Consumer(s) |
|
Eecs_EESRegistration |
Request |
Request/Response |
EES |
|
Update |
|||
|
Deregister |
8.4.4.4.2 Eecs_EESRegistration_Request operation
API operation name: Eecs_EESRegistration_Request
Description: The consumer requests to register the EES on the ECS.
Inputs: See clause 8.4.4.3.2.
Outputs: See clause 8.4.4.3.3.
See clause 8.4.4.2.2 for details of usage of this operation.
8.4.4.4.3 Eecs_EESRegistration_Update operation
API operation name: Eecs_EESRegistration_Update
Description: The consumer requests to update the registered information of the EES on the ECS.
Inputs: See clause 8.4.4.3.4.
Outputs: See clause 8.4.4.3.5.
See clause 8.4.4.2.3 for details of usage of this operation.
8.4.4.4.4 Eecs_EESRegistration_Deregister operation
API operation name: Eecs_EESRegistration_Deregister
Description: The consumer requests to deregister the EES from the ECS.
Inputs: See clause 8.4.4.3.6.
Outputs: See clause 8.4.4.3.7.
See clause 8.4.4.2.4 for details of usage of this operation.