Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.558  Word version:  17.4.0

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

 

8.4  RegistrationWord‑p. 52

8.4.1  GeneralWord‑p. 52

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 RegistrationWord‑p. 52

8.4.2.1  GeneralWord‑p. 52

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  ProceduresWord‑p. 52

8.4.2.2.1  GeneralWord‑p. 52
Following are supported for EEC registration:
  • EEC registration procedure;
  • EEC registration update procedure;
  • EEC de-registration procedure; and
  • EEC Context relocation procedure.
8.4.2.2.2  EEC registrationWord‑p. 52
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.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.4.2.2.2-1: EEC registration procedure
Figure 8.4.2.2.2-1: EEC registration procedure
(⇒ copy of original 3GPP image)
Up
Step 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.
Step 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 and reserves corresponding resources.
Step 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 a 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.
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.
Step 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.
Up
8.4.2.2.3  EEC registration updateWord‑p. 54
Figure 8.4.2.2.3-1 illustrates EEC registration update procedure.
Pre-conditions:
  1. EEC has already registered with the EES.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.4.2.2.3-1: EEC registration update procedure
Up
Step 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).
Step 2.
Upon receiving the request from the EEC, the EES validates the registration update request and verifies the security credentials.
Step 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.
Up
8.4.2.2.4  EEC de-registrationWord‑p. 54
Figure 8.4.2.2.4-1 illustrates EEC de-registration procedure.
Pre-conditions:
  1. EEC has already registered with the EES.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.4.2.2.4-1: EEC de-registration procedure
Figure 8.4.2.2.4-1: EEC de-registration procedure
(⇒ copy of original 3GPP image)
Up
Step 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.
Step 2.
Upon receiving the request from the EEC, the EES validates the de-registration request and verifies the security credentials.
Step 3.
Upon successful authorization, the EES sends a successful de-registration response.

8.4.2.3  Information flowsWord‑p. 55

8.4.2.3.1  GeneralWord‑p. 55
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 requestWord‑p. 55
Table 8.4.2.3.2-1 describes information elements in the EEC registration request from the EEC to the EES.
Information element Status Description
EECIDMUnique identifier of the EEC.
UE IdentifierOThe identifier of the hosting UE (i.e. GPSI or identity token)
Security credentialsMSecurity 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 SupportOIndicates if the EEC supports service continuity or not. The IE also indicates which ACR scenarios are supported by the EEC.
Proposed expiration timeOProposed expiration time for the registration.
EEC context ID (NOTE)OIdentifier of the EEC context obtained from a previous registration.
Source EESID (NOTE)OIdentifier of the EES that provided EEC context ID.
Source EES Endpoint (NOTE)OThe 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.
Up
8.4.2.3.3  EEC registration responseWord‑p. 56
Table 8.4.2.3.3-1 describes information elements in the EEC registration response from the EES to the EEC.
Information element Status Description
Successful responseOIndicates that the registration request was successful.
> Registration IDMIdentifier of the EEC registration.
> Expiration timeMIndicates the expiration time of the registration. To maintain an active registration status, a registration update is required before the expiration time.
> EEC context IDOIdentifier of the EEC Context information available at the EES that performed the registration.
> EEC Context Relocation statusOIndicates whether the EEC context retrieval from the S-EES was successful or not.
> list of unfulfilled AC informationOList of ACIDs of the AC Profile(s) for which the requirements indicated in the AC profile(s) cannot be fulfilled
>> ACIDMApplication Identifier
>> reasonOReason indicating the cause (e.g. EAS not available, requirements cannot be fulfilled)
Failure responseOIndicates that the registration request failed.
> CauseMProvides the cause for registration request failure.
Up
8.4.2.3.4  EEC registration update requestWord‑p. 56
Table 8.4.2.3.4-1 describes information elements in the EEC registration update request from the EEC to the EES.
Information element Status Description
Registration IDMIdentifier of the EEC registration.
Security credentialsMSecurity 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 timeOProposed expiration time for the updated registration.
Up
8.4.2.3.5  EEC registration update responseWord‑p. 57
Table 8.4.2.3.5-1 describes information elements in the EEC registration update response from the EES to the EEC.
Information element Status Description
Successful responseOIndicates that the registration update request was successful.
> Expiration timeMIndicates 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 informationOList of ACIDs of the AC Profile(s) for which the requirements indicated in the AC profile(s) cannot be fulfilled
>> ACIDMApplication Identifier
>> reasonOReason indicating the cause (e.g. EAS not available, requirements cannot be fulfilled)
Failure responseOIndicates that the registration update request failed.
Up
8.4.2.3.6  EEC de-registration requestWord‑p. 57
Table 8.4.2.3.6-1 describes information elements in the EEC de-registration request from the EEC to the EES.
Information element Status Description
Registration IDMIdentifier of the EEC registration.
Security credentialsMSecurity credentials resulting from a successful authorization for the edge computing service.
Up
8.4.2.3.7  EEC de-registration responseWord‑p. 57
Table 8.4.2.3.7-1 describes information elements in the EEC de-registration response from the EES to the EEC.
Information element Status Description
Successful responseOIndicates that the de-registration request was successful.
Failure responseOIndicates that the de-registration request failed.
> CauseMProvide the cause for de-registration request failure.
Up

