Frame-based device mode idle period physical uplink shared channel repetition processing

Abstract

In summary, various aspects of this disclosure relate to wireless communications. In some aspects, a user equipment (UE) can determine that a Physical Uplink Shared Channel (PUSCH) repetition overlaps with an idle period associated with a fixed frame period used for communication on an unlicensed channel in frame-based device mode. The UE can avoid transmitting on the unlicensed channel during one or more symbols of the PUSCH repetition that coincide with this idle period. Numerous other aspects are provided.

Description

Technical Field

[0001] In summary, aspects of this disclosure relate to wireless communications, and more specifically, aspects of this disclosure relate to techniques and apparatus for repeating Physical Uplink Shared Channel (PUSCH) processing during idle periods in Frame-Based Device (FBE) mode. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / Improved LTE is an enhanced set of the Universal Mobile Telecommunications System (UMTS) mobile standard released by the 3rd Generation Partnership Project (3GPP).

[0003] A wireless network may include several base stations (BSs) capable of supporting communication for multiple user equipments (UEs). UEs can communicate with the base stations (BSs) via downlinks and uplinks. A downlink (or forward link) refers to the communication link from the BS to the UE, and an uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, Access Point (AP), Radio Headend, Transmit / Receive Point (TRP), New Radio (NR) BS, 5G Node B, etc.

[0004] The above multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different user equipment to communicate at the city, country, regional, and even global levels. New Radio (NR) (which can also be referred to as 5G) is a collection of enhancements to the LTE mobile standard released by the 3rd Generation Partnership Project (3GPP). NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (DL) and CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation, thereby better supporting mobile broadband internet access. As the demand for mobile broadband access continues to grow, further improvements to LTE, NR, and other radio access technologies remain useful. Summary of the Invention

[0005] In some aspects, a method of wireless communication performed by a user equipment (UE) includes: determining that a Physical Uplink Shared Channel (PUSCH) repetition overlaps with an idle period associated with a Fixed Frame Period (FFP) for communication on an unlicensed channel in Frame-Based Equipment (FBE) mode; and avoiding transmission on the unlicensed channel during one or more symbols of the PUSCH repetition that overlap with the idle period.

[0006] In some aspects, a UE for wireless communication includes a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors are configured to: determine that a PUSCH repetition overlaps with an idle period associated with an FFP for communication on an unlicensed channel in FBE mode; and avoid transmission on the unlicensed channel during one or more symbols of the PUSCH repetition that overlap with the idle period.

[0007] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: determine that a PUSCH repetition overlaps with an idle period associated with an FFP for communication on an unlicensed channel in FBE mode; and avoid transmission on the unlicensed channel during one or more symbols of the PUSCH repetition that overlap with the idle period.

[0008] In some aspects, an apparatus for wireless communication includes: a unit for determining that a PUSCH repetition overlaps with an idle period associated with an FFP for communication on an unlicensed channel in FBE mode; and a unit for avoiding transmission on the unlicensed channel during one or more symbols of the PUSCH repetition that overlap with the idle period.

[0009] In summary, the terms include as fully described herein with reference to the accompanying drawings and description, and as illustrated by the accompanying drawings and description, methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment, and / or processing systems.

[0010] The foregoing has provided a fairly broad overview of the features and technical advantages of examples according to this disclosure in order to better understand the detailed description that follows. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for performing the same purposes of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and manner of operation) and their associated advantages will be better understood when considered in conjunction with the accompanying drawings, based on the description below. Each drawing in the accompanying drawings is provided for illustrative and descriptive purposes and is not intended to limit the scope of the claims. Attached Figure Description

[0011] To gain a more detailed understanding of the features of this disclosure, a more specific description of the brief overview above can be obtained by referring to various aspects (some of which are shown in the accompanying drawings). However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not intended to limit the scope of the disclosure, as other equally valid aspects can be recognized by this description. The same reference numerals in different drawings may identify the same or similar elements.

[0012] Figure 1 This is a diagram illustrating examples of wireless networks according to various aspects of this disclosure.

[0013] Figure 2 This is a diagram illustrating an example of communication between a base station and a UE in a wireless network according to various aspects of this disclosure.

[0014] Figure 3 This is a diagram illustrating examples of unlicensed radio frequency bands according to various aspects of this disclosure.

[0015] Figures 4A-4BThis is a diagram illustrating an example of a fixed frame period (FFP) including channel occupancy time according to various aspects of this disclosure, during which one or more devices may transmit on an unlicensed channel.

[0016] Figures 5A-5B This is a diagram illustrating an example of Physical Uplink Shared Channel (PUSCH) repetition according to various aspects of this disclosure.

[0017] Figure 6 , Figure 7 , Figures 8A-8D and Figures 9A-9D This is a diagram illustrating an example of PUSCH repetition processing in a frame-based device (FBE) mode idle period, according to various aspects of this disclosure.

[0018] Figure 10 This is a diagram illustrating an example process associated with PUSCH repetition processing during idle periods in FBE mode, according to various aspects of this disclosure.

[0019] Figure 11 This is a block diagram of an example device for wireless communication according to various aspects of this disclosure. Detailed Implementation

[0020] The various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function given herein. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of this disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will recognize that the scope of this disclosure is intended to cover any aspect of the disclosure herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, an apparatus or method may be implemented using any number of the aspects set forth herein. Furthermore, the scope of this disclosure is intended to cover such apparatuses or methods practiced using structures, functionalities, or structures and functionalities other than or different from the aspects of this disclosure set forth herein. It should be understood that any aspect of this disclosure herein may be embodied by one or more elements of the claims.

[0021] Several aspects of a telecommunications system will now be described with reference to various devices and techniques. These devices and techniques will be described in detail below and illustrated in the accompanying drawings by various frames, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether such an element is implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system.

[0022] It should be noted that although terms commonly associated with 5G or NR Radio Access Technologies (RATs) may be used herein to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RATs, 4G RATs and / or RATs after 5G (e.g., 6G).

[0023] Figure 1 This is a diagram illustrating an example of a wireless network 100 according to various aspects of this disclosure. Wireless network 100 may be or may include elements of a 5G (NR) network, an LTE network, etc. Wireless network 100 may include several base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE) and may also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), access point, Transmit / Receive Point (TRP), etc. Each BS can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0024] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with service subscriptions. A picocell can cover a relatively small geographic area and allow unrestricted access by UEs with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a residential area) and allow restricted access by UEs associated with that femtocell (e.g., UEs in a Closed User Group (CSG)). A BS used for macrocells can be referred to as a macro BS. A BS used for picocells can be referred to as a pico BS. A BS used for femtocells can be referred to as a femtocell BS or a home BS. Figure 1In the examples shown, BS110a can be a macro BS for macro cell 102a, BS110b can be a pico BS for pico cell 102b, and BS110c can be a femto BS for femto cell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” are used interchangeably herein.

[0025] In some respects, the cell may not be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile BS. In some respects, BSs may interconnect with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (such as direct physical connections, virtual networks, and / or similar interfaces using any suitable transport network).

[0026] The wireless network 100 may also include a relay station. A relay station is an entity that can receive data transmissions from an upstream station (e.g., a BS or a UE) and transmit data transmissions to a downstream station (e.g., a UE or a BS). A relay station can also be a UE capable of relaying transmissions for other UEs. Figure 1 In the example shown, relay BS110d can communicate with macro BS110a and UE 120d to facilitate communication between BS110a and UE 120d. A relay BS can also be referred to as a relay station, relay base station, repeater, etc.

[0027] Wireless network 100 can be a heterogeneous network comprising different types of Base Stations (BSs) (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs can have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs can have high transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and relay BSs can have lower transmit power levels (e.g., 0.1 to 2 watts).

[0028] Network controller 130 can be coupled to a group of base stations (BSs) and can provide coordination and control for these BSs. Network controller 130 can communicate with the BSs via backhaul. BSs can also communicate with each other via wireless or wired backhaul (e.g., directly or indirectly).

[0029] UE 120 (e.g., 120a, 120b, 120c) may be distributed throughout the wireless network 100, and each UE may be stationary or mobile. UE may also be referred to as an access terminal, terminal, mobile station, user unit, station, etc. UE may be a cellular phone (e.g., a smartphone), personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet device, camera, gaming device, netbook, smartbook, ultrabook, medical device or apparatus, biometric sensor / device, wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), entertainment device (e.g., music or video device, or satellite radio unit), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, GPS device, or any other suitable device configured to communicate via wireless or wired media.

[0030] Some UEs can be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, instruments, monitors, location tags, etc., which can communicate with a base station, another device (e.g., a remote device), or some other entity. Wireless nodes can provide connectivity to or to a network (e.g., a wide area network such as the Internet or cellular networks) via wired or wireless communication links, for example. Some UEs can be considered Internet of Things (IoT) devices, and / or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 can be included within a housing housing the components of UE 120 (such as processor components, memory components, etc.). In some aspects, the processor components and memory components can be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) can be operatively coupled, communicatively coupled, electronically coupled, electrically coupled, etc.

[0031] Typically, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

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

[0033] Alternatively or alternatively, wireless network 100 may include one or more wireless local area network (WLAN) access points 140 and one or more WLAN stations 150. WLAN access points 140 may wirelessly communicate with WLAN stations 150 via one or more WLAN access point antennas over one or more communication links. In some aspects, WLAN access points 140 may communicate with WLAN stations 150 using one or more Wi-Fi communication standards, such as IEEE 802.11 (e.g., IEEE 802.11a, IEEE 802.11n, or IEEE 802.11ac)). In some aspects, WLAN access points 140 and base station 110 may be the same device or may be co-located. Alternatively or alternatively, WLAN station 150 and UE 120 may be the same device or may be co-located.

