Frequency bundling transmission (FBT) method for ultra-reliable low latency communication (URLLC) system

Abstract

Methods, devices, and systems for mitigating the impact of high power narrowband interference on hybrid automatic repeat request (HARQ) performance in URLLC systems. In a first aspect, this application relates to implementation of frequency bundled transmissions (FBT) that may enable a device to transmit different individual redundancy versions (RVs) of the same uplink data for multiple preconfigured frequency resources simultaneously or near simultaneously. In a second aspect, the application relates to implementation of FBT with frequency domain repetition, which may enable a device to transmit a redundant version bundle of the same uplink data simultaneously or near simultaneously on multiple pre-configured frequency resources.

Description

[0001] Related applications This application claims the benefit and priority of U.S. Provisional Patent Application No. 63 / 456,294, filed March 31, 2023, the entire contents of which are incorporated herein by reference. Background Technology

[0002] Operating cellular communication systems on frequency bands shared with other systems, such as airborne radar, can lead to interference and impaired functionality of critical systems. Mitigation measures may increase transmission and processing latency, which may not be suitable for many implementations, such as Ultra-Reliable Low-Latency Communications (URLLC) applications. Summary of the Invention

[0003] This document describes implementations of systems and methods for mitigating the impact of high-power narrowband interference on the performance of Hybrid Automatic Repeat Request (HARQ) in URLLC systems. In a first aspect, this application relates to an implementation of Frequency Bundled Transmission (FBT), which enables devices to transmit different individual redundant versions (RVs) of the same uplink data on multiple pre-configured frequency resources simultaneously or nearly simultaneously. In a second aspect, this application relates to an implementation of FBT with frequency domain repetition, which enables devices to transmit bundles of redundant versions of the same uplink data simultaneously or nearly simultaneously on multiple pre-configured frequency resources.

[0004] These solutions can significantly reduce latency in URLLC applications that include one-shot decoding. In one-shot decoding, multiple redundant versions are correctly decoded in a single time instance to account for the correct decoding of the original transmitted data. FBT implementations can be advantageous for use cases that require increased reliability while maintaining bandwidth to support multiple users, such as transportation applications. FBT implementations with frequency domain repetition can be advantageous for use cases that require maximum reliability but have no major bandwidth constraints, such as remote surgery, because this approach can potentially account for multiple one-shot decoding opportunities in each transmission instance. Attached Figure Description

[0005] A more detailed understanding can be obtained from the following description, given by way of example in conjunction with the accompanying drawings, wherein the same reference numerals in the drawings indicate the same elements, and wherein: Figure 1A This is a system diagram illustrating an example communication system in which one or more of the disclosed embodiments may be implemented; Figure 1B This illustrates that, according to an embodiment, it is possible to Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) used within a communication system shown; Figure 1C This illustrates that, according to an embodiment, it is possible to Figure 1A The system diagram shows an example radio access network (RAN) and an example core network (CN) used within the communication system shown. Figure 1D This illustrates that, according to an embodiment, it is possible to Figure 1A The system diagram shows another example RAN and another example CN used in the communication system shown; Figure 2A This is a diagram based on some implementations of time-domain resource allocation; Figure 2B This is a diagram of an embodiment of time-domain resource allocation with enabled time-slot aggregation; Figure 2C This is a diagram of an embodiment of time-domain resource allocation with disabled slot aggregation; Figure 2D This is a table illustrating the implementation of resource allocation types in the downlink control information (DCI) format; Figure 2E This is a diagram based on examples of frequency domain resource allocation type 0 implemented by some entities; Figure 2F This is a diagram based on some implementations of frequency domain resource allocation type 2; Figure 3A This is an illustration of an example of frequency-bundled transmission across multiple resource block groups based on some implementations; Figure 3B This is an illustration of another example of frequency-bundled transmission across multiple resource block groups based on some implementation; Figure 3C This is an example table of various transmission timings and redundant versions of frequency resources based on frequency bundled transmissions on multiple resource block groups; Figure 3D It is a diagram based on some implementations of frequency bundling transmission with frequency wrap-around; Figure 3E This is an illustration based on some implementations of frequency-bundled transmission with frequency domain repetition; Figure 3F These are illustrations based on examples of frequency-bundled transmissions with frequency domain repetition and frequency shift; and Figure 4 It is a flowchart based on some implemented methods for frequency-bundled transmission. Detailed Implementation

[0006] With the recent ability of cellular communication systems to operate on new shared frequency bands, interference between these systems and other non-cooperative systems such as airborne radar has become a major problem. To mitigate these and other issues, dynamic spectrum sharing techniques can be used to enable radar and cellular systems to coexist. Radar signal characteristics, such as high transmitter peak power, narrow bandwidth, and periodicity, as well as the sensitive design of radar receivers, are likely important considerations. Furthermore, interference from radar can potentially degrade the performance of modern commercial wireless systems that rely on low latency and high throughput. This problem is particularly critical for latency-sensitive use cases such as Ultra-Reliable Low-Latency Communication (URLLC), where conventional interference mitigation methods are not suitable. For example, feedback for uplink (UL) transmissions on the Physical Uplink Shared Channel (PUSCH) can be carried on subsequent UL licenses, requiring increased transmission and processing latency.

[0007] Such mechanisms do not meet the latency requirements of URLLC. PUSCH slot aggregation can be used to enable Radio Transport Receiver Units (WTRUs), User Equipment (UEs), or other devices to transmit the same transport block on a pre-configured number of consecutive slots without waiting for Hybrid Automatic Repeat Request (HARQ) feedback. While this can help reduce latency, it may not be sufficient because retransmissions still occur sequentially in time. For example, if interfering transmissions are longer than the allocated slots (or have a periodicity that partially or completely overlaps with retransmissions), all transmissions may fail. This problem can be particularly critical for URLLC because transmissions can occur at the sub-slot level.

[0008] Therefore, this disclosure relates to systems and methods for mitigating the impact of high-power narrowband interference on HARQ performance in URLLC. A base station or other device can detect the presence of an interference source and notify the WTRU or other device to simultaneously transmit different redundant versions of the same uplink data on multiple frequency resources. In a first aspect, this disclosure relates to the implementation of Frequency Bundled Transmission (FBT), which enables the WTRU or other device to simultaneously transmit different individual redundant versions (RVs) of the same uplink data on multiple pre-configured frequency resources. Unlike PUSCH slot aggregation, which allows the base station to signal to the WTRU the time separation between different RVs, the implementation of FBT allows the base station or other device to signal to the WTRU the frequency separation between different simultaneous RVs. Pre-configured frequency shifts and time shifts between transmission instances can be applied to maximize data transmission reliability and minimize latency. Frequency wrap-around can be implemented to allow FBT implementation to operate at the lower edge of the available frequency band.

