Concurrent transmission scheduling and prioritization

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may obtain one or more joint scheduling rules associated with long term evolution (LTE) communications and new radio (NR) communications in a half-duplex communication system. The UE may identify a channel busy rate (CBR) associated with the half-duplex communication system. The UE may prioritize LTE communications or NR communications based at least in part on the one or more joint scheduling rules and the CBR. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 052,766, filed on November 4, 2022, entitled “CONCURRENT TRANSMISSIONSCHEDULING AND PRIORITIZATION” and assigned to the assignee of this application. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for concurrent transmission scheduling and prioritization. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. The UE may communicate with the network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include obtaining one or more joint scheduling rules associated with long term evolution (LTE) communication and new radio (NR) communication in a half-duplex communication system. The method may include identifying a channel busy rate (CBR) associated with the half-duplex communication system. The method may include prioritizing LTE communication or NR communication based at least in part on the one or more joint scheduling rules and the CBR.

[0008] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include identifying an overlap between an NR transmission and a dedicated short range communication (DSRC) transmission. The method may include obtaining one or more rules for prioritizing the NR transmission or the DSRC transmission based at least in part on the overlap between the NR transmission and the DSRC transmission. The method may include sending at least one of the NR transmission or the DSRC transmission based at least in part on the one or more rules.

[0009] Some aspects described herein relate to an apparatus for wireless communication performed by a UE. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to obtain one or more joint scheduling rules associated with LTE communication and NR communication in a half-duplex communication system. The one or more processors may be configured to identify a CBR associated with the half-duplex communication system. The one or more processors may be configured to prioritize LTE communication or NR communication based at least in part on one or more joint scheduling rules and the CBR.

[0010] Some aspects described herein relate to an apparatus for wireless communication performed by a UE. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to identify an overlap between an NR transmission and a DSRC transmission. The one or more processors may be configured to obtain one or more rules for prioritizing NR transmission or DSRC transmission based at least in part on the overlap between the NR transmission and the DSRC transmission. The one or more processors may be configured to send at least one of the NR transmission or the DSRC transmission based at least in part on the one or more rules.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to obtain one or more joint scheduling rules associated with LTE communication and NR communication in a half-duplex communication system. The instruction set, when executed by one or more processors of the UE, may cause the UE to identify a CBR associated with the half-duplex communication system. The instruction set, when executed by one or more processors of the UE, may cause the UE to prioritize LTE communication or NR communication based at least in part on the one or more joint scheduling rules and the CBR.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to identify an overlap between an NR transmission and a DSRC transmission. The instruction set, when executed by one or more processors of the UE, may cause the UE to obtain one or more rules for prioritizing NR transmissions or DSRC transmissions based at least in part on the overlap between the NR transmission and the DSRC transmission. The instruction set, when executed by one or more processors of the UE, may cause the UE to send at least one of the NR transmissions or the DSRC transmissions based at least in part on the one or more rules.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for obtaining one or more joint scheduling rules associated with LTE communication and NR communication in a half-duplex communication system. The apparatus may include components for identifying a CBR associated with the half-duplex communication system. The apparatus may include components for prioritizing LTE communication or NR communication based at least in part on the one or more joint scheduling rules and the CBR.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for identifying an overlap between an NR transmission and a DSRC transmission. The apparatus may include means for obtaining one or more rules for prioritizing the NR transmission or the DSRC transmission based at least in part on the overlap between the NR transmission and the DSRC transmission. The apparatus may include means for transmitting at least one of the NR transmission or the DSRC transmission based at least in part on the one or more rules.

[0015] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to and as illustrated in the accompanying drawings.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations of the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The devices incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in a variety of devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

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

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

[0021] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of sidelink communication and V2X communication according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of side link communication and access link communication according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example of vehicle networking communication according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example of concurrent transmission scheduling according to the present disclosure.

[0026] Figure 8 is a diagram illustrating an example of concurrent transmission priority sorting according to the present disclosure.

[0027] Fig. 9 is a diagram illustrating an example of overlapping dedicated short range communication (DSRC) and new radio (NR) communications.

[0028] Fig.10 is a diagram illustrating an example of overlapping DSRC and NR communications according to the present disclosure.

[0029] Fig.11 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0030] Fig.12 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0031] Fig.13 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0032] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method practiced using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0033] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0034] Although various aspects may be described herein using terminology generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or 5G and beyond (e.g., 6G) RATs.

[0035] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0036] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.

[0037] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​the network node 110 and / or a network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. The network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0038] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with the network node 110. In some aspects, the term "base station" or "network node" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions, but not another base station function. In this way, a single device may include more than one base station.

[0039] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communications between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0040] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0041] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link. In some aspects, the network controller 130 may be, or may include, a CU or a core network device.

[0042] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), 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 smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0043] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0044] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0045] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network node 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0046] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0047] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). Bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, thus effectively extending the characteristics of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz), and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF band.

[0048] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0049] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may obtain one or more joint scheduling rules associated with LTE communication and NR communication in a half-duplex communication system; identify a channel busy rate (CBR) associated with the half-duplex communication system; and prioritize LTE communication or NR communication based at least in part on the one or more joint scheduling rules and the CBR. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0050] In some aspects, UE 120 may include a communication manager 140. As described in greater detail elsewhere herein, the communication manager 140 may identify an overlap between an NR transmission and a DSRC transmission; obtain one or more rules for prioritizing the NR transmission or the DSRC transmission based at least in part on the overlap between the NR transmission and the DSRC transmission; and transmit at least one of the NR transmission or the DSRC transmission based at least in part on the one or more rules. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0051] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0052] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0053] At network node 110, transmit processor 220 may receive data destined for UE 120 (or a set of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCSs) for UE 120 at least in part based on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) data for UE 120 at least in part based on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signal (CRS) or demodulation reference signal (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 may process the corresponding output symbol stream (e.g., for OFDM) using the respective modulator component to obtain a stream of output samples. Each modem 232 may also process the stream of output samples (e.g., convert to analog, amplify, filter, and / or up-convert) using the respective modulator component to obtain a downlink signal. Modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234t).

[0054] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0055] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0056] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0057] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, reference Figures 7 to 13 ) any aspects of any of the methods described herein.

[0058] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and provide the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 7 to 13 ) any aspects of any of the methods described herein.

[0059] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in the may perform one or more techniques associated with concurrent transmission scheduling and prioritization, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Fig.11 Process 1100, Fig.12 1200 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), may cause one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Fig.11 Process 1100, Fig.12 The process 1200 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0060] In some aspects, the UE 120 includes means for obtaining one or more joint scheduling rules associated with LTE communications and NR communications in a half-duplex communication system; means for identifying a CBR associated with the half-duplex communication system; and / or means for prioritizing LTE communications or NR communications based at least in part on the one or more joint scheduling rules and the CBR. Means for the UE 120 to perform operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0061] In some aspects, the UE 120 includes means for identifying an overlap between an NR transmission and a DSRC transmission; means for obtaining one or more rules for prioritizing the NR transmission or the DSRC transmission based at least in part on the overlap between the NR transmission and the DSRC transmission; and / or means for transmitting at least one of the NR transmission or the DSRC transmission based at least in part on the one or more rules. Means for the UE 120 to perform operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0062] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0063] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0064] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0065] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. The DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0066] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0067] Figure 3 3 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RTRIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0068] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces, the one or more interfaces being configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wireless transmission medium, or both.

[0069] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0070] 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 RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional partition such as that defined by 3GPP. In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may further host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0071] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. based on functional splitting (e.g., functional splitting defined by 3GPP) (such as lower layer functional splitting). In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0072] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTRIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0073] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0074] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to regulate RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0075] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0076] Figure 4 is a diagram illustrating an example 400 of sidelink communication and V2X communication according to the present disclosure.

[0077] like Figure 4 As shown, the first UE 405-1 can communicate with the second UE 405-2 (and one or more other UEs 405) via one or more side link channels 410. UEs 405-1 and 405-2 can communicate using one or more side link channels 410 for P2P communication, D2D communication, V2X communication (e.g., which may include V2V communication, V2I communication and / or V2P communication) and / or mesh networking. In one example, the first UE 405-1 can be a first vehicle, and the second UE 405-2 can be a second vehicle or a network node. The first vehicle and the second vehicle can communicate using V2X communication (such as V2V communication). In some aspects, one or more side link channels 410 can use a PC5 interface and / or can operate in a high frequency band (e.g., a 5.9 GHz band). Additionally or alternatively, the UE 405 may use global navigation satellite system (GNSS) timing to synchronize the timing of a transmit time interval (TTI) (eg, a frame, subframe, time slot, or symbol).

