Enhanced PDSCH VRB-to-VRB mapping for coexistence of high-power narrowband interference sources

Abstract

A method implemented by a Wireless Transmit / Receive Unit (WTRU) is disclosed. The method may include mapping resource allocation information for data transmission to a set of virtual resource block bundles. The method may further include mapping the set of virtual resource block bundles to a set of first physical resource block bundles based on a first mapping function. Additionally, the method may include mapping the set of first physical resource block bundles to a set of second physical resource block bundles. The second physical resource block bundle set may include both the first and second physical resource block bundles. The first physical resource block bundles may be usable for data transmission, while the second physical resource block bundles may not be usable for data transmission.

Description

[0001] Cross-reference to related applications This application claims the benefit of U.S. Provisional Application No. 63 / 540,842, filed September 27, 2023, the contents of which are incorporated herein by reference. Background Technology

[0002] Physical Downlink Shared Channel (PDSCH) resource allocation type 0 is a bitmap-based allocation scheme. The most flexible way to indicate the set of resource blocks a device should receive for downlink transmission is to include a bitmap in the Bandwidth Part (BWP) equal in size to the number of resource blocks. This allows for scheduling any combination of resource blocks for transmission to the device, but can result in very large bitmaps in high-bandwidth scenarios. To reduce the bitmap size while maintaining sufficient allocation flexibility, resource allocation type 0 does not point to individual resource blocks (RBs), but rather to groups of consecutive RBs. The size of such a group of resource blocks (RBG) is determined by the size of the BWP. For each size of the BWP, there may be two different configurations, resulting in different RBG sizes for a given BWP size.

[0003] On the other hand, resource allocation type 1 does not rely on a bitmap. Instead, it encodes resource allocation as the start position and length of the RB allocation. As a result, resource allocation type 1 only supports allocations with consecutive frequencies, thereby reducing the number of bits required to signal 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 VRBs are directly mapped to their corresponding PRBs. For resource allocation type 1, both interleaved and non-interleaved mappings are supported. The VRB-to-PRB mapping bit in the DCI (if present only in the downlink) indicates whether allocation signaling uses interleaved or non-interleaved mapping. In the uplink, non-interleaved mapping is always used. Summary of the Invention

[0005] This disclosure relates to techniques for ensuring robust and efficient interleaved or non-interleaved virtual resource block (VRB) to physical resource block (PRB) mapping of the Physical Downlink Shared Channel (PDSCH), while mitigating interference to and from high-power narrowband interference sources through dynamic triggering of PDSCH VRB to SkipPRB mapping for the coexistence of high-power narrowband interference sources.

[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 data transmission. The method may further include mapping the received resource allocation information for data transmission to a set of virtual resource block bundles. Furthermore, the 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 physical resource block bundles may be contiguous. Additionally, the method may include mapping the first set of physical resource block bundles to a first set of second physical resource block bundles. The second set of physical resource block bundles may include both the first and second physical resource block bundles. The first physical resource block bundle may be available for data transmission, while the second physical resource block bundle may not be available for data transmission. The first physical resource block bundle may be discontinuous. Furthermore, the method may include using corresponding allocated resources from the first physical resource block bundle for data reception.

[0007] In another aspect, a method for wireless communication is disclosed. This method may include mapping a set of virtual resource block bundles to a set of first physical resource block bundles based on a first mapping function. The first set of physical resource block bundles may be contiguous. The method may further include mapping the first set of physical resource block bundles to a first set of second physical resource block bundles. The second set of physical resource block bundles may include both the first and second physical resource block bundles. The first set of physical resource block bundles may be available for data transmission, while the second set may not be available for data transmission. The first set of physical resource block bundles may be discontinuous. Furthermore, the method may include using the first set of physical resource block bundles for data transmission. Attached Figure Description

[0008] A more detailed understanding can be obtained from the following description given by way of example in conjunction with the accompanying drawings, wherein similar reference numerals in the drawings indicate similar elements, and in which: Figure 1A This is a system diagram illustrating an example communication system in which one or more of the disclosed embodiments may be implemented; Figure 1B The illustration shows a method according to one embodiment. Figure 1A The illustrated system diagram shows an example wireless transmit / receive unit (WTRU) used in a communication system. Figure 1C The illustration shows a method according to one embodiment. Figure 1AThe illustrated system diagram shows an example radio access network (RAN) and an example core network (CN) used in the communication system. Figure 1D The illustration shows a method according to one embodiment. Figure 1A The illustrated system diagram shows yet another example RAN and yet another example CN used in the communication system; Figure 2 The illustration shows an example of the mapping from Virtual Resource Block (VRB) to Physical Resource Block (PRB) in Physical Downlink Shared Channel (PDSCH); Figure 3 The illustration shows an example of the mapping from Physical Downlink Shared Channel (PDSCH) interleaved Virtual Resource Block (VRB) to Skip PRB (Skip Physical Resource Block (PRB)); Figure 4 The illustration shows an example of mapping from a Physical Downlink Shared Channel (PDSCH) non-interleaved Virtual Resource Block (VRB) to a Skipped Physical Resource Block (PRB). Figure 5 This is a flowchart of a method for mapping PRB to SkipPRB for data reception, based on an example implementation scheme; Figure 6 This is a flowchart of a method for VRB-to-SkipPRB mapping for data transmission, based on another example implementation scheme; and Figure 7 This is a flowchart of a method for VRB-to-SkipPRB mapping for data reception, based on another example implementation scheme. Detailed Implementation

[0009] Recent trends are driving researchers to create solutions for cellular network deployments in the presence of high-power narrowband interference sources, such as radio detection and ranging (RADAR). While the baseline capabilities offered by 5G can be used to provide some degree of coexistence with high-power narrowband interference sources, enhancements may be needed to realize the full potential of 5G.

[0010] When high-power narrowband interference sources such as RADAR operate in a frequency band overlapping with resource blocks (RBs) transmitted to the WTRU via interleaved Physical Downlink Shared Channel (PDSCH), the WTRU may be unable to reliably receive data radio bearers (DRBs) and signaling radio bearers (SRBs) on the downlink. Furthermore, the possibility of interleaved PDSCH transmissions interfering with high-power narrowband interference source systems is also problematic. Therefore, new mechanisms and technologies are needed to ensure robust and efficient PDSCH transmission and reception when coexisting with high-power narrowband interference sources.

[0011] This disclosure relates to a technique for ensuring robust and efficient PDSCH interleaved or non-interleaved virtual resource block (VRB) to physical resource block (PRB) mapping, while mitigating interference to and from high-power narrowband interference sources through dynamic triggering of PDSCH VRB to SkipPRB mapping for the coexistence of high-power narrowband interference sources.

[0012] Figure 1A This is a schematic diagram illustrating an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multi-access system that provides content such as voice, data, video, messages, and broadcasts to multiple wireless users. The communication system 100 enables multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 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 Spectrum OFDM (ZT-UW-DFT-S-OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), and so on.

[0013] like Figure 1AAs shown, the communication 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 switched telephone network (PSTN) 108, the Internet 110, and other networks 112. However, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d can be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d (any of which can be referred to as a station (STA)) can be configured to transmit and / or receive wireless signals and can include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of WTRUs 102a, 102b, 102c, and 102d can be interchangeably referred to as a UE.

[0014] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106, the Internet 110, and / or other networks 112. For example, base stations 114a and 114b may be base transceiver stations (BTS), NodeBs, eNodeBs (eNBs), home node Bs, home eNodeBs, next-generation NodeBs (such as gNodeBs (gNBs)), new radio (NR) NodeBs, site controllers, access points (APs), wireless routers, and so on. Although base stations 114a and 114b are each depicted as a single element, it should be understood that base stations 114a and 114b may include any number of interconnected base station and / or network elements.

[0015] Base station 114a may be part of RAN 104, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In one embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

[0016] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via air interface 116. Air interface 116 can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 116.

[0017] More specifically, as described above, the communication system 100 can be a multi-access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations 114a and WTRUs 102a, 102b, and 102c in RAN 104 can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can establish an 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).

