Uplink data communication in a narrow bandwidth data communication bandwidth part

Abstract

A user equipment (UE) may be configured to utilize a narrow bandwidth data communication bandwidth part for data communications. Here, a conventional interleaved virtual resource block (RB) to physical RB mapping technique is insufficient. For example, conventional interleaved virtual RB to physical RB mapping is based in part on a size of an active bandwidth part, and RBs are interleaved over the entire active bandwidth part. However, for a narrow bandwidth data communication bandwidth part, communication is not supported outside of a particular narrow bandwidth part. The conventional interleaved virtual RB to physical RB mapping could cause some virtual RBs to be mapped to physical RBs that are least partially outside of the narrow bandwidth data communication bandwidth part and, therefore, the conventional interleaved virtual RB to physical RB mapping should not be utilized for interleaved virtual RB to physical RB mapping on a narrow bandwidth data communication bandwidth part.

Description

UPLINK DATA COMMUNICATION IN A NARROW BANDWIDTH DATACOMMUNICATION BANDWIDTH PARTCROSS-REFERENCE TO RELATED APPLICATION

[0001] This Patent Application claims priority to India Patent Application No. 202241056230, filed on September 30, 2022, entitled “INTERLEAVED VIRTUAL RESOURCE BLOCK (RB) TO PHYSICAL RB MAPPING FOR A NARROW BANDWIDTH DATA COMMUNICATION BANDWIDTH PART,” and assigned to the assignee hereof. The disclosure of the prior Application is considered part of and is incorporated by reference into this Patent Application.FIELD OF THE DISCLOSURE

[0002] Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for uplink data communication in a narrow bandwidth data communication bandwidth part.BACKGROUND

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, or the like). Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3 GPP).

[0004] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as a user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. “Downlink” (or “DL”) refers to a communication link from the network node to the UE, and “uplink” (or “UL”) refers to a communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via a locallink (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among other examples).

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

[0006] In a scenario in which a user equipment (UE) (e.g., an enhanced reduced capability UE (eRedCap UE)) is to utilize a narrow bandwidth data communication bandwidth part for data communications, a conventional interleaved virtual resource block (RB) to physical RB mapping technique is insufficient. For example, conventional interleaved virtual RB to physical RB mapping is based in part on a size of an active bandwidth part (e.g., a 20 MHz bandwidth part), which is larger than that of the narrow bandwidth data communication bandwidth part, and RBs are interleaved over the entire active bandwidth part. However, in the case of a narrow bandwidth data communication bandwidth part, communication is not supported outside of a particular narrow bandwidth part (e.g., a particular 5MHz bandwidth part). The conventional interleaved virtual RB to physical RB mapping could cause some virtual RBs to be mapped to physical RBs that are least partially outside of the narrow bandwidth data communication bandwidth part and, therefore, the conventional interleaved virtual RB to physical RB mapping should not be utilized for interleaved virtual RB to physical RB mapping on a narrow bandwidth data communication bandwidth part.

[0007] Some aspects described herein relate to a method of wireless communication performed by an apparatus of a UE. The method may include receiving downlink control information (DCI) indicating a frequency domain resource allocation (FDRA) within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part. The methodmay include performing interleaved virtual RB to physical RB mapping based at least in part on information associated with the narrow bandwidth data communication bandwidth part and the FDRA within the narrow bandwidth data communication bandwidth part.

[0008] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part. The one or more processors may be configured to perform interleaved virtual RB to physical RB mapping based at least in part on information associated with the narrow bandwidth data communication bandwidth part and the FDRA within the narrow bandwidth data communication bandwidth part.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part. The set of instructions, when executed by one or more processors of the UE, may cause the UE to perform interleaved virtual RB to physical RB mapping based at least in part on information associated with the narrow bandwidth data communication bandwidth part and the FDRA within the narrow bandwidth data communication bandwidth part.

[0010] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part. The apparatus may include means for performing interleaved virtual RB to physical RB mapping based at least in part on information associated with the narrow bandwidth data communication bandwidth part and the FDRA within the narrow bandwidth data communication bandwidth part.

[0011] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part. The one or more processors may be configured to transmit one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth part.

[0012] Some aspects described herein relate to a method of wireless communication performed by an apparatus of a UE. The method may include receiving DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part. The method may include transmitting one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth part.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth part.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part. The apparatus may include means for transmitting one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth part.

[0015] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, network entity, network node, and / or processing system as substantially described with reference to and as illustrated by the drawings and specification.

[0016] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Fig. 1 is a diagram illustrating an example of a wireless network.

[0018] Fig. 2 is a diagram illustrating an example of a network node in communication with a user equipment (UE) in a wireless network.

[0019] Fig. 3 is a diagram illustrating an example disaggregated base station architecture.

[0020] Fig. 4 is a diagram illustrating an example associated with interleaved virtual resource block (RB) to physical RB mapping.

[0021] Figs. 5A and 5B are diagrams illustrating examples associated with uplink data communication in a narrow bandwidth data communication bandwidth part.

[0022] Fig. 6A is a flowchart of an example method of wireless communication.

[0023] Fig. 6B is a flowchart of an example method of wireless communication.

[0024] Fig. 7 is a diagram of an example apparatus for wireless communication.

[0025] Fig. 8 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.DETAILED DESCRIPTION

[0026] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purposes of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may 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.

[0027] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, or the like (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0028] By way of example, an element, or any portion of an element, or any combination of elements may be implemented with a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processorsin the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or the like, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0029] Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), compact disk ROM (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, combinations of the aforementioned types of computer- readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0030] While aspects may be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and / or a RAT subsequent to 5G (e.g., 6G).