[0078] like Figure 4As further shown, the one or more sidelink channels 410 may include a physical sidelink control channel (PSCCH) 415, a physical sidelink shared channel (PSSCH) 420, and / or a physical sidelink feedback channel (PSFCH) 425. The PSCCH 415 may be used to communicate control information, similar to a physical downlink control channel (PDCCH) and / or a physical uplink control channel (PUCCH) used for cellular communication with the network node 110 via an access link or access channel. The PSSCH 420 may be used to communicate data, similar to a physical downlink shared channel (PDSCH) and / or a physical uplink shared channel (PUSCH) used for cellular communication with the network node 110 via an access link or access channel. For example, the PSCCH 415 may carry sidelink control information (SCI) 430, which may indicate various control information for sidelink communication, such as one or more resources (e.g., time resources, frequency resources, and / or space resources), wherein a transport block (TB) 435 may be carried on the PSSCH 420. The TB 435 may include data. The PSFCH 425 may be used to communicate sidelink feedback 440, such as hybrid automatic repeat request (HARQ) feedback (eg, acknowledgement or negative acknowledgement (ACK / NACK) information), transmit power control (TPC), and / or scheduling request (SR).

[0079] Although shown on PSCCH 415, in some aspects SCI 430 may include multiple communications in different levels, such as a first level SCI (SCI-1) and a second level SCI (SCI-2). SCI-1 may be sent on PSCCH 415. SCI-2 may be sent on PSSCH 420. SCI-1 may include, for example, an indication of one or more resources (e.g., time resources, frequency resources, and / or space resources) on PSSCH 420, information for decoding sidelink communications on PSSCH, a quality of service (QoS) priority value, a resource reservation period, a PSSCH demodulation reference signal (DMRS) pattern, an SCI format for SCI-2, a beta offset for SCI-2, a number of PSSCH DMRS ports, and / or a modulation and coding scheme (MCS). SCI-2 may include information associated with data transmission on the PSSCH 420, such as a hybrid automatic repeat request (HARQ) process ID, a new data indicator (NDI), a source identifier, a destination identifier, and / or a channel state information (CSI) report trigger.

[0080] In some aspects, one or more sidelink channels 410 may use a resource pool. For example, a scheduling assignment (e.g., included in SCI 430) may be sent in a subchannel using specific resource blocks (RBs) across time. In some aspects, data transmissions associated with the scheduling assignment (e.g., on PSSCH 420) may occupy adjacent RBs in the same subframe as the scheduling assignment (e.g., using frequency division multiplexing). In some aspects, the scheduling assignment and the associated data transmission are not sent on adjacent RBs.

[0081] In some aspects, the UE 405 may operate using a sidelink transmission mode (e.g., mode 1) in which resource selection and / or scheduling is performed by the network node 110 (e.g., a base station, CU, or DU). For example, the UE 405 may receive a grant for sidelink channel access and / or scheduling from the network node 110 (e.g., directly or via one or more network nodes) (e.g., in downlink control information (DCI) or in a radio resource control (RRC) message, such as a grant for configuration). In some aspects, the UE 405 may operate using a transmission mode (e.g., mode 2) in which resource selection and / or scheduling is performed by the UE 405 (e.g., instead of the network node 110). In some aspects, the UE 405 may perform resource selection and / or scheduling by sensing channel availability for transmission. For example, UE 405 may measure received signal strength indicator (RSSI) parameters associated with various sidelink channels (e.g., sidelink RSSI (S-RSSI) parameters), may measure reference signal received power (RSRP) parameters associated with various sidelink channels (e.g., PSSCH-RSRP parameters), and / or may measure reference signal received quality (RSRQ) parameters associated with various sidelink channels (e.g., PSSCH-RSRQ parameters), and may select a channel for transmission of sidelink communications based at least in part on the measurements.

[0082] Additionally or alternatively, the UE 405 may perform resource selection and / or scheduling using the SCI 430 received in the PSCCH 415, which may indicate occupied resources and / or channel parameters. Additionally or alternatively, the UE 405 may perform resource selection and / or scheduling by determining a channel busy rate (CBR) associated with each sidelink channel, which may be used for rate control (e.g., by indicating a maximum number of resource blocks that the UE 405 may use for a particular set of subframes).

[0083] In a transmission mode in which resource selection and / or scheduling is performed by the UE 405, the UE 405 may generate a sidelink grant and may transmit the grant in the SCI 430. The sidelink grant may indicate, for example, one or more parameters (e.g., transmission parameters) for an upcoming sidelink transmission, such as one or more resource blocks (e.g., for TB 435) to be used for the upcoming sidelink transmission on the PSSCH 420, one or more subframes to be used for the upcoming sidelink transmission, and / or a modulation and coding scheme (MCS) to be used for the upcoming sidelink transmission. In some aspects, the UE 405 may generate a sidelink grant that indicates one or more parameters for semi-persistent scheduling (SPS), such as the periodicity of the sidelink transmission. Additionally or alternatively, the UE 405 may generate a sidelink grant for event-driven scheduling (such as for an on-demand sidelink message).

[0084] As indicated above, Figure 4 are provided as examples. Other examples can be found in relation to Figure 4 The examples described are different.

[0085] Figure 5 is a diagram illustrating an example 500 of side link communications and access link communications according to the present disclosure.

[0086] like Figure 5 As shown, the transmitter (Tx) / receiver (Rx) UE 505 and the Rx / Tx UE 510 can communicate with each other via a side link, as described above in conjunction with Figure 4 In some cases, the Tx / Rx UE 505 may be a first vehicle (such as the first vehicle 405-1), and the Tx / Rx UE 510 may be a second vehicle (such as the second vehicle 405-2) or a network node. As further shown in the figure, in some side link modes, the network node 110 may communicate with the Tx / Rx UE 505 (e.g., directly or via one or more network nodes), such as via a first access link. Additionally or alternatively, in some side link modes, the network node 110 may communicate with the Rx / Tx UE 510 (e.g., directly or via one or more network nodes), such as via a first access link. The Tx / Rx UE 505 and / or the Rx / Tx UE 510 may correspond to one or more UEs described elsewhere herein, such as Figure 1120. Thus, a direct link between UEs 120 (e.g., via a PC5 interface) may be referred to as a side link, and a direct link between network 110 and UE 120 (e.g., via a Uu interface) may be referred to as an access link. Sidelink communications may be sent via a side link, and access link communications may be sent via an access link. Access link communications may be downlink communications (from network node 110 to UE 120) or uplink communications (from UE 120 to network node 110).

[0087] As indicated above, Figure 5 are provided as examples. Other examples can be found in relation to Figure 5 The examples described are different.

[0088] Figure 6 600 is a diagram illustrating an example of V2X communication according to the present disclosure. A vehicle 605 may include one or more antennas 610. For example, the vehicle 605 may include an antenna 610-1 for communicating with one or more other devices (such as another vehicle 615, a network node 110, or a UE 120, etc.). Antenna 610-1 may be configured to communicate with one or more other devices using one or more V2X technologies (such as NR V2X and LTE V2X). In another example, the vehicle 605 may include two antennas (such as antenna 610-1 and antenna 610-2) for communicating with one or more devices.

[0089] In some cases, different V2X technologies may be deployed on different channels in the Intelligent Transport System (ITS) band. A V2X transceiver may need to support different V2X technologies (e.g., NR V2X and LTE V2X) concurrently for both transmission and reception. For automotive products, there may be two antennas (such as antennas 610-1 and 610-2) that are shared for transmission and reception and for different technologies. This may be due to, for example, the high cost of wiring on the floor of the car and poor isolation between antennas. In some cases, the half-duplex nature of V2X technology may be due to the limitations of shared antennas for transmission and reception in V2X. For example, once there is a transmission using any V2X technology from any one of the antennas 610, there may be no reception for all V2X technologies on all antennas 610.

[0090] In some cases, each of the V2X technologies (NR V2X and LTE V2X) may independently select transmit resources using autonomous channel sensing (e.g., for the channel on which the respective technology is deployed) and semi-persistent scheduling (SPS) transmit scheduling. Each V2X technology may attempt to minimize the negative impact of received packet drops due to the half-duplex restriction on the channel. In some cases, the autonomous scheduling process of each respective V2X technology may search for available resources for transmit scheduling only on the channel associated with that V2X technology. If two V2X technologies independently select transmit resources, there is a possibility that some portions of the received traffic (from the other technology) will be dropped.

[0091] In some cases, NR V2X transmissions may require two transmit antennas (such as antennas 610-1 and 610-2) and may need to support MIMO. When two transmissions with cyclic delay diversity (CDD) occur, this can improve LTE V2X performance. Concurrent transmissions (via two antennas) for two V2X technologies (where each antenna uses a single transmission) may be unacceptable. Concurrent transmissions using two antennas (where two V2X technology signals are transmitted simultaneously on different channels) may involve more complex, demanding, and expensive RF front-end (RFFE) designs that are not available with existing RF solutions. Therefore, time division multiplexing (TDM) may need to be used for transmissions using concurrent V2X technologies. In some cases, if two V2X technologies are trying to use the same resources or use resources that overlap in time to schedule transmissions, arbitration may be required to select only one specific V2X technology to transmit at any given time. However, current arbitration methods are not sufficient to select between V2X technologies to reduce or eliminate concurrent transmissions. This may result in an increase in the number of dropped communications. Techniques and apparatus described herein can reduce the number of dropped communications based at least in part on the use of transmission scheduling for LTE V2X and NR V2X. Additional details are provided below in conjunction with Figure 7 to describe.

