PUSCH enhancements for RADAR coexistence

Abstract

A wireless transmit-receive unit (WTRU) and a method for mitigating radar interference to PUSCH transmission are disclosed. The method may comprise: transmitting a message informing a network of a PUSCH MIMO layer aggregation capability; receiving a MIMO rank; receiving an indication of using PUSCH MIMO layer aggregation; determining a PUSCH layer aggregation level based on the MIMO rank; and transmitting a plurality of redundancy versions of a PUSCH codeword including one or more code blocks based on the PUSCH layer aggregation level. The WTRU may be configured to transmit a message notifying a network of a PUSCH MIMO layer aggregation capability; receiving a MIMO rank; receiving an indication of using PUSCH MIMO layer aggregation; determining a PUSCH layer aggregation level based on the MIMO rank; and transmitting a plurality of redundancy versions of a PUSCH codeword including one or more code blocks based on the PUSCH layer aggregation level.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 336,899, filed on April 29, 2022, the contents of which are incorporated herein by reference.

[0003] Government Rights Statement

[0004] This invention was made with Government support under Project NSC-20-2084: Dynamic Spectrum Sharing 5G Network Enhancement Prototype, also known as Enhanced Security and Coexistence of DoD-5G (ENSURED-5G); OTA No. W15QKN-15-9-1004, Base and Project Agreement 2017-314A-Mod-03, Subcontract 2021-01. The Government has certain rights in this invention. Background Art

[0005] Recent trends are driving researchers to create solutions for cellular network deployment in the presence of high-power narrowband interferers (e.g., RADAR). While the baseline functionality provided by 5G can be used to provide a certain degree of coexistence with RADAR, enhancements will be needed to realize the full 5G potential.

[0006] When a narrowband high power interferer such as RADAR operates in a frequency band that overlaps with the RBs used by the WTRU to transmit on the PUSCH, the gNB will not be able to reliably receive the Data Radio Bearer (DRB) and Signaling Radio Bearer (SRB) traffic on the uplink and uplink HARQ retransmissions. In addition, uplink control information (UCI), such as HARQ ACK / NACK feedback for downlink transmissions and downlink channel state information (CSI) feedback may also be sent on the PUSCH channel. In the case where the PUSCH can be reliably received in the presence of interference, the PUSCH transmission has the potential to interfere with the RADAR system, which is also problematic. Summary of the invention

[0007] Aspects, features and advantages of the disclosed embodiments ensure robust and efficient PUSCH transmission and reception in the presence of RADAR interference. A method implemented by a wireless transmit / receive unit (WTRU) may include: sending a message notifying a network of PUSCH MIMO layer aggregation capability; receiving a MIMO rank; receiving an indication of using PUSCH MIMO layer aggregation; determining a PUSCH layer aggregation level based on the MIMO rank; and sending multiple redundant versions of a PUSCH codeword including one or more code blocks based on the PUSCH layer aggregation level. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] A more detailed understanding may be obtained from the following description given by way of example in conjunction with the accompanying drawings, in which like reference numerals indicate like elements, and in which:

[0009] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented;

[0010] Figure 1B is an example of an embodiment in which Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within the illustrated communication system;

[0011] Figure 1C is an example of an embodiment in which Figure 1A a system diagram of an example Radio Access Network (RAN) and an example Core Network (CN) used within the illustrated communication system;

[0012] Figure 1D is an example of an embodiment in which Figure 1A A system diagram of another example RAN and another example CN used within the illustrated communication system;

[0013] Figure 2 is a diagram depicting potential scenarios where a wireless network encounters interference from RADAR;

[0014] Figure 3 is an exemplary configuration for uplink cancellation;

[0015] Figure 4 is an exemplary configuration for PUSCH time domain resource allocation;

[0016] Figure 5 is an exemplary configuration for PUSCH time domain resource allocation;

[0017] Figure 6 is an exemplary configuration for PUSCH aggregation;

[0018] Figure 7 is an exemplary configuration for PUSCH power control;

[0019] Figure 8 An exemplary system for sensing RADAR information is shown;

[0020] Fig. 9 An exemplary PUCSH resource cancellation in the presence of RADAR interference is shown;

[0021] Fig. 10A An exemplary PUSCH resource cancellation in the presence of RADAR interference is shown;

[0022] Fig. 10B An exemplary PUSCH resource cancellation in the presence of RADAR interference is shown;

[0023] Fig. 10C An exemplary PUSCH resource cancellation in the presence of RADAR interference is shown;

[0024] Fig.11A An exemplary serial mapping of two redundant versions of a codeword to two MIMO layers is shown;

[0025] Fig. 11B An exemplary serial mapping of three redundant versions of a codeword to three MIMO layers is shown;

[0026] Fig. 11C An exemplary serial mapping of four redundant versions of a codeword to four MIMO layers is shown;

[0027] Fig. 12A An exemplary parallel mapping of two redundant versions of a codeword to two MIMO layers is shown;

[0028] Fig. 12B An exemplary parallel mapping of three redundant versions of a codeword to three MIMO layers is shown;

[0029] Fig. 12C An exemplary parallel mapping of four redundant versions of a codeword to four MIMO layers is shown;

[0030] Fig.13 is a flow chart of an example process implemented by a WTRU including PUSCH layer aggregation. DETAILED DESCRIPTION

[0031] Figure 1A 1 is a diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of 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 OFDM (ZT-UW-DFT-S-OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0032] like Figure 1A As 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, but 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 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 send and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, 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 device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0033] The communication system 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 other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an evolved Node B (eNB), a Home Node B, a Home evolved Node B, a next generation Node B such as a gNode B (gNB), a new radio (NR) Node B, 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.

[0034] 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), a relay node, etc. The base station 114a and / or the base station 114b may be configured to send 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 a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrums. A cell may provide coverage of wireless services to 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, a cell associated with the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver 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 send and / or receive signals in a desired spatial direction.

[0035] 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 (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).

[0036] More specifically, as noted above, the communication 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, etc. 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), that may use Wideband CDMA (WCDMA) to establish the air interface 116. 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).

[0037] 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) that may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-APro).

[0038] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology (such as NR radio access) that may establish the air interface 116 using NR.

[0039] 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 together implement LTE radio access and NR radio access, for example using the dual connectivity (DC) principle. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to / from multiple types of base stations (e.g., eNBs and gNBs).

[0040] 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, CDMA2000 1X, 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), etc.

[0041] Figure 1AThe base station 114b in the may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, 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 a femtocell. As Figure 1A As shown, the base station 114 b may have a direct connection to the Internet 110. Therefore, the base station 114 b may not need to access the Internet 110 via the CN 106.

[0042] 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 different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not described in detail in the accompanying drawings, the CN 106 may be 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. Figure 1A Although not shown in the figure, 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 utilize NR radio technology, the CN 106 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0043] The CN 106 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides 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), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired communication networks and / or wireless communication 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.

[0044] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication 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 via different wireless links). Figure 1A The illustrated WTRU 102c 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.

[0045] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, 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. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0046] 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 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. 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 environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0047] The send / receive element 122 may be configured to send a signal to a base station (e.g., base station 114a) or receive a signal from the base station via an air interface 116. For example, in one embodiment, the send / receive element 122 may be an antenna configured to send and / or receive an RF signal. In an embodiment, the send / receive element 122 may be a transmitter / detector configured to send and / or receive, for example, IR, UV or visible light signals. In another embodiment, the send / receive element 122 may be configured to send and / or receive both RF signals and optical signals. It should be understood that the send / receive element 122 may be configured to send and / or receive any combination of wireless signals.

[0048] Although the transmit / receive element 122 Figure 1B 1 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.

