WO2025072817A1 - Pdsch vrb-to-vrb mapping enhancements for high-power narrowband interferer coexistence - Google Patents

Abstract

A method implemented by a wireless transmit/receive unit (WTRU) is disclosed. The method may include mapping resource allocation information of a data transmission to a set of virtual resource block bundles. The method may also include mapping the set of virtual resource block bundles to a first set of physical resource block bundles based on a first mapping function. Further, the method may include mapping the first set of the physical resource block bundles to the first physical resource block bundles of a second set of physical resource block bundles. The second set of the physical resource block bundles may include the first physical resource block bundles and second physical resource block bundles. The first physical resource block bundles may be available for data transmission and the second physical resource block bundles may be unavailable for data transmission.

Description

PDSCH VRB-TO-VRB MAPPING ENHANCEMENTS FOR HIGH-POWER NARROWBAND INTERFERER COEXISTENCE CROSS-REFERENCE TO RELATED APPLICATIONS [0001] This application claims the benefits of U.S. Provisional Application No.63/540,842, filed September 27, 2023, the contents of which are incorporated by reference. BACKGROUND [0002] Physical downlink shared channel (PDSCH) resource allocation type 0 is a bitmap-based allocation scheme. The most flexible way of indicating the set of resource blocks that a device is to receive for a downlink transmission is to include a bitmap with a size equal to the number of resource blocks in the bandwidth part (BWP). This may allow for an arbitrary combination of the resource blocks to be scheduled for transmission to the device but may also result in a very large bitmap in the case of a large bandwidth. To reduce the bitmap size while keeping sufficient allocation flexibility, resource allocation type 0 points not to individual resource blocks (RBs), but to groups of contiguous RBs. The size of such a resource block group (RBG) is determined by the size of the BWP. Two different configurations are possible for each size of the BWP, possibly resulting in different RBG sizes for a given size of the BWP. [0003] On the other hand, resource allocation type 1 does not rely on a bitmap. Instead, it encodes the resource allocation as a start position and the length of the RB allocation. As a result, resource allocation type 1 only supports frequency-contiguous allocations, thereby reducing the number of bits required for signaling the RB allocation. [0004] All resource allocation types refer to virtual resource blocks (VRBs). For resource allocation type 0, a non-interleaved mapping from virtual to physical resource blocks is used, meaning that the VRBs are mapped directly to the corresponding PRBs. For resource allocation type 1, both interleaved and non-interleaved mapping are supported. The VRB-to-PRB mapping bit (if present in downlink only) in the DCI indicates whether the allocation signaling uses interleaved or non-interleaved mapping. In the uplink, non-interleaved mapping is always used. SUMMARY [0005] The present disclosure is directed to techniques that ensure robust and efficient physical downlink shared channel (PDSCH) interleaved or non-interleaved virtual resource block (VRB)-to-physical resource block (PRB) mapping while mitigating the interference to and from the high-power narrowband interferer via dynamic triggering of PDSCH VRB-to-SkipPRB mapping for high-power narrowband interferer coexistence. [0006] In one aspect, a method implemented by a wireless transmit/receive unit (WTRU) is disclosed. The method may include receiving a downlink control transmission. The downlink control transmission may include resource allocation information for a data transmission. The method may also include mapping the received resource allocation information of the data transmission to a set of virtual resource block bundles. Further, the -1- 8687062.1 method may include mapping the set of virtual resource block bundles to a first set of physical resource block bundles based on a first mapping function. The first set of the physical resource block bundles may be contiguous. Additionally, the method may include mapping the first set of the physical resource block bundles to the first physical resource block bundles of a second set of physical resource block bundles. The second set of the physical resource block bundles may include the first physical resource block bundles and second physical resource block bundles. The first physical resource block bundles may be available for data transmission and the second physical resource block bundles may be unavailable for data transmission. The first physical resource block bundles may be non-contiguous. Further, the method may include using the corresponding allocated resources in the first physical resource block bundles for data reception. [0007] In another aspect, a method for wireless communications is disclosed. The method may include mapping a set of virtual resource block bundles to a first set of physical resource block bundles based on a first mapping function. The first set of the physical resource block bundles may be contiguous. The method may also include mapping the first set of the physical resource block bundles to the first physical resource block bundles of a second set of physical resource block bundles. The second set of the physical resource block bundles may include the first physical resource block bundles and second physical resource block bundles. The first physical resource block bundles may be available for data transmission and the second physical resource block bundles may be unavailable for data transmission. The first physical resource block bundles may be non-contiguous. Further, the method may include using the first physical resource block bundles for a data transmission. BRIEF DESCRIPTION OF THE DRAWINGS [0008] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, wherein like reference numerals in the figures indicate like elements, and wherein: [0009] FIG.1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented; [0010] FIG.1B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG.1A according to an embodiment; [0011] FIG.1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG.1A according to an embodiment; [0012] FIG.1D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG.1A according to an embodiment; [0013] FIG.2 illustrates an example of a physical downlink shared channel (PDSCH) interleaved virtual resource block (VRB)-to-physical resource block (PRB) mapping; [0014] FIG.3 illustrates an example of a physical downlink shared channel (PDSCH) interleaved virtual resource block (VRB)-to-skip physical resource block (PRB) mapping; -2- 8687062.1 [0015] FIG.4 illustrates an example of a physical downlink shared channel (PDSCH) non-interleaved virtual resource block (VRB)-to-skip physical resource block (PRB) mapping. [0016] FIG.5 is a flow chart of a method of PRB-to-SkipPRB mapping for a data reception, according to an example implementation; [0017] FIG.6 is a flow chart of a method of VRB-to-SkipPRB mapping for a data transmission, according to another example implementation; and [0018] FIG.7 is a flow chart of a method of VRB-to-SkipPRB mapping for a data reception, according to another example implementation. DETAILED DESCRIPTION [0019] Recent trends are driving researchers to create solutions for cellular network deployments in the presence of high-power narrowband interferers (e.g., radio detection and ranging (RADAR)). Although the baseline functionality provided by 5G could be used to provide some level of coexistence with high-power narrowband interferers, enhancements may be required to realize the full 5G potential. [0020] When a high-power narrowband interferer, such as RADAR, operates in a band that overlaps with the resource blocks (RBs) transmitted to the WTRU for an interleaved physical downlink shared channel (PDSCH), the WTRU may not be able to reliably receive data radio bearer (DRB) and signaling radio bearer (SRB) traffic on the downlink. In addition, there is a potential for the interleaved PDSCH transmission to interfere with the high-power narrowband interferer system, which is also problematic. Therefore, there is a need for new mechanisms and techniques to ensure robust and efficient PDSCH transmission and reception when coexisting with high-power narrowband interferers. [0021] The present disclosure to directed to techniques that ensure robust and efficient PDSCH interleaved or non-interleaved virtual resource block (VRB)-to-physical resource block (PRB) mapping while mitigating the interference to and from a high-power narrowband interferer via dynamic triggering of PDSCH VRB-to-SkipPRB mapping for high-power narrowband interferer coexistence. [0022] FIG.1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single- carrier FDMA (SC-FDMA), zero-tail unique-word discrete Fourier transform Spread OFDM (ZT-UW-DFT-S- OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like. [0023] As shown in FIG.1A, the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public -3- 8687062.1 switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a station (STA), may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE. [0024] The communications systems 100 may also include a base station 114a and/or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and/or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as a gNode B (gNB), a new radio (NR) NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements. [0025] The base station 114a may be part of the RAN 104, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, and the like. The base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions. [0026] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency -4- 8687062.1 (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT). [0027] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed Uplink (UL) Packet Access (HSUPA). [0028] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro). [0029] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using NR. [0030] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB). [0031] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA20001X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like. [0032] The base station 114b in FIG.1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG.1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106. -5- 8687062.1 [0033] The RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in FIG.1A, it will be appreciated that the RAN 104 and/or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may be utilizing a NR radio technology, the CN 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology. [0034] The CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT. [0035] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG.1A may be configured to communicate with the base station 114a, which may employ a cellular- based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology. [0036] FIG.1B is a system diagram illustrating an example WTRU 102. As shown in FIG.1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment. [0037] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless -6- 8687062.1 environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG.1B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip. [0038] The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In an embodiment, the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals. [0039] Although the transmit/receive element 122 is depicted in FIG.1B as a single element, the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116. [0040] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example. [0041] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown). [0042] The processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li- ion), etc.), solar cells, fuel cells, and the like. -7- 8687062.1 [0043] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment. [0044] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors. The sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor and the like. [0045] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and DL (e.g., for reception) may be concurrent and/or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the DL (e.g., for reception)). [0046] FIG.1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106. [0047] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a. [0048] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users -8- 8687062.1 in the UL and/or DL, and the like. As shown in FIG.1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface. [0049] The CN 106 shown in FIG.1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator. [0050] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA. [0051] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface. The SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like. [0052] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. [0053] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. [0054] Although the WTRU is described in FIGS.1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network. [0055] In representative embodiments, the other network 112 may be a WLAN. [0056] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, -9- 8687062.1 where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic. The peer-to- peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication. [0057] When using the 802.11ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in 802.11 systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS. [0058] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel. [0059] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non- contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC). [0060] Sub 1 GHz modes of operation are supported by 802.11af and 802.11ah. The channel operating bandwidths, and carriers, are reduced in 802.11af and 802.11ah relative to those used in 802.11n, and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support Meter Type Control/Machine- Type Communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited -10- 8687062.1 bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life). [0061] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes. Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode) transmitting to the AP, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle. [0062] In the United States, the available frequency bands, which may be used by 802.11ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah is 6 MHz to 26 MHz depending on the country code. [0063] FIG.1D is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106. [0064] The RAN 104 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c). [0065] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using -11- 8687062.1 subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing a varying number of OFDM symbols and/or lasting varying lengths of absolute time). [0066] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non- standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c. [0067] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, DC, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG.1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface. [0068] The CN 106 shown in FIG.1D may include at least one AMF 182a, 182b, at least one UPF 184a,184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator. [0069] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of non-access stratum (NAS) signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and the like. The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi. -12- 8687062.1 [0070] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 106 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 106 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet-based, and the like. [0071] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, and the like. [0072] The CN 106 may facilitate communications with other networks. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local DN 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b. [0073] In view of FIGs.1A-1D, and the corresponding description of FIGs.1A-1D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions. [0074] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and/or performing testing using over-the-air wireless communications. [0075] The one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., -13- 8687062.1 testing) wired and/or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data. [0076] Physical downlink shared channel (PDSCH)-frequency domain resource allocation. PDSCH resource allocation type 0 is a bitmap-based allocation scheme. The most flexible way of indicating the set of resource blocks that a device is to receive for a downlink transmission is to include a bitmap with size equal to the number of resource blocks in the bandwidth part (BWP). This may allow for an arbitrary combination of the resource blocks to be scheduled for transmission to the device but may also result in a very large bitmap in the case of a large bandwidth. To reduce the bitmap size while keeping sufficient allocation flexibility, resource allocation type 0 points not to individual resource blocks (RBs), but to groups of contiguous RBs. The size of such a resource block group (RBG) is determined by the size of the BWP. Two different configurations are possible for each size of the BWP, possibly resulting in different RBG sizes for a given size of the BWP. [0077] On the other hand, resource allocation type 1 does not rely on a bitmap. Instead, it encodes the resource allocation as a start position and the length of the RB allocation. As a result, resource allocation type 1 only supports frequency-contiguous allocations, thereby reducing the number of bits required for signaling the RB allocation. [0078] All resource allocation types refer to virtual resource blocks (VRBs). For resource allocation type 0, a non-interleaved mapping from virtual to physical resource blocks (PRBs) is used, meaning that the VRBs are mapped directly to the corresponding PRBs. For resource allocation type 1, both interleaved and non- interleaved mapping are supported. The VRB-to-PRB mapping bit (if present in downlink only) in the DCI indicates whether the allocation signaling uses interleaved or non-interleaved mapping. In the uplink, non- interleaved mapping is always used. [0079] The resource allocation scheme used for radio resource allocation (RRC) may be configured as: type 0, type 1, dynamic selection between type 0 and type 1, and type 2. For fallback DCIs, only resource allocation type 1 is supported as a small overhead is more important than the flexibility to configure non- contiguous resources. [0080] PDSCH VRB-to-PRB Mapping. The time-frequency resources to be used for PDSCH transmission are signaled by the scheduler as a set of VRBs and a set of orthogonal frequency divisional multiplexing (OFDM) symbols. To schedule these resources, the modulation symbols are mapped to resource elements in a frequency-first, time-second manner. The VRBs containing the modulation symbols are mapped to PRBs in the BWP used for transmission. Depending on the BWP used for transmission, the common resource blocks (CRBs) and hence the exact frequency location on the carrier can be determined. [0081] There are two methods for mapping VRBs to PRBs: non-interleaved and interleaved mapping. The mapping used can be controlled on a dynamic basis using the VRB-to-PRB mapping bit in the DCI scheduling the transmission. Non-interleaved mapping means that a VRB maps directly to a PRB in the same BWP. This is useful in cases when the network tries to allocate transmissions to physical resources with instantaneously -14- 8687062.1 favorable channel conditions. On the other hand, the reason for interleaved mapping is to achieve frequency diversity, the benefits of which can be motivated separately for small and large resource allocations. Interleaved VRB-to-PRB mapping is supported for resource allocation type 1 only since resource allocation type 0 can provide a high degree of flexibility in resource allocation. [0082] For small resource allocations (e.g., voice services), channel-dependent scheduling may not be desirable from an overhead perspective due to the amount of feedback signaling required or may not be possible due to fast channel variations for a rapidly moving device. In this regard, frequency diversity by distributing the transmission in the frequency domain is an alternative way to exploit channel variations. Although frequency diversity can be achieved by using resource allocation type 0, this resource allocation scheme implies a large control signaling overhead relative to the data payload transmitted, as well as limited possibilities to signal very small allocations. Instead, by using the more compact resource allocation type 1, which is only capable of signaling contiguous resource allocations, combined with an interleaved VRB-to-PRB mapping, frequency diversity can be achieved with a relatively small overhead. [0083] For large resource allocations possibly spanning the whole BWP, frequency diversity may still be advantageous. In the case of a large transport block, that is, at very high data rates, the coded data are split into multiple code blocks. Mapping the coded data directly to PRBs in a frequency-first manner would result in each code block occupying only a small number of contiguous PRBs. Hence, if the channel quality varies across the frequency range used for transmission, some code blocks may suffer worse quality than other code bocks, possibly resulting in the overall transport block failing to decode despite almost all code blocks being correctly decoded. If an interleaved resource block mapping is used, one code block occupying a contiguous set of VRBs may be distributed in the frequency domain across multiple, widely spread PRBs, similar to the case of small resource allocations. The result of interleaved VRB-to-PRB mapping is a quality averaging effect across the code blocks, resulting in higher likelihood of correctly decoding very large transport blocks. [0084] The interleaver may be a simple row-column interleaver with depth 2. Adjacent frequency blocks are placed half-BWP-bandwidth separation apart. The interleaving is performed in units of L_i RBs, with L_i equal to 2 or 4. This is to reduce the WTRU complexity and to preserve the precoding resource block groups (PRGs), which can also be 2 or 4 RBs. In order to preserve PRGs after interleaving, the grid of the Li RB interleaver units may be defined in such a way that it aligns with the PRG grid. In addition, the combination of PRG size equals 4 and Li equals to 2 is precluded because this may not preserve PRGs. The interleaver can be switched on and off with an indicator bit in the downlink grant. The “VRB-to-PRB mapping” indicator is included in DCI format 1_01_1, and 1_2. [0085] The WTRU may assume the VRBs are mapped to PRBs according to the indicated mapping scheme (i.e., non-interleaved or interleaved mapping). If no mapping scheme is indicated, the WTRU may assume non- interleaved mapping. For non-interleaved VRB-to-PRB mapping, virtual resource block ^^ is mapped to physical resource block ^^, except for PDSCH transmissions scheduled with DCI format 1_0 in a common search space in which case virtual resource block ^^ is mapped to physical resource block ^^ + ^^_s ^C t_a ^O r_t ^RESET where ^^_s ^C t_a ^O r_t ^RESET -15- 8687062.1 is the lowest-numbered physical resource block in the control resource set in which the corresponding DCI was received. [0086] For interleaved VRB-to-PRB mapping, the mapping process is defined by resource block bundles and virtual resource blocks. Resource block bundles are defined as for PDSCH transmissions scheduled with DCI format 1_0 with the CRC scrambled by SI-RNTI in Type 0-PDCCH common search space in CORESET 0, the set of ^^_B ^s W^ize P_,init resource blocks in CORESET 0 are divided into ^^_bundle = ⌈ ^^_B ^s W^ize P_,init⁄ ^^ ⌉ resource-block bundles in increasing order of the resource-block number and bundle number where ^^ = 2 is the bundle size and ^^_B ^s W^ize P_,init is the size of CORESET 0. A resource block bundle ^^_bundle − 1 consists of ^^_B ^s W^ize P_,init mod ^^ resource blocks if ^^_B ^s W^ize P_,init mod ^^ > 0 and ^^ resource blocks otherwise, all other resource block bundles consists of ^^ resource blocks. [0087] Resource block bundles are defined as for PDSCH transmissions scheduled with DCI format 1_0 in any common search space in bandwidth part ^^ with starting position ^^_B ^s W^tar P^t , _^^ , other than Type 0-PDCCH common search space in CORESET 0, the set of ^^_B ^s W^ize P_,init virtual resource blocks _{0,1, … , ^^_B ^s W^ize P_,init − 1_}, where ^^_B ^s W^ize P_,init is the size of CORESET 0 if CORESET 0 is configured for the cell and the size of initial downlink part if CORESET 0 is not configured for the cell, are divided into ^^_bundle virtual resource-block increasing order of the virtual resource-block number and virtual bundle number and the set of ^^_B ^s W^ize P_,init physical resource blocks _{ ^^_s ^C t_a ^O r_t ^RESET, ^^_s ^C t_a ^O r_t ^RESET + 1, … , ^^_s ^C t_a ^O r_t ^RESET + ^^_B ^s W^ize P_,init − 1_} are divided into ^^_bundle physical resource-block bundles in

