Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.433  Word version:  19.0.0

Top   Top   Up   Prev   Next
0…   4…   7…   8…   9.2…   9.2.2.3…   9.2.3…   9.2.4…   9.3…   9.3.2.2…   9.3.3…   9.3.4…   9.4…   9.5…   9.5.3…   9.5.4…   9.6…   9.7…   9.7.3…   9.7.4…   9.8…   9.9…   9.10…   A…   C… 
9.7 SEALDD enabled data transmission quality measurement  9.7.1 General  9.7.2 Procedures  9.7.2.1 Data transmission quality measurement  9.7.2.2 Data transmission quality query  9.7.2.3 Data transmission quality measurement reported by SEALDD client 
...

 

9.7  SEALDD enabled data transmission quality measurement  p. 64

9.7.1  General  p. 64

The following clauses specify procedures, information flows and APIs for SEALDD enabled data transmission quality measurement.

9.7.2  Procedures  p. 64

9.7.2.1  Data transmission quality measurement  p. 64

Figure 9.7.2.1-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 TS 23.501.
  2. The VAL server discovers and selects the SEALDD server by CAPIF functions.
Reproduction of 3GPP TS 23.433, Fig. 9.7.2.1-1: SEALDD enabled data transmission quality measurement procedure
Figure 9.7.2.1-1: SEALDD enabled data transmission quality measurement procedure
Up
Step 1.
An on-going regular data transmission connection is established according to clause 9.2.2.2.
Step 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), and may also include reporting criteria, reporting frequency, spatial condition and temporal condition.
Step 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.
Step 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.
Step 5.
The SEALDD client receives the DL monitoring packet, and records the local time T2.
Step 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.
Step 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 can also calculate 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.
Step 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) 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 can send 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.
Up

9.7.2.2  Data transmission quality query  p. 66

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.
Reproduction of 3GPP TS 23.433, Fig. 9.7.2.2-1: SEALDD enabled data transmission quality query procedure
Figure 9.7.2.2-1: SEALDD enabled data transmission quality query procedure
Up
Step 1.
The consumers (e.g. VAL server, SEALDD server, NSCE server, ADAE server) can send 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.
Step 2.
The SEALDD server responds with the transmission quality measurement result (e.g. packet delay, bitrate, packet loss rate).

9.7.2.3  Data transmission quality measurement reported by SEALDD client  p. 67

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.
Reproduction of 3GPP TS 23.433, Fig. 9.7.2.3-1: VAL data transmission quality measurement reported by SEALDD client
Figure 9.7.2.3-1: VAL data transmission quality measurement reported by SEALDD client
Up
Step 1.
An on-going regular data transmission connection is established according to clause 9.2.2.2.
The transmission quality measurement can be triggered by VAL server or VAL client, which is described in step 2 to step 5 and step 6, correspondingly.
Step 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.
Step 3.
Upon receiving the request, the SEALDD server performs an authorization check. If authorization is successful, the SEALDD server responds to the VAL server.
Step 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. The SEALDD client, based on the received service quality guarantee policy including thresholds and action, can take corrective action as described in clause 9.7.2.3.
Step 6.
The VAL client triggers the SEALDD transmission quality measurement procedure to the SEALDD client, in order to collect the measurement report information.
Step 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.
Step 8.
The SEALDD server receives the UL monitoring packet, and records the local time T2.
Step 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 UL 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.
Step 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 can also calculate 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 if present in the SEALDD transmission quality measurement subscription request in order to generate the transmission quality measurement report.
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.
Step 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.
Step 13.
The SEALDD client reports the data transmission quality measurement results to the VAL client.
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.
Up

Up   Top   ToC