Listen first, speak laterFailureRecoverCancel

Abstract

A device for performing listen-before-talk failure recovery and canceling a recovery response based on a trigger is provided. The device can monitor a consistent listen-before-talk (LBT) failure of an uplink transmission to a base station, determine whether to perform an LBT recovery response based on the monitoring, detect a trigger, and cancel the LBT recovery response or reset the monitoring based on the trigger.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATION(S)

[0002] This application claims the benefit of U.S. Provisional Application Serial No. 62 / 989,463, entitled “LISTEN BEFORE TALK FAILURERECOVERY CANCELLATION,” filed on March 13, 2020, and U.S. Patent Application No. 17 / 197,698, entitled “LISTEN BEFORE TALK FAILURERECOVERY CANCELLATION,” filed on March 10, 2021, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to communication systems and, more particularly, to wireless communication systems utilizing listen-before-talk. Background Art

[0004] Wireless communication systems are widely deployed. Wireless communication systems are widely deployed to provide various telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued mobile broadband evolution promulgated by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Certain aspects of 5GNR may be based on the 4G Long Term Evolution (LTE) standard. 5G NR technology requires further improvements. These improvements may also be applicable to other multiple access technologies and telecommunication standards that adopt these technologies. Summary of the invention

[0006] The following presents a simplified summary of one or more aspects to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is neither intended to identify key or important elements of all aspects, nor to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that is presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a user equipment (UE). The apparatus may monitor a consistent listen-before-talk (LBT) failure of transmissions between a base station and the UE, determine whether to perform an LBT recovery response based on the monitoring, detect a trigger, and cancel the LBT recovery response or reset the monitoring based on the trigger.

[0008] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a base station. The apparatus may transmit an RRC reconfiguration message to a user equipment (UE) to reconfigure parameters of the UE, and transmit a listen-before-talk (LBT) failure response cancellation indicator to the UE based on the parameters.

[0009] To accomplish the foregoing and related ends, one or more aspects include features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features represent only a few of the various ways in which the principles of the various aspects may be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A , 2B , 2C and 2D are diagrams showing examples of a first 5G / NR frame, a DL channel within a 5G / NR subframe, a second 5G / NR frame and a UL channel within a 5G / NR subframe, respectively.

[0012] Figure 3 is a diagram showing an example of a base station and a user equipment (UE) in an access network.

[0013] Figure 4 is a communication flow diagram illustrating a listen-before-talk (LBT) failure recovery response.

[0014] Figure 5 is a communication flow diagram illustrating recovery response cancellation based on received indicators.

[0015] Figure 6is a communication flow diagram illustrating recovery response cancellation based on RRC reconfiguration with synchronization.

[0016] Figure 7 is a communication flow diagram illustrating recovery response cancellation based on reconfigured parameters.

[0017] Figure 8 is a communication flow diagram illustrating recovery response cancellation based on radio link failure.

[0018] Fig. 9 is a communication flow chart showing the cancellation of the recovery response in the conditional switching.

[0019] Fig.10 is a communication flow diagram illustrating recovery response cancellation in dual active protocol stack switching.

[0020] Fig.11 is a communication flow diagram illustrating recovery response cancellation in a failed dual active protocol stack switch.

[0021] Fig.12 is a flow chart of a wireless communication method.

[0022] Fig.13 is a flow chart of a wireless communication method.

[0023] Fig.14 is a diagram illustrating an example of a hardware implementation for an example apparatus.

[0024] Fig.15 is a diagram illustrating another example of a hardware implementation for another example apparatus. DETAILED DESCRIPTION

[0025] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obfuscation of such concepts.

[0026] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0027] For example, an element or any part of an element or any combination of elements may be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system may execute software. Software should be broadly interpreted as representing instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or others.

[0028] Therefore, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on a computer-readable medium or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. The storage medium may be any available medium that a computer can access. By way of example and not limitation, such a computer-readable medium may include a random access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), an optical disk storage device, a magnetic disk storage device, other magnetic storage devices, a combination of computer-readable media of the above types, or any other medium that can be used to store computer executable code in the form of computer-accessible instructions or data structures.

[0029] Figure 1 1 is a diagram showing an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0030] A base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with the core network 190 via a second backhaul link 184. The base station 102 may perform one or more of the following functions, among other functions: user data transmission, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, non-access stratum (NAS) message distribution, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and device tracking, RAN information management (RIM), paging, positioning, and warning messaging. The base stations 102 may communicate with each other directly or indirectly (eg, through the EPC 160 or the core network 190) via a third backhaul link 134 (eg, an X2 interface). The third backhaul link 134 may be wired or wireless.

[0031] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' can have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network can also include a home evolved Node B (eNB) (HeNB), which can provide services to a restricted group called a closed subscriber group (CSG). The communication link 120 between base station 102 and UE 104 can include an uplink (UL) (also called a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also called a forward link) transmission from base station 102 to UE 104. The communication link 120 can use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link can be through one or more carriers. The base station 102 / UE 104 may use spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated for DL ​​than for UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0032] Certain UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through various wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on IEEE 802.11 standards, LTE, or NR.

[0033] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 in the 5 GHz unlicensed spectrum via a communication link 154. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available prior to communication.

[0034] The small cell 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may utilize NR and use the same 5 GHz unlicensed spectrum used by the Wi-Fi AP 150. The small cell 102' utilizing NR in the unlicensed spectrum may expand the coverage of the access network and / or increase the capacity of the access network.

[0035] Base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include and / or be referred to as an eNB, gNodeB (gNB), or other type of base station. Some base stations, such as gNB 180, may operate in traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near mmW frequencies for communicating with UE 104. When gNB 180 operates in mmW or near mmW frequencies, gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is part of the radio frequency (RF) in the electromagnetic spectrum. EHF ranges from 30 GHz to 300 GHz, with wavelengths between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near mmW may extend down to frequencies of 3 GHz with wavelengths of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz and is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands (e.g., 3 GHz-300 GHz) have extremely high path losses and short distances. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays to facilitate beamforming.

[0036] Base station 180 may transmit beamformed signals in one or more transmit directions 182' to UE 104. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182". UE 104 may also transmit beamformed signals in one or more transmit directions to base station 180. Base station 180 may receive beamformed signals in one or more receive directions from UE 104. Base station 180 / UE 104 may perform beam training to determine the best receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions of base station 180 may be the same or may be different. The transmit and receive directions of UE 104 may be the same or may be different.

[0037] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and collecting charging information related to eMBMS.

[0038] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Typically, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services.

[0039] A base station may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other suitable term. Base station 102 provides an access point to EPC 160 or core network 190 for UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a health care device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0040] Reference again Figure 1 In some aspects, the UE 104 and / or the base station 180 may include a listen-before-talk (LBT) failure recovery response cancellation component 198 configured to determine a consistent LBT failure, perform a consistent LBT failure recovery response, and respond to the consistent LBT failure recovery response that triggers cancellation of the plan. While the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0041] Figure 2A FIG200 is a diagram showing an example of a first subframe within a 5G / NR frame structure. Figure 2B FIG230 is a diagram showing an example of DL channels within a 5G / NR subframe. Figure 2C Figure 250 shows an example of a second subframe within a 5G / NR frame structure. Figure 2D FIG280 is a diagram showing an example of UL channels within a 5G / NR subframe. The 5G / NR frame structure may be FDD, where, for a particular set of subcarriers (carrier system bandwidth), subframes within a subcarrier set are dedicated to either DL or UL, or the 5G / NR frame structure may be TDD, where, for a particular set of subcarriers (carrier system bandwidth), subframes within a subcarrier set are dedicated to both DL and UL. Figure 2A , 2C In the example provided, it is assumed that the 5G / NR frame structure is TDD, where subframe 4 is configured with slot format 28 (mainly DL), where D is DL, U is UL, and X is flexible for use between DL / UL, and subframe 3 is configured with slot format 34 (mainly UL). Although subframes 3 and 4 are shown in slot formats 34 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format (dynamically through DL control information (DCI), or semi-statically / statically through radio resource control (RRC) signaling) through the received slot format indicator (SFI). Please note that the description below also applies to the 5G / NR frame structure for TDD.

