Techniques for Data Rate Sharing in Uplink and Sidelink Wireless Communications

Abstract

Some aspects described herein relate to considering data rates of multiple interfaces when determining whether to decode communications received via the multiple interfaces, and / or to considering the multiple interfaces when determining parameters for authorizing resources for one or more of the multiple interfaces.

Description

[0001] Cross - Reference to Related Applications

[0002] This patent application claims priority to Greek Patent Application No. 20190100456, entitled "TECHNIQUES FOR DATA RATE SHARING FOR UPLINK AND SIDELINK WIRELESS COMMUNICATIONS", filed on October 14, 2019, and U.S. Patent Application No. 17 / 069,541, entitled "TECHNIQUES FOR DATA RATE SHARING FOR UPLINK AND SIDELINK WIRELESS COMMUNICATIONS", filed on October 13, 2020, which are assigned to the assignee of the present application and are hereby incorporated herein by reference in their entirety for all purposes. Field of the Disclosure

[0003] Aspects of the present disclosure generally relate to wireless communication systems, and more particularly, to communicating using multiple different interfaces. Background Art

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

[0005] These multi - access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, or even global level. For example, the fifth - generation (5G) wireless communication technology (which may be referred to as 5G new radio (5G NR)) is envisioned to expand and support various usage scenarios and applications with respect to the current mobile network generation. In one aspect, 5G communication technology may include: enhanced mobile broadband for accessing multimedia content, services, and data to handle human - centric usage cases; ultra - reliable low - latency communication (URLLC) with certain specifications for latency and reliability; and massive machine - type communication, which may allow the transmission of a very large number of connected devices and relatively small amounts of non - latency - sensitive information. However, as the demand for mobile broadband access continues to increase, further improvements in 5G communication technology and subsequent technologies may be desirable.

[0006] In some wireless communication technologies (such as 5G), a user equipment (UE) can communicate through multiple interfaces. The multiple interfaces can include the Uu interface between the UE and a base station, where the UE can receive communication from the base station through the downlink and send communication to the base station through the uplink. Additionally, the multiple interfaces can include a sidelink interface, where the UE can directly communicate with one or more other UEs through a sidelink channel (e.g., without passing through the base station). SUMMARY OF THE INVENTION

[0007] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects, nor is it intended to identify key or critical elements of all aspects or to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that follows.

[0008] According to an example, a method for wireless communication is provided. The method includes: receiving downlink communication from an access point on a set of downlink resources; receiving sidelink communication from a user equipment (UE) on a set of sidelink resources that at least overlaps with the set of downlink resources in the time domain; determining whether the downlink communication and the sidelink communication meet a threshold data rate; determining whether to decode at least one of the downlink communication or the sidelink communication based on determining whether the downlink communication and the sidelink communication meet the threshold data rate; and decoding at least one of the downlink communication or the sidelink communication based on determining to decode.

[0009] In another example, a method for wireless communication is provided, including: receiving, for a UE, the threshold data rate supported by the UE; determining, for the UE, a set of sidelink resources configured to receive sidelink communication from one or more other UEs; determining, for the UE, a set of downlink resources configured to receive downlink communication; determining, based on the threshold data rate, one or more downlink parameters for sending downlink communication to the UE; and sending, based on the one or more downlink parameters, at least a downlink resource grant indicating the set of downlink resources to the UE.

[0010] In another example, a method for wireless communication is provided, including: determining whether uplink communication and sidelink communication meet a threshold data rate; determining whether to send at least one of the uplink communication or the sidelink communication based on determining whether the uplink communication and the sidelink communication meet the threshold data rate; and sending at least one of the uplink communication or the sidelink communication based on determining to send.

[0011] In another example, a device for wireless communication is provided, including: 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 execute the instructions to perform the operations of the methods and examples described above and further herein. In another aspect, a device for wireless communication is provided, which includes units for performing the operations of the methods and examples described above and further herein. In yet another aspect, a computer-readable medium is provided, which includes code executable by one or more processors to perform the operations of the methods and examples described above and further herein.

[0012] In yet another example, a device for wireless communication is provided, which includes 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: determine whether to transmit at least one of the uplink communication and the sidelink communication based on determining whether the uplink communication and the sidelink communication meet a threshold data rate; and transmit the at least one of the uplink communication and the sidelink communication based on determining to transmit.

[0013] To achieve the above and related purposes, the one or more aspects include the features fully described hereinafter and particularly pointed out in the claims. The following description and the drawings detail certain illustrative features of the one or more aspects. However, these features merely indicate several of the various ways in which the principles of the various aspects can be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Aspects of the disclosure will be described below in conjunction with the drawings, which are provided to illustrate rather than limit the aspects of the disclosure, where like reference numerals represent like elements, and in which:

[0015] Figure 1 An example of a wireless communication system according to aspects of the present disclosure is shown;

[0016] Figure 2 is a block diagram showing an example of a UE according to aspects of the present disclosure;

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

[0018] Figure 4 is a flowchart showing an example of a method for determining data rates for receiving communications through multiple interfaces according to aspects of the present disclosure;

[0019] Figure 5 is a flowchart illustrating an example of a method for determining a data rate for sending communications over multiple interfaces in accordance with various aspects of the present disclosure;

[0020] Figure 6 is a flowchart illustrating an example of a method for considering data rates of multiple interfaces when scheduling resources in accordance with various aspects of the present disclosure; and

[0021] Figure 7 is a block diagram illustrating an example of a MIMO communication system including a base station and a UE in accordance with various aspects of the present disclosure. Detailed Description

[0022] Aspects are now described with reference to the drawings. In the following description, numerous specific details are set forth for purposes of explanation in order to provide a thorough understanding of one or more aspects. It is evident, however, that the aspects may be practiced without these specific details.

[0023] The described features generally relate to enabling data sharing among multiple interfaces in wireless communications. For example, a user equipment (UE) may communicate using multiple interfaces, which may include: communication over the Uu interface (e.g., on an uplink and / or downlink channel with a base station), communication over a sidelink interface (e.g., on a sidelink channel with one or more other UEs), etc. Additionally, the UE may determine the data rate of a communication when determining whether to decode a downlink communication and / or whether to encode or transmit an uplink communication, and in the case where the data rate of the communication exceeds a threshold data rate, may avoid decoding and / or encoding / transmitting. In the case where the UE communicates simultaneously over multiple interfaces, it may consider or otherwise measure the data rates for the multiple interfaces when determining whether to decode and / or encode / transmit the communication over the interfaces.

[0024] In one example, the UE may consider the total data rate of two (or all) interfaces and may compare the total data rate of simultaneously received or simultaneously encoded / transmitted communications with a threshold when determining whether to decode or encode / transmit a communication. In one example, the interfaces may correspond to the same or different network operators or public land mobile networks (PLMNs), the same or different cells or corresponding access points (e.g., gNBs), etc. Additionally, the interfaces may be on different component carriers (CCs), use different bandwidth parts (BWPs) or other portions of the bandwidth, etc.

[0025] In one example, an access point may consider multiple interfaces configured at a UE when determining the data rate of one or more interfaces provided (or configured) by the access point. For example, the access point may determine the data rate of the Uu interface (e.g., for downlink communications sent over the Uu interface, or for resources or other parameters configured for uplink communications by the UE over the Uu interface) at least in part based on known or determined data rate parameters for another interface. For example, the other interface may include a sidelink interface, and the data rate parameters for the sidelink interface may be configured by the access point associated with the Uu interface, or by another access point, or by the UE or one or more other UEs.

[0026] In a specific example, in the 3rd Generation Partnership Project (3GPP) New Radio (NR), as specified in Section 5.1.3 of Technical Specification (TS) 38.214 v.15.7.0, within a cell group, if the following conditions are not met at any given time instant, the UE may not need to process the Physical Downlink Shared Channel (PDSCH) transmission in slot s in serving cell j, and for j = 0, 1, 2 … J - 1, slot s j overlaps with that time instant: j where J is the number of configured serving cells belonging to a frequency range, and for the jth serving cell, M is the number of Transport Blocks (TBs) transmitted in slot s

[0027]

[0028] T = 10 j / 2 slot μ(j) where μ(j) is the numerology of the PDSCH in slot s of the jth serving cell, and for the mth TB, -3 A is the number of bits in the transport block, C is the total number of code blocks of the transport block, C′ is the number of scheduled code blocks of the transport block, and DataRate [Mbps] is calculated as: the maximum data rate summed over all carriers in that frequency range for any signaled band combination and feature set consistent with the configured serving cells. In this example, a slot may be a unit of time resource defined by a set of symbols (e.g., Orthogonal Frequency Division Multiplexing (OFDM) symbols). μ(j) j where A is the number of bits in the transport block, C is the total number of code blocks of the transport block, C′ is the number of scheduled code blocks of the transport block, and DataRate [Mbps] is calculated as: the maximum data rate summed over all carriers in that frequency range for any signaled band combination and feature set consistent with the configured serving cells. In this example, a slot may be a unit of time resource defined by a set of symbols (e.g., Orthogonal Frequency Division Multiplexing (OFDM) symbols). where A is the number of bits in the transport block, C is the total number of code blocks of the transport block, C′ is the number of scheduled code blocks of the transport block, and DataRate [Mbps] is calculated as: the maximum data rate summed over all carriers in that frequency range for any signaled band combination and feature set consistent with the configured serving cells. In this example, a slot may be a unit of time resource defined by a set of symbols (e.g., Orthogonal Frequency Division Multiplexing (OFDM) symbols).