[0092] As indicated above, Figure 6 are provided as examples. Other examples can be found in relation to Figure 6 The examples described are different.

[0093] Figure 7is a diagram illustrating an example 700 of concurrent transmission scheduling according to the present disclosure. UE 120 may communicate with network node 110. Network node 110 may be CU 310, DU 330, or RU 340, among others. In some aspects, network node 110 may be another UE or may be included in another UE. For example, UE 120 may be a first vehicle (such as vehicle 405-1) and network node 110 may be another vehicle (such as vehicle 405-2). UE 120 and network node 110 may communicate using LTE V2X communication or NR V2X communication, among others. V2X communication may be cellular V2X (C-V2X) communication.

[0094] As shown by reference numeral 705, UE 120 may obtain one or more joint scheduling rules associated with LTE communication and NR communication in a half-duplex communication system. UE 120 may obtain the one or more joint scheduling rules based at least in part on overlap between LTE communication (such as LTE transmission) and NR communication (such as NR transmission). The one or more joint scheduling rules may indicate prioritizing LTE communication or NR communication based at least in part on a CBR associated with the half-duplex communication system.

[0095] As shown by reference numeral 710, the UE 120 may identify a CBR associated with a half-duplex communication system. The CBR associated with the half-duplex communication system may be used by the UE 120 to determine a priority for performing LTE communication or NR communication.

[0096] As indicated by reference numeral 715, the UE 120 may prioritize LTE communications or NR communications based at least in part on one or more joint scheduling rules and the CBR. As described herein, when transmission is performed using either of the V2X technologies (LTE V2X or NR V2X), reception for both V2X technologies may be limited due to the half-duplex nature of the communication system. Any reception resources that overlap in time with transmission resources may be excluded by the channel sensing algorithms on both technologies. In this case, joint scheduling and mutual awareness of scheduling decisions may be required to eliminate the probability of overlap of transmission resources for the two V2X technologies (e.g., using resource reselection (SPS), non-SPS scheduling, periodic physical sidelink feedback channel (PSFCH) or sidelink synchronization signal (SLSS) slots in NR, etc.).

[0097] In some aspects, one or more prioritization rules may indicate prioritizing LTE communications or NR communications based at least in part on the CBR of the half-duplex communication system. One or more joint scheduling rules may indicate multiple CBR thresholds, such as a low CBR threshold and a high CBR threshold. In one example, the low CBR threshold may be 0.3, and the high CBR threshold may be 0.8. However, other thresholds may be used. Additionally or alternatively, different numbers of thresholds may be used. For example, a single CBR threshold may be used, or three CBR thresholds may be used, and so on.

[0098] In a first example, the UE 120 may identify that the CBR associated with the half-duplex communication system does not meet the low CBR threshold. For example, the UE 120 may determine that the CBR associated with the half-duplex communication system is less than, or less than or equal to 0.3. In this example, there may be sufficient free resources on both channels to allow TDM transmission using both V2X technologies. For example, LTE communications and NR communications may be multiplexed (using TDM) for transmission scheduling with little or no discarding of SPS receive traffic. Assuming there is a joint free transmission resource selection across the two V2X technologies, the UE 120 may perform TDM transmission.

[0099] In a second example, UE 120 may identify that the CBR associated with the half-duplex communication system meets the low CBR threshold but does not meet the high CBR threshold. For example, UE 120 may determine that the CBR associated with the half-duplex system is greater than, or greater than or equal to 0.3, but less than, or less than or equal to 0.8. In this example, there may not be enough free resources on both channels to minimize or eliminate dropped receptions. In some aspects, safety-related communications may be given higher priority than non-safety-related communications.

[0100] In some aspects, safety-related LTE-V2X reception may be given priority over non-safety-related NR-V2X reception. By applying different free resource classification thresholds (e.g., based at least in part on RSSI measurements or RSRP measurements, etc.) to LTE communications and NR communications, safety-related LTE-V2X reception may be given higher priority than non-safety-related NR-V2X reception. Different free resource classification thresholds may be used to expand the NR free resource pool to move NR transmission scheduling away from occupied resources on LTE-V2X. This may allow controlled technology TDM operation with priority sorting.

[0101] In some aspects, safety-related NR-V2X reception may be given priority over non-safety-related LTE-V2X reception. By applying different free resource classification thresholds (e.g., based at least in part on RSSI measurements or RSRP measurements, etc.) to NR communications and LTE communications, safety-related LTE-V2X reception may be given higher priority than non-safety-related LTE-V2X reception. Different free resource classification thresholds may be used to expand the LTE free resource pool to move LTE transmission scheduling away from occupied resources on NR-V2X. This may allow controlled technology TDM operation with priority sorting.

[0102] In a third example, UE 120 may identify that a CBR associated with a half-duplex communication system meets a high CBR threshold. For example, UE 120 may determine that a CBR associated with a half-duplex system is greater than, or greater than or equal to, 0.8.

[0103] In some aspects, the UE 120 may be required to drop (or delay) some NR traffic (transmission and / or reception) by giving priority to safety-related LTE-V2X communications. The NR transmission dropping (or delaying) may be performed in advance based at least in part on the scheduling level. In some aspects, the NR PSFCH transmission scheduling may be performed only during the second LTE-V2X time slot. This may increase the probability that partially overlapping received LTE-V2X packets are not lost even in the event of a last symbol erasure due to an NR transmission.

[0104] In some aspects, the UE 120 may be required to drop (or delay) some LTE traffic (transmission and / or reception) by giving priority to safety-related NR-V2X communications. The LTE transmission dropping (or delaying) may be performed in advance based at least in part on the scheduling level. In some aspects, the LTE PSFCH transmission scheduling may be performed only during the second NR-V2X time slot. This may increase the probability that partially overlapping received NR-V2X packets are not lost even in the event of a last symbol erasure due to LTE transmission.

[0105] As described above, if two V2X technologies are attempting to schedule transmissions using the same resources or using resources that overlap in time, arbitration may be required to select only one specific V2X technology to transmit at a given time. However, current arbitration methods are not sufficient to select between V2X technologies to reduce or eliminate concurrent transmissions. This may result in an increase in the number of dropped communications. The techniques and devices described herein may reduce the number of dropped communications based at least in part on the use of transmission scheduling for LTE V2X and NR V2X. The techniques and devices described herein may provide multiple advantages, such as simpler designs and performance gains with reduced hardware and specific implementation constraints. For example, there may be fewer receive traffic drops for concurrent V2X technologies (and / or better transmit and receive joint TDM across the two V2X technologies), no drops for LTE-V2X critical safety messages from closed environments (LTE-V2X SPS transmissions may be prioritized by the joint scheduler), and fewer transmission drops across the two V2X technologies due to TDM transmission constraints (avoiding transmission conflicts through joint transmission resource selection across V2X technologies).

[0106] As indicated above, Figure 7 are provided as examples. Other examples can be found in relation to Figure 7 The examples described are different.

[0107] In some aspects, the vehicle 605 may include two antennas, such as a first antenna 610-1 and a second antenna 610-2. The first antenna 610-1 and the second antenna 610-2 may be configured to perform communications using dedicated short range communications (DSRC) and / or NR V2X.

[0108] In some cases, different automotive technologies such as DSRC and NR V2X may be deployed on different channels in the ITS band. The V2X transceiver may need to support different automotive technologies concurrently for both transmission and reception. For automotive products, there may be two antennas (such as antennas 610-1 and 610-2) that are shared for transmission and reception and for different concurrent technologies. This may be due to, for example, the high cost of wiring on the floor of the car and poor isolation between the antennas. In some cases, the half-duplex nature of the V2X technology may be due to the limitations of the shared antennas used for transmission and reception in V2X. For example, once there is a transmission using any V2X technology from any one of the antennas 610, there may be no reception for all V2X technologies on all antennas 610.

[0109] In some cases, each of the automotive technologies (DSRC and NR-V2X) can independently select transmission resources to avoid channel conflicts using autonomous channel sensing (for the channels in which the respective technology is deployed), SPS transmission scheduling (in the case of NR-V2X), or carrier sense multiple access with collision avoidance (CSMA / CA) with clear channel assessment (CCA) (in the case of DSRC). In some cases, the autonomous scheduling process of each respective automotive technology can search only on the channels associated with that automotive technology for available resources for transmission scheduling. If the two automotive technologies independently select transmission resources, there is a possibility that some portion of the received traffic (from the other automotive technology) will be dropped. In some cases, joint or mutual awareness of transmission decisions, resource selection, and transmission scheduling or access can be used to minimize the potential dropping of received traffic due to half-duplex limitations along with concurrent automotive technology support requirements. However, this type of cross-technology cooperation and coordination may not be possible in the case of a DSRC and V2X technology combination.

