Uplink allocation in a wireless communication system

Abstract

A method of wireless communication, the method comprising: identifying a resource block assignment for a non-data uplink resource within a set of resource blocks; determining a first resource block range that is lower than the resource block assignment for the non-data uplink resource and identifying a second resource block range that is higher than the resource block assignment for the non-data uplink resource; calculating a first bandwidth associated with the first resource block range and calculating a second bandwidth associated with the second resource block range; and configuring a first wireless communication device to operate within a discrete bandwidth level that is sufficient to encompass a larger one of the first bandwidth and the second bandwidth, wherein the discrete bandwidth level is less than a full uplink bandwidth assigned by a network serving the first wireless communication device.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims priority to and the benefit of U.S. Patent Application No. 17 / 082,885 filed October 28, 2020, the disclosure of which is hereby incorporated by reference herein in its entirety as if fully set forth below and for all applicable purposes. TECHNICAL FIELD

[0003] The present application relates to wireless communication systems, and in particular, to uplink allocation in a wireless communication network.

[0004] INTRODUCTION

[0005] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems can be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). A wireless multiple-access communication system can include a number of base stations (BSs), each simultaneously supporting communications for multiple communication devices, which can be otherwise known as user equipment (UE).

[0006] To meet the growing demands for expanded mobile broadband connectivity, wireless communication technologies are advancing from the long-term evolution (LTE) technology to a next generation new radio (NR) technology, which can be referred to as 5th Generation (5G). For example, NR is designed to provide lower latency, higher bandwidth or throughput, and higher reliability than LTE. NR is designed to operate over a wide range of spectrum bands, for example, from low-frequency bands below about 1 gigahertz (GHz) and mid-frequency bands from about 1 GHz to about 6 GHz, to high-frequency bands such as mmWave frequency bands. NR is also designed to operate across different spectrum types from licensed spectrum to unlicensed and shared spectrum. Spectrum sharing enables operators to opportunistically aggregate spectrum to dynamically support high-bandwidth services. Spectrum sharing can extend the benefits of NR technologies to operating entities that can not have access to licensed spectrum.

[0007] Furthermore, both users of UEs and designers of UEs are concerned with energy usage because it affects battery life. Generally speaking, the more bandwidth assigned to a UE, the more power used by the UE, the more battery consumed by the UE. There is a current need in the art for improved techniques for conserving energy usage at UEs.

[0008] BRIEF OVERVIEW OF SOME EXAMPLES

[0009] The following presents a simplified summary of some aspects of the disclosure in order to provide a basic understanding of the discussed technology. This summary is not an extensive overview of all contemplated aspects of the disclosure, and is intended to neither identify key or critical elements of all aspects of the disclosure nor delineate the scope of any or all aspects of the disclosure. Its sole purpose is to present some concepts of one or more aspects of the disclosure in a simplified form as a prelude to the more detailed description that is presented later.

[0010] For example, in an aspect of the disclosure, a method of wireless communication includes identifying a resource block assignment for a non-data uplink resource within a set of resource blocks; determining a first range of resource blocks that is lower than the resource block assignment for the non-data uplink resource and identifying a second range of resource blocks that is higher than the resource block assignment for the non-data uplink resource; calculating a first bandwidth associated with the first range of resource blocks and calculating a second bandwidth associated with the second range of resource blocks; and configuring a first wireless communication device to operate within a discrete bandwidth level sufficient to encompass a larger one of the first bandwidth and the second bandwidth, where the discrete bandwidth level is less than a full uplink bandwidth assigned by a network serving the first wireless communication device.

[0011] In an additional aspect of the disclosure, an apparatus includes a transceiver configured to communicate with a network on an uplink channel and a processor configured to identify a resource block assignment for a non-data uplink resource within a set of resource blocks, determine a first range of resource blocks that is lower than the resource block assignment for the non-data uplink resource and identify a second range of resource blocks that is higher than the resource block assignment for the non-data uplink resource, and configure the transceiver to operate within a discrete bandwidth level sufficient to encompass a larger one of the first range of resource blocks and the second range of resource blocks, where the discrete bandwidth level is less than a full uplink bandwidth assigned by the network.

[0012] In an additional aspect of the disclosure, a non-transitory computer- readable medium having program code recorded thereon, the program code comprising code for receiving an information element from a base station, the information element defining a resource block assignment for a non-data uplink resource, code for determining a first range of resource blocks that is lower than the resource block assignment and determining a second range of resource blocks that is higher than the resource block assignment, and code for tuning hardware within a user equipment to operate within a bandwidth level corresponding to a larger one of the first range or the second range and less than a full uplink bandwidth assignment assigned by the base station.

[0013] In an additional aspect of the disclosure, a user equipment includes means for determining that the user equipment does not support non-contiguous physical UL shared channel (PUSCH) allocation and means for tuning hardware of the user equipment to operate within a discrete bandwidth level less than a full uplink bandwidth assignment in response to the determination.

[0014] Other aspects, features, and embodiments of the present disclosure will become apparent to those of ordinary skill in the art, upon reviewing the description of specific example embodiments of the present disclosure in conjunction with the accompanying figures. While features of the present disclosure can be discussed relative to certain embodiments and figures below, all embodiments of the present disclosure can include one or more of the advantageous features discussed herein. In other words, while one or more BRIEF DESCRIPTION OF DRAWINGS

[0016] Figure 1 A wireless communication network is illustrated in accordance with some aspects of the present disclosure.

[0017] Figure 2 A block diagram of a user equipment (UE) is illustrated in accordance with some aspects of the present disclosure.

[0018] Figure 3 A radio frame structure is illustrated in accordance with some aspects of the present disclosure.

[0019] Figure 4 Numerous different discrete bandwidth levels for a UE are illustrated in accordance with some aspects of the present disclosure.

[0020] Figure 5 Characteristics of uplink as defined by the network are illustrated in accordance with some aspects of the present disclosure.

[0021] Figure 6 A block diagram of a user equipment (UE) in accordance with some aspects of the present disclosure.

[0022] Figure 7 A block diagram of an exemplary base station (BS) in accordance with some aspects of the present disclosure.

[0023] Figure 8 A flow diagram of a communication method in accordance with some aspects of the present disclosure.

[0024] DETAILED DESCRIPTION

[0025] The detailed description set forth below, in connection with the appended drawings and embodiments described theriin, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0026] This disclosure relates generally to wireless communication systems (also referred to as wireless communication networks). In various implementations, techniques and apparatus can be used for wireless communication networks such as Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, Single-Carrier FDMA (SC-FDMA) networks, LTE networks, Global System for Mobile Communications (GSM) networks, fifth generation (5G) or new radio (NR) networks, among other communication networks. As described herein, the terms“network” and“system” can be used interchangeably.