[0049] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. For example, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0050] The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit) and may receive user input data therefrom. 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 a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a 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 a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0051] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power to 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, etc.

[0052] 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 from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0053] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules 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 electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, FM radio unit, digital music player, media player, video game player module, Internet browser, virtual reality and / or augmented reality (VR / AR) device, activity tracker, etc. The peripheral device 138 may include one or more sensors. The sensor may be one or more of the following: 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, etc.

[0054] 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 specific subframes for both 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 for reducing and / or substantially eliminating self-interference via signal processing performed by hardware (e.g., a choke) or via a processor (e.g., a separate processor (not shown) or via the 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 specific subframes for both UL (e.g., for transmission) or DL ​​(e.g., for reception)) may be concurrent and / or simultaneous.

[0055] Figure 1C 1 is a system diagram showing the RAN 104 and the CN 106 in accordance with 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.

[0056] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-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 evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

[0057] Each of the evolved Node 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 in UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.

[0058] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. 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] The MME 162 may be connected to each of the evolved Node-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, etc. 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.

[0060] The SGW 164 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an 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 the user plane during inter-evolved Node-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.

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

[0062] 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 be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts 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 other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers.

[0063] Although the WTRU Figures 1A to 1D Although described as wireless terminals, it is contemplated that in certain representative embodiments, such terminals may (eg, temporarily or permanently) use a wired communications interface with a communications network.

[0064] In a representative embodiment, the other network 112 may be a WLAN.

[0065] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STA) 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 to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and leading to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be transmitted to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be transmitted by the AP, for example, wherein the source STA may transmit traffic to the AP, and the AP may deliver traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be transmitted between the source STA and the destination STA (e.g., directly between them) using a direct link establishment (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (eg, all STAs in the STA) may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad hoc" communication mode.

[0066] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP may send beacons on a fixed channel (such as a primary channel). The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a dynamically set width. The primary channel may be an operating channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) may listen to the primary channel. If the primary channel is listened / 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.

[0067] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0068] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz channels and / or 80MHz channels can be formed by combining continuous 20MHz channels. 160MHz channels can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be sent by the transmitter STA. At the receiver of the receiver STA, the above-mentioned operation for the 80+80 configuration can be reversed, and the combined data can be transmitted to the medium access control (MAC).

[0069] 802.11af and 802.11ah support operating modes below 1GHz. 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 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter 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 support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0070] 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 primary channels. The primary channel may have a bandwidth equal to the maximum 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 (which supports the minimum bandwidth operating mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (which only supports a 1MHz operating mode) is transmitting to the AP, all available bands may be considered busy even if most of the available bands remain idle.

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

[0072] Figure 1D1 is a system diagram showing the RAN 104 and the CN 106 in accordance with an embodiment. As noted above, the RAN 104 may employ 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.

[0073] 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, the gNBs 180a, 180b may utilize beamforming to send signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may, for example, use multiple antennas to send 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 an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNB 180a and the gNB 180b (and / or the gNB 180c).

[0074] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with a parameter set that may be scalable. For example, 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 the gNBs 180a, 180b, 180c using subframes or Transmission Time Intervals (TTIs) of varying or scalable lengths (e.g., containing varying numbers of OFDM symbols and / or varying absolute time lengths over time).

[0075] 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 a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRU 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the evolved Node-B 160a, 160b, 160c. For example, the WTRU 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more evolved Node-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the evolved Node-B 160a, 160b, 160c may act as a mobility anchor for the WTRU 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRU 102a, 102b, 102c.

[0076] Each of the gNBs 180a, 180b, 180c may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, support of network slicing, interworking between DC, NR and E-UTRA, routing of user plane data towards user plane functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0077] Figure 1DThe illustrated CN 106 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although the aforementioned 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.

[0078] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of non-access stratum (NAS) signaling, mobility management, etc. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of services utilized by the WTRU 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, etc. 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.

[0079] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 106 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 106 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure the traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy implementation and QoS, providing DL data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0080] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the 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, etc.

[0081] 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 acts 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 other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to the DNs 185a, 185b via the UPFs 184a, 184b via the N3 interfaces to the UPFs 184a, 184b and the N6 interfaces between the UPFs 184a, 184b and the local DNs 185a, 185b.

[0082] Given that Figures 1A to 1D as well as Figures 1A to 1D Corresponding to the description of the present invention, one or more or all of the functions described herein with reference to one or more of the following items may be performed by one or more simulation devices (not shown): WTRU102a to 102d, base station 114a to 114b, evolved Node B 160a to 160c, MME 162, SGW 164, PGW 166, gNB180a to 180c, AMF 182a to 182b, UPF 184a to 184b, SMF 183a to 183b, DN 185a to 185b and / or any other device described herein. The simulation device may be one or more devices configured to mimic one or more or all of the functions described herein. For example, the simulation device can be used to test other devices and / or simulate network and / or WTRU functions.

[0083] The simulation device may be designed to implement one or more tests of other devices in a laboratory environment and / or in an operator network environment. For example, one or more simulation devices may perform one or more functions 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. One or more simulation devices may perform one or more functions or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device may be directly coupled to another device for the purpose of testing and / or performing tests using over-the-air wireless communications.

[0084] One or more simulation devices can perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test scenario in a test laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices can be test equipment. Direct RF coupling and / or wireless communication via RF circuits (e.g., which may include one or more antennas) can be used by the simulation device to send and / or receive data.

[0085] The following abbreviations may be referred to in this document:

[0086] 3GPP Third Generation Partnership Project

[0087] 5G Fifth Generation

[0088] AOA Angle of Arrival

[0089] BW Bandwidth

[0090] BWP Bandwidth Part

[0091] CB Code Block

[0092] CBG Code Block Group

[0093] CCE Control Channel Element

[0094] CI Cancel Indicator

[0095] CORESET Control Resource Set

[0096] CRC Cyclic Redundancy Check

[0097] C-RNTI Cell-specific Radio Network Temporary Identifier

[0098] CI-RNTI Cancellation Indicator Radio Network Temporary Identifier

[0099] CS-RNTI Configured Scheduling Radio Network Temporary Identifier

[0100] CSI Channel State Information

[0101] CSI-RS Channel State Information-Reference Signal

[0102] DCI Downlink Control Information

[0103] DL Downlink

[0104] DMRS Demodulation Reference Signal

[0105] DRB Data Radio Bearer

[0106] ENSURED-5G Enhanced Security and Coexistence of DoD-5G

[0107] gNB Next Generation (5G) NodeB

[0108] MAC Media Access Control

[0109] MAC-CE MAC Control Element

[0110] MCS Modulation and Coding Scheme

[0111] MCS-C-RNTI Modulation and Coding Scheme Cell Specific Radio Network

[0112] Temporary Identifier

[0113] MSB Most Significant Bit

[0114] NDI New Data Indicator

[0115] NR New Radio

[0116] OAM Operations, Administration and Maintenance

[0117] OFDM Orthogonal Frequency Division Multiplexing

[0118] PDCCH Physical Downlink Control Channel

[0119] PHY Physical Layer

[0120] PRB Physical Resource Block

[0121] PSD Power Spectral Density

[0122] PUCCH Physical Uplink Control Channel

[0123] PUSCH Physical Uplink Shared Channel

[0124] QCL Quasi-collocation

[0125] QOS Quality of Service

[0126] RACH Random Access Channel

[0127] RADAR Radio Detection and Ranging

[0128] RB Resource Block

[0129] RE Resource Element

[0130] REG Resource Element Group

[0131] RIV Resource Indicator Value

[0132] RRC Radio Resource Control

[0133] RV Redundancy Version

