Synchronization of multi-modal data services

Abstract

The present disclosure provides systems, apparatus, equipment, and methods, including computer programs encoded on storage media, for data unit synchronization. A first wireless communication device transmits (515) a first single modality data unit of a first data stream to a second wireless communication device. The first wireless communication device transmits (520) a second single modality data unit of a second data stream different from the first data stream to the second wireless communication device. The first wireless communication device transmits (530) a first indicator of a synchronization delay associated with the first single modality data unit and the second single modality data unit to the second wireless communication device.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit and priority of U.S. Provisional Patent Application No. 63 / 595,667, filed November 2, 2023, entitled “Synchronization of Multi-Modal Data Traffic,” the contents of which are expressly incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure relates generally to wireless communications, and more specifically to the synchronization of multimodal data services. Background Technology

[0004] The 3rd Generation Partnership Project (3GPP) specifies a radio interface known as Fifth Generation (5G) New Radio (NR) (5G NR). The architecture of a 5G NR wireless communication system (5GS) includes a 5G core (5GC) network, a 5G radio access network (5G-RAN), and user equipment (5G UE). Compared to previous generations of cellular communication systems, the 5G NR architecture aims to provide increased data rates, reduced latency, and / or increased capacity.

[0005] Generally speaking, wireless communication systems provide various telecommunications services (e.g., telephone, video, data, messaging, etc.) based on multiple access technologies that support communication with multiple users (such as Orthogonal Frequency Division Multiple Access (OFDMA)). Improvements in mobile broadband have continued the development of such wireless communication technologies.

[0006] Multimodal services (e.g., extended reality (XR) applications) involve the transmission of multiple unimodal data types (e.g., video data, audio data, haptic data, game control data, gesture data, etc.). Multimodal services require multimodal data streams that are correlated with each other and may originate from different sources. Due to network limitations (e.g., network congestion, scheduling, etc.), differences in the arrival times of multimodal data streams can lead to user-perceptible synchronization problems associated with different data streams. Summary of the Invention

[0007] The following is a simplified overview of one or more aspects to provide a basic understanding of such aspects. This overview is not a comprehensive summary of all anticipated aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0008] The UE or network entity (e.g., base station, base station element, core network entity, etc.) transmits single-modal data organized into sets of Protocol Data Units (PDUs) and / or data bursts. A PDU set includes one or more PDUs carrying a payload of an information unit (e.g., user content or control information) generated at the application level. The synchronized arrival of multiple single-modal streams (e.g., video, audio, haptic data, etc.) supports a pleasant multimodal user experience. Latency in one of these streams (e.g., an audio stream), while tolerable for the user for that particular stream, may be unacceptable if it is not synchronized with a video or haptic stream associated with the same application.

[0009] To address the potential lack of synchronization between different data streams, a data source entity (e.g., a UE or network entity) implements control techniques for measuring and reporting synchronization delays. For example, the data source entity transmits a first unimodal data unit and a second unimodal data unit. The data source entity transmits a multimodal service identifier indicating that the first and second unimodal data units are associated with the same multimodal application. The first data unit includes at least one of a first PDU, a first PDU set, or a first data burst. The second data unit includes at least one of a second PDU, a second PDU set, or a second data burst. The data source entity measures the synchronization delay from the end of transmission of the first unimodal data unit to the end of transmission of the second unimodal data unit. The data source entity transmits an indicator of the synchronization delay between the first and second unimodal data units. The synchronization delay indicator may include a time period value indicating the synchronization delay, a time period value indicating the amount of time the synchronization delay exceeds a synchronization delay threshold, and / or a code point indicating that the synchronization delay exceeds a synchronization delay threshold. In some aspects, the data source entity transmits the synchronization delay indicator periodically. Alternatively, when the synchronization delay exceeds the synchronization delay threshold for the synchronization delay measurement period, the data source entity sends a synchronization delay indicator.

[0010] In some aspects, the data source entity sends a signal to the data destination entity to correct for synchronization delay. Alternatively, the data source entity, based on a synchronization delay exceeding a synchronization delay threshold, merges the Quality of Service (QoS) stream associated with the first unimodal data unit and the QoS stream associated with the second unimodal data unit onto the same Data Radio Bearer (DRB). Alternatively, the data source entity concatenates the Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) associated with the first unimodal data unit and the PDCP SDU associated with the second unimodal data unit.

[0011] In some aspects, the data source entity increases the priority or bit rate associated with the first or second single-mode data unit based on the synchronization delay exceeding a synchronization delay threshold, depending on which PDU set is late. For example, the late PDU set is moved to a higher-priority logical channel (LCH) or mapped to a QoS stream with lower latency or higher priority.

[0012] Depending on some aspects, the UE sends (or the network entity sends to the UE) a first single-mode data unit of a first data stream. The UE sends (or the network entity sends to the UE) a second single-mode data unit of a second data stream different from the first data stream. The UE sends (or the network entity sends to the UE) a first indicator of the synchronization delay associated with the first and second single-mode data units.

[0013] The technical benefits of this disclosure include measuring and reporting synchronization latency within a single-modal stream of multimodal data services. Further benefits include network entities and / or UEs using references... Figures 2 to 19 The example described is used to correct synchronization delay. Attached Figure Description

[0014] Figure 1 A diagram of a wireless communication system according to an embodiment is shown, the wireless communication system including a plurality of user equipment (UEs) and network entities communicating through one or more cells.

[0015] Figure 2 A diagram of a wireless communication system according to an embodiment is shown, the wireless communication system including a plurality of UEs and network entities in communication.

[0016] Figure 3A A diagram illustrating multiple service flows between the UE and the application server according to an embodiment is shown.

[0017] Figure 3B A timing diagram showing the synchronization delay between a first service flow and a second service flow according to an embodiment is shown.

[0018] Figure 4 A timing diagram of the synchronization delay between the first PDU set and the second PDU set according to an embodiment is shown.

[0019] Figure 5 This is a signaling diagram illustrating communication between a UE (user unit) as a data source entity and a network entity as a data destination entity for synchronizing multimodal data streams, according to an embodiment.

[0020] Figure 6 This is a signaling diagram illustrating communication between a network entity acting as a data source and a UE acting as a data destination for synchronizing multimodal data streams, according to an embodiment.

[0021] Figure 7 This is a signaling diagram illustrating communication between the core network, which acts as the data source entity, and the RAN, which acts as the data destination entity, for synchronizing multimodal data streams according to an embodiment.

[0022] Figure 8 This is a signaling diagram illustrating communication between the RAN, which acts as a data source entity, and the core network, which acts as a data destination entity, for synchronizing multimodal data streams, according to an embodiment.

[0023] Figure 9 This is a flowchart of a method for detecting synchronization delay in a multimodal data stream by a data source entity according to an embodiment, and requesting correction of the synchronization delay at the data destination entity when the synchronization delay meets a threshold criterion.

[0024] Figure 10 This is a flowchart of a method for a data source entity to detect synchronization delays in a multimodal data stream and periodically report the synchronization delays to a data destination entity, according to an embodiment.

[0025] Figure 11 This is a flowchart of a method for detecting synchronization delay in a multimodal data stream by a data source entity according to an embodiment and correcting the synchronization delay by increasing the priority or bit rate of the multimodal data stream.

[0026] Figure 12 This is a flowchart of a method for detecting synchronization delay in a multimodal data stream by a data source entity according to an embodiment and correcting the synchronization delay by merging or concatenating the multimodal data streams.

[0027] Figure 13 This is a flowchart of a method for a data source entity to detect synchronization delays in a multimodal data stream and discard or reallocate resources to a delayed PDU set, according to an embodiment.

[0028] Figure 14 An example Delay Status Report (DSR) with multimodal synchronization information is shown according to an embodiment.

[0029] Figure 15 An example synchronization DSR with multimodal synchronization information is shown according to an embodiment.

[0030] Figure 16 This is a flowchart of a wireless communication method at a first wireless communication device according to an embodiment.

[0031] Figure 17 This is a flowchart of a wireless communication method at a second wireless communication device according to an embodiment.

[0032] Figure 18This is a diagram illustrating a hardware implementation of an example UE device according to some embodiments.

[0033] Figure 19 This is a diagram illustrating hardware implementations of one or more example network entities according to some embodiments.

[0034] exist Figures 1 to 19 In this context, the same reference numerals refer to the same elements. Detailed Implementation

[0035] Figure 1 Figure 100 illustrates a wireless communication system associated with multiple cells 190. The wireless communication system includes user equipment (UE) 102 and base station / network entity 104. Some base stations may include an aggregated base station architecture, and others may include a decomposed base station architecture. The aggregated base station architecture utilizes a radio protocol stack physically or logically integrated within a single radio access network (RAN) node. The decomposed base station architecture utilizes a protocol stack physically or logically distributed across two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110). For example, CU 110 is implemented within a RAN node, and one or more DU 108s may be located in the same location as CU 110, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DU 108 may be implemented to communicate with one or more RU 106s. Any of RU 106, DU 108, and CU 110 can be implemented as a virtual unit, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). Base station / network entity 104 (e.g., an aggregated base station or a decomposed unit of a base station, such as RU 106 or DU 108) can be referred to as a transmit receiver point (TRP).