[0027] An OFDMA network can implement a radio technology such as evolved UTRA (E- UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA, and GSM are part of universal mobile telecommunication system (UMTS). In particular, long term evolution (LTE) is a release of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents from an organization named“3rd Generation Partnership Project” (3GPP) and cdma2000 is described in documents from an organization named“3rd Generation Partnership Project 2” (3GPP2). These various radio technologies and standards are known or are being developed. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between groups of telecommunications associations that aims to define a global standard for the third generation (3G) mobile phone

[0028] In particular, 5G networks contemplate diverse deployments, diverse spectrum, and diverse services and devices that can be implemented using a unified, OFDM- based air interface. In order to reach these goals, further enhancements to LTE and LTE- Advanced are considered in addition to development of the new radio technology for 5G NR networks. 5G NR will be capable of scaling to deliver extreme mobile broadband (eMBB) for high-speed wireless devices, massive machine type communications (mMTC) for IoT devices with deep coverage, and ultra-reliable low-latency communications (URLLC) for mission-critical auxiliaries. 2 2 5G NR can be implemented to: use optimized OFDM-based waveforms with scalable numerology and transmission time interval (TTI); have a common, flexible framework to efficiently multiplex services and features using dynamic, low-latency time

[0029] 5G NR can be implemented to: use optimized OFDM-based waveforms with scalable numerology and transmission time interval (TTI); have a common, flexible framework to efficiently multiplex services and features using dynamic, low-latency time

[0030] ​The scalable numerology design of 5G NR facilitates scalable TTIs to meet diverse latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmissions to start on symbol boundaries. 5G NR also contemplates a self-contained integrated subframe design with uplink / downlink scheduling information, data, and acknowledgement in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive uplink / downlink that can be flexibly configured on a per-cell basis to dynamically switch between UL and downlink to meet current traffic needs.

[0031] Various other aspects and features of the disclosure are further described below. It should be apparent that the teachings herein can be embodied in a wide variety of forms and that any specific structure, function, or both being disclosed herein is merely representative and not limiting. Based on the teachings herein one of an ordinary skill in the art should appreciate that an aspect disclosed herein can be implemented independently of any other aspects and that two or more aspects can be combined in various ways. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects set forth herein. In addition, such an apparatus can be implemented or such a method can be practiced using other structure, functionality, or structure and functionality consistent with those set forth herein. Like numbers refer to like elements throughout. Additionally, a skilled artisan will understand that the order of steps or order for accessing or retrieving the described hardware, software, or firmware can differ from that described herein, without changing the underlying function of the methods described herein.

[0032] Some NR techniques include techniques for a network to allocate bandwidth for uplink (UL) communications by a user equipment (UE). For example, in some instances, a full uplink bandwidth can be 100 MHz. This bandwidth can be shared with some non-data uplink resources, such as random access channels (RACH), physical UL control channels (PUCCH), sounding reference signals (SRS), and the like. In this example, the non-data uplink resources include signals and channels for control data, rather than user data.

[0033] In contrast, an example of an uplink resource that carries user data is a physical UL shared channel (PUSCH). In some instances, a PUSCH can be assigned to non-contiguous resource blocks. Thus, if some resource blocks are used for non-data uplink resources, a PUSCH can still be assigned to resource blocks above and below the resource blocks assigned to non-data uplink resources. In such instances, the PUSCH can use all or almost all of the full uplink bandwidth assigned by the network.

[0034] In other examples, a UE can not support non-contiguous PUSCH allocations. In other words, in such instances, the network can only allocate contiguous resource blocks to the PUSCH. In instances where non-data resources are assigned to resource blocks near the lower or upper boundary of the resource block range, contiguous PUSCH allocations can still use all or almost all of the full uplink bandwidth assigned by the network.

[0035] However, some networks can assign one or more non-data uplink resources to resource blocks near the center of the carrier bandwidth (i.e., near the middle of the resource block range). A set of non-contiguous resource blocks above and below the resource blocks for the non-data uplink resources can then be assigned to UEs that support non-contiguous PUSCH allocations. In contrast, UEs that do not support non-contiguous PUSCH allocations can have their uplink bandwidth reduced by about half due to the PUSCH allocation, which can only use resource blocks above or below the non-data uplink resources for any given frame.

[0036] Various embodiments herein address the situation where a UE does not support non-contiguous PUSCH allocations. For example, if a UE is forced to use less than the full uplink bandwidth due to the placement of non-data resources, various embodiments can detect this configuration and perform techniques to reduce power usage.

[0037] For example, some embodiments can include a UE detecting that it does not support non-contiguous PUSCH allocations (e.g., does not support PUSCH allocation Type 0). The UE can then identify a resource block assignment for a non-data uplink resource, such as a RACH. To facilitate illustration, there can be 100 resource blocks 0-99, and the RACH can be assigned to resource block 50. The UE can then determine a first resource block range below the resource block assignment (e.g., 0-49) and a second resource block range above the resource block assignment for the non-data uplink resource (e.g., 51-99). The UE can then calculate a first bandwidth associated with the first resource block range and a second bandwidth associated with the second resource block range. In one example, each resource block corresponds to the same amount of bandwidth, such that the range with the most resource blocks also corresponds to a larger bandwidth. In this example, the first range has 50 resource blocks, which is greater than the second range of 49 resource blocks; thus, the first range corresponds to a larger bandwidth than the second range.

[0038] Continuing this example, the UE can then configure itself to operate within discrete bandwidth levels covering the maximum bandwidth across two resource block ranges. For ease of explanation, if there are five discrete bandwidth levels (including a level at 25 MHz and a level at 30 MHz), and if the bandwidth corresponding to the first range is 27 MHz, then the UE configures itself to operate at a discrete bandwidth level of 30 MHz. The discrete bandwidth level can be less than the full uplink bandwidth assigned by the network. For example, if the full uplink bandwidth is 60 MHz, and the UE configures itself to operate with a bandwidth not exceeding 30 MHz, it can save itself the power and performance differences associated with tuning to operate with the full 60 MHz bandwidth. Of course, these figures are merely examples, and the scope of the embodiments is not limited to any number of resource blocks, bandwidths, or center frequencies.

[0039] Several benefits can be provided by various aspects of this disclosure. For example, a general rule for wireless transmitters is that current (and therefore power) is proportional to carrier bandwidth. Therefore, various embodiments that are tuned to operate at a level not exceeding discrete bandwidth (which is less than the full uplink bandwidth) can save power. Similarly, a general rule is that noise increases with increasing bandwidth. Therefore, various embodiments that are tuned to operate at a bandwidth less than the full uplink bandwidth can reduce noise, as measured exponentially by factors such as signal-to-noise ratio (SNR), error vector magnitude (EVM), etc. In other words, various embodiments can reduce power consumption, thereby increasing the battery life of the wireless device and improving performance by reducing noise. In contrast, when compared to the various embodiments described herein, a UE that is tuned to use the full uplink bandwidth, even if it is only allocated a portion of that bandwidth, can use more power and experience more noise for the same amount of available bandwidth.

[0040] Figure 1 A wireless communication network 100 according to some aspects of this disclosure is described. Network 100 may be a 5G network. Network 100 includes several base stations (BSs) 105 (labeled 105a, 105b, 105c, 105d, 105e, and 105f, respectively) and other network entities. BS 105 may be a station communicating with UE 115, and may also be referred to as an evolved B-node (eNB), a next-generation eNB (gNB), an access point, etc. Each BS 105 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to that specific geographic coverage area of ​​BS 105 and / or the BS subsystem serving that coverage area, depending on the context in which the term is used. Figure 4 , 5 The actions of 8 can be performed by either of UE 115.

[0041] A BS 105 can provide communication coverage for a macro cell or a small cell, such as a pico cell or a femto cell, and / or other types of cell. A macro cell generally covers a relatively large geographic area (e.g., 5-10 miles in radius) and can allow unrestricted access by UEs with service subscriptions with the network provider. A small cell such as a pico cell can also cover a relatively small geographic area and can allow restricted access by UEs such as UEs in the same home as a subscriber or UEs for which the same network provider has a subscription. A BS for a macro cell can be referred to as a macro BS. A BS for a small cell can be referred to as a small cell BS, a pico BS, a femto BS, or a home BS. In Figure 1 In the example shown in FIG. 1, BSs 105d, 105d, and 105e can be regular macro BSs, while BSs 105a and 105c can be macro BSs that enable one of three-dimensional (3D), full dimensional (FD), or massive MIMO. BSs 105a and 105c can utilize their higher dimension MIMO capabilities to increase coverage and capacity using 3D beamforming in both altitude and azimuth. BS 105f can be a small cell BS, which can be a home node or an AP. BSs 105 can support one or more (e.g., two, three, four, etc.) cells.

[0042] The network 100 can support synchronous or asynchronous operation. For synchronous operation, the BSs can have similar frame timing, and transmissions from different BSs can be approximately aligned in time. For asynchronous operation, the BSs can have different frame timing, and transmissions from different BSs can not be aligned in time.

[0043] The UEs 115 are dispersed throughout the wireless network 100, and each UE 115 can be stationary or mobile. A UE 115 can also be referred to as a terminal, a mobile station, a subscriber unit, a station, or the like. A UE 115 can be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, or the like. In one aspect, a UE 115 can be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, a UE can be a device that does not include a UICC. In some aspects, UEs 115 that do not include a UICC can also be referred to as IoT devices or Internet of Everything (IoE) devices. UEs 115a-115d are examples of mobile smart phone-type devices accessing network 100 A UE 115 can also be a machine specifically configured to perform communication, including machine type communication (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT) and the like. UEs 115e-115h are examples of various machines configured to access the network 100 configured to perform communication. UEs 115i- 115k are examples of vehicles equipped with wireless communication devices configured to access network 100 configured to perform communication. A UE 115 can be able to communicate with any type of the BSs, whether macro BS, small cell, or the like. In Figure 1 In general, a lightning bolt (e.g., a communication link) indicates a wireless transmission between a UE 115 and a serving BS 105, desired transmissions between BSs 105, backhaul transmissions between BSs, or sidelink transmissions between UEs 115, the serving BS 105 being a BS designated to serve the UE 115 on the downlink (DL) and / or uplink (UL).

[0044] In operation, BSs 105a and 105c can serve UEs 115a and 115b using 3D beamforming and coordinated spatial techniques, such as coordinated multipoint (CoMP) or multi-connectivity. Macro BS 105d can perform backhaul communications with BSs 105a and 105c, and small cell BS 105f, as well as query communications with apparatus 150. Macro BS 105d can also transmit multicast services which are subscribed to and received by UEs 115c and 115d. Such multicast services can include mobile television or stream video, or can include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts.

[0045] The BSs 105 can also communicate with a core network. The core network can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some of the BSs 105 (e.g., which can be an example of gNBs or access node controllers (ANCs)) can interface with the core network

[0046] The network 100 can also support mission critical communications with ultra-reliable and redundant links for mission critical devices, such as the UE 115e, which can be an example of an unmanned aerial vehicle (UAV). Redundant communication links with the UE 115e can include links from the macro BSs 105d and 105e, as well as the small cell BS 105f. Other machine type devices, such as the UE 115f (e.g., a thermometer), the UE 115g (e.g., a smart meter), and UE 115h (e.g., a wearable device) can communicate through the network 100 either directly with BSs, such as the small cell BS 105f, and the macro BS 105e, or in multi-step

[0047] In some implementations, the network 100 utilizes OFDM-based waveforms for communications. An OFDM-based system can partition the system BW into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, tones, frequency channels, and so on. Each subcarrier can be modulated with data. In some instances, the subcarrier spacing can be fixed, and the total number of subcarriers (K) can be dependent on the system BW. The system BW can also be partitioned into subbands. In other instances, the subcarrier spacing and / or the duration of TTIs can be scalable.

[0048] In some aspects, the BSs 105 can assign or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RBs)) for downlink (DL) and uplink (UL) transmissions in the network 100. DL refers to the transmission direction from a BS 105 to a UE 115, whereas UL refers to the transmission direction from a UE 115 to a BS 105. The communication can be in the form of radio frames. A radio frame can be divided into multiple subframes or slots, for example, about 10. Each slot can be further divided into sub-slots. In FDD mode, simultaneous UL and DL transmissions can occur in different frequency bands. In FDD mode, simultaneous UL and DL transmissions can occur in different frequency bands. In TDD mode, UL and DL transmissions occur at different time periods using the same frequency band. For example, a subset of the subframes (e.g., DL subframes) in a radio frame can be used for DL transmissions, and another subset of the subframes (e.g., UL subframes) in the radio frame can be used for UL transmissions.