[0134] SINR Signal to Interference and Noise Ratio

[0135] SLIV start and length indicator value

[0136] SRB Signalling Radio Bearer

[0137] SRS Sounding Reference Signal

[0138] SSB SS / PBCH block

[0139] SUL Supplementary Uplink

[0140] TB Transfer Block

[0141] TPMI Transmit Precoding Matrix Indicator

[0142] UCI Uplink Control Information

[0143] UL Uplink

[0144] URLLC Ultra-Reliable Low Latency Communications

[0145] refer to Figure 2 , shows an example potential interference scenario 200 where communications between a base station 210 and a remote WTRU 250 may be adversely affected by the presence of narrowband interference sources such as RADAR station 202 and / or RADAR (or reflections therefrom) on a plane 204. The following example implementation addresses a potential interference avoidance solution for PUSCH communications between the WTRU 250 and the base station 210.

[0146] Uplink preemption between WTRUs is described herein. Uplink preemption involves mechanisms for controlling interference from low priority traffic to latency critical high priority traffic. Two mechanisms are available: 1) cancellation, where low priority transmissions are cancelled; 2) power boosting, where high priority transmissions use a higher power level than would be used without preemption.

[0147] The cancellation method involves the reception of a cancellation indicator, which is sent using DCI format 2_4 scrambled with CI-RNTI (cancellation indicator RNTI). The cancellation indicator is a bitmap indicating a set of OFDM symbols and resource blocks that should be cancelled. Upon receiving the cancellation indicator, the UE shall stop the transmission of any PUSCH or SRS that (partially) overlaps with any of the cancelled resources.

[0148] The cancellation indicator must appear at least a certain time before the start of a PUSCH (or SRS) transmission in order to cancel that transmission. This is required to allow the WTRU to properly process and take into account the cancellation indicator. This also means that, assuming the WTRU is able to receive and transmit simultaneously and has enough time to cancel the repeated PUSCH, a PUSCH transmission already in progress cannot be stopped - with one exception - a PUSCH transmission configured with a repetition factor of 2 and receiving a cancellation indicator during the first transmission will cancel the second transmission.

[0149] If the WTRU is provided with UplinkCancellation, then the WTRU is provided with a search space set in one or more serving cells for monitoring a first PDCCH candidate having an L CI The CCE aggregation level of the CCE is used to detect the DCI format 2_4 provided by the CI-RNTI. UplinkCancellation also provides the WTRU with:

[0150] The serving cell set represented by ci-ConfigurationPerServingCell includes a serving cell index set and a corresponding position set of fields in DCI format 2_4 represented by positionInDCI; the number of fields in DCI format 2_4 represented by positionInDCI-forSUL, for each serving cell of the SUL carrier, if the serving cell is configured with a SUL carrier; the information payload size for DCI format 2_4 represented by dci-PayloadSize-ForCI; and the indication of time-frequency resources represented by timeFrequencyRegion.

[0151] For a serving cell with an associated field in DCI format 2_4, the field is represented as: N CI , the number of bits provided by ci-PayloadSize; B CI , the number of PRBs provided by frequencyRegionforCI in timeFrequencyRegion; T CI , the number of symbols, excluding symbols used to receive SS / PBCH blocks and DL symbols indicated by tdd-UL-DL-ConfigurationCommon, from the number of symbols provided by timeDurationforCI in timeFrequencyRegion, if the PDCCH monitoring period for the search space set with DCI format 2_4 is one slot and there is more than one PDCCH monitoring opportunity in one slot, otherwise equal to the PDCCH monitoring period; and G CI , the number of partitions, for T provided by timeGranularityforCI in timeFrequencyRegion CI symbol.

[0152] From N CI The MSB of the bit G CI The bit set has G CI A one-to-one mapping of symbol groups, where the first Each group in the group includes Symbol and remainder Each group in the group includes Symbol. The WTRU determines the symbol duration of the SCS configuration with respect to the active DL BWP where the WTRU monitors the PDCCH for DCI format 2_4 detection.

[0153] For a set of symbols, the N from the MSB of each bit set BI =N CI / G CI The bit has N BI One-to-one mapping of PRB groups, where the first Each group in the group includes And the remaining Each group in the group includes WTRU will offset RB according to frequencyRegionforCI ( start and length L RB Indicated as RIV) and according to the offsetToCarrier in FrequencyInfoUL-SIB or FrequencyInfoUL (indicating the SCS configuration of the active DL BWP carrier) The first PRB index is determined as And the number of consecutive RBs is determined as B CI =L RB , where the WTRU monitors the PDCCH for DCI format 2_4 detection.

[0154] In type 1 uplink resource allocation, the resource block assignment information indicates the size to the scheduled UE. A set of contiguously allocated non-interleaved virtual resource blocks within the effective bandwidth part of , except when DCI format 0_0 is decoded in any common search space, in which case the initial UL bandwidth part shall be used size.

[0155] The uplink type 1 resource allocation field consists of a field corresponding to the starting virtual resource block (RB start ) and the length L of the resource blocks allocated continuously RB The resource indicator value is defined as:

[0156] if but

[0157]

[0158] otherwise

[0159]

[0160] Where L RB ≥1 and should not exceed

[0161] The indication by DCI format 2_4 for the serving cell applies to PUSCH transmission or SRS transmission on the serving cell. If PUSCH transmission or SRS transmission is scheduled by DCI format, the indication by DCI format 2_4 is applicable to PUSCH transmission or SRS transmission only if the last symbol of PDCCH reception providing the DCI format is earlier than the first symbol of PDCCH reception providing DCI format 2_4. For the serving cell, the WTRU shall T CI The first symbol of the symbol is determined to be T′ from the time when the WTRU detects the end of PDCCH reception of DCI format 2_4 proc,2 The first symbol after T′ proc,2 Derived from T for PUSCH processing capability 2 [TS 38.214] proc,2 , assuming where d offsetProvided by delta_Offset, μ is the minimum SCS configuration μ between the SCS configuration of PDCCH and the scs-SpecificCarrierList provided in FrequencyInfoUL or FrequencyInfoUL-SIB UL The WTRU does not expect the corresponding symbol T proc,2 Before canceling PUSCH transmission or SRS transmission, assume that after the WTRU detects the last symbol of the CORESET of DCI format 2_4 2,1 =0.

[0162] If the PUSCH transmission has repetition type B, a WTRU detecting DCI format 2_4 for the serving cell cancels the PUSCH transmission or the actual repetition of the PUSCH transmission, or cancels the SRS transmission on the serving cell in the following cases respectively: if the transmission is a PUSCH with priority 0, if the WTRU is provided with uplinkCancellationPriority; from T CI A set of symbols in DCI format 2_4 N BI The corresponding set of bits has at least one bit value '1' and includes a symbol of a (repetition of) a PUSCH transmission or an SRS transmission; and CI The PRB group of PRB has a corresponding bit value of '1' in a bit set corresponding to a symbol group in DCI format 2_4, and includes PRBs for PUSCH transmission (repetition) or SRS transmission; wherein cancellation of PUSCH transmission (repetition) includes all symbols in a group of symbols having a corresponding bit value of '1' in DCI format 2_4, starting from the earliest symbol of PUSCH transmission (repetition); and cancellation of SRS transmission includes only symbols in one or more groups of symbols having a corresponding bit value of '1' in DCI format 2_4.

[0163] If the WTRU cancels PUSCH transmission or SRS transmission based on the indication of DCI format 2_4, the WTRU does not expect to send PUSCH or SRS on symbols including symbols of the canceled PUSCH transmission or SRS transmission scheduled by the second DCI format, where the last symbol received by the PDCCH providing the second DCI format is later than the first symbol received by the PDCCH providing DCI format 2_4.