[0036] The operation and / or network design of base station 104 can be based on the aggregation characteristics of base station functionality. For example, a decomposed base station architecture can be utilized in an Integrated Access Backhaul (IAB) network, an Open Radio Access Network (O-RAN) network, or a Virtual Radio Access Network (vRAN) (which may also be referred to as a Cloud Radio Access Network (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing functionality for at least one unit, which allows for flexibility in network design. Various units in a decomposed base station architecture or a decomposed RAN architecture can be configured to communicate with at least one other unit via wired or wireless communication. For example, base stations 104d, 104e and / or RUs 106a, 106b, 106c, 106d can communicate with UEs 102a, 102b, 102c, 102d and / or 102s via one or more radio frequency (RF) access links based on a Uu interface. In the example, multiple RUs 106 and / or base stations 104 can simultaneously serve UE 102, such as through intra-cell and / or inter-cell access links between UE 102 and RUs 106 / base stations 104.

[0037] RU 106, DU 108, and CU 110 may include (or may be coupled to) one or more interfaces configured to transmit or receive information / signals via wired or wireless transmission media. For example, a wired interface may be configured to transmit or receive information / signals via a wired transmission media, such as a fronthaul link 160 between RU 106d and a baseband unit (BBU) 112 of base station 104d associated with cell 190d. BBU 112 includes DU 108 and CU 110, and may also have a wired interface (e.g., a midhaul link) configured between DU 108 and CU 110 to transmit or receive information / signals between DU 108 and CU 110. In a further example, a wireless interface that may include a receiver, transmitter, or transceiver such as an RF transceiver may be configured to transmit and / or receive information / signals via a wireless transmission medium, such as information transmitted between RU 106a in cell 190a and base station 104e in cell 190e via inter-cell communication beams 136-138 of RU 106a and base station 104e.

[0038] RU 106 can be configured to implement low-level functionality. For example, RU 106 is controlled by DU 108 and can correspond to a logical node that manages RF processing functions or low-level PHY functionality, such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction, and filtering. The functionality of RU 106 can be based on functional partitioning, such as low-level functional partitioning.

[0039] RU 106 can send or receive over-the-air (OTA) communications with one or more UEs 102. For example, RU 106b of cell 190b communicates with UE 102b of cell 190b via a first communication beamset 132 of RU 106b and a second communication beamset 134b of UE 102b, which may correspond to inter-cell communication beams or, in some examples, inter-cell communication beams. For example, UE 102b of cell 190b can communicate with RU 106a of cell 190a via a third communication beamset 134a of UE 102b and a fourth communication beamset 136 of RU 106a. DU 108 can control the real-time and non-real-time characteristics of control plane and user plane communications of RU 106.

[0040] Any combination of RU 106, DU 108, and CU 110, or a reference to them individually, may correspond to base station 104. Therefore, base station 104 may include at least one of RU 106, DU 108, or CU 110. Base station 104 provides UE 102 with access to core network 120. Base station 104 may relay communication between UE 102 and core network 120. Base station 104 may be associated with macro cells of higher-power cellular base stations and / or small cells of lower-power cellular base stations. For example, cell 190e may correspond to a macro cell, while cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network including at least one macro cell and at least one small cell may be referred to as a "heterogeneous network." One or more CUs 110 may communicate directly with core network 120 via a backhaul link. For example, CU 110 may communicate with core network 120 via a backhaul link based on a next-generation (NG) interface. One or more CUs 110 can also communicate indirectly with the core network 120 via one or more decomposed base station units, such as near real-time RAN intelligent controllers (RICs) via E2 links and service management and orchestration (SMO) frameworks that can be associated with non-real-time RICs.

[0041] Transmissions from UE 102 to base station 104 / RU 106 are referred to as uplink (UL) transmissions, while transmissions from base station 104 / RU 106 to UE 102 are referred to as downlink (DL) transmissions. Uplink transmissions can also be referred to as reverse link transmissions, and downlink transmissions can also be referred to as forward link transmissions. For example, RU 106d uses the antenna of base station 104d in cell 190d to send downlink / forward link communication to UE 102d, or receive uplink / reverse link communication from UE 102d, based on the Uu interface associated with the access link between UE 102d and base station 104d / RU 106d.

[0042] The communication link between UE 102 and base station 104 / RU 106 can be based on multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link can be associated with one or more carriers. UE 102 and base station 104 / RU 106 can utilize up to a total of Yx Each carrier allocated in MHz carrier aggregation Y Spectral bandwidths of MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, 800 MHz, 1600 MHz, 2000 MHz, etc.), where x Each component carrier (CC) is used for communication in each of the uplink and downlink directions. The carriers may or may not be adjacent to each other along the spectrum. In the example, uplink and downlink carriers may be allocated asymmetrically, with more or fewer carriers allocated to the uplink or downlink. A component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be associated with a primary cell (PCell), and the secondary component carriers may be associated with secondary cells (SCells).

[0043] Some UEs, such as UEs 102a and 102s, can perform device-to-device (D2D) communication via sidelinks. For example, sidelink / D2D communication utilizes the spectrum of a wireless wide area network (WWAN) associated with uplink and downlink communication. Such sidelink / D2D communication can be performed by various wireless communication systems such as Wi-Fi, Bluetooth, LTE, and NR systems.

[0044] UE 102 and base station 104 / RU 106 may each include multiple antennas. These multiple antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that facilitate beamforming operation. For example, RU 106b transmits downlink beamforming signals to UE 102b based on a first communication beamset 132 in one or more transmit directions of RU 106b. UE 102b may receive downlink beamforming signals from RU 106b based on a second communication beamset 134b in one or more receive directions of UE 102b. In a further example, UE 102b may also transmit uplink beamforming signals (e.g., sounding reference signals (SRS)) to RU 106b based on the second communication beamset 134b in one or more transmit directions of UE 102b. RU 106b may receive uplink beamforming signals from UE 102b in one or more receive directions of RU 106b. UE 102b can perform beam training to determine the optimal reception and transmission directions for the beamformed signal. The transmission and reception directions for UE 102 and base station 104 / RU 106 can be the same or different.

[0045] In a further example, the beamformed signal can be transmitted between the first base station / RU 106a and the second base station 104e. For example, base station 104e of cell 190e can transmit the beamformed signal to RU 106a based on communication beam 138 in one or more transmit directions of base station 104e. RU 106a can receive the beamformed signal from base station 104e of cell 190e based on RU communication beam 136 in one or more receive directions of RU 106a. In a further example, base station 104e transmits a downlink beamformed signal to UE 102e based on communication beam 138 in one or more transmit directions of base station 104e. UE 102e receives the downlink beamformed signal from base station 104e based on UE communication beam 130 in one or more receive directions of UE 102e. UE 102e can also transmit uplink beamforming signals to base station 104e in one or more transmission directions of UE 102e based on UE communication beam 130, so that base station 104e can receive uplink beamforming signals from UE 102e in one or more reception directions of base station 104e.

[0046] Base station 104 may include and / or be referred to as a network entity. That is, "network entity" may refer to base station 104 or at least one element of base station 104, such as RU 106, DU 108, and / or CU 110. Base station 104 may also include and / or be referred to as Next Generation Evolved Node B (ng-eNB), Next Generation NB (gNB), Evolved NB (eNB), access point, base transceiver, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), TRP, network node, network device, or other related terms. Base station 104 or the entity at base station 104 may be implemented as an IAB node, relay node, sidelink node, aggregated (monolithic) base station, or a decomposed base station including one or more RU 106, DU 108, and / or CU 110. Aggregated or decomposed base station sets may be referred to as Next Generation Radio Access Network (NG-RAN). In some examples, UE 102a operates in dual connectivity (DC) with base station 104e and base station / RU 106a. In such cases, base station 104e can be the primary node, while base station / RU 160a can be the secondary node.

[0047] Still referencing Figure 1 In some aspects, either of the UEs 102 (the first wireless communication device) may include a multimodal dataset (MMDS) component 140 configured to transmit a first single-mode PDU set of a first data stream to a second wireless communication device. The MMDS component 140 is further configured to transmit a second single-mode PDU set of a second data stream, different from the first data stream, to the second wireless communication device. The MMDS component 140 is further configured to transmit a first indicator of the synchronization delay associated with the first and second single-mode PDU sets to the second wireless communication device.

[0048] In some aspects, any of the base stations 104 or the network entity of the base station 104 (the second wireless communication device) may include a synchronization delay component 150 configured to receive a first single-mode PDU set from the first wireless communication device of a first data stream. The synchronization delay component 150 is further configured to receive a second single-mode PDU set from the first wireless communication device of a second data stream different from the first data stream. The synchronization delay component 150 is further configured to receive from the first wireless communication device a first indicator of the synchronization delay associated with the first and second single-mode PDU sets.

[0049] therefore, Figure 1A wireless communication system that can be implemented in conjunction with aspects of one or more other accompanying figures described herein is described. Furthermore, although the following description may focus on 5G NR, the concepts described herein are applicable to other similar fields, such as 5G-Advanced and future versions, LTE, LTE-advanced (LTE-A), and other wireless technologies such as 6G.

[0050] Figure 2 A diagram of a wireless communication system 200 is shown, comprising multiple UEs 102 and a network entity 104 communicating via an access link 250 (e.g., a Uu access link). Network entity 104 communicates with a core network 120 via a backhaul link 252a (e.g., an Xn interface). Core network 120 communicates with an XR server 121 via an N6 interface 254. UEs 102 communicate directly with each other via direct links 253 (e.g., a LAN, a sidelink PC5, WiFi, a Universal Serial Bus (USB), etc.). UEs 102 execute applications using multimodal data, such as extended reality (XR) applications (e.g., augmented reality (AR), virtual reality (VR), and / or mixed reality (MR)). In some aspects, UEs 102 transmit multimodal data associated with XR applications to XR server 121. UE 102 transmits video data to XR server 121 via network entity 104 and core network 120 using backhaul link 252 and N6 interface 254. In some aspects, XR device 201 (e.g., XR headset, XR glasses) performs XR applications and uses UE 102a as a hub / gateway to communicate with XR server 121. For example, the XR application or video codec resides in XR device 201, and the modem resides in UE 102a. XR device 201 communicates with UE 102a using additional link 250c (e.g., LAN, sidelink PC5, WiFi, USB, wired cable, etc.).

[0051] XR applications require multimodal data services to create immersive and engaging XR experiences for users. For example, an XR application might use a head-mounted display (HMD) to provide a visual view of the environment, speakers to deliver audio content, and haptic gloves to provide haptic feedback. Multimodal flows can terminate at different endpoints; for instance, audio and video data streams can be handled by VR glasses, while haptic feedback can be handled by haptic gloves. The different content streams are often related, and they are presented to the user synchronously at the endpoints, requiring the network to deliver them with similar latency.

[0052] Each unimodal data stream in a multimodal data stream can be of a different type of data, such as audio, video, location, haptic data, etc. Each unimodal data stream in a multimodal data stream is associated with the same application (e.g., an XR service). To address the potential lack of synchronization between different data streams, a data source entity (e.g., UE 102, network entity 104, core network 120, or XR server 121) implements control techniques for measuring and reporting synchronization delays. For example, the data source entity sends a first unimodal PDU set and a second unimodal PDU set. The data source entity sends a multimodal service identifier indicating that the first and second unimodal PDU sets are associated with the same multimodal application. The data source entity measures the synchronization delay from the end of transmission of the first unimodal PDU set to the end of transmission of the second unimodal PDU set. The data source entity sends an indicator of the synchronization delay between the first and second single-mode PDU sets to the data destination entity (e.g., UE 102, network entity 104, core network 120, or XR server 121). The data source entity may send a request to the data destination entity to correct the synchronization delay. Alternatively, the data source entity implements control techniques to correct the synchronization delay.

[0053] Figure 3A Figure 300 illustrates multiple service flows between UE 102 and application server 121 according to an embodiment. UE 102 transmits multiple service flows with application server 121 via network entity 104 and core network 120. Service flows include any number of service flows associated with a multimodal application. For example, service flow 1 includes a first PDU set 311 (e.g., video data) and a second PDU set 313 (e.g., haptic data). Users of the application expect the first and second service flows to arrive synchronously for a pleasant multimodal user experience. If the service flows are not synchronized, the delay in the arrival of the first PDU set 311 relative to the arrival of the second PDU set 313 (or the delay in the arrival of the second PDU set 313 relative to the arrival of the first PDU set 311) may be unacceptable. The method of this disclosure includes detecting synchronization delays between service flows and correcting the synchronization delays when the delays meet a threshold criterion (e.g., the synchronization delay exceeds a threshold). The synchronization delay can be based on the maximum tolerable time interval between the stimulus initiation associated with the first monomodal PDU set 311 and the stimulus initiation associated with the second monomodal PDU set 313.

