Uplink data communication in narrow bandwidth data communication bandwidth portion

Abstract

A user equipment (UE) may be configured to utilize a narrow bandwidth data communication bandwidth portion for data communication. A conventional technology for interleaving virtual resource blocks (RBs) to physical RB mapping is not enough. For example, a conventional interleaving virtual RB to physical RB mapping is based in part on the size of an active bandwidth portion, and RBs are interleaved throughout the active bandwidth portion. However, for a narrow bandwidth data communication bandwidth portion, communication is not supported outside a particular narrow bandwidth portion. The conventional interleaving virtual RB-to-physical RB mapping may cause some virtual RBs to map to physical RBs that are at least partially outside of the narrow bandwidth data communication bandwidth portion, and thus the conventional interleaving virtual RB-to-physical RB mapping should not be utilized for an interleaving virtual RB-to-physical RB mapping over the narrow bandwidth data communication bandwidth portion.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims the priority of Indian 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 is assigned to the assignee of this application. The disclosure of the prior application is considered a part of this patent application and is incorporated into this patent application by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for uplink data communications in a narrow bandwidth data communications bandwidth portion. Background Art

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

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

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. 5G (which may be referred to as New Radio (NR)) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. 5G is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) 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, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in 4G, 5G and other radio access technologies remain useful. Summary of the invention

[0007] In a scenario where a user equipment (UE) (e.g., an enhanced reduced capability UE (eRedCap UE)) is to utilize a narrow bandwidth data communication bandwidth portion for data communication, conventional interleaved virtual resource block (RB) to physical RB mapping techniques are insufficient. For example, conventional interleaved virtual RB to physical RB mapping is based in part on the size of an active bandwidth portion (e.g., a 20 MHz bandwidth portion), which is larger than the size of the narrow bandwidth data communication bandwidth portion, and the RBs are interleaved across the entire active bandwidth portion. However, in the case of a narrow bandwidth data communication bandwidth portion, communications are not supported outside of a particular narrow bandwidth portion (e.g., a particular 5 MHz bandwidth portion). The conventional interleaved virtual RB to physical RB mapping may cause some virtual RBs to be mapped to physical RBs that are at least partially outside of the narrow bandwidth data communication bandwidth portion, and thus 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 portion.

[0008] 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 portion, the narrow bandwidth data communication bandwidth portion having a bandwidth that is smaller than a bandwidth of an active bandwidth portion. The method may include performing interleaved virtual RB to physical RB mapping based at least in part on information associated with the narrow bandwidth data communication bandwidth portion and the FDRA within the narrow bandwidth data communication bandwidth portion.

[0009] Some aspects described herein relate to a UE for wireless communication. The UE may include: a memory; and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to receive a DCI indicating an FDRA within a narrow bandwidth data communication bandwidth portion, the narrow bandwidth data communication bandwidth portion having a bandwidth less than a bandwidth of an active bandwidth portion. 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 portion and the FDRA within the narrow bandwidth data communication bandwidth portion.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a DCI indicating an FDRA within a narrow bandwidth data communication bandwidth portion, the narrow bandwidth data communication bandwidth portion having a bandwidth less than a bandwidth of an active bandwidth portion. The instruction set, 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 portion and the FDRA within the narrow bandwidth data communication bandwidth portion.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a DCI indicating an FDRA within a narrow bandwidth data communication bandwidth portion, the narrow bandwidth data communication bandwidth portion having a bandwidth less than a bandwidth of an active bandwidth portion. 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 portion and the FDRA within the narrow bandwidth data communication bandwidth portion.

[0012] 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 a DCI indicating an FDRA within a narrow bandwidth data communication bandwidth portion, the narrow bandwidth data communication bandwidth portion having a bandwidth less than a bandwidth of an active bandwidth portion. The one or more processors may be configured to send one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth portion.

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

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

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

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

[0017] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily utilized as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and methods of operation) and the associated advantages will be better understood according to the following description. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of limitations to the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 is a diagram illustrating an example of a wireless network.

[0019] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network.

[0020] Figure 3 is a diagram illustrating an example decomposed base station architecture.

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

[0022] Figure 5A and Figure 5B is a diagram illustrating an example associated with uplink data communication in a narrow-bandwidth data communication bandwidth portion.

[0023] Fig. 6A is a flow chart of an example method of wireless communication.

[0024] Figure 6B is a flow chart of an example method of wireless communication.

[0025] Figure 7 is a diagram of an example apparatus for wireless communications.

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

[0027] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent configurations in which the concepts described herein may be practiced. For the purpose of providing a thorough understanding of the various concepts, the specific embodiments include specific details. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, in order to avoid obscuring such concepts, well-known structures and components are shown in block diagram form.