[0029] Similarly, in section 6.1.4 of TS 38.214 v.15.7.0, for the j-th serving cell, if the processingType2Enabled of the higher layer parameter PDSCH-ServingCellConfig is configured for the serving cell and set to enabled, or if at least one I MCS >W, where for MCS tables 5.1.3.1-1 and 5.1.3.1-3, W = 28, and for MCS table 5.1.3.1-2, W = 27, then the UE does not need to (and can avoid) process the PDSCH transmission if the following conditions are not met:

[0030]

[0031] where L is the number of symbols allocated to the PDSCH, M is the number of TBs in the PDSCH, where μ is the numerology of the PDSCH, and for the m-th TB, A is the number of bits in the transport block, C is the total number of code blocks of the transport block, C′ is the number of scheduled code blocks of the transport block, and DataRateCC [Mbps] is calculated as: for any signaled band combination and feature set consistent with the serving cell, the maximum data rate of the carrier in the band of the serving cell, where the data rate value is given by the following formula and includes the scaling factor f(i).

[0032] Similarly, for uplink communication, in section 6.1.4 of TS 38.214 v.15.7.0, within a cell group, if the following conditions are not met at any given time instant, the UE does not need to process the physical uplink shared channel (PUSCH) transmission in slot s j in serving cell j, and for j = 0, 1, 2 … J−1, slot s j overlaps with that time instant:

[0033]

[0034] where J is the number of configured serving cells belonging to a frequency range, and for the j-th serving cell, M is the number of TBs sent in slot s j T slot μ(j) = 10 -3 / 2 μ(j) , where μ(j) is the numerology of the PUSCH in slot s j of the j-th serving cell, and for the m-th TB, A is the number of bits in the defined transport block, C is the total number of code blocks of the transport block, C′ is the number of scheduled code blocks of the transport block, and DataRate [Mbps] is calculated as: the maximum data rate summed over all carriers in the frequency range for any signaled band combination and feature set consistent with the configured serving cell, where the data rate value is given by the formula in Subclause 4.1.2 of TS 38.306, including the scaling factor f(i).

[0035] For example, the data rate value can be given by the following formula, as specified in Section 4.1.2 of TS 38.306 v15.7.0:

[0036]

[0037] where J is the number of aggregated component carriers in a band or band combination, R max = 948 / 1024, for the jth CC, is the maximum number of supported layers given by the higher layer parameter maxNumberMIMO-LayersPDSCH for downlink and the maximum of the higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH for uplink, is the maximum supported modulation order given by the higher layer parameter supportedModulationOrderDL for downlink and the higher layer parameter supportedModulationOrderUL for uplink, f (j) is the scaling factor given by the higher layer parameter scalingFactor and can take the values 1, 0.8, 0.75, and 0.4, μ is the numerology, is the average OFDM symbol duration in a subframe of the numerology μ, i.e., (Note that normal cyclic prefix can be assumed), is the maximum resource block (RB) allocation in the bandwidth BW (j) with the numerology μ, where BW (j) is the maximum bandwidth supported by the UE in a given band or band combination, OH (j) is the overhead and takes the following values: 0.14 for frequency range FR1 of downlink (DL), 0.18 for frequency range FR2 of DL, 0.08 for frequency range FR1 of uplink (UL), and 0.10 for frequency range FR2 of UL.

[0038] In addition, in one example, the value of f can be reconfigured across different cells of the same physical uplink control channel (PUCCH) group (except when it is set to 1 or if timing capability #2 is configured). This enables data sharing across different cells. For example, the overall throughput is still below the UE capability, but the per-CC data rate can change. As mentioned herein, processing capability #1 and processing capability #2 for the downlink can be defined as in Section 5.3 of TS 38.214 v15.7.0, which may include processing time for handling downlink communications based on different capabilities, and processing capability #1 and processing capability #2 for the uplink can be defined as in Section 6.4 of TS 38.214 v15.7.0, which may include processing time for handling uplink communications based on different capabilities. In either case, the timing capability can be configured or otherwise specified such that the UE and / or the base station can determine the timing capability and can make other determinations at least in part based on the timing capability, as further described herein.

[0039] Aspects described herein relate to using data sharing between interfaces (e.g., between the Uu and sidelink interfaces) where the UE can communicate over the interfaces simultaneously. In addition, aspects described herein relate to an access point (e.g., gNB) performing operations to attempt to ensure that data sharing does not violate the maximum data rate condition at the UE. Various scenarios are considered and explained herein, such as: (1) where the interfaces have the same operator / PLMN and the same cell / gNB, (2) where the interfaces have the same operator / PLMN and different cells / gNBs, (3-1) where the interfaces have different operators / PLMNs and the UE is configured to transmit in one band of a first operator and receive in a different band of another operator or an unlicensed band such as an intelligent transportation system (ITS) for vehicle-to-everything (V2X), etc., or (3-2) where the interfaces have different operators / PLMNs and the UE is configured to transmit / receive in a band different from the band configured for another interface (e.g., configured to transmit / receive on a sidelink that is not in the band of the operator controlling the Uu, which can be a band of another operator or in an unlicensed band such as an ITS for V2X). In addition, various resource allocation modes are considered and explained herein, such as: Mode 1, where an access point (e.g., gNB) can schedule resources for sidelink transmission or configure resources for SL transmission (and the UE can determine when to use the configured resources); or Mode 2, where the UE determines resources based on sensing, measuring, reserving, etc. of resources for transmission on the sidelink (e.g., using listen-before-talk or other idle channel assessment functions).

[0040] Various scenarios and resource allocation patterns can cause the access point to use different functions to determine the data rate of one or more interfaces. In any case, for receiving communications, the UE can determine the data rate as the total of the concurrent interfaces, which can include: for each interface on which communications are received simultaneously from the access point (e.g., via the Uu interface), from one or more UEs (e.g., via the sidelink interface), etc., considering multiple CCs, BWPs, etc. The UE can determine whether to decode the communications accordingly based on whether the simultaneously received communications match a threshold data rate. Similarly, for transmitting communications, the UE can determine the data rate as the total of the concurrent interfaces, which can include: for each interface through which communications are to be transmitted simultaneously to the access point (e.g., via the Uu interface) and to one or more UEs (e.g., via the sidelink interface), etc., considering multiple CCs, BWPs, etc. The UE can determine whether to encode and / or transmit the communications accordingly based on whether the simultaneously transmitted communications are scheduled to match a threshold data rate.

[0041] The following will refer to Figure 1-7 introduce the features in more detail.

[0042] As used in this application, the terms "component", "module", "system", etc. are intended to include computer-related entities, such as but not limited to hardware, software, combinations of hardware and software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable program, an execution thread, a program, and / or a computer. As an illustration, an application running on a computing device and the computing device can both be components. One or more components can reside within a process and / or an execution thread, and a component can be located on one computer and / or distributed between two or more computers. Additionally, these components can execute from various computer-readable media storing various data structures. These components can communicate through local and / or remote processes, e.g., according to a signal having one or more data packets, such as data from a component, which interacts with another component in a local system, a distributed system, and / or with other systems through a network such as the Internet. Software should be broadly interpreted to represent instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, execution threads, processes, functions, etc., whether it is referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0043] The techniques described herein can be used in a variety of wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other systems. The terms "system" and "network" are generally used interchangeably. CDMA systems can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and so on. CDMA2000 covers the IS-2000, IS-95, and IS-856 standards. Releases 0 and A of IS-2000 are commonly referred to as CDMA2000 1X, 1X, and so on. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), and so on. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. TDMA systems can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA systems can implement radio 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 TM and so on. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE-A, and GSM are described in the literature from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in the literature from an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein can be used in the systems and radio technologies mentioned above and other systems and radio technologies, including cellular (e.g., LTE) communication on shared radio frequency bands. However, the following description describes the LTE / LTE-A system for purposes of example and uses LTE terminology in most of the following description, although these techniques are applicable beyond LTE / LTE-A applications (e.g., applicable to Fifth Generation (5G) New Radio (NR) networks or other next-generation communication systems).

[0044] The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Changes can be made to the functionality and arrangement of the elements discussed without departing from the scope of the present disclosure. Various processes or components can be appropriately omitted, substituted, or added in various examples. For example, the methods described can be performed in an order different from that described, and various steps can be added, omitted, or combined. Additionally, features described with respect to some examples can be combined in other examples.

[0045] Various aspects or features will be presented in accordance with a system that may include several devices, components, modules, and so on. It should be understood and appreciated that various systems may include additional devices, components, modules, and so on, and / or may not include all of the devices, components, modules, and so on discussed in conjunction with the figures. Combinations of these methods may also be used.