[0054] Figure 3BA timing diagram 301 illustrating the synchronization delay between a first service flow 311 and a second service flow 313 according to an embodiment is shown. In some aspects, the MMDS 303 includes one or more PDUs and / or a set of PDUs carrying information payloads (e.g., audio data, video data, haptic data, gesture data, etc.) from multiple multimodal QoS flows associated with the same service (e.g., an XR service). The MMDS 303 can be considered as a data unit used to calculate the synchronization delay. Figure 3B In this context, the first MMDS 303a includes a first PDU set 311a and a second PDU set 313a.

[0055] In some aspects, service flow 1 311 includes a first PDU set 311a arriving at the transmit buffer at time t1a and a third PDU set 311b arriving at the transmit buffer at time t1b. Service flow 1 may include periodic data (e.g., video data). The periodicity of the data arriving at the buffer may correspond to frame rate 321 (shown as time periods 321a, 321b). In some aspects, service flow 2 313 includes a second PDU set 313a (e.g., haptic data) arriving at the buffer at time t5a and a fourth PDU set 313b arriving at the buffer at time t5b.

[0056] Within the first MMDS 303a, the second PDU set 313a arrives at the buffer later than the first PDU set 311a by a time gap 318a (time t5a minus time t1a). The data source entity begins sending PDU set 311a at time t2a and completes sending PDU set 311a at time t3a, thus generating the first PDU set sending time 309a. The data source entity begins sending PDU set 313a at time t7a and completes sending PDU set 313a at time t8a, thus generating the second PDU set sending time 312a.

[0057] In some aspects, the data source entity measures the synchronization delay 319a of the first MMDS 303a as the time period from the end of transmission of the first PDU set 311a to the end of transmission of the second PDU set 313a (time t8a minus time t3a). See reference... Figures 5 to 13 As described, the data source entity reports synchronization delays to the data destination entity. In some aspects, the data source entity sends a request to the data destination entity to correct the synchronization delay. Alternatively or concurrently, the data source entity implements methods for correcting synchronization delays.

[0058] exist Figure 3BIn this embodiment, the second MMDS 303b includes a third PDU set 311b and a fourth PDU set 313b. In some aspects, traffic flow 1 311 includes a third PDU set 311b arriving at the transmit buffer at time t1b. The periodicity of the data arriving at the buffer may correspond to the frame rate 321b. In some aspects, traffic flow 2 313 includes a fourth PDU set 313b (e.g., haptic data) arriving at the buffer at time t5b. The fourth PDU set 313b arrives at the buffer later than the third PDU set 311b by a time gap 318b (time t5b minus time t1b). The data source entity begins transmitting the third PDU set 311b from the buffer at time t2b and completes the transmission at time t3b, resulting in a third PDU set transmission time 309b. The data source entity begins transmitting the fourth PDU set 313b at time t7b and completes the transmission at time t8b, resulting in a fourth PDU set transmission time 312b. Here, the amount of synchronization delay 319b is different from (for example, greater than) the amount of synchronization delay 319a.

[0059] In some aspects, when synchronization delay 319 meets a threshold criterion (e.g., synchronization delay 319 exceeds a synchronization delay threshold), the data source entity reports and / or corrects synchronization delay 319. Figure 3B In the example, the second PDU set 313 arrives at the transmit buffer and is transmitted later than the first PDU set 311. However, this disclosure is not limited to this, and the first PDU set 311 may arrive and / or be transmitted later than the second PDU set 313. The synchronization delay or synchronization delay difference can be a positive or negative value. If the value is positive, it means that the first PDU set 311 is earlier than the second PDU set 313. If the value is negative, it means that the second PDU set 313 is earlier than the first PDU set 311. Different synchronization delay thresholds may be used depending on whether the reference traffic flow (e.g., traffic flow 1) is periodic, whether traffic flow 1 is earlier than traffic flow 2 or traffic flow 2 is earlier than traffic flow 1, and / or other factors.

[0060] Figure 4 A timing diagram 400 is shown illustrating the synchronization delay between the fifth PDU set 311c and the sixth PDU set 313c according to an embodiment. (Continued) Figure 3B MMDS service flow, and Figure 3B compared to, Figure 4 A more detailed description of the synchronization delay threshold of 417 is provided. Figure 4In MMDS 303c, a fifth PDU set 311c and a sixth PDU set 313c are included. In some aspects, the fifth PDU set 311c has a first delay budget 305 (e.g., a latency requirement). The fifth PDU set 311c arrives at the transmit buffer at time t1c. The sixth PDU set 313c arrives at the transmit buffer at time t5c, resulting in a buffer arrival time difference 318c. If the fifth PDU set 311c is not transmitted within the first delay budget 305, the data source entity discards the fifth PDU set 311c at time t4c. If the sixth PDU set 313c is not transmitted within the second delay budget 307, the data source entity discards the sixth PDU set 313c at time t9c. The first delay budget 305 and the second delay budget 307 can be predefined (e.g., predefined in 3GPP TS 22.261) and based on the type of data (e.g., video, audio, haptic, control, etc.) associated with the fifth PDU set 311c and the sixth PDU set 313c, respectively.

[0061] exist Figure 4 In the example, the data source entity begins sending the fifth PDU set 311c at time t2c and completes the transmission at time t3c, resulting in a fifth PDU set transmission time 309c within the first delay budget 305. The data source entity begins sending the sixth PDU set 313c at time t7c and completes the transmission at time t8c, resulting in a sixth PDU set transmission time 312c within the second delay budget 307 ending at time t9c. However, the data source entity does not send the sixth PDU set 313c within the synchronization delay threshold 417. The data source entity can report synchronization delays exceeding the synchronization delay threshold and / or correct the synchronization delay, as shown in the reference. Figures 5 to 13 As described, the value of the synchronization delay threshold 417 can be predefined based on the type of data associated with the first traffic flow 311 and the second traffic flow 313, respectively (e.g., predefined in 3GPP TS 22.261).

[0062] Figure 5Signaling diagram 500 illustrates communication for synchronizing multimodal data streams between UE 102, acting as a data source entity, and network entity 104, acting as a data destination entity, according to an embodiment. UE 102 sends a 505 MMDS identifier to network entity 104. In this regard, UE 102 sends the MMDS identifier to network entity 104 via RRC signaling, Time-Sensitive Communication Assistance Information (TSCAI), UE Assistance Information, or other suitable communication mechanisms. The MMDS identifier identifies a set of QoS streams associated with the same multimodal service. For example, the MMDS identifier may be associated with multiple QoS streams related to the same XR service for UE 102 or multiple UEs 102. The MMDS identifier indicates to network entity 104 the QoS streams belonging to a first PDU set and a second PDU set. For example, the MMDS may consist of video frames and associated audio and / or haptic PDU sets required by the application at the same time. The MMDS identifier is included in the reference... Figure 14 and Figure 15 In the described data structure, in some aspects, UE 102 and / or network entity 104 may use MMDS to perform packet drop. For example, if one or more packets of MMDS are dropped or lost, the entire MMDS is dropped.

[0063] Network entity 104 sends a 510 synchronization delay reporting period indicator and / or measurement period indicator to UE 102 via RRC signaling, Media Access Control-Control Element (MAC-CE) messages, Downlink Control Information (DCI) or other suitable communication mechanisms. The measurement period indicator indicates how often UE 102 measures the synchronization delay. The synchronization delay reporting period indicator indicates how often UE 102 reports the synchronization delay to network entity 104. Synchronization delay reporting can be activated / deactivated by network entity 104 via RRC signaling and / or dynamic DCI signaling.

[0064] UE 102 sends 515 the first PDU set (e.g., the first single-mode PDU set) to network entity 104, as shown in reference. Figure 3B Elements 311a, 311b and Figure 4 As described in element 311c. UE 102 sends 520 a second PDU set (e.g., a second single-mode PDU set) to network entity 104, as referenced. Figure 3B Elements 313a, 313b and Figure 4 The element 313c is described.

[0065] UE 102 measures the synchronization delay between the first PDU set and the second PDU set, as shown in reference 525. Figure 3B Elements 319a, 319b and Figure 4As described in element 319c. In some aspects, UE 102 measures the maximum, average, or median synchronization delay difference between QoS flows within a defined time window, a moving average, or based on an infinite impulse response (IIR) filter. In some aspects, if the synchronization delay meets a threshold criterion (e.g., the synchronization delay exceeds a synchronization delay threshold), MMDS comprising the first and second PDU sets may be discarded.

[0066] In some aspects, the UE 102 application processor (e.g., application processor 1806) monitors synchronization delay and signals the synchronization delay to the UE 102 modem processor (e.g., modem processor 1826) when the synchronization delay meets a threshold criterion. For example, when the QoS flow is a multimodal service flow generated by the tethered XR device 201.