[0028] Several aspects of telecommunication systems will now be presented with reference to various devices and methods. These devices 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, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0029] By way of example, a "processing system" that may include one or more processors implements an element, or any part of an element, or any combination of elements. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. One or more processors in a processing system can execute software. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether it is referred to by software, firmware, middleware, microcode, hardware description language, or other names.

[0030] Therefore, in one or more example embodiments, the described functions can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions can be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), compact disk ROM (CD-ROM), or other optical disk storage, magnetic disk storage, or other magnetic storage devices, a combination of computer-readable media of the above types, 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0043] Devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, or channels by frequency or wavelength. 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 ranges designated 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 (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

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

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

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

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

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

[0049] At the network node 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may use one or more channel quality indicators (CQIs) received from the UE 120 to select one or more modulation and coding schemes (MCSs) for the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 using the MCS selected for the UE 120 and may provide data symbols to the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., 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 (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

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

[0051] 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.

[0052] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include or may be included in 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, antenna group, set of antenna elements, or antenna array may include one or more antenna elements (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or coupled to one or more transmit or receive components (such as Figure 2 One or more antenna elements of one or more components).

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

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

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

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

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

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

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

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

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

[0062] Figure 3 3 is a diagram illustrating an example decomposed base station architecture 300. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed 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). The CU 310 may communicate with one or more DUs 330 via respective midhaul links (such as via an F1 interface). Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

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

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

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

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

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

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

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

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

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

[0072] In the uplink direction, non-interleaved mapping is used between the allocated virtual RBs and the actual physical RBs on the PUSCH. For example, this means that virtual RB n is mapped onto physical RB n (ie, the virtual RB is the same as the physical RB).

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

[0074] DCI (e.g., DCI format 1_0 or DCI format 1_1) may be used to signal downlink resource allocation type 1 on the PDCCH. In general, resource allocation type 1 uses a resource indication value (RIV) to indicate a set of virtual RBs allocated within the active bandwidth part (BWP) of the UE. As described above, the UE maps the set of virtual RBs to actual physical RBs using either non-interleaved mapping or interleaved mapping.

[0075] The set of allocated VRBs assigned to the UE is contiguous. When non-interleaved mapping is used, the virtual RB is the same as the physical RB, and therefore the allocated physical RB is also contiguous. Such allocation may be referred to as local resource allocation. When interleaved mapping is used, an interleaving function is used to derive the allocated physical RB from the allocated virtual RB. In this case, the allocated physical RB is unlikely to be contiguous. Such allocation may be referred to as distributed resource allocation. RIV indicates the starting virtual RBRB start and the number of consecutively allocated virtual RBs L RB The value of RIV is based on the starting virtual RB RB start , the number of consecutively allocated virtual RBs L RB and the size of the active bandwidth portion to be sure.

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

[0077] Figure 4 is a diagram illustrating an example 400 associated with interleaving virtual RB to physical RB mapping. In general, the active bandwidth part BWP includes RB and in the starting position Here, the total RB is divided into RB bundles, where L is the RB bundle size configured via RRC signaling. Figure 4 As shown, the virtual RB bundles at the lower and upper ends of the bandwidth part are mapped to the physical RB bundles at the lower and upper edges of the bandwidth part. As further shown, if the size of the bandwidth part is 24 RBs and the RB bundle size L is 4 RBs, there may be 6 bundles (depending on the boundaries of the bandwidth parts 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 onto physical RB bundles using an interleaving function defined as follows:

[0078] Virtual RB bundle j is mapped to physical RB bundle r×C+c

[0079] where j = 2×c+r; r = 0, 1, ..., R-1; c = 0, 1, ..., C-1; R = 2; and C = N Bundle / R. Figure 4 As an example of a bandwidth with 6 bundles (C=3), according to the above function, virtual RB bundle 1 (VRBB1) is mapped to physical RB bundle 3 (PRBB3), virtual RB bundle 2 (VRBB2) is mapped to physical RB bundle 1 (PRBB1), virtual RB bundle 3 (VRBB3) is mapped to physical RB bundle 4 (PRBB4), and virtual RB bundle 4 (VRBB4) is mapped to physical RB bundle 2 (PRBB2).

[0080] Additionally, in some wireless communication systems, a network node may serve different UEs of different categories and / or support different UEs of different capabilities. For example, a network node may serve a first category of UEs with less advanced capabilities (e.g., lower capabilities and / or reduced capabilities) and a second category of UEs with higher capabilities (e.g., higher capabilities). The first category of UEs may have a reduced feature set compared to the second category of UEs and may be referred to as reduced capability (RedCap) UEs, low-end UEs and / or NR light UEs, among other examples. The first category of UEs may be, for example, MTC UEs, eMTC UEs and / or IoT UEs, as described above in conjunction with Figure 1The second category of UEs may have an advanced feature set compared to the second category of UEs and may be referred to as baseline UEs, high-end UEs, NR UEs, and / or advanced UEs, among other examples.

[0081] In addition, in some systems, the network node may serve a third category of UEs having less advanced capabilities than the first category of UEs. The third category of UEs may have a reduced feature set compared to the first category of UEs and may be referred to as enhanced reduced capability (eRedCap) UEs, low-end UEs, and / or NR ultra-light UEs, among other examples. The third category of UEs may be, for example, MTC UEs, eMTC UEs, and / or IoT UEs, as described above in conjunction with Figure 1 Descriptive.

[0082] In some wireless communication systems, UEs of the first or third category have the capability to meet the requirements of a first (earlier) wireless communication standard but not a second (later) wireless communication standard, while UEs of the second category have the capability to meet the requirements of the second (later) wireless communication standard (and in some cases, also the first wireless communication standard).

[0083] For example, the first category of UEs may support a lower maximum MCS than the second category of UEs (e.g., quadrature phase shift keying (QPSK) compared to 256-quadrature amplitude modulation (QAM), etc.), may support a lower maximum transmit power than the second category of UEs, may have less advanced beamforming capabilities than the second category of UEs (e.g., may not be able to form as many beams as the second category of UEs), may require longer processing time than the second category of UEs, may include less hardware than the second category of UEs (e.g., fewer antennas, fewer transmit antennas, and / or fewer receive antennas), and / or may not be able to communicate over a maximum bandwidth portion as wide as the second category of UEs, as well as other examples. For another example, the third category of UEs may support a lower MCS than the first category of UEs, may support a lower maximum transmit power than the first category of UEs, may have less advanced beamforming capabilities than the first category of UEs, may require longer processing time than the first category of UEs, may include less hardware than the first category of UEs, and / or may not be able to communicate (or be allowed to communicate) over a maximum bandwidth portion as wide as the first category of UEs, as well as other examples.

[0084] In some systems, the bandwidth portion on which some UEs, such as UEs in the third category of UEs (e.g., eRedCap UEs), are allowed to send and receive data communications (e.g., unicast PDSCH communications, broadcast PDSCH communications, PUSCH communications, etc.) may have a size that is smaller than the size of the UE's active bandwidth portion. For example, the UE may be allowed to send and receive data communications in a data communications bandwidth portion having a bandwidth of only 5 MHz, while the active bandwidth portion has a bandwidth of 20 MHz. Such bandwidth portions are referred to herein as narrow-bandwidth data communications bandwidth portions. It is noteworthy that the UE may be allowed to use bandwidth portions having a bandwidth up to the bandwidth of the active bandwidth portion for sending and receiving other physical channels and signals.

[0085] In a scenario where a UE (e.g., an eRedCap UE) is to utilize a narrow bandwidth data communication bandwidth portion for data communication, 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 the size of the active bandwidth portion, and the RBs are interleaved across the entire active bandwidth portion. However, in the case of a narrow bandwidth data communication bandwidth portion, communications are not supported outside of a specific narrow bandwidth portion (e.g., a specific 5 MHz bandwidth portion). Conventional interleaved virtual RB to physical RB mapping may cause some virtual RBs to be mapped to physical RBs that are at least partially outside of the narrow bandwidth data communication bandwidth portion, and therefore, conventional interleaved virtual RB to physical RB mapping may not be applicable.

[0086] Some techniques and devices described herein enable interleaved virtual RB to physical RB mapping for narrow bandwidth data communication bandwidth portions. In some aspects, a UE may receive a DCI indicating an FDRA within a narrow bandwidth data communication bandwidth portion (e.g., a bandwidth portion having a bandwidth less than the bandwidth of an active bandwidth portion), 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 portion and the FDRA within the narrow bandwidth data communication bandwidth portion. In this way, interleaved virtual RB to physical RB mapping may be performed for UEs (e.g., eRedCap UEs) utilizing narrow bandwidth data communication bandwidth portions. Additional details are described below.

[0087] Some techniques and apparatus described herein enable uplink data communications in a narrow-bandwidth data communications bandwidth portion. In some aspects, a UE may receive a DCI indicating an FDRA within a narrow-bandwidth data communications bandwidth portion (e.g., a bandwidth portion having a bandwidth less than the bandwidth of an active bandwidth portion), and may send one or more uplink data communications based at least in part on the FDRA within the narrow-bandwidth data communications bandwidth portion.

[0088] Figure 5Aand Figure 5B is a diagram illustrating an example associated with uplink data communication in a narrow bandwidth data communication bandwidth portion. Figure 5A As shown, example 500 includes communications 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 the 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.

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

[0090] In some aspects, UE 120 may identify the narrow bandwidth data communication bandwidth portion based at least in part on information identifying a number of RBs used for the narrow bandwidth data communication bandwidth portion and information indicating a starting RB for the narrow bandwidth data communication bandwidth portion.

[0091] The number of RBs used for the narrow bandwidth data communication bandwidth portion indicates the maximum size of the narrow bandwidth data communication bandwidth portion (in RBs). In some aspects, the number of RBs used for the narrow bandwidth data communication bandwidth portion is configured on the UE 120 (e.g., by the network node 110) via RRC signaling. Alternatively, in some aspects, the number of RBs used for the narrow bandwidth data communication bandwidth portion is predetermined by the UE 120 or pre-configured on the UE 120 (e.g., according to an applicable wireless communication standard). The number of RBs used for the narrow bandwidth data communication bandwidth portion is referred to herein as the number of RBs N. maxRB .

[0092] In some aspects, the information indicating the starting RB of the narrow bandwidth data communication bandwidth portion includes an indication of the starting RB of the narrow bandwidth data communication bandwidth portion, wherein the indication is received in a DCI. For example, in some aspects, the network node 110 may send a DCI indicating the starting RB for the narrow bandwidth data communication bandwidth portion, and the UE 120 may receive the DCI. Here, the UE 120 may determine, based at least in part on the starting RB for the narrow bandwidth data communication bandwidth portion and the number of RBs N indicated in the DCI. maxRBTo identify the narrow bandwidth data communication bandwidth portion. In some aspects, the starting RB of the narrow bandwidth data communication bandwidth portion may be indicated using an RB index included in a set of RB indexes configured on the UE (e.g., via DCI), wherein each RB index in the set of RB indexes maps to a corresponding starting RB for the narrow bandwidth data communication bandwidth portion. In some aspects, the set of RB indexes may be configured on the UE 120 via RRC signaling (e.g., by the network node 110). In this way, a pool of flexible RB indexes or candidate RB indexes may be used to indicate the narrow bandwidth data communication bandwidth portion, thereby increasing the flexibility of the assignment of the narrow bandwidth data communication bandwidth portion.

[0093] In some aspects, the information indicating the starting RB of the narrow bandwidth data communication bandwidth portion includes an indication of the starting RB for the FDRA within the narrow bandwidth data communication bandwidth portion. For example, in some aspects, UE 120 may determine the starting RB for the FDRA based at least in part on the starting RB and the number of RBs N indicated in the DCI. maxRB In some such aspects, the actual number of RBs in the narrow bandwidth data communication bandwidth portion (ie, the actual size of the narrow bandwidth data communication bandwidth portion) may be less than the number of RBs N. maxRB (For example, to ensure that the narrow bandwidth data communication bandwidth portion is confined to the active bandwidth portion).

[0094] In some implementations, the information identifying the starting RB for the narrow-bandwidth data communication bandwidth portion includes an indication of the starting RB for the narrow-bandwidth data communication bandwidth portion, wherein the indication is received via RRC signaling. For example, in some aspects, the network node 110 may send RRC signaling indicating the starting RB for the narrow-bandwidth data communication bandwidth portion, and the UE 120 may receive the RRC signaling. Here, the UE 120 may determine, at least in part, the starting RB for the narrow-bandwidth data communication bandwidth portion and the number of RBs N indicated via the RRC signaling. maxRB Thus, in some aspects, the narrow bandwidth data communication bandwidth portion may be (semi-statically) configured via RRC signaling.

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

[0096] Alternatively, in some aspects, the FDRA corresponds to the size of the active bandwidth portion. 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 portion), then in some aspects, the value carried in the FDRA field of the DCI may be based at least in part on the size of the active bandwidth portion.

[0097] like Figure 5A As further shown at 504, 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 portion and the FDRA within the narrow bandwidth data communication bandwidth portion.

[0098] In some aspects, UE 120 determines the number of RBs N for the narrow bandwidth data communication bandwidth portion based at least in part on the starting RB, the number of RBs N, and the like indicated in the DCI. maxRB The interleaved virtual RB to physical RB mapping may be performed based on the RB bundle size L and the RB bundle size L. For example, in some aspects, the UE 120 receives a DCI indicating a narrow bandwidth communication bandwidth portion (e.g., via a starting RB for the narrow bandwidth data communication bandwidth portion, as described above) and an actual FDRA within the narrow bandwidth data communication bandwidth portion. In such a scenario, the interleaved virtual RB to physical RB mapping may be based at least in part on the starting RB for the narrow bandwidth data communication bandwidth portion indicated in the DCI (rather than the starting RB of the active bandwidth portion). ), the number of RBs N maxRB (rather than the size of the active bandwidth ) and RB bundle size L. In some aspects, RB bundle size L may be configured on UE 120 (eg, by network node 110) via RRC signaling.

[0099] Alternatively, in some aspects, UE 120 determines the number of RBs N based at least in part on the starting RB, the number of RBs N, and the number of RBs N for the FDRA within the narrow bandwidth data communication bandwidth portion. maxRB The interleaved virtual RB to physical RB mapping may be performed based at least in part on the starting RB for the FDRA as indicated by the DCI (rather than the starting RB for the active bandwidth portion). ), the number of RBs N maxRB (rather than the size of the active bandwidth ) and RB bundle size L. In some such aspects, less than the number of RBs N maxRBThe value of may be used in association with performing interleaved virtual RB to physical RB mapping (eg, when less than the number of RBs N maxRB The value of defines the narrow-bandwidth data communication bandwidth portion to ensure that the narrow-bandwidth data communication bandwidth portion is limited to the active bandwidth portion, as described above).