[0018] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement radio technologies such as evolved UMTS terrestrial radio access (E-UTRA), which may use Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro) to establish air interface 116.

[0019] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR wireless access, which can use NR to establish air interface 116.

[0020] In one embodiment, base station 114a and WTRUs 102a, 102b, and 102c can implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can jointly implement LTE radio access and NR radio access, for example, using the dual connectivity (DC) principle. Therefore, the air interface used by WTRUs 102a, 102b, and 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0021] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0022] For example, Figure 1ABase station 114b can be a wireless router, home node B, home eNodeB, or access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area, such as commercial locations, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for drone use), roads, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114b can be directly connected to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106.

[0023] RAN 104 can communicate with CN 106, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, and 102d. Data can have different Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, and / or perform advanced security functions such as user authentication. Although in Figure 1A As not shown, but it should be understood that RAN 104 and / or CN 106 can communicate directly or indirectly with other RANs that use the same RAT as RAN 104 or a different RAT. For example, in addition to connecting to RAN 104, which may utilize NR radio technology, CN 106 can also communicate with another RAN (not shown) that uses GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0024] CN 106 can also serve as a gateway for WTRUs 102a, 102b, 102c, and 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN 104 or a different RAT.

[0025] Some or all of the WTRUs 102a, 102b, 102c, and 102d in the communication system 100 may include multi-mode capabilities (e.g., WTRUs 102a, 102b, 102c, and 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). For example... Figure 1A The WTRU 102c shown can be configured to communicate with base station 114a, which may employ cellular-based radio technology, and to communicate with base station 114b, which may employ IEEE 802 radio technology.

[0026] Figure 1B This is a system diagram illustrating example WTRU 102. (Example:) Figure 1B As shown, among other things, WTRU 102 may include, in particular, 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 supply 134, a global positioning system (GPS) chipset 136, and / or other peripheral devices 138, etc. It should be understood that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments.

[0027] Processor 118 can be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), any other type of integrated circuit (IC), a state machine, etc. Processor 118 can perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 can be coupled to transceiver 120, which can be coupled to transmitting / receiving element 122. Although Figure 1B The processor 118 and transceiver 120 are depicted as separate components, but it should be understood that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

[0028] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) over air interface 116. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In one embodiment, transmitting / receiving element 122 can be, for example, a transmitter / detector configured to transmit and / or receive IR, UV, or visible light signals. In yet another embodiment, transmitting / receiving element 122 can be configured to transmit and / or receive both RF and optical signals. It should be understood that transmitting / receiving element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0029] Although the transmitting / receiving element 122 is in Figure 1B While depicted as a single element, WTRU 102 may include any number of transmit / receive elements 122. More specifically, WTRU 102 may employ MIMO technology. Thus, in one embodiment, WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals on air interface 116.

[0030] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multi-mode capability. Therefore, for example, transceiver 120 may include multiple transceivers to enable WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0031] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit) and can receive user input data therefrom. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad 128. Furthermore, the processor 118 can access and store information from any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. 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. Removable memory 132 may include a user identification module (SIM) card, memory stick, secure digital storage (SD) card, etc. In other embodiments, the processor 118 can access and store information from memory that is not physically located on WTRU 102 (e.g., a server or home computer (not shown)).

[0032] The processor 118 can receive power from the power supply 134 and can be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 can be any suitable device that powers the WTRU 102. For example, the power supply 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, etc.

[0033] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to, or instead of, information from the GPS chipset 136, the WTRU 102 may receive location information on the air interface 116 from base stations (e.g., base stations 114a, 114b) and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that the WTRU 102 may acquire location information using any suitable location determination method while remaining consistent with the embodiments.

[0034] The processor 118 may be further coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or videos), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors. These sensors may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, attitude sensors, biosensors, humidity sensors, etc.

[0035] WTRU 102 may include a full-duplex radio for which the transmission and reception of some or all signals (e.g., signals associated with specific subframes for UL (e.g., for transmission) and downlink (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 hardware (e.g., chokes) or via signal processing by a processor (e.g., a separate processor (not shown) or via processor 118). In one embodiment, WTRU 102 may include a half-duplex radio for which the transmission and reception of some or all signals (e.g., signals associated with specific subframes for UL (e.g., for transmission) or DL ​​(e.g., for reception)) may be concurrent and / or simultaneous.

[0036] Figure 1C This diagram illustrates a system diagram of RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with CN 106.

[0037] RAN 104 may include eNode-Bs 160a, 160b, and 160c; however, it should be understood that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. eNode-Bs 160a, 160b, and 160c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c on air interface 116. In one embodiment, eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Therefore, for example, eNode-B 160a may use multiple antennas to transmit and / or receive radio signals from WTRU 102a.

[0038] Each of the eNode-B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, etc. Figure 1C As shown, eNode-B 160a, 160b, and 160c can communicate with each other on the X2 interface.

[0039] Figure 1C The CN 106 shown 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 described as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0040] The MME 162 can connect to each of the eNode-Bs 162a, 162b, and 162c in RAN 104 via the S1 interface and can act as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0041] The SGW 164 can connect to each of the eNode Bs 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 can typically route and forward user data packets to / from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions, such as anchoring the user plane during inter-eNode B handover, triggering paging when DL data is available for WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0042] SGW 164 can connect to PGW 166, which can provide WTRU 102a, 102b, 102c with access to packet-switched networks such as Internet 110, so as to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0043] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRU 102a, 102b, and 102c with access to a circuit-switched network such as PSTN 108, facilitating communication between WTRU 102a, 102b, and 102c and traditional landline communication equipment. For example, CN 106 may include, or be able to communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 106 and PSTN 108. Furthermore, CN 106 can provide WTRU 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0044] Despite WTRU in Figure 1A-1D While described as a wireless terminal, it is conceivable that, in some representative embodiments, such a terminal may use (e.g., temporarily or permanently) a wired communication interface with a communication network.