[0067] UE 102 sends a 530 synchronization delay indicator to network entity 104 and / or the core network via PDCP control PDU, Radio Link Control (RLC) PDU, MAC-CE, RRC signaling, TSCAI, UE assistance information, UCI, DSR, or other suitable communication mechanisms. In some aspects (not shown), UE 102 sends a UE capability signaling message to network entity 104 (e.g., s upportOfSynchronizationDelaySignalling It has the ability to signal to notify it of the synchronization delay.

[0068] UE 102 periodically and / or when the synchronization delay meets a synchronization delay threshold criterion (e.g., the synchronization delay exceeds the synchronization delay threshold). Network entity 104 can configure a synchronization delay threshold for each PDU session and / or a set of QoS flows for UE 102. In some aspects, UE 102 sends a 530 synchronization delay indicator when the synchronization delay is consistently higher than the synchronization delay threshold (e.g., within a specified / configurable window or for a specified / configurable number of measurement periods). The synchronization delay can be indicated as a time period (e.g., milliseconds, number of time slots, number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, number of frames, number of subframes, etc.), a time period indicating the amount of time the synchronization delay exceeds the synchronization delay threshold (e.g., milliseconds, number of time slots, number of OFDM symbols, number of frames, number of subframes, etc.), and / or a code point indicating that the synchronization delay meets the synchronization delay threshold criterion. In some aspects, UE 102 sends the synchronization delay indicator as a range of synchronization delays within a time period rather than a single value. For example, a synchronization delay indicator may include the minimum, maximum, mean, median, and variance of the synchronization delay over a time period, the maximum value of the synchronization delay over a time period, and / or the average value of the synchronization delay over a time period (e.g., based on an IIR filter).

[0069] In some aspects, when the difference between a newly measured synchronization delay and a previously reported synchronization delay exceeds a differential synchronization delay threshold criterion configured by network entity 104, UE 102 sends a 530 synchronization delay indicator. In some aspects, UE 102 may be configured with a disable timer to prevent UE 102 from over-reporting.

[0070] UE 102 may optionally send a request for synchronization delay correction to network entity 104 via RRC signaling, TSCAI, UE assistance information, UCI, or other suitable communication mechanisms. In some aspects, network entity 104 interprets the synchronization delay indicator as an implicit request to correct the synchronization delay. In response, network entity 104 corrects the synchronization delay. For example, network entity 104 increases the priority of the lagging PDU set and / or moves the lagging PDU set to a higher priority LCH. Alternatively or additionally, network entity 104 may move PDU sets of the same MMDS to the same LCH or to multiple LCHs with similar priorities to improve synchronization. Alternatively or additionally, network entity 104 may adjust the priority of a group of LCHs carrying the same MMDS. For example, network entity 104 may temporarily or permanently set the priority of a group of LCHs to be the same to improve synchronization.

[0071] The network entity may optionally send command 540 to UE 102 to adjust the LCH parameters associated with the lagging traffic flow. For example, the network entity may optionally send command 540 to UE 102 to increase the priority and / or priority bit rate (PBR) of the LCH carrying the lagging traffic flow. In response, UE 102 increases the priority and / or PBR of the LCH carrying the lagging traffic flow by command 545. Alternatively, UE 102 maps the lagging traffic flow to a higher priority LCH. After adjusting the LCH parameters, UE 102 sends command 550, LCH parameter adjustment confirmation, to the network entity. The LCH parameter adjustment confirmation indicates the LCH parameter adjustment to network entity 104. In some aspects, UE 102 allocates resources (e.g., time resources, frequency resources, and / or spatial resources) only to selected logical channels based on LCH restrictions. To correct for synchronization delay, UE 102 can allocate the remaining resources after the conventional logical channel prioritization (LCP) procedure to late packets or late flows belonging to logical channels that would otherwise not be mapped to such resources according to the conventional LCP procedure.

[0072] If the QoS flows associated with the first and second PDU sets are mapped to two different data radio bearers (DRBs), these two QoS flows may experience two different delays in the RAN. The RAN delay threshold can be obtained from the synchronization delay (specified from the core network or signaled). The RAN can define / specify new synchronization thresholds to be followed in RAN transmissions. In some aspects, UE 102 corrects for synchronization delay by merging QoS flows 555 onto the same DRB. For example, UE 102 may optionally merge the QoS flows associated with the first PDU set and the QoS flows associated with the second PDU set 555. UE 102 may merge 555 QoS flows when the synchronization delay exceeds the synchronization delay threshold. UE 102 may optionally transmit 556 a third PDU set (e.g., video data) and a fourth PDU set (e.g., haptic data) merged onto the same QoS flow.

[0073] In some aspects, UE 102 concatenates PDCP SDUs from multiple QoS streams of the same multimodal service into the same PDCP PDU. For example, UE 102 concatenates PDCP SDUs of a first PDU set with PDCP SDUs of a second PDU set. UE 102 may optionally transmit a fifth PDU set (e.g., video data) concatenated with a sixth PDU set (e.g., haptic data). The PDCP header indicates that the SDUs are concatenated.

[0074] Figure 6 Signaling diagram 600 illustrates communication for synchronizing multimodal data streams between a network entity 104 (as a data source entity) and a UE 102 (as a data destination entity) according to an embodiment. Network entity 104 sends a first PDU set (e.g., a first single-mode PDU set) 615 to UE 102. Network entity 104 sends a second PDU set (e.g., a second single-mode PDU set) 620 to UE 102. Network entity 104 sends the first and second PDU sets 615 / 620, similar to reference... Figure 3B , Figure 4 and Figure 5 The method described.

[0075] Network entity 104 measures the synchronization delay between the first PDU set and the second PDU set, as shown in reference 625. Figure 3B , Figure 4 and Figure 5 As described. In some aspects, network entity 104 measures the maximum, average, or median delay difference between QoS flows within a defined time window, using a moving average, or based on an IIR filter. In some aspects, network entity 104 may discard MMDS comprising first and second PDU sets if the synchronization delay meets a threshold criterion (e.g., the synchronization delay exceeds a synchronization delay threshold).

[0076] Network entity 104 corrects synchronization delay 636. For example, when the synchronization delay meets a synchronization delay threshold criterion, network entity 104 corrects synchronization delay 636. In some aspects, when the synchronization delay is consistently higher than the synchronization delay threshold (e.g., within a specified / configurable window or for a specified / configurable number of measurement periods), network entity 104 corrects synchronization delay 636. For example, network entity 104 increases the priority of a 645 lagging PDU set and / or moves the lagging PDU set to a higher priority LCH. Alternatively or additionally, network entity 104 may move PDU sets of the same MMDS to the same LCH or to multiple LCHs with similar priorities to improve synchronization. Alternatively or additionally, network entity 104 may adjust the priority of a group of LCHs carrying the same MMDS. For example, network entity 104 may temporarily or permanently set the priority of a group of LCHs to be the same. After adjusting the LCH parameters, network entity 104 sends a 650 LCH parameter adjustment to UE 102. The LCH parameter adjustment indicates the LCH parameter adjustment to UE 102.

[0077] In some aspects, network entity 104 corrects synchronization delays by merging QoS flows 655 onto the same DRB. For example, network entity 104 may optionally merge QoS flows associated with a first PDU set and QoS flows associated with a second PDU set 655. Network entity 104 may optionally send 656 a third PDU set and a fourth PDU set merged onto the same QoS flow.

[0078] In some aspects, network entity 104 concatenates PDCP SDUs from multiple QoS flows of the same multimodal service into the same PDCP PDU by 660. Network entity 104 may optionally send 670 a fifth PDU set concatenated with the sixth PDU set. The PDCP header indicates that the SDUs are concatenated.

[0079] In some aspects, network entity 104 may consider the synchronization delay of traffic flows associated with the same multimodal service to readjust the Connected Mode Discontinuous Receive (C-DRX) configuration (e.g., adjust periodicity, duration, or non-duration). When the synchronization delay meets a synchronization delay threshold criterion, network entity 104 may decide to switch from a single C-DRX configuration for all traffic flows associated with the same multimodal service to multiple C-DRX configurations (e.g., one C-DRX configuration per traffic flow). Multiple C-DRX configurations can be active simultaneously. Activation / deactivation of C-DRX configurations can be semi-static (e.g., via RRC) or dynamic (e.g., via DCI signaling). The DCI bit field can be defined to activate / deactivate multiple C-DRX configurations. Taking into account the synchronization delay of UL traffic flows associated with the same multimodal service, UE 102 may signal its preferred C-DRX configuration to network entity 104.

[0080] Figure 7 Signaling diagram 700 illustrates communication for synchronizing multimodal data streams between a core network 120, acting as a data source entity, and a RAN (e.g., a network entity), acting as a data destination entity, according to an embodiment. The core network 120 (e.g., Application Functions (AF), Session Management Functions (SMF), Policy Control Functions (PCF), and / or User Plane Functions (UPF)) sends a 705 MMDS identifier to the network entity 104. In this regard, the core network 120 sends the MMDS identifier to the network entity 104 via a General Packet Radio Service Tunneling Protocol User Plane (GTP-U) header, TSCAI, and / or Next Generation Application Protocol (NGAP). In some aspects, the core network 120 receives the MMDS identifier from the application server via a Real-Time Transport Protocol (RTP) header and / or RTP header extensions. For example, existing bit fields or new bit fields may be used to signal the MMDS identifier to the core network 120.

[0081] Core network 120 sends a first PDU set (e.g., a first single-mode PDU set) 715 to network entity 104. Core network 120 sends a second PDU set (e.g., a second single-mode PDU set) 720 to network entity 104. Core network 120 sends the first and second PDU sets 715 / 720, similar to referenced. Figure 3B , Figure 4 and Figure 5 The method described, but using backhaul link 252.

[0082] Core network 120 measures the synchronization delay between the first PDU set and the second PDU set, similar to the reference. Figure 3B , Figure 4 and Figure 5The method described.

[0083] Core network 120 sends a 730 synchronization delay indicator to network entity 104. In some aspects, the synchronization delay indicator indicates the type of dependency or synchronization delay requirement. For example, audio-haptic dependencies differ from visual-haptic dependencies, resulting in different synchronization requirements. The synchronization delay indicator can signal that two specific flows in a flow group should adhere to a specific delay synchronization threshold (e.g., an indicated explicit value or a value derived from the indicator). In some aspects, core network 120 sends the 730 synchronization delay indicator to network entity 104 periodically. Alternatively or additionally, core network 120 sends the 730 synchronization delay indicator to network entity 104 when the synchronization delay meets a synchronization delay threshold criterion. In some aspects, the priority indicator may be associated with MMDS. For example, core network 120 (e.g., AF / SMF / PCF / UPF, etc.) can signal a priority indication to network entity 104 for MMDSs (e.g., via GTP-U headers) with a large synchronization delay (e.g., exceeding a certain threshold) that are to be scheduled by network entity 104 with higher priority. In some aspects, a lagging PDU set can be marked as lagging (e.g., in the GTP-U header from UPF to RAN). New or conventional bit fields can be used to indicate lagging PDUs or PDU sets. Marking can be performed when the synchronization delay meets a synchronization delay threshold criterion.

[0084] During the handover process, information regarding synchronization between QoS flows (e.g., synchronization delay, differential synchronization delay, QoS flow ID, MMDS, MMDS sequence number, etc.) can be transmitted from the source network entity 104 to the destination network entity 104 via the Xn interface. Alternatively, synchronization information can be coordinated via AMF within the core network 120 using information elements in NGAP to signal the synchronization delay to the source network entity 104.

[0085] Core network 120 may optionally send a request 735 to network entity 104 for correction of synchronization delay. In some aspects, network entity 104 interprets the synchronization delay indicator as an implicit request to correct the synchronization delay. In response, the network entity corrects 736 the synchronization delay, as shown in reference... Figure 5 and Figure 6 As described.

[0086] Figure 8 Signaling diagram 800 illustrates communication for synchronizing multimodal data streams between a RAN (e.g., network entity) 104, acting as a data source entity, and a core network 120, acting as a data destination entity, according to an embodiment. Network entity 104 sends an 805 MMDS identifier to core network 120. In some aspects, network entity 104 is as described in reference... Figure 5 The description involves receiving an MMDS identifier from UE 102 and forwarding the MMDS identifier to core network 120.

[0087] Core network 120 sends an 810 synchronization delay report period indicator and / or measurement period indicator to network entity 104. The measurement period indicator indicates how often network entity 104 measures the synchronization delay. The synchronization delay report period indicator indicates how often network entity 104 sends the synchronization delay to core network 120. Synchronization delay reporting can be activated / deactivated by core network 120.

[0088] Network entity 104 sends a first PDU set (e.g., a first single-mode PDU set) 815 to core network 120. Network entity 104 sends a second PDU set (e.g., a second single-mode PDU set) 820 to core network 120.

[0089] Network entity 104 measures the synchronization delay between the first PDU set and the second PDU set, similar to the reference. Figure 3B , Figure 4 and Figure 5 The method described.

[0090] Network entity 104 sends an 830 synchronization delay indicator to core network 120. In some aspects, network entity 104 periodically sends the 830 synchronization delay indicator to core network 120. Alternatively or additionally, network entity 104 sends the 830 synchronization delay indicator to core network 120 when the synchronization delay meets a synchronization delay threshold criterion.

[0091] Network entity 104 may optionally send a request for correction of synchronization delay to core network 120. In some aspects, core network 120 interprets the synchronization delay indicator as an implicit request to correct the synchronization delay. In response, core network 120 corrects the synchronization delay.

[0092] Alternatively or concurrently, when the synchronization delay meets a synchronization delay threshold criterion, network entity 104 corrects the synchronization delay. For example, network entity 104 increases the priority / PBR of the 845-latency PDU set and / or moves the latency PDU set to a higher priority LCH, as per reference. Figure 6 As described, network entity 104 sends an 850 LCH parameter adjustment confirmation to core network 120 after adjusting the LCH parameters. The LCH parameter adjustment confirmation indicates to core network 120 that the LCH parameters have been adjusted.

[0093] In some aspects, network entity 104 corrects synchronization delays by merging QoS flows 855 onto the same DRB, as referenced. Figure 6As described. Network entity 104 may optionally send 856 sets of third and fourth PDUs merged into the same QoS stream.

[0094] In some aspects, network entity 104 concatenates PDCP SDUs from multiple QoS flows of the same multimodal service into the same PDCP PDU, as shown in reference 860. Figure 6 As described. Network entity 104 may optionally send 870 a fifth PDU set concatenated with the sixth PDU set. The PDCP header indicates that the SDUs are concatenated.

[0095] Figure 9 This is a flowchart of a method 900 according to an embodiment for detecting synchronization delay in a multimodal data stream by a data source entity and requesting correction of the synchronization delay at the data destination entity when the synchronization delay meets a threshold criterion. Method 900 relates to... Figures 5 to 8 .

[0096] The data source entity sends a 905 MMDS identifier to the data destination entity, as shown in the reference. Figure 5 , Figure 7 and Figure 8 The 505, 705 and 805 described in the document.

[0097] The data source entity may optionally receive a 910 synchronization delay report period indicator and / or a measurement period indicator from the data destination entity, as shown in the reference. Figure 5 and Figure 8 The 510 and 810 described in the text.

[0098] The data source entity sends the first PDU set (e.g., the first unimodal PDU set) to the data destination entity, as shown in the reference. Figures 5 to 8 The values ​​described in 515, 615, 715, and 815.

[0099] The data source entity sends the second PDU set (920) to the data destination entity, as shown in the reference. Figures 5 to 8 The values ​​520, 620, 720, and 820 described in the text.

[0100] The data source entity measures the synchronization delay between the first PDU set and the second PDU set, as shown in reference 925. Figures 5 to 8 The values ​​525, 625, 725, and 825 described in the text.

[0101] The data source entity determines whether the 926 synchronization delay meets the threshold criteria (e.g., exceeds the synchronization delay threshold), as per reference. Figures 5 to 8As described. If the data source entity determines 926 No, the synchronization delay does not meet the threshold criterion, then the data source sends an additional PDU set. If the data source entity determines 926 Yes, the synchronization delay does meet the threshold criterion, then the data source entity sends a 930 synchronization delay indicator to the data destination entity, as described in the reference. Figure 5 , Figure 7 and Figure 8 As described in 530, 730, and 830. The data source entity may optionally send a 935 request to the data destination entity for correction of synchronization delay, as referred to... Figure 5 , Figure 7 and Figure 8 The terms 535, 735, and 835 are described in the text.

[0102] Figure 10 This is a flowchart of a method 1000 according to an embodiment of a data source entity detecting synchronization delay in a multimodal data stream and periodically reporting the synchronization delay to a data destination entity. Method 1000 relates to... Figures 5 to 8 .

[0103] The data source entity sends a 1005 MMDS identifier to the data destination entity, as shown in the reference. Figure 5 , Figure 7 and Figure 8 The 505, 705 and 805 described in the document.

[0104] The data source entity may optionally receive a 1010 synchronization delay report period indicator and / or a measurement period indicator from the data destination entity, as shown in the reference. Figure 5 and Figure 8 The 510 and 810 described in the text.

[0105] The data source entity sends the first PDU set of 1015 to the data destination entity, as shown in the reference. Figures 5 to 8 The values ​​described in 515, 615, 715, and 815.

[0106] The data source entity sends the second PDU set of 1020 to the data destination entity, as shown in the reference. Figures 5 to 8 The values ​​520, 620, 720, and 820 described in the text.

[0107] The data source entity measures the synchronization delay between the first PDU set and the second PDU set (refer to...). Figures 5 to 8 The values ​​525, 625, 725, and 825 described in the text.

[0108] The data source entity periodically sends a 1030 synchronization delay indicator to the data destination entity, as shown in the reference. Figure 5 , Figure 7 and Figure 8As described in 530, 730, and 830. The data source entity periodically sends a 1030 synchronization delay indicator to the data destination entity based on the synchronization delay report period indicator received at 1010.

[0109] The data source entity may optionally send a 1035 request to the data destination entity for correction of synchronization delay, as shown in the reference. Figure 5 , Figure 7 and Figure 8 The terms 535, 735, and 835 are described in the text.

[0110] Figure 11 This is a flowchart of a method 1100 for detecting synchronization delay in a multimodal data stream and correcting the synchronization delay by increasing the priority or bit rate of the multimodal data stream, according to an embodiment. Method 1100 relates to... Figures 5 to 8 And based on Figure 9 The description in the text is constructed.

[0111] The data source entity sends an 1105 MMDS identifier to the data destination entity, as shown in the reference. Figure 5 , Figure 7 , Figure 8 and Figure 9 The numbers 505, 705, 805, and 905 describe this.

[0112] The data source entity may optionally receive a synchronization delay report period indicator and / or a measurement period indicator from the data destination entity, as shown in the reference. Figure 5 , Figure 8 and Figure 9 The numbers 510, 810, and 910 in the text describe this.

[0113] The data source entity sends the first PDU set (1115) to the data destination entity, as shown in the reference. Figures 5 to 9 The values ​​515, 615, 715, 815, and 915 described in the text.

[0114] The data source entity sends the second PDU set of 1120 to the data destination entity, as shown in the reference. Figures 5 to 9 The values ​​520, 620, 720, 820, and 920 described in the text.

[0115] The data source entity measures the synchronization delay between the first PDU set and the second PDU set, as shown in reference 1125. Figures 5 to 9 The values ​​525, 625, 725, 825, and 925 described in the text.

[0116] this Figure 11 and Figure 9 The difference lies in that the data source entity determines whether the 1126 synchronization delay consistently meets a threshold criterion (e.g., exceeding the synchronization delay threshold over a period of time), as referenced. Figure 5 , Figure 6 and Figure 7 As described. If the data source entity determines 1126 No, the synchronization delay does not consistently meet the threshold criterion, then the data source sends an additional PDU set. If the data source entity determines 1126 Yes, the synchronization delay consistently meets the threshold criterion over a time period, then the data source entity increases the priority or bit rate of the QoS stream associated with the first or second PDU set by 1145, as described in the reference. Figure 5 , Figure 6 and Figure 8 The values ​​described in 545, 645, and 845.

[0117] After adjusting the LCH parameters, the data source entity sends an 1150 LCH parameter adjustment acknowledgment to the data sink entity. The LCH parameter adjustment acknowledgment indicates an adjustment to the priority or bit rate of the QoS stream associated with the first or second PDU set.

[0118] Figure 12 This is a flowchart of a method 1200 for detecting synchronization delay in a multimodal data stream and correcting the synchronization delay by merging or concatenating the multimodal data streams, according to an embodiment. Method 1200 relates to... Figures 5 to 8 And based on Figure 9 The description in the text is constructed. Steps 1205, 1210, 1215, 1220, and 1225 correspond to... Figure 9 Steps 905, 910, 915, 920, and 925.

[0119] this Figure 12 and Figure 9 The difference lies in that the data source entity determines whether the 1226 synchronization delay consistently meets a threshold criterion (e.g., exceeding the synchronization delay threshold over a time period), as referenced. Figure 5 , Figure 6 and Figure 7 As described. If the data source entity determines 1226 is not true, and the synchronization delay does not consistently meet the threshold criterion, the data source sends an additional PDU set. If the data source entity determines 1226 is true, and the synchronization delay consistently meets the threshold criterion over a time period, the data source entity merges the QoS stream associated with 1255 and the first and second PDU sets, as described in the reference. Figure 5 , Figure 6 and Figure 8 As described in 555, 655, and 855. Alternatively or alternatively, the data source entity concatenates the SDUs of the QoS stream associated with the first PDU set and the second PDU set, as referenced. Figure 5 , Figure 6 and Figure 8 The 560, 660 and 860 described.

[0120] Figure 13 This is a flowchart of a method 1300, according to an embodiment, for a data source entity to detect synchronization delays in a multimodal data stream and discard or reallocate resources to the delayed PDU set. Method 1300 relates to... Figures 5 to 8 And based on Figure 9 The description in the text is constructed. Steps 1305, 1310, 1315, 1320, and 1325 correspond to... Figure 9 Steps 905, 910, 915, 920, and 925.

[0121] this Figure 13 and Figure 9 The difference lies in that the data source entity determines whether the 1326 synchronization delay meets a threshold criterion (e.g., exceeds a synchronization delay threshold), as shown in the reference. Figure 5 , Figure 6 and Figure 7 As described. If the data source entity determines 1226 No, the synchronization delay does not meet the threshold criterion, then the data source sends an additional PDU set. If the data source entity determines 1326 Yes, the synchronization delay does meet the threshold criterion, then the data source entity discards 1345 the lagging PDU set or reallocates resources to the lagging PDU set, as described in the reference. Figure 5 As described.

[0122] Figure 14 An example Delay Status Report (DSR) 1400 with multimodal synchronization information according to an embodiment is shown. UE 102 sends DSR 1400 to network entity 104 to indicate delay information LCH or each Logical Channel Group (LCG). The LCG is indicated by LCG ID 1471. In the example, UE 102 sends DSR 1400 to indicate delay information for an LCH transmit buffer, which includes first and second data units of QoS flows requiring synchronization. The first data unit includes at least one of a first PDU, a first PDU set, or a first data burst. The second data unit includes at least one of a second PDU, a second PDU set, or a second data burst. In another example, UE 102 sends DSR 1400 to indicate delay information for an LCG. DSR 1400 may further include a buffer size 1478 to indicate the data capacity in the logical channel buffer along with the data priority. Network entity 104 uses information included in DSR 1400 to perform “delay-aware” uplink scheduling of data in the logical channel buffer (e.g., based on the urgency and / or priority of the data).

[0123] UE 102 calculates the remaining time 1474 before the PDCP drop timers 305 and 307 expire for data units in the logical channel transmit buffer. For example, UE 102 indicates to network entity 104 via DSR 1400 that the expiration time (e.g., drop time) of the PDCP drop timers is the remaining delay time before data units in the logical channel buffer should be dropped. DSR 1400 can indicate to network entity 104 the remaining delay time and the capacity information of the PDU set in the logical channel buffer using buffer size 1478. In scenarios where each QoS flow of a multimodal service is mapped to a different LCG, network entity 104 can use the reported DSR 1400 to obtain an estimate of the synchronization delay 319.

[0124] DSR 1400 includes additional information 1471, 1472 to enable network entity 104 to identify the mapping of different QoS flows to different LCGs and to know the associated PDU / PDU set sequence number 1476 (e.g., network entity 104 should know the synchronization delay and the PDU set associated with the synchronization delay).

[0125] In some respects, network entity 104 determines the synchronization delay 319 for the first PDU set and the second PDU set based on DSR 1400 and the following equation (1):

[0126] by Figure 4 For example, BD1 is the buffer delay (t2c-t1c) before the transmission of the first PDU set. BD1 can be calculated as PDCPdiscardTimer - DSR1, where DSR1 is the delay status report for the first PDU set. BD2 is the buffer delay (t7c-t5c) for the second PDU set. BD2 can be calculated as PDCPdiscardTimer – DSR2, where DSR2 is the delay status report for the second PDU set. T1 is the transmission time of the first PDU set (t3c-t2c). T2 is the transmission time of the second PDU set (t8c-t7c). Toffset is the arrival offset 318 or transmission offset 319 between the first and second PDU sets.

[0127] Equation (1) can be generalized to QoS service flows, as shown in the following equation (2):

[0128] Where DSRflow1 is the DSR of stream 1, DSRflow2 is the DSR of stream 2, Tflow1 is the (average) transmission time of stream 1, Tflow2 is the (average) transmission time of stream 2, and Toffset is the time offset between stream 1 and stream 2.

[0129] In some respects, network entity 104 calculates equation (2) based on the following assumptions: (a) DSR 1400 is available at network entity 104 for each packet of flow 1 and flow 2; (b) network entity 104 can distinguish between DSR 1400 for flow 1 and DSR 1400 for flow 2; (c) network entity 104 knows, based on multimodal public ID 1475, that a particular DSR 1400 for flow 1 and a particular DSR 1400 for flow 2 are associated with the same multimodal service; (d) network entity 104 is aware of the association between the first PDU set and the second PDU set that will be experienced simultaneously by the user; and (e) the offset between service flows is known to network entity 104.

[0130] In some aspects, DSR 1400 indicates QoS flow ID 1472, PDU set sequence number 1476 (e.g., the start of data) or range of PDU / PDU set sequence number (e.g., the start and length of data or the start and end of data), multimodal common ID 1475, MMDS sequence number 1477 (a mapping between data of QoS flow 1 and associated data of QoS flow 2 (e.g., multimodal IDs for each group across multiple flows provided by the application)), reserved bits 1473, and delay status 1474.

[0131] Figure 15 An example synchronization S-DSR 1500 with multimodal synchronization information according to an embodiment is shown. For Figure 14 Alternatively, if network entity 104 cannot obtain the synchronization delay from DSR 1400, S-DSR 1500 may be used by network entity 104 to obtain the synchronization delay. UE 102 sends S-DSR 1500 to network entity 104 via MAC-CE, RRC signaling (e.g., UE assistance information), or another communication mechanism.

[0132] The S-DSR 1500 indicates delay information for multiple QoS flows. For example, the S-DSR 1500 indicates: (a) the multimodal common ID 1575 (the mapping between data of QoS flow 1 and associated data of QoS flow 2); (b) QoS flow ID 1 1581; (c) QoS flow ID 2 1583; (d) the delay associated with QoS flow 1 1584; (e) the delay associated with QoS flow 2 1585; (f) the PDU / PDU set sequence number associated with flow 1 1588; (g) the PDU / PDU set sequence number associated with flow 2 1589; (h) the MMDS sequence number 1577; and reserved bits 1582.

[0133] In some aspects, UE 102 sends an S-DSR 1500 to network entity 104, whereby the S-DSR 1500 indicates the delay and / or differential delay for multiple QoS flows (e.g., two, three, or more QoS flows). In one example, three QoS flows belong to the same multimodal service. QoS flow 1 is considered the reference QoS flow. UE 102 signals the delay for QoS flow 1 in the S-DSR 1500. UE 102 signals the differential delay for each of QoS flows 2 and QoS flows 3 in the S-DSR 1500, obtaining the incremental delay with reference to QoS flow 1.

[0134] Figure 16 This is a flowchart 1600 of a wireless communication method at a first wireless communication device according to an embodiment. (Refer to...) Figures 1 to 15 This method can be performed by UE 102, network entity 104, or core network 120. In an embodiment, the first wireless communication device sends a 1605 multimodal service identifier to the second wireless communication device. For example, refer to... Figure 5 , Figure 7 and Figures 8 to 13 The first wireless communication device sends 505, 705, 805, 905, 1005, 1105, 1205 and 1305 multimodal service identifiers to the second wireless communication device.

[0135] The first wireless communication device may optionally receive a 1610 synchronization delay report periodicity / measurement indicator from the second wireless communication device. For example, refer to Figure 5 and Figures 8 to 13 The first wireless communication device may optionally receive 510, 810, 910, 1010, 1110, 1210, 1310 synchronization delay report periodic / measurement indicators from the second wireless communication device.

[0136] The first wireless communication device sends a first single-mode PDU set of 1615 to the second wireless communication device. For example, refer to Figures 5 to 13The first wireless communication device sends a first single-mode PDU set of 515, 615, 715, 815, 915, 1015, 1115, 1215, and 1315 to the second wireless communication device.

[0137] The first wireless communication device sends a second single-mode PDU set of 1620 to the second wireless communication device. For example, refer to Figures 5 to 13 The first wireless communication device sends a second single-mode PDU set of 520, 620, 720, 820, 920, 1020, 1120, 1220, and 1320 to the second wireless communication device.

[0138] The first wireless communication device sends a first indicator 1630, associated with the synchronization delay of the first single-mode PDU set and the second single-mode PDU set, to the second wireless communication device. For example, refer to Figure 5 , Figure 7 , Figure 8 and Figure 10 The first wireless communication device sends 530, 730, 830, and 1030 first indicators of the synchronization delay associated with the first single-mode PDU set and the second single-mode PDU set to the second wireless communication device.

[0139] The first wireless communication device may optionally send a request for correction of the synchronization delay to the second wireless communication device. For example, refer to... Figure 5 , Figure 7 , Figure 8 , Figure 9 and Figure 10 The first wireless communication device may optionally send a 535, 635, 835, 935, or 1035 request for correction of synchronization delay to the second wireless communication device.

[0140] Figure 17 This is a flowchart 1700 of a method for wireless communication at a second wireless communication device according to an embodiment. (Refer to...) Figures 1 to 15 This method can be performed by UE 102, network entity 104, or core network 120. In an embodiment, the second wireless communication device receives a 1705 multimodal service identifier from the first wireless communication device. For example, refer to... Figure 5 , Figure 7 and Figures 8 to 13 The second wireless communication device receives 505, 705, 805, 905, 1005, 1105, 1205 and 1305 multimodal service identifiers from the first wireless communication device.

[0141] The second wireless communication device may optionally send a 1710 synchronization delay report periodic / measurement indicator to the first wireless communication device. For example, refer to Figure 5 and Figures 8 to 13The second wireless communication device may optionally send 510, 810, 910, 1010, 1110, 1210, and 1310 synchronization delay report periodic / measurement indicators to the first wireless communication device.

[0142] The second wireless communication device receives a first single-mode PDU set (1715) from the first wireless communication device. For example, refer to... Figures 5 to 13 The second wireless communication device receives a first single-mode PDU set of 515, 615, 715, 815, 915, 1015, 1115, 1215, and 1315 from the first wireless communication device.

[0143] The second wireless communication device receives a second single-mode PDU set (1720) from the first wireless communication device. For example, refer to... Figures 5 to 13 The second wireless communication device receives a second single-mode PDU set of 520, 620, 720, 820, 920, 1020, 1120, 1220, and 1320 from the first wireless communication device.

[0144] The second wireless communication device receives from the first wireless communication device a first indicator 1730 of the synchronization delay associated with the first single-mode PDU set and the second single-mode PDU set. For example, refer to Figure 5 , Figure 7 , Figure 8 and Figure 10 The second wireless communication device receives from the first wireless communication device a first indicator of the synchronization delay associated with the first single-mode PDU set and the second single-mode PDU set, which is 530, 730, 830, and 1030.

[0145] The second wireless communication device may optionally receive a request from the first wireless communication device 1735 for correction of the synchronization delay. For example, refer to Figure 5 , Figure 7 , Figure 8 , Figure 9 and Figure 10 The second wireless communication device may optionally receive requests from the first wireless communication device for correction of synchronization delay via 535, 735, 835, 935, and 1035.

[0146] Figure 18Figure 1800 illustrates an example of a hardware implementation of UE device 1802. UE device 1802 may be UE 102, a component of UE 102, or may implement UE functionality. UE device 1802 may include an application processor 1806, which may have on-chip memory 1806'. In the example, application processor 1806 may be coupled to a secure digital (SD) card 1808 and / or a display 1810. Application processor 1806 may also be coupled to a sensor module 1812, a power supply 1814, an additional memory module 1816, a camera 1818, and / or other related components.

[0147] The UE equipment 1802 may further include a wireless baseband processor 1826, which may be referred to as a modem. The wireless baseband processor 1826 may have on-chip memory 1826'. Together with and similarly to the application processor 1806, the wireless baseband processor 1826 may also be coupled to a sensor module 1812, a power supply 1814, an additional memory module 1816, a camera 1818, and / or other related components. The wireless baseband processor 1826 may additionally be coupled to one or more Subscriber Identity Module (SIM) cards 1820 and / or one or more transceivers 1830 (e.g., wireless RF transceivers).

[0148] Within one or more transceivers 1830, the UE equipment 1802 may include a Bluetooth module 1832, a WLAN module 1834, an SPS module 1836 (e.g., a GNSS module), and / or a cellular module 1838. The Bluetooth module 1832, WLAN module 1834, SPS module 1836, and cellular module 1838 may each include an on-chip transceiver (TRX), or in some cases, only a transmitter (TX) or only a receiver (RX). The Bluetooth module 1832, WLAN module 1834, SPS module 1836, and cellular module 1838 may each include a dedicated antenna and / or utilize antenna 1840 to communicate with one or more other nodes. For example, UE equipment 1802 can communicate with another UE (e.g., sidelink communication) and / or with network entity 104 (e.g., uplink / downlink communication) via transceiver 1830 and antenna 1840, wherein network entity 104 may correspond to a base station or a unit of a base station (such as RU 106, DU 108 or CU 110).

[0149] The wireless baseband processor 1826 and application processor 1806 may each include computer-readable media / memory 1826' and 1806', respectively. An additional memory module 1816 may also be considered a computer-readable media / memory. Each computer-readable media / memory 1826', 1806', and 1816 may be non-transitory. The wireless baseband processor 1826 and application processor 1806 may each be responsible for general processing, including executing software stored on the computer-readable media / memory 1826', 1806', and 1816. This software, when executed by the wireless baseband processor 1826 / application processor 1806, causes the wireless baseband processor 1826 / application processor 1806 to perform the various functions described herein. The computer-readable media / memory may also be used to store data manipulated by the wireless baseband processor 1826 / application processor 1806 during software execution. The wireless baseband processor 1826 / application processor 1806 may be a component of UE 102. UE equipment 1802 may be a processor chip (e.g., a modem and / or application) and includes only the wireless baseband processor 1826 and / or the application processor 1806. In other examples, UE equipment 1802 may be the entire UE 102 and may include additional modules for equipment 1802.

[0150] As in Figure 1 The discussion in the article and about Figure 16 The implemented MMDS component 140 of the first wireless communication device is configured to transmit a first single-mode PDU set of a first data stream to the second wireless communication device. The MMDS component 140 is further configured to transmit a second single-mode PDU set of a second data stream, different from the first data stream, to the second wireless communication device. The MMDS component 140 is further configured to transmit a first indicator of the synchronization delay associated with the first and second single-mode PDU sets to the second wireless communication device. The MMDS component 140 may reside within application processor 1806 (e.g., at 140a), within wireless baseband processor 1826 (e.g., at 140b), or within both application processor 1806 and wireless baseband processor 1826. MMDS components 140a-140b may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or a combination thereof.

[0151] Figure 19Figure 1900 illustrates an example of a hardware implementation of one or more network entities 104. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functionality. The one or more network entities 104 may include or correspond to at least one of RU 106, DU 108, or CU 110. CU 110 may include a CU processor 1946, which may have on-chip memory 1946'. In some aspects, CU 110 may further include an additional memory module 1956 and / or a communication interface 1948, both of which may be coupled to the CU processor 1946. CU 110 may communicate with DU 108 via a midhaul link 162—such as an F1 interface between the communication interface 1948 of CU 110 and the communication interface 1928 of DU 108.

[0152] DU 108 may include a DU processor 1926, which may have on-chip memory 1926'. In some aspects, DU 108 may further include an additional memory module 1936 and / or a communication interface 1928, both of which may be coupled to the DU processor 1926. DU 108 may communicate with RU 106 via a frontlink 160 between DU 108's communication interface 1928 and RU 106's communication interface 1908.

[0153] RU 106 may include an RU processor 1906, which may have on-chip memory 1906'. In some aspects, RU 106 may further include an additional memory module 1916, a communication interface 1908, and one or more transceivers 1930, all of which may be coupled to the RU processor 1906. RU 106 may further include an antenna 1940, which may be coupled to one or more transceivers 1930, such that RU 106 can communicate with UE 102 via the antenna 1940 through one or more transceivers 1930.

[0154] On-chip memories 1906', 1926', 1946' and additional memory modules 1916, 1936, 1956 can each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1906, 1926, 1946 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor 1906, 1926, 1946, the software causes the processor 1906, 1926, 1946 to perform the various functions described herein. The computer-readable medium / memory can also be used to store data manipulated by the processors 1906, 1926, 1946 during software execution. In the example, the synchronization delay component 150 may be located at any of one or more network entities 104, such as at CU 110; at both CU 110 and DU 108; at each of CU 110, DU 108 and RU 106; at DU 108; at both DU 108 and RU 106; or at RU 106.

[0155] As in Figure 1 The discussion in the article and about Figure 17 The synchronization delay component 150 of the second wireless communication device is configured to receive a first single-mode PDU set from the first wireless communication device of a first data stream. The synchronization delay component 150 is further configured to receive a second single-mode PDU set from the first wireless communication device of a second data stream different from the first data stream. The synchronization delay component 150 is further configured to receive a first indicator of the synchronization delay associated with the first and second single-mode PDU sets from the first wireless communication device. The synchronization delay component 150 may reside within one or more processors of one or more network entities 104, such as within an RU processor 1906 (e.g., at 150a), a DU processor 1926 (e.g., at 150b), and / or a CU processor 1946 (e.g., at 150c). Synchronization delay components 150a-150c may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors 1906, 1926, 1946 configured to perform the stated process / algorithm, and stored in a computer-readable medium for implementation by one or more processors 1906, 1926, 1946, or a combination thereof.

[0156] The specific order or hierarchy of the boxes in the processes and flowcharts disclosed herein is illustrative of the exemplary methods. Therefore, the specific order or hierarchy of the boxes in the processes and flowcharts can be rearranged. Some boxes may also be merged or deleted. Dashed lines may indicate optional elements of the diagrams. The appended method claims present the elements of each box in the exemplary order, and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.

[0157] The detailed descriptions presented herein, in conjunction with accompanying drawings, depict various configurations, but do not represent the only configurations in which the concepts described herein can be practiced. These detailed descriptions include specific details used to provide a comprehensive explanation of the various concepts. However, these concepts can be practiced without using these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0158] Various apparatuses and methods are presented with reference to aspects of wireless communication systems (such as telecommunications systems). These apparatuses and methods are described in the following detailed description and are shown in the accompanying drawings by various boxes, components, circuits, processes, call flows, systems, algorithms, etc. (collectively, "elements"). These elements can be implemented using electronic hardware, computer software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system.

