Method and apparatus for prioritizing transmissions of various types of wireless communications

Abstract

A method and apparatus for prioritizing transmissions of various types of wireless communications are disclosed. Aspects described herein relate to prioritizing particular types of uplink communications, which may include: identifying a first priority level associated with sidelink traffic; identifying a second priority level associated with the uplink traffic; determining whether to prioritize the sidelink traffic or the uplink traffic based at least in part on comparing the first priority level with a second priority level; and transmitting at least one of the sidelink traffic or the uplink traffic based at least in part on determining whether the sidelink traffic or the uplink traffic is to be prioritized.

Description

[0001] This application is a divisional application of a Chinese invention patent application filed on June 23, 2020, with application number 202080051392.8 (international application number PCT / US2020 / 039170), and invention name “Method and device for prioritizing transmission of various types of wireless communications”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This patent application claims priority to provisional application No. 62 / 877,679, filed on July 23, 2019, entitled “TECHNIQUES FOR PRIORITIZING TRANSMISSION OF TYPES OF WIRELESS COMMUNICATIONS,” and U.S. patent application No. 16 / 834,748, filed on March 30, 2020, entitled “TECHNIQUES FOR PRIORITIZING TRANSMISSION OF TYPES OF WIRELESS COMMUNICATIONS,” the entire contents of which are expressly incorporated herein by reference. Technical Field

[0004] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly to techniques for prioritizing transmissions of particular types of wireless communications. Background Art

[0005] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, etc. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, and orthogonal frequency division multiple access (OFDMA) systems, and single-carrier frequency division multiple access (SC-FDMA) systems.

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. For example, the fifth generation (5G) wireless communication technology, which may be referred to as 5G New Radio (5G NR), is designed to expand and support diverse usage scenarios and applications relative to current mobile network generations. On the one hand, 5G communication technology may include: enhanced mobile broadband for human-centric use cases for accessing multimedia content, services, and data; ultra-reliable low latency communications (URLLC) with certain specifications on latency and reliability; and massive machine type communications, which may allow very large numbers of connected devices and the transmission of relatively small amounts of non-delay sensitive information.

[0007] Some wireless communication networks include vehicle-based communication devices that can communicate from vehicle to vehicle (V2V), vehicle to infrastructure (V2I) (e.g., from vehicle-based communication devices to road infrastructure nodes), vehicle to network (V2N) (e.g., from vehicle-based communication devices to one or more network nodes, such as base stations), combinations thereof, and / or with other devices, which can be collectively referred to as vehicle-to-everything (V2X) communications. Thus, user equipment (UE) can be configured to transmit a variety of different types of traffic. Summary of the invention

[0008] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not an exhaustive overview of all conceived aspects, and is neither intended to identify the key or critical elements of all aspects nor to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be presented later.

[0009] According to an example, a wireless communication method is provided. The method includes: identifying a first priority level associated with sidelink traffic at a media access control (MAC) layer; identifying a second priority level associated with uplink traffic; comparing the second priority level associated with the uplink traffic with an uplink threshold; determining whether to prioritize at least one of the sidelink traffic or the uplink traffic based at least in part on comparing the second priority level with the uplink threshold; and transmitting at least one of the sidelink traffic or the uplink traffic based at least in part on determining whether to prioritize the sidelink traffic or the uplink traffic.

[0010] One or more of the above examples may further include: wherein determining whether to prioritize the sidelink traffic or the uplink traffic includes: determining to prioritize the uplink traffic over the sidelink traffic based on determining that the second priority level for the uplink traffic is below the uplink threshold.

[0011] One or more of the above examples may further include: wherein determining whether to prioritize the sidelink traffic or the uplink traffic includes: determining to prioritize the sidelink traffic over the uplink traffic based on determining that the first priority level of the sidelink traffic is below the sidelink threshold.

[0012]

[0013] One or more of the above examples may further include: wherein determining to prioritize the sidelink traffic over the uplink traffic is further based on determining that a second priority level associated with the uplink traffic is not below an uplink threshold.

[0013] One or more of the above examples may further include: wherein determining whether to prioritize the sidelink traffic or the uplink traffic includes: giving priority to the uplink traffic over any sidelink traffic, or over any other type of uplink traffic when the uplink traffic includes at least one of random access channel traffic or emergency traffic.

[0014] One or more of the above examples may further include: wherein identifying a first priority level associated with side link traffic includes: identifying the first priority level as the highest logical channel priority among multiple logical channels in a MAC protocol data unit (PDU) associated with the side link traffic.

[0015]

[0013] One or more of the above examples may further include where identifying a second priority level associated with uplink traffic includes identifying the second priority level at a MAC layer as a logical channel priority of one or more logical channels in communications associated with the uplink traffic.

[0016]

[0013] One or more of the above examples may further include: wherein the transmitting includes transmitting one of the sidelink traffic or the uplink traffic based on determining to prioritize the sidelink traffic or the uplink traffic.

[0017] One or more of the above examples may further include: selecting at least one of a first power for transmitting sidelink traffic or a second power for transmitting uplink traffic based on determining whether to prioritize the sidelink traffic or the uplink traffic, wherein transmitting at least one of the sidelink traffic or the uplink traffic includes transmitting the sidelink traffic based on the first power and transmitting the uplink traffic based on the second power.

[0018] One or more of the above examples may further include receiving at least one of the first priority level or the second priority level via radio resource control (RRC) layer signaling.

[0019]

[0013] One or more of the above examples may further include: wherein the first priority level of the sidelink traffic is the same as a priority level indicated in a physical sidelink control channel (PSCCH).

[0020] One or more of the above examples may further include: identifying that the first priority level is a PC5 fifth generation (5G) quality of service (QoS) indicator (5QI) (PQI) based on sidelink traffic, or identifying that the second priority level is a PQI based on uplink traffic.

[0021] One or more of the above examples may further include: wherein the first priority level is a logical channel priority configured based on a PC5 fifth generation (5G) quality of service (QoS) indicator (5QI) (PQI) for sidelink traffic, and the second priority level is a logical channel priority based on the 5QI for uplink traffic.

[0022]

[0013] One or more of the above examples may further include: wherein the sidelink traffic and the uplink traffic correspond to separate radio access technologies, and wherein determining whether to prioritize the sidelink traffic or the uplink traffic is based at least in part on the separate radio access technologies.

[0023] According to an example, a device for wireless communication is provided, the device comprising a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled to the transceiver and the memory. The one or more processors are configured to: identify a first priority level associated with sidelink traffic at a MAC layer; identify a second priority level associated with uplink traffic; compare the second priority level associated with uplink traffic with an uplink threshold; determine whether to prioritize at least one of the sidelink traffic or the uplink traffic based at least in part on comparing the second priority level with the uplink threshold; and transmit at least one of the sidelink traffic or the uplink traffic based at least in part on determining whether to prioritize the sidelink traffic or the uplink traffic.

[0024]

[0013] One or more of the above examples may further include: wherein the one or more processors are configured to determine to prioritize uplink traffic over sidelink traffic based on determining that the second priority level for the uplink traffic is below the uplink threshold.

[0025]

[0013] One or more of the above examples may further include: wherein the one or more processors are configured to determine to prioritize sidelink traffic over uplink traffic based on determining that the first priority level of the sidelink traffic is below a sidelink threshold.

[0026]

[0013] One or more of the above examples may further include: wherein the one or more processors are configured to determine to prioritize sidelink traffic over uplink traffic based further on determining that a second priority level associated with the uplink traffic is not below an uplink threshold.

[0027] One or more of the above examples may further include: wherein the one or more processors are configured to determine whether to prioritize the side link traffic or the uplink traffic at least in part by: giving priority to the uplink traffic over any side link traffic, or over any other type of uplink traffic when the uplink traffic includes at least one of random access channel traffic or emergency traffic.

[0028] One or more of the above examples may further include: wherein the one or more processors are configured to identify a first priority level associated with side link traffic at least in part by identifying the first priority level as the highest logical channel priority among multiple logical channels in a MAC protocol data unit (PDU) associated with the side link traffic.

[0029] One or more of the above examples may further include: wherein the one or more processors are configured to identify a second priority level associated with uplink traffic at least in part by: identifying the second priority level at the MAC layer as a logical channel priority of one or more logical channels in communications associated with the uplink traffic.

[0030]

[0013] One or more of the above examples may further include: wherein the one or more processors are configured to transmit one of the sidelink traffic or the uplink traffic based on determining to prioritize the sidelink traffic or the uplink traffic.

[0031] According to another example, a device for wireless communication is provided, the device comprising: a device for identifying a first priority level associated with sidelink traffic at a MAC layer; a device for identifying a second priority level associated with uplink traffic; a device for comparing the second priority level associated with the uplink traffic with an uplink threshold; a device for determining whether to prioritize at least one of the sidelink traffic or the uplink traffic based at least in part on comparing the second priority level with the uplink threshold; and a device for transmitting at least one of the sidelink traffic or the uplink traffic based at least in part on determining whether to prioritize the sidelink traffic or the uplink traffic.

[0032]

[0013] One or more of the above examples may further include: wherein the means for determining determines to prioritize uplink traffic over sidelink traffic based on determining that the second priority level for the uplink traffic is below the uplink threshold.

[0033] One or more of the above examples may further include: wherein the device for determining determines to prioritize sidelink traffic over uplink traffic based on determining that a first priority level of the sidelink traffic is lower than a sidelink threshold and further based on determining that a second priority level associated with the uplink traffic is not lower than an uplink threshold.