[0009] In a second aspect, this disclosure relates to an implementation of a frequency-domain repetitive FBT that enables a WTRU or other device to simultaneously transmit redundant versions (RV) bundles (e.g., {RV2, RV3, RV1, RV0} of the same uplink data on multiple pre-configured frequency resources. The base station or other device can signal the frequency separation between the RV bundles to the WTRU via parameters such as the J2 offset parameter. Time shifts and pre-configured frequency shifts between transmission instances can be applied to maximize data transmission reliability and minimize latency. Frequency wrap-around can be implemented to allow the FBT to operate at the lower edge of the available frequency band.

[0010] In some implementations, the WTRU or other devices may inform the network whether it supports FBT and / or has FBT with frequency domain repetition as part of its WTRU capability message. The network may optionally enable or disable these features for the WTRU via Radio Resource Control (RRC) signaling based on the WTRU capabilities and network requirements. If the WTRU indicates that it does not support these solutions, in some implementations, the network may use legacy behavior for all PUSCH transports, as described in 3GPP TS 38.214 Release 17.1.0, which is incorporated herein by reference.

[0011] Implementations of these systems and methods can significantly reduce latency in URLLC applications using “one-shot” decoding. In one-shot decoding, sufficient redundant versions are correctly decoded within a single time instance to account for the correct decoding of the original transmitted data. Implementations of FBT can be a suitable solution for use cases requiring increased reliability while maintaining bandwidth to support multiple users, such as transportation applications. Implementations of FBT with frequency domain repetition may be beneficial for use cases requiring maximum reliability but without major bandwidth constraints, such as remote surgery, as this approach can potentially account for multiple one-shot decoding opportunities in each transmission instance.

[0012] For reference, this article uses various abbreviations and acronyms, for example, as follows: 3GPP Third Generation Partnership Project 5G 5th generation ACKA confirmed BWP bandwidth portion CG configuration authorization or cell group CP cyclic prefix CRC Cyclic Redundancy Check DCI Downlink Control Information DL downlink DM-RS demodulation reference signal eMBB Enhanced Mobile Broadband FBT Frequency Bundled Transmission gNB NR node B HARQ Hybrid Automatic Repeat Request IM Interference Measurement LTE, for example, from 3GPP LTE R8 and above Long Term Evolution. MAC Media Access Control MCS modulation and coding scheme MIB (Master Information Block) MIMO (Multiple Input Multiple Output) NACK (Negative) NAS Non-Access Layer NR New Radio OFDM (Orthogonal Frequency Division Multiplexing) PDCCH (Physical Downlink Control Channel) PDU (Packet Data Unit) PHY physical layer PO paging timing PUCCH (Physical Uplink Control Channel) PUSCH Physical Uplink Shared Channel RA (Random Access) RACH Random Access Channel RADAR Radio Direction and Ranging RAR Random Access Response RB resource block RBG resource block group RE Resource Elements RF radio front end RNTI Radio Network Identifier RNA RAN Notification Region RO RACH timing RRC Radio Resource Control RS reference signal RV Redundant Version SCS Subcarrier Spacing SIB System Information Blocks (e.g., SIB1, SIB2, etc.) TB transfer block TTI Transmission Time Interval UE User Equipment UL uplink URLLC: Ultra-Reliable and Low-Latency Communication WLAN (Wireless Local Area Network) and related technologies (IEEE 802.1 domain) WTRU Wireless Transmitter / Receiver Unit Before discussing the implementations and embodiments of the systems and methods discussed herein, it may be helpful to briefly discuss embodiments of communication systems and devices that can be used with these systems and methods.

[0013] Figure 1A This is a diagram illustrating an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multiple access system providing content such as voice, data, video, messaging, broadcasting, etc., to multiple wireless users. The communication system 100 enables multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero Tail Unique Word Discrete Fourier Transform Spread Spectrum OFDM (ZT-UW-DTS-S-OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), and the like.

[0014] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112. However, it will 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. As examples, any of WTRUs 102a, 102b, 102c, and 102d may be referred to as a Station (STA), configured to transmit and / or receive wireless signals, and may include User Equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, and the like. Any of WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0015] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106, the Internet 110, and / or other networks 112. As an example, base stations 114a and 114b may be base transceiver stations (BTS), Node Bs, eNode Bs (eNBs), home Node Bs, home eNode Bs, next-generation Node Bs such as gNode Bs (gNBs), new radio (NR) Node Bs, site controllers, access points (APs), wireless routers, and the like. Although each of base stations 114a and 114b is depicted as a single element, it will be appreciated that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

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

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

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

[0019] In the embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which can use Long Term Evolution (LTE) and / or LTE-A Advanced (LTE-A) and / or LTE-A Pro Advanced (LTE-A Pro) to establish air interface 116.

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

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

[0022] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as IEEE 802.11 (i.e., WiFi), IEEE 802.16 (i.e., Global Microwave Access Interoperability (WiMAX)), CDMA2000, CDMA2000 3X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate Evolution of GSM (EDGE), GSM EDGE (GERAN), and the like.

[0023] Figure 1ABase station 114b can be, for example, a wireless router, a home node B, a home eNode B, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a commercial location, home, vehicle, campus, industrial facility, air corridor (e.g., for drone use), road, and the like. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In another embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114b can have a direct connection to the Internet 110. Therefore, it is not required that base station 114b access the Internet 110 via CN 106.

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

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

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

[0027] Figure 1B This is a system diagram illustrating example WTRU 102. (See diagram below.) Figure 1B As shown, WTRU 102 may, among other things, include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other peripheral devices 138. It should be understood that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments.

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

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

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

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

[0032] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit), and can receive user input data therefrom. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad 128. Additionally, the processor 118 can access information from and store data therein from any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. Non-removable memory 130 can include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 can include a subscriber identity module (SIM) card, memory stick, secure digital storage (SD) card, and the like. In other embodiments, the processor 118 can access information from and store data in memory that is not physically located on WTRU 102, such as on a server or home computer (not shown).

[0033] The processor 118 may receive power from the power supply 134 and may be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 may be any suitable device for powering the WTRU 102. For example, the power supply 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

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

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

[0036] WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with a specific subframe 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 to reduce and / or substantially eliminate self-interference via hardware (e.g., a choke) or via a processor (e.g., a separate processor (not shown) or via processor 118). In embodiments, WTRU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with a specific subframe for UL (e.g., for transmission) or DL ​​(e.g., for reception)) may occur concurrently and / or simultaneously.

[0037] Figure 1C This is a system diagram illustrating RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 may employ E-UTRA radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 104 may also communicate with CN 106.

[0038] RAN 104 may include eNode-B 160a, 160b, 160c, but will be appreciated that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. Each of eNode-B 160a, 160b, 160c may include one or more transceivers for communicating with WTRU 102a, 102b, 102c via air interface 116. In one embodiment, eNode-B 160a, 160b, 160c may implement MIMO technology. Thus, for example, eNode-B 160a may use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a.

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

[0040] Figure 1C The CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (PGW) 166. Although the foregoing elements are depicted as part of 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.

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

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

[0043] The SGW 164 can connect to the PGW 166, which provides WTRU 102a, 102b, and 102c with access to packet-switched networks such as the Internet 110, facilitating communication between WTRU 102a, 102b, and 102c and IP-enabled devices.

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

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

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

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