[0159] An element, or any part of an element, or any combination of elements, can be implemented as a “processing system” including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other similar hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system can execute software, which may be referred to as software, firmware, middleware, microcode, hardware description languages, or others. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0160] If the functionality described herein is implemented in software, then such functionality may be stored on or encoded as one or more instructions or code on a computer-readable medium, such as a non-transitory computer-readable storage medium. Computer-readable media include computer storage media and may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible by a computer. The storage medium can be any available medium accessible to a computer.

[0161] The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, form factors, sizes, and package arrangements. For example, aspects, implementations, and / or use cases can be generated via integrated chip implementations and other devices based on non-modular components, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / procurement devices, medical devices, devices supporting artificial intelligence (AI), devices supporting machine learning (ML), etc. The scope of aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein.

[0162] Apparatus incorporating the aspects and features described herein may also include additional components and features for implementing and practicing the claimed and described aspects and features. For example, the transmission and reception of wireless signals necessarily include numerous components for analog and digital purposes, such as hardware components, antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc. The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user devices, etc., in various configurations.

[0163] The description herein is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein, but should be interpreted in light of the full scope of this disclosure consistent with the language of the claims.

[0164] Unless explicitly stated otherwise, references to singular elements do not imply "one and only one," but rather "one or more." Terms such as "if," "when," and "at" do not imply an immediate temporal relationship or response. That is, phrases such as "when" do not imply an immediate action in response to or during the occurrence of an action, but simply that an action will occur if the condition is met, without requiring a specific or immediate temporal constraint on the occurrence of the action. The terms "may," "may," and "can" as used herein generally carry certain connotations. For example, "may" refers to a permissible feature that may or may not occur, "may" refers to a feature that is very likely to occur, and "can" refers to a capability (e.g., being able to). The phrase "for example" generally carries a similar connotation to "may," and therefore, "may" is sometimes excluded from sentences that include "for example" or other similar phrases.