[0110] C-V2X is a synchronous technology that uses autonomous SPS scheduling based at least in part on channel sensing. The C-V2X scheduling algorithm can take into account the half-duplex limitations of the communication to minimize C-V2X received traffic drops. In contrast, DSRC is an asynchronous technology where channel access is contention-based and relies on the CSMA / CA algorithm with CCA to avoid or minimize conflicts on the shared channel. Accordingly, there may not be a transmission scheduling on specific time resources predefined according to some criteria. Instead, in the case of DSRC, there may be asynchronous or unpredictable contention-based channel access that is at least in part based on the enhanced distributed channel access (EDCA) algorithm that allows QoS (e.g., prioritization or differentiation of channel access for different messages, traffic types, or priorities). EDCA is an advanced version of the distributed coordination function (DCF) that allows contention-based access with QoS (e.g., DCF with four priorities). DCF is a basic contention-based channel access method that is at least in part based on CSMA / CA but without QoS differentiation between different traffic or data types. EDCA can use different arbitration interframe spaces (AIFS) and contention window (CW) sizes for different access categories (AC) or traffic priorities.

[0111] In some cases, CCA is based on physical channel sensing (CS) including RSSI measurements. These measurements can drive the CCA state of EDCA. Since DSRC does not have predictable (or controllable) advance transmission time (e.g., the transmission timing is determined by the EDCA channel access process that depends on other users via CCA), joint scheduling solutions to avoid transmission conflicts across technologies are not applicable (e.g., due to the combination of synchronous and non-synchronous technologies). In some cases, joint scheduling (e.g., as in the case of LTE-V2X and NR-V2X concurrency) can mitigate or minimize both receive packet drops due to half-duplex limitations and transmit packet drops due to transmission conflicts between concurrent technologies or transmissions overlapping in time. Some other options for multiplexing transmissions for concurrent DSRC and NR-V2X technologies (e.g., using TDM) may include delaying DSRC transmissions to avoid any transmission drops due to overlap (in time) between DSRC transmissions and NR-V2X transmissions; giving priority to DSRC transmissions that convey safety or other critical messages and dropping or delaying NR-V2X transmissions in the event of a conflict or overlap in time between DSRC and NR-V2X transmissions; and giving priority to one of the technology transmissions based at least in part on the transmission message priority (e.g., regardless of which technology is being used, a higher priority message may be sent and the other transmission may be dropped or delayed). Additional details are provided below in conjunction with Figure 8-10 to describe.

[0112] Figure 8 8 is a diagram illustrating an example 800 of concurrent transmission prioritization according to the present disclosure. UE 120 may communicate with network node 110. Network node 110 may be CU 310, DU 330, or RU 340, among others. In some aspects, network node 110 may be another UE or may be included in another UE. For example, UE 120 may be a first vehicle (such as vehicle 405-1) and network node 110 may be another vehicle (such as vehicle 405-2). UE 120 and network node 110 may communicate using DSRC or NR-V2X communication, among others. NR-V2X communication may be NR-C-V2X communication.

[0113] Giving priority to NR transmissions by delaying DSRC transmissions can result in fewer transmission drops across both technologies (e.g., NR and DSRC). In some aspects, the NR transmission time can be fixed. In the example of giving priority to overlapping DSRC transmissions, NR transmissions can be sent or dropped. However, there is no fixed transmission time for DSRC. Therefore, in the example of giving priority to overlapping NR transmissions, DSRC transmissions can be delayed (rather than dropped).

[0114] The transmit duty cycle of V2X may be low (e.g., limited to 3%), and the effective NR transmit session duration may be limited. The effective NR transmit session duration limit (from the DSRC perspective with TDM technology transmit constraints) may be equal to the NR transmit preparation time plus the NR transmit time plus the DSRC transmit time (e.g., NR Tx preparation time + NR Tx duration + DSRC Tx configuration time), which may be equal to 1.5 + 0.5 + 0.5 = 2.5 milliseconds (assuming single slot transmission for NR). In some cases, NR scheduling may be performed three slots before the transmit start time, and back-to-back transmit scheduling may be avoided or limited in order to maintain DSRC high latency limits. In some cases, the DSRC actual transmit time or latency may be based at least in part on the CCA process and may be a function of the CBR. Some additional delays (e.g., relatively low delays) may have no effect on the DSRC actual transmit time or latency.

[0115] As shown by reference numeral 805, UE 120 may identify an overlap between an NR transmission and a DSRC transmission. The overlap between the NR transmission and the DSRC transmission may be a complete overlap or may be a partial overlap. In some aspects, the NR transmission and the DSRC transmission may be multiplexed transmissions (e.g., using TDM).

[0116] As shown by reference numeral 810, UE 120 may obtain one or more rules for prioritizing NR transmissions or DSRC transmissions based at least in part on the overlap between the NR transmissions and the DSRC transmissions. In some aspects, UE 120 may prioritize NR transmissions. Additional details are described below.

[0117] As indicated by reference numeral 815, UE 120 may transmit at least one of a NR transmission or a DSRC transmission based at least in part on one or more rules.

[0118] In a first example, NR transmission can be scheduled before DSRC transmission. In this example, the overlapping DSRC data transmission session can be delayed until the NR transmission is completed. The DSRC transmission session can include a DSRC transmission configuration delay portion, a CCA / channel contention portion, and a physical layer protocol data unit (PPDU) transmission duration portion.

[0119] When a DSRC medium access control service data unit (MSDU) packet enters the EDCA transmit queue and an NR transmit is already scheduled, DSRC transmit configuration may not be performed. For example, the transmit path may be shared for both technologies and the NR transmit may be given priority over the DSRC transmit. DSRC CCA may be delayed until the NR transmit is complete by simulating a "channel busy" condition for the DSRC channel access controller / EDCA (which may be disconnected from the actual CCA measurement in the physical layer). DSRC transmission may be configured after (e.g., immediately after) the NR transmit is completed. Once the NR transmit session is completed and the DSRC transmit is configured, the CCA may switch back to performing the actual physical channel sensing and the DSRC transmit session may continue as usual.

[0120] DSRC ACK transmissions (e.g., for unicast receive packets) that overlap with the active time of an NR transmit session (NR Tx configuration + NR transmit timeslot + DSRC transmit configuration) may be discarded. DSRC ACK transmissions may be discarded based at least in part on the assumption that DSRC ACK transmissions cannot be delayed. Unicast messages may be a minority of communications on a DSRC channel, and once a unicast receive packet is received, the DSRC ACK duration and start of transmission may be predictable.

[0121] Combination Fig. 9 Additional details regarding these features are described.

[0122] In a second example, a DSRC transmission may be scheduled before an NR transmission. In the case of an NR transmission session that overlaps with a DSRC transmission, the ongoing DSRC transmission session or channel contention attempt may be stopped or delayed from the time the NR transmission is scheduled until the NR transmission is completed. This may assume, for example, that a PPDU transmission has not yet been initiated.

[0123] The DSRC transmission session may be stopped or delayed based at least in part on a "channel busy" condition emulating a DSRC channel access controller or scheduler (EDCA) until the NR transmission session is completed and the DSRC transmission is reconfigured.

[0124] Once the NR transmission session is completed and the DSRC transmission is reconfigured, CCA can switch back to performing the actual physical channel sensing, and the DSRC transmission session can continue as usual with the same enhanced digital channel access function (EDCAF) parameters (such as the same random access (RA) back-off (BO) counter value and codeword (CW) size, etc.) as before the time when the DSRC transmission was stopped.

[0125] In some aspects, DSRC ACK transmissions (e.g., for unicast reception packets) that overlap with the valid time of an NR transmission session (NR transmission configuration + NR transmission time slot + DSRC transmission configuration) may be discarded. The DSRC ACK transmissions may be discarded based at least in part on the assumption that the DSRC ACK transmissions cannot be delayed.

[0126] In some aspects, there may be no active DSRC transmission or NR transmission stop in the physical layer or MAC layer. If a DSRC PPDU transmission has been triggered by EDCA, the transmission may be performed, and if the DSRC PPDU transmission duration overlaps with the NR transmission configuration time slot, the NR transmission may be discarded. The PPDU transmission duration (e.g., at least one of the medium access control (MAC) protocol data unit (MPDU) header fields) may be known in advance by the transmitter.

[0127] Combination Fig.10 Additional details regarding these features are described.

[0128] As indicated above, Figure 8 are provided as examples. Other examples can be found in relation to Figure 8 The examples described are different.

[0129] Fig. 9 900 is a diagram illustrating an example of overlapping DSRC and NR communications. In some aspects, NR transmissions may be scheduled before DSRC transmissions. As indicated by reference numeral 905, NR transmissions may be scheduled at time slot n. NR transmission configuration 910 may be scheduled at time slot n+2, and NR transmission time slot 915 may be scheduled at time slot n+3.

[0130] As shown by reference numeral 920, an MSDU packet associated with a DSRC transmission may enter an EDCA transmission queue after time slot n. For example, an MSDU packet may enter an EDCA transmission queue after time slot n but before time slot n+2. As shown by reference numeral 925, the MSDU packet may be delayed in the EDCA transmission queue until after the NR transmission is completed. The DSRC transmission configuration may be delayed based at least in part on the fact that the transmission paths for NR transmission and DSRC transmission are shared and NR transmission is given priority. The DSRC CCA may be delayed based at least in part on a "channel busy" condition (as shown by reference numeral 940) that simulates a DSRC channel access controller or EDCA (which may be disconnected from the actual CCA measurement at the physical layer). The DSRC CCA may be delayed until the NR transmission session is completed, and the DSRC transmission may be configured after (e.g., immediately after) the NR transmission session is completed.