[0048] When operating in 802.11ac infrastructure mode or a similar mode, the AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of fixed width (e.g., a 20 MHz wide bandwidth) or dynamically configured. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, carrier-sense multiple access (CSMA / CA) with collision avoidance can be implemented, for example, in an 802.11 system. For CSMA / CA, each STA (e.g., each STA includes the AP) and can sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, that particular STA can back off. A single STA (e.g., only one station) can transmit at any given time within a given BSS.

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

[0050] Very High Throughput (VHT) STAs can support wide channels of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. A 40 MHz and / or 80 MHz channel can be formed by combining consecutive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels or by combining two non-consecutive 80 MHz channels; this can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, data passes through a segmentation parser, which divides the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing can be performed separately for each stream. The streams can be mapped onto two 80 MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the above operations for the 80+80 configuration can be reversed, and the combined data can be transmitted to Media Access Control (MAC).

[0051] The sub-1 GHz operating mode is supported by 802.11af and 802.11ah. The channel operating bandwidth and carrier are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support instrument-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 (e.g., only support) certain and / or limited bandwidths. MTC devices may include batteries with a battery life exceeding a threshold (e.g., to maintain a very long battery life).

[0052] WLAN systems supporting multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that can be designated as the primary channel. The primary channel can have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STAs operating in the BSS that support the minimum bandwidth operating mode. In the 802.11ah example, for STAs supporting (e.g., only supporting) the 1 MHz mode (e.g., MTC type devices), the primary channel can be 1 MHz wide, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy, for example, because an STA (which only supports the 1 MHz operating mode) is transmitting to the AP, then all available frequency bands can be considered busy even if most of the available frequency bands remain idle.

[0053] In the United States, the available frequency bands for 802.11ah are from 902 MHz to 928 MHz. In South Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. Depending on the country code, the total bandwidth available for 802.11ah ranges from 6 MHz to 26 MHz.

[0054] Figure 1DThis is a system diagram illustrating RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 can employ NR radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 104 can also communicate with CN 106.

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

[0056] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with scalable numberology. For example, OFDM symbol spacing and / or OFDM subcarrier spacing can vary for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing different numbers of OFDM symbols and / or absolute times of varying durations).

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

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

[0059] Figure 1DThe CN 106 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. Although the foregoing elements are depicted as part of 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.

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

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

[0062] UPF 184a and 184b can be connected via an N3 interface to one or more of gNB 180a, 180b, and 180c in RAN 104. This N3 interface provides WTRU 102a, 102b, and 102c with access to packet-switched networks, such as the Internet, to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, and so on.

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

[0064] Given Figure 1A-1D and to Figure 1A-1D The corresponding descriptions herein refer to the following: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or one or more other devices described herein. One or more of the functions described herein may be performed by one or more emulation devices (not shown). Emulation devices may be one or more devices configured to emulate one or more of the functions described herein. For example, emulation devices may be used to test other devices and / or simulate network and / or WTRU functions.

[0065] Simulation devices can be designed to perform one or more tests on other devices in a laboratory environment and / or a carrier network environment. For example, one or more simulation devices may perform one or more or all of their functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. One or more simulation devices may perform one or more or all of their functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. Simulation devices may be directly coupled to another device for testing and / or performing tests using over-the-air wireless communication.

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

[0067] Before discussing the specific details of the solution implementation, it may be helpful to briefly discuss the implementation of URLLC systems and the time-domain and frequency-domain resource allocation methods using the Physical Uplink Shared Channel (PUSCH). Unlike LTE, which uses slot-based transmission (mapping type A) where transmissions can only begin at the beginning of a slot, 5G uses sub-slot-based transmission (mapping type B), which facilitates services with low latency requirements. In 5G, packets can be scheduled across more transmission opportunities within a single slot compared to LTE. Furthermore, the gNB has the ability to puncture DL eMBB resources to schedule URLLC transmissions as quickly as possible.

[0068] Furthermore, uplink configuration grants (CGs) can be used to support low-latency uplink transmissions. The configured grant resources are indicated to the WTRU by the gNB and used for PUSCH transmissions without requiring a scheduling request or explicit grant. In many implementations, two types of UL CGs, Type 1 and Type 2, can be utilized. In Type 1, RRC signaling is used to configure time and frequency resources, as well as all other relevant parameters, such as periodicity and repetition. In Type 2, only the number of periodicities and repetitions is configured via RRC signaling, and the remaining parameters can be sent via DCI.

[0069] URLLC use cases, among others, can include AR / VR, smart grids, automation, and the transportation and power distribution industries. Many of these use cases require higher reliability and lower latency in both uplink and downlink transmissions compared to less critical communications. For example, in DL transmissions, enhancements such as PDCCH monitoring capabilities and new DCI formats can be leveraged to increase reliability and reduce latency. Additional enhancements may include URLLC support in unlicensed spectrum portions, improved physical layer feedback, and in-device multiplexing and prioritization.

[0070] In many implementations, in order for data transmission and reception to occur, the network may need to notify the WTRU which time slots / symbols are available for data transmission and reception. Depending on the implementation, this resource allocation signaling can occur dynamically or in a semi-persistent manner.

[0071] In uplink dynamic scheduling, resource allocation information is transmitted via PDCCH DCI. In 5G NR, DCI formats 0_0 and 0_1 are used for dynamic PUSCH time-domain resource allocation. These formats carry 4 bits of 'time-domain resource allocation', which points to one of the rows in a lookup table (e.g., up to 16 rows in some implementations), where each row provides the following parameters: • Slot offset K2, used to indicate the offset of the slot used for PUSCH transmission; • SLIV (jointly encoded start and length indicator values), used to derive the values ​​of the start symbol 'S' and the assigned length 'L'; and • The 'PUSCH mapping type' to be applied to the PUSCH transmission, type A or type B, determines the location of the first DM-RS symbol.

[0072] Figure 2A This is a diagram illustrating an embodiment of time-domain resource allocation, and shows an example with an allocation set of K2 = 1 time slot, S = 7 symbols, and L = 5 symbols. In many implementations, each time-domain resource allocation must be contained within a single time slot—that is, allocations absolutely cannot span multiple time slots. A cyclic prefix (CP) can play a role in determining the number of symbols allocated. For a normal CP, a time slot can contain 14 symbols; for an extended CP, a time slot can contain 12 symbols. Therefore, 'S+L' should not exceed these limits for the corresponding CP.

[0073] There are two types of PUSCH resource allocation tables: • “Default PUSCH Time Domain Allocation Table A”; and • The RRC configuration table PUSCH-TimeDomainAllocationList, conveyed by PUSCH-ConfigCommon or PUSCH-Config.

[0074] WTRU can select an appropriate table. It can also utilize the additional slot delay value defined for the first transmission of a PUSCH authorized and scheduled by RAR, which increases with the SCS.

[0075] The IE PUSCH-TimeDomainResourceAllocation is used to determine the time-domain offset between the PDCCH and PUSCH. In many implementations, the PUSCH-TimeDomainResourceAllocationList can list up to 64 PUSCH-TimeDomainResourceAllocations. The WTRU determines the bit width of the DCI field based on the number of entries in the PUSCH-TimeDomainResourceAllocationList. The DCI will indicate to the WTRU which configured time-domain allocation must be used for this UL authorization.

