SEALDD server Service Preparation Phase (This Phase is used by the VAL server to get SEALDD server prepared for SEALDD client access):

1. When the VAL server decides to use the SEALDD service for data transmission enhancement, it discovers the SEALDD server (e.g. by CAPIF).
2. Then the VAL server triggers SEALDD service subscription procedure to the discovered SEALDD server, in that procedure, SEALDD server is associated with the VAL server, and specific SEALDD server resource (e.g. address/port of the SEALDD server for redundant transmission) is allocated for the VAL server's service to transfer SEALDD traffic.
3. For EDN scenario, the SEALDD server or VAL server will register the association information to the EES.

SEALDD client Service Consuming Phase (When SEALDD server is prepared in SEALDD server Service Preparation Phase, the VAL client(s) can trigger SEALDD client to connect to specific prepared SEALDD server for SEALDD service):

1. When VAL client request to use SEALDD service to transmit the VAL traffic to VAL server, the VAL client or SEALDD client can discover the proper SEALDD server associated with the VAL server (e.g. via EAS discovery, DNS query, pre-configuration or Application layer signalling).
2. Then SEALDD client can interact with SEALDD server to negotiate for SEALDD data transfer. If Address/Port is allocated in SEALDD service subscription phase, it will be notified to SEALDD client in this step.
3. Data transmission connection is established between the SEALDD client and SEALDD server for SEALDD traffic transfer.
4. The whole configuration is accomplished and the VAL traffic is transferred via the SEALDD connection.