[0164] Exemplary uplink deconfiguration Figure 3, as shown in 300. Table 1 shows an exemplary UplinkCancellation field description. Table 2 shows a CI-ConfigurationPerServingCell field description. Table 3 shows conditionally existing terms.

[0165]

[0166] Table 1

[0167]

[0168] Table 2

[0169]

[0170] Table 3

[0171] PUSCH aggregation is described herein. In NR, the PUSCH time domain resource allocation (TDRA) for data transmission is dynamically signaled in the DCI. This is useful because the portion of the timeslot available for uplink transmission can vary from slot to slot as a result of using dynamic TDD or the amount of resources used for uplink control signaling. In addition, the timeslot in which the transmission occurs also needs to be signaled as part of the time domain allocation. Although downlink data is typically sent in the same timeslot as the corresponding DCI assignment, this is typically not the case for uplink transmissions.

[0172] DCI formats 0_0 and 0_1 can be used for dynamic PUSCH time domain resource allocation. They carry a "time domain resource allocation" field of up to 4 bits, which points to a row in a lookup table of up to 16 rows, each of which provides the following parameters: slot offset K2, used to indicate the offset of the time slot used for PUSCH transmission; SLIV (jointly coded start and length indicator value), used to derive the value of the start symbol 'S' and the allocation length 'L'; and the "PUSCH mapping type" to be applied to PUSCH transmission, type A or type B, which determines the first DM-RS symbol position.

[0173] To this end, the RRC IE PUSCH-TimeDomainResourceAllocation is used to determine the time domain offset between PDCCH and PUSCH. PUSCH-TimeDomainResourceAllocationList lists up to 16 PUSCH-TimeDomainResourceAllocations. The WTRU determines the bit width of the DCI field based on the number of entries in PUSCH-TimeDomainResourceAllocationList. The DCI will indicate which configured time domain allocation the WTRU must use to fulfill the UL grant. Figure 4 , 400 shows an exemplary PUSCH-TimeDomainResourceAllocationList configuration.

[0174] In addition, the configured grants can be used to facilitate uplink transmissions without dynamic grants in order to reduce control signaling. Two types of configured grants are supported, differing in the way they are activated: configured grant type 1, where the uplink grant is provided by RRC, including activation of the grant; and configured grant type 2, where the transmission period is provided by RRC and L1 / L2 signaling is used to activate transmission.

[0175] The configured grant type 1 uses RRC signaling to set all transmission parameters, including periodicity, time offset and frequency resources and possible modulation and coding scheme for uplink transmissions. The time domain resource allocation for the configured grant type 1 is performed via RRC. PDCCH DCI 0_0 or 0_1 addressed to the CS-RNTI (configured Scheduling-RNTI) is used only for retransmissions. Once the network configures the time domain resources using RRC, the only way to change the allocation is by transmitting an RRC reconfiguration message to the WTRU.

[0176] The configured grant type 2 is similar to downlink semi-persistent scheduling. That is, RRC signaling is used to configure the periodicity, and the transmission parameters are provided as part of the activation using PDCCH. The time domain resource allocation in the configured grant type 2 is done using PDCCH DCI 0_0 or 0_1 addressed to the CS-RNTI (even for retransmissions). Once configured and activated using DCI 0_0 or 0_1, the UE periodically uses the same time domain resources until the configured grant is deactivated.

[0177] Additionally, NR supports timeslot aggregation for PUSCH transmissions, where the WTRU retransmits in consecutive timeslots (i.e., sends the same TB on multiple consecutive timeslots) without waiting for feedback from the gNB. This is beneficial in cell edge scenarios where retransmissions are more likely. Timeslot aggregation is configured via RRC signaling using the following parameters:

[0178] The pusch-AggregationFactor in the PUSCH-Config IE is used for dynamic scheduling. This field can take 2, 4 or 8 repeated values; pusch-AggregationFactor

[0179] ENUMERATED{n2,n4,n8}

[0180] The repK in the ConfiguredGrantConfig IE is used for the configured grant case. This field is mandatory and takes values ​​of 1, 2, 4 and 8. When repK>1, slot aggregation is activated; repK ENUMERATED{n1,n2,n4,n8}.

[0181] DCI format 0_2 allows enhanced flexibility in field size, which can carry up to 6 bits of "time domain resource allocation" corresponding to up to 64 rows of lookup tables in RRC. The "time domain resource allocation" field in DCI format 0_2 is used as an index into the RRC configuration table from which the time domain allocation is obtained. Each row includes at least: a time slot offset (K2), that is, a time slot relative to the time slot in which the DCI is received. In the uplink, time slot offsets from 0 to 7 can be used. The relatively large time slot offset compared to the downlink (0 to 3) is due to the need to further schedule uplink transmissions in the future in order to coexist with LTE TDD; the first OFDM symbol in the time slot in which data is transmitted (S); the duration of the transmission in terms of the number of OFDM symbols in the time slot (L).

[0182] Figure 5 , 500 shows an exemplary configuration of PUSCH-TimeDomainResourceAllocationList-16.

[0183] 3GPP also defines a default time domain resource allocation table for use in the absence of a configuration table, as illustrated in Table 4. These default tables can be used until the necessary table configuration is provided. In many cases, the default table is sufficient, in which case no other values ​​need to be configured. In addition, additional columns can be configured in the table in R16. For example, in order to better support URLLC, the number of times the transmission should be repeated can be configured. Therefore, by appropriately configuring numberOfRepetitions-r16 in the time domain resource allocation table, time slot aggregation (PUSCH repetition type A) can be indicated in a dynamic manner. Table 4 shows the default PUSCH time domain resource allocation for normal CP.

[0184]

[0185] Table 4

[0186] In addition, PUSCH repetition type B may eliminate the time gap between repetitions, and because the repetitions are performed in consecutive subslots, one slot may include more than one repetition of a transport block. For PUSCH scheduled by DCI format 0_1, if pusch-RepTypeIndicatorDCI-0-1-r16 is set to 'pusch-RepTypeB', the UE applies the PUSCH repetition type B procedure when determining the time domain resource allocation. For PUSCH scheduled by DCI format 0_2, if pusch-RepTypeIndicatorDCI-0-2-r16 is set to 'pusch-RepTypeB', the WTRU applies the PUSCH repetition type B procedure when determining the time domain resource allocation. Otherwise, the WTRU applies the PUSCH repetition type A procedure when determining the time domain resource allocation for PUSCH scheduled by PDCCH. Figure 6 , 600 shows an exemplary PUSCH configuration.

[0187] For PUSCH repetition type A, the start symbol S relative to the start of the slot and the number of consecutive symbols L allocated for PUSCH, counted from symbol S, are determined according to the start and length indicator SLIV of the index row.

[0188] If (L-1)≤7, then

[0189] SLIV=14·(L-1)+S

[0190] otherwise

[0191] SLIV=14·(14-L+1)+(14-1-S)

[0192] Where 0<L≤14-S, and

[0193] For PUSCH repetition type B, the starting symbol S relative to the start of the slot and the number of consecutive symbols L allocated for PUSCH, counted from symbol S, are provided by the startSymbol and length of the index row of the resource allocation table, respectively.

[0194] For PUSCH repetition type A, when PUSCH scheduled via DCI format 0_1 ​​or 0_2 is sent in a PDCCH with a CRC scrambled with C-RNTI, MCS-C-RNTI or CS-RNTI with NDI=1, the number of repetitions K is determined as follows: if numberOfRepetitions exists in the resource allocation table, then the number of repetitions K is equal to numberOfRepetitions; otherwise, if the WTRU is configured with pusch-AggregationFactor, then the number of repetitions K is equal to pusch-AggregationFactor; otherwise K=1.