[0076] The `PUSCH-TimeDomainResourceAllocationList` IE contains `K2`, the `PUSCH` mapping type, and `startSymbolAndLength` (SLIV). A value of `K2=0` considers PUSCH transfers within the same time slot (i.e., a self-contained time slot) upon receiving authorization. When the `K2` field is absent, in many implementations, WTRU is applied: • The value is 1 when PUSCH SCS is 15 / 30 kHz; • The value of 2 when PUSCH SCS is 60 kHz, and • Value 3 when PUSCH SCS is 120KHz.

[0077] Other values ​​can be used in other implementations.

[0078] The parameter `startSymbolAndLength` provides an index as a start and length indicator (SLIV) that indicates a valid combination of the start symbol and length (joint encoding). The 'S' and 'L' values ​​assigned to PUSCH are determined from the SLIV, as follows: If (L − 1) ≤ 7: SLIV = 14.(L − 1) + S otherwise: SLIV = 14⋅(14 − L + 1) + (14 − 1 − S) Among them 0 <L ≤ 14 – S。

[0079] The parameter mappingType defines the DM-RS configuration for PUSCH transmission as follows: Type A and Type B.

[0080] In some implementations using PUSCH mapping type A, DM-RS are mapped relative to the start of the time slot if frequency hopping is disabled, and relative to the start of each hop if frequency hopping is enabled. The position of the first DM-RS symbol for type A is configured via MIB or via ServingCellConfigCommon (SIB1 or dedicated signaling) through RRC. The field dmrs-type-A-position indicates two values, pos2 or pos3 (i.e., the first DMRS symbol is at symbol 2 or symbol 3 within the time slot).

[0081] In some implementations using PUSCH mapping type B, DM-RS is mapped relative to the start of the PUSCH assignment. (If frequency hopping is disabled, the DM-RS symbol is the first symbol at the start of the PUSCH transmission, and if frequency hopping is enabled, DM-RS is mapped relative to the start of each hop.)

[0082] For uplink semi-persistent scheduling, DCI 0_0 and DCI 0_1 are addressed to the configured scheduling RNTI (CS-RNTI). The grant received using the CS-RNTI is called the configured grant. The configured grant is given to the WTRU by the network, and the WTRU uses it according to the pre-configured timing given by the network. There are two types of configured grants: Type 1 and Type 2.

[0083] Time-domain resource allocation for configuration, using authorization type 1, is performed via RRC. PDCCH DCI0_0 or 0_1, addressed to CS-RNTI, is used only for retransmission. Once the network has configured time-domain resources using RRC, the only way to change the allocation is by sending an RRC econfiguration message to the WTRU.

[0084] In the configured license type 2, time-domain resource allocation is accomplished using PDCCH DCI 0_0 or 0_1, which is addressed to CS-RNTI (and even for retransmission). Once configured with DCI 0_0 or 0_1, the WTRU periodically uses the same time-domain resources until the configured license is deactivated.

[0085] In slot aggregation, the WTRU does not wait for feedback from the gNB; instead, it retransmits the PUSCH in consecutive slots (i.e., transmits the same TB on multiple consecutive slots). This is beneficial in cell-edge scenarios where retransmission is more likely. The set of all retransmissions of the same TB is called a bundle. The same HARQ procedure is used for each transmission within a bundle. For each bundle, a HARQ retransmission is triggered without waiting for feedback from previous transmissions.

[0086] In many implementations, the following parameters are used to configure slot aggregation via RRC signaling.

[0087] The PUSCH-AggregationFactor field within the PUSCH-Config IE is used for dynamic scheduling. This field can take 2, 4, or 8 repeated values ​​as shown below. When the field does not exist, WTRU applies a value of 1. The PUSCH-AggregationFactor can be enumerated as {n2, n4, n8}. • The repK field within the ConfiguredGrantConfig IE, which specifies the authorization settings. This field can take values ​​of 1, 2, 4, and 8. When repK > 1, slot aggregation is activated. repK can be enumerated as {n1, n2, n4, n8}.

[0088] The network sends DCI format 0_1 ​​on the PDCCH, where CRC is scrambled using C-RNTI or MCS-C-RNTI for dynamic licensing and CS-RNTI for NDI=1 for configured licensing.

[0089] Considering that PUSCH-AggregationFactor is suitable for dynamic scheduling and repK is suitable for configured uplink authorization, WTRU follows the following process: • When the MAC entity is configured with PUSCH-AggregationFactor>1 or repK>1, the parameters PUSCH-AggregationFactor / repK provide the number of transmissions of the same TB within the bundle.

[0090] • After the initial transmission, the PUSCH-AggregationFactor-1 or repK-1 HARQ retransmission follows within the bundle.

[0091] • The same HARQ procedure is used for each transmission that is part of the same bundle.

[0092] • WTRU can apply the same symbol allocation PUSCH-AggregationFactor / repK consecutive time slots repeating TB across each time slot.

[0093] • PUSCH repetition type B can be used to eliminate time gaps between repetitions, and because repetitions are performed in consecutive sub-slots, a slot may contain more than one repetition of a transport block.

[0094] For dynamic scheduling, the first one to be applied to TB can be determined. n A redundant version of the transmission timing, where n=0,1,... (PUSCH-A ggregationFactor-1).

[0095] For the configuration grant, the repK-RV parameter (if configured within the configuredGrantConfig IE) is used to export the redundancy versioning pattern to be applied to repeating. If the repK-RV parameter is not configured, the redundancy versioning used for uplink transmission can be set to 0. repK-RV can be enumerated as {s1-0231, s2-0303, s3-0000}.

[0096] When time slot aggregation is active, PUSCH is limited to a single transport layer. Figure 2B This is a diagram of an embodiment of time-domain resource allocation with slot aggregation enabled, specifically illustrating an example of PUSCH slot aggregation with an aggregation factor of 4 for the RV patterns {RV2, RV3, RV1, RV0} derived for dynamic scheduling. In contrast, Figure 2C This is a diagram of an embodiment of time-domain resource allocation with time slot aggregation disabled.

[0097] NR supports the following resource allocation types: • Uplink resource allocation type 0 for PUSCH is used only when transform precoding is disabled.

[0098] • Type 1 and Type 2 of uplink resource allocation schemes for PUSCH for two cases when transform precoding is enabled or disabled.

[0099] The network notifies the WTRU via RRC signaling which resource allocation scheme to use. The PUSCH-Config IE is used for dynamic resource allocation, and the ConfiguredGrantConfig IE is used for configured granted (semi-persistent) resource allocation. For example, the PUSCH-Config IE is shown below: PUSCH-Config ... resourceAllocation enumeration {resourceAllocationType0, resourceAllocationType1, dynamicSwitch} resourceAllocationForDCI-Format0-2-r16 enumerated {resourceAllocationType0, resourceAllocationType1, dynamicSwitch} ... The `resourceAllocation` field refers to resource allocation using DCI format 0_1, and the `resourceAllocationForDCI-Format0-2` field refers to DCI format 0_2. The values ​​of these two fields should be interpreted as follows: • resourceAllocationType0 -> Resource allocation type 0 should be used.