[0165] Unless otherwise expressly stated, the term "some" means one or more. Combinations such as "at least one of A, B, or C" or "one or more of A, B, or C" include any combination of A, B, and / or C, such as A and B, A and C, B and C, or A and B and C, and may include multiple A, multiple B, and / or multiple C, or may include only A, only B, or only C. A set should be interpreted as a set of elements having one or more elements. Furthermore, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, the phrase "X takes A or B" is intended to mean either of the natural inclusive permutations. That is, the phrase "X takes A or B" is satisfied by any of the following instances: X takes A; X takes B; or X takes both A and B. Terms or articles such as “a,” “an,” and / or “the” can refer to one or more of the items, features, elements, etc., following the term or article. For example, the expression “a small component” does not exclude references to multiples of the component, because “multiple small components” necessarily includes “a small component.” Therefore, the expression “a small component” can be interpreted as “at least one small component,” or similarly, as “one or more small components.”

[0166] Unless otherwise explicitly indicated, ordinal terms such as “first” and “second” do not necessarily imply order in time, sequence, numerical value, etc., but are used to distinguish different instances of the term or phrase following each ordinal term. As used in the specification and figures, reference numerals are sometimes cross-referenced between figures to indicate the same or similar features. Features that are identical in multiple figures may be labeled with the same reference numerals in multiple figures. Features that are similar but not identical in multiple figures may be labeled with reference numerals that have different leading numerals but share one or more of the same trailing numerals (e.g., 206, 306, 406, etc. may refer to similar features in the figures). Sometimes, “X” is used generally to indicate multiple variations of a feature. For example, “X06” may generally refer to all reference numerals ending in “06” (e.g., 206, 306, 406, etc.).