[0100] Alternatively, in some aspects, UE 120 may configure the starting RB, the number of RBs N, and the bandwidth portion for narrow bandwidth data communication based at least in part on the starting RB, the number of RBs N, and the bandwidth portion for narrow bandwidth data communication configured via RRC signaling. maxRB The interleaved virtual RB to physical RB mapping may be performed based on the RB bundle size L and the RB bundle size L. For example, in some aspects, the UE 120 receives RRC signaling indicating a narrow bandwidth data communication bandwidth portion and receives a DCI indicating an FDRA within the narrow bandwidth data communication bandwidth portion. In such a scenario, the interleaved virtual RB to physical RB mapping may be based at least in part on the starting RB for the narrow bandwidth data communication bandwidth portion (rather than the starting RB of the active bandwidth portion) indicated via the RRC signaling. ), the number of RBs N maxRB (rather than the size of the active bandwidth ) and RB bundle size L.

[0101] As shown at 506, UE 120 may send 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, UE 120 may map one or more virtual RBs indicated by the FDRA to one or more physical RBs, and may send or receive data communications in the identified one or more physical RBs. Additionally or alternatively (e.g., in an alternative scheme for performing interleaved virtual RB to physical RB mapping as described herein), UE 120 may send one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth portion. That is, UE 120 may send one or more uplink data communications in resources corresponding to the FDRA indicated in the DCI received by UE 120.