[0042] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10 milliseconds) may be divided into 10 equally sized subframes (1 millisecond). Each subframe may include one or more time slots. A subframe may also include a mini-time slot, which may include 7, 4, or 2 symbols. Depending on the time slot configuration, each time slot may include 7 or 14 symbols. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter set (numerology). For slot configuration 0, different parameter sets μ0 to 5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Therefore, for slot configuration 0 and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframes. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 5. Thus, parameter set μ=0 has a subcarrier spacing of 15kHz, while parameter set μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ = 2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0043] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0044] like Figure 2A As shown, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a specific configuration). x, where 100x is the port number, but other DM-RS configurations are also possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0045] Figure 2B Examples of various DL channels within a subframe of a frame are shown. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in one OFDM symbol. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of the frame. The UE 104 uses the PSS to determine the subframe / symbol timing and the physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of the frame. The UE uses the SSS to determine the physical layer cell identification group number and the radio frame timing. Based on the physical layer identification and the physical layer cell identification group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the location of the above-mentioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0046] like Figure 2C As shown, some of the REs carry DM-RS for channel estimation at the base station (indicated as R for one specific configuration, but other DM-RS configurations are also possible). The UE can transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be transmitted in the first one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a sounding reference signal (SRS). The SRS can be transmitted in the last symbol of the subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The base station can use the SRS for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0047] Figure 2DExamples of various UL channels within a subframe of a frame are shown. The PUCCH may be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may be additionally used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0048] Figure 3 3 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functions. Layer 3 includes a radio resource control (RRC) layer, while layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functions associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and switching support functions; RLC layer functions associated with transmission of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority processing, and logical channel priority processing.

[0049] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1 includes a physical (PHY) layer, which may include error detection of transmission channels, forward error correction (FEC) encoding / decoding of transmission channels, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time domain and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes, as well as to perform spatial processing. The channel estimate may be derived from a reference signal and / or channel state feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0050] At the UE 350, each receiver 354RX receives a signal through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0051] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0052] Similar to the functions described for DL ​​transmission performed in conjunction with the base station 310, the controller / processor 359 provides RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority processing, and logical channel priority processing.

[0053] The TX processor 368 may select an appropriate coding and modulation scheme and facilitate spatial processing using channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0054] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0055] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0056] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 198 related aspects.

[0057] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 198 related aspects.

[0058] Figure 4 is a communication flow diagram 400 illustrating a listen-before-talk (LBT) failure recovery response.

[0059] UE 402 may attempt to transmit uplink data 410 to base station 404. UE 402 may transmit uplink data 410 to base station 404 on a spectrum shared with other protocols. For example, UE 402 may transmit uplink data 410 on an unlicensed spectrum shared with WiFi. Base station 404 may include a primary cell for communicating on a primary carrier and a secondary cell for communicating on other carriers. UE 402 may transmit uplink data 410 to the primary cell or the secondary cell of base station 404. In some aspects, in the case where UE 402 utilizes dual connectivity, base station 404 may be a primary node or a secondary node.

[0060] UE 402 may utilize an LBT process (e.g., a channel clearing process) to transmit uplink data 410. For example, UE 402 may monitor an uplink channel to determine whether another device is transmitting on the channel, and if no other device is transmitting on the channel, UE 402 may transmit uplink data 410. In some aspects, UE 402 may monitor the channel within a set time period (e.g., 25 μs), and if no other device is transmitting on the channel during the set time period, it may transmit on the channel (e.g., Category 2 LBT). In some aspects, UE 402 may have a contention window and may randomly select a number within the contention window. UE 402 may count down from the selected number, and if the channel remains clear until the countdown reaches zero, UE 402 may transmit on the channel (e.g., Category 4 LBT).

[0061] As shown at 412, the UE 402 can monitor for consistent LBT failures as it transmits uplink data 410 to the base station 404. LBT failures occur when the UE 402 monitors the uplink channel during the LBT process and determines that it cannot transmit on the channel because another device is already transmitting on the channel. Consistent LBT failures occur when multiple LBT failures occur during a period of time, when multiple LBT failures occur without a set amount of time between failures, or when a set percentage of LBT attempts result in an LBT failure.

[0062] As shown at 414, UE 402 may determine that a consistent LBT failure has occurred on the uplink. For example, when an LBT failure occurs, UE 402 may start a timer and increment a counter. If another LBT failure occurs before the timer expires, UE 402 may again increment the counter and reset the timer. If the timer expires without an LBT failure, UE 402 may reset the counter to zero. If the counter exceeds a threshold, UE 402 may determine that a consistent LBT failure has occurred.

[0063] As shown at 416, upon determining that a consistent LBT failure has occurred, the UE 402 may perform a consistent LBT failure recovery response (hereinafter referred to as a "recovery response"). The recovery response may depend on whether the consistent LBT failure occurred on a primary cell or a secondary cell. If the consistent LBT failure occurs on a primary cell (or, for example, on a primary secondary cell (PSCell) in the case where the base station 404 is a secondary node), the UE 402 may change the bandwidth part (BWP) used for the uplink, RACH with the base station 404 on the new BWP, and may resume transmitting uplink data 410 on the new BWP. If the consistent LBT failure occurs on a secondary cell, the UE 402 may report the failure to the network (e.g., to the base station 404), and in some aspects, may stop transmitting uplink data 410 to the base station 404. In response to a report indicating a consistent LBT failure on a secondary cell, the base station 404 may deactivate or reconfigure the secondary cell.

[0064] In some aspects, before executing the recovery response shown at 416, the UE 402 may detect a trigger. Upon detecting the trigger, the UE 402 may cancel the recovery response (e.g., may not execute the recovery response). In some aspects, the UE 402 may reset the monitoring shown at 412 in response to the trigger even if a consistent LBT failure has not been determined. For example, in the case where the UE 402 increments a counter based on the LBT failure to determine a consistent LBT failure, the UE 402 may set the counter to zero in response to the trigger. Examples of triggers are discussed below.

[0065] Figure 5 5 is a communication flow diagram 500 illustrating recovery response cancellation based on received indicators. UE 502 may transmit uplink data 510 to base station 504 using an LBT process, and as shown at 512, UE 502 may monitor for consistent LBT failures (e.g., as described above with respect to FIG. 5 ) when transmitting uplink data 510 to base station 504. Figure 4 In some aspects, as shown at 514, UE 502 may determine that a consistent LBT failure has occurred (e.g., as described above with respect to Figure 4 described above).

[0066] The base station 504 may transmit an RRC reconfiguration message 520 to the UE 502. The RRC reconfiguration message 520 may reconfigure parameters of the UE 502. The base station 504 may also transmit an LBT failure response cancel indicator 522 to the UE 502. The LBT failure response cancel indicator 522 may be incorporated into the RRC reconfiguration message 520, or may be transmitted separately. The LBT failure response cancel indicator 522 may instruct the UE 502 to cancel a recovery response and / or reset monitoring for a consistent LBT failure. In response to receiving the LBT failure response cancel indicator 522, the UE 502 may cancel a recovery response planned in response to determining a consistent LBT failure as shown at 514, and / or may reset monitoring as shown at 512.

[0067] The RRC reconfiguration message 520 may reconfigure parameters of the UE 502 that affect the LBT failures, and which may reduce the number of LBT failures experienced or may make a recovery response unnecessary. The base station 504 may transmit an LBT failure response cancel indicator 522, instructing the UE 502 to cancel the recovery response and / or reset monitoring of consistent LBT failures associated with the parameters reconfigured by the RRC message 520.

[0068] In some aspects, the LBT failure response cancel indicator 522 may indicate that the UE 502 cancels a recovery response and / or resets monitoring for a consistent LBT failure that occurs on a specified BWP or a specified cell (e.g., a primary cell or a secondary cell). For example, the base station 504 may determine to transmit the RRC reconfiguration message 520 to reconfigure the parameters of the BWP of the UE 502, transfer the UE 502 to another BWP, or reconfigure communications between the UE 502 and the cell. The LBT failure response cancel indicator 522 may indicate that the UE 502 cancels a recovery response or resets monitoring for a LBT failure based on a reconfigured BWP or a reconfigured cell. As shown at 530, the UE 502 may cancel a recovery response planned in response to determining a consistent LBT failure on a reconfigured BWP or cell as shown at 514, and / or may reset monitoring for a reconfigured BWP or cell as shown at 512.

