BEAM SWITCHING AFTER EXECUTING LISTEN-BEFORE-SPEAKING

Abstract

Apparatus, methods, and systems for beam switching after the LBT procedure are disclosed. An apparatus (500) includes a processor (505) and a transceiver (525) operating in the unauthorized spectrum, wherein the transceiver (525) supports a plurality of device panels. The processor (505) executes (805) a first Listen-Before-You-Talk ("LBT") procedure using omnidirectional detection to acquire a first Channel Occupancy Time ("COT") and executes (810) a first uplink transmission of a first transport block ("TB") during the first COT and using a first device panel in response to a successful LBT. Here, the first uplink transmission uses a first portion of the first COT. The processor (505) executes (815) a directional LBT procedure so that a second device panel acquires a remaining portion of the first COT.

Description

BEAM SWITCHING AFTER EXECUTING LISTEN-BEFORE-SPEAKING CROSS REFERENCE TO RELATED APPLICATIONS This application claims priority to United States Provisional Patent Application Number 62 / 987,284 entitled “DIRECTIONAL LISTEN-BEFORE-TALK PROCEDURE” and filed on March 9, 2020 for Karthikeyan Ganesan, Ankit Bhamri, and Ali Ramadan Ali, said application being incorporated herein by reference.This application also claims priority to International Patent Application PCT / IB2021 / 050693 entitled “PERFORMING A LISTEN-BEFORE-TALK ON BEAMS AND / OR PANELS” and filed on January 29, 2021 for Ankit Bhamri, Ali Ramadan Ali, Alexander Johann Maria Golitschek Edler von Elbwart, Karthikeyan Ganesan, and Joachim Lóhr, said application claims priority to United States Provisional Patent Application Number 62 / 967,269 entitled “APPARATUSES, METHODS, AND SYSTEMS FOR FAST DIRECTIONAL LBT AT UE IN CONNECTED MODE” and filed on January 29, 2020 for Ankit Bhamri, Ali Ramadan Ali, Alexander Johann Maria Golitschek Edler von Elbwart, Karthikeyan Ganesan, and Joachim Loehr, said applications are incorporated herein by reference. FIELD OF INVENTION The subject matter disclosed herein generally refers to wireless communications and more particularly to directional listen-before-you-talk (“LBT”) procedures, especially for autonomous uplink communications using unauthorized spectrum. BACKGROUND OF THE INVENTION In some wireless communication systems, the service is complemented by operation in unlicensed spectrum. However, operation in unlicensed spectrum requires a Clear Channel Assessment (“CCA”) prior to transmission, for example, involving an LBT procedure. In NR-U, channel access in the downlink and uplink relies on CCA (e.g., LBT procedure) to gain channel access. Before any transmission, the gNB and / or UE must first scan the channel to discover if any communications are in progress. No beamforming is considered for LBT in NR-U in Rei. 16, and only omnidirectional LBT is assumed. BRIEF DESCRIPTION OF THE INVENTION Procedures for beam switching following the LBT procedure are disclosed. Such procedures may be implemented by devices, systems, methods, or computer program products. A User Equipment (“UE”) device method includes executing a Listen-Before-You-Speak (“LBT”) procedure prior to a first configured grant (“CG”) resource opportunity and executing an uplink (“UL”) transmission from a first transport block (“TB”) during the first opportunity and utilizing a first beam in response to a successful LBT. The method includes initiating a timer in response to the UL transmission, determining that a UL transmission failure has occurred if no Hybrid Automatic Repeat Request (“HARQ”) Acknowledgment (“ACK”) feedback is received within the timer's duration, and switching to a second beam for subsequent UL transmission from the first TB in response to determining that a UL transmission failure has occurred. Another method of a UE involves executing a first LBT procedure using omnidirectional detection to acquire a first Channel Occupancy Time (COT) and executing a first UL transmission of a first TB during the first COT and using a first beam in response to successful LBT, where the first UL transmission uses a first portion of the first COT. The second method involves executing a directional LBT procedure so that a second beam acquires a remaining portion of the first COT. BRIEF DESCRIPTION OF THE FIGURES A more specific description of the modalities briefly described above will be provided by reference to specific modalities illustrated in the accompanying drawings. While it is understood that these drawings show only some modalities and therefore will not be considered a limitation of scope, the modalities will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which: FIGURE 1 is a schematic block diagram illustrating one modality of a wireless communication system for beam switching after the LBT procedure; FIGURE 2 is a block diagram illustrating one modality of a 5G New Radio (“NR”) protocol stack; FIGURE 3 is a diagram illustrating a directional LBT mode prior to UL transmission; FIGURE 4 is a diagram that illustrates one mode of a radio frame during which LBT procedure is executed; FIGURE 5 is a diagram illustrating one modality of a user equipment device that can be used for beam switching after the LBT procedure; FIGURE 6 is a diagram illustrating one modality of a network equipment device that can be used for beam switching after the LBT procedure; FIGURE 7 is a flowchart diagram illustrating one modality of a first method for beam switching after the LBT procedure; and FIGURE 8 is a flowchart diagram illustrating one modality of a second method for beam switching after the LBT procedure. DETAILED DESCRIPTION OF THE INVENTION As an expert in the field will appreciate, aspects of modalities can be incorporated as a system, device, method, or program product. Therefore, modalities can take the form of a purely hardware modality, a purely software modality (including firmware, resident software, microcode, etc.), or a modality that combines software and hardware aspects. For example, the disclosed modalities can be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, mass-produced semiconductors such as logic chips, transistors, or other discrete components. The disclosed modalities can also be implemented on programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable matrix logic, programmable logic devices, or similar. As another example, the disclosed modalities can include one or more physical or logical blocks of executable code that can be organized, for example, as an object, procedure, or function. Furthermore, the modes may take the form of a program product embedded in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereafter referred to as code. The storage devices may be tangential, non-transient, and / or non-transmittable. The storage devices may not incorporate signals. In a certain mode, the storage devices use only signals to access a code. Any combination of one or more computer-readable media may be used. The computer-readable medium may be a computer-readable storage medium. The computer-readable storage medium may be a storage device that stores the code. The storage device may be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any convenient combination thereof. More specific examples (a non-exhaustive list) of the storage device Second, computer-readable storage media would include the following: an electrical connection with one or more wires, a laptop floppy disk, a hard disk, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or Flash memory), portable compact disc (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the context of this document, a computer-readable storage medium may be any tangible medium capable of containing or storing a program for use by or in connection with an instruction-executing system, apparatus, or device. Code for performing operations for different modalities can be any number of lines long 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++, or similar, and conventional procedural programming languages ​​such as C, or similar, and / or machine languages ​​such as assembly languages. The code can run 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 the remote computer or server.In this last scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (“LAN”), wireless LAN (“WLAN”), or a wide area network (“WAN”), or the connection can be made to an external computer (e.g., through the Internet using an Internet Service Provider (“ISP”)). Furthermore, the features, structures, or characteristics of the modalities can be combined in any convenient way. The following description provides numerous specific details, such as programming examples, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a comprehensive understanding of the modalities. A person skilled in the art will recognize, however, that the modalities can be practiced without one or more of the specific details, or with other methods, components, materials, and so on. In other cases, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of a modality. Reference in this specification to “a modality,” “the modality,” or similar language means that a particular feature, structure, or characteristic described in connection with the modality is included in at least one modality. Therefore, occurrences of the phrases “in a modality,” “in the modality,” and similar language in this specification may all, but do not necessarily, refer to the same modality, but mean “one or more, but not all, modalities” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including, but not limited to,” unless expressly specified otherwise. An enumerated list of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise.The terms “a,” “one,” and “the” also refer to “one or more” unless expressly specified otherwise. As used here, a list with the conjunction “and / or” includes any single item in the list or any 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 here, a list using the terminology “one or more of” includes any single item in the list or any 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 here, a list using the terminology “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, “an element 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 herein, “an element selected from the group consisting of A, B, and C and combinations thereof” 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. Aspects of the modalities are described below with reference to schematic flowchart diagrams and / or schematic block diagrams of program methods, devices, systems, and products according to the modalities. It is understood that each block in the schematic flowchart diagrams and / or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams 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 the instructions, which are executed through the processor of the computer or other programmable data processing apparatus, create the means to implement the functions / acts specified in the flowchart diagrams and / or block diagrams. The code can also be stored on a storage device that can instruct a computer, other programmable data processing apparatus, or other devices to operate in a particular manner, such that the instructions stored on the storage device produce a manufactured item, including instructions that implement the function / act specified in the flowchart diagrams and / or block diagrams. The code can also be loaded into a computer, other programmable data processing device, or other devices to cause a series of operational steps to be executed on the computer, other programmable device, or other devices to produce a computer-implemented process such that the code running on the computer or other programmable device provides processes to implement the functions / acts specified in the flowchart diagrams and / or block diagrams. The flowcharts and / or block diagrams in the figures illustrate the architecture, functionality, and operation of various implementations of devices, systems, methods, and program products according to different modalities. In this sense, each block in the flowcharts and / or block diagrams can represent a module, segment, or portion of code, which includes one or more executable code instructions to implement the specified logical functions. It should also be noted that, in some alternative implementations, the functions observed in the block may occur out of the order shown in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on the functionality involved. Other steps and methods can be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, in the illustrated figures. Although various arrow and line types can be used in block diagrams and / or flowcharts, it is understood that these do not limit the scope of the corresponding modes. In fact, some arrows or other connectors can be used to indicate only the logical flow of the mode shown. For example, an arrow might indicate a waiting or monitoring period of unspecified duration between enumerated steps of the mode shown. It should also be noted that each block in block diagrams and / or flowcharts, and combinations of blocks in block diagrams and / or flowcharts, can be implemented through systems based on special-purpose hardware that execute the specified functions or actions, or combinations of special-purpose hardware and code. The description of elements in each figure may refer to elements in process figures. Similar numbers refer to similar elements in all figures, including alternate forms of similar elements. This disclosure generally describes systems, methods, and apparatus for beam-switching after the LBT procedure. This disclosure addresses, but is not limited to, the unlicensed-band channel access mechanism for the high-frequency range (specifically FR2 or FR4). More specifically, because beam-based operation is assumed for the unlicensed spectrum in FR2 and beyond, it is crucial to perform listen-before-you-talk (“LBT”) in a specific beam direction rather than omnidirectional LBT. This disclosure describes panel switching during LBT faults on the UE side in connected mode and provides solutions for enabling faster channel access for AUL by switching panel / beam-based LBT faults on the UE in connected mode, also considering interference / LBT faults on the gNB side. Essentially, if an LBT fault exists on the UE in the specific panel / beam direction, how can the UE perform autonomous switching from one panel / beam to another to execute LBT faster? Alternatively, how can parallel LBT be enabled using multiple panels simultaneously for AUL? In NR-U, channel access in both the downlink and uplink is based on LBT; however, no beamforming is considered for LBT in NR-U in Rei. 16, and only omnidirectional LBT is assumed. The NR-U LBT procedures for channel access can be summarized as follows: Both gNB-initiated and UE-initiated COTs use Category 4 LBT (“Cat-4”) where the start of a new transmission burst always executes LBT with exponential backoff. The only exception is when the DRS must be at most 1 ms in duration and is not multiplexed with unicast PDSCH. As used here, a Cat-4 LBT procedure refers to LBT with a random backoff and a variable-size contention window. A UL transmission within a COT initiated by gNB or a subsequent DL transmission within a COT initiated by UE or gNB may be transmitted immediately without detection only if the interval from the end of the previous transmission is no greater than 16 ps; otherwise, Category 2 (“Cat-2”) LBT must be used, and the interval may not exceed 25 ps. As used herein, a Cat-2 LBT procedure refers to LBT without random backtracking. In several configurations, a UE can include multiple antenna panels. An identifier (ID) is supported that can be used at least to indicate panel-specific UL transmission. The ID can be defined considering the possibility of reusing / modifying the Rel-15 specification support or by introducing a new ID. In some configurations, the UE is not required to explicitly disclose its UL antenna panel implementation. In other configurations, the UE's capability signaling can be used for panel-specific UL transmission. A panel identifier (panel ID) that will be used at least to indicate panel-specific UL transmission may include one of the following: 1) an SRS resource set ID; 2) an ID that is 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 that is additionally configured in spatial relationship information. The panel ID (without excluding the reuse of an existing ID) may be used for panel selection-based transmission of PUSCH, PUCCH, and SRS among multiple activated panels. In some configurations, multiple panels are implemented in a single UE, and only one panel can be activated at a time, with a predetermined panel activation / switching delay. In some configurations, multiple panels are implemented in a UE, and multiple panels can be activated simultaneously, with one or more panels being used for transmission. In some configurations, multiple panels are implemented in a UE, and multiple panels can be activated simultaneously, but only one panel can be used for transmission. Note that this does not require a UE to always activate multiple panels simultaneously. Also note that the UE can control panel activation / deactivation. In other modes, a new panel ID can be used, which can be applied implicitly or explicitly to the transmission for a target RS resource or set of resources, for the PUCCH resource, or for the SRS resource. In these modes, panel-specific signaling is executed using the new panel ID either implicitly (for example, through DL beam reporting enhancement) or explicitly. If signaled explicitly, the ID can be configured in the target RS / channel or reference RS (for example, in the DL RS resource configuration or in spatial relationship information). As used here, a “UE panel” refers to a logical entity that can be mapped to the UE’s physical antennas. Under certain conditions, the gNB may assume that the mapping between the UE’s physical antennas and the “UE panel” logical entity will not change when activated for transmission. Depending on the UE’s implementation, a “UE panel” may have at least the following functionality as an operational unit of the antenna group to independently control its Tx beam. A primary issue addressed by this disclosure relates to how to handle Tx UL faults during multi-panel operation with space LBT. The disclosure provides several solutions involving panel switching during LBT faults on the UE side in connected mode and offers solutions for enabling faster channel access for autonomous uplink transmission (“AUL”) by switching beam / panel-based LBT faults on the UE in connected mode, also considering interference / LBT faults on the gNB side. The disclosure provides solutions for enabling the UE to autonomously switch from one panel / beam to another to perform LBT faster in the event of an LBT failure in the UE in the specific panel / beam direction. The disclosure also provides solutions for enabling parallel LBT using multiple panels simultaneously for AUL. A second problem addressed by this disclosure relates to beam / panel switching initiated by the UE during the same Channel Occupancy Time (“COT’j”). The disclosure provides solutions for how to acquire a remnant portion of the COT during multi-panel operation with spatial LBT. Figure 1 shows a beam-switched wireless communication system 100 after the LBT procedure, according to disclosure modalities. In one modality, 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 unit 121 with which the remote unit 105 communicates using wireless communication links 123. Although a specific number of remote units 105, base units 121, wireless communication links 123, RANs 120, and mobile core networks 140 are shown in FIGURE 1, a person skilled in the art will recognize that any number of remote units 105, base units 121, wireless communication links 123, RANs 120, and mobile core networks 140 may be included in the wireless communication system 100. In one implementation, RAN 120 complies with the 5G system specified in the 3GPP specifications. For example, RAN 120 might be an NG-RAN, implementing NR RATs and / or LTE RATs. In another example, RAN 120 might include non-3GPP RATs (for example, Wi-Fi® or WLAN that complies with the 802.11 family of the Institute of Electrical and Electronics Engineers (“IEEE”)). In yet another implementation, RAN 120 complies with the LTE system. MA / a / ZUZZ / UI II or as specified in the 3GPP specifications. More generally, however, the Wireless 100 communication system may implement other proprietary or open communication networks, such as Worldwide Interoperability for Microwave Access (“WiMAX”) or standards from the IEEE 802.16 family, among others. This disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol. In one configuration, remote units 105 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart televisions (e.g., internet-connected televisions), smart appliances (e.g., internet-connected appliances), set-top boxes, game consoles, security systems (including security cameras), vehicle onboard computers, networking devices (e.g., routers, switches, modems), or similar devices. In some configurations, remote units 105 include wearable devices such as smartwatches, fitness trackers, head-mounted optical displays, or similar devices.In addition, remote units 105 may be referred to as UEs, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user terminals, wireless transmit / receive unit (“WTRU”), a device, or by other terminology used in the art. In several embodiments, the remote unit 105 includes a subscriber identity and / or identification module (“SIM”) and mobile equipment (“ME”) providing mobile termination functions (e.g., radio transmission, transfer, language encoding and decoding, error detection and correction, signaling, and SIM access). In some embodiments, the remote unit 105 may include terminal equipment (“TE”) and / or may be incorporated into an apparatus or device (e.g., a computing device, as described above). Remote units 105 can communicate directly with one or more base units 121 in RAN 120 via uplink (“UL”) and downlink (“DL”) communication signals. Additionally, UL and DL communication signals can be carried over wireless communication links 123. Here, RAN 120 acts as an intermediary network, providing remote units 105 with access to the mobile core network 140. As described in more detail below, RAN 120 can send a measurement and reporting configuration 111 to remote unit 105, whereby remote unit 105 sends a measurement report 113 to RAN 120. In some configurations, remote units 105 communicate with an application server 151 via a network connection to the mobile core network 140. For example, an application 107 (e.g., a web browser application, media client, telephone, and / or Voice over Internet Protocol (“VoIP”)) on a remote unit 105 can trigger the remote unit 105 to establish a protocol data unit (“PDU”) session (or other data connection) with the mobile core network 140 via the RAN 120. The mobile core network 140 then relays traffic between the remote unit 105 and the application server 151 over the packet data network 150 using the PDU session. The PDU session represents a logical connection between the remote unit 105 and the User Plane Function (“UPF”) 141. In order to establish a PDU session (or PDN connection), remote unit 105 must register with the mobile core network 140 (also referred to as “joined to the mobile core network” in the context of a Fourth Generation (“4G”) system). Note that remote unit 105 can establish one or more PDU sessions (or other data connections) with the mobile core network 140. Because of this, remote unit 105 can have at least one PDU session to communicate with the packet data network 150. Remote unit 105 can establish additional PDU sessions to communicate with other data networks and / or other communication peers. In the context of a 5G system (“5GS”), the term “PDU Session” refers to a data connection that provides end-to-end (“E2E”) user plane (“UP”) connectivity between the remote unit 105 and a specific Data Network (“DN”) via UPF 141. A PDU Session supports one or more Quality of Service (“QoS”) Streams. In some modes, there may be a one-to-one mapping between a QoS Stream and a QoS profile, such that all packets belonging to a specific QoS Stream have the same 5G QoS Identifier (“5QI”). In the context of a 4G / LTE system, such as the Evolved Packet System (“EPS”), a Packet Data Network (“PDN”) connection (also referred to as an EPS session) provides end-to-end (E2E) connectivity between the remote unit and a PDN. The PDN connectivity procedure establishes an EPS Carrier, i.e., a tunnel between the remote unit and a Packet Gateway (“PGW”, not shown) in the mobile core network. In some modes, there is a one-to-one mapping between an EPS Carrier and a QoS profile, so that all packets belonging to a specific EPS Carrier have the same QoS Class Identifier (“QCI”). Base 121 units can be distributed over a geographic region. In some modalities, a base 121 unit may also be referred to as an access terminal, an access point, a base, a base station, a Node-B (“NB”), an evolved Node-B (abbreviated as eNodeB or “eNB,” also known as an Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) Node-B), a 5G / NR Node-B (“gNB”), or a Node-B of Base units, a relay node, a RAN node, or by any other terminology used in the art. Base units 121 are generally part of a RAN, such as RAN 120, which may include one or more controllers communicatively coupled to one or more corresponding base units 121. These and other elements of the radio access network are not illustrated but are generally well known to those skilled in the art. Base units 121 connect to the mobile core network 140 via RAN 120. Base units 121 can service a number of remote units 105 within a service area, such as a cell or cell sector, via a wireless communication link 123. Base units 121 can communicate directly with one or more of the remote units 105 using communication signals. Typically, base units 121 transmit DL communication signals to service the remote units 105 in the time, frequency, and / or space domains. Additionally, DL communication signals can be carried over wireless communication links 123. Wireless communication links 123 can be any convenient carrier in the licensed or unlicensed radio spectrum. Wireless communication links 123 facilitate communication between one or more remote units 105 and / or one or more base units 121.Note that during NR-U operation, base unit 121 and remote unit 105 communicate over unauthorized radio spectrum. In one configuration, the 140 mobile core network is a 5GC or an Evolved Packet Core (“EPC”), which can be coupled to a packet data network 150, such as the Internet and private data networks, among other data networks. A remote unit 105 can have a subscription or other account with the 140 mobile core network. Each 140 mobile core network belongs to a single PLMN. This disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol. The mobile core network 140 includes several network functions (“NF”). As shown, the mobile core network 140 includes at least one UPF 141. The mobile core network 140 also includes multiple control plane functions (“CP”) including, but not limited to, an Access and Mobility Management Function (“AMF”) 143 that serves the RAN 120, a Session Management Function (“SMF”) 145, a Policy Control Function (“PCF”) 147, and a Unified Data Management Function (“UDM”). In some modalities, the UDM is co-located with a User Data Repository (“UDR”), shown as a combined entity “UDM / UDR” 149. In several modalities, the mobile core network 140 may also include an Authentication Server Function (“AUSF”), a Network Repository Function (“NRF”) (used by the various NFs to discover and communicate with each other over Application Programming Interfaces (“APIs”)), or other NFs defined for the 5GC.In some configurations, the 140 mobile core network may include an authentication, authorization and accounting (“AAA”) server. In various configurations, the Mobile Core 140 network supports different types of mobile data connections and different types of network segments, where each mobile data connection uses a specific network segment. Here, a “network segment” refers to a portion of the Mobile Core 140 network optimized for a certain type of traffic or communication service. A network instance can be identified by a unique Network Segment Selection Assistance Information (“S-NSSAI”), while a set of network segments that the Remote Unit 105 is authorized to use is identified by the Network Segment Selection Assistance Information (“NSSAI”). Here, “NSSAI” refers to a vector value including one or more S-NSSAI values. In some configurations, the various network segments may include separate instances of network functions, such as SMF 145 and UPF 141.In some configurations, different network segments may share some common network functions, such as AMF 143. The different network segments are not shown in FIGURE 1 for ease of illustration, but their support is assumed. Although specific numbers and types of network functions are shown in FIGURE 1, a person skilled in the art will recognize that any number and type of network functions can be included in the 140 mobile core network. Furthermore, in an LTE variant where the 140 mobile core network is an EPC, the network functions shown can be replaced with appropriate EPC entities, such as a Mobility Management Entity (“MME”), a Service Gateway (“SGW”), a PGW, a Home Subscriber Server (“HSS”), and the like. For example, AMF 143 can be mapped to an MME, SMF 145 can be mapped to a control plane portion of a PGW and / or an MME, UPF 141 can be mapped to an SGW and a user plane portion of the PGW, UDM / UDR 149 can be mapped to an HSS, and so on. Although FIGURE 1 shows components of a 5G RAN and a 5G core network, the modes described for beam switching after the LBT procedure apply to other types of communication networks and RATs, including variants of IEEE 802.11, Global System for Mobile Communications (“GSM”, i.e., a 2G digital cellular network), General Packet Radio Service (“GPRS”), Universal Mobile Telecommunications System (“UMTS”, LTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfox, and the like. The Remote Unit 105 is configured with multiple UE panels either during initial access or in connected mode using SRI. As used here, a “UE panel” refers to a logical entity that can be mapped to physical UE antennas. Under certain conditions, the gNB may assume that it will not change the mapping between physical UE antennas and the logical entity “UE panel enabled for transmission.” Depending on the Remote Unit 105 implementation, a “UE panel” may have at least the functionality of an antenna group unit to independently control its Tx beam. According to a first solution, the remote unit 105 handles the Tx UL fault by switching to a different panel / beam and using the same configured granting resources. According to a second solution, the remote unit 105 handles the Tx UL fault by switching to a different panel / beam, where the different panels / beams have different granting resources configured. According to a third solution, the remote unit 105 handles the Tx UL fault by running LBT on multiple panels / beams and selecting only one panel / beam for UL transmission. Here, the multiple panels / beams use the same configured granting resources. According to a third solution, remote unit 105 handles the Tx UL fault by running LBT on multiple panels / beams and selecting only one panel / beam for UL transmission. In this solution, the multiple panels / beams utilize different configured granting resources. Additionally, remote unit 105 selects multiple panels / beams for UL transmission. According to a second solution, the remote unit 105 handles the Tx UL fault by switching to a different panel / beam, where the different panels / beams have different granting resources configured. In the following descriptions, the term “RAN node” is used for the base station but can be replaced by any other radio access node, such as gNB, eNB, Base Station (“BS”), Access Point (“AP”), etc. Furthermore, the operations are primarily described in the context of 5G NR. However, the proposed solutions / methods are also equally applicable to other mobile communication systems that support measurement reporting on non-public networks. FIGURE 2 shows a stack of NR 200 protocols, according to disclosure modalities. Although FIGURE 2 shows a UE 205, a RAN node 210, and an AMF 215 in a 5G core network (“5GC”), these are representative of a set of remote units 105 that interact with a base unit 121 and a mobile core network 140. As shown, the protocol stack 200 comprises a User Plane protocol stack 220 and a Control Plane protocol stack 225. The User Plane protocol stack 220 includes a physical layer (“PHY”) 230, a Media Access Control (“MAC”) sublayer 235, a Radio Link Control (“RLC”) sublayer 240, a Packet Data Convergence Protocol (“PDCP”) sublayer 245, and a Service Data Adaptation Protocol layer IVIA / a / ZUZZ / UIII UO (“SDAP”) 250. The Control Plane protocol stack 225 includes a physical layer 230, a MAC sublayer 235, an RLC sublayer 240, and a PDCP sublayer 245. The Control Plane protocol stack 225 also includes a Radio Resource Control (“RRC”) layer 255 and a Non-Access Stratum (“NAS”) layer 260. The AS layer (also referred to as the “AS protocol stack”) for the User Plane protocol stack 220 consists of at least the SDAP, PDCP, RLC, and MAC sublayers, and the physical layer. The AS layer for the Control Plane protocol stack 225 consists of at least the RRC, PDCP, RLC, and MAC sublayers, and the physical layer. Layer 2 (“L2”) is divided into the SDAP, PDCP, RLC, and MAC sublayers. Layer 3 (“L3”) includes the RRC sublayer 255 and the NAS layer 260 for the control plane and includes, for example, an Internet Protocol (“IP”) layer or PDU layer (not shown) for the user plane. L1 and L2 are referred to as “lower layers,” while L3 and above (e.g., transport layer, application layer) are referred to as “higher layers.” Physical layer 230 provides transport channels to MAC sublayer 235. Physical layer 230 can execute CCA / LBT procedures as described here. In some modes, physical layer 230 can send an LBT UL failure notification to a MAC entity in MAC sublayer 235. MAC sublayer 235 provides logical channels to RLC sublayer 240. RLC sublayer 240 provides RLC channels to PDCP sublayer 245. PDCP sublayer 245 provides radio carriers to SDAP sublayer 250 and / or RRC layer 255. SDAP sublayer 250 provides QoS flows to the core network (e.g., 5GC). RRC layer 255 allows the addition, modification, and release of Carrier Aggregation and / or Dual Connectivity. The RRC 255 layer also manages the establishment, configuration, maintenance, and release of Signaling Radio Carriers (“SRBs”) and Data Radio Carriers (“DRBs”). The ÑAS 260 layer is located between the UE 205 and the 5GC 215. ÑAS messages are passed transparently across the RAN. The ÑAS 260 layer is used to manage the establishment of communication sessions and maintain continuous communication with the UE 205 as it moves between different cells of the RAN. In contrast, the AS layer, located between the UE 205 and the RAN, carries information about the wireless portion of the network. Figure 3 shows a directional LBT scenario 300, according to the disclosure modalities. Scenario 300 may involve a UE 205, a RAN node 210 to which the UE 205 wishes to send a UL transmission, and an access point (“AP”) 305 that is representative of a potential user of the same communication frequencies as the UE 205 and the 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 unit 121. The UE 205 has generated a UL TB for transmission to the RAN node 210 and, therefore, executes an LBT procedure for a configured set of Tx panels / beams corresponding to the UL transmission. As shown, UE 205 executes an LBT procedure on at least one beam #1 at time 't1', i.e., in preparation for UL transmission using CG resources. Note that the LBT procedure determines whether RAN node 210, AP 305, or another device is using the channel (i.e., radio frequencies) that UE 205 will use for UL transmission. Here, it is assumed that beam #1 is a detection beam corresponding to a first UE panel and that UE 205 supports multiple panels. As shown, LBT is successful in detecting beam #1. Where the LBT procedure involves evaluating multiple beams, it is assumed here that a Tx beam and / or UE panel corresponding to the detection of beam #1 is selected. UE 205 executes a UL transmission on CG resources using Tx Beam #1 and starts a UL fault timer. However, there is an uplink transmission fault, and therefore RAN node 210 either does not receive the UL transmission or cannot decode it. Because the UE does not receive a HARQ-ACK from RAN node 210 before the fault timer expires, the UE determines that the UL transmission failed. As used here, “HARQ-ACK” can collectively represent Positive Acknowledgment (“ACK”) and Negative Acknowledgment (“NACK”). ACK means that a TB is correctly received, while NACK (or NAK) means that a TB is incorrectly received. In response to determining a Tx UL failure for Tx Beam #1, UE 205 switches to a second beam detection panel / UE and executes LBT on at least beam #2 at time 72, i.e., in preparation for UL transmission using a second CG resource allocation. Here, it is assumed that LBT is successful for detection of panel / beam #2. Therefore, UE 205 executes UL transmission on the corresponding Tx panel / beam #2. However, if LBT fails for Rx panel / beam #2, then UE 205 continues executing an LBT procedure for the configured set of Tx panels / beams until LBT is successful or until LBT fails for all configured panels / beams. Figure 4 shows an LBT procedure for a radio frame for unauthorized communication, according to disclosure modalities. When a communication channel is a wideband unauthorized carrier (e.g., several hundred MHz), the CCA / LBT procedure is based on detecting the energy level in multiple sub-bands of the communication channel, as shown in Figure 4. The LBT parameters (such as type / duration, free channel evaluation parameters, etc.) are configured in the UE by the RAN node. In one modality, the LBT procedure is executed at the PHY layer. Figure 4 also shows the frame structure of radio frame 405 for unauthorized communication between UE 205 and RAN node 210. Radio frame 405 can be divided into subframes (indicated by subframe boundaries 420) and further divided into slots (indicated by slot boundaries 425). Radio frame 405 uses flexible arrangements where uplink and downlink operations are on the same frequency channel but are separated in time. However, subframes are not configured as a downlink subframe or an uplink subframe, and a particular subframe can be used by either UE 205 or RAN node 210. As discussed previously, LBT is executed before a transmission. Where LBT does not coincide with a slot boundary 425, a reservation signal 430 can be transmitted to reserve the channel until the slot boundary is reached and data transmission begins. As discussed earlier, according to one initial solution, the UE 205 is configured with the same CG resource for different panels / beams. When the UE 205 executes CCA / LBT on one of the configured detection beams and transmits a TB on one of the configured Tx beams after the LBT's success, the UE 205 initiates (i.e., starts) a timer. The UE 205 detects (i.e., declares) a Tx UL fault if it does not receive HARQ feedback within a specified time, for example, when the timer expires. In one mode, this timer is the CG retransmission timer. In another mode, this timer is a new timer introduced specifically for the purpose of detecting a Tx UL fault. Note that the CG retransmission timer is implicitly associated with decoding failure at the RAN node due to interference, channel failure, or a short LBT transmission from the RAN node. However, in another implementation of the first solution, a new timer—different from the CG retransmission timer—is introduced. This timer may be a specific LBT / CCA timer associated with a certain channel access priority class. Regardless of the implementation, the timer is started after the uplink TB transmission and stopped after receiving the corresponding HARQ feedback. Additionally, the timer's expiration triggers autonomous panel / beam switching, as discussed below. As used here, UE autonomous behavior refers to UE-initiated behavior where the UE executes the behavior in response to an internal trigger and without waiting for (and receiving) instructions from the network (e.g., RAN and / or CN). Therefore, UE 205 autonomously switching to a different panel / beam refers to UE-initiated switching to a different panel / beam, where the UE 205 performs the switching without receiving instructions from the network to switch the panel / beam. Upon detecting (i.e., determining) a Tx UL fault, the UE 205 is permitted to autonomously switch to a different panel / beam to execute CCA / LBT for the (re)transmission of the same TB on the same CG resource. In one mode, the UE 205 autonomously switches to a different detection beam—from among the configured detection beams—to execute CCA / LBT. In another mode, the UE 205 autonomously switches to a different Tx beam—from among the configured Tx beams—to retransmit the TB. In the first solution's configuration, the RAN 210 node (e.g., gNB) reports HARQ feedback using the same spatial filter used for CG transmission. Aperiodic Uplink Control Information (“A-UCI”) indicates the panel / beam ID used by the UE 205 in the CG resource. Here, the UE 205 can select the first panel for LBT-UL transmission from a set of panels / beams configured based on the DL channel signal strength, where the selection can be based on measurements in SSB, CSI-RS, etc. According to the second solution, the UE 205 is configured with a different CG resource for different panels / beams. As in the first solution, the UE 205 runs CCA / LBT for each TX panel / beam and transmits a TB after the LBT succeeds. If the UE 205 does not receive HARQ feedback within a specified time period (i.e., upon expiration of the CG retransmission timer or the new LBT / CCA-specific timer, discussed earlier), then the UE 205 declares a Tx UL failure. Once again, the RAN node 210 reports HARQ feedback using the same spatial filter used for CG transmission. A-UCI indicates the panel / beam ID used by the UE on the CG resource. Upon detecting / declaring a Tx UL fault, UE 205 can autonomously switch to a different panel / beam to execute CCA / LBT for the transmission of the same TB on the different CG resources. However, in the second solution, each CG resource is associated with a TX panel / beam of UE 205. In one mode of the second solution, UE 205 starts the CG retransmission timer after the TB transmission and declares the Tx UL fault upon expiration of the CG retransmission timer. As described earlier, the CG retransmission timer can be used implicitly in association with a decoding failure at the RAN node due to interference, a short channel, or an LBT fault in the RAN node's transmission. In another iteration of the second solution, the UE 205 starts a new timer—different from the CG retransmission timer—after the TB transmission and declares a Tx UL fault upon the CG retransmission timer's expiration. As described earlier, the new timer can be a LBT / CCA-specific timer that may be associated with a certain channel access priority class. Alternatively, the new timer can be a CG-specific timer. Regardless of the implementation, the timer is started after the TB transmission on the uplink and stops after receiving the corresponding HARQ feedback. The timer's expiration triggers autonomous panel / beam switching. According to the second solution, the UE 205 can select the first panel for LBT-UL transmission from the array of panels / beams based on the DL channel signal strength. This selection can be based on measurements taken on SSB, CSI-RS, etc. The UE 205 then selects the CG resource with the same TBS for retransmission. Alternatively, the UE 205 can first select the CG resource with the same TBS and then select the UE panel for UL transmission. The UE 205 can also choose to use the same HARQ process to transmit on a different CG resource, provided the TBS remains the same. According to the third solution, the UE 205 can be configured with the same CG resources for multiple panels / beams. Furthermore, the UE 205 runs LBT on a plurality of panels / beams, where only one panel / beam is selected for UL transmission. The UE 205 executes the first LBT / CCA with one panel / beam and transmits a TB after the successful LBT / CCA procedure. Immediately after the CG retransmission timer (or the new LBT / CCA-specific timer introduced earlier) expires without receiving a HARQ-ACK, the UE 205 executes a second LBT with another set of panels / beams on the same CG resource. In some modes, the second LBT can be executed using multiple panels / beams simultaneously on the same CG resource. After the successful completion of the LBT / CCA procedure, the UE 205 executes UL transmission on the panel / beam based on LBT-ED, where ED is compared for different panels / beams and a panel / beam is selected based on the lowest ED value. In another implementation, the first LBT can be run on one panel / beam and when it fails, then the second LBT can be run on two panels / beams simultaneously from among the configured set of panels / beams and when it fails, then a third LBT can be run on three panels / beams simultaneously from among the configured set of panels / beams, and so on. According to the fourth solution, the UE 205 can be configured with different CG resources for different panels / beams. The UE 205 runs LBT on multiple panels / beams. Furthermore, the UE can select multiple panels / beams for UL transmission on different CG resources. The UE 205 can execute LBT / CCA simultaneously on the configured set of panels / beams, and the same TB is repeated across the different CG resources after the LBT succeeds. Here, CG resources are allocated to each TX panel / beam separately. The RAN node provides HARQ feedback on the same spatial filter used to receive the CG resources. The UE 205 stops retransmitting the initial transmission on all CG resources after receiving at least one HARQ-ACK and also purges the HARQ buffer memory of the entire HARQ process. In one implementation, the HARQ feedback can be transmitted from one or multiple panels of the RAN node after the short LBT. The strategies described above for handling directional LBT and UL failure can be extended to other channels used in the wireless communication system. According to a fifth solution, the UE 205 can perform a RACH preamble transmission using another panel / beam when LBT fails for the first panel / beam. When the UE 205 fails to transmit a RACH preamble from the panel associated with the highest SSB DL signal reception quality due to the LBT failure, the UE 205 can autonomously switch to another panel / beam for the RACH preamble transmission. Here, the UE 205 can choose the panel / beam based on the next best SSB DL signal reception quality. In some modes, the UE 205 does not increment the preamble transmission counter or the preamble increment counters when it autonomously switches to another panel / beam for the RACH preamble transmission. In an alternate implementation, CCA / LBT can be executed simultaneously using multiple panels / beams, and the RACH preamble transmission is executed using only one panel / beam, where the panel / beam is chosen for RACH preamble transmission based on the DL signal strength reception quality. In another implementation, the RACH preamble + MsgA transmission is executed on multiple panels after successful CCA / LBT, where MsgA (i.e., the first message of a 2-step random access procedure) contains the UE identity and the panel / beam ID, and the RAN 210 node can transmit only one RAR based on the RACH preamble reception quality. According to a sixth solution, the UE 205 executes CCA for omnidirectional transmissions and short LBTs for directional transmissions. Here, the UE 205 can execute a "first LBT" for, for example, a CAT-4 LBT as an exponential backoff counter-based access in an omnidirectional manner. This LBT either succeeds or fails (both cases) to acquire the channel or switches to another panel / beam for directional transmission. Then, the UE 205 can execute a "second LBT" using a CAT-2 LBT with a shorter LBT for power detection, either for 25ps or 16ps. The sixth solution is applicable to ML / a / ZUZZ / U 1 II uo data channel, control channel, RACH / SRS transmission. In another implementation of the sixth solution, the second LBT can also be executed simultaneously using a plurality of panels / beams. According to a seventh solution, the Downlink Control Information (“DCI”) for the common group of RAN node 210 (e.g., gNB) indicates a plurality of panels / beams where CCA / LBT is successful as part of the COT DL sharing information. Here, RAN node 210 can indicate in DCI information for a plurality of panels / beams in the “Panel / Beam ID” element, the “CSI-RS configuration” element, the “SSB configuration” element, or in the form of Transmit Configuration Indicator (“TCI”) or QCL-Type D states, where CCA / LBT is successfully executed for the COT sharing initiated at DL. In this case, a COT sharing field in the DCI contains a plurality of COT sharing indicators, each represented by a TCI state or a QCL-Type D ratio with one or more transmission beams configured in a semi-static manner.The UE 205, after receiving this DCI information containing the COT DL Sharing Indicator, can then choose to run CCA / LBT on any of the indicated beams / panels or all of them simultaneously using the shortest LBT (e.g., CAT-2 LBT type) for UL transmission. UL transmission could be performed using one or multiple beams / panels, which could be programmed by the DCI or by the autonomous uplink on the CG resource configured as explained in the previous modes. With reference to the Quasi-Co-Location (“QCL”) assumptions, in some modes the UE 205 is configured with a list of up to M TCI State configurations within the PDSCH-Config upper layer parameter to decode PDSCH according to a detected PDCCH with DCI intended for the UE and cell in service determined, where the value of M depends on the UE's maxNumberConfiguredTCIstatesPerCC capability. Each State-TCI configuration contains parameters to configure a QCL relationship between one or two downlink reference signals and the DM-RS ports of the PDSCH, the DM-RS port of the PDCCH, or the CSI-RS ports of a CSI-RS resource. The QCL relationship is configured by the upper-layer parameter 'qcl-Type1' for the first RS DL, and the upper-layer parameter 'qcl-Type2' for the second RS DL (if configured). For two RS DLs, the QCL types are not the same, regardless of whether the references are to the same RS DL or different RS DLs. The quasi-co-location types corresponding to each RS DL are provided by the upper-layer parameter qcl-Type in QCL-Info and can take one of the following values: • 'QCL-TypeA': {Doppler shift, Doppler dispersion, average delay, delay dispersion} • 'QCL-TypeB': {Doppler shift, Doppler dispersion} • 'QCL-TypeC': {Doppler shift, average delay} • 'QCL-TypeD': {spatial Rx parameter} In some modes, the UE 205 receives an activation command used to map up to eight TCI states to the encoding points of the DCI field 'Transmit Configuration Indication' in a CC / BWP DL or a set of CCs / BWPs DL, respectively. When a set of TCI state IDs is activated for a set of CCs / BWPs DL, where the applicable list of Component Carriers (“CCs”) is determined by the CC specified in the activation command, the same set of TCI state IDs is applied to all BWPs DL in the specified CCs. When a UE 205 supports two TCI states at one encoding point of the DCI field 'Transmit Configuration Indication', the UE 205 can receive an activation command, then the activation command is used to map up to eight combinations of one or two TCI states to the encoding points of the DCI field 'Transmit Configuration Indication'. When the UE 205 is going to transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH that carries the activation command, the indicated mapping between the TCI states and the encoding points of the DCI field 'Transmit Configuration Indication' should be applied starting from the first slot that is after slot n + where μ is the SCS configuration for the PUCCH.If the tci-PresentlnDCI parameter is set to “enabled” or tci-PresentlnDCI-ForFormat1_2 is configured for the Control Resource Set (“CORESET”) by scheduling the PDSCH, and the time offset between the receipt of the DCI DL and the corresponding PDSCH is equal to or greater than timeDurationForQCL if applicable, after a UE 205 receives an initial upper-layer configuration of TCI states and before receiving the activation command, the UE 205 can assume that the DM-RS ports of the PDSCH of an in-service cell are quasi-co-located with the SS / PBCH block determined in the initial access procedure with respect to 'QCL-TypeA', and where applicable, also with respect to 'QCL-TypeD'. If a UE 205 is configured with the upper-layer parameter tci-PresentlnDCI set to 'enabled' for the CORESET programming the PDSCH, the UE 205 assumes that the TCI field is present in the DCI 1_1 format of the PDCCH transmitted on the CORESET. If a UE is configured with the upper-layer parameter tci-PresentlnDCIForFormat1_2 for the CORESET programming the PDSCH, the UE assumes that the TCI field with a DCI field size specified by tci-PresentlnDCI-ForFormat1_2 is present in the DCI 1_2 format of the PDCCH transmitted on the CORESET.If the PDSCH is programmed by a DCI format that does not have a TCI field, and the time offset between the DCI DL reception and the corresponding PDSCH is equal to or greater than a timeDurationForQCL threshold, if applicable, where the threshold is based on the UE's reported ability to determine the quasi-co-location of the PDSCH antenna port, UE 205 assumes that the TCI state or QCL assumption for the PDSCH is identical to the TCI state or QCL assumption, whichever applies, for the CORESET used for PDCCH transmission. If the PDSCH is programmed by a DCI format that includes the TCI field, and the TCI field in the DCI on the programming component carrier points to the TCI states enabled on the programmed component carrier or BWP DL, the UE 205 will use the TCI state according to the value of the 'Transmit Configuration Indication' field in the PDCCH detected with DCI to determine the quasi-co-location of the PDSCH antenna port. The UE 205 can assume that the DM-RS ports of a cell-in-service PDSCH are quasi-co-located with the RS(s) in the TCI state with respect to the QCL type parameters provided by the indicated TCI state if the time offset between the DCI DL reception and the corresponding PDSCH is equal to or greater than a timeDurationForQCL threshold, where the threshold is based on the UE's reported capacity. When the UE 205 is configured with a single-slot PDSCH, the reported TCI state should be based on the TCI states enabled in the slot with the programmed PDSCH. When the UE 205 is configured with a multi-slot PDSCH, the reported TCI state should be based on the TCI states enabled in the first slot with the programmed PDSCH, and the UE 205 will expect the enabled TCI states to be the same across all slots with the programmed PDSCH. Regardless of the tci-PresentlnDCI and tci-PresentlnDCI-ForFormat1_2 settings in connected RRC mode, if all TCI encoding points are mapped to a single TCI state and the offset between DCI DL reception and the corresponding PDSCH is less than the timeDurationForQCL threshold, the UE 205 can assume that the DM-RS ports of a cell in service are quasi-co-located with the RS(s) with respect to the QCL parameters used for quasi-co-location indication of the CORESET PDCCH associated with a monitored search space with the lowest controIResourceSetld in the last slot in which one or more CORESETs within the active BWP of the cell in service are monitored by the UE 205. In this case, if the PDSCH DM-RS 'QCL-TypeD' is different from that of the PDCCH DM-RS with which it is If they overlap in at least one symbol, the UE 205 is expected to prioritize the reception of the PDCCH associated with that CORESET.This also applies to the case of intra-band AC (when the PDSCH and the CORESET are on different component carriers). If none of the TCI states configured for the in-service cell of the programmed PDSCH contains 'QCL-Type D', the UE 205 will obtain the other QCL assumptions from the TCI states specified for its programmed PDSCH without considering the time offset between the DCI DL reception and the corresponding PDSCH. If a UE 205 configured by the PDCCH-Config upper-layer parameter contains two different CORESETPoolIndex values ​​in ControIResourceSet, for both cases, when tci-PresentlnDCI is set to 'enabled' and tci-PresentlnDCI is not configured in connected RRC mode, if the offset between the DCI DL reception and the corresponding PDSCH is less than the timeDurationForQCL threshold,The UE 205 can assume that the PDSCH DM-RS ports associated with a CORESETPoolIndex value of an in-service cell are quasi-co-located with the RS(s) with respect to the QCL parameters used for the quasi-co-location indication of the PDCCH of the CORESET associated with a monitored search space with the lowest ID-CORESET among the CORESETs, which are configured with the same CORESETPoolIndex value as the PDCCH that programs that PDSCH, in the last slot in which one or more CORESETs associated with the same CORESETPoolIndex value as the PDCCH that programs that PDSCH within the active BWP of the in-service cell are monitored by the UE 205. If the offset between the DCI DL reception and the corresponding PDSCH is less than the timeDurationForQCL threshold and at least one TCI state configured for the in-service cell of the programmed PDSCH contains 'QCL-Type D', and at least one TCI coding point indicates two TCI states, the UE 205 can assume that the DM-RS ports of a PDSCH in service are quasi-co-located with the RS(s) with respect to the QCL parameters associated with the TCI states corresponding to the lowest coding point among the TCI coding points containing two different TCI states. For a periodic CSI-RS resource in a zero-power CSI-RS resource set (“NZP-CSI-RS-ResourceSet”) configured with the trs-lnfo top-layer parameter, UE 205 will expect a TCI-State to indicate one of the following quasi-colocation types: 'QCL-TypeC' with an SS / PBCH block and, where applicable, 'QCL-TypeD' with the same SS / PBCH block, or 'QCL-TypeC' with an SS / PBCH block and, where applicable, 'QCL-TypeD' with a II uo CSI-RS resource in an NZP-CSI-RS-ResourceSet configured with upper-layer parameter repetition, or For an aperiodic CSI-RS resource in an NZP-CSI-RS-ResourceSet configured with the trs-lnfo top-layer parameter, UE 205 will expect a TCI-State to indicate 'QCLTypeA' with a periodic CSI-RS resource in an NZP-CSI-RS-ResourceSet configured with the trs-lnfo top-layer parameter and, where applicable, 'QCL-TypeD' with the same periodic CSI-RS resource. For a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured without the trs-lnfo top-layer parameter and without top-layer parameter repetition, UE 205 will expect a TCI-State to indicate one of the following quasi-co-location types: 'QCL-TypeA' with a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured with the trs-lnfo top-layer parameter and, where applicable, 'QCL-TypeD' with the same CSI-RS resource, or 'QCL-TypeA' with a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured with the trs-lnfo top-layer parameter and, where applicable, 'QCL-TypeD' with an SS / PBCH block, or 'QCL-TypeA' with a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured with the trs-lnfo top-layer parameter and, where applicable, 'QCL-TypeD' with a CSIRS resource in an NZP-CSI-RS-ResourceSet configured with the trs-lnfo top-layer parameter and, where applicable, 'QCL-TypeD' with a CSIRS resource in an NZP-CSI-RS-ResourceSet configured with top-layer parameter repetition, or 'QCL-TypeB' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with the top-layer parameter trs-lnfo when 'QCL-TypeD' is not applicable. For a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured with upper-layer parameter repetition, UE 205 will expect a TCI-State to indicate one of the following quasi-co-location types: 'QCL-TypeA' with a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured with the trs-lnfo top-layer parameter and, where applicable, 'QCL-TypeD' with the same CSI-RS resource, or 'QCL-TypeA' with a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured with the trs-lnfo top-layer parameter and, where applicable, 'QCL-TypeD' with a CSIRS resource in an NZP-CSI-RS-ResourceSet configured with top-layer parameter repetition, or 'QCL-TypeC' with an SS / PBCH block and, where applicable, 'QCL-TypeD' with the same SS / PBCH block. For the PDCCH DM-RS, EU 205 will expect a TCI-State to indicate one of the following types of quasi-co-location: 'QCL-TypeA' with a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured with the trs-lnfo top-layer parameter and, where applicable, 'QCL-TypeD' with the same CSI-RS resource, or 'QCL-TypeA' with a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured with the trs-lnfo top-layer parameter and, where applicable, 'QCL-TypeD' with a CSIRS resource in an NZP-CSI-RS-ResourceSet configured with top-layer parameter repetition, or 'QCL-TypeA' with a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured without the trs-lnfo top-layer parameter and without top-layer parameter repetition and, where applicable, 'QCL-TypeD' with the same CSI-RS resource. For the PDSCH DM-RS, EU 205 will expect a TCI-State to indicate one of the following types of quasi-co-location: 'QCL-TypeA' with a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured with the trs-lnfo top-layer parameter and, where applicable, 'QCL-TypeD' with the same CSI-RS resource, or 'QCL-TypeA' with a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured with the trs-lnfo top-layer parameter and, where applicable, 'QCL-TypeD' with a CSIRS resource in an NZP-CSI-RS-ResourceSet configured with repeating top-layer parameter, or 'QCL-TypeA' with a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured without the trs-lnfo top-layer parameter and without top-layer parameter repetition and, where applicable, 'QCL-TypeD' with the same CSI-RS resource. Figure 5 shows a user equipment appliance 500 that can be used for beam switching after the LBT procedure, according to the disclosure modalities. In several modalities, the user equipment appliance 500 is used to implement one or more of the solutions described above. The user equipment appliance 500 can be a modality of the remote unit 105 and / or the UE 205, described above. In addition, the user equipment appliance 500 can include a processor 505, a memory 510, an input device 515, an output device 520, and a transceiver 525. In some embodiments, the input device 515 and the output device 520 are combined into a single device, such as a touchscreen. In some embodiments, the user equipment apparatus 500 may not include an input device 515 and / or an output device 520. In several embodiments, the user equipment apparatus 500 may include one or more of the following: the processor 505, the memory 510, and the transceiver 525, and may not include the device IVIA / a / ZUZZ / UIII UO input 515 and / or output device 520. As shown, the 525 transceiver includes at least one 530 transmitter and at least one 535 receiver. In some modes, the 525 transceiver communicates with one or more cells (or wireless coverage areas) supported by one or more 121 base units. In several modes, the 525 transceiver operates in unlicensed spectrum. Furthermore, the 525 transceiver may include multiple UE panels supporting one or more beams. Additionally, the 525 transceiver may support at least one 540 network interface and / or 545 application interface. The 545 application interfaces may support one or more APIs. The 540 network interfaces may support 3GPP benchmarks, such as Uu, N1, PC5, etc. Other 540 network interfaces may be supported, as understood by a person skilled in the art. The processor 505, in one configuration, can include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 505 can be a microcontroller, a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processing unit, a field-programmable gate array (FPGA), or a similar programmable controller. In some configurations, the processor 505 executes instructions stored in memory 510 to carry out the methods and routines described herein. The processor 505 is communicatively coupled to memory 510, input device 515, output device 520, and transceiver 525.In some configurations, the 505 processor may include an application processor (also known as the "main processor") which manages application domain and operating system ("OS") functions and a baseband processor (also known as the "baseband radio processor") which manages radio functions. In several modes, the 505 processor controls the 500 user equipment appliance to implement the UE behaviors described above. For example, the 505 processor can execute an LBT procedure on a first UE panel before a first CG resource opportunity. The 505 processor executes UL transmission from a first TB during the first opportunity and using the first UE panel in response to a successful LBT. In some modes, the UL transmission during the first opportunity is achieved through uplink control information (“UCI”) that identifies the UE panel used for transmission on the CG resource. Note that although the user equipment appliance is described in terms of executing an LBT procedure for a “set of UE panels,” in other modes LBT can be executed for a “set of beams.”"As used herein, the term 'panel / beam' (or similar notation) indicates that the description applies to a UE panel and / or beam." In some modes, the execution of the LBT procedure comprises performing a free channel evaluation for a plurality of detection UE panels. In such modes, the execution of the first TB UL transmission further comprises transmitting the first TB using at least one additional TX UE panel from the plurality of detection UE panels for which LBT is successful, where each TX UE panel is associated with different CG resources. In some modes, the execution of the first TB UL transmission on the first occasion involves selecting only one of the plurality of UE TX panels and transmitting the first TB using the selected UE TX panel. In some modes, the individual panel from the plurality of UE TX panels is selected based on the lowest energy detection value from the free channel evaluations of the detection UE panel. In such modes, there is a type-D QCL relationship between the plurality of detection UE panels and the plurality of UE TX panels. Processor 505 initiates a timer in response to the UL transmission. In some modes, the timer comprises either a CG retransmission timer or a panel fault timer, which is different from the CG retransmission timer. In some modes, the panel fault timer is associated with a certain channel access priority class. In some modes, the timer value corresponds to a channel access priority class for the UL transmission. In some modes, the 505 processor determines the UL transmission failure because it does not receive HARQ-ACK feedback within the timer's duration. In other modes, the 505 processor receives at least one HARQ-ACK feedback for the first TB and terminates the timer in response to the HARQ-ACK feedback. Here, the 505 processor also purges a HARQ buffer memory associated with the first TB transmission in response to receiving the HARQ-ACK feedback for the first TB. In some modes, the processor also terminates the first TB retransmission in response to receiving at least one HARQ-ACK feedback and purges all HARQ buffer memories associated with the first TB transmission. Processor 505 switches to a second UE panel for subsequent UL transmission from the first TB in response to detecting a UL transmission failure. In some modes, the initial UL transmission is associated with a first HARQ process. In these modes, executing the UL transmission a second time using the second UE panel involves reusing the first HARQ process. In some modes, the UE is configured with multiple detection UE panels. In these modes, the LBT procedure is executed using a first detection UE panel, where switching to the second UE panel involves switching from the first detection UE panel to a second detection UE panel. In some modes, the UE is configured with multiple TX UE panels. In these modes, the UL transmission from a first TB is executed for a first TX UE panel, where switching to the second UE panel involves switching from the first TX UE panel to a second TX UE panel. In some modes, the second UE panel is associated with the same CG resources as the first UE panel. In these modes, the subsequent UL transmission is executed using the same time-frequency resource as the first instance of CG resources. In other modes, each UE TX panel is associated with different CG resources. In these modes, the subsequent UL transmission is executed using a different time-frequency resource than the first instance of CG resources. In some modes, executing the subsequent UL transmission involves selecting a CG resource that has the same TB size as the first instance of CG resources. In several modes, the 500 user equipment device supports time-domain multiplexing (“TDM”) of DL / UL transmissions on different panels / beams within the same COT. Here, the 505 processor can execute LBT (i.e., directional or omnidirectional LBT) at the beginning of the COT. In some modes, the 505 processor executes additional directional LBT with a detection panel / beam covering the next TX panel / beam for each panel / beam switch in the middle of the COT, as described here. Note that when additional directional LBT is executed, the first LBT can cover all TDM panels / beams or only the first TX panel / beam. In other modes, the 505 processor does not execute additional LBT before each panel / beam switch in the middle of the COT where the detection panels / beams for the (first) LBT procedure cover all TDM panels / beams. In several modes, the 505 processor executes a first LBT procedure using omnidirectional detection to acquire a first COT. Through the 525 transceiver, the 505 processor executes a first UL transmission of a first TB during the first COT and uses a first TX panel / beam in response to a successful LBT. Here, the first UL transmission uses a first portion of the first COT (i.e., it does not use the entire first COT). The 505 processor then executes a directional LBT procedure so that a second UE panel acquires the remaining portion of the first COT. In some modes, the 505 processor executes the first LBT procedure using a Category-4 (“Cat-4”) LBT procedure to acquire the first COT (i.e., LBT with random backlash and a variable-size containment window). In these modes, the 505 processor also executes the directional LBT procedure using a Category-2 (“Cat-2”) LBT procedure (i.e., LBT without random backlash). In some modes, the execution of the first LBT procedure involves concurrently executing directional LBT procedures for all configured UE panels. 510 memory, in one configuration, is a computer-readable storage medium. In some configurations, 510 memory includes volatile computer storage media. For example, 510 memory may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some configurations, 510 memory includes non-volatile computer storage media. For example, 510 memory may include a hard disk drive, flash memory, or any other convenient non-volatile computer storage device. In some configurations, 510 memory includes both volatile and non-volatile computer storage media. In some configurations, memory 510 stores data related to beam switching after the LBT procedure. For example, memory 510 can store various parameters, panel / beam configurations, resource allocations, policies, and similar data as described earlier. In some configurations, memory 510 also stores program code and related data, such as the operating system or other driver algorithms that operate on the 500 device. Input Device 515, in one configuration, may include any known computer input device, including a touchpad, button, keyboard, light pen, microphone, or similar device. In some configurations, Input Device 515 may be integrated with Output Device 520, for example, as a touchscreen or similar touch-sensitive display. In some configurations, Input Device 515 includes a touchscreen so that text can be entered using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some configurations, Input Device 515 includes two or more different devices, such as a keyboard and a touchpad. The 520 output device, in one modality, is designed to emit visual, audible, and / or optical signals. In some modalities, the 520 output device includes an electronically controllable display or display device capable of emitting visual data to a user. For example, the 520 output device may include, but is not limited to, an LCD screen, an LED display, an OLED display, a projector, or a similar display device with the ability to emit images, text, or the like to a user. As another non-limiting example, the 520 output device may include a portable display separate from, but communicatively coupled to, the rest of the 500 user equipment apparatus, such as a smartwatch, smart glasses, head-up display, or the like.In addition, the 520 output device can be a component of a smartphone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or similar. In some configurations, the 520 output device includes one or more speakers to produce sound. For example, the 520 output device may produce an audible alert or notification (e.g., a beep or buzzer). In some configurations, the 520 output device includes one or more aptic devices to produce vibrations, movement, or other actuated feedback. In some configurations, all or parts of the 520 output device may be integrated with the 515 input device. For example, the 515 input device and the 520 output device may form a touchscreen or similar touch-sensitive display. In other configurations, the 520 output device may be located near the 515 input device. Transceiver 525 communicates with one or more network functions of a mobile communication network through one or more access networks. Transceiver 525 operates under the control of processor 505 to transmit and receive messages, data, and other signals. For example, processor 505 can selectively activate transceiver 525 (or portions thereof) at specific times to send and receive messages. The 525 transceiver includes at least the 530 transmitter and at least one 535 receiver. One or more 530 transmitters may be used to provide UL communication signals to a 121 base unit, such as the UL transmissions described herein. Similarly, one or more 535 receivers may be used to receive DL communication signals from the 121 base unit, as described herein. Although only one 530 transmitter and one 535 receiver are illustrated, the 500 user equipment apparatus may have any convenient number of 530 transmitters and 535 receivers. Furthermore, the 530 transmitters and 535 receivers may be any convenient type of transmitter and receiver.In one embodiment, the 525 transceiver includes a first transmitter / receiver pair used to communicate with a mobile communication network over authorized radio spectrum and a second transmitter / receiver pair used to communicate with a mobile communication network over unauthorized radio spectrum. IVIA / a / ZUZZ / UIII UO In some configurations, the first transmitter / receiver pair used to communicate with a mobile communication network over licensed radio spectrum and the second transmitter / receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum can be combined into a single transceiver unit, for example, a single chip that performs functions for use with both licensed and unlicensed radio spectrum. In some configurations, the first transmitter / receiver pair and the second transmitter / receiver pair can share one or more hardware components. For example, some 525 transceivers, 530 transmitters, and 535 receivers can be implemented as physically separate components that have access to a shared hardware and / or software resource, such as the 540 network interface. In several configurations, one or more 530 transmitters and / or one or more 535 receivers can be implemented and / or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-a-chip, an ASIO, or another type of hardware component. In some configurations, one or more 530 transmitters and / or one or more 535 receivers can be implemented and / or integrated into a multi-chip module. In some configurations, other components such as the 540 network interface or other hardware components / circuits can be integrated with any number of 530 transmitters and / or 535 receivers onto a single chip. In such configurations, the 530 transmitters and 535 receivers can be logically configured as a 525 transceiver using one or more common control signals or as modular 530 transmitters and 535 receivers implemented on the same hardware chip or on a multi-chip module. Figure 6 shows a network equipment appliance 600 that can be used for beam switching after the LBT procedure, according to the disclosure modalities. In one modality, the network equipment appliance 600 can be an implementation of a RAN node, such as the base unit 121, the RAN node 210, or gNB, described earlier. In addition, the base network equipment appliance 600 can include a processor 605, a memory 610, an input device 615, an output device 620, and a transceiver 625. In some configurations, the 615 input device and the 620 output device are combined into a single device, such as a touchscreen. In some configurations, the 600 network equipment appliance may not include either the 615 input device and / or the 620 output device. In several configurations, the 600 network equipment appliance may include one or more of the 605 processor, the 610 memory, and the 625 transceiver, and may not include the 615 input device and / or the 620 output device. As shown, the transceiver 625 includes at least one transmitter 630 and at least one receiver 635. Here, the transceiver 625 communicates with one or more remote units 105. Additionally, the 625 transceiver can support at least one 640 network interface and / or 645 application interface. 645 application interfaces can support one or more APIs. 640 network interfaces can support 3GPP benchmarks, such as Uu, N1, N2, and N3. Other 640 network interfaces may be supported, as understood by someone skilled in the art. The 605 processor, in one configuration, can include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the 605 processor can be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, or a similar programmable controller. In some configurations, the 605 processor executes instructions stored in memory 610 to perform the methods and routines described herein. The 605 processor is communicatively coupled to memory 610, input device 615, output device 620, and transceiver 625. In several modes, the 600 network equipment appliance is a RAN node (for example, gNB) that sends UE configurations and receives measurement reports, as described here. In these modes, the 605 processor controls the 600 network equipment appliance to perform the behaviors described above. When operating as a RAN node, the 605 processor may include an application processor (also known as the "main processor") that manages application domain and operating system ("OS") functions and a baseband processor (also known as the "baseband radio processor") that manages radio functions. 610 memory, in one configuration, is a computer-readable storage medium. In some configurations, 610 memory includes volatile computer storage media. For example, 610 memory may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some configurations, 610 memory includes non-volatile computer storage media. For example, 610 memory may include a hard disk drive, flash memory, or any other convenient non-volatile computer storage device. In some configurations, 610 memory includes both volatile and non-volatile computer storage media. In some configurations, memory 610 stores data related to beam switching after the LBT procedure. For example, memory 610 can store parameters, configurations, resource allocations, policies, and the like, as described earlier. In some configurations, memory 610 also stores program code and related data, such as an operating system or other driver algorithms that operate on the remote unit 65. Input device 615, in one embodiment, may include a known computer input device, including a touchpad, button, keyboard, light pen, microphone, or similar device. 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 so that text can be entered using a virtual keyboard displayed on the touchscreen and / or by typing on the touchscreen. In some embodiments, input device 615 includes two or more different devices, such as a keyboard and a touchpad. The 620 output device, in one configuration, is designed to output visual, audible, and / or visual signals. In some configurations, the 620 output device includes an electronically controllable display or display device capable of outputting visual data to a user. For example, the 620 output device may include, but is not limited to, an LCD screen, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, or the like to a user. As another non-limiting example, the 620 output device may include a portable display separate from, but communicatively coupled with, the rest of the 600 network equipment apparatus, such as a smartwatch, smart glasses, a head-up display, or the like.In addition, the 620 output device can be a component of a smartphone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or similar. In some embodiments, the output device 620 includes one or more speakers to produce sound. For example, the output device 620 may produce an audible alert or notification (e.g., a beep or buzzer). In some embodiments, the output device 620 includes one or more aptic devices to produce vibration, motion, or other aptic feedback. In some embodiments, all or parts of the output device 620 may be integrated with the input device 615. For example, the input device 615 and the output device 620 may form a touchscreen or similar touch-sensitive display. In other embodiments, the output device 620 may be located near the input device 615. The 625 transceiver includes at least one 630 transmitter and at least one 635 receiver. One or more 630 transmitters can be used to communicate with the UE, as described herein. Similarly, one or more 635 receivers can be used to communicate with network functions in the PLMN and / or RAN, as described herein. Although only one 630 transmitter and one 635 receiver are illustrated, the 600 network equipment apparatus can have any convenient number of 630 transmitters and 635 receivers. Furthermore, the 630 transmitters and 635 receivers can be any convenient type of transmitter and receiver. Figure 7 shows one embodiment of a Method 700 for beam switching after the LBT procedure, according to the embodiments in the disclosure. In several embodiments, Method 700 is executed by a UE, such as the Remote Unit 105, the UE 205, and / or the User Equipment Apparatus 800, described above. In some embodiments, Method 700 is executed by a processor, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, or similar. Method 700 begins and executes 705 a Listen-Before-You-Speak (“LBT”) procedure prior to a first configured grant resource (“CG”) occasion. Method 700 includes executing 710 the uplink (“UL”) transmission of a first transport block (“TB’j”) during the first occasion and using a first beam in response to a successful LBT. Method 700 includes starting 715 a timer in response to the UL transmission. Method 700 includes determining 720 the failure of the UL transmission if no HARQ-ACK feedback is received within the timer's duration. Method 700 includes switching 725 to a second beam for subsequent UL transmission of the first TB in response to determining the failure of the UL transmission. Method 700 terminates. Figure 8 shows one embodiment of a Method 800 for beam switching after the LBT procedure, according to the embodiments in the disclosure. In several embodiments, Method 800 is executed by a UE, such as the Remote Unit 105, the UE 205, and / or the User Equipment Apparatus 800, described above. In some embodiments, Method 800 is executed by a processor, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, or similar. Method 800 begins and executes 805 a first LBT procedure using omnidirectional detection to acquire a first COT. Method 800 includes executing 810 a first UL transmission of a first TB during the first COT and using a first beam in response to successful LBT. Here, the first UL transmission uses only a first portion of the first COT. Method 800 includes executing 815 a directional LBT procedure so that a second beam acquires a remaining portion of the first COT. Method 800 ends. A first apparatus for beam switching after the LBT procedure is disclosed herein, in accordance with the disclosure modalities. The first apparatus may be implemented by a UE, such as the remote unit 105, the UE 205, and / or the user equipment apparatus 800, described above. The first apparatus includes a processor and a transceiver operating in the unauthorized spectrum, where the transceiver supports a plurality of UE panels. The processor executes an LBT procedure on a first UE panel prior to a first CG resource opportunity. The processor executes a UL transmission from a first TB during the first opportunity and utilizes the first UE panel in response to successful LBT, initiating a timer in response to the UL transmission.The processor determines that a UL transmission failure has occurred in response to not receiving any HARQACK feedback within the timer duration and switches to a second UE panel for further UL transmission from the first TB in response to determining that a UL transmission failure has occurred. Note that although the first apparatus is described in terms of executing an LBT procedure and transmission for a set of “UE panels,” in other modes the LBT procedure and transmission may be executed for a set of “beams.” In some modes, the UE is configured with multiple detection UE panels. In these modes, the LBT procedure is executed using a first detection UE panel, where switching to the second UE panel involves switching from the first detection UE panel to a second detection UE panel. In some modes, the UE is configured with multiple TX UE panels. In these modes, the UL transmission from a first TB is executed for a first TX UE panel, where switching to the second UE panel involves switching from the first TX UE panel to a second TX UE panel. In some modes, the second UE panel is associated with the same CG resources as the first UE panel. In these modes, the subsequent UL transmission is executed using the same time-frequency resource as the first instance of CG resources. In other modes, each UE TX panel is associated with different CG resources. In these modes, the subsequent UL transmission is executed using a different time-frequency resource than the first instance of CG resources. In some modes, executing the subsequent UL transmission involves selecting a CG resource that has the same TB size as the first instance of CG resources. In some modes, the timer comprises either a CG retransmission timer or a panel failure timer that differs from the CG retransmission timer. In some modes, the panel failure timer is associated with a specific channel access priority class. In some modes, the UL transmission during the first time is associated with a first HARQ process. In such modes, executing the UL transmission during the second time and using the second UE panel involve reusing the first HARQ process. In some modes, the execution of the LBT procedure includes performing a free-channel evaluation for a plurality of detection UE panels. In these modes, the execution of the first TB UL transmission on the first occasion involves selecting only one of the plurality of TX UE panels and transmitting the first TB using the selected TX UE panel. In some modes, the individual panel from the plurality of TX UE panels is selected based on the lowest energy detection value from the detection UE panel's free-channel evaluations. In these modes, there is a type-D QCL relationship between the plurality of detection UE panels and the plurality of TX UE panels. In some modes, the execution of the LBT procedure includes performing a free channel evaluation for a plurality of detection UE panels. In such modes, the execution of the first TB UL transmission also includes transmitting the first TB using at least one additional TX UE panel from the plurality of detection UE panels for which the LBT is successful, where each TX UE panel is associated with different CG resources. In some modes, the processor also terminates the retransmission of the first TB in response to receiving at least one HARQACK feedback and purges all HARQ buffer memories associated with the transmission of the first TB. In some modes, the first UL transmission is accompanied by a UCI that identifies the UE panel used for transmission in the CG resource. In some modes, the timer value corresponds to a channel access priority class for the UL transmission. In some modes, the processor also terminates the timer upon receiving at least one HARQ-ACK feedback for the first TB and purges a HARQ buffer memory associated with the first TB transmission upon receiving the HARQ-ACK feedback for the first TB. A first method for beam switching after the LBT procedure is disclosed here, in accordance with the disclosure modalities. The first method can be executed by a UE, such as the Remote Unit 105, the UE 205, and / or the User Equipment Apparatus 800, described above. The first method includes receiving a first message containing a first indication of an access mode from a UE, where the UE is connected to a non-public radio cell, and transmitting a second message specifying at least one RAN node measurement configuration to the UE. The first method also includes executing an LBT procedure before a first CG resource opportunity and executing a UL transmission from a first TB during the first opportunity, and using a first beam in response to a successful LBT.The first method involves starting a timer in response to the UL transmission, determining that a UL transmission failure has occurred in response to not receiving any HARQ-ACK feedback within the timer's duration, and switching to a second beam for subsequent UL transmission from the first TB in response to determining that a transmission failure has occurred. UL. Note that although the first method is described in terms of running an LBT procedure and transmission for a set of “beams,” in other modalities the LBT procedure and transmission can be run for a set of “UE panels.” In some modes, the UE is configured with multiple detection beams. In these modes, the LBT procedure is executed using a first detection beam, where switching to the second beam involves switching from the first detection beam to a second detection beam. In some modes, the UE is configured with multiple TX beams. In these modes, the UL transmission from a first TB is executed for a first TX beam, where switching to the second beam involves switching from the first TX beam to a second TX beam. In some modes, the second beam is associated with the same CG resources as the first beam. In these modes, the subsequent UL transmission is executed using the same time-frequency resource as the first instance of CG resources. In other modes, each TX beam is associated with different CG resources. In these modes, the subsequent UL transmission is executed using a different time-frequency resource than the first instance of CG resources. In some modes, executing the subsequent UL transmission involves selecting a CG resource that has the same TB size as the first instance of CG resources. In some modes, the timer comprises either a CG retransmission timer or a beam failure timer that differs from the CG retransmission timer. In some modes, the beam failure timer is associated with a specific channel access priority class. In some modes, the UL transmission during the first time is associated with a first HARQ process. In such modes, executing the UL transmission during the second time and using the second beam involve reusing the first HARQ process. In some modes, the execution of the LBT procedure includes performing a free-channel evaluation for a plurality of detection beams. In these modes, the execution of the first TB UL transmission on the first occasion involves selecting only one of the plurality of TX beams and transmitting the first TB using the selected TX beam. In some modes, the individual beam from the plurality of TX beams is selected based on the lowest detection energy value from the detection beam's free-channel evaluations. In these modes, there is a type-D QCL relationship between the plurality of detection beams and the plurality of TX beams. In some modes, the execution of the LBT procedure includes performing a free channel evaluation for a plurality of detection beams, wherein the execution of the UL transmission of the first TB further includes transmitting the first TB using at least one additional TX beam from the plurality of detection beams for which the LBT is successful, where each TX beam is associated with different CG resources. In some modes, the first method further includes terminating the retransmission of the first TB in response to receiving at least one HARQ-ACK feedback and purging all HARQ buffer memories associated with the transmission of the first TB. In some modes, the first UL transmission is accompanied by the UCI, which identifies the beam used for transmission in the CG resource. In some modes, the timer value corresponds to a channel access priority class for the UL transmission. In some modes, the first method also includes terminating the timer in response to receiving at least one HARQ-ACK feedback for the first TB and purging a HARQ buffer memory associated with the first TB transmission in response to receiving HARQ-ACK feedback for the first TB. A second beam-switching apparatus is disclosed herein, following the LBT procedure, in accordance with the disclosure modalities. The second apparatus may be implemented by a UE, such as the Remote Unit 105, the UE 205, and / or the User Equipment Apparatus 800, described above. The second apparatus includes a processor and a transceiver operating in the unauthorized spectrum, wherein the transceiver supports a plurality of UE panels. The processor executes a first LBT procedure using omnidirectional detection to acquire a first COT and executes a first UL transmission of a first TB during the first COT, using a first UE panel in response to successful LBT. Herein, the first UL transmission uses a first portion of the first COT [i.e., it does not use the entire first COT]. The processor then executes a directional LBT procedure so that a second UE panel acquires a remaining portion of the first COT.Note that although the second device is described in terms of running an LBT procedure and transmission for a set of “UE panels,” in other modes the LBT procedure and transmission can be run for a set of “beams.” In some configurations, the execution of the first LBT procedure involves using a Category-4 (“Cat-4”) LBT procedure to acquire the first COT, where the execution of the directional LBT procedure involves using a Category-2 (“Cat-2”) LBT procedure. In some configurations, the execution of the first LBT procedure involves concurrently executing directional LBT procedures for all configured UE panels. A second method for beam switching after the LBT procedure is disclosed here, in accordance with the disclosure modalities. The second method can be executed by a UE, such as the Remote Unit 105, the UE 205, and / or the User Equipment Apparatus 800, described above. The second method includes executing a first LBT procedure using omnidirectional detection to acquire a first COT and executing a first UL transmission of a first TB during the first COT and using a first beam in response to successful LBT, wherein the first UL transmission uses a first portion of the first COT [i.e., it does not use the entire first COT]. The second method also includes executing a directional LBT procedure so that a second beam acquires a remaining portion of the first COT.Note that although the second method is described in terms of running an LBT procedure and transmission for a set of “beams”, in other modalities the LBT procedure and transmission can be run for the set of “UE panels.” In some modes, the execution of the first LBT procedure involves using a Category-4 (“Cat-4”) LBT procedure to acquire the first COT, where the execution of the directional LBT procedure involves using a Category-2 (“Cat-2”) LBT procedure. In some modes, the execution of the first LBT procedure involves concurrently executing directional LBT procedures for all configured beams. The modalities may be practiced in other specific ways. The modalities described are to be considered in all respects as illustrative only and not restrictive. The scope of the invention is then indicated by the appended claims instead of the foregoing description. All changes arising within the meaning and range of equivalence of the claims shall be encompassed within their scope.

Claims

1. A method on a User Equipment (UE), the method being characterized in that it comprises: executing a Listen-Before-You-Speak (“LBT”) procedure prior to a first configured grant resource occasion (“CG’j”); executing an uplink transmission (“UL”) of a first transport block (“TB”) during the first occasion and utilizing a first beam in response to a successful LBT; initiating a timer in response to the UL transmission; determining the failure of the UL transmission if no HARQ-ACK feedback is received within the duration of the timer; and switching to a second beam for subsequent UL transmission of the first TB in response to determining the failure of the UL transmission.

2. The method according to claim 1, characterized in that the UE is configured with multiple detection beams, wherein the LBT procedure is executed using a first detection beam, and wherein switching to the second beam comprises switching from the first detection beam to a second detection beam.

3. The method according to claim 1, characterized in that the UE is configured with multiple transmission beams (“TX”), wherein the UL transmission of a first TB is executed for a first TX beam, and wherein switching to the second beam comprises switching from the first TX beam to a second TX beam.

4. The method according to claim 1, characterized in that the second beam is associated with the same CG resources as the first beam, wherein the subsequent UL transmission is executed using the same time-frequency resource as the first instance of CG resources.

5. The method according to claim 1, characterized in that each TX beam is associated with different CG resources, wherein the subsequent UL transmission is executed using a different time-frequency resource than the first instance of CG resources.

6. The method according to claim 5, characterized in that the execution of the subsequent UL transmission comprises selecting a CG resource that has the same TB size as the first instance of CG resources.

7. The method according to claim 1, characterized in that the IVIA / a / ZUZZ / UIII UO timer comprises one of: a CG retransmission timer; and a beam failure timer that is different from the CG retransmission timer.

8. The method according to claim 7, characterized in that the beam failure timer is associated with a certain channel access priority class.

9. The method according to claim 1, characterized in that the UL transmission during the first time is associated with a first HARQ process, wherein the execution of the UL transmission during the second time and the use of the second beam comprise the reuse of the first HARQ process.

10. The method according to claim 1, characterized in that the execution of the LBT procedure comprises performing a free channel evaluation for a plurality of detection beams, wherein the execution of the UL transmission of the first TB on the first occasion comprises selecting only one of the plurality of TX beams and transmitting the first TB using the selected TX beam.

11. The method according to claim 10, characterized in that a single one of the plurality of TX beams is selected based on a lower energy detection value from among the free channel evaluations of the detection beam; wherein there is a type-D QCL relationship between the plurality of detection beams and the plurality of TX beams.

12. The method according to claim 1, characterized in that the execution of the LBT procedure comprises performing a free channel evaluation for a plurality of detection beams, wherein the execution of the UL transmission of the first TB further comprises transmitting the first TB using at least one additional TX beam from among the plurality of detection beams for which the LBT is successful, wherein each TX beam is associated with different CG resources.

13. The method according to claim 12, characterized in that it further comprises: terminating the retransmission of the first TB in response to receiving at least one HARQ-ACK feedback; and purging all HARQ buffer memories associated with the transmission of the first TB.

14. The method according to claim 1, characterized in that the UL transmission during the first time is accompanied by the first uplink control information (“UCI”), wherein the UCI identifies the beam used for transmission in the CG resource.

15. The method according to claim 1, characterized in that the timer value corresponds to a channel access priority class for UL transmission.

16. The method according to claim 1, characterized in that it further comprises: terminating the timer in response to receiving at least one HARQ-ACK feedback for the first TB; and purging a HARQ buffer memory associated with the transmission of the first TB in response to receiving the HARQ-ACK feedback for the first TB.

17. A user equipment (“UE”) apparatus characterized in that it comprises: an unlicensed spectrum-operable transceiver, wherein the transceiver comprises a plurality of UE panels; and a processor that: executes a Listen-Before-Speak (“LBT”) procedure on a first UE panel prior to a first configured resource allocation (“CG’j”); executes the uplink (“UL”) transmission of a first transport block (“TB”) during the first allocation and use of the first UE panel in response to a successful LBT; initiates a timer in response to the UL transmission; determines the failure of the UL transmission if no HARQ-ACK feedback is received within the duration of the timer; and switches to a second UE panel for further UL transmission of the first TB in response to determining the failure of the UL transmission.

18. A method for a User Equipment (“UE”), the method characterized in that it comprises: executing a first Listen-Before-You-Talk (“LBT”) procedure using omni-directional detection to acquire a first channel occupancy time (“COT”); executing a first uplink transmission (“UL”) of a first transport block (“TB”) during the first COT and utilizing a first beam in response to a successful LBT, wherein the first UL transmission utilizes a first portion of the first COT (i.e., does not utilize the entirety of the first COT); and executing a directional LBT procedure for a second beam to acquire a remaining portion of the first COT.

19. The method according to claim 18, characterized in that the execution of the first LBT procedure comprises using a category-4 (“cat-4”) LBT procedure to acquire the first COT, wherein the execution of the directional LBT procedure comprises using a category-2 (“cat-2”) LBT procedure. IVIA / a / ZUZZ / UIII UO 20. An apparatus (i.e., UE), characterized in that it comprises: a transceiver operable in the unauthorized spectrum, wherein the transceiver comprises a plurality of UE panels; and a processor that: executes a first Listen-Before-You-Talk (“LBT”) procedure using omnidirectional detection to acquire a first channel occupancy time (“COT”); executes a first uplink (“UL”) transmission of a first transport block (“TB”) during the first COT and utilizes a first UE panel in response to a successful LBT, wherein the first UL transmission utilizes a first portion of the first COT (i.e., does not utilize the entirety of the first COT); and executes a directional LBT procedure for a second UE panel to acquire a remaining portion of the first COT.

Images