[0102] In one alternative to performing interleaved virtual RB to physical RB mapping as described herein, UE 120 may be configured such that interleaved virtual RB to physical RB mapping does not apply to certain classes of UEs (eg, eRedCap UEs).

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

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

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

[0106] Fig. 6A is a flow chart of an example process 600 for wireless communication. The process 600 may be performed by, for example, a UE (eg, UE 120).

[0107] At 610, the UE may receive a DCI indicating a FDRA within a narrow bandwidth data communication bandwidth portion having a bandwidth that is less than a bandwidth of the active bandwidth portion. Figure 7 The depicted communication manager 140 and / or receiving component 702) may receive a DCI indicating a FDRA within a narrow bandwidth data communication bandwidth portion having a bandwidth less than a bandwidth of an active bandwidth portion, as described above in conjunction with, for example, Figure 5A Described at 502.

[0108] In some aspects, the bandwidth of the narrow bandwidth data communications bandwidth portion is 5 megahertz (MHz).

[0109] In some aspects, the narrow bandwidth data communications bandwidth portion is identified based at least in part on information identifying a number of RBs used for the narrow bandwidth data communications bandwidth portion.

[0110] In some aspects, the number of RBs used for the narrow bandwidth data communication bandwidth portion is configured via RRC signaling.

[0111] In some aspects, the number of RBs used for the narrow bandwidth data communication bandwidth portion is predetermined.