[0045] In a representative embodiment, another network 112 may be a WLAN.

[0046] A WLAN in Infrastructure Basic Services Set (BSS) mode can have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can access or interface with a distributed system (DS) or another type of wired / wireless network that transmits traffic to and / or out of the BSS. Traffic originating outside the BSS destined for a STA can reach and be delivered to the STA via the AP. Traffic originating from a STA destined for an external BSS can be sent to the AP for delivery to the appropriate destination. For example, traffic between STAs within the BSS can be transmitted via the AP, where the source STA can send traffic to the AP, and the AP can deliver traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic can be transmitted between source and destination STAs (e.g., directly between them) using Direct Link Establishment (DLS). In some representative embodiments, the DLS can use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using the Standalone BSS (IBSS) mode may not have an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode is sometimes referred to here as an "ad-hoc" communication mode.

[0047] When using 802.11ac infrastructure operating mode or a similar operating mode, the AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of a fixed width (e.g., a wide bandwidth of 20 MHz) or a dynamically configured width. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, such as in an 802.11 system, Carrier Sense Multiple Access (CSMA / CA) with collision avoidance can be implemented. For CSMA / CA, each STA, including the AP, can sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, that particular STA can back off. A single STA (e.g., only one station) can transmit at any given time within a given BSS.

[0048] High-throughput (HT) STAs can communicate using a 40 MHz wide channel, for example, by combining a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels.

[0049] Very High Throughput (VHT) STAs can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. 40 MHz and / or 80 MHz channels can be formed by combining consecutive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels, or by combining two non-consecutive 80 MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data passes through a segment resolver, which splits the data into two streams. Each stream can be processed separately using Inverse Fast Fourier Transform (IFFT) and time-domain processing. These streams can be mapped onto two 80 MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the operation of the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC).

[0050] 802.11af and 802.11ah support operating modes below 1 GHz. The channel operating bandwidth and carrier in 802.11af and 802.11ah are reduced compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV whitespace (TVWS) spectrum, while 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 metering-type control / machine-type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only) certain and / or limited bandwidths. MTC devices may include batteries with a battery life exceeding a threshold (e.g., to maintain a very long battery life).

[0051] WLAN systems that can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include channels that can be designated as the primary channel. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STA among all STAs operating in the BSS that supports the minimum bandwidth operating mode. In the example of 802.11ah, for STAs that support (e.g., only support) the 1 MHz mode (e.g., MTC type devices), the primary channel can be 1 MHz wide, 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 Sense and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, because an STA (which only supports the 1 MHz operating mode) is transmitting to the AP, all available bands can be considered busy, even if most available bands remain idle.

[0052] In the United States, the available frequency band for 802.11ah is from 902 MHz to 928 MHz. In South Korea, the available frequency band is from 917.5 MHz to 923.5 MHz. In Japan, the available frequency band is from 916.5 MHz to 927.5 MHz. The total available bandwidth for 802.11ah is 6 MHz to 26 MHz, depending on the country code.

[0053] Figure 1D This diagram illustrates a system diagram of RAN 104 and CN 106 according to one embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using NR radio technology. RAN 104 can also communicate with CN 106.

[0054] RAN 104 may include gNBs 180a, 180b, and 180c; however, it should be understood that RAN 104 may include any number of gNBs while remaining consistent with the embodiments. gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c on air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c. Therefore, for example, gNB 180a may use multiple antennas to transmit and / or receive radio signals from WTRU 102a. In one embodiment, gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers (not shown) to WTRU 102a. A subset of these component carriers can be on unlicensed spectrum, while the remaining component carriers can be on licensed spectrum. In one embodiment, gNBs 180a, 180b, and 180c can implement Coordinated Multipoint (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0055] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with scalable digitization. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing can differ for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing a variable number of OFDM symbols and / or a continuously variable absolute time).

[0056] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without accessing other RANs (e.g., eNode-Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can utilize one or more of gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect with gNBs 180a, 180b, and 180c, while also communicating / connecting with another RAN such as eNode-Bs 160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c, as well as one or more eNode-Bs 160a, 160b, and 160c. In a non-standalone configuration, eNode-Bs 160a, 160b, and 160c can act as mobility anchors for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, and 102c.

[0057] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slicing support, interoperability between DC, NR, and E-UTRA, routing user plane data to User Plane Functions (UPF) 184a and 184b, and routing control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other on the Xn interface.

[0058] Figure 1DThe CN 106 shown 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. Although the foregoing elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0059] AMF 182a and 182b can connect to one or more gNBs 180a, 180b, and 180c in RAN 104 via the N2 interface and can act as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different Protocol Data Unit (PDU) sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating Non-Access Stratum (NAS) signaling, mobility management, and so on. AMF 182a and 182b can use network slicing to customize CN support for WTRU 102a, 102b, and 102c based on the service type used by WTRU 102a, 102b, and 102c. For example, different network slices can be created for different use cases, such as services relying on Ultra Reliable Low Latency Time (URLLC) access, services relying on Enhanced Massive Mobile Broadband (eMBB) access, services for MTC access, and so on. AMF 182a and 182b can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as LTE, LTE-A, LTE-A Pro and / or non-3GPP access technologies such as WiFi.

[0060] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 106 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 106 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure the routing of services through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, etc. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

