hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.2.3 SEALDD enabled URLLC transmission connection establishment based on policy
|
The SEALDD servers has Data Delivery (DD) policy being provisioned. The DD policy includes reliable transmission service for the associated VAL traffic. Before the application communication between VAL client and VAL server starts, the DD policy is enforced by the SEALDD server to establish the SEALDD connection.
Pre-conditions:
1. The SEALDD server has DD policies available.
Figure 9.3.2.3-1: Policy enforced by SEALDD server for redundant connectivity
The procedure is same as step 1 to 7 in clause 9.2.2.3 with differences that:
- in step 2, the SEALDD server enforces the policy to trigger URLLC transmission connection establishment.
- in step 5 and 6, the SEALDD server allocates dual SEALDD-S connection information for sending and receiving packet over SEALDD-UU reference point, then SEALDD server sends URLLC transmission connection establishment request to the SEALDD client with SEALDD-UU flow IDs, VAL service ID, the dual IP address and port. The request is responded by the SEALDD client. Dual UE IP address (and port) may be included by the SEALDD client in the response or sent in a separate update message by SEALDD client if a different UE IP address is to be used in SEALDD connection user plane.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.2.4 SEALDD enabled URLLC transmission connection deletion based on policy
|
Figure 9.3.2.4-1: SEALDD enabled URLLC transmission connection deletion
The procedure is same as step 1 to 8 in clause 9.2.2.4 with differences that in step 4 to 5, the SEALDD server requests URLLC transmission connection deletion to the SEALDD client and the SEALDD client responds with URLLC transmission connection deletion response.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.2.5 SEALDD client initiated connection release
|
Figure 9.3.2.5-1 illustrates the procedure for SEALDD client initiated connection release procedure from the SEALDD client to the SEALDD server.
Figure 9.3.2.5-1: SEALDD client initiated connection release
1. The SEALDD client sends the SEALDD URLLC connection release request to the SEALDD server to release the established connection.
2. The SEALDD server releases the SEALDD-UU redundant data transmission connection (which was established by SEALDD client or SEALDD server) and sends the response in the SEALDD URLLC connection release response message. Upon receiving the acknowledgement, the SEALDD client releases the connection resources.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.3 Information flows
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.3.1 SEALDD URLLC transmission request
|
See clause 9.2.3.1 for the details of information flow with the following clarification:
- The bandwidth related IEs are not applicable.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.3.2 SEALDD URLLC transmission response
|
See clause 9.2.3.2 for the details of information flow.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.3.3 SEALDD URLLC transmission connection establishment request
|
Table 9.3.3.3-1 describes the information flow from the SEALDD client to the SEALDD server or from the SEALDD server to the SEALDD client for requesting the URLLC transmission connection establishment.
Table 9.3.3.3-1: SEALDD URLLC transmission connection establishment request
Information element
Status
Description
SEALDD client ID
O
Identity of the SEALDD client.
Identity
O
The VAL user ID of the VAL user or VAL UE ID
SEALDD-UU flow IDs
M
(See NOTE 1)
Identity of the SEALDD-UU flows.
VAL server ID
O
(See NOTE 1)
Identity of the VAL server.
VAL service ID
O
(See NOTE 1)
Identity of the VAL service.
SEALDD traffic descriptors
O
A pair of SEALDD traffic descriptors (e.g. address, port, transport layer protocol) of the SEALDD client side (for client side initiated request) or the SEALDD server side (for server side initiated request) used to establish redundant SEALDD connection.
Capability for BAT and periodicity adaptation
O
(See NOTE 2)
Indicates BAT and periodicity adaptation capability of the SEALDD client (for client side initiated request).
For URLLC transmission, it includes capability for BAT and periodicity adaptation per SEALDD traffic descriptor.
Transmission assistance info
O
(See NOTE 2, NOTE 3)
Indicates transmission assistance information for uplink SEALDD traffic of the SEALDD client side (for client side initiated request).
It includes BAT, BAT window, periodicity, and periodicity range.
For URLLC transmission, it includes assistance information per SEALDD traffic descriptor.
NOTE 1: The SEALDD-UU flow ID is used by the SEALDD client and SEALDD server to identify different application traffic, and it is mapped from the VAL service ID.
NOTE 2: If provided, BAT window and periodicity range are mutually exclusive with capability for BAT and periodicity adaptation.
NOTE 3: The periodicity range may only be present together with the periodicity when BAT and BAT window are present. The BAT window may only be present together with the BAT.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.3.4 SEALDD URLLC transmission connection establishment response
|
Table 9.3.3.4-1 describes the information flow from the SEALDD server to the SEALDD client or from the SEALDD client to the SEALDD server for responding to the URLLC transmission connection establishment.
Table 9.3.3.4-1: SEALDD URLLC transmission connection establishment response
Information element
Status
Description
Result
M
Indicates the success or failure of establishing the SEALDD connection.
SEALDD traffic descriptors
O
A pair of SEALDD traffic descriptors (e.g. address, port, transport layer protocol) of the SEALDD server side (for client side initiated request) or the SEALDD client side (for server side initiated request) used to establish redundant SEALDD connection.
Cause
O
(See NOTE 1)
Indicates the reason for the failure, e.g. SEALDD policy mismatch.
Capability for BAT and periodicity adaptation
O
(See NOTE 2)
Indicates BAT and periodicity adaptation capability for SEALDD client in server side initiated request.
For URLLC transmission, it includes capability for BAT and periodicity adaptation per SEALDD traffic descriptor.
Transmission assistance info
O
(See NOTE 2, NOTE 3)
Indicates transmission assistance information for uplink SEALDD traffic of the SEALDD client side (for server side initiated request).
It includes BAT, BAT window, periodicity, and periodicity range.
For URLLC transmission, it includes assistance information per SEALDD traffic descriptor.
NOTE 1: The IE is only present if the Result is failure.
NOTE 2: If provided, BAT window and periodicity range are mutually exclusive with capability for BAT and periodicity adaptation.
NOTE 3: The periodicity range may only be present together with the periodicity when BAT and BAT window are present. The BAT window may only be present together with the BAT.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.3.5 SEALDD URLLC transmission connection update request
|
Table 9.3.3.5-1 describes the information flow from the SEALDD client to the SEALDD server for requesting the URLLC transmission connection update.
Table 9.3.3.5-1: SEALDD URLLC transmission connection update request
Information element
Status
Description
SEALDD client ID
M
Identity of the SEALDD client.
SEALDD-UU flow IDs
M
(See NOTE)
Identity of the SEALDD-UU flows.
VAL server ID
O
(See NOTE)
Identity of the VAL server.
VAL service ID
O
(See NOTE)
Identity of the VAL service.
SEALDD traffic descriptors
O
A pair of SEALDD traffic descriptors (e.g. address, port, transport layer protocol) of the SEALDD client side used to establish redundant SEALDD connection.
NOTE: The SEALDD-UU flow IDs is used by the SEALDD client and SEALDD server to identify different application traffic, and it is mapped from the VAL service ID.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.3.6 SEALDD URLLC transmission connection update response
|
Table 9.3.3.6-1 describes the information flow from the SEALDD server to the SEALDD client for responding to the redundant transmission connection update.
Table 9.3.3.6-1: SEALDD URLLC transmission connection update response
Information element
Status
Description
Result
M
Indicates the success or failure of updating the SEALDD connection.
Cause
O
See NOTE
Indicates the reason for the failure, e.g. SEALDD policy mismatch.
NOTE: The IE is only present if the Result is failure
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.3.7 SEALDD URLLC transmission connection release request
|
See clause 9.2.3.5 for the details of information flow.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.3.8 SEALDD URLLC transmission connection release response
|
See clause 9.2.3.6 for the details of information flow.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.4 APIs
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.4.1 General
|
Table 9.3.4.1-1 illustrates the APIs exposed by SEALDD server for URLLC transmission.
Table 9.3.4.1-1: List of SEALDD server APIs for redundant transmission
API Name
API Operations
Operation Semantics
Consumer(s)
Sdd_URLLCTransmission
Request
Request/Response
VAL server
Sdd_URLLCTransmissionConnnection
Establish
Request/Response
SEALDD client, SEALDD server
Update
Request/Response
SEALDD client, SEALDD server
Release
Request/Response
SEALDD client, SEALDD server
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.4.2 Sdd_URLLCTransmission Request operation
|
API operation name: Sdd_URLLCTransmission Request
Description: The consumer requests for one time for URLLC transmission service.
Inputs: See clause 9.3.3.1.
Outputs: See clause 9.3.3.2
See clause 9.3.2.1 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.4.3 Sdd_URLLCTransmissionConnection_Establish operation
|
API operation name: Sdd_URLLCTransmissionConnection_Establish
Description: The consumer requests for URLLC transmission connection establishment.
Inputs: See clause 9.3.3.3.
Outputs: See clause 9.3.3.4.
See clause 9.3.2.1 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.4.4 Sdd_URLLCTransmissionConnection_Update operation
|
API operation name: Sdd_URLLCTransmissionConnection_Update
Description: The consumer requests or URLLC transmission connection update.
Inputs: See clause 9.3.3.5.
Outputs: See clause 9.3.3.6.
See clause 9.3.2.1 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.4.5 Sdd_URLLCTransmissionConnection_Release operation
|
API operation name: Sdd_URLLCTransmissionConnection_Release
Description: The consumer requests for URLLC transmission connection release.
Inputs: See clause 9.3.3.7.
Outputs: See clause 9.3.3.8.
See clause 9.3.2.5 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.4 SEALDD server discovery and selection
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.4.1 General
|
The following clauses specify procedures, information flow and APIs for SEALDD server discovery and selection for VAL server and SEALDD client.
There are two scenarios of how SEALDD service is used:
- Scenario (a): SEALDD service is used for both signalling and data traffic transfer.
- Scenario (b): SEALDD service is used only for data traffic transfer.
NOTE: For the same VAL application, VAL servers for Scenario (a) and Scenario (b) and VAL servers without SEALDD service may coexist in the same EDN. The three types of servers may use different EAS IDs or other information (e.g. EAS service, additional associated SEALDD server information) to differentiate each other for EAS discovery.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.4.2 SEALDD server discovery and selection for VAL server
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.4.2.1 General
|
CAPIF architecture and functionalities are reused to enable VAL server discover and select SEALDD server.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.4.2.2 Procedure
|
The SEALDD server and VAL server may support CAPIF as shown in Figure 9.4.2.2-1. When CAPIF is supported:
- The SEALDD server shall support the CAPIF API provider domain functions (i.e. CAPIF-2/2e (SEALDD-S interface), CAPIF-3/3e, CAPIF-4/4e and CAPIF-5/5e as specified in 3GPP TS 23.222 [3]);
- The VAL server shall act as API invoker and support the API invoker functions (i.e. CAPIF-1/1e and CAPIF-2/2e (SEALDD-S interface) as specified in 3GPP TS 23.222 [3]); and
- The SEALDD server shall act as API invoker and support the API invoker functions (i.e. CAPIF-1/1e and CAPIF-2/2e (SEALDD-E interface) as specified in 3GPP TS 23.222 [3]).
Figure 9.4.2.2-1: SEALDD adaptation in the CAPIF architecture
The VAL server discovers a proper SEALDD server from CAPIF core function with different discovery filters, e.g. expected AEF location. If a VAL server is changed during UE mobility, a new SEALDD server may be discovered and selected.This is also applicable for the VAL server acting as EAS to discover and select an SEALDD server in EDN scenario to use SEALDD-S services, if any.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.4.3 SEALDD server discovery and selection for SEALDD client
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.4.3.1 General
|
The VAL client uses existing mechanisms (e.g. DNS query mechanism, application layer signalling mechanism) to find an appropriate SEALDD server in non-EDN scenario and EDN scenario. The VAL client provides the SEALDD server information to the SEALDD client when the SEALDD service is required.
NOTE: DNS query mechanism and application layer signalling mechanism are outside the scope of SA6.
The EAS registration procedure of 3GPP TS 23.558 [10] is enhanced to enable VAL/SEALDD client to discover and select proper SEALDD server in EDN scenario.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.4.3.2 EDN scenario
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.4.3.2.1 VAL server registered to EES with associated SEALDD server address as VAL server endpoint
|
Figure 9.4.3.2.1-1: VAL server registered to EES with associated SEALDD server address as VAL server endpoint
1. The VAL server discovers and selects the SEALDD server (e.g. by CAPIF functions).
2. The VAL server decides to use SEALDD service to enhance data transmission and send a SEALDD data transmission subscription request (e.g. SEALDD enabled regular transmission request in clause 9.2.2) to the SEALDD server.
3. Upon receiving the request, the SEALDD server performs an authorization check and responds with a SEALDD data transmission subscription response (e.g. SEALDD enabled regular transmission response in clause 9.2.2).
4. The VAL server (as an EAS) registers to the EES as described in clause 8.4.3.2.2 of 3GPP TS 23.558 [10] 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 3GPP TS 23.558 [10]. 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 uses the EAS discovery procedure defined in clause 8.5 of 3GPP TS 23.558 [10] to find the VAL server's address which is SEALDD server's address. The VAL client initiates SEALDD service via SEALDD client with the SEALDD server's address. This procedure is applicable to for scenario (a).
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.4.3.2.2 EAS registered to EES with associated SEALDD server information
|
Figure 9.4.3.2.2-1: EAS register to EES with associated SEALDD server information
1. The SEALDD server (as an EAS) registered to EES with SEALDD profile (i.e. EAS profile) as an API provider.
2. The EAS (VAL) server discovers and selects the SEALDD server (e.g. by CAPIF functions).
3. The EAS (VAL server) decides to use SEALDD service to enhance data transmission and send a SEALDD data transmission subscription request (e.g. SEALDD enabled regular transmission request in clause 9.2.2) to the SEALDD server.
4. Upon receiving the request, the SEALDD server performs an authorization check and responds with a SEALDD data transmission subscription response (e.g. SEALDD enabled regular transmission response in clause 9.2.2).
5. The VAL server (as an EAS) registers to the EES as described in clause 8.4.3.2.2 of 3GPP TS 23.558 [10] 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 3GPP TS 23.558 [10]. 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 uses the EAS discovery procedure defined in clause 8.5 of 3GPP TS 23.558 [10] to find the VAL server's address and associated SEALDD server's address. The VAL client initiates SEALDD service via SEALDD client with the SEALDD server's address. For scenario (b), the VAL client also establishes 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.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.4.3.2.3 VAL server and SEALDD server registered to EES
|
Figure 9.4.3.2.3-1: VAL server and SEALDD server registered to EES
1. The VAL server (acting as an EAS) registers to the EES, if the VAL server has not indicated the associated SEALDD server as described in clause 9.4.3.2.1 or clause 9.4.3.2.2, the VAL server includes an indication of whether using SEALDD service is needed.
2. Optionally, the SEALDD server (acting as an EAS) registers to the EES.
3. The EEC performs service provisioning procedure as described in clause 8.3.3.2.2 of 3GPP TS 23.558 [10]. 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 3GPP TS 23.436 [13].
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).
NOTE: In step 4, the EES identifies the VAL server that needs to use SEALDD server, based on the SEALDD service needed indication in step 1.
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 initiates SEALDD service via SEALDD client with the SEALDD server's address. The data transmission between the VAL client and the VAL server is enabled via the SEALDD connection, as specified in clause 9.2.2.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.4.4 Information flows
|
The information flow about the SEALDD server discovery for VAL server/SEALDD server reuses the defined information flow in CAPIF (e.g. service API publish in clause 8.3.2, Service API discover in clause 8.7.2), as specified in 3GPP TS 23.222 [3].
For SEALDD server discovery for VAL client in EDN scenario, the information flows for EAS registration and EAS discovery in caluse 8.4.3.3 and clause 8.5.3 of 3GPP TS 23.558 [10].
The information flow about regular SEALDD data transmission subscription refers to the SEALDD enabled regular transmission request/response in clauses 9.2.3.1 and 9.2.3.2.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.4.5 APIs
|
The APIs about SEALDD server discovery for VAL server/SEALDD server reuses the defined APIs in CAPIF (e.g. CAPIF_Publish_Service_API in clause 10.3, CAPIF_Discover_Service _API in clause 10.2), as specified in 3GPP TS 23.222 [3].
The APIs about SEALDD server discovery for VAL client in EDN scenario, reuses the defined APIs in EDGEAPP (e.g. Eees_EASRegistration API in clause 8.4.3.4, Eees_EASDiscovery API in clause 8.5.4), as specified in 3GPP TS 23.558 [10].
The APIs about regular SEALDD data transmission subscription refers to the Sdd_RegularTransmission API, as defined in clause 9.2.4.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5 SEALDD enabled data storage
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.1 General
|
The following clauses specify procedures, information flows and APIs for SEALDD enabled data storage, the stored data may be queried by the creator or the other network functions for context or content transfer.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.2 Procedure
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.2.1 Data storage creation
|
Pre-conditions:
1. The VAL server has discovered and selected the SEALDD server by CAPIF functions.
2. The SEALDD client has discovered and selected the SEALDD server as specified in clause 9.4.3.
Figure 9.5.2.1-1: Storage service creation
1. 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).
NOTE 1: If the VAL client determines to use SEALDD storage service, the request is first sent to the SEALDD client hosted on the same UE, and then the SEALDD client send the Sdd_DataStorage_Creation request to the SEALDD server.
NOTE 2: The detailed request between VAL client and SEALDD client is out of scope of this release of this specification.
NOTE 3: The identifier of application data can be included in step 1 for storing the same application data in multiple SEALDD servers. The consumer (e.g. SEALDD client) can retrieve the same application data from different SEALDD servers by using the identifier of application data, as specified in clause 9.5.2.3.
2. 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.
3. 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.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.2.2 Data storage reservation
|
Pre-conditions:
1. The VAL server has discovered and selected the SEALDD server by CAPIF functions.
2. The SEALDD client has discovered and selected the SEALDD server as specified in clause 9.4.3.
Figure 9.5.2.2-1: Storage service reservation
1. 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.
2. 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.
3. 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.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.2.3 Data storage fetch
|
Pre-conditions:
1. VAL client/server has stored data in SEALDD server.
2. 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).
Figure 9.5.2.3-1: Access to stored data in SEALDD server
1. 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.
NOTE: The consumer requesting for the stored data can be the data storage creator or other network functions.
2. Upon receiving the request, the SEALDD server performs an authorization check to verify if the requested data (according to the data access control policy) is 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.
3. If the verification was successful, the SEALDD server responds with the requested data.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.2.4 Data storage management
|
Pre-conditions:
1. The SEALDD service is configured to track and maintain data storage access information (i.e. status information).
2. 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).
Figure 9.5.2.4-1: Storage management procedure
1. 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.
2. 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.
NOTE: Based on the data management or storage status information available in SEALDD server as per the procedure in clause 9.5.2.1, the SEALDD server may send a notification to the requester (e.g. SEALDD client, VAL server) with the collected management or storage status information.
3. 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.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.2.5 Stored data transfer between VAL servers via SEALDD server
|
Pre-conditions:
1. The source VAL server already obtains the serving target SEALDD server of the target VAL server.
2. 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.
Figure 9.5.2.5-1: Stored data transfer procedure between VAL servers
1. 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.
2. The SEALDD sever responds to the requested VAL server with the subscription result, if successful, the response includes the subscription ID, expiration time.
3. The source VAL server determines to use the stored data transfer service provided by the serving SEALDD server. The source VAL server invokes a SEALDD data storage delivery request, the request includes the identifier of the stored data needed to be delivered, or the stored data (i.e., the source VAL server does not use data storage creation to store data to the source SEALDD server before), the target VAL server information and the target SEALDD server information.
4. The source SEALDD server sends a SEALDD delivery connection establish request towards the target SEALDD server with the source SEALDD server information, the target VAL server information, and the supporting transport layer protocols for data delivery.
5. The target SEALDD server responds to the source SEALDD server with the traffic descriptor of target SEALDD server (e.g. address/port, transport layer protocol). The target SEALDD server may allocate the storage for the target VAL server.
NOTE: The transport layer protocol between SEALDD server connection can be different depending on the specific application scenarios, compared with the connection between SEALDD client and SEALDD server in clause 9.2.
6. Upon receiving the traffic descriptor of target SEALDD server, the source SEALDD server sends the requested data corresponding to the identifier of the stored data to the target SEALDD server.
7. The source SEALDD server responds to the source VAL server with the result of data delivery.
8. The target SEALDD server sends the received data to the target VAL server via the notification message. Optionally, the target SEALDD server may only send the identifier of the received data to the target VAL server in the notification message, the target VAL server obtains the stored data originated from the source VAL server, by invoking the Sdd_DataStorage_Fetch API to the target SEALDD server, as specified in clause 9.5.2.2.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.3 Information flows
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.3.1 SEALDD data storage creation request
|
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.
Table 9.5.3.1-1: SEALDD data storage creation request
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.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.3.2 SEALDD data storage creation response
|
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.
Table 9.5.3.2-1: SEALDD data storage creation response
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.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.3.3 SEALDD data storage status notification
|
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.
Table 9.5.3.3-1: SEALDD data storage status notification
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.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.3.4 SEALDD data storage fetch request
|
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.
Table 9.5.3.4-1: SEALDD data storage fetch request
Information element
Status
Description
Identifier of the stored data
M
Identify the stored data queried by the requesting consumer
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.3.5 SEALDD data storage fetch response
|
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.
Table 9.5.3.5-1: SEALDD data storage fetch response
Information element
Status
Description
Result
M
Success or failure.
The fetched application data
O
The fetched application data returned to the requesting consumer
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.3.6 SEALDD data storage management request
|
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.
Table 9.5.3.6-1: SEALDD data storage management request
Information element
Status
Description
Storage management operation
M
The operation (e.g. update, refresh, or delete) to manage the stored data
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.3.7 SEALDD data storage management response
|
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.
Table 9.5.3.7-1: SEALDD data storage management response
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
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.3.8 SEALDD data storage delivery subscription request
|
Table 9.5.3.8-1 describes the information flow from the VAL server to the SEALDD server for data storage delivery subscription.
Table 9.5.3.8-1: SEALDD data storage delivery subscription request
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
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.3.9 SEALDD data storage delivery subscription response
|
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.
Table 9.5.3.9-1: SEALDD data storage delivery subscription response
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.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.3.10 SEALDD data storage delivery notification
|
Table 9.5.3.10-1 describes the information flow from the SEALDD server to the VAL server for notifying the received stored data.
Table 9.5.3.9-1: SEALDD data storage delivery notification
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.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.3.11 SEALDD data storage delivery request
|
Table 9.5.3.11-1 describes the information flow from the VAL server to the SEALDD server for requesting the data storage delivery.
Table 9.5.3.11-1: SEALDD data storage delivery request
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.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.3.12 SEALDD data storage delivery response
|
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.
Table 9.5.3.12-1: SEALDD data storage delivery response
Information element
Status
Description
Result
M
Success or failure.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.3.13 SEALDD delivery connection establish request
|
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.
Table 9.5.3.13-1: SEALDD delivery connection establish request
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
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.3.14 SEALDD delivery connection establish response
|
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.
Table 9.5.3.14-1: SEALDD delivery connection establish response
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
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.4 APIs
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.4.1 General
|
Table 9.5.4.1-1 illustrates the APIs exposed by SEALDD server for data storage.
Table 9.5.4.1-1: List of SEALDD server APIs for data storage
API Name
API Operations
Operation Semantics
Consumer(s)
Sdd_ DataStorage_Creation
Request
Request/Response
SEALDD client, VAL server
Sdd_ DataStorage_Fetch
Request
Request/Response
SEALDD client, VAL server, other SEALDD server
Sdd_ DataStorage_Management
Request
Request/Response
SEALDD client, VAL server
Sdd_DataStorage_Delivery_Subscription
Request
Request/Response
VAL server
Sdd_DataStorage_Delivery_notification
Notify
Subscribe/notify
VAL server
Sdd_DataStorage_Delivery
Request
Request/Response
VAL server
Sdd_DeliveryConnection_Establish
Request
Request/Response
SEALDD server
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.4.2 Sdd_DataStorage_Creation Request operation
|
API operation name: Sdd_DataStorage_Creation Request
Description: The consumer requests for one time for data storage creation or data storage reservation.
Inputs: See clause 9.5.3.1.
Outputs: See clause 9.5.3.2
See clause 9.5.2.1 and clause 9.5.2.2 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.4.3 Sdd_DataStorage_Fetch Request operation
|
API operation name: Sdd_DataStorage_Fetch Request
Description: The consumer requests for one time for data storage Fetch.
Inputs: See clause 9.5.3.4.
Outputs: See clause 9.5.3.5.
See clause 9.5.2.3 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.4.4 Sdd_DataStorage_Management Request operation
|
API operation name: Sdd_DataStorage_Management Request
Description: The consumer requests for one time for data storage management.
Inputs: See clause 9.5.3.6.
Outputs: See clause 9.5.3.7.
See clause 9.5.2.4 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.4.5 Sdd_DataStorage_Delivery_Subscription Request operation
|
API operation name: Sdd_DataStorage_Delivery_Subscription Request
Description: The consumer requests for one time for data storage delivery subscription.
Inputs: See clause 9.5.3.8.
Outputs: See clause 9.5.3.9.
See clause 9.5.2.5 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.4.6 Sdd_DataStorage_Delivery_Notification operation
|
API operation name: Sdd_DataStorage_Delivery_Notification
Description: The consumer is notified with the received stored data from SEALDD server.
Inputs: See clause 9.5.3.10.
Outputs: None.
See clause 9.5.2.5 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.4.7 Sdd_DataStorage_Delivery Request operation
|
API operation name: Sdd_DataStorage_Delivery Request
Description: The consumer requests for one time for data storage delivery.
Inputs: See clause 9.5.3.11.
Outputs: See clause 9.5.3.12.
See clause 9.5.2.5 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.5.4.8 Sdd_DeliveryConnection_Establish Request operation
|
API operation name: Sdd_DeliveryConnection_Establish Request
Description: The consumer requests for one time for delivery connection establishment between SEALDD servers.
Inputs: See clause 9.5.3.13.
Outputs: See clause 9.5.3.14.
See clause 9.5.2.5 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6 SEALDD server relocation
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.1 General
|
The SEALDD server may be relocated due to UE mobility or load re-balance.
If SEALDD server is adapted to EDGEAPP as an EAS, the EAS relocation procedure is used to support SEALDD server relocation for both UE mobility and SEALDD server load re-balance. If SEALDD is not adapted to EDGEAPP, for UE mobility, the SEALDD client discovers (e.g. using DNS) a new SEALDD server in the target area and establish a new SEALDD communication channel including the old SEALDD communication channel information. For load re-balance, the SEALDD server discovers (e.g. using DNS) an equivalent SEALDD server and communicate with the new SEALDD server.
Based on existing service continuity mechanism supported by 3GPP core network (e.g. BP/ULCL), during SEALDD server relocation with UPF change, the new UPF takes care of the existing unfinished application traffic flow towards the old VAL server and inter-UPF tunnel is used to forward the traffic. For new application traffic flow which may have UE's new IP address as source IP address, the new SEALDD server sends it directly to the new VAL server.
For SEALDD server relocation, the inter-SEALDD server communication via SEALDD-E reference point is needed, which transfers the SEALDD context from the old SEALDD server to the new SEALDD server.
The following procedures detail the EDGEAPP ACT part between old SEALDD server (i.e. S-EAS) and new SEALDD server (i.e. T-EAS) as described in 3GPP TS 23.558 [10], clause 8.8.2.2 to clause 8.8.2.6. Also, a high-level flow is provided to show the scenario used in EDN.
NOTE 1: The way to provide SEALDD server endpoint can be via VAL server or via EES, and discovery of the new SEALDD server can utilize procedure described in clause 9.4. The ACT procedure in the VAL server is also executed according to EDGEAPP ACR scenario but its detail is out of scope of SA6.
NOTE 2: The SEALDD context scope (e.g. service level and/or UE level) has the same granularity with SEALDD transmission request information in clause 9.2.3.1.
NOTE 3: How context synchronization is performed between SEALDD server and VAL server in context transfer is out of scope in this document.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.2 Procedures
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.2.1 SEALDD context transfer
|
Figure 9.6.2.1-1 describes SEALDD context transfer procedure in pull (step 1a and 2a) or push (step 1b and 2b) operation.
Pre-conditions:
1. For pull operation, the old SEALDD server endpoint is available in the new SEALDD server
2. For push operation, the new SEALDD server endpoint is available in the old SEALDD server.
Figure 9.6.2.1-1: SEALDD context transfer
The transferred SEALDD context includes the service subscription information created upon VAL server's interaction for requesting SEALDD transmission service (e.g. step 1 and 2 in Figure 9.2.2.1-1), and also the SEALDD client and SEALDD server communication tunnel management information (e.g. UE IP address) which is created upon SEALDD client's interaction for requesting data transmission (e.g. step 5 and 6 in Figure 9.2.2.1‑1). If new SEALDD server supports transportation layer service continuity, additional transport layer context (e.g. TCP/TLS/QUIC) is transferred from old SEALDD server to new SEALDD server. If the new SEALDD Server is not provisioned with the VAL server configured SEALDD policy, then it pulls from the Old SEALDD server via the pull operation. The push operation does not support the transfer of the VAL server configured SEALDD policy between Old and New SEALDD server.
The new SEALDD server, after receiving the SEALDD context from the old SEALDD server, allocates IP address and port for SEALDD-UU user plane communication. The new SEALDD server also sends back to the old SEALDD server with the allocated endpoint information If operation is push. Then the old SEALDD server requests 5GC to perform IP replacement procedure, as defined in clause 6.3.3 of 3GPP 23.548 [8]. The request includes the traffic descriptor of old SEALDD server (i.e., SEALDD-UU address/port), the traffic descriptor of new SEALDD server (i.e., SEALDD-UU address/port) and/or the target DNAI.
Optionally, after receiving the SEALDD context with the SEALDD-UU endpoint from the old SEALDD server, the new SEALDD server requests 5GC to perform IP replacement procedure.
NOTE: The TCP/TLS/QUIC context transfer is required to support the SEALDD server relocation with IP replacement procedure, as described in clause 9.6.2.2.
To improve the seamless SEALDD relocation, the old SEALDD server may stop the downlink data transmission before pushing the SEALDD context to the new SEALDD server, the context data may include content breakpoint information, as defined in clause 9.6.3.1. After the SEALDD client connects to the new SEALDD server, the new SEALDD server transmits the downlink traffic to the SEALDD client based on content breakpoint information.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.2.2 SEALDD relocation in EDN
|
Pre-conditions:
1. VAL Server 1 and 2 are adapted to the EDGEAPP as EAS.
2. VAL Server 1 and 2 register its associated SEALDD server in EES as described in clause 9.4.3.2.
Figure 9.6.2.2-1: SEALDD support of UE's service continuity
1. An application client on a UE, acting as a VAL client, establishes a SEALDD-UU flow over SEALDD-UU to send application data to VAL Server 1. SEALDD client and SEALD server 1 maintain SEALDD-UU flow information (e.g., SEALDD-UU flow ID, VAL IDs/addresses, VAL requirements).
2. Application data between the VAL Client and VAL Server 1 is sent via the SEALDD-UU flow.
3. The UE moves and generates a mobility event in the 5GC.
4. The UE's mobility event triggers the execution of an Application Context Relocation (ACR) procedure as described in 3GPP TS 23.558 [10]; or VAL server 1 triggers ACR due to load re-balancing reason. Any of the ACR scenarios detailed in 3GPP TS 23.558 [10] clauses 8.8.2.2-8.8.2.6 may occur. In this step, the first three phases of the ACR procedure are performed, up to ACT. In this step VAL Server 1 acts as EAS 1 and VAL Server 2 as EAS 2, therefore participating in corresponding signalling. VAL server 2 has been selected as SEALDD-enabled server meeting the ACR criteria to be the target EAS. The associated SEALDD server 2 has also been selected and may support transportation layer (e.g. UDP/TCP/QUIC) service continuity.
5a. Before triggering ACT, VAL Server 1 sends a SEALDD notification of ACR event to SEALDD Server 1.
5b. Before triggering ACT, VAL Server 2 sends a SEALDD notification of ACR event to SEALDD Server 2.
6a. SEALDD server 1 transfers the SEALDD context to the SEALDD server 2 which serves VAL Server 2 as described in clause 9.6.2.1, with push operation. The SEALDD server 1 obtains the SEALDD server 2 endpoint for SEALDD-UU user plane to the SEALDD client, as specified in clause 9.6.2.1.
6b. SEALDD server 2 obtains the SEALDD context from the SEALDD server 1 by using the pull operation, as described in clause 9.6.2.1.
7. SEALDD server 1 applies the functionality specified in 3GPP TS 23.502 [6] clause 5.2.6.7 for AF traffic influence, providing the N6 routing information for the SEALDD client and SEALDD server 2. The SEALDD server 1 may:
- If the SEALDD server 2 supports transportation layer service continuity, additionally includes SEALDD IP replacement information (i.e. SEALDD server 1 endpoint and SEALDD server 2 endpoint for SEALDD-UU user plane) in the AF traffic influence. Since the UE is not aware of SEALDD server change, the new SEALDD traffic (due to new VAL traffic sent by VAL client) is sent by UPF towards the new SEALDD server, this handling in UPF is agnostic to the SEALDD server 2. Or,
- send AF traffic influence with target DNAI of SEALDD server 2, and simultaneous connectivity indicator, to request 5GC to maintain the simultaneous connectivity over source PSA and target PSA with source SEALDD server and target SEALDD server, as described in clause 6.3.4 of 3GPP TS 23.548 [8].
8. If the SEALDD server 2 has no transportation layer service continuity support, a SEALDD Connection info update notification is sent to SEALDD client, e.g. to update the allocated IP address and port for SEALDD-UU user plane communication. Then the SEALDD client acknowledges the received SEALDD Connection info update notification. After SEALDD client is aware of the new SEALDD-UU IP address and port, it starts to send new SEALDD traffic (received from the VAL client) over the new connection. The new SEALDD server maps the received SEALDD traffic to the application traffic according to the SEALDD traffic descriptor and VAL service ID. The new SEALDD server sends the recovered application traffic to new VAL server. The downlink application traffic sent from the new VAL server to VAL client is processed similarly.
9. SEALDD Server 1 notifies VAL Server 1 of the completion of the SEALDD-UU flow transfer.
10. VAL Server 1 (acting as EAS1) and VAL Server 2 (acting as EAS 2) execute the Application Context Transfer (ACT) procedure step corresponding to the pending ACR scenario (3GPP TS 23.558 [10] clauses 8.8.2.2‑8.8.2.6), which is out the 3GPP scope.
11. The post-ACR clean-up phase is executed, as described in the corresponding ACR scenario (3GPP TS 23.558 [10] clauses 8.8.2.2-8.8.2.6).
12. The application data from the VAL Client is sent via the SEALDD-UU flow (with SEALDD server 2) to VAL Server 2.
NOTE: The SEALDD-UU client endpoint of the SEALDD-UU flow in this step is maintained the same as in step 1.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.3 Information flows
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.3.1 SEALDD context push request
|
Table 9.6.3.1-1 describes the information flow from the old SEALDD server to the new SEALDD server to push the SEALDD context.
Table 9.6.3.1-1: SEALDD context push request
Information element
Status
Description
Requestor ID
M
Identifies the requestor (i.e. old SEALDD server).
SEALDD-UU Context
M
Identifies the context related to SEALDD-UU connection, which is created upon SEALDD connection establishment.
SEALDD-S Context
M
Identifies the context related to SEALDD-S subscription.
Transport layer context
O
Identifies the context related to Transport layer (e.g. TCP/TLS/QUIC) for SEALDD-UU user plane communication.
Content breakpoint information
O
The downlink data breakpoint information for pre-provisioned data.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.3.2 SEALDD context push response
|
Table 9.6.3.2-1 describes the information flow from the new SEALDD server to the old SEALDD server for responding to the SEALDD context push request.
Table 9.6.3.2-1: SEALDD context push response
Information element
Status
Description
Result
M
(NOTE)
Success or failure.
New SEALDD server endpoint
O
The endpoint (IP address and port) on the new SEALDD for SEALDD-UU user plane communication.
Applicable for successful result.
NOTE: The result is failed if the new SEALDD server rejects the relocation for SEALDD client.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.3.3 SEALDD context pull request
|
Table 9.6.3.3-1 describes the information flow from the new SEALDD server to the old SEALDD server to pull the SEALDD context.
Table 9.6.3.3-1: SEALDD context pull request
Information element
Status
Description
Requestor ID
M
Identifies the requestor (i.e. new SEALDD server).
SEALDD policy indication
O
Indicates the need to transfer the VAL server configured SEALDD policy.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.3.4 SEALDD context pull response
|
Table 9.6.3.4-1 describes the information flow from the old SEALDD server to the new SEALDD server for responding to the SEALDD context pull request.
Table 9.6.3.4-1: SEALDD context pull response
Information element
Status
Description
Result
M
Success or failure.
SEALDD-UU Context
O
(NOTE)
Identifies the context related to SEALDD-UU connection, which is created upon SEALDD connection establishment.
SEALDD-S Context
O
(NOTE)
Identifies the context related to SEALDD-S subscription.
Transport layer context
O
(NOTE)
Identifies the context related to Transport layer (e.g. TCP/TLS/QUIC) for SEALDD-UU user plane communication.
SEALDD policy
O
(NOTE)
Indicates the VAL server configured SEALDD policy.
NOTE: These IEs are applicable when the result is success.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.3.5 SEALDD inform ACR event request
|
Table 9.6.3.5-1 describes the information flow from the VAL server to the SEALDD server to inform the ACR event, for ACR coordination purpose.
Table 9.6.3.5-1: SEALDD inform ACR event request
Information element
Status
Description
VAL server ID
M
Identity of the VAL server
VAL service ID
O
Identity of the VAL service
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.3.6 SEALDD inform ACR event response
|
Table 9.6.3.6-1 describes the information flow from the SEALDD server to the VAL server for responding to the SEALDD inform ACR event request.
Table 9.6.3.6-1: SEALDD inform ACR event response
Information element
Status
Description
Result
M
Success or failure.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.3.7 SEALDD inform ACR event notification
|
Table 9.6.3.7-1 describes the information flow from the SEALDD server to the VAL server for notifying ACR event related information.
Table 9.6.3.7-1: SEALDD inform ACR event notifiation
Information element
Status
Description
SEALDD flow transfer result
M
Success or failure.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.4 APIs
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.4.1 General
|
Table 9.6.4.1-1 illustrates the APIs exposed by SEALDD server for UE’s service continuity.
Table 9.6.4.1-1: List of SEALDD server APIs for UE’s service continuity
API Name
API Operations
Operation Semantics
Consumer(s)
Sdd_DDContext
Push Request
Request/Response
SEALDD server
Pull Request
Request/Response
SEALDD server
Sdd_InformACREvent
Request
Subscribe/Notify
VAL server
Notify
Subscribe/Notify
VAL server
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.4.2 Sdd_DDContext_Push Request operation
|
API operation name: Sdd_DDContext_Push Request
Description: The consumer requests to push SEALDD context.
Inputs: See clause 9.6.3.1.
Outputs: See clause 9.6.3.2
See clause 9.6.2.1 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.4.3 Sdd_DDContext_Pull Request operation
|
API operation name: Sdd_DDContext_Pull Request
Description: The consumer requests to pull SEALDD context.
Inputs: See clause 9.6.3.3.
Outputs: See clause 9.6.3.4
See clause 9.6.2.1 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.4.4 Sdd_InformACREvent_Request operation
|
API operation name: Sdd_InformACREvent_Request
Description: The consumer informs ACR event to SEALDD server, for ACR coordination purpose.
Inputs: See clause 9.6.3.5.
Outputs: See clause 9.6.3.6.
See clause 9.6.2.2 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.6.4.5 Sdd_ InformACREvent _Notify operation
|
API operation name: Sdd_ InformACREvent_Notify
Description: SEALDD server notifies information about previously informed ACR event.
Inputs: See clause 9.6.3.7.
Outputs: See clause 9.6.3.7.
See clause 9.6.2.2 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7 SEALDD enabled data transmission quality measurement
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.1 General
|
The following clauses specify procedures, information flows and APIs for SEALDD enabled data transmission quality measurement.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.2 Procedures
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.2.1 Data transmission quality measurement
|
Figure 9.7.2-1 illustrate the procedure for SEALDD enabled data transmission quality measurement. The SEALDD client and SEALDD server is enhanced to carry out the data transmission quality measurement.
Pre-conditions:
1. The SEALDD server and SEALDD client are synchronized to the time source provided by 5GS as specified in 3GPP TS 23.501 [5].
2. The VAL server discovers and selects the SEALDD server by CAPIF functions.
Figure 9.7.2.1-1: SEALDD enabled data transmission quality measurement procedure
1. An on-going regular data transmission connection is established according to clause 9.2.2.2.
2. The VAL server sends a SEALDD transmission quality measurement subscription request to the SEALDD server. The request includes the identifiers of the application traffic (e.g. VAL service ID, VAL server ID), requirement of transmission quality measurement (e.g. latency, jitter, bitrate, packet loss rate) and measurement target UE (e.g. a single UE, a group of UEs or all UEs), flow(s) traffic descriptor(s), and may also include reporting criteria, reporting frequency, spatial condition and temporal condition.
NOTE 1: The spatial and/or temporal condition can be used by SEALDD server to apply when and where the measurement is performed. For instance, the measurement is expected to be done for a group of VAL UEs with a scheduled route (from city A to city B via highway A2 and A3), from 9:00 a.m. to 11:00 a.m. on Tuesday and from 1:00 p.m. to 5:00 p.m. on Thursday.
3. Upon receiving the request, the SEALDD server performs an authorization check. If authorization is successful, the SEALDD server sends a response to the VAL server with the subscription ID, expiration time.
4. If the transmission quality measurement requirement list provided by VAL server in step 2, indicates that the latency is needed to be measured, the SEALDD server initiates the DL packet delay measurement. The SEALDD server encapsulates the DL monitoring packet (i.e. DL SEALDD packet with SEALDD DL monitoring header and VAL traffic as payload, or dummy DL SEALDD packet generated for data transmission quality monitoring) with local time T1 when the SEALDD server sends out the DL monitoring packets. The SEALDD server considers the spatial and/or temporal conditions when starting/resuming the transmission quality measurement. If the conditions are not satisfied, the SEALDD server stops/suspends the transmission quality measurement.
NOTE 2: For other metrics in transmission quality measurement requirement list (e.g. bitrate), the transmission quality result can be obtained by performance detection on the SEALDD server within a period of time.
5. The SEALDD client receives the DL monitoring packet, and records the local time T2. If the endpoint for the SEALDD traffic is located at the tethered device, the SEALDD client in 5G UE measures the QoS between the SEALDD client in 5G UE and the SEALDD client (i.e. for architecture that has the SEALDD client on the tethered device) or the VAL client (i.e. for architecture that without the SEALDD client on the tethered device) in tethered device, e.g., the SEALDD client may measure the tethered link delay using the ICMP ping protocol as defined in IETF RFC792 [RFC792]). The detailed procedures of Tethering link measurement and provisioning is defined in clause 9.12.2.3.
NOTE 3: The tethered link measurement between SEALDD client and VAL client is based on assumption that there is business agreement between the VAL provider and the SEALDD provider, which request the VAL client to respond to ICMP Ping packet.
NOTE 4: Only RTT can be measured for the link between SEALDD client and the tethered device.
6. Similarly, the SEALDD client encapsulates the UL monitoring packet (i.e. UL SEALDD packet with SEALDD UL monitoring header and VAL traffic as payload, or dummy UL SEALDD packet generated for data transmission quality monitoring) with local time T2 recorded in step 5 and local time T3 when the SEALDD client sends out the UL monitoring packet. If the endpoint for the VAL traffic is located at the tethered device, the measurement delay in the tethered link (step 5) is considered in T2 and T3 timestamps, e.g., T2 timestamp includes the half of the measurement delay and T3 timestamp excludes the half of the measurement delay.
NOTE 5: With ICMP ping over tethered link, it is assumed that the UL packet delay and the DL packet delay are the same between the tethering UE and the tethered device.
7. The SEALDD server records the local time T4 when the SEALDD server receives the UL monitoring packet and calculates the latency with T1, T2, T3, T4. The SEALDD server also calculates the bitrate, jitter and packet loss rate over a certain period over a specific SEALDD connection by recording the status of the SEALDD packets carrying VAL traffic or dummy SEALDD packets generated for transmission quality measurement reports. The SEAL DD server also evaluates the reporting criteria if present in the SEALDD transmission quality measurement subscription request in order to generate the transmission quality measurement report.
8. The SEALDD server reports the data transmission quality measurement results (e.g. latency, jitter, bitrate, packet loss rate) to the VAL server via the notification message.
When a VAL group ID or a list of VAL UE IDs or all VAL UEs indication is received in step 2, step 4 to step 7 is repeated for VAL UEs in the group/list or for all VAL UEs. The SEALDD server maps the VAL UE group ID to a list of VAL UE IDs if a VAL group ID is received. The SEALDD server identifies SEALDD connections corresponding to the desired VAL UE(s) or flow(s) traffic descriptor(s) to trigger measurement. And depending on the reporting requirement for multiple UEs, the SEALDD server calculates the needed report for the VAL server. When the VAL server decides to update or unsubscribe transmission quality measurement subscription after performing step 2 and step 3, the VAL server sends data transmission quality measurement subscription update request and data transmission quality measurement unsubscribe request to SEALDD server, as specified in Table 9.7.3.9-1 and Table 9.7.3.11-1, respectively.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.2.2 Data transmission quality query
|
Figure 9.7.2.2-1 illustrate the procedure for SEALDD enabled data transmission quality query. This procedure is used to obtain the historical transmission quality result already measured as described in clause 9.7.2.1.
Pre-conditions:
1. The SEALDD server performs the data transmission quality measurement procedure, as described in clause 9.7.2.1.
Figure 9.7.2.2-1: SEALDD enabled data transmission quality query procedure
1. The consumers (e.g. VAL server, SEALDD server, NSCE server, ADAE server) sends a SEALDD transmission quality query request to the SEALDD server to obtain the transmission quality measurement result. The request includes the identifiers of the application traffic (e.g. VAL service ID, VAL server ID), VAL UE ID or VAL UE group ID, flow(s) traffic descriptor(s), or crossflow measurement information.
2. The SEALDD server responds with the transmission quality measurement result (e.g. packet delay, bitrate, packet loss rate).
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.2.3 Data transmission quality measurement reported by SEALDD client
|
Figure 9.7.2.3-1 illustrate the procedure for SEALDD enabled data transmission quality measurement for VAL traffic. The SEALDD client receives transmission quality measurement requirement, decides to start VAL data transmission monitoring and generates measurement reports.
Figure 9.7.2.3-1: VAL data transmission quality measurement reported by SEALDD client
1. An on-going regular data transmission connection is established according to clause 9.2.2.2.
The transmission quality measurement may be triggered by VAL server or VAL client, which is described in step 2 to step 5 and step 6, correspondingly.
The request may include the crossflow measurement information (e.g. {[traffic descriptor 1, UL]; [traffic descriptor 2/DL]}) associated in the same multi-modal service for crossflow RTT measurement.
The detailed procedures of Tethering link measurement and provisioning is defined in clause 9.12.2.3.
2. The VAL server sends a SEALDD transmission quality measurement subscription request to the SEALDD server. The request includes the identifiers of the application traffic (e.g. VAL service ID, VAL server ID), requirement of transmission quality measurement (e.g. latency, jitter, bitrate) and measurement target UE (e.g. a single UE, a group of UEs or all UEs), and may also include reporting criteria, reporting frequency, spatial condition and temporal condition.
NOTE 1: The spatial and/or temporal condition can be used by SEALDD client to apply when and where the measurement is performed. For instance, the measurement is expected to be done for a group of VAL UEs with a scheduled route (from city A to city B via highway A2 and A3), from 9:00 a.m. to 11:00 a.m. on Tuesday and from 1:00 p.m. to 5:00 p.m. on Thursday.
3. Upon receiving the request, the SEALDD server performs an authorization check. If authorization is successful, the SEALDD server responds to the VAL server.
4-5. The SEALDD server sends a SEALDD transmission quality measurement subscription request to the SEALDD client and the SEALDD client responds to the SEALDD server.
If crossflow RTT measurement requirement is received from the VAL server, the SEALDD server identifies the SEALDD connections for the involved VAL UEs and sends to the SEALDD client(s) with crossflow RTT measurement requirement including corresponding UL/DL flow information.
The SEALDD server sends the Non-3GPP access measurement information in the SEALDD transmission quality measurement subscription request to the SEALDD client.
6. The VAL client triggers the SEALDD transmission quality measurement procedure to the SEALDD client, in order to collect the measurement report information.
7. After SEALDD client determines to start measurement process, upon UL packet arrival, the SEALDD client initiates the UL packet delay measurement. The SEALDD client encapsulates the UL monitoring packet (i.e. UL SEALDD packet with SEALDD UL monitoring header and VAL traffic as payload for VAL data transmission quality monitoring) with local time T1 when the SEALDD client sends out the UL monitoring packet. The SEALDD client considers the spatial and/or temporal conditions when starting/resuming the transmission quality measurement. If the conditions are not satisfied, the SEALDD client stops/suspends the transmission quality measurement.
For crossflow RTT measurement, the SEALDD client received UL flow information starts recording local time T1 when sending out the 1st UL packet matching the UL flow information to the SEALDD server. The T1 is sent in the encapsulated UL monitoring packet to the SEALDD server.
8. The SEALDD server receives the UL monitoring packet, and records the local time T2.
9. Similarly, the SEALDD server encapsulates the DL monitoring packet (i.e. DL SEALDD packet with SEALDD DL monitoring header and VAL traffic as payload, or dummy DL SEALDD packet generated for data transmission quality monitoring in case there is no DL VAL traffic for DL packet delay monitoring) with local time T2 recorded in step 8 and local time T3 when the SEALDD server sends out the DL monitoring packet.
NOTE 2: When the SEALDD server sends the dummy DL packet as monitoring response to the SEALDD client depends on SEALDD server implementation.
For crossflow RTT measurement, when the 1st DL packet matching the received DL flow information is to be sent, the SEALDD server encapsulates the DL monitoring packet with previously received T1 and sends the DL monitoring packet to the SEALDD client.
10. The SEALDD client records the local time T4 when the SEALDD client receives the DL monitoring packet and calculates the latency with T1, T2, T3, T4. The SEALDD client also calculates the bitrate and jitter over a certain period over a specific SEALDD connection by recording the status of the SEALDD monitoring packets. The SEALDD client also evaluates the reporting criteria and the flow alignment reporting criteria if present in the SEALDD transmission quality measurement subscription request in order to generate the transmission quality measurement report.
For crossflow RTT measurement, if T1 is received in the DL packet, the SEALDD client records local time T2 and calculates RTT based on T1 and T2.
Depending on which entity triggers the data transmission quality measurement, step 11 and step 12 corresponds to step 2 to step 5, step 13 corresponds to step 6.
For the Non-3GPP access measurement, if the Non-3GPP access measurement information includes list of WLAN SSIDs, then the SEALDD client performs the signal strength measurement for the requested WLAN SSID. If the request contains location-based measurement then the SEALDD client measures the signal strength of nearby WLAN SSIDs based on its location.
If the delay difference, i.e., the bound of the difference of the end-to-end time delay among all associated flows, is requested, the SEALDD client calculates the delay difference between VAL server and SEALDD client, based on the arrival time and the timestamp (e.g., timestamp as recorded in the RTP header) among all associated flows identified by the Multi-modal SEALDD flow ID. The arrival time of first detected flow and last detected flow, Ta and Tb, are recorded, and the delay difference is the difference between Ta and Tb. Then SEALDD client sends the calculated delay difference to the SEALDD server.
NOTE 3: The cross flow RTT measurement calculated by the SEALDD client does not need to differentiate whether the RTT measures are taken over the PDUs of a PDU set.
11-12. The SEALDD client reports the data transmission quality measurement results (e.g. latency, jitter, bitrate) to the VAL server via the SEALDD server. The report also includes the list of WLAN SSIDs and their signal strength measurements (like RSSI). The Measurement range indicate the scope of the measurement, e.g., end to end measurement, tethering link measurement etc.
13. The SEALDD client reports the data transmission quality measurement results to the VAL client.
NOTE 4: The crossflow RTT measurement calculated by the SEALDD client in step 10 can be used as an estimation of the lower bound for the Motion-to-Photon latency in the XR scenarios.
When a VAL group ID or a list of VAL UE IDs or all VAL UEs indication is received in step 2, step 4 to step 11 is repeated for VAL UEs in the group/list or for all VAL UEs. The SEALDD server maps the VAL UE group ID to a list of VAL UE IDs if a VAL group ID is received. The SEALDD server identifies SEALDD connections corresponding to the desired VAL UE(s) to trigger measurement. And depending on the reporting requirement for multiple UEs, the SEALDD server collects and aggregates the needed report for the VAL server.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.3 Information flows
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.3.1 SEALDD enabled data transmission quality measurement subscription request
|
Table 9.7.3.1-1 describes the information flow from the VAL server to the SEALDD server for subscribing to the data transmission measurement service.
Table 9.7.3.1-1: SEALDD transmission quality measurement subscription request
Information element
Status
Description
Application traffic identifiers
M
Identify of the application traffic (e.g. VAL server ID, VAL service ID)
Identity
O
(See NOTE)
Identifier of the VAL UE or VAL user for which measurements need to be provided.
VAL UE/user group ID
O
(See NOTE)
Identifier of a specific VAL UE/user group, as defined in clause 7.5 of 3GPP TS 23.434 [4].
Identity list
O
(See NOTE)
Identifies a list of VAL UEs, e.g. the list of UE ID, or a list of VAL users.
All VAL UEs or VAL users Indication
O
(See NOTE)
Indicates all VAL UEs or VAL users of the application identified by application traffic identifiers.
Flow(s) traffic descriptor(s)
O
(See NOTE)
Indicates the flow(s) traffic descriptor(s) (Address/port or URL) for the measurement.
Crossflow measurement information
O
(see NOTE)
Represents the crossflow measurement information, e.g., list of pairs traffic descriptor with traffic direction (UL or DL).
Example of the crossflow measurement information: {[traffic descriptor 1, UL]; [traffic descriptor 2, DL]}.
Measurement conditions
O
Indicates the temporal and/or spatial conditions.
Transmission quality measurement requirements list
M
The measurement requirement information
> Measurement ID
M
Measurement identifiers, e.g. UL/DL/E2E latency, UL/DL bitrate, UL/DL/E2E packet loss rate, UL/DL/E2E jitter, and crossflow identifier (e.g., crossflow latency, crossflow bitrate, crossflow packet loss rate, crossflow jitter).
> Reporting frequency
O
The reporting frequency of measurement results (e.g. periodic reporting). If not present, it implies periodic reporting.
> Reporting periodicity
O
If the reporting frequency is periodic, the reporting periodicity shall be provided. For multiple UEs/users, it is recommended to give sufficient time to allow report aggregation.
> Reporting granularity
O
The reporting granularity indicates whether the measurement report is for individual VAL UE/user or for VAL UE/user group or for all VAL UEs/users, if VAL UE/user group or all VAL UEs/users is the measurement target.
> Measurement period window
O
Indicates the measurement period window for transmission quality measurements
> Measurement expiration time
O
Indicates the measurement expiration time
> Reporting criteria
O
Indicates the criteria for reporting measurement results, e.g. if the latency or bitrate reaches below or above a certain value. It also includes a unique identifier for each criteria of more than one criteria is specified.
NOTE: One of them shall be present as the measurement target UE or traffic descriptor.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.3.2 SEALDD enabled data transmission quality measurement subscription response
|
Table 9.7.3.2-1 describes the information flow from the SEALDD server to the VAL server for responding to the transmission quality measurement subscription request.
Table 9.7.3.2-1: SEALDD transmission quality measurement subscription response
Information element
Status
Description
Result
M
Success or failure.
Subscription ID
O
Subscription identifier corresponding to the subscription. Applicable for successful result.
Expiration time
O
Indicates the expiration time of the subscription. Applicable for successful result.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.3.3 SEALDD enabled data transmission quality measurement notification
|
Table 9.7.3.3-1 describes the information flow from the SEALDD server to the VAL server for notifying the transmission quality measurement reports.
Table 9.7.3.3-1: SEALDD transmission quality measurement notification
Information element
Status
Description
Subscription ID
M
Subscription identifier corresponding to the subscription.
Transmission quality measurement reports list
M
The generated transmission quality results in SEALDD server or SEALDD client, as specified in Table 9.7.3.3-2.
Table 9.7.3.3-2 describes the information elements for the transmission quality measurement reports list, provided by the SEALDD server after performing transmission quality measurement.
Table 9.7.3.3-2: SEALDD transmission quality measurement reports list
Information element
Status
Description
> Measurement ID
M
Measurement identifiers, (e.g. UL/DL/E2E latency, UL/DL bitrate, UL/DL/E2E packet loss rate, UL/DL/E2E jitter) and crossflow identifiers (e.g., crossflow latency, crossflow bitrate, crossflow packet loss rate, crossflow jitter).
> VAL UE/user ID(s) or flow(s)traffic descriptor(s)
O
(see NOTE)
It indicates the VAL UE(s) or VAL user(s) under SEALDD measurement. For a single VAL UE/user or flow(s)traffic descriptor(s), it can be omitted and the associated measurement values are for the single VAL UE/user. For multiple VAL UEs/users or flow(s)traffic descriptor(s) with reporting granularity set to individual UE/user or flow traffic descriptor, the associated measurement values are for individual VAL UE/user or flow traffic descriptor as indicated in this IE. For multiple VAL UEs/users with reporting granularity set to VAL UE/user group/list or all VAL UEs/users, the associated measurement values are aggregation for all VAL UEs/users or the VAL UE/user group/list and this IE includes the measured VAL UEs/users.
> Crossflow measurement information
O
(see NOTE)
Represents the crossflow measurement information, e.g., list of pairs traffic descriptor with traffic direction (UL or DL).
Example of the crossflow measurement information: {[traffic descriptor 1, UL]; [traffic descriptor 2, DL]}.
> Average measurement value
O
The average measurement value of measurement results
> Minimum measurement value
O
The minimum measurement value of measurement results
> maximum measurement value
O
The maximum measurement value of measurement results
> Standard deviation measurement value
O
Standard deviation measurement value of measurement results
> kPercentile measurement value
O
Indicates the kpercentile measurement value of measurement results
> Measurement period
O
Indicates the measurement period
> Timestamp
O
Indicates the timestamp of measurement results
NOTE: These IEs are mutually exclusive.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.3.4 SEALDD enabled data transmission quality query request
|
Table 9.7.3.4-1 describes the information flow from the other consumers (e.g. SEALDD server, NSCE server, ADAE server) to the SEALDD server for querying the data transmission quality measurement result.
Table 9.7.3.4-1: SEALDD transmission quality query request
Information element
Status
Description
Application traffic identifiers
M
Identify of the application traffic (e.g. VAL server ID, VAL service ID)
VAL UE/user ID(s) or flow(s) traffic descriptor(s)
O
(see NOTE)
Identifier of VAL UE(s), VAL user(s), or flow(s) traffic descriptor(s) need to be queried, e.g. single VAL UE/user, multiple VAL UEs/users, flow(s) traffic descriptor(s), or VAL UE/user group
Crossflow measurement information
O
(see NOTE)
Represents the crossflow measurement information, e.g., list of pairs traffic descriptor and traffic direction (UL or DL).
Example of the crossflow measurement information: {[traffic descriptor 1, UL]; [traffic descriptor 2, DL]}.
NOTE: These IEs are mutually exclusive.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.3.5 SEALDD enabled data transmission quality query response
|
Table 9.7.3.5-1 describes the information flow from the SEALDD server to the other consumers (e.g. SEALDD server, NSCE server, etc) for returning the data transmission quality reports.
Table 9.7.3.5-1: SEALDD transmission quality query response
Information element
Status
Description
Result
M
Success or failure.
Transmission quality measurement reports list
M
The generated transmission quality results in SEALDD server, as specified in Table 9.7.3.3-2.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.3.6 Transmission quality measurement subscription request
|
Table 9.7.3.6-1 describes the information flow from the SEALDD server to the SEALDD client for data transmission measurement subscription.
Table 9.7.3.6-1: Transmission quality measurement subscription request
Information element
Status
Description
SEALDD-UU flow ID
O
(see NOTE)
Identifier of the SEALDD-UU flow.
Multi-modal SEALDD flow ID
O
(see NOTE)
Identity of the multi-modal SEALDD flows associated with the SEALDD multi-modal connection for the measurement.
Measurement conditions
O
Indicates the temporal and/or spatial conditions.
Transmission quality measurement requirements list
M
The measurement requirement information
> Measurement ID
M
Measurement identifiers, e.g. latency, bitrate, jitter, signal strength (e.g. RSSI)
> Reporting frequency
O
The reporting frequency of measurement results (e.g. periodic reporting). If not present, it implies periodic reporting.
> Reporting periodicity
O
If the reporting frequency is periodic, the reporting periodicity shall be provided.
> Measurement period window
O
Indicates the measurement period window for transmission quality measurements
> Measurement expiration time
O
Indicates the measurement expiration time
> Reporting criteria
O
Indicates the criteria for reporting measurement results, e.g. if the latency or bitrate reaches below or above a certain value. It also includes a unique identifier for each criteria if more than one criteria is specified.
> Delay difference indicator
O
Indicates the delay difference needs to be measured.
> Flow alignment reporting criteria
O
Indicates the criteria for reporting flow alignment measurement results, e.g. if the flow alignment buffering reaches below or above a certain value for a certain amount of time. It also includes a unique identifier for each criteria if more than one criteria is specified.
> SEALDD policy
O
Specifies quality guarantee policies associated with the SEALDD connection
>> Quality guarantee policy
M
Indicates the event (e.g. measurement threshold) to be measured for, the quality guarantee.
>> Non-3GPP access measurement information
O
Indicates the non-3GPP access(like WLAN) measurement policy (e.g. WLAN SSIDs, BSSID, location-based measurement)
NOTE: Only one of the information element is present.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.3.7 Transmission quality measurement subscription response
|
Table 9.7.3.7-1 describes the information flow from the SEALDD client to the SEALDD server for responding to the transmission quality measurement subscription request.
Table 9.7.3.7-1: Transmission quality measurement subscription response
Information element
Status
Description
Result
M
Success or failure.
Expiration time
O
Indicates the expiration time of the subscription. Applicable for successful result.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.3.8 Transmission quality measurement notification
|
Table 9.7.3.8-1 describes the information flow from the SEALDD client to the SEALDD server for notifying the transmission quality measurement reports.
Table 9.7.3.8-1: Transmission quality measurement notification
Information element
Status
Description
Transmission quality measurement reports list
M
The generated transmission quality results in SEALDD server
> Measurement ID
M
Measurement identifiers, e.g. latency, bitrate, jitter, delay difference, flow alignment measurement, signal strength (e.g., RSSI)
> Measurement range
O
Indicates the range of the measurement, e.g., end to end measurement, tethering link measurement etc.
> Average measurement value
O
The average measurement value of measurement results
> Minimum measurement value
O
The minimum measurement value of measurement results
> maximum measurement value
O
The maximum measurement value of measurement results
> Standard deviation measurement value
O
Standard deviation measurement value of measurement results
> kPercentile measurement value
O
Indicates the kpercentile measurement value of measurement results
> Measurement period
O
Indicates the measurement period
> Timestamp
O
Indicates the timestamp of measurement results
> Non-3GPP access measurement information
O
Indicates the non-3GPP access measurement information report.
> Measured non-3GPP access
O
List of measured non-3GPP access (e.g., WLAN SSID(s)/BSSID(s) or location information).
>> Signal strength value(s)
M
List of signal strength values (e.g., RSSI) for the measured non-3GPP access.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.3.9 SEALDD enabled data transmission quality measurement subscription update request
|
Table 9.7.3.9-1 describes the information flow from the VAL server to the SEALDD server for updating the data transmission measurement subscription service.
Table 9.7.3.9-1: SEALDD transmission quality measurement subscription update request
Information element
Status
Description
Subscription ID
M
Subscription identifier corresponding to the updated subscription.
Updated transmission quality measurement information
O
(see NOTE)
The updated transmission quality measurement information, as described in Table 9.7.3.1-1.
NOTE: At least one of these IEs in Table 9.7.3.1-1 is present.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.3.10 SEALDD enabled data transmission quality measurement subscription update response
|
Table 9.7.3.10-1 describes the information flow from the SEALDD server to the VAL server for responding to the transmission quality measurement subscription update request.
Table 9.7.3.10-1: SEALDD transmission quality measurement subscription update response
Information element
Status
Description
Result
M
Success or failure.
Expiration time
O
Indicates the expiration time of the subscription. Applicable for successful result.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.3.11 SEALDD enabled data transmission quality measurement unsubscribe request
|
Table 9.7.3.11-1 describes the information flow from the VAL server to the SEALDD server for unsubscribing to the data transmission measurement service.
Table 9.7.3.11-1: SEALDD transmission quality measurement unsubscribe request
Information element
Status
Description
Subscription ID
M
Subscription identifier corresponding to the unsubscription.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.