Apparatus and method for incrementing a transmission counter in response to LBT failure

Abstract

Apparatus, methods, and systems for counter processing in the event of LBT failure are disclosed. An apparatus (1100) includes a transceiver (1125) and a processor (1105) that executes (1305) a Listen-After-Talk (“LBT”) procedure for transmission and detects (1310) an LBT failure in response to transmission. The processor (1105) determines (1315) whether a Media Access Control (“MAC”) entity of the apparatus 1100 is configured with a consistent LBT failure recovery procedure. In response to an indication of LBT failure and in response to the MAC entity not being configured with a consistent LBT failure recovery procedure, the processor (1105) increments (1320) a transmission counter in the absence of uplink transmission.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 013,186, filed April 21, 2020, entitled “RACH / SR COUNTERHANDLING IN CASE OF LBT FAILURE”, by Joachim Loehr, Alexander Johann Maria Golitschek Edler vonElbwart, and Ravi Kuchibhotla, which is incorporated herein by reference. Technical Field

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

[0004] In some wireless communication systems, services are supplemented by operations on unlicensed spectrum. However, operations on unlicensed spectrum require a free channel assessment (“CCA”) prior to transmission, which may involve a Listen-Before-Speak (“LBT”) process.

[0005] In the 3GPP New Radio in unlicensed spectrum (“NR-U”), channel access for both the downlink (“DL”) and uplink (“UL”) depends on CCA (e.g., LBT procedure) to obtain channel access. Before any transmission, the gNB (i.e., the fifth-generation (“5G”) base station) and / or user equipment (“UE”) must first sense the channel to determine if there is ongoing communication on that channel. In Release 16 (“Rel-16”), NR-U’s LBT does not consider beamforming and only assumes omnidirectional LBT. Summary of the Invention

[0006] A procedure for counter handling in the event of LBT failure is disclosed. The procedure can be implemented by an apparatus, system, method, or computer program product.

[0007] A method for a user equipment (“UE”) includes performing a Listen-Before-Talk (“LBT”) procedure for a transmission and detecting an LBT failure for the transmission. A first method includes determining whether the UE’s Media Access Control (“MAC”) entity is configured with a consistent LBT failure recovery procedure. If the UE’s MAC entity is not configured with a consistent LBT failure recovery procedure, the first method includes: in response to an indication of an LBT failure, incrementing a transmission counter in the absence of uplink transmission.

[0008] Another approach for the UE includes performing an LBT procedure for the transmission and detecting LBT failure for the transmission. A second approach includes determining whether consistent LBT failure recovery functionality is supported at the UE. If consistent LBT failure recovery functionality is not supported by the UE, the second approach includes: in response to an LBT failure, indicating LBT success to the UE's MAC entity without performing a corresponding uplink transmission. Attached Figure Description

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

[0010] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system for counter handling in the event of LBT failure;

[0011] Figure 2 This is a block diagram illustrating one embodiment of the 5G New Radio (“NR”) protocol stack;

[0012] Figure 3 This is a diagram illustrating one embodiment of a radio frame in which the LBT process is performed during its duration;

[0013] Figure 4 This is a diagram illustrating one embodiment of the process for handling the RACH counter in the event of an LBT failure;

[0014] Figure 5 This is a diagram illustrating one embodiment of an alternative process for RACH counter handling in the event of LBT failure;

[0015] Figure 6 This is a diagram illustrating one embodiment of another process for handling the RACH counter in the event of LBT failure;

[0016] Figure 7 This is a diagram illustrating one embodiment of an implementation for handling the RACH counter in the event of an LBT failure;

[0017] Figure 8 This is a diagram illustrating one embodiment of the process for handling the SR counter in the event of an LBT failure;

[0018] Figure 9 This is a diagram illustrating one embodiment of an alternative process for handling the SR counter in the event of LBT failure;

[0019] Figure 10 This is a diagram illustrating one embodiment of another process for handling the SR counter in the event of LBT failure;

[0020] Figure 11 This is a diagram illustrating one embodiment of a user equipment device that can be used for counter processing in the event of an LBT failure;

[0021] Figure 12 This is a diagram illustrating one embodiment of a network device that can be used for counter processing in the event of LBT failure;

[0022] Figure 13 This is a flowchart illustrating an embodiment of a first method for counter processing in the event of LBT failure; and

[0023] Figure 14 This is a flowchart illustrating an embodiment of a second method for counter processing in the event of LBT failure. Detailed Implementation

[0024] As those skilled in the art will understand, aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Therefore, embodiments can take the form of a completely hardware embodiment, a completely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining aspects of both software and hardware.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0040] Generally, this disclosure describes systems, methods, and apparatus for counter processing in the event of a Listen-Before-Speak (“LBT”) failure. In NR-U, channel access in both the downlink and uplink relies on LBT; however, in Rel-16, the LBT in NR-U does not consider beamforming and assumes only omnidirectional LBT. The UE's MAC layer entity detects consistent UL LBT failures by receiving UL LBT failure notifications from the physical layer. The NR-U LBT process for channel access can be summarized as follows:

[0041] A) Both gNB-initiated Channel Occupancy Time (“COT”) and UE-initiated COT use Category 4 (“Cat-4”) LBT, where the start of a new transmission burst always executes an LBT with exponential backoff. Exceptions are made only when the duration of the DRS must be at most one ms and not multiplexed with a unicast PDSCH. As used herein, a Cat-4 LBT procedure refers to an LBT with random backoff and a variable-size contention window.

[0042] B) UL transmissions within the channel occupancy time (“COT”) initiated by the gNB, or subsequent DL transmissions within the COT initiated by the UE or gNB, may be transmitted immediately without sensing only if the interval from the end of the previous transmission is no greater than 16 μs. Otherwise, Category 2 (“Cat-2”) LBTs must be used, and the interval cannot exceed 25 μs. As used herein, a Cat-2 LBT procedure refers to an LBT without random backoff.

[0043] According to 3GPP TS 38.321, as long as the selected corresponding SSB or CSI-RS remains unchanged and no LBT failure has occurred in the previous transmission, the transmission counter PREAMBLE_POWER_RAMPING_COUNTER will be incremented each time a new PRACH preamble is transmitted. This last part ensures that power ramping is not applied due to LBT failure.

[0044] The first problem addressed by this disclosure concerns how to handle the RACH counter when a consistent LBT failure occurs. According to the currently specified behavior, the RACH counter PREAMBLE_TRANSMISSION_COUNTER will be stuck at the same value. To resolve this deadlock situation, a consistent LBT detection and recovery procedure is introduced. However, LBT failure detection and recovery is an optional UE capability / feature. Therefore, when the UE does not support this mechanism or the network is not configured with a consistent LBT failure detection and recovery procedure, there will be no recovery in the event of a failed RACH consistency attempt; that is, the UE will not inform the RRC layer about the RACH problem and trigger an RLF because the counter never reaches the configured maximum value preambleTransMax.

