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.20  Interaction with ECS with Repository function |R18|p. 280

8.20.1  Generalp. 280

This clause describes procedures and services provided by the ECS with Repository function (ECS-ER), which is applicable when the ECS-ER is available.

8.20.2  Procedurep. 280

8.20.2.1  Generalp. 280

Clause 8.20.2.2, clause 8.20.2.3 and clause 8.20.2.4 illustrate the application group specific EAS information retrieval procedures.

8.20.2.2  Obtain EAS informationp. 281

Reproduction of 3GPP TS 23.558, Fig. 8.20.2.2-1: Obtain EAS information
Up
Step 1.
The EES sends EAS information get request message to the ECS-ER. The request message includes EAS ID and Application Group ID, and may include bundled EAS ID list and main EAS ID or EAS bundle ID.
Step 2.
Upon receiving the request, the ECS-ER checks if there are any stored EAS(s) serving the application group for the EAS ID, bundled EAS ID list (if received) and main EAS ID (if received) or EAS bundle ID (if received).
Step 3.
If the processing of the request was successful, the ECS-ER responds the EES with EAS information identified in step 2. If EES indicated the support for EDN information and EAS service KPI information in step 1, the ECS-ER also responds the EES with these information.
Up

8.20.2.3  Common EAS information storagep. 281

Pre-condition:
  1. The EES is registered in the ECS supporting repository function.
Reproduction of 3GPP TS 23.558, Fig. 8.20.2.3-1: Common EAS information storage
Up
Step 1.
The EES sends Common EAS information store request message to the ECS-ER. The request message includes EDN information, EES ID, EAS ID, EAS endpoint and Application Group ID, and may include EAS service KPIs, bundled EAS ID and endpoint list, main EAS ID or EAS bundle ID.
Step 2.
Upon receiving the request, the ECS-ER checks if there is any stored EAS serving the application group for the EAS ID, bundled EAS ID list (if received) and main EAS ID (if received) or EAS bundle ID (if received) within the same EDN. If no common EAS is identified, the ECS-ER stores the received information for subsequent binding requests.
Step 3.
The ECS-ER responds the EES with Common EAS information store response message. The ECS-ER may reject the request with common EAS information identified in step 2 or accept the request. For enabling the EEC to further communicate with common EES, the common EES endpoint is also provided with common EAS information.
Up

8.20.2.4  Common EAS information removal |R19|p. 282

Pre-condition:
  1. Common EAS is deregistered from the common EES.
Reproduction of 3GPP TS 23.558, Fig. 8.20.2.4-1: Common EAS information removal
Up
Step 1.
The common EES sends Common EAS information remove request message to the ECS-ER. The request message includes EES ID, EAS ID, EAS endpoint and Application Group ID.
Step 2.
Upon receiving the request, the ECS-ER removes the stored information associated with the common EAS identified in the request.
Step 3.
The ECS-ER responds the common EES with Common EAS information remove response message.

8.20.2.5  Common EAS information update |R19|p. 283

Reproduction of 3GPP TS 23.558, Fig. 8.20.2.5-1: Common EAS information update
Up
Step 1.
The EES sends Common EAS information update request message to the ECS-ER. The request message includes EDN information, EES ID, EAS ID, EAS endpoint and Application Group ID.
Step 2.
Upon receiving the request, the ECS-ER checks if there is any stored EAS serving the application group for the EAS ID within the same EDN. If existing common EAS is found, the ECS-ER updates the EAS endpoint information for subsequent binding; otherwise, the ECS-ER rejects the EES request in step 3.
Step 3.
The ECS-ER responds the EES with Common EAS information update response message.
Up

8.20.3  Information flowsp. 283

8.20.3.1  Generalp. 283

The information flows are specified for EAS information service.

8.20.3.2  EAS information get requestp. 283

Table 8.20.3.2-1 describes the information elements for EAS information get request from the EES to the ECS-ER.
Information element Status Description
Requestor identifierMThe identifier of the EES.
Security credentialsMSecurity credentials resulting from a successful authorization for the edge computing service.
EAS IDMThe identifier of the EAS.
Application Group IDMApplication group identifier as defined in clause 7.2.11.
Bundled EAS ID listOA list of associated EAS IDs in an EAS bundle.
EAS bundle ID (NOTE)OBundle ID as described in clause 7.2.10.
Main EAS ID (NOTE)OThe main EAS ID in an EAS bundle.
NOTE:
If present, only one of these IEs may be present in the message.
Up

8.20.3.3  EAS information get responsep. 283

Table 8.20.3.3-1 describes the information elements for EAS information get response from the ECS-ER to the EES.
Information element Status Description
Successful response (NOTE 1)OIndicates that the request was successful.
> EAS information (NOTE 2)MThis IE includes a list of EAS endpoints and optionally its associated EAS endpoint(s), corresponding to the requested EAS ID(s).
Failure response (NOTE 1)OIndicates that the request has failed.
> EDN informationO This IE includes a list of EDN information corresponding to EAS in the response, as described in Table 8.20.3.4-1.
> EAS service KPIsO This IE includes EAS service KPIs (see Table 8.2.5-1) for the EAS in the response.
> CauseOIndicates the failure cause. Only included when Failure response is included.
NOTE 1:
One of these IEs shall be present in the message.
NOTE 2:
This IE supports common EAS information for a bundle.
Up

8.20.3.4  Common EAS information store requestp. 284