bundle number, where ^^_bundle = ⌈( ^^_B ^s W^ize P_,init + ( ^^_B ^s W^tar P^t , _^^ + ^^_s ^C t_a ^O r_t ^RESET) mod ^^)^⁄ ^^ ⌉, ^^ = 2 is the bundle size, and ^^_s ^C t_a ^O r_t ^RESET

in the control resource set where the corresponding DCI was received. A resource block bundle 0 consists of ^^ − (( ^^_B ^s W^tar P^t , _^^ + ^^_s ^C t_a ^O r_t ^RESET) mod ^^) resource blocks, resource block bundle ^^_bundle − 1 consists of ( ^^_B ^s W^ize P_,init + ^^_B ^s W^tar P^t , _^^ + ^^_s ^C t_a ^O r_t ^RESET)

^^ resource blocks if ( ^^_B ^s W^ize P_,init + ^^_B ^s W^tar P^t , _^^ + ^^_s ^C t_a ^O r_t ^RESET) mod ^^ > 0 and ^^ resource blocks otherwise, all other resource block

[0088] Resource block bundles are defined as for all other PDSCH transmissions, the set of ^^_B ^s W^ize P_{, ^^} resource blocks in bandwidth part i with starting position ^^_B ^s W^tar P^t , _^^ are divided into ^^_bundle = ⌈( ^^_B ^s W^ize P_{, ^^} + ( ^^_B ^s W^tar P^t , _^^ mod ^^ _^^))⁄ ^^ _^^ ⌉ resource-block bundles in increasing order of the resource-block number