[0046] Figure 1 FIG. 4 is a schematic diagram illustrating an example of a wireless communication system and an access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes base stations 102, UEs 104, and an evolved packet core (EPC) 160 and / or a 5G core (5GC) 190. The base stations 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). The macro cells may include base stations. The small cells may include femto cells, pico cells, and micro cells. In one example, the base stations 102 may further include gNBs 180, as further described herein. In one example, some nodes of the wireless communication system may have a modem 240 and a communication component 242 for: decoding communications received through one or more interfaces, encoding / transmitting communications through one or more interfaces, and so on. Additionally, as described herein, some nodes may have a modem 340 and a scheduling component 342 for configuring the communication resources of the UEs on one or more interfaces. Although the UE 104 is shown as having a modem 240 and a communication component 242, and the 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 any type of node may include a modem 240 and a communication component 242 and / or a modem 340 and a scheduling component 342 to provide the corresponding functions described herein.

[0047] 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)) is interfaced with the EPC 160 via a backhaul link 132 (e.g., using the S1 interface). The base station 102 configured for 5G NR (which may be collectively referred to as the Next Generation RAN (NG-RAN)) may be interfaced with the 5GC 190 via a backhaul link 184. Among other functions, the base station 102 may perform one or more of the following functions: transfer 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), user and device tracking, radio access network information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly (e.g., via the EPC 160 or the 5GC 190) with each other via a backhaul link 134 (e.g., using the X2 interface). The backhaul link 134 may be wired or wireless.