[0045] The second problem addressed by this disclosure concerns the transmission of scheduling requests (“SR”) on the Physical Uplink Control Channel (“PUCCH”). In the event of a consistent LBT failure, no higher layer (e.g., the RRC layer) is informed of the link problem and no random access procedure is triggered because the SR counter is not incremented, and therefore sr-TransMax is not exceeded.

[0046] To address the aforementioned issues with current technologies, the following UE behaviors can be implemented.

[0047] UE behavior regarding RACH counter handling depends on UE capabilities and whether the network has configured a consistent LBT failure recovery procedure for the UE. When the UE does not support LBT detection and recovery functionality, or when the UE is not configured with a consistent LBT failure recovery procedure, the UE will increment the RACH counter (e.g., PREAMBLE_TRANSMISSION_COUNTER) if a preamble is not transmitted due to an LBT failure. However, if the UE does support a consistent LBT failure recovery procedure and the UEMAC layer entity is configured with a consistent LBT failure recovery procedure through the network, the UE will not increment the RACH counter (e.g., PREAMBLE_TRANSMISSION_COUNTER) if a preamble is not transmitted due to an LBT failure.

[0048] The UE behavior regarding SR counter handling depends on the UE's capabilities and whether the network has configured a consistent LBT failure recovery procedure for the UE. When the UE does not support LBT detection and recovery functionality, or when the UE is not configured with a consistent LBT failure recovery procedure, the UE will increment the SR transmission counter (e.g., SR_COUNTER) if a preamble is not transmitted due to an LBT failure. If the UE does support a consistent LBT failure recovery procedure and the UE / MAC is configured with a consistent LBT failure recovery procedure via the network, the UE will not increment SR_COUNTER if a preamble is not transmitted due to an LBT failure.

[0049] In some embodiments, the UE's PHY layer indicates to the MAC layer that the LBT was successful, even when the UE does not use a consistent LBT failure recovery procedure or when random access preamble transmission cannot be performed due to LBT failure.

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

[0051] In one implementation, RAN 120 conforms to the 5G system specified in the 3GPP specification. For example, RAN 120 may be an NG-RAN that implements the NR RAT and / or LTE RAT. In another example, RAN 120 may include a non-3GPP RAT (e.g., Or an IEEE 802.11 series compliant WLAN. In another implementation, RAN 120 conforms to the LTE system as specified in the 3GPP specification. However, more generally, the wireless communication system 100 can implement other open or proprietary communication networks, such as Global Microwave Access Interoperability (“WiMAX”) or the IEEE 802.16 series standards, as well as other networks. This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0052] In one embodiment, remote unit 105 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart TVs (e.g., internet-connected TVs), smart appliances (e.g., internet-connected appliances), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), etc. In some embodiments, remote unit 105 includes wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, remote unit 105 may be referred to as UE, subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user terminal, wireless transmit / receive unit (“WTRU”), device, or other terms used in the art. In various embodiments, remote unit 105 includes a subscriber identity and / or identification module (“SIM”) and a mobile device (“ME”) that provides mobile terminal functions (e.g., radio transmission, conversion, voice encoding and decoding, error detection and correction, signaling and access to the SIM). In some embodiments, the remote unit 105 may include a terminal device (“TE”) and / or be embedded in an appliance or device (e.g., a computing device as described above).

[0053] Remote unit 105 can communicate directly with one or more base station units 121 in RAN 120 via uplink (“UL”) and downlink (“DL”) communication signals. Additionally, UL and DL communication signals can be carried on wireless communication link 123. Here, RAN 120 is an intermediate network providing remote unit 105 with access to mobile core network 140. As described in more detail below, remote unit 105 can send directed RACH and / or SR transmissions 125 to base station unit 121.

[0054] In some embodiments, remote unit 105 communicates with application server 151 via a network connection to mobile core network 140. For example, application 107 in remote unit 105 (e.g., a web browser, media client, telephone, and / or Voice over Internet Protocol (“VoIP”) application) can trigger remote unit 105 to establish a Protocol Data Unit (“PDU”) session (or other data connection) with mobile core network 140 via RAN 120. Mobile core network 140 then uses the PDU session to relay services between remote unit 105 and application server 151 in packet data network 150. The PDU session represents a logical connection between remote unit 105 and user plane function (“UPF”) 141.

[0055] To establish a PDU session (or PDN connection), remote unit 105 must register with mobile core network 140 (also referred to as "attached to mobile core network" in the context of fourth-generation ("4G") systems). Note that remote unit 105 may establish one or more PDU sessions (or other data connections) with mobile core network 140. Therefore, remote unit 105 may have at least one PDU session for communicating with packet data network 150. Remote unit 105 may establish additional PDU sessions for communicating with other data networks and / or other communication peers.

[0056] 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 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 embodiments, a one-to-one mapping may exist between QoS streams and QoS profiles, such that all packets belonging to a particular QoS stream have the same 5G QoS identifier (“5QI”).

[0057] In 4G / LTE systems, such as Evolved Packet System (“EPS”), a Packet Data Network (“PDN”) connection (also known as an EPS session) provides end-to-end (E2E) connectivity between the remote unit and the PDN. The PDN connectivity process establishes an EPS bearer, i.e., a tunnel between the remote unit 105 and the packet gateway (“PGW”, not shown) in the mobile core network 140. In some embodiments, a one-to-one mapping exists between the EPS bearer and the QoS profile, such that all packets belonging to a particular EPS bearer have the same QoS class identifier (“QCI”).

[0058] Base station unit 121 may be distributed over a geographical area. In some embodiments, base station unit 121 may also be referred to as an access terminal, access point, base station, base station, node B (“NB”), evolved Node B (abbreviated as eNodeB or “eNB”, also known as Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) node B), 5G / NR node B (“gNB”), home node B, relay node, RAN node, or any other term used in the art. Base station unit 121 is typically part of a RAN such as RAN 120, which may include one or more controllers communicatively coupled to one or more corresponding base station units 121. These and other elements of the radio access network are not shown, but are generally known to those skilled in the art. Base station unit 121 is connected to mobile core network 140 via RAN 120.

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

[0060] In one embodiment, the mobile core network 140 is a 5GC or Evolved Packet Core (“EPC”), which can be coupled to a packet data network 150, such as the Internet and private data networks, as well as other data networks. The remote unit 105 may have a subscription or other account with respect to the mobile core network 140. Each mobile core network 140 belongs to a single PLMN. This disclosure is not intended to limit it to any particular wireless communication system architecture or protocol implementation.