bundle size for bandwidth part i provided by the higher-layer parameter VRB-To-PRB-Interleaver for DCI formats 1_0 and 1_1 in a WTRU-specific search space, or VRB-To-PRB- Interleaver DCI-1-2 for DCI format 1_2, and resource block bundle 0 consists of ^^ _^^ − ( ^^_B ^s W^tar P^t , _^^ mod ^^ _^^) resource blocks, resource block bundle N_bundle – 1 consists of ( ^^_B ^s W^tar P^t , _^^ + ^^_B ^s W^ize P_{, ^^} )mod ^^ _^^ resource blocks if ( ^^_B ^s W^tar P^t , _^^ + ^^_B ^s W^ize P_{, ^^} )mod ^^ _^^> 0, and Li resource blocks

bundles consists of Li resource blocks. -16- 8687062.1 [0089] Virtual resource blocks in the interval ^^ ∈ {0,1, … , ^^_bundle − 1} are mapped to physical resource blocks according to virtual resource block bundle Nbundle – 1 that is mapped to physical resource block bundle N_bundle – 1. The virtual resource block bundle ^^ ∈ {0,1, … , ^^_bundle − 2} is mapped to physical resource block bundle ^^( ^^) where: ^^( ^^) = ^^ ^^ + ^^ ^^ = ^^ ^^ + ^^ ^^ = 0,1, … , ^^ − 1 ^^ = 0,1, … , ^^ − 1 ^^ = 2 ^^ = ⌊ ^^_bundle/ ^^⌋ [0090] The WTRU is not expected to be configured with ^^ _^^ = 2 simultaneously with a PRG size of 4. The WTRU may assume that the same precoding in the frequency domain is used within a physical resource block bundle. The WTRU may not make any assumption that the same precoding is used for different bundles of common resource blocks. [0091] In a first example, dynamic triggering of PDSCH VRB-to-SkipPRB mapping for high-power narrowband interferer coexistence may be used. A benefit of interleaved VRB-to-PRB mapping is frequency diversity. The nominal PDSCH interleaved VRB-to-PRB mapping is summarized below. [0092] Let N_bundle be the number of PRB bundles in a BWP, indexed as ^^ = 0,1, … , ^^_bundle − 1. VRB bundles ^^ ∈ {0,1, … , ^^_bundle − 1} are mapped to PRB bundles according to VRB bundle Nbundle – 1 that is mapped to PRB bundle Nbundle – 1. VRB bundle ^^ ∈ {0,1, … , ^^_bundle − 2} is mapped to PRB bundle ^^ = ^^( ^^) where: ^^( ^^) = ^^ ^^ + ^^ ^^ = ^^ ^^ + ^^ ^^ = 0,1, … , ^^ − 1 ^^ = 0,1, … , ^^ − 1 ^^ = 2 ^^ = ⌊ ^^_bundle/ ^^⌋ [0093] The nominal PDSCH interleaved VRB-to-PRB mapping (assuming N_bundle = 8 and bundle size L = 2) is illustrated in FIG. 2. FIG. 2 illustrates an example of a physical downlink shared channel (PDSCH) interleaved virtual resource block (VRB)-to-physical resource block (PRB) mapping. In this example, C = 4. For r = 0 and c = 0, j = 0 and f(j) = 0 For r = 1 and c = 0, j = 1 and f(j) = 4 For r = 0 and c = 1, j = 2 and f(j) = 1 For r = 1 and c = 1, j = 3 and f(j) = 5 For r = 0 and c = 2, j = 4 and f(j) = 2 For r = 1 and c = 2, j = 5 and f(j) = 6 For r = 0 and c = 3, j = 6 and f(j) = 3 -17- 8687062.1 For r = 1 and c = 3, j = 7 and f(j) = 7 [0094] An effective way to reduce interference with high-power narrowband interferer is for 5G to avoid using the frequency resources overlapping with the high-power narrowband interferer operating bandwidth when the high-power narrowband interferer is actively transmitting or listening for the return pulses. This is known as ‘PRB blanking’. Based on the high-power narrowband interferer rotation timing estimates and the power spectral density, the time-frequency interference region is evaluated and the 5G scheduler can avoid allocating the resource blocks for uplink or downlink traffic in the case of non-interleaved VRB-to-PRB mapping. On the other hand, the interleaved VRB-to-PRB mapping mechanism will need to be enhanced to exclude the PRB bundles that overlap with the high-power narrowband interferer bandwidth. [0095] An approach is for the network to cross out VRBs that may map to the blanked PRBs. In this case, the remaining available VRBs may become non-contiguous, especially for interleaved VRB-to-PRB mapping. As a result, the network needs to schedule the WTRU with non-contiguous frequency domain allocations. To this end, the network can apply resource allocation type 0 to facilitate interleaved VRB-to-PRB mapping with blanked PRBs. Alternatively, resource allocation type 1 may be modified, or a new resource allocation type can be introduced with a list of ‘Frequency domain resource assignment’ in the DCI to support multiple contiguous frequency domain resource assignments. However, both potential resource allocation mechanisms can significantly increase the DCI payload size relative to that of the resource allocation type 1. [0096] To minimize the impacts on the resource allocation complexity and DCI payload size, the interleaved VRB-to-PRB mapping scheme may be modified to step around the high-power narrowband interferer bandwidth during the time when the mapped PRB may fall into the high-power narrowband interferer bandwidth to facilitate PRB blanking, henceforth termed interleaved VRB-to-SkipPRB mapping. The interleaved VRB-to- SkipPRB mapping process is described below. [0097] Let N bundle be the number of ‘nominal’ PRB bundles. The nominal PRB bundles of a given BWP are indexed as ^^ = 0,1, … , ^^_bundle − 1. Let ^^_b ^e u^x n^c d^lu l_e ^ded be the number of excluded PRB bundles (e.g., the number of PRB bundles that overlap with the high-power narrowband interferer bandwidth), the number of included PRB bundles ^^′_bundle = ^^_bundle − ^^_b ^e u^x n^c d^lu l_e ^ded. Note that the excluded PRB bundles do not need to be ^{contiguous. The}

