Logical channel prioritization for synchronization

Abstract

Various aspects of the present disclosure generally relate to wireless communications. Some aspects generally relate to logical channel prioritization for synchronization. Some aspects are more particularly directed to a user equipment (UE) performing logical channel prioritization based on synchronization information. In some aspects, the synchronization information may include a synchronization threshold between two or more logical channels. For example, two or more logical channels may be associated with traffic of a multi-modal service or application. A network node may configure two or more logical channels with corresponding synchronization thresholds based on a multi-modal service or application.

Description

Cross-reference to related applications

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 469,138, filed September 18, 2023, entitled “LOGICAL CHANNEL PRIORITIZATION FOR SYNCHRONIZATION”, assigned to the assignee of this patent application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Technical Field

[0002] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques, apparatus and methods for logical channel priority ordering for synchronization. Background Technology

[0003] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). Examples of such multiple access RATs include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution.

[0005] In some examples, a User Equipment (UE) may schedule or allocate data to available uplink resources via Logical Channel (LCH) priority ordering. As used herein, "Logical Channel" or "LCH" can refer to a channel between the Radio Link Control (RLC) layer and the Media Access Control (MAC) layer that facilitates downlink communication from the network node to the UE and uplink communication from the UE to the network node. An LCH may reside in the control plane and carry control information, or it may reside in the user plane and carry data. For example, a network node may send configuration information including an LCH configuration comprising one or more LCHs. The LCH configuration may indicate the priority of the LCH associated with the LCH configuration (e.g., LCH priority). Priorities may be integer values ​​(e.g., where lower integer values ​​indicate higher priorities).

[0006] A UE may select one or more LCHs to transmit services to network nodes. For example, a UE may select services associated with one or more LCHs to populate available resources for uplink transmission (e.g., populate MAC Protocol Data Units (PDUs)). A UE may select one or more LCHs based on, in response to, or otherwise associated with the priority of the corresponding LCHs associated with the available uplink services to be transmitted. For example, packets for a higher-priority LCH may be scheduled before packets from a lower-priority LCH. In some examples, scheduling packets solely based on LCH priority may result in missed transmission deadlines and / or a lack of synchronization between different packets. For example, some applications may generate multiple types of uplink data streams. Different streams may have different timing deadlines and / or may be associated with synchronization. For example, different data streams of the same application may have different packet delay budgets and / or different data streams may be associated with packets to be synchronized. Scheduling different data streams solely based on LCH priority may result in missed transmission deadlines and / or a lack of synchronization between different packets of different data streams. Summary of the Invention

[0007] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include a processing system comprising one or more processors and one or more memories coupled to the processors. The processing system may be configured to cause the UE to receive configuration information for a set of logical channels, the configuration information indicating a set of synchronization thresholds associated with the set of logical channels. The processing system may be configured to transmit the first data via a first logical channel from the set of logical channels, such that a delay between the UE and the second data of a first and a second logical channel satisfies a synchronization threshold in the set of synchronization thresholds.

[0008] Some aspects described herein relate to a network node for wireless communication. The network node may include a processing system comprising one or more processors and one or more memories coupled to the processors. The processing system may be configured to cause the network node to transmit configuration information for a set of logical channels, the configuration information indicating a set of synchronization thresholds associated with the set of logical channels. The processing system may be configured to receive first data via a first logical channel from the set of logical channels, such that a delay between the network node and second data from a first and a second logical channel satisfies a synchronization threshold in the set of synchronization thresholds.

[0009] Some aspects described herein relate to a method for wireless communication by a UE. The method may include: receiving configuration information for a set of logical channels, the configuration information indicating a set of synchronization thresholds associated with the set of logical channels respectively. The method may include: transmitting the first data via a first logical channel from the set of logical channels, in association with a delay between the first data and the second data of the second logical channel satisfying a synchronization threshold in the set of synchronization thresholds.

[0010] Some aspects described herein relate to a method for wireless communication by a network node. The method may include: transmitting configuration information for a set of logical channels, the configuration information indicating a set of synchronization thresholds associated with the set of logical channels respectively. The method may also include: receiving first data via a first logical channel from the set of logical channels, in association with a delay between first data and second data on a second logical channel satisfying a synchronization threshold in the set of synchronization thresholds.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to receive configuration information for a set of logical channels, the configuration information indicating a set of synchronization thresholds associated with the set of logical channels. When executed by one or more processors of the UE, the set of instructions enables the UE to transmit the first data via a first logical channel from the set of logical channels, in association with a delay between the first data and the second data of the second logical channel satisfying a synchronization threshold in the set of synchronization thresholds.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions enables the network node to transmit configuration information for a set of logical channels, the configuration information indicating a set of synchronization thresholds associated with each set of logical channels. When executed by one or more processors of the network node, the set of instructions enables the network node to receive first data via a first logical channel from the set of logical channels, in association with a delay between first data and second data on a second logical channel satisfying a synchronization threshold in the set of synchronization thresholds.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving configuration information of a set of logical channels, the configuration information indicating a set of synchronization thresholds associated with the set of logical channels. The apparatus may include components for transmitting the first data via a first logical channel from the set of logical channels, in association with a delay between the first data and the second data of the second logical channel satisfying a synchronization threshold in the set of synchronization thresholds.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for transmitting configuration information for a set of logical channels, the configuration information indicating a set of synchronization thresholds associated with the set of logical channels. The apparatus may include components for receiving the first data via a first logical channel from the set of logical channels, in association with a delay between the first data and the second data of the second logical channel satisfying a synchronization threshold in the set of synchronization thresholds.

[0015] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0016] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and their associated advantages will be described below. The disclosed aspects can serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and their associated advantages will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0017] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

[0018] Figure 1 This is a diagram illustrating an example of a wireless communication network according to the present disclosure.

[0019] Figure 2 This is a diagram illustrating communication between an example network node and an example user equipment (UE) in a wireless network according to the present disclosure.

[0020] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0021] Figure 4 This is a diagram illustrating an example of logical channel priority ordering according to this disclosure.

[0022] Figure 5 This is a diagram illustrating an example of a multimodal service as described in this disclosure.

[0023] Figure 6 This is a diagram illustrating an example operation associated with logical channel priority ordering for synchronization, in accordance with this disclosure.

[0024] Figure 7 This is a flowchart illustrating an example process, for example at a UE or a device of a UE, that supports logical channel priority ordering for synchronization, performed according to this disclosure.

[0025] Figure 8 This is a flowchart illustrating an example process, for example at a network node or a device of a network node, that supports logical channel priority ordering for synchronization, according to the present disclosure.

[0026] Figure 9 This is a diagram of an example device for wireless communication that supports logical channel priority ordering for synchronization according to this disclosure.

[0027] Figure 10 This is a diagram of an example device for wireless communication that supports logical channel priority ordering for synchronization according to this disclosure. Detailed Implementation

[0028] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a method of practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods of practice using those other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0029] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various boxes, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0030] In some examples, an application service can be a multimodal service. A multimodal service can be associated with a multimodal business. As used herein, "multimodal business" can refer to a business associated with multiple modes of an application. For example, some applications can generate multiple types of uplink data streams (e.g., multiple modes). For example, an application (e.g., an extended reality (XR) application or a virtual reality (VR) application) can generate audio data, video data, location data, haptic data, and / or other types of data, each associated with the application. For example, an application can implement input from more than one source (such as business streams for audio, video, location, and / or haptics, etc.).

[0031] For example, an application service may be associated with a user equipment (UE) in a first mode (or a first service data stream) and a UE in a second mode (or a second service data stream). These UEs may be the same UE or different UEs. As an example, a UE associated with the first mode may include a head-mounted device, such as a VR headset or VR goggles (e.g., associated with audio and / or video data). A UE associated with the second mode may include wearable components, such as gloves, associated with obtaining tactile data as input.

[0032] Multimodal services can consist of multiple data streams (e.g., collectively referred to as multimodal streams) that are related to each other and may originate from different sources. Each data stream (individually referred to as monomodal data) can be considered as one type of data (e.g., audio, video, location, haptic, and / or another type of data) associated with the same communication service. Multimodal streams may carry closely related data and may require strong coordination to deliver multimodal application data correctly. For example, synchronization between different data streams of the same multimodal application (e.g., between different media components of an XR application) can be important to ensure a positive user experience. For example, if the data streams of different media components of the same multimodal application are not synchronized, the user may be able to detect the lack of synchronization, resulting in a poor user experience. Therefore, in some cases, two or more data streams (e.g., associated with different modalities or media components) may be associated with a synchronization threshold. As used herein, a “synchronization threshold” can refer to the amount of time allowed between the transmission of services associated with two or more data streams (e.g., associated with different modalities or media components) to ensure that a lack of synchronization is not detected.

[0033] For example, by handling multiple media components associated with a multimodal service or application separately, synchronization between different media components can reduce the likelihood of negative impacts on user experience (e.g., the user detecting a lack of synchronization). However, different data streams may have different timing cutoff times. For example, different data streams for the same application may have different packet delay budgets. Therefore, different data streams for the same application may be associated with different logical channels (LCHs) (e.g., associated with different priorities). For example, different data streams may be associated with different LCHs due to the different timing cutoff times of data streams associated with different media components or modes of the same application. Because the UE may transmit data based on, in response to, or otherwise associated with LCH priority ordering that only considers the timing cutoff times of the data streams (e.g., only considering packet delay budgets or remaining delay budgets), this may result in delays between data transmissions for different modes that do not meet the synchronization thresholds for different modes. For example, when scheduling or selecting services to be included in available uplink resources, the UE may only consider LCH priorities, packet delay budgets, and / or remaining delay budgets. Therefore, delays between data transmissions for different modes that do not meet the synchronization thresholds for different modes may exist. Delays can cause users to perceive a significant lack of synchronization, thereby reducing the user experience of multimodal services or applications.

[0034] Various aspects typically involve logical channel prioritization for synchronization. Some aspects are more specifically about the UE performing logical channel prioritization based on, in response to, or otherwise associated with synchronization information. In some aspects, synchronization information may include synchronization thresholds between two or more LCHs. For example, two or more LCHs may be associated with services or applications used for multimodal services. Network nodes may configure two or more LCHs using appropriate synchronization thresholds based on, in response to, or otherwise associated with multimodal services or applications.