[0061] UPF 184a and 184b can be connected to one or more gNBs 180a, 180b, and 180c in RAN 104 via the N3 interface. This N3 interface provides WTRU 102a, 102b, and 102c with access to packet-switched networks (such as the Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices. UPF 184 and 184b can 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 so on.

[0062] CN 106 can facilitate communication with other networks. For example, CN 106 may include, or be able to communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 106 and PSTN 108. Furthermore, CN 106 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, WTRUs 102a, 102b, and 102c may be connected to local DNs 185a and 185b via the N3 interface to UPFs 184a and 184b and the N6 interface between UPFs 184a and 184b and DNs 185a and 185b.

[0063] Given Figure 1A-1D as well as Figure 1A-1D The functions described herein, including one or more of the following, can be performed by one or more emulation devices (not shown): 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, SMF183a-b, DN 185a-b, and / or one or more other devices described herein. An emulation device can be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device can be used to test other devices and / or simulate network and / or WTRU functions.

[0064] Simulation devices can be designed to perform tests on one or more other devices in laboratory and / or carrier network environments. For example, one or more simulation devices can perform 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 to test other devices within the communication network. One or more simulation devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. Simulation devices can be directly coupled to another device and / or use over-the-air wireless communication to perform tests for testing purposes.

[0065] One or more simulation devices may perform one or more functions, including all functions, rather than being implemented / deployed as part of a wired and / or wireless communication network. For example, simulation devices may be used to test test scenarios in laboratory and / or non-deployment (e.g., testing) wired and / or wireless communication networks to implement the testing of one or more components. One or more simulation devices may be test devices. Simulation devices may transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0066] Physical Downlink Shared Channel (PDSCH) - Frequency Domain Resource Allocation PDSCH resource allocation type 0 is a bitmap-based allocation scheme. The most flexible way to indicate the set of resource blocks a device should receive for downlink transmission is to include a bitmap in the Bandwidth Part (BWP) equal in size to the number of resource blocks. This allows any combination of resource blocks to be scheduled for transmission to the device, but can result in very large bitmaps in high-bandwidth scenarios. To reduce the bitmap size while maintaining sufficient allocation flexibility, resource allocation type 0 does not point to individual resource blocks (RBs), but rather to groups of consecutive RBs. The size of such a group of resource blocks (RBG) is determined by the size of the BWP. For each size of the BWP, there may be two different configurations, resulting in different RBG sizes for a given BWP size.

[0067] On the other hand, resource allocation type 1 does not rely on a bitmap. Instead, it encodes resource allocation as the start position and length of the RB allocation. As a result, resource allocation type 1 only supports allocations with consecutive frequencies, thereby reducing the number of bits required to signal the RB allocation.

[0068] 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 VRBs are directly mapped to their corresponding PRBs. For resource allocation type 1, both interleaved and non-interleaved mappings are supported. The VRB-to-PRB mapping bit in the DCI (if present only in the downlink) indicates whether allocation signaling uses interleaved or non-interleaved mapping. In the uplink, non-interleaved mapping is always used.

[0069] The resource allocation scheme for Radio Resource Allocation (RRC) can be configured as: Type 0, Type 1, a dynamic selection between Type 0 and Type 1, and Type 2. For fallback DCI, only resource allocation type 1 is supported because the lower overhead is more important than the flexibility of configuring discontinuous resources.

[0070] 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 Division Multiplexing (OFDM) symbols. To schedule these resources, modulation symbols are mapped to resource elements in a frequency-first, time-second manner. The VRB containing the modulation symbols is mapped to a PRB in the BWP used for transmission. Based on the BWP used for transmission, a Common Resource Block (CRB) can be determined, and thus the exact frequency position on the carrier can be determined.

[0071] There are two methods for mapping VRBs to PRBs: non-interleaved mapping and interleaved mapping. The mapping used can be controlled dynamically using the VRB-to-PRB mapping bits in the DCI of the scheduled transmission. Non-interleaved mapping means that the VRB is directly mapped to the PRB in the same BWP. This is useful when the network is trying to allocate transmissions to physical resources with readily available favorable channel conditions. On the other hand, the reason for interleaved mapping is to achieve frequency diversity, which can be leveraged for small and large resource allocations respectively. Interleaved VRB-to-PRB mapping is supported only for resource allocation type 1, as resource allocation type 0 provides a high degree of flexibility in resource allocation.

[0072] For small resource allocations (e.g., voice services), channel-dependent scheduling may be undesirable from an overhead perspective due to the amount of feedback signaling required, or it may be impossible due to rapid channel changes caused by rapidly moving equipment. In this regard, frequency diversity by distributing transmissions in the frequency domain is an alternative to leveraging channel variations. While frequency diversity can be achieved using resource allocation type 0, this allocation scheme implies a large control signaling overhead relative to the transmitted data payload and a limited possibility of signaling very small allocations. Conversely, frequency diversity can be achieved with relatively low overhead by using the more compact resource allocation type 1 (which can only signal consecutive resource allocations) combined with interleaved VRB to PRB mapping.

[0073] For large resource allocations that may span the entire BWP, frequency diversity may still be advantageous. In the case of large transport blocks, i.e., at very high data rates, coded data is divided into multiple code blocks. Directly mapping the coded data to PRBs in a frequency-first manner will result in each code block occupying only a small number of consecutive PRBs. Therefore, if channel quality varies across the frequency range used for transmission, some code blocks may suffer from worse quality than others, potentially causing the entire transport block to fail to decode, even though almost all code blocks are correctly decoded. If interleaved resource block mapping is used, a code block occupying a set of consecutive VRBs can be distributed across multiple widely spread PRBs in the frequency domain, similar to the case of small resource allocations. The result of interleaved VRB-to-PRB mapping is a quality averaging effect across code blocks, leading to a higher probability of correctly decoding very large transport blocks.

[0074] The interleaver can be a simple row-column interleaver with a depth of 2. Adjacent frequency blocks are separated by a half-BWP bandwidth. Interleaving is... It is executed in units of RB, where It can be either 2 or 4. This is to reduce WTRU complexity and preserve the precoded resource block group (PRG), which can also be 2 or 4 RBs. To preserve the PRG after interleaving, it can be defined in a way that aligns with the PRG mesh. A grid of RB interleaving cells. Furthermore, the PRG size is equal to 4 and Combinations equal to 2 are excluded because this may not preserve the PRG. The interleaver can be enabled and disabled using indicator bits in the downlink grant. The "VRB to PRB mapping" indicator is included in DCI formats 1_0, 1_1, and 1_2.

[0075] WTRU may assume that the VRB is mapped to the PRB according to the indicated mapping scheme (i.e., non-interleaved or interleaved mapping). If no mapping scheme is indicated, WTRU may assume a non-interleaved mapping. For a non-interleaved VRB to PRB mapping, the virtual resource block... n Mapped to physical resource blocks n In addition to PDSCH transmissions scheduled using DCI format 1_0 in the public search space, virtual resource blocks in this case... n Mapped to physical resource blocks ,in It is the physical resource block with the lowest number in the control resource set that receives the corresponding DCI.