^{to the sequentially indexed PRB’ bundles ( ^^′ =} _{0,1, … , ^^′ bundle − 1). The mapping between the included nominal PRB bundle index and the PRB’ bundle} index is written as ^^ = ^^( ^^^′). [0098] Reduced VRB (to be symbolized as VRB’) bundles are defined as the subset of VRB bundles in the ^{interval ^^′ ∈ {0,1, … , ^^′ bundle − 1} . VRB’ bundles are mapped to the PRB’ bundles ^^′ ∈} _{{0,1, … , ^^′ bundle − 1} according to VRB’ bundle N’bundle – 1 that is mapped to the PRB’ bundle N’bundle – 1.} VRB’ bundle ^^′ ∈ {0,1, … , ^^^′ _bundle − 2} is mapped to PRB’ bundle ^^^′ = ^^′( ^^′), where: ^^^′( ^^′⁾ = ^^ ^^′ + ^^′

1 ^^′ = 0,1, … , ^^′ − 1 -18- 8687062.1 ^^ = 2 ^^′ = ^⌊ ^^^′ _bundle/ ^^^⌋ [0099] The transmitting nominal PRB bundle index ^^ = ^^⁽ ^^^′) = ^^⁽ ^^′( ^^′)⁾. [0100] The PDSCH interleaved VRB-to-SkipPRB mapping (assuming Nbundle = 8, ^^_b ^e u^x n^c d^lu l_e ^ded = 2, and bundle size L = 2) is illustrated in FIG.3. FIG.3 illustrates an example of a physical downlink shared channel (PDSCH) interleaved virtual resource block (VRB)-to-skip physical resource block (PRB)