[0034] One or more of the above examples may further include: wherein the means for determining prioritizes the uplink traffic over any side link traffic, or over any other type of uplink traffic, when the uplink traffic includes at least one of random access channel traffic or emergency traffic.

[0035] According to another example, a computer-readable medium including code executable by one or more processors for wireless communication is provided. The code includes code for the following operations: identifying a first priority level associated with sidelink traffic at a MAC layer; identifying a second priority level associated with uplink traffic; comparing the second priority level associated with the uplink traffic with an uplink threshold; determining whether to prioritize at least one of the sidelink traffic or the uplink traffic based at least in part on comparing the second priority level with the uplink threshold; and transmitting at least one of the sidelink traffic or the uplink traffic based at least in part on determining whether to prioritize the sidelink traffic or the uplink traffic.

[0036]

[0013] One or more of the above examples may further include: wherein the code for determining determines to prioritize uplink traffic over sidelink traffic based on determining that a second priority level for the uplink traffic is below an uplink threshold.

[0037] One or more of the above examples may further include: wherein the code for determining is based on determining that the first priority level of the sidelink traffic is lower than the sidelink threshold and further based on determining that the second priority level associated with the uplink traffic is not lower than the uplink threshold to determine that the sidelink traffic is to be prioritized over the uplink traffic.

[0038] One or more of the above examples may further include: wherein the code for determining prioritizes the uplink traffic over any side link traffic, or over any other type of uplink traffic when the uplink traffic includes at least one of random access channel traffic or emergency traffic.

[0039] To achieve the foregoing and related ends, the one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are merely indicative of several of the various ways in which the principles of the various aspects may be employed, and this description is intended to cover all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The disclosed aspects will be described below in conjunction with the accompanying drawings, which are provided to illustrate rather than limit the disclosed aspects, wherein like reference numerals designate like elements, and wherein:

[0041] Figure 1 An example of a wireless communication system according to various aspects of the present disclosure is illustrated;

[0042] Figure 2 is a block diagram illustrating an example of a UE according to various aspects of the present disclosure;

[0043] Figure 3 is a block diagram illustrating an example of a base station according to various aspects of the present disclosure;

[0044] Figure 4A is a flow chart illustrating an example of a method for prioritizing particular types of communications according to various aspects of the present disclosure;

[0045] Figure 4B is a flow chart illustrating an example of a method for prioritizing a particular type of communication based on comparing a priority level to a threshold value in accordance with various aspects of the present disclosure;

[0046] Figure 5 is a flow chart illustrating an example of a method for prioritizing a particular type of uplink communications according to various aspects of the present disclosure;

[0047] Figure 6An example of a system for configuring priorities regarding communications according to various aspects of the present disclosure is illustrated;

[0048] Figure 7 is a block diagram illustrating an example of a MIMO communication system including a base station and UEs according to various aspects of the present disclosure. DETAILED DESCRIPTION

[0049] Now, various aspects are described with reference to the accompanying drawings. In the following description, for the purpose of explanation, numerous specific details are set forth to provide a thorough understanding of one or more aspects. However, it is apparent that such aspects can be practiced without these specific details.

[0050] The described features generally relate to prioritizing specific types of traffic in wireless communications. For example, a user equipment (UE) may be configured for uplink communications with a base station and D2D communications with other UEs. D2D communications may include vehicle-to-vehicle (V2V) communications, vehicle-to-infrastructure (V2I) communications (e.g., from a vehicle-based communication device to a road infrastructure node), vehicle-to-network (V2N) communications (e.g., from a vehicle-based communication device to one or more network nodes, such as a base station), combinations thereof, and / or communications with other devices, which may be collectively referred to as vehicle-to-everything (V2X) communications. In V2X communications, vehicle-based communication devices may communicate with each other and / or with infrastructure nodes on sidelink channels. Although some concepts are generally described in terms of V2X communications / devices, these concepts may similarly be applied more generally to D2D communications / devices to achieve similar functionality.

[0051] In this example, the UE may determine to prioritize sidelink communications over uplink communications, or vice versa, as further described herein. For example, in 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE), multiple scenarios may be supported regarding the ability of a V2X device to simultaneously transmit uplink and sidelink communications. These scenarios may include a first scenario in which the uplink transmission and the sidelink transmission use separate transmit chains and separate power budgets; in this first scenario, prioritized communications may not be required. These scenarios may include a second scenario in which the uplink transmission and the sidelink transmission use separate transmit chains but share a power budget;

[0052] In this second scenario, prioritization can include power sharing between uplink and sidelink transmissions, where the transmissions overlap in time (e.g., but the UE may not be aware of the previous power sharing in the case of a look-ahead conflict and may use a conservative decision about power sharing (e.g., a worst-case assumption of always making power sharing)). These scenarios may include a third scenario in which the uplink transmission and the sidelink transmission share a transmit chain and a power budget; in this third scenario, prioritization can include dropping one transmission or the other. In one example, the configured priority threshold can be comparing the sidelink packet quality of service (QoS) to the uplink transmission, passing or yielding to the uplink transmission. In another example, exceptions may be made for certain transmissions, which always take precedence over the sidelink transmission (e.g., for random access channel (RACH) messages (such as message 1 and / or message 3), for physical uplink shared channel (PUSCH) transmissions for emergency protocol data unit (PDU) connections, etc.).

[0053] In addition, in LTE, the following operations may be performed: comparing the sidelink traffic to a predefined priority threshold; picking uplink traffic that always takes precedence over the sidelink traffic. In this example, the threshold may be configured low enough so that all uplink traffic is prioritized. In an example, the configuration of the sidelink SL ProSe per-packet priority (PPPP) threshold may only allow consideration of which sidelink traffic is important and which sidelink traffic is not important, but may not allow consideration of whether the uplink traffic is important. Therefore, in this example, some important uplink traffic may receive the same treatment as other uplink traffic when compared with the same sidelink traffic.

[0054] In the examples described herein, the UE may prioritize sidelink and / or uplink communications based on additional or different considerations (such as a priority level defined for the communication or a priority level defined for the corresponding logical channel), based on one or more rules for determining the priority of the type of communication (which may be configured by the base station or determined by the UE in other ways), etc. In another example, the priority may be determined based on the type of channel or signaling being transmitted. In another specific example, based on one or more rules for determining the priority (the one or more rules may be configured by the base station or determined by the UE in other ways), a specific type of traffic may be prioritized over other types of traffic. For example, the UE may determine to prioritize uplink ultra-reliable low latency communication (URLLC) traffic over sidelink and other uplink traffic. In any case, for example, prioritized communications may include transmitting these communications while discarding other communications in the same or similar time period, transmitting these communications using a higher transmit power than the transmit power used for other communications in the same or similar time period, etc.

[0055] The following will refer to Figure 1-Figure 7 The described features are presented in more detail.

[0056] As used in this application, the terms "component", "module", "system" and similar terms are intended to include computer-related entities, such as but not limited to hardware, software, a combination of hardware and software, or software in execution. For example, a component can be, but not limited to, a process, a processor, an object, an executable, a thread of execution, a program, and / or a computer running on a processor. As an illustration, both an application running on a computing device and the computing device can be a component. One or more components may reside in a process and / or a thread of execution, and a component may be localized on a computer and / or distributed between two or more computers. In addition, these components can be executed from various computer-readable media on which various data structures are stored. These components can communicate by means of local and / or remote processes, such as according to a signal having one or more data packets, such as data from a component that interacts with another component in a local system, a distributed system, and / or interacts with other systems across a network such as the Internet. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0057] The technology described herein can be used for various wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other systems. The terms "system" and "network" are usually used interchangeably. A CDMA system can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA). CDMA2000 covers IS-2000, IS-95 and IS-856 standards. IS-2000 versions 0 and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. A TDMA system can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA systems can implement technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM TMRadio technologies such as UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and Advanced LTE (LTE-A) are new UMTS versions that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization called the "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies, including cellular (e.g., LTE) communications on shared radio frequency spectrum bands. However, the following description describes an LTE / LTE-A system for example purposes, and LTE terminology is used in most of the following descriptions, but these techniques can also be applied to applications other than LTE / LTE-A (e.g., to fifth generation (5G) new radio (NR) networks or other next generation communication systems).

[0058] The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made to the functions and arrangements of the elements discussed without departing from the scope of the present disclosure. Various examples may appropriately omit, substitute, or add various procedures or components. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, features described with reference to some examples may be combined in other examples.

[0059] Various aspects or features will be presented in the form of systems that may include a number of devices, components, modules, and the like, etc. It should be understood and appreciated that the various systems may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Combinations of these approaches may also be used.

[0060] Figure 11 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) may include a base station 102, a UE 104, an evolved packet core (EPC) 160, and / or a 5G core (5GC) 190. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). The macro cell may include a base station. The small cell may include a femto cell, a pico cell, and a micro cell. In an example, the base station 102 may also include a gNB 180, as further described herein. In an example, some nodes of the wireless communication system may have a modem 240 and a communication component 242 for prioritizing a particular type of communication. In addition, some nodes may have a modem 340 and a scheduling component 342 for scheduling and / or indicating a priority regarding a particular type of communication, as described herein. Although UE 104 is shown as having a modem 240 and a communication component 242, and base station 102 is shown as having a modem 340 and a scheduling component 342, this is an illustrative example, and substantially any node or node type may include a modem 240 and a communication component 242 and / or a modem 340 and a scheduling component 342 to provide the corresponding functionality described herein.

