Content for TS 23.433 Word version: 19.3.0
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…
9.12…
A…
C
D…
9.5.3 Information flows
9.5.3.1 SEALDD data storage creation request
9.5.3.2 SEALDD data storage creation response
9.5.3.3 SEALDD data storage status notification
9.5.3.4 SEALDD data storage fetch request
9.5.3.5 SEALDD data storage fetch response
9.5.3.6 SEALDD data storage management request
9.5.3.7 SEALDD data storage management response
9.5.3.8 SEALDD data storage delivery subscription request
9.5.3.9 SEALDD data storage delivery subscription response
9.5.3.10 SEALDD data storage delivery notification
9.5.3.11 SEALDD data storage delivery request
9.5.3.12 SEALDD data storage delivery response
9.5.3.13 SEALDD delivery connection establish request
9.5.3.14 SEALDD delivery connection establish response
...
...
9.5.3 Information flows p. 60
9.5.3.1 SEALDD data storage creation request p. 60
Table 9.5.3.1-1 describes the information flow from the requesting consumer (e.g., VAL server, SEALDD client) to the SEALDD server for requesting the data storage creation.
| Information element | Status | Description |
|---|---|---|
| Application data | M
(See NOTE 1) | The application data needed to be stored in the SEALDD server |
| Access control policy | O
(See NOTE 1) | The control policy for the requested data access from other consumers (e.g. SEALDD client, VAL server, other SEALDD server) |
| Storage expiration time | O
(See NOTE 1) | The expiration time for the stored data |
| Storage management or status information | O
(See NOTE 1) | Management or status information of the stored data to be tracked or monitored by SEALDD server (e.g. statistics of the stored data, Indications of how often the stored data is accessed or managed) for corresponding notifications. |
| VAL service ID | M
(See NOTE 2) | Identify of the data type to be stored, e.g. video, voice |
| Data length | O
(See NOTE 2) | Identify of the data length to be stored |
| Identifier of application data | O | Identify of the application data |
|
NOTE 1:
These IEs are used for storing application data to the SEALDD server directly, as specified in clause 9.5.2.1.
NOTE 2:
These IEs are used for requesting the SEALDD server to reserve the data storage resource and address, as specified in clause 9.5.2.2.
|
||
9.5.3.2 SEALDD data storage creation response p. 60
Table 9.5.3.2-1 describes the information flow from the SEALDD server to the requesting consumer (e.g., VAL server, SEALDD client) for responding the data storage creation request.
| Information element | Status | Description |
|---|---|---|
| Result | M | Success or failure. |
| Identifier of the stored data | O
(See NOTE 1, NOTE 3) | Identify of the stored data |
| Address for data storage | O
(See NOTE 2) | The reserved address for data storage |
|
NOTE 1:
This IE is used for returning the identifier of the stored data, as specified in clause 9.5.2.1.
NOTE 2:
This IE is used for returning the reserved address for data storage, as specified in clause 9.5.2.2.
NOTE 3:
This IE is same as the identifier of application data, if the identifier of application data is provided in SEALDD data storage creation request message.
|
||
9.5.3.3 SEALDD data storage status notification p. 60
Table 9.5.3.3-1 describes the information flow from the SEALDD server to the requesting consumer (e.g., VAL server, SEALDD client) for sending notifications of the data storage status, as configured in the data storage creation request.
| Information element | Status | Description |
|---|---|---|
| Management or status information of stored data | M | The management or status information of the stored data requested in the storage creation request. |
9.5.3.4 SEALDD data storage fetch request p. 61
Table 9.5.3.4-1 describes the information flow from the requesting consumer (e.g., SEALDD client, VAL server, other SEALDD server) to the SEALDD server for requesting the data storage fetch.
| Information element | Status | Description |
|---|---|---|
| Identifier of the stored data | M | Identify the stored data queried by the requesting consumer |
9.5.3.5 SEALDD data storage fetch response p. 61
Table 9.5.3.5-1 describes the information flow from the SEALDD server to the requesting consumer (e.g., SEALDD client, VAL server, other SEALDD server) for responding the data storage fetch request.
| Information element | Status | Description |
|---|---|---|
| Result | M | Success or failure. |
| The fetched application data | O | The fetched application data returned to the requesting consumer |
9.5.3.6 SEALDD data storage management request p. 61
Table 9.5.3.6-1 describes the information flow from the requesting consumer (e.g., SEALDD client, VAL server) to the SEALDD server for requesting the data storage management.
| Information element | Status | Description |
|---|---|---|
| Storage management operation | M | The operation (e.g. update, refresh, or delete) to manage the stored data |
9.5.3.7 SEALDD data storage management response p. 61
Table 9.5.3.7-1 describes the information flow from the SEALDD server to the requesting consumer (e.g., VAL server, SEALDD client) for responding the data storage management request.
| Information element | Status | Description |
|---|---|---|
| Result | M | Success or failure. |
| The updated information of stored data | O | The updated management or status information of the stored data |
9.5.3.8 SEALDD data storage delivery subscription request p. 61
Table 9.5.3.8-1 describes the information flow from the VAL server to the SEALDD server for data storage delivery subscription.
| Information element | Status | Description |
|---|---|---|
| VAL server information | M | Identify the requested VAL server to subscribe data delivery |
| VAL server address | M | Address/port of the VAL server to receive the data delivery from the SEALDD server |
9.5.3.9 SEALDD data storage delivery subscription response p. 62
Table 9.5.3.9-1 describes the information flow from the SEALDD server to the VAL server for responding the data storage delivery subscription request.
| Information element | Status | Description |
|---|---|---|
| Result | M | Success or failure. |
| Subscription ID | O | Subscription identifier corresponding to the subscription. |
| Expiration time | O | Indicates the expiration time of the subscription. |
9.5.3.10 SEALDD data storage delivery notification p. 62
Table 9.5.3.10-1 describes the information flow from the SEALDD server to the VAL server for notifying the received stored data.
| Information element | Status | Description |
|---|---|---|
| Subscription ID | M | Subscription identifier corresponding to the subscription. |
| Stored data | O
(See NOTE) | The received data corresponding to the VAL server |
| Identifier of the stored data | O
(See NOTE) | Identify of the received stored data in SEALDD server |
|
NOTE:
One of these IEs shall be present in the message.
|
||
9.5.3.11 SEALDD data storage delivery request p. 62
Table 9.5.3.11-1 describes the information flow from the VAL server to the SEALDD server for requesting the data storage delivery.
| Information element | Status | Description |
|---|---|---|
| Target VAL server information | M | Identify the target VAL server |
| Target SEALDD server information | O | Identify the target SEALDD server |
| Identifier of the stored data | O
(See NOTE) | Identify of the stored data needed to be delivered |
| Stored data | O
(See NOTE) | The data from the VAL server |
|
NOTE:
One of these IEs shall be present in the message.
|
||
9.5.3.12 SEALDD data storage delivery response p. 62
Table 9.5.3.12-1 describes the information flow from the SEALDD server to the VAL server for responding the data storage delivery request.
| Information element | Status | Description |
|---|---|---|
| Result | M | Success or failure. |
9.5.3.13 SEALDD delivery connection establish request p. 63
Table 9.5.3.13-1 describes the information flow from the source SEALDD server to the target SEALDD server for requesting the SEALDD delivery connection establishment.
| Information element | Status | Description |
|---|---|---|
| Source SEALDD server information | M | Identify the source SEALDD server. |
| Traffic descriptor of source SEALDD server | O | The traffic descriptor (e.g. address, port, transport layer protocol) of the source SEALDD server. |
| Target VAL server information | M | Identify the target VAL server. |
9.5.3.14 SEALDD delivery connection establish response p. 63
Table 9.5.3.14-1 describes the information flow from the target SEALDD server to the source SEALDD server for responding the SEALDD delivery connection establishment request.
| Information element | Status | Description |
|---|---|---|
| Result | M | Success or failure. |
| Traffic descriptor of target SEALDD server | O | The traffic descriptor (e.g. address, port, transport layer protocol) of the target SEALDD server. |