[0112] In some aspects, the FDRA corresponds to the size of the narrow-bandwidth data communication bandwidth portion.

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

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

[0115] In some aspects, the FDRA corresponds to the size of the active bandwidth portion.

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

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

[0118] 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 portion and the FDRA within the narrow bandwidth data communication bandwidth portion. Figure 7 The depicted communication manager 140 and / or 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 portion and the FDRA within the narrow bandwidth data communication bandwidth portion, as described above in conjunction with, for example Figure 5A and as described at 504 .

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

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

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

[0122] Although Fig. 6A Example blocks of process 600 are shown, but in some aspects, process 600 may include Fig. 6AThe blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 600 may be performed in parallel.

[0123] Figure 6B 6 is a flow diagram of an example process 650 for wireless communication. The process 650 may be performed by, for example, a UE (eg, UE 120).

[0124] At 660, the UE may receive a DCI indicating a FDRA within a narrow bandwidth data communication bandwidth portion having a bandwidth that is less than a bandwidth of the active bandwidth portion. Figure 7 The depicted communication manager 140 and / or receiving component 702) may receive a DCI indicating a FDRA within a narrow bandwidth data communication bandwidth portion having a bandwidth less than a bandwidth of an active bandwidth portion, as described above in conjunction with, for example, Figure 5A Described at 502.

[0125] In some aspects, the bandwidth of the narrow bandwidth data communications bandwidth portion is 5 megahertz (MHz).