[0061] The base station 102 configured for 4G LTE (which may be collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a backhaul link 132 (e.g., using an S1 interface). The base station 102 configured for 5G NR (which may be collectively referred to as the Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a backhaul link 184. The base station 102 may perform, among other functions, one or more of the following functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of alert messages. Base stations 102 may communicate with each other directly or indirectly (e.g., through EPC 160 or 5GC 190) over backhaul link 134 (e.g., using an X2 interface). Backhaul link 134 may be wired or wireless.

[0062] The base station 102 may communicate wirelessly with one or more UEs 104. Each base station 102 may provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group (which may be referred to as a closed subscriber group (CSG)). The communication link 120 between the base station 102 and the UE 104 may include an uplink (UL) (also known as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (DL) (also known as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. These communication links may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (e.g., for x component carriers) for transmission in the DL and / or UL direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) bandwidth. These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

[0063] In another example, some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0064] The wireless communication system may further include a Wi-Fi access point (AP) 150 communicating with a Wi-Fi station (STA) 152 in the 5 GHz unlicensed spectrum via a communication link 154. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) prior to communication to determine whether the channel is available.

[0065] The small cell 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed spectrum as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may boost the coverage of the access network and / or increase the capacity of the access network.

[0066] Whether a small cell 102' or a large cell (e.g., a macro base station), the base station 102 may include an eNB, a gB node (gNB), or other types of base stations. Some base stations (such as gNB 180) may operate in traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with UE 104. When gNB 180 operates in mmW or near mmW frequencies, gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can be extended down to 3 GHz frequencies with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands have extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range. The base station 102 referred to herein may include a gNB 180.

[0067] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may be in communication with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and for collecting eMBMS-related charging information.

[0068] 5GC 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. AMF 192 may be in communication with a unified data management (UDM) 196. AMF 192 may be a control node that processes signaling between UE 104 and 5GC 190. In general, AMF 192 may provide QoS flow and session management. User Internet Protocol (IP) packets (e.g., from one or more UEs 104) may be delivered via UPF 195. UPF 195 may provide UE IP address allocation for one or more UEs and other functions. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services.

[0069] A base station may also be referred to as a gNB, a Node B, an evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable term. Base station 102 provides an access point for UE 104 to EPC 160 or 5GC 190. Examples of UE 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, positioning systems (e.g., satellite, terrestrial), multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, robots, drones, industrial / manufacturing equipment, wearable devices (e.g., smart watches, smart clothing, smart glasses, virtual reality eyepieces, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), vehicles / vehicle equipment, meters (e.g., parking meters, electricity meters, gas meters, water meters, flow meters), gas pumps, large or small kitchen appliances, medical / health care equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some UE 104 may be referred to as IoT devices (e.g., meters, gas pumps, monitors, cameras, industrial / manufacturing equipment, appliances, vehicles, robots, drones, etc.). IoT UEs may include MTC / enhanced MTC (eMTC, also known as CAT-M, Cat M1) UEs, NB-IoT (also known as CAT NB1) UEs, and other types of UEs. In the present disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (further enhanced eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term.

[0070] In one example, referring to the D2D communication described above, where the devices are vehicles or otherwise vehicle-based devices, D2D communication between devices (e.g., on communication link 158) may be referred to as V2V communication, which is defined for 3GPP LTE and is being defined for 5G NR. When a vehicle or vehicle-based device communicates with other infrastructure nodes for vehicle-based communication (e.g., on a side link), this may be referred to as V2I communication. When a vehicle or vehicle-based device communicates with a base station 102 or other network node (e.g., on communication link 120), this may be referred to as V2N communication. The collection of V2V, V2I, V2N, and / or vehicle to everything else may be referred to as V2X communication.

[0071] In one example, UE 104 may be configured to communicate with other UEs / nodes on a sidelink channel (e.g., in D2D or V2X communications), and may be configured to communicate with base station 102 on an uplink channel. In this example, communication component 242 may determine a transmission to prioritize sidelink or uplink communications, as described herein. For example, sidelink transmissions and uplink transmissions may overlap in a shared component carrier (e.g., where corresponding channels use the same or overlapping component carriers). In some cases (e.g., where UE 104 may use different transmission chains), both transmissions may occur but may require a shared transmit power cap. In other cases (e.g., where UE 104 may use a single transmission chain), UE 104 may be able to select only one transmission. Therefore, communication component 242 may determine a priority regarding sidelink or uplink communications, as described herein, where the priority may result in selecting a transmit power or discarding a particular type of traffic, etc. In addition, in one example, communication component 242 can determine that a priority for a particular type of uplink traffic (e.g., URLLC) is higher than a priority for other types of uplink traffic. In one example, scheduling component 342 can configure one or more rules or other priority information to facilitate UE 104 to determine how to prioritize sidelink or uplink transmissions (and / or transmissions for a particular type of uplink traffic), as further described herein.

[0072] Now go to Figure 2-Figure 7 , various aspects are depicted with reference to one or more components and one or more methods that can perform the actions or operations described herein, where various aspects in dashed lines may be optional. Figure 6The operations described in the description are presented in a particular order and / or as being performed by example components, but it should be understood that the order of these actions and the components performing the actions may vary depending on the implementation. Moreover, it should be understood that the following actions, functions, and / or components described may be performed by a specially programmed processor, a processor executing specially programmed software or computer-readable media, or by any other combination of hardware components and / or software components capable of performing the described actions or functions.

[0073] refer to Figure 2 , an example of an implementation of the UE 104 may include various components, some of which have been described above and are further described herein, including components such as one or more processors 212 and memory 216 in communication via one or more buses 244 and a transceiver 202, which may operate in conjunction with a modem 240 and / or a communication component 242 for prioritizing particular types of communications, as described herein.

[0074] In one aspect, the one or more processors 212 may include the modem 240 and / or may be part of the modem 240 using one or more modem processors. Thus, various functions associated with the communication component 242 may be included in the modem 240 and / or the processor 212, and in one aspect, may be performed by a single processor, while in other aspects, different ones of these functions may be performed by a combination of two or more different processors. For example, in one aspect, the one or more processors 212 may include any one or any combination of the following: a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with the transceiver 202. In other aspects, some of the features of the one or more processors 212 and / or the modem 240 associated with the communication component 242 may be performed by the transceiver 202.

[0075] In addition, the memory 216 can be configured to store local versions of data and / or applications 275 used herein, or the communication component 242 and / or one or more subcomponents thereof executed by the at least one processor 212. The memory 216 may include any type of computer-readable medium usable by a computer or the at least one processor 212, such as a random access memory (RAM), a read-only memory (ROM), a tape, a magnetic disk, an optical disk, a volatile memory, a non-volatile memory, and any combination thereof. In one aspect, for example, when the UE 104 is operating the at least one processor 212 to execute the communication component 242 and / or one or more subcomponents thereof, the memory 216 may be a non-transitory computer-readable storage medium storing one or more computer-executable codes defining the communication component 242 and / or one or more subcomponents thereof and / or data associated therewith.

[0076] The transceiver 202 may include at least one receiver 206 and at least one transmitter 208. The receiver 206 may include hardware for receiving data, and / or software code executable by a processor, the code including instructions and stored in a memory (e.g., a computer-readable medium). The receiver 206 may be, for example, a radio frequency (RF) receiver. In one aspect, the receiver 206 may receive signals transmitted by at least one base station 102. Additionally, the receiver 206 may process such received signals and may also obtain measurements of the signals, such as, but not limited to, Ec / Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. The transmitter 208 may include hardware for transmitting data, and / or software code executable by a processor, the code including instructions and stored in a memory (e.g., a computer-readable medium). Suitable examples of the transmitter 208 may include, but are not limited to, an RF transmitter.

[0077] Also, in an aspect, the UE 104 may include an RF front end 288 that may operate in communication with the one or more antennas 265 and the transceiver 202 for receiving and transmitting radio transmissions, such as wireless communications transmitted by at least one base station 102 or wireless transmissions transmitted by the UE 104. The RF front end 288 may be connected to the one or more antennas 265 and may include one or more low noise amplifiers (LNAs) 290, one or more switches 292, one or more power amplifiers (PAs) 298, and one or more filters 296 for transmitting and receiving RF signals.

[0078] In one aspect, the LNA 290 can amplify the received signal to a desired output level. In one aspect, each LNA 290 can have a specified minimum and maximum gain value. In one aspect, the RF front end 288 can use one or more switches 292 to select a particular LNA 290 and its specified gain value based on the desired gain value for a particular application.

[0079] In addition, for example, one or more PAs 298 can be used by the RF front end 288 to amplify the signal to obtain an RF output at a desired output power level. In one aspect, each PA 298 can have a specified minimum and maximum gain value. In one aspect, the RF front end 288 can use one or more switches 292 to select a particular PA 298 and its specified gain value based on the desired gain value for a particular application.

[0080] In addition, for example, one or more filters 296 can be used by the RF front end 288 to filter the received signal to obtain the input RF signal. Similarly, in one aspect, for example, a corresponding filter 296 can be used to filter the output from the corresponding PA 298 to produce an output signal for transmission. In one aspect, each filter 296 can be connected to a specific LNA 290 and / or PA 298. In one aspect, the RF front end 288 can use one or more switches 292 to select a transmit or receive path using a specified filter 296, LNA 290, and / or PA 298 based on the configuration as specified by the transceiver 202 and / or the processor 212.

[0081] As such, the transceiver 202 may be configured to transmit and receive wireless signals through one or more antennas 265 via the RF front end 288. In an aspect, the transceiver may be tuned to operate at a specified frequency so that the UE 104 may communicate, for example, with one or more base stations 102 or one or more cells associated with the one or more base stations 102. In an aspect, the modem 240 may configure the transceiver 202 to operate at a specified frequency and power level based on, for example, a UE configuration of the UE 104 and a communication protocol used by the modem 240.

[0082] In one aspect, modem 240 may be a multi-band-multi-mode modem that may process digital data and communicate with transceiver 202 so that digital data is sent and received using transceiver 202. In one aspect, modem 240 may be multi-band and configured to support multiple frequency bands for a specific communication protocol. In one aspect, modem 240 may be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, modem 240 may control one or more components (e.g., RF front end 288, transceiver 202) of UE 104 to enable transmission and / or reception of signals from the network based on a specified modem configuration. In one aspect, modem configuration may be based on the mode of the modem and the frequency band used. In another aspect, modem configuration may be based on UE configuration information associated with UE 104, such as provided by the network during cell selection and / or cell reselection.

[0083] In one aspect, the communication component 242 may optionally include a priority determination component 252 for determining priorities for transmitting different types of communications, and / or a configuration receiving component 254 for receiving a configuration indicating one or more rules, thresholds, or other parameters related to determining priorities regarding different types of communications, as described herein.

[0084] In one aspect, processor 212 may correspond to combining Figure 7 Similarly, the memory 216 may correspond to one or more of the processors described in conjunction with the UE. Figure 7 The memory described by the UE in.

[0085] refer to Figure 3 , an example of an implementation of a base station 102 (e.g., base station 102 and / or gNB 180, as described above) may include various components, some of which have been described above, but also include components such as one or more processors 312 and memory 316 in communication via one or more buses 344 and a transceiver 302, which may operate in conjunction with a modem 340 and a scheduling component 342 to facilitate determining priorities for transmitting communications, as described herein.

[0086] The transceiver 302, receiver 306, transmitter 308, one or more processors 312, memory 316, application 375, bus 344, RF front end 388, LNA 390, switch 392, filter 396, PA 398, and one or more antennas 365 may be the same as or similar to corresponding components of UE 104 as described above, but are configured or otherwise programmed for base station operation rather than UE operation.

[0087] In an aspect, scheduling component 342 can optionally include a priority configuration component 352 for configuring priority or related rules, thresholds, or other indications for determining priorities regarding different types of communications, as described herein.

[0088] In one aspect, processor 312 may correspond to combining Figure 7 Similarly, the memory 316 may correspond to one or more of the processors described in the base station in FIG. Figure 7 The memory described in the base station.

[0089] Figure 4A A flow chart illustrating an example of a method 400 for prioritizing a particular type of communication in accordance with various aspects described herein. In an example, a UE 104 may use Figure 1 and Figure 2 One or more components described in the method 400 may be used to perform the functions described in the method 400. Figure 4B 1 is a flowchart illustrating a specific example of a method 400 for prioritizing a particular type of communication based on comparing one or more priority levels to one or more thresholds in accordance with various aspects described herein. Figure 1 and Figure 2 One or more components described in the method 400 may be used to perform the functions described in the method 400.

[0090] In method 400, at block 402, a first priority level associated with sidelink traffic may be identified. In one aspect, priority determination component 252 (e.g., in conjunction with processor(s) 212, memory 216, transceiver 202, communication component 242, etc.) may identify a first priority level associated with sidelink traffic. For example, priority determination component 252 may identify the first priority level as indicating a logical channel (LCH) priority of a sidelink channel (e.g., PSSCH, PSCCH, etc.) used to transmit sidelink traffic, indicating QoS information for a corresponding bearer (e.g., 5G QoS indicator (5QI), PC5-5QI (PQI), etc.), etc., or based on the above content to identify the first priority level. In one example, priority determination component 252 may determine the first priority level as being associated with a media access control (MAC) protocol data unit (PDU), wherein the priority level associated with a MAC PDU may be based on the priority level of one or more sidelink LCHs in the MAC PDU (e.g., determined as the highest priority level among the LCHs in the MAC PDU). Thus, in an example, priority determining component 252 can determine a first priority at the MAC layer (eg, based on a priority value specific to the MAC layer).

[0091] In method 400, at block 404, a second priority level associated with uplink traffic may be identified. In one aspect, priority determination component 252 (e.g., in combination with processor(s) 212, memory 216, transceiver 202, communication component 242, etc.) may identify a second priority level associated with uplink traffic. For example, priority determination component 252 may identify the second priority level as indicating an LCH priority of an uplink channel (e.g., PUSCH, PUCCH, etc.) used to transmit uplink traffic, indicating QoS information for a corresponding bearer (e.g., 5G QoS indicator (5QI), PQI, etc.), etc., or based on the above to identify the second priority level. In an example, priority determination component 252 may determine the second priority level as being associated with a MAC PDU, wherein the priority level associated with the MAC PDU may be based on the priority level of one or more uplink LCHs in the MAC PDU (e.g., determined as the highest priority level among the LCHs in the MAC PDU). Thus, in an example, priority determining component 252 can determine a second priority at the MAC layer (eg, based on a priority value specific to the MAC layer).

[0092] In method 400, at block 406, a determination may be made whether to prioritize the sidelink traffic or the uplink traffic based at least in part on the first priority level or the second priority level. In one aspect, priority determination component 252 (e.g., in conjunction with processor(s) 212, memory 216, transceiver 202, communication component 242, etc.) may determine whether to prioritize the sidelink traffic or the uplink traffic based at least in part on the first priority level or the second priority level. For example, priority determination component 252 may determine whether to prioritize a given PDU to be transmitted on a sidelink channel or another given PDU to be transmitted on an uplink channel in the same or overlapping time period (and / or in the same or overlapping frequency resources). In one example, determining whether to prioritize sidelink traffic or uplink traffic can be based on the priority determination component 252 also determining that the first resource for transmitting the sidelink traffic and the second resource for transmitting the uplink traffic (e.g., as indicated in the corresponding received resource grant) overlap in time (e.g., including one or more identical OFDM symbols) and / or frequency (e.g., including one or more identical resource blocks or resource elements). In one example, the priority determination component 252 can generally identify the first priority level and the second priority level as corresponding QoS requirements for the sidelink traffic and the uplink traffic or identify the first priority level and the second priority level based on the corresponding QoS requirements for the sidelink traffic and the uplink traffic, and determine whether to prioritize the sidelink or uplink traffic based on these QoS requirements (e.g., based on comparing the QoS requirements with corresponding thresholds or comparing these QoS requirements with each other, etc.). In one example, this can allow more granularity to distinguish between sidelink and uplink traffic, and the priority between traffic can be adjusted with RRC reconfiguration of the base station 102.

[0093] In one example, a unified metric may be used to evaluate both uplink and sidelink traffic to determine priority. For example, where a sidelink or uplink logical channel is configured, a priority associated with each logical channel may be determined to represent the ranking (e.g., importance) of traffic among all uplink and sidelink traffic (e.g., rather than just sidelink or uplink traffic) for prioritizing one type of traffic or another type of traffic. For example, in determining whether to prioritize the sidelink traffic or the uplink traffic at box 406, optionally at box 408, a logical channel priority for uplink traffic may be compared to a second logical channel priority for sidelink traffic, where these logical channel priorities may be configured for each channel (e.g., for a PSSCH for sidelink traffic and a PUSCH for uplink traffic). On the one hand, the priority determination component 252 (e.g., in combination with the processor(s) 212, the memory 216, the transceiver 202, the communication component 242, etc.) can compare the logical channel priority of the uplink traffic with the second logical channel priority of the sidelink traffic to determine whether to prioritize the uplink or sidelink traffic. In this example, the priority determination component 252 can prioritize the uplink traffic or the sidelink traffic based on the LCH priority and whether the LCH is used for the sidelink traffic or the uplink traffic. In another example, the priority determination component 252 can prioritize the uplink traffic or the sidelink traffic based on comparing the LCH priority with the corresponding threshold, as described herein.

[0094] In one example, in the case where the MAC PDU includes data from multiple logical channels, the priority determination component 252 can use the priority of the highest priority LCH of the corresponding link for comparison in determining the uplink / sidelink priority. As described, for example, the priority regarding the LCH can be configured using RRC signaling (e.g., system information block (SIB) signaling, dedicated signaling for a given UE, etc.) from the base station 102. In another example, the logical channel priority can be configured (e.g., for a sidelink radio bearer (SLRB) associated with the LCH), can be indicated in the control data for the channel or the corresponding resource grant, etc. In addition, in one example, the logical channel priority can be indicated in the MAC header of the communication transmitted on the logical channel.

[0095] In another example, the priority determination component 252 can identify the priority level of the sidelink and / or uplink traffic based on the priority setting of the unified 5QI and / or PQI (e.g., PC5 5QI, where PC5 can be a sidelink interface), so that it can be directly compared with respect to the sidelink and uplink traffic (or associated bearers). In this example, when a bearer is established for a QoS flow of a specific 5QI / PQI, the priority can be inherited and used for comparison. In the above example, the priority between SL and UL does not have to be different, and in this case, if the identified priorities are the same, the priority determination component 252 can use one or more rules to prefer uplink traffic or sidelink traffic. In one example, the rule can be configured by the network (e.g., by the base station 102). Therefore, in one example, in determining whether to prioritize the sidelink traffic or the uplink traffic at box 406, optionally in box 410, it can be determined whether to prioritize the sidelink traffic or the uplink traffic based on one or more configured rules. In an aspect, priority determining component 252 (e.g., in conjunction with processor(s) 212, memory 216, transceiver 202, communication component 242, etc.) can determine whether to prioritize the sidelink traffic or the uplink traffic based on the one or more configured rules. For example, priority determining component 252 can receive or determine the one or more configured rules based on a configuration stored in UE 104 or received from base station 102 (e.g., in RRC signaling, such as SIB or other broadcast signaling, dedicated signaling, etc.).

[0096] In addition, in one example, a first priority level can be identified based on QoS information and a second priority level can be identified based on a logical channel priority. For example, the priority determination component 252 can determine a first priority level regarding sidelink traffic based on PPPP (e.g., PPPP for LTE V2X UE or otherwise). In this example, the first priority level for transmissions granted using sidelink resources can be based on QoS. A PC5 5QI priority level can be defined for sidelink data as part of a QoS profile. Some sidelink traffic may not have a PQI (e.g., a PC5-RRC message or a sidelink MAC control element (CE) or other portion of a MAC header), and the priority determination component 252 can determine a default priority level regarding such signaling (e.g., which can be configured by the network (e.g., by the base station 102)). Additionally, in this example, if the sidelink LCH priority is used to compare with uplink traffic, a set of rules may be specified to map QoS (e.g., PQI priority level) to LCH priority level to facilitate a consistent comparison (e.g., where a connected mode UE obtains the sidelink LCH priority configured in per-UE signaling). In one example, the rules for mapping QoS to LCH may be included in one or more configured rules described above with respect to block 410, which may be configured in UE 104, received in a network configuration, etc. Thus, in one example, priority determination component 252 may determine an LCH for a channel that is mapped to a QoS value (e.g., 5QI, PQI, etc.), and may compare the LCH to another LCH of another channel, a threshold, etc. (as described herein) to determine whether to prioritize the traffic of the channel. Additionally, for example, the "priority" parameter transmitted in the sidelink PSCCH channel may be consistent with the sidelink priority level used in the uplink / sidelink prioritization scheme described herein. For example, the "priority" parameter may be the same, or at least the ranking may be consistent with the ranking used in uplink / sidelink prioritization.

[0097] In another example, in determining whether to prioritize the sidelink traffic or the uplink traffic at block 406, optionally at block 412, it may be determined whether to prioritize the sidelink traffic or the uplink traffic based on a channel or signal type. In one aspect, the priority determination component 252 (e.g., in combination with the processor(s) 212, the memory 216, the transceiver 202, the communication component 242, etc.) may determine whether to prioritize the sidelink traffic or the uplink traffic based on a channel or signal type. For example, the priority determination component 252 may determine whether to prioritize the sidelink or uplink traffic based on one or more exceptions so as to prioritize RACH communications, emergency PDN communications (e.g., plus NR layer 1 / layer 2 uplink communications) over other sidelink and uplink traffic, etc., regardless of the indicated priority. In an example, the priority determination component 252 may determine the priority of a signaling based on the LCH associated with the signaling. For example, a scheduling request (SR), a buffer status report (BSR), a HARQ ACK, etc. associated with a PUSCH may have a high priority (e.g., the highest priority so that these communications take precedence over other communications) LCH. In one example, the priority determination component 252 may determine the priority of other communications that do not have associated QoS (such as a channel quality indicator (CQI), a channel state information (CSI), a sounding reference signal (SRS), etc.), which may always be deprioritized or may take precedence over certain sidelink traffic (e.g., sidelink traffic with a priority that does not reach a threshold, as described in the following example). In addition, the priority determination component 252 may use other mechanisms described herein to determine the priority of other sidelink and / or uplink traffic.

[0098] In yet another example, in determining whether to prioritize the sidelink traffic or the uplink traffic at block 406, optionally at block 414, it may be determined whether to prioritize the sidelink traffic or the uplink traffic based on one or more priority thresholds. In one aspect, the priority determination component 252 (e.g., in combination with the processor(s) 212, the memory 216, the transceiver 202, the communication component 242, etc.) may determine whether to prioritize the sidelink traffic or the uplink traffic based on one or more priority thresholds. In this example, the priority determination component 252 may prioritize one of the sidelink traffic or the uplink traffic, where the identified priority level reaches (or does not reach) one or more thresholds (e.g., whether the priority level is lower than the priority level with respect to the other of the sidelink traffic or the uplink traffic). For example, the threshold(s) may be specified in a configuration stored in the UE 104 and / or received from the network (e.g., from the base station 102). In one example, the threshold can be part of one or more configured rules described in conjunction with block 410 above. Additionally, for example, sidelink traffic and uplink traffic can have associated thresholds, wherein priority determination component 252 can determine to prioritize uplink traffic if the uplink traffic reaches an uplink priority threshold, e.g., regardless of the priority of the sidelink traffic. In another example, priority determination component 252 can determine to prioritize the sidelink traffic if the uplink traffic does not reach the uplink priority threshold and / or if the sidelink traffic reaches the sidelink priority threshold.

[0099] In yet another example, the priority determination component 252 may determine to prioritize the uplink traffic when the priority level of the uplink traffic reaches the uplink priority threshold. In this example, if the priority level of the uplink traffic does not reach the uplink priority threshold, the priority determination component 252 may determine to prioritize the sidelink traffic when the priority level of the sidelink traffic reaches the sidelink priority threshold. In this example, if the priority level of the sidelink traffic does not reach the sidelink priority threshold, the priority determination component 252 may determine to prioritize the uplink traffic. In addition, in an example, the priority determination component 252 may determine the priority level of the uplink traffic (such as SR, BSR, etc.) related to the sidelink communication as the sidelink priority (e.g., instead of the uplink priority for the uplink traffic). Similarly, in an example, the priority determination component 252 may determine the priority threshold of the uplink traffic (such as SR, BSR, etc.) related to the sidelink communication as the sidelink priority threshold (e.g., instead of the uplink priority threshold for the uplink traffic). In these examples, priority determination component 252 can determine whether to prioritize uplink traffic associated with the sidelink communication based on comparing the sidelink priority to a sidelink priority threshold (or comparing the sidelink priority to an uplink priority threshold, comparing the uplink priority to a sidelink priority threshold, etc.).

[0100] When comparing priority levels to thresholds or comparing these priority levels to each other, as described herein, it should be appreciated that the highest priority may have the lowest value with respect to the priority level (e.g., priority=1 may be the highest priority). In this regard, for example, when referring to determining whether the priority reaches a threshold, the priority determination component 252 may determine whether the priority is less than (or equal to) the threshold. In other examples, the highest priority may have the highest value with respect to the priority level (e.g., priority=1 may be the lowest priority). In this regard, for example, when referring to determining whether the priority reaches a threshold, the priority determination component 252 may determine whether the priority is greater than (or equal to) the threshold.

[0101] In a first example, the priority determination component 252 can prioritize communications as follows: (1) RACH communications, emergency PDN communications (e.g., plus NR Layer 1 / Layer 2 uplink communications), etc., and then (2) sidelink and uplink communications based on LCH priorities, as described above. In an alternative to this example, other uplink traffic (e.g., uplink traffic without associated QoS) can always be deprioritized. In a specific example, RACH communications, emergency PDN communications (e.g., plus NR Layer 1 / Layer 2 uplink communications), etc. can be prioritized based on an LCH with a high priority (e.g., a highest priority that outperforms other LCH priorities that may be used for other sidelink and / or uplink communications, or a priority that at least reaches a threshold for prioritizing these communications).

[0102] In a second example, the priority determination component 252 can prioritize communications as follows: (1) RACH communications, emergency PDN communications (e.g., plus NR layer 1 / layer 2 uplink communications), etc.; and then (2) sidelink communications with a priority level that reaches a threshold; and then (3) sidelink and uplink communications based on LCH priority, as described above. In an alternative to this example, other uplink traffic (e.g., uplink traffic without associated QoS) can always be deprioritized.

[0103] In a third example, the priority determination component 252 can prioritize communications as follows: (1) RACH communications, emergency PDN communications (e.g., plus NR layer 1 / layer 2 uplink communications), etc.; and then (2) sidelink and uplink communications based on LCH priorities, as described above; and then (3) sidelink communications with a priority level that does not reach a threshold. In an alternative to this example, other uplink traffic (e.g., uplink traffic without associated QoS) can always be deprioritized. In another alternative to this example, other uplink traffic (e.g., uplink traffic without associated QoS) can be prioritized higher than sidelink communications with a priority level that does not reach a threshold.

[0104] In a fourth example, the priority determination component 252 can prioritize communications as follows: (1) RACH communications, emergency PDN communications (e.g., plus NR layer 1 / layer 2 uplink communications), etc.; then (2) sidelink communications with a priority level that reaches a first threshold; then (3) sidelink and uplink communications based on LCH priority, as described above; and then (4) sidelink communications with a priority level that does not reach a second threshold. In an alternative to this example, other uplink traffic (e.g., uplink traffic without associated QoS) can always be deprioritized. In another alternative to this example, other uplink traffic (e.g., uplink traffic without associated QoS) can be prioritized higher than sidelink communications with a priority level that does not reach a threshold.

[0105] In these examples, the introduction of threshold value can also be realized by keeping those side link traffics assigned with the highest LCH priority in the ranking system.When compared with any uplink traffic, using a separate threshold value can allow to keep the option that some side link traffics can always be de-prioritized.In addition, when using a separate threshold value, a separate independent metric can be used to determine the side link priority (e.g., being used to compare with the configured threshold value), which can be different from LCH priority determination (e.g., performed by network / base station 102). Using a separate threshold value can also work in the case where a unified uplink / side link ranking configuration is unavailable (e.g., UE 104 occupies a cellular cell that does not support side link configuration in base station 102).When using a threshold value in the above example, in one example, the side link traffic reaching the threshold value and the side link traffic considering the LCH priority for prioritization can be mixed in the same MAC PDU, in which case the PDU can inherit a higher priority.

[0106] In yet another example, the priority determination component 252 can prioritize communications of different radio access technologies (RATs). For example, the priority determination component 252 can prioritize NR uplink traffic in determining whether to prioritize the NR uplink or LTE sidelink and can compare it with LTE sidelink traffic with a priority level that reaches a PPPP threshold. In another example, the priority determination component 252 can prioritize NR sidelink traffic or LTE uplink traffic similar to one or more of the above options. In an example, the LTE solution can be reused (assuming that the legacy eNB is the same as the NR out of coverage (OOC) scenario).

[0107] like Figure 4B The method 400 shown in illustrative examples illustrates where determining whether to prioritize the sidelink traffic or the uplink traffic is based on comparing one or more priority levels to one or more thresholds. Figure 4B The method 400 includes the method described herein with reference to Figure 4A 402, 404, 406, 430 shown and described in the method 400 of FIG. 404, and further examples of determining whether to prioritize sidelink traffic or uplink traffic in block 406 are provided. Figure 4B As shown in, and according to some examples described above, in determining whether to prioritize sidelink traffic or uplink traffic at block 406, optionally at block 416, whether to prioritize the sidelink traffic or the uplink traffic can be determined based at least in part on comparing the second priority level to the uplink threshold. In one aspect, priority determination component 252 (e.g., in conjunction with processor(s) 212, memory 216, transceiver 202, communication component 242, etc.) can determine whether to prioritize the sidelink traffic or the uplink traffic based at least in part on comparing the second priority level to the uplink threshold.

[0108] In this example, Figure 4B In the method 400 shown in , optionally at block 418, the second priority level can be compared to an uplink threshold. In one aspect, the priority determination component 252 (e.g., in combination with the processor(s) 212, the memory 216, the transceiver 202, the communication component 242, etc.) can compare the second priority level to the uplink threshold. As described, this can include comparing the second priority level to the uplink threshold to determine whether the second priority level is lower than the uplink threshold, or less than or equal to the uplink threshold (which can indicate that the uplink traffic is to be prioritized if the lower priority level or value corresponds to a higher actual priority). However, in another example, a higher priority level or value can correspond to a higher actual priority, and in this example comparing the second priority level to the uplink threshold can include determining whether the second priority level is higher than the uplink threshold, or greater than or equal to the uplink threshold (which can indicate that the uplink traffic is to be prioritized).

[0109] In determining whether to prioritize the sidelink traffic or the uplink traffic at block 416, optionally at block 420, it may be determined whether the second priority level is below the uplink threshold. In one aspect, the priority determination component 252 (e.g., in conjunction with the processor(s) 212, the memory 216, the transceiver 202, the communication component 242, etc.) may determine whether the second priority level is below the uplink threshold. If so, then optionally at block 422, the uplink traffic may be prioritized, and the priority determination component 252 (e.g., in conjunction with the processor(s) 212, the memory 216, the transceiver 202, the communication component 242, etc.) may prioritize the uplink traffic accordingly. If the second priority level is not below the uplink threshold, then optionally at block 424, the first priority level may be compared to the sidelink threshold. In an aspect, priority determining component 252 (e.g., in conjunction with processor(s) 212, memory 216, transceiver 202, communication component 242, etc.) can accordingly compare the first priority level to a sidelink threshold.

[0110] In this example, optionally at block 426, it may be determined whether the first priority level is below a sidelink threshold. In one aspect, priority determination component 252 (e.g., in conjunction with processor(s) 212, memory 216, transceiver 202, communication component 242, etc.) may determine whether the first priority level is below a sidelink threshold. If so, then optionally at block 428, sidelink traffic may be prioritized, and priority determination component 252 (e.g., in conjunction with processor(s) 212, memory 216, transceiver 202, communication component 242, etc.) may prioritize the sidelink traffic accordingly. If the first priority level is not below the sidelink threshold, then optionally at block 422, uplink traffic may be prioritized, and priority determination component 252 (e.g., in conjunction with processor(s) 212, memory 216, transceiver 202, communication component 242, etc.) may prioritize the uplink traffic accordingly.

[0111] Reference Figure 4A (and Figure 4B), in method 400, at block 430, at least one of the sidelink traffic or the uplink traffic may be transmitted based on determining whether to prioritize the sidelink traffic or the uplink traffic. In one aspect, the communication component 242 (e.g., in conjunction with the processor(s) 212, the memory 216, the transceiver 202, etc.) may transmit at least one of the sidelink traffic or the uplink traffic based at least in part on determining whether to prioritize the sidelink traffic or the uplink traffic. For example, this may be based on a priority level (as described above), based on a priority level for a particular type of traffic or other channel (as further described herein), and the like. Additionally, prioritization may include transmitting one type of communication and discarding one or more other types of communication, transmitting one type of communication using a higher transmit power than used for other types of communication, and the like.

[0112] In one example, when at least one of the sidelink traffic or the uplink traffic is transmitted at block 430, one of the sidelink traffic or the uplink traffic may be transmitted, optionally at block 432. In one aspect, the communication component 242 (e.g., in conjunction with the processor(s) 212, the memory 216, the transceiver 202, etc.) may transmit one of the sidelink traffic or the uplink traffic based on the determined prioritization (e.g., and may discard the other of the sidelink traffic or the uplink traffic).

[0113] In another example, when transmitting at least one of the sidelink traffic or the uplink traffic at block 430, the sidelink traffic may be transmitted at a first transmission power and the uplink traffic may be transmitted at a second transmission power, optionally at block 434. In one aspect, the communication component 242 (e.g., in conjunction with the processor(s) 212, the memory 216, the transceiver 202, etc.) may transmit the sidelink traffic at the first transmission power and transmit the uplink traffic at the second transmission power. For example, the first and second transmission powers may indicate prioritization, and the sidelink traffic and the uplink traffic may be transmitted concurrently based on the respective transmission powers.

[0114] In this example, in method 400, optionally at block 436, at least one of a first transmit power for transmitting sidelink traffic or a second transmit power for transmitting uplink traffic may be selected based on determining whether to prioritize the sidelink traffic or the uplink traffic. In one aspect, priority determination component 252 (e.g., in conjunction with processor(s) 212, memory 216, transceiver 202, communication component 242, etc.) may select at least one of a first transmit power for transmitting sidelink traffic or a second transmit power for transmitting uplink traffic based on determining whether to prioritize the sidelink traffic or the uplink traffic. For example, priority determination component 252 may determine a higher transmit power for traffic determined to have a higher priority, and determine a lower transmit power for traffic determined to have a lower priority. These transmit powers may be within a transmit power budget configured for UE 104. In an example, prioritization component 252 can determine the higher transmit power and subsequently determine the lower transmit power as subtracting the higher transmit power from the power budget of UE 104 (and / or vice versa). In any case, communication component 242 can transmit sidelink traffic according to the first transmit power and uplink traffic according to the second transmit power to prioritize the traffic, as described.

[0115] Figure 5 1 is a flow chart illustrating another example of a method 500 for prioritizing a particular type of communication in accordance with various aspects described herein. In one example, a UE 104 may use Figure 1 and Figure 2 One or more components described in the method 500 may be used to perform the functions described in the method 500.

[0116] In method 500, in box 502, it can be determined that a specific type of uplink traffic is to be prioritized over sidelink traffic. On the one hand, priority determination component 252 (e.g., in combination with processor(s) 212, memory 216, transceiver 202, communication component 242, etc.) can determine that the specific type of uplink traffic is to be prioritized over sidelink traffic (and / or other types of traffic). For example, priority determination component 252 can determine that URLLC traffic is to be prioritized over sidelink traffic and / or other types of traffic (e.g., eMBB traffic). In an example, priority determination component 252 can determine that the specific type of uplink traffic is to be prioritized based on a configuration stored in UE104 or otherwise received from the network (e.g., from base station 102).

[0117] In determining at block 502 that the particular type of uplink traffic is to be prioritized, optionally at block 504, the particular type of uplink traffic may be determined to be prioritized based on an RRC configuration of a logical channel. In one aspect, priority determination component 252 (e.g., in conjunction with processor(s) 212, memory 216, transceiver 202, communication component 242, etc.) may determine to prioritize the particular type of uplink traffic based on an RRC configuration of a logical channel, where the logical channel may correspond to the particular type of uplink traffic. For example, the RRC configuration may include an indicator that the particular type of uplink traffic is to be prioritized and / or otherwise prioritize communications transmitted on the logical channel. For example, the RRC configuration may be used to notify a MAC layer of a selected uplink communication to be prioritized.

[0118] In one example, the configuration may include prioritizing a specific type of uplink communication using a specific 5QI. In another example, for an LCH or dedicated radio bearer (DRB) configuration, a special indication may be added to an RRCConnectionReconfigure message to mark that the special LCH does not use the above-mentioned sidelink / uplink prioritization (e.g., in conjunction with method 400), but may always take precedence over sidelink traffic (and / or other uplink traffic). In yet another example, an LCH for a channel carrying URLLC traffic may have a higher priority than a channel carrying eMBB traffic.

[0119] In one example, similar to the example described above with reference to method 400, in determining at block 502 that the particular type of traffic is to be prioritized, the prioritization component 252 may accordingly prioritize the particular type of uplink traffic having (e.g., originally prioritized) RACH communications, emergency PDN communications, etc., which may be prioritized over all other sidelink traffic and uplink traffic. In another example, the prioritization component 252 may prioritize communications as follows: (1) RACH communications, emergency PDN communications (e.g., plus NR layer 1 / layer 2 uplink communications), and a particular type of uplink communications (e.g., URLLC), etc., which may be indicated by an RRC configuration; then (2) sidelink traffic having a priority level that reaches a PPPP threshold; then (3) uplink traffic; and then (4) sidelink traffic having a priority level that does not reach a PPPP threshold.

[0120] In method 500, at block 506, at least one of the specific type of uplink traffic or the sidelink traffic may be transmitted based on a determination that the specific type of uplink traffic is to be prioritized. In one aspect, communication component 242 (e.g., in conjunction with processor(s) 212, memory 216, transceiver 202, etc.) may transmit at least one of the specific type of uplink traffic or the sidelink traffic based on a determination that the specific type of uplink traffic is to be prioritized. As described, for example, communication component 242 may transmit the specific type of uplink traffic and discard any other sidelink and / or other traffic. In another example, as described, communication component 242 may transmit the specific type of uplink traffic at a first transmit power, and also transmit other sidelinks and / or other traffic at other transmit powers lower than the first transmit power to prioritize the specific type of uplink traffic.

[0121] Figure 6 1 is a flow chart illustrating an example of a method 600 for configuring a priority for a particular type of communication in accordance with various aspects described herein. In one example, a UE 104 may use Figure 1 and Figure 3 One or more components described in the method 600 may be used to perform the functions described in the method 600.

[0122] In method 600, at block 602, an indication of QoS information for a logical channel can be received from a UE. In one aspect, priority configuration component 352 (e.g., in conjunction with processor(s) 312, memory 316, transceiver 302, scheduling component 342, etc.) can receive an indication of QoS information for a logical channel from a UE (e.g., UE 104). For example, scheduling component 342 can establish a DRB with UE 104 for communicating therewith on one or more LCHs. Scheduling component 342 can also provide information about the logical channel to UE 104, and the UE can transmit an indication of QoS information (such as PCI, 5QI, etc.) for communications transmitted on the logical channel.

[0123] In method 600, in box 604, it can be determined at least in part based on the indication of the QoS information whether the first type of uplink traffic of the logical link is to be prioritized over the sidelink traffic. On the one hand, the priority configuration component 352 (e.g., in combination with (all) processors 312, memory 316, transceiver 302, scheduling component 342, etc.) can determine at least in part based on the indication of the QoS information whether the first type of uplink traffic of the logical channel is to be prioritized over the sidelink traffic. For example, in the case where the QoS information reaches a threshold and / or has a higher priority than the QoS information of other LCHs established with UE 104, the priority configuration component 352 can determine that the first type of uplink traffic is to be prioritized. In one example, the QoS information can indicate the QoS for URLLC traffic.

[0124] In method 600, in block 606, a priority indication of whether the first type of uplink traffic is to be given priority over the sidelink traffic can be transmitted to the UE at least in part based on determining whether the first type of uplink traffic is to be given priority over the sidelink traffic. On the one hand, priority configuration component 352 (e.g., in combination with (all) processors 312, memory 316, transceiver 302, scheduling component 342, etc.) can be transmitted to the UE at least in part based on determining whether the first type of uplink traffic is to be given priority over the sidelink traffic. A priority indication of whether the first type of uplink traffic is to be given priority over the sidelink traffic. For example, priority configuration component 352 can transmit the priority indication in the RRC configuration of the LCH, as described above. UE 104 can receive the priority indication and can determine to prioritize the transmission on the LCH accordingly, as described above.

[0125] Figure 7 1 is a block diagram of a MIMO communication system 700 including a base station 102 and a UE 104 according to various aspects of the present disclosure. The MIMO communication system 700 may be illustrated with reference to Figure 1 The base station 102 may be a base station 102. Figure 1 1 and 10. Examples of various aspects of base station 102 are described. Base station 102 may be equipped with antennas 734 and 735, and UE 104 may be equipped with antennas 752 and 753. In MIMO communication system 700, base station 102 may be able to send data on multiple communication links simultaneously. Each communication link may be referred to as a "layer", and the "rank" of a communication link may indicate the number of layers used for communication. For example, in a 2x2 MIMO communication system where base station 102 transmits two "layers", the rank of the communication link between base station 102 and UE 104 is 2.

[0126] At the base station 102, the transmit (Tx) processor 720 may receive data from a data source. The transmit processor 720 may process the data. The transmit processor 720 may also generate a control symbol or a reference symbol. The transmit MIMO processor 730 may perform spatial processing (e.g., precoding) on ​​the data symbol, the control symbol, or the reference symbol, where applicable, and may provide an output symbol stream to the transmit modulators / demodulators 732 and 733. Each modulator / demodulator 732 to 733 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator / demodulator 732 to 733 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a DL signal. In one example, the DL signals from the modulators / demodulators 732 and 733 may be transmitted via antennas 734 and 735, respectively.

[0127] UE 104 may be a reference Figure 1-Figure 2 Examples of various aspects of the UE 104 described. At the UE 104, the UE antennas 752 and 753 can receive DL signals from the base station 102 and can provide the received signals to the modulators / demodulators 754 and 755, respectively. Each modulator / demodulator 754 to 755 can condition (e.g., filter, amplify, downconvert, and digitize) the respective received signals to obtain input samples. Each modulator / demodulator 754 to 755 can further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 756 can obtain the received symbols from the modulator / demodulators 754 and 755, perform MIMO detection on the received symbols where applicable, and provide detected symbols. The receive (Rx) processor 758 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to the data output, and provide decoded control information to the processor 780 or the memory 782.

[0128] Processor 780 may, in some cases, execute stored instructions to instantiate communication component 242 (eg, see Figure 1 and 2 ).

[0129] On the uplink (UL), at the UE 104, a transmit processor 764 may receive and process data from a data source. The transmit processor 764 may also generate reference symbols for a reference signal. The symbols from the transmit processor 764 may be precoded by a transmit MIMO processor 766, if applicable, further processed by modulators / demodulators 754 and 755 (e.g., for SC-FDMA, etc.), and transmitted to the base station 102 according to the communication parameters received from the base station 102. At the base station 102, the UL signals from the UE 104 may be received by antennas 734 and 735, processed by modulators / demodulators 732 and 733, detected by a MIMO detector 736, if applicable, and further processed by a receive processor 738. The receive processor 738 may provide decoded data to a data output and to the processor 740 or memory 742.

[0130] Processor 740 may in some cases execute stored instructions to instantiate scheduling component 342 (eg, see Figure 1 and Figure 3 ).

[0131] The components of the UE 104 may be implemented individually or collectively with one or more ASICs adapted to perform some or all applicable functions in hardware. Each of the modules mentioned may be a device for performing one or more functions related to the operation of the MIMO communication system 700. Similarly, the components of the base station 102 may be implemented individually or collectively with one or more ASICs adapted to perform some or all applicable functions in hardware. Each of the components mentioned may be a device for performing one or more functions related to the operation of the MIMO communication system 700.

[0132] The above detailed description set forth above in conjunction with the accompanying drawings describes examples and does not represent the only examples that can be implemented or fall within the scope of the claims. The term "example" when used in this description means "used as an example, instance, or illustration", rather than "better than" or "better than other examples". This detailed description includes specific details to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0133] Information and signals may be represented using any of a variety of different techniques and technologies. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, computer executable codes or instructions stored on computer-readable media, or any combination thereof.

[0134] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed with a specially programmed device, such as, but not limited to, a processor designed to perform the functions described herein, a digital signal processor (DSP), an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The specially programmed processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The specially programmed processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0135] The functions described herein may be implemented in hardware, software, or any combination thereof. If implemented in software executed by a processor, each function may be stored as one or more instructions or codes on or transmitted by a non-transient computer-readable medium. Other examples and implementations fall within the scope and spirit of the present disclosure and the appended claims. For example, due to the nature of software, the above functions may be implemented using software, hardware, hard wiring, or any combination thereof executed by a specially programmed processor. Features that implement the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented at different physical locations. In addition, the term "or" is intended to represent an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clearly seen from the context, phrases such as "X adopts A or B" are intended to represent any natural concurrent arrangement. That is, for example, the phrase "X adopts A or B" is satisfied by any of the following instances: X adopts A; X adopts B; or X adopts both A and B. Additionally, as used herein (including in the claims), “or” used in a list of items followed by “at least one of” indicates a disjunctive list so that, for example, a list “at least one of A, B, or C” means A or B or C or AB or AC or BC or ABC (A and B and C).