[0035] In some respects, the UE may perform logical channel prioritization based on a synchronization threshold, a delay threshold for the residual delay budget (RDB), and LCH priority. For example, the UE may schedule packets to be included in available uplink resources. The UE may determine whether the packet is associated with a related packet or a related LCH. The UE may schedule related packets (e.g., from related LCHs) to scheduled packets based on, in response to, or otherwise associated with synchronization information between the packet and related packets (e.g., based on, in response to, or otherwise associated with a synchronization threshold). For example, the UE may schedule related packets (e.g., before scheduling one or more packets from higher priority LCHs) based on, in response to, or otherwise associated with a delay between the related packet and the packet satisfying a synchronization threshold (e.g., a synchronization threshold associated with the packet's LCH and / or related LCH).

[0036] In some respects, a related LCH can be an LCH associated with the same multimodal service or application. For example, if a packet has an RDB that meets a latency threshold, the UE can first schedule the packet using the LCH configured with the latency threshold. If the latency between the packet and any related packet meets a synchronization threshold, the UE can schedule the related packet to that packet. In some respects, the UE can identify a related LCH based on, in response to, or otherwise associated with a multimodal service identifier. The multimodal service identifier can be indicated via a Quality of Service (QoS) stream or via a PDU header. Additionally or alternatively, the UE can receive configuration information indicating one or more related LCHs.

[0037] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to increase the likelihood that relevant packets associated with a multimodal service or application (e.g., in the time domain) are synchronized when performing logical channel prioritization. By synchronizing packets associated with a multimodal service or application, the likelihood of latency between packets that a user can detect can be reduced. This can improve the user experience associated with a multimodal service or application.

[0038] Additionally, by performing logical channel priority ordering using delay information (e.g., one or more delay thresholds) and synchronization information (e.g., one or more synchronization thresholds), the UE can ensure that it does not miss packet transmission deadlines and that the scheduled packets to be synchronized are transmitted closely together. For example, the UE can schedule one or more packets (e.g., from a lower priority LCH) to be transmitted near related packets from the same multimodal service or application before another packet from a higher priority LCH. Furthermore, by indicating related LCHs via multimodal service identifiers indicated by QoS flow or PDU headers, the UE can identify related or relevant packets without explicit indication from network nodes, thereby reducing the complexity associated with identifying related LCHs and saving network resources that would otherwise be used to transmit communications indicating related LCHs.

[0039] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0040] As the demand for broadband access increases and as the technologies supported by wireless communication networks evolve, further technological improvements can be adopted or implemented in 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. Such technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, UE functionality with reduced capabilities (RedCap), industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. These technological improvements can support use cases such as wireless backhaul, wireless data centers, XR and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative maneuvering, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, among others. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0041] Figure 1 This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0042] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, carriers, and / or channels according to frequency or wavelength. For example, devices of wireless communication network 100 can communicate using one or more operating frequency bands. In some aspects, multiple wireless networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific RAT (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RATs, 5G / NRRATs, and / or 6G RATs, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0043] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the Very High Frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are often referred to as the mid-band frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0044] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may be referred to as an NR network node, 5G network node, 6G network node, node B, eNB, gNB, access point (AP), transmit / receive point (TRP), mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in a radio access network (RAN).

[0045] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete radio protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete radio protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses the complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0046] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same or different geographical locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as networks conforming to the O-RAN Alliance), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple units that can be deployed independently.

[0047] Network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as functional splits defined by 3GPP). In some examples, DUs may also host one or more lower PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0048] In some aspects, network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0049] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). A network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may move depending on the location of the associated mobile network node 110 (e.g., a train, satellite base station, drone, or NTN network node).

[0050] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0051] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0052] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). UEs 120 may be configured using both uplink and downlink BWPs (where the uplink and downlink BWPs may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0053] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchored network node communicating with a core network. Anchored network node 110 may also be referred to as an IAB donor (or "IAB donor"). Anchored network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of anchored network node 110 may terminate at the core network. Additionally or alternatively, anchored network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). IAB networks typically also include multiple non-anchored network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchored network node 110 can directly communicate with the anchored network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchored network node 110 via one or more other non-anchored network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchored network nodes 110 or other non-anchored network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. For example, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

[0054] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In such examples, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0055] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an XR device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0056] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A group of processors that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire group of processors that are configured or configured to perform the set of functions.

[0057] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0058] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, evolved or enhanced Machine Type Communication (eMTC) UEs (Further Enhanced eMTC (feMTC) UEs, or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be referred to simply as "MTC UEs"). MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles or drones, remote devices, sensors, meters, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0059] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. UEs 120 in the first category facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices capable of URLLC, enhanced mobile broadband (eMBB), and / or precise positioning within the wireless communication network 100, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs. UEs 120 in the third category may have intermediate-level complexity and / or capabilities (e.g., capabilities between first-category UEs 120 and second-capability UEs 120). UEs 120 in the third category may be referred to as reduced-capability UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR simplified UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0060] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communicating through a network node 110 acting as an intermediary). As an example, UE 120a can send data, control information, or other signaling directly to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can use peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols to send and receive sidelink communication. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0061] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0062] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO techniques typically utilize multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some RATs can employ advanced MIMO techniques such as mTRP operations (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0063] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive configuration information for a set of logical channels, the configuration information indicating a set of synchronization thresholds associated with the set of logical channels; and, in connection with a delay between first data and second data on a second logical channel satisfying a synchronization threshold in the set of synchronization thresholds, transmit the first data via a first logical channel from the set of logical channels. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0064] In some aspects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may send configuration information for a set of logical channels, indicating a set of synchronization thresholds associated with the set of logical channels; and receive the first data via a first logical channel from the set of logical channels, in connection with a delay between the first data and the second data on the second logical channel satisfying a synchronization threshold in the set of synchronization thresholds. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

[0065] Figure 2 This is a diagram illustrating communication between an example network node 110 and an example UE 120 in a wireless network according to the present disclosure.

[0066] like Figure 2 As shown, network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0067] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as referring to a combination of... Figure 2 Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0068] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The processors in the first set and the processors in the second set can be the same set of processors or can be different sets of processors. The reference to "one or more memories" should be understood to mean any one or more memories of the corresponding device, such as combined... Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0069] For downlink communication from network node 110 to UE 120, transmitting processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmitting processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) based on the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmitting processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0070] The TX MIMO processor 216 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can provide a set of output symbol streams (e.g., T output symbol streams) to a set of modems 232. For example, each output symbol stream can be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 can use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for Orthogonal Frequency Division Multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 can further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t can transmit a set of downlink signals (e.g., T downlink signals) together via a set of corresponding antennas 234.

[0071] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or on another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0072] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0073] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use to transmit and / or receive communication using RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0074] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0075] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to perform network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0076] UE 120 may include a collection of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a collection of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by a processor (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0077] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110 and can provide a set of received downlink signals (e.g., R received signals) to a set of modems 254. For example, each received signal can be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use the corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain an input sample. Each modem 254 can use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from the set of modems 254, can perform MIMO detection on the received symbols where applicable, and can provide the detected symbols. The receiver processor 258 can process (e.g., decode) the detected symbols, provide the decoded data for the UE 120 to the data sink 260 (which may include a data pipeline, a data queue and / or an application executed on the UE 120), and provide the decoded control information and system information to the controller / processor 280.

[0078] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of the RSRP parameter, RSSI parameter, RSRQ parameter, CQI parameter, TPC parameter, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0079] Transmitter 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmitter 264 can be pre-decoded (where applicable) by TX MIMO processor 266 and further processed by an assembly of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols (where applicable) and can provide an assembly of output symbol streams (e.g., U output symbol streams) to the assembly of modems 254. For example, each output symbol stream can be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 can use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use a corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0080] Modems 254a to 254u can transmit sets of uplink signals (e.g., R uplink signals or U uplink symbols) via corresponding sets of antennas 252. Uplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals can be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals can carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) typically uses techniques similar to those described for uplink data and control transmission and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0081] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0082] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element, which can be used to independently transmit cross-polarized signals. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0083] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0084] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0085] Figure 3 This is an illustration of an example decomposed base station architecture 300 according to the present disclosure. One or more components of the example decomposed base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The decomposed base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more decomposed control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360 (e.g., via an E2 link)). The CU 310 may communicate with one or more DU 330s via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340s via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120s via a corresponding RF access link. In some deployments, a UE 120 may be served simultaneously by multiple RU 340s.

[0086] Each component of the disassembled base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or may be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0087] In some respects, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0088] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0089] The non-RT RIC 350 may include or implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logic functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0090] In some aspects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and can be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns in performance and may employ AI / ML models to perform corrective actions via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0091] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies or perform one or more operations associated with logical channel priority ordering for synchronization, as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies or perform one or more operations associated with logical channel priority ordering for synchronization, as described in more detail elsewhere herein. Figure 2 Any other component, CU 310, DU 330, or RU 340 may execute or instruct, for example Figure 7 The process 700 Figure 8The operation of process 800 or other processes as described herein (alone or in combination with one or more other processors). Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing instruction sets (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the instruction set may be made to be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 7 The process 700 Figure 8 The process 800 or other processes as described herein (alone or in combination with one or more other processors). In some examples, the execution instructions may include run instructions, translation instructions, compilation instructions, and / or interpretation instructions, etc.

[0092] In some aspects, UE 120 includes components for receiving configuration information of a set of logical channels, the configuration information indicating a set of synchronization thresholds associated with the set of logical channels respectively; and / or components for transmitting the first data via a first logical channel from the set of logical channels in association with a delay between the first data and the second data of the second logical channel satisfying a synchronization threshold in the set of synchronization thresholds. Components for enabling UE 120 to perform the operations described herein may include, for example, one or more of a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0093] In some aspects, network node 110 includes components for transmitting configuration information for a set of logical channels, the configuration information indicating a set of synchronization thresholds associated with the set of logical channels respectively; and / or components for receiving first data via a first logical channel from the set of logical channels in association with a delay between first data and second data on a second logical channel satisfying a synchronization threshold in the set of synchronization thresholds. Components for enabling network node 110 to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0094] Figure 4 This is a diagram illustrating an example associated with logical channel priority ordering 400 according to this disclosure. For example... Figure 4 As shown, one or more network nodes 110 and UE 120 can (e.g., on a wireless network, such as in...) Figure 1 Network nodes 110 communicate with each other on a wireless network 100. Each network node 110 may include an RU and / or a device that controls the RU, such as a DU and / or CU. Each network node 110 may be associated with at least one TRP (e.g., within a cell).

[0095] In the first operation 405, UE 120 may send and network node 110 may receive a capability message indicating that UE 120 is configured for LCH restriction. For example, the capability message may include a UECapabilityInformation message as defined in the 3GPP specification. Therefore, UE 120 may use an lcp-Restriction Information Element (IE) as defined in the 3GPP specification to indicate that UE 120 is configured for LCH restriction. In some aspects, network node 110 may send and UE 120 may receive a request for a capability message (e.g., a UECapabilityEnquiry message, as defined in the 3GPP specification). In response to this request, UE 120 may send and network node 110 may receive the capability message.

[0096] In the second operation 410, network node 110 may determine the Logical Channel Priority Order (LCP) for UE 120. Network node 110 may determine the priority of the corresponding LCH. For example, each LCH may be associated with a certain priority. In some examples, the priority may be an integer value (e.g., from 1 to 16, where 1 is the highest priority and 16 is the lowest priority). In some examples, network node 110 may determine at least one constraint (e.g., LCP constraint) based at least in part on the QoS requirements associated with the LCH used for UE 120. As used herein, "logical channel" or "LCH" may refer to a channel between the RLC layer and the MAC layer that facilitates downlink communication from network node 110 to UE 120 and uplink communication from UE 120 to network node 110. The LCH may reside in the control plane and carry control information, or it may reside in the user plane and carry data.

[0097] In one example, network node 110 may identify latency-sensitive services (e.g., services for XR applications). Therefore, network node 110 may determine limitations on the LCH to which latency-sensitive services are assigned, which routes the latency-sensitive services to physical channels with higher data rates (e.g., lower data loads) (e.g., TRPs routed to network node 110). In another example, network node 110 may identify error-sensitive services (e.g., attitude updates for XR applications). Therefore, network node 110 may determine limitations on the LCH to which error-sensitive services are assigned, which routes the error-sensitive services to TRPs of network node 110 with higher robustness (e.g., higher quality and / or reliability). In yet another example, network node 110 may identify LCHs associated with control information for UE 120. Therefore, network node 110 may determine limitations on the LCH to which control information is assigned, which routes the control information to TRPs of network node 110 with higher robustness (e.g., higher quality and / or reliability).

