Step 1.
The VAL server can discover and select the SEALDD server (e.g. by CAPIF functions).
Step 2.
The VAL server decides to use SEALDD service to enhance data transmission and send a regular SEALDD data transmission subscription request to the SEALDD server.
Step 3.
Upon receiving the request, the SEALDD server performs an authorization check and responds with a regular SEALDD data transmission subscription response.
Step 4.
The VAL server (as an EAS) registers to the EES as described in
clause 8.4.3.2.2 of TS 23.558 with the associated SEALDD server address as EAS Endpoint in the EAS profile. The EAS ID used by VAL server in registration may indicate the application service association between the VAL service and SEALDD service implicitly or explicitly.
This procedure reuses the current procedure described in
clause 8.4.3.2.2 of TS 23.558. The VAL server (as an EAS) registers to the EES with the associated SEALDD server address as the EAS Endpoint in the EAS profile. Then the EEC can use the EAS discovery procedure defined in
clause 8.5 of TS 23.558 to find the VAL server's address which is SEALDD server's address. The VAL client can initiate SEALDD service via SEALDD client with the SEALDD server's address. This procedure can be used for scenario (a).
Step 1.
The SEALDD server (as an EAS) registered to EES with SEALDD profile (i.e. EAS profile) as an API provider.
Step 2.
The EAS (VAL) server can discover and select the SEALDD server (e.g. by CAPIF functions).
Step 3.
The EAS (VAL server) decides to use SEALDD service to enhance data transmission and send a regular SEALDD data transmission subscription request to the SEALDD server.
Step 4.
Upon receiving the request, the SEALDD server performs an authorization check and responds with a regular SEALDD data transmission subscription response.
Step 5.
The VAL server (as an EAS) registers to the EES as described in
clause 8.4.3.2.2 of TS 23.558 with the associated SEALDD server information (i.e. SEALDD service and SEALDD server address) as associated EAS ID and EAS Endpoint in the EAS profile.
This procedure reuses the current procedure described in
clause 8.4.3.2.2 of TS 23.558. The VAL server (as an EAS) registers to the EES with the associated SEALDD server information (i.e. SEALDD service and SEALDD server address) as associated EAS ID and EAS Endpoint in the EAS profile. Then the EEC can use the EAS discovery procedure defined in
clause 8.5 of TS 23.558 to find the VAL server's address and associated SEALDD server's address. The VAL client can initiate SEALDD service via SEALDD client with the SEALDD server's address. For scenario (b), the VAL client can also establish the connection with VAL server using the VAL server's information for application signalling transfer and only use the SEALDD connection for application data transfer.
Step 1.
The VAL server (acting as an EAS) registers to the EES.
Step 2.
The SEALDD server (acting as an EAS) registers to the EES.
Step 3.
The EEC performs service provisioning procedure as described in
clause 8.3.3.2.2 of TS 23.558. The EEC is responded with the EES which supports the SEALDD server and the VAL server. The EEC sends the EAS discovery request for EAS bundle including VAL service and SEALDD service. The EES may collect the performance of VAL server and SEALDD server (e.g. E2E latency between the SEALDD server and client and load information of SEALDD and VAL server) from the ADAE server when receiving the EAS discovery request, as specified in
clause 8.2.2 (for transmission quality, e.g. E2E latency) and
8.8.2 (for edge load) of
TS 23.436.
Step 4.
The EES identifies the VAL server and the associated SEALDD server based on the performance of VAL server and the performance of SEALDD server (e.g. to satisfy the AC service KPI).
Step 5.
The EES sends the EAS discovery response to EEC, including the SEALDD server address, the VAL server address.
Upon receiving the SEALDD server address, the VAL server address, the VAL client can initiate SEALDD service via SEALDD client with the SEALDD server's address. The data transmission between the VAL client and the VAL server can be enabled via the SEALDD connection, as specified in
clause 9.2.2.