LBT procedure for a set of panels and / or beams

Abstract

Apparatuses, methods, and systems are disclosed for handling LBT failures for a set of panels / beams. An apparatus (600) includes a transceiver (625) including a plurality of UE panels associated with one or more beams. The apparatus (600) includes a processor (605) that performs (805) LBT procedures for a configured set of UE Tx panels corresponding to an uplink transmission. The processor (605) declares (810) an LBT failure for the uplink transmission in response to determining that the LBT procedures for all of the UE Tx panels in the configured set have failed, and increments (815) an LBT failure counter in response to the LBT failure for the uplink transmission.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 970,594, filed February 5, 2020, entitled “Handling Consistent LBT Failure for Spatial LBT”, by Joachim Loehr, Alexander Golitschek Edler von Elbwart, Ankit Bhamri, Ali Ali, Karthikeyan Ganesan, and Prateek Basu Mallick, which is incorporated herein by reference. Technical Field

[0003] The topics disclosed in this article generally relate to wireless communications, and more specifically to the handling of consistent Listen-After-Speak (“LBT”) failures in spatial multiplexing communications. Background Technology

[0004] The following abbreviations are defined herein, and at least some of them are mentioned in the following description: 3rd Generation Partnership Project (“3GPP”), 5th Generation (“5G”), 5G Access Network (“5G-AN”), 5G Core Network (“5GC” or “5C-CN”), 5G System (“5GS”), Affirmative Acknowledgment (“ACK”), Application Function (“AF”), Access and Mobility Management Function (“AMF”), Application Programming Interface (“API”), Access Layer (“AS”), Autonomous Uplink (“AUL”), Authentication Server Function (“AUSF”), Base Station (“BS”), Bandwidth (“BW”), Bandwidth Component (“BWP”), Clear Channel Assessment (“CCA”), Code Division Multiple Access (“CDMA”), Control Element (“CE”), Configured Licensing (“CG”, Semi-Persistent Licensing of Radio Resources), Core Network (“CN”), Channel Occupancy (“CO”), Channel Occupancy Time (“COT”), Configured Scheduling Radio Network Temporary Identifier (“CS-RNTI”), Channel State Information (“CSI”), CSI Reference Signal (“CSI-RS”), CSI-RS Resource Index (“CRI”), Contention Window Size (“CWS”), Downlink Control Information (“DCI”), Downlink (“DL”), Data Radio Bearer (“DRB”), Discontinuous Transmission (“DTX”), Enhanced Clear Channel Assessment (“eCCA”), Evolved Node B (“eNB”), Evolved Packet Core Network (“EPC”), Evolved Packet System (“EPS”), 5G / NR Node B (“gNB”), General Packet Radio Service (“GPRS”), Global System for Mobile Communications (“GSM”, i.e., 2G digital cellular network), Hybrid Automatic Repeat Request (“HARQ”), Home Subscriber Server (“HSS”), Identifier (“ID”), Internet Protocol (“IP”), Layer 1 (“L1”, also known as the Physical Layer), Layer 1 Identifier (“L1”) Layer 2 (“L2”, also known as the link layer), Layer 2 identifier (“L2 ID”), Layer 3 (“L3”, also known as the network layer), Listen-After-Speak (“LBT”), Long Term Evolution (“LTE”), Media Access Control (“MAC”), Media Access Control Element (“MAC CE”), Primary Cell Group (“MSG”), Mobility Management Entity (“MME”), Negative Acknowledgment (“NACK”) or (“NAK”), Non-Access Stratum (“NAS”), Network Exposure Function (“NEF”), Network Function (“NF”, e.g., network entities performing well-defined functions such as AMF, SMF, PCF, UDM, etc.), New Radio (“NR”), NR in Unlicensed Spectrum (“NR-U”), Network Slice Selection Auxiliary Information (“NSSAI”, e.g.,This includes vector values ​​of one or more S-NSSAI values, primary cell (“PCell”), policy control function (“PCF”), physical downlink control channel (“PDCCH”), physical downlink shared channel (“PDSCH”), packet data unit (“PDU”), physical layer (“PHY”), public land mobile network (“PLMN”), physical random access channel (“PRACH”), primary and secondary cell (“PSCell”, i.e., the SpCell of the SCG), physical uplink control channel (“PUCCH”), physical uplink shared channel (“PUSCH”), quality of service (“QoS”), quasi-co-location (“QCL”), random access procedure (“RACH”), radio access network (“RAN”), radio access technology (“RAT”), radio link failure (“RLF”), radio network temporary identifier (“RNTI”), radio resource control (“RRC”), and reference signal (“RS”, e.g., CSI). RS, Receive (“RX”), Secondary Cell (“SCell”), Secondary Cell Group (“SCG”), Shared Channel (“SCH”), Spatial Division Multiplexing (“SDM”), Signal-to-Interference-plus-Noise Ratio (“SINR”), Session Management Function (“SMF”), Single Network Slice Selection Auxiliary Information (“S-NSSAI”), Specific Cell (“SpCell”, e.g., referring to the PCell of the MCG or the PSCell of the SCG), SRS Resource Indicator (“SRI”), Sounding Reference Signal (“SRS”), Synchronization Signal (“SS”), Synchronization Signal / Physical Broadcast Channel (“SS / PBCH”), Synchronization Signal Block (“SSB”), SS / PB CH Block Resource Index (“SSBRI”), Transport Block (“TB”), Transport Configuration Indicator (“TCI”), Time Division Multiplexing (“TDM”), Transmit (“Tx”), Uplink Control Information (“UCI”), Unified Data Management (“UDM”), Unified Data Repository (“UDR”), User Entity / Equipment (Mobile Terminal) (“UE”, e.g., including Mobile Equipment “ME”, Subscriber Identity and / or Identification Module “SIM”), Uplink (“UL”), Uplink Shared Channel (“UL-SCH”), Universal Mobile Telecommunications System (“UMTS”), User Plane Function (“UPF”), and Global Interoperability Microwave Access (“WiMAX”). As used herein, “HARQ-ACK” can collectively represent a positive response (“ACK”), a negative response (“NACK”), and a discontinuous transmission (“DTX”). ACK means that the TB was received correctly, while NACK (or NAK) means that the TB was received incorrectly, and DTX means that the TB was not detected.

[0005] In some wireless communication systems, services are supplemented by operations on unlicensed spectrum. However, operations on unlicensed spectrum require clear channel assessment (“CCA”) prior to transmission, involving, for example, a listen-before-speak (“LBT”) process.

[0006] In NR-U, channel access relies on the LBT process in both the downlink and uplink. The gNB and / or UE must first sense the channel to identify any communication that is not in progress before any transmission. However, in NR-U version 16, beamforming for LBT is not considered, and only omnidirectional LBT is assumed. Summary of the Invention

[0007] A process for handling LBT failures in an assembly of panels / beams is disclosed. This process can be implemented by an apparatus, system, method, or computer program product.

[0008] One method for a UE includes performing an LBT procedure for a set of configurations corresponding to uplink transmissions of Tx beams. The method includes declaring an uplink transmission LBT failure in response to determining that an LBT procedure for all Tx beams in the set of configurations has failed. The method also includes incrementing an LBT failure counter in response to an uplink transmission LBT failure. Attached Figure Description

[0009] A more specific description of the embodiments briefly described above will be presented with reference to the specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only a few embodiments and should therefore not be considered as limiting the scope; the embodiments will be described and explained with additional specificity and detail using the drawings, in which:

[0010] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system for handling LBT failures in a panel / beam aggregation process;

[0011] Figure 2 This is a block diagram illustrating one embodiment of the NR protocol stack;

[0012] Figure 3 This is a diagram illustrating an embodiment of a failure in the LBT (Local Level By Transmission) processing space;

[0013] Figure 4 This is a diagram illustrating one embodiment of a radio frame used to perform LBT;

[0014] Figure 5 This is a diagram illustrating one embodiment of an indication of channel occupancy time sharing;

[0015] Figure 6This is a diagram illustrating one embodiment of a user equipment apparatus that can be used to process LBT failures in response to panel / beam aggregation;

[0016] Figure 7 This is a diagram illustrating one embodiment of a network device apparatus that can be used to process LBT failures in a panel / beamset aggregation process; and

[0017] Figure 8 This is a flowchart illustrating one embodiment of a method for handling LBT failures in a panel / beam array. Detailed Implementation

[0018] As those skilled in the art will understand, aspects of the embodiments can be embodied as systems, apparatus, methods, or program products. Therefore, embodiments can take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects.

[0019] For example, the disclosed embodiments can be implemented as hardware circuitry, including custom-designed very large-scale integration (“VLSI”) circuitry or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments can also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code, which may, for example, be organized as objects, processes, or functions.

[0020] Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transferable. The storage device may not embody signals. In one embodiment, the storage device uses only signals for accessing the code.

[0021] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof.

[0022] More specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable compact disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium capable of containing or storing a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0023] The code used to perform the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer can be connected to the user's computer via any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or it can be connected to an external computer (e.g., via the Internet provided by an Internet service provider).