[0048] 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, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network including small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group that 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 referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple-input and multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be over one or more carriers. The base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) per carrier allocated in carrier aggregation of up to Yx MHz (e.g., for x component carriers) for transmission in the DL and / or UL directions. The carriers may be adjacent to each other or non-adjacent. The allocation of carriers may be asymmetric for the DL and UL (e.g., more or fewer carriers may be allocated for the DL than for the UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carriers may be referred to as secondary cells (SCells).

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

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

[0051] The small cell 102' may operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell 102' may adopt NR and use the same 5 GHz unlicensed spectrum as that used by the Wi-Fi AP 150. The small cell 102' adopting NR in the unlicensed spectrum may improve the coverage of the access network and / or increase the capacity of the access network.

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

[0053] 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 communicate with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that processes signaling between the UE 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All User Internet Protocol (IP) packets are routed through the Serving Gateway 166, which is itself 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 an IP service 176. The IP service 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 functions for MBMS user service provision 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 for a particular broadcast service, and may be responsible for session management (start / stop) and for collecting charging information related to eMBMS.

[0054] The 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. The AMF 192 may communicate with a Unified Data Management (UDM) 196. The AMF 192 is a control node that processes signaling between the UE 104 and the 5GC 190. Generally, the AMF 192 provides QoS flow and session management. User Internet Protocol (IP) packets (e.g., from one or more UEs 104) may be routed through the UPF 195. The UPF 195 may provide UE IP address allocation and other functions for one or more UEs. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS streaming service, and / or other IP services.

[0055] A base station may also be referred to as a gNB, Node B, evolved Node B (eNB), access point, base station transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit receive point (TRP), or some other appropriate 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, laptop computers, personal digital assistants (PDAs), satellite radio devices, positioning systems (e.g., satellite, terrestrial), multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, gaming consoles, tablet computers, smart devices, robots, drones, industrial / manufacturing equipment, wearable devices (e.g., smart watches, smart clothing, smart glasses, virtual reality glasses, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), vehicle / vehicle equipment, meters (e.g., parking meters, electricity meters, fuel gauges, water meters, flow meters), fuel pumps, large or small kitchen appliances, medical / healthcare equipment, implants, sensors / actuators, displays, or any other similar functional device. Some of UE 104 may be referred to as IoT devices (e.g., meters, 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 this disclosure, eMTC and NB-IoT may refer to future technologies that can evolve from or be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further 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, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

[0056] In one example, the communication component 242 of UE 104-a (and / or other UEs) can receive communications through one or more interfaces, such as the Uu interface from one or more base stations 102 and the sidelink interface from one or more UEs (e.g., UE 104-b). For example, the communication component 242 can determine whether the simultaneously received communications meet the threshold data rate at UE 104-a. Additionally, for example, the scheduling component 342 can attempt to send a communication to UE 104-a that, together with any other communications that UE 104-a may be receiving from other devices (e.g., communications received from one or more other UEs via the sidelink, communications received from one or more other base stations 102 via the Uu interface, etc.), meets the threshold data rate.

[0057] Turning now to Figure 2-7 , aspects can be described with reference to one or more components and one or more methods that can perform the actions or operations described herein, where the aspects in the dashed lines can be optional. Although the operations described below are presented in a particular order and / or presented as being performed by example components, it should be understood that the order of the actions and the components performing the actions can vary depending on the implementation. Additionally, it should be understood that the following actions, functions, and / or components described can be performed by a specially programmed processor, a processor executing specially programmed software or a computer-readable medium, or any other combination of hardware components and / or software components capable of performing the described actions or functions. Figure 4-6

[0058] Figure 2 Referring to , an example of an implementation of UE 104 can include various components, some of which have been described above and are further described herein, including components such as one or more processors 212, a memory 216, and a transceiver 202 that communicate via one or more buses 244, which can operate in conjunction with a modem 240 and / or a communication component 242 to determine whether a communication meets the threshold data rate, as described herein.

[0059] In one aspect, one or more processors 212 may include a modem 240 and / or may be part of a modem 240 that uses one or more modem processors. Accordingly, 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, one or more processors 212 may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receive processor, or a transceiver processor associated with the transceiver 202. In other aspects, some 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.

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

[0061] 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 executable by a processor, including instructions and code 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 these received signals and may also obtain measurement results 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), and the like. The transmitter 208 may include hardware for transmitting data and / or software executable by a processor, including instructions and code stored in a memory (e.g., a computer-readable medium). Suitable examples of the transmitter 208 may include, but are not limited to, RF transmitters.

[0062] In addition, in one aspect, the UE 104 may include an RF front end 288, which may communicate with one or more antennas 265 and a transceiver 202 for receiving and transmitting wireless transmissions, such as wireless communications sent by at least one base station 102 or wireless transmissions sent by the UE 104. The RF front end 288 may be connected to one or more antennas 265 and may include one or more low-noise amplifiers (LNAs) 290 for transmitting and receiving RF signals, one or more switches 292, one or more power amplifiers (PAs) 298, and one or more filters 296.

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

[0064] In addition, for example, the RF front end 288 may use one or more PAs 298 to amplify the signal for RF output to an expected output power level. In one aspect, each PA 298 may have specified minimum and maximum gain values. In one aspect, the RF front end 288 may use one or more switches 292 to select a particular PA 298 and its specified gain value based on the expected gain value for a particular application.

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

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

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

[0068] In one aspect, as described herein, the communication component 242 can optionally include a data rate determination component 252 for determining the data rate of the communication received through one or more interfaces, and a decoding component 254 for decoding the communication based on determining whether the data rate meets a threshold data rate configured for the UE 104.

[0069] In one aspect, the (one or more) processors 212 can correspond to one or more of the processors described in the UE in connection with Figure 7 Similarly, the memory 216 can correspond to the memory described in the UE in connection with Figure 7

[0070] Refer to Figure 3 ​, An example of an implementation of base station 102 (e.g., base station 102 and / or gNB 180 as described above) can include various components, some of which have been described above, but including components such as one or more processors 312 and memory 316 that communicate via one or more buses 344, and transceiver 302, which can operate in conjunction with modem 340 and scheduling component 342 to configure the communication of UE 104 over one or more interfaces, as described herein.

[0071] 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 can be the same as or similar to the corresponding components of UE 104 as described above, but are configured or otherwise programmed for base station operations corresponding to UE operations.

[0072] In one aspect, scheduling component 342 may optionally include a data rate configuration component 352 for configuring the data rate or related parameters of the communication to be sent to the UE, and / or a resource configuration component 354 for configuring the communication resources of the UE on one or more interfaces (e.g., uplink / downlink resources on the Uu interface, sidelink resources on the sidelink interface, etc.).

[0073] In one aspect, (one or more) processors 312 may correspond to one or more of the processors described in connection with the base station in Figure 7 Similarly, memory 316 may correspond to the memory described in connection with the base station in Figure 7

[0074] Figure 4 A flowchart showing an example of a method 400 for determining the data rate associated with communications received simultaneously over multiple interfaces is shown. In one example, a UE (e.g., UE 104-a) can use Figure 1 and 2 one or more of the components described in

[0075] ​In method 400, at block 402, downlink communication may be received from an access point on a downlink resource set. In one aspect, communication component 242, such as in conjunction with (one or more) processors 212, memory 216, transceiver 202, etc., may receive downlink communication from an access point (e.g., base station 102, which may be a gNB) on a downlink resource set. For example, the downlink communication may include communication received via the PDSCH, physical downlink control channel (PDCCH), or other downlink channels. The downlink communication may be received according to a modulation and coding scheme (MCS), transport block size (TBS), etc., which may result in a data rate for the downlink communication (e.g., based on the above formula). Additionally, for example, communication component 242 may receive downlink communication from an access point in a corresponding cell and / or from one or more other access points and / or other cells of the access point. Further, for example, communication component 242 may receive downlink communication via one or more CCs, BWPs, etc.

[0076] In one example, in method 400, optionally, at block 404, a downlink grant for downlink resources may be received from an access point. In one aspect, communication component 242, such as in conjunction with (one or more) processors 212, memory 216, transceiver 202, etc., may receive a downlink grant for downlink resources from an access point. For example, communication component 242 may receive the downlink grant via a control channel (e.g., PDCCH) with the access point. In other examples, UE 104 may receive a downlink grant for downlink resources from one or more other access points and / or cells.

[0077] In method 400, at block 406, sidelink communication may be received from a UE on a sidelink resource set that overlaps with the downlink resource set in the time domain. In one aspect, communication component 242, such as in conjunction with (one or more) processors 212, memory 216, transceiver 202, etc., may receive sidelink communication from a UE on a sidelink resource set that overlaps with the downlink resource set in the time domain. In this example, communication component 242 may receive downlink communication and sidelink communication simultaneously. For example, the sidelink communication may include communication received via the PSSCH, PSCCH, or other sidelink channels. The sidelink communication may be received according to MCS, TBS, etc., which may result in a data rate for the sidelink communication (e.g., based on the above formula). Additionally, for example, communication component 242 may receive sidelink communication via one or more CCs, BWPs, etc.

[0078] In addition, although aspects are generally described herein in the context of downlink communication and sidelink communication (e.g., the Uu interface and the sidelink interface), these concepts can be similarly applied to other types of interfaces where the UE receives communication and / or the communication may be subject to data rate constraints for decoding through these interfaces.

[0079] In one example, in method 400, optionally, at block 408, a sidelink grant for sidelink resources can be received from an access point. In one aspect, communication component 242, e.g., in conjunction with (one or more) processors 212, memory 216, transceiver 202, etc., can receive a sidelink grant for sidelink resources from an access point. For example, communication component 242 can receive the sidelink grant through a control channel (e.g., PDCCH) with the access point. This can be part of the above-described resource allocation mode 1, where base station 102 can configure sidelink communication resources for UE 104 to use in communication with other UEs, and the configured resources can be exact and / or can be a set of resources from which the UE (and / or other UEs) can select resources for sidelink communication. In other examples, as described (e.g., in resource allocation 2), UE 104 can determine sidelink resources (e.g., without a grant) based on sensing, measuring, reserving, etc. of resources using pre-talk listening or other idle channel assessment strategies.

[0080] In method 400, at block 410, it can be determined whether the downlink communication and the sidelink communication meet a threshold data rate. In one aspect, data rate determination component 252, e.g., in conjunction with (one or more) processors 212, memory 216, transceiver 202, communication component 242, etc., can determine whether the downlink communication and the sidelink communication meet a threshold data rate. For example, data rate determination component 252 can determine the threshold data rate at or configured by UE 104 as described above, and can determine whether the data rates of the downlink communication and the sidelink communication (e.g., when considering these communications together for simultaneously received communication) are less than or equal to the threshold data rate. For example, data rate determination component 252 can determine the total data rate by adding the calculated data rate of the downlink communication to the data rate of the sidelink communication received simultaneously therewith, and can compare the total data rate with the threshold data rate. In addition, the downlink communication can include downlink communication received through one or more CCs or BWPs, from one or more cells of the same or different gNBs, from one or more same or different operators / PLMNs, etc., and the sidelink communication can include sidelink communication received from one or more UEs through one or more CCs or BWPs, related to the same or different operators / PLMNs, etc.

[0081] When the downlink communication and the sidelink communication comply with the data rate at block 410, at block 412, at least one of the downlink communication or the sidelink communication can be decoded. In one aspect, the decoding component 254, such as in conjunction with one or more processors 212, memory 216, transceiver 202, communication component 242, etc., can decode at least one of the downlink communication or the sidelink communication or a combination thereof. Optionally, in the case where the downlink communication and the sidelink communication do not comply with the data rate at block 410, at block 414, an error event can be determined and / or reported. In one aspect, the decoding component 254, such as in conjunction with one or more processors 212, memory 216, transceiver 202, communication component 242, etc., can determine and / or report an error event. For example, the decoding component 254 can report the error event to an interface (e.g., Uu interface or sidelink interface), to a sending entity (e.g., a base station for downlink communication or another UE for sidelink communication), etc.

[0082] Figure 5 A flowchart illustrating an example of a method 500 for determining data rates associated with communications transmitted simultaneously over multiple interfaces is shown. In one example, a UE (e.g., UE 104-a) can use Figure 1 and 2 one or more components described in to perform the functions described in method 400.

[0083] In method 500, at block 502, it can be determined whether the uplink communication and the sidelink communication comply with a threshold data rate. In one aspect, the data rate determination component 252, such as in conjunction with one or more processors 212, memory 216, transceiver 202, communication component 242, etc., can determine whether the uplink communication and the sidelink communication comply with the threshold data rate. For example, the data rate determination component 252 can determine the threshold data rate at or configured by the UE 104 as described above, and can determine whether the data rates of the uplink communication and the sidelink communication (e.g., for simultaneously transmitted communications, when considered together (e.g., summed), whether the data rates of these communications) are less than or equal to the threshold data rate.

[0084] For example, the data rate determination component 252 can determine the total data rate by adding the data rates of the calculated uplink communication and the sidelink communication that are sent simultaneously with each other (or are scheduled to be sent simultaneously with each other, e.g., sent simultaneously within overlapping time periods). In this example, the data rate determination component 252 can compare the total data rate with a threshold data rate. For example, the data rate determination component 252 can determine the data rate for the uplink communication based on one or more parameters for sending the uplink communication, as described above, and the parameters can be configured by the base station 102. For example, the data rate determination component 252 can determine the data rate for the sidelink communication based on one or more parameters for sending the sidelink communication, as described above, and the parameters can be configured by the base station 102, the UE 104, one or more other UEs 104, etc. In addition, the uplink communication can include uplink communications that are scheduled to be sent through one or more CCs or BWPs, sent to one or more cells of the same or different gNBs, sent to one or more of the same or different operators / PLMNs, etc., and the sidelink communication can include sidelink communications sent to one or more UEs through one or more CCs or BWPs, sidelink communications related to the same or different operators / PLMNs, etc.

[0085] In the case where the uplink communication and the sidelink communication at block 502 meet the threshold data rate, at block 504, the uplink communication can be sent to the access point on the uplink resource set. In one aspect, the communication component 242, e.g., in combination with (one or more) processors 212, memory 216, transceiver 202, etc., can send the uplink communication to the access point (e.g., the base station 102) on the uplink resource set. For example, the communication component 242 can use the parameters for determining the data rate (e.g., and through the Uu interface) to send the uplink communication, as described above. For example, this can also include: determining to encode the uplink communication for transmission on the scheduled resources. Additionally, in the case where the uplink communication and the sidelink communication at block 502 meet the threshold data rate, at block 506, the sidelink communication can be sent to one or more UEs on the sidelink resource set. In one aspect, the communication component 242, e.g., in combination with (one or more) processors 212, memory 216, transceiver 202, etc., can send the sidelink communication to one or more UEs on the sidelink resource set (e.g., and through the sidelink interface). For example, the communication component 242 can use the parameters for determining the sidelink data rate to send the sidelink communication, as described above. For example, this can also include determining to encode the sidelink communication for transmission on the scheduled resources.

[0086] In the case where the uplink communication and the sidelink communication at block 502 do not meet the threshold data rate, optionally, at block 508, an error event may be determined and / or reported. In one aspect, the communication component 242, e.g., in conjunction with (one or more) processors 212, memory 216, transceiver 202, etc., may determine and / or report the error event. For example, the communication component 242 may report the error event to an interface (e.g., the Uu interface or the sidelink interface), to a receiving entity (e.g., a base station for uplink communication or another UE for sidelink communication), etc.

[0087] In one example, optionally, at block 510, an uplink grant for uplink resources may be received from an access point. In one aspect, the communication component 242, e.g., in conjunction with (one or more) processors 212, memory 216, transceiver 202, etc., may receive the uplink grant for uplink resources from an access point (e.g., base station 102, which may be a gNB). For example, the uplink grant may include uplink resources for transmission via PUCCH, PUSCH, etc. Further, in one example, the uplink grant may include or may otherwise indicate one or more other parameters for transmitting the uplink communication, or be related to one or more other parameters for transmitting the uplink communication, such as MCS, TBS, etc., which may result in a data rate for the uplink communication (e.g., based on the above formula). Additionally, for example, the communication component 242 may send the uplink communication to the access point in the corresponding cell and / or to one or more other access points and / or other cells of the access point. Further, for example, the communication component 242 may send the uplink communication via one or more CCs, BWPs, etc.

[0088] In one example, in method 500, optionally, at block 512, a sidelink authorization for sidelink resources may be received from an access point. In one aspect, the communication component 242, e.g., in conjunction with (one or more) processors 212, memory 216, transceiver 202, etc., may receive a sidelink authorization for sidelink resources from an access point. For example, the communication component 242 may receive the sidelink authorization via a control channel (e.g., PDCCH) with the access point. This may be part of the above-described resource allocation mode 1, where the base station 102 may configure sidelink communication resources for use by the UE 104 in communication with other UEs, where the configured resources may be exact and / or may be a set of resources from which the UE (and / or other UEs) may select resources for sidelink communication. In other examples, as described (e.g., in resource allocation 2), the UE 104 may determine sidelink resources (e.g., without authorization) based on sensing, measuring, reserving, etc., resources using a pre-talk listen or other idle channel assessment strategy.

[0089] Figure 6 A flowchart of an example of a method 600 for scheduling resources and / or communication based on determining data rates associated with multiple interfaces is shown. In one example, an access point (e.g., base station 102, which may be a gNB) may use Figure 1 and 3 one or more components described in to perform the functions described in method 600. For example, when the UE 104 is using multiple interfaces (e.g., Uu and sidelink) simultaneously, the access point may take steps or actions to attempt to ensure that a threshold data rate (also referred to as a maximum data rate) at the UE 104 is not violated.

[0090] In method 600, at block 602, an indication of a threshold data rate supported by a UE may be received. In one aspect, a data rate configuration component 352, e.g., in conjunction with one or more processors 312, memory 316, transceiver 302, scheduling component 342, etc., may receive an indication of a threshold data rate supported by a UE (e.g., UE 104). For example, UE 104 may configure the threshold data rate and may provide the value to base station 102. In another example, UE 104 may configure the threshold data rate of UE 104 based on one or more other parameters of UE 104 (e.g., UE category, quality of service (QoS) requirements, etc.). Additionally, in one example, the data rate configuration component 352 may receive one or more parameters configured for UE 104 or one or more parameters configured by UE 104, which may be used to calculate the threshold data rate. As described above, the threshold data rate may be related to the maximum data rate at which a UE (e.g., UE 104) may receive communications (e.g., receive simultaneously over multiple interfaces) for decoding, where the UE may avoid decoding received communications that exceed the threshold data rate. In another example, the threshold data rate may be related to the maximum data rate at which a UE (e.g., UE 104) may send communications (e.g., simultaneously over multiple interfaces), where the UE may avoid sending and / or encoding communications that exceed the threshold data rate.

[0091] In method 600, at block 604, a set of sidelink resources configured for a UE to communicate with one or more other UEs may be determined. In one aspect, a data rate configuration component 352, e.g., in conjunction with one or more processors 312, memory 316, transceiver 302, scheduling component 342, etc., may determine a set of sidelink resources configured for a UE (e.g., UE 104) to communicate with one or more other UEs. For example, the scheduling component 342 may have configured the set of sidelink resources, and the data rate configuration component 352 may accordingly determine the set of sidelink resources it has configured. In other examples, the data rate configuration component 352 may not know the sidelink resources used by UE 104 (e.g., in the case where UE 104 determines the resources, such as in resource allocation mode 2, and / or in the case where the resources correspond to another operator / PLMN, etc.). Additionally, as described, the set of sidelink resources may correspond to one or more CCs, BWPs, operators / PLMNs, etc. The sidelink resources may correspond to resources used by UE 104 in sending sidelink communications to one or more other UEs and / or resources used by UE 104 in receiving sidelink communications from one or more other UEs.

[0092] In method 600, at block 606, a set of resources configured for communication with one or more cells may be determined for a UE. In one aspect, a data rate configuration component 352, e.g., in conjunction with (one or more) processors 312, memory 316, transceiver 302, scheduling component 342, etc., may determine a set of resources configured for communication with one or more cells (e.g., a cell of base station 102 or other cells) for a UE (e.g., UE 104). In one example, the scheduling component 342 may allocate downlink resources for UE 104, and the data rate configuration component 352 may accordingly determine a downlink resource set. In another example, the data rate configuration component 352 may determine downlink resources allocated to UE 104 by other cells (e.g., other cells of base station 102 or other cells from other base stations in the same or different operator / PLMN, etc.). Similarly, in one example, the scheduling component 342 may allocate uplink resources for UE 104, and the data rate configuration component 352 may accordingly determine an uplink resource set. In another example, the data rate configuration component 352 may determine uplink resources allocated to UE 104 by other cells (e.g., other cells of base station 102 or other cells from other base stations in the same or different operator / PLMN, etc.). Additionally, as described above, the set of resources may correspond to one or more CCs, BWPs, operator / PLMNs, etc.

[0093] In method 600, at block 608, one or more parameters for communication with the UE may be determined based on a threshold data rate. In one aspect, a data rate configuration component 352, e.g., in conjunction with (one or more) processors 312, memory 316, transceiver 302, scheduling component 342, etc., may determine one or more parameters for communication with a UE (e.g., UE 104) based on a threshold data rate. For example, the data rate configuration component 352 may determine one or more downlink parameters that are or include the data rate used in transmitting downlink communication to UE 104, which may be based on the threshold data rate and / or the determined downlink resource set, sidelink resource set, and / or other parameters. In another example, the data rate configuration component 352 may determine one or more downlink parameters that are or include parameters for calculating or estimating the data rate for transmitting downlink communication to the UE, e.g., the number of configured serving cells belonging to a frequency range as described above, the number of TBs transmitted in a time slot, the digital scheme of the PDSCH, the number of bits in the transport block, the number of code blocks or scheduled code blocks of the transport block, etc.

[0094] In another example, the data rate configuration component 352 may determine one or more uplink parameters that are or include the data rate used when scheduling the UE 104 for transmitting uplink communications, which may be based on a threshold data rate and / or the determined set of uplink resources, sidelink resources, and / or other parameters. In another example, the data rate configuration component 352 may determine one or more uplink parameters that are or include parameters for calculating or estimating the data rate of uplink communications at the UE, e.g., the number of configured serving cells belonging to a frequency range as described above, the number of TBs transmitted in a time slot, the digital scheme of the PDSCH, the number of bits in a transport block, the number of code blocks of a transport block or the number of scheduled code blocks, and so on.

[0095] For example, in method 600, optionally at block 610, an expected data rate may be calculated based on one or more parameters. In one aspect, the data rate configuration component 352, e.g., in conjunction with (one or more of) the processor 312, the memory 316, the transceiver 302, the scheduling component 342, etc., may calculate the expected data rate, which may be for an interface such as the Uu interface. For example, the data rate configuration component 352 may also calculate the expected data rate based on a set of sidelink resources, where the sidelink resources at least partially overlap in time with the resource set, as further described herein (e.g., where the sidelink resources for receiving communications overlap with the set of downlink resources, or where the sidelink resources for transmitting communications overlap with the set of uplink resources). Additionally, in one example, the data rate configuration component 352 may determine one or more parameters based on the expected data rate (e.g., determine downlink parameters based on the expected downlink data rate and / or determine uplink parameters based on the expected uplink data rate).

[0096] For example, in method 600, optionally at block 612, an expected sidelink data rate may be calculated based on one or more sidelink parameters. In one aspect, the data rate configuration component 352, e.g., in conjunction with (one or more of) the processor 312, the memory 316, the transceiver 302, the scheduling component 342, etc., may calculate the expected sidelink data rate based on one or more sidelink parameters. Further, in one example, the data rate configuration component 352 may determine one or more parameters based on the expected sidelink data rate (e.g., one or more downlink parameters for simultaneous UE reception or one or more uplink parameters for simultaneous UE transmission), as further described herein.

[0097] In method 600, at block 614, a resource grant for indicating a resource set or at least one of corresponding communications may be sent to a UE based on one or more parameters. In one aspect, a resource configuration component 354, such as in conjunction with (one or more of) processor 312, memory 316, transceiver 302, scheduling component 342, etc., may send a resource authorization for indicating a resource set or at least one of corresponding communications to a UE based on one or more parameters. For example, the resource configuration component 354 may configure and send a resource authorization or communication based on an expected data rate and / or an expected sidelink data rate to attempt to meet a threshold data rate at UE 104, as described in various scenarios / examples herein. In one example, this may include the resource configuration component 354 configuring and / or sending a downlink resource authorization or downlink communication based on an expected downlink data rate and / or an expected sidelink data rate to attempt to meet the threshold data rate at UE 104 that receives downlink communications and sidelink data communications. In another example, this may include the resource configuration component 354 configuring and / or sending an uplink resource authorization or uplink communication based on an expected uplink data rate and / or an expected sidelink data rate to attempt to meet the threshold data rate at UE 104 that sends uplink communications and sidelink data communications.

[0098] Similarly, in one example, such as in resource allocation scheme 1 where base station 102 schedules sidelink resources for a UE, in method 600, optionally at block 616, one or more sidelink parameters for sidelink communications to the UE may be determined based on a threshold data rate. In one aspect, a data rate configuration component 352, such as in conjunction with (one or more of) processor 312, memory 316, transceiver 302, scheduling component 342, etc., may determine one or more sidelink parameters for sidelink communications to a UE (e.g., UE 104) based on the threshold data rate. For example, the data rate configuration component 352 may determine one or more sidelink parameters that are or include the data rate used in receiving (and / or for other UEs in sending) sidelink communications, which may be based on the threshold data rate and / or based on the determined downlink resource set, sidelink resource set, and / or other parameters.

[0099] In this example, in method 600, optionally, at block 618, a sidelink resource grant indicating a set of sidelink resources may be sent to the UE (and / or other UEs) based on one or more sidelink parameters. In one aspect, the resource configuration component 354, e.g., in conjunction with (one or more of) the processor 312, the memory 316, the transceiver 302, the scheduling component 342, etc., may send a sidelink resource grant indicating a set of sidelink resources to the UE (and / or other UEs) based on one or more sidelink parameters. For example, the resource configuration component 354 may configure and send the sidelink resource grant based on the expected downlink data rate and / or the expected sidelink data rate to attempt to meet the threshold data rate at the UE 104, as described in various scenarios / examples herein.

[0100] Although described in terms of downlink communication and receiving sidelink communication on the Uu interface, the functionality described herein may be similarly applied to sending uplink communication and sending sidelink communication (e.g., simultaneously) over the Uu interface to determine data rates, etc., for simultaneously sending uplink communication and sidelink communication.

[0101] In a particular example, to enable data sharing, various scenarios may be considered. In a first scenario, the data rate determination component 352 may consider a single set of parameter values per CC for each frequency band or combination of frequency bands (e.g., at blocks 608, 610, etc.) when determining the data rate of the UE and / or other downlink parameters for scheduling resources for the UE and / or sending downlink communication to the UE. In one example, the UE 104 may report its capabilities for different parameters (e.g., together with or similar to reporting its threshold data rate at block 602). The parameters may include the number of layers, the modulation order, the parameter f, etc. In one example, the UE 104 may report its capabilities to the base station 102 (e.g., if within cell coverage) or to a second UE in sidelink communication, where the second UE may report the capabilities on behalf of the UE. As described herein, the data rate determination component 352 may use these parameters to calculate the maximum data rate as described herein, where the maximum data rate may be calculated for each CC and may include: calculating the data rate based on the maximum value of the parameter values for each interface or based on calculating the data rate for each interface and selecting the maximum value of the data rates.

[0102] For example, if different parameter values are considered and / or reported for each parameter of Uu and sidelink (SL), the data rate determination component 352 may calculate one or more downlink parameters (e.g., at block 608) in accordance with or based on jointly determining the threshold data rates of Uu and SL. For example, the data rate determination component 352 may separately calculate the total threshold data rates of Uu and SL based on different parameter values, and then use the maximum data rate as the threshold for the check condition. For example, as described above, this may include using the following formula to separately calculate the total data rate of each interface:

[0103]

[0104] In another example, the data rate determination component 352 may take the maximum value for each parameter associated with each interface, and then calculate the data rate to be used as a threshold for the check condition or otherwise determine resource scheduling or other parameters for downlink and / or sidelink communication to UE 104.

[0105] Additionally, in one example, to calculate the data rate for SL (e.g., at block 612), if multiple resource pools are configured for SL and the configured parameters of each resource pool are different, the data rate determination component 352 may take the maximum value of each parameter, or then calculate the maximum data rate again, and use the maximum value among the calculated maximum data rates as the candidate maximum data rate for SL (e.g., for the calculation of the above threshold data rate). This may apply to both DL data sharing and UL data sharing. Additionally, to take the maximum value for each parameter, as described above, BW may be an exception because for data rate sharing, it is set to the component carrier BW. In any case, in the first scenario, the data rate determination component 352 may determine one or more sidelink parameters for sidelink communication at the UE based on the threshold data rate, and may send a sidelink resource grant indicating the sidelink resources based on the one or more sidelink parameters.

[0106] In another example of this solution, the data rate determination component 352 can calculate the expected data rate for communication on the Uu interface (e.g., at block 610) based on one or more parameters corresponding to the Uu interface (e.g., uplink parameters or downlink parameters), can calculate the expected sidelink data rate for sidelink communication (e.g., at block 612) based on one or more sidelink parameters, and / or can determine one or more Uu parameters (e.g., at block 608) or sidelink parameters (e.g., at block 616) based on comparing the maximum of the expected Uu data rate and the expected sidelink data rate with a threshold data rate. As described, in an example where there are multiple sidelink resource pools, calculating the expected sidelink data rate can include calculating the data rate for each resource pool and taking the maximum value. In another example of this solution, the data rate determination component 352 can calculate the expected maximum data rate for Uu communication based on determining the maximum value of each of one or more Uu parameters or one or more sidelink parameters, and / or can determine one or more Uu parameters or sidelink parameters based on comparing the maximum expected Uu data rate with a threshold data rate. Similarly, in this example, for multiple sidelink resource pools, the expected sidelink data rate can be the maximum value of the data rates calculated for each pool.

[0107] In a second solution, the data rate determination component 352 can consider separate sets of data rate parameters for Uu and SL for each component carrier for each frequency band or combination of frequency bands. In this case, the data rate determination component 352 can calculate and check the threshold data rate (e.g., as the Uu parameter or sidelink parameter as described above) separately between the Uu carrier and the SL carrier. Even if both SL and Uu are supported on one CC, for the purpose of data rate calculation, the data rate determination component 352 can treat these interfaces as two carriers (or virtual carriers) (e.g., at blocks 610 and / or 612). For example, given that CC1 only has Uu, CC2 has Uu and SL, and CC3 only has SL, the data rate determination component 352 can calculate the threshold data rate for Uu on CC1 and CC2 and the threshold data rate for SL on CC2 and CC3. The scheduling component 342 can schedule Uu DL / UL on CC1 and CC2 such that the data rate conditions for Uu DL / UL are met (e.g., based on sending resource authorization at block 614). Similarly, in the case where the scheduling component 342 schedules sidelink resources, the scheduling component 342 can schedule SL Tx / Rx on CC2 and CC3 so as to meet the data rate conditions for SL Tx / Rx (e.g., based on sending resource authorization at block 618).

[0108] In any case, in the second scenario, the data rate determination component 352 may determine one or more sidelink parameters for sidelink communication at the UE based on a threshold data rate, and may send a sidelink resource grant indicating the sidelink resources based on the one or more sidelink parameters.

[0109] In another example of this scenario, the data rate determination component 352 may calculate an expected Uu data rate for communication on the Uu interface (e.g., uplink communication or downlink communication at block 610) based on one or more Uu parameters, may calculate an expected sidelink data rate for sidelink communication (e.g., at block 612) based on one or more sidelink parameters, may determine one or more Uu parameters based on comparing the expected Uu data rate with the threshold data rate (e.g., at block 608), and / or may determine sidelink parameters based on comparing the expected sidelink data rate with the threshold data rate (e.g., at block 616).

[0110] In one example, the first and second scenarios above may be used in various scenarios of combinations of per-interface operator / PLMN, cell / gNB, CC, BWP, and so on. Thus, for example, the data rate determination component 352 may determine which scenario to apply when further determining the data rate, as described below.

[0111] As described, in the first scenario, the interface can correspond to the same operator / PLMN and the same cell / gNB. In this example, assuming resource allocation mode 1 (where the gNB schedules Uu and sidelink resources), and (2) timing capability 1 for both Uu and SL, data sharing across SL carriers and Uu carriers can be allowed and can be based on the above first scheme. For example, in resource allocation mode 1, transmission / reception is under the control of the same gNB, so the gNB can ensure that the data rate condition is not violated. For data rate sharing in DL for DL / reception and in UL for UL / transmission, the timing capability condition can be met. For the DL / reception part, for example, the UE receives the PDSCH on Uu and can report HARQ-ACK on the PUCCH. The N1 gap can be based on the minimum processing timing capability 1. The UE can also receive the PSSCH from another UE on SL and can send the HARQ-ACK back to the other UE on the physical sidelink feedback channel (PSFCH). The gap between the end of the PSSCH and the start of the PSFCH can also be based on timing capability 1. For the UL / transmission part, the UE can receive UL authorization from the gNB and can send the PUSCH. The N2 gap can be based on the minimum processing timing capability 1. The UE can also receive downlink control information (DCI) from the gNB, which schedules the PSCCH / PSSCH transmission to another UE on the sidelink. The gap between the end of the PDCCH carrying the DCI and the start of the PSCCH / PSSCH can also be based on timing capability 1.

[0112] For another option, when data rate calculation and comparison are performed separately for Uu and SL, data rate sharing for SL can be performed only on the CC / BWP / resource pool configured with timing capability #1.

[0113] In the example of scenario 1 above, SL and Uu can be on the same component carrier. In this example, for reception, the SL receiving UE can receive the PDSCH on the Uu BWP and the PSSCH on the SL BWP. These two transmissions may overlap and the UE may be able to decode both (e.g., as long as the data sharing condition across the aggregated component carriers is met, there is no problem). If the UE cannot handle two overlapping (unicast) PDSCH / PSSCH, one of them may not be processed. Similarly in this case, if the data rate sharing condition across the aggregated component carriers is met, there may be no problem.

[0114] If a component carrier is configured with timing capability 2, and if the UE supports both Uu and SL on the same component carrier, then both Uu operation and SL operation can be based on timing capability 2. In this case, the maximum data rate of the same carrier can be satisfied regardless of whether the UE can handle overlapping Uu channels and SL channels or discard one channel (i.e., the carrier cannot be used for data sharing). In another case, in this example, assuming that the BWPs for Uu and SL are independently configured, the timing capabilities of Uu and SL can also be independently configured. For example, Uu Tx / Rx can be based on capability 2, while SL operation can be based on capability 1. In this case, the data rate determination component 352 can calculate and check the data rates for each interface as described above.

[0115] In another example, in resource allocation mode 2 (e.g., where the sidelink UE determines resources based on sensing, measuring, and reserving resources), the gNB may not know when the transmitting UE will send sidelink communication. Therefore, when trying to ensure that no error events occur due to violation of the maximum data rate condition, the gNB can be conservative in its Uu allocation when overlapping with potential SL Rx resources. Thus, the data rate determination component 352 can calculate and check the data rates for each interface separately (e.g., where the sidelink data rate can be calculated based on the UE capability information available to the base station 102 as described above). In another example, Uu resources and SL resources can be fully time-division multiplexed (e.g., non-overlapping in the time domain), in which case a single parameter and / or the corresponding data rate per component carrier or band combination can be considered as described above.

[0116] In the above scenario 2, in the case of using the same operator / PLMN and different cells / gNBs for Uu and SL, even when using resource allocation mode 1, the gNBs may not know about each other's resource allocations. Therefore, the data rate determination component 352 can calculate and check the data rates for each interface as described above. In another example, in scenario 2, Uu resources and SL resources can be fully time-division multiplexed (e.g., non-overlapping in the time domain), in which case a single parameter and / or the corresponding data rate per component carrier or band combination can be considered as described above (e.g., and / or based on the data rate determination component 352 determining that the resources are fully time-division multiplexed).

[0117] In the above scenario 3-1, in the case where there are different operators, UEi Tx is in the band of operator i while Rx is not, the data rate determination component 352 can calculate and check the data rates for each interface separately, as described above. In another example, in scenario 3-1, the Uu PDSCH and SL (Tx or Rx) resources can be fully time-division multiplexed (e.g., non-overlapping in the time domain), in which case a single parameter and / or the corresponding data rate for each component carrier or band combination can be considered, as described above (e.g., and / or based on the data rate determination component 352 determining that the resources are fully time-division multiplexed).

[0118] In the above scenario 3-2, in the case where the SL Tx / Rx of a UE is not within the band of its operator, if the UE is a visiting UE and has a Uu link to the gNB of its own operator, the data rate determination component 352 can calculate and check the data rates for each interface separately, as described above. In another example, in this case, the Uu PDSCH and SL Tx resources can be fully time-division multiplexed (e.g., non-overlapping in the time domain), in which case a single parameter and / or the corresponding data rate for each component carrier or band combination can be considered, as described above (e.g., and / or based on the data rate determination component 352 determining that the resources are fully time-division multiplexed). In another case where the UE is fully roaming, this can be similar to scenario 1 above (where different operators have SL and Uu interfaces for the UE), and the conditions regarding whether to use a single parameter / data rate for the interface or to calculate and check the parameter / data rate separately can be similar to those described above regarding scenario 1. Similarly, in the case where the UE is fully roaming, it can be in a situation similar to scenario 2 above with another operator, in which case the conditions regarding whether to use a single parameter / data rate for the interface or to calculate and check the parameter / data rate separately can be similar to those described above regarding scenario 2.

[0119] Figure 7 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 can illustrate aspects of the wireless communication access network 100 described with reference to Figure 1 described. The base station 102 can be an example of aspects of the base station 102 described with reference to Figure 1 described. In addition, the UE 104 can communicate with another UE on the sidelink resources using similar functions described herein for the communication between the UE 104 and the base station 102.

[0120] 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 is capable of simultaneously transmitting data over multiple communication links. 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 2×2 MIMO communication system where base station 102 transmits two "layers", the rank of the communication link between base station 102 and UE 104 is two.

[0121] At base station 102, transmit (Tx) processor 720 may receive data from a data source. Transmit processor 720 may process the data. Transmit processor 720 may also generate control symbols or reference symbols. Transmit MIMO processor 730 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, or reference symbols (if applicable), and may provide output symbol streams to transmit modulators / demodulators 732 and 733. Each modulator / demodulator 732 to 733 may process its 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 modulators / demodulators 732 and 733 may be transmitted via antennas 734 and 735, respectively.

[0122] UE 104 may be an example of aspects of UE 104 described in Figure 1-2 . At UE 104, UE antennas 752 and 753 may receive the DL signals from base station 102 and may provide the received signals to modulators / demodulators 754 and 755, respectively. Each modulator / demodulator 754 to 755 may condition (e.g., filter, amplify, down-convert, and digitize) its respective received signal to obtain input samples. Each modulator / demodulator 754 to 755 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 756 may obtain the received symbols from modulators / demodulators 754 and 755, perform MIMO detection (if applicable) on the received symbols, and provide detected symbols. Receive (Rx) processor 758 may process (e.g., demodulate, de-interleave, and decode) the detected symbols, provide the decoded data for UE 104 to a data output, and provide the decoded control information to processor 780 or memory 782.

[0123] In some cases, processor 780 may execute stored instructions to instantiate communication component 242 (e.g., refer to Figure 1 and 2 ).

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

[0125] In some cases, the processor 740 may execute stored instructions to instantiate the scheduling component 342 (e.g., refer to Figure 1 and 3 ).

[0126] The components of the UE 104 may be implemented individually or jointly with one or more ASICs that are adapted to perform some or all of the applicable functions in hardware. Each of the mentioned modules may be a unit 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 jointly with one or more ASICs that are adapted to perform some or all of the applicable functions in hardware. Each of the mentioned components may be a unit for performing one or more functions related to the operation of the MIMO communication system 700.

[0127] The above detailed description set forth above in conjunction with the accompanying drawings describes numerous examples and does not represent the only examples that may be implemented or that are within the scope of the claims. The term "example" as used in this specification means "serving as an example, instance, or illustration" and not "preferred" or "superior to other examples". The detailed description includes specific details for providing an understanding of the described techniques. However, the techniques may be practiced without these specific details. In some examples, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0128] Any one of a variety of different technologies and techniques can be used to represent information and signals. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, computer-executable code or instructions stored on a computer-readable medium, or any combination thereof.