[0069] In some aspects, the LBT failure response cancellation indicator 522 may indicate that the UE 502 cancels the recovery response and / or resets the monitoring of the consistent LBT failure that occurs for the specified type of transmission. The type of transmission may be a RACH, PUSCH, PUCCH, or a transmission using a certain LBT type (category 2, category 4). For example, the base station 504 may determine to transmit an RRC reconfiguration message 520 to reconfigure the parameters associated with the transmission type (e.g., channels, LBT parameters, etc. for the transmission type). The LBT failure response cancellation indicator 522 may indicate that the UE 502 cancels the recovery response or resets the monitoring of the LBT failure based on the transmission for the transmission type. As shown at 530, the UE 502 may cancel the recovery response planned in response to determining the consistent LBT failure for the transmission of the transmission type as shown at 514, and / or may reset the monitoring of the transmission of the transmission type as shown at 512. For example, the cancellation may occur at the MAC layer. A planned recovery response may include reporting the LBT failure in a MAC Control Element (CE), and a canceled recovery response may include not sending the MAC CE.

[0070] Figure 6 6 is a communication flow diagram 600 illustrating a recovery response cancellation based on RRC reconfiguration with synchronization. UE 602 may transmit uplink data 610 to base station 604 using an LBT procedure, and as shown at 612, UE 602 may monitor for consistent LBT failures (e.g., as described above with respect to FIG. 6 ) when transmitting uplink data 610 to base station 604. Figure 4 In some aspects, as shown at 614, UE 602 may determine that a consistent LBT failure has occurred (e.g., as described above with respect to Figure 4 described above).

[0071] The base station 604 may transmit an RRC reconfiguration message 620 to the UE 602, instructing the UE 602 to perform reconfiguration with synchronization. The RRC reconfiguration message 620 may be transmitted in response to a handover of the UE 602 or in response to changing a security key of the UE 602. The UE 602 may receive the RRC reconfiguration message 620, and may reset parameters and perform a RACH procedure 622 with the base station 604 in response to the RRC reconfiguration message 620.

[0072] Based on receiving the RRC reconfiguration message 620, the UE 602 may cancel a recovery response planned in response to determining a consistent LBT failure as shown at 614, and / or may reset monitoring as shown at 612. In some aspects, the UE 602 may cancel a recovery response or reset monitoring upon receiving the RRC reconfiguration message 620, as shown at 630. In some aspects, the UE 602 may cancel a recovery response or reset monitoring upon completion of the RACH procedure 622, as shown at 632.

[0073] The UE 602 may cancel the recovery response or reset monitoring of a subset of cells of the base station 604 in response to the RRC reconfiguration message 620, as shown at 630 and 632. In some aspects, the UE 602 may cancel the recovery response or reset monitoring of transmissions to the primary cell of the base station 604 without resetting monitoring of transmissions to the secondary cell(s) of the base station 604. In some aspects, the UE 602 may cancel the recovery response and reset monitoring of transmissions to the primary cell and all secondary cells of the base station 604. In some aspects, the UE 602 may cancel the recovery response and reset monitoring of transmissions to the primary cell of the base station 604 and to the secondary cells of the base station 604 as affected by the parameters configured based on the RRC reconfiguration message 620 with synchronization.

[0074] Figure 7 7 is a communication flow diagram 700 illustrating a recovery response cancellation based on reconfigured parameters. UE 702 may transmit uplink data 710 to base station 704 using an LBT procedure, and as shown at 712, UE 702 may monitor for consistent LBT failures (e.g., as described above with respect to FIG. 7 ) when transmitting uplink data 710 to base station 704. Figure 4 In some aspects, as shown at 714, UE 702 may determine that a consistent LBT failure has occurred (e.g., as described above with respect to Figure 4 described above).

[0075] The base station 704 may reconfigure the parameters of the UE 702. For example, the base station 704 may transmit an RRC reconfiguration message 720 to the UE 702, and the RRC reconfiguration message 720 may reconfigure the parameters of the UE 702. As shown at 722, the UE 702 may determine that the consistent LBT failure determined at 714 and / or the monitoring shown at 712 is associated with the parameters reconfigured by the RRC reconfiguration message 720.

[0076] In some aspects, the RRC reconfiguration message 720 may reconfigure a BWP for the UE 702 to transmit uplink data 710, or may reconfigure parameters of a BWP on which the UE 702 transmits uplink data 710. At 722, the UE 702 may determine that a consistent LBT failure on the BWP is associated with the reconfigured parameters, and may determine that monitoring for consistent LBT failures on the BWP is associated with the reconfigured parameters.

[0077] In some aspects, the RRC reconfiguration message 720 may reconfigure one or more LBT subbands for the UE 702. LBT subbands may also be referred to as RB sets. The one or more LBT subbands for the UE 702 may be one or more RB sets that contain active BWPs for the UE 702. The RRC reconfiguration message 720 may reconfigure the one or more LBT subbands for the UE 702 by configuring the BWP for the UE 702 to be in one or more different subbands. At 722, the UE 702 may determine that consistent LBT failures on the one or more subbands are associated with the reconfigured parameters, and may determine that monitoring for consistent LBT failures on the one or more subbands is associated with the reconfigured parameters.

[0078] In some aspects, the RRC reconfiguration message 720 may reconfigure the LBT detection / recovery process for the UE 702. For example, the RRC reconfiguration message 720 may change the value of a timer or counter used to determine whether a consistent LBT failure has occurred (e.g., as described above with respect to 414), or may disable LBT detection and recovery. At 722, the UE 702 may determine that a consistent LBT failure determined using a previous detection / recovery process is associated with the reconfigured parameters, and may determine that monitoring for consistent LBT failures using the previous detection / recovery process is associated with the reconfigured parameters.

[0079] In some aspects, the RRC reconfiguration message 720 may reconfigure LBT parameters (e.g., channel access priority level CAPC) for the UE 702. At 722, the UE 702 may determine that a consistent LBT failure determined using previous LBT parameters is associated with the reconfigured parameters, and may determine that monitoring for consistent LBT failures using previous LBT parameters is associated with the reconfigured parameters.

[0080] As shown at 730, the UE 702 may cancel a recovery response based on a consistent LBT failure determined at 722 to be associated with the reconfigured parameters, and / or may reset monitoring determined at 722 to be associated with the reconfigured parameters. The UE 702 may perform the canceling or resetting without being instructed to do so by the base station 704.

[0081] Figure 8 800 is a communication flow chart illustrating cancellation of a recovery response based on a radio link failure. UE 802 may utilize dual connectivity to transmit on multiple component carriers. For example, UE 802 may transmit uplink data 810 to a primary node 804 on a first carrier (e.g., 5G NR), and may transmit uplink data 811 to a secondary node 806 on a second carrier (e.g., LTE). UE 802 may use an LBT process to transmit both uplink data 810 and uplink data 811. As shown at 812, UE 802 may monitor for consistency in its transmission of uplink data 810 to primary node 804 and in its transmission of uplink data 811 to secondary node 806 LBT failures (e.g., as described above with respect to Figure 4 In some aspects, as shown at 814, UE 802 may determine that a consistent LBT failure has occurred for any transmission (e.g., as described above with respect to Figure 4 described above).

[0082] UE 802 may detect a radio link failure 820 of a link between UE 802 and primary node 804 or a link between UE 802 and secondary node 806. In response to detecting radio link failure 820, UE 802 may cancel a recovery response planned based on determining a consistent LBT failure and / or may reset monitoring for a consistent LBT failure, as shown at 830.

[0083] In some aspects, in the case where the radio link failure 820 is for a link between the UE 802 and the PSCell of the secondary node 806, the UE 802 may cancel a recovery response based on a consistent LBT failure of transmissions to the secondary cell of the secondary node 806, and / or may reset monitoring of a consistent LBT failure of transmissions to the secondary cell of the secondary node 806. In some aspects (e.g., aspects where primary cell group recovery is not enabled), in the case where the radio link failure 820 is for a link between the UE 802 and the primary cell of the primary node 804, the UE 802 may cancel a recovery response based on a consistent LBT failure of transmissions to the secondary cell of the primary node 804 and transmissions to the secondary cell of the secondary node 806.

[0084] In some aspects, the UE 802 may be configured to utilize a primary cell group recovery. In the event that the radio link failure 820 is for a link between the UE 802 and the primary cell of the primary node 804, the UE 802 may notify the secondary node 806 of the radio link failure 820 and the secondary node 806 may notify the primary node 804 of the radio link failure 820. The primary node 804 may send some instructions to the secondary node 806 to compensate for the link failure between the primary node 804 and the UE 802. The UE 802 may cancel a recovery response based on a consistent LBT failure of transmission to the secondary cell of the primary node 804, but may not cancel a recovery response based on a consistent LBT failure of transmission to the secondary cell of the secondary node 806.

[0085] Fig. 9 900 is a communication flow diagram illustrating recovery response cancellation in conditional handover. UE 902 may transmit uplink data 910 to source base station 906 using an LBT procedure, and as shown at 912, UE 902 may monitor for consistent LBT failures (e.g., as described above with respect to FIG. 1 ) when transmitting uplink data 910 to source base station 906. Figure 4 described above).