that the PDSCH interleaved VRB-to-SkipPRB mapping preserves the contiguous VRB allocation property of allocation type 1. [0101] On the WTRU side, the WTRU may perform the interleaved VRB-to-SkipPRB mapping after receiving the contiguously scheduled VRB’s in the DCI (with resource allocation type 1). To this end, the network can use MAC-CE or group common signaling to inform the WTRU about the PRBs that may be excluded during VRB-to-PRB mapping, as exemplified by the PDSCH PRB Exclusion MAC CE command below, where R/F/LCID (1 byte) is avoid using the frequency resources overlapping with the high-power narrowband interferer operating bandwidth when the high defined a R is a Reserved bit, which is set to 0, F is a format field (1 bit), and LCID is Logical Channel ID (6 bits), where eLCID (1 or 2 bytes, 1 byte if LCID 33, 2 bytes if LCID = 34) is Extended Logic Channel ID, a unique eLCID value may be used to identify the PDSCH fractional interleaving command, and where L (1 or 2 bytes, 1 byte if F = 0, 2 bytes if F = 1) is the field length indicating the length of the corresponding MAC SDU or variable sized MAC-CE in bytes. [0102] A VRB-to-PRB Mapping Exclusion PRB Range field indicates the PRB range that may be excluded in the PDSCH VRB-to-PRB mapping process. The PRB range is specified using the resource indication value (RIV). The value of all 0s restores PDSCH interleaved VRB-to-PRB mapping to normal operation. In an example, multiple VRB-to-PRB Mapping Exclusion PRB Range fields can be included to accommodate non- contiguous exclusion PRB ranges. For example, a VRB-to-PRB Mapping Exclusion PRB Bundle Bitmap can be provided in the MAC CE to indicate the PRB bundles to be excluded in the PDSCH VRB-to-PRB mapping process (a bit of 1 indicates that the specific PRB bundles are excluded by the interleaver, and a bit of 0 indicates otherwise). [0103] Non-interleaved VRB-to-SkipPRB mapping is shown in FIG.4. FIG.4 illustrates an example of a physical downlink shared channel (PDSCH) non-interleaved virtual resource block (VRB)-to-skipPRB mapping. The benefit of adopting non-interleaved VRB-to-SkipPRB mapping is to facilitate the use of resource allocation type 1 to allocate resource across the PRB exclusion region, which enhances the scheduling multiplexing flexibility and hence spectral efficiency when PRB blanking is applied. To this end, the non-interleaved VRB- to-SkipPRB mapping may also be used to schedule around other types of pre-allocated high priority resources using resource allocation type 1 if the pre-allocated PRB locations can be included in the L1/L2 and/or higher layer control signaling. [0104] For illustration, a configuration of 16 PRBs available in the system (0..15) is considered, with 4 of them being impacted by Radar interference (8..11). For non-interleaved operation, VRB-to-PRB mapping is 1 to 1. If UE1 needs 6 PRBs for data transmission, the scheduler may allocate VRBs/PRBs (0..5) to UE1 and the remaining unscheduled VRBs/PRBs are (6,7) and (12,13,14,15). However, if UE2 also needs 6 PRBs for data -19- 8687062.1 transmission, the scheduler cannot allocate the remaining non-contiguous VRBs/PRBs to UE2 when using resource allocation type 1. Therefore, only UE1 can be scheduled in this time slot. UE2 will need to wait for the next time slot. As a result, PRB resources are not efficiently utilized. On the other hand, if we consider VRB-to- skipPRB mapping, as shown in FIG.4, the available VRB’s are (0..11). UE1 may be allocated VRB’s (0..5) and UE2 may be allocated VRB’s (6..11). After VRB-to-skipPRB mapping, UE1 will be transmitted on PRBs (0..5) and UE2 will be transmitted on PRBs (6,7) and (12,13,14,15). In this case, both UEs can be scheduled in the same time slot, thus improving the resource utilization efficiency. [0105] The network can use dedicated DCI signaling to dynamically indicate PDSCH VRB-to-SkipPRB mapping by introducing a new skip-PRB mapping flag (e.g., in DCI format 1_0, 1_1, and 1_2) to indicate whether the VRB-to-PRB mapping field is triggering the baseline VRB-to-PRB mapping algorithm or the VRB- to-SkipPRB mapping algorithm. When the skip-PRB mapping flag is absent or set to 0, the VRB-to-PRB mapping field (present only for resource allocation type 1) is interpreted the same way as baseline, as shown in Table 1. On the other hand, when the skip-PRB mapping flag is set to 1, VRB-to-PRB mapping = 0 indicating non-interleaved VRB-to-SkipPRB mapping and VRB-to-PRB mapping = 1 indicating interleaved VRB-to- SkipPRB mapping. Table 1: VRB-to-PRB mapping Bit field mapped to index VRB-to-PRB mapping 0 Non-interleaved 1 Interleaved [0106] On the WTRU side, upon receiving the PDSCH VRB-to-SkipPRB mapping indication in the DCI, a WTRU may perform the VRB-to-SkipPRB mapping. FIG.5 shows a flow chart of an exemplary method 500 of PRB-to-SkipPRB mapping for a data reception. The method 500 can be implemented using a WTRU. It will be appreciated that while the method 500 is described as a series of acts or events, the method 500 is not limited by the ordering of such acts or events. Some acts can occur in different orders and/or concurrently with other acts or events apart from those described herein. Further, the method 500 can include other acts or events that have not been depicted for simplicity, while other illustrated acts or events can be removed or modified. [0107] At block 502, the method 500 involves determining the PRB bundles used or included for transmitting data within an active BWP. The included PRB bundles may be determined based on bundles unused or excluded from the data transmission. In some examples, the included PRB bundles may be determined based on the VRB-to-PRB Mapping Exclusion PRB Range or VRB-to-PRB Mapping Exclusion PRB Bundle Bitmap information received in the latest MAC CE. The included PRB bundles within the active BWP may further be determined by blacklisting the excluded PRB bundles within the active BWP. At block 504, the method 500 involves defining the mapping of the included PRB bundles to a set of sequentially indexed or contiguous PRB’ bundles. The included PRB bundles may be mapped to the set of the PRB’ bundles according to a non- interleaved mapping scheme. At block 506, the method 500 involves determining a reduced set or subset of -20- 8687062.1 VRB’ bundles (i.e., sequentially indexed or contiguous VRB’ bundles). The reduced set of the VRB’ bundles may be determined based on the number of included PRB bundles of the set of PRB bundles. For example, the number of VRB’ bundles may be equal to the number of included PRB bundles. [0108] At block 508, the method 500 involves mapping the scheduled reduced set of the VRB’ bundles to the set of PRB’ bundles after receiving the information of scheduled contiguous VRB’s (with resource allocation type 1) in the DCI for a data channel (e.g., PDSCH) reception within an active BWP. For example, the WTRU may perform interleaved or non-interleaved VRB’-to-PRB’ bundle mapping, as per the setting of the VRB-to- SkipPRB mapping in the DCI. At block 510, the method 500 involves mapping the PRB’ bundles to the included PRB bundles for data reception. For example, a WTRU may perform PRB’-to-PRB bundle mapping to locate the scheduled PRBs for a received PDSCH signal. The WTRU may inform the network of its capability to support PDSCH VRB-to-SkipPRB Mapping, as exemplified by the following information message. Definitions for parameters Per M FDD-TDD DIFF FR1- FR2 DIFF pdschVrbToSkipPrbMapping Indicates whether the WTRU WTRU No No No supports PDSCH VRB-to-SkipPRB mapping. [0109] In an embodiment, dynamic triggering of PDSCH VRB-to-SkipPRB mapping for high-power narrowband interferers coexistence occurs. An external node to the network can determine the interferer characteristics such as carrier frequency, bandwidth, periodicity, dwell time, AoA, and PSD. These measurements can also be determined within the wireless network by observing the measurements relevant to both WTRUs and the gNBs. The network determines the excluded PRB bundles within the active BWP based on the detected high-power narrowband interferers bandwidth. The network determines the set of WTRUs that incur significant interference from the high-power narrowband interferers. The network uses MAC- CE or group common signaling to inform the WTRUs about the PRBs to be excluded from PDSCH (e.g., via one or more VRB-to-PRB Mapping Exclusion PRB Range fields or a VRB-to-PRB Mapping Exclusion PRB Bundle Bitmap) if interleaved or non-interleaved VRB-to-SkipPRB mapping is to be applied. The network uses dedicated DCI signaling to dynamically trigger PDSCH interleaved or non-interleaved VRB-to-SkipPRB mapping. [0110] The network may perform interleaved or non-interleaved VRB-to-SkipPRB mapping for PDSCH transmission. FIG.6 shows a flow chart of an exemplary method 600 for VRB-to-SkipPRB mapping for a data transmission (e.g., a PDSCH transmission). The method 600 can be implemented at a base station or node. In some examples, the method 600 may be implemented by a WTRU for a data transmission. It will be appreciated that while the method 600 is described as a series of acts or events, the method 600 is not limited by the ordering of such acts or events. Some acts can occur in different orders and/or concurrently with other acts or events apart from those described herein. Further, the method 600 can include other acts or events that have not been depicted for simplicity, while other illustrated acts or events can be removed or modified. -21- 8687062.1 [0111] At block 602, the method involves determining the PRB bundles to be included or used to transmit data for a data channel transmission within an active BWP. The PRB bundles to be included for the data transmission may be determined by excluding PRB bundles that are not to be used for the data transmission. The excluded PRB bundles may correspond with one or more interfering signals (e.g., a RADAR signal) that overlap with the data channel transmission. The included PRB bundles may be non-contiguous. At block 604, the method 600 involves defining the mapping of the included PRB bundles to a set of sequentially indexed or contiguous PRB’ bundles. The included PRB bundles may be mapped to the set of PRB’ bundles according to a non-interleaved mapping scheme. At block 606, the method 600 involves determining a reduced set or subset of VRB’ bundles (i.e., a set of sequentially indexed or contiguous VRB’ bundles). The reduced set of VRB’ bundles may be determined based on the number of included PRB bundles. For example, the number of VRB’ bundles of the reduced set of the VRB’ bundles may be equal to the number of included PRB bundles. [0112] At block 608, the method 600 involves mapping the scheduled reduced set of VRB’ bundles to the set of PRB’ bundles after making the decision to schedule contiguous VRB’s (with resource allocation type 1) in the DCI. For example, a network may perform interleaved or non-interleaved VRB’-to-PRB’ bundle mapping, as indicated to a receiving device (e.g., a WTRU) in download control information (DCI). In one embodiment, the number of VRB’ bundles ( ^^′_bundle) can be determined by rounding up the ratio of (number of scheduled VRB’s) to (VRB’ bundle size). The number of scheduled VRB’s in each VRB’ bundle is equal to the VRB’ bundle size for VRB’ bundle 0.. ^^′_bundle-2. The number of scheduled VRB’s in VRB’ bundle ^^′_bundle-1 is equal to the VRB’ bundle size if mod(number of scheduled VRB’s, VRB’ bundle size) = 0. Otherwise, the number of scheduled VRB’s in VRB’ bundle ^^′_bundle-1 is equal to mod(number of scheduled VRB’s, VRB’ bundle size). The number of scheduled PRB’s in each PRB’ bundle is the same as the number of scheduled VRB’s in the corresponding VRB’ bundle that maps to the PRB’ bundle. At block 610, the method 600 may involve mapping the PRB’ bundles to the included PRB bundles for a data transmission. The PRB’ bundles may be sequentially indexed or contiguous and the included PRB bundles may be non-contiguous. For example, the network may perform PRB’-to-nominal (included) PRB bundle mapping for PDSCH transmission. The number of scheduled PRBs in each PRB bundle is the same as the number of scheduled PRB’s in the corresponding PRB’ bundle that maps to the PRB bundle. The WTRU receives PDSCH data from the scheduled PRBs within the mapped PRB bundles. [0113] Upon the reception of the DCI signaling to indicate PDSCH interleaved or non-interleaved VRB-to- SkipPRB mapping, a WTRU may perform VRB-to-SkipPRB mapping. FIG. 7 shows a flow chart of an exemplary method 700 for VRB-to-SkipPRB mapping for a data reception (e.g., of a PDSCH transmission). The method 700 can be implemented by a WTRU. It will be appreciated that while the method 700 is described as a series of acts or events, the method 700 may not limited by the ordering of such acts or events. Some acts can occur in different orders and/or concurrently with other acts or events apart from those described herein. Further, the method 700 can include other acts or events that have not been depicted for simplicity, while other illustrated acts or events can be removed or modified. -22- 8687062.1 [0114] At block 702, the method 700 involves determining PRB bundles that are excluded from use or not used for a data transmission. For example, a WTRU may retrieve the latest information about one or more VRB-to-PRB Mapping Exclusion PRB Range fields or the VRB-to-PRB Mapping Exclusion PRB Bundle Bitmap to determine the excluded or unused PRB bundles. At block 704, the method 700 involves determining the PRB bundles used or included for the data transmission. For example, the WTRU may determine the included PRB bundles within the active BWP by blacklisting the excluded PRB bundles within the active BWP. [0115] At block 706, the method 700 involves defining the mapping of the included PRB bundles to a set of sequentially indexed or contiguous PRB’ bundles. The included PRB bundles may be mapped to the set of the PRB’ bundles according to a non-interleaved mapping scheme. At block 708, the method 700 involves determining a reduced set or subset of VRB’ bundles (i.e., sequentially indexed or contiguous VRB’ bundles). The reduced set of the VRB’ bundles may be determined based on the number of included PRB bundles. For example, the number of the VRB’ bundles of the reduced set of the VRB’ bundles may be equal to the number of included PRB bundles. [0116] At block 710, the method 700 involves mapping the scheduled reduced set of the VRB’ bundles to the set of the PRB’ bundles after receiving the information of scheduled contiguous VRB’s (with resource allocation type 1) in the DCI, indicating the use of VRB-to-SkipPRB mapping. The WTRU may perform interleaved or non-interleaved VRB’-to-PRB’ bundle mapping, as per the setting of the VRB-to-SkipPRB mapping in the DCI. In one embodiment, the number of VRB’ bundles ( ^^′_bundle) can be determined by rounding up the ratio of (number of scheduled VRB’s) to (VRB’ bundle size). The number of scheduled VRB’s in each VRB’ bundle is equal to the VRB’ bundle size for VRB’ bundle 0.. ^^′_bundle-2. The number of scheduled VRB’s in VRB’ bundle ^^′_bundle-1 is equal to the VRB’ bundle size if mod(number of scheduled VRB’s, VRB’ bundle size) = 0. Otherwise, the number of scheduled VRB’s in VRB’ bundle ^^′_bundle-1 is equal to mod(number of scheduled VRB’s, VRB’ bundle size). The number of scheduled PRB’s in each PRB’ bundle is the same as the number of scheduled VRB’s in the corresponding VRB’ bundle that maps to the PRB’ bundle. At block 712, the method 700 involves mapping the PRB’ bundles to the included PRB bundles for data reception. The PRB’ bundles may be sequentially indexed or contiguous and the included PRB bundles may be non-contiguous. The PRB’ bundles may be mapped to the PRB bundles based on a mapping function. The number of scheduled PRBs in each PRB bundle is the same as the number of scheduled PRB’s in the corresponding PRB’ bundle that maps to the PRB bundle. The WTRU receives PDSCH data from the scheduled PRBs within the mapped PRB bundles. [0117] Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, -23- 8687062.1 semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto- optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer. -24- 8687062.1