[0049] The DL subframes and the UL subframes can be further divided into several regions. For example, each DL or UL subframe can have pre-defined regions for transmission of reference signals, control information, and data. A reference signal is a predetermined signal that facilitates communication between a BS 105 and a UE 115. For example, a reference signal can have a particular pilot pattern or structure, where pilot tones can span across an operational BW or frequency band, each positioned at a pre-defined time and a pre-defined frequency. For example, a BS 105 can transmit a cell-specific reference signal (CRS) and / or a channel state information - reference signal (CSI-RS) to enable a UE 115 to estimate a DL channel. Similarly, a UE 115 can transmit a sounding reference signal (SRS) to enable a BS 105 to estimate a UL channel. Control information can comprise resource assignments and protocol

[0050] In some aspects, the network 100 can be an NR network deployed over a licensed spectrum. The BSs 105 can transmit synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in the network 100 to facilitate synchronization. The BSs 105 can broadcast system information associated with the network 100 (e.g., including a master information block (MIB), remaining system information (RMSI), and other system information (OSI)) to facilitate initial network access. In some instances, the BSs 105 can broadcast PSS, SSS, and / or MIB in the form of synchronization signal blocks (SSBs) over a physical broadcast channel (PBCH) and can broadcast RMSI and / or OSI over a physical downlink shared channel (PDSCH).

[0051] In some aspects, a UE 115 attempting to access the network 100 can perform an initial cell search by detecting a PSS from a BS 105. The PSS can enable synchronization of time period timing and can indicate a physical layer identity value. The UE 115 can then receive an SSS. The SSS can enable synchronization of radio frame timing and can provide a cell identity value, which can be combined with the physical layer identity value to identify the cell. The PSS and the SSS can be located in a central portion of a carrier or anywhere in the carrier.

[0052] After receiving the PSS and SSS, the UE 115 can receive a MIB. The MIB can include system information for initial network access and scheduling information for RMSI and / or OSI. After decoding the MIB, the UE 115 can receive RMSI and / or OSI. The RMSI and / or OSI can include radio resource control (RRC) information related to RACH procedures, paging, control resource set (CORESET) for physical downlink control channel (PDCCH) monitoring, PUCCH, PUSCH, power control, and SRS.

[0053] After obtaining the MIB, RMSI, and / or OSI, the UE 115 can perform a random access procedure to establish a connection with the BS 105. In some examples, the random access procedure can be a four-step random access procedure. For example, the UE 115 can transmit a random access preamble and the BS 105 can respond with a random access response. The random access response (RAR) can include a detected random access preamble identifier (ID) corresponding to the random access preamble, timing advance (TA) information, a UL grant, a temporary cell radio network temporary identifier (C-RNTI), and / or a backoff indicator. Upon receiving the random access response, the UE 115 can transmit a connection request to the BS 105 and the BS 105 can respond with a connection response. The connection response can indicate a contention resolution. In some examples, the random access preamble, the RAR, the connection request, and the connection response can be referred to as message 1 (MSG 1), message 2 (MSG 2), message 3 (MSG 3), and message 4 (MSG 4), respectively. In some examples, the random access procedure can be a two-step random access procedure, where the UE 115 can transmit a random access preamble and a connection request in a single transmission, and the BS 105 can respond by transmitting a random access response and a connection response in a single transmission.

[0054] After establishing a connection, the UE 115 and the BS 105 can enter a normal operations phase where operational data can be exchanged. For example, the BS 105 can schedule the UE 115 for UL and / or DL communications. The BS 105 can transmit UL and / or DL scheduling grants to the UE 115 via a PDCCH. The scheduling grants can be transmitted in the form of DL control information (DCI). The BS 105 can transmit DL communication signals (e.g., carrying data) to the UE 115 via a PDSCH according to a DL scheduling grant. The UE 115 can transmit UL communication signals to the BS 105 via a PUSCH and / or PUCCH according to a UL scheduling grant.