[0129] The various illustrative blocks and components described in connection with the present disclosure can be implemented or executed with a specially programmed device designed to perform the functions described herein, such as, but not limited to, a processor, 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 can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. The specially programmed processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0130] The functions described herein can be implemented in hardware, software, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a non-transitory computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope and spirit of the present disclosure and the appended claims. For example, due to the nature of software, the above functions can be implemented using software, hardware, hardwiring, or any combination thereof executed by a specially programmed processor. The features implementing the functions can also be physically located in various positions, including being distributed such that portions of the functions are implemented at different physical locations. Additionally, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, phrases such as "X employs A or B" are intended to mean any natural inclusive arrangement. That is, for example, any of the following instances satisfies the phrase "X employs A or B": X employs A; X employs B; or X employs both A and B. Further, as used herein, including in the claims, the "or" as used in a list of items beginning with "at least one" indicates a disjunctive list, such that a list of, for example, "at least one of A, B, or C" represents A or B or C or AB or AC or BC or ABC (A and B and C).

[0131] Computer-readable media includes both computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Storage media can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instruction or data structures and that can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor. Also, any connection is properly termed a computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of media. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0132] The foregoing description of the disclosure has been provided to enable a person skilled in the art to make or use the disclosure. Those skilled in the art will readily appreciate various modifications to the disclosure, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Additionally, while the elements of the described aspects and / or embodiments may be described or claimed in the singular, the plural forms are also included unless expressly stated to be limited to the singular form. Further, unless otherwise stated, any part or all of any aspect and / or embodiment may be used in conjunction with any other part or all of any other aspect and / or embodiment. Accordingly, the disclosure is not limited to the examples and designs described herein, but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication, comprising: receiving downlink communication from an access point on a downlink resource set; receiving sidelink communication from a user equipment (UE) on a sidelink resource set that at least overlaps with the downlink resource set in the time domain; determining whether to decode at least one of the downlink communication or the sidelink communication based on a first scheme or a second scheme, based on determining whether the downlink communication and the sidelink communication meet a threshold data rate, wherein the first scheme is defined as: determining a total data rate by adding the data rate of the downlink communication and the data rate of the sidelink communication received simultaneously with the downlink communication; comparing the determined total data rate with the threshold data rate to determine whether the determined total data rate is less than or equal to the threshold data rate; and wherein the second scheme is defined as: determining a first total data rate of the downlink communication based on a data rate parameter value of an interface configured to receive the downlink communication; determining a second total data rate of the sidelink communication based on a data rate parameter value of another interface configured to receive the sidelink communication; determining a maximum data rate between the first total data rate and the second total data rate; and comparing the determined maximum data rate with the threshold data rate to determine whether the determined maximum data rate is less than or equal to the threshold data rate; and decoding at least one of the downlink communication or the sidelink communication based on determining to perform decoding.