[0061] Mobile core network 140 includes several network functions (“NFs”). As depicted, mobile core network 140 includes at least one UPF 141. Mobile core network 140 also includes multiple control plane (“CP”) functions, including but not limited to Access and Mobility Management Functions (“AMF”) 143, Session Management Functions (“SMF”) 145, Policy Control Functions (“PCF”) 147, and Unified Data Management Functions (“UDM”) serving RAN 120. In some embodiments, the UDM is quasi-co-located with a User Data Repository (“UDR”), which is described as a combined entity “UDM / UDR” 149. In various embodiments, mobile core network 140 may also include an Authentication Server Function (“AUSF”), a Network Repository Function (“NRF”) (used by various NFs to discover and communicate with each other via an Application Programming Interface (“API”), or other NFs defined for 5GC. In some embodiments, mobile core network 140 may include an Authentication, Authorization, and Accounting (“AAA”) server.

[0062] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a "network slice" refers to a portion of the mobile core network 140 optimized for a specific service type or communication service. A network instance may be identified by a single network slice selection aid information ("S-NSSAI"), while the set of network slices authorized for use by the remote unit 105 is identified by network slice selection aid information ("NSSAI"). Here, "NSSAI" refers to a vector value including one or more S-NSSAI values. In some embodiments, various network slices may include separate instances of network functions, such as SMF 145 and UPF 141. In some embodiments, different network slices may share some common network functions, such as AMF 143. For illustration purposes, Figure 1 Different network slices are not shown, but their support is assumed.

[0063] Despite Figure 1A specific number and type of network functions are described, but those skilled in the art will recognize that any number and type of network functions can be included in the mobile core network 140. Furthermore, in which the mobile core network 140 is an LTE variant of the EPC, the described network functions can be replaced by appropriate EPC entities, such as the Mobility Management Entity (“MME”), Serving Gateway (“SGW”), PGW, Home Subscriber Server (“HSS”), etc. For example, AMF 143 can be mapped to the MME, SMF 145 can be mapped to the control plane portion of the PGW and / or mapped to the MME, UPF 141 can be mapped to the SGW and the user plane portion of the PGW, UDM / UDR 149 can be mapped to the HSS, etc.

[0064] Although Figure 1 The components of the 5G RAN and 5G core network are described, but the described embodiments for counter handling in the event of LBT failure are applicable to other types of communication networks and RATs, including IEEE 802.11 variants, Global System for Mobile Communications (“GSM”, i.e., 2G digital cellular networks), General Packet Radio Service (“GPRS”), General Mobile Telecommunications System (“UMTS”), LTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfox, and others.

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

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

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

[0068] Physical layer 220 provides a transport channel to MAC sublayer 225. As described herein, physical layer 220 can perform CCA / LBT procedures using an energy detection threshold. In some embodiments, physical layer 220 can send a notification of UL LBT failure to the MAC entity at MAC sublayer 225. MAC sublayer 225 provides a logical channel to RLC sublayer 230. RLC sublayer 230 provides an RLC channel to PDCP sublayer 235. PDCP sublayer 235 provides radio bearers to SDAP sublayer 240 and / or RRC layer 245. SDAP sublayer 240 provides QoS flows to the core network (e.g., 5GC). RRC layer 245 provides the addition, modification, and release of carrier aggregation and / or dual connectivity. RRC layer 245 also manages the establishment, configuration, maintenance, and release of signaling radio bearers (“SRBs”) and data radio bearers (“DRBs”).

[0069] NAS layer 250 is located between UE 205 and 5GC 515. NAS messages are transparently transmitted through the RAN. NAS layer 250 is used to manage the establishment of communication sessions and to maintain continuous communication with UE 205 when UE 205 moves between different cells in the RAN. Conversely, AS layer is located between UE 205 and the RAN (i.e., RAN node 210) and carries information through the radio portion of the network.

[0070] The UE can use various transport counters, including the RACH transport counter and the SR transport counter. An example of a RACH transport counter is `PREAMBLE_TRANSMISSION_COUNTER`, which starts at 1 (during the first PRACH transmission) and increments by 1 each time a PRACH is retransmitted. As defined in 3GPP TS 38.321, `PREAMBLE_TRANSMISSION_COUNTER` is used to detect and declare RACH failures. `PREAMBLE_TRANSMISSION_COUNTER` is incremented when no RA response is received within the ra-ResponseWindow duration. When the counter reaches its configured maximum value (preambleTransMax+1), a random access failure is declared, and an RLF (on the MCG) or SCG failure occurs.

[0071] Since the ra-ResponseWindow only starts with the actual msg1 or msgA transmission, it is not started when these transmissions fail due to LBT failure. Therefore, when a consistent LBT failure occurs, PREAMBLE_TRANSMISSION_COUNTER will be stuck at the same value. When RAN2 agrees on PREAMBLE_TRANSMISSION_COUNTER, it is assumed that the consistent UL LBT failure detection and recovery mechanism will take effect and break the deadlock caused by the stuck counter.

[0072] An example of an SR transmission counter is SR_COUNTER, which also starts at 1 (on the first SR transmission) and is incremented by 1 each time an SR is retransmitted. SR_COUNTER can be used to detect and declare SR failures, for example, when the maximum number of SR transmissions (i.e., sr-TransMax) has been reached.

[0073] The aforementioned issues / issues can be addressed by mandating that remote unit 105 support a consistent LBT failure recovery procedure. It should also be noted that the consistent LBT failure recovery procedure is designed to be more efficient than the traditional RLF procedure, which may be prematurely triggered when relying on a traditional procedure not optimized for NR-U / LBT. However, even mandatory support / capability may not be sufficient, as the network also needs to support and configure it. Therefore, the following solution describes counter handling for considering the UE's ability to support a consistent LBT failure recovery procedure in the event of an LBT failure.

[0074] Figure 3 The LBT process 300 for a radio frame 305 for unlicensed communication according to an embodiment of the present disclosure is described. When the communication channel is a wide-bandwidth unlicensed carrier 310 (e.g., several hundred megahertz), the CCA / LBT process depends on the energy levels on multiple subbands 315 of the detected communication channel, such as... Figure 3 As shown in the diagram. LBT parameters (such as type / duration, idle channel assessment parameters, etc.) can be configured by RAN node 210 in UE 205. In one embodiment, the LBT procedure is performed at PHY layer 220.

[0075] When performing omnidirectional LBT, the entity (i.e., UE 205 or RAN node) can use an omnidirectional sensing beam. Alternatively, the entity can perform directional LBT simultaneously using multiple beams (i.e., corresponding to multiple device panels) to simulate omnidirectional sensing. When performing directional LBT, the entity (i.e., UE or RAN node) performs LBT for a given beam (i.e., corresponding to a given spatial direction). Note that each directional beam can correspond to one or more device panels.

[0076] Figure 3 The frame structure of radio frame 305 for unlicensed communication between UE 205 and RAN node 210 is also depicted. Radio frame 305 can be divided into subframes (indicated by subframe boundary 320) and can be further divided into time slots (indicated by time slot boundary 325). Radio frame 305 uses a flexible arrangement in which uplink and downlink operation are on the same frequency channel but are separated in time. However, subframes are not configured as downlink subframes or uplink subframes, and specific subframes can be used by either UE 205 or RAN node 210. As previously discussed, LBT is performed before transmission. In the event of a misalignment between LBT and time slot boundary 325, a reservation signal 330 can be transmitted to reserve (i.e., occupy) the channel until the time slot boundary is reached and data transmission begins.

[0077] Figure 4A process 400 for RACH counter processing in the event of an LBT failure is depicted according to an embodiment of the first solution. Process 400 is performed by a UE, such as UE 205, operating in a mobile communication network. According to the first solution, the UE behavior regarding RACH counter processing, such as PREAMBLE_TRANSMISSION_COUNTER, depends on the UE capability, i.e., whether UE 205 supports the LBT failure detection and recovery process.

[0078] For UE 205 that does not support LBT detection and recovery functionality—that is, the UE capability indicates that it does not support this functionality—if the preamble is not transmitted due to LBT failure, i.e., in the case where the PHY layer 220 indicates LBT failure for PRACH preamble transmission, UE 205 increments PREAMBLE_TRANSMISSION_COUNTER.

[0079] If UE 205 does support LBT detection and recovery procedures, and the preamble is not transmitted due to LBT failure, then UE 205 does not increment PREAMBLE_TRANSMISSION_COUNTER.

[0080] As depicted, process 400 begins when UE 205 detects that a PRACH preamble has not been transmitted due to an LBT failure (see box 405). UE 205 determines whether it supports LBT detection and recovery (i.e., has the capability for LBT detection and recovery) (see decision box 410). If so, UE 205 does not increment the RACH counter (i.e., PREAMBLE_TRANSMISSION_COUNTER) when a preamble is not transmitted due to an LBT failure (see box 415). Otherwise, if UE 205 does not support LBT detection and recovery (i.e., also referred to as a consistent LBT failure recovery process), UE 205 increments the RACH counter when a preamble is not transmitted due to an LBT failure (see box 420).

[0081] Figure 5 A procedure 500 for RACH counter processing in the event of an LBT failure is described according to an embodiment of the second solution. Procedure 500 is performed by a UE, such as UE 205, operating in a mobile communication network. According to the second solution, the UE behavior regarding RACH counter processing depends on whether UE 205 has been configured with a consistent LBT failure recovery procedure, for example, whether the parameter lbt-FailureRecoveryConfig is configured.

[0082] If the MAC entity of UE 205 is not configured with a consistent LBT failure recovery procedure via RRC, and if the preamble is not transmitted due to LBT failure, i.e., if the PHY layer 220 indicates an LBT failure for the PRACH preamble transmission, UE 205 increments PREAMBLE_TRANSMISSION_COUNTER.

[0083] If the UE / MAC is configured with a consistent LBT failure recovery procedure through the network, and the preamble is not transmitted due to LBT failure, then UE 205 does not increment PREAMBLE_TRANSMISSION_COUNTER.

[0084] As depicted, process 500 begins when UE 205 detects that a PRACH preamble has not been transmitted due to an LBT failure (see box 505). UE 205 determines whether the MAC entity is configured with a consistent LBT failure recovery procedure (see decision box 510). If the MAC entity is configured with a consistent LBT failure recovery procedure (e.g., the parameter lbt-FailureRecoveryConfig is configured), then UE 205 does not increment the RACH counter (i.e., PREAMBLE_TRANSMISSION_COUNTER) when a preamble is not transmitted due to an LBT failure (see box 515). Otherwise, if the MAC entity is not configured with a consistent LBT failure recovery procedure, then UE 205 increments the RACH counter when a preamble is not transmitted due to an LBT failure (see box 520).

[0085] Figure 6 A process 600 for RACH counter processing in the event of an LBT failure is depicted according to an embodiment of the third solution. Process 600 is performed by a UE, such as UE 205, operating in a mobile communication network. According to the second solution, the UE behavior regarding RACH counter processing depends not only on the UE capabilities for LBT detection and recovery, but also on whether UE 205 has been configured with a consistent LBT failure recovery process, for example, whether the parameter lbt-FailureRecoveryConfig is configured.

[0086] If UE 205 does not support LBT detection and recovery functionality (i.e., also known as a consistent LBT failure recovery procedure) or the MAC entity is not configured with a consistent LBT failure recovery procedure via RRC, and if the preamble is not transmitted due to LBT failure, i.e., if the PHY layer 220 indicates an LBT failure for the PRACH preamble transmission, UE 205 increments PREAMBLE_TRANSMISSION_COUNTER.

[0087] If UE 205 does support a consistent LBT failure recovery procedure and the UE / MAC is configured with a consistent LBT failure recovery procedure via the network, then if the preamble is not transmitted due to an LBT failure, UE 205 will not increment PREAMBLE_TRANSMISSION_COUNTER.

[0088] As depicted, process 600 begins when UE 205 detects that a PRACH preamble has not been transmitted due to an LBT failure (see box 605). UE 205 determines whether it supports LBT detection and recovery (i.e., has the capability for LBT detection and recovery) (see decision box 610). If so, UE 205 determines whether the MAC entity is configured with a consistent LBT failure recovery procedure (see decision box 615). If UE 205 supports both LBT detection and recovery (i.e., also referred to as a consistent LBT failure recovery procedure) and the MAC entity is configured with a consistent LBT failure recovery procedure (e.g., the parameter lbt-FailureRecoveryConfig is configured), then UE 205 does not increment the RACH counter (i.e., PREAMBLE_TRANSMISSION_COUNTER) when a preamble is not transmitted due to an LBT failure (see box 620). Otherwise, if UE 205 does not support LBT detection and recovery—or if the MAC entity is not configured with a consistent LBT failure recovery procedure—UE 205 increments the RACH counter when a preamble is not transmitted due to an LBT failure (see box 625).

[0089] Figure 7 Text 700 illustrates an implementation 705 of the proposed third solution. As depicted, the 3GPP specification relates to random access preamble transmissions (i.e., described in Clause 5.1.3 of 3GPP TS 38.321). According to implementation 705, if PREAMBLE_TRANSMISSION_COUNTER is greater than one and if an LBT failure indication is received from a lower layer for the last PRACH preamble transmission, the UE may increment PREAMBLE_TRANSMISSION_COUNTER by one based on whether the UE supports and / or is configured with a consistent LBT failure recovery procedure.

[0090] Figure 8 A process 800 for SR transmission counter processing in the event of LBT failure is depicted according to an embodiment of the fourth solution. Process 800 is performed by a UE, such as UE 205, operating in a mobile communication network. According to the third solution, the UE behavior regarding SR transmission counter processing (e.g., SR_COUNTER) depends on the UE capability, i.e., whether UE 205 supports the LBT failure detection and recovery process.

[0091] In the case where UE 205 does not support LBT detection and recovery functionality (i.e., UE capability indicates that the functionality is not supported), if SR is not transmitted due to LBT failure (e.g., on PUCCH), that is, in the case where LBT failure is indicated by PHY layer 220 for SR transmission, UE 205 increments the SR transmission counter (e.g., SR_COUNTER).

[0092] If UE 205 does support LBT detection and recovery procedures, and SR is not transmitted due to LBT failure, then UE 205 does not increment the SR transmission counter.

[0093] As depicted, process 800 begins when UE 205 detects that an SR has not been transmitted due to an LBT failure (see box 805). UE 205 determines whether it supports LBT detection and recovery (i.e., has the capability for LBT detection and recovery) (see decision box 810). If so, UE 205 does not increment the SR transmission counter (e.g., SR_COUNTER) when an SR is not transmitted due to an LBT failure (see box 815). Otherwise, if UE 205 does not support LBT detection and recovery (i.e., also referred to as a consistent LBT failure recovery process), UE 205 increments the SR transmission counter when an SR is not transmitted due to an LBT failure (see box 820).

[0094] Figure 9 A procedure 900 for SR transmission counter processing in the event of an LBT failure is described according to an embodiment of the fifth solution. Procedure 900 is performed by a UE, such as UE 205, operating in a mobile communication network. According to the fifth solution, the UE behavior regarding SR_COUNTER processing depends on whether UE 205 has been configured with a consistent LBT failure recovery procedure, i.e., whether lbt-FailureRecoveryConfig is configured.

[0095] If a MAC entity is not configured with a consistent LBT failure recovery procedure via RRC, and an SR is not transmitted due to an LBT failure (e.g., on the PUCCH), i.e., the LBT failure is indicated by the PHY for SR transmission, then UE 205 increments the SR transmission counter (e.g., SR_COUNTER).

[0096] If the UE / MAC is configured with a consistent LBT failure recovery procedure through the network, and the SR is not transmitted due to LBT failure, then UE 205 will not increment SR_COUNTER.

[0097] As depicted, process 900 begins when UE 205 detects that an SR has not been transmitted due to an LBT failure (see box 905). UE 205 determines whether the MAC entity is configured with a consistent LBT failure recovery procedure (see decision box 910). If the MAC entity is configured with a consistent LBT failure recovery procedure (e.g., the parameter lbt-FailureRecoveryConfig is configured), then UE 205 does not increment the SR transmission counter (e.g., SR_COUNTER) when an SR is not transmitted due to an LBT failure (see box 915). Otherwise, if the MAC entity is not configured with a consistent LBT failure recovery procedure, then UE 205 increments the SR transmission counter when an SR is not transmitted due to an LBT failure (see box 920).

[0098] Figure 10 The following describes a process 1000 for SR transmission counter processing in the event of an LBT failure, according to an embodiment of the sixth solution. Process 1000 is performed by a UE, such as UE 205, operating in a mobile communication network. According to the fourth solution, the UE behavior regarding SR_COUNTER processing depends not only on the UE's capabilities but also on whether UE 205 has been configured with a consistent LBT failure recovery procedure, i.e., whether lbt-FailureRecoveryConfig is configured.

[0099] If UE 205 does not support LBT detection and recovery functionality (i.e., also known as a consistent LBT failure recovery procedure) or the MAC entity is not configured with a consistent LBT failure recovery procedure via RRC, then if an SR is not transmitted due to an LBT failure (e.g., on the PUCCH), i.e., the PHY indicates an LBT failure for the SR transmission, then UE 205 increments the SR transmission counter (e.g., SR_COUNTER).

[0100] If UE 205 does support a consistent LBT failure recovery procedure and the UE / MAC is configured with a consistent LBT failure recovery procedure via the network, then if SR is not transmitted due to LBT failure, UE 205 will not increment SR_COUNTER.

[0101] As depicted, process 1000 begins when UE 205 detects that an SR has not been transmitted due to an LBT failure (see box 1005). UE 205 determines whether it supports LBT detection and recovery (i.e., has the capability for LBT detection and recovery) (see decision box 1010). If so, UE 205 determines whether the MAC entity is configured with a consistent LBT failure recovery procedure (see decision box 1015). If UE 205 supports both LBT detection and recovery (i.e., also referred to as a consistent LBT failure recovery procedure) and the MAC entity is configured with a consistent LBT failure recovery procedure (e.g., the parameter lbt-FailureRecoveryConfig is configured), then UE 205 does not increment the SR transmission counter (e.g., SR_COUNTER) when an SR is not transmitted due to an LBT failure (see box 1020). Otherwise, if UE 205 does not support LBT detection and recovery—or if the MAC entity is not configured with a consistent LBT failure recovery procedure—UE 205 increments the SR transmission counter when an SR is not transmitted due to an LBT failure (see box 1025).

[0102] According to the seventh solution, the PHY layer 220 of UE 205 indicates to the MAC layer 225 that LBT was successful when UE 205 does not use the consistent LBT failure recovery procedure. As noted above, UE 205 may not use the consistent LBT failure recovery procedure due to UE capability (i.e., in cases where UE 205 does not support LBT detection and recovery functionality) and / or because the network is not configured with consistent LBT failure recovery functionality (i.e., lbt-FailureRecoveryConfig is not configured).

[0103] In some embodiments, the PHY layer 220 indicates LBT success even when PRACH transmission cannot be performed due to LBT failure. In some embodiments, the PHY layer 220 also indicates LBT success even when SR transmission cannot be performed due to LBT failure.

[0104] Figure 11 User equipment device 1100, which can perform counter processing in the event of LBT failure, is depicted according to embodiments of the present disclosure. In various embodiments, user equipment device 1100 is used to implement one or more of the solutions described above. User equipment device 1100 may be an embodiment of the remote unit 105 and / or UE 205 described above. Furthermore, user equipment device 1100 may include processor 1105, memory 1110, input device 1115, output device 1120, and transceiver 1125.

[0105] In some embodiments, input device 1115 and output device 1120 are combined into a single device, such as a touchscreen. In some embodiments, user equipment device 1100 may not include any input device 1115 and / or output device 1120. In various embodiments, user equipment device 1100 may include one or more of the following: processor 1105, memory 1110, and transceiver 1125, and may not include input device 1115 and / or output device 1120.

[0106] As depicted, transceiver 1125 includes at least one transmitter 1130 and at least one receiver 1135. In some embodiments, transceiver 1125 communicates with one or more cells (or radio coverage areas) supported by one or more base station units 121. In various embodiments, transceiver 1125 may operate on unlicensed spectrum. Furthermore, transceiver 1125 may include multiple UE panels supporting one or more beams. Additionally, transceiver 1125 may support at least one network interface 1140 and / or application interface 1145. One or more application interfaces 1145 may support one or more APIs. One or more network interfaces 1140 may support 3GPP reference points such as Uu, N1, PC5, etc. Other network interfaces 1140 may be supported, as will be understood by those skilled in the art.

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

[0108] In various embodiments, processor 1105 controls user equipment device 1100 to implement the UE behavior described above. In some embodiments, processor 1105 includes an application processor (also referred to as a "main processor") that manages application domain and operating system ("OS") functions and a baseband processor (also referred to as a "baseband radio processor") that manages radio functions.

[0109] In various embodiments, processor 1105 controls user equipment device 1100 to implement the UE behavior described above. For example, processor 1105 performs a Listen-Before-Speak (“LBT”) procedure for a transmission and detects LBT failure for a transmission.

[0110] In some embodiments, the processor 1105 determines whether the Media Access Control (“MAC”) entity of the user equipment device 1100 is configured with a consistent LBT failure recovery procedure. If the MAC entity is not configured with a consistent LBT failure recovery procedure, the processor 1105 increments a transmission counter in response to an LBT failure indication if no uplink transmission is transmitted.

[0111] However, if the MAC entity is configured with a consistent LBT failure recovery procedure, the processor 1105 prevents the transmission counter from incrementing in the absence of uplink transmission in response to an LBT failure indication. In some embodiments, the UE includes a physical layer. In such an embodiment, detecting an LBT failure for transmission may include the physical layer sending an LBT failure indication to the MAC entity.

[0112] In some embodiments, the processor 1105 determines whether consistent LBT failure recovery functionality is supported at the user equipment device 1100. If the UE does not support consistent LBT failure recovery functionality, the processor 1105 increments the preamble transmission counter in response to an LBT failure indication without transmitting uplink data. However, if the user equipment device 1100 supports consistent LBT failure recovery functionality and the AMC entity is configured with a consistent LBT failure recovery procedure, the processor 1105 prevents the transmission counter from incrementing in response to an LBT failure without transmitting uplink data.

[0113] In some embodiments, the transmission may be a RACH preamble transmission. In such embodiments, the transmission counter may be a preamble transmission counter. In some embodiments, the transmission may be an SR transmission. In such embodiments, the transmission counter may be an SR transmission counter.

[0114] In some embodiments, the processor 1105 determines whether consistent LBT failure recovery functionality is supported at the user equipment device 1100. If the user equipment device 1100 does not support consistent LBT failure recovery functionality, the processor 1105, in response to an LBT failure, indicates LBT success to the MAC entity of the user equipment device 1100 without performing the corresponding uplink transmission.

[0115] In some embodiments, consistent LBT failure recovery functionality is determined not to be supported in response to the MAC entity not being configured with a consistent LBT failure recovery procedure. In some embodiments, the transport may be a RACH preamble transport. In other embodiments, the transport may be an SR transport.

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

[0117] In some embodiments, memory 1110 stores data related to counter processing in the event of LBT failure. For example, memory 1110 may store various parameters, panel / beam configurations, resource assignments, strategies, etc., as described above. In some embodiments, memory 1110 also stores program code and related data, such as an operating system or other controller algorithms operating on device 1100.

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

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

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

[0121] Transceiver 1125 communicates with one or more network functions of a mobile communication network via one or more access networks. Transceiver 1125 operates under the control of processor 1105 to transmit and receive messages, data, and other signals. For example, processor 1105 may selectively activate transceiver 1125 (or a portion thereof) at specific times to send and receive messages.

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

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

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

[0125] Figure 12 A network device 1200, which can be used for counter processing in the event of LBT failure, is depicted according to embodiments of the present disclosure. In one embodiment, the network device 1200 may be an implementation of a RAN node, such as base station unit 121, RAN node 212, or gNB as described above. Furthermore, the base station network device 1200 may include a processor 1205, a memory 1210, an input device 1215, an output device 1220, and a transceiver 1225.

[0126] In some embodiments, input device 1215 and output device 1220 are combined into a single device, such as a touchscreen. In some embodiments, network device 1200 may not include any input device 1215 and / or output device 1220. In various embodiments, network device 1200 may include one or more of the following: processor 1205, memory 1210, and transceiver 1225, and may not include input device 1215 and / or output device 1220.

[0127] As depicted, transceiver 1225 includes at least one transmitter 1230 and at least one receiver 1235. Here, transceiver 1225 communicates with one or more remote units 125. Additionally, transceiver 1225 may support at least one network interface 1240 and / or application interface 1245. The application interface(s) 1245 may support one or more APIs. The network interface(s) 1240 may support 3GPP reference points such as Uu, N1, N2, and N3. Other network interfaces 1240 may be supported, as will be understood by those skilled in the art.

[0128] In one embodiment, processor 1205 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 1205 may be a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or similar programmable controller. In some embodiments, processor 1205 executes instructions stored in memory 1210 to perform the methods and routines described herein. Processor 1205 is communicatively coupled to memory 1210, input device 1215, output device 1220, and transceiver 1225.

[0129] In various embodiments, network device 1200 is a RAN node (e.g., gNB) communicating with one or more UEs, as described herein. In such embodiments, processor 1205 controls network device 1200 to perform the RAN behaviors described above. When operating as a RAN node, processor 1205 may include an application processor (also referred to as the "main processor") that manages application domain and operating system ("OS") functions and a baseband processor (also referred to as the "baseband radio processor") that manages radio functions.

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

[0131] In some embodiments, memory 1210 stores data related to counter processing in the event of LBT failure. For example, memory 1210 may store parameters, configurations, resource assignments, policies, etc., as described above. In some embodiments, memory 1210 also stores program code and related data, such as an operating system or other controller algorithms operating on device 1200.

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

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

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

[0135] Transceiver 1225 includes at least a transmitter 1230 and at least one receiver 1235. As described herein, one or more transmitters 1230 can be used to communicate with a UE. Similarly, as described herein, one or more receivers 1235 can be used to communicate with network functions in a PLMN and / or RAN. Although only one transmitter 1230 and one receiver 1235 are illustrated, network device 1200 can have any suitable number of transmitters 1230 and receivers 1235. Furthermore, the transmitter(s) 1230 and receiver(s) 1235 can be of any suitable type.

[0136] Transceiver 1225 can operate on unlicensed spectrum, and includes multiple gNB panels. As used herein, "gNB panel" refers to a logical entity that can be mapped to a physical gNB antenna. Depending on the implementation, a "gNB panel" can have the operational function of an antenna group element to independently control its Tx beam.

[0137] Figure 13 One embodiment of a method 1300 for counter processing in the event of LBT failure, according to embodiments of the present disclosure, is described. In various embodiments, method 1300 is performed by a user equipment device in a mobile communication network, such as remote unit 105, UE 205, and / or user equipment device 1100 as described above. In some embodiments, method 1300 is performed by a processor, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0138] Method 1300 begins and performs the LBT procedure 1305 for the transmission. Method 1300 includes detecting an LBT failure 1310 for the transmission. Method 1300 includes determining 1315 whether the UE's MAC entity is configured with a consistent LBT failure recovery procedure. If the UE's MAC entity is not configured with a consistent LBT failure recovery procedure, the first method includes: in response to an LBT failure indication, incrementing a transmission counter 1320 in the absence of uplink transmission. Method 1300 ends.