[0076] For interleaved VRB to PRB mapping, the mapping process is defined by resource block bundling and virtual resource blocks. Resource block bundling is defined as follows: for PDSCH transmissions scheduled in DCI format 1_0 with CRC scrambled by SI-RNTI in the type 0-PDCCH common search space in CORESET 0, the resource block bundling in CORESET 0... The set of resource blocks is divided into groups according to the ascending order of resource block number and bundle number. A resource block bundle, of which It is the bundle size, and It is the size of CORESET 0. If Then resource block bundling Depend on It consists of individual resource blocks, and otherwise, resource blocks are bundled. Depend on L It consists of 1 resource block, and all other resource blocks are bundled together by 1 resource block. L It consists of a resource block.

[0077] Resource block bundling is defined as: for a common search space of type 0-PDCCH that is different from CORESET 0, the starting position is... bandwidth portion i PDSCH transmissions scheduled in DCI format 1_0 within any public search space, A collection of virtual resource blocks (If CORESET 0 is configured for the cell, then) It is the size of CORESET 0, and if CORESET 0 is not configured for the cell, then... (The initial downlink bandwidth portion) is divided into virtual resource block numbers and virtual bundle numbers in ascending order. A virtual resource block is bundled, and A collection of physical resource blocks They are divided into groups according to ascending order of physical resource block number and physical bundle number. A bundle of physical resource blocks, among which... , It is the bundle size, and It is the physical resource block with the lowest number in the control resource set corresponding to the DCI. Resource block binding 0 is... It consists of resource blocks, if Then resource block bundling Depend on It consists of individual resource blocks, and otherwise, resource blocks are bundled. Depend on L It consists of 1 resource block, and all other resource blocks are bundled together by 1 resource block. L It consists of a resource block.

[0078] Resource block bundling is defined as follows: for all other PDSCH transfers, the starting position is... bandwidth portion In The set of resource blocks is divided into groups according to the ascending order of resource block number and bundle number. A resource block bundle, of which The bandwidth portion is provided by the higher-level parameters of the VRB-to-PRB interleaver for DCI format 1_0 and 1_1, or for the VRB-to-PRB interleaver DCI-1-2 for DCI format 1_2, within the WTRU-specific search space. The bundle size, and the resource block bundle 0 is determined by... It consists of resource blocks, if Then resource block bundling Depend on It consists of individual resource blocks, and otherwise, resource blocks are bundled. Depend on It consists of 1 resource block, and all other resource blocks are bundled together by 1 resource block. It consists of a resource block.

[0079] Based on the binding mapped to physical resource blocks Virtual resource block bundling ,interval Virtual resource blocks are mapped to physical resource blocks. Virtual resource block bundling. Mapped to physical resource block bundles ,in: .

[0080] It is expected that WTRU will not be configured simultaneously. The PRG size is 4. WTRU may assume the same precoding in the frequency domain is used within a physical resource block bundle. WTRU may not make any assumptions that the same precoding is used in different bundles of common resource blocks.

[0081] In the first example, dynamic triggering of the PDSCH VRB to SkipPRB mapping for the coexistence of high-power narrowband interference sources can be used. The benefit of interleaved VRB to PRB mapping is frequency diversity. The nominal PDSCH interleaved VRB to PRB mapping is summarized below.

[0082] set up This is the number of PRB bundles in BWP, indexed as... According to the PRB bundle VRB Bundling VRB Bundling Mapped to PRB bundles. VRB bundles Mapped to PRB bundle ,in: .

[0083] Figure 2 The diagram illustrates the nominal PDSCH interleaved VRB to PRB mapping (assuming...). And the size of the bundle 2). Figure 2 This illustration shows an example of the mapping from Virtual Resource Block (VRB) to Physical Resource Block (PRB) in Physical Downlink Shared Channel (PDSCH). In this example, C = 4.

[0084] for r = 0 and c = 0, j = 0 and = 0 for r = 1 and c = 0, j = 1 and = 4 for r = 0 and c = 1, j = 2 and = 1 for r = 1 and c = 1, j = 3 and = 5 for r = 0 and c = 2,j = 4 and = 2 for r = 1 and c = 2, j = 5 and = 6 for r = 0 and c = 3, j = 6 and = 3 for r = 1 and c = 3, j = 7 and = 7.

[0085] For 5G, an effective way to reduce interference from high-power narrowband interference sources is to avoid using frequency resources that overlap with the operating bandwidth of the high-power narrowband interference source when it actively transmits or listens for return pulses. This is known as "PRB blanking." Based on the high-power narrowband interference source's rotating timing estimation and power spectral density, the time-frequency interference region is assessed, and in the case of non-interleaved VRB-to-PRB mapping, the 5G scheduler can avoid allocating resource blocks for uplink or downlink services. On the other hand, it will be necessary to enhance the interleaved VRB-to-PRB mapping mechanism to exclude PRB bundling that overlaps with the bandwidth of the high-power narrowband interference source.

[0086] One approach is for the network to cross out VRBs that might map to a blanking PRB. In this case, the remaining available VRBs may become discontinuous, especially for interleaved VRB-to-PRB mappings. As a result, the network needs to schedule WTRUs with discontinuous frequency domain allocations. To address this, the network can apply resource allocation type 0 to facilitate the use of interleaved VRB-to-PRB mappings of blanking PRBs. Alternatively, resource allocation type 1 can be modified, or a new resource allocation type can be introduced that has a list of 'frequency domain resource assignments' in the DCI to support multiple contiguous frequency domain resource assignments. However, both potential resource allocation mechanisms significantly increase the DCI payload size compared to resource allocation type 1.

[0087] To minimize the impact on resource allocation complexity and DCI payload size, the interleaved VRB to PRB mapping scheme can be modified to step around the high-power narrowband interference source bandwidth during the time period when the mapped PRB might fall into the bandwidth of the high-power narrowband interference source, thus facilitating PRB blanking. This is hereinafter referred to as interleaved VRB to SkipPRB mapping. The interleaved VRB to SkipPRB mapping process is described below.

[0088] Let N bundles be the number of 'nominal' PRB bundles. The nominal PRB bundles for a given BWP are indexed as... .set up This refers to the number of excluded PRB bundles (e.g., the number of PRB bundles whose bandwidth overlaps with that of high-power narrowband interference sources), and the number of included PRB bundles. Note that excluded PRB bundles do not need to be consecutive. Included PRB bundles are mapped to PRB' bundles with sequential indices ( The mapping between the included nominal PRB bundle index and the PRB' bundle index is written as follows: .