[0100] • resourceAllocationType1 -> Resource Allocation Type 1 should be used.

[0101] • The resource allocation type remains flexible, meaning that type 0 or type 1 should be used as indicated by the DCI. The MSB bit of the 'Frequency Domain Resource Allocation' field within DCI 0_1 / 0_2 is used to indicate resource allocation type 0 or type 1 (bit value = 0 -> type 0 and bit value = 1 -> type 1).

[0102] exist Figure 2D The table shows a summary of resource allocation types in DCI format.

[0103] For Type 0 uplink resource allocation, the network can request the WTRU to use Type 0 via RRC signaling (resourceAllocationType 0) or via DCI format 0_1 / 0_2 (dynamicSwitch). Type 0 uplink resource allocation can include a bitmap-based resource allocation scheme. RB allocation information includes a bitmap indicating the resource block groups (RBGs) allocated to the scheduled WTRU. An RBG is a contiguous set of virtual resource blocks (VRBs). In Type 0, non-interleaved VRB-to-PRB mapping is performed (i.e., VRBn is directly mapped to PRBn).

[0104] The number of RBs within an RBG is derived based on the RRC parameter rbg-size configured by PUSCH-Config and the size of the bandwidth portion.

[0105] The parameter `rbg-Size` controls the choice between Configuration 1 and Configuration 2 for the RBG size used for PUSCH. If this IE exists, Configuration 2 should be used; otherwise, Configuration 1 should be used. This field only applies to uplink resource allocation type 0: PUSCH-Config The {config2} enumeration of rbg-Size ... The bitmap has a size N RBG Bits, where each bit in the bitmap represents an RBG, and RBG#0 to RBG#N RBG -1 maps from the MSB of the bitmap to the LSB.

[0106] The frequency domain resource allocation field within DCI 0_1 / 0_2 is used to indicate which RBGs are allocated to WTRUs. If the corresponding bit in the bitmap is 1, the RBG is allocated to the WTRU; if the bit is 0, the RBG is not allocated to the WTRU.

[0107] Figure 2E This is a diagram illustrating an example of frequency domain resource allocation type 0, where: BWP's starting RB=37 BWP size = 24 RBs Rbg configuration = configuration2 RBG size = 4 The size of the first RGB is 4 The final RGB size is 4. All other RBG sizes = 4 In Type 1 uplink resource allocation, the network provides the WTRU with encoded values ​​for the RB length and the starting resource block number. It only supports contiguous allocation of resource blocks. For Type 1, the number of bits required to represent the RB set is less than that for Type 0. Because Type 1 occupies fewer bits compared to Type 0, the fallback DCI format 0_0 uses Type 1. For the fallback DCI format, reduced overhead is desired compared to the scheduling flexibility resulting from non-contiguous RB allocation. The network can allocate resources for Type 1 via the 'Frequency Domain Resource Allocation' field within DCI formats 0_0, 0_1, and 0_2.

[0108] Typically, the uplink type 1 resource allocation field is defined by the starting virtual resource block (RB). start The length of the resource indication value (RIV) and the continuously allocated RB (LRB) consists of the resource indication value (RIV).

[0109] For Type 2 uplink resource allocation, multiple interleavings of RBs are defined, where interleaving m∈{0,1,...,M-1} consists of common RBs {m,M+m,2M+m,3M+m,...}, where M is the number of interleavings. The interpretation of the field 'Frequency Domain Resource Allocation' in DCI format 0_1 ​​depends on whether useInterlacePUCCH-PUSCH-r16 is configured within BWP-UplinkDedicated. If it is configured, WTRU will use Type 2 uplink frequency domain resource allocation for PUSCH. Figure 2F This is a diagram based on an example of frequency domain resource allocation type 2 implemented by some entities.

[0110] Frequency-bundled transmission mitigates the effects of periodic narrowband interference by allowing WTRUs to simultaneously transmit different redundant versions of the same uplink data on multiple pre-configured frequency resources. Figure 3A The diagram illustrates an example of PDCCH timing, where DCI 0_0 or DCI 0_1 schedules UL data after K2 symbols and a J2 RBG offset (in the example shown, K2=1 and J2=0). Frequency-bundled transmissions are carried out simultaneously on different frequency resources at the allocated symbols / RBGs.

[0111] Figure 3B Another example of UL data transmitted in a time-slot aggregation manner over four consecutive mini-time slots and in a frequency-bundled transmission manner over four consecutive RBGs is shown (in the example shown, K2=1 and J2=0, timeShiftSymbols=1, freqShiftRBG=1, and FreqGap=3). The figure also shows a radar signal with a duration of less than eight RBGs in time and frequency (shown as diagonal stripes). The signal repeats periodically every three symbols. Here, FBT paired with PUSCH time-slot aggregation and shifted in time and frequency could potentially help transmit all four RVs in three transmission instances instead of four.

[0112] The network transmits via frequency-bundled configuration using RRC signaling as follows: The PUSCH-FrequencyBundlingFactor within the PUSCH-Config IE is used for dynamic scheduling and is defined below. The PUSCH-FrequencyBundlingFactor enumerates {n1, n2, n4, n8}. • The `repJ` field within the `ConfiguredGrantConfig` IE, which specifies the authorization settings. This field is mandatory and can take values ​​of 1, 2, 4, and 8. When `repJ > 1`, frequency binding is activated.

[0113] repJ enumerates {n1, n2, n4, n8} • timeShiftSymbols: This is used to indicate the time shift of symbols between the first transmission and subsequent retransmissions (after K2 time slots). This time shift may not be applicable if the system cannot support it.

[0114] timeShiftSymbols {n0, n1, ..., n12}, where n0 means no time shift is applied (e.g., URLLC application).

[0115] For systems operating in TDD mode, conflicts between scheduling UL symbols and time slot formats may not occur because both timeShiftSymbols and TDD-UL-DL-ConfigCommon (which determines the time slot format) are part of RRC signaling. Additional parameters include: • freqShiftRBG: This is used to indicate the frequency shift of RBGs between instances of the same transmission but at different times. If the system cannot support this frequency shift, it may not be applicable.

[0116] freqShiftRBG {n0, n1, ..., n16}, where n0 means no frequency shift is applied.

[0117] • FreqGap: This defines the frequency separation between simultaneous HARQ transmissions. In many implementations, a maximum value can be set for type 0 assignments in FR1.

[0118] The network transmits DCI format 0_1, utilizing CRC continuation with scrambled C-RNTI or MCS-C-RNTI for dynamic licensing and CS-RNTI with NDI=1 for configured licensing. In the PDCCH (DCI) used for uplink scheduling, the following parameters are received: • J2: Similar to K2, this parameter indicates the offset of the first UL transmission in units of RBs. This offset can be configured to be greater than the bandwidth of the interference source to minimize the probability of erroneous reception. Since the minimum rbg-Size for config#1 is 2 RBs and the minimum rbg-Size for config#2 is 4 RBs, and the maximum possible carrier bandwidth is limited to 275 RBs for any SCS, J2 can be defined as follows: J2 enumerates {n0, n1, ..., n136}, where J0 indicates that the first retransmission occurs in the same RBG as the DCI schedule.