[0086] The source base station 906 may transmit a conditional handover grant 920 to the UE 902 indicating to the UE 902 that the UE 902 may perform a handover to another candidate base station without an explicit instruction to do so from the source base station 906. The conditional handover grant 920 may include conditions that should be met before the handover is performed, such as a channel measurement between the UE 902 and the source base station 906 being below a threshold level and / or a channel measurement between the UE 902 and a candidate base station being above a threshold level.

[0087] In some aspects, as shown at 914, the UE 902 can determine that a consistent LBT failure has occurred (e.g., as described above with respect to Figure 4 This determination may be made after receiving the conditional switching authorization 920, such as Fig. 9 As shown, or in some aspects may be made prior to receiving conditional switch grant 920.

[0088] As shown at 922, before performing a recovery response based on the determined consistent LBT failure, the UE 902 may initiate a handover process 922 with the target base station 904 based on the conditional handover authorization 920. For example, the UE 902 may perform channel measurements on a channel between the UE 902 and the target base station 904, determine that the measurements support a handover to the target base station 904, and determine that it is authorized to handover to the target base station 904 based on the conditional handover authorization 920.

[0089] Upon completion of the handover process 922 , the UE 902 may cancel a recovery response to a consistent LBT failure determined based on transmissions to the source base station 906 (eg, as determined as shown at 914 ).

[0090] In some aspects, if the UE 902 determines that the consistent LBT has failed but does not initiate a recovery response before initiating the handover 922, the UE 902 may suspend or defer the recovery response until the handover process is completed 922. If the handover process is successful, the UE 902 may cancel the recovery response, as shown at 930. If the handover process fails, the UE 902 may resume the recovery response.

[0091] Fig.10 1000 is a communication flow diagram illustrating recovery response cancellation in dual active protocol stack switching. UE 1002 may transmit uplink data 1010 to source base station 1006 using an LBT process, and as shown at 1012, UE 1002 may monitor for consistent LBT failures (e.g., as described above with respect to FIG. 1010 ) when transmitting uplink data 1010 to source base station 1006. Figure 4 described above).

[0092] In a dual active protocol stack system, the UE 1002 may be able to maintain its connection with the source base station 1006 during the handover until the target base station 1004 instructs it to release the connection, so as to reduce or eliminate the interruption in the uplink / downlink based on the handover. The UE 1002 may determine to handover to the target base station 1004 (e.g., the source base station 1006 may instruct the UE 1002 to handover to the target base station 1004). The UE 1002 may perform a RACH procedure 1022 with the target base station 1004. After the RACH procedure 1022 is completed, the UE may handover its uplink to the target base station 1004 and may transmit uplink data to the target base station 1004. Once the UE 1002 has handed over its uplink to the target base station 1004, the target base station 1004 may transmit a release command 1026 to the UE 1002. Upon receiving the release command 1026, the UE 1002 may release the connection with the source base station 1006.

[0093] In some aspects, as shown at 1014, UE 1002 may determine that a consistent LBT failure has occurred for transmissions to source base station 1006 before UE 1002 releases the connection with source base station 1006 (e.g., as described above with respect to Figure 4 For example, UE 1002 may determine that a consistent LBT failure has occurred before UE 1002 determines to switch to target base station 1004 or before UE 1002 transfers its uplink to target base station 1004.

[0094] Based on the handover to the target base station 1004, the UE 1002 may cancel the recovery response planned in response to the determination of a consistent LBT failure shown at 1014. In some aspects, the UE 1002 may cancel the recovery response upon completing the RACH procedure 1022, as shown at 1030. In some aspects, the UE 1002 may cancel the recovery response upon handing over the uplink to the target base station 1004, as shown at 1032. In some aspects, the UE 1002 may cancel the recovery response and release the connection with the source base station 1006 upon receiving the release command 1026, as shown at 1034. In some aspects, upon canceling the recovery response, the UE 1002 may transmit a report 1024 to the target base station 1004 indicating that a consistent LBT failure was determined for the source base station 1006 or indicating that the recovery response was canceled.

[0095] Fig.11 1 is a communication flow diagram 1100 illustrating recovery response cancellation in a failed dual active protocol stack switch. UE 1102 may initially connect with source base station 1106. UE 1102 may transmit uplink data 1124 to the source base station.

[0096] UE 1102 may determine to handover to target base station 1104 (e.g., source base station 1106 may instruct UE 1102 to handover to target base station 1104). UE 1102 may perform a RACH procedure 1122 with target base station 1104. After RACH procedure 1122 is completed, UE 1102 may handover its uplink to target base station 1104. UE 1102 may transmit uplink data 1110 to target base station 1104 using an LBT procedure, and as shown at 1112, UE 1102 may monitor for consistent LBT failures (e.g., as described above with respect to FIG. 1114 ) when it transmits uplink data 1110 to target base station 1104. Figure 4 described above).

[0097] As indicated at 1114, UE 1102 may determine that a consistent LBT failure has occurred when it transmits uplink data 1110 to target base station 1104 (e.g., as described above with respect to Figure 4 described above).

[0098] As shown at 1124, the handover of UE 1102 to target base station 1104 may fail. For example, RACH procedure 1122 may fail, or a radio link failure between UE 1102 and target base station 1104 may occur before the connection with source base station 1106 is released. Upon handover failure, as shown at 1130, UE 1102 may cancel a planned recovery response in response to determining that a consistent LBT in transmissions to target base station 1104 failed.

[0099] Since the target base station 1104 has not yet instructed the UE 1102 to release the connection with the source base station 1106, the UE 1102 remains connected to the source base station 1106. The UE 1102 may fall back to the source base station 1106, handover its uplink to the source base station 1106, and transmit uplink data 1126 to the source base station 1106. In some aspects, the UE 1102 may transmit a report 1128 to the source base station 1106 indicating that a consistent LBT failure was determined for the source base station 1106 or indicating that the recovery response was cancelled.

[0100] The above examples have been described with reference to a consistency LBT failure on an uplink transmission. However, in some aspects, the UE may perform the above examples based on a consistency failure on a downlink transmission. For example, the UE may monitor downlink communications received from a base station. The base station may attempt to transmit a reference signal at regular intervals and may utilize an LBT process to transmit the downlink transmission. While monitoring the downlink communications from the base station, the UE may determine that a reference signal is not received and may determine that the base station has experienced an LBT failure for the downlink transmission. The UE may monitor for a consistency LBT failure on the downlink transmission in the same manner as described above with respect to monitoring for a consistency LBT failure on the uplink transmission. Upon determining a consistency LBT failure for the downlink transmission, the UE may perform recovery operations. In some aspects, the UE may perform the above-described LBT failure on the downlink transmission. Figure 5 , 6 , 7, 8, 9, 10 and 11 examples to cancel the recovery operation, or reset the monitoring for consistent LBT failure on downlink transmission.

[0101] Fig.12 1200 is a flow chart of a wireless communication method. The method may be performed by a UE (eg, UE 350, 402, 502, 602, 702, 802, 902, 1002, 1102).

[0102] At 1202, the UE may monitor for consistent LBT failures of transmissions between the base station and the UE. Upon detecting a consistent LBT failure, an LBT recovery response may be initiated. For example, the UE may determine whether to perform an LBT recovery response based on the monitoring. The transmission may be an uplink transmission. The transmission may be a downlink transmission. The transmission may be to a primary cell of a base station. The transmission may be to a secondary cell of a base station.