[0089] Reduced VRB (symbolized as VRB') bundles are defined as intervals. A subset of VRB bundles in the dataset. Based on the bundles mapped to PRBs. VRB' Bundling VRB' bundles are mapped to PRB' bundles. VRB's Bundling Mapped to PRB' bundle ,in: .

[0090] The transmitted nominal PRB bundle index .

[0091] Figure 3 The diagram illustrates the mapping from PDSCH interleaved VRB to SkipPRB (assuming...). , And the size of the bundle =2). Figure 3 The illustration shows an example of a Physical Downlink Shared Channel (PDSCH) interleaved Virtual Resource Block (VRB) to Skip Physical Resource Block (PRB) mapping. Note that the PDSCH interleaved VRB to Skip PRB mapping preserves the contiguous VRB allocation attribute of allocation type 1.

[0092] On the WTRU side, after receiving a continuously scheduled VRB' (with resource allocation type 1) in the DCI, the WTRU can perform interleaved VRB to SkipPRB mapping. To this end, the network can use MAC-CE or group common signaling to notify the WTRU of PRBs that may be excluded during VRB-PRB mapping, as illustrated below by the PDSCH PRB exclusion MAC CE command, where R is a reserved bit set to 0, F is a format field (1 bit), and LCID is a logical channel ID (6 bits), to avoid R / F / LCID (1 byte) using frequency resources that overlap with the operating bandwidth of high-power narrowband interference sources, where eLCID (1 or 2 bytes, 1 byte if LCID = 33, 2 bytes if LCID = 34) is the extended logical channel ID, and a unique eLCID value can be used to identify PDSCH partial interleaving commands, and where L (1 or 2 bytes, 1 byte if F = 0, 2 bytes if F = 1) is a field length in bytes indicating the length of the corresponding MAC SDU or variable-size MAC-CE.

[0093] The VRB-to-PRB mapping exclude PRB range field indicates the range of PRBs that can be excluded during the PDSCH VRB-to-PRB mapping process. A Resource Indicator Value (RIV) is used to specify the PRB range. A value of all zeros restores the PDSCH interleaving VRB-to-PRB mapping to normal operation. In the example, multiple VRB-to-PRB mapping exclude PRB range fields can be included to accommodate discontinuous excluded PRB ranges. For example, a VRB-to-PRB mapping exclude PRB bundle bitmap can be provided in the MAC CE to indicate the PRB bundles to be excluded during the PDSCH VRB-to-PRB mapping process (a bit of 1 indicates that the interleaver excludes a specific PRB bundle, and a bit of 0 indicates otherwise).

[0094] Figure 4 The non-interleaved VRB to SkipPRB mapping is shown. Figure 4 The illustration shows an example of a non-interleaved Virtual Resource Block (VRB) to SkipPRB mapping in the Physical Downlink Shared Channel (PDSCH). The advantage of using non-interleaved VRB to SkipPRB mapping is that it facilitates resource allocation across PRB exclusion areas using Resource Allocation Type 1, which enhances scheduling multiplexing flexibility and thus improves spectral efficiency when applying PRB blanking. Therefore, if the pre-allocated PRB locations can be included in L1 / L2 and / or higher-level control signaling, non-interleaved VRB to SkipPRB mapping can also be used to schedule bypasses other types of pre-allocated high-priority resources using Resource Allocation Type 1.

[0095] To illustrate, a configuration of 16 available PRBs (0..15) in the system is considered, of which 4 (8..11) are affected by radar interference. For non-interleaved operation, the VRB-to-PRB mapping is 1 to 1. If UE1 requires 6 PRBs for data transmission, the scheduler can allocate VRB / PRB (0..5) to UE1, and the remaining unscheduled VRB / PRBs are (6, 7) and (12, 13, 14, 15). However, if UE2 also requires 6 PRBs for data transmission, the scheduler cannot allocate the remaining non-contiguous VRB / PRBs to UE2 when using resource allocation type 1. Therefore, only UE1 is scheduled in this time slot. UE2 will need to wait for the next time slot. As a result, PRB resources are not effectively utilized. On the other hand, if we consider the VRB-to-skipPRB mapping, such as... Figure 4 As shown, the available VRB' is (0..11). UE1 can be assigned VRB' (0..5) and UE2 can be assigned VRB' (6..11). After VRB to skipPRB mapping, UE1 will transmit on PRB (0..5) and UE2 will transmit on PRBs (6,7) and (12,13,14,15). In this case, the two UEs can be scheduled in the same time slot, thereby improving resource utilization efficiency.

[0096] The network can dynamically indicate PDSCH VRB to SkipPRB mapping using dedicated DCI signaling by introducing new skip-PRB mapping flags (e.g., in DCI formats 1_0, 1_1, and 1_2) to indicate whether the VRB to PRB mapping field triggers 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 (existing only for resource allocation type 1) is interpreted in the same way as the 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 indicates non-interleaved VRB to SkipPRB mapping, while VRB to PRB mapping = 1 indicates interleaved VRB to SkipPRB mapping.

[0097] Table 1: VRB to PRB Mapping .

[0098] On the WTRU side, when a PDSCH VRB to SkipPRB mapping instruction is received in the DCI, the WTRU can perform the VRB to SkipPRB mapping. Figure 5A flowchart of an exemplary method 500 for PRB-to-SkipPRB mapping for data reception is shown. Method 500 can be implemented using WTRU. It will be understood that although method 500 is described as a series of actions or events, method 500 is not limited to the order of such actions or events. Some actions may occur in a different order and / or simultaneously with other actions or events besides those described herein. Furthermore, method 500 may include other actions or events not depicted for simplicity, and other illustrated actions or events may be removed or modified.

[0099] At box 502, method 500 relates to determining PRB bundles used for or included in data transmission within the active BWP. Included PRB bundles can be determined based on unused bundles or bundles excluded from data transmission. In some examples, included PRB bundles can be determined based on VRB-to-PRB mapping exclusion ranges or VRB-to-PRB mapping exclusion PRB bundle bitmap information received in the latest MAC CE. Included PRB bundles within the active BWP can be further determined by blacklisting excluded PRB bundles within the active BWP. At box 504, method 500 relates to defining a mapping of included PRB bundles to a sequentially indexed or consecutive set of PRB' bundles. According to a non-interleaved mapping scheme, included PRB bundles can be mapped to this set of PRB' bundles. At box 506, method 500 relates to determining a reduced set or subset of VRB' bundles (i.e., sequentially indexed or consecutive VRB' bundles). The reduced set of VRB' bundles can be determined based on the number of included PRB bundles in the set of PRB bundles. For example, the number of VRB bundles can be equal to the number of included PRB bundles.