[0055] In some aspects, the BSs 105 can communicate with the UEs 115 using hybrid automatic repeat request (HARQ) techniques to improve communication reliability, for example, to provide ultra-reliable low-latency communication (URLLC) services. The BSs 105 can schedule the UEs 115 for PDSCH communication by transmitting a DL grant in a PDCCH. The BSs 105 can transmit a DL data packet to a UE 115 in accordance with the scheduling in the PDSCH. The DL data packet can be transmitted in the form of a transport block (TB). If the UE 115 successfully receives the DL data packet, the UE 115 can transmit a HARQ acknowledgment (ACK) to the BS 105. Conversely, if the UE 115 fails to successfully receive the DL transmission, the UE 115 can transmit a HARQ negative acknowledgment (NACK) to the BS 105. Upon receiving the HARQ NACK from the UE 115, the BS 105 retransmits the DL data packet to the UE 115. The retransmission can include the same encoded version of the DL data as the initial transmission. Alternatively, the retransmission can include a different encoded version of the DL data than the initial transmission. The UE 115 can apply soft combining to combine the encoded data received from the initial transmission and the retransmission for decoding. The BSs 105 and UEs 115 can also apply HARQ to UL communication using substantially similar mechanisms as for DL HARQ.

[0056] In some aspects, the network 100 can operate over a system BW or a component carrier (CC) BW. The network 100 can partition the system BW into multiple BWPs (e.g., multiple portions). The BSs 105 can dynamically assign the UEs 115 to operate over a certain BWP (e.g., a certain portion of the system BW). The assigned BWP can be referred to as the active BWP. The UE 115 can monitor the active BWP for signaling information from the BSs 105. The BSs 105 can schedule the UE 115 for UL or DL communication in the active BWP. In some aspects, the BSs 105 can assign a pair of BWPs within a CC to the UE 115 for UL and DL communication. For example, the pair of BWPs can include one BWP for UL communication and one BWP for DL communication.

[0057] In some aspects, the network 100 can operate over a shared channel, which can include a shared frequency band or an unlicensed frequency band. For example, the network 100 can be an NR-U (NR-U) network. The BSs 105 and UEs 115 can be operated by multiple network operating entities. To avoid collisions, the BSs 105 and UEs 115 can employ a listen-before-talk (LBT) procedure to monitor a transmission opportunity (TXOP) in the shared channel. For example, a transmitting node (e.g., a BS 105 or a UE 115) can perform an LBT before transmitting in the channel. When the LBT passes, the transmitting node can in turn transmit. When the LBT fails, the transmitting node can refrain from transmitting in the channel. In an example, the LBT can be based on energy detection. For example, when a signal energy measured from the channel is below a threshold, the LBT result is pass. Conversely, when the signal energy measured from the channel exceeds the threshold, the LBT result is fail. In another example, the LBT can be based on signal detection. For example, when no channel reservation signal (e.g., a predetermined preamble signal) is detected in the channel, the LBT result is pass.

[0058] In some aspects, the network 100 can operate over a higher frequency band (e.g., in a frequency range 1 (FR1) band or a frequency range 2 (FR2) band). FR1 can refer to frequencies in a sub-6 GHz range, while FR2 can refer to frequencies in a mmWave range. To overcome high path loss at the higher frequencies, the BSs 105 and UEs 115 can communicate with one another using directional beams. For example, the BSs 105 can transmit SSBs by sweeping across a pre-defined set of beam directions, and can repeat the SSB transmissions at a certain time interval on the set of beam directions to allow UEs 115 to perform initial network access. In the example of BS 105b (shown as NTN resources), it can transmit SSBs on each of its beams at a scheduled time, even if the beams are not steered. In some instances, each beam and its corresponding characteristics can be identified by a beam index. For example, each SSB can include an indication of a beam index corresponding to the beam used for the SSB transmission. The UEs 115 can determine signal measurements (such as reference signal received power (RSRP) and / or reference signal received quality (RSRQ)) for the SSBs in different beam directions and select a best DL beam. The UEs 115 can indicate the selection by transmitting a PRACH signal (e.g., MSG1) using a PRACH resource associated with the selected beam direction. For example, an SSB transmitted in a particular beam direction or on a particular beam can indicate a PRACH resource that the UE 115 can use to communicate with the BS 105 in that particular beam direction. After selecting the best DL beam, the UE 115 can complete a random access procedure (e.g., a 4-step random access or a 2-step random access) and proceed with network registration and normal operational data exchange with the BS 105.

[0059] In some aspects, the network 100 can be an IoT network, and the UEs 115 can be IoT nodes, such as smart printers, monitors, gaming nodes, cameras, audio-video (AV) production equipment, industrial IoT devices, etc. The transmission payload data size of IoT nodes can generally be relatively small (e.g., on the order of tens of bytes). In some aspects, the network 100 can be a massive IoT network serving tens of thousands of nodes (e.g., UEs 115) over a higher frequency band, such as an FR1 band or an FR2 band.

[0060] Figure 2 is Figure 1 a block diagram of an example design of a UE 115. According to some aspects, the UE 115 can perform the actions of Figure 4 , 5 and 8, including configuring itself to operate within discrete bandwidth levels that encompass less than a full uplink bandwidth. Moreover, such functionality can be stored as computer-executable code at the memory 282 and executed by the data processor / controller 280. As the data processor / controller 280 executes the code, it can implement the logic described with respect to Figure 8 and respond accordingly by tuning the transmitter hardware. Such transmitter hardware is illustrated by all or parts of the antenna interface circuit 224, power amplifier 254, and transmit circuit 252.

[0061] In this example design, the wireless device 110 includes a transceiver 220 coupled to a primary antenna 210, a transceiver 222 coupled to a secondary antenna 212, and a data processor / controller 280. The transceiver 220 includes multiple (K) receivers 230pa-230pk and multiple (K) transmitters 250pa-250pk to support multiple frequency bands, multiple radio technologies, carrier aggregation, etc. The transceiver 222 includes L receivers 230sa-230sl and L transmitters 250sa-250sl to support multiple frequency bands, multiple radio technologies, carrier aggregation, receive diversity, multiple-input multiple-output (MIMO) transmission from multiple transmit antennas to multiple receive antennas, etc.

[0062] In Figure 2In the exemplary design shown, each receiver 230 includes a low noise amplifier (LNA) 240 and receive circuitry 242. For data reception, the antennas 210 receive signals from the BS and / or other transmitter stations and provide received radio frequency (RF) signals, which can be routed through the antenna interface circuitry 224 and presented as input RF signals to the selected receiver. The antenna interface circuitry 224 can include switches, duplexers, transmit filters, receive filters, matching circuits, etc. The following description assumes that receiver 230pa is the selected receiver. Within receiver 230pa, LNA 240pa amplifies the input RF signal and provides an output RF signal. Receive circuitry 242pa down-converts the output RF signal from RF to baseband, amplifies the down-converted signal and filters the down-converted signal, and provides an analog input signal to the data processor 280. The receive circuitry 242pa can include mixers, filters, amplifiers, matching circuits, oscillators, local oscillators (LO) generators, phase-locked loops (PLLs), etc. Each remaining receiver 230 in transceivers 220 and 222 can operate in a similar manner as receiver 230pa.

[0063] In Figure 2 In the exemplary design shown, each transmitter 250 includes transmit circuitry 252 and a power amplifier (PA) 254. For data transmission, the data processor 280 processes (e.g., encodes and modulates) data to be transmitted and provides an analog output signal to the selected transmitter. The following description assumes that transmitter 250pa is the selected transmitter. Within transmitter 250pa, the transmitter circuitry 252pa amplifies, filters, and up-converts the analog output signal from baseband to RF and provides a modulated RF signal. The transmit circuitry 252pa can include amplifiers, filters, mixers, matching circuits, oscillators, LO generators, phase-locked loops (PLLs), etc. The PA 254pa receives and amplifies the modulated RF signal and provides a transmit RF signal having the appropriate output power level. The transmit RF signal can be routed through the antenna interface circuitry 224 and transmitted via the antennas 210. Each remaining transmitter 250 in transceivers 220 and 222 can operate in a similar manner as transmitter 250pa.