[0098] In some examples, network node 110 may determine the Priority Bit Rate (PBR) for each LCH. The PBR can be the data rate provided to an LCH before any resources are allocated to a lower-priority LCH. For example, to avoid starvation of some LCHs (e.g., to avoid a scenario where traffic on a given LCH cannot be sent because higher-priority LCHs have traffic filling available resources), the PBR may set a limit for each LCH. For example, when filling available resources, the PBR may indicate the amount of data to be added from each LCH. If any resources remain, they can be filled according to the LCH priority.

[0099] In the third operation 415, network node 110 may send, and UE 120 may receive, a configuration for a set of LCHs that indicates at least one constraint (for the LCHs in the set). For example, in the third operation 415, network node 110 may send configuration information including LCH configurations for one or more LCHs. The LCH configuration may include LogicalChannelConfigRRC parameters (e.g., as defined by 3GPP or otherwise fixed). The LCH configuration may indicate the priority (e.g., LCH priority) and / or PBR (e.g., via prioritizedBitRate IE) of the LCHs associated with the LCH configuration.

[0100] In the fourth operation 420, UE 120 may select one or more LCHs for services to be transmitted to network node 110. For example, different LCHs may be associated with different QoS requirements, as described above. In some examples, UE 120 may select services associated with one or more LCHs to populate available resources for uplink transmission (e.g., populate MAC Protocol Data Units (PDUs)). UE 120 may select one or more LCHs based on, in response to, or otherwise associated with the priority of the respective LCHs associated with the available uplink services to be transmitted.

[0101] For example, such as Figure 4 As shown, the uplink buffer of UE 120 can indicate that LCH 1, LCH 2, and LCH 3 are associated with uplink services available for transmission. LCH 1 can be associated with priority 1 and the first PBR. LCH 2 can be associated with priority 2 (e.g., indicating a lower priority than priority 1) and the second PBR. LCH 3 can be associated with priority 3 (e.g., indicating a lower priority than priority 1 and priority 2) and the third PBR.

[0102] In the fourth operation 420, firstly, UE 120 can select services to be included in the MAC PDU from LCH 1, up to the amount of services indicated by the first PBR. Secondly, UE 120 can select services to be included in the MAC PDU from LCH 2, up to the amount of services indicated by the second PBR. Thirdly, UE 120 can select services to be included in the MAC PDU from LCH 3, up to the amount of services indicated by the third PBR. Figure 4As shown, LCH 3 can be associated with fewer services than those indicated by the third PBR, allowing UE 120 to select all services associated with LCH 3. UE 120 can fill any remaining space in available resources (e.g., in the MAC PDU) according to the priority of the LCH. For example, fourthly, UE 120 can fill the remaining space in available resources (e.g., in the MAC PDU) with services associated with LCH 1 (e.g., because LCH 1 has the highest priority). If any remaining resources exist after adding services associated with LCH 1 to the MAC PDU, UE 120 can fill the remaining space in available resources (e.g., in the MAC PDU) with services associated with LCH 2.

[0103] In the fifth operation 425, UE 120 may use the LCH to transmit uplink communication. For example, UE 120 may transmit uplink communication via available resources (e.g., via MAC PDU). Services included in the uplink communication (e.g., data or control information) may be associated with, in response to, or otherwise related to the selection of services according to LCH priority (e.g., as performed in the fourth operation 420).

[0104] Figure 5 This is a diagram illustrating an example of a multimodal service 500 associated with this disclosure. For example... Figure 5 As shown, one or more UEs 120 can communicate with the application server 505 via RAN 510. RAN 510 can be a wireless network, such as... Figure 1 The wireless network 100. RAN 510 may include one or more network nodes 110, such as one or more RUs, one or more DUs, and / or one or more CUs, etc. Application server 505 may be associated with application services (e.g., may serve or otherwise support application services). As an example, application services may be associated with XR services, VR services, and / or another type of service.

[0105] In some examples, an application service can be a multimodal service. A multimodal service can be associated with a multimodal business. As used herein, "multimodal business" can refer to a business associated with multiple modes of an application. For example, some applications can generate multiple types of uplink data streams (e.g., multiple modes). For example, an application (e.g., an XR application or a VR application) can generate audio data, video data, location data, haptic data, and / or other types of data, each associated with the application. For example, application server 505 can support applications that receive input from more than one source (such as business streams for audio, video, location, haptics, etc.).

[0106] For example, such as Figure 5 As shown, the application service can be associated with UE 120 in the first mode (or first service data flow 515) and UE 120 in the second mode (or second service data flow 520). Figure 5 The UE 120 shown may be the same UE or may be different UEs. As an example, the UE 120 associated with the first mode may include a head-mounted device, such as a VR head-mounted device or VR goggles (e.g., associated with audio data and / or video data). The UE 120 associated with the first mode may include wearable components, such as gloves, associated with obtaining tactile data as input.

[0107] Multimodal services may include multiple data streams that are related to each other and may originate from different sources (e.g., collectively referred to as multimodal streams). Each data stream (individually referred to as monomodal data) may be considered as one type of data associated with the same communication service (e.g., audio, video, location, haptic, and / or another type of data). Data streams including multimodal services may originate from a single UE (via a single device or via multiple devices connected to a single UE) or from multiple UEs. Multimodal streams may be associated with a multimodal service identifier (ID). The multimodal service ID may be an indicator of the application service associated with the multimodal service. The RAN 510's Policy Control Function (PCF) can use the information indicated by the multimodal service ID to derive the correct policy and charging control (PCC) rules and apply QoS policies to data streams that are part of a given multimodal application.

[0108] Multimodal streams can carry closely related data and may require strong coordination to deliver multimodal application data correctly. For example, synchronization between different data streams of the same multimodal application (e.g., between different media components of an XR application) can be important to ensure a positive user experience. For instance, if the data streams of different media components of the same multimodal application are out of sync, the user may be able to detect the lack of synchronization, resulting in a poor user experience. Therefore, in some cases, two or more data streams (e.g., associated with different modalities or media components) may be associated with a synchronization threshold. As used herein, a “synchronization threshold” can refer to the allowable amount of time between the transmission of services associated with two or more data streams (e.g., associated with different modalities or media components) to ensure that a lack of synchronization is not detected. For example, a synchronization threshold can be defined as the allowable (e.g., maximum) tolerable time interval at which two stimuli begin, where one stimulus is presented to one sense and another stimulus is presented to another sense, such that the accompanying sensory objects are perceived as synchronized. A synchronization threshold may also be referred to as a multimodal synchronization threshold.

[0109] For example, by handling multiple media components associated with a multimodal service or application separately, synchronization between different media components can reduce the likelihood of negative impacts on the user experience (e.g., the user detecting a lack of synchronization). Applying synchronization thresholds in RAN 510 can help support immersive multimodal applications when the synchronization threshold between two or more modalities is less than the application's latency key performance indicator (KPI). As an example, the synchronization threshold between audio and haptic data streams may include an allowable audio latency of 50 ms (e.g., indicating that audio data should be delayed by up to 50 ms compared to the corresponding haptic data) and an allowable haptic latency of 25 ms (e.g., indicating that haptic data should be delayed by up to 25 ms compared to the corresponding audio data). As another example, the synchronization threshold between visual and haptic data streams may include an allowable visual latency of 15 ms (e.g., indicating that visual data should be delayed by up to 15 ms compared to the corresponding haptic data) and an allowable haptic latency of 50 ms (e.g., indicating that haptic data should be delayed by up to 50 ms compared to the corresponding visual data). For each data stream or media component, "latency" can refer to the situation where that media component is delayed compared to another media component (for example, visual latency can refer to the delay of a visual data stream compared to a haptic data stream).

[0110] Different data streams can have different timing deadlines. For example, different data streams within the same application can have different packet delay budgets. As an example, an application can generate gesture or control packets containing information with a packet delay budget of 4 ms, and these gesture or control packets can arrive at intervals of 10 ms for transmission (e.g., are generated). Such gesture data can be based on, respond to, or otherwise correlated with user head movement and / or user field of vision, etc. For example, an application can sample head position every 10 ms and generate updates to transmit to another end of the application (such as application server 505). An application can also generate gesture tracking information to track user hand movements, and this gesture tracking information can have a longer packet delay budget of 10 ms and can arrive at intervals of 40 ms for transmission. An application can generate voice or audio for transmission, which can have a longer delay budget of 15 ms and can arrive at intervals of 20 ms for transmission. In this example, the application can generate different traffic streams with different packet delay budgets and different generation periods.

[0111] Therefore, different data streams for the same application can be associated with different LCHs (e.g., associated with different priorities). For example, different data streams can be associated with different LCHs due to different timing deadlines associated with different media components or modalities of the same application. Because the UE can transmit data based on, in response to, or otherwise associated with LCH priority ordering that only considers the timing deadline of the data stream (e.g., only considers the packet delay budget or the remaining delay budget), this can result in delays between data transmissions for different modalities that do not meet the synchronization thresholds for those modalities. For example, when scheduling or selecting services to be included in available uplink resources, the UE may only consider LCH priority, packet delay budget, and / or remaining delay budget. Therefore, delays between data transmissions for different modalities that do not meet the synchronization thresholds for those modalities may exist. These delays can cause users to perceive a significant lack of synchronization, thereby degrading the user experience of the application.

[0112] Figure 6 This is a diagram illustrating an example operation 600 associated with logical channel priority ordering for synchronization according to this disclosure. (See diagram for example.) Figure 6 As shown, one or more network nodes 110 (e.g., base stations, CUs, DUs, and / or RUs) can communicate with UE 120. In some aspects, network node 110 and UE 120 can be part of a wireless network (such as wireless network 100). UE 120 and network node 110 can... Figure 6 The operation shown has been performed after a wireless connection has been established.

[0113] In the first operation 605, UE 120 may send and network node 110 may receive a capability report. The capability report may indicate whether UE 120 supports a certain feature and / or one or more parameters associated with that feature. The capability report may indicate capability information. For example, capability information may indicate capabilities and / or parameters for using synchronization information to perform LCH prioritization. As another example, the capability report may indicate capabilities and / or parameters for performing LCH prioritization using a synchronization threshold associated with a multimodal service or application. One or more operations described herein may be based on, in response to, or otherwise associated with the capability information in the capability report. For example, the UE may perform communication based on the capability information, or may receive configuration information based on the capability information. In some aspects, the capability report may indicate UE support for receiving configuration information for a set of LCHs, which indicates the synchronization threshold of the corresponding LCH in the LCH set. Additionally or alternatively, the capability report may indicate UE support for transmitting uplink communication comprising data selected and / or scheduled via one or more LCHs from the LCH set that are prioritized in association with a synchronization threshold.

[0114] In the second operation 610, network node 110 may determine an LCH priority ordering for synchronization associated with multimodal services or applications. For example, network node 110 may determine that one or more LCHs will be associated with synchronization-based scheduling and / or deadline-based scheduling. For example, "deadline-based" scheduling may refer to scheduling LCHs based on, in response to, or otherwise associated with a latency threshold and RDB (or remaining latency budget) of the service associated with a given LCH. For example, network node 110 may determine the priority level of the respective LCHs among one or more LCHs. Additionally, network node 110 may determine a latency threshold for the respective LCHs among one or more LCHs. Network node 110 may configure each LCH in the LCHs using the latency threshold of the RDB to be applied to the PDU. UE 120 may compare the RDB for each PDU in the LCH buffer with the latency threshold. Each LCH may be configured using an LCH scheduling priority to be used for LCP. UE 120 may schedule data transmissions from different LCHs based on, in response to, or otherwise associated with a priority and based on, in response to, or otherwise associated with a delay threshold.

