Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.558  Word version:  19.0.0

Top   Top   Up   Prev   Next
0…   5…   6…   6.2a…   6.2b…   6.3…   6.4…   7…   8…   8.3…   8.3.3…   8.3.3.3…   8.4…   8.4.3…   8.4.4…   8.5…   8.6…   8.6.3…   8.6.4…   8.6.6…   8.7…   8.8…   8.8.2.5…   8.8.2A…   8.8.3…   8.8.4…   8.8.5…   8.9…   8.14…   8.14.3…   8.15…   8.17…   8.17.3…   8.17.4…   8.18…   8.19…   8.20…   9…   A…   A.4…   A.5…   B… 
8.4.3 EAS Registration  8.4.3.1 General  8.4.3.2 Procedures  8.4.3.2.1 General  8.4.3.2.2 EAS registration  8.4.3.2.3 EAS registration update  8.4.3.2.4 EAS de-registration  8.4.3.3 Information flows  8.4.3.3.1 General  8.4.3.3.2 EAS registration request  8.4.3.3.3 EAS registration response  8.4.3.3.4 EAS registration update request  8.4.3.3.5 EAS registration update response  8.4.3.3.6 EAS de-registration request  8.4.3.3.7 EAS de-registration response  8.4.3.4 APIs  8.4.3.4.1 General  8.4.3.4.2 Eees_EASRegistration_Request operation  8.4.3.4.3 Eees_EASRegistration_Update operation  8.4.3.4.4 Eees_EASRegistration_Deregister operation 
...

 

8.4.3  EAS Registration  p. 81

8.4.3.1  General  p. 81

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  Procedures  p. 81

8.4.3.2.1  General  p. 81
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  p. 82
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.
Reproduction of 3GPP TS 23.558, Fig. 8.4.3.2.2-1: EAS Registration procedure
Figure 8.4.3.2.2-1: EAS Registration procedure
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. If the request includes bundle ID, the EES stores the received information. 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 update  p. 82
Pre-conditions:
  1. The EAS has already registered with the EES.
Reproduction of 3GPP TS 23.558, Fig. 8.4.3.2.3-1: EAS registration update procedure
Figure 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. If the request includes updated bundle ID, the EES updates the stored information. 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-registration  p. 83
Pre-conditions:
  1. The EAS has already registered with the EES.
Reproduction of 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
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 flows  p. 84

8.4.3.3.1  General  p. 84
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  p. 84
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 response  p. 84
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 request  p. 85
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 response  p. 85
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 request  p. 85
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 response  p. 86
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  APIs  p. 86

8.4.3.4.1  General  p. 86
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 operation  p. 86
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  p. 86
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  p. 86
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.

Up   Top   ToC