[0126] In some aspects, the narrow bandwidth data communications bandwidth portion is identified based at least in part on information identifying a number of RBs used for the narrow bandwidth data communications bandwidth portion.

[0127] In some aspects, the number of RBs used for the narrow bandwidth data communication bandwidth portion is configured via RRC signaling.

[0128] In some aspects, the number of RBs used for the narrow bandwidth data communication bandwidth portion is predetermined.

[0129] In some aspects, the FDRA corresponds to the size of the narrow-bandwidth data communication bandwidth portion.

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

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

[0132] In some aspects, the FDRA corresponds to the size of the active bandwidth portion.

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

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

[0135] At 670, the UE may send one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communications bandwidth portion. Figure 7 The depicted communication manager 140 and / or transmitting 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 portion, as described above in conjunction with, for example, Figure 5A and as described at 506 .

[0136] Although Figure 6B Example blocks of process 650 are shown, but in some aspects, process 650 may include Figure 6B The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 650 may be performed in parallel.

[0137] Figure 7 700 is a diagram of an example apparatus 700 for wireless communication. Apparatus 700 may be a UE, or a UE may include apparatus 700. In some aspects, apparatus 700 includes a receiving component 702 and a transmitting component 704 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 700 may communicate with another apparatus 706 (such as a UE, a network node, or another wireless communication device) using receiving component 702 and transmitting component 704. As further shown, apparatus 700 may include a communication manager 140. Communication manager 140 may include mapping component 708, as well as other examples.

[0138] In some aspects, the apparatus 700 may be configured to perform Figure 5A and Figure 5B Additionally or alternatively, the apparatus 700 may be configured to perform one or more processes described herein, such as Fig. 6A Course 600 and / or Figure 6B The process 650. In some aspects, Figure 7The device 700 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Figure 7 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in 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 can be executed by a controller or processor to perform the function or operation of the component.

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

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

[0141] The receiving component 702 may receive a DCI indicating an FDRA within a narrow bandwidth data communication bandwidth portion having a bandwidth less than a bandwidth of the active bandwidth portion. 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 portion and the FDRA within the narrow bandwidth data communication bandwidth portion. In some aspects, the sending component 704 may send one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth portion.

[0142] Receiving component 702 can receive a DCI indicating a starting RB for a narrow bandwidth data communications bandwidth portion, wherein the narrow bandwidth data communications bandwidth portion is identified based at least in part on the starting RB for the narrow bandwidth data communications bandwidth portion.

[0143] Receiving component 702 can receive a DCI indicating a starting RB for a FDRA within a narrow bandwidth data communications bandwidth portion, wherein the narrow bandwidth data communications bandwidth portion is identified based at least in part on the starting RB for the FDRA within the narrow bandwidth data communications bandwidth portion.

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

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

[0146] Figure 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.

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