[0064] Continuing the example, when the data processor / controller 280 issues a command signal to configure the UE 115 to operate at a discrete bandwidth level, it can power up or not power up various ones of the power amplifiers 254, and it can configure the filters, mixers, matching circuits, oscillators, LO generators, and PLLs to operate at a particular center frequency or range of frequencies to support that bandwidth level.

[0065] Figure 2 Exemplary designs of receivers 230 and transmitters 250 are shown. The receivers and transmitters can also include Figure 2other circuitry not shown, such as filters, matching circuitry, and so on. All or a portion of transceivers 220 and 222 can be implemented on one or more analog ICs, RF ICs (RFICs), mixed-signal ICs, and so on. For example, LNA 240 and receive circuitry 242 within transceivers 220 and 222 can be implemented on separate IC chips, as described below. Circuitry among transceivers 220 and 222 can also be implemented in other ways.

[0066] Data processor / controller 280 can perform various functions for wireless device 110. For example, data processor 280 can perform processing for data received via receiver 230 and data transmitted via transmitter 250. Controller 280 can control operation of various circuitry within transceivers 220 and 222. Memory 282 can store program codes and data for data processor / controller 280. Data processor / controller 280 can be implemented on one or more application specific integrated circuits (ASICs) and / or other ICs.

[0067] Figure 3 is a timing diagram illustrating a radio frame structure 300 in accordance with some aspects of the present disclosure. Radio frame structure 300 can be employed by BSs (such as BS 105) and UEs (such as UE 115) in a network, such as network 100, for communication. In particular, a BS can communicate with a UE using time-frequency resources configured as shown in radio frame structure 300. In Figure 3 In radio frame structure 300, the x-axis represents time in some arbitrary units, and the y-axis represents frequency in some arbitrary units. Radio frame structure 300 includes a radio frame 301. The duration of radio frame 301 can vary depending on aspects. In one example, radio frame 301 can have a duration of about 10 milliseconds. Radio frame 301 includes a number M of slots 302, where M can be any suitable positive integer. In one example, M can be about 10.

[0068] Each slot 302 includes a number of subcarriers 304 in frequency and a number of symbols 306 in time. The number of subcarriers 304 and / or the number of symbols 306 in a slot 302 can vary depending on aspects, such as based on a channel bandwidth, a subcarrier spacing (SCS), and / or a cyclic prefix (CP) mode. One subcarrier 304 in frequency and one symbol 306 in time form one resource element (RE) 312 for transmission. A resource block (RB) 310 is formed from a number of consecutive subcarriers 304 in frequency and a number of consecutive symbols 306 in time.

[0069] In one example, a BS (e.g., BS 105 in network 100) can schedule a UE (e.g., UE 115) in time with a time granularity of a slot 302 or a mini-slot 308. Figure 1 In one example, a BS (e.g., BS 105 in network 100) can schedule a UE (e.g., UE 115) in time with a time granularity of a slot 302 or a mini-slot 308.Figure 1 and 2 UL and / or DL communications with a UE 115 in a system 300. Each slot 302 can be time-divided into a number K of mini-slots 308. (The integer K can be the same or different from the integer K in Figure 2 ). Each mini-slot 308 can include one or more symbols 306. The mini-slots 308 in a slot 302 can have variable lengths. For example, when a slot 302 includes a number N of symbols 306, a mini-slot 308 can have a length between 1 and (N-1) symbols 306. In some aspects, a mini-slot 308 can have a length of about two symbols 306, about four symbols 306, or about seven symbols 306. In some examples, a BS can schedule a UE in frequency granularity of resource blocks (RBs) 310 (e.g., including about 12 subcarriers 304).

[0070] Figure 4 An example table illustrating transmission bandwidth configuration levels for an example UE is illustrated. Specifically, Figure 4 The table of Figure 3 may be the same or different from the number N in

[0071] The top row includes a number of entries, each corresponding to a discrete bandwidth level supported by the UE. For example, from 5 MHz to 100 MHz, there are a total of 12 discrete bandwidth levels. In some examples, the number of discrete bandwidth levels and their values are a function of the underlying hardware of the UE. In other words, Figure 4 The numbers shown in the table of

[0072] For an example UE, the discrete bandwidth levels supported are known at design time, but can also be discovered using testing or simulation. Examples of underlying hardware that affect the number of discrete bandwidth levels can include a number of PLLs that provide a sampling frequency for a transceiver of the UE. For example, a higher bandwidth can require a higher sampling frequency, which can be provided using a different PLL or multiple PLLs or other hardware to provide a higher sampling frequency than a lower sampling frequency. The same can be true for mixers, LOs, power amplifiers, upconverters, baseband and digital chains, etc. The above reference Figure 2Example hardware is described. In other words, in some examples, a higher discrete bandwidth level may require powering on additional hardware or using more current to drive existing hardware compared to a lower discrete bandwidth level. Therefore, tuning an example UE to support a 25MHz discrete bandwidth level may use more power than tuning a UE to support a 5MHz discrete bandwidth level. Similarly, tuning a UE to support a 100MHz bandwidth level may use more power than tuning a UE to support a 25MHz bandwidth level. Tuning the hardware in a UE to support a lower discrete bandwidth level may include powering some hardware while not powering others, reducing the clock frequency, reducing the operating voltage or operating current, etc.

[0073] Tuning hardware may include selecting operating modes for components such as power amplifiers. For example, a power amplifier operating in envelope tracking (ET) mode may be more efficient than operating in average power tracking (APT) mode. In one example, the power amplifier may support ET up to a first bandwidth level, but may use APT for bandwidth levels above the first bandwidth level and up to the full bandwidth level. Therefore, if discrete bandwidth levels support ET, the tuning hardware may include placing the power amplifier in ET mode to take advantage of the power savings and lower noise of ET relative to APT.

[0074] Figure 4 The leftmost column of the table shows the different subcarrier spacings, and the rows to the right of the leftmost column show the number of RBs that support the bandwidth level using that subcarrier.

[0075] Figure 5 This is a table of example uplink characteristics of an example BS according to one embodiment. For example, the network can assign these characteristics, and the UE communicating with the base station can adapt to these characteristics. Figure 5 For example, the total uplink bandwidth is 100MHz, RACH is assigned at resource block 114, while PUCCH is assigned at blocks 112 and 159. See... Figure 4 For example, 100MHz of uplink bandwidth corresponds to 273 resource blocks with a 30kHz subcarrier. Therefore, for ease of explanation in this example, it is assumed that the uplink uses a 30kHz subcarrier and that a subset of the 273 resource blocks will be used to assign PUSCH.

[0076] When the UE and the BS negotiate to set up communications, the UE can transmit a RRC UE capability message information element to the BS. In one example embodiment, the UE can parse its own RRC UE capability message information element to determine whether it supports non-contiguous PUSCH allocation by determining whether PUSCH allocation type 0 or type 1 is supported. Allocation type 1 does not support non-contiguous allocation, while allocation type 0 supports non-contiguous allocation. Continuing the example embodiment, the BS can also parse the RRC UE capability message information element to determine the capabilities of the UE. Further, when the UE and the BS negotiate, the BS can send a control message to the UE to inform the UE of the bandwidth, RACH assignment, and PUCCH assignment, as well as to allocate PUSCH to a subset of RBs.

[0077] Once the UE determines that it does not support non-contiguous PUSCH allocation, it can perform a power saving technique by tuning itself to support some but not all of the full uplink bandwidth of 100 MHz. In the present example, the resource blocks are numbered 0-272, and the RACH is assigned at RB 114, and the PUCCH is assigned at 112 and 159. Thus, the BS can allocate PUSCH to either the first range of resource blocks 0-111 or the second range of resource blocks 160-272 during a given frame.

[0078] Given this constraint, the UE can then calculate a first bandwidth associated with the first range, and a second bandwidth associated with the second range. For the first range of resource blocks 0-111, the bandwidth can be calculated by multiplying the number of subcarriers (e.g., 12) by the subcarrier spacing (e.g., 30 kHz) by the number of resource blocks in the range (112). Thus, for the first range of resource blocks, the bandwidth is 40.32 MHz. A similar calculation for the second range of resource blocks gives a bandwidth of 40.68 MHz. Taking the maximum of the two gives the larger bandwidth of 40.68 MHz.