[0136] Computer-readable media include both computer storage media and communication media, including any media that facilitates a computer program to be transferred from one place to another. Storage media can be any available media that can be accessed by a general or special-purpose computer. As an example and not limitation, computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code means of an instruction or data structure form and can be accessed by a general or special-purpose computer or a general or special-purpose processor. Similarly, any connection is also properly referred to as a computer-readable medium. For example, if software is transmitted from a website, a server or other remote sources using a coaxial cable, a fiber optic cable, a twisted pair, a digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of the medium. Disk and disc as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, wherein disk usually reproduces data magnetically, while disc reproduces data optically with laser. Combinations of the above media are also included in the scope of computer-readable media.

[0137] The previous description of the disclosure is provided to enable those skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the common principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. In addition, although the elements of the described aspects and / or embodiments may be described or claimed in the singular, the plural is also contemplated unless explicitly stated to be limited to the singular. In addition, all or part of any aspect and / or embodiment may be used in conjunction with all or part of any other aspect and / or embodiment, unless otherwise stated. Thus, the disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A wireless communication method, comprising: identifying, at a medium access control (MAC) layer, a first priority level associated with sidelink traffic; identifying a second priority level associated with uplink traffic; comparing the second priority level associated with uplink traffic to an uplink threshold; determining whether to prioritize at least one of the sidelink traffic or the uplink traffic based at least in part on comparing the second priority level to the uplink threshold; as well as At least one of the sidelink traffic or the uplink traffic is transmitted based at least in part on determining whether to prioritize the sidelink traffic or the uplink traffic.