[0115] For example, if no packets in a subset of time-based LCHs have a residual delay budget exceeding the corresponding delay threshold, a strict priority scheme (e.g., a priority-based scheme not scheduled based on, in response to, or otherwise associated with delay or synchronization) can be used to schedule each LCH (e.g., including time-based LCHs and any priority-based LCHs). For example, UE 120 may populate uplink resources of a TB with packets from one or more LCHs based on, in response to, or otherwise associated with a strict priority process. If at least one packet in a subset of time-based LCHs has a residual delay budget exceeding the corresponding delay threshold, uplink resources in the available TB can be populated according to a process where the LCH with packets exceeding its delay threshold is scheduled first. For example, if at least one PDU has a residual delay budget below a threshold amount, UE 120 may populate uplink resources of a TB based on, in response to, or otherwise associated with the shortest residual delay budget.

[0116] Additionally or alternatively, network node 110 may determine a synchronization threshold for a corresponding LCH among one or more LCHs. For example, network node 110 may determine one or more LCHs to be associated with synchronization-based scheduling. Network node 110 may determine a synchronization threshold for a corresponding LCH. For example, network node 110 may use the corresponding synchronization threshold to configure one or more LCHs. Network node 110 may determine the synchronization threshold based on, in response to, or otherwise associated with a modality or media component associated with a service to be conveyed via the LCH.

[0117] In some aspects, network node 110 may (e.g., based on, in response to, or otherwise associated with a multimodal service or application) determine relationships or correlations between different LCHs. For example, network node 110 may determine that one or more LCHs are associated with a multimodal service ID (e.g., indicating that the one or more LCHs are related and / or associated with each other). As an example, network node 110 may determine that an LCH is associated with different types of services (e.g., different modalities or different media components) used for a multimodal service or application. In some aspects, network node 110 may determine that a given LCH is associated with a synchronization threshold for each associated LCH (e.g., each related or associated LCH). For example, network node 110 may determine that a first LCH is associated with a second and a third LCH (e.g., the first, second, and third LCHs may be associated with different types of services used for the same multimodal service or application). Network node 110 may determine that the first LCH is associated with a first synchronization threshold of the second LCH. Additionally, network node 110 may determine that the first LCH is associated with a second synchronization threshold of the third LCH. As another example, a given synchronization threshold for an LCH can indicate different values ​​for the corresponding associated LCH.