[0024] Furthermore, the features, structures, or characteristics described in the embodiments can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of these specific details or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the embodiments.

[0025] Throughout this specification, references to "an embodiment," "embodiment," or similar language mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Therefore, unless expressly stated otherwise, the phrases "in an embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily, refer to the same embodiment, but rather mean "one or more, but not all, embodiments." Unless expressly stated otherwise, the terms "comprising," "including," "having," and variations thereof mean "including, but not limited to,". Unless expressly stated otherwise, the list of enumerated items does not imply that any or all items are mutually exclusive. Unless expressly stated otherwise, the terms "an," "a," and "the" also mean "one or more".

[0026] As used herein, a list containing the conjunction “and / or” includes any single item in the list or a combination of items in the list. For example, a list of A, B, and / or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term “one or more of” includes any single item in the list or a combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term “one of” includes one and only one of any single item in the list. For example, “one of A, B, and C” includes only A, only B, or only C and excludes combinations of A, B, and C. As used herein, “selected from the group consisting of A, B, and C” includes one and only one of A, B, or C and excludes combinations of A, B, and C. As used in this article, “selecting members of a group consisting of A, B, and C and their combinations” includes only A, only B, only C, combinations of A and B, combinations of B and C, combinations of A and C, or combinations of A, B, and C.

[0027] Aspects of the embodiments are described below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that individual blocks in the schematic flowcharts and / or schematic block diagrams, as well as combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that instructions executable by the processor of the computer or other programmable data processing apparatus create means for implementing the functions / actions specified in the flowcharts and / or block diagrams.

[0028] The code can also be stored in a storage device that can instruct a computer, other programmable data processing device or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of art including instructions that implement the functions / actions specified in the flowchart and / or block diagram.

[0029] The code may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device, thereby producing a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the functions / actions specified in the flowchart and / or block diagram.

[0030] The flowcharts and / or block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the flowcharts and / or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing a specified logical function.

[0031] It should also be noted that in some alternative implementations, the functions marked in the boxes may not appear in the order shown in the diagram. For example, two boxes shown consecutively may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order, depending on the functions involved. Other steps and methods that are equivalent in function, logic, or effect to one or more boxes or portions thereof shown in the diagram can be conceived.

[0032] While various arrow and line types may be used in flowcharts and / or block diagrams, they are not intended to limit the scope of the corresponding embodiments. In practice, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For example, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of a depicted embodiment. It will also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs the specified function or action.

[0033] The description of the elements in each figure can be referenced to the elements in the preceding figures. In all figures, the same reference numerals refer to the same elements, including alternative embodiments of the same elements.

[0034] This disclosure typically describes systems, methods, and apparatus for handling spatial LBT failures. A UE's MAC layer entity relies on receiving notification of a UL LBT failure from the physical layer to detect a consistent UL LBT failure. After declaring a consistent LBT failure on the PCell or PSCell for the active UL BWP, the UE can switch to another UL BWP and initiate a RACH procedure (e.g., assuming the UE is configured with another UL BWP having configured RACH resources).

[0035] In some embodiments, if a consistent UL LBT failure is detected on the PCell and UL LBT failures are detected on "N" possible BWPs, the UE performs RLF recovery. When a consistent uplink LBT failure is detected on the PSCell, the UE notifies the MN via the SCG failure information procedure after a consistent UL LBT failure has been detected on "N" BWPs. Here, "N" represents the number of configured BWPs with configured PRACH resources. If N is greater than one, this depends on the UE implementation of which BWP the UE selects.

[0036] When a consistent uplink LBT failure is detected on the SCell, a new MAC CE is used to report this failure to the node to which the SCell belongs. Whether the MAC CE can be used to report failed FFS on the PCell is also considered. In the case of a consistent LBT failure, the UE can be allowed to autonomously switch the UL BWP. In NR-U version 16, beamforming is not considered for LBT and only omnidirectional LBT is assumed.

[0037] The NR-U LBT process for channel access can be summarized as follows: 1) Both gNB-initiated COTs and UE-initiated COTs use Category 4 LBT, where the start of a new transmission burst always performs LBT with exponential backoff. This is except when the duration of the DRS must be at most one ms and is not multiplexed with a unicast PDSCH; 2) UL transmissions within a gNB-initiated COT or subsequent DL transmissions within a UE-initiated or gNB-initiated COT can be transmitted immediately without sensing only if the gap with the end of the previous transmission does not exceed 16 μs. Otherwise, Category 2 LBT must be used and the gap cannot exceed 25 μs.

[0038] In various embodiments, the UE may include multiple antenna panels. Identifiers (IDs) that can be used to indicate panel-specific UL transmissions are supported. The possibility of reusing / modifying version 15 specification support or introducing new IDs may be considered when defining IDs. In some embodiments, the UE is not required to explicitly expose its UL antenna panel implementation. In other embodiments, UE capability signaling may be used for panel-specific UL transmissions.

[0039] The panel identifier (panel ID) used to indicate a panel-specific UL transmission may include one of the following: 1) an SRS resource set ID, where the FFS is further associated with other RSs (if needed); 2) an ID directly associated with a reference RS resource and / or resource set; 3) an ID that can be assigned to a target RS resource or resource set; and 4) an ID additionally configured in the spatial relationship information. The panel ID (without excluding the reuse of existing IDs) can be used for panel-selection-based transmissions of PUSCH, PUCCH, and SRS across multiple active panels.

[0040] In some embodiments, multiple panels are implemented on the UE, and only one panel can be activated at a time according to a predetermined panel switching / activation delay. In some embodiments, multiple panels are implemented on the UE, and multiple panels can be activated at once, and one or more panels can be used for transmission. In some embodiments, multiple panels are implemented on the UE, and multiple panels can be activated at once, but only one panel can be used for transmission. Note that this does not require the UE to always activate multiple panels simultaneously. Also note that the UE can control panel activation / deactivation.

[0041] In other embodiments, a new panel ID can be used, which can be implicitly / explicitly applied to transmissions for a target RS resource or resource set, for a PUCCH resource, or for an SRS resource. In such embodiments, the new panel ID is used implicitly (e.g., via DL beam reporting enhancement) or explicitly to perform panel-specific signaling. If explicitly signaled, the ID can be configured in the target RS / channel or reference RS (e.g., in the DL RS resource configuration or in spatial relation information).

[0042] Regarding beam management, in some embodiments, the UE will report CRI / SSBRI, where CRI / SSBRI refers to the preferred spatial relation RS for UL transmission. In some embodiments, the SRI field in the DCI can be used to indicate multiple SRS resources and the UE's autonomous selection of one SRS resource from multiple SRS resources for PUSCH beam determination. In other embodiments, beam-specific PHR reporting is used to transparently determine the beam-specific MPE impact, i.e., by the difference between Pcmax (i.e., the configured maximum UE output power, the value of which is calculated based on P-MPR) and the required transmission power. Note that, according to Section 6.2.1 of the current 3GPP TS38.214, when a given SRS resource set is configured for beam management, it is possible to transmit only a single SRS resource within the SRS resource set at a given time.

[0043] As used herein, "UE panel" refers to a logical entity that can be mapped to a physical UE antenna. Under certain conditions, the gNB can assume that the mapping between the UE's physical antenna and the logical entity "UE panel" activated for transmission will not change. Depending on the UE's own implementation, the "UE panel" can have at least the following functionalities as an antenna group unit to independently control its Tx beam.

[0044] For a UE-initiated channel occupation (“CO”), the reference duration for adjusting the contention window size (“CWS”) is defined as follows.

[0045] For a CO with a PUSCH and for each set of LBT bandwidth targeted to maintain a single contention window, the reference duration for CWS adjustment is from the start of the CO until the end of the first time slot when at least one PUSCH is transmitted over all resources allocated for the PUSCH, or until the end of the first transmission burst by a UE containing a PUSCH transmitted over all resources allocated for the PUSCH, whichever occurs earlier.

