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

Top   Top   Up   Prev   None
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… 
E Support for common EAS  E.1 General  E.2 Procedure  $ Change history 

 

E  Support for common EAS |R19|  p. 303

E.1  General  p. 303

Specific support for common EAS was introduced in Rel-18. This is an EAS which serves multiple UEs belonging to the same application group. Common EAS is required to ensure that the users belonging to the same application group receives same service. In Rel-18, whether to select common EAS for the group or not is based on ECSP policy.
Up

E.2  Procedure  p. 304

E.2.1  General  p. 304

Support for common EAS may require (re)use of following procedures (based on the deployment option as to whether ECS-ER is used or not):
Up

E.2.2  Common EAS support without repository function  p. 304

Figure E.2.2-1 illustrates the common EAS discovery and announcement procedure when repository function is not available.
Reproduction of 3GPP TS 23.558, Fig. E.2.2-1: Common EAS discovery and announcement (without repository function)
Figure E.2.2-1: Common EAS discovery and announcement (without repository function)
Up
Step 1.
If the EEC has not already cached the service provisioning information, the EEC sends a service provisioning request to the ECS (as per clause 8.3.3.2.2). The request may include Application group profile as per information flow specified in Table 8.3.3.3.2-1.
Step 2.
Upon receiving the request, the ECS processes the request (as per clause 8.3.3.2.2). When Application group profile is provided in the request, if the ECS-ER is not available, then the ECS identifies EES(s) based on the information contained in the request.
Step 3.
The ECS responds to the EEC's request with a service provisioning response (as per clause 8.3.3.2.2) that includes a list of EDN configuration information, which includes a list of relevant EES(s) information and EDN connection information. The response may contain singe EES (common EES) or multiple EESs.
Step 4.
The EEC sends an EAS discovery request to the EES (as per clause 8.5.2.2). The request includes Application group profile in the discovery filters as per information flow specified in Table 8.5.3.2-2.
Case a) Common EAS information is already available at the EES
Step a1.
If the common EAS information related to the Application Group ID is available at the EES, then the EES provides information of that EAS as result for EAS discovery (as per clause 8.5.2.2). The response message includes information elements as specified in Table 8.5.3.3-1.
Case b) Common EAS information is not available at the EES, EES selects common EAS (based on ECSP policy)
Step b1.
The EES identifies an EAS for the Application Group ID based on the provided EAS discovery filters.
Step b2.
If no ECS-ER is available and the EES initiates Retrieve EES request as specified in clause 8.8.3.3 to retrieve list of EESs for the common EAS announcement.
Step b3-b4.
When the ECS-ER is not available and the EES selects the common EAS, the selected common EAS is announced to other EES(s) as per procedure specified in clause 8.19.
Step b5.
The EES sends an EAS discovery response to the EEC (as per clause 8.5.2.2). The response message includes information elements as specified in Table 8.5.3.3-1.
Case c) Common EAS not available at EES, EEC selects the common EAS
Step c1.
The EES identifies the EAS(s) based on the provided EAS discovery filters and the UE location. The EES sends an EAS discovery response to the EEC (as per clause 8.5.2.2), which includes information about the discovered EASs (as specified in Table 8.5.3.3-1) based on the provided EAS discovery filters.
Step c2.
EEC selects an EAS from the list of EASs received in the EAS discovery response as the common EAS.
Step c3.
The EEC sends the EAS information provisioning request to the EES (as per clause 8.15.2.2). The request includes information elements as specified in Table 8.15.3.2-1.
Step c4.
When Application Group information is included in the request, the EAS provided is considered Common EAS for the Application Group. The EES determines the other EESs to which announce common EAS request needs to be sent as described in clause 8.8.3.3.
Step c5 - c6.
The selected common EAS is announced to other EES(s) as per procedure specified in clause 8.19.
Step c7.
The EES sends an EAS information provisioning response to the EEC indicating a successful status. The response message includes the information elements as specified in Table 8.15.3.2-1.
Up

E.2.3  Common EAS support with repository function  p. 306

Figure E.2.3-1 illustrates the common EAS discovery and announcement procedure when repository function is available.
Reproduction of 3GPP TS 23.558, Fig. E.2.3-1: Common EAS discovery and announcement (with repository)
Figure E.2.3-1: Common EAS discovery and announcement (with repository)
Up
Step 1.
Similar to step-1 in clause E.2.2.
Step 2.
Upon receiving the request, the ECS processes the request (as per clause 8.3.3.2.2). When Application group profile is provided in the request, if the ECS-ER is available,
  • EES information is not available corresponding to the Application Group ID, then the ECS identifies EES(s) and stores the identified EES(s)'s information and related Application group ID into the ECS-ER;
else if
  • EES information is available corresponding to the Application Group ID, then the ECS retrieves the EES(s) information corresponding to the Application Group ID from the ECS-ER.
Step 3.
Similar to step-3 in clause E.2.2.
Step 4.
Similar to step-4 in clause E.2.2.
Case a) Common EAS information is already available
Step a1.
Similar to step-a1 in clause E.2.2.
Case b) Common EAS not available at EES, EES selects common EAS (based on ECSP policy)
Step b1.
The EES identifies an EAS for the Application Group ID based on the provided EAS discovery filters.
Step b2 - b3.
If ECS-ER is available, the ECS interacts with the ECS-ER to store the common EAS information as described in clause 8.20.2.3. If common EAS information is already available corresponding to the Application Group ID in the repository, then the ECS-ER returns the common EAS information to the EES as described in clause 8.20.2.3.
Step b4.
Similar to step-b5 in clause E.2.2.
Case c) Common EAS not available at EES, EEC selects common EAS
Step c1.
Similar to step-c1 in clause E.2.2.
Step c2.
Similar to step-c2 in clause E.2.2.
Step c3.
Similar to step-c3 in clause E.2.2.
Step c4 - c5.
If there is ECS-ER, the EEC selected EAS is used in interaction between the EES and ECS-ER as specified in clause 8.20.2.3, and EEC receives common EAS in the EAS information provisioning response. If the common EAS is registered to another EES, then the EES endpoint of the EES where the common EAS is registered is also included in the EAS information provisioning response.
Step c6.
Similar to step-c7 in clause E.2.2.
Up

$  Change history  p. 309

Up   Top