[0131] As shown by reference numeral 930, the DSRC transmit configuration may be restored. The DSRC transmit configuration may be restored based at least in part on the completion of the NR transmit session. Once the NR transmit session is completed and the DSRC transmit is configured, the CCA may switch back to performing the actual physical channel sensing and the DSRC transmit session may continue as usual. As shown by reference numeral 935, the DSRC transmit session may be restored. In some aspects, DSRC ACK transmissions (for unicast packets) that overlap with the effective time of the NR transmit session (NR transmit configuration + NR transmit timeslot + DSRC transmit configuration) may be discarded. The DSRC ACK transmissions may be discarded based at least in part on the assumption that the DSRC ACK transmissions cannot be delayed.

[0132] As indicated above, Fig. 9 are provided as examples. Other examples can be found in relation to Fig. 9 The examples described are different.

[0133] Fig.10 1000 is a diagram illustrating an example of overlapping DSRC and NR communications according to the present disclosure. As shown by reference numeral 1005, an MSDU packet (associated with a DSRC transmission) may be prepared for the MAC layer. As shown by reference numeral 1010, a UE 120 may perform a DSRC transmission configuration. As shown by reference numeral 1015, a DSRC transmission session may be initiated and may last for a certain duration.

[0134] As indicated by reference numeral 1020, NR transmit scheduling may occur at time slot n. NR transmit scheduling may overlap with an ongoing DSRC transmit session. As indicated by reference numeral 1025, a DSRC transmit session / channel contention attempt may be stopped or delayed based at least in part on the NR transmit being scheduled and until the NR transmit session is completed. This may assume that a PPDU transmission has not yet been initiated.

[0135] As indicated by reference numeral 1030, the DSRC transmit session may be stopped or delayed based at least in part on a "channel busy" condition emulating DSRC EDCA until the NR transmit session is completed. As indicated by reference numeral 1035, the UE 120 may perform NR transmit configuration at time slot n+2. As indicated by reference numeral 1040, the UE 120 may perform NR transmission at time slot n+3.

[0136] As indicated by reference numeral 1045, DSRC transmission may be configured based at least in part on the completion of NR transmission. As indicated by reference numeral 1050, once the NR transmission session is completed and DSRC transmission is configured, CCA may switch back to actual physical channel sensing and the UE 120 may continue the DSRC transmission session as usual with the same EDCAF parameters (such as the same random access (RA) backoff (BO) counter value and codeword (CW) size, etc.) as before the time when DSRC transmission was stopped. In some aspects, DSRC ACK transmissions (for unicast packets) that overlap with the valid time of the NR transmission session (NR transmission configuration + NR transmission slot + DSRC transmission configuration) may be discarded. The DSRC ACK transmissions may be discarded based at least in part on the assumption that the DSRC ACK transmissions cannot be delayed.

[0137] In some aspects, if a DSRC PPDU transmission has been triggered by EDCA (e.g., before the NR transmission is scheduled at time slot n), the DSRC transmission may be performed, and the NR transmission may be dropped if the PPDU transmission overlaps with the NR transmission configuration time slot 1035. The PPDU transmission duration (e.g., at least one of the MPDU header fields) may be known in advance by the transmitter.

[0138] As indicated above, Fig.10 are provided as examples. Other examples can be found in relation to Fig.10 The examples described are different.

[0139] Fig.11 is a diagram illustrating an example process 1100 performed, for example, by a UE in accordance with the present disclosure. Example process 1100 is an example of a UE (eg, UE 120) performing operations associated with concurrent transmission scheduling and prioritization.