[0046] If a CO has a PUSCH but does not have any PUSCH transmitted over all the resources allocated for that PUSCH, then the duration of the first transmission burst performed by the UE within the CO containing the PUSCH is a reference duration for CWS adjustment.

[0047] The first problem addressed by this disclosure concerns how to determine consistent LBT failure using spatial LBT in the presence of multi-panel operation. For the definition of consistent LBT failure in NR-U, spatial LBT and multi-panel transmission have not been considered to date. Version 16 assumes the UE is performing only omnidirectional LBT. This disclosure provides several embodiments aimed at defining events of consistent LBT failure and corresponding UE behavior that allow the benefits of performing CCA / LBT procedures (in parallel) on multiple panels / beams to be utilized. Additionally, this disclosure presents a solution for the efficient management of sets of panels / beams active in the UE for transmission and / or reception.

[0048] The second problem addressed by this disclosure concerns UE-initiated COT sharing in the presence of spatial LBT. In the case of UE-initiated COT sharing, the gNB is unaware of the spatial characteristics (spatial filters) used by the UE for the LBT procedure; that is, the gNB does not know which Rx panel / beam the UE is performing CCA / LBT within the acquired COT. Therefore, the gNB can perform subsequent DL transmissions within the shared COT for completely different spatial orientations, which can lead to increased collisions.

[0049] Figure 1A wireless communication system 100 for handling LBT failures in a panel / beamset cluster according to embodiments of the present disclosure is described. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a radio access network (“RAN”) 120, and a mobile core network 140. The RAN 120 and the mobile core network 140 form a mobile communication network. The RAN 120 may consist of a base station unit 121, and the remote unit 105 communicates with the base station unit 121 using a wireless communication link 123. Although in Figure 1 The document depicts a specific number of remote units 105, base station units 121, wireless communication links 123, RAN 120, and mobile core network 140, but those skilled in the art will recognize that any number of remote units 105, base station units 121, wireless communication links 123, RAN 120, and mobile core network 140 can be included in the wireless communication system 100.

[0050] In one implementation, the wireless communication system 100 conforms to the 5G system specified in the 3GPP specification. However, more generally, the wireless communication system 100 can implement other open or proprietary communication networks, such as LTE or WiMAX, and other networks. This disclosure is not intended to limit it to any particular wireless communication system architecture or protocol implementation.

[0051] In one embodiment, remote unit 105 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart TVs (e.g., internet-connected TVs), smart appliances (e.g., internet-connected appliances), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), etc. In some embodiments, remote unit 105 may include wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, remote unit 105 may be referred to as a UE, subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user terminal, wireless transmit / receive unit (“WTRU”), device, or other terms used in the art.

[0052] Remote unit 105 can communicate directly with one or more base station units 121 in RAN 120 via uplink (“UL”) and downlink (“DL”) communication signals. Additionally, UL and DL communication signals can be carried on wireless communication link 123. Here, RAN 120 is an intermediate network providing remote unit 105 with access to the mobile core network 140.

[0053] In some embodiments, remote unit 105 communicates with application server 151 (or another communication peer) via a network connection to mobile core network 140. For example, application 107 in remote unit 105 (e.g., web browser, media client, telephony / VoIP application) can trigger remote unit 105 to establish a PDU session (or other data connection) with mobile core network 140 using RAN 120 (e.g., a 3GPP access network and / or a non-3GPP access network). Mobile core network 140 then uses the PDU session to relay services between remote unit 105 and data network 150 (e.g., application server 151). The PDU session represents a logical connection between remote unit 105 and UPF 141. To establish a PDU session, remote unit 105 must register with the mobile core network. Note that remote unit 105 can establish one or more PDU sessions (or other data connections) with mobile core network 140. Therefore, remote unit 105 can have at least one PDU session for communicating with data network 150. Remote unit 105 can establish additional PDU sessions for communication with other data networks and / or other communication peers.

[0054] Base station unit 121 may be distributed across a geographical area. In some embodiments, base station unit 121 may also be referred to as an access terminal, access point, base station, base station, node B, eNB, gNB, home node B, relay node, RAN node, or any other term used in the art. Base station unit 121 is typically part of a radio access network (“RAN”) such as RAN 120, which may include one or more controllers communicatively coupled to one or more corresponding base station units 121. These and other elements of the radio access network are not shown, but are generally known to those skilled in the art. Base station unit 121 is connected to mobile core network 140 via RAN 120.

[0055] Base station unit 121 can serve multiple remote units 105 within its service area, such as a cell or cell sector, via wireless communication link 123. Base station unit 121 can communicate directly with one or more remote units 105 via communication signals. Typically, base station unit 121 transmits DL communication signals to serve remote units 105 in the time, frequency, and / or spatial domains. Furthermore, DL communication signals can be carried on wireless communication link 123. Wireless communication link 123 can be any suitable carrier in the licensed or unlicensed radio spectrum. Wireless communication link 123 facilitates communication between one or more remote units 105 and / or one or more base station units 121.

[0056] In one embodiment, the mobile core network 140 is a 5G core (“5GC”) or an evolved packet core (“EPC”) that may be coupled to packet data networks 150, such as the Internet and private data networks, as well as other data networks. The remote unit 105 may have a subscription or other account with respect to the mobile core network 140. Each mobile core network 140 belongs to a single Public Land Mobile Network (“PLMN”). This disclosure is not intended to limit the implementation of any particular wireless communication system architecture or protocol.

[0057] Mobile core network 140 includes several network functions (“NFs”). As depicted, mobile core network 140 includes one or more user plane functions (“UPFs”) 141. Mobile core network 140 also includes multiple control plane functions, including but not limited to access and mobility management functions (“AMFs”) 143, session management functions (“SMFs”) 145, policy control functions (“PCFs”) 147, and unified data management functions (“UDMs”) 149 serving RAN 120. In various embodiments, mobile core network 140 may also include authentication server functions (“AUSFs”), network repository functions (“NRFs”) (used by various NFs to discover and communicate with each other via APIs), network exposure functions (“NEFs”), or other NFs defined for 5GC.

[0058] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a "network slice" refers to a portion of the mobile core network 140 optimized for a specific service type or communication service. Each network slice includes a set of CP and / or UP network functions. Network instances may be identified by S-NSSAI, while the set of network slices authorized for use by the remote unit 105 is identified by NSSAI. In some embodiments, various network slices may include individual instances of network functions, such as SMF 145 and UPF 141. In some embodiments, different network slices may share some common network functions, such as AMF 143. For illustration purposes, in Figure 1 Different network slices are not shown, but their support is assumed.

[0059] Despite Figure 1 The document describes a specific number and type of network functions, but those skilled in the art will recognize that any number and type of network functions can be included in the mobile core network 140. Furthermore, in the case where the mobile core network 140 is an EPC, the described network functions can be replaced by appropriate EPC entities, such as MME, S-GW, P-GW, HSS, etc. In some embodiments, the mobile core network 140 may include an AAA server.

[0060] Specifically, remote unit 105 can detect LBT failures of at least one panel / beam corresponding to an uplink transmission and track LBT failures of all panels and beams supported by remote unit 105 (e.g., for all active / configured panels / beams). When a predefined maximum number of LBT failure indications have been received, remote unit 105 can autonomously deactivate a panel / beam.

[0061] In some embodiments, deactivating a panel / beam includes ignoring beam-specific information in the DCI or UL license. In some embodiments, deactivating a panel / beam includes selecting a different panel / beam for LBT and / or the corresponding uplink transmission. In such embodiments, remote unit 105 activates the selected panel / beam and may initiate a RACH procedure for the newly activated panel / beam. In various embodiments, the deactivated panel / beam and the selected panel / beam belong to a set of active / configured panels / beams.

[0062] Although Figure 1 The description depicts components of the 5G RAN and 5G core network, but the described embodiment for handling LBT failures in the panel / beamset set is applicable to other types of communication networks and RATs, including IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, Bluetooth, ZigBee, Sigfoxx, etc. For example, in LTE variants involving EPC, AMF 143 can be mapped to the MME, SMF 145 can be mapped to the control plane portion of the PGW and / or mapped to the MME, UPF 141 can be mapped to the SGW and the user plane portion of the PGW, UDM / UDR 149 can be mapped to the HSS, etc.

