Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.558  Word version:  19.2.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…   E…

 

8.4  Registrationp. 77

8.4.1  Generalp. 77

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 Registrationp. 78

8.4.2.1  Generalp. 78

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.
In deployments with bundled EAS(s) registered to different EESs, to perform EEC registration (if needed) the EEC sends the EEC registration message to all the associated EES for the EAS bundle.
Up

8.4.2.2  Proceduresp. 78

8.4.2.2.1  Generalp. 78
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 registrationp. 78
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.
Reproduction of 3GPP TS 23.558, Fig. 8.4.2.2.2-1: EEC registration procedure
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. The EEC may include indication for UE mobility support requirement to 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 e.g., without failing to meet the requirements of the already registered EECs, and reserves corresponding resources (e.g., for EASs). If the AC Profile(s) include EAS bundle information the reserved EAS resources are apportioned among the EASs in the bundle, based on the indicated requirements and local policies.
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 bundle EAS information (either as EAS bundle identifier or as a list of EASIDs) is included and the EAS selection request indicator is set, then the EES determines whether all or a subset of the EAS(s) in the bundle are registered and instantiated. If only a subset of bundle EASs is found, the EES may determine whether instantiable but not yet instantiated EASs match the subset of remaining (i.e. not yet found) bundle EASs and performs the dynamic EAS instantiation triggering procedure in clause 8.12 for this subset.
If the EEC provides in the registration request a UE type, the EES may use this information to apply UE-type-specific local policies.
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 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.
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 updatep. 80
Figure 8.4.2.2.3-1 illustrates EEC registration update procedure.
Pre-conditions:
  1. EEC has already registered with the EES.
Reproduction of 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) parameters, including new or updated selected EAS information. The EEC may include indication for UE mobility support requirement to the EES.
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-registrationp. 81
Figure 8.4.2.2.4-1 illustrates EEC de-registration procedure.
Pre-conditions:
  1. EEC has already registered with the EES.
Reproduction of 3GPP TS 23.558, Fig. 8.4.2.2.4-1: EEC de-registration procedure
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 flowsp. 81

8.4.2.3.1  Generalp. 81
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 requestp. 81
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).
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.
EAS selection request indicatorOIndicates the request for EAS selection support from the EES (e.g., for constrained device).
UE typeOIndicates UE or device type (e.g. constrained device)
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.
UE Mobility Support RequirementOIndicates UE requires mobility support or not.
NOTE:
This IE shall not be present when EEC registration is performed as part of ACR.
Up
8.4.2.3.3  EEC registration responsep. 82
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 time (NOTE)OIndicates 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.
> Discovered EAS listOList 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 profileMProfile of the EAS. Each element is described in clause 8.2.4.
> 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.
NOTE:
The Expiration time IE shall be included if based on the ECSP policy the EES requires EEC to periodically refresh the EEC registration.
Up
8.4.2.3.4  EEC registration update requestp. 83
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.
UE Mobility Support RequirementOIndicates UE requires mobility support or not.
Up
8.4.2.3.5  EEC registration update responsep. 83
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 time (NOTE)OIndicates 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.
NOTE:
The Expiration time IE shall be included if based on the ECSP policy the EES requires EEC to periodically refresh the EEC registration.
Up
8.4.2.3.6  EEC de-registration requestp. 84
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 responsep. 84
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  APIsp. 84

8.4.2.4.1  Generalp. 84
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 operationp. 85
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 operationp. 85
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 operationp. 85
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.

Up   Top   ToC