2. The method of claim 1 , wherein determining whether to prioritize the sidelink traffic or the uplink traffic comprises: Determining to prioritize the uplink traffic over the sidelink traffic is based on determining that the second priority level for the uplink traffic is below the uplink threshold.

3. The method of claim 1 , wherein determining whether to prioritize the sidelink traffic or the uplink traffic comprises: A determination is made to prioritize the sidelink traffic over the uplink traffic based on a determination that the first priority level of the sidelink traffic is below a sidelink threshold.

4. The method of claim 3, wherein determining to prioritize the sidelink traffic over the uplink traffic is further based on determining that the second priority level associated with the uplink traffic is not below the uplink threshold.

5. The method of claim 1 , wherein determining whether to prioritize the sidelink traffic or the uplink traffic comprises: The uplink traffic is prioritized over any sidelink traffic if the uplink traffic includes at least one of random access channel traffic or emergency traffic, or over any other type of uplink traffic.

6. The method of claim 1 , wherein identifying the first priority level associated with sidelink traffic comprises: The first priority level is identified as a highest logical channel priority among a plurality of logical channels in a MAC protocol data unit (PDU) associated with the sidelink traffic.

7. The method of claim 6, wherein identifying the second priority level associated with uplink traffic comprises: The second priority level is identified at the MAC layer as a logical channel priority of one or more logical channels in communications associated with uplink traffic.