8.4.2.4  APIsWord‑p. 58

8.4.2.4.1  GeneralWord‑p. 58
Table 8.4.2.4.1-1 illustrates the API for EEC registration.
API Name API Operations Operation Semantics Consumer(s)
Eees_EECRegistrationRequestRequest/ResponseEEC
Update
Deregister
Up
8.4.2.4.2  Eees_EECRegistration_Request operationWord‑p. 58
API operation name:
Eees_EECRegistration_Request
Description:
The consumer requests to register the EEC on the EES.
Inputs:
Outputs:
See clause 8.4.2.2.2 for details of usage of this operation.
8.4.2.4.3  Eees_EECRegistration_Update operationWord‑p. 58
API operation name:
Eees_EECRegistration_Update
Description:
The consumer requests to update the registered information of the EEC on the EES.
Inputs:
Outputs:
See clause 8.4.2.2.3 for details of usage of this operation.
8.4.2.4.4  Eees_EECRegistration_Deregister operationWord‑p. 58
API operation name:
Eees_EECRegistration_Deregister
Description:
The consumer requests to de-register the EEC from the EES.
Inputs:
Outputs:
See clause 8.4.2.2.4 for details of usage of this operation.

8.4.3  EAS RegistrationWord‑p. 59

8.4.3.1  GeneralWord‑p. 59

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

8.4.3.2  ProceduresWord‑p. 59

8.4.3.2.1  GeneralWord‑p. 59
Following are supported for EAS registration:
  • EAS registration procedure;
  • EAS registration update procedure; and
  • EAS de-registration procedure.
8.4.3.2.2  EAS registrationWord‑p. 59
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.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.4.3.2.2-1: EAS Registration procedure
Figure 8.4.3.2.2-1: EAS Registration procedure
(⇒ copy of original 3GPP image)
Up
Step 1.
The EAS determines that registration to the EES is needed (e.g. the EAS is instantiated and started up).
Step 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.
Step 3.
The EES performs an authorization check to verify whether the EAS has the authorization to register on the EES.
Step 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.
Up
8.4.3.2.3  EAS registration updateWord‑p. 60
Pre-conditions:
  1. The EAS has already registered with the EES.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.4.3.2.3-1: EAS registration update procedure
Up
Step 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).
Step 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.
Step 3.
The EES performs an authorization check to verify whether the EAS has the authorization to update the registration on the EES.
Step 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.
Up
8.4.3.2.4  EAS de-registrationWord‑p. 60
Pre-conditions:
  1. The EAS has already registered with the EES.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.4.3.2.4-1: EAS de-registration procedure
Figure 8.4.3.2.4-1: EAS de-registration procedure
(⇒ copy of original 3GPP image)
Up
Step 1.
The EAS determines that its existing registration needs to be terminated (e.g. because the services of the EAS are not needed anymore).
Step 2.
The EAS sends an EAS de-registration request to the EES. The request shall include the registration ID.
Step 3.
The EES performs an authorization check to verify whether the EAS has the authorization to de-register explicitly.
Step 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 flowsWord‑p. 61