[0063] In the following description, the term "RAN node" is used for the base station, but it can be replaced by any other radio access node, such as gNB, eNB, BS, AP, NR, etc. Furthermore, the operation is described primarily in the context of 5G NR. However, the proposed solution / method is equally applicable to other mobile communication systems that support spatial multiplexing communications.

[0064] In various embodiments, an antenna port is defined such that a channel transmitting a symbol on the antenna port can be inferred from a channel transmitting another symbol on the same antenna port. One or more antenna ports are used for UL transmission.

[0065] Two antenna ports are said to be quasi-co-located (“QCL”) if the large-scale properties of a channel that transmits symbols on one antenna port can be inferred from the channel that transmits symbols on another antenna port. Large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. Two antenna ports may be quasi-co-located relative to a subset of the large-scale properties. Spatial Rx parameters may include one or more of the following: angle of arrival (“AoA”), main AoA, average AoA, angular spread, power angular spectrum of AoA (“PAS”), average departure angle (“AoD”), PAS of AoD, transmit / receive channel correlation, transmit / receive beamforming, spatial channel correlation, etc.

[0066] According to embodiments, an "antenna port" can be a logical port that corresponds to a beam (generated by beamforming) or a physical antenna on the device. In some embodiments, a physical antenna can be directly mapped to a single antenna port, where the antenna port corresponds to an actual physical antenna. Alternatively, a set or subset of physical antennas, or an antenna set or antenna array or antenna subarray, can be mapped to one or more antenna ports after applying complex weights, cyclic delays, or both to the signal on each physical antenna. A set of physical antennas can have antennas from a single module or panel or from multiple modules or panels. As in antenna virtualization schemes such as cyclic delay diversity ("CDD"), the weights can be fixed. The process for deriving an antenna port from a physical antenna can be specific to the device implementation and transparent to other devices.

[0067] Throughout the various embodiments of this disclosure, the terms quasico-location and quasico-located will be understood primarily in relation to the spatial channel correlation of transmit / receive beamforming, but should not be limited thereto.

[0068] According to the first solution, if LBT fails on all panels / beams on which LBT is performed for the corresponding UL transmission, then LBT failure is declared for the UL transmission; that is, LBT failure is indicated for each UL transmission. Here, it is assumed that remote unit 105 performs LBT on a set of panels and / or beams, for example, the set of panels / beams can be indicated / configured by base station unit 121 for the corresponding UL transmission.

[0069] According to the second solution, remote unit 105 counts LBT failures (e.g., LBT failure indications as indicated by the physical layer) on a per-panel / beam basis and deactivates a panel / beam when a predefined maximum number of LBT failure indications has been received. If—for all active panels / beams—the predefined maximum number of LBT failures has been met (or exceeded), remote unit 105 declares a consistent LBT failure for the UL BWP.

[0070] According to the third solution, the Rx panel / beam used by remote unit 105 for the LBT process can be different from the Rx panel / beam used for DL ​​data / control reception. In one implementation of this solution, the Rx panel / beam used for the LBT process is determined by Tx panel / beam information associated with the corresponding UL transmission for which the LBT process is performed. For example, remote unit 105 uses panel / beam information carried in the DCI (UL License), such as SRI, to set the Rx panel / beam for the corresponding LBT process / CCA. In other words, the RX panel / beam used for CCA / LBT and the Tx panel / beam used for the corresponding UL transmission will have the same spatial characteristics.

[0071] According to the fourth solution, remote unit 105 is allowed to autonomously change the Tx panel / beam (or spatial filter) used for the configured licensed PUSCH. For this solution, it is assumed that the PDCCH carrying Tx panel / beam information, such as SRI, is activated for license type 2. In the case of license type 1, the Tx panel / beam to be used for CG PUSCH transmission is configured via higher-layer signaling, such as RRC signaling. Since the validity period of the configured license may be quite long, it may be necessary to update the spatial filter (Tx panel / beam) used for CG PUSCH transmission, for example, due to the mobility of the remote unit.

[0072] According to the fifth solution, remote unit 105 applies SRI information received within the dynamic UL license not only for the corresponding dynamic PUSCH transmission but also for licensed PUSCH transmissions configured for subsequent configurations within the same cell. According to this solution, base station unit 121 can perform all subsequent scheduled UL transmissions, e.g., on the PUSCH, by means of a single DCI update / manipulation of the Tx panel / beam.

[0073] According to the sixth solution, whenever remote unit 105 is sharing its COT with base station unit 121 (or other nodes), for example, when remote unit 105 indicates COT sharing information within AUL-UCI or CG-UCI, remote unit 105 signals information about the spatial filter (Rx panel / beam) used for the CCA / LBT process. This information can be used by base station unit 121 for subsequent DL transmission within the shared COT. Here, it is assumed that base station unit 121 performs DL transmission with the same spatial characteristics (e.g., the same / similar spatial filter) as the spatial characteristics used to perform LBT on the Rx panel / beam. Essentially, what should be avoided is that remote unit 105 performs LBT for a specific spatial direction, and then base station unit 121 performs DL transmission in the opposite spatial direction within the COT acquired by remote unit 105.

[0074] In one exemplary implementation of the sixth solution, remote unit 105 transmits its Rx panel / beam information to base station unit 121 via a signal within the CG / AUL-UCI. This information may include TCI status information.

[0075] According to the seventh solution, remote unit 105 is not permitted to switch Tx panels / beams during COT. Remote unit 105 will use the same spatial filter for UL transmission during COT as used for the CCA / LBT process. If remote unit 105 changes its UL panel / beam during COT, remote unit 105 will perform CCA / LBT before transmitting on the uplink with a different UL Tx panel / beam.

[0076] Figure 2 An NR protocol stack 200 according to an embodiment of this disclosure is depicted. Although Figure 2 The diagram shows UE 205, RAN node 210, and 5G core network (“5GC”) 215, but these represent a collection of remote units 105 that interact with base station unit 121 and mobile core network 140. As depicted, protocol stack 200 includes user plane protocol stack 220 and control plane protocol stack 225. User plane protocol stack 220 includes physical (“PHY”) layer 230, media access control (“MAC”) sublayer 235, radio link control (“RLC”) sublayer 240, packet data convergence protocol (“PDCP”) sublayer 245, and service data adaptation protocol (“SDAP”) layer 250. Control plane protocol stack 225 includes physical layer 230, MAC sublayer 235, RLC sublayer 240, and PDCP sublayer 245. Control plane protocol stack 225 also includes radio resource control (“RRC”) layer 255 and non-access stratum (“NAS”) layer 260.

[0077] The AS layer (also referred to as the "AS protocol stack") for the user plane protocol stack 220 consists of at least SDAP, PDCP, RLC, and MAC sublayers, as well as a physical layer. The AS layer for the control plane protocol stack 225 consists of at least RRC, PDCP, RLC, and MAC sublayers, as well as a physical layer. Layer 2 ("L2") is divided into SDAP, PDCP, RLC, and MAC sublayers. Layer 3 ("L3") includes the RRC sublayer 255 and NAS layer 260 for the control plane and includes, for example, the Internet Protocol ("IP") layer or PDU layer (as depicted) for the user plane. L1 and L2 are referred to as "lower layers," while L3 and higher layers (e.g., transport layer, application layer) are referred to as "higher layers" or "upper layers."

[0078] Physical layer 230 provides a transport channel to MAC sublayer 235. MAC sublayer 235 provides a logical channel to RLC sublayer 240. RLC sublayer 240 provides an RLC channel to PDCP sublayer 245. PDCP sublayer 245 provides radio bearers to SDAP sublayer 250 and / or RRC layer 255. SDAP sublayer 250 provides QoS flows to the core network (e.g., 5GC 215). RRC layer 255 provides the addition, modification, and release of carrier aggregation and / or dual connectivity. RRC layer 255 also manages the establishment, configuration, maintenance, and release of signaling radio bearers (“SRB”) and data radio bearers (“DRB”). NAS layer 260 is used to communicate non-radio signaling between UE 205 and, for example, AMF in 5GC 215 (or MME for LTE / EPS scenarios).

[0079] Figure 3 A scenario 300 for handling spatial LBT failure according to embodiments of this disclosure is depicted. Scenario 300 may involve a UE 205, a RAN node 210 with which the UE 205 expects to transmit UL transmissions, and an access point (“AP”) 305 as a potential user on the same communication frequency as the UE 205 and RAN node 210. The UE 205 may be an implementation of remote unit 105 and the RAN node 210 may be an implementation of base station unit 121. The UE 205 has generated a UL TB for transmission to RAN node 210 and therefore performs the LBT procedure for a set of Tx panel / beam configurations corresponding to the UL transmission.