[0139] Figure 14 An embodiment of a method 1400 for counter processing in the event of LBT failure, according to embodiments of the present disclosure, is described. In various embodiments, method 1400 is performed by a user equipment device in a mobile communication network, such as remote unit 105, UE 205, and / or user equipment device 1100 as described above. In some embodiments, method 1400 is performed by a processor, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0140] Method 1400 begins and performs the LBT procedure 1405 for the transmission. Method 1400 includes detecting an LBT failure 1410 for the transmission. Method 1400 includes determining 1415 whether consistent LBT failure recovery functionality is supported at the UE. If the UE does not support consistent LBT failure recovery functionality, then method 1400 includes: in response to the LBT failure, indicating LBT success 1420 to the UE's MAC entity without performing a corresponding uplink transmission. Method 1400 ends.

[0141] This document discloses a first apparatus for counter processing in the event of an LBT failure, according to embodiments of the present disclosure. The first apparatus may be executed by a user equipment apparatus such as remote unit 105, UE 205, and / or user equipment apparatus 1100 in a mobile communication network. The first apparatus includes a processor and a receiver for operation utilizing a shared spectrum channel access. The processor performs a Listen-Before-Talk (“LBT”) procedure for a transmission and detects an LBT failure for a transmission. The processor determines whether the UE’s MAC entity is configured with a consistent LBT failure recovery procedure. If the UE’s MAC entity is not configured with a consistent LBT failure recovery procedure, the first method includes: incrementing a transmission counter in the absence of uplink transmission, in response to an indication of an LBT failure.