[0148] 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 components for communicating with various other devices through a transmission medium. The transceiver 830 receives signals from one or more antennas 835, extracts information from the received signals, and provides the extracted information to the processing system 810 (specifically the receiving component 702). In addition, the transceiver 830 receives information from the processing system 810 (specifically the transmitting 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.

[0149] 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 executing software stored on the computer readable medium / memory 825. The software, when executed by the processor 820, causes the processing system 810 to perform various functions described herein for any particular device. The computer readable medium / memory 825 may also be used to store data manipulated by the processor 820 when executing the software. The processing system also includes at least one of the illustrated components. A component may be: a software module 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.

[0150] 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 a component for receiving a DCI indicating a FDRA within a narrow bandwidth data communication bandwidth portion, the narrow bandwidth data communication bandwidth portion having a bandwidth less than the bandwidth of the active bandwidth portion; a component for performing interleaved virtual RB to physical RB mapping based at least in part on information associated with the narrow bandwidth data communication bandwidth portion and the FDRA within the narrow bandwidth data communication bandwidth portion; and / or a component for sending one or more uplink data communications based at least in part on the FDRA within the narrow bandwidth data communication bandwidth portion. The aforementioned components may be one or more of the aforementioned components of the processing system 810 of the apparatus 700 and / or the apparatus 805 configured to perform the functions recited by the aforementioned components. 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 components 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 stated herein.

[0151] Figure 8 are provided as examples. Other examples can be combined with Figure 8 The examples described are different.

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

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

[0154] Aspect 2: The method according to aspect 1, wherein the bandwidth of the narrow bandwidth data communication bandwidth portion is 5 megahertz (MHz).

[0155] Aspect 3: The method according to any one of aspects 1 to 2, wherein the narrow-bandwidth data communication bandwidth portion is identified based at least in part on information identifying a number of RBs used for the narrow-bandwidth data communication bandwidth portion.

[0156] Aspect 4: The method according to aspect 3, wherein the number of RBs used for the narrow bandwidth data communication bandwidth portion is configured via RRC signaling.

[0157] Aspect 5: The method according to aspect 3, wherein the number of RBs used for the narrow bandwidth data communication bandwidth portion is predetermined.

[0158] Aspect 6: The method according to any one of aspects 1 to 5, wherein the FDRA corresponds to the size of the narrow-bandwidth data communication bandwidth portion.

[0159] Aspect 7: According to the method described in any one of Aspects 1 to 6, the method further includes: receiving a DCI indicating a starting RB for the narrow bandwidth data communication bandwidth portion, wherein the narrow bandwidth data communication bandwidth portion is identified at least in part based on the starting RB for the narrow bandwidth data communication bandwidth portion.

[0160] Aspect 8: The method according to 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 in the set of RB indexes being mapped to a corresponding starting RB for the narrow bandwidth data communication bandwidth portion.

[0161] Aspect 9: A method according to any one of Aspects 7 to 8, wherein the interleaved virtual RB to physical RB mapping is performed at least in part based on the starting RB used for the narrow bandwidth data communication bandwidth portion, the number of RBs used for the narrow bandwidth data communication bandwidth portion, and the RB bundle size.

[0162] Aspect 10: The method according to any one of aspects 1 to 9, wherein the FDRA corresponds to the size of the active bandwidth portion.

[0163] Aspect 11: According to the method described in any one of Aspects 1 to 10, the method further includes: receiving a DCI indicating a starting RB for the FDRA within the narrow-bandwidth data communication bandwidth portion, wherein the narrow-bandwidth data communication bandwidth portion is identified at least in part based on the starting RB for the FDRA within the narrow-bandwidth data communication bandwidth portion.

[0164] Aspect 12: A method according to Aspect 11, wherein the interleaved virtual RB to physical RB mapping is performed at least in part based on the starting RB of the FDRA within the narrow bandwidth data communication bandwidth portion, the number of RBs used for the narrow bandwidth data communication bandwidth portion, and the RB bundle size.

[0165] Aspect 13: According to the method described in any one of Aspects 1 to 12, the method further includes: receiving RRC signaling of a starting RB configured for the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified at least in part based on the RRC signaling of the starting RB configured for the narrow bandwidth data communication bandwidth part.

[0166] Aspect 14: A method according to aspect 13, wherein the interleaved virtual RB to physical RB mapping is performed at least in part based on the starting RB for the narrow bandwidth data communication bandwidth portion, the number of RBs for the narrow bandwidth data communication bandwidth portion and the RB bundle size configured via RRC signaling.

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

[0168] Aspect 16: A device for wireless communication, the device comprising: a memory and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more aspects of aspects 1 to 14.

[0169] Aspect 17: An apparatus for wireless communication, the apparatus comprising: at least one component for performing the method according to one or more aspects of aspects 1 to 14.

[0170] 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 according to one or more of aspects 1 to 14.

[0171] Aspect 19: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more of aspects 1 to 14.

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

[0173] Aspect 21: The method according to aspect 20, wherein the bandwidth of the narrow bandwidth data communication bandwidth portion is 5 megahertz (MHz).

[0174] Aspect 22: The method according to any one of aspects 20 to 21, wherein the narrow-bandwidth data communication bandwidth portion is identified based at least in part on information identifying a number of RBs used for the narrow-bandwidth data communication bandwidth portion.

[0175] Aspect 23: The method according to aspect 22, wherein the number of RBs used for the narrow bandwidth data communication bandwidth portion is configured via RRC signaling.

[0176] Aspect 24: The method according to aspect 22, wherein the number of RBs used for the narrow bandwidth data communication bandwidth portion is predetermined.

[0177] Aspect 25: The method according to any one of Aspects 20 to 24, wherein the FDRA corresponds to the size of the narrow-bandwidth data communication bandwidth portion.

[0178] Aspect 26: According to the method described in any one of Aspects 20 to 25, the method further includes: receiving a DCI indicating a starting RB for the narrow bandwidth data communication bandwidth portion, wherein the narrow bandwidth data communication bandwidth portion is identified at least in part based on the starting RB for the narrow bandwidth data communication bandwidth portion.

[0179] Aspect 27: A method according to aspect 26, wherein the starting RB is indicated using an RB index included in a set of RB indices configured on the UE, each RB index in the set of RB indices being mapped to a corresponding starting RB for the narrow bandwidth data communication bandwidth portion.

[0180] Aspect 28: The method according to any one of Aspects 20 to 27, wherein the FDRA corresponds to the size of the active bandwidth portion.

[0181] Aspect 29: According to the method described in any one of Aspects 20 to 28, the method further includes: receiving a DCI indicating a starting RB for the FDRA within the narrow-bandwidth data communication bandwidth portion, wherein the narrow-bandwidth data communication bandwidth portion is identified at least in part based on the starting RB for the FDRA within the narrow-bandwidth data communication bandwidth portion.

[0182] Aspect 30: According to the method described in any one of Aspects 20 to 29, the method further includes: receiving RRC signaling of a starting RB configured for the narrow bandwidth data communication bandwidth part, wherein the narrow bandwidth data communication bandwidth part is identified at least in part based on the RRC signaling of the starting RB configured for the narrow bandwidth data communication bandwidth part.

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

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

[0185] Aspect 33: An apparatus for wireless communication, the apparatus comprising: at least one component for performing the method according to one or more aspects of aspects 20 to 30.

[0186] 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 according to one or more of aspects 20 to 30.

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

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

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

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

[0191] Although the specific combination of features is stated 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 can be combined in a manner that is not specifically stated in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, 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 sorting of a, b and c).

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

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: receiving downlink control information (DCI) indicating a frequency domain resource allocation (FDRA) within a narrow bandwidth data communications bandwidth portion having a bandwidth less than a bandwidth of an active bandwidth portion; as well as One or more uplink data communications are transmitted based at least in part on the FDRA within the narrow-bandwidth data communications bandwidth portion.