[0140] like Fig.11 As shown, in some aspects, process 1100 may include obtaining one or more joint scheduling rules associated with LTE communication and NR communication in a half-duplex communication system (block 1110). For example, a UE (e.g., using Fig.13 The communication manager 140 and / or obtaining component 1308 depicted in FIG. 1 may obtain one or more joint scheduling rules associated with LTE communication and NR communication in a half-duplex communication system, as described above.

[0141] like Fig.11 As further shown, in some aspects, process 1100 may include identifying a CBR associated with a half-duplex communication system (block 1120). For example, a UE (eg, using Fig.13 The communication manager 140 and / or identification component 1310 depicted in FIG. 1 may identify a CBR associated with a half-duplex communication system, as described above.

[0142] like Fig.11 As further shown, in some aspects, process 1100 may include prioritizing LTE communications or NR communications based at least in part on one or more joint scheduling rules and CBR (block 1130). For example, a UE (e.g., using Fig.13 The communication manager 140 and / or the prioritization component 1312 depicted in FIG. 1 may prioritize LTE communications or NR communications based at least in part on one or more joint scheduling rules and CBR, as described above.

[0143] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0144] In a first aspect, at least one of LTE communication and NR communication is V2X communication.

[0145] In a second aspect, alone or in combination with the first aspect, the LTE communication is a cellular V2X communication and the NR communication is another cellular V2X communication.

[0146] In a third aspect, alone or in combination with one or more of the first and second aspects, identifying a CBR associated with the half-duplex communication system includes determining that the CBR associated with the half-duplex communication system does not satisfy a low CBR threshold.

[0147] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, one or more joint scheduling rules indicate combining LTE communications and NR communications using time division multiplexing (TDM) operations based at least in part on a CBR associated with a half-duplex communication system not satisfying a low CBR threshold.

[0148] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 1100 includes sending LTE communications and NR communications using TDM operations based at least in part on one or more joint scheduling rules.

[0149] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, it also includes identifying a joint free transmission resource selection across LTE communication and NR communication in a half-duplex communication system.

[0150] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, identifying a CBR associated with the half-duplex communication system comprises determining that the CBR associated with the half-duplex communication system satisfies a low CBR threshold but does not satisfy a high CBR threshold.

[0151] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, one or more joint scheduling rules indicate prioritizing safety-related communications over non-safety-related communications.

[0152] In a ninth aspect, either alone or in combination with one or more of aspects 1 to 8, prioritizing LTE communications or NR communications includes prioritizing LTE receptions based at least in part on whether the LTE receptions are safety-related receptions or high priority receptions.

[0153] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, prioritizing LTE reception includes extending one or more resources from an NR free resource pool to enable time division multiplexing operation indicating prioritization of LTE reception.

[0154] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, prioritizing LTE communications or NR communications includes prioritizing NR receptions based at least in part on whether the NR receptions are safety-related receptions or high priority receptions.

[0155] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, prioritizing NR reception includes extending one or more resources from an LTE free resource pool to enable time division multiplexing operation indicating prioritization of NR reception.

[0156] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, identifying a CBR associated with the half-duplex communication system comprises determining that the CBR associated with the half-duplex communication system satisfies a high CBR threshold.

[0157] In a fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, a CBR associated with a half-duplex communication system satisfies a high CBR threshold indicating high traffic congestion conditions for both LTE communications and NR communications.

[0158] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, prioritizing LTE communications or NR communications includes prioritizing LTE receptions based at least in part on whether the LTE receptions are safety-related receptions or high priority receptions, and discarding or delaying NR communications.

[0159] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, discarding or delaying NR communication includes discarding or delaying NR communication before the NR communication and at least in part based on the scheduling indication.

[0160] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, discarding or delaying NR communication includes discarding or delaying NR transmission and NR reception.

[0161] In an eighteenth aspect, either alone or in combination with one or more of aspects one to seventeen, prioritizing LTE communications or NR communications includes prioritizing BR receptions based at least in part on whether the NR receptions are safety-related receptions or high priority receptions, and discarding or delaying LTE communications.

[0162] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, dropping or delaying the LTE communication includes dropping or delaying the LTE communication prior to the LTE communication and based at least in part on the scheduling indication.

[0163] In a twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, dropping or delaying LTE communications includes dropping or delaying LTE transmission and LTE reception.

[0164] although Fig.11 Example blocks of process 1100 are shown, but in some aspects, process 1100 may include Fig.11 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1100 may be performed in parallel.

[0165] Fig.12 is a diagram illustrating an example process 1200 performed, for example, by a UE according to the present disclosure. Example process 1200 is an example of a UE (eg, UE 120) performing operations associated with concurrent transmission scheduling and prioritization.

[0166] like Fig.12 As shown, in some aspects, process 1200 may include identifying overlap between NR transmissions and DSRC transmissions (block 1210). For example, a UE (e.g., using Fig.13 The communication manager 140 and / or identification component 1310 depicted in FIG. 1 may identify overlaps between NR transmissions and DSRC transmissions, as described above.

[0167] like Fig.12 As further shown, in some aspects, process 1200 may include obtaining one or more rules for prioritizing NR transmissions or DSRC transmissions based at least in part on overlap between the NR transmissions and the DSRC transmissions (block 1220). Fig.13The communication manager 140 and / or the prioritization component 1312 depicted in FIG. 1 may obtain one or more rules for prioritizing NR transmissions or DSRC transmissions based at least in part on overlap between NR transmissions and DSRC transmissions, as described above.

[0168] like Fig.12 As further shown, in some aspects, process 1200 may include sending at least one of an NR transmission or a DSRC transmission based at least in part on one or more rules (block 1230). For example, a UE (e.g., using Fig.13 The communication manager 140 and / or the transmitting component 1304 depicted in FIG. 1 may transmit at least one of the NR transmission or the DSRC transmission based at least in part on one or more rules, as described above.

[0169] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0170] In a first aspect, the overlap between the NR transmission and the DSRC transmission is at least a partial overlap between an NR transmission session including the NR transmission and a DSRC transmission session including the DSRC transmission.

[0171] In a second aspect, either alone or in combination with the first aspect, the NR transmission is a cellular vehicle network transmission.

[0172] In a third aspect, alone or in combination with one or more of the first and second aspects, the NR transmission and the DSRC transmission are time division multiplexed transmissions.

[0173] In a fourth aspect, alone or in combination with one or more of the first to third aspects, NR transmission is associated with a fixed transmission time and DSRC transmission is not associated with a fixed transmission time, and DSRC transmission can be delayed but NR transmission cannot be delayed.

[0174] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, one or more rules indicate that NR transmissions are to take precedence over DSRC transmissions.

[0175] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, NR transmissions are scheduled before DSRC transmissions.

[0176] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 1200 includes delaying a DSRC transmission session including a DSRC transmission until the NR transmission is complete.

[0177] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 1200 includes obtaining an indication that a DSRC MSDU packet has entered an EDCA transmission queue; obtaining an indication that an NR transmission session including an NR transmission is in progress; and delaying a DSRC CCA process at least in part based on a channel busy condition of an emulated DSRC channel access controller or an EDCA scheduler until the NR transmission is complete.

[0178] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, process 1200 includes performing a DSRC transmission configuration at least in part based on the completion of the NR transmission.

[0179] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 1200 includes switching a CCA process to a physical channel sensing mode at least in part based on the completion of the NR transmission, and initiating a DSRC transmission session.

[0180] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 1200 includes discarding a DSRC acknowledgment transmission that overlaps with the active time of an NR transmission session.

[0181] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, a DSRC acknowledgment transmission is associated with a unicast reception.

[0182] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, a DSRC transmission is scheduled before an NR transmission.

[0183] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, process 1200 includes stopping an ongoing DSRC transmission session, delaying an ongoing DSRC transmission session, or allowing an ongoing DSRC transmission session and delaying future DSRC transmission sessions at least in part based on an overlap between a DSRC transmission session and an NR transmission session including an NR transmission.

[0184] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, stopping an ongoing DSRC transmission session, delaying an ongoing DSRC transmission session, or allowing an ongoing DSRC transmission session and delaying future DSRC transmission sessions includes emulating a channel busy condition of a DSRC channel access controller or an EDCA transmission scheduler until the NR transmission is complete.

[0185] In a sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, process 1200 includes switching a CCA process to actual physical channel sensing based at least in part on NR transmission completion, and continuing the DSRC transmission session.

[0186] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, continuing the DSRC transmission session includes continuing the DSRC transmission session using the same EDCAF parameters as before stopping or delaying the DSRC transmission session.

[0187] In an eighteenth aspect, either alone or in combination with one or more of the first to seventeenth aspects, process 1200 includes discarding a DSRC confirmation transmission that overlaps with a valid time of an NR transmission session.

[0188] In a nineteenth aspect, either alone or in combination with one or more of the first to eighteenth aspects, the DSRC confirmation transmission is associated with unicast reception.

[0189] In a twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, process 1200 includes discarding an NR transmission based at least in part on a DSRC physical layer PPDU being triggered prior to an NR transmission session including the NR transmission.

[0190] In a twenty-first aspect, either alone or in combination with one or more of the first to twentieth aspects, one or more rules indicate prioritizing DSRC transmissions based at least in part on being a particular type of transmission.

[0191] In a twenty-second aspect, either alone or in combination with one or more of the first to twenty-first aspects, process 1200 includes transmitting a DSRC transmission based at least in part on the DSRC transmission being a particular type of transmission, and discarding the NR transmission.

[0192] In a twenty-third aspect, either alone or in combination with one or more of the first to twenty-second aspects, the specific type of transmission is a safety-related transmission or a critical message-related transmission.

[0193] In a twenty-fourth aspect, either alone or in combination with one or more of aspects one to twenty-third, one or more rules indicate prioritizing NR transmissions or DSRC transmissions based at least in part on the priority of the NR transmissions or DSRC transmissions.

[0194] In a twenty-fifth aspect, either alone or in combination with one or more of aspects one to twenty-four, process 1200 includes sending an NR transmission based at least in part on the NR transmission having a higher priority than the DSRC transmission, and discarding or delaying the DSRC transmission based at least in part on the DSRC transmission having a lower priority than the NR transmission.

[0195] In a twenty-sixth aspect, either alone or in combination with one or more of aspects one to twenty-fifth, process 1200 includes sending a DSRC transmission based at least in part on the DSRC transmission having a higher priority than the NR transmission, and discarding or delaying the NR transmission based at least in part on the NR transmission having a lower priority than the DSRC transmission.

[0196] although Fig.12 An example block diagram of process 1200 is shown, but in some aspects, process 1200 may include Fig.12 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1200 may be performed in parallel.

[0197] Fig.13 1 is a diagram of an example device 1300 for wireless communication according to the present disclosure. The device 1300 may be a UE, or the UE may include the device 1300. In some aspects, the device 1300 includes a receiving component 1302 and a sending component 1304, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the device 1300 may communicate with another device 1306 (such as a UE, a base station, or another wireless communication device) using the receiving component 1302 and the sending component 1304. As further shown, the device 1300 may include a communication manager 140. The communication manager 140 may include one or more of an acquisition component 1308, an identification component 1310, a priority sorting component 1312, or a switching component 1314, etc.

[0198] In some aspects, the apparatus 1300 may be configured to perform the Figures 7 to 10 Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Fig.11 Process 1100, Fig.12 In some aspects, Fig.13 The device 1300 and / or one or more components shown may include a combination of Figure 2 One or more components of the UE. Additionally or alternatively, Fig.13 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0199] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1306. The receiving component 1302 may provide the received communications to one or more other components of the device 1300. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1300. In some aspects, the receiving component 1302 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the UE.

[0200] Transmit component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1306. In some aspects, one or more other components of device 1300 may generate communications and may provide the generated communications to transmit component 1304 for transmission to device 1306. In some aspects, transmit component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1306. In some aspects, transmit component 1304 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0201] The obtaining component 1308 can obtain one or more joint scheduling rules associated with LTE communication and NR communication in the half-duplex communication system. The identifying component 1310 can identify a CBR associated with the half-duplex communication system. The prioritization component 1312 can prioritize LTE communication or NR communication based at least in part on the one or more joint scheduling rules and the CBR. The sending component 1304 can send the LTE communication and the NR communication using TDM operation based at least in part on the one or more joint scheduling rules.

[0202] The identifying component 1310 can identify an overlap between the NR transmission and the DSRC transmission. The obtaining component 1308 can obtain one or more rules for prioritizing the NR transmission or the DSRC transmission based at least in part on the overlap between the NR transmission and the DSRC transmission. The transmitting component 1304 can transmit at least one of the NR transmission or the DSRC transmission based at least in part on the one or more rules.

[0203] The prioritization component 1312 may delay a DSRC transmission session including a DSRC transmission until the NR transmission is completed. The obtaining component 1308 may obtain an indication that a DSRC medium access control service data unit (MSDU) packet has entered an enhanced distributed channel access (EDCA) transmission queue. The obtaining component 1308 may obtain an indication that an NR transmission session including an NR transmission is ongoing. The prioritization component 1312 may delay the DSRC CCA process until the NR transmission is completed based at least in part on a channel busy condition simulating a DSRC channel access controller or an EDCA scheduler. The transmission component 1304 may perform DSRC transmission configuration based at least in part on the completion of the NR transmission. The switching component 1314 may switch the CCA process to a physical channel sensing mode based at least in part on the completion of the NR transmission and initiate a DSRC transmission session.

[0204] The prioritization component 1312 may discard DSRC confirmation transmissions that overlap with the effective time of the NR transmission session. The prioritization component 1312 may stop the ongoing DSRC transmission session, delay the ongoing DSRC transmission session, or allow the ongoing DSRC transmission session and delay the future DSRC transmission session based at least in part on the DSRC transmission session overlapping the NR transmission session including the NR transmission. The switching component 1314 may switch the idle channel assessment (CCA) process to the actual physical channel sensing based at least in part on the NR transmission completion, and continue the DSRC transmission session. The prioritization component 1312 may discard DSRC confirmation transmissions that overlap with the effective time of the NR transmission session. The prioritization component 1312 may discard NR transmissions based at least in part on the DSRC PPDU being triggered before the NR transmission session including the NR transmission. The transmission component 1304 may transmit the DSRC transmission based at least in part on the DSRC transmission being a specific type of transmission, and discard the NR transmission. The transmitting component 1304 may transmit the NR transmission based at least in part on the NR transmission having a higher priority than the DSRC transmission, and may discard or delay the DSRC transmission based at least in part on the DSRC transmission having a lower priority than the NR transmission. The transmitting component 1304 may transmit the DSRC transmission based at least in part on the DSRC transmission having a higher priority than the NR transmission, and may discard or delay the NR transmission based at least in part on the NR transmission having a lower priority than the DSRC transmission.

[0205] Fig.13 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.13 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.13 Two or more components shown may be implemented in a single component, or Fig.13 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.13 The assembly of (one or more) components shown may be described as being executable by Fig.13 Another collection of components shown performs one or more functions.

[0206] The following provides an overview of some aspects of the disclosure:

[0207] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: obtaining one or more joint scheduling rules associated with long term evolution (LTE) communication and new radio (NR) communication in a half-duplex communication system; identifying a channel busy rate (CBR) associated with the half-duplex communication system; and prioritizing LTE communication or NR communication based at least in part on the one or more joint scheduling rules and the CBR.

[0208] Aspect 2: The method according to aspect 1, wherein at least one of the LTE communication and the NR communication is vehicle-to-everything (V2X) communication.

[0209] Aspect 3: The method according to aspect 2, wherein the LTE communication is a cellular V2X communication, and the NR communication is another cellular V2X communication.

[0210] Aspect 4: The method according to any one of aspects 1 to 3, wherein identifying the CBR associated with the half-duplex communication system comprises determining that the CBR associated with the half-duplex communication system does not satisfy a low CBR threshold.

[0211] Aspect 5: A method according to aspect 4, wherein the one or more joint scheduling rules indicate combining the LTE communication and the NR communication using time division multiplexing (TDM) operation based at least in part on the CBR associated with the half-duplex communication system not satisfying the low CBR threshold.

[0212] Aspect 6: The method according to aspect 5 also includes sending the LTE communication and the NR communication using the TDM operation based at least in part on the one or more joint scheduling rules.

[0213] Aspect 7: The method according to Aspect 5, further comprising identifying a joint free transmission resource selection across the LTE communication and the NR communication in the half-duplex communication system.

[0214] Aspect 8: The method according to any one of aspects 1 to 7, wherein identifying the CBR associated with the half-duplex communication system includes determining that the CBR associated with the half-duplex communication system satisfies a low CBR threshold but does not satisfy a high CBR threshold.

[0215] Aspect 9: The method according to aspect 8, wherein the one or more joint scheduling rules indicate that safety-related communications are prioritized over non-safety-related communications.

[0216] Aspect 10: The method of aspect 9, wherein prioritizing the LTE communication or the NR communication comprises prioritizing the LTE reception based at least in part on whether the LTE reception is a safety-related reception or a high priority reception.

[0217] Aspect 11: The method according to aspect 10, wherein prioritizing the LTE reception includes extending one or more resources from an NR free resource pool to enable time division multiplexing operation indicating prioritizing the LTE reception.

[0218] Aspect 12: The method according to aspect 9, wherein prioritizing the LTE communication or the NR communication includes prioritizing the NR reception based at least in part on whether the NR reception is a safety-related reception or a high priority reception.

[0219] Aspect 13: The method according to aspect 12, wherein prioritizing the NR reception includes extending one or more resources from an LTE free resource pool to enable time division multiplexing operation indicating prioritizing the NR reception.

[0220] Aspect 14: The method according to any one of aspects 1 to 13, wherein identifying the CBR associated with the half-duplex communication system comprises determining that the CBR associated with the half-duplex communication system satisfies a high CBR threshold.

[0221] Aspect 15: The method according to aspect 14, wherein the CBR associated with the half-duplex communication system satisfies the high CBR threshold to indicate high traffic congestion conditions for both the LTE communication and the NR communication.

[0222] Aspect 16: A method according to Aspect 14, wherein prioritizing the LTE communication or the NR communication includes prioritizing the LTE reception at least in part based on whether the LTE reception is a safety-related reception or a high priority reception, and discarding or delaying the NR communication.

[0223] Aspect 17: The method according to aspect 16, wherein discarding or delaying the NR communication includes discarding or delaying the NR communication before the NR communication and based at least in part on the scheduling indication.

[0224] Aspect 18: The method according to Aspect 16, wherein discarding or delaying the NR communication includes discarding or delaying NR transmission and NR reception.

[0225] Aspect 19: A method according to Aspect 14, wherein prioritizing the LTE communication or the NR communication includes prioritizing the NR reception at least in part based on whether the NR reception is a safety-related reception or a high priority reception, and discarding or delaying the LTE communication.

[0226] Aspect 20: The method of aspect 19, wherein dropping or delaying the LTE communication comprises dropping or delaying the LTE communication prior to the LTE communication and based at least in part on a scheduling indication.

[0227] Aspect 21: The method according to aspect 19, wherein dropping or delaying the LTE communication includes dropping or delaying LTE transmission and LTE reception.

[0228] Aspect 22: A method of wireless communication performed by a user equipment (UE), the method comprising: identifying an overlap between a new radio (NR) transmission and a dedicated short range communication (DSRC) transmission; obtaining one or more rules for prioritizing the NR transmission or the DSRC transmission based at least in part on the overlap between the NR transmission and the DSRC transmission; and sending at least one of the NR transmission or the DSRC transmission based at least in part on the one or more rules.

[0229] Aspect 23: The method according to Aspect 22, wherein the overlap between the NR transmission and the DSRC transmission is at least a partial overlap between an NR transmission session including the NR transmission and a DSRC transmission session including the DSRC transmission.

[0230] Aspect 24: A method according to any one of Aspects 22 to 23, wherein the NR transmission is a cellular vehicle network transmission.

[0231] Aspect 25: A method according to any one of Aspects 22 or 24, wherein the NR transmission and the DSRC transmission are time division multiplexed transmissions.

[0232] Aspect 26: A method according to any one of Aspects 22 to 25, wherein the NR transmission is associated with a fixed transmission time and the DSRC transmission is not associated with a fixed transmission time, and wherein the DSRC transmission can be delayed but the NR transmission cannot be delayed.

[0233] Aspect 27: A method according to any one of Aspects 22 to 26, wherein the one or more rules indicate that the NR transmission is to take precedence over the DSRC transmission.

[0234] Aspect 28: The method according to aspect 27, wherein the NR transmission is scheduled before the DSRC transmission.

[0235] Aspect 29: The method according to Aspect 28 further includes delaying a DSRC transmission session including the DSRC transmission until the NR transmission is completed.

[0236] Aspect 30: The method according to Aspect 29 further includes obtaining an indication that a DSRC medium access control service data unit (MSDU) packet has entered an enhanced distributed channel access (EDCA) transmission queue; obtaining an indication that an NR transmission session including the NR transmission is in progress; and delaying a DSRC clear channel assessment (CCA) process based at least in part on a channel busy condition of a simulated DSRC channel access controller or EDCA scheduler until the NR transmission is completed.

[0237] Aspect 31: The method according to aspect 30 further includes performing DSRC transmission configuration based at least in part on the completion of the NR transmission.

[0238] Aspect 32: The method according to aspect 31 also includes switching the CCA process to a physical channel sensing mode based at least in part on the completion of the NR transmission, and initiating the DSRC transmission session.

[0239] Aspect 33: The method according to Aspect 32 further includes discarding DSRC confirmation transmission that overlaps with the valid time of the NR transmission session.

[0240] Aspect 34: The method according to aspect 33, wherein the DSRC confirmation transmission is associated with unicast reception.

[0241] Aspect 35: A method according to aspect 28, wherein the DSRC transmission is scheduled before the NR transmission.

[0242] Aspect 36: The method according to Aspect 35 also includes stopping the ongoing DSRC transmission session, delaying the ongoing DSRC transmission session, or allowing the ongoing DSRC transmission session and delaying future DSRC transmission sessions based at least in part on the DSRC transmission session overlapping with the NR transmission session including the NR transmission.

[0243] Aspect 37: A method according to Aspect 36, wherein stopping the ongoing DSRC transmission session, delaying the ongoing DSRC transmission session, or allowing the ongoing DSRC transmission session and delaying the future DSRC transmission session includes simulating a channel busy condition of a DSRC channel access controller or an enhanced distributed channel access (EDCA) transmission scheduler until the NR transmission is completed.

[0244] Aspect 38: The method according to aspect 36 further includes switching a clear channel assessment (CCA) process to actual physical channel sensing based at least in part on the NR transmission completion, and continuing the DSRC transmission session.

[0245] Aspect 39: The method according to aspect 38, wherein continuing the DSRC transmission session includes continuing the DSRC transmission session using the same enhanced digital channel access function (EDCAF) parameters as before stopping or delaying the DSRC transmission session.

[0246] Aspect 40: The method according to Aspect 38 further includes discarding DSRC confirmation transmissions that overlap with the valid time of the NR transmission session.

[0247] Aspect 41: The method according to aspect 40, wherein the DSRC confirmation transmission is associated with unicast reception.

[0248] Aspect 42: The method of aspect 35 further comprises discarding the NR transmission based at least in part on a DSRC physical layer protocol data unit (PPDU) being triggered prior to an NR transmission session including the NR transmission.

[0249] Aspect 43: The method according to any one of aspects 22 to 42, wherein the one or more rules indicate prioritizing the DSRC transmission based at least in part on the DSRC transmission being a particular type of transmission.

[0250] Aspect 44: The method according to Aspect 43 further includes transmitting the DSRC transmission based at least in part on the DSRC transmission being the specific type of transmission, and discarding the NR transmission.

[0251] Aspect 45: The method according to aspect 43, wherein the specific type of transmission is a security-related transmission or a critical message-related transmission.

[0252] Aspect 46: The method according to any one of aspects 22 to 45, wherein the one or more rules indicate prioritizing the NR transmission or the DSRC transmission at least partially based on the priority of the NR transmission or the DSRC transmission.

[0253] Aspect 47: The method according to aspect 46, further comprising transmitting the NR transmission at least partially based on the NR transmission having a higher priority than the DSRC transmission, and discarding or delaying the DSRC transmission at least partially based on the DSRC transmission having a lower priority than the NR transmission.

[0254] Aspect 48: The method according to aspect 46, further comprising transmitting the DSRC transmission at least partially based on the DSRC transmission having a higher priority than the NR transmission, and discarding or delaying the NR transmission at least partially based on the NR transmission having a lower priority than the DSRC transmission.

[0255] Aspect 49: An apparatus for wireless communication at a device, the apparatus comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 1 to 48.

[0256] Aspect 50: A device for wireless communication, the device comprising a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 48.

[0257] Aspect 51: 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 48.

[0258] Aspect 52: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 48.

[0259] Aspect 53: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, 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 48.

[0260] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0261] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0262] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0263] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of each aspect. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of each aspect includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes 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 with 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).