[0100] At block 508, method 500 relates to mapping a reduced set of scheduled VRB' bundles (having resource allocation type 1) to a set of PRB' bundles after receiving information in the DCI about consecutive VRB's scheduled for reception of a data channel (e.g., PDSCH) within an active BWP. For example, the WTRU may perform interleaved or non-interleaved VRB' to PRB' bundle mapping according to the VRB-to-SkipPRB mapping settings in the DCI. At block 510, method 500 relates to mapping PRB' bundles to included PRB bundles for data reception. For example, the WTRU may perform PRB' to PRB bundle mapping to locate the scheduled PRB for received PDSCH signals. The WTRU may notify the network of its ability to support PDSCH VRB-to-SkipPRB mapping, as illustrated by the following information message.

[0101] In one embodiment, dynamic triggering of PDSCH VRB to SkipPRB mapping occurs for the coexistence of high-power narrowband interference sources. External nodes of the network can determine interference source characteristics such as carrier frequency, bandwidth, period, dwell time, AoA, and PSD. These measurements can also be determined within the wireless network by observing measurements associated with both WTRUs and gNBs. The network determines the excluded PRB bundles within the active BWP based on the detected high-power narrowband interference source bandwidth. The network identifies the set of WTRUs that are causing significant interference from the high-power narrowband interference sources. If interleaved or non-interleaved VRB to SkipPRB mapping is to be applied, the network uses MAC-CE or group common signaling to notify the WTRUs of the PRBs to be excluded from the PDSCH (e.g., excluding PRB range fields or VRB to PRB bundle bitmaps via one or more VRB to PRB mappings). The network uses dedicated DCI signaling to dynamically trigger PDSCH interleaved or non-interleaved VRB to SkipPRB mapping.

[0102] The network can perform interleaved or non-interleaved VRB to SkipPRB mapping for PDSCH transports. Figure 6 A flowchart illustrating an exemplary method 600 for VRB-to-SkipPRB mapping for data transmission (e.g., PDSCH transmission) is shown. Method 600 can be implemented at a base station or node. In some examples, method 600 can be implemented by a WTRU for data transmission. It will be understood that although method 600 is described as a series of actions or events, method 600 is not limited to the order of such actions or events. Some actions may occur in a different order and / or simultaneously with other actions or events besides those described herein. Furthermore, method 600 may include other actions or events not depicted for simplicity, and other illustrated actions or events may be removed or modified.

[0103] At block 602, the method involves determining PRB bundles to be included or used for data transmission within the active BWP for data channel transmission. PRB bundles to be included for data transmission can be determined by excluding PRB bundles not used for data transmission. Excluded PRB bundles may correspond to one or more interfering signals (e.g., RADAR signals) overlapping with data channel transmission. The included PRB bundles may be discontinuous. At block 604, method 600 involves defining a mapping of the included PRB bundles to a sequentially indexed or consecutive set of PRB' bundles. According to a non-interleaved mapping scheme, the included PRB bundles may be mapped to a set of PRB' bundles. At block 606, method 600 involves determining a reduced set or subset of VRB' bundles (i.e., a sequentially indexed or consecutive set of 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 in the reduced set of VRB' bundles may be equal to the number of included PRB bundles.

[0104] At block 608, method 600 involves mapping a reduced set of scheduled VRB' bundles to a set of PRB' bundles after making a decision in the DCI to schedule consecutive VRBs (having resource allocation type 1). For example, the network may perform interleaved or non-interleaved VRB' to PRB' bundle mapping as indicated to the receiving device (e.g., WTRU) in the Download Control Information (DCI). In one embodiment, the number of VRB' bundles ( The number of VRBs scheduled in each VRB bundle is determined by rounding up the ratio of (the number of VRBs' scheduled) to (the size of the VRB' bundle). The VRB' bundle size. If mod(number of scheduled VRB's, VRB' bundle size) = 0, then the VRB' bundle size is... The number of VRBs scheduled in the middle is equal to the VRB' bundle size. Otherwise, the VRB' bundle size is... The number of VRBs' scheduled in a PRB' bundle is equal to mod(number of scheduled VRBs', VRB' bundle size). The number of PRBs' scheduled in each PRB' bundle is the same as the number of VRBs' scheduled in the corresponding VRB' bundle mapped to the PRB' bundle. At box 610, method 600 may involve mapping PRB' bundles to included PRB bundles used for data transmission. PRB' bundles may be sequentially indexed or contiguous, while included PRB bundles may be discontiguous. For example, the network may perform PRB' to nominal (included) PRB bundle mapping for PDSCH transmission. The number of PRBs scheduled in each PRB bundle is the same as the number of PRBs' scheduled in the corresponding PRB' bundle mapped to the PRB bundle. The WTRU receives PDSCH data from the scheduled PRBs within the mapped PRB bundles.

[0105] When a DCI signaling indicating whether to perform a PDSCH interleaved or non-interleaved VRB-to-SkipPRB mapping is received, the WTRU can perform the VRB-to-SkipPRB mapping. Figure 7 A flowchart illustrating an exemplary method 700 for VRB-to-SkipPRB mapping for data reception (e.g., data reception for PDSCH transmission) is shown. Method 700 can be implemented by a WTRU. It will be understood that although method 700 is described as a series of actions or events, method 700 is not limited to the order of such actions or events. Some actions may occur in a different order and / or occur simultaneously with other actions or events besides those described herein. Furthermore, method 700 may include other actions or events not depicted for simplicity, and other illustrated actions or events may be removed or modified.

[0106] At box 702, method 700 relates to determining PRB bundles excluded from use or not used for data transmission. For example, the WTRU may retrieve up-to-date information about one or more VRB-to-PRB mapping excluded PRB range fields or VRB-to-PRB mapping excluded PRB bundle bitmaps to determine excluded or unused PRB bundles. At box 704, method 700 relates to determining PRB bundles used or included for data transmission. For example, the WTRU may determine included PRB bundles within an active BWP by blacklisting excluded PRB bundles within the active BWP.

[0107] At box 706, method 700 involves defining a mapping of the included PRB bundles to a set of sequentially indexed or consecutively linked PRB' bundles. According to a non-interleaved mapping scheme, the included PRB bundles can be mapped to a set of PRB' bundles. At box 708, method 700 involves determining a reduced set or subset of VRB' bundles (i.e., sequentially indexed or consecutively linked VRB' bundles). The reduced set of VRB' bundles can be determined based on the number of included PRB bundles. For example, the number of VRB' bundles in the reduced set of VRB' bundles can be equal to the number of included PRB bundles.