2. The UE of claim 1, wherein the bandwidth of the narrow-bandwidth data communication bandwidth portion is 5 megahertz (MHz). 3 . The UE of claim 1 , wherein the narrow-bandwidth data communication bandwidth portion is identified based at least in part on information identifying a number of RBs used for the narrow-bandwidth data communication bandwidth portion. 4 . The UE of claim 3 , wherein the number of RBs used for the narrow-bandwidth data communication bandwidth portion is configured via radio resource control (RRC) signaling. 5 . The UE of claim 3 , wherein the number of RBs used for the narrow-bandwidth data communication bandwidth portion is predetermined. The UE of claim 1 , wherein the FDRA corresponds to a size of the narrow-bandwidth data communications bandwidth portion.

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

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 in the set of RB indexes being mapped to a corresponding starting RB for the narrow-bandwidth data communication bandwidth portion.

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

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

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

12. A method of wireless communication performed by a device of a user equipment (UE), the method comprising: receiving downlink control information (DCI) indicating a frequency domain resource allocation (FDRA) within a narrow bandwidth data communications bandwidth portion having a bandwidth less than a bandwidth of an active bandwidth portion; as well as One or more uplink data communications are transmitted based at least in part on the FDRA within the narrow-bandwidth data communications bandwidth portion.

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

14. The method of claim 12, wherein the narrow-bandwidth data communications bandwidth portion is identified based at least in part on information identifying a number of RBs used for the narrow-bandwidth data communications bandwidth portion.

15. The method of claim 14, wherein the number of RBs used for the narrow-bandwidth data communications bandwidth portion is configured via radio resource control (RRC) signaling.

16. The method of claim 14, wherein the number of RBs used for the narrow bandwidth data communication bandwidth portion is predetermined.

17. The method of claim 12, wherein the FDRA corresponds to a size of the narrow-bandwidth data communications bandwidth portion.

18. The method according to claim 12, further comprising: A DCI is received that indicates a starting RB for the narrow-bandwidth data communications bandwidth portion, wherein the narrow-bandwidth data communications bandwidth portion is identified based at least in part on the starting RB for the narrow-bandwidth data communications bandwidth portion.

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 in the set of RB indexes being mapped to a corresponding starting RB for the narrow-bandwidth data communication bandwidth portion.

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

21. The method according to claim 12, further comprising: A DCI is received that indicates a starting RB for the FDRA within the narrow-bandwidth data communications bandwidth portion, wherein the narrow-bandwidth data communications bandwidth portion is identified based at least in part on the starting RB for the FDRA within the narrow-bandwidth data communications bandwidth portion.

22. The method according to claim 12, further comprising: Radio resource control (RRC) signaling is received that configures a starting RB for the narrow bandwidth data communications bandwidth portion, wherein the narrow bandwidth data communications bandwidth portion is identified based at least in part on the RRC signaling that configures the starting RB for the narrow bandwidth data communications bandwidth portion.

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

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

25. The non-transitory computer readable medium of claim 23, wherein the narrow-bandwidth data communications bandwidth portion is identified based at least in part on information identifying a number of RBs used for the narrow-bandwidth data communications bandwidth portion.

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

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

28. The apparatus of claim 27, wherein the bandwidth of the narrow bandwidth data communications bandwidth portion is 5 megahertz (MHz).

29. The apparatus of claim 27, wherein the narrow-bandwidth data communications bandwidth portion is identified based at least in part on information identifying a number of RBs used for the narrow-bandwidth data communications bandwidth portion.

30. The apparatus of claim 27, wherein the FDRA corresponds to a size of the narrow-bandwidth data communications bandwidth portion.

Images