[0034] Devices in the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices in the wireless network 100 can communicate using an operating band with a first frequency range (FR1), which can span from 410 MHz to 7.125 GHz, and / or can communicate using an operating band with a second frequency range (FR2), which can span from 24.25 GHz to 52.6 GHz. Frequencies between FR1 and FR2 are sometimes referred to as intermediate frequency (IF) bands. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as the "sub-6 GHz" band. Similarly, FR2, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) designated as the "millimeter wave" band by the International Telecommunication Union (ITU), is often referred to as the "millimeter wave" band. Therefore, unless otherwise specified, it should be understood that the terms "sub-6GHz" and the like (if used herein) can broadly refer to frequencies less than 6GHz, frequencies within FR1, and / or intermediate frequency band frequencies (e.g., greater than 7.125GHz). Similarly, unless otherwise specified, it should be understood that the terms "millimeter wave" and the like (if used herein) can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or intermediate frequency band frequencies (e.g., less than 24.25GHz). It is contemplated that the frequencies included in FR1 and FR2 can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0035] In some aspects, devices of wireless network 100 may communicate with each other using licensed and / or unlicensed radio frequency spectrum bands. For example, base station 110 and UE 120 may communicate using RATs such as Licensed Assisted Access (LAA), Enhanced LAA (eLAA), Further Enhanced LAA (feLAA), and NR Unlicensed (NR-U). In some aspects, WLAN access point 140 and WLAN station 150 may communicate with each other using only unlicensed radio frequency spectrum bands (instead of licensed radio frequency spectrum bands). Therefore, base station 110, UE 120, WLAN access point 140, WLAN station 150, etc., may share unlicensed radio frequency spectrum bands. Because devices operating under different protocols (e.g., different RATs) may share unlicensed radio frequency spectrum bands, transmitting devices may need to compete for access to the unlicensed radio frequency spectrum bands before transmission.

[0036] For example, in a shared or unlicensed frequency band, a transmitting device may compete with other devices for channel access before transmitting on the shared or unlicensed channel to reduce and / or prevent collisions on the shared or unlicensed channel. To compete for channel access, the transmitting device may perform a channel access procedure (such as a Listen-Before-Speak (LBT) procedure or another type of channel access procedure) for shared or unlicensed frequency band channel access. The channel access procedure may be performed to determine whether the physical channel (e.g., the radio resources of the channel) is free to use or busy (e.g., being used by another wireless communication device (such as another UE, IoT device, or WLAN device, and other examples)). The channel access procedure may include: sensing or measuring the physical channel during a channel access gap (which may also be referred to as a contention window (CW)) (e.g., performing a Reference Signal Received Power (RSRP) measurement, detecting an energy level, or performing another type of measurement), and determining whether the shared or unlicensed channel is idle or busy based at least in part on the signals sensed or measured on the physical channel (e.g., at least in part on whether the measurement meets a threshold). If the transmitting device determines that the channel access procedure is successful, the transmitting device may perform one or more transmissions on a shared or unlicensed channel during the Transmission Opportunity (TXOP) period, which may extend the Channel Occupancy Time (COT).

[0037] As pointed out above, Figure 1 This is provided as an example. Other examples may differ from the one provided. Figure 1 The example described.

[0038] Figure 2 This is a diagram illustrating an example 200 of communication between base station 110 and UE 120 in wireless network 100 according to various aspects of this disclosure. Base station 110 may be equipped with T antennas 234a to 234t, and UE 120 may be equipped with R antennas 252a to 252r, wherein generally, T ≥ 1 and R ≥ 1.

[0039] At base station 110, transmitting processor 220 can receive data for one or more UEs from data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQI) received from each UE, process (e.g., code and modulate) the data for each UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. Transmitting processor 220 can also process system information (e.g., semi-static resource allocation information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper-layer signaling, etc.), and provide overhead symbols and control symbols. Transmitting processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), etc.) and synchronization signals (e.g., primary synchronization signal (PSS) and secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding, if applicable) on data symbols, control symbols, overhead symbols, and / or reference symbols, and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can (e.g., for OFDM, etc.) process its corresponding output symbol stream to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted via T antennas 234a to 234t respectively.

[0040] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations, and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can adjust (e.g., filter, amplify, down-convert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM, etc.) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide the detected symbols. Receive processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to data sink 260, and provide decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine the Received Reference Signal Power (RSRP), Received Signal Strength Indicator (RSSI), Received Reference Signal Quality (RSRQ), Channel Quality Indicator (CQI), etc. In some aspects, one or more components of the UE 120 may be included in the housing 284.

[0041] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, for example, in a core network. Network controller 130 may communicate with base station 110 via communication unit 294.

[0042] On the uplink, at UE 120, the transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmit processor 264 can also generate reference symbols for one or more reference signals. Symbols from the transmit processor 264 can be pre-coded (if applicable) by the TX MIMO processor 266, further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to base station 110. In some aspects, UE 120 includes a transceiver. The transceiver can include any combination of antenna 252, modulator and / or demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to execute aspects of any of the methods described herein, for example, as referenced Figure 6 , Figure 7 , Figures 8A-8D , Figures 9A-9D and / or Figure 10 Described.

[0043] At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 can provide decoded data to data sink 239 and decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246, which schedules UE 120 for downlink and / or uplink communication. In some aspects, base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modulator and / or demodulator 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute aspects of any of the methods described herein, for example, as referenced Figure 6 , Figure 7 , Figures 8A-8D , Figures 9A-9D and / or Figure 10 Described.

[0044] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120 and / or Figure 2 Any other components may perform one or more techniques associated with Physical Uplink Shared Channel (PUSCH) repetition during idle periods in Frame-Based Device (FBE) mode, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component can perform or direct, for example Figure 10The operation of process 1000 and / or other processes as described herein. Memory 242 and 282 may store data and program code for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code, program code, etc.) for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly, or after compilation, translation, interpretation, etc.), may cause one or more processors, UE 120 and / or base station 110 to perform or direct, for example... Figure 10 The operation of process 1000 and / or other processes as described herein. In some aspects, execution instructions may include run instructions, translation instructions, compilation instructions, interpretation instructions, etc.

[0045] In some aspects, UE 120 includes: elements for determining that a PUSCH repetition overlaps with an idle period associated with a fixed frame period (FFP) for communication on an unlicensed channel in FBE mode; and / or elements for avoiding transmission on the unlicensed channel during one or more symbols of the PUSCH repetition that overlap with the idle period. Elements for the UE to perform the operations described herein may include, for example, antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, modulator 254, controller / processor 280, and / or memory 282.

[0046] In some aspects, the UE includes: a unit for avoiding transmission on an unlicensed channel during one or more symbols of a PUSCH repetition outside of an idle period, based at least in part on the determination that a PUSCH repetition is associated with a Type A configuration.

[0047] In some aspects, the UE includes: a unit for segmenting a PUSCH repeat into multiple actual repeats, wherein the PUSCH repeat is segmented around an idle period at least in part based on determining that the PUSCH repeat is associated with a type B configuration; and / or a unit for transmitting one or more actual repeats of the multiple actual repeats that do not overlap with the idle period.

[0048] In some aspects, the UE includes: a unit for avoiding the transmission of one or more actual repetitions outside of idle periods and occupying a single symbol among multiple actual repetitions.

[0049] In some aspects, the UE includes: a unit for transmitting PUSCH repetitions that do not overlap with idle periods in the next FFP, based at least in part on the detection of downlink activity in the channel occupancy time associated with the next FFP.

[0050] In some aspects, the UE includes: a unit for performing a listen-before-speak procedure in an interval prior to a PUSCH repetition that does not overlap with an idle period, based at least in part on a threshold being met in the gap between an uplink transmission burst and a downlink transmission burst.

[0051] In some aspects, the UE includes: a unit for avoiding the transmission of one or more PUSCHs scheduled in the next FFP.

[0052] Although Figure 2 The boxes in the diagram are shown as different components, but the functions described above with respect to these boxes can be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by controller / processor 280 or under the control of controller / processor 280.

[0053] As pointed out above, Figure 2 This is provided as an example. Other examples may differ from the one provided. Figure 2 The example described.

[0054] Figure 3 This is a diagram illustrating example 300 of an unlicensed radio frequency band according to various aspects of this disclosure.

[0055] To meet the growing demands of the business, various efforts have been made to improve the spectrum efficiency in wireless networks, thereby increasing network capacity (e.g., through the use of higher-order modulation, advanced MIMO antenna technology, multi-cell coordination techniques, etc.). Another possible way to increase network capacity is to expand system bandwidth. However, the available spectrum in lower frequency bands that have traditionally been licensed or otherwise allocated to mobile network operators has become very scarce. Therefore, various technologies have been developed to enable Cellular Radio Access Technologies (RATs) to operate in unlicensed or other shared spectrum. For example, Licensed Assisted Access (LAA) uses downlink carrier aggregation to combine LTE in licensed frequency bands with LTE in unlicensed frequency bands (e.g., the 2.4 and / or 5 GHz bands already occupied by wireless LAN (WLAN) or “Wi-Fi” devices). In other examples, enhanced LAA (eLAA) and further enhanced LAA (feLAA) technologies implement both uplink and downlink LTE operations in unlicensed spectrum, MulteFire is an LTE-based technology that operates in both unlicensed and shared spectrum in standalone mode, NR-U implements NR operations in unlicensed spectrum, and so on.

[0056] For example, as in Figure 3As shown by reference numeral 305, unlicensed radio frequency (RF) bands (such as a 6 GHz unlicensed RF band) can span a frequency range and can utilize frequency division duplex (FDD). In an FDD system, a first band (e.g., a first sub-band of an unlicensed RF band) can be used for downlink communication, as shown by reference numeral 310, and a second band (e.g., a second sub-band of an unlicensed RF band) can be used for uplink communication, as shown by reference numeral 315. "Downlink communication" can refer to communication from a control node to a node (e.g., controlled, configured, and / or scheduled by the control node), such as from base station 110 to UE 120, from WLAN access point 140 to WLAN station 150, etc. "Uplink communication" can refer to communication from a node to a control node, such as from UE 120 to base station 110, from WLAN station 150 to WLAN access point 140, etc.

[0057] As in Figure 3 Furthermore, as shown by reference numeral 320, the downlink frequency band can be divided into multiple downlink channels (sometimes referred to as downlink frequency channels). Similarly, as shown by reference numeral 325, the uplink frequency band can be divided into multiple uplink channels (sometimes referred to as uplink frequency channels). As shown by reference numeral 330, each downlink channel can correspond to a single uplink channel. This can be referred to as channel pairing, where a downlink channel is paired with an uplink channel. In this configuration, control nodes and nodes can use a specific downlink channel for downlink communication and can use a specific uplink channel paired with or corresponding to that specific downlink channel for uplink communication. In example 300, downlink channel 1 is paired with uplink channel 1, downlink channel 2 is paired with uplink channel 2, downlink channel 3 is paired with uplink channel 3, and so on.

[0058] Although Figure 3Example 300 illustrates an unlicensed RF band utilizing FDD, but in some cases, unlicensed communication channels can utilize Time Division Duplex (TDD). For example, in an unlicensed communication channel utilizing TDD, uplink and downlink transmissions can be time-separated and performed on the same frequency channel. However, unlike TDD in licensed spectrum, subframes, time slots, symbols, etc., are not limited to being configured for uplink or downlink communication, and can be configured for downlink transmissions by the base station or uplink transmissions by the UE. Furthermore, unlicensed communication can support dynamic TDD, where uplink-downlink allocation can change over time to adapt to service conditions. For example, to enable dynamic TDD, radio devices (e.g., base stations, UEs, etc.) can determine when to transmit and in which resources to transmit based on the channel occupancy time structure. Typically, channel occupancy time can include multiple transmission intervals (e.g., multiple time slots), and each transmission interval can include one or more downlink resources, one or more uplink resources, one or more flexible resources, etc. In this way, the channel occupancy time structure reduces power consumption, channel access delay, etc.