2. The method according to claim 1, wherein the downlink resource set and the sidelink resource set correspond to the same component carrier.

3. The method according to claim 1, wherein the downlink resource set and the sidelink resource set correspond to different component carriers.

4. The method according to claim 1, further comprising: receiving a downlink grant from the access point indicating the downlink resource set.

5. The method according to claim 4, further comprising: receiving a sidelink grant from the access point indicating the sidelink resource set.

6. The method according to claim 1, wherein determining the total data rate includes: calculating the total data rate of the downlink communication received from each serving cell among one or more serving cells including the access point and the sidelink communication received from one or more transmitting sidelink UEs including the UE; and comparing the total data rate with the threshold data rate.

7. The method according to claim 1, wherein the downlink resource set and the sidelink resource set correspond to the same component carrier, and wherein determining whether to perform decoding is further based on determining whether the downlink communication, the sidelink communication, and communication on a different component carrier meet the threshold data rate.

8. The method according to claim 1, wherein Determining whether to decode at least one of the downlink communication or the sidelink communication includes: determining not to decode at least one of the downlink communication or the sidelink communication, and further includes: performing at least one of determining an error event or reporting an error event based on the determination of not decoding.

9. A method for wireless communication, comprising: Based on a first scheme or a second scheme, determining whether to transmit at least one of the uplink communication and the sidelink communication based on determining whether the uplink communication and the sidelink communication meet a threshold data rate, wherein the first scheme is defined as: Determining a total data rate by adding the data rate of the uplink communication and the data rate of the sidelink communication transmitted simultaneously with the uplink communication; Comparing the determined total data rate with the threshold data rate to determine whether the determined total data rate is less than or equal to the threshold data rate; and wherein the second scheme is defined as: Determining a first total data rate of the uplink communication based on a data rate parameter value of an interface configured to receive the uplink communication; Determining a second total data rate of the sidelink communication based on a data rate parameter value of another interface configured to receive the sidelink communication; Determining a maximum data rate between the first total data rate and the second total data rate; and Comparing the determined maximum data rate with the threshold data rate to determine whether the determined maximum data rate is less than or equal to the threshold data rate; and Transmitting at least one of the uplink communication and the sidelink communication based on the determination of transmission.