[0080] At time 't1', UE 205 performs LBT on the first Rx panel / beam. Note that the LBT procedure determines whether RAN node 210, AP 305, or another device is using the channel (i.e., radio frequency) that UE 205 will use for UL transmission. Here, it is assumed that LBT fails for Rx panel / beam #1. At time 't2', UE 205 performs LBT on the second Rx panel / beam. Here, it is assumed that LBT succeeds for Rx panel / beam #2. Therefore, UE 205 performs UL transmission on the corresponding Tx panel / beam #2. However, if LBT fails for Rx panel / beam #2, UE 205 continues to perform LBT procedures for the set of Tx panel / beam configurations until LBT succeeds or until LBT fails for all configured panels / beams.

[0081] According to the first solution, UE 205 declares an LBT failure for a UL transmission in the event that all panel / beam LBTs performed on it for the corresponding UL transmission have failed; that is, it indicates an LBT failure for each UL transmission. It is assumed that UE 205 performs LBTs on a set of panels and / or beams used for the corresponding UL transmission. In various embodiments, the set of panels / beams can be indicated / configured by RAN node 210. The LBT process can be performed in parallel for the configured set of panels / beams, or alternatively, as... Figure 3 The LBT procedure is performed in the TDM mode as described in the diagram. If any LBT using the configured panel and / or beam fails, UE 205 considers the LBT for the corresponding uplink transmission to have failed. Note that LBT failure is determined on a per-transmission basis.

[0082] When a lower-layer entity performs multiple LBT procedures before a UL transmission and no transmission is performed, an LBT failure indication is sent from the lower layer to the MAC entity. Therefore, the LBT failure counter, such as LBT_COUNTER, is incremented by one. It should be noted that even when the UE 205 is performing LBTs on two different Rx panels / beams and only one LBT on one of the two panels / beams is successful, the counter is not incremented for the failed LBTs; that is, LBT_COUNTER is not counted per panel / beam.

[0083] According to one implementation of the first solution, UE 205 measures (and tracks) LBT failures per panel / beam that differ from the counter LBT_COUNTER. UE 205 can further report LBT failure statistics, such as LBT failures per panel / beam, to RAN node 210, which can use this information for future scheduling / UL beam management. In addition to per-transmission LBT failure processing as described above, LBT failures can also be counted per panel / beam.

[0084] Therefore, UE 205 may have a counter, such as LBT_COUNTER, for declaring consistent LBT failures, which is incremented by one when all LBT attempts fail for UL transmission, and then has additional (supplementary) counters for one or each active panel / beam. Here, the supplementary counters may be used to generate some statistics about LBT failures per panel / beam. In one variant, a subset of the LBT statistics obtained per panel / beam is reported to RAN node 210. For example, UE 205 may only report LBT statistics for panels / beams where LBT failures exceed a certain (e.g., predefined) threshold, for example, to reduce reporting overhead.

[0085] According to another implementation of the first solution, UE 205 counts and / or reports LBT failures by group of panels and / or beams with the same QCL relationship. In such embodiments, the group LBT failure counter is incremented for each panel and / or beam group only when all panels and / or beams belonging to the same QCL group have failed.

[0086] According to the second solution, UE 205 tracks LBT failures on a per-panel / beam basis, such as LBT failure indications as indicated by the physical layer, and autonomously deactivates (e.g., UE-initiated) a panel / beam when a predefined maximum number of LBT failure indications have been received for that panel / beam. According to the second solution, if the predefined maximum number of LBT failures has been exceeded / met for all active panels / beams, UE 205 declares a consistent LBT failure for the UL BWP. In cases where the maximum number of LBT failures (e.g., lbt-FailureInstanceMaxCount) has been met / exceeded for a panel / beam, UE 205 can autonomously deactivate the panel / beam; that is, UE 205 will not perform any further LBT procedures on that panel / beam. In some embodiments, UE 205 can notify RAN node 210 when deactivating a panel / beam, for example, by sending a MAC CE or any other signaling.

[0087] When a certain number of pre-configured LBTs for a specific panel / beam have failed, UE 205 is allowed to autonomously deactivate this panel / beam. This may imply that UE 205 ignores beam-specific information signaled in the DCI / UL license and, for example, selects different panels / beams from the set of active / configured panels / beams for LBT and / or corresponding UL transmissions. According to one implementation, UE 205 may also autonomously activate another panel / beam upon (autonomous) deactivation and perform a random access procedure for the newly activated panel / beam. Alternatively, UE 205 may notify the network (e.g., RAN node 210) about the newly activated panel / beam, for example, by signaling a MAC CE or any other signaling.

[0088] Figure 4 The LBT process 400 for unlicensed communication 405 according to an embodiment of the present disclosure is described. When the communication channel is a wide-bandwidth unlicensed carrier 410 (e.g., several hundred MHz), the CCA / LBT process relies on detecting, such as Figure 4 The energy levels on multiple sub-bands 415 of the communication channel are shown. LBT parameters (such as type / duration, idle channel assessment parameters, etc.) are configured in UE 205 by RAN node 210.

[0089] Figure 4 The frame structure of radio frame 405 for unlicensed communication between UE 205 and RAN node 210 is also depicted. Radio frame 405 can be divided into subframes (indicated by subframe boundary 420) and can be further divided into time slots (indicated by time slot boundary 425). Radio frame 405 uses a flexible arrangement in which uplink and downlink operations are on the same frequency channel but separated in time. However, subframes are not configured as downlink subframes or uplink subframes, and specific subframes can be used by either UE 205 or RAN node 210. As previously discussed, LBT is performed before transmission. If LBT does not conflict with time slot boundary 425, a reservation signal 430 can be transmitted to reserve the channel until the time slot boundary is reached and data transmission begins.

[0090] According to the third solution, the Rx panel / beam used by UE 205 for the LBT procedure can be different from the Rx panel / beam used for DL ​​data / control reception. In an exemplary implementation of this solution, the Rx panel / beam used for the LBT procedure is determined by the Tx panel / beam information associated with the corresponding UL transmission for which the LBT procedure is performed. For example, UE 205 uses panel / beam information carried in the DCI (UL License), such as SRI, to set the Rx panel / beam for the corresponding LBT procedure / CCA. In other words, the Rx panel / beam used for CCA / LBT and the Tx panel / beam used for the corresponding UL transmission will have the same spatial characteristics.

[0091] According to one implementation of this solution, the reference signal used to define the Rx panel / beam (spatial filter) for CCA / LBT is an SRS resource, for example, indicated by the SRI in the DCI. It should be noted that the panel / beam indication is a reference to the previously transmitted / configured reference signal in the form of a spatial QCL relationship. UE 205 will apply the same spatial characteristics as the SRS indicated by the SRI for the corresponding UL transmission for reception (for CCA / LBT).

[0092] In another implementation of this solution, a mapping is configured between the SRI (Signaled Reference Indicator) signaled within the DCI (UL License) and the TCI (Transmission Configuration Indicator) used for CCA / LBT procedures. Downlink beam indication is performed by signaling a so-called Transport Configuration Indicator (TCI) to the UE 205, which provides the UE 205 with a spatial QCL reference for setting its Rx panel / beam. The UE 205 is configured with a list of TCI states via higher-layer signaling, where each TCI state is configured with a set of CSI-RS or SSB IDs. In each state, a CSI-RS or SSB ID is selected to be used as the spatial QCL reference. By introducing the mapping between SRI (states) and TCI (states), the network can control which Rx panel / beam the UE 205 uses for the CCA / LBT procedure. In other words, the mapping allows the network to configure which CSI-RS or SSB ID the UE 205 uses as the QCL reference for the CCA / LBT procedure.

[0093] In one embodiment, a third solution can be implemented by defining MAC entity behavior to include the following for the case where an LBT failure indication has been received from a lower layer and LBT_COUNTER >= lbt-FailureInstanceMaxCount.

[0094] When none of the UL BWPs configured with PRACH timing in the serving cell acting as SpCell have declared a consistent LBT failure, the MAC entity will deactivate the active UL BWP for each active serving cell configured with lbt-FailureRecoveryConfig, switch the active UL BWP to the UL BWP configured with PRACH timing in this serving cell that has not yet declared a consistent LBT failure, and activate the selected UL BWP. Note that during the BWP handover operation, the DL BWP can also be switched if necessary.