[0103] At 1206, the UE may detect a trigger. In some aspects, the UE may receive an RRC reconfiguration message from a base station that may reconfigure parameters of the UE related to the transmission, and the trigger may be receiving the RRC reconfiguration message. The parameter may be associated with a bandwidth portion of the transmission. The parameter may be associated with an LBT subband for the transmission. The parameter may be associated with monitoring for consistent LBT failures. The parameter may be a parameter of an LBT procedure for the transmission. The trigger may be detecting a radio link failure. The trigger may be a conditional handover of the UE to a target base station.

[0104] In some aspects, the UE may receive an RRC reconfiguration message from the base station that reconfigures parameters of the UE related to the transmission, and the UE may receive an LBT failure response cancellation indicator corresponding to the RRC message from the base station. The trigger may be receiving the LBT failure response cancellation indicator. The LBT failure response cancellation indicator may identify a bandwidth portion of the transmission, a channel of the transmission with a consistent LBT failure, or an LBT type of the transmission.

[0105] In some aspects, the UE may receive an RRC reconfiguration message indicating a reconfiguration with synchronization, and the trigger may be based on the RRC reconfiguration message. The trigger may be receiving the RRC reconfiguration message. The trigger may be completion of a synchronization procedure initiated by the RRC reconfiguration message with synchronization.

[0106] In some aspects, the trigger may be based on a dual active protocol stack switch from the UE to the target base station. The trigger may be the completion of a random access channel procedure for the dual active protocol stack switch. The transmission may be an uplink transmission, and the trigger may be that the UE switches its uplink to the target base station. The trigger may be receiving a release command from the target base station instructing the UE to release a connection with the base station. The trigger may be a failure of the dual active protocol stack switch from the UE to the base station.

[0107] At 1208, the UE may cancel the LBT recovery response or reset monitoring based on the trigger. The transmission may be to a primary cell of the base station, and the LBT recovery response may change the transmission from the first bandwidth portion of the UE to the second bandwidth portion of the UE. The transmission may be to a secondary cell of the base station, and the recovery response may be reporting a consistent LBT failure to the base station and stopping the transmission.

[0108] In some aspects, the UE may receive an RRC reconfiguration message indicating a reconfiguration with synchronization, and the trigger may be based on the RRC reconfiguration message. The trigger may be receiving an RRC reconfiguration message. The trigger may be the completion of a synchronization process initiated by an RRC reconfiguration message with synchronization. In response to detecting the trigger, the UE may cancel all LBT recovery responses or reset all monitoring of consistent LBT failures for transmissions to the primary cell. The UE may cancel all LBT recovery responses or reset all monitoring of consistent LBT failures for transmissions to the primary cell in response to detecting the trigger, and may cancel all LBT recovery responses or reset all monitoring of consistent LBT failures for transmissions to the secondary cell in response to detecting the trigger. The UE may cancel all LBT recovery responses or reset all monitoring of consistent LBT failures for transmissions to the primary cell in response to detecting the trigger, and may determine whether to cancel all LBT recovery responses or reset all monitoring of consistent LBT failures for transmissions to the secondary cell in response to detecting the trigger based on whether the RRC reconfiguration message reconfigures parameters associated with the secondary cell.

[0109] In some aspects, the trigger may be detection of a radio link failure. The base station may be a secondary node, the radio link failure may be with a primary secondary cell of the base station, and the UE may cancel all LBT recovery responses or reset all monitoring of LBT failures for consistency of transmissions to the secondary cells of the base station in response to detecting the radio link failure. The base station may be a primary node, the radio link failure may be with a primary cell of the base station, primary cell group recovery may be enabled, and the UE may cancel all LBT recovery responses or reset all monitoring of LBT failures for consistency of transmissions to the secondary cells of the base station in response to detecting the radio link failure. The base station may be a primary node, the radio link failure may be with a primary cell of the base station, and the UE may cancel all LBT recovery responses or reset all monitoring of LBT failures for consistency of transmissions to the secondary cells of the base station and to the secondary cells of the secondary node in response to detecting the radio link failure.

[0110] Fig.13 1300 is a flow chart of a wireless communication method. The method may be performed by a base station or a node of a base station (eg, base stations 310, 404, 504, 604, 704, 804, 806, 904, 906, 1004, 1006, 1104, 1106).

[0111] At 1302, a base station may transmit an RRC reconfiguration message to a user equipment (UE) to reconfigure parameters of the UE. The parameters may be associated with a bandwidth portion of a transmission between the UE and the base station, a channel of a transmission, or an LBT type of a transmission. The transmission may be an uplink transmission.

[0112] At 1304, the base station may transmit an LBT failure response cancel indicator to the UE based on the parameter. The LBT failure response cancel indicator may identify a bandwidth portion of the transmission, a channel of the transmission, or an LBT type of the transmission.

[0113] Fig.14 1400 is a diagram illustrating an example of a hardware implementation of an apparatus 1402. The apparatus 1402 is a UE and includes a cellular baseband processor 1404 (also referred to as a modem) coupled to a cellular RF transceiver 1422 and one or more subscriber identity modules (SIM) cards 1420, an application processor 1406 coupled to a secure digital (SD) card 1408 and a screen 1410, a Bluetooth module 1412, a wireless local area network (WLAN) module 1414, a global positioning system (GPS) module 1416, and a power supply 1418. The cellular baseband processor 1404 communicates with the UE 104 and / or the BS 102 / 180 via the cellular RF transceiver 1422. The cellular baseband processor 1404 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 1404 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1404, causes the cellular baseband processor 1404 to perform the various functions described above. The computer-readable medium / memory may also be used to store data that the cellular baseband processor 1404 manipulates when executing the software. The cellular baseband processor 1404 also includes a receiving component 1430, a communication manager 1432, and a transmission component 1434. The communication manager 1432 includes one or more of the components shown. The components within the communication manager 1432 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1404. The cellular baseband processor 1404 may be a component of the UE 350 and may include a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1402 may be a modem chip and include only the baseband processor 1404, and in another configuration, the device 1402 may be the entire UE (e.g., see Figure 3 350) and includes the aforementioned additional modules of device 1402.

[0114] The communication manager 1432 includes a consistent LBT failure component 1440, which is configured to monitor consistent LBT failures of transmissions between the base station and the UE, for example, as described in conjunction with Fig.12 The communication manager 1432 also includes an LBT recovery response component 1442, which is configured to determine whether to perform an LBT recovery response based on the monitoring performed by the consistency LBT failure component 1440, for example, as combined with Fig.12The communication manager 1432 also includes a trigger detection component 1444, which is configured to detect a trigger, for example, as described in conjunction with Fig.12 1206. The communication manager 1432 also includes a recovery response cancellation component 1446. In some aspects, the recovery response cancellation component 1446 is configured to cancel the LBT recovery response (e.g., triggered by the LBT recovery response component 1442) based on the trigger detected by the trigger detection component 1444, for example, as combined Fig.12 In some aspects, the recovery response cancellation component 1446 is configured to reset the monitoring of the consistency LBT failure component 1440 for the consistency LBT failure based on the trigger detected by the trigger detection component 1444, for example, as combined with Fig.12 As described in 1208.

[0115] The device may include executing the aforementioned Fig.12 Each box in the flowchart has additional components. Therefore, Fig.12 Each block in the aforementioned flow chart of can be performed by a component, and the apparatus may include one or more of these components. The component may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0116] In one configuration, the device 1402, and in particular the cellular baseband processor 1404, includes a device for monitoring a consistent listen-before-talk (LBT) failure of transmissions between a base station and a UE, a device for determining whether to perform an LBT recovery response based on the monitoring, a device for detecting a trigger, and a device for canceling the LBT recovery response or resetting the monitoring based on the trigger. In some configurations, the device 1402, and in particular the cellular baseband processor 1404, includes a device for receiving an RRC reconfiguration message from a base station, the RRC reconfiguration message reconfiguring parameters of the UE related to the transmission, wherein the trigger is receiving the RRC reconfiguration message. The aforementioned means may be one or more of the aforementioned components of the device 1402, which are configured to perform the functions recited by the aforementioned means. As described above, the device 1402 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the aforementioned means may be a TX processor 368, an RX processor 356, and a controller / processor 359 configured to perform the functions recited by the aforementioned means.

