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.433  Word version:  19.1.0

Top   Top   Up   Prev   Next
0…   4…   7…   8…   9.2…   9.2.2.3…   9.2.3…   9.2.4…   9.3…   9.3.2.2…   9.3.3…   9.3.4…   9.4…   9.5…   9.5.3…   9.5.4…   9.6…   9.7…   9.7.3…   9.7.4…   9.8…   9.9…   9.9.3…   9.10…   9.10.3…   9.11…   9.11.3…   A…   C   D… 
9.11 SEALDD Background data transfer  9.11.1 General  9.11.2 Procedures  9.11.2.1 SEALDD Background data transfer  9.11.2.2 SEALDD Background data transfer subscription update  9.11.2.3 SEALDD Background data transfer unsubscribe 
...

 

9.11  SEALDD Background data transfer |R19|  p. 91

9.11.1  General  p. 91

The following clauses specify procedures and information flow for SEALDD Background data transfer (BDT). The SEALDD supports BDT in downlink (DL) centric direction, e.g., streaming a video clip to the VAL client, and in uplink (UL) centric direction, e.g., uploading drone captured data to the VAL server.

9.11.2  Procedures  p. 91

9.11.2.1  SEALDD Background data transfer  p. 91

Figure 9.11.2.1-1 illustrates the procedure for SEALDD Background data transfer.
Reproduction of 3GPP TS 23.433, Fig. 9.11.2.1-1: SEALDD Background data transfer
Figure 9.11.2.1-1: SEALDD Background data transfer
Up
Step 1.
The VAL server sends a SEALDD Background data transfer subscription request to the SEALDD server. The request includes the VAL service ID and list of VAL UE IDs or VAL group ID and may also include desired time window, desired area information (e.g., when a UE enters a geographical area), Policy Selection Guidance, data volume.
Step 2.
The SEALDD server authorizes the request from the VAL server.
Step 3.
The SEALDD server starts the BDT configuration negotiation with the SEAL NRM server as described in clause 14.3.13 of TS 23.434. The SEALDD server performs Network resource adaptation negotiation with the SEAL NRM server as described in clause 14.3.3.3 of TS 23.434. Policies are set for the BDT data transfer using the previously negotiated BDT Reference ID.
Step 4.
The SEALDD server sends the SEALDD Background data transfer subscription response, containing the result of the operation which includes the result and may include the BDT subscription identifier.
Step 5.
The VAL server uses clause 9.5.2 procedure to sends the BDT data to the SEALDD server. During the transmission time window, the SEALDD server sends the BDT data to SEALDD client(s) and monitors the quality, e.g., latency, jitter, bitrate, packet loss rate, of the transmission. The SEALDD client forwards the BDT data received to the VAL client.
Step 6.
The SEALDD server notifies the VAL server about the delivery result by sending the SEALDD Background data transfer notification including the BDT subscription identifier and optionally the list of VAL UEs which received the BDT data, the executed time window and quality of the BDT data transmission based on the measurements in step 5.
Up

9.11.2.2  SEALDD Background data transfer subscription update  p. 92

Figure 9.11.2.2-1 illustrates the procedure for SEALDD Background data transfer subscription update from VAL server to the SEALDD server.
Pre-condition:
  • The SEALDD Background data transfer in DL direction procedure has been performed.
Reproduction of 3GPP TS 23.433, Fig. 9.11.2.2-1: SEALDD Background data transfer subscription update
Figure 9.11.2.2-1: SEALDD Background data transfer subscription update
Up
Step 1.
The VAL server can trigger a BDT update by sending a SEALDD Background data transfer subscription update request. The request contains BDT subscription identifier and may contain desired time window, desired area information (e.g., when a UE enters a geographical area), Policy Selection Guidance, data volume.
Step 2.
The SEALDD server starts a new BDT configuration negotiation with the SEAL NRM server as described in clause 14.3.13.5 of TS 23.434. The SEALDD also performs Network resource adaptation negotiation with the SEAL NRM server as described in clause 14.3.3.3 of TS 23.434 for the new BDT transmission.
Step 3.
The SEALDD server sends the SEALDD Background data transfer subscription update response to the VAL server, containing result and optionally the BDT subscription identifier.
Up

9.11.2.3  SEALDD Background data transfer unsubscribe  p. 93

Figure 9.11.2.3-1 illustrates the procedure for SEALDD Background data transfer unsubscribe from either the SEALDD client or VAL server to the SEALDD server.
Pre-condition:
  • The SEALDD Background data transfer procedure has been performed.
Reproduction of 3GPP TS 23.433, Fig. 9.11.2.3-1: SEALDD Background data transfer unsubscribe
Figure 9.11.2.3-1: SEALDD Background data transfer unsubscribe
Up
Step 1.
The VAL server can trigger a BDT deletion by sending a SEALDD Background data transfer unsubscribe request to the SEALDD server. The request contains the BDT subscription identifier.
Step 2.
The SEALDD server negotiates the BDT configuration with the SEAL NRM server as described in clause 14.3.13.6 of TS 23.434 and deletes any stored application data related to the BDT subscription identifier.
Step 3.
The SEALDD server sends the SEALDD Background data transfer unsubscribe response to the VAL server, containing result of the operation.
Up

Up   Top   ToC