[0079] Now looking at Figure 4 which has a discrete bandwidth level at 40 MHz and another discrete bandwidth level at 50 MHz. To support 40.68 MHz, the UE can configure its hardware at the 50 MHz discrete bandwidth level. This discrete bandwidth level is less than the full uplink bandwidth of 100 MHz assigned by the network, as shown in Figure 5 In other words, the UE can tune its hardware to use about half of the available uplink bandwidth, which generally is expected to result in power savings and improved performance, as discussed above.

[0080] Figure 6 is a block diagram of an example UE 600 in accordance with some aspects of the disclosure. The UE 600 can be the UE 100 above in Figure 1 and 2The UE 115 discussed in connection with FIG. 1, and Figure 6 representations of the above references Figure 2 described concepts in another manner. As shown, the UE 600 can include a processor 602, a memory 604, a beam module 608, a transceiver 610 (including a modem subsystem 612 and a radio frequency (RF) unit 614), and one or more antennas 616. These elements can be in direct or indirect communication with each other, for example via one or more buses. The transceiver 610 can communicate with the network 100 using the RF unit 614. The transceiver 610 can also include a modem subsystem 612 to modulate the signals and to demodulate received signals. The RF unit 614 can include a receiver and a transmitter that can be coupled to one or more antennas 616 and that can receive and send communication signals between the transceiver 610 and the network 100. The transceiver 610 can be implemented as one or more analog components, digital components, or a combination thereof.

[0081] The processor 602 can include a central processing unit (CPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 602 can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0082] The memory 604 can include a cache memory (e.g., of the processor 602), random access memory (RAM), a magnetic disk, an optical disk, a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a solid state memory device, a hard disk drive, another form of volatile or non-volatile memory, or a combination thereof. In one aspect, the memory 604 includes a non-transitory computer-readable medium. The memory 604 can store or have recorded thereon, instructions 606. The instructions 606 can include instructions that, when executed by the processor 602, enable the processor 602 to perform operations described herein in connection with aspects of the disclosure, for example, as described with reference to the UE 115 in connection with aspects of the disclosure (e.g., aspects of FIGS. 1-8). The instructions 606 can also be referred to as program code. Program code can be used to cause a wireless communication device to perform the operations described herein, for example, by causing one or more processors, such as the processor 602, to control or command the wireless communication device to do so. The terms “instructions” and “code” should be interpreted broadly to include any type of computer-readable statement(s). For example, the terms “instructions” and “code” can refer to one or more programs, routines, sub-routines, functions, procedures, etc. “Instructions” and “code” can include a single computer-readable statement or many computer-readable statements. Figure 4 、 5 The memory 604 can include a cache memory (e.g., of the processor 602), random access memory (RAM), a magnetic disk, an optical disk, a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a solid state memory device, a hard disk drive, another form of volatile or non-volatile memory, or a combination thereof. In one aspect, the memory 604 includes a non-transitory computer-readable medium. The memory 604 can store or have recorded thereon, instructions 606. The instructions 606 can include instructions that, when executed by the processor 602, enable the processor 602 to perform operations described herein in connection with aspects of the disclosure, for example, as described with reference to the UE 115 in connection with aspects of the disclosure (e.g., aspects of FIGS. 1-8). The instructions 606 can also be referred to as program code. Program code can be used to cause a wireless communication device to perform the operations described herein, for example, by causing one or more processors, such as the processor 602, to control or command the wireless communication device to do so. The terms “instructions” and “code” should be interpreted broadly to include any type of computer-readable statement(s). For example, the terms “instructions” and “code” can refer to one or more programs, routines, sub-routines, functions, procedures, etc. “Instructions” and “code” can include a single computer-readable statement or many computer-readable statements.

[0083] The beam module 608 can be implemented via hardware, software, or combinations thereof. For example, the beam module 608 can be implemented as a processor, circuit, and / or instructions 606 stored in the memory 604 and executed by the processor 602. In some instances, the beam module 608 can be integrated within the modem subsystem 612. For example, the beam module 608 can be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem 612. In some examples, the beam module 608 can be used for beamforming and beam recovery.

[0084] As shown, the transceiver 610 can include the modem subsystem 612 and the RF unit 614. The transceiver 610 can be configured to communicate bi-directionally with other devices, such as the BS 105. The modem subsystem 612 can be configured to modulate and / or encode data from the memory 604 and / or beam module 608 according to a modulation and coding scheme (MCS) (e.g., a low-density parity check (LDPC) coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.). The RF unit 614 can be configured to process (e.g., perform analog to digital conversion or digital to analog conversion, etc.) modulated / encoded data from the modem subsystem 612 (for outbound transmission) or transmissions originating from another source such as the UE 115 or the BS 105. The RF unit 614 can be further configured to perform analog beamforming via the beam module 608 in conjunction with digital beamforming. Although shown together in the transceiver 610, the modem subsystem 612 and the RF unit 614 can be separate devices that are coupled together at the UE 115 to enable the UE 115 to communicate with other devices.

[0085] The RF unit 614 can provide the modulated and / or processed data, e.g., data packets (or more generally, data messages that can contain one or more data packets and other information), to the antennas 616 for transmission to one or more other devices. The antennas 616 can further receive data messages transmitted from other devices. The antennas 616 can provide the received data messages for processing and / or demodulation at the transceiver 610. The transceiver 610 can provide demodulated and decoded data (e.g., SSBs, PDCCH, PDSCH, beam switch commands, CSI-RS resource configurations, CSI-RS report configurations, BFR resource configurations) to the beam module 608 for processing. The antennas 616 can include multiple antennas of similar or different designs in order to sustain multiple transmission links. The RF unit 614 can configure the antennas 616.

[0086] In an aspect, the UE 600 can include multiple transceivers 610 implementing different radio access technologies (RATs) (e.g., NR and LTE). In an aspect, the UE 600 can include a single transceiver 610 implementing multiple RATs (e.g., NR and LTE). In an aspect, the transceiver 610 can include various components, where different combinations of components can implement

[0087] Figure 7 is a block diagram of an example BS 700 according to some aspects of the present disclosure. The BS 700 can be a BS 105 in the network 100 as discussed above in connection with Fig. 1. As shown, the BS 700 can include a processor 702, a memory 704, a beam module 708, a transceiver 710 including a modem subsystem 712 and a RF unit 714, and one or more antennas 716. These elements can be in direct or indirect communication with each other, for example via one or more buses. The BS 700 can include additional elements not shown Figure 1

[0088] The processor 702 can have various features as a specific-type processor. For example, these can include a CPU, a DSP, an ASIC, a controller, a FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 702 can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0089] ​The memory 704 can include cache memory (e.g., of the processor 702), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid state memory devices, one or more hard disk drives, memristor-based arrays, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some aspects, the memory 704 can comprise a non-transitory computer-readable medium. The memory 704 can store instructions 706. The instructions 706 can include instructions that, when executed by the processor 702, enable the processor 702 to perform operations described herein (e.g., assigning resource blocks and scheduling PUSCH). The instructions 706 can also be referred to as code, which can be broad interpreted to include any type of computer-readable statements, as discussed above. The beam module 708 can be used for beamforming and beam recovery. Figure 6

[0090] As shown, the transceiver 710 can include the modem subsystem 712 and the RF unit 714. The transceiver 710 can be configured to communicate bi-directionally with other devices, such as the UEs 115 and / or 300 and / or another core network element. The modem subsystem 712 can be configured to modulate and / or encode data according to a MCS (e.g., a LDPC coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.). The RF unit 714 can be configured to process (e.g., perform analog to digital conversion or digital to analog conversion, etc.) modulated / encoded data (e.g., SSBs, RMSIs, MIBs, system information blocks - SIBs, frame based equipment - FBE configurations, PRACH configurations, PDCCHs, PDSCHs) from the modem subsystem 712 (on out-of-band transmissions) or the transmissions originating from another source such as a UE 115, a node 315, and / or a BS 700. The RF unit 714 can be further configured to perform analog beamforming on the transmissions via the beam module 708 in combination with digital beamforming. Although shown as integrated together in transceiver 710, the modem subsystem 712 and / or the RF unit 714 can be separate devices that are coupled together at the BS 105 to enable the BS 105 to communicate with other devices.