10. The method according to claim 9, wherein, The uplink resource set associated with the uplink communication and the sidelink resource set associated with the sidelink communication correspond to the same component carrier.

11. The method according to claim 9, wherein, The uplink resource set associated with the uplink communication and the sidelink resource set associated with the sidelink communication correspond to different component carriers.

12. The method according to claim 9, further comprising: Receiving an uplink grant from an access point indicating an uplink resource set for transmitting the uplink communication to the access point.

13. The method according to claim 12, further comprising: Receiving a sidelink grant from the access point indicating a sidelink resource set.

14. The method according to claim 9, wherein, Determining the total data rate includes: Calculating the total data rate of the uplink communication scheduled to be transmitted to each serving cell among one or more serving cells and the sidelink communication scheduled to be transmitted to each sidelink UE among one or more sidelink UEs; and Comparing the total data rate with the threshold data rate.

15. The method according to claim 9, wherein, The uplink communication and the sidelink communication correspond to the same component carrier, and wherein determining whether to transmit is based on determining whether the uplink communication, the sidelink communication, and communication on a different component carrier meet a threshold data rate.

16. The method according to claim 9, wherein, determining whether to transmit at least one of the uplink communication or the sidelink communication includes: determining not to transmit at least one of the uplink communication or the sidelink communication, and further includes: based on the determination of not transmitting, performing at least one of determining an error event or reporting an error event.