[0118] In the third operation 615, network node 110 can send and UE can receive configuration information. In some aspects, the UE can receive configuration information via one or more of the following: system information (e.g., Master Information Block (MIB) and / or System Information Block (SIB), RRC signaling, one or more MAC-CE and / or DCI, etc.

[0119] In some aspects, the configuration information may indicate one or more candidate configuration and / or communication parameters. In some aspects, one or more candidate configuration and / or communication parameters may be selected, activated, and / or deactivated via subsequent instructions. For example, a subsequent instruction may select a candidate configuration and / or communication parameter from the one or more candidate configuration and / or communication parameters. In some aspects, the subsequent instructions may include dynamic instructions, such as one or more MAC-CE and / or one or more DCI messages, etc.

[0120] In some aspects, the configuration information and / or capability report described in conjunction with the third operation 615 may include information transmitted via multiple communications. Additionally or alternatively, network node 110 may transmit the configuration information or communications including at least a portion of the configuration information before and / or after UE 120 transmits the capability report. For example, network node 110 may transmit a first portion of the configuration information before the capability report, UE 120 may transmit at least a portion of the capability report, and network node 110 may transmit a second portion of the configuration information after receiving the capability report.

[0121] In some aspects, configuration information may instruct UE 120 to perform synchronization-based LCH priority ordering. For example, configuration information may instruct UE 120 to consider synchronization thresholds of one or more LCHs when performing logical channel priority ordering. Configuration information may indicate configuration information for a set of one or more LCHs. For example, configuration information may include the LCH configuration of a corresponding LCH included in a set of one or more LCHs. Configuration information may indicate the synchronization thresholds of a corresponding LCH in a set of one or more LCHs. For example, the LCH configuration of a given LCH may indicate one or more synchronization thresholds associated with the given LCH.

[0122] In some aspects, configuration information may indicate that one or more LCHs are associated with priority-based, synchronization-based, and / or deadline-based scheduling or logical channel priority ordering. For example, configuration information may indicate that LCH priority ordering is a function of the LCH priority, delay threshold, and / or synchronization threshold associated with a given LCH. For example, configuration information may indicate that one or more LCHs are associated with synchronization-based scheduling and deadline-based scheduling. "Synchronization-based" scheduling or LCH priority ordering may refer to scheduling LCHs based on, in response to, or otherwise associated with synchronization thresholds and the transmission timing of associated data (e.g., associated PDUs) transmitted via associated or related LCHs.

[0123] For example, configuration information may indicate the use of one or more synchronization thresholds (e.g., associated or related LCHs) to configure one or more LCHs. For example, an LCH may be associated with one or more synchronization thresholds for a synchronization-based schedule used for the LCH. Additionally, configuration information may indicate the use of delay thresholds of the PDU's RDB to configure one or more LCHs. For example, a delay threshold may be associated with the RDB of a deadline-based schedule for the LCH. Additionally, configuration information may indicate the use of priorities (e.g., integer values ​​indicating LCH priorities) to configure one or more LCHs.

[0124] In some aspects, configuration information may include indications of one or more LCH dependencies. For example, configuration information may include one or more RRC parameters indicating one or more LCH dependencies (e.g., network node 110 can configure LCH dependencies between one or more LCHs via RRC). The one or more LCH dependencies may indicate that two or more LCHs should be synchronized according to at least one of the configured synchronization thresholds. For example, LCH dependencies may indicate that two or more LCHs are associated or related (e.g., for synchronization purposes). As an example, the LCH dependency between a first LCH and a second LCH may indicate that if one or more PDUs are sent for the first LCH, the associated one or more PDUs should be sent via the second LCH within the time amount indicated by the synchronization threshold of the first or second LCH.

[0125] UE 120 can configure itself at least in part based on configuration information. In some respects, UE 120 can be configured to perform one or more of the operations described herein, at least in part based on configuration information.

[0126] In the fourth operation 620, UE 120 may determine the data to be included in uplink communications based on, in response to, or otherwise associated with synchronization information. For example, UE 120 may schedule data from the uplink buffer based on, in response to, or otherwise associated with LCH priority ordering (e.g., data may be allocated to available uplink shared channel resources based on, in response to, or otherwise associated with LCH priority ordering). LCH priority ordering may include time-based scheduling and / or synchronization-based scheduling. For example, UE 120 may prioritize one or more LCHs in association with a synchronization threshold associated with the LCH.

[0127] For example, as described elsewhere herein, UE 120 may be configured using a first or more LCHs associated with a corresponding synchronization threshold. UE 120 may be configured using a second or more LCHs associated with a corresponding delay threshold. UE 120 may be associated with a third or more LCHs associated with a corresponding LCH priority. The first or more LCHs, the second or more LCHs, and the third or more LCHs may be the same or more LCHs, may include one or more common LCHs, or may be different LCHs. The LCH priority ordering performed by UE 120 for scheduling data to be included in uplink communication may be a function of the synchronization threshold, RDB (and / or delay threshold), and LCH priority.

[0128] When selecting data (e.g., packets or PDUs) to be included in available uplink resources, UE 120 may determine whether the corresponding data (e.g., the corresponding packets or PDUs) should be scheduled based on a synchronization threshold. For example, UE 120 may determine that two or more packets (or PDUs) should be synchronized. In some aspects, UE 120 may determine to synchronize two or more packets based on, in response to, or otherwise associated with a QoS flow associated with two or more packets (e.g., two or more PDUs or a set of two or more PDUs). For example, the packets included in the data are associated with a reflected QoS flow that indicates an identifier of a multimodal service. The QoS flow may indicate one or more associated LCHs in a set of LCHs associated with one or more packets. In other words, the multimodal service ID may be indicated via reflected QoS. “Reflected QoS” may refer to the QoS applied to uplink packets implicitly derived from one or more downlink packets. For example, when UE 120 receives a downlink packet that includes a reflected QoS indicator and a QoS flow identifier (QFI), UE 120 can apply the same QoS associated with the downlink packet to an uplink packet that has one or more attributes matching the downlink packet. If UE 120 indicates support for reflected QoS during PDU session establishment, the multimodal service ID can also be applied to UL QoS flows (e.g., to uplink packets that match one or more attributes of the downlink packet including the multimodal service ID). Therefore, UE 120 can (e.g., via the multimodal service ID indicated by the reflected QoS) obtain an indication of the existence of certain QoS flows that are multimodally mapped to the relevant LCH. For example, each packet can be identified via a QoS flow ID and a sequence number. Because the PDCP header of the packet may not be obfuscated or encrypted, the MAC component of UE 120 can access the PDCP sequence number to identify the QoS flow (and multimodal service ID) associated with each packet.

[0129] As another example, UE 120 may determine to synchronize two or more packets (e.g., two or more PDUs or a set of two or more PDUs) based on, in response to, or otherwise associated with an application-layer indication. For example, data included in the uplink buffer may include one or more PDUs, each PDU including an indication in its respective header indicating that the one or more PDUs should be synchronized according to at least one of the synchronization thresholds. For example, the one or more PDUs to be synchronized may be associated with different LCHs (e.g., associated LCHs). For example, the application layer may indicate in the PDU header an indication regarding coupled QoS flows (e.g., similar to a public service ID), such that at the MAC layer, the QoS flows and / or LCHs are identified as multimodal flows to be synchronized.

[0130] As another example, UE 120 may determine to synchronize two or more packets (e.g., two or more PDUs or sets of PDUs) based on, in response to, or otherwise associated with an uplink indicator. For example, one or more LCH correlations may be indicated via an uplink indicator (e.g., where one or more LCH correlations indicate that two or more LCHs are to be synchronized according to at least one of the synchronization thresholds). Therefore, UE 120 may identify two or more LCHs to be synchronized. UE 120 may determine that the two or more packets are included in the associated LCH. Therefore, UE 120 may determine that two or more packets (e.g., two or more PDUs or sets of PDUs) are to be synchronized. As another example, UE 120 may determine to synchronize two or more packets (e.g., two or more PDUs or sets of PDUs) based on, in response to, or otherwise associated with configured LCH correlations. For example, configuration information (e.g., one or more RRC parameters) may configure one or more LCH correlations (e.g., for multimodal service synchronization). UE 120 may (e.g., based on, in response to, or otherwise associated with configuration information) determine that two or more packets are included in the relevant LCH. Therefore, UE 120 may determine that two or more packets (e.g., two or more PDUs or two or more sets of PDUs) need to be synchronized.

[0131] In some respects, if no packets in one or more deadline-based LCHs (e.g., LCHs configured using a delay threshold) have RDBs that do not meet (e.g., exceed) the corresponding delay threshold, each LCH in the LCHs (e.g., including deadline-based LCHs, synchronization-based LCHs, and any priority-based LCHs) can be scheduled using strict priority schemes (e.g., priority-based schemes that are not based on, in response to, or otherwise associated with delay) and synchronization-based scheduling.

[0132] For example, UE 120 may follow the combination as follows Figure 4Similar operations are described to populate available uplink resources (e.g., uplink shared channel resources). Additionally, when selecting data (e.g., packets or PDUs) to be included in available uplink resources, UE 120 may determine whether the corresponding data (e.g., the corresponding packet or PDU) should be scheduled based on a synchronization threshold. For example, the first packet may be scheduled based on, in response to, or otherwise associated with an LCH priority associated with the LCH associated with the first packet. UE 120 may determine that the first packet needs to be synchronized with one or more other packets. For example, UE 120 may determine that the first LCH is associated with one or more related LCHs. The synchronization threshold associated with the first LCH may be associated with packets including the first packet that are associated with the first LCH and one or more related LCHs.

[0133] For example, a first packet may be delivered at a first time T1. T1 may be the time when the first packet is delivered to the modem of UE 120 and / or the time when the first packet is delivered to the PDCP component of UE 120. A second packet may be delivered at a second time T2 (e.g., included in an LCH associated with the first LCH). T2 may be the time when the second packet is delivered to the modem of UE 120 and / or the time when the second packet is delivered to the PDCP component of UE 120. UE 120 may compare the difference between T1 and T2 with a synchronization threshold associated with the first LCH to determine whether to schedule the second packet before another packet in a higher priority LCH. For example, if the difference between T1 and T2 does not meet the synchronization threshold, UE 120 may schedule the second packet based on, in response to, or otherwise associated with a strict LCH priority (e.g., in combination with...). Figure 4 (Similar to the described method) to schedule another packet. If the difference between T1 and T2 meets the synchronization threshold, the UE 120 may schedule the second packet (e.g., before scheduling packets from the higher priority LCH). The UE 120 may continue to schedule packets in a similar manner (e.g., by strict priority and by synchronization-based scheduling for any scheduled packets) until the available uplink resources (e.g., available TB) have been filled.

[0134] If at least one packet in an LCH based on a deadline has an RDB exceeding the corresponding delay threshold, uplink resources in the available TB can be populated according to the procedure in which the LCH of the packet with the delay threshold is scheduled first. For example, among buffered packets in one or more LCHs, UE 120 may first select the packet with the smallest RDB to populate the available TB. In other words, UE 120 may first schedule LCHs with packets that have exceeded their delay thresholds. From the LCHs with packets that have exceeded their delay thresholds, UE 120 may first schedule packets with the smallest RDB for the available TB. If uplink resources are still available in the TB after scheduling the first packet, UE 120 may determine whether the first packet is associated with any relevant LCH. For example, UE 120 may determine whether the first packet (e.g., a first PDU or a first set of PDUs) should be synchronized with a second packet (e.g., a second PDU or a second set of PDUs) in a similar manner as described elsewhere herein. If UE 120 determines that the first packet needs to be synchronized with the second packet, UE 120 can use synchronization-based scheduling to schedule the second packet.

[0135] For example, UE 120 can determine whether the difference between a first time associated with a first packet and a second time associated with a second packet satisfies a synchronization threshold associated with the LCH of the first packet. If the difference between the first time associated with the first packet and the second time associated with the second packet satisfies the synchronization threshold associated with the LCH of the first packet, UE 120 can use the second packet to fill the available resources in TB. In other words, if there is not enough space in TB for the second packet, UE 120 can schedule the remainder of the packet in the next available transmission opportunity (e.g., when the next logical channel priority ordering is triggered). If the difference between the first time associated with the first packet and the second time associated with the second packet does not satisfy the synchronization threshold associated with the LCH of the first packet, UE 120 can avoid scheduling the second packet.

[0136] In other words, the uplink resources of the TB can be allocated to a first one or more packets having an RDB that satisfies the delay threshold of the corresponding LCH associated with the first one or more packets. Additionally, the uplink resources of the TB can be allocated to any packet associated with the first one or more packets according to multimodal service, the synchronization threshold being associated with the corresponding LCH associated with the first one or more packets. In this way, the UE 120 can ensure that packets or PDUs with small RDBs are transmitted first, and any packets to be synchronized with those packets are transmitted within the amount of time required to satisfy the synchronization threshold (e.g., thereby reducing the likelihood that a lack of synchronization is detectable by the user).

[0137] If remaining uplink resources exist in the TB after scheduling the first packet and related packets (e.g., using synchronization-based scheduling), UE 120 may select packets (e.g., PDUs) with the second minimum RDB to populate the remaining resources in the TB. UE 120 continues to select packets or PDUs to populate the TB based on, in response to, or otherwise associated with packets with the next minimum residual delay budget and / or related packets used for synchronization, until each PDU has an RDB exceeding the corresponding delay threshold of the PDU's LCH (e.g., until no PDU has a residual delay budget less than its delay threshold) or until the TB is fully populated. If remaining uplink resources remain in the TB after each PDU with an RDB exceeding the corresponding delay threshold has been applied, UE 120 may schedule the remaining PDUs of the LCH based on, in response to, or otherwise associated with strict priority operations (e.g., in a manner similar to that described elsewhere herein).

[0138] In some respects, UE 120 can determine the delay budget (e.g., packet delay budget (PDB)) of packets associated with synchronization (e.g., with multimodal services) by taking synchronization errors into account. For example, a packet included in data may be associated with a PDB. The packet may be associated with an LCH associated with a synchronization threshold. UE 120 may use a modified PDB (or dynamic PDB) that is modified in association with the PDB and the synchronization threshold to prioritize the LCH. For example, UE 120 may update the PDB of some packets based on, in response to, or otherwise associated with synchronization errors, instead of using a static PDB to schedule or prioritize the LCH. For example, packet A may be scheduled at time T. A At a point with a transmission deadline (e.g., defined by the first PDB), packet B can be sent at time T. B There is a transmission deadline (e.g., defined by a second PDB), and the synchronization error between packet A and packet B (e.g., defined by a synchronization threshold) can be D. If T A With T B If the difference between them is greater than D, then one of the transmission deadlines for packet A and / or packet B can be modified. For example, UE 120 can modify the PDB of packet A and / or packet B to ensure T A With T B The difference between them is less than or equal to D. For example, UE 120 can modify the second PDB of packet B so that the transmission deadline of packet B is T. A +D. If T A With T BIf the difference between them is less than or equal to D, then UE 120 can avoid modifying the PDB of packet A or packet B. In such examples, UE 120 can use strict priority-based scheduling and deadline-based scheduling to perform logical channel priority ordering and scheduling of packets (e.g., after modifying any PDB or transmission deadline based on synchronization information), as described elsewhere in this document.

[0139] In the fifth operation 625, UE 120 may transmit and network node 110 may receive uplink communication. The uplink communication may indicate (e.g., included in a TB) data. Data may be transmitted via one or more LCHs from a configured set of LCHs that are prioritized in association with one or more synchronization thresholds, as described in more detail elsewhere herein. The data may be XR data, VR data, and / or data associated with a multimodal service or application. For example, UE 120 may transmit TBs that are scheduled and / or allocated as described in conjunction with the fourth operation 620. Therefore, UE 120 can ensure that packets or PDUs used for multimodal services or applications are synchronized. This reduces the likelihood that users will perceive a significant lack of synchronization, thereby improving the user experience associated with multimodal services or applications.

[0140] Figure 7 This is a flowchart illustrating an example process 700 performed, for example, at a UE or a device of a UE, according to the present disclosure, to support logical channel priority ordering for synchronization. Example process 700 is an example in which the device or the UE (e.g., UE 120) performs operations associated with logical channel priority ordering for synchronization.

[0141] like Figure 7 As shown, in some aspects, process 700 may include: receiving configuration information for a set of logical channels, the configuration information indicating a set of synchronization thresholds associated with the set of logical channels respectively (block 710). For example, a UE (such as by using...) Figure 9 The communication manager 140 or receiving component 902 depicted herein may receive configuration information for a set of logical channels, which indicates a set of synchronization thresholds associated with the set of logical channels, as described above.

[0142] like Figure 7 Further shown, in some aspects, process 700 may include: transmitting the first data via a first logical channel from the set of logical channels in association with a delay between the first data and the second data of the second logical channel satisfying a synchronization threshold in the set of synchronization thresholds (block 720). For example, a UE (such as by using...) Figure 9The communication manager 140 or transmitting component 904 depicted herein may transmit the first data via a first logical channel from the set of logical channels, as described above, in association with the delay between the first data and the second data of the second logical channel satisfying a synchronization threshold in the set of synchronization thresholds.

[0143] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes described elsewhere in this document.

[0144] In the first additional aspect, the set of synchronization thresholds is associated with one or more multimodal services.

[0145] In a second additional aspect, either alone or in conjunction with the first aspect, the first data is associated with one or more packets related to reflected Quality of Service (QoS), the parameters of which indicate the identifier of the multimodal service in the one or more multimodal services, the identifier indicating that the first logical channel and the second logical channel are associated logical channels.

[0146] In a third additional aspect, the synchronization threshold is associated with the one or more groups, either alone or in combination with one or more of the first and second aspects.

[0147] In a fourth additional aspect, either alone or in combination with one or more of the first to third aspects, the configuration information indicates a corresponding delay threshold for the logical channel set, which is associated with the residual delay budget.

[0148] In the fifth additional aspect, either alone or in combination with one or more of the first to fourth aspects, the configuration information indicates the corresponding logical channel priority value of the logical channel set.

[0149] In a sixth additional aspect, either alone or in combination with one or more of the first to fifth aspects, the first data is associated with a first one or more packets associated with the first logical channel, and the second data is associated with a second one or more packets associated with the second logical channel, the first logical channel being associated with the synchronization threshold, and the first logical channel being associated with the second logical channel according to multimodal service, and transmitting the first data includes: transmitting the first one or more packets in association with prioritizing the first logical channel relative to one or more higher priority logical channels included in the set of logical channels, the prioritization being associated with the delay satisfying the synchronization threshold.

[0150] In the seventh additional aspect, either alone or in combination with one or more of the first to sixth aspects, the delay occurs between a first time associated with the first or more packets and a second time associated with the second or more packets, wherein the first time is associated with the arrival of the first or more packets at the PDCP component of the UE and the second time is associated with the arrival of the second or more packets at the PDCP component.

[0151] In the eighth additional aspect, either alone or in combination with one or more of the first to seventh aspects, process 700 includes scheduling the second or more packets for transmission in association with a logical channel priority value associated with the second logical channel, the logical channel priority value being indicated by the configuration information.

[0152] In the ninth additional aspect, either alone or in combination with one or more of the first to eighth aspects, the transmission of the first data includes the first data via one or more uplink resources, the one or more uplink resources being allocated to: the second data, the allocation being associated with the second data having a residual delay budget that satisfies the delay threshold of the second logical channel, and the first data, the allocation being associated with: the first logical channel being associated with the second logical channel.

[0153] In the tenth additional aspect, the first logical channel and the second logical channel are associated with multimodal services, either alone or in combination with one or more of the first to ninth aspects.

[0154] In the eleventh additional aspect, alone or in combination with one or more of the first to tenth aspects, transmitting the first data comprises: transmitting data including the first data and the second data via one or more uplink resources, the one or more uplink resources being allocated to: a first or more packets associated with the first data and having a residual delay budget that satisfies a delay threshold of a corresponding logical channel associated with the first or more packets; and / or any packet associated with the first or more packets according to a multimodal service, the allocation being associated with a synchronization threshold, the synchronization threshold being associated with the corresponding logical channel associated with the first or more packets.

[0155] In the twelfth additional aspect, either alone or in combination with one or more of the first to eleventh aspects, the first data and the second data include one or more PDUs, the one or more PDUs including in their respective headers an indication that the one or more PDUs are to be synchronized according to the synchronization threshold, the one or more PDUs being associated with different logical channels.

[0156] In the thirteenth additional aspect, either alone or in combination with one or more of the first to twelfth aspects, the first logical channel and the second logical channel are associated with an uplink indicator that identifies a logical channel correlation associated with the first logical channel and the second logical channel, the logical channel correlation indicating that the first logical channel and the second logical channel are to be synchronized according to the synchronization threshold.

[0157] In the fourteenth additional aspect, either alone or in combination with one or more of the first to thirteenth aspects, the configuration information includes an indication of the logical channel correlation between the first logical channel and the second logical channel, the channel correlation indicating that the first logical channel and the second logical channel should be synchronized according to the synchronization threshold.

[0158] In the fifteenth additional aspect, alone or in combination with one or more of the first to fourteenth aspects, the first data includes two or more sets of PDUs to be synchronized according to the synchronization threshold.

[0159] In the sixteenth additional aspect, alone or in combination with one or more of the first to fifteenth aspects, the packet associated with the first data is associated with a packet delay budget, the packet is associated with the first logical channel, and transmitting the first data includes: transmitting the packet by prioritizing the first logical channel using a modified packet delay budget that is modified in association with the packet delay budget and the synchronization threshold.

[0160] In the seventeenth additional aspect, the first data includes XR data, either alone or in combination with one or more of the first to sixteenth aspects.

[0161] In the eighteenth additional aspect, alone or in combination with one or more of the first to seventeenth aspects, the first data is associated with one or more packets related to one or more multimodal services.

[0162] although Figure 7 An example box for process 700 is shown, but in some respects, it differs from... Figure 7 Compared to the boxes depicted, process 700 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 700 may be executed in parallel.

[0163] Figure 8This is a flowchart illustrating an example process 800, performed according to the present disclosure, for example at a network node or a device of a network node, to support logical channel priority ordering for synchronization. Example process 800 is an example in which the device or the network node (e.g., network node 110) performs operations associated with logical channel priority ordering for synchronization.

[0164] like Figure 8 As shown, in some aspects, process 800 may include: transmitting configuration information for a set of logical channels, the configuration information indicating a set of synchronization thresholds associated with the set of logical channels (box 810). For example, network nodes (such as those using...) Figure 10 The communication manager 150 or transmitting component 1004 depicted herein can transmit configuration information for a set of logical channels, which indicates a set of synchronization thresholds associated with the set of logical channels, as described above.

[0165] like Figure 8 Further shown, in some aspects, process 800 may include: receiving the first data via a first logical channel from the set of logical channels in association with a delay between the first data and the second data of the second logical channel satisfying a synchronization threshold in the set of synchronization thresholds (box 820). For example, network nodes (such as those using...) Figure 10 The communication manager 150 or receiving component 1002 depicted herein may receive the first data via a first logical channel from the set of logical channels, in association with the delay between the first data and the second data of the second logical channel satisfying a synchronization threshold in the set of synchronization thresholds.

[0166] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes described elsewhere in this document.

[0167] In the first additional aspect, the set of synchronization thresholds is associated with one or more multimodal services.

[0168] In a second additional aspect, either alone or in conjunction with the first aspect, the first data is associated with one or more packets related to reflected Quality of Service (QoS), the parameters of which indicate the identifier of the multimodal service in the one or more multimodal services, the identifier indicating that the first logical channel and the second logical channel are associated logical channels.

[0169] In a third additional aspect, the synchronization threshold is associated with the one or more groups, either alone or in combination with one or more of the first and second aspects.

[0170] In a fourth additional aspect, either alone or in combination with one or more of the first to third aspects, the configuration information indicates a corresponding delay threshold for the logical channel set, which is associated with the residual delay budget.

[0171] In the fifth additional aspect, either alone or in combination with one or more of the first to fourth aspects, the configuration information indicates the corresponding logical channel priority value of the logical channel set.

[0172] In a sixth additional aspect, either alone or in combination with one or more of the first to fifth aspects, the first data is associated with a first one or more packets associated with the first logical channel, and the second data is associated with a second one or more packets associated with the second logical channel, the first logical channel being associated with the synchronization threshold, and the first logical channel being associated with the second logical channel according to multimodal service, and receiving the first data includes: receiving the first one or more packets in association with prioritizing the first logical channel relative to one or more higher priority logical channels included in the set of logical channels, the prioritization being associated with the delay satisfying the synchronization threshold.

[0173] In the seventh additional aspect, the first data is received, either alone or in combination with one or more of the first to sixth aspects, via one or more uplink resources, the one or more uplink resources being allocated to: the second data, the allocation being associated with the second data having a residual delay budget that satisfies the delay threshold of the second logical channel, and the first data, the allocation being associated with: the first logical channel being associated with the second logical channel.

[0174] In the eighth additional aspect, the first logical channel and the second logical channel are associated with multimodal services, either alone or in combination with one or more of the first to seventh aspects.

[0175] In the ninth additional aspect, data comprising the first data and the second data is received, either alone or in combination with one or more of the first to eighth aspects, via one or more uplink resources, the one or more uplink resources being allocated to: a first or more packets associated with the first data and having a residual delay budget that satisfies a delay threshold of a corresponding logical channel associated with the first or more packets; and / or any packet associated with the first or more packets according to a multimodal service, the allocation being associated with a synchronization threshold associated with the corresponding logical channel associated with the first or more packets.

[0176] In the tenth additional aspect, either alone or in combination with one or more of the first to ninth aspects, the first data and the second data include one or more PDUs, the one or more PDUs including in their respective headers an indication that the one or more PDUs are to be synchronized according to the synchronization threshold, the one or more PDUs being associated with different logical channels.

[0177] In the eleventh additional aspect, either alone or in combination with one or more of the first to tenth aspects, the first logical channel and the second logical channel are associated with an uplink indicator that identifies a logical channel correlation associated with the first logical channel and the second logical channel, the logical channel correlation indicating that the first logical channel and the second logical channel are to be synchronized according to the synchronization threshold.

[0178] In the twelfth additional aspect, either alone or in combination with one or more of the first to eleventh aspects, the configuration information includes an indication of the logical channel correlation between the first logical channel and the second logical channel, the channel correlation indicating that the first logical channel and the second logical channel should be synchronized according to the synchronization threshold.

[0179] In the thirteenth additional aspect, alone or in combination with one or more of the first to twelfth aspects, the first data includes two or more sets of PDUs to be synchronized according to the synchronization threshold.

[0180] In the fourteenth additional aspect, alone or in combination with one or more of the first to thirteenth aspects, the packet associated with the first data is associated with a packet delay budget, the packet is associated with the first logical channel, and receiving the first data includes: prioritizing the first logical channel to receive the packet according to a modified packet delay budget that is modified in association with the packet delay budget and the synchronization threshold.

[0181] In the fifteenth additional aspect, the first data and / or the second data include XR data, either alone or in combination with one or more of the first to fourteenth aspects.

[0182] In the sixteenth additional aspect, either alone or in combination with one or more of the first to fifteenth aspects, the first data and / or the second data includes one or more packets associated with one or more multimodal services.

[0183] although Figure 8 An example box for process 800 is shown, but in some respects, it differs from... Figure 8Compared to the boxes depicted, process 800 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 800 may be executed in parallel.

[0184] Figure 9 This is a diagram of an example device 900 for wireless communication that supports logical channel priority ordering for synchronization according to this disclosure. Device 900 may be a UE, or a UE may include device 900. In some aspects, device 900 includes a receiving component 902, a transmitting component 904, and a communication manager 140 that can communicate with each other (e.g., via one or more buses). As shown, device 900 can use the receiving component 902 and the transmitting component 904 to communicate with another device 906 (such as a UE, a network node, or another wireless communication device).

[0185] In some respects, device 900 may be configured and / or capable of operating to perform the functions described herein. Figure 6 One or more operations described herein. Additionally or alternatively, device 900 may be configured and / or capable of operating to perform one or more processes described herein, such as Figure 7 The process 700. In some aspects, the device 900 may include the above-described combination. Figure 2 One or more components of the UE as described.

[0186] Receiver 902 may receive communications from device 906, such as reference signals, control information, and / or data communications. Receiver 902 may provide the received communications to one or more other components of device 900, such as communication manager 140. In some aspects, receiver 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components. In some aspects, receiver 902 may include the combinations described above. Figure 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers / processors, and / or one or more memories.

[0187] Transmitting component 904 can transmit communications, such as reference signals, control information, and / or data communications, to device 906. In some aspects, communication manager 140 can generate communications and send the generated communications to transmitting component 904 for transmission to device 906. In some aspects, transmitting component 904 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and send the processed signals to device 906. In some aspects, transmitting component 904 may include the above-described combinations. Figure 2 The described UE includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, and / or one or more memories. In some aspects, the transmit component 904 may co-located with the receive component 902 in one or more transceivers.

[0188] Communication manager 140 may receive or cause receiving component 902 to receive configuration information for a set of logical channels, the configuration information indicating a set of synchronization thresholds associated with the set of logical channels respectively. Communication manager 140 may transmit the first data via a first logical channel from the set of logical channels in association with a delay between the first data and the second data of the second logical channel satisfying a synchronization threshold in the set of synchronization thresholds, or may cause transmitting component 904 to transmit the first data via a first logical channel from the set of logical channels in association with a delay between the first data and the second data of the second logical channel satisfying a synchronization threshold in the set of synchronization thresholds. In some aspects, communication manager 140 may perform one or more operations as described elsewhere herein by one or more components of communication manager 140.

[0189] Communication manager 140 may include the above-mentioned components. Figure 2 The described UE includes one or more controllers / processors and one or more memories. In some aspects, the communication manager 140 may include a collection of components, such as scheduling component 908, etc. Alternatively, this collection of components may be separate from and distinct from the communication manager 140. In some aspects, one or more components in this collection of components may include those described above. Figure 2 The described UE may include one or more controllers / processors, one or more memories, or may be implemented within one or more controllers / processors or one or more memories of the UE. Additionally or alternatively, one or more components in this set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by one or more controllers or one or more processors to perform the function or operation of the component.

[0190] The receiving component 902 can receive configuration information for a set of logical channels, which indicates a set of synchronization thresholds associated with the set of logical channels. The transmitting component 904 can transmit the first data via a first logical channel from the set of logical channels, in association with the delay between the first data and the second data of the second logical channel satisfying a synchronization threshold in the set of synchronization thresholds.

[0191] The scheduling component 908 can schedule the second or more packets for transmission in association with a logical channel priority value associated with the second logical channel, which is indicated by the configuration information.

[0192] Figure 9 The number and arrangement of components shown are provided as an example. In fact, with... Figure 9 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 9 The two or more components shown can be implemented within a single component, or Figure 9 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 9 The collection of (one or more) components shown is executable and described as being composed of Figure 9 Another set of components shown performs one or more functions.

[0193] Figure 10 This is a diagram of an example device 1000 for wireless communication that supports logical channel priority ordering for synchronization according to this disclosure. Device 1000 may be a network node, or a network node may include device 1000. In some aspects, device 1000 includes a receiving component 1002, a transmitting component 1004, and a communication manager 150 that can communicate with each other (e.g., via one or more buses). As shown, device 1000 can use the receiving component 1002 and the transmitting component 1004 to communicate with another device 1006 (such as a UE, a network node, or another wireless communication device).

[0194] In some respects, the device 1000 may be configured and / or capable of operating to perform the functions described herein. Figure 6 One or more operations described herein. Additionally or alternatively, the device 1000 may be configured and / or capable of operating to perform one or more processes described herein, such as Figure 8 The process 800. In some aspects, the device 1000 may include the above-described combination. Figure 2 One or more components of the network node described.

[0195] Receiver 1002 may receive communications, such as reference signals, control information, and / or data communications, from device 1006. Receiver 1002 may provide the received communications to one or more other components of device 1000, such as communication manager 150. In some aspects, receiver 1002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components. In some aspects, receiver 1002 may include the combinations described above. Figure 2 The described network node includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, and / or one or more memories.

[0196] The transmitting component 1004 can transmit communications, such as reference signals, control information, and / or data communications, to the device 1006. In some aspects, the communication manager 150 can generate communications and send the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can send the processed signals to the device 1006. In some aspects, the transmitting component 1004 may include the above-described combinations. Figure 2 The described network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, and / or one or more memories. In some aspects, the transmit component 1004 may co-located with the receive component 1002 in one or more transceivers.

[0197] The communication manager 150 may send, or cause the transmitting component 1004 to send, configuration information for a set of logical channels, which indicates a set of synchronization thresholds associated with the set of logical channels. The communication manager 150 may receive the first data via a first logical channel from the set of logical channels in association with a delay between the first data and the second data of the second logical channels satisfying a synchronization threshold in the set of synchronization thresholds, or may cause the receiving component 1002 to receive the first data via a first logical channel from the set of logical channels in association with a delay between the first data and the second data of the second logical channels satisfying a synchronization threshold in the set of synchronization thresholds. In some aspects, the communication manager 150 may perform one or more operations as described elsewhere herein by one or more components of the communication manager 150.

[0198] Communication manager 150 may include the above-mentioned combination Figure 2 The described network node includes one or more controllers / processors, one or more memories, one or more schedulers, and / or one or more communication units. In some aspects, the communication manager 150 may include a collection of components, such as identifying component 1008, etc. Alternatively, this collection of components may be separate from and distinct from the communication manager 150. In some aspects, one or more components in this collection may include those described above. Figure 2 The described network node may include, or may contain, one or more controllers / processors, one or more memories, one or more schedulers, and / or one or more communication units. Additionally or alternatively, one or more components of this set may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of that component.

[0199] The transmitting component 1004 can transmit configuration information for a set of logical channels, which indicates a set of synchronization thresholds associated with the set of logical channels. The receiving component 1002 can receive the first data via a first logical channel from the set of logical channels, in association with the delay between the first data and the second data of the second logical channel satisfying a synchronization threshold in the set of synchronization thresholds.

[0200] The determining component 1008 can determine the synchronization threshold for the corresponding logical channel in the set of logical channels. The determining component 1008 can determine the synchronization threshold based on, in response to, or otherwise associated with a multimodal service or application.

[0201] Figure 10 The number and arrangement of components shown are provided as an example. In fact, with... Figure 10 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 10 The two or more components shown can be implemented within a single component, or Figure 10 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 10 The collection of (one or more) components shown is executable and described as being composed of Figure 10 Another set of components shown performs one or more functions.

[0202] The following provides an overview of some aspects of this disclosure:

[0203] Aspect 1: A method for wireless communication by a user equipment (UE), the method comprising: receiving configuration information of a set of logical channels, the configuration information indicating a set of synchronization thresholds associated with the set of logical channels respectively; and transmitting the first data via the first logical channel in connection with a delay between the first data and the second data of the second logical channel satisfying a synchronization threshold in the set of synchronization thresholds associated with at least one of the first logical channel or the second logical channel from the set of logical channels.

[0204] Aspect 2: According to the method of aspect 1, the set of synchronization thresholds is associated with one or more multimodal services.

[0205] Aspect 3: According to the method of aspect 2, wherein the first data is associated with one or more packets related to reflection quality of service (QoS), the parameters of the reflection QoS indicating an identifier of the multimodal service in the one or more multimodal services, the identifier indicating that the first logical channel and the second logical channel are associated logical channels.

[0206] Aspect 4: According to the method of aspect 3, wherein the synchronization threshold associated with the logical channel is associated with a group comprising the one or more packets, the group being associated with the logical channel and the one or more associated logical channels.

[0207] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the configuration information indicates a corresponding delay threshold for the logical channel set, the delay threshold being associated with a residual delay budget.

[0208] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the configuration information indicates the corresponding logical channel priority value of the logical channel set.

[0209] Aspect 7: The method according to any one of Aspects 1 to 6, wherein: the first data is associated with a first one or more packets associated with the first logical channel, and the second data is associated with a second one or more packets associated with the second logical channel, the first logical channel being associated with the synchronization threshold, and the first logical channel being associated with the second logical channel according to a multimodal service; and sending the first data comprises: sending the first one or more packets in association with prioritizing the first logical channel relative to one or more higher priority logical channels included in the set of logical channels, the prioritization being associated with the delay satisfying the synchronization threshold.

[0210] Aspect 8: The method according to aspect 7, wherein: the delay is between a first time associated with the first one or more packets and a second time associated with the second one or more packets, and the first time is associated with the arrival of the first one or more packets at the Packet Data Convergence Protocol (PDCP) component of the UE, and the second time is associated with the arrival of the second one or more packets at the PDCP component.

[0211] Aspect 9: The method according to any one of Aspects 7 to 8, the method further comprising: scheduling the second one or more packets for transmission in association with a logical channel priority value associated with the second logical channel, the logical channel priority value being indicated by the configuration information.

[0212] Aspect 10: The method according to any one of Aspects 1 to 9, wherein transmitting the first data comprises: transmitting the first data via one or more uplink resources, the one or more uplink resources being allocated to: the second data, the allocation being associated with the second data having a residual delay budget that satisfies a delay threshold of the second logical channel, and the first data, the allocation being associated with: the first logical channel being associated with the second logical channel.

[0213] Aspect 11: According to the method of aspect 10, wherein the first logical channel and the second logical channel are associated with and related to a multimodal service.

[0214] Aspect 12: The method according to any one of Aspects 1 to 11, wherein transmitting the first data comprises: transmitting data including the first data and the second data via one or more uplink resources, the one or more uplink resources being allocated to: a first or more packets associated with the first data and having a residual delay budget that satisfies a delay threshold of a corresponding logical channel associated with the first or more packets; or any packet associated with the first or more packets according to a multimodal service, the allocation being associated with a synchronization threshold, the synchronization threshold being associated with the corresponding logical channel associated with the first or more packets.

[0215] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the first data and the second data comprise one or more Protocol Data Units (PDUs), wherein the one or more Protocol Data Units (PDUs) include in their respective headers an indication that the one or more PDUs are to be synchronized according to the synchronization threshold, and the one or more PDUs are associated with different logical channels.

[0216] Aspect 14: The method according to any one of Aspects 1 to 13, wherein the first logical channel and the second logical channel are associated with an uplink indicator, the uplink indicator identifying a logical channel correlation associated with the first logical channel and the second logical channel, the logical channel correlation indicating that the first logical channel and the second logical channel are to be synchronized according to the synchronization threshold.

[0217] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the configuration information includes an indication of logical channel correlation between the first logical channel and the second logical channel, the channel correlation indicating that the first logical channel and the second logical channel shall be synchronized according to the synchronization threshold.

[0218] Aspect 16: The method according to any one of Aspects 1 to 15, wherein the first data comprises two or more sets of Protocol Data Units (PDUs) to be synchronized according to the synchronization threshold.

[0219] Aspect 17: The method according to any one of Aspects 1 to 16, wherein the packet associated with the first data is associated with a packet delay budget, the packet is associated with the first logical channel, and wherein transmitting the first data comprises: transmitting the packet by prioritizing the first logical channel using a modified packet delay budget that is modified in association with the packet delay budget and the synchronization threshold.

[0220] Aspect 18: The method according to any one of aspects 1 to 17, wherein the first data includes extended reality (XR) data.

[0221] Aspect 19: The method according to any one of Aspects 1 to 18, wherein the first data is associated with one or more multimodal services.

[0222] Aspect 20: A method for wireless communication by a network node, the method comprising: transmitting configuration information of a set of logical channels, the configuration information indicating a set of synchronization thresholds associated with the set of logical channels respectively; and receiving the first data via the first logical channel in connection with a delay between the first data and the second data of the second logical channel satisfying a synchronization threshold in the set of synchronization thresholds associated with at least one of the first logical channel or the second logical channel from the set of logical channels.

[0223] Aspect 21: According to the method of aspect 20, the set of synchronization thresholds is associated with one or more multimodal services.

[0224] Aspect 22: According to the method of aspect 21, wherein the first data is associated with one or more packets related to reflection quality of service (QoS), the parameters of the reflection QoS indicating an identifier of the multimodal service in the one or more multimodal services, the identifier indicating that the first logical channel and the second logical channel are associated logical channels.

[0225] Aspect 23: According to the method of aspect 22, wherein the synchronization threshold is associated with the one or more packets.

[0226] Aspect 24: The method according to any one of Aspects 20 to 23, wherein the configuration information indicates a corresponding delay threshold for the logical channel set, the delay threshold being associated with a residual delay budget.

[0227] Aspect 25: The method according to any one of Aspects 20 to 24, wherein the configuration information indicates a corresponding logical channel priority value of the logical channel set.

[0228] Aspect 26: A method according to any one of Aspects 20 to 25, wherein: the first data is associated with a first one or more packets associated with the first logical channel, and the second data is associated with a second one or more packets associated with the second logical channel, the first logical channel being associated with the synchronization threshold, and the first logical channel being associated with the second logical channel according to a multimodal service; and wherein receiving the first data comprises: receiving the first one or more packets in association with prioritizing the first logical channel relative to one or more higher priority logical channels included in the set of logical channels, the prioritization being associated with the delay satisfying the synchronization threshold.

[0229] Aspect 27: The method according to any one of Aspects 20 to 26, wherein receiving the first data comprises: receiving the first data via one or more uplink resources, the one or more uplink resources being allocated to: the second data, the allocation being associated with the second data having a residual delay budget that satisfies a delay threshold of the second logical channel, and the first data, the allocation being associated with: the first logical channel being associated with the second logical channel.

[0230] Aspect 28: The method according to aspect 27, wherein the first logical channel and the second logical channel are associated with and related to a multimodal service.

[0231] Aspect 29: A method according to any one of Aspects 20 to 28, wherein receiving the first data comprises: receiving the first data via one or more uplink resources, the one or more uplink resources being allocated to: a first or more packets associated with the first data and having a residual delay budget that satisfies a delay threshold of a corresponding logical channel associated with the first or more packets; or any packet associated with the first or more packets according to a multimodal service, the allocation being associated with a synchronization threshold, the synchronization threshold being associated with the corresponding logical channel associated with the first or more packets.

[0232] Aspect 30: The method according to any one of Aspects 20 to 29, wherein the first data comprises one or more Protocol Data Units (PDUs), the one or more PDUs including in their respective headers an indication that the one or more PDUs are to be synchronized according to at least one of the synchronization thresholds, the one or more PDUs being associated with different logical channels.

[0233] Aspect 31: The method according to any one of Aspects 20 to 30, wherein one or more logical channel dependencies are indicated via an uplink indicator, the one or more logical channel dependencies indicating that two or more logical channels are to be synchronized according to at least one of the synchronization thresholds.

[0234] Aspect 32: The method according to any one of Aspects 20 to 31, wherein the configuration information includes an indication of one or more logical channel dependencies, the one or more logical channel dependencies indicating that two or more logical channels are to be synchronized according to the synchronization threshold.

[0235] Aspect 33: The method according to any one of Aspects 20 to 32, wherein the first data comprises two or more sets of Protocol Data Units (PDUs) to be synchronized according to the synchronization threshold.

[0236] Aspect 34: The method according to any one of Aspects 20 to 33, wherein the packet associated with the first data is associated with a packet delay budget, the packet is associated with the first logical channel, and wherein receiving the first data comprises: prioritizing the receiving of the packet using a modified packet delay budget, which is modified in association with the packet delay budget and the synchronization threshold, according to the first logical channel.

[0237] Aspect 35: The method according to any one of Aspects 20 to 34, wherein the first data includes extended reality (XR) data.

[0238] Aspect 36: The method according to any one of Aspects 20 to 35, wherein the first data is associated with one or more multimodal services.

[0239] Aspect 37: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 36.

[0240] Aspect 38: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 36.

[0241] Aspect 39: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 36.

[0242] Aspect 40: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 1 to 36.

[0243] Aspect 41: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 36.

[0244] Aspect 42: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 36.

[0245] Aspect 43: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 36.

[0246] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit all aspects to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or from various practices.

[0247] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and software. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein can be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to any specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein.

[0248] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0249] Although specific combinations of features are set forth in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set. As used herein, the phrase “at least one of” in the list of items refers to any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0250] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Similarly, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”).

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: A processing system, comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the UE to: Receive configuration information for a set of logical channels, wherein the configuration information indicates a set of synchronization thresholds associated with the set of logical channels respectively; as well as The first data is transmitted via the first logical channel when the delay between the first data and the second data of the second logical channel satisfies a synchronization threshold in the set of synchronization thresholds associated with at least one of the first logical channel or the second logical channel from the set of logical channels.

