Content for  TS 23.558  Word version:  19.3.0

The EEC sends the EAS information provisioning request to the EES:

1. "ACR scenario selection announcement". The request may include ACR scenario list selected by the EEC, EEC security credentials, selected EASID, selected EAS endpoint, EECID and ACID. For the EAS bundles scenario, the request may include the ACR scenario list for EAS bundles selected by the EEC.
2. "ACR scenario selection request". The request may include AC profile, EEC service continuity support, EEC security credentials, EECID and ACID.
3. "EAS selection". Informs the EES of EAS selection. When Application Group information is included in the request, the EAS provided is considered Common EAS for Application Group.

The EAS information provisioning request may include associated EES(s) endpoint and the DNAIs and service area of the selected EAS(s). If the EEC has selected an EAS which is instantiable but not yet instantiated, the EEC includes the selected EASID without including the selected EAS endpoint in the request. The request may contain the associated EES(s) information along with the bundle EAS information (i.e. list of EASID) and the bundle EAS type indicating direct bundle, each associated EES(s) is along with part of or all the list of EASID, when EEC determines the associated EES(s) based on the EDN configuration information and bundle EAS information (e.g. list of EASID and direct bundle type).

Upon receiving the request from the EEC, the EES validates the EEC information request and verifies if the EEC is authorized for this operation.

1. "ACR scenario selection announcement". The EES may send the ACR Selection notification to the selected EAS if the EAS has subscribed and if EES allows EEC based ACR scenario selection. Otherwise, EES may respond with status failure and include appropriate reason. For the EAS bundles scenario, the EES may send the ACR selection notification to the bundled EAS(s).
2. "ACR scenario selection request". The EES selects the ACR scenario list and may send the ACR Selection notification to the selected EAS if the EAS has subscribed. The EES may include the ACR scenario list in the EAS information provisioning response. For the EAS bundles scenario, the EES selects the ACR scenario list for EAS bundles based on the AC/EEC/EES(s)/EAS(s) service continuity support, and sends the ACR scenario list to the bundled EAS(s).
3. "EAS selection". When Application Group information is not provided, the EES determines that the EAS in the request is providing services to the AC with the indicated ACID e.g. for EEC Context handling purposes as described in clause 8.9. When Application Group information is included in the request, the EAS provided is considered Common EAS for the Application Group.

If the EEC or EES selected ACR scenario list for EAS bundle includes EAS executed ACR scenario (as described in clause 8.8.2.8), the EES also sends DNAIs and service area of the selected EAS(s) to the main EAS in the ACR selection notification. The request may contain the associated EES(s) information along with the bundle EAS information (i.e. list of EASID) and the bundle EAS type indicating direct bundle, each associated EES(s) is along with part of or all the list of EASID, when EEC determines the associated EES(s) based on the EDN configuration information and bundle EAS information (e.g. list of EASID and direct bundle type). If the request contains selected EAS ID and selected EAS Endpoint, the EES may apply the EAS traffic influence with the N6 routing information of the EAS in the 3GPP Core Network, based on application KPIs and if the EAS traffic influence was not done before (e.g. neither in EAS discovery procedure nor the EAS perform traffic influence). When the selection is that of a common EAS for application group, the request message may contain the list of EESs for a certain Application Group ID, received from the ECS in the service provisioning response message. This application group related information may be used for further common EAS announcement(s) between EES(s). In the case of no ECS-ER, if the request message does not contain the list of EESs for a certain Application Group ID, then the EES determines the other EESs to which announce common EAS request needs to be sent as described in clause 8.8.3.3. If there is ECS-ER, the EEC selected EAS is used in interaction between the EES and ECS-ER, as described in clause 8.20.2.3 to store the common EAS information., If the ECS-ER provides a different common EAS information in the response it is forwarded to the EEC in the EAS information provisioning response. If the ECS-ER-provided 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. If the request contains the selected EASID and the selected EAS endpoint is not included, the EES verifies if instantiation of EAS is needed and may trigger the ECSP management system to instantiate the EAS as in clause 8.12. When the request contains EEC Service Continuity Support IE and the EEC context has been established, the EES includes the IE into the EEC context described in Table 8.2.8-1.

IIf the processing of the request was successful, the EES sends an EAS information provisioning response to the EEC indicating a successful status. If an EEC context has been established, the response also includes the list of selected ACR scenario(s) into the session context IE within EEC context as described in Table 8.2.8-2; otherwise, the EES shall indicate a failure status and include appropriate reasons. If the EES has triggered EAS instantiation based on the EAS information provisioning request and obtained the newly instantiated EAS information, the response contains information about the newly instantiated EAS, including the EAS endpoint information.