[0091] ​RF unit 714 may provide modulated and / or processed data (e.g., data packets (or more generally, data messages containing one or more data packets and other information)) to antenna 716 for transmission to one or more other devices. Antenna 716 may be similar to antennas 210, 212 discussed above. This may include, for example, information transmission for completing attachment to a network and communication with the resident UE 115 or 215 according to some aspects of this disclosure. Antenna 716 may further receive data messages transmitted from other devices and provide the received data messages for processing and / or demodulation at transceiver 710. Transceiver 710 may provide demodulated and decoded data (e.g., PUCCH control information, PRACH signals, PUSCH data) to beamforming module 708 for processing. Antenna 716 may include multiple antennas of similar or different designs to maintain multiple transmission links.

[0092] In one example, transceiver 710 is configured to transmit system information to the UE including FBE configuration indicating multiple frame periods, each frame period including a gap period for contention at the beginning of the frame period, and to communicate with the UE based on the FBE configuration, for example by coordinating with beam module 708.

[0093] In one aspect, the BS 700 may include multiple transceivers 710 implementing different RATs (e.g., NR and LTE). In another aspect, the BS 700 may include a single transceiver 710 implementing multiple RATs (e.g., NR and LTE). In yet another aspect, the transceiver 710 may include various components, wherein different combinations of the components can implement different RATs.

[0094] Figure 8 This is a flowchart of method 800 according to some aspects of this disclosure. Method 800 can be generated by network 100 (e.g., Figure 1 This can be implemented by any UE 115 (as shown). For example, UE 115 may utilize one or more components (such as processor 602 or 280, memory 604 or 282, transceiver 610, 220 or 222, and one or more antennas 616, 210 or 212) to perform the steps of method 800. As explained, method 800 includes several enumeration steps, but implementations of method 800 may include additional steps before, after, and between these enumeration steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0095] In action 810, the UE identifies resource block assignments within the resource block set for non-data uplink resources. Examples of non-data uplink resources include RACH, and the UE can identify resource block assignments from the RACH information element sent by the BS when communication is established.

[0096] However, the scope of the embodiments is not limited to any one type of non-data uplink resource. The UE can also use other information elements transmitted by the BS to identify resource block assignments for SRS, PUCCH, etc. For example, in the example of FIG. 11, the UE identifies resource block assignments for both RACH and PUCCH. Figure 5

[0097] At act 820, the UE determines a first range of resource blocks below the resource block assignment for the non-data uplink resource. In the example of FIG. 11, the first range of resource blocks is below resource block 112 assigned to RACH. In this example, the range of resource blocks below a particular resource block includes resource blocks having subcarriers lower than the subcarrier frequencies assigned to the non-data uplink resource. Figure 5

[0098] Act 820 can also include determining a second range of resource blocks above the resource block assignment. In this example, the range of resource blocks above a particular resource block includes resource blocks having subcarriers higher than the subcarrier frequencies assigned to the non-data uplink resource. In the example of FIG. 11, the second range of resource blocks is above resource block 159 assigned to PUCCH. In examples where the UE does not support non-contiguous PUSCH allocation, the first and second ranges of resource blocks can not both be used during a single frame, although each can be used in different frames as assigned by the network. As a result, the PUSCH can be limited in bandwidth to some portion of the full uplink bandwidth assigned by the network. Figure 5

[0099] At act 830, the UE can calculate a first bandwidth associated with the first range of resource blocks. An example is given above with reference to Figure 4 and 5 where the number of subcarriers is multiplied by the SCS and the number of resource blocks to provide the bandwidth.

[0100] Act 830 can also include calculating a second bandwidth associated with the second range of resource blocks, similar to calculating the first bandwidth, although possibly with a different number of resource blocks. For example, in the example of Figure 4 and Figure 5 one range of resource blocks includes 112 resource blocks, while the other range of resource blocks includes 113 resource blocks, so the bandwidth is slightly more.

[0101] In another implementation, the UE can simply select the range of resource blocks having the higher number of resource blocks and calculate its bandwidth. In other words, in some implementations, the UE can omit calculating the bandwidth associated with the smaller range of resource blocks.

[0102] ​​​At act 840, the UE configures itself to operate within a discrete bandwidth level that is sufficient to encompass the largest of the first bandwidth and the second bandwidth. In other words, the UE can configure itself to operate within a discrete bandwidth level that is sufficient to encompass the larger range of resource blocks. The above references Figure 4 Examples of discrete bandwidth levels are given. Act 840 can further include the UE transmitting user data on the PUSCH within the discrete bandwidth level.

[0103] As explained above with reference to Figure 4 The discrete bandwidth level can be a function of the underlying hardware of the UE, such that powering up different hardware components, setting operational modes, providing different clock frequencies, voltages, and currents can tune the UE for different discrete bandwidth levels. For example, in some examples, tuning the hardware to support a discrete bandwidth level can include powering up some power amplifiers while powering down others, setting operational modes of the power amplifiers, setting sampling frequencies of clocks at appropriate levels, and so on.

[0104] Act 840 can include tuning the UE to operate within an appropriate discrete bandwidth level that is less than the full uplink bandwidth assigned by the network. For example, in an example in which the full uplink bandwidth is 100 MHz and the UE tunes itself to operate within a discrete bandwidth level of 50 MHz, the UE can not be able to provide the full 100 MHz bandwidth without retuning its hardware. However, as a result of being tuned to less than the full uplink bandwidth, the UE can benefit from lower power usage, lower noise, and better performance characteristics such as can be measured by SNR and EVM. Act 840 can also include communicating with the network on a data channel, such as a PUSCH, within the discrete bandwidth level.

[0105] The scope of embodiments is not limited to the acts of method 800, as other embodiments can add, omit, modify, or rearrange various acts as appropriate. For example, method 800 can be repeated each time the UE establishes communication with the BS or reestablishes communication with the BS.

[0106] Further, some embodiments can perform method 800 for each of a plurality of ports supporting uplink in a multiple-input multiple-output (MIMO) device. For example, Figure 2 A UE 115 of FIG. 1 is shown with multiple inputs in multiple outputs, and method 800 can be performed for each of those outputs that support uplink communication. Further, method 800 can be repeated for each carrier in a carrier aggregation scheme.

[0107] In another example, the method 800 can further include an act of the UE determining whether it supports non-contiguous PUSCH allocation. Such an act can include the UE parsing its own settings or parsing a RRC capability information element that identifies whether either or both of PUSCH allocation Type 0 or Type 1 is supported. Indeed, some embodiments can conditionally perform any combination of acts 810-840 upon determining that PUSCH allocation Type 0 is not supported by the UE.

[0108] Further, some embodiments can perform any combination of acts 810-840 upon determining that a certain threshold has been met or exceeded. For example, upon detecting that the UE battery has fallen below a threshold or / and the UE uplink block error rate (BLER) has risen above a threshold, the UE can perform one or more of acts 810-840.

[0109] Information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that can be referenced throughout the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0110] The various illustrative blocks and modules described in connection with the disclosure herein can be implemented or performed with a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices (e.g., 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).

[0111] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations thereof. Features implementing functions can also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations. Also, as used herein, including in the claims, "or" as used in a list of items prefaced by "comprising" or "including" indicates an inclusive list such that, for example, a list of [A, B, or C] means A or B or C or any combination thereof.