Table 8.20.3.4-1 describes the information elements for common EAS information store request from the EES to the ECS-ER.
Information element Status Description
Requestor identifierMThe identifier of the EES.
Security credentialsMSecurity credentials resulting from a successful authorization for the edge computing service.
EAS IDMThe identifier of the EAS.
EAS endpointMEndpoint information (e.g. URI, FQDN, IP address) used to communicate with the EAS.
Common EAS bundle informationOEAS bundle information to which the EAS belongs.
> Bundled EAS ID and endpoint listMA list of associated EAS IDs and the corresponding EAS endpoints in an EAS bundle.
> Main EAS ID (NOTE)OThe main EAS ID in an EAS bundle.
> EAS bundle ID (NOTE)OBundle ID as described in clause 7.2.10.
Application Group IDMApplication group identifier as defined in clause 7.2.11. If main EAS ID or EAS bundle ID is provided, it identifies the group of UEs associated with the main EAS ID or the EAS bundle ID.
EDN informationMInformation of EDN where the EAS resides.
> DNNMData network name to identify the EDN.
> DNAI(s)ODNAI(s) associated with the EDN.
EAS service KPIsO Service characteristics provided by EAS, detailed in Table 8.2.5-1.
NOTE:
If present, only one of these IEs may be present in the message.
Up

8.20.3.5  Common EAS information store responsep. 284

Table 8.20.3.5-1 describes the information elements for common EAS information store response from the ECS-ER to the EES.
Information element Status Description
Successful response (NOTE)OIndicates that the request was successful.
Failure response (NOTE)OIndicates that the request has failed.
> CauseOIndicates the failure cause. Only included when Failure response is included.
> Common EAS informationOThis IE includes common EAS endpoint and optionally its associated EAS endpoint(s), corresponding to the requested EAS ID(s).
> Common EES endpointOThis IE includes common EES endpoint address. It shall be provided when common EAS information is provided.
NOTE:
One of these IEs shall be present in the message.
Up

8.20.3.6  Common EAS information remove request |R19|p. 285

Table 8.20.3.6-1 describes the information elements for common EAS information remove request from the EES to the ECS-ER.
Information element Status Description
Requestor identifierMThe identifier of the EES.
Security credentialsMSecurity credentials resulting from a successful authorization for the edge computing service.
EAS IDMThe identifier of the EAS.
Application Group IDMApplication group identifier as defined in clause 7.2.11.
EAS endpointMEndpoint information (e.g. URI, FQDN, IP address) used to communicate with the EAS.
Up

8.20.3.7  Common EAS information remove response |R19|p. 285

Table 8.20.3.7-1 describes the information elements for common EAS information remove response from the ECS-ER to the EES.
Information element Status Description
Successful response (NOTE)OIndicates that the request was successful.
Failure response (NOTE)OIndicates that the request has failed.
> CauseOIndicates the failure cause. Only included when Failure response is included.
NOTE:
One of these IEs shall be present in the message.
Up

8.20.3.8  Common EAS information update request |R19|p. 285

Table 8.20.3.8-1 describes the information elements for common EAS information update request from the EES to the ECS-ER.
Information element Status Description
Requestor identifierMThe identifier of the EES.
Security credentialsMSecurity credentials resulting from a successful authorization for the edge computing service.
EAS IDMThe identifier of the EAS.
EAS endpointMEndpoint information (e.g. URI, FQDN, IP address) used to communicate with the EAS.
Application Group IDMApplication group identifier as defined in clause 7.2.11.
EDN informationMInformation of EDN where the EAS resides.
> DNNMData network name to identify the EDN.
> DNAI(s)ODNAI(s) associated with the EDN.
Up

8.20.3.9  Common EAS information update response |R19|p. 286

Table 8.20.3.9-1 describes the information elements for common EAS information update response from the ECS-ER to the EES.
Information element Status Description
Successful response (NOTE)OIndicates that the request was successful.
Failure response (NOTE)OIndicates that the request has failed.
> CauseOIndicates the failure cause. Only included when Failure response is included.
NOTE:
One of these IEs shall be present in the message.
Up

8.20.4  APIsp. 286

8.20.4.1  Generalp. 286

Table 8.20.4.1-1 illustrates the API for EAS information management.
API Name API Operations Operation Semantics Consumer(s)
Eecs_EASInfoManagementStoreRequest/ ResponseEES
UpdateRequest/ ResponseEES
RemoveRequest/ ResponseEES
GetRequest/ ResponseEES
Up

8.20.4.2  Eecs_EASInfoManagement_Store operationp. 286

API operation name:
Eecs_EASInfoManagement_Store
Description:
The consumer requests EAS information storage service from the ECS.
Inputs:
Outputs:
See clause 8.20.2.3 for details of usage of this operation.

8.20.4.3  Eecs_EASInfoManagement_Get operationp. 286

API operation name:
Eecs_EASInfoManagement_Get
Description:
The consumer obtains EAS information from the ECS.
Inputs:
Outputs:
See clause 8.20.2.2 for details of usage of this operation.

8.20.4.4  Eecs_EASInfoManagement_Remove operation |R19|p. 287

API operation name:
Eecs_EASInfoManagement_Remove
Description:
The consumer requests to remove EAS information from the ECS.
Inputs:
Outputs:
See clause 8.20.2.4 for details of usage of this operation.

8.20.4.5  Eecs_EASInfoManagement_Update operation |R19|p. 287

API operation name:
Eecs_EASInfoManagement_Update
Description:
The consumer requests EAS information update service from the ECS.
Inputs:
Outputs:
See clause 8.20.2.5 for details of usage of this operation.

Up   Top   ToC