Content for &nbsp; TS 23.433 &nbsp; Word version:&nbsp; 19.3.0

The VAL client/server determines to use SEALDD storage service, which could store/host data on behalf of the VAL client/server. The consumer (e.g. SEALDD client, VAL server) send a Sdd_DataStorage_Creation request to the SEALDD server, e.g. using the downlink push mode by VAL server over SEALDD-S interface, as defined in clause 9.1. The request includes the data to be stored and information associated with the data, such as access control policy, expiration time of the storage, etc, and optionally, the identifier of application data. The consumer may also specify in the request the management or status information of the data storage that is required (e.g., information about how often the stored data is accessed or managed).

The SEALDD server checks for the authorization of the storage service creation request. If the request is successfully authorized, then the SEALDD server configures the storage service based on the request and stores the data at the storage server. If status information of the stored data is requested, the SEALDD server will start to monitor the status of the stored data, such as to track the accesses to the data for the data access status.

Figure 9.5.2.2-1: Storage service reservation

The SEALDD server sends a response to the requesting consumer (e.g. SEALDD client, VAL server). The response indicates if the request is accepted and the identifier of the stored data (if applicable). Upon receiving the response, the requesting consumer may create a record for the stored data.

9.5.2.2 Data storage reservation p. 56

Pre-conditions:

The VAL server has discovered and selected the SEALDD server by CAPIF functions.
The SEALDD client has discovered and selected the SEALDD server as specified in clause 9.4.3.

Reproduction of 3GPP TS 23.433, Fig. 9.5.2.2-1: Storage service reservation

The consumer (e.g. SEALDD client, VAL server) send a Sdd_DataStorage_Creation request to the SEALDD server. The request includes the VAL service ID and the data length.

The SEALDD server checks for the authorization of the storage service Creation request. If the request is successfully authorized, then the SEALDD server allocates and reserves the address for data storage.

Figure 9.5.2.3-1: Access to stored data in SEALDD server

The SEALDD server sends a response to the requesting consumer (e.g. SEALDD client, VAL server). The response indicates if the request is accepted and the address for data storage. Upon receiving the response, the stored data may be delivered via push mode from the requesting consumer to the SEALDD server.

9.5.2.3 Data storage fetch p. 57

Pre-conditions:

VAL client/server has stored data in SEALDD server.
The consumer (e.g. SEALDD client/VAL server/other SEALDD server) requesting the stored data has got the identifier of the stored data (e.g. via application layer signalling or other mechanisms).

Reproduction of 3GPP TS 23.433, Fig. 9.5.2.3-1: Access to stored data in SEALDD server

The consumer (e.g. SEALDD client/VAL server/other SEALDD server) sends a Sdd_DataStorage_Fetch request to the SEALDD server with the identifier of the stored data.

Upon receiving the request, the SEALDD server performs an authorization check to verify if the requested data (according to the data access control policy) can be accessed by the consumer. The SEALDD server will also check whether the stored data is expired. If the requested data fetched by SEALDD client is not be stored by the SEALDD server, the SEALDD server may use the downlink pull mode if possible, to retrieve the data/content from the VAL server over SEALDD-S interface, as defined in clause 9.1.

Figure 9.5.2.4-1: Storage management procedure

If the verification was successful, the SEALDD server responds with the requested data.

9.5.2.4 Data storage management p. 58

Pre-conditions:

The SEALDD service is configured to track and maintain data storage access information (i.e. status information).
A storage service creation request procedure from the consumer (e.g. SEALDD client, VAL server) to the SEALDD server has been performed. The request includes a subscription to data storage access information (i.e. status information).

Reproduction of 3GPP TS 23.433, Fig. 9.5.2.4-1: Storage management procedure

Based on the received stored data status information, the requesting consumer (e.g. SEALDD client, VAL server) determines to perform a management operation, such as to update, refresh, or delete the stored data. The VAL client/server sends a Sdd_DataStorage_Management request to the SEALDD server to perform the determined management operation.

The SEALDD server processes the storage management request. If the request is accepted, the SEALDD server performs the required management operation on the stored data.

Figure 9.5.2.5-1: Stored data transfer procedure between VAL servers

The SEALDD server sends a response to the requesting consumer (e.g. SEALDD client, VAL server) with the result of the management operation, which may include updated information of the stored data.

9.5.2.5 Stored data transfer between VAL servers via SEALDD server p. 58

Pre-conditions:

The source VAL server already obtains the serving target SEALDD server of the target VAL server.
The source VAL server may have stored data to the source SEALDD server and obtained the identifier of the stored data by invoking Sdd_DataStorage_Creation API in clause 9.5.2.1.

Reproduction of 3GPP TS 23.433, Fig. 9.5.2.5-1: Stored data transfer procedure between VAL servers

The VAL server sends a SEALDD data storage delivery subscription request to its serving SEALDD server with the VAL server information, and the VAL server address to receive the stored data delivery.

The SEALDD sever responds to the requested VAL server with the subscription result, if successful, the response includes the subscription ID, expiration time.