[0112] As will be appreciated by persons skilled in the art, many modifications, changes, substitutions, and alterations to the implementations of the apparatus of the disclosure can be made without departing from the spirit and scope of the disclosure. Therefore, the scope of the disclosure is not intended to be limited to the particular implementations described herein, but rather, are to be accorded the widest scope consistent with this disclosure as wired in the appended claims and their functional equivalents.​

Claims

1. A method of wireless communication, the method comprising: identifying a resource block assignment within a set of resource blocks for a non-data uplink resource; determining a first resource block range and determining a second resource block range, wherein the first resource block range comprises a first plurality of resource blocks having subcarriers with a frequency lower than subcarriers associated with the non-data uplink resource, and wherein the second resource block range comprises a second plurality of resource blocks having subcarriers with a frequency higher than subcarriers associated with the non-data uplink resource; calculating a first bandwidth associated with the first resource block range and calculating a second bandwidth associated with the second resource block range; and configuring a first wireless communication device to operate within a discrete bandwidth level sufficient to encompass a larger of the first bandwidth and the second bandwidth, wherein the discrete bandwidth level is less than a full uplink bandwidth assigned by a network serving the first wireless communication device.

2. The method of claim 1, wherein determining the first resource block range is performed in response to determining that a physical UL shared channel (PUSCH) allocation type 0 is not supported by the first wireless communication device.

3. The method of claim 1, wherein determining the first resource block range is performed in response to determining that a non-contiguous physical UL shared channel (PUSCH) allocation is not supported by the first wireless communication device.

4. The method of claim 1, further comprising: determining that a non-contiguous physical UL shared channel (PUSCH) allocation is not supported by the first wireless communication device by parsing a radio resource control (RRC) capability information element.

5. The method of claim 1, wherein the non-data uplink resource comprises an item selected from a list consisting of: a random access channel (RACH), a sounding reference signal (SRS), and a physical UL control channel (PUCCH).

6. The method of claim 1, wherein the non-data uplink resource does not carry user data.

7. The method of claim 1, wherein the non-data uplink resource carries control data.

8. The method of claim 1, wherein the non-data uplink resource comprises an item selected from a list consisting of: a signal and a channel.

9. The method of claim 1, wherein the first wireless communication device comprises a user equipment (UE). communicating user data with the network on a physical UL shared channel (PUSCH) within the discrete bandwidth level.

10. The method of claim 1, further comprising: tuning hardware within the first wireless communication device to support the discrete bandwidth level.

11. The method of claim 1, wherein configuring the first wireless communication device comprises: powering a power amplifier within the first wireless communication device.

12. The method of claim 11, wherein tuning the hardware comprises: setting a sampling frequency of a clock within the first wireless communication device.

13. The method of claim 11, wherein tuning the hardware comprises: tuning transceiver hardware within the first wireless communication device to not support the full uplink bandwidth.

14. The method of claim 1, wherein configuring the first wireless communication device comprises:

15. The method of claim 1, wherein configuring the first wireless communication device is performed in response to determining that a battery level of the first wireless communication device has fallen below a threshold value. ​ 16. The method of claim 1, wherein configuring the first wireless communication device is performed in response to determining that an uplink block error rate (BLER) has risen above a threshold.

17. An apparatus comprising: a transceiver configured to: communicate with a network on an uplink channel; and a processor configured to: identify a resource block assignment for non-data uplink resources within a set of resource blocks; calculate a first bandwidth of a first range of resource blocks and calculate a second bandwidth of a second range of resource blocks, wherein the first range of resource blocks comprises a first plurality of resource blocks having subcarriers with a frequency lower than subcarriers associated with the non-data uplink resources, and wherein the second range of resource blocks comprises a second plurality of resource blocks having subcarriers with a frequency higher than subcarriers associated with the non-data uplink resources; and configure the transceiver to operate within a discrete bandwidth level sufficient to encompass a larger one of the first bandwidth and the second bandwidth, wherein the discrete bandwidth level is less than a full uplink bandwidth assigned by the network.

18. The apparatus of claim 17, wherein the apparatus comprises a user equipment (UE).

19. The apparatus of claim 17, wherein the transceiver comprises a clock, and wherein the processor is operable to configure the transceiver by setting a sampling frequency of the clock.

20. The apparatus of claim 17, wherein the uplink channel comprises a physical UL shared channel (PUSCH).

21. The apparatus of claim 20, wherein the processor is further configured to communicate with the network according to the discrete bandwidth level on the PUSCH.

22. The apparatus of claim 17, wherein the processor is further configured to: parse a radio resource control (RRC) capability information element to determine that non-contiguous physical UL shared channel (PUSCH) allocations are not supported by the apparatus.

23. The apparatus of claim 17, wherein the transceiver comprises a power amplifier, and wherein the processor is operable to configure the transceiver by setting the power amplifier to an envelope tracking mode.

24. An apparatus comprising a non-transitory computer-readable medium having program code recorded thereon, the program code, when executed by a processor of the apparatus, causes the apparatus to: receive an information element from a base station, the information element defining a resource block assignment for non-data uplink resources; calculate a first bandwidth of a first range of resource blocks and calculate a second bandwidth of a second range of resource blocks, wherein the first range of resource blocks comprises a first plurality of resource blocks having subcarriers with a frequency lower than subcarriers associated with the non-data uplink resources, and wherein the second range of resource blocks comprises a second plurality of resource blocks having subcarriers with a frequency higher than subcarriers associated with the non-data uplink resources; and ​ ​ tuning hardware within the user equipment to operate within a bandwidth level corresponding to a larger one of the first bandwidth and the second bandwidth and less than a full uplink bandwidth assignment assigned by the base station.

25. The apparatus of claim 24, wherein the program code, when executed by the processor, further causes the apparatus to: communicate from the user equipment to the base station on a physical UL shared channel (PUSCH) according to the bandwidth level.

26. The apparatus of claim 24, wherein the program code, when executed by the processor, further causes the apparatus to: determine that the user equipment does not support non-contiguous physical UL shared channel (PUSCH) allocation.

27. The apparatus of claim 24, wherein the program code, when executed by the processor, further causes the apparatus to: determine that the user equipment does not support physical UL shared channel (PUSCH) allocation type 0.

28. The apparatus of claim 24, wherein tuning the hardware comprises: providing power to a first subset of power amplifiers within the user equipment and powering down a second subset of power amplifiers within the user equipment.

29. The apparatus of claim 24, wherein tuning the hardware comprises: setting a sampling frequency of a clock within the user equipment.

30. The apparatus of claim 24, wherein the non-data uplink resources comprise an item selected from the list consisting of: a random access channel (RACH), a sounding reference signal (SRS), and a physical UL control channel (PUCCH).

31. A user equipment comprising: means for determining that the user equipment does not support non-contiguous physical UL shared channel (PUSCH) allocation; means for calculating a bandwidth of a first range of resource blocks and calculating a bandwidth of a second range of resource blocks, wherein a discrete bandwidth level is sufficient to encompass a bandwidth associated with a larger one of the first range of resource blocks and the second range of resource blocks, wherein the first range of resource blocks comprises a first plurality of resource blocks having subcarriers with a lower frequency than subcarriers associated with non-data uplink resources, and wherein the second range of resource blocks comprises a second plurality of resource blocks having subcarriers with a higher frequency than subcarriers associated with the non-data uplink resources; and means for tuning hardware of the user equipment to operate within the discrete bandwidth level less than a full uplink bandwidth assignment in response to determining that the user equipment does not support non-contiguous PUSCH allocation.

32. The user equipment of claim 31, further comprising: means for communicating with a base station on the PUSCH according to the discrete bandwidth level.

33. The user equipment of claim 31, wherein the hardware comprises an item selected from the list consisting of: a plurality of power amplifiers, a mixer, a local oscillator, and a phase-locked loop.

34. The user equipment of claim 31, wherein the means for determining that the user equipment does not support non-contiguous PUSCH allocation comprises: means for parsing a radio resource control (RRC) capability information element.

Images