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.20 Interaction with ECS with Repository function  8.20.1 General  8.20.2 Procedure  8.20.2.1 General  8.20.2.2 Obtain EAS information  8.20.2.3 Common EAS information storage  8.20.3 Information flows  8.20.3.1 General  8.20.3.2 EAS information get request  8.20.3.3 EAS information get response  8.20.3.4 Common EAS information store request  8.20.3.5 Common EAS information store response  8.20.4 APIs  8.20.4.1 General  8.20.4.2 Eecs_EASInfoManagement_Store operation  8.20.4.3 Eecs_EASInfoManagement_Get operation 
...

 

8.20  Interaction with ECS with Repository function |R18|  p. 263

8.20.1  General  p. 263

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  Procedure  p. 263

8.20.2.1  General  p. 263

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 information  p. 263

Reproduction of 3GPP TS 23.558, Fig. 8.20.2.2-1: Obtain EAS information
Figure 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.
Up

8.20.2.3  Common EAS information storage  p. 263

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
Figure 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 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.3  Information flows  p. 264

8.20.3.1  General  p. 264

The information flows are specified for EAS information service.

8.20.3.2  EAS information get request  p. 264

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:
Only one of these IEs may be present in the message.
Up

8.20.3.3  EAS information get response  p. 265

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.
> 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 request  p. 265

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.
NOTE:
Only one of these IEs may be present in the message.
Up

8.20.3.5  Common EAS information store response  p. 266

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.4  APIs  p. 266

8.20.4.1  General  p. 266

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

8.20.4.2  Eecs_EASInfoManagement_Store operation  p. 266

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

8.20.4.3  Eecs_EASInfoManagement_Get operation  p. 266

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

Up   Top   ToC