[0195] For PUSCH transmissions with grants configured with type 1 or type 2, if numberOfRepetitions is present in the time domain resource allocation table, the number of (nominal) repetitions K to be applied to the transmitted transport block is provided by the index row in the table; otherwise K is provided by the parameter repK configured by higher layers.

[0196] For PUSCH repetition type A, in case K>1, the same symbol allocation is applied over K consecutive time slots, and PUSCH is limited to a single transmission layer. The WTRU may repeat a TB (transport block) over K consecutive time slots, applying the same symbol allocation in each time slot. The redundancy version to be applied at the nth transmission opportunity of a TB is determined according to Table 5 below, where n=0, 1, ... K-1.

[0197] For PUSCH repetition type B, after determining the invalid symbols for PUSCH repetition type B transmission for each of the K nominal repetitions, the remaining symbols are considered as potentially valid symbols for PUSCH repetition type B transmission. If the number of potentially valid symbols for PUSCH repetition type B transmission is greater than 0 for the nominal repetition, the nominal repetition consists of one or more actual repetitions, where each actual repetition consists of a contiguous set of all potentially valid symbols that can be used for PUSCH repetition type B transmission in the timeslot. Except for the case where L=1, the actual repetition of a single symbol is omitted. The WTRU may repeat a TB in an actual repetition. The redundancy version to be applied to the nth actual repetition may be determined according to Table 5 (where the count includes the omitted actual repetitions).

[0198]

[0199] Table 5

[0200] This article describes PUSCH power boosting. For 5G uplink power control, the WTRU will first estimate the amount of power required to communicate with the gNB based on its own path loss estimate (i.e., open loop power control). The gNB will then instruct the WTRU to increase or decrease transmit power, typically to meet a predetermined SINR target.

[0201] In an embodiment, the WTRU may be configured with up to three values ​​of the open-loop power control target receive power parameter P0 for the PUSCH. One of the P0 values ​​corresponds to the normal transmit power, while the other (up to two) P0 values ​​(p0-List-r16, e.g. Figure 7 , as shown in 700) is configured such that the transmit power is increased compared to normal. Which of the configured values ​​is to be used is indicated in scheduling via DCI format 0_2 (power control parameter set). In this way, the network can choose to dynamically boost the power of a high priority WTRU so that interference from other WTRUs with overlapping time-frequency allocations is less of a problem and high priority transmissions are properly received.

[0202] Dynamic power boost cannot be applied to the configured grant. It also assumes that the WTRU has available power to provide the boost, which may not be the case for limited coverage scenarios where the WTRU is already at its maximum power.

[0203] This document describes PUSCH MIMO: In NR, PUSCH supports two different MIMO schemes: codebook-based transmission and non-codebook-based transmission. When the RRC parameter txConfig is set to "codebook", the WTRU is configured with codebook-based transmission; when the RRC parameter txConfig is set to "non-codebook", the WTRU is configured with non-codebook-based transmission. For both UL MIMO schemes, each UL channel transmission is precoded with the UL DM-RS in the same way as the data. In the case of non-codebook-based UL MIMO, the way PUSCH is precoded is not specified, and the precoding itself is transparent to the gNB. In the case of codebook-based UL MIMO, the precoding follows the TPMI included in the UL grant; therefore the precoding is opaque to the gNB.

[0204] In the UL, up to rank 4 spatial multiplexing is supported using the CP-OFDM waveform. The MIMO layers are mapped to a single codeword, which means that the channel bits from the code blocks are evenly distributed across the layers. The modulation order and code rate are the same across all layers. The SNR on each layer can be different, but the single codeword arrangement ensures that the code blocks distributed across the layers will experience the same average SNR.

[0205] The basic principle of codebook-based PUSCH transmission is that the network decides the uplink transmission rank, i.e., the number of layers to be transmitted, and the corresponding precoder for transmission. The network informs the WTRU of the selected transmission rank and precoder matrix as part of the uplink scheduling grant. On the WTRU side, the precoder matrix is ​​then applied to the PUSCH transmission, thereby mapping the indicated number of layers to the antenna ports.

[0206] In order to select the appropriate rank and corresponding precoder matrix, the network needs to estimate the channel between the WTRU antenna ports and the corresponding network receive antennas. To achieve this, a WTRU configured for codebook based transmission of PUSCH will typically be configured for transmission of at least one multi-port SRS. Based on measurements of the configured SRS, the network can probe the channel and determine the appropriate rank and precoder matrix. Codebook based precoding is typically used when uplink downlink reciprocity does not hold, i.e., when uplink measurements are required to determine the appropriate uplink precoding.

[0207] Compared to codebook-based precoding, non-codebook-based precoding is based on WTRU measurements and network precoder indications. Based on downlink measurements, such as measurements on the configured CSI-RS, the WTRU selects an uplink multi-layer precoder that it deems appropriate. Therefore, non-codebook-based precoding is based on the assumption of channel reciprocity, i.e., the UE can obtain detailed knowledge of the uplink channel based on downlink measurements.

[0208] In the case of non-codebook based UL MIMO, the WTRU autonomously decides the precoding to use for each SRS port / resource. The SRI in the PUSCH scheduling grant selects a subset or all of these SRS resources for the transmission of PUSCH, and the WTRU then sends one MIMO layer for each indicated SRS resource. The WTRU then sends the PUSCH layer in the same way as it sent the indicated SRS resource in the most recent SRS resource transmission.

[0209] The following implementation scheme is described to ensure robust and efficient PUSCH transmission and reception when coexisting with RADAR: De-schedule resources for PUSCH transmission and reception to avoid time / frequency resources that will be subject to interference from RADAR. Dynamic triggering of PUSCH aggregation of UE will be subject to interference from RADAR. Power boosting of PUSCH transmission of UE will be subject to interference from RADAR.

[0210] The present invention describes canceled resources, including uplink preemption between WTRUs that cancel low priority transmissions. A high priority uplink transmission may be scheduled over a low priority transmission already in progress by another WTRU. A Cancellation Indicator (CI) is a bitmap that indicates a set of OFDM symbols and resource blocks that should be canceled for a transmission. The interpretation of the bitmap is configurable so that each bit represents one or more OFDM symbols in the time domain and a set of RBs within a bandwidth portion. The Cancellation Indicator is sent using DCI format 2_4 scrambled with CI-RNTI.

[0211] In order to coexist with RADAR, the gNB may cancel time / frequency resources that will be subject to interference from RADAR. The cancelled resources may correspond to continuous or non-contiguous time / frequency resources. Upon receiving the cancellation indicator, the WTRU may stop sending any PUSCH or SRS (but not UL transmissions related to PUCCH and RACH) that overlap (partially) with any of the cancelled resources (more specifically, the WTRU stops transmission starting from the indicated symbol and does not resume afterwards). The cancellation must occur within a certain minimum time before the start of PUSCH (or SRS) transmission to allow the UE to properly process and take into account the cancellation indicator.

[0212] In an embodiment, the gNB may use information characterizing the operation of the RADAR to determine the revoked resources. The gNB 820 may receive this information from an external entity 830, such as Figure 8 8, which also shows a WTRU 810. Alternatively, the gNB may perform measurements to determine information characterizing the operation of the RADAR. And in yet another alternative, the measurements performed by the gNB may be used in combination with information provided by an external entity to characterize the operation of the RADAR.

[0213] Silent periods may be used to allow RADAR measurements to be performed by external entities and / or the gNB. In one example, the silent periods may be implemented by the gNB as scheduling gaps; i.e., the gNB will not schedule UL / DL transmissions during the period when measurements are performed.