[0167] Structural and functional equivalents of the various aspects of the elements described throughout this disclosure, known or subsequently learned by those skilled in the art, are expressly incorporated herein by reference and are covered by the claims. The terms “module,” “mechanism,” “element,” “device,” etc., may not be substitutes for the term “component.” Therefore, no claim element shall be construed as means plus function unless the phrase “component for…” is explicitly stated herein. As used herein, the phrase “based on” should not be construed as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, unless expressly stated otherwise, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) shall be construed as “at least based on A.”

[0168] The following examples are illustrative only and can be combined with other examples or teachings described herein without limitation.

[0169] Example 1 is a method of wireless communication performed by a first wireless communication device, the method comprising: transmitting a first single-mode data unit of a first data stream to a second wireless communication device; transmitting a second single-mode data unit of a second data stream different from the first data stream to the second wireless communication device; and transmitting a first indicator of the synchronization delay between the first single-mode data unit and the second single-mode data unit to the second wireless communication device.

[0170] Example 2 can be combined with the method of Example 1, and further includes: measuring the synchronization delay based on the time period from the end of transmission of the first single-mode data unit to the end of transmission of the second single-mode data unit.

[0171] Example 3 can be combined with the method of any of Examples 1 to 2, wherein the first indicator includes at least one of the following: a first time period value indicating the synchronization delay; a second time period value indicating the amount of time by which the synchronization delay exceeds the synchronization delay threshold; or a code point indicating that the synchronization delay exceeds the synchronization delay threshold.

[0172] Example 4 can be combined with the method of Example 3, wherein the synchronization delay threshold is based on the maximum tolerable time interval between the start of the first stimulus associated with the first monomodal data unit and the start of the second stimulus associated with the second monomodal data unit.

[0173] Example 5 may be combined with the method of any of Examples 1 to 4, and further includes at least one of the following: sending a signal to a second wireless communication device to correct the synchronization delay.

[0174] Example 6 can be combined with the method of any of Examples 1 to 5, and further includes: receiving a second indicator of reporting periodicity from a second wireless communication device, wherein sending the first indicator includes periodically sending the first indicator based on the reporting periodicity.

[0175] Example 7 can be combined with the method of any of Examples 1 to 6, wherein sending the first indicator includes sending the first indicator when the synchronization delay exceeds a synchronization delay threshold for the synchronization delay measurement period.

[0176] Example 8 can be combined with the method of any of Examples 1 to 7, and further includes: merging a first Quality of Service (QoS) stream associated with a first single-mode data unit and a second QoS stream associated with a second single-mode data unit onto the same data radio bearer (DRB) based on the synchronization delay exceeding a synchronization delay threshold.

[0177] Example 9 can be combined with the method of any of Examples 1 to 8, and further includes: concatenating a first Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) associated with a first single-modal data unit and a second PDCP SDU associated with a second single-modal data unit based on the synchronization delay exceeding a synchronization delay threshold.

[0178] Example 10 can be combined with the method of any of Examples 1 to 9, and further includes: sending a multimodal service identifier to a second wireless communication device, the multimodal service identifier indicating that the first single-mode data unit and the second single-mode data unit are associated with the same multimodal application.