8. The method of claim 1, wherein the transmitting comprises: One of the sidelink traffic or the uplink traffic is transmitted based on a determination to prioritize the sidelink traffic or the uplink traffic.

9. The method of claim 1, further comprising selecting at least one of a first power for transmitting the sidelink traffic or a second power for transmitting the uplink traffic based on determining whether to prioritize the sidelink traffic or the uplink traffic, wherein transmitting at least one of the sidelink traffic or the uplink traffic comprises transmitting the sidelink traffic based on the first power and transmitting the uplink traffic based on the second power.

10. The method of claim 1, further comprising receiving at least one of the first priority level or the second priority level via radio resource control (RRC) layer signaling.

11. The method of claim 1, wherein the first priority level of the sidelink traffic is the same as a priority level indicated in a physical sidelink control channel (PSCCH).

12. The method of claim 1, wherein identifying the first priority level is based on a PC5 fifth generation (5G) quality of service (QoS) indicator (5QI) (PQI) of the sidelink traffic, or identifying the second priority level is based on a PQI of uplink traffic.

13. A method as claimed in claim 1, wherein the first priority level is a logical channel priority configured based on a PC5 fifth generation (5G) quality of service (QoS) indicator (5QI) (PQI) of the sidelink traffic, and the second priority level is a logical channel priority based on the 5QI of the uplink traffic.