[0031] Fig. 1 is a diagram illustrating an example of a wireless network 100. The wireless network 100 may be or may include elements of a 5G (for example, NR) network or a 4G (for example, Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more network nodes 110 (shown as a network node 110a, a network node 110b, a network node 110c, and a network node 1 lOd), a user equipment (UE) 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e), or other entities. A network node 110 is an example of a network node that communicates with UEs 120. As shown, a network node 110 may include one or more network nodes. For example, a network node 110 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (for example, within a single device or unit). As another example, a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0032] In some examples, a network node 110 is or includes a network node that communicates with UEs 120 via a radio access link, such as an RU. In some examples, anetwork node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or a core network via a backhaul link, such as a CU. In some examples, a network node 110 (such as an aggregated network node 110 or a disaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. A network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (for example, in 4G), a gNB (for example, in 5G), an access point, or a transmission reception point (TRP), a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, the network nodes 110 may be interconnected to one another or to one or more other network nodes 110 in the wireless network 100 through various types of fronthaul, midhaul, and / or backhaul interfaces, such as a direct physical connection, an air interface, or a virtual network, using any suitable transport network.

[0033] In some examples, a network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term “cell” can refer to a coverage area of a network node 110 or a network node subsystem serving this coverage area, depending on the context in which the term is used. A network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscription. A femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by UEs 120 having association with the femto cell (for example, UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In the example shown in Fig.1, the network node 110a may be a macro network node for a macro cell 102a, the network node 110b may be a pico network node for a pico cell 102b, and the network node 110c may be a femto network node for a femto cell 102c. A network node may support one or multiple (for example, three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a network node 110 that is mobile (for example, a mobile network node).

[0034] In some aspects, the term “base station” or “network node” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, “basestation” or “network node” may refer to a CU, a DU, an RU, a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, or a combination thereof. In some aspects, the term “base station” or “network node” may refer to one device configured to perform one or more functions, such as those described herein in connection with the network node 110. In some aspects, the term “base station” or “network node” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a quantity of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function, and the term “base station” or “network node” may refer to any one or more of those different devices. In some aspects, the term “base station” or “network node” may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term “base station” or “network node” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.

[0035] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive a transmission of data from an upstream node (for example, a network node 110 or a UE 120) and send a transmission of the data to a downstream node (for example, a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. In the example shown in Fig. 1, the network node 1 lOd (for example, a relay network node) may communicate with the network node 110a (for example, a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, or a relay, among other examples.

[0036] The wireless network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different impacts on interference in the wireless network 100. For example, macro network nodes may have a high transmit power level (for example, 5 to 40 watts) whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (for example, 0. 1 to 2 watts).

[0037] A network controller 130 may couple to or communicate with a set of network nodes 110 and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link. In someaspects, the network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

[0038] The UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. A UE 120 may include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit. A UE 120 may be a cellular phone (for example, a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (for example, a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (for example, a smart ring or a smart bracelet)), an entertainment device (for example, a music device, a video device, or a satellite radio), a vehicular component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, or any other suitable device that is configured to communicate via a wireless or wired medium.

[0039] Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. An MTC UE or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, or a location tag, that may communicate with a network node, another device (for example, a remote device), or some other entity. Some UEs 120 may be considered Intemet-of-Things (loT) devices, or may be implemented as NB-IoT (narrowband loT) devices. Some UEs 120 may be considered a Customer Premises Equipment. A UE 120 may be included inside a housing that houses components of the UE 120, such as processor components or memory components. In some examples, the processor components and the memory components may be coupled together. For example, the processor components (for example, one or more processors) and the memory components (for example, a memory) may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled.

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

[0041] In some examples, two or more UEs 120 (for example, shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (for example, without using a network node 110 as an intermediary to communicate with one another). For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (for example, which mayinclude a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), or a mesh network. In such examples, a UE 120 may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by the network node 110.

[0042] Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, or channels. For example, devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

[0043] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7. 125 GHz - 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics or FR2 characteristics, and thus may effectively extend features of FR1 or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0044] With these examples in mind, unless specifically stated otherwise, the term “sub-6 GHz,” if used herein, may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave,” if used herein, may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (for example, FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) may be modified, and techniques described herein are applicable to those modified frequency ranges.

[0045] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive downlink control information (DCI) indicating a frequency domain resource allocation (FDRA) within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part;and perform interleaved virtual resource block (RB) to physical RB mapping based at least in part on information associated with the narrow bandwidth data communication bandwidth part and the FDRA within the narrow bandwidth data communication bandwidth part. Further, as described in more detail elsewhere herein, the communication manager 140 may receive DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part; and transmit one or more uplink data communication based at least in part on the FDRA within the narrow bandwidth data communication bandwidth part. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0046] As indicated above, Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.

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

[0048] At the network node 110, a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120). The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 using one or more channel quality indicators (CQIs) received from that UE 120. The network node 110 may process (for example, encode and modulate) the data for the UE 120 using the MCS(s) selected for the UE 120 and may provide data symbols for the UE 120. The transmit processor 220 may process system information (for example, for semi-static resource partitioning information (SRPI)) and control information (for example, CQI requests, grants, or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (for example, a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (for example, a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple -input multiple-output (MIMO) processor 230 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, or the reference symbols, if applicable, and may provide a set of output symbol streams (for example,T output symbol streams) to a corresponding set of modems 232 (for example, T modems), shown as modems 232a through 232t. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232. Each modem 232 may use a respective modulator component to process a respective output symbol stream (for example, for OFDM) to obtain an output sample stream. Each modem 232 may further use a respective modulator component to process (for example, convert to analog, amplify, fdter, or upconvert) the output sample stream to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (for example, T downlink signals) via a corresponding set of antennas 234 (for example, T antennas), shown as antennas 234a through 234t.

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

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

[0051] One or more antennas (for example, antennas 234a through 234t or antennas 252a through 252r) may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, or an antenna array may include one or more antenna elements (within a single housing or multiple housings),a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled to one or more transmission or reception components, such as one or more components of Fig. 2.

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

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

[0054] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or any other component(s) of Fig. 2 may perform one or more techniques associated with interleaved virtual RB to physical RB mapping for a narrow bandwidth data communication bandwidth part, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or any other component(s) of Fig. 2 may perform or direct operations of, for example, process 600 of Fig. 6A, process 650 of Fig. 6B, and / or other processes as described herein. The memory242 and the memory 282 may store data and program codes for the network node 110 and the UE 120, respectively. In some examples, the memory 242 and / or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and / or interpreting) by one or more processors of the network node 110 and / or the UE 120, may cause the one or more processors, the UE 120, and / or the network node 110 to perform or direct operations of, for example, process 600 of Fig. 6A, process 650 of Fig. 6B, and / or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and / or interpreting the instructions, among other examples.

[0055] In some aspects, the UE 120 includes means for receiving DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part; and / or means for performing interleaved virtual RB to physical RB mapping based at least in part on information associated with the narrow bandwidth data communication bandwidth part and the FDRA within the narrow bandwidth data communication bandwidth part. In some aspects, the UE 120 includes means for receiving DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part; and / or means for transmitting one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth part. The means for the UE 120 to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0056] While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0057] As indicated above, Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.

[0058] Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station, or a network equipment may be implementedin an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP, or a cell, among other examples), or one or more units (or one or more components) performing base station functionality, may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station. “Network entity” or “network node” may refer to a disaggregated base station, or to one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

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

[0060] Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of communication systems by separating base station functionality into one or more units that can be individually deployed. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0061] Fig. 3 is a diagram illustrating an example disaggregated base station architecture 300. The disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units (such as a Near-RT RIC 325 via an E2 link, or a Non-RT RIC 315 associated with a Service Management and Orchestration (SMO) Framework 305, or both). A CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as through Fl interfaces. Each of the DUs 330 maycommunicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be simultaneously served by multiple RUs 340.

[0062] Each of the units, including the CUs 310, the DUs 330, the RUs 340, as well as theNear-RT RICs 325, the Non-RT RICs 315, and the SMO Framework 305, may include one or more interfaces or be coupled with one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to one or multiple communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of the units can include a wired interface, configured to receive or transmit signals over a wired transmission medium to one or more of the other units, and a wireless interface, which may include a receiver, a transmitter or transceiver (such as a RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0063] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among other examples. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (for example, Central Unit - User Plane (CU-UP) functionality), control plane functionality (for example, Central Unit - Control Plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit can communicate bidirectionally with a CU-CP unit via an interface, such as the El interface when implemented in an O-RAN configuration. The CU 310 can be implemented to communicate with a DU 330, as necessary, for network control and signaling.

[0064] Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples. In some aspects, the DU 330 may further host one or more low PHY layers, such as implemented by one or more modules for a fast Fourier transform (FFT), an inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (whichalso may be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.

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

[0066] The SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (such as an 01 interface). For virtualized network elements, the SMO Framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, non-RT RICs 315, and Near-RT RICs 325. In some implementations, the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an 01 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with each of one or more RUs 340 via a respective 01 interface. The SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.

[0067] The Non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near-RT RIC 325. The Non-RT RIC 315 may be coupled to or communicate with (such as via an Al interface) the Near-RT RIC 325. The Near-RT RIC 325 may be configured to include a logical function that enables near-realtime control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.

[0068] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 325, the Non-RT RIC 315 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 325 and may be received at the SMO Framework 305 or the Non-RT RIC 315 from non-network data sources or from network functions. In some examples, the Non-RT RIC 315 or the Near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 305 (such as reconfiguration via an 01 interface) or via creation of RAN management policies (such as Al interface policies).

[0069] As indicated above, Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.

[0070] In some wireless communication systems, a network node may allocate a UE one or more virtual RBs when receiving a physical downlink shared channel (PDSCH) resource allocation or a physical uplink shared channel (PUSCH) resource allocations on a physical downlink control channel (PDCCH). The UE may be configured to map the set of virtual RBs onto a set of physical RBs.

[0071] In the uplink direction, a non-interleaved mapping is used between the allocated virtual RBs and the actual physical RBs on the PUSCH. This means, for example, that virtual RB n maps onto physical RB n (i.e., virtual RBs are the same as physical RBs).

[0072] In the downlink direction, a non-interleaved mapping is applied if resource allocation type 0 is used to signal the allocation of the virtual RBs on the PDCCH. If resource allocation type 1 is used to signal the allocation of the virtual RBs on the PDCCH, then the mapping from the virtual RBs to actual physical RBs can be either non-interleaved or interleaved. Here, the interleaved mapping should be configured by the RRC layer prior to being used. Once interleaved mapping has been configured, a virtual RB to physical RB mapping field in DCI (e.g., DCI format 1 0 or DCI format 1 1) can be used to indicate whether interleaved mapping should be applied.

[0073] Downlink resource allocation type 1 can be signaled on the PDCCH using DCI (e.g., DCI format 1 0 or DCI format 1 1). In general, resource allocation type 1 uses a resource indication value (RIV) to indicate a set of allocated virtual RBs within an active bandwidth part (BWP) of the UE. As noted above, the UE maps the set of virtual RBs to actual physical RBs using either a non-interleaved mapping or an interleaved mapping.

[0074] The set of allocated VRBs allocated to be UE is continuous. When using noninterleaved mapping, a virtual RB is the same as a physical RB, and so the allocated physical RBs are also contiguous. Such allocation can be referred to as localized resource allocation. When using interleaved mapping, allocated physical RBs are deduced from allocated virtualRBs using an interleaving function. In this case, the allocated physical RBs are less likely to be contiguous. Such allocation can be referred to as distributed resource allocation. The RIV indicates a starting virtual RB RBstart and a quantity of consecutive allocated virtual RBs LRBS. A value of the RIV is determined based on the starting virtual RB RBstart, the quantity of consecutive allocated virtual RBs LRBS, and a size of the active bandwidth part NB^eP.

[0075] Interleaved virtual RB to physical RB mapping uses the concept of an RB bundle. An RB bundle is a set of contiguous RBs within the bandwidth part. A network node can use a vrb- To-PRB-Interleaver information element in the PDSCH-Config to configure the RB bundle size as either 2 RBs or 4 RBs. If the UE is instructed to use the interleaved mapping without having received the vrb-To-PRB-Interleaver information element, then the UE assumes a bundle size of 2 RBs. RB bundles at lower and upper ends of the bandwidth part may contain fewer RBs than configured, depending on a position of the bandwidth part within a set of common RBs. A smaller bundle is generated when the end of the bandwidth part does not coincide with an integer multiple of the bundle size from the perspective of common RB numbering.

[0076] Fig. 4 is a diagram illustrating an example 400 associated with interleaved virtual RB to physical RB mapping. In general, an active bandwidth part BWP includes NBWP RBS and starts at a starting position Ng^pt. Here, total RBs are divided into NBundte=[(IV p p + (Ngwp mod L)) / L RB bundles, where L is an RB bundle size configured via RRC signaling. As shown in Fig. 4, virtual RB bundles at the lower and upper ends of the bandwidth part are mapped on the physical RB bundles at the lower and upper edges of the bandwidth part. As further shown, if the size of the bandwidth part NB Pis 24 RBs and the RB bundle size L is 4 RBs, then there may be 6 bundles (depending on boundaries of the bandwidth part relative to the set of common RBs). In this example, virtual RB bundle 0 (VRBB0) is mapped onto physical RB bundle 0 (PRBB0), and virtual RB bundle 5 (VRBB5) is mapped onto physical RB bundle 5 (PRBB5). The remaining virtual RB bundles are mapped on physical RB bundles using an interleaving function defined as:Virtual RB bundle j is mapped to physical RB bundle r x C + c where; = 2 xc+ r; r = 0, I, ... , R - I; c = 0, I, ... , C - I; R = 2; and C = NBundle!R. Taking Fig. 4 as an example of a bandwidth having 6 bundles (C = 3), virtual RB bundle 1 (VRBB1) is mapped onto physical RB bundle 3 (PRBB3), virtual RB bundle 2 (VRBB2) is mapped onto physical RB bundle 1 (PRBB1), virtual RB bundle 3 (VRBB3) is mapped onto physical RB bundle 4 (PRBB4), and virtual RB bundle 4 (VRBB4) is mapped onto physical RB bundle 2 (PRBB2) according to the above function.

[0077] Additionally, in some wireless communication systems, a network node may serve different UEs of different categories and / or different UEs that support different capabilities. For example, the network node may serve a first category of UEs that have a less advanced capability (e.g., a lower capability and / or a reduced capability) and a second category of UEs that have a more advanced capability (e.g., a higher capability). A UE of the first category may have a reduced feature set compared to UEs of the second category, and may be referred to as a reduced capability (RedCap) UE, a low tier UE, and / or an NR-Lite UE, among other examples. A UE of the first category may be, for example, an MTC UE, an eMTC UE, and / or an loT UE, as described above in connection with Fig. 1. A UE of the second category may have an advanced feature set compared to UEs of the second category, and may be referred to as a baseline UE, a high tier UE, an NR UE, and / or a premium UE, among other examples.

[0078] Further, in some systems, the network node may serve a third category of UEs that have a less advanced capability than the first category of UEs. A UE of the third category may have a reduced feature set compared to UEs of the first category, and may be referred to as an enhanced reduced capability (eRedCap) UE, a lower tier UE, and / or an NR-Superlite UE, among other examples. A UE of the third category may be, for example, an MTC UE, an eMTC UE, and / or an loT UE, as described above in connection with Fig. 1.

[0079] In some wireless communication systems, a UE of the first category or the third category has capabilities that satisfy requirements of a first (earlier) wireless communication standard but not a second (later) wireless communication standard, while a UE of the second category has capabilities that satisfy requirements of the second (later) wireless communication standard (and also the first wireless communication standard, in some cases).

[0080] For example, UEs of the first category may support a lower maximum MCS than UEs of the second category (e.g., quadrature phase shift keying (QPSK) or the like as compared to 256-quadrature amplitude modulation (QAM) or the like), may support a lower maximum transmit power than UEs of the second category, may have a less advanced beamforming capability than UEs of the second category (e.g., may not be capable of forming as many beams as UEs of the second category), may require a longer processing time than UEs of the second category, may include less hardware than UEs of the second category (e.g., fewer antennas, fewer transmit antennas, and / or fewer receive antennas), and / or may not be capable of communicating on as wide of a maximum bandwidth part as UEs of the second category, among other examples. As another example, UEs of the third category may support a lower MCS than UEs of the first category, may support a lower maximum transmit power than UEs of the first category, may have a less advanced beamforming capability than UEs of the first category, may require a longer processing time than UEs of the first category, may include less hardware than UEs of the first category, and / or may not be capable of communicating (or permitted to communicate) on as wide of a maximum bandwidth part as UEs of the first category, among other examples.

[0081] In some systems, a bandwidth part on which some UEs, such as a UE in the third category of UEs (e.g., an eRedCap UE), is permitted to transmit and receive data communications (e.g., unicast PDSCH communications, broadcast PDSCH communication, PUSCH communications, or the like) may have a smaller size than that of an active bandwidth part of the UE. For example, the UE may be permitted to transmit and receive data communications in a data communication bandwidth part that has a bandwidth of only 5 MHz, while an active bandwidth part has a bandwidth of 20 MHz. Such a bandwidth part is herein referred to as a narrow bandwidth data communication bandwidth part. Notably, the UE may be permitted to use a bandwidth part having a bandwidth up to that of the active bandwidth part for transmitting and receiving other physical channels and signals.

[0082] In a scenario in which a UE (e.g., an eRedCap UE) is to utilize a narrow bandwidth data communication bandwidth part for data communications, the conventional interleaved virtual RB to physical RB mapping technique described above is insufficient. For example, conventional interleaved virtual RB to physical RB mapping is based in part on a size of the active bandwidth part, and RBs are interleaved over the entire active bandwidth part. However, in the case of a narrow bandwidth data communication bandwidth part, communication is not supported outside of a particular narrow bandwidth part (e.g., a particular 5 MHz bandwidth part). The conventional interleaved virtual RB to physical RB mapping could cause some virtual RBs to be mapped to physical RBs that are least partially outside of the narrow bandwidth data communication bandwidth part and, therefore, the conventional interleaved virtual RB to physical RB mapping cannot be applied.

[0083] Some techniques and apparatuses described herein enable interleaved virtual RB to physical RB mapping for a narrow bandwidth data communication bandwidth part. In some aspects, a UE may receive DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part (e.g., a bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part), and may perform interleaved virtual RB to physical RB mapping based at least in part on information associated with the narrow bandwidth data communication bandwidth part and the FDRA within the narrow bandwidth data communication bandwidth part. In this way, interleaved virtual RB to physical RB mapping can be performed for a UE (e.g., an eRedCap UE) that utilizes a narrow bandwidth data communication bandwidth part. Additional details are described below.

[0084] Some techniques and apparatuses described herein enable uplink data communication in a narrow bandwidth data communication bandwidth part. In some aspects, a UE may receive DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part (e.g., a bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part), and may transmit one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth part.

[0085] Figs. 5A and 5B are diagrams illustrating examples associated uplink data communication in a narrow bandwidth data communication bandwidth part. As shown in Fig. 5 A, example 500 includes communication between a network node 110 and a UE 120. In some aspects, the network node 110 and the UE 120 may be included in a wireless network, such as a wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0086] As shown in Fig. 5 A at 502, a network node 110 may transmit, and a UE 120 may receive DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part. In some aspects, the narrow bandwidth data communication bandwidth part has a bandwidth that is smaller than a bandwidth of an active bandwidth part. For example, the narrow bandwidth data communication bandwidth part may have a bandwidth of 5 MHz, while the active bandwidth part may have a bandwidth that is larger than 5 MHz (e.g., 20 MHz). Fig. 5B is an illustrative example of a narrow bandwidth data communication bandwidth part as comparable to the active bandwidth part and a system bandwidth.

[0087] In some aspects, the UE 120 may identify the narrow bandwidth data communication bandwidth part based at least in part on information that identifies a quantity of RBs for the narrow bandwidth data communication bandwidth part and information that indicates a starting RB of the narrow bandwidth data communication bandwidth part.

[0088] The quantity of RBs for the narrow bandwidth data communication bandwidth part indicates a maximum size (in RBs) of the narrow bandwidth data communication bandwidth part. In some aspects, the quantity of RBs for the narrow bandwidth data communication bandwidth part is configured on the UE 120 (e.g., by the network node 110) via RRC signaling. Alternatively, in some aspects, the quantity of RBs for the narrow bandwidth data communication bandwidth part is pre-determined by the UE 120 or pre-configured on the UE 120 (e.g., according to an applicable wireless communication standard). The quantity of RBs for the narrow bandwidth data communication bandwidth part is herein referred to as a quantity of RBs NmaxRB.

[0089] In some aspects, the information that indicates the starting RB of the narrow bandwidth data communication bandwidth part includes an indication of a starting RB of the narrow bandwidth data communication bandwidth part, with the indication being received in DCI. For example, in some aspects, the network node 110 may transmit, and the UE 120 may receive, DCI indicating a starting RB for the narrow bandwidth data communication bandwidth part. Here, the UE 120 may identify the narrow bandwidth data communication bandwidth part based at least in part on the starting RB for the narrow bandwidth data communication bandwidth part indicated in DCI and the quantity of RBs NmaxRB. In some aspects, the starting RB of the narrow bandwidth data communication bandwidth part may be indicated (e.g., via DCI) using an RB index included in a set of RB indices configured on the UE, where each RB index of the set of RB indices mapsto a respective starting RB for the narrow bandwidth data communication bandwidth part. In some aspects, the set of RB indices can be configured on the UE 120 (e.g., by the network node 110) via RRC signaling. In this way, a flexible RB index or pool of candidate RB indices can be used to indicate the narrow bandwidth data communication bandwidth part, thereby increasing flexibility of narrow bandwidth data communication bandwidth part assignment.

[0090] In some aspects, the information that indicates the starting RB of the narrow bandwidth data communication bandwidth part includes an indication of a starting RB for the FDRA within the narrow bandwidth data communication bandwidth part. For example, in some aspects, the UE 120 may identify the narrow bandwidth data communication bandwidth part based at least in part on the starting RB for the FDRA indicated in DCI and the quantity of RBs NmaxRB. In some such aspects, the actual quantity of RBs in the narrow bandwidth data communication bandwidth part (i.e., an actual size of the narrow bandwidth data communication bandwidth part) may be less than the quantity of RBs NmaxRB(e.g., to ensure that the narrow bandwidth data communication bandwidth part is confined to the active bandwidth part).

[0091] In some implementations, the information that identifies the starting RB for the narrow bandwidth data communication bandwidth part includes an indication of a starting RB of the narrow bandwidth data communication bandwidth part, with the indication being received via RRC signaling. For example, in some aspects, the network node 110 may transmit, and the UE 120 may receive, RRC signaling indicating a starting RB for the narrow bandwidth data communication bandwidth part. Here, the UE 120 may identify the narrow bandwidth data communication bandwidth part based at least in part on the starting RB for the narrow bandwidth data communication bandwidth part indicated via RRC signaling and the quantity of RBs NmaxRB. Thus, the narrow bandwidth data communication bandwidth part may in some aspects be (semi- statically) configured via RRC signaling.

[0092] In some aspects, the FDRA corresponds to a size of the narrow bandwidth data communication bandwidth part. For example, if the DCI (received at 502) includes an indication of the starting RB of the narrow bandwidth data communication bandwidth part, then a value carried in an FDRA field of the DCI may in some aspects be based at least in part on a size of the narrow bandwidth data communication bandwidth part (e.g., rather than being based on a size of the active bandwidth part).

[0093] Alternatively, in some aspects, the FDRA corresponds to a size of the active bandwidth part. For example, if the DCI (received at 502) includes an indication of the starting RB of the FDRA (rather than an indication of the starting RB of the narrow bandwidth data communication bandwidth part), then a value carried in an FDRA field of the DCI may in some aspects be based at least in part on the size of the active bandwidth part.

[0094] As further shown in Fig. 5A at 504, the UE 120 may perform interleaved virtual RB to physical RB mapping based at least in part on information associated with the narrow bandwidth data communication bandwidth part and the FDRA within the narrow bandwidth data communication bandwidth part.

[0095] In some aspects, the UE 120 performs the interleaved virtual RB to physical RB mapping based at least in part on the starting RB for the narrow bandwidth data communication bandwidth part indicated in DCI, the quantity of RBs NmaxRB, and an RB bundle size L. For example, in some aspects the UE 120 receives DCI that indicates the narrow bandwidth data communication bandwidth part (e.g., via a starting RB for the narrow bandwidth data communication bandwidth part, as described above) and an actual FDRA within the narrow bandwidth data communication bandwidth part. In such a scenario, interleaved virtual RB to physical RB mapping may be performed based at least in part on the starting RB for the narrow bandwidth data communication bandwidth part indicated in DCI (rather than the starting RB of the active bandwidth part NBwpt)- the quantity of RBs NmaxRB(rather than a size of the active bandwidth NBWP), and the RB bundle size L. In some aspects, the RB bundle size L may be configured on the UE 120 (e.g., by the network node 110) via RRC signaling.

[0096] Alternatively, in some aspects, the UE 120 performs interleaved virtual RB to physical RB mapping based at least in part on the starting RB for the FDRA within the narrow bandwidth data communication bandwidth part, the quantity of RBs NmaxRB, and the RB bundle size L. For example, in some aspects the UE 120 receives DCI that indicates the narrow bandwidth data communication bandwidth part (e.g., via a starting RB for the FDRA, as described above) and an actual FDRA within the narrow bandwidth data communication bandwidth part. In such a scenario, interleaved virtual RB to physical RB mapping may be performed based at least in part on the starting RB for the FDRA as indicated the DCI (rather than the starting RB of the active bandwidth part NBwBt). the quantity of RBs NmaxRB(rather than a size of the active bandwidth iV p p), and the RB bundle size L. In some such aspects, a value that is less than the quantity of RBs NmaxRBmay be used in association with performing interleaved virtual RB to physical RB mapping (e.g., when a value that is less than the quantity of RBs NmaxRBdefines the narrow bandwidth data communication bandwidth part to ensure that the narrow bandwidth data communication bandwidth part is confined to the active bandwidth part, as described above).

[0097] Alternatively, in some aspects, the UE 120 may perform interleaved virtual RB to physical RB mapping based at least in part on the starting RB for the narrow bandwidth data communication bandwidth part configured via RRC signaling, the quantity of RBs NmaxRB, and the RB bundle size L. For example, in some aspects the UE 120 receives RRC signaling that indicates the narrow bandwidth data communication bandwidth part and receives DCI that indicates the FDRA within the narrow bandwidth data communication bandwidth part. In such ascenario, interleaved virtual RB to physical RB mapping may be performed based at least in part on the starting RB for the narrow bandwidth data communication bandwidth part indicated via RRC signaling (rather than the starting RB of the active bandwidth part Nswpt). the quantity of RBs NmaxRB(rather than a size of the active bandwidth NB^eP), and the RB bundle size L.

[0098] As shown at 506, the UE 120 may transmit one or more uplink data communications or receive one or more downlink data communications based at least in part on the interleaved virtual RB to physical RB mapping. That is, the UE 120 may map one or more virtual RBs indicated by the FDRA to one or more physical RBs, and may transmit or receive data communications in the identified one or more physical RBs. Additionally, or alternatively, (e.g., in one alternative to performing interleaved virtual RB to physical RB mapping as described herein), the UE 120 may transmit one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth part. That is, the UE 120 may transmit one or more uplink data communications in resources corresponding to the FDRA indicated in the DCI received by the UE 120.

[0099] In one alternative to performing interleaved virtual RB to physical RB mapping as described herein, the UE 120 may be configured to such that interleaved virtual RB to physical RB mapping is not applied to a particular category of UEs (e.g., eRedCap UEs).

[0100] In other alternative, the UE 120 may be configured such that interleaved virtual RB to physical RB mapping is performed only if a size of the active bandwidth part is the same as that of the narrow bandwidth data communication bandwidth part.

[0101] In another alternative, for resource allocation type 0, a nominal RB group size may be fixed or configured only depending on higher layer parameter rbg-Size configured by PDSCH- Config / PUSCH-Config (e.g., 2 RBs or 4 RBs depending on rbg-Size) regardless of a configured bandwidth part size.

[0102] As indicated above, Fig. 5A and 5B is provided as an example. Other examples may differ from what is described with respect to Fig. 5A and 5B.

[0103] Fig. 6A is a flowchart of an example process 600 of wireless communication. The process 600 may be performed by, for example, a UE (e.g., UE 120).

[0104] At 610, the UE may receive DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part. For example, the UE (e.g., using communication manager 140 and / or reception component 702, depicted in Fig. 7) may receive DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part, as described above in connection with, for example, Fig. 5A at 502.

[0105] In some aspects, a bandwidth of the narrow bandwidth data communication bandwidth part is 5 megahertz (MHz).

[0106] In some aspects, the narrow bandwidth data communication bandwidth part is identified based at least in part on information that identifies a quantity of RBs for the narrow bandwidth data communication bandwidth part.

[0107] In some aspects, the quantity of RBs for the narrow bandwidth data communication bandwidth part is configured via RRC signaling.

[0108] In some aspects, the quantity of RBs for the narrow bandwidth data communication bandwidth part is pre-determined.

[0109] In some aspects, the FDRA corresponds to a size of the narrow bandwidth data communication bandwidth part.

[0110] In some aspects, process 600 includes receiving DCI indicating a starting RB for the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the starting RB for the narrow bandwidth data communication bandwidth part.[OHl] In some aspects, the starting RB is indicated using an RB index included in a set of RB indexes configured on the UE, each RB index of the set of RB indices mapping to a respective starting RB for the narrow bandwidth data communication bandwidth part.

[0112] In some aspects, the FDRA corresponds to a size of the active bandwidth part.

[0113] In some aspects, process 600 includes receiving DCI indicating a starting RB for the FDRA within the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the starting RB for the FDRA within the narrow bandwidth data communication bandwidth part.

[0114] In some aspects, process 600 includes receiving RRC signaling configuring a starting RB for the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the RRC signaling configuring the starting RB for narrow bandwidth data communication bandwidth part.

[0115] At 620, the UE may perform interleaved virtual RB to physical RB mapping based at least in part on information associated with the narrow bandwidth data communication bandwidth part and the FDRA within the narrow bandwidth data communication bandwidth part. For example, the UE (e.g., using communication manager 140 and / or mapping component 708, depicted in Fig. 7) may perform interleaved virtual RB to physical RB mapping based at least in part on information associated with the narrow bandwidth data communication bandwidth part and the FDRA within the narrow bandwidth data communication bandwidth part, as described above in connection with, for example, Fig. 5A and at 504.

[0116] In some aspects, the interleaved virtual RB to physical RB mapping is performed based at least in part on the starting RB for the narrow bandwidth data communication bandwidth part, a quantity of RBs for the narrow bandwidth data communication bandwidth part, and an RB bundle size.

[0117] In some aspects, the interleaved virtual RB to physical RB mapping is performed based at least in part on the starting RB for the FDRA within the narrow bandwidth data communication bandwidth part, a quantity of RBs for the narrow bandwidth data communication bandwidth part, and an RB bundle size.

[0118] In some aspects, the interleaved virtual RB to physical RB mapping is performed based at least in part on the starting RB for the narrow bandwidth data communication bandwidth part configured via RRC signaling, a quantity of RBs for the narrow bandwidth data communication bandwidth part, and an RB bundle size.

[0119] Although Fig. 6A shows example blocks of process 600, in some aspects, process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 6A. Additionally, or alternatively, two or more of the blocks of process 600 may be performed in parallel.

[0120] Fig. 6B is a flowchart of an example process 650 of wireless communication. The process 650 may be performed by, for example, a UE (e.g., UE 120).

[0121] At 660, the UE may receive DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part. For example, the UE (e.g., using communication manager 140 and / or reception component 702, depicted in Fig. 7) may receive DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part, as described above in connection with, for example, Fig. 5A at 502.

[0122] In some aspects, a bandwidth of the narrow bandwidth data communication bandwidth part is 5 megahertz (MHz).

[0123] In some aspects, the narrow bandwidth data communication bandwidth part is identified based at least in part on information that identifies a quantity of RBs for the narrow bandwidth data communication bandwidth part.

[0124] In some aspects, the quantity of RBs for the narrow bandwidth data communication bandwidth part is configured via RRC signaling.

[0125] In some aspects, the quantity of RBs for the narrow bandwidth data communication bandwidth part is pre-determined.

[0126] In some aspects, the FDRA corresponds to a size of the narrow bandwidth data communication bandwidth part.

[0127] In some aspects, process 650 includes receiving DCI indicating a starting RB for the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the starting RB for the narrow bandwidth data communication bandwidth part.

[0128] In some aspects, the starting RB is indicated using an RB index included in a set of RB indexes configured on the UE, each RB index of the set of RB indices mapping to a respective starting RB for the narrow bandwidth data communication bandwidth part.

[0129] In some aspects, the FDRA corresponds to a size of the active bandwidth part.

[0130] In some aspects, process 650 includes receiving DCI indicating a starting RB for the FDRA within the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the starting RB for the FDRA within the narrow bandwidth data communication bandwidth part.

[0131] In some aspects, process 650 includes receiving RRC signaling configuring a starting RB for the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the RRC signaling configuring the starting RB for narrow bandwidth data communication bandwidth part.

[0132] At 670, the UE may transmit one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth part. For example, the UE (e.g., using communication manager 140 and / or transmission component 704, depicted in Fig. 7) may transmit one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth part, as described above in connection with, for example, Fig. 5A and at 506.

[0133] Although Fig. 6B shows example blocks of process 650, in some aspects, process 650 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 6B. Additionally, or alternatively, two or more of the blocks of process 650 may be performed in parallel.

[0134] Fig. 7 is a diagram of an example apparatus 700 for wireless communication. The apparatus 700 may be a UE, or a UE may include the apparatus 700. In some aspects, the apparatus 700 includes a reception component 702 and a transmission component 704, which may be in communication with one another (for example, via one or more buses and / or one or more other components). As shown, the apparatus 700 may communicate with another apparatus 706 (such as a UE, a network node, or another wireless communication device) using the reception component 702 and the transmission component 704. As further shown, the apparatus 700 mayinclude the communication manager 140. The communication manager 140 may include a mapping component 708, among other examples.

[0135] In some aspects, the apparatus 700 may be configured to perform one or more operations described herein in connection with Figs. 5 A and 5B. Additionally, or alternatively, the apparatus 700 may be configured to perform one or more processes described herein, such as process 600 of Fig. 6A and / or process 650 of Fig. 6B. In some aspects, the apparatus 700 and / or one or more components shown in Fig. 7 may include one or more components of the UE described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 7 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0136] The reception component 702 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 706. The reception component 702 may provide received communications to one or more other components of the apparatus 700. In some aspects, the reception component 702 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 700. In some aspects, the reception component 702 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2.

[0137] The transmission component 704 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 706. In some aspects, one or more other components of the apparatus 700 may generate communications and may provide the generated communications to the transmission component 704 for transmission to the apparatus 706. In some aspects, the transmission component 704 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 706. In some aspects, the transmission component 704 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2. In some aspects, thetransmission component 704 may be co-located with the reception component 702 in a transceiver.

[0138] The reception component 702 may receive DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part. In some aspects, the mapping component 708 may perform interleaved virtual RB to physical RB mapping based at least in part on information associated with the narrow bandwidth data communication bandwidth part and the FDRA within the narrow bandwidth data communication bandwidth part. In some aspects, the transmission component 704 may transmit one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth part.

[0139] The reception component 702 may receive DCI indicating a starting RB for the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the starting RB for the narrow bandwidth data communication bandwidth part.

[0140] The reception component 702 may receive DCI indicating a starting RB for the FDRA within the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the starting RB for the FDRA within the narrow bandwidth data communication bandwidth part.

[0141] The reception component 702 may receive RRC signaling configuring a starting RB for the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the RRC signaling configuring the starting RB for narrow bandwidth data communication bandwidth part.

[0142] The number and arrangement of components shown in Fig. 7 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 7. Furthermore, two or more components shown in Fig. 7 may be implemented within a single component, or a single component shown in Fig. 7 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 7 may perform one or more functions described as being performed by another set of components shown in Fig. 7.

[0143] Fig. 8 is a diagram illustrating an example 800 of a hardware implementation for an apparatus 805 employing a processing system 810. The apparatus 805 may be a UE.

[0144] The processing system 810 may be implemented with a bus architecture, represented generally by the bus 815. The bus 815 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 810 and the overall designconstraints. The bus 815 links together various circuits including one or more processors and / or hardware components, represented by the processor 820, the illustrated components, and the computer-readable medium / memory 825. The bus 815 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and / or power management circuits.

[0145] The processing system 810 may be coupled to a transceiver 830. The transceiver 830 is coupled to one or more antennas 835. The transceiver 830 provides a means for communicating with various other apparatuses over a transmission medium. The transceiver 830 receives a signal from the one or more antennas 835, extracts information from the received signal, and provides the extracted information to the processing system 810, specifically the reception component 702. In addition, the transceiver 830 receives information from the processing system 810, specifically the transmission component 704, and generates a signal to be applied to the one or more antennas 835 based at least in part on the received information.

[0146] The processing system 810 includes a processor 820 coupled to a computer-readable medium / memory 825. The processor 820 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 825. The software, when executed by the processor 820, causes the processing system 810 to perform the various functions described herein for any particular apparatus. The computer-readable medium / memory 825 may also be used for storing data that is manipulated by the processor 820 when executing software. The processing system further includes at least one of the illustrated components. The components may be software modules running in the processor 820, resident / stored in the computer readable medium / memory 825, one or more hardware modules coupled to the processor 820, or some combination thereof.

[0147] In some aspects, the processing system 810 may be a component of the UE 120 and may include the memory 282 and / or at least one of the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In some aspects, the apparatus 805 for wireless communication includes means for receiving DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part; means for performing interleaved virtual RB to physical RB mapping based at least in part on information associated with the narrow bandwidth data communication bandwidth part and the FDRA within the narrow bandwidth data communication bandwidth part; and / or means for transmitting one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth part. The aforementioned means may be one or more of the aforementioned components of the apparatus 700 and / or the processing system 810 of the apparatus 805 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 810 may include the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In one configuration,the aforementioned means may be the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280 configured to perform the functions and / or operations recited herein.

[0148] Fig. 8 is provided as an example. Other examples may differ from what is described in connection with Fig. 8.

[0149] The following provides an overview of some Aspects of the present disclosure:

[0150] Aspect 1: A method of wireless communication performed by an apparatus of a UE, comprising: receiving DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part; and performing interleaved virtual RB to physical RB mapping based at least in part on information associated with the narrow bandwidth data communication bandwidth part and the FDRA within the narrow bandwidth data communication bandwidth part.

[0151] Aspect 2: The method of Aspect 1, wherein a bandwidth of the narrow bandwidth data communication bandwidth part is 5 megahertz (MHz).

[0152] Aspect 3: The method of any of Aspects 1-2, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on information that identifies a quantity of RBs for the narrow bandwidth data communication bandwidth part.

[0153] Aspect 4: The method of Aspect 3, wherein the quantity of RBs for the narrow bandwidth data communication bandwidth part is configured via RRC signaling.

[0154] Aspect 5: The method of Aspect 3, wherein the quantity of RBs for the narrow bandwidth data communication bandwidth part is pre-determined.

[0155] Aspect 6: The method of any of Aspects 1-5, wherein the FDRA corresponds to a size of the narrow bandwidth data communication bandwidth part.

[0156] Aspect 7: The method of any of Aspects 1-6, further comprising receiving DCI indicating a starting RB for the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the starting RB for the narrow bandwidth data communication bandwidth part.

[0157] Aspect 8: The method of Aspect 7, wherein the starting RB is indicated using an RB index included in a set of RB indexes configured on the UE, each RB index of the set of RB indices mapping to a respective starting RB for the narrow bandwidth data communication bandwidth part.

[0158] Aspect 9: The method of any of Aspects 7-8, wherein the interleaved virtual RB to physical RB mapping is performed based at least in part on the starting RB for the narrow bandwidth data communication bandwidth part, a quantity of RBs for the narrow bandwidth data communication bandwidth part, and an RB bundle size.

[0159] Aspect 10: The method of any of Aspects 1-9, wherein the FDRA corresponds to a size of the active bandwidth part.

[0160] Aspect 11: The method of any of Aspects 1-10, further comprising receiving DCI indicating a starting RB for the FDRA within the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the starting RB for the FDRA within the narrow bandwidth data communication bandwidth part.

[0161] Aspect 12: The method of Aspect 11, wherein the interleaved virtual RB to physical RB mapping is performed based at least in part on the starting RB for the FDRA within the narrow bandwidth data communication bandwidth part, a quantity of RBs for the narrow bandwidth data communication bandwidth part, and an RB bundle size.

[0162] Aspect 13: The method of any of Aspects 1-12, further comprising receiving RRC signaling configuring a starting RB for the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the RRC signaling configuring the starting RB for narrow bandwidth data communication bandwidth part.

[0163] Aspect 14: The method of Aspect 13, wherein the interleaved virtual RB to physical RB mapping is performed based at least in part on the starting RB for the narrow bandwidth data communication bandwidth part configured via RRC signaling, a quantity of RBs for the narrow bandwidth data communication bandwidth part, and an RB bundle size.

[0164] Aspect 15: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-14.

[0165] Aspect 16: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-14.

[0166] Aspect 17: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-14.

[0167] Aspect 18: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-14.

[0168] Aspect 19: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-14.

[0169] Aspect 20: A method of wireless communication performed by an apparatus of a UE, comprising: receiving DCI indicating an FDRA within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part; and transmitting one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth part.

[0170] Aspect 21: The method of Aspect 20, wherein a bandwidth of the narrow bandwidth data communication bandwidth part is 5 megahertz (MHz).

[0171] Aspect 22: The method of any of Aspects 20-21, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on information that identifies a quantity of RBs for the narrow bandwidth data communication bandwidth part.

[0172] Aspect 23: The method of Aspect 22, wherein the quantity of RBs for the narrow bandwidth data communication bandwidth part is configured via RRC signaling.

[0173] Aspect 24: The method of Aspect 22, wherein the quantity of RBs for the narrow bandwidth data communication bandwidth part is pre-determined.

[0174] Aspect 25: The method of any of Aspects 20-24, wherein the FDRA corresponds to a size of the narrow bandwidth data communication bandwidth part.

[0175] Aspect 26: The method of any of Aspects 20-25, further comprising receiving DCI indicating a starting RB for the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the starting RB for the narrow bandwidth data communication bandwidth part.

[0176] Aspect 27: The method of Aspect 26, wherein the starting RB is indicated using an RB index included in a set of RB indexes configured on the UE, each RB index of the set of RB indices mapping to a respective starting RB for the narrow bandwidth data communication bandwidth part.

[0177] Aspect 28: The method of any of Aspects 20-27, wherein the FDRA corresponds to a size of the active bandwidth part.

[0178] Aspect 29: The method of any of Aspects 20-28, further comprising receiving DCI indicating a starting RB for the FDRA within the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the starting RB for the FDRA within the narrow bandwidth data communication bandwidth part.

[0179] Aspect 30: The method of any of Aspects 20-29, further comprising receiving RRC signaling configuring a starting RB for the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based atleast in part on the RRC signaling configuring the starting RB for narrow bandwidth data communication bandwidth part.

[0180] Aspect 31: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 20-30.

[0181] Aspect 32: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 20-30.

[0182] Aspect 33: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 20-30.

[0183] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 20-30.

[0184] Aspect 35: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 20-30.

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

[0186] As used herein, the term “component” is intended to be broadly construed as hardware and / or a combination of hardware and software. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware and / or a combination of hardware and software. It will be apparent that systems and / or methods described herein may be implemented in different forms of hardware and / or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, since those skilled in the art will understand that software and hardware can be designed to implement the systems and / or methods based, at least in part, on the description herein.

[0187] As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.

[0188] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).

[0189] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of’).

Claims

WHAT IS CLAIMED IS:

1. A user equipment (UE) for wireless communication, comprising: a memory; and one or more processors, coupled to the memory, configured to: receive downlink control information (DCI) indicating a frequency domain resource allocation (FDRA) within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part; and transmit one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth part.

2. The UE of claim 1, wherein a bandwidth of the narrow bandwidth data communication bandwidth part is 5 megahertz (MHz).

3. The UE of claim 1, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on information that identifies a quantity of RBs for the narrow bandwidth data communication bandwidth part.

4. The UE of claim 3, wherein the quantity of RBs for the narrow bandwidth data communication bandwidth part is configured via radio resource control (RRC) signaling.

5. The UE of claim 3, wherein the quantity of RBs for the narrow bandwidth data communication bandwidth part is pre -determined.

6. The UE of claim 1, wherein the FDRA corresponds to a size of the narrow bandwidth data communication bandwidth part.

7. The UE of claim 1, wherein the one or more processors are further configured to receive DCI indicating a starting RB for the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the starting RB for the narrow bandwidth data communication bandwidth part.

8. The UE of claim 7, wherein the starting RB is indicated using an RB index included in a set of RB indexes configured on the UE, each RB index of the set of RB indices mapping to a respective starting RB for the narrow bandwidth data communication bandwidth part.

9. The UE of claim 1, wherein the FDRA corresponds to a size of the active bandwidth part.

10. The UE of claim 1, wherein the one or more processors are further configured to receive DCI indicating a starting RB for the FDRA within the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the starting RB for the FDRA within the narrow bandwidth data communication bandwidth part.1 1 . The UE of claim 1, wherein the one or more processors are further configured to receive radio resource control (RRC) signaling configuring a starting RB for the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the RRC signaling configuring the starting RB for narrow bandwidth data communication bandwidth part.

12. A method of wireless communication performed by an apparatus of a user equipment (UE), comprising: receiving downlink control information (DCI) indicating a frequency domain resource allocation (FDRA) within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part; and transmitting one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth part.

13. The method of claim 12, wherein a bandwidth of the narrow bandwidth data communication bandwidth part is 5 megahertz (MHz).

14. The method of claim 12, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on information that identifies a quantity of RBs for the narrow bandwidth data communication bandwidth part.

15. The method of claim 14, wherein the quantity of RBs for the narrow bandwidth data communication bandwidth part is configured via radio resource control (RRC) signaling.

16. The method of claim 14, wherein the quantity of RBs for the narrow bandwidth data communication bandwidth part is pre -determined.

17. The method of claim 12, wherein the FDRA corresponds to a size of the narrow bandwidth data communication bandwidth part.

18. The method of claim 12, further comprising receiving DCI indicating a starting RB for the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the starting RB for the narrow bandwidth data communication bandwidth part.

19. The method of claim 18, wherein the starting RB is indicated using an RB index included in a set of RB indexes configured on the UE, each RB index of the set of RB indices mapping to a respective starting RB for the narrow bandwidth data communication bandwidth part.

20. The method of claim 12, wherein the FDRA corresponds to a size of the active bandwidth part.

21. The method of claim 12, further comprising receiving DCI indicating a starting RB for the FDRA within the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the starting RB for the FDRA within the narrow bandwidth data communication bandwidth part.

22. The method of claim 12, further comprising receiving radio resource control (RRC) signaling configuring a starting RB for the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on the RRC signaling configuring the starting RB for narrow bandwidth data communication bandwidth part.

23. A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising: one or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: receive downlink control information (DCI) indicating a frequency domain resource allocation (FDRA) within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part; and transmit one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth part.

24. The non-transitory computer-readable medium of claim 23, wherein a bandwidth of the narrow bandwidth data communication bandwidth part is 5 megahertz (MHz).

25. The non-transitory computer-readable medium of claim 23, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on information that identifies a quantity of RBs for the narrow bandwidth data communication bandwidth part.

26. The non-transitory computer-readable medium of claim 23, wherein the FDRA corresponds to a size of the narrow bandwidth data communication bandwidth part.

27. An apparatus for wireless communication, comprising: means for receiving downlink control information (DCI) indicating a frequency domain resource allocation (FDRA) within a narrow bandwidth data communication bandwidth part, the narrow bandwidth data communication bandwidth part having a bandwidth that is smaller than a bandwidth of an active bandwidth part; and means for transmitting one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth part.

28. The apparatus of claim 27, wherein a bandwidth of the narrow bandwidth data communication bandwidth part is 5 megahertz (MHz).

29. The apparatus of claim 27, wherein the narrow bandwidth data communication bandwidth part is identified based at least in part on information that identifies a quantity of RBs for the narrow bandwidth data communication bandwidth part.

30. The apparatus of claim 27, wherein the FDRA corresponds to a size of the narrow bandwidth data communication bandwidth part.

Images