2. The UE of claim 1, wherein the set of synchronization thresholds is associated with one or more multimodal services.

3. The UE of claim 2, wherein the first data is associated with one or more packets related to reflected quality of service (QoS), the parameters of the reflected QoS indicating an identifier of a multimodal service in the one or more multimodal services, the identifier indicating that the first logical channel and the second logical channel are associated logical channels.

4. The UE of claim 1, wherein the configuration information indicates at least one of the following: The corresponding delay threshold of the logical channel set, which is associated with the residual delay budget, or The corresponding logical channel priority value of the logical channel set.

5. The UE according to claim 1, wherein: The first data is associated with one or more packets associated with the first logical channel, and the second data is associated with one or more packets associated with the second logical channel. The first logical channel is associated with the synchronization threshold, and the first logical channel is associated with the second logical channel according to multimodal service. In order for the UE to transmit the first data, the processing system is configured to cause the UE to transmit the first one or more packets in association with a first logical channel that prioritizes the first logical channel relative to one or more higher priority logical channels included in the set of logical channels, the prioritization being associated with the delay satisfying the synchronization threshold.

6. The UE according to claim 5, wherein: The delay occurs between a first time associated with the first or more packets and a second time associated with the second or more packets, and The first time is associated with the arrival of the first one or more packets at the Packet Data Convergence Protocol (PDCP) component of the UE, and the second time is associated with the arrival of the second one or more packets at the PDCP component.