[0117] Fig.151500 is a diagram illustrating an example of a hardware implementation of an apparatus 1502. Apparatus 1502 is a BS and includes a baseband unit 1504. Baseband unit 1504 may communicate with UE 104 via a cellular RF transceiver. Baseband unit 1504 may include a computer-readable medium / memory. Baseband unit 1504 is responsible for general processing, including executing software stored on a computer-readable medium / memory. When executed by baseband unit 1504, the software causes baseband unit 1504 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by baseband unit 1504 when executing the software. Baseband unit 1504 also includes a receiving component 1530, a communication manager 1532, and a transmission component 1534. Communication manager 1532 includes one or more of the components shown. Components within communication manager 1532 may be stored in a computer-readable medium / memory and / or configured as hardware within baseband unit 1504. The baseband unit 1504 may be a component of the BS 310 and may include a memory 376 and / or at least one of the TX processor 316 , the RX processor 370 , and the controller / processor 375 .

[0118] The communication manager 1532 includes an RRC reconfiguration message component 1540, which is configured to transmit an RRC reconfiguration message to the UE to reconfigure the parameters of the UE, for example, as combined with Fig.13 The communication manager 1532 also includes a cancellation index component 1542, which is configured to transmit an LBT failure response cancellation indicator to the UE based on the parameter, for example, as combined with Fig.13 As described in 1304.

[0119] The apparatus may include executing Fig.13 The additional components of each box of the algorithm in the preceding flowchart. Therefore, Fig.13 Each block in the aforementioned flow chart may be performed by a component and the apparatus may include one or more of these components. The component may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0120] In one configuration, the apparatus 1502, and in particular the baseband unit 1504, includes a device for transmitting an RRC reconfiguration message to the UE to reconfigure the parameters of the UE, and a device for transmitting an LBT failure response cancellation indicator to the UE based on the parameters. The aforementioned means may be one or more of the aforementioned components of the apparatus 1502 configured to perform the functions recorded by the aforementioned means. As described above, the apparatus 1502 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Therefore, in one configuration, the aforementioned means may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recorded by the aforementioned means.

[0121] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is an illustration of an example method. Based on design preferences, it is understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged. In addition, some blocks can be combined or omitted. The attached method claims present the elements of the various blocks in a sample order and are not meant to be limited to the specific order or hierarchy presented.

[0122] The foregoing description is provided so that any person skilled in the art can practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to conform to the full scope consistent with the language claims, wherein the reference to an element in the singular is not intended to represent "one and only one" (unless specifically stated), but "one or more". The term "exemplary" is used herein to represent "as an example, instance or illustration". Any aspect described as "exemplary" herein need not be interpreted as being preferred or superior to other aspects. Unless otherwise specifically stated, the term "some" refers to one or more. Combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C" and "A, B, C or any combination thereof" include any combination of A, B and / or C, and may include multiple A, multiple B or multiple C. In particular, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members or multiple members of A, B, or C. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or later become known to one of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly recited in the claims. Words such as "module," "mechanism," "element," "device," etc. may not be a substitute for the word "device." Therefore, any claim element shall not be interpreted as a device plus function unless the element is expressly recited using the phrase "device for..."

[0123] Implementation examples are described in the following numbered items. The following examples are merely illustrative and may be combined with other embodiments or aspects of the teachings described herein without limitation.

[0124] 1. A method for wireless communication at a user equipment (UE), comprising: monitoring a consistent listen-before-talk (LBT) failure of transmission between a base station and the UE; determining whether to perform an LBT recovery response based on the monitoring; detecting a trigger; and canceling the LBT recovery response or resetting the monitoring based on the trigger.

[0125] 2. The method of item 1, wherein the transmission is to a primary cell of a base station, and wherein the LBT recovery response is to change the transmission from a first bandwidth portion of the UE to a second bandwidth portion of the UE.

[0126] 3. The method of item 1, wherein the transmission is to a secondary cell of the base station, and the recovery response is to report a consistent LBT failure to the base station and stop the transmission.

[0127] 4. The method of any one of items 1-3 further includes receiving an RRC reconfiguration message from a base station, wherein the RRC reconfiguration message reconfigures parameters of the UE related to transmission, wherein the trigger is receiving the RRC reconfiguration message.

[0128] 5. The method of any one of items 1-4, wherein the parameter is associated with a bandwidth portion of the transmission.

[0129] 6. The method of any one of items 1-4, wherein the parameter is associated with the transmitted LBT subband.

[0130] 7. The method of any of items 1-4, wherein the parameter is associated with monitoring for consistent LBT failures.

[0131] 8. The method of any one of items 1-4, wherein the parameter is a parameter of the LBT process used for transmission.

[0132] 9. The method of any one of items 1-3 also includes: receiving an RRC reconfiguration message from a base station, which RRC reconfiguration message reconfigures parameters of the UE related to the transmission; and receiving an LBT failure response cancellation indicator corresponding to the RRC message from the base station, wherein the trigger is receiving the LBT failure response cancellation indicator.

[0133] 10. The method of any of items 1-3 and 9, wherein the LBT failure response cancel indicator identifies a bandwidth portion of a transmission, a channel of a transmission having a consistent LBT failure, or an LBT type of transmission.

[0134] 11. The method of item 1 further includes receiving an RRC reconfiguration message indicating a reconfiguration with synchronization, wherein the trigger is based on the RRC reconfiguration message.

[0135] 12. The method of any one of items 1 and 11, wherein the trigger is receiving an RRC reconfiguration message.

[0136] 13. The method of any one of items 1 and 11, wherein the trigger is completion of a synchronization process initiated by an RRC reconfiguration message with synchronization.

[0137] 14. The method of any one of items 1 and 11-13, wherein the UE cancels all LBT recovery responses or resets all monitoring of consistent LBT failures for transmissions to the primary cell in response to detecting a trigger.

[0138] 15. A method according to any one of items 1 and 11-13, wherein the UE responds to detection that triggers the cancellation of all LBT recovery responses or the reset of all monitoring of consistent LBT failures for transmissions to the primary cell, and responds to detection that triggers the cancellation of all LBT recovery responses or the reset of all monitoring of consistent LBT failures for transmissions to the secondary cell.

[0139] 16. A method according to any one of items 1 and 11-13, wherein the UE cancels all LBT recovery responses or resets all monitoring of consistent LBT failures for transmissions to the primary cell in response to detecting a trigger, and determines whether to cancel all LBT recovery responses or reset all monitoring of consistent LBT failures for transmissions to the secondary cell in response to detecting a trigger based on whether the RRC reconfiguration message reconfigures parameters associated with the secondary cell.

[0140] 17. The method of item 1, wherein the trigger is detection of a radio link failure.

[0141] 18. A method according to any one of items 1 and 17, wherein the base station is a secondary node, wherein the radio link failure is with a primary secondary cell of the base station, and wherein the UE cancels all LBT recovery responses or resets all monitoring of LBT failures for consistency of transmissions to the secondary cell of the base station in response to detecting the radio link failure.

[0142] 19. A method according to any one of items 1 and 17, wherein the base station is a primary node, wherein the radio link failure is with a primary cell of the base station, wherein primary cell group recovery is enabled, and wherein the UE cancels all LBT recovery responses or resets all monitoring of consistent LBT failures for transmissions to secondary cells of the base station in response to detecting the radio link failure.

[0143] 20. A method according to any one of items 1 and 17, wherein the base station is a primary node, wherein the radio link failure is with a primary cell of the base station, and wherein the UE cancels all LBT recovery responses or resets all monitoring of LBT failures for consistency of transmissions to secondary cells of the base station and to secondary cells of the secondary node in response to detecting the radio link failure.

[0144] 21. The method of item 1, wherein the trigger is a conditional handover of the UE to a target base station.

[0145] 22. The method of item 1, wherein the trigger is based on a dual-active protocol stack switch from the UE to the target base station.

[0146] 23. The method of any one of items 1 and 22, wherein the trigger is the completion of a random access channel procedure for dual active protocol stack switching.

[0147] 24. The method of any one of items 1 and 22, wherein the transmission is an uplink transmission, and wherein the trigger is the UE switching its uplink to the target base station.

[0148] 25. The method of any one of items 1 and 22, wherein the trigger is receiving a release command from the target base station, instructing the UE to release the connection with the base station.

[0149] 26. The method of item 1, wherein the trigger is a failure of a dual-active protocol stack handover from the UE to the base station.