[0059] In unlicensed RF bands (e.g., the 6 GHz unlicensed RF band), all or part of the band can be licensed to entities known as fixed service incumbents. Therefore, when operating a cellular RAT (e.g., using LAA, eLAA, feLAA, MulteFire, NR-U, etc.) in unlicensed spectrum, a challenge arises in ensuring fair coexistence with incumbent devices (e.g., WLAN devices) that may operate in the unlicensed spectrum. For example, before gaining access to an unlicensed channel and / or transmitting on it, transmitting devices (e.g., base station 110, UE 120, etc.) may need to perform a Listen-Before-Speak (LBT) procedure to compete for access to the unlicensed channel. The LBT procedure may include an Empty Channel Assessment (CCA) procedure to determine whether the unlicensed channel is available (e.g., not occupied by other transmitters). Specifically, the device performing the CCA procedure may detect the energy level on the unlicensed channel and determine whether the energy level meets (e.g., less than or equal to) a threshold (sometimes referred to as the energy detection threshold, etc.). When the energy level meets (e.g., is below) a threshold, the LBT process is considered successful, and the transmitting device can gain access to the unlicensed channel for a duration known as the channel occupancy time. During the channel occupancy time, the transmitting device can perform one or more transmissions without having to perform any additional LBT operations. However, when the energy level fails to meet (e.g., is equal to or exceeds) the energy detection threshold, the LBT process fails, and the transmitting device's contention for access to the unlicensed channel is unsuccessful.

[0060] In cases where the LBT process fails due to the CCA process, resulting in the determination that the unlicensed channel band is unavailable (e.g., because the energy level detected on the unlicensed channel indicates that another device is already using the channel), the CCA process can be re-executed at a later time. In environments where the transmitting device may lack access to the unlicensed channel (e.g., due to WLAN activity or transmissions by other devices), an extended CCA (eCCA) process can be employed to increase the likelihood that the transmitting device will successfully gain access to the unlicensed channel. For example, the transmitting device performing the eCCA process can execute a random number of CCA processes (from 1 to q) based on an eCCA counter. If and / or when the transmitting device senses that the channel has become idle, the transmitting device can begin a random waiting period based on the eCCA counter, and if the channel remains idle during the random waiting period, transmission begins.

[0061] As pointed out above, Figure 3 This is provided as an example. Other examples may differ from the one provided. Figure 3 The example described.

[0062] Figures 4A-4B This is a diagram illustrating an example 400 of a fixed frame period including channel occupancy time according to various aspects of this disclosure, during which one or more devices may transmit on an unlicensed channel.

[0063] In wireless networks supporting communication in unlicensed spectrum, the LBT process can be performed in either Load-Based Device (LBE) mode or Frame-Based Device (FBE) mode. In LBE mode, the transmitting device can perform channel sensing associated with the LBT process at any time and use random backoff if the unlicensed channel is found to be busy. In FBE mode, the base station can perform channel sensing associated with the LBT process at fixed time instances, and if the unlicensed channel is found to be busy, the base station waits before sensing the unlicensed channel again until the fixed time period has elapsed. Specifically, the fixed time instance when the base station performs channel sensing can be defined according to a Fixed Frame Period (FFP).

[0064] For example, Figure 4A An example FFP 410 base station is depicted, which can be used for communication in unlicensed spectrum. (e.g.) Figure 4A As shown, FFP 410 may include a Channel Occupancy Time (COT) 412, during which the base station may transmit one or more downlink communications. In some cases, see the following reference... Figure 4B As described, the base station can share the channel occupancy time 412 with the UE, enabling the UE to transmit one or more uplink communications during the channel occupancy time 412. For example... Figure 4A As shown, after the channel occupancy time 412, FFP 410 may also include an idle period 414 (sometimes referred to as an interval period, etc.) at the end of FFP 410. Specifically, the idle period 414 of FFP 410 provides time for performing the LBT process before the next FFP 410. The FFP 410 including the channel occupancy time 412 and the idle period 414 can have a duration of 1 millisecond (ms), 2 ms, 2.5 ms, 4 ms, 5 ms, or 10 ms. Within every two radio frames (e.g., even-numbered radio frames), the starting position of FFP 410 can be given by i*P, where i = {0, 1, ..., 20 / P-1}, and P is the duration of FFP 410 (in ms). For a given subcarrier spacing (SCS), idle time period 414 is calculated by dividing the upper limit of the specified minimum allowable idle time period by Ts, where the minimum duration of idle time period 414 is at most 100 microseconds (μs) and is 5% of the duration of FFP 410, and Ts is the symbol duration of the given SCS. Therefore, idle time period 414 can occupy no less than 5% of the duration of FFP 410, and channel occupancy time 412 can occupy no more than 95% of the duration of FFP 410.

[0065] In FBE mode, FFP configuration can be indicated in a system information block (e.g., SIB-1) or signaled to the UE in UE-specific radio resource control (RRC) signaling (e.g., for the FBE secondary cell use case). If the network indicates that the FBE mode will be used for downlink and / or uplink permission, a category 2 LBT (25μs) (e.g., an LBT without random backoff) or a category 4 LBT (e.g., an LBT with random backoff and a variable-size contention window), the UE can perform channel-aware measurements in a 9μs time slot (e.g., a single LBT) within a 25μs interval. If the UE detects one or more downlink signals or downlink channels (e.g., Physical Downlink Control Channel (PDCCH), Synchronization Signal Block (SSB), Physical Broadcast Channel (PBCH), Residual Minimum System Information (RMSI), Group Common PDCCH (GC-PDCCH), etc.) from the base station within FFP 410, UE transmissions may occur within FFP 410. The same 2-bit field can be used in both LBE and FBE modes to indicate LBT type, cyclic prefix extension, channel access priority level indication, etc.

[0066] In the NR-U FBE mode of version 16NR, only the base station can act as the initiator of acquiring channel occupancy time, and the UE can act only as the responder (e.g., sharing the channel occupancy time acquired by the base station). Therefore, in NR-U FBE mode, the channel access rules can be as follows: If the base station wants to initiate channel occupancy time 412, the Category 1 (Cat-1) LBT procedure may not apply, and the base station can perform the Category 2 (Cat-2) LBT procedure during the idle period 414 exactly before FFP 410. If the base station wants to send a downlink burst during the channel occupancy time 412 acquired by the base station, the base station can perform the Cat-1 LBT procedure if the gap with the previous downlink burst or the previous uplink burst is within 16 μs; otherwise, if the gap is greater than 16 μs, the Cat-2 LBT procedure can be performed. If the UE intends to transmit an uplink burst within the channel occupancy time 412 obtained by the base station, it can perform a Cat-1 LBT procedure if the gap with the previous downlink or uplink burst is within 16 μs; otherwise, it can perform a Cat-2 LBT procedure if the gap is greater than 16 μs. It is worth noting that the Cat-2 LBT procedure for FBE mode may differ from the Cat-2 LBT procedure (25 μs or 16 μs) in LBE mode. In some aspects, a 9 μs measurement may be required exactly before transmission, with at least 4 μs required for measurement. As indicated by reference numeral 416, the 9 μs measurement required to initiate channel occupancy time 412 in the next FFP 410 can be referred to as a single LBT. However, neither the Cat-1 LBT procedure nor the Cat-2 LBT procedure is suitable for cases where the UE will initiate channel occupancy time in FBE mode, because the UE cannot initiate channel occupancy time in version 16NR-U FBE mode.

[0067] Therefore, although wireless networks can be configured to use unlicensed spectrum to achieve faster data rates, provide a more responsive user experience, and offload services from licensed spectrum, a limitation of FBE mode is that the UE cannot initiate channel occupancy time to perform uplink transmissions. Therefore, to improve access, efficiency, and latency on unlicensed channels, wireless networks can allow the base station and UE to share channel occupancy time. For example, as in... Figure 4BAs shown by reference numeral 420 in the accompanying drawings, if a base station successfully competes for access to an unlicensed channel (e.g., by performing a passed LBT procedure), the base station may send a COT indicator to one or more UEs (e.g., using Group Common Downlink Control Information (DCI)), and the COT indicator from the base station may indicate that one or more UEs do not need to initiate FFP. Alternatively, one or more UEs may share the channel occupancy time acquired by the base station and transmit one or more uplink communications during the shared channel occupancy time.

[0068] In a fully controlled environment, it may be sufficient to allow the base station to compete for access to unlicensed channels and share the channel occupancy time initiated by the base station with one or more UEs. For example, a “fully controlled” environment can refer to an environment that is restricted or otherwise controlled so that no other RAT or operator is operating in the coverage area. Therefore, in a fully controlled environment, the LBT process may always pass, even in FBE mode. However, in practice, a fully controlled environment may be difficult to achieve because even if the environment is considered clean, there may be some other RAT operating. For example, even if no WLAN access points are deployed in the environment, employees working in a cleaned workshop may carry WLAN stations that send WLAN access probes. Therefore, in a nearly fully controlled environment, the probability of the LBT process performed by the base station failing is very small, which may lead to unacceptable performance for services with strict quality of service requirements (e.g., Ultra-Reliable Low-Latency Communication (URLLC), Industrial Internet of Things (IIoT) applications, etc.). For example, even with an LBT failure rate as low as 10%, -3 In the event of a failure of the LBT procedure performed by the base station at the beginning of the FFP, the base station and any UE communicating with the base station must abandon the entire FFP. Therefore, the probability that URLLC packets scheduled for delivery within the FFP cannot be delivered is 10%. -3 10 -3 The failure probability may not be sufficient to meet the reliability requirements of URLLC, which typically require 10. -6 Or higher reliability. Furthermore, these problems are exacerbated in uncontrolled environments where there may be many incumbent and / or competing devices vying for access to unlicensed channels.