[0179] Example 11 can be combined with the method of any of Examples 1 to 10, and further includes: receiving from the second wireless communication device a fourth indicator for measuring the synchronization delay between the first single-mode data unit and the second single-mode data unit.

[0180] Example 12 can be combined with the method of any of Examples 1 to 11, wherein the synchronization delay between the first unimodal data unit and the second unimodal data unit includes the difference between a first delay associated with a first QoS flow of the first unimodal data unit and a second delay associated with a second QoS flow of the second unimodal data unit.

[0181] Example 13 may be combined with the method of any of Examples 1 to 12, and further includes: increasing at least one of the priority or bit rate associated with the third single-mode data unit based on the synchronization delay exceeding a synchronization delay threshold; and sending a fifth indicator to the second wireless communication device indicating the increase in priority or bit rate.

[0182] Example 14 may be combined with the method of any of Examples 1 to 13, and further includes: receiving from the second wireless communication device a sixth indicator for increasing at least one of the priority or bit rate associated with the fourth single-mode data unit; and increasing the priority or bit rate associated with the fourth single-mode data unit.

[0183] Example 15 can be combined with the method of any of Examples 1 to 14, and further includes: discarding the fifth single-mode data unit based on the synchronization delay exceeding a synchronization delay threshold or based on the importance PSI of the protocol data unit (PDU) set of the fifth single-mode data unit satisfying a PSI threshold.

[0184] Example 16 can be combined with the method of any of Examples 1 to 15, wherein the first indicator includes a Delay Status Report (DSR) that includes at least one of the following: a Logical Channel Group (LCG) identifier; a Quality of Service (QoS) flow identifier for a first single-mode data unit (SMU); a QoS flow identifier for a second SMU; a delay associated with the QoS of the first SMU; a delay associated with the QoS of the second SMU; a sequence number for the first SMU; a sequence number for the first SMU; a Multimodal Data Set (MMDS) sequence number; or an MMDS common identifier identifying the first SMU and the second SMU.

[0185] Example 17 can be combined with the method of any of Examples 1 to 16, wherein sending the first indicator includes sending the first indicator via at least one of: Radio Resource Control (RRC) signaling; or Media Access Control-Control Unit (MAC-CE) message.

[0186] Example 18 can be combined with the method of any of Examples 1 to 17, wherein: the first single-modal data unit includes at least one of a first PDU, a first PDU set, or a first data burst; and the second single-modal data unit includes at least one of a second PDU, a second PDU set, or a second data burst.

[0187] Example 19 can be combined with the method of any of Examples 1 to 18, wherein the first monomodal data unit and the second monomodal data unit include at least one of the following: video data; audio data; haptic data; game control data; or posture data.

[0188] Example 20 is a method of wireless communication performed by a second wireless communication device, the method comprising: receiving a first single-mode data unit of a first data stream from a first wireless communication device; receiving a second single-mode data unit of a second data stream different from the first data stream from the first wireless communication device; and receiving a first indicator of a synchronization delay between the first single-mode data unit and the second single-mode data unit from the first wireless communication device.

[0189] Example 21 can be combined with the method of Example 20, wherein the first indicator includes at least one of the following: a first time period value indicating the synchronization delay; a second time period value indicating the amount of time by which the synchronization delay exceeds the synchronization delay threshold; or a code point indicating that the synchronization delay exceeds the synchronization delay threshold.

[0190] Example 22 can be combined with the method of Example 21, wherein the synchronization delay threshold is based on the maximum tolerable time interval between the start of the first stimulus associated with the first monomodal data unit and the start of the second stimulus associated with the second monomodal data unit.

[0191] Example 23 may be combined with the method of any of Examples 20 to 22, and further includes at least one of the following: receiving a signal from a first wireless communication device to correct the synchronization delay; or sending a signal to a network entity to correct the synchronization delay.

[0192] Example 24 may be combined with the method of any of Examples 20 to 23, and further includes: sending a second indicator of reporting periodicity to a first wireless communication device, wherein receiving the first indicator includes periodically receiving the first indicator based on the reporting periodicity.

[0193] Example 25 can be combined with the method of any of Examples 20 to 24, wherein receiving the first indicator includes receiving the first indicator when the synchronization delay exceeds a synchronization delay threshold for the synchronization delay measurement period.

[0194] Example 26 may be combined with the method of any of Examples 20 to 25, and further includes: receiving a multimodal service identifier from a first wireless communication device, the multimodal service identifier indicating that the first unimodal data unit and the second unimodal data unit are associated with the same multimodal application.

[0195] Example 27 may be combined with the method of any of Examples 20 to 26, and further includes: sending a fourth indicator to the first wireless communication device for measuring the synchronization delay associated with the first single-mode data unit and the second single-mode data unit.

[0196] Example 28 can be combined with the method of any of Examples 20 to 27, wherein the synchronization delay associated with the first unimodal data unit and the second unimodal data unit includes the difference between a first delay associated with a first QoS flow of the first unimodal data unit and a second delay associated with a second QoS flow of the second unimodal data unit.

[0197] Example 29 may be combined with the method of any of Examples 20 to 28, and further includes: receiving from the first wireless communication device an increased fifth indicator of at least one of priority or bit rate associated with the third single-mode data unit.

[0198] Example 30 may be combined with the method of any of Examples 20 to 29, and further includes: sending a sixth indicator to the first wireless communication device to increase at least one of the priority or bit rate associated with the fourth single-mode data unit.

[0199] Example 31 can be combined with the method of any of Examples 20 to 30, wherein the first indicator includes a Delay Status Report (DSR) that includes at least one of the following: a Logical Channel Group (LCG) identifier; a Quality of Service (QoS) flow identifier for a first single-mode data unit (SMU); a QoS flow identifier for a second SMU; a delay associated with the QoS of the first SMU; a delay associated with the QoS of the second SMU; a sequence number for the first SMU; a sequence number for the first SMU; a Multimodal Data Set (MMDS) sequence number; or an MMDS common identifier identifying the first SMU and the second SMU.

[0200] Example 32 can be combined with the method of any of Examples 20 to 31, wherein receiving the first indicator includes receiving the first indicator via at least one of: Radio Resource Control (RRC) signaling; or Media Access Control-Control Unit (MAC-CE) message.

[0201] Example 33 can be combined with the method of any of Examples 20 to 32, wherein: the first single-modal data unit includes at least one of a first protocol data unit (PDU), a first PDU set, or a first data burst; and the second single-modal data unit includes at least one of a second PDU, a second PDU set, or a second data burst.

[0202] Example 34 can be combined with the method of any of Examples 20 to 33, wherein the first monomodal data unit and the second monomodal data unit include at least one of the following: video data; audio data; haptic data; game control data; or posture data.

[0203] Example 35 is an apparatus for wireless communication, including a memory, a transceiver, and a processor coupled to the memory and the transceiver, the apparatus being configured to implement a method as described in any of Examples 1 through 34.

Claims

1. A method for wireless communication performed by a first wireless communication device, the method comprising: The first single-mode data unit that transmits (515) the first data stream to the second wireless communication device; Send (520) a second single-mode data unit of a second data stream that is different from the first data stream to the second wireless communication device; as well as Send (530) a first indicator of the synchronization delay between the first single-mode data unit and the second single-mode data unit to the second wireless communication device.

2. The method of claim 1, further comprising: The synchronization delay (525) is measured based on the time interval from the end of transmission of the first single-mode data unit to the end of transmission of the second single-mode data unit.

3. The method as described in any one of claims 1 to 2, wherein, The first indicator includes at least one of the following: Indicates the first time period value of the synchronization delay; A second time period value indicating the amount of time by which the synchronization delay exceeds the synchronization delay threshold; or The code point indicating that the synchronization delay exceeds the synchronization delay threshold.

4. The method of claim 3, wherein, The synchronization delay threshold is based on the maximum tolerable time interval between the start of a first stimulus associated with the first monomodal data unit and the start of a second stimulus associated with the second monomodal data unit.

5. The method of any one of claims 1 to 4, further comprising at least one of the following: A signal (535) is sent to the second wireless communication device to correct the synchronization delay.

6. The method of any one of claims 1 to 5, further comprising: Receive (510) a second indicator of reporting periodicity from the second wireless communication device, wherein sending (530) the first indicator includes sending (530) the first indicator periodically based on the reporting periodicity.

7. The method as described in any one of claims 1 to 6, wherein, Sending (530) the first indicator includes sending (530) the first indicator when the synchronization delay exceeds the synchronization delay threshold for the synchronization delay measurement period.

8. The method of any one of claims 1 to 7, further comprising: Based on the synchronization delay exceeding the synchronization delay threshold, the first QoS stream associated with the first single-mode data unit and the second QoS stream associated with the second single-mode data unit are merged (555) onto the same data radio bearer (DRB).

9. The method of any one of claims 1 to 8, further comprising: Based on the fact that the synchronization delay exceeds the synchronization delay threshold, the first Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) associated with the first single-modal data unit and the second PDCPSDU associated with the second single-modal data unit are concatenated (560).

10. The method of any one of claims 1 to 9, further comprising: Send a (505) multimodal service identifier to the second wireless communication device, the multimodal service identifier indicating that the first unimodal data unit and the second unimodal data unit are associated with the same multimodal application.

11. The method as claimed in any one of claims 1 to 10, wherein, The first wireless communication device is a user equipment (UE), and the second wireless communication device is a network entity.

12. The method according to any one of claims 1 to 10, wherein, The first wireless communication device is a core network entity, and the second wireless communication device is a radio access network (RAN) entity.

13. The method of any one of claims 1 to 12, further comprising: Receive (510) a fourth indicator from the second wireless communication device for measuring the synchronization delay between the first single-mode data unit and the second single-mode data unit.

14. The method of any one of claims 1 to 13, further comprising: Based on the synchronization delay exceeding the synchronization delay threshold, increase (545) at least one of the priority or bit rate associated with the third single-mode data unit; as well as Send (550) a fifth indicator to the second wireless communication device, indicating an increase in the priority or the bit rate.

15. The method of any one of claims 1 to 14, further comprising: The fifth single-modal data unit is discarded if the synchronization delay exceeds the synchronization delay threshold or if the importance PSI of the PDU set of the fifth single-modal data unit meets the PSI threshold.

16. A method for wireless communication performed by a second wireless communication device, the method comprising: The first single-mode data unit receives (515) the first data stream from the first wireless communication device; Receive (520) a second single-mode data unit from the first wireless communication device, which is a second data stream different from the first data stream; as well as (530) Receives a first indicator of the synchronization delay between the first single-mode data unit and the second single-mode data unit from the first wireless communication device.

17. The method of claim 16, further comprising: (505) A multimodal service identifier is received from the first wireless communication device, the multimodal service identifier indicating that the first unimodal data unit and the second unimodal data unit are associated with the same multimodal application.

18. An apparatus for wireless communication, comprising a memory, a transceiver, and a processor coupled to the memory and the transceiver, the apparatus being configured to implement the method as claimed in any one of claims 1 to 17.

Images