[0264] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one project is intended to be referred to, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus include: Memory; as well as one or more processors coupled to the memory and configured to: obtaining one or more joint scheduling rules associated with long term evolution (LTE) communications and new radio (NR) communications in a half-duplex communication system; identifying a channel busy rate (CBR) associated with the half-duplex communication system; and Prioritize LTE communications or NR communications based at least in part on the one or more joint scheduling rules and the CBR.

2. The apparatus of claim 1, wherein at least one of the LTE communication and the NR communication is vehicle-to-everything (V2X) communication.

3. The apparatus of claim 1, wherein to identify the CBR associated with the half-duplex communication system, the one or more processors are configured to determine that the CBR associated with the half-duplex communication system does not satisfy a low CBR threshold.

4. The apparatus of claim 3, wherein the one or more joint scheduling rules indicate combining the LTE communication and the NR communication using time division multiplexing (TDM) operation based at least in part on the CBR associated with the half-duplex communication system not satisfying the low CBR threshold.

5. The apparatus of claim 4, wherein the one or more processors are further configured to transmit the LTE communications and the NR communications using the TDM operation based at least in part on the one or more joint scheduling rules.

6. The apparatus of claim 1, wherein to identify the CBR associated with the half-duplex communication system, the one or more processors are configured to determine that the CBR associated with the half-duplex communication system satisfies a low CBR threshold but does not satisfy a high CBR threshold. 7 . The apparatus of claim 6 , wherein the one or more joint scheduling rules indicate prioritizing safety-related communications over non-safety-related communications.