[0150] 27. The method of any one of items 1-26, wherein the transmission is an uplink transmission.

[0151] 28. An apparatus for performing wireless communications at a user equipment (UE), comprising: a device for monitoring a consistent listen-before-talk (LBT) failure of transmission between a base station and the UE; a device for determining whether to perform an LBT recovery response based on the monitoring; a device for detecting a trigger; and a device for canceling the LBT recovery response or resetting the monitoring based on the trigger.

[0152] 29. An apparatus for performing wireless communications at a user equipment (UE), comprising: a memory; and at least one processor connected to the memory and configured to: monitor a consistent listen-before-talk (LBT) failure of transmission between a base station and the UE; determine whether to perform an LBT recovery response based on the monitoring; detect a trigger; and cancel the LBT recovery response or reset the monitoring based on the trigger.

[0153] 30. The apparatus of item 29, wherein the transmission is to a primary cell of a base station, and wherein the LBT recovery response is to change the transmission from a first bandwidth portion of the UE to a second bandwidth portion of the UE.

[0154] 31. The apparatus of item 29, wherein the transmission is to a secondary cell of a base station, and the recovery response is to report a consistent LBT failure to the base station and stop the transmission.

[0155] 32. An apparatus according to any one of items 29-31, wherein the processor is further configured to receive an RRC reconfiguration message from a base station, the RRC reconfiguration message reconfiguring parameters of the UE related to transmission, wherein the trigger is receiving the RRC reconfiguration message.

[0156] 33. An apparatus as claimed in any one of items 29 to 32, wherein the parameter is associated with a bandwidth portion of the transmission.

[0157] 34. An apparatus as claimed in any one of items 29 to 32, wherein the parameter is associated with a transmitted LBT subband.

[0158] 35. The apparatus of any of items 29-32, wherein the parameter is associated with monitoring for consistent LBT failures.

[0159] 36. An apparatus as in any one of items 29-32, wherein the parameter is a parameter of an LBT process for transmission.

[0160] 37. An apparatus of any one of items 29-31, wherein the processor is further configured to: receive an RRC reconfiguration message from a base station, the RRC reconfiguration message reconfiguring parameters of the UE related to transmission; and receive an LBT failure response cancellation indicator corresponding to the RRC message from the base station, wherein the trigger is receiving the LBT failure response cancellation indicator.

[0161] 38. The apparatus of any of items 29-31 and 37, wherein the LBT failure response cancel indicator identifies a bandwidth portion of a transmission, a channel of a transmission having a consistent LBT failure, or an LBT type of transmission.

[0162] 39. The apparatus of item 29, wherein the processor is further configured to receive an RRC reconfiguration message indicating a reconfiguration with synchronization, wherein the trigger is based on the RRC reconfiguration message.

[0163] 40. The apparatus of any one of items 29 and 39, wherein the trigger is reception of an RRC reconfiguration message.

[0164] 41. An apparatus as in any one of items 29 and 39, wherein the trigger is completion of a synchronization process initiated by an RRC reconfiguration message with synchronization.

[0165] 42. An apparatus as in any one of items 29 and 39-41, wherein the UE cancels all LBT recovery responses or resets all monitoring of consistent LBT failures for transmissions to the primary cell in response to detecting a trigger.

[0166] 43. An apparatus of any one of items 29 and 39-41, wherein the UE responds to detecting a trigger to cancel all LBT recovery responses or reset all monitoring of consistent LBT failures for transmissions to a primary cell, and responds to detecting a trigger to cancel all LBT recovery responses or reset all monitoring of consistent LBT failures for transmissions to a secondary cell.

[0167] 44. An apparatus of any one of items 29 and 39-41, wherein the UE cancels all LBT recovery responses or resets all monitoring of consistent LBT failures for transmissions to the primary cell in response to detecting a trigger, and determines whether to cancel all LBT recovery responses or reset all monitoring of consistent LBT failures for transmissions to the secondary cell in response to detecting a trigger based on whether the RRC reconfiguration message reconfigures parameters associated with the secondary cell.

[0168] 45. The apparatus of claim 29, wherein the trigger is detection of a radio link failure.

[0169] 46. ​​An apparatus of any one of items 29 and 45, wherein the base station is a secondary node, wherein the radio link failure is with a primary secondary cell of the base station, and wherein the UE cancels all LBT recovery responses or resets all monitoring of consistent LBT failures for transmissions to the secondary cell of the base station in response to detecting the radio link failure.

[0170] 47. An apparatus of any one of items 29 and 45, wherein the base station is a primary node, wherein the radio link failure is with a primary cell of the base station, wherein primary cell group recovery is enabled, and wherein the UE cancels all LBT recovery responses or resets all monitoring of consistent LBT failures for transmissions to secondary cells of the base station in response to detecting the radio link failure.

[0171] 48. An apparatus of any one of items 29 and 45, wherein the base station is a primary node, wherein the radio link failure is with a primary cell of the base station, and wherein the UE cancels all LBT recovery responses or resets all monitoring of LBT failures for consistency of transmissions to secondary cells of the base station and to secondary cells of the secondary node in response to detecting the radio link failure.

[0172] 49. The device of item 29, wherein the trigger is a conditional handover of the UE to a target base station.

[0173] 50. The apparatus of item 29, wherein the trigger is based on a dual-active protocol stack switch from the UE to the target base station.

[0174] 51. The apparatus of any one of items 29 and 50, wherein the trigger is the completion of a random access channel procedure for dual active protocol stack switching.

[0175] 52. An apparatus as in any one of items 29 and 50, wherein the transmission is an uplink transmission, and wherein the trigger is the UE switching its uplink to the target base station.

[0176] 53. The apparatus of any one of items 29 and 50, wherein the trigger is receiving a release command from the target base station instructing the UE to release the connection with the base station.

[0177] 54. The apparatus of item 29, wherein the trigger is a failure of a dual-active protocol stack handover from the UE to the base station.

[0178] 55. An apparatus as in any one of items 29-54, wherein the transmission is an uplink transmission.

[0179] 56. A non-transitory computer-readable medium storing computer-executable code for wireless communication at a user device, wherein the code, when executed by a processor, causes the processor to perform the method of any one of items 1-27.

[0180] 57. A method for wireless communication at a base station, comprising: transmitting an RRC reconfiguration message to a user equipment (UE) to reconfigure parameters of the UE; and transmitting a listen before talk (LBT) failure response cancellation indicator to the UE based on the parameters.

[0181] 58. The method of item 57, wherein the parameter is associated with a bandwidth portion of the transmission between the UE and the base station, a channel of the transmission between the UE and the base station, or an LBT type of the transmission between the UE and the base station, and wherein the LBT failure response cancellation indicator identifies the bandwidth portion of the transmission, the channel of the transmission, or the LBT type of the transmission.

[0182] 59. The method of any one of items 57-58, wherein the transmission between the UE and the base station is an uplink transmission.

[0183] 60. An apparatus for performing wireless communications at a base station, comprising: a device for transmitting an RRC reconfiguration message for reconfiguring parameters of a user equipment (UE) to the UE; and a device for transmitting a listen-before-talk (LBT) failure response cancellation indicator to the UE based on the parameters.

[0184] 61. An apparatus for performing wireless communications in a base station, comprising: a memory; and at least one processor connected to the memory and configured to: transmit an RRC reconfiguration message to a user equipment (UE) for reconfiguring parameters of the UE; and transmit a listen-before-talk (LBT) failure response cancellation indicator to the UE based on the parameters.

[0185] 62. The apparatus of item 61, wherein the parameter is associated with a bandwidth portion of a transmission between the UE and the base station, a channel of a transmission between the UE and the base station, or an LBT type of a transmission between the UE and the base station, and wherein the LBT failure response cancellation indicator identifies the bandwidth portion of the transmission, the channel of the transmission, or the LBT type of the transmission.

[0186] 63. An apparatus according to any one of items 61-62, wherein the transmission between the UE and the base station is an uplink transmission.

[0187] 64. A non-transitory computer-readable medium storing computer-executable code for wireless communication at a user device, wherein the code, when executed by a processor, causes the processor to perform the method of any of items 57-59.

[0188] 65. An apparatus for performing wireless communications at a user equipment (UE), comprising: a device for monitoring a consistent listen-before-talk (LBT) failure of transmission between a base station and the UE, wherein an LBT recovery response is initiated when a consistent LBT failure is detected; a device for detecting a trigger; and a device for canceling the LBT recovery response or resetting the monitoring based on the trigger.