14. The method of claim 1, wherein the sidelink traffic and the uplink traffic correspond to separate radio access technologies, and wherein determining whether to prioritize the sidelink traffic or the uplink traffic is based at least in part on the separate radio access technologies.

15. An apparatus for wireless communication, comprising: Transceiver; a memory configured to store instructions; as well as one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: identifying, at a medium access control (MAC) layer, a first priority level associated with sidelink traffic; identifying a second priority level associated with uplink traffic; comparing the second priority level associated with uplink traffic to an uplink threshold; determining whether to prioritize at least one of the sidelink traffic or the uplink traffic based at least in part on comparing the second priority level to the uplink threshold; as well as At least one of the sidelink traffic or the uplink traffic is transmitted based at least in part on determining whether to prioritize the sidelink traffic or the uplink traffic.

16. The apparatus of claim 15, wherein the one or more processors are configured to determine to prioritize the uplink traffic over the sidelink traffic based on determining that the second priority level with respect to the uplink traffic is below the uplink threshold.

17. The apparatus of claim 15, wherein the one or more processors are configured to determine to prioritize the sidelink traffic over the uplink traffic based on determining that the first priority level of the sidelink traffic is below a sidelink threshold.

18. The apparatus of claim 17, wherein the one or more processors are configured to determine to prioritize the sidelink traffic over the uplink traffic based further on determining that the second priority level associated with the uplink traffic is not below the uplink threshold.