7. The UE of claim 5, wherein the processing system is further configured to cause the UE to: The second or more packets are scheduled for transmission in association with a logical channel priority value associated with the second logical channel, the logical channel priority value being indicated by the configuration information.

8. The UE according to claim 1, wherein, In order for the UE to send the first data, the processing system is configured to cause the UE to: The first data is transmitted via one or more uplink resources, wherein the one or more uplink resources are allocated to: The second data, the allocation being associated with a residual delay budget that satisfies the delay threshold of the second logical channel, and The first data, the allocation is associated with the following: the first logical channel is associated with the second logical channel.

9. The UE of claim 8, wherein the first logical channel and the second logical channel are associated with and related to a multimodal service.

10. The UE according to claim 1, wherein, In order for the UE to send the first data, the processing system is configured to cause the UE to: Data including the first data and the second data is transmitted via one or more uplink resources, wherein the one or more uplink resources are allocated to: The first one or more packets, which are included in the data, have a residual delay budget that satisfies the delay threshold of the corresponding logical channel associated with the first one or more packets, or Any packet associated with the first one or more packets according to a multimodal service, the assignment being associated with a synchronization threshold, the synchronization threshold being associated with the corresponding logical channel associated with the first one or more packets.

11. The UE of claim 1, wherein the first data and the second data comprise one or more Protocol Data Units (PDUs), the one or more PDUs including in their respective headers an indication that the one or more PDUs are to be synchronized according to the synchronization threshold, the one or more PDUs being associated with different logical channels.