[0108] At block 710, method 700 involves mapping a reduced set of scheduled VRB' bundles to a set of PRB' bundles after receiving information in the DCI about consecutive VRB's (having resource allocation type 1) (thus indicating the use of VRB-to-SkipPRB mapping). Depending on the VRB-to-SkipPRB mapping settings in the DCI, the WTRU can perform interleaved or non-interleaved VRB'-to-PRB' bundle mapping. In one embodiment, the number of VRB' bundles ( The number of VRBs scheduled in each VRB bundle is determined by rounding up the ratio of (the number of VRBs' scheduled) to (the size of the VRB' bundle). The VRB' bundle size. If mod(number of scheduled VRB's, VRB' bundle size) = 0, then the VRB' bundle size is... The number of VRBs scheduled in the middle is equal to the VRB' bundle size. Otherwise, the VRB' bundle size is... The number of VRBs' scheduled in a PRB' bundle is equal to mod(number of scheduled VRBs', VRB' bundle size). The number of PRBs' scheduled in each PRB' bundle is the same as the number of VRBs' scheduled in the corresponding VRB' bundle mapped to the PRB' bundle. At block 712, method 700 involves mapping PRB' bundles to included PRB bundles used for data transmission. PRB' bundles can be sequentially indexed or contiguous, while included PRB bundles can be discontiguous. PRB' bundles can be mapped to PRB bundles based on a mapping function. The number of PRBs scheduled in each PRB bundle is the same as the number of PRBs' scheduled in the corresponding PRB' bundle mapped to the PRB bundle. The WTRU receives PDSCH data from the PRBs scheduled within the mapped PRB bundles.

[0109] Although the features and elements have been described above in specific combinations, those skilled in the art will understand that each feature or element can be used alone or in any combination with other features and elements. Furthermore, the methods described herein can be implemented as 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 via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as internal hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROMs and digital multifunction discs (DVDs)). The processor associated with the software can be used to implement a radio frequency transceiver used in a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

1. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: Receive downlink control transmission, wherein the downlink control transmission includes resource allocation information for data transmission; The resource allocation information transmitted is mapped to a set of virtual resource blocks; The virtual resource block bundle set is mapped to the first physical resource block bundle set based on the first mapping function, wherein the first physical resource block bundle set is contiguous; The first physical resource block bundle set is mapped to a first physical resource block bundle within the second physical resource block bundle set based on a second mapping function, wherein the second physical resource block bundle set includes both the first and second physical resource block bundles, wherein the first physical resource block bundle is available for data transmission, wherein the second physical resource block bundle is not available for data transmission, and wherein the first physical resource block bundle is non-contiguous; and The allocated resources mapped in the first physical resource block bundle are used for data reception.

2. The method according to claim 1, wherein, The virtual resource block bundles in the virtual resource block bundle set are either contiguous or sequentially indexed.

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

4. The method according to claim 1 or 3, wherein, The second physical resource block bundle overlaps with at least one signal that interferes with the data transmission, and 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 a first physical resource block bundle for the data transmission based on the determination of the second physical resource block bundle.

6. The method of claim 1, further comprising determining the number of virtual resource block bundles based on the 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 includes a one-to-one mapping function.

8. The method according to claim 1 or 7, wherein, The first mapping function includes an interleaved mapping function or a non-interleaved mapping function.

9. The method according to claim 1 or 2, wherein, The first physical resource block bundle includes a first physical resource block bundle and a second physical resource block bundle, wherein the first physical resource block bundle and the second physical resource block bundle are not contiguous.

10. The method according to claim 1, wherein, Each of the first physical resource block bundles includes multiple resource blocks, and the data transmission includes physical downlink shared channel (PDSCH) transmission within the active bandwidth portion.

11. The method according to claim 1, wherein, The downlink control transmission includes downlink control information, wherein the downlink control information indicates whether blanking techniques were used during the mapping of the data transmission.

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

13. The method according to claim 3, wherein, The bitmap or range value received from the network identifies a second physical resource block bundle that was not used to transmit data for the data transmission.

14. A method for wireless communication, comprising: The virtual resource block bundle set is mapped to the first physical resource block bundle set based on the first mapping function, wherein the first physical resource block bundle set is contiguous; The first physical resource block bundle set is mapped to a first physical resource block bundle within the second physical resource block bundle set based on a second mapping function, wherein the second physical resource block bundle set includes both the first and second physical resource block bundles, wherein the first physical resource block bundle is available for data transmission, wherein the second physical resource block bundle is not available for data transmission, and wherein the first physical resource block bundle is non-contiguous; and The first physical resource block is used for data transmission.

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

16. The method according to claim 14 or 15, wherein, The second physical resource block bundle corresponds to the interference signal, and each of the second physical resource block bundles is not used to transmit data for the data transmission.

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

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 includes a one-to-one mapping function.

19. The method according to claim 14 or 18, wherein, The first mapping function includes an interleaved mapping function or a non-interleaved 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 comprises multiple resource blocks, and wherein the data transmission includes physical downlink shared channel (PDSCH) transmission within the active bandwidth portion.

21. A wireless transmit / receive unit (WTRU), comprising: transceiver; as well as The processor is configured as follows: Receive downlink control transmission, wherein the downlink control transmission includes resource allocation information for data transmission; The resource allocation information transmitted is mapped to a set of virtual resource blocks; The virtual resource block bundle set is mapped to the first physical resource block bundle set based on the first mapping function, wherein the first physical resource block bundle set is contiguous; The first physical resource block bundle set is mapped to a first physical resource block bundle within the second physical resource block bundle set based on a second mapping function, wherein the second physical resource block bundle set includes both the first and second physical resource block bundles, wherein the first physical resource block bundle is available for data transmission, wherein the second physical resource block bundle is not available for data transmission, and wherein the first physical resource block bundle is non-contiguous; and The allocated resources mapped in the first physical resource block bundle are used for data reception.

22. The WTRU according to claim 21, wherein, The virtual resource block bundles in the virtual resource block bundle set are either contiguous or sequentially indexed.

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

24. The WTRU according to claim 21, wherein, The second physical resource block bundle overlaps with at least one signal that interferes with the data transmission, and 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 a first physical resource block bundle for the data transmission based on the determination of the second physical resource block bundle.

26. A wireless transmit / receive unit (WTRU), comprising: transceiver; as well as The processor is configured as follows: The virtual resource block bundle set is mapped to the first physical resource block bundle set based on the first mapping function, wherein the first physical resource block bundle set is contiguous; The first physical resource block bundle set is mapped to a first physical resource block bundle within the second physical resource block bundle set based on a second mapping function, wherein the second physical resource block bundle set includes both the first and second physical resource block bundles, wherein the first physical resource block bundle is available for data transmission, wherein the second physical resource block bundle is not available for data transmission, and wherein the first physical resource block bundle is non-contiguous; and The first physical resource block is used for data transmission.

Images