[0069] Therefore, in situations where only the base station can compete for access to an unlicensed channel in FBE mode, if the LBT procedure performed by the base station fails, and / or the base station does not perform the LBT procedure because it has no downlink data to transmit, the UE may be unable to transmit on the uplink. Therefore, in cases where the base station fails to perform the LBT procedure or the UE does not detect a COT indicator from the base station (e.g., because the base station does not perform the LBT procedure due to lack of downlink activity, interference with downlink detection in the radio channel, etc.), the UE can be allowed to act as the initiating device to perform the LBT procedure and acquire channel occupancy time in FBE mode. For example, as shown by reference numeral 422, if the UE does not detect a COT indicator from the base station, the UE can perform the LBT procedure to start FFP and initiate a COT, in which it transmits one or more uplink communications. Therefore, as further shown by reference numeral 424, if the LBT procedure succeeds, the UE can transmit one or more uplink communications on the unlicensed channel, and the detection of uplink transmission from the UE can indicate to the base station that it can share the channel occupancy time acquired by the UE to perform downlink transmissions.

[0070] In some respects, allowing the UE to initiate channel occupancy time in FBE mode can improve access to unlicensed channels, reduce uplink latency, save power, and reduce interference. For example, when the UE initiates channel occupancy time, it can use the time to transmit the Physical Random Access Channel (PRACH) for initial network access. Specifically, during initial network access, the UE may not be configured with a System Information Radio Network Temporary Identifier (SI-RNTI) or another known RNTI (e.g., Downlink Control Information (DCI) scrambled using the SI-RNTI or other known RNTI) to monitor downlink transmissions to determine whether the base station has acquired the channel occupancy time. This can limit the UE's ability to transmit the PRACH for initial network access, thereby enabling the UE to initiate channel occupancy time before the UE is configured to monitor downlink transmissions from the base station to achieve uplink PRACH transmission.