Claims

CLAIMS What is Claimed: 1. A method implemented by a wireless transmit/receive unit (WTRU), the method comprising: receiving a downlink control transmission, wherein the downlink control transmission includes resource allocation information for a data transmission; mapping the resource allocation information of the data transmission to a set of virtual resource block bundles; mapping a set of virtual resource block bundles to a first set of physical resource block bundles based on a first mapping function, wherein the first set of the physical resource block bundles are contiguous; mapping the first set of the physical resource block bundles to first physical resource block bundles of a second set of physical resource block bundles based on a second mapping function, wherein the second set of the physical resource block bundles includes the first physical resource block bundles and second physical resource block bundles, wherein the first physical resource block bundles are available for data transmission, wherein the second physical resource block bundles are unavailable for data transmission, and wherein the first physical resource block bundles are non-contiguous; and using allocated resources mapped in the first physical resource block bundles for data reception.

2. The method of claim 1, wherein the virtual resource block bundles of the set of the virtual resource block bundles are contiguous or sequentially indexed.

3. The method of claim 1, further comprising determining the first physical resource block bundles or the second physical resource block bundles of the second set of the physical resource block bundles based on a bitmap or a range value received from a network.

4. The method of claims 1 or 3, wherein the second physical resource block bundles overlap with at least one signal interfering with the data transmission, and wherein each of the second physical resource block bundles is not used to transmit data for the data transmission.