[0095] According to the fourth solution, UE 205 is allowed to autonomously change the Tx panel / beam (spatial filter) used for configured licensed PUSCH. For this solution, it is assumed that for configured license type 2, the PDCCH carrying Tx panel / beam information, such as SRI, is activated. In the case of configured license type 1, the Tx panel / beam to be used for CG PUSCH transmission is configured via higher-layer signaling, such as RRC signaling.

[0096] Because the validity period of the configured permission can be quite long (e.g., several seconds), it may be necessary to update the spatial filter (Tx panel / beam) used for CG PUSCH transmission, for example, due to the mobility of UE 205. According to one implementation of the fourth solution, UE 205 can update its transmission beam characteristics, i.e., Tx panel / beam, based on the quality of CSI-RS / SSB. For example, UE 205 can update the beam characteristics to provide the highest CSI-RS / SSBSINR.

[0097] According to a further implementation of the fourth solution, UE 205 can notify RAN node 210 about the currently used Tx panel / beam. Reporting the currently used Tx panel / beam, for example, UE 205 might only report changes in the Tx panel / beam, allowing RAN node 210 to consider this information for future scheduling. In a particular implementation of the fourth solution, for cases where a licensed PUSCH is transmitted on an unlicensed cell, UE 205 includes information about the currently used Tx panel / beam in the AUL-UCI or CG-UCI. In another implementation of the fourth solution, UE 205 reports the Tx panel / beam information within the MAC control element.

[0098] As one alternative embodiment, the current set of panels / beams is used. In addition, the network (e.g., RAN node 210) configures a candidate set of panels / beams based on the capabilities of UE 205. UE 205 performs CCA / LBT and / or CSI-RS / SSB measurements on the candidate set. The measurements are reported to RAN node 210, which may cause RAN node 210 to configure UE 205 with an updated set of current panels / beams. Alternatively, UE 205 may autonomously update its current set of panels / beams and notify the network (e.g., as previously described).

[0099] According to the fifth solution, UE 205 applies SRI information received within the dynamic UL license not only for corresponding dynamic PUSCH transmissions but also for licensed PUSCH transmissions configured for subsequent configurations within the same cell. With this solution, RAN node 210 can update / manipulate the Tx panel / beam for all subsequently scheduled UL transmissions, e.g., on the PUSCH, using a single DCI. Since RAN node 210 does not need to attach a specific PDCCH for the configured license transmission, such as a PDCCH addressed to CS-RNTI, to change the Tx panel / beam used for CG PUSCH transmissions, this solution reduces signaling overhead.

[0100] In one particular implementation of this solution, the DCI, or UL license, contains explicit information, namely whether the SRI information will also be applied to the configured license.

[0101] Figure 5 Table 500 depicts the fields used for AUL-UCI. Note that AUL-UCI includes a Channel Occupancy Time (“COT”) sharing indication field. According to the sixth solution, whenever UE 205 is sharing its COT with RAN node 210 (or other nodes), for example, when UE 205 indicates COT sharing information within the CG / AUL-UCI, UE 205 signals information about the spatial filters (Rx panels / beams) used for the CCA / LBT procedure. This information can be used by RAN node 210 for subsequent DL transmissions within the shared COT.

[0102] For the sixth solution, it is assumed that RAN node 210 performs DL transmission with the same spatial characteristics (e.g., the same / similar spatial filters) as the spatial characteristics used to perform LBT on the Rx panel / beam. Therefore, UE 205 performs LBT for a specific spatial direction, and then RAN node 210 performs DL transmission in the opposite spatial direction within the COT obtained by UE 205.

[0103] In one exemplary implementation of this solution, UE 205 transmits UE 205Rx panel / beam information to RAN node 210 via a signal within the AUL-UCI. This information may include TCI status information.

[0104] According to the seventh solution, UE 205 is not permitted to switch Tx panels / beams during COT. UE 205 will use the same spatial filter for UL transmission during COT as used for the CCA / LBT procedure. If UE 205 changes its UL panel / beam during COT, UE 205 will perform CCA / LBT before transmitting on the uplink with a different UL Tx panel / beam.

[0105] Figure 6 User equipment device 600, according to embodiments of the present disclosure, can be used for processing LBT failures in a panel / beamset configuration. In various embodiments, user equipment device 600 is used to implement one or more of the solutions described above. User equipment device 600 may be an embodiment of remote unit 105 and / or UE 205 as described above. Furthermore, user equipment device 600 may include processor 605, memory 610, input device 615, output device 620, and transceiver 625.

[0106] In some embodiments, input device 615 and output device 620 are combined into a single device, such as a touchscreen. In some embodiments, user equipment device 600 may not include any input device 615 and / or output device 620. In various embodiments, user equipment device 600 may include one or more of the following: processor 605, memory 610, and transceiver 625, and may not include input device 615 and / or output device 620.

[0107] As depicted, transceiver 625 includes at least one transmitter 630 and at least one receiver 635. Here, transceiver 625 communicates with one or more cells supported by one or more base station elements 121, including PCell and / or PSCell, and optionally one or more SCells. Additionally, transceiver 625 may support at least one network interface 640 and / or application interface 645. Application interface 645 may support one or more APIs. Network interface 640 may support 3GPP reference points such as Uu and PC5. Other network interfaces 640 may be supported, as will be understood by those skilled in the art.

[0108] In one embodiment, processor 605 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 605 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, processor 605 executes instructions stored in memory 610 to perform the methods and routines described herein. Processor 605 is communicatively coupled to memory 610, input device 615, output device 620, and transceiver 625.

[0109] In various embodiments, processor 605 controls user equipment device 600 to implement the UE behavior described above. For example, via transceiver 625, processor 605 performs an LBT procedure for a set of UE Tx panels configured corresponding to UL transmission. Processor 605 declares an LBT failure for UL transmission in response to determining that the LBT procedure for all UE Tx panels in the configured set has failed. Additionally, processor 605 increments an LBT failure counter in response to an LBT failure for UL transmission. Note that while user equipment device is described in terms of performing an LBT procedure for a “set of UE panels,” in other embodiments, LBT may be performed for a “set of beams.” As used herein, the term “panel / beam” (or similar annotation) indicates that this description applies to UE panels and / or beams.

[0110] In some embodiments, the processor 605 performs LBT procedures on a set of panel / beam configurations by concurrently executing multiple LBT procedures (i.e., performing LBT procedures in parallel on the set of panels / beams). In other embodiments, the processor 605 performs LBT procedures on a set of panel / beam configurations by sequentially executing multiple LBT procedures (i.e., performing LBT procedures in a TDM manner on the set of panels / beams).

[0111] In some embodiments, processor 605 tracks per-panel / beam LBT failures for each panel / beam in a configured set. In such embodiments, processor 605 performs autonomous deactivation (i.e., UE-initiated deactivation) of the first panel / beam in the configured set in response to a first panel / beam LBT failure counter associated with the first panel / beam exceeding a threshold.

[0112] In some embodiments, processor 605 activates a second panel / beam in response to deactivating the first panel / beam and uses the second panel / beam to perform a random access procedure (i.e., a RACH procedure). In some embodiments, the UL transmission corresponds to a configured license. In some embodiments, processor 605 controls transceiver 625 to report LBT failure statistics to the RAN node, wherein the LBT failure statistics include per-panel / beam LBT failures for a set of panel / beam configurations.

[0113] In some embodiments, the processor 605 organizes panels / beams into at least one group of panels / beams, wherein all panels / beams in the group have the same QCL relationship. In such embodiments, the processor 605 tracks a per-panel / beam LBT failure counter for each group, wherein the per-panel / beam LBT failure counter for a group is incremented only when all panels / beams in the group experience an LBT failure.

[0114] In some embodiments, processor 605 performs the LBT process using a first receive Rx panel / beam corresponding to a first panel / beam of a configured set and further uses a second Rx panel / beam for downlink reception, wherein the first Rx panel / beam is different from the second Rx panel / beam. In some embodiments, processor 605 selects the first Rx panel / beam based on the SRI included in the uplink license for UL transmission.

[0115] In some embodiments, declaring an LBT failure for a UL transmission includes the physical layer entity of user equipment device 600 sending an LBT failure indication to the MAC entity of user equipment device 600, wherein the MAC entity increments an LBT failure counter.