[0119] WTRU follows the process defined below: • The parameter pusch-FrequencyBundlingFactor>1 or repJ>1 provides the number of transmissions if the same TB is within the bundle.

[0120] • After the initial transmission, a pusch-FrequencyBundlingFactor-1 or repJ-1 retransmission is sent within the bundle, each retransmission having the same HARQ process number.

[0121] • WTRU applies the same symbol allocation to the pusch-FrequencyBundlingFactor / repJ frequency subcarrier to repeat UL data across each time slot / mini-time slot.

[0122] For dynamic scheduling, in some implementations, such as Figure 3C The table shows the redundant version to be applied to the nth transmission timing on the mth RBG, where n = 0, 1, ... (pusch-aggregationFactor-1) and m = 0, 1, ... (pusch-FrequencyBundlingFactor-1), where for n <= pusch-aggregationFactor-1 and m <= pusch-FrequencyBundlingFactor-1, the (n, m)th transmission uses according to... Figure 3C The table has a redundant version identifier (rvid=). Other implementations may utilize other enumerations or versioning methods.

[0123] In some implementations, if the frequency range of the FBT exceeds the supported bandwidth, frequency wrap-around can be used, such as... Figure 3D As shown in the diagram. In the example shown, FBT is activated without PUSCH slot aggregation. A bundle of four transmissions {RVid=2, RVid=3, RVid=1, RVid=0} is performed simultaneously on symbols 2 and 3. The first transmission begins at RBG8, with FreqGap=3 RBGs between transmissions. Frequency wrap-around is used to accommodate the last transmission (RVid=0) over the maximum bandwidth of 17 RBGs.

[0124] In many implementations, the WTRU can notify the network of its capability or support for frequency bundled transmissions. The network can optionally enable or disable this feature for the WTRU based on its capabilities and network requirements. The WTRU can notify the network of its capabilities via an informational message that may include the parameter "FBTS upport," indicating whether the WTRU can support frequency bundled transmissions. This parameter can be set to a flag, a predefined bit, or any other string. This parameter can be sent on a per-WTRU basis and may also indicate frequency and / or time-domain capabilities and the range of available frequencies.

[0125] In implementations with frequency-bundled transmissions featuring frequency domain repetition, bundles of UL data retransmissions (e.g., {RVid=2, RVid=3, RVid=1, RVid=0}) can be transmitted across multiple frequency resources in the frequency domain, such as... Figure 3E As shown in the diagram. This diagram illustrates the PDCCH timing, where DCI 0_0 or DCI 0_1 schedules UL data after the K2 offset. After the assigned offset, frequency-bundled transmissions with frequency domain repetition are transmitted simultaneously on different frequency resources and separated by J2 RBG.

[0126] Figure 3E An example of UL data transmitted using FBT with frequency domain repetition and slot aggregation over four consecutive mini-time slots is shown. In each transmission instance, the bundle of four transmissions is transmitted over four consecutive RBGs and repeated simultaneously after the four RBGs. The transmissions in each transmission instance are shifted by one symbol in the time domain and by one RBG in the frequency domain.

[0127] In some implementations, frequency domain repetition can also be paired with PUSCH slot aggregation, and frequency shifting can be applied between simultaneous transmissions, such as... Figure 3F As shown, Figure 3F Another example of frequency-bundled transmission with frequency domain repetition and frequency shift is shown.

[0128] The network is configured for frequency-domain repetition transmission via RRC signaling in the same manner as its configured frequency-bundling transmission. Similar to FBT, the network can transmit the following via RRC signaling: The `pusch-FrequencyBundlingFactor` within the `PUSCH-Config` IE is used for dynamic scheduling and is defined below. The Pusch-FrequencyBundlingFactor enumerates {n1, n2, n4, n8}. • The `repJ` field within the `ConfiguredGrantConfig` IE, which specifies the authorization settings. This field is mandatory and can take values ​​of 1, 2, 4, and 8. When `repJ > 1`, frequency binding is activated.

[0129] repJ enumerates {n1, n2, n4, n8} ·numOfBundles, this parameter indicates the number of bundles transmitted simultaneously. numOfBundles is an enumeration of {n1, n2, n4, n8}. • timeShiftSymbols: This is used to indicate the symbol time shift between the first transmission and subsequent retransmissions (after K2 time slots). This time shift may not be applicable if the system cannot support it.

[0130] timeShiftSymbols{n0, n1, ..., n2, n12}, where n0 means no time shift is applied (e.g., URLLC application). For systems operating in TDD mode, conflicts between scheduling UL symbols and time slot formats may not occur because both timeShiftSymbols and TDD-UL-DL-ConfigCommon (which determines the time slot format) are part of RRC signaling. Additional parameters include: • freqShiftRBG: This is used to indicate the frequency shift of RBGs between instances of the same transmission but at different times. If the system cannot support this frequency shift, it may not be applicable.

[0131] freqShiftRBG {n0, n1, ..., n16}, where n0 means no frequency shift is applied.

[0132] • FreqGap: This defines the frequency separation between simultaneous HARQ beams. In some implementations, the maximum value can be predetermined or specified; In the PDCCH (DCI) used for uplink scheduling, the following parameters are received: J2: Similar to FBT, this parameter indicates the offset between simultaneous UL transmissions, in units of RBs. This offset can be configured to be greater than the bandwidth of the interference source to minimize the probability of erroneous reception. Since the minimum rbg-Size for config#1 is 2 RBs and the minimum rbg-Size for config#2 is 4 RBs, and the maximum possible carrier bandwidth is limited to 275 RBs for any SCS, J2 can be defined as follows: J2 enumerates {n0, n1, ..., n136}, where J0 indicates that the first retransmission of the first bundle occurs in the same RBG as the DCI schedule.

[0133] In some implementations, the WTRU can notify the network of its frequency-domain repetition support for frequency-bundled transmissions. The network can optionally enable or disable this feature for the WTRU based on its capabilities and network requirements. The WTRU can notify the network of its capabilities via an informational message that may include the parameter "FBTwithFreqRepSupport" indicating whether the WTRU can support frequency-bundled transmissions. This parameter can be set to a flag, a predefined bit, or any other string. This parameter can be sent on a per-WTRU basis and may also indicate frequency and / or time-domain capabilities and the range of available frequencies.

[0134] Figure 4 This is a flowchart of a method 400 for frequency-bundled transmission according to some implementations. In some specific implementations at 402, a device, such as a WTRU, station (STA), user equipment (UE), wireless device, portable computer, smartphone, or other device, may transmit a request for capacity allocation to a second device, such as another WTRU, access point (AP), peer-to-peer wireless device, portable computing device, or any other type and form of wireless device. The request may include a request regarding whether the other device can use one or more of time-slot aggregation, frequency aggregation, frequency-bundled transmission, frequency domain repetition, and / or time-domain repetition. In other implementations, 402 may be skipped, and the other device may periodically broadcast its capacity in response to a first device joining the network, etc.