[0189] 66. The apparatus of item 65 further comprises a device for receiving an RRC reconfiguration message from a base station, wherein the RRC reconfiguration message reconfigures parameters of the UE related to transmission, wherein the trigger is receiving the RRC reconfiguration message.

[0190] 67. The apparatus of claim 65, wherein the trigger is detection of a radio link failure.

[0191] 68. A non-transitory computer-readable medium storing computer-executable code for wireless communication at a user equipment (UE), which code, when executed by a processor, causes the processor to: monitor for consistent listen-before-talk (LBT) failures of transmissions between a base station and the UE, wherein an LBT recovery response is initiated when a consistent LBT failure is detected; detect a trigger; and cancel the LBT recovery response or reset the monitoring based on the trigger.

[0192] 69. The non-transitory computer-readable medium of item 68, wherein the code, when executed by a processor, further causes the processor to receive an RRC reconfiguration message from a base station, the RRC reconfiguration message reconfiguring parameters of the UE related to transmission, wherein the trigger is receiving the RRC reconfiguration message.

[0193] 70. The non-transitory computer-readable medium of item 68, wherein the trigger is detection of a radio link failure.

Claims

1. A method for wireless communication at a user equipment (UE), include: monitoring a consistent listen-before-talk (LBT) failure of transmissions between a base station and the UE, wherein an LBT recovery response is initiated when a consistent LBT failure is detected; Detection triggers; and canceling the LBT recovery response or resetting the monitoring based on the trigger, The method also includes receiving an RRC reconfiguration message from the base station, and based on receiving the RRC reconfiguration message, canceling the LBT recovery response and / or resetting the monitoring, wherein the RRC reconfiguration message reconfigures parameters of the UE related to the transmission, wherein the parameters are associated with a bandwidth portion of the transmission, an LBT subband of the transmission, or monitoring of the consistent LBT failure.

2. The method according to claim 1, in, The transmission is to a primary cell of the base station, and wherein the LBT recovery response is to change the transmission from a first bandwidth portion of the UE to a second bandwidth portion of the UE.

3. The method according to claim 1, in, The transmission is to a secondary cell of the base station, and the recovery response is to report the consistent LBT failure to the base station and stop the transmission.

4. The method according to claim 1, in, The trigger is receiving the RRC reconfiguration message.

5. The method according to claim 4, in, The parameters are parameters of the LBT process used for the transmission.

6. The method according to claim 1, further comprising: include: An LBT failure response cancellation indicator corresponding to the RRC message is received from the base station, wherein the trigger is receiving the LBT failure response cancellation indicator.

7. The method according to claim 1, in, The trigger is detection of a radio link failure.

8. The method according to claim 7, in, The base station is a secondary node, wherein the radio link failure is with a primary and secondary cell of the base station, and wherein the UE cancels all LBT recovery responses or resets all monitoring of consistent LBT failures for transmissions to the secondary cell of the base station in response to detecting the radio link failure.

9. The method according to claim 7, in, The base station is a primary node, wherein the radio link failure is with a primary cell of the base station, wherein primary cell group recovery is enabled, and wherein the UE cancels all LBT recovery responses or resets all monitoring of consistent LBT failures for transmissions to secondary cells of the base station in response to detecting the radio link failure.

10. The method according to claim 7, in, The base station is a primary node, wherein the radio link failure is with a primary cell of the base station, and wherein the UE cancels all LBT recovery responses or resets all monitoring of consistent LBT failures for transmissions to a secondary cell of the base station and to a secondary cell of a secondary node in response to detecting the radio link failure.

11. The method according to claim 1, in, The triggering is based on a dual active protocol stack switching from the UE to a target base station.

12. An apparatus for wireless communication at a user equipment (UE), include: Memory; as well as at least one processor coupled to the memory and configured to: monitoring a consistent listen-before-talk (LBT) failure of transmissions between a base station and the UE, wherein an LBT recovery response is initiated when a consistent LBT failure is detected; Detection triggers; and canceling the LBT recovery response or resetting the monitoring based on the trigger, The processor is also configured to receive an RRC reconfiguration message from the base station, and based on receiving the RRC reconfiguration message, cancel the LBT recovery response and / or reset the monitoring, wherein the RRC reconfiguration message reconfigures parameters of the UE related to the transmission, wherein the parameters are associated with a bandwidth portion of the transmission, an LBT subband of the transmission, or monitoring of the consistent LBT failure.

13. The device according to claim 12, in, The transmission is to a primary cell of the base station, and wherein the LBT recovery response is to change the transmission from a first bandwidth portion of the UE to a second bandwidth portion of the UE.

14. The device according to claim 12, in, The transmission is to a secondary cell of the base station, and the recovery response is to report the consistent LBT failure to the base station and stop transmission.

15. The device according to claim 12, in, The trigger is receiving the RRC reconfiguration message.

16. The device according to claim 15, in, The parameters are parameters of the LBT process used for the transmission.

17. The device according to claim 12, in, The processor is further configured to: An LBT failure response cancellation indicator corresponding to the RRC message is received from the base station, wherein the trigger is receiving the LBT failure response cancellation indicator.

18. The device according to claim 12, in, The trigger is detection of a radio link failure.

19. The device according to claim 18, in, The base station is a secondary node, wherein the radio link failure is with a primary and secondary cell of the base station, and wherein the UE cancels all LBT recovery responses or resets all monitoring of consistent LBT failures for transmissions to the secondary cell of the base station in response to detecting the radio link failure.

20. The device according to claim 18, in, The base station is a primary node, wherein the radio link failure is with a primary cell of the base station, wherein primary cell group recovery is enabled, and wherein the UE cancels all LBT recovery responses or resets all monitoring of consistent LBT failures for transmissions to secondary cells of the base station in response to detecting the radio link failure.

21. The device according to claim 18, in, The base station is a primary node, wherein the radio link failure is with a primary cell of the base station, and wherein the UE cancels all LBT recovery responses or resets all monitoring of consistent LBT failures for transmissions to a secondary cell of the base station and to a secondary cell of a secondary node in response to detecting the radio link failure.

22. The device according to claim 12, in, The triggering is based on a dual active protocol stack switching from the UE to a target base station.

23. An apparatus for wireless communication at a user equipment (UE), include: means for monitoring a consistent listen-before-talk (LBT) failure of transmissions between a base station and the UE, wherein an LBT recovery response is initiated upon detection of a consistent LBT failure; a device for detecting a trigger; and means for cancelling said LBT recovery response or resetting said monitoring based on said trigger, The apparatus also includes a device for receiving an RRC reconfiguration message from the base station, canceling the LBT recovery response and / or resetting the monitoring based on receiving the RRC reconfiguration message, wherein the RRC reconfiguration message reconfigures parameters of the UE related to the transmission, wherein the parameters are associated with a bandwidth portion of the transmission, an LBT subband of the transmission, or monitoring of the consistent LBT failure.

24. The device according to claim 23, in, The trigger is receiving the RRC reconfiguration message.

25. The device according to claim 23, in, The trigger is detection of a radio link failure.

26. A non-transitory computer readable medium storing computer executable code for wireless communication at a user equipment (UE), the code, when executed by a processor, causing the processor to: monitoring a consistent listen-before-talk (LBT) failure of transmissions between a base station and the UE, in, Initiate LBT recovery response when consistent LBT failure is detected; Detection trigger; as well as canceling the LBT recovery response or resetting the monitoring based on the trigger, The code, when executed by the processor, also causes the processor to receive an RRC reconfiguration message from the base station, and based on receiving the RRC reconfiguration message, cancel the LBT recovery response and / or reset the monitoring, wherein the RRC reconfiguration message reconfigures parameters of the UE related to the transmission, wherein the parameters are associated with a bandwidth portion of the transmission, an LBT subband of the transmission, or monitoring of the consistent LBT failure.

27. The non-transitory computer readable medium of claim 26, in, The trigger is receiving the RRC reconfiguration message.

28. The non-transitory computer readable medium of claim 26, in, The trigger is detection of a radio link failure.

29. A computer program product comprising computer instructions which, when executed by one or more processors of a user equipment (UE), cause the one or more processors to perform the method according to any one of claims 1-11.

Images