[0142] However, if the UE's MAC entity is configured with a consistent LBT failure recovery procedure, the processor prevents the transmission counter from incrementing in the absence of uplink transmissions in response to an LBT failure indication. In some embodiments, the UE includes a physical layer. In such an embodiment, detecting an LBT failure for transmission may include the physical layer sending an LBT failure indication to the MAC entity.

[0143] In some embodiments, the processor determines whether consistent LBT failure recovery functionality is supported at the UE. If the UE does not support consistent LBT failure recovery functionality, the processor increments the preamble transmission counter in response to an LBT failure indication without transmitting uplink data. However, if the UE supports consistent LBT failure recovery functionality and if the AMC entity is configured with a consistent LBT failure recovery procedure, the processor prevents incrementing the transmission counter in response to an LBT failure without transmitting uplink data.

[0144] In some embodiments, the transmission may be a RACH preamble transmission. In such embodiments, the transmission counter may be a preamble transmission counter. In some embodiments, the transmission may be an SR transmission. In such embodiments, the transmission counter may be an SR transmission counter.

[0145] According to embodiments of this disclosure, a first method for counter processing in the event of an LBT failure is disclosed herein. The first method can be performed by a user equipment device in a mobile communication network, such as remote unit 105, UE 205, and / or user equipment device 1100. The first method includes performing an LBT procedure for a transmission and detecting an LBT failure for the transmission. The first method includes determining whether the UE's MAC entity is configured with a consistent LBT failure recovery procedure. If the UE's MAC entity is not configured with a consistent LBT failure recovery procedure, the first method includes: incrementing a transmission counter in the absence of uplink transmission, in response to an indication of an LBT failure.