5. The method of claim 1 or 3, further comprising determining the first physical resource block bundles used for the data transmission based on a determination of the second physical resource block bundles.

6. The method of claim 1, further comprising determining a number of the virtual resource block bundles based on a number of the first physical resource block bundles.

7. The method of claim 1, further comprising determining at least one of the first mapping function or the second mapping function, wherein at least one of the first mapping function or the second mapping function comprises a one-to-one mapping function.

8. The method of claim 1 or 7, wherein the first mapping function comprises an interleaving mapping function or a non-interleaving mapping function. -25- 8687062.1

9. The method of claims 1 or 2, wherein the first physical resource block bundles include a first physical resource block bundle and a second physical resource block bundle, and wherein the first physical resource block bundle and the second physical resource block bundle are non-contiguous.

10. The method of claim 1, wherein each of the first physical resource block bundles includes a plurality of resource blocks, and wherein the data transmission comprises a physical downlink shared channel (PDSCH) transmission within an active bandwidth part.

11. The method of claim 1, wherein the downlink control transmission includes downlink control information, and wherein the downlink control information indicates whether a blanking technique is used during mapping for the data transmission.

12. The method of claim 1, wherein the downlink control transmission includes downlink control information, and wherein the downlink control information indicates whether an interleaving or non- interleaving mapping scheme is used for the data transmission.