[0135] At 404, in some implementations, the first device may receive time and / or frequency allocation information. This may be transmitted periodically or dynamically in response to a request at 402, or in response to any other type and form of request or trigger. The time and / or frequency allocation information may include transmission configuration parameters such as offsets and / or mini-slot offsets for uplink transmissions based on resource blocks (e.g., J2, K2 parameters); start symbol and / or length (S and L parameters); mapping type parameters; the number of repeated or redundant transmissions; time shifts for the number of symbols; frequency shifts within resource block groups; frequency gaps or intervals within resource block groups; and / or any other type and form of information or parameters for data transmission and / or retransmission or redundant transmission.

[0136] At 406, in some embodiments, the first device can select the allocated resources (e.g., time slots or symbols and one or more resource block groups) for data transmission. In some implementations, the first device can select multiple resource blocks for transmission (e.g., frequency-bundled transmission for a bandwidth exceeding that of a single resource block group).

[0137] At 408, in some embodiments, the first device may determine the number of redundant transmissions to be performed (e.g., one retransmission, two retransmissions, four retransmissions, etc.) based on the received allocation information.

[0138] At 410, in some embodiments where multiple frequency-bundled transmissions are to be performed, the first device can determine how the transmissions should be separated or what frequency gaps should be included between the transmission portions. For example, in the above... Figure 3E In some implementations shown, frequency-bundled transmissions may include multiple consecutive frequency ranges or resource block groups. In, for example... Figure 3A In other implementations shown, frequency-bundled transmission may have portions separated by a predetermined number of resource block groups (e.g., 3 groups), which may correspond to a continuous frequency range (e.g., 10MHz, 20MHz, 40MHz, etc.).

[0139] As discussed above, in some implementations, separating frequency-bundled transmissions with intervals can cause one or more transmission segments to exceed the allocated range, as shown in 3D. At 412, the first device can determine whether the frequency interval and the number of segments or portions (and the initial resource block group) will cause one or more resource blocks to exceed the end of the allocated range. If so, at 414, the first device can determine alternative resource blocks for “wrapping around” one or more segments of the frequency range—that is, if a block at a predetermined interval would exceed the range. n If there are multiple resource blocks, then the first device can be identified as being above the bottom of that range. n A resource block. In other words, the first device can select a transmission frequency within a predetermined range such that the difference between the original determined transmission frequency of the redundant version and the end of the predetermined range it exceeds is equal to the difference between the selected transmission frequency and the opposite end of the predetermined range.

[0140] At 416, the first device can determine whether there are any additional segments, retransmissions, or redundant transmissions that have not yet been scheduled. If so, at 418, the first device can identify the start of a subsequent transmission based on the time shift in the symbol and / or the frequency shift in the resource block group, according to the received allocation information. The first device can then repeat 410-418 for each additional retransmission or redundant transmission (and for the frequency-bundled segments or portions of the redundant transmission).

[0141] At 420, the first device can transmit uplink data and redundant transmissions based on the selected or scheduled time slots and resource block groups. As mentioned above, using time and / or frequency diversity to schedule transmissions can help avoid interference from sources such as airport or weather radar or other transmission devices in the same allocated frequency area.

[0142] Accordingly, in the first aspect, this disclosure relates to an apparatus, such as a WTRU, configured to receive information determining the allocated frequency and time resources for uplink data transmission. In some implementations, based on the received information, the apparatus can simultaneously transmit individual HARQ redundant versions of the same data on different frequency resources. In further implementations, frequency bundled transmission (FBT) technology can be combined with PUSCH slot aggregation to increase the probability of correct data decoding. Transmission of individual redundant versions can take into account more reliable data transmission while maintaining maximum user capacity in the system. Multiple mini-slots can be transmitted simultaneously on different frequency resources, thereby supporting latency-sensitive applications in URLLC systems. In some implementations, the gNB can determine the K2 and J2 parameters based on prior knowledge of interference patterns. In various implementations, uplink retransmission can occur in non-adaptive or adaptive modes (e.g., in adaptive mode implementations, retransmission parameters, such as MCS, can be changed according to channel conditions such as, for example, radar interference levels at the gNB). In some implementations, FBT can be configured with dynamic scheduling or semi-persistent scheduling and frequency resource allocation type 0, type 1, or type 2.

[0143] In another aspect, this disclosure relates to an apparatus, such as a WTRU, configured to receive information determining the allocated frequency and time resources for uplink data transmission. Based on the received information, the apparatus can simultaneously transmit bundles of HARQ redundant versions of the same data on different frequency resources. In some implementations, frequency bundled transmission (FBT) techniques can repeat in the time domain at a predetermined frequency shift to increase the probability of correct data decoding. The transmission of redundant bundles considers more reliable data transmission (compared to FBT), but may reduce user capacity in some implementations. Multiple mini-slots can be transmitted simultaneously on different frequency resources, thereby supporting latency-sensitive applications in URLLC systems. In some implementations, the gNB can determine the K2 and J2 parameters based on prior knowledge of interference patterns. Uplink retransmissions can occur in non-adaptive or adaptive modes (e.g., in adaptive mode implementations, retransmission parameters, such as MCS, can change according to channel conditions such as, for example, radar interference levels at the gNB). In some implementations, FBTs with frequency domain repetition can be configured with dynamic scheduling or semi-persistent scheduling and frequency resource allocation types 0, 1, or 2.

[0144] In some aspects, this disclosure relates to a method for frequency-bundled transmission of redundant versions of data. The method includes receiving information by a wireless device identifying allocated frequency and time resources for uplink data transmission. The method also includes transmitting uplink data by the wireless device via the first allocated frequency and time resources. The method further includes transmitting at least one redundant version of the uplink data by the wireless device via additional allocated frequency and time resources.

[0145] In some embodiments, the information identifying the allocated frequency and time resources includes information identifying the time separation between the transmission of uplink data and the transmission of at least one redundant version of the uplink data. In some embodiments, the information identifying the allocated frequency and time resources includes information identifying the frequency separation between the transmission of uplink data and the transmission of at least one redundant version of the uplink data. In another embodiment, transmitting at least one redundant version of the uplink data further includes the wireless device determining that a first transmission frequency indicating the redundant version exceeds a predetermined range. In yet another embodiment, the method includes: in response to the determination, the wireless device selecting a second transmission frequency within the predetermined range such that the difference between the first transmission frequency of the redundant version and one end of the predetermined range it exceeds is equal to the difference between the second transmission frequency and the opposite end of the predetermined range.

[0146] In some embodiments, information identifying the allocated frequency and time resources is transmitted by the second wireless device in response to the wireless device receiving a transmission including information indicating the frequency-bundling transmission capability of the wireless device.