[0146] However, if the UE's MAC entity is configured with a consistent LBT failure recovery procedure, the first method includes: preventing the incrementing transmission counter in the absence of uplink transmission in response to an LBT failure indication. In some embodiments, the UE includes a physical layer. In such an embodiment, detecting an LBT failure for transmission may include the physical layer sending an LBT failure indication to the MAC entity.

[0147] In some embodiments, the first method includes determining whether consistent LBT failure recovery functionality is supported at the UE. If the UE does not support consistent LBT failure recovery functionality, the first method includes incrementing a preamble transmission counter in the absence of uplink transmission in response to an indication of LBT failure. However, if the UE supports consistent LBT failure recovery functionality and if a consistent LBT failure recovery procedure is configured for the MAC entity, the first method includes preventing the transmission counter from incrementing in the absence of uplink transmission in response to an LBT failure.

[0148] In some embodiments, the transmission may be a RACH preamble transmission. In such embodiments, the transmission counter may be a preamble transmission counter. In some embodiments, the transmission may be an SR transmission. In such embodiments, the transmission counter may be an SR transmission counter.

[0149] This document discloses a second apparatus for performing counter processing in the event of an LBT failure, according to embodiments of the present disclosure. The second apparatus may be implemented by a user equipment apparatus in a mobile communication network, such as remote unit 105, UE 205, and / or user equipment apparatus 1100 as described above. The second apparatus includes a processor and a transceiver for operating via shared spectrum channel access. The processor performs an LBT procedure on a transmission (e.g., on the shared spectrum) and detects an LBT failure for a transmission opportunity. The processor determines whether consistent LBT failure recovery functionality is supported at the UE. If consistent LBT failure recovery functionality is not supported at the UE, the processor, in response to the LBT failure, indicates LBT success to the UE's MAC entity without performing a corresponding uplink transmission.