8.4.3.3.1  GeneralWord‑p. 61
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 requestWord‑p. 61
Table 8.4.3.3.2-1 describes information elements in the EAS registration request from the EAS to the EES.
Information element Status Description
EAS ProfileM EAS Profile as described in Table 8.2.4-1
Security credentialsMSecurity credentials of the EAS.
Proposed expiration timeOProposed expiration time for the registration
Up
8.4.3.3.3  EAS registration responseWord‑p. 61
Table 8.4.3.3.3-1 describes information elements in the EAS registration response from the EES to the EAS.
Information element Status Description
Successful responseOIndicates that the registration request was successful.
> Registration IDMIdentifier of the registration.
> Expiration timeOIndicates 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 responseOIndicates that the registration request failed.
> CauseOIndicates the cause of registration request failure
Up
8.4.3.3.4  EAS registration update requestWord‑p. 62
Table 8.4.3.3.4-1 describes information elements in the EAS registration update request from the EAS to the EES.
Information element Status Description
Registration IDMIdentifier of the registration.
Security credentialsMSecurity 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)OProposed expiration time for the registration
NOTE:
At least one of the IEs is included.
Up
8.4.3.3.5  EAS registration update responseWord‑p. 62
Table 8.4.3.3.5-1 describes information elements in the EAS registration update response from the EES to the EAS.
Information element Status Description
Successful responseOIndicates that the registration update request was successful.
> Expiration timeOIndicates 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 responseOIndicates that the registration update request failed.
> CauseOIndicates the cause of registration update request failure
Up
8.4.3.3.6  EAS de-registration requestWord‑p. 62
Table 8.4.3.3.6-1 describes information elements in the EAS de-registration request from the EAS to the EES.
Information element Status Description
Registration IDMIdentifier of the registration.
Security credentialsMSecurity credentials of the EAS
Up
8.4.3.3.7  EAS de-registration responseWord‑p. 63
Table 8.4.3.3.7-1 describes information elements in the EAS de-registration response from the EES to the EAS.
Information element Status Description
Successful responseOIndicates that the de-registration request was successful.
Failure responseOIndicates that the de-registration request failed.
> CauseOIndicates the cause of de-registration request failure
Up

8.4.3.4  APIsWord‑p. 63

8.4.3.4.1  GeneralWord‑p. 63
Table 8.4.3.4.1-1 illustrates the API for EAS registration.
API Name API Operations Operation Semantics Consumer(s)
Eees_EASRegistrationRequestRequest/ResponseEAS
Update
Deregister
Up
8.4.3.4.2  Eees_EASRegistration_Request operationWord‑p. 63
API operation name:
Eees_EASRegistration_Request
Description:
The consumer requests to register the EAS on the EES.
Inputs:
Outputs:
See clause 8.4.3.2.2 for details of usage of this operation.
8.4.3.4.3  Eees_EASRegistration_Update operationWord‑p. 63
API operation name:
Eees_EASRegistration_Update
Description:
The consumer requests to update the registered information of the EAS on the EES.
Inputs:
Outputs:
See clause 8.4.3.2.3 for details of usage of this operation.
8.4.3.4.4  Eees_EASRegistration_Deregister operationWord‑p. 63
API operation name:
Eees_EASRegistration_Deregister
Description:
The consumer requests to deregister the EAS from the EES.
Inputs:
Outputs:
See clause 8.4.3.2.4 for details of usage of this operation.

8.4.4  EES RegistrationWord‑p. 64

8.4.4.1  GeneralWord‑p. 64

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  ProceduresWord‑p. 64

8.4.4.2.1  GeneralWord‑p. 64
Void
8.4.4.2.2  EES registrationWord‑p. 64
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.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.4.4.2.2-1: EES Registration procedure
Figure 8.4.4.2.2-1: EES Registration procedure
(⇒ copy of original 3GPP image)
Up
Step 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.
Step 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.
Step 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.
Up
8.4.4.2.3  EES registration updateWord‑p. 64
Pre-conditions:
  1. The EES has already registered on the ECS.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.4.4.2.3-1: EES registration update procedure