[0214] The determination of the cancelled resources may be based on time / frequency information characterizing the operation of the RADAR; for example, frequency, bandwidth, and period. For example, the frequency and bandwidth of the RADAR burst may be used to determine the frequency resources allocated as the cancelled resources; and the start time and duration of the RADAR burst may be used to determine the symbols allocated as the cancelled resources over the already scheduled PUSCH resources. Fig. 9 The resources are shown to be cancelled in a scenario where RADAR is operating, so that the PUSCH transmission 910 will be interfered during symbols 5 and 6, 920 and partially overlap with the allocated PUSCH bandwidth.

[0215] The gNB may consider the direction of PUSCH transmission when determining whether the cancelled resources are needed to coexist with RADAR. For example, resources may be cancelled only for PUSCH transmission in the direction that will be interfered by RADAR.

[0216] In one example, the RADAR AOA information is used by the gNB to determine the spatial direction of the RADAR interference in the cell. The gNB will then use the cancelled resources 930 to stop PUSCH transmissions from UEs located in the area of ​​the cell that will be subject to RADAR interference.

[0217] The gNB may determine the effective "communication" direction of the WTRU based on the spatial direction of the SSB or CSI-RS used to receive the PUSCH. Alternatively, the UE's position may be determined by the gNB using a positioning algorithm, may be (pre-)configured in the gNB via an Operation, Administration, and Maintenance (OAM) interface, or may be reported by the WTRU to the gNB.

[0218] The gNB may also consider the interference level when determining whether the cancelled resources need to coexist with the RADAR. For example, resources may be cancelled only when the interference from the RADAR is above a threshold. The threshold may be preconfigured, dynamically determined, or provided by an external entity.

[0219] Different thresholds may be defined and selected by the gNB. For example, a set of thresholds may be defined based on MCS or modulation order. The gNB may then select an appropriate threshold based on the MCS or modulation order used for the PUSCH. In other embodiments, the threshold may be selected based on characteristics of the data, characteristics of the service, and / or characteristics of the device; for example, the QoS of the data sent on the PUSCH, the service provided to the device, the device type.

[0220] The (re)configuration defined by the cancelled resource bitmap can be done using broadcast or dedicated higher layer signaling. For the scenario using broadcast signaling, the UE can be made aware of the change in the cancelled resource configuration by setting the systemInfoModification bit of the short message. Then, at the start of the next modification period, the WTRU can use the SI acquisition procedure to obtain the new cancelled resource bitmap configuration. The bitmap in DCI format 2_4 can be used to enable or disable the cancelled resources based on whether the WTRU will be interfered with by the RADAR and whether there is a PUSCH transmission scheduled for the WTRU.

[0221] This document describes the adaptation of cancelled resources for timing drift. Time synchronization cannot be assumed between the gNB and the RADAR, and thus, the symbol pattern affected by the RADAR interference may drift over time. In an implementation, the gNB can reset the bitmap of the cancelled resources to the symbols that are affected by the RADAR interference and drift over time. Fig. 10A Illustrates an example where for t0 ≤ t < t1, symbol 6 of the cancelled PUSCH resource 1030 is affected by the RADAR interference 1020. The PUSCH resources 1010 for symbols 0 - 5 are not affected during this time frame. Fig. 10B Illustrates an example where for t1 ≤ t < t2, symbols 5 and 6 are affected by the interference 1020. Fig. 10C Illustrates an example where for t2 ≤ t, symbol 5 is affected by the interference 1020. In these examples, it is assumed that the duration of the RADAR interference is less than or equal to the duration of the symbol. However, the same concept can also be applied to scenarios where the duration of the RADAR interference is greater than the duration of the symbol.

[0222] The reset of the cancelled resources can be done using the bitmap in the scheduling DCI format 2_4 to enable or disable the cancelled resources based on whether the WTRU will be interfered with by the RADAR and whether there is a PUSCH transmission scheduled for the WTRU.

[0223] This document describes PUSCH aggregation. To coexist with the RADAR, the gNB can configure PUSCH aggregation for the WTRUs that will be interfered with by the RADAR. When the RADAR interference exceeds a threshold, the configuration of PUSCH aggregation can be triggered for the WTRU. This threshold can be preconfigured, determined dynamically, or provided by an external entity. Different thresholds can be defined and selected by the gNB. For example, a set of thresholds can be defined based on the MCS or modulation order. Then, the gNB selects an appropriate threshold based on the MCS or modulation order used for the PUSCH. In other implementations, the threshold can be selected based on the characteristics of the data, the characteristics of the service, and / or the characteristics of the device; for example, the QoS of the data transmitted on the PUSCH, the service provided to the device, the device type.

[0224] The gNB may use information characterizing the operation of the RADAR to determine the level of interference. In one example, the RADAR AOA information is used by the gNB to determine the spatial direction of the RADAR interference in the cell. The gNB may then configure PUSCH aggregation for WTRUs located in areas of the cell that will be subject to RADAR interference exceeding a threshold. The gNB may determine the effective "communication" direction of the WTRU based on the spatial direction of the SSB or CSI-RS used to receive the PUSCH. Alternatively, the location of the WTRU may be determined by the gNB using a positioning algorithm, may be (pre-)configured in the gNB via an OAM interface, or may be reported to the gNB by the WTRU.

[0225] In an embodiment, the gNB may consider the interference level when determining numberOfRepetitions / pusch-AggregationFactor / repK for PUSCH aggregation. For example, a threshold may be used to define numberOfRepetitions within a range of interference levels as shown in Table 6.

[0226] Interference level numberOfRepetitions <![CDATA[Interference level < threshold 1]]> 1 <![CDATA[Threshold 1 ≤ interference level < Threshold 2]]> 2 <![CDATA[Threshold 2 ≤ interference level < Threshold 3]]> 4 <![CDATA[Threshold 3 ≤ interference level < Threshold 4]]> 8 <![CDATA[Threshold 4 ≤ interference level]]> 16

[0227] Table 6

[0228] Broadcast or dedicated higher layer signaling may be used for (re)configuration of PUSCH aggregation. Alternatively, DCI may be used to dynamically configure PUSCH aggregation. For example, DCI format 0_2 may be used to dynamically configure an index pointing to a specific numberOfRepetitions value in the RRC-configured time domain resource allocation table to be used for a given PUSCH transmission.

[0229] The PUSCH aggregation discussed so far is applied in the time domain with a single layer transmission. In rank>1 rich scattering environments (and / or dual polarization), multi-layer MIMO transmission (codebook-based or non-codebook-based) is possible. In this scenario, multiple redundancy versions can be sent simultaneously on multiple layers (called PUSCH layer aggregation) while using the same HARQ process to improve HARQ efficiency rather than system capacity. For non-codebook-based UL MIMO, the network can exclude SRI, which is most significantly affected by RADAR.

[0230] In one embodiment, the channel bits of each code block (CB) 1110 of multiple redundancy versions are evenly distributed over the MIMO layers, such as Fig.11A (rank = 2), Fig. 11B (rank = 3) and Fig. 11C (rank=4) CBG indicates code block group.

[0231] Fig.11A Codewords rv0 1114 and rv2 1116 are shown to be serially mapped 1110 to layer 0 1120 and layer 1 1130 .

[0232] Fig. 11B Codewords rv0 1114 , rv2 1116 , and rv3 1118 are shown as being serially mapped 1110 to layer 0 1120 , layer 1 1130 , and layer 2 1140 .

[0233] Fig. 11C Codewords rv0 1114 , rv2 1116 , and rv3 1118 are shown as well as rv1 being serially mapped 1110 to layer 0 1120 , layer 1 1130 , layer 2 1140 , and layer 3 1150 .