[0150] In some embodiments, in response to the MAC entity not being configured with a consistent LBT failure recovery procedure, it is determined that consistent LBT failure recovery functionality is not supported. In some embodiments, the transport may be a RACH preamble transport. In other embodiments, the transport may be an SR transport.

[0151] According to embodiments of this disclosure, a second method for counter processing in the event of an LBT failure is disclosed. The second method can be performed by a user equipment device in a mobile communication network, such as remote unit 105, UE 205, and / or user equipment device 1100. The second method includes performing an LBT procedure for a transmission and detecting an LBT failure for the transmission. The second method includes determining whether consistent LBT failure recovery functionality is supported at the UE. If the UE does not support consistent LBT failure recovery functionality, the second method includes: in response to an LBT failure, indicating LBT success to the UE's MAC entity without performing a corresponding uplink transmission.

[0152] In some embodiments, it is determined that the consistent LBT failure recovery functionality does not support the occurrence of a MAC entity not being configured with a consistent LBT failure recovery procedure. In some embodiments, the transport may be a RACH preamble transport. In other embodiments, the transport may be an SR transport.

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

Claims

1. A method for a user equipment (UE) device, the method comprising: The Listen-Before-Speak (LBT) process is executed for transmission. The LBT transmission detection failed. Determine whether the UE's Media Access Control (MAC) entity is configured with a consistent LBT failure recovery procedure; as well as In response to the LBT failure indication and in response to the fact that the UE's MAC entity is not configured with the consistent LBT failure recovery procedure, the transmission counter is incremented in the absence of uplink transmission.