[0147] In some embodiments, the transmission of a first redundant version of at least one redundant version of uplink data is performed concurrently with the transmission of uplink data. In another embodiment, uplink data transmission is performed on a first resource block group of the allocated frequency resources, and the transmission of the first redundant version is performed on a second adjacent resource block group of the allocated frequency resources. In yet another embodiment, uplink data transmission is performed on a first resource block group of the allocated frequency resources, and the transmission of the first redundant version is performed on a second non-adjacent resource block group of the allocated frequency resources.

[0148] In some embodiments, the transmission of a second redundant version of at least one redundant version of the uplink data is performed at a later time and on a resource block group in an allocated frequency resource that is different from the resource block group used for the transmission of the uplink data.

[0149] In another aspect, this disclosure relates to a wireless transmit / receive unit (WTRU). The WTRU includes one or more receivers configured to receive information identifying allocated frequency and time resources for uplink data transmission. The WTRU also includes one or more transmitters configured to: transmit uplink data via a first allocated frequency resource and a first allocated time resource; and transmit at least one redundant version of the uplink data via additional allocated frequency and time resources.

[0150] In some embodiments, the information identifying the allocated frequency and time resources includes information identifying the time separation between the transmission of uplink data and the transmission of at least one redundant version of the uplink data. In some embodiments, the information identifying the allocated frequency and time resources includes information identifying the frequency separation between the transmission of uplink data and the transmission of at least one redundant version of the uplink data. In another embodiment, the WTRU includes one or more processors configured to determine that a first transmission frequency indicating a redundant version exceeds a predetermined range. In yet another embodiment, the one or more processors are further configured to select a second transmission frequency within the predetermined range such that the difference between the first transmission frequency of the redundant version and one end of the predetermined range it exceeds is equal to the difference between the second transmission frequency and the opposite end of the predetermined range.

[0151] In some embodiments, information identifying the allocated frequency and time resources is transmitted by the remote wireless device in response to the remote wireless device receiving a transmission including information indicating the frequency-bundling transmission capability of the remote wireless device.

[0152] In some embodiments, the transmission of a first redundant version of at least one redundant version of uplink data is performed concurrently with the transmission of uplink data. In another embodiment, uplink data transmission is performed on a first resource block group of the allocated frequency resources, and the transmission of the first redundant version is performed on a second adjacent resource block group of the allocated frequency resources. In yet another embodiment, uplink data transmission is performed on a first resource block group of the allocated frequency resources, and the transmission of the first redundant version is performed on a second non-adjacent resource block group of the allocated frequency resources.

[0153] In some embodiments, the transmission of a second redundant version of at least one redundant version of the uplink data is performed at a later time and on a resource block group in an allocated frequency resource that is different from the resource block group used for the transmission of the uplink data.

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

Claims

1. A method for frequency-bundled transmission of redundant versions of data, comprising: The wireless device receives information identifying the allocated frequency and time resources used for uplink data transmission; Uplink data is transmitted by a wireless device via the first allocated frequency resources and the first allocated time resources; as well as At least one redundant version of uplink data is transmitted by a wireless device via additional allocated frequency and time resources.

2. The method according to claim 1, wherein, Information identifying the allocated frequency and time resources includes information identifying the time interval between the transmission of uplink data and the transmission of at least one redundant version of the uplink data.

3. The method according to any of the preceding claims, wherein, Information identifying the allocated frequency and time resources includes information identifying the frequency separation between uplink data transmissions and at least one redundant version of the uplink data transmission.

4. The method according to claim 3, wherein, At least one redundant version for transmitting uplink data also includes a first transmission frequency of the redundant version that is determined by the wireless device to be outside a predetermined range, indicating that the frequency separation of the redundant version exceeds a predetermined range.

5. The method according to claim 4, further comprising: In response to the determination, the wireless device selects a second transmission frequency within a predetermined range such that the difference between the redundant version of the first transmission frequency and one end of the predetermined range it exceeds is equal to the difference between the second transmission frequency and the opposite end of the predetermined range.

6. The method according to any of the preceding claims, wherein, Information identifying the allocated frequency and time resources is transmitted by the second wireless device in response to the wireless device receiving a transmission including information indicating the frequency-bundled transmission capability of the wireless device.

7. The method according to any of the preceding claims, wherein, The transmission of the first redundant version of at least one redundant version of the uplink data is performed concurrently with the transmission of the uplink data.

8. The method according to claim 7, wherein, Uplink data transmission is performed on the first resource block group of the allocated frequency resources, and the transmission of the first redundant version is performed on the second adjacent resource block group of the allocated frequency resources.

9. The method according to claim 7, wherein, Uplink data transmission is performed on the first resource block group of the allocated frequency resources, and the transmission of the first redundant version is performed on the second non-adjacent resource block group of the allocated frequency resources.

10. The method according to any of the preceding claims, wherein, The transmission of the second redundant version of at least one redundant version of the uplink data is performed at a later time and on a resource block group of allocated frequency resources that is different from the resource block group used for the transmission of the uplink data.

11. A wireless transmit / receive unit (WTRU), comprising: One or more receivers are configured to receive information identifying the allocated frequency and time resources used for uplink data transmission; as well as One or more transmitters are configured to: Uplink data is transmitted via the first allocated frequency resources and the first allocated time resources, and At least one redundant version of uplink data is transmitted via additional allocated frequency and time resources.

12. The WTRU according to claim 11, wherein, Information identifying the allocated frequency and time resources includes information identifying the time interval between the transmission of uplink data and the transmission of at least one redundant version of the uplink data.

13. The WTRU according to claim 11 or 12, wherein, Information identifying the allocated frequency and time resources includes information identifying the frequency separation between uplink data transmissions and at least one redundant version of the uplink data transmission.

14. The WTRU of claim 13, further comprising one or more processors configured to determine that a first transmission frequency of the frequency separation indication redundant version exceeds a predetermined range.

15. The WTRU according to claim 14, wherein, One or more processors are further configured to select a second transmission frequency within a predetermined range, such that the difference between the first transmission frequency of the redundant version and one end of the predetermined range it exceeds is equal to the difference between the second transmission frequency and the opposite end of the predetermined range.

16. The WTRU according to any one of claims 11 to 15, wherein, Information identifying the allocated frequency and time resources is transmitted by the remote wireless device in response to the remote wireless device receiving a transmission including information indicating the frequency-bundled transmission capabilities of the remote wireless device.

17. The WTRU according to any one of claims 11 to 16, wherein, The transmission of the first redundant version of at least one redundant version of the uplink data is performed concurrently with the transmission of the uplink data.

18. The WTRU according to claim 17, wherein, Uplink data transmission is performed on the first resource block group of the allocated frequency resources, and the transmission of the first redundant version is performed on the second adjacent resource block group of the allocated frequency resources.

19. The WTRU according to claim 17, wherein, Uplink data transmission is performed on the first resource block group of the allocated frequency resources, and the transmission of the first redundant version is performed on the second non-adjacent resource block group of the allocated frequency resources.

20. The WTRU according to any one of claims 11 to 19, wherein, The transmission of the second redundant version of at least one redundant version of the uplink data is performed at a later time and on a resource block group of allocated frequency resources that is different from the resource block group used for the transmission of the uplink data.

Images