19. An apparatus as described in claim 15, wherein the one or more processors are configured to determine whether to prioritize the sidelink traffic or the uplink traffic at least in part by: giving priority to the uplink traffic over any sidelink traffic, or over any other type of uplink traffic when the uplink traffic includes at least one of random access channel traffic or emergency traffic.

20. An apparatus as described in claim 15, wherein the one or more processors are configured to identify the first priority level associated with sidelink traffic at least in part by identifying the first priority level as a highest logical channel priority among multiple logical channels in a MAC protocol data unit (PDU) associated with the sidelink traffic.

21. An apparatus as described in claim 20, wherein the one or more processors are configured to identify the second priority level associated with uplink traffic at least in part by: identifying the second priority level as a logical channel priority of one or more logical channels in communications associated with the uplink traffic at the MAC layer.

22. The apparatus of claim 15, wherein the one or more processors are configured to transmit one of the sidelink traffic or the uplink traffic based on a determination to prioritize the sidelink traffic or the uplink traffic.

23. A device for wireless communication, comprising: means for identifying, at a medium access control (MAC) layer, a first priority level associated with sidelink traffic; means for identifying a second priority level associated with uplink traffic; means for comparing said second priority level associated with uplink traffic to an uplink threshold; means for determining whether to prioritize at least one of the sidelink traffic or the uplink traffic based at least in part on comparing the second priority level to the uplink threshold; as well as Means for transmitting at least one of the sidelink traffic or the uplink traffic based at least in part on determining whether to prioritize the sidelink traffic or the uplink traffic.

24. The apparatus of claim 23, wherein the means for determining determines to prioritize the uplink traffic over the sidelink traffic based on determining that the second priority level for the uplink traffic is below the uplink threshold.

25. An apparatus as described in claim 23, wherein the device for determining determines to give priority to the sidelink traffic over the uplink traffic based on determining that the first priority level of the sidelink traffic is lower than a sidelink threshold and further based on determining that the second priority level associated with the uplink traffic is not lower than the uplink threshold.

26. The apparatus of claim 23, wherein the means for determining prioritizes the uplink traffic over any sidelink traffic, or over any other type of uplink traffic, if the uplink traffic includes at least one of random access channel traffic or emergency traffic.

27. A computer readable medium comprising code executable by one or more processors for wireless communication, the code comprising code for: identifying, at a medium access control (MAC) layer, a first priority level associated with sidelink traffic; identifying a second priority level associated with uplink traffic; comparing the second priority level associated with uplink traffic to an uplink threshold; determining whether to prioritize at least one of the sidelink traffic or the uplink traffic based at least in part on comparing the second priority level to the uplink threshold; as well as At least one of the sidelink traffic or the uplink traffic is transmitted based at least in part on determining whether to prioritize the sidelink traffic or the uplink traffic.

28. The computer-readable medium of claim 27, wherein the code for determining determines to prioritize the uplink traffic over the sidelink traffic based on determining that the second priority level for the uplink traffic is below the uplink threshold.

29. A computer-readable medium as described in claim 27, wherein the code for determining is based on determining that the first priority level of the sidelink traffic is lower than a sidelink threshold and further based on determining that the second priority level associated with the uplink traffic is not lower than the uplink threshold to determine that the sidelink traffic is to be prioritized over the uplink traffic.

30. The computer-readable medium of claim 27, wherein the code for determining prioritizes the uplink traffic over any sidelink traffic if the uplink traffic includes at least one of random access channel traffic or emergency traffic, or over any other type of uplink traffic.

Images