[0234] The SNR on each layer may be different, but the code blocks distributed over the layers will experience the same average SNR.

[0235] In another embodiment, codewords associated with different redundancy versions are mapped to different MIMO layers in a parallel manner, such as Fig. 12A (rank = 2), Fig. 12B (rank = 3) and Fig. 12C (rank=4). In this embodiment, codewords associated with different redundancy versions may experience different SNRs.

[0236] Fig. 12A Shown is a codeword rv0 1210 mapped to layer 0 1220 and a codeword rv2 mapped to layer 1 1230. Individual code blocks are labeled 1211.

[0237] Fig. 12B Codeword rv0 1210 mapped to layer 0 1220 , codeword rv2 mapped to layer 1 1230 , and codeword rv3 1214 mapped to layer 2 1240 are shown.

[0238] Fig. 12C Codeword rv0 1210 mapped to layer 0 1220 , codeword rv2 mapped to layer 1 1230 , codeword rv3 1214 mapped to layer 2 1240 , and codeword rv1 1216 mapped to layer 3 1250 are shown.

[0239] In an embodiment, the network may trigger PUSCH layer aggregation via a scheduling grant. For example, a "layer aggregation" bit may be defined in DCI format 0_1 ​​and format 0_2. When the layer aggregation bit is set to 0, the redundancy version is determined by Table 5 (as shown above). On the other hand, when the layer aggregation bit is set to 1, if the uplink MIMO rank is equal to 2, 3, or 4, respectively, the redundancy version will be determined by Table 7, Table 8, or Table 9. Note that in the case where time domain repetition is not applied, the redundancy version for layer aggregation will be determined in the redundancy version table for n=0.

[0240]

[0241] Table 7

[0242]

[0243]

[0244] Table 8

[0245]

[0246] Table 9

[0247] In an embodiment, a "layer sub-aggregation bit" may be further defined for rank>2 to subdivide the number of layers to be aggregated and facilitate the trade-off between reliability and capacity. For example, if the layer sub-aggregation bit is set to 1, the redundancy version may be determined by Table 10 or Table 11 if the downlink MIMO rank is equal to 3 or 4, respectively. Note that the "layer sub-aggregation bit" is transmitted only when rank>2, and the "layer aggregation bit" is set to 1.

[0248]

[0249] Table 10

[0250]

[0251] Table 11

[0252] In addition to the above-mentioned bundled transmission, layer aggregation can also be applied in conventional HARQ processes. For example, the network transmits redundancy version 0 during the initial transmission and uses layer aggregation to retransmit multiple redundant versions of the erroneous CBG (assuming that rank>1 is available during retransmission) to enhance reliability and reduce latency. In principle, if it is considered beneficial, the network can also use both layer aggregation and repetition to transmit multiple redundant versions of the erroneous CBG. The WTRU shall inform the network of its ability to support PUSCH layer aggregation, as illustrated by the following information message in Table 12.

[0253]

[0254] Table 12

[0255] This article describes PUSCH power boosting. One way to reduce interference to RADAR is for the gNB to avoid using time-frequency resources when the RADAR is actively transmitting or listening to return pulses. This is called PRB blanking. Based on an estimate of the RADAR rotation timing and the power spectral density (PSD), the time-frequency interference area is evaluated and the gNB scheduler avoids allocating the corresponding PRBs for uplink or downlink traffic.

[0256] On the other hand, PRB blanking may result in a decrease in uplink cell throughput due to reduced radio resources. To this end, the PUSCH transmit power can be boosted to mitigate the impact on uplink cell throughput after PRB blanking is triggered, without the risk of harming RADAR (because the power boost is performed outside the RADAR bandwidth). In an embodiment, PUSCH power boost can also be triggered without PRB blanking, as long as there is no risk of interference from the 5G WTRU to the RADAR (while RADAR interference to 5G is still significant), such as when the RADAR is far enough away, or when the main beam of the RADAR is not pointed at the 5G system.

[0257] In an embodiment, when the RADAR interference exceeds a threshold, a power boost may be triggered for the WTRU. The threshold may be preconfigured, dynamically determined, or provided by an external entity. Different thresholds may be defined and selected by the gNB. For example, a set of thresholds may be defined based on MCS or modulation order. The gNB then selects an appropriate threshold based on the MCS or modulation order used for the PUSCH. In further embodiments, the threshold may be selected based on characteristics of the data, characteristics of the service, and / or characteristics of the device; for example, the QoS of the data sent on the PUSCH, the service provided to the device, and the type of device. The gNB may use information characterizing the operation of the RADAR to determine the level of interference. In one example, the RADAR AOA information is used by the gNB to determine the spatial direction of the RADAR interference in the cell. The gNB will then use power boosting for WTRUs located in areas of the cell that will be subject to RADAR interference exceeding the threshold.

[0258] The gNB may determine the effective "communication" direction of the WTRU based on the spatial direction of the SSB or CSI-RS used to receive the PUSCH. Alternatively, the position of the WTRU may be determined by the gNB using a positioning algorithm, may be (pre-)configured in the gNB via the OAM interface, or may be reported by the WTRU to the gNB.

[0259] For WTRUs that support power boosting, power boosting may be performed explicitly by using a target received power P0 higher than the nominal P0 value for outer loop power control via dynamic scheduling. In this regard, the SINR target in the gNB for inner loop power control also needs to be increased accordingly. For WTRUs that do not support power boosting capability, the P0 value may be updated via RRC signaling with the SINR target increased. Note that since R16 supports configuration of only two additional P0 values, more than two values ​​may be considered to provide further flexibility.

[0260] In one embodiment of the present disclosure, the gNB may be configured to perform the following instructions: receiving information characterizing the operation of the RADAR; based on the received information, determining time / frequency resources that may be subject to interference from the RADAR; based on the determined time / frequency resources, configuring the WTRU with a definition of a bitmap of cancelled time / frequency resources that should not be used for PUSCH transmission; identifying the WTRU to which the cancelled resources need to be applied and scheduling the cancelled resources to prohibit the identified WTRU from using the cancelled resources for PUSCH transmission, regardless of any previous scheduling grant. In another aspect of this embodiment: the information characterizing the operation of the RADAR may include: angle of arrival (AOA), frequency, bandwidth (BW), etc. Wherein configuring the WTRU with the cancelled set of time / frequency resources further includes: determining whether the WTRU will be subject to interference from the RADAR based on the location of the WTRU in the cell. In another aspect of this embodiment, determining the communication direction of the WTRU may be based on the spatial direction of the SS / PBCH block (SSB) or channel state information reference signal (CSI-RS) received for PUSCH. In another aspect of this embodiment, determining the time / frequency resources that may be subject to interference from the RADAR may also include determining whether the interference from the RADAR is above a threshold, and in addition, the modulation and coding scheme (MCS) of the PUSCH may be used to select a threshold from a threshold set based on the MCS. In another aspect of this embodiment, the canceled time / frequency resource set corresponds to an RB in one or more symbols allocated for PUSCH transmission. In another aspect of this embodiment, the definition of the bitmap of the canceled time / frequency resources is configured via broadcast or dedicated higher layer signaling, and is dynamically enabled / disabled via a bitmap in the downlink control information (DCI). In another aspect of this embodiment, the reconfiguration of the canceled time / frequency resources is triggered in response to a timing drift between the gNB and the RADAR.