[0116] In one embodiment, memory 610 is a computer-readable storage medium. In some embodiments, memory 610 includes volatile computer storage media. For example, memory 610 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 610 includes non-volatile computer storage media. For example, memory 610 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 610 includes both volatile and non-volatile computer storage media.

[0117] In some embodiments, memory 610 stores data related to LBT failures in the collective processing of panels / beams. For example, memory 610 may store panel / beam configurations, resource configurations, etc. In some embodiments, memory 610 also stores program code and related data, such as an operating system or other controller algorithms running on device 600.

[0118] In one embodiment, input device 615 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, etc. In some embodiments, input device 615 may be integrated with output device 620, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 615 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 615 includes two or more different devices, such as a keyboard and a touch panel.

[0119] In one embodiment, output device 620 is designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 620 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 620 may include, but is not limited to, LCD displays, LED displays, OLED displays, projectors, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, output device 620 may include a wearable display, such as a smartwatch, smart glasses, head-up display, etc., that is separate from but communicatively coupled to the rest of user equipment device 600. Furthermore, output device 620 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0120] In some embodiments, output device 620 includes one or more speakers for generating sound. For example, output device 620 may generate an auditory alarm or notification (e.g., a beep or ringtone). In some embodiments, output device 620 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of output device 620 may be integrated with input device 615. For example, input device 615 and output device 620 may form a touchscreen or similar touch-sensitive display. In other embodiments, output device 620 may be located near input device 615.

[0121] Transceiver 625 includes at least a transmitter 630 and at least one receiver 635. One or more transmitters 630 can be used to provide UL communication signals to base station unit 121, as described herein as UL transmission. Similarly, as described herein, one or more receivers 635 can be used to receive DL communication signals from base station unit 121. Although only one transmitter 630 and one receiver 635 are illustrated, user equipment device 600 can have any suitable number of transmitters 630 and receivers 635. Furthermore, transmitters 630 and receivers 635 can be of any suitable type. In one embodiment, transceiver 625 includes a first transmitter / receiver pair for communicating with a mobile communication network on licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network on unlicensed radio spectrum.

[0122] In some embodiments, a first transmitter / receiver pair for communicating with a mobile communication network on licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network on unlicensed radio spectrum may be combined into a single transceiver unit, such as a single chip performing functions for use with both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, certain transceivers 625, transmitters 630, and receivers 635 may be implemented as physically separate components that access shared hardware and / or software resources, such as, for example, a network interface 640.

[0123] In various embodiments, one or more transmitters 630 and / or one or more receivers 635 may be implemented and / or integrated into a single hardware component, such as a multi-transceiver chip, system-on-a-chip, ASIC, or other type of hardware component. In some embodiments, one or more transmitters 630 and / or one or more receivers 635 may be implemented and / or integrated into a multi-chip module. In some embodiments, other components such as network interface 640 or other hardware components / circuitets may be integrated with any number of transmitters 630 and / or receivers 635 into a single chip. In such embodiments, transmitters 630 and receivers 635 may be logically configured as transceivers 625 using one or more common control signals or as modular transmitters 630 and receivers 635 implemented in the same hardware chip or multi-chip module.

[0124] Figure 7This description depicts one embodiment of a network device apparatus 700 that can be used to process LBT failures for panel / beam aggregations according to embodiments of the present disclosure. In some embodiments, the network apparatus 700 may be an embodiment of a RAN node and its supporting hardware, such as base station unit 121, RAN node 210, and / or gNB as described above. Furthermore, the network device apparatus 700 may include a processor 705, a memory 710, an input device 715, an output device 720, and a transceiver 725. In some embodiments, the network device apparatus 700 does not include any input device 715 and / or output device 720.

[0125] As depicted, transceiver 725 includes at least one transmitter 730 and at least one receiver 735. Here, transceiver 725 communicates with one or more remote units 105. Additionally, transceiver 725 may support at least one network interface 740 and / or application interface 745. Application interface 745 may support one or more APIs. Network interface 740 may support 3GPP reference points such as Uu, N1, N2, and N3. Other network interfaces 740 may be supported, as will be understood by those skilled in the art.

[0126] In one embodiment, processor 705 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 705 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, processor 705 executes instructions stored in memory 710 to perform the methods and routines described herein. Processor 705 is communicatively coupled to memory 710, input device 715, output device 720, and transceiver 725.

[0127] In various embodiments, processor 705 controls network device apparatus 700 to implement the RAN node behavior described above. For example, processor 705 may support one or more serving cells serving a UE, including PCell and / or SCell. In various embodiments, transceiver 725 may receive BFRQs, as described herein. Furthermore, as described herein, processor 705 may allocate UL-SCH resources to a UE.

[0128] In one embodiment, memory 710 is a computer-readable storage medium. In some embodiments, memory 710 includes volatile computer storage media. For example, memory 710 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 710 includes non-volatile computer storage media. For example, memory 710 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 710 includes both volatile and non-volatile computer storage media.

[0129] In some embodiments, memory 710 stores data related to LBT failures in aggregate processing for a panel / beam, such as UE identity, panel / beam configuration, resource permissions, etc. In some embodiments, memory 710 also stores program code and related data, such as an operating system (“OS”) or other controller algorithms running on network device device 700, and one or more software applications.

[0130] In one embodiment, input device 715 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, etc. In some embodiments, input device 715 may be integrated with output device 720, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 715 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 715 includes two or more different devices, such as a keyboard and a touch panel.

[0131] In one embodiment, output device 720 may include any known electronically controllable display or display device. Output device 720 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 720 includes an electronic display capable of outputting visual data to a user. Furthermore, output device 720 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0132] In some embodiments, output device 720 includes one or more speakers for generating sound. For example, output device 720 may generate an auditory alarm or notification (e.g., a beep or ringtone). In some embodiments, output device 720 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of output device 720 may be integrated with input device 715. For example, input device 715 and output device 720 may form a touchscreen or similar touch-sensitive display. In other embodiments, all or part of output device 720 may be located near input device 715.

[0133] As discussed above, transceiver 725 can communicate with one or more remote units and / or with one or more network functions that provide access to one or more PLMNs. Transceiver 725 operates under the control of processor 705 to transmit messages, data, and other signals, and also to receive messages, data, and other signals. For example, processor 705 can selectively activate the transceiver (or a portion thereof) at specific times to send and receive messages.

[0134] Transceiver 725 may include one or more transmitters 730 and one or more receivers 735. In some embodiments, one or more transmitters 730 and / or one or more receivers 735 may share transceiver hardware and / or circuitry. For example, one or more transmitters 730 and / or one or more receivers 735 may share antennas, antenna tuners, amplifiers, filters, oscillators, mixers, modulators / demodulators, power supplies, etc. In one embodiment, transceiver 725 implements multiple logical transceivers using different communication protocols or protocol stacks while using common physical hardware.

[0135] Figure 8 One embodiment of a method 800 for processing LBT failures for a panel / beamset according to embodiments of the present disclosure is described. In various embodiments, method 800 is performed by a UE such as remote unit 105, UE 205, and / or user equipment device 600 as described above. In some embodiments, method 800 is performed by a processor such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0136] Method 800 begins and performs the LBT procedure 805 for a set of configurations of Tx beams corresponding to the uplink transmission. Method 800 includes declaring an LBT failure for the uplink transmission at 810 in response to determining that the LBT procedure for all Tx beams in the configuration set has failed. Method 800 includes incrementing the LBT failure counter at 815 in response to the LBT failure for the uplink transmission. Method 800 ends.

[0137] This document discloses a first apparatus for processing LBT failures for an assembly of panels / beams according to embodiments of the present disclosure. The first apparatus may be implemented by a UE, such as remote unit 105, UE 205, and / or user equipment apparatus 600 as described above. The first apparatus includes a transceiver comprising a plurality of UE panels associated with one or more beams. The first apparatus includes a processor that performs an LBT procedure for an assembly of configurations of UE Tx panels corresponding to an uplink transmission. The processor declares an LBT failure for the uplink transmission in response to determining that an LBT procedure for all UE Tx panels in the configuration set has failed, and increments an LBT failure counter in response to the LBT failure for the uplink transmission. Note that while the first apparatus is described as performing an LBT procedure for an “assembly of UE panels,” in other embodiments, LBT may be performed for an “assembly of beams.”

[0138] In some embodiments, performing an LBT procedure on a set of UE Tx panel configurations includes performing multiple LBT procedures concurrently (i.e., performing LBT on the set of UE Tx panels in parallel). In other embodiments, performing an LBT procedure on a set of UE Tx panel configurations includes performing multiple LBT procedures sequentially (i.e., performing LBT on the set of UE Tx panels in a TDM manner).