13. The method of claim 3, wherein the bitmap or a range value received from the network identifies the second physical resource block bundles that are unused to transmit data for the data transmission.

14. A method for wireless communications comprising: mapping a set of virtual resource block bundles to a first set of physical resource block bundles based on a first mapping function, wherein the first set of the physical resource block bundles are contiguous; mapping the first set of the physical resource block bundles to the first physical resource block bundles of a second set of physical resource block bundles based on a second mapping function, wherein the second set of the physical resource block bundles includes the first physical resource block bundles and second physical resource block bundles, wherein the first physical resource block bundles are available for data transmission, wherein the second physical resource block bundles are unavailable for data transmission, and wherein the first physical resource block bundles are non-contiguous; and using the first physical resource block bundles for a data transmission.

15. The method of claim 14, further comprising determining a number of the virtual resource block bundles based on a number of the first physical resource block bundles, wherein the set of the virtual resource block bundles are contiguous or sequentially indexed.

16. The method of claims 14 or 15, wherein the second physical resource block bundles correspond to an interfering signal, and wherein the each of the second physical resource block bundles is not used for transmitting data for the data transmission.

17. The method of claim 14, further comprising determining the first physical resource block bundles used for data transmission based on the second physical resource block bundles.

18. The method of claim 14, further comprising defining at least one of the first mapping function or the second mapping function, wherein at least one of the first mapping function or the second mapping function comprises a one-to-one mapping function. -26- 8687062.1

19. The method of claim 14 or 18, wherein the first mapping function comprises an interleaving mapping function or a non-interleaving mapping function.

20. The method of claim 14, wherein the method is implemented by a wireless transmit/receive unit (WTRU) or a base station, wherein each of the physical resource block bundles includes a plurality of resource blocks, and wherein the data transmission comprises a physical downlink shared channel (PDSCH) transmission within an active bandwidth part.

21. A wireless transmit/receive unit (WTRU) comprising: a transceiver; and a processor configured to: receive a downlink control transmission, wherein the downlink control transmission includes resource allocation information for a data transmission; map the resource allocation information of the data transmission to a set of virtual resource block bundles; map a set of virtual resource block bundles to a first set of physical resource block bundles based on a first mapping function, wherein the first set of the physical resource block bundles are contiguous; map the first set of the physical resource block bundles to first physical resource block bundles of a second set of physical resource block bundles based on a second mapping function, wherein the second set of the physical resource block bundles includes the first physical resource block bundles and second physical resource block bundles, wherein the first physical resource block bundles are available for data transmission, wherein the second physical resource block bundles are unavailable for data transmission, and wherein the first physical resource block bundles are non-contiguous; and using allocated resources mapped in the first physical resource block bundles for data reception.

22. The WTRU of claim 21, wherein the virtual resource block bundles of the set of the virtual resource block bundles are contiguous or sequentially indexed.

23. The WTRU of claim 21, wherein the processor is further configured to determine the first physical resource block bundles or the second physical resource block bundles of the second set of the physical resource block bundles based on a bitmap or a range value received from a network.

24. The WTRU of claim 21, wherein the second physical resource block bundles overlap with at least one signal interfering with the data transmission, and wherein each of the second physical resource block bundles is not used to transmit data for the data transmission.

25. The WTRU of claim 21, further comprising determining the first physical resource block bundles used for the data transmission based on a determination of the second physical resource block bundles.

26. A wireless transmit/receive unit (WTRU) comprising: a transceiver; and a processor configured to: -27- 8687062.1 mapping a set of virtual resource block bundles to a first set of physical resource block bundles based on a first mapping function, wherein the first set of the physical resource block bundles are contiguous; mapping the first set of the physical resource block bundles to the first physical resource block bundles of a second set of physical resource block bundles based on a second mapping function, wherein the second set of the physical resource block bundles includes the first physical resource block bundles and second physical resource block bundles, wherein the first physical resource block bundles are available for data transmission, wherein the second physical resource block bundles are unavailable for data transmission, and wherein the first physical resource block bundles are non-contiguous; and using the first physical resource block bundles for a data transmission. -28- 8687062.1