12. The UE of claim 1, wherein the first logical channel and the second logical channel are associated with an uplink indicator, the uplink indicator identifying a logical channel correlation associated with the first logical channel and the second logical channel, the logical channel correlation indicating that the first logical channel and the second logical channel are to be synchronized according to the synchronization threshold.

13. A network node for wireless communication, the network node comprising: A processing system, comprising one or more processors and one or more memories coupled to the one or more processors, is configured to cause the network node to: Send configuration information for a set of logical channels, wherein the configuration information indicates a set of synchronization thresholds associated with the set of logical channels respectively; as well as The first data is received via the first logical channel when the delay between the first data and the second data of the second logical channel satisfies a synchronization threshold in the set of synchronization thresholds associated with at least one of the first logical channel or the second logical channel from the set of logical channels.

14. The network node of claim 13, wherein the first data is associated with one or more packets related to reflected Quality of Service (QoS), the parameters of the reflected QoS indicating an identifier of a multimodal service in the one or more multimodal services, the identifier indicating that the first logical channel and the second logical channel are associated logical channels.

15. The network node of claim 13, wherein the set of synchronization thresholds is associated with one or more multimodal services.

16. The network node according to claim 13, wherein: The first data is associated with a first or more packets associated with the first logical channel, and the second data is associated with a second or more packets associated with the second logical channel, the first logical channel being associated with the synchronization threshold, and the first logical channel being associated with the second logical channel according to the multimodal service; and In order for the network node to receive the first data, the processing system is configured to cause the network node to receive the first one or more packets in association with prioritizing the first logical channel relative to one or more higher priority logical channels included in the set of logical channels, the prioritization being associated with the delay satisfying the synchronization threshold.

17. The network node according to claim 13, wherein, In order for the network node to receive the first data, the processing system is configured to cause the network node to: The first data is received via one or more uplink resources, wherein the one or more uplink resources are allocated to: The second data, the allocation being associated with a residual delay budget that satisfies the delay threshold of the second logical channel, and The first data, the allocation is associated with the following: the first logical channel is associated with the second logical channel.

18. The network node of claim 13, wherein the configuration information includes an indication of logical channel correlation between the first logical channel and the second logical channel, the logical channel indicating that the first logical channel and the second logical channel shall synchronize according to the synchronization threshold.

19. The network node of claim 13, wherein the first data comprises two or more sets of protocol data units (PDUs) to be synchronized according to the synchronization threshold.

20. The network node of claim 13, wherein the packet associated with the first data is associated with a packet delay budget, the packet is associated with the first logical channel, and in order for the network node to receive the first data, the processing system is configured to cause the network node to: The packets are prioritized for reception based on the first logical channel using a modified packet delay budget that is associated with the packet delay budget and the synchronization threshold.

21. A method for wireless communication by a user equipment (UE), the method comprising: Receive configuration information for a set of logical channels, wherein the configuration information indicates a set of synchronization thresholds associated with the set of logical channels respectively; as well as The first data is transmitted via the first logical channel when the delay between the first data and the second data of the second logical channel satisfies a synchronization threshold in the set of synchronization thresholds associated with at least one of the first logical channel or the second logical channel from the set of logical channels.

22. The method of claim 21, wherein the first data is associated with one or more packets related to reflection quality of service (QoS), the parameters of the reflection QoS indicating an identifier of a multimodal service in the one or more multimodal services, the identifier indicating that the first logical channel and the second logical channel are associated logical channels.

23. The method according to claim 21, wherein: The first data is associated with a first or more packets associated with the first logical channel, and the second data is associated with a second or more packets associated with the second logical channel, the first logical channel being associated with the synchronization threshold, and the first logical channel being associated with the second logical channel according to the multimodal service; and Sending the first data includes: sending the first one or more packets in association with prioritizing the first logical channel relative to one or more higher priority logical channels included in the set of logical channels, the prioritization being associated with the delay satisfying the synchronization threshold.

24. The method of claim 21, wherein sending the first data comprises: The first data is transmitted via one or more uplink resources, wherein the one or more uplink resources are allocated to: The second data, the allocation being associated with a residual delay budget that satisfies the delay threshold of the second logical channel, and The first data, the allocation is associated with the following: the first logical channel is associated with the second logical channel.

25. The method of claim 21, wherein sending the first data comprises: Data including the first data and the second data is transmitted via one or more uplink resources, wherein the one or more uplink resources are allocated to: The first one or more packets, which are included in the data, have a residual delay budget that satisfies the delay threshold of the corresponding logical channel associated with the first one or more packets, or Any packet associated with the first one or more packets according to a multimodal service, the assignment being associated with a synchronization threshold, the synchronization threshold being associated with the corresponding logical channel associated with the first one or more packets.

26. A method for wireless communication by a network node, the method comprising: Send configuration information for a set of logical channels, wherein the configuration information indicates a set of synchronization thresholds associated with the set of logical channels respectively; as well as The first data is received via the first logical channel when the delay between the first data and the second data of the second logical channel satisfies a synchronization threshold in the set of synchronization thresholds associated with at least one of the first logical channel or the second logical channel from the set of logical channels.

27. The method of claim 26, wherein the set of synchronization thresholds is associated with one or more multimodal services.

28. The method of claim 27, wherein the first data is associated with one or more packets related to reflected quality of service (QoS), the parameters of the reflected QoS indicating an identifier of a multimodal service in the one or more multimodal services, the identifier indicating that the first logical channel and the second logical channel are associated logical channels.

29. The method according to claim 26, wherein: The first data is associated with a first or more packets associated with the first logical channel, and the second data is associated with a second or more packets associated with the second logical channel, the first logical channel being associated with the synchronization threshold, and the first logical channel being associated with the second logical channel according to the multimodal service; and The first one or more packets are received in association with prioritizing the first logical channel relative to one or more higher priority logical channels included in the set of logical channels, the prioritization being associated with the delay satisfying the synchronization threshold.

30. The method of claim 26, wherein receiving the first data comprises: The first data is received via one or more uplink resources, wherein the one or more uplink resources are allocated to: The second data, the allocation being associated with a residual delay budget that satisfies the delay threshold of the second logical channel, and The first data, the allocation is associated with the following: the first logical channel is associated with the second logical channel.

Images