Up
Step 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.
Step 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.
Step 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.
Up
8.4.4.2.4  EES de-registrationWord‑p. 65
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.4.4.2.4-1: EES de-registration procedure
Figure 8.4.4.2.4-1: EES de-registration procedure
(⇒ copy of original 3GPP image)
Up
Step 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.
Step 2.
Upon receiving the request from the EES, the ECS verifies the security credentials of the EES and removes the corresponding EES registration information.
Step 3.
The ECS sends an EES de-registration response indicating success or failure of the de-registration operation.

8.4.4.3  Information elementsWord‑p. 66

8.4.4.3.1  GeneralWord‑p. 66
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 requestWord‑p. 66
Table 8.4.4.3.2-1 describes information elements for an EES registration request from the EES to the ECS.
Information element Status Description
EES ProfileM Profile information as specified in Table 8.2.6-1
Security credentialsMSecurity credentials of the EES.
Proposed expiration timeOProposed expiration time for the registration
Up
8.4.4.3.3  EES registration responseWord‑p. 66
Table 8.4.4.3.3-1 describes information elements for an EES registration response from the ECS to the EES.
Information element Status Description
Successful responseOIndicates that the registration request was successful.
> Registration IDMIdentifier of the registration.
> Expiration timeOIndicates 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 responseOIndicates that the registration request failed.
> CauseOIndicates the cause of registration request failure
Up
8.4.4.3.4  EES registration update requestWord‑p. 66
Table 8.4.4.3.4-1 describes information elements for an EES registration update request from the EES to the ECS.
Information element Status Description
Updated EES Profile (NOTE)O Profile information as specified in Table 8.2.6-1
Security credentialsMSecurity credentials of the EES.
Registration IDMIdentifier of the registration.
Proposed expiration time (NOTE)OProposed expiration time for the registration
NOTE:
At least one of the IEs is included.
Up
8.4.4.3.5  EES registration update responseWord‑p. 66
Table 8.4.4.3.5-1 describes information elements for an EES registration update response from the ECS to the EES.
Information element Status Description
Successful responseOIndicates that the registration update request was successful.
> Expiration timeOIndicates 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 responseOIndicates that the registration update request failed.
> CauseOIndicates the cause of registration update request failure
Up
8.4.4.3.6  EES de-registration requestWord‑p. 67
Table 8.4.4.3.6-1 describes information elements for an EES de-registration request from the EES to the ECS.
Information element Status Description
Registration IDMIdentifier of the registration.
Security credentialsMSecurity credentials of the EES
Up
8.4.4.3.7  EES de-registration responseWord‑p. 67
Table 8.4.4.3.7-1 describes information elements for an EES de-registration response from the ECS to the EES.
Information element Status Description
Successful responseOIndicates that the de-registration request was successful.
Failure responseOIndicates that the de-registration request failed.
> CauseOIndicates the cause of de-registration request failure
Up

8.4.4.4  APIsWord‑p. 67

8.4.4.4.1  GeneralWord‑p. 67
Table 8.4.4.4.1-1 illustrates the API for EES registration.
API Name API Operations Operation Semantics Consumer(s)
Eecs_EESRegistrationRequestRequest/ResponseEES
Update
Deregister
Up
8.4.4.4.2  Eecs_EESRegistration_Request operationWord‑p. 67
API operation name:
Eecs_EESRegistration_Request
Description:
The consumer requests to register the EES on the ECS.
Inputs:
Outputs:
See clause 8.4.4.2.2 for details of usage of this operation.
8.4.4.4.3  Eecs_EESRegistration_Update operationWord‑p. 68
API operation name:
Eecs_EESRegistration_Update
Description:
The consumer requests to update the registered information of the EES on the ECS.
Inputs:
Outputs:
See clause 8.4.4.2.3 for details of usage of this operation.
8.4.4.4.4  Eecs_EESRegistration_Deregister operationWord‑p. 68
API operation name:
Eecs_EESRegistration_Deregister
Description:
The consumer requests to deregister the EES from the ECS.
Inputs:
Outputs:
See clause 8.4.4.2.4 for details of usage of this operation.

Up   Top   ToC