[0071] Furthermore, allowing the UE to initiate channel occupancy time enables the UE to transmit the Physical Uplink Control Channel (PUCCH) and / or Physical Uplink Shared Channel (PUSCH) earlier in the FFP associated with the base station. For example, when sharing channel occupancy time acquired by the base station, the UE must confirm that the base station has acquired the channel occupancy time by detecting downlink activity in an earlier portion of the FFP in order to achieve transmission in a later portion of the FFP (e.g., the UE needs to reserve time in an earlier portion of the base station's FFP to allow time for downlink transmission from the base station, time for the UE to process downlink transmissions, etc.). Additionally, allowing the UE to initiate channel occupancy time can save power at the base station and / or reduce interference on unlicensed channels. For example, in order to share channel occupancy time and achieve uplink transmission within the shared channel occupancy time, the base station needs to actively transmit one or more downlink communications in an earlier portion of the FFP, even if the base station does not need to transmit downlink communications. This can result in additional power consumption at the base station and additional interference on unlicensed channels, which can be avoided by allowing the UE to initiate channel occupancy time. Furthermore, allowing the UE to initiate channel occupancy time instead of relying on shared channel occupancy time obtained by the base station can avoid problems that might otherwise arise when downlink signal detection has reliability limitations.

[0072] As pointed out above, Figures 4A-4B This is provided as an example. Other examples may differ from the one provided. Figures 4A-4B The example described.

[0073] Figures 5A-5B This is a diagram illustrating example 500 of PUSCH repetition according to various aspects of this disclosure. In wireless networks such as NR networks, a UE may transmit repetitions of specific uplink communications to increase reliability and / or robustness (e.g., to increase the likelihood that the base station will be able to successfully detect the UE and / or decode the uplink communications). For example, the UE may be configured to transmit multiple repetitions of PUSCH communications at multiple transmission times, using multiple panels and / or to multiple TRPs, and other examples. In this way, the UE reduces the likelihood that uplink communications will be dropped due to interruptions in uplink transmissions on the radio link (e.g., due to objects physically blocking the transmission path on the radio link and / or other communication interference with the radio link, etc.). In some cases, the UE may change one or more transmission parameters when transmitting repetitions of uplink communications. For example, the UE may use multiple different PUSCH transmission times occurring in different time slots, micro-time slots, symbols, etc., to transmit different repetitions of PUSCH communications (e.g., the same transport block). Generally, repetitions of PUSCH communications associated with dynamic granting and / or configured granting can have one of two types, which may be referred to herein as Type A and Type B.

[0074] For example, as in Figure 5A As shown by reference numeral 510 in the accompanying drawing, the UE can receive downlink control information (DCI) configured with PUSCH repetition of type A. In some aspects, the DCI configuring PUSCH repetition can instruct the UE to transmit K repetitions of PUSCH communication across K consecutive time slots, and the DCI can also instruct start and length indicator values ​​(SLIVs) to be applied to each PUSCH repetition. For example, the SLIV can indicate the start symbol S and symbol length L within the time slot, which are applied to the K repetitions of PUSCH communication across K consecutive time slots. For example, in Figure 5A In this configuration, the UE is configured to transmit two Type A repetitions of PUSCH communication (K=2), where each PUSCH repetition starts from the tenth symbol in the time slot (S=10), and each PUSCH repetition has a length of four symbols (L=4). Therefore, when the UE is configured to transmit multiple PUSCH repetitions with Type A configuration, the UE transmits K repetitions of PUSCH communication across K consecutive time slots, where the same SLIV is applied to each PUSCH repetition, and individual PUSCH repetitions are not allowed to cross time slot boundaries.

[0075] Alternatively or concurrently, as indicated by reference numeral 520 in the accompanying drawings, the UE may receive a DCI configured with type B PUSCH repetitions. In some aspects, the DCI configured with type B repetitions can schedule type B repetitions within and / or across time slots (e.g., type B repetitions may be allowed to cross time slot boundaries), can dynamically instruct the UE to transmit K nominal PUSCH repetitions, each with a nominal symbol length L, and can instruct to transmit K nominal PUSCH repetitions consecutively starting from a specific symbol within time slot S, wherein S and L are indicated in the SLIV parameters. Furthermore, in some aspects, the DCI may instruct nominal PUSCH inter-frequency hopping applicable to the K nominal PUSCH repetitions. For example, in Figure 5B In this configuration, the UE is configured to transmit two types of B repetitions (K=2) of PUSCH communication, each of which has a length of four symbols (L=4) and is transmitted across eight consecutive symbols (L*K=8) starting from the tenth symbol in the time slot (S=10).

[0076] Therefore, when a UE is configured to transmit multiple nominal PUSCH repeats with a type B configuration back-to-back, there is a possibility that one or more nominal PUSCH repeats will cross slot boundaries and / or conflict with downlink symbols or invalid symbols (e.g., guard symbols, etc.). Therefore, the UE can determine whether a nominal PUSCH repeat crosses slot boundaries and / or conflicts with downlink or invalid symbols (e.g., based on one or more predefined rules or semi-static RRC configuration information and other examples), and if so, can segment the nominal PUSCH repeat into one or more actual repeats around slot boundaries and / or downlink or invalid symbols.

[0077] For example, as in Figure 5B As shown by reference numeral 522 in the accompanying drawing, a Type B configuration can be provided to the UE to transmit two nominal PUSCH repeats (K=2), each having a length of seven symbols (L=7), and transmitted across fourteen consecutive symbols (L*K=14) starting from the fourth symbol in the time slot (S=10). In this case, the first nominal PUSCH repeat covers the seven symbols in the first time slot, and the second nominal PUSCH repeat covers the last three symbols in the first time slot and the first four symbols in the next time slot. In other words, the second nominal PUSCH repeat crosses the time slot boundary. Therefore, in some aspects, the UE can segment the second nominal PUSCH repeat around the time slot boundary, resulting in two actual PUSCH repeats that do not cross the time slot boundary. For example, as... Figure 5B As shown, the second nominal PUSCH repeat can be segmented into a first actual PUSCH repeat covering the last three symbols in the first time slot and a second actual PUSCH repeat covering the first four symbols in the next time slot.

[0078] Furthermore, in cases where a nominal PUSCH repeat conflicts with one or more downlink symbols and / or one or more invalid symbols, the nominal PUSCH repeat may be segmented around the downlink and / or invalid symbols. For example, as shown by reference numeral 524, the first symbol in the second time slot is a downlink symbol, and the second symbol in the second time slot is an invalid symbol (e.g., a guard symbol between a downlink symbol and an uplink symbol). Therefore, in addition to segmenting the second nominal PUSCH repeat around the time slot boundary, the nominal repeat may be segmented around the downlink or invalid symbols. For example, in some aspects, for each nominal PUSCH repeat that conflicts with one or more downlink and / or invalid symbols, the UE may identify one or more remaining symbols that are considered to be potentially valid symbols in which the actual PUSCH repeat of type B can be transmitted. Therefore, if the number of potentially valid symbols is greater than zero for a nominal PUSCH repeat, the nominal PUSCH repeat can be segmented into one or more actual PUSCH repeats, each of which comprises a continuous set of all potentially valid symbols (e.g., uplink symbols, flexible symbols, etc.) that can be used to send the PUSCH repeat within a time slot, except that actual PUSCH repeats covering a single symbol are discarded (e.g., not sent), unless the nominal length L has a configured value of one (1).

[0079] In some cases, a UE can be configured to transmit PUSCH repetitions of type A and / or type B on unlicensed channels. In such cases, transmissions on unlicensed channels can be configured in FBE mode, whereby the FFP, including the base station and the UE served by the base station, will avoid idle periods during which transmissions occur. For example, as described above, the device might be required to avoid transmissions during idle periods to achieve coexistence with WLAN devices that may be attempting to transmit on unlicensed channels, or to provide time for performing LBT procedures before the next FFP, and other examples. However, the behavior of handling PUSCH repetitions overlapping with idle periods of the FFP in FBE mode is generally undefined.

[0080] Some aspects described herein relate to techniques and apparatus for handling one or more PUSCH repetitions that at least partially overlap with idle periods in FBE mode. For example, a UE may determine that a PUSCH repetition overlaps with an idle period associated with an FFP used for communication on an unlicensed channel in FBE mode, and the UE may avoid transmission on the unlicensed channel during one or more symbols of the PUSCH repetition that coincide with that idle period. For example, in the case where a PUSCH repetition overlaps with an idle period in an FFP associated with a base station and / or an FFP associated with the UE, the UE may avoid transmitting a PUSCH repetition of type A. Alternatively, depending on whether the node associated with the FFP has acquired channel occupancy time, the UE may conditionally avoid transmitting type A repetitions that overlap with idle periods. In the case of type B repetitions that at least partially overlap with idle periods in an FFP, the UE may segment the nominal PUSCH repetition around the idle period and transmit only the actual repetitions that do not overlap with the idle period. Alternatively, depending on whether the node associated with the FFP has acquired channel occupancy time, the UE may conditionally segment nominal type B repetitions that overlap with idle periods. In this way, the UE can send one or more PUSCH repeats on an unlicensed channel while ensuring that no PUSCH transmissions occur during idle periods.

[0081] As pointed out above, Figures 5A-5B This is provided as an example. Other examples may differ from the one provided. Figures 5A-5B The example described.

[0082] Figure 6 This is a diagram illustrating example 600 associated with PUSCH repetition processing during idle periods in FBE mode, according to various aspects of this disclosure. Figure 6 As shown, Example 600 includes a base station capable of communicating with a UE in a wireless network. As described herein, the base station and the UE communicate on the uplink and downlink using one or more unlicensed channels in FBE mode. Furthermore, in Example 600, the base station can initiate an LBT procedure to obtain channel occupancy time in FBE mode, and the UE can share the channel occupancy time obtained by the base station if the UE detects one or more downlink transmissions from the base station. Figure 6In this configuration, the UE can be configured to transmit one or more PUSCH repeats of type A, and the FFP configured for the base station can include an idle period during which neither the base station nor the UE is permitted to transmit. Therefore, if one or more PUSCH repeats of type A overlap at least partially with an idle period in the FFP configured for the base station, the UE can determine how to handle the PUSCH repeats that overlap at least partially with the idle period.

[0083] For example, when a UE is configured to transmit one or more PUSCH repeats associated with a Type A configuration, the UE can discard any PUSCH repeats that overlap with an idle period in an FFP associated with the base station. In other words, the UE can avoid transmitting Type A PUSCH repeats when a PUSCH repeat overlaps with an idle period in an FFP associated with the base station. In this way, other devices (e.g., LBE devices) may have the opportunity to perform a Cat-4 LBT procedure during the idle period to gain access to an unlicensed channel. Furthermore, in the presence of one or more PUSCH repeats scheduled in the next FFP (e.g., after the transmission of PUSCH repeats is interrupted during an idle period), the transmission of the PUSCH repeats in the next FFP may be conditional, at least in part, based on whether the UE detects one or more downlink transmissions from the base station in that next FFP. Therefore, the UE can resume transmitting PUSCH repetitions scheduled in the next FFP, at least in part, based on detecting one or more downlink transmissions from the base station in the next FFP, but is subject to the restriction of not transmitting type A PUSCH repetitions during idle periods in the next FFP. For example, if the gap between a downlink transmission burst and an uplink transmission burst does not exceed 16 μs, the UE can resume transmitting PUSCH repetitions in the next FFP without sensing an unlicensed channel. Otherwise, if the gap between a downlink transmission burst and an uplink transmission burst exceeds 16 μs, the UE can resume transmitting PUSCH repetitions in the next FFP after a successful Cat-2 LBT procedure (e.g., sensing a sensing slot duration of at least 9 μs of idle time on an unlicensed channel within a 25 μs interval immediately preceding the transmission).

[0084] For example, such as Figure 6As shown, the UE can be configured to transmit four PUSCH repetitions of type A across four consecutive time slots, where each PUSCH repetition covers 11 symbols, and each PUSCH repetition starts from the fourth symbol in the time slot. In this case, the UE transmits a first PUSCH repetition (repetition #0) that does not overlap with the idle period in the FFP associated with the base station. However, the second PUSCH repetition (repetition #1) overlaps with the idle period in the FFP associated with the base station. Therefore, as shown by reference numeral 610, the UE avoids transmitting the second PUSCH repetition because it overlaps with the idle period in the FFP associated with the base station. Furthermore, in example 600, two additional PUSCH repetitions are scheduled in the next FFP associated with the base station. Therefore, as shown by reference numeral 612, the UE can resume the transmission of the PUSCH repetition in the next FFP at least in part based on the detection of downlink activity during the channel occupancy time of the FFP. For example, in Figure 6 In this scenario, the gap between downlink and uplink transmission bursts may exceed 16 μs, allowing the UE to perform a Cat-2 LBT procedure just before the third PUSCH repetition (repetition #2), and resume PUSCH repetition transmission if the Cat-2 LBT procedure passes. Alternatively, if downlink activity is detected and the gap between downlink and uplink transmission bursts does not exceed 16 μs, the UE can resume PUSCH repetition transmission without performing an LBT procedure. As further illustrated by reference numeral 614, the fourth PUSCH repetition (repetition #3) overlaps with an idle period in the next FFP associated with the base station, thus the UE avoids transmitting the fourth PUSCH repetition due to the overlap with an idle period in the FFP associated with the base station.

[0085] As pointed out above, Figure 6 This is provided as an example. Other examples may differ from the one provided. Figure 6 The example described.

[0086] Figure 7 This is a diagram illustrating example 700 associated with PUSCH repetition processing during idle periods in FBE mode, according to various aspects of this disclosure. Figure 7 As shown, Example 700 includes a base station capable of communicating with a UE in a wireless network. As described herein, the base station and the UE communicate on the uplink and downlink using one or more unlicensed channels in FBE mode. Furthermore, in Example 700, the base station can initiate an LBT procedure to obtain channel occupancy time in FBE mode, and the UE can share the channel occupancy time obtained by the base station if the UE detects one or more downlink transmissions from the base station. Figure 7In this configuration, the UE can be configured to transmit one or more PUSCH repeats of type B, and the FFP configured for the base station can include an idle period during which neither the base station nor the UE is permitted to transmit. Therefore, if one or more PUSCH repeats of type B overlap at least partially with an idle period in the FFP configured for the base station, the UE can determine how to handle the PUSCH repeats that overlap at least partially with the idle period.

[0087] For example, when a UE is configured to transmit nominal PUSCH repeats associated with a Type B configuration and overlapping with an idle period in an FFP associated with a base station, the UE can segment the nominal PUSCH repeats around the idle period, resulting in one or more actual repeats. Therefore, in addition to discarding actual PUSCH repeats occupying a single symbol, the UE can transmit only one or more actual PUSCH repeats that do not overlap with the idle period in the FFP associated with the base station. In other words, the UE can avoid transmitting Type B PUSCH repeats during one or more symbols overlapping with the idle period in the FFP associated with the base station. In this way, other devices (e.g., LBE devices) can have the opportunity to perform a Cat-4 LBT procedure during the idle period to gain access to an unlicensed channel. Furthermore, if one or more PUSCH repeats scheduled for the next FFP exist (e.g., after the transmission of PUSCH repeats is interrupted during an idle period), the transmission of PUSCH repeats in that next FFP can be conditional, at least in part, based on whether the UE detects one or more downlink transmissions from the base station in that next FFP. Therefore, the UE can resume transmitting PUSCH repetitions scheduled in the next FFP, at least in part, based on detecting one or more downlink transmissions from the base station in the next FFP, but is subject to the limitation of segmenting type B PUSCH repetitions that overlap with the idle period in the next FFP around the idle period. For example, if the gap between the downlink transmission burst and the uplink transmission burst does not exceed 16 μs, the UE can resume transmitting PUSCH repetitions in the next FFP without sensing an unlicensed channel. Otherwise, if the gap between the downlink transmission burst and the uplink transmission burst exceeds 16 μs, the UE can resume transmitting PUSCH repetitions in the next FFP after performing a successful Cat-2LBT procedure (e.g., sensing a sensing slot duration of at least 9 μs of idle time on an unlicensed channel within a 25 μs interval that ends immediately before transmission).

[0088] For example, such as Figure 7As shown, the UE can be configured to transmit six consecutive nominal PUSCH repetitions of type B, starting from the fifth symbol in a time slot, where each PUSCH repetition has a nominal length of 4 symbols. In this case, the UE transmits the first two nominal PUSCH repetitions (Rep#0 and Rep#1), which do not cross time slot boundaries, do not conflict with downlink or invalid symbols, and do not overlap with idle periods in the FFP associated with the base station. However, the third nominal PUSCH repetition crosses a time slot boundary and is therefore segmented into two actual repetitions (Rep#2 and Rep#3). The UE then transmits the next two nominal PUSCH repetitions (Rep#4 and Rep#5), which do not cross time slot boundaries, do not conflict with downlink or invalid symbols, and do not overlap with idle periods in the FFP associated with the base station. However, the next nominal repetition overlaps with idle periods in the FFP associated with the base station. Therefore, as shown by reference numeral 710 in the attached figure, the UE segments the nominal PUSCH repeats that overlap with the idle period in the FFP associated with the base station into actual PUSCH repeats (Rep#6) that do not overlap with the idle period. Thus, the UE can transmit the actual repeats that do not overlap with the idle period and can otherwise avoid transmission during the symbol period that overlaps with the idle period in the FFP associated with the base station.

[0089] Furthermore, in Example 700, the UE is configured to transmit an additional PUSCH repetition of type B in the next FFP associated with the base station. Therefore, as indicated by reference numeral 712, the UE can resume the transmission of the PUSCH repetition in the next FFP at least in part based on the detection of downlink activity during the channel occupancy time of the FFP. For example, in Figure 7 In this scenario, the gap between downlink and uplink transmission bursts may exceed 16 μs. Therefore, the UE can perform a Cat-2 LBT procedure exactly before a PUSCH repetition (repetition #1), and if the Cat-2 LBT procedure succeeds, it resumes transmitting PUSCH repetitions. If the Cat-2 LBT procedure fails, the UE can attempt another Cat-2 LBT procedure exactly before the next PUSCH repetition. Thus, in the event of a Cat-2 LBT procedure failure, the UE can continue attempting Cat-2 LBT procedures during a subsequent candidate LBT position that occurs exactly before a nominal or actual PUSCH repetition of type B. Alternatively, if downlink activity is detected and the gap between downlink and uplink transmission bursts does not exceed 16 μs, the UE can resume transmitting PUSCH repetitions without performing an LBT procedure.

[0090] As pointed out above, Figure 7 This is provided as an example. Other examples may differ from the one provided. Figure 7The example described.

[0091] Figures 8A-8D These are diagrams illustrating examples 800, 820, 840, and 860 related to PUSCH repetition processing during idle periods in FBE mode, according to various aspects of this disclosure. Figures 8A-8D As shown, Examples 800, 820, 840, and 860 include a base station capable of communicating with a UE in a wireless network. As described herein, the base station and the UE communicate on the uplink and downlink using one or more unlicensed channels in FBE mode. Furthermore, in Examples 800, 820, 840, and 860, the base station can initiate an LBT procedure to acquire channel occupancy time in FBE mode, and the UE can share the channel occupancy time acquired by the base station if the UE detects one or more downlink transmissions from the base station. Additionally, the UE can be allowed to initiate an LBT procedure to acquire channel occupancy time in FBE mode. Therefore, in Examples 800, 820, 840, and 860, a first FFP (e.g., "base station FFP") can be configured for the base station, and a second FFP (e.g., "UE FFP") can be configured for the UE. The base station FFP and the UE FFP can each include idle periods, and the UE can be configured to transmit one or more PUSCH repetitions of type A. Therefore, if one or more PUSCH repeats of type A overlap at least partially with idle periods in the base station FFP and / or UE FFP, the UE can determine how to handle (e.g., whether to send or discard) the PUSCH repeats.

[0092] For example, a UE can be configured to send one or more PUSCH repeats associated with a Type A configuration that do not overlap with idle periods in the base station FFP or UE FFP, and the UE can discard any PUSCH repeats that overlap with idle periods in the base station FFP or UE FFP. In this case, if a PUSCH repeat overlaps with an idle period in the base station FFP or UE FFP, the UE can avoid sending Type A PUSCH repeats regardless of whether the corresponding node acquires channel occupancy time. In this way, other devices (e.g., LBE devices) may have the opportunity to perform a Cat-4 LBT procedure during the idle periods of the base station FFP and UE FFP to acquire access to an unlicensed channel. For example, as Figure 8AAs shown, the UE can be configured to transmit four PUSCH repetitions of type A across four consecutive time slots, where each PUSCH repetition covers 11 symbols, and each PUSCH repetition starts from the fourth symbol in the time slot. In this case, the UE transmits a first PUSCH repetition (repetition #0) that does not overlap with the idle periods in the base station FFP or UE FFP. However, the second PUSCH repetition (repetition #1) overlaps with the idle periods in both the base station FFP and UE FFP. Therefore, as indicated by reference numeral 810, the UE avoids transmitting the second PUSCH repetition due to its overlap with the idle periods in both the base station FFP and UE FFP. Furthermore, as indicated by reference numeral 812, the UE avoids transmitting a third PUSCH repetition (repetition #2) due to its overlap with the idle periods in the UE FFP, and as indicated by reference numeral 814, the UE avoids transmitting a fourth PUSCH repetition (repetition #3) due to its overlap with the idle periods in both the UE FFP and base station FFP.

[0093] Alternatively, with both base station FFP and UE FFP configured and the UE configured to transmit PUSCH repetitions of type A, the UE can always discard PUSCH repetitions overlapping with idle periods in the base station FFP, regardless of whether the base station has acquired channel occupancy time. Furthermore, the UE can only discard PUSCH repetitions overlapping with idle periods in the UE FFP if it has acquired channel occupancy time. In this way, always discarding PUSCH repetitions overlapping with idle periods in the base station FFP can provide a guaranteed idle period in the base station FFP, during which other devices (e.g., LBE devices) can have the opportunity to compete for access to an unlicensed channel (e.g., if the UE fails to detect downlink activity from the base station and incorrectly determines that the base station has not yet acquired channel occupancy time). For example, as in... Figure 8B As shown by reference numeral 830, the UE can avoid sending a second PUSCH repetition of type A (repetition #1) due to overlap with the idle period in the base station's FFP. Similarly, as shown by reference numeral 832, even if the base station has not yet acquired the channel occupancy time, the UE can avoid sending a fourth PUSCH repetition (repetition #3) due to overlap with the idle period in the base station's FFP. Although in Figure 8B It is not specifically shown, but if the PUSCH repetition does not overlap with the idle period in the base station FFP and the UE has not yet acquired the channel occupancy time, the UE will send a PUSCH repetition that overlaps with the idle period in the UE FFP.

[0094] Alternatively, in cases where a PUSCH repetition of type A overlaps with an idle period in the FFP associated with a node, the UE can avoid sending the PUSCH repetition if the node acquires channel occupancy time; otherwise, the UE can send the PUSCH repetition if the node does not acquire channel occupancy time. In other words, PUSCH repetitions overlapping with idle periods in the base station's FFP can only be discarded if the base station acquires channel occupancy time, and PUSCH repetitions overlapping with idle periods in the UE's FFP can only be discarded if the UE acquires channel occupancy time. For example, as... Figure 8C As shown, the base station can acquire the channel occupancy time in the first FFP associated with the base station, but can choose not to acquire the channel occupancy time in the second FFP associated with the base station. Therefore, as indicated by reference numeral 850, the UE can avoid transmitting a PUSCH repetition (repetition #1) that overlaps with the idle period in the first base station FFP because the base station has already acquired the channel occupancy time. However, as indicated by reference numeral 852, the UE can still transmit a PUSCH repetition (repetition #3) even though it overlaps with the idle period in the base station FFP because the base station has not acquired the channel occupancy time in the second base station FFP. Furthermore, as... Figure 8C As shown, the UE does not acquire channel occupancy time in the first or second UE FFP, but acquires channel occupancy time in the third and fourth UE FFPs. Therefore, if PUSCH repetition would overlap with an idle period in the first or second UE FFP, the UE will still be allowed to send PUSCH repetition despite the overlap, because the UE has not acquired channel occupancy time. However, if PUSCH repetition would overlap with an idle period in the third or fourth UE FFP, the UE will avoid sending PUSCH repetition due to the overlap, because the UE has acquired channel occupancy time.

[0095] Alternatively, when the UE is configured to transmit multiple PUSCH repetitions of type A across different FFPs, the UE can be restricted to transmitting PUSCH repetitions only in the first FFP. Furthermore, in such a case, the UE can at least partially base its decisions on the above reference. Figures 8A-8C One or more of the described techniques are used to discard PUSCH repetitions that overlap with idle periods in the first FFP. For example, as in Figure 8DAs shown by reference numeral 870, the UE may discard the second PUSCH duplicate (duplicate #1) scheduled in the first base station FFP, because it overlaps with the idle period following the channel occupancy time acquired by the base station in the first base station FFP. Furthermore, as shown by reference numeral 872, due to restrictions on scheduling multiple PUSCH duplicates across different FFPs, PUSCH duplicates in the next FFP (e.g., the next base station FFP) are discarded.

[0096] As pointed out above, Figures 8A-8D This is provided as an example. Other examples may differ from the one provided. Figures 8A-8D The example described.

[0097] Figures 9A-9D These are figures illustrating examples 900, 920, 940, and 960 related to PUSCH repetition processing during idle periods in FBE mode, according to various aspects of this disclosure. Figures 9A-9D As shown, Examples 900, 920, 940, and 960 include a base station capable of communicating with a UE in a wireless network. As described herein, the base station and the UE communicate on the uplink and downlink using one or more unlicensed channels in FBE mode. Furthermore, in Examples 900, 920, 940, and 960, the base station can initiate an LBT procedure to acquire channel occupancy time in FBE mode, and the UE can share the channel occupancy time acquired by the base station if the UE detects one or more downlink transmissions from the base station. Additionally, the UE can be allowed to initiate an LBT procedure to acquire channel occupancy time in FBE mode. Therefore, in Examples 900, 920, 940, and 960, a first FFP (e.g., "base station FFP") can be configured for the base station, and a second FFP (e.g., "UE FFP") can be configured for the UE. The base station FFP and the UE FFP can each include idle periods, and the UE can be configured to transmit one or more nominal PUSCH repetitions of type B. Therefore, when a nominal PUSCH repetition at least partially overlaps with an idle period in the base station FFP and / or UE FFP, the UE can determine how to handle (e.g., whether to send, segment, or discard) the nominal PUSCH repetition.

[0098] For example, a UE can be configured to transmit one or more nominal PUSCH repeats that do not overlap with idle periods in either the base station FFP or the UE FFP, and the UE can segment any nominal PUSCH repeat that overlaps with idle periods in either the base station FFP or the UE FFP. For instance, if a nominal PUSCH repeat overlaps with an idle period in the base station FFP, the UE can segment the nominal PUSCH repeat around the idle period in the base station FFP; if a nominal PUSCH repeat overlaps with an idle period in the UE FFP, the UE can segment the nominal PUSCH repeat around the idle period in the UE FFP; or if a nominal PUSCH repeat overlaps with two idle periods, the UE can segment the nominal PUSCH repeat around the idle periods in both the base station FFP and the UE FFP. In this case, the UE can segment the nominal PUSCH repeat into one or more actual repeats and can only transmit actual repeats that do not overlap with idle periods in either FFP. In other words, the UE can avoid transmitting duplicate PUSCH of type B during symbols that coincide with idle periods in the base station FFP and symbols that coincide with idle periods in the UE FFP.

[0099] For example, as in Figure 9A As shown by reference numeral 910, the UE can segment nominal PUSCH repeats that overlap with idle periods in the first UE FFP. A nominal PUSCH repeat can have a nominal length of four symbols and can be segmented into actual repeats (Rep#3), which occupy two symbols that do not overlap with idle periods in the UE FFP. Therefore, the UE can transmit the actual repeat and can avoid transmission during the next two symbol periods that overlap with idle periods in the UE FFP. Similarly, as shown by reference numerals 912, 914, and 916, the UE can segment nominal PUSCH repeats that overlap with idle periods in the first base station FFP, nominal PUSCH repeats that overlap with idle periods in the second UE FFP, and nominal PUSCH repeats that overlap with idle periods in the third UE FFP, and the UE can transmit only the segments that do not overlap with idle periods in either the base station FFP or the UE FFP.

[0100] Alternatively, with both base station FFP and UE FFP configured and the UE configured to transmit PUSCH repetitions of type B, the UE can always segment PUSCH repetitions overlapping with idle periods in the base station FFP, regardless of whether the base station acquires channel occupancy time. Furthermore, segmentation of PUSCH repetitions overlapping with idle periods in the UE FFP can only be performed when the UE acquires channel occupancy time. In this way, always segmenting PUSCH repetitions overlapping with idle periods in the base station FFP provides a guaranteed idle period in the base station FFP, offering other devices the opportunity to compete for access to an unlicensed channel (e.g., if the UE fails to detect downlink activity from the base station and incorrectly determines that the base station has not yet acquired channel occupancy time). For example, as in... Figure 9B As shown in Figures 930-1 and 930-2, the UE can segment nominal (Type B) PUSCH repetitions that overlap with idle periods in the base station's FFP, regardless of whether the base station acquires channel occupancy time. However, if the UE does not acquire channel occupancy time, the UE does not segment nominal PUSCH repetitions that overlap with idle periods in the UE's FFP. For example, in Figure 9B In this process, the UE does not segment the third nominal PUSCH repeat (Rep#3) that overlaps with the idle period in the first UE FFP because the UE does not acquire the channel occupancy time. As further shown in Figure 932, the UE segments the nominal PUSCH repeat that overlaps with the idle period in the third UE FFP around the idle period in the third UE FFP because the UE acquires the channel occupancy time in the third UE FFP.

[0101] Alternatively, when a nominal PUSCH repetition of type B overlaps with an idle period in the FFP associated with the root node, if the node acquires channel occupancy time, the UE can segment the nominal PUSCH repetition around the idle period and only transmit segments that do not overlap with that idle period. Otherwise, if the node does not acquire channel occupancy time, the UE can avoid segmenting the nominal PUSCH repetition that overlaps with the idle period in the FFP associated with the root node. In other words, the UE can only segment the nominal PUSCH repetition that overlaps with the idle period in the base station's FFP around the idle period in the base station's FFP if the base station acquires channel occupancy time. Similarly, the UE can only segment the nominal PUSCH repetition that overlaps with the idle period in the UE's FFP around the idle period in the UE's FFP if the UE acquires channel occupancy time. For example, as Figure 9CAs shown, the base station can obtain the channel occupancy time in the first base station's FFP, but can choose not to obtain the channel occupancy time in the second base station's FFP. Therefore, as indicated by reference numeral 950 in the attached figure, the UE can segment the nominal PUSCH repetition that overlaps with the idle period in the first base station's FFP, and only transmit segments that do not overlap with the idle period in the first base station's FFP, because the base station has already obtained the channel occupancy time in the first base station's FFP. Furthermore, as... Figure 9C As shown, the UE does not acquire the channel occupancy time in the first or second UE FFP, but acquires the channel occupancy time in the third and fourth UE FFPs. Therefore, as indicated by reference numeral 952, the UE can segment nominal PUSCH repetitions that overlap with idle periods in the third UE FFP, and only transmit segments that do not overlap with idle periods in the third UE FFP, since the UE has already acquired the channel occupancy time in the third UE FFP. Furthermore, the UE can transmit one or more nominal PUSCH repetitions that overlap with idle periods in the first or second UE FFP without segmentation (e.g., Rep#4), because the UE has not acquired the channel occupancy time in the first or second UE FFP.

[0102] Alternatively, when the UE is configured to transmit multiple PUSCH repetitions of type B across different FFPs, the UE can be restricted to transmitting PUSCH repetitions only in the first FFP. Furthermore, in such a case, the UE can at least partially base its decisions on the above reference. Figures 9A-9C One or more of the described techniques are used to segment PUSCH repetitions that overlap with idle periods in the first FFP. For example, as in Figure 9D As shown by reference numeral 970, the UE can segment nominal PUSCH repeats that overlap with idle periods in the first base station FFP, and can only send actual repeats (e.g., segments of nominal PUSCH repeats) that do not overlap with idle periods in the first base station FFP. Furthermore, as shown by reference numeral 972, nominal PUSCH repeats in the next FFP (e.g., the next base station FFP) are discarded due to restrictions on scheduling multiple PUSCH repeats across different FFPs.

[0103] As pointed out above, Figures 9A-9D This is provided as an example. Other examples may differ from the one provided. Figures 9A-9D The example described.

[0104] Figure 10This is a diagram illustrating, for example, an example process 1000 performed by a UE according to various aspects of this disclosure. Example process 1000 is an example in which a UE (e.g., UE 120) performs operations associated with PUSCH repetition processing during an idle period in FBE mode.

[0105] like Figure 10 As shown, in some aspects, process 1000 may include: determining that a PUSCH repetition overlaps with an idle period associated with an FFP used for communication on an unlicensed channel in FBE mode (box 1010). For example, the UE (e.g., using...) Figure 11 The determining component 1108 described herein can determine that PUSCH repetitions overlap with idle periods associated with FFPs used for communication on unlicensed channels in FBE mode, as described above.

[0106] like Figure 10 Further shown, in some aspects, process 1000 may include: avoiding transmission on an unlicensed channel during one or more symbols of PUSCH repetition that coincide with idle periods (box 1020). For example, the UE (e.g., using...) Figure 11 The transmitting component 1104 described above can avoid transmitting on an unlicensed channel during one or more symbols of a PUSCH repeat that coincide with an idle period.

[0107] Process 1000 may include additional aspects, such as any single aspect or any combination thereof described below and / or in conjunction with one or more other process descriptions elsewhere described herein.

[0108] In the first aspect, process 1000 includes: at least in part based on determining that PUSCH repetition is associated with type A configuration, avoiding transmission on an unlicensed channel during one or more symbols of PUSCH repetition outside of idle periods.

[0109] In the second aspect, whether alone or in combination with the first aspect, transmissions on unlicensed channels are avoided during one or more symbols of PUSCH repetition outside of idle periods, or at least in part based on determining the association between FFP and the base station.

[0110] In the third aspect, either alone or in combination with one or more of the first and second aspects, the avoidance of transmission on the unlicensed channel during one or more symbols of PUSCH repetition outside of the idle period is based at least in part on determining that the FFP is associated with the UE and that the UE has acquired the channel occupancy time associated with the FFP.

[0111] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, transmission on an unlicensed channel is avoided during one or more symbols of PUSCH repetition outside of idle periods, or at least in part based on determining that the node associated with the FFP has acquired the channel occupancy time associated with the FFP.

[0112] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 1000 includes: segmenting a PUSCH repeat into a plurality of actual repeats, wherein the PUSCH repeat is segmented around an idle period at least in part based on determining that the PUSCH repeat is associated with a type B configuration, and process 1000 further includes: sending one or more actual repeats of the plurality of actual repeats that do not overlap with the idle period.

[0113] In the sixth aspect, either alone or in combination with one or more aspects from the first to the fifth aspects, process 1000 includes: avoiding the transmission of one or more actual repetitions outside of idle periods and occupying a single symbol among multiple actual repetitions.

[0114] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, PUSCH repetition is also segmented around idle periods based at least in part on determining that FFP is associated with a base station.

[0115] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, PUSCH repetition is also segmented around the idle period based at least in part on determining that the FFP is associated with the UE and that the UE has acquired the channel occupancy time associated with the FFP.

[0116] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, PUSCH repetition is also segmented around the idle period based at least in part on determining that the node associated with the FFP has acquired the channel occupancy time associated with the FFP.

[0117] In the tenth aspect, either alone or in combination with one or more aspects from the first to the ninth aspect, process 1000 includes: transmitting a PUSCH repetition that does not overlap with an idle period in the next FFP, based at least in part on the detection of downlink activity in the channel occupancy time associated with the next FFP.

[0118] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, PUSCH repeats are still sent at least in part based on the start symbol of the PUSCH repeat corresponding to the boundary of the actual repeat associated with the type B configuration.

[0119] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, process 1000 includes: performing an LBT process in the interval prior to a PUSCH repetition that does not overlap with an idle period, based at least in part on a threshold being met in the gap between an uplink transmission burst and a downlink transmission burst.

[0120] In the thirteenth aspect, alone or in combination with one or more aspects from the first to the twelfth aspects, process 1000 includes: avoiding the transmission of one or more PUSCHs scheduled in the next FFP.

[0121] Although Figure 10 An example box of process 1000 is shown, but in some aspects, process 1000 may include... Figure 10 The boxes depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Alternatively, two or more boxes in process 1000 may be executed in parallel.

[0122] Figure 11 This is a block diagram of an example device 1100 for wireless communication. Device 1100 may be a UE, or a UE may include device 1100. In some aspects, device 1100 includes a receiving component 1102 and a transmitting component 1104, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1100 can use the receiving component 1102 and the transmitting component 1104 to communicate with another device 1106 (such as a UE, a base station, or another wireless communication device). As further shown, device 1100 may include one or more of a determining component 1108, a segmentation component 1110, or an LBT component 1112, as well as other examples.

[0123] In some respects, device 1100 can be configured to perform the functions described herein. Figure 6 , Figure 7 , Figures 8A-8D and / or Figures 9A-9D One or more operations described herein. Alternatively or concurrently, device 1100 may be configured to perform one or more processes described herein, such as Figure 10 The process is 1000. In some aspects, Figure 11 The device 1100 and / or one or more components shown may include the above-described components. Figure 2 One or more components of the UE as described. Alternatively or in addition, Figure 11 One or more components shown can be combined with the above. Figure 2The description is implemented within one or more components. Alternatively, one or more components in the set of components may be implemented, at least partially, as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0124] Receiver 1102 may receive communications from device 1106, such as reference signals, control information, data communications, or combinations thereof. Receiver 1102 may provide the received communications to one or more other components of device 1100. In some aspects, receiver 1102 may perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signal to one or more other components of device 1106. In some aspects, receiver 1102 may include the combinations described above. Figure 2 The described UE includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0125] Transmitting component 1104 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1106. In some aspects, one or more other components of device 1106 can generate communications and provide the generated communications to transmitting component 1104 for transmission to device 1106. In some aspects, transmitting component 1104 can perform signal processing (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, and other examples) on the generated communications and can transmit the processed signal to device 1106. In some aspects, transmitting component 1104 can include the combinations described above. Figure 2 The described UE includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1104 may be co-located with the receive component 1102 in a transceiver.

[0126] Component 1108 can determine that PUSCH repetition overlaps with an idle period associated with an FFP used for communication on an unlicensed channel in FBE mode. In some aspects, component 1108 may include the above-described combination of... Figure 2The described UE includes one or more antennas, demodulators, MIMO detectors, receive processors, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. Transmit component 1104 can avoid transmission on unlicensed channels during one or more symbols of PUSCH repetition that coincide with idle periods.

[0127] The transmitting component 1104 may, at least in part, avoid transmitting on an unlicensed channel during one or more symbols of a PUSCH repeat outside of an idle period, based on the determination that the PUSCH repeat is associated with a type A configuration.

[0128] Segmentation component 1110 can segment PUSCH repeats into multiple actual repeats around idle periods, at least in part, based on determining that PUSCH repeats are associated with type B configuration. In some aspects, segmentation component 1110 may include the above-described combination of... Figure 2 The described UE includes one or more antennas, demodulators, MIMO detectors, receive processors, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof.

[0129] The sending component 1104 can send one or more actual repetitions that do not overlap with idle periods from a plurality of actual repetitions.

[0130] The sending component 1104 can avoid sending one or more actual repetitions outside of the idle period and occupying a single symbol from multiple actual repetitions.

[0131] The transmitting component 1104 may transmit PUSCH repetitions that do not overlap with idle periods in the next FFP, based at least in part on the detection of downlink activity during the channel occupancy time associated with the next FFP.

[0132] LBT component 1112 may perform the LBT process in the interval prior to a PUSCH repetition that does not overlap with the idle period, based at least in part on a threshold being met during the gap between uplink and downlink transmission bursts. In some aspects, LBT component 1112 may include the above-described combination of... Figure 2 The described UE includes one or more antennas, demodulators, MIMO detectors, receive processors, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof.

[0133] The sending component 1104 can avoid sending one or more PUSCHs that are scheduled in the next FFP.

[0134] Figure 11 The number and arrangement of components shown are provided as an example. In reality, they can exist in combination with... Figure 11The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 11 The two or more components shown can be implemented within a single component, or Figure 11 The single component shown can be implemented as multiple distributed components. Alternatively, Figure 11 The set (one or more) components shown can perform actions described by Figure 11 The other set of components shown performs one or more functions.

[0135] The foregoing disclosure provides explanations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or from practice in the aspects.

[0136] As used herein, the term "component" is intended to be interpreted broadly as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented using hardware, firmware, and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented using various forms of hardware, firmware, and / or combinations of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not intended to limit any aspect. Therefore, while the operation and behavior of the systems and / or methods are described herein without reference to specific software code, it is to be understood that the software and hardware can be designed to implement the systems and / or methods, at least in part, based on the descriptions herein.

[0137] As used in this article, depending on the context, satisfying the threshold can refer to a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0138] Even if a specific combination of features is recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the aspects. In fact, many of these features can be combined in ways that are not specifically recited in the claims and / or specifically disclosed in the specification. While each dependent claim listed below may directly depend on only one claim, the disclosure of each aspect includes a combination of each dependent claim with every other claim in the claim set. The phrase “at least one of” in the list of items refers to any combination of those items, including single members. For example, “at least one of: a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination of multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0139] No element, action, or instruction used herein should be construed as critical or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items mentioned in conjunction with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.) and may be used interchangeably with “one or more.” The phrase “only one” or similar language is used where only one item is expected. Furthermore, as used herein, the terms “has,” “have,” “having,” and / or similar terms are intended to be open-ended terms. Furthermore, unless explicitly stated otherwise, the phrase “based on” is intended to mean “at least partially based on.” Furthermore, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or” unless otherwise expressly stated (e.g., if used in combination with “any” or “only one”).

Claims

1. A method for wireless communication performed by a user equipment (UE), comprising: It is determined that the Physical Uplink Shared Channel (PUSCH) overlaps with idle periods, which are associated with fixed frame periods (FFP) used for communication on unlicensed channels in Frame-Based Device (FBE) mode. Avoid transmitting PUSCH repetitions on the unlicensed channel during one or more symbols of the PUSCH repetition that coincide with the idle period. Determine whether the idle period is associated with a first FFP associated with the base station or with a second FFP associated with the UE; as well as The PUSCH repeat is segmented into multiple actual repeats, wherein the PUSCH repeat is segmented around the idle period based at least in part on one or more of the following: Determine that the idle period is associated with the first FFP; or It is determined that the idle period is associated with the second FFP and that the UE has acquired the channel occupancy time associated with the second FFP.

2. The method according to claim 1, further comprising: Based at least in part on determining that the PUSCH repetition is associated with a Type A configuration, transmissions on the unlicensed channel are avoided during one or more symbols outside the idle period of the PUSCH repetition.

3. The method according to claim 2, wherein, Whether to avoid transmission on the unlicensed channel during the PUSCH repetition outside the idle period or at least in part based on determining that the FFP is associated with the base station.

4. The method according to claim 2, wherein, Whether to avoid transmission on the unlicensed channel during the PUSCH repeats outside the idle period or at least in part based on determining that the FFP is associated with the UE and that the UE has acquired the channel occupancy time associated with the FFP.

5. The method according to claim 2, wherein, Whether to avoid transmission on the unlicensed channel during the PUSCH repeats outside the idle period or at least in part based on determining that the node associated with the FFP has acquired the channel occupancy time associated with the FFP.

6. The method according to claim 1, in, The PUSCH repeat is segmented around the idle period based at least in part on the determination that the PUSCH repeat is associated with a type B configuration; as well as The method further includes sending one or more actual repetitions from the plurality of actual repetitions that do not overlap with the idle period.

7. The method according to claim 6, further comprising: Avoid sending one or more actual repetitions outside the idle period and occupying a single symbol.

8. The method according to claim 6, wherein, The PUSCH repeating is also segmented around the idle period based at least in part on determining that the node associated with the FFP has acquired the channel occupancy time associated with the FFP.

9. The method according to claim 1, further comprising: The PUSCH repetition that does not overlap with the idle period is transmitted in the next FFP based at least in part on the detection of downlink activity during the channel occupancy time associated with the next FFP.

10. The method according to claim 9, wherein, The PUSCH repeat is also sent at least in part based on the start symbol of the PUSCH repeat, which corresponds to the boundary of the actual repeat associated with the type B configuration.

11. The method of claim 9, further comprising: The listen-before-speak process is performed in the interval prior to the PUSCH repetition that does not overlap with the idle period, based at least in part on the threshold being met in the gap between the uplink and downlink transmission bursts.

12. The method according to claim 1, further comprising: Avoid sending duplicate PUSCHs scheduled in the next FFP.

13. A user equipment (UE) for wireless communication, comprising: One or more memory units; as well as One or more processors operatively coupled to the one or more memories, wherein the one or more memories and the one or more processors are configured to: It is determined that the Physical Uplink Shared Channel (PUSCH) overlaps with idle periods, which are associated with fixed frame periods (FFP) used for communication on unlicensed channels in Frame-Based Device (FBE) mode. Avoid transmitting PUSCH repetitions on the unlicensed channel during one or more symbols of the PUSCH repetition that coincide with the idle period. Determine whether the idle period is associated with a first FFP associated with the base station or with a second FFP associated with the UE; as well as The PUSCH repeat is segmented into multiple actual repeats, wherein the PUSCH repeat is segmented around the idle period based at least in part on one or more of the following: Determine that the idle period is associated with the first FFP; or It is determined that the idle period is associated with the second FFP and that the UE has acquired the channel occupancy time associated with the second FFP.

14. The UE according to claim 13, wherein, The one or more processors are further configured to: Based at least in part on determining that the PUSCH repetition is associated with a Type A configuration, transmissions on the unlicensed channel are avoided during one or more symbols outside the idle period of the PUSCH repetition.

15. The UE according to claim 14, wherein, Whether to avoid transmission on the unlicensed channel during the PUSCH repetition outside the idle period or at least in part based on determining that the FFP is associated with the base station.

16. The UE according to claim 14, wherein, Whether to avoid transmission on the unlicensed channel during the PUSCH repeats outside the idle period or at least in part based on determining that the FFP is associated with the UE and that the UE has acquired the channel occupancy time associated with the FFP.

17. The UE according to claim 14, wherein, Whether to avoid transmission on the unlicensed channel during the PUSCH repeats outside the idle period or at least in part based on determining that the node associated with the FFP has acquired the channel occupancy time associated with the FFP.

18. The UE according to claim 13, in, The PUSCH repeats are segmented around the idle period at least in part based on determining that the PUSCH repeats are associated with a type B configuration; and The one or more processors are also configured to send one or more actual repetitions of the plurality of actual repetitions that do not overlap with the idle period.

19. The UE according to claim 18, wherein, The one or more processors are further configured to: Avoid sending one or more actual repetitions outside the idle period and occupying a single symbol.

20. The UE according to claim 18, wherein, The PUSCH repeating is also segmented around the idle period based at least in part on determining that the node associated with the FFP has acquired the channel occupancy time associated with the FFP.

21. The UE according to claim 13, wherein, The one or more processors are further configured to: The PUSCH repetition that does not overlap with the idle period is transmitted in the next FFP based at least in part on the detection of downlink activity during the channel occupancy time associated with the next FFP.

22. The UE according to claim 21, wherein, The PUSCH repeat is also sent at least in part based on the start symbol of the PUSCH repeat, which corresponds to the boundary of the actual repeat associated with the type B configuration.

23. The UE according to claim 21, wherein, The one or more processors are further configured to: The listen-before-speak process is performed in the interval prior to the PUSCH repetition that does not overlap with the idle period, based at least in part on the threshold being met in the gap between the uplink and downlink transmission bursts.

24. The UE according to claim 13, wherein, The one or more processors are further configured to: Avoid sending duplicate PUSCHs scheduled in the next FFP.

25. A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising: One or more instructions, which, when executed by one or more processors of a user equipment (UE), cause the UE to perform the following operations: It is determined that the Physical Uplink Shared Channel (PUSCH) overlaps with idle periods, which are associated with fixed frame periods (FFP) used for communication on unlicensed channels in Frame-Based Device (FBE) mode. Avoid transmitting PUSCH repetitions on the unlicensed channel during one or more symbols of the PUSCH repetition that coincide with the idle period. Determine whether the idle period is associated with a first FFP associated with the base station or with a second FFP associated with the UE; as well as The PUSCH repeat is segmented into multiple actual repeats, wherein the PUSCH repeat is segmented around the idle period based at least in part on one or more of the following: Determine that the idle period is associated with the first FFP; or It is determined that the idle period is associated with the second FFP and that the UE has acquired the channel occupancy time associated with the second FFP.

26. The non-transitory computer-readable medium according to claim 25, in, The PUSCH repeats are segmented around the idle period at least in part based on determining that the PUSCH repeats are associated with a type B configuration; and The instruction set also causes the UE to send one or more actual repetitions that do not overlap with the idle period from among the plurality of actual repetitions.

27. The non-transitory computer-readable medium of claim 26, wherein the instruction set further causes the UE to perform the following operations: Avoid sending one or more actual repetitions outside the idle period and occupying a single symbol.

28. A user equipment (UE) for wireless communication, comprising: Units for determining the overlap of Physical Uplink Shared Channel (PUSCH) repetitions and idle periods, the idle periods being associated with fixed frame periods (FFP) for communication on unlicensed channels in Frame-Based Device (FBE) mode. A unit for preventing the transmission of PUSCH repetition on the unlicensed channel during one or more symbols of the PUSCH repetition that coincide with the idle period. A unit for determining whether the idle period is associated with a first FFP associated with the base station or with a second FFP associated with the UE; as well as Units for segmenting the PUSCH repetition into multiple actual repetitions, wherein the PUSCH repetition is segmented around the idle period based at least in part on one or more of the following: Determine that the idle period is associated with the first FFP; or It is determined that the idle period is associated with the second FFP and that the UE has acquired the channel occupancy time associated with the second FFP.

29. The UE according to claim 28, in, The PUSCH repeats are segmented around the idle period at least in part based on determining that the PUSCH repeats are associated with a type B configuration; and The UE also includes a unit for transmitting one or more actual repetitions that do not overlap with the idle period from among the plurality of actual repetitions.

30. The UE according to claim 29, further comprising: Units used to avoid sending one or more actual repetitions outside the idle period and occupying a single symbol among the multiple actual repetitions.

Images