8. The apparatus of claim 7, wherein to prioritize the LTE communications or the NR communications, the one or more processors are configured to prioritize the LTE reception based at least in part on whether the LTE reception is a safety-related reception or a high priority reception.

9. The apparatus of claim 7, wherein, to prioritize the LTE communications or the NR communications, the one or more processors are configured to prioritize the NR reception based at least in part on whether the NR reception is a safety-related reception or a high priority reception.

10. The apparatus of claim 1, wherein to identify the CBR associated with the half-duplex communication system, the one or more processors are configured to determine that the CBR associated with the half-duplex communication system satisfies a high CBR threshold.

11. The apparatus of claim 10, wherein the CBR associated with the half-duplex communication system satisfying the high CBR threshold indicates high traffic congestion conditions for both the LTE communication and the NR communication.

12. The apparatus of claim 10, wherein to prioritize the LTE communications or the NR communications, the one or more processors are configured to prioritize the LTE reception based at least in part on whether the LTE reception is a safety-related reception or a high priority reception, and to discard or delay the NR communication.

13. The apparatus of claim 10, wherein to prioritize the LTE communication or the NR communication, the one or more processors are configured to prioritize the NR reception based at least in part on whether the NR reception is a safety-related reception or a high priority reception, and to discard or delay the LTE communication.

14. An apparatus for wireless communication at a user equipment (UE), the apparatus include: Memory; as well as one or more processors coupled to the memory and configured to: Identify overlaps between New Radio (NR) transmissions and Dedicated Short Range Communications (DSRC) transmissions; obtaining one or more rules for prioritizing the NR transmissions or the DSRC transmissions based at least in part on the overlap between the NR transmissions and the DSRC transmissions; and At least one of the NR transmission or the DSRC transmission is transmitted based at least in part on the one or more rules.

15. The apparatus of claim 14, wherein the overlap between the NR transmission and the DSRC transmission is at least a partial overlap between an NR transmission session including the NR transmission and a DSRC transmission session including the DSRC transmission.

16. The apparatus of claim 14, wherein the NR transmission and the DSRC transmission are time division multiplexed transmissions.

17. The apparatus of claim 14, wherein the one or more rules indicate that the NR transmission is to take precedence over the DSRC transmission.

18. The apparatus of claim 17, wherein the NR transmission is scheduled before the DSRC transmission.

19. The apparatus of claim 18, wherein the one or more processors are further configured to delay a DSRC transmission session including the DSRC transmission until the NR transmission is completed.

20. The apparatus of claim 19, wherein the one or more processors are further configured to: Obtaining an indication that a DSRC medium access control service data unit (MSDU) packet has entered an enhanced distributed channel access (EDCA) transmit queue; obtaining an indication that an NR transmit session including the NR transmit is ongoing; and A DSRC clear channel assessment (CCA) procedure is delayed based at least in part on a channel busy condition simulating a DSRC channel access controller or an EDCA scheduler until the NR transmission is completed.

21. The apparatus of claim 20, wherein the one or more processors are further configured to perform DSRC transmission configuration based at least in part on the completion of the NR transmission.

22. The apparatus of claim 21 , wherein the one or more processors are further configured to switch the CCA process to a physical channel sensing mode and initiate the DSRC transmission session based at least in part on the completion of the NR transmission.

23. The apparatus of claim 18, wherein the DSRC transmission is scheduled before the NR transmission.

24. The apparatus of claim 23, wherein the one or more processors are further configured to stop an ongoing DSRC transmit session, delay the ongoing DSRC transmit session, or allow the ongoing DSRC transmit session and delay a future DSRC transmit session based at least in part on the DSRC transmit session overlapping an NR transmit session including the NR transmit.

25. The apparatus of claim 24, wherein in order to stop the ongoing DSRC transmission session, delay the ongoing DSRC transmission session, or allow the ongoing DSRC transmission session and delay the future DSRC transmission session, the one or more processors are configured to simulate a channel busy condition of a DSRC channel access controller or an enhanced distributed channel access (EDCA) transmission scheduler until the NR transmission is completed.

26. The apparatus of claim 24, wherein the one or more processors are further configured to switch a clear channel assessment (CCA) process to actual physical channel sensing based at least in part on the NR transmission completion, and to continue the DSRC transmission session.

27. The apparatus of claim 15, wherein the one or more rules indicate prioritizing the DSRC transmission based at least in part on whether the DSRC transmission is a safety-related transmission or a critical message-related transmission, and wherein the one or more processors are further configured to transmit the DSRC transmission and discard the NR transmission based at least in part on whether the DSRC transmission is the safety-related transmission or the critical message-related transmission.

28. The apparatus of claim 14, wherein the one or more rules indicate prioritizing the NR transmission or the DSRC transmission based at least in part on a priority of the NR transmission or the DSRC transmission, and wherein the one or more processors are further configured to: transmitting the NR transmission based at least in part on the NR transmission having a higher priority than the DSRC transmission, and discarding or delaying the DSRC transmission based at least in part on the DSRC transmission having a lower priority than the NR transmission; or The DSRC transmission is transmitted based at least in part on the DSRC transmission having a higher priority than the NR transmission, and the NR transmission is discarded or delayed based at least in part on the NR transmission having a lower priority than the DSRC transmission.

29. A method of wireless communication performed by a user equipment (UE), the method include: obtaining one or more joint scheduling rules associated with long term evolution (LTE) communications and new radio (NR) communications in a half-duplex communication system; identifying a channel busy rate (CBR) associated with the half-duplex communication system; and Prioritize LTE communications or NR communications based at least in part on the one or more joint scheduling rules and the CBR.

30. A method of wireless communication performed by a user equipment (UE), the method include: Identify overlaps between New Radio (NR) transmissions and Dedicated Short Range Communications (DSRC) transmissions; obtaining one or more rules for prioritizing the NR transmissions or the DSRC transmissions based at least in part on the overlap between the NR transmissions and the DSRC transmissions; and At least one of the NR transmission or the DSRC transmission is transmitted based at least in part on the one or more rules.

Images