[0139] In some embodiments, the processor tracks per-panel LBT failures for each UE Tx panel in the configured set. In such embodiments, the processor performs autonomous deactivation (i.e., UE-initiated deactivation) of the first UE Tx panel in the configured set in response to a first per-panel LBT failure counter associated with the first UE Tx panel exceeding a threshold.

[0140] In some embodiments, the processor activates a second UE Tx panel in response to deactivating the first UE Tx panel and uses the second UE Tx panel to perform a random access procedure. In some embodiments, the uplink transmission corresponds to a configured license. In some embodiments, the processor (e.g., via a transceiver) reports LBT failure statistics to the RAN node, wherein the LBT failure statistics include per-panel LBT failures for a set of configurations for the UE Tx panels.

[0141] In some embodiments, the processor forms at least one group of UE Tx panels, wherein all UE Tx panels in the group have the same QCL relationship. In such embodiments, the processor tracks a per-panel LBT failure counter for each group, wherein the per-panel LBT failure counter for a group is incremented only when all UE Tx panels in the group experience an LBT failure.

[0142] In some embodiments, the LBT procedure is performed using a first receiving UE Rx panel corresponding to a first UE Tx panel of a configured set. In such embodiments, the processor further uses a second UE Rx panel for downlink reception, wherein the first UE Rx panel is different from the second UE Rx panel. In some embodiments, the first UE Rx panel is selected based on the SRI included in the uplink license for uplink transmission.

[0143] In some embodiments, declaring an LBT failure for an uplink transmission includes the device's physical layer entity sending an LBT failure indication to the device's MAC entity, wherein the MAC entity increments the LBT failure counter.

[0144] This document discloses a first method for handling LBT failures for a set of panels / beams according to embodiments of this disclosure. The first method can be performed by a UE such as the remote unit 105, UE 205, and / or user equipment device 600 described above. The first method includes performing an LBT procedure for a set of configurations of Tx beams corresponding to uplink transmissions. The first method includes declaring an LBT failure for an uplink transmission in response to determining that an LBT procedure for all Tx beams in the configured set has failed, and incrementing an LBT failure counter in response to the LBT failure for the uplink transmission. Note that although the first method is described as performing an LBT procedure for a “set of beams,” in other embodiments, LBT can be performed for a “set of UE panels.”

[0145] In some embodiments, performing an LBT process on a set of Tx beam configurations includes performing multiple LBT processes concurrently (i.e., performing LBT on the set of Tx beams in parallel). In other embodiments, performing an LBT process on a set of Tx beam configurations includes performing multiple LBT processes sequentially (i.e., performing LBT on the set of Tx beams in a TDM manner).

[0146] In some embodiments, the first method includes tracking per-beam LBT failures for each Tx beam in a configured set. In such embodiments, the first method may further include performing autonomous deactivation (i.e., UE-initiated deactivation) of the first Tx beam in the configured set in response to a first per-beam LBT failure counter associated with the first Tx beam exceeding a threshold.

[0147] In some embodiments, the first method includes activating a second Tx beam in response to deactivating a first Tx beam and using the second Tx beam to perform a random access procedure. In some embodiments, the uplink transmission corresponds to a configured license. In some embodiments, the first method includes reporting LBT failure statistics to the RAN node, wherein the LBT failure statistics include per-beam LBT failures for a set of configurations for the Tx beam.

[0148] In some embodiments, the first method includes forming at least one group of Tx beams, wherein all Tx beams in the group have the same QCL relationship. In such embodiments, the first method includes tracking a per-beam LBT failure counter for each group, wherein the per-beam LBT failure counter for the group is incremented only when all Tx beams in the group experience an LBT failure.

[0149] In some embodiments, the LBT process is performed using a first receive Rx beam corresponding to a first Tx beam of a configured set, the method further including using a second Rx beam for downlink reception, wherein the first Rx beam is different from the second Rx beam. In some embodiments, the first Rx beam is selected based on the SRI included in the uplink license for uplink transmission.

[0150] In some embodiments, declaring an LBT failure for uplink transmission includes the UE's physical layer entity sending an LBT failure indication to the UE's MAC entity, wherein the MAC entity increments the LBT failure counter.

[0151] The embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects as illustrative rather than restrictive. Therefore, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All variations within the equivalent meaning and scope of the claims should be included within their scope.

Claims

1. A method for assembling a user equipment (UE), comprising: For the set of configurations of the transmit Tx beam corresponding to the uplink transmission, perform the Listen-Before-Speak (LBT) process; In response to determining that the LBT process for all Tx beams in the configured set has failed, an LBT failure for the uplink transmission is declared. as well as In response to an LBT failure for the uplink transmission, the LBT failure counter is incremented. The method further includes tracking each beam LBT failure for each Tx beam in the configured set.

2. The method according to claim 1, wherein, Executing the LBT process for the set of Tx beam configurations includes executing multiple LBT processes concurrently.

3. The method according to claim 1, wherein, Performing the LBT process for the set of Tx beam configurations includes sequentially executing multiple LBT processes.

4. The method of claim 1, further comprising, in response to a first per-beam LBT failure counter associated with the first Tx beam exceeding a threshold, performing autonomous deactivation of the first Tx beam of the configured set.

5. The method of claim 4, further comprising: In response to deactivating the first Tx beam, the second Tx beam is activated; and The second Tx beam is used to perform the random access procedure.

6. The method according to claim 4, wherein, The uplink transmission corresponds to the configured license.

7. The method of claim 1, further comprising reporting LBT failure statistics to a radio access network (RAN) node, the LBT failure statistics including LBT failures for each beam of a set of configurations for the Tx beam.

8. The method of claim 1, further comprising: At least one group of Tx beams is formed, wherein all Tx beams in the group have the same quasi-colocation relationship; Track the per-beam LBT failure counter for each group. The LBT failure counter for each beam in a group is incremented only when all Tx beams in the group experience an LBT failure.

9. The method according to claim 1, wherein, The LBT process is performed using a first receive Rx beam corresponding to a first Tx beam of the configured set, the method further comprising using a second Rx beam for downlink reception, wherein the first Rx beam is different from the second Rx beam.

10. The method according to claim 9, wherein, The first Rx beam is selected based on the Probe Reference Signal Resource Indicator (SRI) included in the uplink license for the uplink transmission.

11. The method according to claim 1, wherein, The statement regarding LBT failure in the uplink transmission includes the UE's physical layer entity sending an LBT failure indication to the UE's MAC entity, wherein the MAC entity increments the LBT failure counter.

12. A user equipment (UE), comprising: Memory; as well as A processor, coupled to the memory, and configured to cause the UE to: For the set of UE transmit Tx panel configurations corresponding to uplink transmissions, perform the Listen-Before-Speak (LBT) procedure. In response to determining that the LBT process for all UE Tx panels in the set of configurations has failed, an LBT failure for the uplink transmission is declared. and In response to an LBT failure for the uplink transmission, the LBT failure counter is incremented. For each UE Tx panel in the configured set, track each panel LBT failure.

13. The UE of claim 12, further comprising, in response to a first per-panel LBT failure counter associated with the first UE Tx panel exceeding a threshold, performing autonomous deactivation of the first UE Tx panel of the configured set.

14. The UE of claim 13, further comprising: In response to deactivating the first UE Tx panel, the second UE Tx panel is activated; and The second UE Tx panel is used to perform the random access procedure.

15. The UE of claim 12, further comprising reporting LBT failure statistics to a radio access network (RAN) node, the LBT failure statistics including per-panel LBT failures for a set of configurations for the UE Tx panel.

16. The UE according to claim 12, further comprising: Forming at least one group of UE Tx panels, wherein all UE Tx panels in the group have the same quasi-co-location relationship; Track the per-panel LBT failure counter for each group. The per-panel LBT failure counter for a group is incremented only when all UE Tx panels in the group experience an LBT failure.

17. The UE according to claim 12, wherein, The LBT process is performed using a first UE receive Rx panel corresponding to a first UE Tx panel of the configured set, wherein the processor further uses a second UE Rx panel for downlink reception, wherein the first UE Rx panel is different from the second UE Rx panel.

18. The UE according to claim 17, wherein, The first UE Rx panel is selected based on the Probe Reference Signal Resource Indicator (SRI) included in the uplink license for the uplink transmission.

Images