17. An apparatus for wireless communication, comprising: a transceiver; a memory configured to store instructions; and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: receive downlink communication from an access point on a downlink resource set; receive sidelink communication from a user equipment (UE) on a sidelink resource set that at least overlaps with the downlink resource set in the time domain; based on a first scheme or a second scheme, determine whether to decode at least one of the downlink communication or the sidelink communication based on determining whether the downlink communication and the sidelink communication meet a threshold data rate, wherein the first scheme is defined as: determining a total data rate by adding the data rate of the downlink communication and the data rate of the sidelink communication received simultaneously with the downlink communication; and comparing the determined total data rate with the threshold data rate to determine whether the determined total data rate is less than or equal to the threshold data rate; and wherein the second scheme is defined as: determining a first total data rate of the downlink communication based on a data rate parameter value of an interface configured to receive the downlink communication; determining a second total data rate of the sidelink communication based on a data rate parameter value of another interface configured to receive the sidelink communication; determining a maximum data rate between the first total data rate and the second total data rate; and comparing the determined maximum data rate with the threshold data rate to determine whether the determined maximum data rate is less than or equal to the threshold data rate; and based on determining to decode, decode at least one of the downlink communication or the sidelink communication.

18. The apparatus according to claim 17, wherein, the downlink resource set and the sidelink resource set correspond to the same component carrier.

19. The apparatus according to claim 17, wherein, the downlink resource set and the sidelink resource set correspond to different component carriers.

20. The apparatus according to claim 17, wherein, the one or more processors are further configured to: receive from the access point a downlink grant indicating the downlink resource set and a sidelink grant indicating the sidelink resource set.

21. The apparatus according to claim 17, wherein, the one or more processors are configured to determine the total data rate at least in part by: calculating the total data rate of the downlink communication received from each of one or more serving cells including the access point and the sidelink communication received from one or more transmitting sidelink UEs including the UE; and comparing the total data rate with the threshold data rate.

22. The apparatus according to claim 17, wherein, the downlink resource set and the sidelink resource set correspond to the same component carrier, and wherein the one or more processors are configured to: further determine whether to perform decoding based on determining whether the downlink communication, the sidelink communication, and the communication on a different component carrier meet the threshold data rate.

23. The apparatus according to claim 17, wherein, in the case where the one or more processors determine not to decode at least one of the downlink communication or the sidelink communication, the one or more processors are further configured to: perform at least one of determining an error event or reporting an error event based on determining not to perform decoding.

24. An apparatus for wireless communication, comprising: a transceiver; a memory configured to store instructions; and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: determine whether to transmit at least one of the uplink communication or the sidelink communication based on a first scheme or a second scheme and based on determining whether the uplink communication and the sidelink communication meet the threshold data rate, wherein the first scheme is defined as: determining a total data rate by adding the data rate of the uplink communication and the data rate of the sidelink communication transmitted simultaneously with the uplink communication; and comparing the determined total data rate with the threshold data rate to determine whether the determined total data rate is less than or equal to the threshold data rate; and wherein the second scheme is defined as: determining a first total data rate of the uplink communication based on a data rate parameter value of an interface configured to receive the uplink communication; determining a second total data rate of the sidelink communication based on a data rate parameter value of another interface configured to receive the sidelink communication; determining a maximum data rate between the first total data rate and the second total data rate; and comparing the determined maximum data rate with the threshold data rate to determine whether the determined maximum data rate is less than or equal to the threshold data rate; and transmitting the at least one of the uplink communication or the sidelink communication based on determining to transmit.

25. The apparatus according to claim 24, wherein, the uplink resource set associated with the uplink communication and the sidelink resource set associated with the sidelink communication correspond to the same component carrier.

26. The apparatus according to claim 24, wherein, the set of uplink resources associated with the uplink communication and the set of sidelink resources associated with the sidelink communication correspond to different component carriers.

27. The apparatus according to claim 24, wherein, the one or more processors are further configured to: receive from an access point an uplink grant indicating a set of uplink resources for transmitting the uplink communication to the access point and a sidelink grant indicating a set of sidelink resources.

28. The apparatus according to claim 24, wherein, the one or more processors are configured to determine the total data rate at least in part by: calculating the total data rate of the uplink communication scheduled to be transmitted to each of one or more serving cells and the sidelink communication scheduled to be transmitted to each of one or more sidelink UEs; and comparing the total data rate with the threshold data rate.

29. The apparatus according to claim 24, wherein, the uplink communication and the sidelink communication correspond to the same component carrier, and wherein the one or more processors are configured to: determine whether to transmit based on determining whether the uplink communication, the sidelink communication, and the communication on a different component carrier meet the threshold data rate.

30. The apparatus according to claim 24, wherein, in a case where the one or more processors determine not to transmit at least one of the uplink communication or the sidelink communication, the one or more processors are further configured to: perform at least one of determining an error event or reporting an error event based on the determination of not transmitting.

Images