[0261] In one embodiment of the present disclosure, the gNB may be configured to execute the following instructions: configure a time domain resource allocation table to include one or more repetition options for PUSCH aggregation; receive information characterizing the operation of the RADAR; based on the received information, determine the time / frequency resources that may be subject to interference from the RADAR; determine the rank of the PUSCH transmission. If the rank>1, determine whether to include layer aggregation to combat RADAR interference; determine the modulation order and code rate of the PUSCH transmission; determine the RB set to be allocated to the WTRU for PUSCH transmission; determine the PUSCH aggregation (repetition) factor to be used to overcome interference from the RADAR; and schedule the WTRU to send PUSCH using PUSCH time domain repetition and / or layer aggregation. In another aspect of this embodiment, the information characterizing the operation of the RADAR may include: AOA, frequency, BW, etc. In another aspect of this embodiment, determining the RB set including the time / frequency resources that may be subject to interference from the RADAR also includes determining whether the WTRU will be subject to interference from the RADAR based on the location of the WTRU in the cell. In another aspect of this embodiment, the effective communication direction of the WTRU is determined based on the spatial direction of the SSB or CSI-RS used to receive the PUSCH. In another aspect of this embodiment, determining the time / frequency resources that may be subject to interference from the RADAR also includes determining whether the interference from the RADAR exceeds a threshold. In another aspect of this embodiment, the MCS of the PUSCH can be used to select a threshold from a threshold set based on the MCS. In another aspect of this embodiment, the degree of PUSCH aggregation (including time domain repetition and / or layer aggregation) is determined based on one or more of the following: the MCS of the PUSCH; and / or interference from the RADAR that exceeds the threshold; and / or the quality of service (QoS) of the data sent on the PUSCH. In another aspect of this embodiment, the PUSCH aggregation / repetition factor can be configured via broadcast or dedicated higher layer signaling, and the time domain repetition and / or layer aggregation of the PUSCH can be dynamically enabled / disabled via DCI.

[0262] In one embodiment of the present disclosure, the gNB may be configured to perform the following instructions: receive information characterizing the operation of the RADAR; based on the received information, determine the time / frequency resources that may be subject to interference from the RADAR; determine the set of RBs to be allocated to the WTRU for PUSCH transmission; determine whether the WTRU will require a power boost for PUSCH transmission to overcome interference from the RADAR and / or mitigate cell capacity reduction due to PRB blanking; and notify the WTRU to perform PUSCH transmission using the power boost as identified. In another aspect of this embodiment, the information characterizing the operation of the RADAR may include: AOA, frequency, BW, etc. In another aspect of this embodiment, determining whether the resources allocated to the WTRU for PUSCH transmission will require a power boost to overcome interference from the RADAR and / or mitigate cell capacity reduction due to PRB blanking also includes determining whether the WTRU will be subject to interference from the RADAR based on the location of the WTRU in the cell. In another aspect of this embodiment, the effective communication direction of the WTRU is determined based on the spatial direction of the SSB or CSI-RS used to receive the PUSCH. In another aspect of this embodiment, determining the time / frequency resources that may be subject to interference from RADAR also includes: determining that the interference from RADAR exceeds a threshold. In another aspect of this embodiment, the MCS of the PUSCH can be used to select a threshold from a threshold set based on the MCS. In another aspect of this embodiment, the PUSCH target received power P0 set can be configured via broadcast or dedicated higher layer signaling and dynamically selected via dedicated DCI signaling. In another aspect of this embodiment, WTRU-group common signaling can be used to select the target received power p0 of the PUSCH for the WTRU group. In another aspect of this embodiment, MAC-CE can be used to select the target received power p0 of the PUSCH.

[0263] Fig.13is a flow chart illustrating an exemplary process implemented by a wireless transmit / receive unit (WTRU) according to an embodiment disclosed herein. At 1310, the WTRU sends a message notifying the network of PUSCH MIMO layer aggregation capabilities. At 1312, the WTRU receives a MIMO rank. At 1314, the WTRU receives an indication of using PUSCH MIMO layer aggregation (with or without sub-aggregation). At 1316, the WTRU determines a PUSCH layer aggregation level based on the MIMO rank and possible sub-aggregation indication. At 1318, the WTRU sends multiple redundant versions of a PUSCH codeword including one or more code blocks based on the PUSCH layer aggregation level. The method of claim 1, wherein for each redundant version, each code block of the PUSCH codeword is evenly distributed across multiple MIMO layers. In another embodiment, code blocks for different redundant versions of the codeword are mapped to different MIMO layers. In another embodiment, the indication of using PUSCH MIMO layer aggregation is made by a DCI signaling bit. In another embodiment, PUSCH MIMO layer aggregation is performed in a HARQ process. In another embodiment, the indication of using PUSCH MIMO layer aggregation includes an indication of using sub-aggregation. In another embodiment, the PUSCH layer aggregation level is determined based on the MIMO rank and the sub-aggregation indication. In another embodiment, the PUSCH layer aggregation level is further based on the interference level. In another embodiment, the interference level is related to the RADAR signal.

[0264] Although features and elements are described above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with 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 (sent 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 built-in hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

1. A method implemented by a wireless transmit / receive unit (WTRU), comprising: Send a message to inform the network of the PUSCH MIMO layer aggregation capability; Receive MIMO rank; receiving an indication to use PUSCH MIMO layer aggregation; determining a PUSCH layer aggregation level based on the MIMO rank; and Multiple redundancy versions of a PUSCH codeword including one or more code blocks are transmitted based on the PUSCH layer aggregation level.

2. The method according to claim 1, wherein for each redundancy version, each code block of the PUSCH codeword is evenly distributed across multiple MIMO layers. 3 . The method of claim 1 , wherein the code blocks for different redundancy versions of the codeword are mapped to different MIMO layers.

4. The method according to any one of claims 1 to 3, wherein the indication of using PUSCH MIMO layer aggregation is made by a DCI signaling bit.

5. The method according to any one of claims 1 to 4, wherein PUSCH MIMO layer aggregation is performed in a HARQ process.

6. The method according to any one of claims 1 to 5, wherein the indication of using PUSCH MIMO layer aggregation comprises an indication of using sub-aggregation. 7 . The method of claim 6 , wherein the PUSCH layer aggregation level is determined based on the MIMO rank and the sub-aggregation indication.

8. The method according to any one of claims 1 to 7, wherein the PUSCH layer aggregation level is further based on an interference level.

9. The method of claim 8, wherein the interference level is related to a RADAR signal.

10. A wireless transmit / receive unit (WTRU), comprising: Transmitter; Receiver; and A processor, the processor communicating with the transmitter and the receiver, the processor and the transmitter or the receiver being configured to: Send a message to inform the network of the PUSCH MIMO layer aggregation capability; Receive MIMO rank; receiving an indication to use PUSCH MIMO layer aggregation; determining a PUSCH layer aggregation level based on the MIMO rank; and Multiple redundancy versions of a PUSCH codeword including one or more code blocks are transmitted based on the PUSCH layer aggregation level.

11. The WTRU of claim 10, wherein for each redundancy version, each code block of the PUSCH codeword is evenly distributed across multiple MIMO layers.

12. The WTRU of claim 10, wherein the code blocks for different redundancy versions of the codeword are mapped to different MIMO layers.

13. The WTRU of any one of claims 10 to 12, wherein the indication of using PUSCH MIMO layer aggregation is made by a DCI signaling bit.

14. The WTRU of any one of claims 10 to 13, wherein PUSCH MIMO layer aggregation is performed in a HARQ process.

15. The WTRU of any one of claims 10 to 14, wherein the indication to use PUSCH MIMO layer aggregation comprises an indication to use sub-aggregation.

16. The WTRU of claim 15, wherein the PUSCH layer aggregation level is determined based on the MIMO rank and the sub-aggregation indication.

17. The WTRU of any one of claims 10 to 16, wherein the PUSCH layer aggregation level is further based on an interference level.

18. The WTRU of claim 17, wherein the interference level is related to a RADAR signal.

Images