2. The method according to claim 1, further comprising: In response to the LBT failure indication and in response to the UE's MAC entity being configured with the consistent LBT failure recovery procedure, the increment of the transmission counter is prevented in the absence of uplink transmission.

3. The method according to claim 1, further comprising: Before determining whether the MAC entity of the UE is configured with a consistent LBT failure recovery procedure, determine whether consistent LBT failure recovery functionality is supported at the UE. In response to the indication of LBT failure and in response to the UE not supporting the consistent LBT failure recovery functionality, the transmission counter is incremented in the absence of uplink transmission; as well as In response to the UE supporting the consistent LBT failure recovery functionality, a determination is made as to whether the UE's MAC entity is configured with a consistent LBT failure recovery procedure.

4. The method of claim 3, further comprising: In response to the LBT failure and in response to the UE supporting the consistent LBT failure recovery functionality and further in response to the UE's MAC entity being configured with the consistent LBT failure recovery procedure, the increment of the transmission counter is prevented in the absence of uplink transmission.

5. The method according to claim 1, wherein, The transmission includes a random access channel (RACH) preamble transmission, and the transmission counter includes a preamble transmission counter.

6. The method according to claim 1, wherein, The transmission includes a schedule request (SR) transmission, and the transmission counter includes an SR transmission counter.

7. The method according to claim 1, wherein, The UE includes a physical layer, wherein the transmission detection LBT failure includes the physical layer sending an LBT failure indication to the MAC entity.

8. A method for a user equipment (UE) device, the method comprising: The Listen-Before-Speak (LBT) process is executed for transmission. The LBT transmission detection failed. Determine whether consistent LBT failure recovery functionality is supported at the UE; as well as In response to the LBT failure and in response to the UE not supporting the consistent LBT failure recovery functionality, the LBT success is indicated to the UE's Media Access Control (MAC) entity without performing the corresponding uplink transmission.

9. The method according to claim 8, wherein, Since the MAC entity of the UE is not configured with a consistent LBT failure recovery procedure, it is determined that consistent LBT failure recovery functionality is not supported.

10. The method according to claim 8, wherein, The transmission includes one of the random access channel (RACH) preamble transmission and the scheduling request (SR) transmission.

11. A user equipment (UE) apparatus, comprising: A transceiver, the transceiver being used for operation via shared spectrum channel access; and Processor, the processor: The Listen-Before-Speak (LBT) process is executed for transmission. The LBT transmission detection failed. Determine whether the Media Access Control (MAC) entity of the device is configured with a consistent LBT failure recovery procedure; and In response to the indication of LBT failure and in response to the fact that the MAC entity is not configured with the consistent LBT failure recovery procedure, the transmission counter is incremented if no uplink transmission is transmitted.

12. The apparatus according to claim 11, wherein, The processor, in response to the LBT failure indication and in response to the MAC entity being configured with the consistent LBT failure recovery procedure, prevents the transmission counter from incrementing in the absence of uplink transmission.

13. The apparatus according to claim 11, wherein, The processor further: Before determining whether the MAC entity of the device is configured with a consistent LBT failure recovery procedure, determine whether consistent LBT failure recovery functionality is supported at the device. and In response to the indication of LBT failure and in response to the device not supporting the consistent LBT failure recovery functionality, the transmission counter is incremented in the absence of uplink transmission; as well as In response to the device supporting the consistent LBT failure recovery functionality, a determination is made as to whether the MAC entity of the device is configured with a consistent LBT failure recovery procedure.

14. The apparatus according to claim 13, wherein, The processor, in response to the LBT failure and in response to the device supporting the consistent LBT failure recovery functionality and further in response to the MAC entity being configured with the consistent LBT failure recovery process, prevents the transmission counter from incrementing in the absence of uplink transmission.

15. The apparatus of claim 11, wherein the transmission includes a random access channel (RACH) preamble transmission, and wherein, The transmission counter includes a preamble transmission counter.

16. The apparatus according to claim 11, wherein, The transmission includes a schedule request (SR) transmission, and the transmission counter includes an SR transmission counter.

17. The apparatus according to claim 11, wherein, The device includes a physical layer, wherein detecting a transmission LBT failure includes the physical layer sending an LBT failure indication to the MAC entity.

18. A user equipment (UE) apparatus, comprising: A transceiver, the transceiver being used for operation via shared spectrum channel access; as well as Processor, the processor: The Listen-Before-Speak (LBT) process is executed for transmission. The LBT transmission detection failed. Determine whether consistent LBT failure recovery functionality is supported at the device. and In response to the LBT failure and in response to the device not supporting the consistent LBT failure recovery functionality, the LBT success is indicated to the media access control (MAC) entity of the device without performing the corresponding uplink transmission.

19. The apparatus according to claim 18, wherein, Since the MAC entity is not configured with a consistent LBT failure recovery procedure, it is determined that consistent LBT failure recovery functionality is not supported.

20. The apparatus according to claim 18, wherein, The transmission includes one of the random access channel (RACH) preamble transmission and the scheduling request (SR) transmission.

Images