Communication channel failure detection and recovery

Abstract

A wireless device can perform a listen-before-talk (LBT) procedure for uplink transmissions. An LBT failure recovery procedure can be initiated based on a failure of one or more LBT procedures. The LBT failure recovery procedure can be suspended and / or cancelled based on one or more conditions, such as receiving a configuration (or reconfiguration) parameter, receiving an indication of a bandwidth part switch, deactivating a cell, and / or receiving a request to set (or reset) a communication layer of the wireless device.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 908,473, filed September 30, 2019, which is incorporated herein by reference in its entirety. Background Technology

[0003] Multiple communication devices use the same communication channel to transmit and / or receive signals. The communication devices determine the availability of the channel used for signal transmission to avoid interfering with communication from other communication devices. Summary of the Invention

[0004] The following overview presents a simplified overview of some features. This overview is not a comprehensive review and is not intended to identify important or key elements.

[0005] Wireless communication can be transmitted and / or received via one or more communication channels. Communication via a communication channel can be initiated based on determining that the communication channel is available and / or unoccupied. For example, if it is determined that the communication channel is occupied and / or unavailable, the wireless device may not transmit signals via that channel. The wireless device may repeat one or more operations (e.g., a listen-before-speak procedure) to determine channel occupancy and / or availability, which may delay signal transmission via the channel. Based on one or more determinations of communication channel occupancy and / or unavailability, the wireless device may initiate a failure recovery procedure (e.g., a listen-before-speak failure recovery procedure). The failure recovery procedure may delay signal transmission by the wireless device. The failure recovery procedure can be aborted and / or canceled based on one or more conditions, which may reduce the delay in signal transmission by the wireless device and / or reduce the likelihood that the wireless device will send and / or receive messages based on incorrect and / or inefficient communication configurations. The various examples described herein enable wireless devices to establish communication via a channel using failure detection and recovery procedures that can provide advantages such as reduced power consumption, reduced interference, and / or reduced latency.

[0006] These and other features and advantages are described in more detail below. Attached Figure Description

[0007] Some features are shown in the accompanying drawings by way of example rather than limitation. In the accompanying drawings, similar numbers indicate similar elements.

[0008] Figure 1A and Figure 1B An exemplary communication network is shown.

[0009] Figure 2A An exemplary user plane is shown.

[0010] Figure 2BAn exemplary control plane configuration is shown.

[0011] Figure 3 An example of a protocol layer is shown.

[0012] Figure 4A An exemplary downlink data flow for user plane configuration is shown.

[0013] Figure 4B An exemplary format of the MAC subheader in a Media Access Control (MAC) Protocol Data Unit (PDU) is shown.

[0014] Figure 5A An exemplary mapping for a downlink channel is shown.

[0015] Figure 5B An exemplary mapping for the uplink channel is shown.

[0016] Figure 6 An exemplary Radio Resource Control (RRC) state and RRC state transitions are shown.

[0017] Figure 7 An exemplary configuration of the frame is shown.

[0018] Figure 8 An exemplary resource configuration for one or more carriers is shown.

[0019] Figure 9 An exemplary configuration of the Bandwidth Component (BWP) is shown.

[0020] Figure 10A An exemplary carrier aggregation configuration based on component carriers is shown.

[0021] Figure 10B An example group of cells is shown.

[0022] Figure 11A An exemplary mapping of one or more Synchronization Signal / Physical Broadcast Channel (SS / PBCH) blocks is shown.

[0023] Figure 11B An exemplary mapping of one or more Channel State Information Reference Signals (CSI-RS) is shown.

[0024] Figure 12A An example of a downlink beam management procedure is shown.

[0025] Figure 12B An example of an uplink beam management procedure is shown.

[0026] Figure 13A An exemplary four-step random access procedure is shown.

[0027] Figure 13B An exemplary two-step random access procedure is shown.

[0028] Figure 13C An exemplary two-step random access procedure is shown.

[0029] Figure 14A An example of CORESET configuration is shown.

[0030] Figure 14B An example of the mapping from control channel elements to resource element groups (CCE to REG) is shown.

[0031] Figure 15A An example of communication between a wireless device and a base station is shown.

[0032] Figure 15B Exemplary elements of a computing device are shown that can be used to implement any of the various devices described herein.

[0033] Figure 16A , Figure 16B , Figure 16C and Figure 16D Examples of uplink and downlink signal transmission are shown.

[0034] Figure 17 An example of a failed detection of Listen-Before-Speak (LBT) is shown.

[0035] Figure 18 An example of LBT failure detection is shown.

[0036] Figure 19 An exemplary communication for failure recovery (e.g., LBT failure recovery) is shown.

[0037] Figure 20 An exemplary method for beam failure recovery and LBT failure recovery is shown.

[0038] Figure 21 The communication used for failure recovery (e.g., LBT failure recovery) is shown.

[0039] Figure 22 Exemplary communications for LBT failure recovery and beam failure recovery are shown.

[0040] Figure 23 Exemplary communications for LBT failure recovery and beam failure recovery are shown.

[0041] Figure 24A and Figure 24B An exemplary data transmission based on LBT failure detection is shown.

[0042] Figure 25An exemplary data transmission based on LBT failure detection is shown.

[0043] Figure 26 An exemplary data transmission based on LBT failure detection is shown.

[0044] Figure 27 An exemplary method for LBT failure detection is shown. Detailed Implementation

[0045] The accompanying drawings and description provide examples. It should be understood that the examples shown and / or described in the drawings are non-exclusive, and the features shown and described can be practiced in other examples. Examples of operation for wireless communication systems are provided, which can be used in the technical field of multi-carrier communication systems. More specifically, the techniques disclosed herein can relate to communication channel failure detection and recovery.

[0046] Figure 1A An exemplary communication network 100 is illustrated. Communication network 100 may include a mobile communication network. Communication network 100 may include, for example, a Public Land Mobile Network (PLMN) operated / managed / run by a network operator. Communication network 100 may include one or more of a core network (CN) 102, a radio access network (RAN) 104, and / or a wireless device 106. Communication network 100 may include one or more data networks (DNs) 108, and / or devices within communication network 100 may communicate with one or more data networks (e.g., via CN 102). Wireless device 106 may communicate with one or more DNs 108, such as a public DN (e.g., the Internet), a private DN, and / or an operator-internal DN. Wireless device 106 may communicate with one or more DNs 108 via RAN 104 and / or via CN 102. CN 102 may provide / configure one or more interfaces to wireless device 106 leading to one or more DNs 108. As part of the interface functionality, CN 102 can establish an end-to-end connection between wireless device 106 and one or more DNs 108, authenticate wireless device 106, provide / configure charging functions, etc.

[0047] Wireless device 106 can communicate with RAN 104 via radio communication through an air interface. RAN 104 can communicate with CN 102 via various communications (e.g., wired and / or wireless communications). Wireless device 106 can establish a connection with CN 102 via RAN 104. RAN 104 can provide / configure, for example, scheduling, radio resource management, and / or retransmission protocols as part of the radio communication. The communication direction from RAN 104 to wireless device 106 via the air interface can be referred to as downlink and / or downlink communication direction. The communication direction from wireless device 106 to RAN 104 via the air interface can be referred to as uplink and / or uplink communication direction. For example, downlink transmissions can be separated and / or distinguished from uplink transmissions based on at least one of the following: frequency division duplex (FDD), time division duplex (TDD), any other duplex scheme, and / or one or more combinations thereof.

[0048] As used throughout, the term "wireless device" can include one or more of the following: mobile device, fixed (e.g., non-mobile) device configured for or usable for wireless communication, computing device, node, device capable of wireless communication, or any other device capable of transmitting and / or receiving signals. As a non-limiting example, a wireless device can include, for example: telephone, mobile phone, Wi-Fi phone, smartphone, tablet, computer, laptop computer, sensor, instrument, wearable device, Internet of Things (IoT) device, hotspot, cellular repeater, vehicle roadside unit (RSU), relay node, automobile, wireless user equipment (e.g., user equipment (UE), user terminal (UT), etc.), access terminal (AT), mobile station, handheld device, wireless transceiver unit (WTRU), wireless communication device, and / or any combination thereof.

[0049] RAN 104 may include one or more base stations (not shown). As used throughout, the term "base station" may include one or more of the following: a base station, a node, a node B (NB), an evolved Node B (eNB), a gNB, an ng-eNB, a relay node (e.g., an Integrated Access and Backhaul (IAB) node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an access point (e.g., a Wi-Fi access point), a transmit and receive point (TRP), a computing device, a device capable of wireless communication, or any other device capable of transmitting and / or receiving signals. A base station may include one or more of each of the elements listed above. For example, a base station may include one or more TRPs. As other non-limiting examples, a base station may include one or more of the following: a Node B (e.g., associated with Universal Mobile Telecommunications System (UMTS) and / or third-generation (3G) standards), an evolved Node B (eNB) (e.g., associated with Evolved Universal Terrestrial Radio Access (E-UTRA) and / or fourth-generation (4G) standards), a Remote Radio Header (RRH), a baseband processing unit coupled to one or more RRHs, a repeater node or relay node for extending the coverage area of ​​a donor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (gNB) (e.g., associated with NR and / or fifth-generation (5G) standards), an Access Point (AP) (e.g., associated with, for example, Wi-Fi or any other suitable wireless communication standard), any other generation base station, and / or any combination thereof. A base station may include one or more devices, such as at least one base station central device (e.g., a gNB central unit (gNB-CU)) and at least one base station distributed device (e.g., a gNB distributed unit (gNB-DU)).

[0050] (For example, in RAN 104) A base station may include one or more antenna sets for wireless communication with wireless device 106, e.g., via an air interface. One or more base stations may include antenna sets (e.g., three antenna sets or any other number of antenna sets) to control multiple cells or sectors individually (e.g., three cells, three sectors, any other number of cells, or any other number of sectors). The size of a cell may be determined by the range within which a receiver (e.g., a base station receiver) can successfully receive transmissions from a transmitter (e.g., a wireless device transmitter) operating within the cell. One or more cells of a base station (e.g., individually or in combination with other cells) may provide / configure radio coverage to wireless device 106 over a wide geographical area to support wireless device mobility. A base station including three sectors (e.g., or n sectors, where n represents any quantity n) may be referred to as a three-sector site (e.g., or an n-sector site) or a three-sector base station (e.g., an n-sector base station).

[0051] One or more base stations (e.g., in RAN 104) can be implemented as sectorized sites with more or fewer than three sectors. One or more base stations in RAN 104 can be implemented as access points, baseband processing units / units coupled to several RRHs, and / or repeaters or relay nodes for extending the coverage area of ​​nodes (e.g., donor nodes). Baseband processing units / units coupled to RRHs can be part of a centralized or cloud RAN architecture, for example, where baseband processing units / units can be centralized in a pool of baseband processing units / units or virtualized. Repeater nodes can amplify and transmit (e.g., transmit, retransmit, rebroadcast, etc.) radio signals received from donor nodes. Relay nodes can perform substantially the same / similar functions as repeater nodes. Relay nodes can decode radio signals received from donor nodes, for example, to remove noise before amplifying and transmitting the radio signals.

[0052] RAN 104 can be deployed as a homogeneous network of base stations (e.g., macrocell base stations) with similar antenna patterns and / or similar high-level transmission power. RAN 104 can also be deployed as a heterogeneous network of base stations (e.g., different base stations with different antenna patterns). In a heterogeneous network, small cell base stations can be used to provide / configure small coverage areas, such as coverage areas overlapping with relatively large coverage areas provided / configured by other base stations (e.g., macrocell base stations). Small coverage areas can be provided / configured in areas with high data traffic (or so-called "hot spots") or in areas with weak macrocell coverage. Examples of small cell base stations, in descending order of coverage area, can include microcell base stations, picocell base stations, and femtocell base stations or femtocell base stations.

[0053] The examples described herein can be used in various types of communications. For example, communications can be based on the 3rd Generation Partnership Project (3GPP) (e.g., one or more network elements similar to a communications network 100), communications based on the Institute of Electrical and Electronics Engineers (IEEE), communications based on the International Telecommunication Union (ITU), communications based on the International Organization for Standardization (ISO), and so on. 3GPP has defined specifications for multiple generations of mobile networks: 3G networks called UMTS, 4G networks called Long Term Evolution (LTE) and LTE Advanced (LTE-A), and 5G networks called 5G Systems (5GS) and NR Systems. 3GPP can define specifications for even more generations of communications networks (e.g., 6G and / or any other generations of communications networks). Examples can be described with reference to a 3GPP 5G network called Next Generation RAN (NG-RAN) or any other communications network, such as one or more elements (e.g., RAN) of a 3GPP network and / or a non-3GPP network. The examples described herein can be applied to other communication networks, such as 3G and / or 4G networks, as well as communication networks that may not yet be finalized / designated (e.g., 3GPP 6G networks), satellite communication networks, and / or any other communication networks. NG-RAN implements and updates 5G radio access technology known as NR, and can be configured to implement 4G radio access technology and / or other radio access technologies, such as other 3GPP and / or non-3GPP radio access technologies.

[0054] Figure 1B An exemplary communication network 150 is illustrated. This communication network may include a mobile communication network. Communication network 150 may include, for example, a PLMN operated / managed / run by a network operator. Communication network 150 may include one or more of the following: CN 152 (e.g., a 5G core network (5G-CN)), RAN 154 (e.g., NG-RAN), and / or radio devices 156A and 156B (collectively, radio devices 156). Communication network 150 may include one or more data networks (DN) 170, and / or devices within communication network 150 may communicate with one or more data networks (e.g., via CN 152). This can be discussed in relation to... Figure 1A The corresponding components are implemented and operated in essentially the same or similar manner.

[0055] A CN 152 (e.g., 5G-CN) can provide / configure one or more interfaces to a radio device 156, leading to one or more DNs 170, such as public DNs (e.g., the Internet), private DNs, and / or operator-internal DNs. As part of its interface functionality, the CN 152 (e.g., 5G-CN) can establish end-to-end connections between the radio device 156 and one or more DNs, authenticate the radio device 156, and / or provide / configure billing functions. The CN 152 (e.g., 5G-CN) can be a service-based architecture, which may differ from other CNs (e.g., 3GPP 4GCN). The architecture of a CN 152 (e.g., 5G-CN) node can be defined as network functions providing services via interfaces to other network functions. The network functions of the CN 152 (e.g., 5G CN) can be implemented in various ways, such as as network elements on dedicated or shared hardware, software instances running on dedicated or shared hardware, and / or virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0056] CN 152 (e.g., 5G-CN) may include Access and Mobility Management Function (AMF) device 158A and / or User Plane Function (UPF) device 158B, which may be a separate component or a single AMF / UPF device 158. UPF device 158B may serve as a gateway between RAN 154 (e.g., NG-RAN) and one or more DN 170s. UPF device 158B may perform functions such as: packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification supporting traffic flow routing to one or more DN 170s, user plane Quality of Service (QoS) handling (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic authentication), downlink packet buffering, and / or downlink data notification triggering. UPF device 158B can be used as an anchor point within / between Radio Access Technology (RAT) mobility, an external Protocol (or Packet) Data Unit (PDU) session point interconnected to one or more DNs, and / or a branch point supporting multi-homed PDU sessions. Radio device 156 can be configured to receive services via PDU sessions, which may be a logical connection between the radio device and the DN.

[0057] The AMF device 158A can perform functions such as: Non-Access Stratum (NAS) signaling termination, NAS signaling security, Access Stratum (AS) security control, inter-CN node signaling for mobility between access networks (e.g., 3GPP access networks and / or non-3GPP access networks), idle-mode radio device reachability (e.g., idle-mode UE reachability for paging retransmission control and execution), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming rights checking, mobility management control (e.g., subscriptions and policies), network slice support, and / or Session Management Function (SMF) selection. NAS can refer to functions operating between the CN and the radio device, while AS can refer to functions operating between the radio device and the RAN.

[0058] CN 152 (e.g., 5G-CN) may include Figure 1B One or more additional network functions may not be shown. CN152 (e.g., 5G-CN) may include one or more means of implementing at least one of the following: Session Management Function (SMF), NR Repository Function (NRF), Policy Control Function (PCF), Network Open Function (NEF), Unified Data Management (UDM), Application Function (AF), Authentication Server Function (AUSF), and / or any other function.

[0059] RAN 154 (e.g., NG-RAN) can communicate with radio device 156 via radio communication (e.g., air interface). Radio device 156 can communicate with CN 152 via RAN 154. RAN 154 (e.g., NG-RAN) may include one or more first-type base stations (e.g., gNBs including gNB 160A and gNB 160B (collectively referred to as gNB 160)) and / or one or more second-type base stations (e.g., ngeNBs including ng-eNB 162A and ng-eNB 162B (collectively referred to as ng eNB 162)). RAN 154 may include one or more base stations of any quantity type. gNB 160 and ng eNB 162 may be referred to as base stations. Base stations (e.g., gNB 160 and ng eNB 162) may include one or more antenna sets for wireless communication (e.g., via air interface) with radio device 156. One or more base stations (e.g., gNB 160 and / or ng eNB 162) may include multiple antenna sets to control multiple cells (or sectors) respectively. The cells of the base stations (e.g., gNB 160 and ng-eNB 162) can provide radio coverage to the wireless device 156 over a wide geographical area to support the movement of the wireless device.

[0060] Base stations (e.g., gNB 160 and / or ng-eNB 162) can connect to CN 152 (e.g., 5G CN) via a first interface (e.g., NG interface) and to other base stations via a second interface (e.g., Xn interface). The NG and Xn interfaces can be established using direct physical connections and / or indirect connections via underlying transport networks such as Internet Protocol (IP) transport networks. Base stations (e.g., gNB 160 and / or ng-eNB 162) can communicate with wireless device 156 via a third interface (e.g., Uu interface). Base station (e.g., gNB 160A) can communicate with wireless device 156A via the Uu interface. The NG, Xn, and Uu interfaces can be associated with a protocol stack. The protocol stack associated with said interfaces can be... Figure 1B The network elements shown are used to exchange data and signaling messages. The protocol stack can include two planes: a user plane and a control plane. Any other plane can be used (e.g., within the protocol stack). The user plane handles data of interest to the user. The control plane handles signaling messages of interest to the network elements.

[0061] One or more base stations (e.g., gNB 160 and / or ng-eNB 162) may communicate with one or more AMF / UPF devices (e.g., AMF / UPF 158) via one or more interfaces (e.g., NG interfaces). A base station (e.g., gNB 160A) may communicate with and / or connect to the UPF 158B of the AMF / UPF 158 via an NG user plane (NG-U) interface. The NG-U interface may provide / perform the delivery (e.g., unsecured delivery) of user plane PDUs between the base station (e.g., gNB 160A) and the UPF device (e.g., UPF 158B). A base station (e.g., gNB 160A) may communicate with and / or connect to the AMF device (e.g., AMF 158A) via an NG control plane (NG-C) interface. The NG-C interface can provide / perform functions such as NG interface management, radio device context management (e.g., UE context management), radio device mobility management (e.g., UE mobility management), NAS message transmission, paging, PDU session management, configuration transmission, and / or alarm message transmission.

[0062] For user plane and control plane configurations, the radio device can access the base station via an interface (e.g., a Uu interface). The base station (e.g., gNB 160) can provide user plane and control plane protocol termination to the radio device 156 via the Uu interface. The base station (e.g., gNB 160A) can provide user plane and control plane protocol termination to the radio device 156A via the Uu interface associated with the first protocol stack. The base station (e.g., ng-eNB 162) can provide evolved UMTS Terrestrial Radio Access (EUTRA) user plane and control plane protocol termination to the radio device 156 via a Uu interface (e.g., where EUTRA may refer to 3GPP 4G Radio Access Technology). The base station (e.g., ng-eNB 162B) can provide EUTRA user plane and control plane protocol termination to the radio device 156B via the Uu interface associated with the second protocol stack. User plane and control plane protocol termination can include, for example, NR user plane and control plane protocol termination, 4G user plane and control plane protocol termination, etc.

[0063] CN 152 (e.g., 5G-CN) can be configured to handle one or more radio accesses (e.g., NR, 4G, and / or any other radio access). The NR network / device (or any first network / device) can also be connected to the 4G core network / device (or any second network / device) in a non-standalone mode (e.g., non-standalone operation). In non-standalone mode / operation, the 4G core network can be used to provide (or at least support) control plane functions (e.g., initial access, mobility, and / or paging). Although Figure 1B Only one AMF / UPF 158 is shown, but one or more base stations (e.g., one or more gNBs and / or one or more ng-eNBs) can connect to multiple AMF / UPF nodes, for example, to provide redundancy and / or load sharing across multiple AMF / UPF nodes.

[0064] Network elements (e.g., Figure 1B The interfaces between the network elements shown (e.g., Uu, Xn, and / or NG interfaces) can be associated with a protocol stack that the network elements can use to exchange data and signaling messages. The protocol stack can include two planes: a user plane and a control plane. Any other plane can be used (e.g., within the protocol stack). The user plane can handle data associated with the user (e.g., data of interest to the user). The control plane can handle data associated with one or more network elements (e.g., signaling messages of interest to the network elements).

[0065] Figure 1A The communication network 100 and / or Figure 1BThe communication network 150 may include any quantity / number and / or type of devices, such as computing devices, wireless devices, mobile devices, handheld devices, tablets, laptops, Internet of Things (IoT) devices, hotspots, cellular repeaters, and / or more generally, user equipment (e.g., UE). While this document may refer to one or more of the aforementioned types of devices (e.g., UE, wireless device, computing device, etc.), it should be understood that any device herein may include any one or more of the aforementioned types or similar devices. The communication network and any other networks referenced herein may include LTE networks, 5G networks, satellite networks, and / or any other networks used for wireless communication (e.g., any 3GPP network and / or any non-3GPP network). The devices, systems, and / or methods described herein may be generally described as being implemented on one or more devices (e.g., wireless devices, base stations, eNBs, gNBs, computing devices, etc.) in one or more networks, but it should be understood that one or more features and steps may be implemented on any device and / or in any network.

[0066] Figure 2A An exemplary user plane configuration is shown. The user plane configuration may include, for example, the NR user plane protocol stack. Figure 2B An exemplary control plane configuration is shown. The control plane configuration may include, for example, an NR control plane protocol stack. One or more of the user plane configuration and / or control plane configuration may use a Uu interface that may be located between the wireless device 210 and the base station 220. Figure 2A and Figure 2B The protocol stack shown can be essentially used for, for example Figure 1B The protocol stacks of the Uu interface between the wireless device 156A and the base station 160A shown are the same or similar.

[0067] User plane configuration (e.g., NR user plane protocol stack) may include multiple layers (e.g., five layers or any other number of layers) implemented in radio device 210 and base station 220 (e.g., such as...). Figure 2A(As shown). At the bottom of the protocol stack, the Physical Layer (PHY) 211 and 221 can provide transport services to higher layers of the protocol stack and can correspond to Layer 1 of the Open Systems Interconnection (OSI) model. Protocol layers above PHY 211 may include Media Access Control (MAC) 212, Radio Link Control (RLC) 213, Packet Data Convergence Protocol (PDCP) 214, and / or Service Data Application Protocol (SDAP) 215. Protocol layers above PHY 221 may include Media Access Control (MAC) 222, Radio Link Control (RLC) 223, Packet Data Convergence Protocol (PDCP) 224, and / or Service Data Application Protocol (SDAP) 225. One or more of the four protocol layers above PHY 211 can correspond to Layer 2 of the OSI model or the Data Link Layer. One or more of the four protocol layers above PHY 221 can correspond to Layer 2 of the OSI model or the Data Link Layer.

[0068] Figure 3 An example of a protocol layer is shown. A protocol layer can include, for example, the NR user plane protocol stack. One or more services can be provided between protocol layers. SDAP (e.g., Figure 2A and Figure 3 SDAPs 215 and 225 (shown) can perform Quality of Service (QoS) flow processing. Radio devices (e.g., radio devices 106, 156A, 156B, and 210) can receive services via / through a PDU session, which may be a logical connection between the radio device and the DN. A PDU session may have one or more QoS flows 310. A DN's UPF (e.g., UPF 158B) can map IP packets to one or more QoS flows of the PDU session, for example, based on one or more QoS requirements (e.g., in terms of latency, data rate, error rate, and / or any other quality / service requirements). SDAPs 215 and 225 can perform mapping / demapping between one or more QoS flows 310 and one or more radio bearers 320 (e.g., data radio bearers). The mapping / demapping between one or more QoS flows 310 and radio bearers 320 can be determined by SDAP 225 of base station 220. The mapping between QoS flows 310 and radio bearers 320 can be notified by reflection mapping and / or control signaling received from base station 220 via SDAP 215. For reflection mapping, SDAP 225 of base station 220 can use QoS Flow Indicators (QFIs) to mark downlink packets, which can be monitored / detected / identified / indicated / observed by SDAP 215 of radio device 210 to determine the mapping / demapping between one or more QoS flows 310 and radio bearers 320.

[0069] PDCP (e.g., Figure 2A and Figure 3 PDCPs 214 and 224 shown can perform header compression / decompression, for example, to reduce the amount of data that may be transmitted via the air interface, perform encryption / decryption to prevent unauthorized decoding of data transmitted via the air interface, and / or perform integrity protection (e.g., to ensure that control messages originate from their intended source). PDCPs 214 and 224 can perform retransmission of undelivered packets, reordering and repackaging of packets, and / or removal of duplicate packets received due to, for example, handover (e.g., intra-gNB handover). PDCPs 214 and 224 can perform packet duplication, for example, to increase the likelihood of packets being received. The receiver can receive packets repeatedly and can remove any duplicate packets. Packet duplication may be useful for certain services, such as those requiring high reliability.

[0070] The PDCP layers (e.g., PDCP 214 and 224) can (e.g., in a dual-connectivity scenario / configuration) perform mapping / demapping between segmented radio bearers and RLC channels (e.g., RLC channel 330). Dual connectivity can refer to a technique that allows a radio device to communicate with multiple cells (e.g., two cells), or more generally, multiple cell groups, including a primary cell group (MCG) and a secondary cell group (SCG). For example, if a single radio bearer is handled by a cell group in dual connectivity (e.g., one of the radio bearers provided / configured as serviced by PDCP 214 and 224 to SDAP 215 and 225), then segmented bearers can be configured and / or used. PDCP 214 and 224 can map / demapping between segmented radio bearers and RLC channel 330 belonging to the cell group.

[0071] The RLC layer (e.g., RLC 213 and 223) can perform segmentation, retransmission via Automatic Repeat Request (ARQ), and / or removal of duplicate data units received from the MAC layer (e.g., MAC 212 and 222, respectively). The RLC layer (e.g., RLC 213 and 223) can support multiple transmission modes (e.g., three transmission modes: Transparent Mode (TM); Unacknowledged Mode (UM); and Acknowledged Mode (AM)). The RLC layer can perform one or more of the aforementioned functions, for example, based on the transmission mode in which the RLC layer is operating. RLC configuration can be based on logical channels. RLC configuration can be independent of parameter sets and / or Transmission Time Interval (TTI) duration (or other durations). The RLC layer (e.g., RLC 213 and 223) can provide / configure the RLC channel as a service to the PDCP layer (e.g., PDCP 214 and 224, respectively), for example... Figure 3 As shown in the image.

[0072] The MAC layer (e.g., MAC 212 and 222) can perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing / demultiplexing data units / data portions belonging to one or more logical channels to / from / to the PHY layer (e.g., PHY 211 and 221, respectively) into transport blocks (TBs). The MAC layer of the base station (e.g., MAC 222) can be configured to perform scheduling, scheduling information reporting, and / or prioritization among radio devices via dynamic scheduling. Scheduling may be performed by the base station (e.g., base station 220 at MAC 222) for downlink and / or uplink. The MAC layer (e.g., MAC 212 and 222) can be configured to perform error correction via Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA), prioritization among the logical channels of radio device 210 via logical channel prioritization and / or padding. The MAC layer (e.g., MAC 212 and 222) can support one or more parameter sets and / or transmission timings. Mapping constraints in logical channel prioritization can control which parameter set and / or transmission timings a logical channel can use. The MAC layer (e.g., MAC 212 and 222) can provide / configure logical channel 340 as a service to the RLC layer (e.g., RLC 213 and 223).

[0073] The PHY layer (e.g., PHY 211 and 221) can perform transport channel to physical channel mapping and / or digital and analog signal processing functions, for example, for transmitting and / or receiving information (e.g., via an air interface). Digital and / or analog signal processing functions may include, for example, encoding / decoding and / or modulation / demodulation. The PHY layer (e.g., PHY 211 and 221) can perform multi-antenna mapping. The PHY layer (e.g., PHY 211 and 221) can provide / configure one or more transport channels (e.g., transport channel 350) as services to the MAC layer (e.g., MAC 212 and 222, respectively).

[0074] Figure 4A An exemplary downlink data stream for user plane configuration is shown. User plane configuration may include, for example... Figure 2A The NR user plane protocol stack is shown. For example, one or more TBs can be generated based on the data stream transmitted via the user plane protocol stack. Figure 4A As shown, the downlink data flow of three IP packets (n, n+1, and m) via the NR user plane protocol stack can (e.g., at base station 220) generate two TBs. The uplink data flow via the NR user plane protocol stack can be similar. Figure 4AThe downlink data flow is shown in the diagram. For example, three IP packets (n, n+1, and m) can be determined based on two TBs from the uplink data flow via the NR user plane protocol stack. The first quantity of packets (e.g., three or any other quantity) can be determined based on the second quantity of TBs (e.g., two or another quantity).

[0075] For example, if SDAP 225 receives three IP packets (or other amounts of IP packets) from one or more QoS flows and maps the three packets (or other amounts of packets) to radio bearers (e.g., radio bearers 402 and 404), then a downlink data flow can begin. SDAP 225 can map IP packets n and n+1 to the first radio bearer 402 and IP packet m to the second radio bearer 404. The SDAP header (in...) Figure 4A Each SDAP SDU shown (preceded by an "H") can be added to an IP packet to generate an SDAP PDU, which may be referred to as a PDCP SDU. Data units transmitted from / to higher protocol layers may be referred to as service data units (SDUs) of lower protocol layers, and data units transmitted from / to lower protocol layers may be referred to as protocol data units (PDUs) of higher protocol layers. Figure 4A As shown, the data unit from SDAP 225 can be an SDU (e.g., PDCP SDU) of a lower protocol layer PDCP 224, and can also be a PDU (e.g., SDAP PDU) of SDAP 225.

[0076] Each protocol layer (e.g., Figure 4A The protocol layers shown) or at least some of the protocol layers can: perform their own functions (e.g., regarding...) Figure 3 Each protocol layer described has one or more functions, which can add corresponding headers and / or forward the corresponding output to the next lower layer (e.g., its corresponding lower layer). PDCP 224 can perform IP header compression and / or encryption. PDCP 224 can forward its output (e.g., PDCP PDU, i.e., RLC SDU) to RLC 223. RLC 223 can optionally perform fragmentation (e.g., as described in the diagram). Figure 4A (As shown in the diagram for IP packets m). RLC 223 can forward its output (e.g., two RLC PDUs, i.e., two MAC SDUs, generated by adding corresponding sub-headers to two SDU segments (SDU Seg)) to MAC 222. MAC 222 can multiplex many RLC PDUs (MAC SDUs). MAC 222 can attach MAC sub-headers to RLC PDUs (MACSDUs) to form a TB. MAC sub-headers can be distributed across the entire MAC PDU (e.g., in...). Figure 4A(As shown in the NR configuration). The MAC sub-header can be located entirely at the beginning of the MAC PDU (e.g., in the LTE configuration). For example, if the MAC PDU sub-header is calculated before assembling the complete MAC PDU, the NR MAC PDU structure can reduce processing time and / or associated latency.

[0077] Figure 4B An exemplary format of the MAC subheader in a MAC PDU is shown. A MAC PDU may include a MAC subheader (H) and a MAC SDU. Each of one or more MAC subheaders may include: an SDU length field indicating the length (e.g., in bytes) of the MAC SDU corresponding to the MAC subheader; a Logical Channel Identifier (LCID) field identifying / indicating the logical channel from which the MAC SDU originates to aid the demultiplexing process; a flag (F) indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0078] One or more MAC control elements (CEs) can be added to or inserted into a MAC PDU through a MAC layer, such as MAC 223 or MAC 222. Figure 4B As shown, two MAC CEs can be inserted / added before two MAC PDUs. MAC CEs can also be inserted / added at the beginning of a MAC PDU for downlink transmission (e.g., ...). Figure 4B (As shown in the diagram). One or more MAC CEs can be inserted / added to the end of the MAC PDU for uplink transmission. MAC CEs can be used for in-band control signaling. Exemplary MAC CEs may include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs (e.g., activation / deactivation for PDCP repeated detection, channel state information (CSI) reports, sounding reference signal (SRS) transmissions, and MAC CEs for previously configured components); discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. MAC CEs may be preceded by a MAC subheader (with a format similar to that described in the MAC subheader of the MAC SDU), and MAC CEs can be identified by a reserved value in the LID field, which indicates the type of control information included in the corresponding MAC CE.

[0079] Figure 5A An exemplary mapping for downlink channels is shown. Mapping for uplink channels may include mappings between downlink channels (e.g., logical channels, transport channels, and physical channels). Figure 5BAn exemplary mapping for uplink channels is shown. The mapping for uplink channels can include mappings between uplink channels (e.g., logical channels, transport channels, and physical channels). Information can be passed through / via channels between the RLC layer, MAC layer, and PHY layer of a protocol stack (e.g., the NR protocol stack). Logical channels can be used between the RLC layer and the MAC layer. Logical channels can be classified / indicated as control channels that can (e.g., in the NR control plane) carry control information and / or configuration information, or traffic channels that can (e.g., in the NR user plane) carry data. Logical channels can be classified / indicated as dedicated logical channels that can be dedicated to a specific wireless device, and / or common logical channels that can be used by more than one wireless device (e.g., a group of wireless devices).

[0080] Logical channels can be defined by the type of information they carry. This set of logical channels (e.g., in an NR configuration) may include one or more channels described below. A Paging Control Channel (PCCH) may include / carry one or more paging messages for paging a radio device whose location is unknown to the network at the cell level. A Broadcast Control Channel (BCCH) may include / carry system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIBs). Radio devices can use system information messages to obtain information about how to configure the cell and how to operate within it. A Common Control Channel (CCCH) may include / carry control messages and random access. A Dedicated Control Channel (DCCH) may include / carry control messages destined for / from a specific radio device to configure configuration information for that device. A Dedicated Traffic Channel (DTCH) may include / carry user data destined for / from a specific radio device.

[0081] Transport channels can be used between the MAC layer and the PHY layer. A transport channel can be defined by how the information it carries is sent / transmitted (e.g., via the air interface). (For example, it can be defined by NR configuration or any other configuration.) The set of transport channels can include one or more of the following channels: Paging channel (PCH) can include / carry paging messages originating from the PCCH. Broadcast channel (BCH) can include / carry MIBs from the BCCH. Downlink shared channel (DL-SCH) can include / carry downlink data and signaling messages, including SIBs from the BCCH. Uplink shared channel (UL-SCH) can include / carry uplink data and signaling messages. Random access channel (RACH) can provide wireless devices with access to the network without any prior scheduling.

[0082] The PHY layer can use physical channels to pass / transmit information between processing levels within the PHY layer. A physical channel can have an associated set of time-frequency resources for carrying information from one or more transport channels. The PHY layer can generate control information to support lower-level operations. The PHY layer can provide / transmit control information to lower levels of the PHY layer via physical control channels (e.g., referred to as L1 / L2 control channels). The set of physical channels and physical control channels (e.g., defined by NR configuration or any other configuration) can include one or more of the following channels: Physical Broadcast Channel (PBCH) which can include / carry MIBs from the BCH; Physical Downlink Shared Channel (PDSCH) which can include / carry downlink data and signaling messages from the DL-SCH, and paging messages from the PCH; and Physical Downlink Control Channel (PDCCH) which can include / carry downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling clearances, and uplink power control commands. The Physical Uplink Shared Channel (PUSCH) may include / carry uplink data and signaling messages from the UL-SCH, and in some cases, uplink control information (UCI) as described below. The Physical Uplink Control Channel (PUCCH) may include / carry UCI, which may include HARQ acknowledgments, channel quality indicators (CQI), precoding matrix indicators (PMI), ranking indicators (RI), and scheduling requests (SR). The Physical Random Access Channel (PRACH) can be used for random access.

[0083] The physical layer can generate physical signals to support low-level operations, which can be analogous to a physical control channel. For example... Figure 5A and Figure 5B As shown, physical layer signals (e.g., which may be defined by NR configuration or any other configuration) may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DM-RS), a sounding reference signal (SRS), a phase tracking reference signal (PT RS), and / or any other signals.

[0084] One or more of the channels (e.g., logical channels, transport channels, physical channels, etc.) can be used to perform functions associated with the control plan protocol stack (e.g., the NR control plane protocol stack). Figure 2B An exemplary control plane configuration (e.g., the NR control plane protocol stack) is shown. For example... Figure 2BAs shown, a control plane configuration (e.g., an NR control plane protocol stack) can use one or more substantially identical / similar protocol layers (e.g., PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224) as an example user plane configuration (e.g., an NR user plane protocol stack). The four similar protocol layers can include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. For example, a control plane configuration (e.g., an NR control plane stack) could have Radio Resource Control (RRC) 216 and 226 and NAS protocols 217 and 237 on top of the control plane configuration (e.g., an NR control plane protocol stack) instead of SDAP 215 and 225. A control plane configuration could include AMF 230 containing NAS protocol 237.

[0085] NAS protocols 217 and 237 can provide control plane functionality between wireless device 210 and AMF 230 (e.g., AMF 158A or any other AMF) and / or more generally, between wireless device 210 and CN (e.g., CN 152 or any other CN). NAS protocols 217 and 237 can provide control plane functionality between wireless device 210 and AMF 230 via signaling messages referred to as NAS messages. There may not be a direct path between wireless device 210 and AMF 230 through which NAS messages can be transmitted. NAS messages can be transmitted using AS interfaces with Uu and NG interfaces. NAS protocols 217 and 237 can provide control plane functions such as authentication, security, connection settings, mobility management, session management, and / or any other functions.

[0086] RRC layers 216 and 226 can provide / configure control plane functions between the radio device 210 and the base station 220 and / or more generally, between the radio device 210 and the RAN (e.g., base station 220). RRC layers 216 and 226 can provide / configure control plane functions between the radio device 210 and the base station 220 via signaling messages, which may be referred to as RRC messages. RRC messages can be sent / transmitted between the radio device 210 and the RAN (e.g., base station 220) using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC layer can multiplex control plane data and user plane data into the same TB. RRC layers 216 and 226 can provide / configure control plane functions, such as one or more of the following: broadcasting system information related to AS and NAS; paging initiated by CN or RAN; establishing, maintaining, and releasing RRC connections between radio device 210 and RAN (e.g., base station 220); security functions, including key management; establishing, configuring, maintaining, and releasing signaling radio bearers and data radio bearers; mobility functions; QoS management functions; radio device measurement reporting (e.g., radio device measurement reports) and control over the reports; detecting radio link failures and recovery from radio link failures (RLF); and / or NAS message transmission. As part of establishing an RRC connection, RRC layers 216 and 226 can establish an RRC context, which may involve configuring parameters for communication between radio device 210 and RAN (e.g., base station 220).

[0087] Figure 6 Exemplary RRC states and RRC state transitions are illustrated. The RRC state of a wireless device can change to another RRC state (e.g., an RRC state transition of the wireless device). The wireless device can be substantially the same as or similar to wireless devices 106, 210, or any other wireless device. The wireless device can be in at least one of a plurality of states, such as including three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 606 (e.g., RRC_IDLE), and RRC inactive 604 (e.g., RRC_INACTIVE). RRC inactive 604 can be an RRC connected but inactive state.

[0088] An RRC connection can be established for a wireless device. This can be, for example, during an RRC connection state. During an RRC connection state (e.g., during RRC connection 602), the wireless device can have an established RRC context and can have at least one RRC connection with a base station. The base station can resemble one of one or more base stations (e.g., Figure 1A One or more base stations of RAN 104 shown, Figure 1BOne of the gNB 160 or ng-eNB 162 shown. Figure 2A and Figure 2B (Base station 220 shown, or any other base station). A base station connected to a radio device (e.g., with an established RRC connection) may have the radio device's RRC context. The RRC context, which may be referred to as the radio device context (e.g., UE context), may include parameters for communication between the radio device and the base station. These parameters may include one or more of the following, for example: AS context; radio link configuration parameters; bearer configuration information (e.g., related to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or layer configuration information (e.g., PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information). During RRC connection states (e.g., RRC connection 602), the mobility of the radio device may be managed / controlled by the RAN (e.g., RAN 104 or NG RAN 154). The radio device may measure the received signal level (e.g., reference signal level, reference signal received power, reference signal received quality, received signal strength indicator, etc.) based on one or more signals transmitted from the serving cell and neighboring cells. The wireless device can report these measurements to the serving base station (e.g., the base station currently serving the wireless device). The serving base station of the wireless device can, for example, request a switch to a cell of one of the neighboring base stations based on the reported measurements. The RRC state can be transitioned from an RRC connected state (e.g., RRC connected 602) to an RRC idle state (e.g., RRC idle 606) via a connection release procedure 608. The RRC state can be transitioned from an RRC connected state (e.g., RRC connected 602) to an RRC inactive state (e.g., RRC inactive 604) via a connection deactivation procedure 610.

[0089] An RRC context may not be established for the radio device. This could be, for example, during an RRC idle state. During an RRC idle state (e.g., RRC Idle 606), an RRC context may not be established for the radio device. During an RRC idle state (e.g., RRC Idle 606), the radio device may not have an RRC connection with the base station. During an RRC idle state (e.g., RRC Idle 606), the radio device may be in a sleep state for most of the time (e.g., to conserve battery power). The radio device may wake up periodically (e.g., every Discontinuous Receive (DRX) cycle) to monitor paging messages (e.g., paging messages sent from the RAN). The mobility of the radio device can be managed by the radio device through a cell reselection procedure. The RRC state can transition from an RRC idle state (e.g., RRC Idle 606) to an RRC connected state (e.g., RRC Connected 602) via a connection establishment procedure 612, which may involve a random access procedure.

[0090] The previously established RRC context can be maintained for the radio device. This can be, for example, during an RRC inactivity state. During an RRC inactivity state (e.g., RRC inactivity 604), the previously established RRC context can be maintained in both the radio device and the base station. Compared to a transition from an RRC idle state (e.g., RRC idle 606) to an RRC connected state (e.g., RRC connected 602), maintaining the RRC context allows for / permits a faster transition to the RRC connected state (e.g., RRC connected 602) with reduced signaling overhead. During an RRC inactivity state (e.g., RRC inactivity 604), the radio device can be in a sleep state, and the mobility of the radio device can be managed / controlled by the radio device through cell reselection. The RRC state can transition from an RRC inactivity state (e.g., RRC inactivity 604) to an RRC connected state (e.g., RRC connected 602) via a connection recovery procedure 614. The RRC state can be transitioned from an RRC inactive state (e.g., RRC inactive 604) to an RRC idle state (e.g., RRC idle 606) via a connection release procedure 616, which can be the same as or similar to the connection release procedure 608.

[0091] RRC states can be associated with mobility management mechanisms. During RRC idle states (e.g., RRC Idle 606) and RRC inactive states (e.g., RRC Inactive 604), mobility can be managed / controlled by the radio device through cell reselection. The purpose of mobility management during RRC idle states (e.g., RRC Idle 606) or RRC inactive states (e.g., RRC Inactive 604) can be to enable / permit the network to notify the radio device of events via paging messages, without having to broadcast paging messages across the entire mobile communication network. For example, mobility management mechanisms used during RRC idle states (e.g., RRC Idle 606) or RRC idle states (e.g., RRC Inactive 604) can enable / permit the network to track the radio device at the cell group level, allowing paging messages to be broadcast on the cells of the cell group in which the radio device currently camps (e.g., instead of sending paging messages across the entire mobile communication network). Mobility management mechanisms for RRC idle states (e.g., RRC idle 606) and RRC inactive states (e.g., RRC inactive 604) can track radio devices at the cell group level. Mobility management mechanisms can track using, for example, different packet granularities. Multiple levels of cell packet granularity may exist (e.g., three levels of cell packet granularity: a single cell; cells within a RAN area identified by a RAN Area Identifier (RAI); and a group of cells within a RAN area referred to as a tracking area and identified by a Tracking Area Identifier (TAI)).

[0092] A tracking area can be used to track radio devices (e.g., to track the location of radio devices at the CN level). A CN (e.g., CN 102, 5G CN 152, or any other CN) can send a list of TAIs associated with the radio device's registration area (e.g., UE registration area) to the radio device. For example, if a radio device (e.g., through cell reselection) moves to a cell associated with a TAI that may not be included in the list of TAIs associated with the UE registration area, the radio device can perform a registration update with the CN to allow the CN to update the radio device's location and provide the radio device with the new UE registration area.

[0093] RAN areas can be used to track radio devices (e.g., to track the location of radio devices at the RAN level). For radio devices in an RRC inactive state (e.g., RRC inactive 604), the radio device can be assigned / provided / configured with a RAN notification area. A RAN notification area can include one or more cell identities (e.g., a RAI list and / or a TAI list). A base station can belong to one or more RAN notification areas. A cell can belong to one or more RAN notification areas. For example, if a radio device (e.g., via cell reselection) moves to a cell not included in a RAN notification area assigned / provided / configured to the radio device, the radio device can perform a notification area update with the RAN to update the radio device's RAN notification area.

[0094] The base station that stores the RRC context of the wireless device or the last serving base station of the wireless device may be referred to as the anchor base station. The anchor base station may maintain the RRC context of the wireless device at least during the time period when the wireless device is in the anchor base station's RAN notification area and / or during the time period when the wireless device is in an RRC inactive state (e.g., RRC inactive 604).

[0095] Base station (e.g., Figure 1B A gNB 160 or any other base station can be divided into two parts: a central unit (e.g., a base station central unit, such as a gNB CU) and one or more distributed units (e.g., base station distributed units, such as a gNBDU). The base station central unit (CU) can be coupled to one or more base station distributed units (DUs) using an F1 interface (e.g., an F1 interface defined in the NR configuration). The base station CU may include an RRC layer, a PDCP layer, and an SDAP layer. The base station distributed unit (DU) may include an RLC layer, a MAC layer, and a PHY layer.

[0096] Physical signals and physical channels (e.g., regarding Figure 5A and Figure 5BThe data described can be mapped to one or more symbols (e.g., Orthogonal Frequency Division Multiplexing (OFDM) symbols or any other symbols in an NR configuration). OFDM is a multicarrier communication scheme that transmits / transmits data via F orthogonal subcarriers (or tones). For example, before transmitting data, the data can be mapped to a series of complex symbols called source symbols (e.g., M-QAM symbols, M-PSK symbols, or any other modulation symbols) and divided into F parallel symbol streams. The F parallel symbol streams can be considered as if they were in the frequency domain. The F parallel symbols can be used as input to an Inverse Fast Fourier Transform (IFFT) block, which transforms them into the time domain. The IFFT block can receive F source symbols at a time, one source symbol from each of the F parallel symbol streams. The IFFT block can use each source symbol to modulate the amplitude and phase of one of the F sinusoidal fundamental functions corresponding to the F orthogonal subcarriers. The output of an IFFT block can be F time-domain samples representing the sum of F orthogonal subcarriers. These F time-domain samples can form a single OFDM symbol. For example, after one or more processes (e.g., adding a cyclic prefix) and upconversion, the OFDM symbol provided / output by the IFFT block can be transmitted / transmitted over the air interface at the carrier frequency. Before being processed by the IFFT block, the F parallel symbol streams can be mixed, for example, using a Fast Fourier Transform (FFT) block. This operation can produce a Discrete Fourier Transform (DFT) precoded OFDM symbol, which can be used by one or more radio devices in the uplink to reduce the peak-to-average power ratio (PAPR). The inverse processing of the OFDM symbols at the receiver can be performed using the FFT block to recover the data mapped to the source symbols.

[0097] Figure 7 An exemplary configuration of a frame is shown. A frame may include, for example, an NR radio frame, into which OFDM symbols may be grouped. A frame (e.g., an NR radio frame) may be identified / indicated by a System Frame Number (SFN) or any other value. The SFN may repeat at a period of 1024 frames. The duration of an NR frame may be 10 milliseconds (ms) and may include 10 subframes with a duration of 1 ms. Subframes may be divided into one or more time slots (e.g., depending on the parameter set and / or different subcarrier spacing). Each of the one or more time slots may include, for example, 14 OFDM symbols per time slot. Any amount of symbols, time slots, or duration can be used for any time interval.

[0098] The duration of a time slot can depend on the parameter set of the OFDM symbols used for the time slot. For example, flexible parameter sets can be supported to accommodate different deployments (e.g., cells with carrier frequencies below 1 GHz up to cells with carrier frequencies in the mmWave range). Flexible parameter sets can be supported, for example, in NR configurations or any other radio configurations. Parameter sets can be defined based on subcarrier spacing and / or cyclic prefix duration. Subcarrier spacing can be increased by a power of two of a baseline subcarrier spacing of 15 kHz. Cyclic prefix duration can be decreased by a power of two of a baseline cyclic prefix duration of 4.7 μs, for example, in parameter sets for NR configurations or any other radio configurations. Parameter sets can be defined using the following combinations of subcarrier spacing / cyclic prefix duration: 15 kHz / 4.7 μs; 30 kHz / 2.3 μs; 60 kHz / 1.2 μs; 120 kHz / 0.59 μs; 240 kHz / 0.29 μs and / or any other combination of subcarrier spacing / cyclic prefix duration.

[0099] A time slot can have a fixed number / quantity of OFDM symbols (e.g., 14 OFDM symbols). A parameter set with a higher subcarrier spacing can have a shorter time slot duration and more time slots per subframe. Figure 7 The example shown is a transmission structure with parameter set dependent slot duration and number of slots per subframe. Figure 7 (The parameter set with a subcarrier spacing of 240 kHz is not shown in the diagram). Subframes (e.g., in an NR configuration) can be used as parameter set-independent time references. Time slots can be used as units for scheduling uplink and downlink transmissions. Scheduling (e.g., in an NR configuration) can be decoupled from the time slot duration. Scheduling can begin at any OFDM symbol. For example, scheduling can continue transmission, for example, to support the same number of symbols required for low latency. These partial time slot transmissions can be referred to as micro-slot or sub-slot transmissions.

[0100] Figure 8 An exemplary resource configuration for one or more carriers is shown. The resource configuration may include time slots in the time and frequency domains for NR carriers or any other carriers. Time slots may include resource elements (REs) and resource blocks (RBs). A resource element (RE) may be a minimum physical resource (e.g., in an NR configuration). An RE may span an OFDM symbol in the time domain multiplied by a subcarrier in the frequency domain, for example... Figure 8 As shown in the diagram. RB can span twelve consecutive REs in the frequency domain, for example... Figure 8As shown in the diagram, a carrier (e.g., an NR carrier) can be limited to a certain number of RBs and / or subcarriers (e.g., 275 RBs or 275 × 12 = 3300 subcarriers). If such a limitation is used, it can limit the carrier (e.g., NR carrier) frequency based on the subcarrier spacing (e.g., for subcarrier spacings of 15, 30, 60, and 120 kHz, the carrier frequencies are 50, 100, 200, and 400 MHz, respectively). A 400 MHz bandwidth can be set based on a 400 MHz bandwidth limit per carrier. Any other bandwidth can be set based on a bandwidth limit per carrier.

[0101] It can be on a carrier (e.g., NR, for example) Figure 8 The entire bandwidth (as shown in the example) uses a single set of parameters. In other exemplary configurations, multiple sets of parameters can be supported on the same carrier. NR and / or other access technologies can support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all wireless devices are capable of receiving the full carrier bandwidth (e.g., due to hardware limitations and / or different wireless device capabilities). For example, receiving and / or utilizing the full carrier bandwidth may be prohibitive in terms of wireless device power consumption. Wireless devices can adjust the size of their receive bandwidth, for example, based on the amount of traffic scheduled to be received by the wireless device (e.g., to reduce power consumption and / or for other purposes). Such adjustments can be referred to as bandwidth adaptation.

[0102] The configuration of one or more Bandwidth Parts (BWPs) can support one or more radio devices that cannot receive the full carrier bandwidth. BWPs can support bandwidth adaptation for such radio devices, for example, those that cannot receive the full carrier bandwidth. A BWP (e.g., an NR-configured BWP) can be defined by a subset of consecutive RBs on a carrier. A radio device can be configured (e.g., via an RRC layer) with one or more downlink BWPs per serving cell and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). For example, at a given time, one or more configured BWPs of the serving cell can be active. One or more BWPs can be referred to as the active BWPs of the serving cell. For example, if the serving cell is configured with a secondary uplink carrier, the serving cell can have one or more first active BWPs on the uplink carrier and one or more second active BWPs on the secondary uplink carrier.

[0103] Downlink BWPs from a configured set of downlink BWPs can be linked with uplink BWPs from a configured set of uplink BWPs (e.g., for unpaired spectrum). For example, a downlink BWP and an uplink BWP can be linked if the downlink BWP index and the uplink BWP index are the same. The wireless device can expect that the center frequency of the downlink BWP is the same as the center frequency of the uplink BWP (e.g., for unpaired spectrum).

[0104] A base station can configure one or more control resource sets (CORESETs) for a radio device for at least one search space. The base station can configure one or more CORESETs for a radio device, for example, for a set of downlink BWPs configured on a primary cell (PCell) or secondary cell (SCell). The search space can include a set of locations in the time and frequency domains where the radio device can monitor / find / detect / identify control information. The search space can be a radio device-specific search space (e.g., a UE-specific search space) or a common search space (e.g., potentially usable by multiple radio devices or a group of radio user equipments). The base station can configure a common search space for a group of radio devices on a PCell or on a primary / secondary cell (PSCell) within an active downlink BWP.

[0105] A base station can configure one or more resource sets for a radio device for one or more PUCCH transmissions (e.g., for uplink BWPs in a configured set of uplink BWPs). The radio device can receive downlink receptions (e.g., PDCCH or PDSCH) in a downlink BWP, for example, based on a configured set of parameters for the downlink BWP (e.g., configured subcarrier spacing and / or configured cyclic prefix duration). The radio device can transmit / transmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWP, for example, based on a configured set of parameters (e.g., configured subcarrier spacing and / or configured cyclic prefix length of the uplink BWP).

[0106] One or more BWP indicator fields may be provided / included in the downlink control information (DCI). The value of the BWP indicator field can indicate which BWP in the configured set of BWPs is the active downlink BWP for one or more downlink receptions. The value of one or more BWP indicator fields can indicate the active uplink BWP for one or more uplink transmissions.

[0107] The base station can semi-statically configure a default downlink BWP within the set of downlink BWPs associated with the PCell for the radio device. For example, if the base station does not provide / configure a default downlink BWP to / for the radio device, the default downlink BWP can be the initially active downlink BWP. The radio device can determine which BWP is the initially active downlink BWP, for example, based on the CORESET configuration obtained using the PBCH.

[0108] The base station can configure a BWP inactivity timer value for the wireless device to use the PCell. The wireless device can start or restart the BWP inactivity timer at any appropriate time. For example, the wireless device can start or restart the BWP inactivity timer if one or more conditions are met. These conditions may include at least one of the following: the wireless device detects a DCI indicating an active downlink BWP other than the default downlink BWP used for paired spectrum operation; the wireless device detects a DCI indicating an active downlink BWP other than the default downlink BWP used for unpaired spectrum operation; and / or the wireless device detects a DCI indicating an active uplink BWP other than the default uplink BWP used for unpaired spectrum operation. For example, if the wireless device does not detect a DCI within a time interval (e.g., 1 ms or 0.5 ms), the wireless device can start / run the BWP inactivity timer towards expiration (e.g., incrementing from zero to the BWP inactivity timer value, or decrementing from the BWP inactivity timer value to zero). For example, if the BWP inactivity timer expires, the wireless device can switch from the active downlink BWP to the default downlink BWP.

[0109] The base station can semi-statically configure one or more BWPs for the wireless device. The wireless device can, for example, switch the active BWP from the first BWP to the second BWP after receiving a DCI indicating that the second BWP is the active BWP. The wireless device can, for example, switch the active BWP from the first BWP to the second BWP after (for example, based on or in response to) the expiration of a BWP inactivity timer (e.g., if the second BWP is the default BWP).

[0110] Downlink BWP handover can refer to switching an active downlink BWP from a first downlink BWP to a second downlink BWP (e.g., the second downlink BWP is activated and the first downlink BWP is deactivated). Uplink BWP handover can refer to switching an active uplink BWP from a first uplink BWP to a second uplink BWP (e.g., the second uplink BWP is activated and the first uplink BWP is deactivated). Downlink and uplink BWP handovers can be performed independently (e.g., in paired spectrum / multiple paired spectrum). Downlink and uplink BWP handovers can be performed simultaneously (e.g., in unpaired spectrum / multiple unpaired spectrum). Handovers between configured BWPs can be performed, for example, based on RRC signaling, DCI signaling, the expiration of a BWP inactivity timer, and / or the initiation of random access.

[0111] Figure 9An example of a configured BWP is shown. Multiple BWPs (e.g., three configured BWPs on an NR carrier) can be used for bandwidth adaptation. A wireless device configured with multiple BWPs (e.g., three BWPs) can switch from one BWP to another at a handover point. BWPs may include: BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and BWP 906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. BWP 902 may be the initially active BWP, and BWP 904 may be the default BWP. The wireless device can switch between BWPs at a handover point. The wireless device can switch from BWP 902 to BWP 904 at handover point 908. The handover at handover point 908 can occur for any suitable reason. The handover at handover point 908 may occur, for example, after (e.g., based on or in response to) the expiration of a BWP inactivity timer (e.g., indicating a switch to the default BWP). The handover at handover point 908 may occur, for example, after receiving (e.g., based on or in response to) a DCI indicating that BWP 904 is the active BWP. The wireless device may, for example, switch from active BWP 904 to BWP 906 at handover point 910 after receiving (e.g., based on or in response to) a DCI indicating that BWP 906 is the new active BWP. The wireless device may, for example, switch from active BWP 906 to BWP 904 at handover point 912 after (e.g., based on or in response to) a BWP inactivity timer expiring. The wireless device may, for example, switch from active BWP 906 to BWP 904 at handover point 912 after receiving (e.g., after receiving (e.g., based on or in response to) a DCI indicating that BWP 904 is the new active BWP. The wireless device may, for example, switch from active BWP 904 to BWP 902 at handover point 914 after receiving (e.g., after receiving (e.g., based on or in response to) a DCI indicating that BWP 902 is the new active BWP.

[0112] For example, if a radio device is configured for a secondary cell with a default downlink BWP and timer values ​​of a configured set of downlink BWPs, the radio device procedure for switching BWPs on the secondary cell can be the same as / similar to the procedure on the primary cell. The radio device can use the timer values ​​and default downlink BWP of the secondary cell in the same / similar manner as the radio device uses the timer values ​​and / or default BWP of the primary cell. Timer values ​​(e.g., BWP inactivity timers) can be configured, for example, via RRC signaling or any other signaling per cell (e.g., for one or more BWPs). One or more active BWPs can be switched to another BWP, for example, based on the expiration of the BWP inactivity timer.

[0113] Two or more carriers can be aggregated, and carrier aggregation (CA) can be used to send / transmit data simultaneously to / from the same wireless device (e.g., to increase the data rate). The aggregated carriers in a CA can be referred to as component carriers (CCs). For example, if CA is configured / used, a wireless device can have a certain number of serving cells (e.g., one CC per serving cell). A CC can have multiple configurations in the frequency domain.

[0114] Figure 10A An exemplary CA configuration based on CC is shown. For example... Figure 10A As shown, the three types of CA configurations can include in-band (adjacent) configuration 1002, in-band (non-adjacent) configuration 1004, and / or inter-band configuration 1006. In in-band (adjacent) configuration 1002, two CCs can be aggregated in the same frequency band (frequency band A) and can be located directly adjacent to each other within that frequency band. In in-band (non-adjacent) configuration 1004, two CCs can be aggregated in the same frequency band (frequency band A), but can be separated from each other by a gap within that frequency band. In inter-band configuration 1006, two CCs can be located in different frequency bands (e.g., frequency band A and frequency band B, respectively).

[0115] The network can set a maximum number of CCs that can be aggregated (e.g., up to 32 CCs can be aggregated in the NR, or any other number can be aggregated in other systems). Aggregated CCs can have the same or different bandwidths, subcarrier spacing, and / or duplex schemes (TDD, FDD, or any other duplex scheme). The serving cell for a radio device using CA can have downlink CCs. One or more uplink CCs can optionally be configured for the serving cell (e.g., for FDD). For example, if the radio device has more data traffic in the downlink than in the uplink, the ability to aggregate more downlink carriers than uplink carriers may be useful.

[0116] For example, if CA is configured, one of the aggregated cells of the radio device can be referred to as the primary cell (PCell). The PCell can be, for example, the serving cell that the radio device initially connects to or accesses during RRC connection establishment, RRC connection re-establishment, and / or handover. The PCell can provide / configure NAS mobility information and security input for the radio device. The radio device can have different PCells. For downlink, the carrier corresponding to the PCell can be referred to as the downlink primary CC (DL PCC). For uplink, the carrier corresponding to the PCell can be referred to as the uplink primary CC (UL PCC). Other aggregated cells of the radio device (e.g., associated with CCs other than the DL PCC and UL PCC) can be referred to as secondary cells (SCells). SCells can be configured, for example, after configuring the PCell for the radio device. SCells can be configured via an RRC connection reconfiguration procedure. For downlink, the carrier corresponding to the SCell can be referred to as the downlink secondary CC (DLSCC). For uplink, the carrier corresponding to the SCell can be referred to as the uplink secondary CC (UL SCC).

[0117] The SCell configured on a wireless device can be activated or deactivated, for example, based on traffic and channel conditions. Deactivating a SCell may cause the wireless device to stop receiving PDCCH and PDSCH on the SCell, as well as transmitting PUSCH, SRS, and CQI on the SCell. This can be achieved, for example, using MAC CE (e.g., regarding...). Figure 4B The MAC CE (Configuration Controller Entity) describes the activation or deactivation of a configured SCell. The MAC CE can use a bitmap (e.g., one bit per SCell) to indicate which SCells of the wireless device (e.g., within a subset of configured SCells) are activated or deactivated. A configured SCell can be deactivated, for example, after (e.g., based on or in response to) an SCell deactivation timer expiring (e.g., each SCell can be configured with one SCell deactivation timer).

[0118] DCI (Distributed Control Information) can include control information for the cell, such as scheduling allocation and scheduling grants. DCI can be sent / transmitted via the cell corresponding to the scheduling allocation and / or scheduling grant; this can be referred to as self-scheduling. DCI including control information for the cell can be sent / transmitted via another cell; this can be referred to as cross-carrier scheduling. Uplink Control Information (UCI) can include control information for aggregated cells, such as HARQ acknowledgments and channel state feedback (e.g., CQI, PMI, and / or RI). UCI can be sent / transmitted via the uplink control channel (e.g., PUCCH) of the PCell or a specific SCell (e.g., an SCell configured with PUCCH). For a large number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. Cells can be divided into multiple PUCCH groups.

[0119] Figure 10B An exemplary group of cells is shown. Aggregated cells can be configured to one or more PUCCH groups (e.g., such as...). Figure 10BAs shown in the diagram. One or more cell groups or one or more uplink control channel groups (e.g., PUCCH group 1010 and PUCCH group 1050) may each include one or more downlink CCs. PUCCH group 1010 may include one or more downlink CCs, for example, three downlink CCs: PCell 1011 (e.g., DL PCC), SCell 1012 (e.g., DL SCC), and SCell 1013 (e.g., DL SCC). PUCCH group 1050 may include one or more downlink CCs, for example, three downlink CCs: PUCCH SCell (or PSCell) 1051 (e.g., DL SCC), SCell 1052 (e.g., DLSCC), and SCell 1053 (e.g., DL SCC). One or more uplink CCs of PUCCH group 1010 may be configured as PCell 1021 (e.g., UL PCC), SCell 1022 (e.g., UL SCC), and SCell 1023 (e.g., UL SCC). One or more uplink CCs of PUCCH group 1050 can be configured as PUCCH SCell (or PSCell) 1061 (e.g., UL SCC), SCell 1062 (e.g., UL SCC), and SCell 1063 (e.g., UL SCC). UCIs associated with the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) can be sent / transmitted via the uplink of PCell 1021 (e.g., via the PUCCH of PCell 1021). UCIs associated with the downlink CCs of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) can be sent / transmitted via the uplink of PUCCH SCell (or PSCell) 1061 (e.g., via the PUCCH of PUCCH SCell 1061). For example, if Figure 10B If the aggregated cells shown are not divided into PUCCH groups 1010 and 1050, a single uplink PCell can be configured to send / transmit UCIs associated with six downlink CCs. For example, if UCIs 1031, 1032, 1033, 1071, 1072, and 1073 are sent / transmitted via PCell 1021, PCell 1021 may become overloaded. By partitioning the transmission of UCIs between PCell 1021 and PUCCH SCell (or PSCell) 1061, overload can be prevented and / or reduced.

[0120] A PCell may include a downlink carrier (e.g., PCell 1011) and an uplink carrier (e.g., PCell 1021). An SCell may include only a downlink carrier. A cell including a downlink carrier and optionally an uplink carrier may be assigned a physical cell ID and a cell index. For example, depending on the context in which the physical cell ID is used, the physical cell ID or cell index may indicate / identify the downlink carrier and / or uplink carrier of the cell. The physical cell ID may be determined, for example, using synchronization signals (e.g., PSS and / or SSS) transmitted / transmitted via the downlink component carrier. The cell index may be determined, for example, using one or more RRC messages. The physical cell ID may be referred to as the carrier ID, and the cell index may be referred to as the carrier index. The first physical cell ID of the first downlink carrier may refer to the first physical cell ID of the cell including the first downlink carrier. Essentially the same / similar concepts may apply, for example, carrier activation. Activation of the first carrier may refer to the activation of the cell including the first carrier.

[0121] The multicarrier nature of the PHY layer can be exposed / indicated to the MAC layer (e.g., in CA configuration). HARQ entities can operate on the serving cell. Transport blocks can be generated based on the allocation / license of each serving cell. Transport blocks and potential HARQ retransmissions of transport blocks can be mapped to serving cells.

[0122] For the downlink, the base station may send / transmit (e.g., unicast, multicast, and / or broadcast) one or more reference signals (RS) (e.g., PSS, SSS, CSI-RS, DM-RS, and / or PT-RS) to one or more radio devices. For the uplink, one or more radio devices may send / transmit one or more RS (e.g., DM-RS, PT-RS, and / or SRS) to the base station. PSS and SSS may be sent / transmitted by the base station and used by one or more radio devices to synchronize one or more radio devices with the base station. Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) blocks may include PSS, SSS, and PBCH. The base station may periodically send / transmit bursts of SS / PBCH blocks, which may be referred to as SSBs.

[0123] Figure 11A An exemplary mapping of one or more SS / PBCH blocks is shown. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, such as...). Figure 11A(As shown in the diagram). Bursts can be transmitted / transmitted periodically (e.g., every 2 frames, every 20 ms, or any other duration). Bursts can be limited to half-frames (e.g., the first half-frame lasting 5 ms). Such parameters can be configured, for example, based on at least one of the following (e.g., the number of SS / PBCH blocks per burst, the periodicity of the burst, the position of the burst within a frame): the carrier frequency of the cell transmitting / transmitting the SS / PBCH blocks; the cell's parameter set or subcarrier spacing; network configuration (e.g., using RRC signaling); and / or any other suitable factors. For example, a radio device can assume the subcarrier spacing of the SS / PBCH blocks based on the monitored carrier frequency, unless the radio network configures the radio device to assume a different subcarrier spacing.

[0124] SS / PBCH blocks can span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, such as...). Figure 11A The symbols (as shown, or any other quantity / number of symbols) can span one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers or any other quantity / number of subcarriers). The PSS, SSS, and PBCH can have a common center frequency. The PSS can be transmitted first and can span, for example, one OFDM symbol and 127 subcarriers. The SSS can be transmitted after the PSS (e.g., two symbols later) and can span one OFDM symbol and 127 subcarriers. The PBCH can be transmitted after the PSS (e.g., spanning the next three OFDM symbols) and can span 240 subcarriers (e.g., in the second and fourth OFDM symbols, such as...). Figure 11A (as shown) and / or can span fewer than 240 subcarriers (e.g., in the third OFDM symbol, such as Figure 11A (as shown in the image).

[0125] (For example, if the radio device is searching for a cell) The radio device may not know the location of the SS / PBCH block in the time and frequency domains. The radio device can monitor the carrier used for the PSS, for example, to find and select cells. The radio device can monitor the frequency location within the carrier. For example, if no PSS is found after a certain duration (e.g., 20 ms), the radio device can search for the PSS at different frequency locations within the carrier. The radio device can search for the PSS at different frequency locations within the carrier, for example, as indicated by the synchronization grating. For example, if a PSS is found at a location in the time and frequency domains, the radio device can determine the locations of the SSS and PBCH separately based on the known structure of the SS / PBCH block. The SS / PBCH block can be a cell-defined SS block (CD-SSB). The primary cell can be associated with a CD-SSB. The CD-SSB can be located on a synchronization grating. Cell selection / search and / or reselection can be based on the CD-SSB.

[0126] The SS / PBCH block can be used by a radio device to determine one or more parameters of a cell. The radio device can determine the cell's Physical Cell Identifier (PCI) based, for example, on the sequences of the PSS and SSS. The radio device can determine the location of the cell's frame boundary based, for example, on the location of the SS / PBCH block. The SS / PBCH block can indicate that it has been transmitted / transmitted according to a transmission mode. The SS / PBCH block in the transmission mode can be at a known distance from the frame boundary (e.g., a predefined distance in the RAN configuration between one or more networks, one or more base stations, and one or more radio devices).

[0127] The PBCH can use QPSK modulation and / or forward error correction (FEC). FEC can use polarity coding. One or more symbols spanned by the PBCH may include / carry one or more DM-RS for demodulating the PBCH. The PBCH may include an indication of the cell's current system frame number (SFN) and / or an SS / PBCH block timing index. These parameters can facilitate time synchronization between the radio device and the base station. The PBCH may include a MIB, which is used to send / transmit one or more parameters to the radio device. The MIB can be used by the radio device to locate the Residual Minimal System Information (RMSI) associated with the cell. The RMSI may include System Information Block Type 1 (SIB1). SIB1 may include information about the radio device accessing the cell. The radio device can use one or more parameters of the MIB to monitor the PDCCH, which can be used to schedule the PDSCH. The PDSCH may include SIB1. SIB1 can be decoded using parameters provided / included in the MIB. The PBCH may indicate that SIB1 is absent. The radio device may, for example, point to a frequency based on a PBCH indicating that SIB1 is absent. The radio device can search for SS / PBCH blocks at the frequency pointed to by the radio device.

[0128] The wireless device may assume that one or more SS / PBCH blocks transmitted / transmitted with the same SS / PBCH block index are quasi-co-located (QCL) (e.g., having substantially the same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameters). The wireless device may not assume a QCL for the transmission of SS / PBCH blocks with different SS / PBCH block indices. SS / PBCH blocks (e.g., SS / PBCH blocks within a half-frame) may be transmitted / transmitted in spatial directions (e.g., using different beams spanning a coverage area of ​​the cell). A first SS / PBCH block may be transmitted / transmitted in a first spatial direction using a first beam, a second SS / PBCH block may be transmitted / transmitted in a second spatial direction using a second beam, a third SS / PBCH block may be transmitted / transmitted in a third spatial direction using a third beam, a fourth SS / PBCH block may be transmitted / transmitted in a fourth spatial direction using a fourth beam, and so on.

[0129] A base station can, for example, transmit / transmit multiple SS / PBCH blocks within the frequency range of a carrier. The first PCI of the first SS / PBCH block among the multiple SS / PBCH blocks may differ from the second PCI of the second SS / PBCH block among the multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted / transmitted at different frequency locations may be different or substantially the same.

[0130] CSI-RS can be sent / transmitted by the base station and used by the radio device to acquire / obtain / determine Channel State Information (CSI). The base station can configure one or more CSI-RS for the radio device for channel estimation or any other suitable purpose. The base station can configure one or more of the same / similar CSI-RS for the radio device. The radio device can measure one or more CSI-RS. The radio device can estimate the downlink channel state and / or generate a CSI report, for example, based on measurements of one or more downlink CSI-RS. The radio device can send / transmit the CSI report to the base station (e.g., based on periodic CSI reports, semi-persistent CSI reports, and / or aperiodic CSI reports). The base station can use feedback provided by the radio device (e.g., estimated downlink channel state) to perform link adaptation.

[0131] A base station can semi-statically configure one or more CSI-RS resource sets for a wireless device. CSI-RS resources can be associated with location and periodicity in both the time and frequency domains. The base station can selectively activate and / or deactivate CSI-RS resources. The base station can instruct the wireless device to activate and / or deactivate CSI-RS resources within the CSI-RS resource set.

[0132] A base station can configure a wireless device to report CSI measurements. The base station can configure the wireless device to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the wireless device can be configured with multiple CSI reports in a specific timing and / or periodicity. For aperiodic CSI reporting, the base station can request CSI reports. The base station can command the wireless device to measure configured CSI-RS resources and provide CSI reports related to the measurements. For semi-persistent CSI reporting, the base station can configure the wireless device to periodically send / transmit periodic reports and selectively activate or deactivate periodic reports (e.g., via one or more activation / deactivation MAC CEs and / or one or more DCIs). The base station can, for example, use RRC signaling to configure the CSI-RS resource set and CSI reports for the wireless device.

[0133] CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports (or any other number of antenna ports). The radio device can be configured, for example, to use / adopt the same OFDM symbols for both the downlink CSI-RS and CORESET if the downlink CSI-RS and CORESET are quasi-co-located spatially and the resource elements associated with the downlink CSI-RS are outside the physical resource block (PRB) configured for the CORESET. The radio device can also be configured, for example, to use / adopt the same OFDM symbols for both the downlink CSI-RS and SS / PBCH blocks if the downlink CSI-RS and SS / PBCH blocks are quasi-co-located spatially and the resource elements associated with the downlink CSI-RS are outside the PRB configured for the SS / PBCH blocks.

[0134] Downlink DM-RS can be transmitted / transmitted by the base station and received / used by the radio device for channel estimation. Downlink DM-RS can be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). The network (e.g., NR network) can support one or more variable and / or configurable DM-RS modes for data demodulation. At least one downlink DM-RS configuration can support a frontload DM-RS mode. Frontload DM-RS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station can semi-statically configure a certain number / quantity (e.g., maximum number / quantity) of frontload DM-RS symbols for PDSCH for the radio device. A DM-RS configuration can support one or more DM-RS ports. A DM-RS configuration can support up to eight orthogonal downlink DM-RS ports per radio device (e.g., for single-user MIMO). A DM-RS configuration can support up to four orthogonal downlink DM-RS ports per radio device (e.g., for multi-user MIMO). Radio networks can support (e.g., at least for CP-OFDM) a common DM-RS structure for both downlink and uplink. DM-RS locations, DM-RS modes, and / or scrambling sequences can be the same or different. Base stations can, for example, use the same precoding matrix to transmit / transmit downlink DM-RS and the corresponding PDSCH. Radio devices can use one or more downlink DM-RS to perform coherent demodulation / channel estimation of the PDSCH.

[0135] A transmitter (e.g., a transmitter at a base station) may use a precoder matrix for a portion of the transmission bandwidth. The transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. For example, the first and second precoder matrices may differ based on the difference between the first and second bandwidths. The wireless device may assume that the same precoding matrix is ​​used across PRB sets. This PRB set may be identified / indicated / identified / represented as a Precoded Resource Block Group (PRG).

[0136] The PDSCH may include one or more layers. The radio device may assume that at least one symbol with a DM-RS exists on one or more layers of the PDSCH. Higher layers may configure one or more DM-RSs of the PDSCH (e.g., up to three DMRSs of the PDSCH). Downlink PT-RS may be transmitted / transmitted by the base station and used by the radio device, for example, for phase-noise compensation. The presence of downlink PT-RS may depend on RRC configuration. The presence and / or mode of downlink PT-RS may be configured on a radio device-specific basis, for example, using RRC signaling and / or a combination of one or more parameters that may be indicated by the DCI for other purposes (e.g., modulation and coding scheme (MCS)). If configured, the dynamic presence of downlink PT-RS may be associated with one or more DCI parameters including at least one MCS. The network (e.g., an NR network) may support multiple PT-RS densities defined in the time and / or frequency domains. Frequency domain density (if configured / existing) may be associated with at least one configuration of scheduled bandwidth. The wireless device may assume that the precoding of the DM-RS ports and PT-RS ports is the same. The number of PT-RS ports may be less than the number of DM-RS ports in the scheduled resources. Downlink PT-RS can be configured / allocated / constrained within the time / frequency duration scheduled by the wireless device. Downlink PT-RS can be transmitted / transmitted via symbols, for example, to facilitate phase tracking at the receiver.

[0137] A wireless device can transmit / transmit uplink DM-RS to a base station, for example, for channel estimation. The base station can use the uplink DM-RS to coherently demodulate one or more uplink physical channels. The wireless device can transmit / transmit uplink DM-RS using PUSCH and / or PUCCH. The uplink DM-RS can span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station can configure the wireless device with one or more uplink DM-RS configurations. At least one DM-RS configuration can support a frontload DM-RS mode. Frontload DM-RS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DM-RS can be configured to transmit / transmit one or more symbols of PUSCH and / or PUCCH. The base station can semi-statically configure a certain number / quantity (e.g., a maximum number / quantity) of frontload DM-RS for PUSCH and / or PUCCH for the wireless device, which the wireless device can use to schedule single-symbol DM-RS and / or dual-symbol DM-RS. The network (e.g., an NR network) can support (e.g., for Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM)) a common DM-RS structure for both downlink and uplink. The DM-RS location, DM-RS mode, and / or scrambling sequence can be substantially the same or different.

[0138] The PUSCH may include one or more layers. A radio device may transmit / transmit at least one symbol with a DM-RS on one or more layers of the PDSCH. Higher layers may configure one or more DM-RSs of the PUSCH (e.g., up to three DMRSs). For example, depending on the radio device's RRC configuration, an uplink PT-RS (which may be used by the base station for phase tracking and / or phase-noise compensation) may or may not be present. The presence and / or mode of the uplink PT-RS may be configured on a radio device-specific basis (e.g., UE-specific basis), for example, through a combination of one or more parameters that may be indicated by the DCI for other purposes (e.g., MCS). If configured, the dynamic presence of the uplink PT-RS may be associated with one or more DCI parameters including at least an MCS. The radio network may support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency domain density (if configured / existing) may be associated with at least one configuration of the scheduled bandwidth. The radio device may assume that the precoding of the DM-RS port and the PT-RS port is the same. The number of PT-RS ports can be less than the number of DM-RS ports in the scheduled resources. Uplink PT-RS can be configured, allocated, and constrained during the scheduling time / frequency duration of the wireless device.

[0139] One or more SRSs can be transmitted / transmitted by a radio device to a base station, for example, to perform channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted / transmitted by the radio device enables / allows the base station to estimate the uplink channel state at one or more frequencies. The scheduler at the base station can use / adopt the estimated uplink channel state to allocate one or more resource blocks for uplink PUSCH transmissions by the radio device. The base station can semi-statically configure one or more SRS resource sets for the radio device. For each SRS resource set, the base station can configure one or more SRS resources for the radio device. The suitability of an SRS resource set can be configured, for example, through higher-layer (e.g., RRC) parameters. For example, if the higher-layer parameters indicate beam management, SRS resources in one or more SRS resource sets (e.g., having the same / similar temporal behavior, periodicity, aperiodicity, etc.) can be transmitted / transmitted at some time (e.g., simultaneously). The radio device can transmit / transmit one or more SRS resources from the SRS resource set. The network (e.g., an NR network) can support aperiodic, periodic, and / or semi-persistent SRS transmissions. A wireless device may transmit / transmit SRS resources, for example, based on one or more trigger types. One or more trigger types may include higher-layer signaling (e.g., RRC) and / or one or more DCI formats. At least one DCI format may be used / embedded for the wireless device to select at least one of one or more configured sets of SRS resources. SRS trigger type 0 may refer to SRS triggered based on higher-layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. The wireless device may be configured to, for example, transmit / transmit SRS after the transmission of the PUSCH and the corresponding uplink DM-RS if the PUSCH and SRS are transmitted / transmitted in the same time slot. The base station can semi-statically configure the radio device using one or more SRS configuration parameters indicating at least one of the following: SRS resource configuration identifier; number of SRS ports; temporal behavior of SRS resource configuration (e.g., indication of periodic, semi-persistent, or aperiodic SRS); periodicity at the time slot, micro-time slot, and / or subframe level; offset of periodic and / or aperiodic SRS resources; number of OFDM symbols in SRS resources; starting OFDM symbols for SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0140] Antenna ports can be determined / defined such that the channel transmitting a symbol on the same antenna port can be inferred from the channel transmitting another symbol on that antenna port. For example, if a first symbol and a second symbol are transmitted / transmitted on the same antenna port, the receiver can infer / determine the channel (e.g., attenuation gain, multipath delay, etc.) for transmitting the second symbol on the antenna port from the channel used to transmit the first symbol on that antenna port. For example, if one or more large-scale properties can be inferred from the channel transmitting the second symbol on the second antenna port to the channel transmitting the first symbol on that antenna port, then the first antenna port and the second antenna port can be referred to as quasi-co-located (QCL). The one or more large-scale properties can include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial reception (Rx) parameters.

[0141] Channels using beamforming may require beam management. Beam management may include beam measurement, beam selection, and / or beam indication. A beam may be associated with one or more reference signals. A beam may be identified by one or more beamforming reference signals. A wireless device may, for example, perform downlink beam measurements and generate a beam measurement report based on one or more downlink reference signals (e.g., CSI-RS). A wireless device may, for example, perform a downlink beam measurement procedure after establishing an RRC connection with a base station.

[0142] Figure 11B An exemplary mapping of one or more CSI-RS is shown. CSI-RS can be mapped in both the time and frequency domains. Figure 11BEach rectangular block shown may correspond to a resource block (RB) within the cell's bandwidth. The base station may send / transmit one or more RRC messages, which include CSI-RS resource configuration parameters indicating one or more CSI-RS. One or more of these parameters may be configured via higher-layer signaling (e.g., RRC and / or MAC signaling) used for CSI-RS resource configuration. One or more of the parameters may include at least one of the following: CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., the position of symbols and resource elements (REs) in a subframe), CSI-RS subframe configuration (e.g., the position, offset, and periodicity of the subframe in a radio frame), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmission comb, quasi-co-address (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0143] One or more beams can be configured for a wireless device in a specific configuration. Figure 11B Three beams (beam #1, beam #2, and beam #3) are shown, but more or fewer beams can be configured. Beam #1 can be assigned CSI-RS 1101, which can be transmitted / transmitted on one or more subcarriers in the RB of the first symbol. Beam #2 can be assigned CSI-RS 1102, which can be transmitted / transmitted on one or more subcarriers in the RB of the second symbol. Beam #3 can be assigned CSI-RS 1103, which can be transmitted / transmitted on one or more subcarriers in the RB of the third symbol. For example, by using frequency division multiplexing (FDM), the base station can use other subcarriers in the same RB (e.g., subcarriers not used for transmitting / transmitting CSI-RS 1101) to transmit another CSI-RS associated with the beam of another wireless device. For example, by using time domain multiplexing (TDM), the beam for the wireless device can be configured such that the beam for the wireless device uses a different symbol than the beams of other wireless devices. For example, by using TDM, a wireless device can be served with beams in orthogonal symbols (e.g., without overlapping symbols).

[0144] CSI-RS (e.g., CSI-RS 1101, 1102, 1103) can be sent / transmitted by a base station and used by a wireless device for one or more measurements. The wireless device can measure the RSRP of the configured CSI-RS resources. The base station can configure the wireless device using a reporting configuration, and the wireless device can report RSRP measurements (e.g., via one or more base stations) to the network based on the reporting configuration. The base station can determine one or more Transmission Configuration Indication (TCI) states, including multiple reference signals, based on the reported measurement results. The base station can indicate one or more TCI states to the wireless device (e.g., via RRC signaling, MAC CE, and / or DCI). The wireless device can receive downlink transmissions with Rx beams determined based on one or more TCI states. The wireless device may or may not have beam mapping capability. If the wireless device has beam mapping capability, it can determine the spatial filter of the transmission (Tx) beam, for example, based on the spatial filter corresponding to the Rx beam. For example, if the wireless device lacks beamforming capability, it can perform an uplink beam selection procedure to determine the spatial filter for the Tx beam. The wireless device can perform the uplink beam selection procedure, for example, based on one or more Sounding Reference Signal (SRS) resources configured for it by the base station. The base station can, for example, select and indicate the uplink beam of the wireless device based on measurements of one or more SRS resources transmitted / transmitted by the wireless device.

[0145] A wireless device can, for example, determine / evaluate (e.g., measure) the channel quality of one or more beampup links in a beam management procedure. A beampup link may include a base station's Tx beam and a wireless device's Rx beam. The base station's Tx beam can transmit / transmit downlink signals, and the wireless device's Rx beam can receive downlink signals. The wireless device can, for example, transmit / transmit a beam measurement report based on the evaluation / determination. The beam measurement report may indicate one or more beampup quality parameters, said one or more beampup quality parameters including at least one of the following: one or more beam identifiers (e.g., beam index, reference signal index, etc.), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or ranking indicator (RI).

[0146] Figure 12AAn example of a downlink beam management procedure is shown. One or more downlink beam management procedures (e.g., downlink beam management procedures P1, P2, and P3) can be executed. Procedure P1 can enable measurements (e.g., wireless device measurements) on the Tx beams of a TRP (or multiple TRPs) (e.g., to support the selection of one or more base station Tx beams and / or wireless device Rx beams). The base station Tx beams and the wireless device Rx beams are displayed as ellipses in the top and bottom rows of P1, respectively. Beamforming (e.g., at the TRP) can include Tx beam sweeping for a beam set (e.g., beam sweeping displayed as ellipses in the top rows of P1 and P2 rotates in a counterclockwise direction indicated by the dashed arrows). Beamforming (e.g., at the wireless device) can include Rx beam sweeping for a beam set (e.g., beam sweeping displayed as ellipses in the bottom rows of P1 and P3 rotates in a clockwise direction indicated by the dashed arrows). Procedure P2 can be used for measurements on the Tx beam that enable TRP (e.g., wireless device measurements) (displayed in the top row of P2 as an ellipse rotating counterclockwise in the direction indicated by the dashed arrow). The wireless device and / or base station can perform procedure P2, for example, using a smaller beam set than that used in procedure P1, or using a narrower beam than that used in procedure P1. Procedure P2 can be referred to as beam refinement. The wireless device can perform procedure P3 for Rx beam determination, for example, by using the same Tx beam of the base station and sweeping the Rx beam of the wireless device.

[0147] Figure 12BAn example of an uplink beam management procedure is shown. One or more uplink beam management procedures (e.g., uplink beam management procedures U1, U2, and U3) can be executed. Procedure U1 can be used to enable a base station to perform measurements on the Tx beam of a wireless device (e.g., to support the selection of one or more Tx beams of the wireless device and / or the Rx beam of the base station). The Tx beam of the wireless device and the Rx beam of the base station are shown as ellipses in the top and bottom rows of U1, respectively. Beamforming (e.g., at the wireless device) can include one or more beam sweeps, such as Tx beam sweeps from a beam set (shown as ellipses rotating clockwise in the bottom rows of U1 and U3, indicated by dashed arrows). Beamforming (e.g., at the base station) can include one or more beam sweeps, such as Rx beam sweeps from a beam set (shown as ellipses rotating counterclockwise in the top rows of U1 and U2, indicated by dashed arrows). For example, if the UE uses a fixed Tx beam, procedure U2 can be used to enable the base station to adjust its Rx beam. The radio device and / or base station may execute procedure U2, for example, using a smaller beam set than that used in procedure P1, or using a narrower beam than that used in procedure P1. Procedure U2 may be referred to as beam refinement. For example, if the base station uses a fixed Rx beam, the radio device may execute procedure U3 to adjust its Tx beam.

[0148] A wireless device can, for example, initiate / start / execute a beam failure recovery (BFR) procedure based on the detection of a beam failure. The wireless device can, for example, send / transmit a BFR request (e.g., preamble, UCI, SR, MACCE, etc.) based on initiating a BFR procedure. The wireless device can, for example, detect a beam failure based on determining that the quality of the beam pair link of the associated control channel is unsatisfactory (e.g., an error rate higher than an error rate threshold, received signal power lower than a received signal power threshold, timer expiration, etc.).

[0149] A wireless device may, for example, use one or more reference signals (RS) to measure the quality of a beamp-link, said one or more reference signals including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more DM-RS. The quality of the beamp-link may be based on one or more of the following: block error rate (BLER), RSRP value, signal-to-noise-interference ratio (SINR) value, RSRQ value, and / or CSI value measured on the RS resources. A base station may indicate quasi-co-location of the RS resources with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, etc.). For example, if the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, attenuation, etc.) from transmissions to the wireless device via the RS resources are similar to or the same as the channel characteristics from transmissions to the wireless device via the channel, then the RS resources of the channel and one or more DM-RSs may be quasi-co-located.

[0150] Networks (e.g., NR networks including gNBs and / or ng-eNBs) and / or radio devices can initiate / start / execute random access procedures. Radio devices in an RRC idle (e.g., RRC_IDLE) state and / or an RRC inactive (e.g., RRC_INACTIVE) state can initiate / execute random access procedures to request connection settings to the network. Radio devices can initiate / start / execute random access procedures from an RRC connected (e.g., RRC_CONNECTED) state. Radio devices can initiate / start / execute random access procedures to request uplink resources (e.g., for uplink transmission of SR in the absence of available PUCCH resources) and / or acquire / obtain / determine uplink timing (e.g., if the uplink synchronization state is not synchronized). Radio devices can initiate / start / execute random access procedures to request one or more System Information Blocks (SIBs) (e.g., other System Information Blocks, such as SIB2, SIB3, etc.). Radio devices can initiate / start / execute random access procedures for beam failure recovery requests. The network can initiate / start / execute random access procedures, such as for handover and / or for establishing SCell addition time alignments.

[0151] Figure 13AAn exemplary four-step random access procedure is illustrated. A four-step random access procedure may include four contention-based random access procedures. For example, before initiating a random access procedure, the base station may send / transmit configuration message 1310 to the wireless device. The four-step random access procedure may include the transmission of four messages, including: a first message (e.g., Msg 1 1311), a second message (e.g., Msg 2 1312), a third message (e.g., Msg 3 1313), and a fourth message (e.g., Msg 4 1314). The first message (e.g., Msg 1 1311) may include a preamble (or random access preamble). The first message (e.g., Msg 1 1311) may be referred to as a preamble. The second message (e.g., Msg 2 1312) may include a random access response (RAR). The second message (e.g., Msg 2 1312) may be referred to as a RAR.

[0152] For example, configuration message 1310 can be sent / transmitted using one or more RRC messages. One or more RRC messages can indicate one or more Random Access Channel (RACH) parameters to the radio device. One or more RACH parameters can include at least one of the following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station can send / transmit (e.g., broadcast or multicast) one or more RRC messages to one or more radio devices. One or more RRC messages can be radio device-specific. Radio device-specific one or more RRC messages can be dedicated RRC messages sent / transmitted to the radio device, for example, in an RRC connected (e.g., RRC_CONNECTED) state and / or an RRC inactive (e.g., RRC_INACTIVE) state. The radio device can determine the time-frequency resources and / or uplink transmission power for transmitting a first message (e.g., Msg 1 1311) and / or a third message (e.g., Msg 3 1313) based on one or more RACH parameters. The wireless device may determine the reception timing and the downlink channel for receiving the second message (e.g., Msg 2 1312) and the fourth message (e.g., Msg 4 1314) based, for example, one or more RACH parameters.

[0153] One or more RACH parameters provided / configured / included in configuration message 1310 may indicate one or more physical RACH (PRACH) timings available for transmitting the first message (e.g., Msg 1 1311). One or more PRACH timings may be predefined (e.g., by a network including one or more base stations). One or more RACH parameters may indicate one or more available sets of one or more PRACH timings (e.g., prach-ConfigIndex). One or more RACH parameters may indicate the association between (a) one or more PRACH timings and (b) one or more reference signals. One or more RACH parameters may indicate the association between (a) one or more preambles and (b) one or more reference signals. One or more reference signals may be SS / PBCH blocks and / or CSI-RS. One or more RACH parameters may indicate the amount / number of SS / PBCH blocks mapped to PRACH timings and / or the amount / number of preambles mapped to SS / PBCH blocks.

[0154] One or more RACH parameters provided / configured / included in configuration message 1310 can be used to determine the uplink transmission power of the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313). One or more RACH parameters can indicate a reference power (e.g., the received target power and / or the initial power of the preamble transmission) for the preamble transmission. One or more power offsets may exist, indicated by one or more RACH parameters. One or more RACH parameters can indicate: a power ramp step; a power offset between the SSB and CSI-RS; a power offset between the transmissions of the first message (e.g., Msg 1 1311) and the third message (e.g., Msg 3 1313); and / or a power offset value between preamble groups. One or more RACH parameters may indicate, for example, that a wireless device may use to determine one or more thresholds for at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., normal uplink (NUL) carrier and / or supplementary uplink (SUL) carrier).

[0155] The first message (e.g., Msg 1 1311) may include one or more preamble transmissions (e.g., preamble transmission and one or more preamble retransmissions). RRC messages can be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group may include one or more preambles. The wireless device may determine the preamble group, for example, based on path loss measurements and / or the magnitude of a third message (e.g., Msg 3 1313). The wireless device may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal with an RSRP higher than an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, if the association between one or more preambles and at least one reference signal is configured by an RRC message, the wireless device may select at least one preamble associated with one or more reference signals and / or the selected preamble group.

[0156] The wireless device may determine the preamble based, for example, on one or more RACH parameters provided / configured / included in configuration message 1310. The wireless device may determine the preamble based, for example, on path loss measurement (RSRP) and / or the magnitude of a third message (e.g., Msg 3 1313). One or more RACH parameters may indicate: the preamble format; the maximum amount / number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). The base station may use one or more RACH parameters to configure an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) for the wireless device. If such an association is configured, the wireless device may, for example, determine the preamble to be included in a first message (e.g., Msg 1 1311) based on this association. The first message (e.g., Msg 1 1311) may be sent / transmitted to the base station via one or more PRACH timings. The wireless device may use one or more reference signals (e.g., SSB and / or CSI-RS) to select the preamble and determine the PRACH timing. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) can indicate the association between the PRACH timing and one or more reference signals.

[0157] For example, if no response is received after (e.g., based on or in response to) a preamble transmission (e.g., within a period of time, such as a monitoring window for monitoring RAR), the wireless device can perform a preamble retransmission. The wireless device can increase the uplink transmission power used for the preamble retransmission. The wireless device can select the initial preamble transmission power, for example, based on path loss measurements and / or the target received preamble power configured by the network. The wireless device can determine to retransmit / re-transmit the preamble and can ramp up the uplink transmission power. The wireless device can receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramp step for the preamble retransmission. The ramp step can be the amount by which the uplink transmission power used for retransmission is incrementally increased. For example, if the wireless device determines that the same reference signal (e.g., SSB and / or CSI-RS) is used as in the previous preamble transmission, the wireless device can ramp up the uplink transmission power. The wireless device can, for example, use a counter parameter (e.g., PREAMBLE_TRANSMISSION_COUNTER) to calculate the amount / number of preamble transmissions and / or retransmissions. For example, if the amount / number of preamble transmissions exceeds a threshold configured by one or more RACH parameters (e.g., preambleTransMax) and no successful response (e.g., RAR) is received, the wireless device can determine that the random access procedure has not been successfully completed.

[0158] The second message (e.g., Msg 2 1312), received by a wireless device, may include a RAR. The second message (e.g., Msg 2 1312) may include multiple RARs corresponding to multiple wireless devices. The second message (e.g., Msg 2 1312) may be received, for example, after (e.g., based on or in response to) sending / transmitting the first message (e.g., Msg 1 1311). The second message (e.g., Msg 2 1312) may be scheduled on the DL-SCH and may be indicated by the PDCCH, for example, using a Random Access Radio Network Temporary Identifier (RA RNTI). The second message (e.g., Msg 2 1312) may indicate that the first message (e.g., Msg 1 1311) was received by the base station. The second message (e.g., Msg 2 1312) may include a time alignment command that the wireless device can use to adjust the transmission timing of the wireless device, a scheduling permission for transmitting the third message (e.g., Msg 3 1313), and / or a temporary cell RNTI (TC-RNTI). For example, after sending / transmitting the first message (e.g., Msg 1 1311) (e.g., a preamble), the wireless device may determine / start a time window (e.g., a ra-ResponseWindow) to monitor the PDCCH for the second message (e.g., Msg 2 1312). The wireless device may determine the start time of the time window, for example, based on the PRACH timing used by the wireless device to send / transmit the first message (e.g., Msg 1 1311) (e.g., a preamble). The radio device may initiate the time window at one or more symbols following the last symbol of the first message including the preamble (e.g., Msg 1 1311) (e.g., the symbol in which the first message including the preamble transmission (e.g., Msg 1 1311) is completed, or the first PDCCH timing after the end of the preamble transmission). One or more symbols may be determined based on a set of parameters. The PDCCH may be mapped in a common search space configured by RRC messages (e.g., a Type 1-PDCCH common search space). The radio device may identify / determine the RAR, for example, based on the RNTI. The Radio Network Temporary Identifier (RNTI) may be used based on one or more events that initiate / start a random access procedure. The radio device may use the RA-RNTI, for example, for one or more communications associated with random access or any other purpose. The RA-RNTI may be associated with the PRACH timing of the radio device transmitting / transmitting the preamble. The radio device may determine the RA-RNTI, for example, based on at least one of the following: OFDM symbol index; time slot index; frequency domain index; and / or the UL carrier indicator of the PRACH timing. An exemplary RA-RNTI can be determined as follows:

[0159] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

[0160] Wherein, s_id can be the index of the first OFDM symbol of the PRACH timing (e.g., 0 ≤ s_id < 14), t_id can be the index of the first slot of the PRACH timing in the system frame (e.g., 0 ≤ t_id < 80), f_id can be the index of the PRACH timing in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id can be the UL carrier used for preamble transmission (e.g., 0 for NUL carriers and 1 for SUL carriers).

[0161] A wireless device may send / transmit a third message (e.g., Msg 31313) after (e.g., based on or in response to) successfully receiving a second message (e.g., Msg 21312) (e.g., using the resources identified in Msg 2 1312). The third message (e.g., Msg 3 1313) can be used for contention resolution, for example, in a contention-based random access procedure. Multiple wireless devices may send / transmit the same preamble to a base station, and the base station may send / transmit a RAR corresponding to a wireless device. For example, a collision may occur if multiple wireless devices interpret the RAR as corresponding to themselves. Contention resolution (e.g., using a third message (e.g., Msg 3 1313) and a fourth message (e.g., Msg 4 1314)) can be used to increase the likelihood that a wireless device will not mistakenly use the identity of another wireless device. The wireless device may include a device identifier (e.g., C-RNTI (if assigned), TC RNTI included in a second message (e.g., Msg 3 1313), and / or any other suitable identifier) ​​in a third message (e.g., Msg 2 1312), for example, to perform contention resolution.

[0162] A fourth message (e.g., Msg 4 1314) can be received, for example, after (e.g., based on or in response to) sending / transmitting a third message (e.g., Msg 3 1313). For example, if a C-RNTI is included in the third message (e.g., Msg 3 1313), the base station can use the C-RNTI to address the radio device on the PDCCH (e.g., the base station can send the PDCCH to the radio device). For example, if a unique C RNTI of the radio device is detected on the PDCCH (e.g., the PDCCH is scrambled with the C-RNTI), it can be determined that the random access procedure was successfully completed. For example, if a TC RNTI is included in the third message (e.g., Msg 3 1313) (e.g., if the radio device is in an RRC idle (e.g., RRC_IDLE) state or is not connected to the base station for some reason), the fourth message (Msg 4 1314) can be received using the DL-SCH associated with the TC RNTI. For example, if the MAC PDU is successfully decoded and the MAC PDU includes a radio device contention resolution identity MAC CE that matches or otherwise corresponds to the CCCH SDU sent / transmitted in a third message (e.g., Msg 3 1313), the radio device can determine that the contention resolution was successful and / or the radio device can determine that the random access procedure was successfully completed.

[0163] The radio device can be configured with SUL carriers and / or NUL carriers. Initial access (e.g., random access) can be supported via an uplink carrier. The base station can configure the radio device using multiple RACH configurations (e.g., two independent RACH configurations, including one for an SUL carrier and another for an NUL carrier). For random access in a cell configured with an SUL carrier, the network can indicate which carrier (NUL or SUL) to use. For example, if the measured quality of one or more reference signals (e.g., one or more reference signals associated with an NUL carrier) is below a broadcast threshold, the radio device can determine to use an SUL carrier. Uplink transmissions of the random access procedure (e.g., a first message (e.g., Msg 1 1311) and / or a third message (e.g., Msg 3 1313)) can be maintained on the selected carrier or can be performed via the selected carrier. The radio device can switch uplink carriers during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). The wireless device may determine and / or switch uplink carriers for the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313) based, for example, on channel idle assessment (e.g., listen-before-speak).

[0164] Figure 13BA two-step random access procedure is illustrated. A two-step random access procedure may include a two-step contention-free random access procedure. Similar to a four-step contention-based random access procedure, the base station may send / transmit configuration message 1320 to the radio device before the procedure is initiated. Configuration message 1320 may be similar in some respects to configuration message 1310. Figure 13B The procedure shown may include the transmission of two messages: a first message (e.g., Msg 1 1321) and a second message (e.g., Msg 2 1322). The first message (e.g., Msg 1 1321) and the second message (e.g., Msg 2 1322) may be similar in some respects to the first message (e.g., Msg 1 1311) and the second message (e.g., Msg 2 1312), respectively. The two-step contention-free random access procedure may not include messages similar to a third message (e.g., Msg 3 1313) and / or a fourth message (e.g., Msg 4 1314).

[0165] A two-step (e.g., contention-free) random access procedure can be configured / initiated for beam failure recovery, additional SI requests, SCell addition, and / or handover. The base station can indicate or assign a preamble to the radio device for the first message (e.g., Msg 11321). The radio device can receive the preamble indication (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0166] For example, after (e.g., based on or in response to) the transmission / transmission of a preamble, the radio device can initiate a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for RAR. The base station can configure one or more beam failure recovery parameters for the radio device, which are, for example, independent time windows and / or independent PDCCHs in a search space (e.g., recoverySearchSpaceId) indicated by an RRC message. The base station can configure one or more beam failure recovery parameters, for example, in conjunction with a beam failure recovery request. The independent time window for monitoring the PDCCH and / or RAR can be configured to initiate after the transmission / transmission of a beam failure recovery request (e.g., the window can initiate with any number of symbols and / or time slots after the transmission of the beam failure recovery request). The radio device can monitor PDCCH transmissions with addresses pointing to CellRNTI (C-RNTI) in the search space. During a two-step (e.g., contention-free) random access procedure, for example, after (e.g., based on or in response to) transmitting a first message (e.g., Msg 1 1321) and receiving a corresponding second message (e.g., Msg 2 1322), the wireless device can determine that the random access procedure was successful. For example, if the PDCCH transmission address points to the corresponding C-RNTI, the wireless device can determine that the random access procedure has been successfully completed. For example, if the wireless device receives a RAR including a preamble identifier corresponding to the preamble transmitted / transmitted by the wireless device, and / or the RAR includes a MAC sub-PDU with the preamble identifier, the wireless device can determine that the random access procedure has been successfully completed. The wireless device can determine the response as an indication of acknowledgment of the SI request.

[0167] Figure 13C An exemplary two-step random access procedure is shown. Similar to... Figure 13A and 13B In the random access procedure shown, the base station may send / transmit configuration message 1330 to the wireless device before the procedure is initiated. Configuration message 1330 may be similar in some respects to configuration message 1310 and / or configuration message 1320. Figure 13C The program shown may include the transmission of multiple messages (e.g., two messages, including: a first message (e.g., Msg A 1331) and a second message (e.g., Msg B 1332)).

[0168] Msg A 1320 can be sent / transmitted in the uplink transmission of a wireless device. Msg A 1320 may include one or more transmissions of preamble 1341 and / or one or more transmissions of transport block 1342. Transport block 1342 may include the content of a third message (e.g., Msg 3 1313) (e.g., ...). Figure 13ASimilar or equivalent content to (as shown in the diagram). Transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, etc.). The wireless device may receive a second message (e.g., Msg B 1332) after sending / transmitting a first message (e.g., based on or in response to) the first message (e.g., Msg A 1331). The second message (e.g., Msg B 1332) may include content similar to that of the second message (e.g., Msg 2 1312) (e.g., ...). Figure 13A The content of the second message (e.g., Msg 2 1322) shown in the RAR) Figure 13B The contents of the RAR (as shown) and / or the fourth message (e.g., Msg 4 1314) (e.g., Figure 13A Similar and / or equivalent content (as shown in the image).

[0169] Wireless devices can initiate / propose a two-step random access procedure for licensed and / or unlicensed spectrum (e.g., Figure 13C (The two-step random access procedure is shown in the diagram). A radio device may determine whether to initiate / initiate a two-step random access procedure based on one or more factors. One or more factors may include at least one of the following: the radio access technology in use (e.g., LTE, NR, etc.); whether the radio device has a valid TA; cell size; the RRC status of the radio device; spectrum type (e.g., licensed vs. unlicensed); and / or any other suitable factors.

[0170] The wireless device can determine the radio resources and / or uplink transmission power for preamble 1341 and / or transport block 1342 based on the two-step RACH parameters included in configuration message 1330 (e.g., included in the first message (e.g., Msg A 1331)). The RACH parameters can indicate the MCS, time-frequency resources, and / or power control for preamble 1341 and / or transport block 1342. The time-frequency resources (e.g., PRACH) for transmitting preamble 1341 and the time-frequency resources (e.g., PUSCH) for transmitting transport block 1342 can be multiplexed using FDM, TDM, and / or CDM. The RACH parameters enable the wireless device to determine the reception timing and the downlink channel for monitoring and / or receiving the second message (e.g., Msg B 1332).

[0171] Transport block 1342 may include data (e.g., delay-sensitive data), a radio device identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may send / transmit a second message (e.g., MsgB 1332) as a response to the first message (e.g., Msg A 1331). The second message (e.g., Msg B 1332) may include at least one of the following: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., radio resource allocation and / or MCS); a radio device identifier (e.g., a UE identifier for contention resolution); and / or an RNTI (e.g., a C-RNTI or TC-RNTI). For example, if the preamble identifier in the second message (e.g., Msg B 1332) corresponds to or matches the preamble sent / transmitted by the wireless device, and / or the wireless device identifier in the second message (e.g., Msg B 1332) corresponds to or matches the wireless device identifier in the first message (e.g., Msg A 1331) (e.g., transport block 1342), then the wireless device can determine that the two-step random access procedure has been successfully completed.

[0172] The wireless device and the base station can exchange control signaling (e.g., control information). This control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., Layer 1) and / or MAC layer (e.g., Layer 2) of the wireless device or base station. Control signaling may include downlink control signaling sent / transmitted from the base station to the wireless device and / or uplink control signaling sent / transmitted from the wireless device to the base station.

[0173] Downlink control signaling may include at least one of the following: downlink scheduling allocation; uplink scheduling grants indicating uplink radio resources and / or transmission formats; time slot format information; pre-occupancy indications; power control commands; and / or any other suitable signaling. Radio devices can receive downlink control signaling in payloads transmitted / transmitted by the base station via the PDCCH. The payload transmitted / transmitted via the PDCCH may be referred to as downlink control information (DCI). The PDCCH may be a group common PDCCH (GC-PDCCH) shared by a group of radio devices. The GC-PDCCH may be scrambled by a group common RNTI.

[0174] For example, a base station can attach one or more Cyclic Redundancy Check (CRC) parity bits to a DCI to facilitate the detection of transmission errors. For instance, if the DCI is intended for a wireless device (or a group of wireless devices), the base station can scramble the CRC parity bits with the identifier of the wireless device (or the identifier of the group of wireless devices). Scrambling the CRC parity bits with an identifier can include a Modulo-2 addition (or XOR operation) of the identifier value and the CRC parity bits. The identifier can include a 16-bit value of the RNTI.

[0175] DCIs can be used for various purposes. The purpose can be indicated by the type of RNTI used to scramble the CRC parity bits. A DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) can indicate paging information and / or system information change notifications. A P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) can indicate broadcast transmission of system information. A SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) can indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) can indicate dynamically scheduled unicast transmissions and / or triggering of PDCCH ordered random access. A DCI with CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to...). Figure 13A The Msg 3 shown is Msg 3 of 1313. Other RNTIs configured by the base station for the radio device may include: configured scheduling RNTI (CS RNTI), transmission power control - PUCCH RNTI (TPCPUCCH-RNTI), transmission power control - PUSCH RNTI (TPC-PUSCH-RNTI), transmission power control - SRS RNTI (TPC-SRS-RNTI), interrupt RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), modulation and coding scheme cell RNTI (MCS-C RNTI), etc.

[0176] For example, depending on the purpose and / or content of the DCI, a base station may send / transmit a DCI with one or more DCI formats. DCI format 0_0 can be used to schedule PUSCH in a cell. DCI format 0_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​can be used to schedule PUSCH in a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 can be used to schedule PDSCH in a cell. DCI format 1_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 can be used to schedule PDSCH in a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 can be used to provide a slot format indication to a group of radio devices. DCI format 2_1 can be used to notify / inform a group of radio devices of physical resource blocks and / or OFDM symbols, where the group of radio devices may assume there are no transmissions directed to that group of radio devices. DCI format 2_2 can be used to transmit Transmit Power Control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 can be used to transmit a set of TPC commands for SRS transmission by one or more wireless devices. New DCI formats with new features can be defined in future versions. DCI formats can have different DCI sizes, or they can share the same DCI size.

[0177] For example, after scrambling the DCI with RNTI, the base station can process the DCI using channel coding (e.g., polarity coding), rate matching, scrambling, and / or QPSK modulation. The base station can map the coded and modulated DCI onto resource elements used and / or configured for the PDCCH. The base station can transmit / transmit the DCI via a PDCCH occupying multiple consecutive control channel elements (CCEs), for example, based on the DCI payload size and / or the base station's coverage. The number of consecutive CCEs (referred to as the aggregation level) can be 1, 2, 4, 8, 16, and / or any other suitable number. A CCE can include several (e.g., 6) resource element groups (REGs). REGs can include resource blocks in OFDM symbols. The mapping of the coded and modulated DCI onto resource elements can be based on the mapping between CCEs and REGs (e.g., CCE-to-REG mapping).

[0178] Figure 14AAn example of a CORESET configuration is shown. CORESET configuration can be for a bandwidth portion or any other frequency band. A base station can transmit / transmit DCI via PDCCH on one or more control resource sets (CORESETs). A CORESET can include time-frequency resources, where a radio device attempts to decode the DCI using one or more search spaces. The base station can configure the size and location of the CORESET in the time-frequency domain. A first CORESET 1401 and a second CORESET 1402 can occur or be set / configured at the first symbol of a time slot. The first CORESET 1401 can overlap with the second CORESET 1402 in the frequency domain. A third CORESET 1403 can occur or be set / configured at the third symbol of a time slot. A fourth CORESET 1404 can occur or be set / configured at the seventh symbol of a time slot. CORESETs can have different numbers of resource blocks in the frequency domain.

[0179] Figure 14B An example of CCE-to-REG mapping is shown. CCE-to-REG mapping can be performed for DCI transmissions via CORESET and PDCCH processing. CCE-to-REG mapping can be interleaved mapping (e.g., for the purpose of providing frequency diversity) or non-interleaved mapping (e.g., for the purpose of facilitating interference coordination and / or frequency-selective transmission in the control channel). The base station can perform different or the same CCE-to-REG mappings for different CORESETs. CORESETs can be associated with CCE-to-REG mappings (e.g., via RRC configuration). CORESETs can be configured with antenna port QCL parameters. Antenna port QCL parameters can indicate the QCL information of DM-RS for PDCCH reception via the CORESET.

[0180] A base station can send / transmit one or more RRC messages to a radio device, the one or more RRC messages including configuration parameters for one or more CORESETs and one or more search space sets. The configuration parameters can indicate the association between the search space set and the CORESET. The search space set can include a set of PDCCH candidates formed by CCEs (e.g., at a given aggregation level). The configuration parameters can indicate at least one of the following: the number of PDCCH candidates to be monitored at each aggregation level; the PDCCH monitoring periodicity and PDCCH monitoring mode; one or more DCI formats to be monitored by the radio device; and / or whether the search space set is a common search space set or a radio device-specific search space set (e.g., a UE-specific search space set). The radio device can predefine and know the CCE set in the common search space set. The CCE set in the radio device-specific search space set (e.g., a UE-specific search space set) can be configured, for example, based on the radio device's identity (e.g., C-RNTI).

[0181] like Figure 14B As shown, the wireless device can determine the time-frequency resources of a CORESET based on one or more RRC messages. The wireless device can determine, for example, the CCE-to-REG mapping of the CORESET (e.g., interleaved or uninterleaved and / or mapping parameters) based on the CORESET's configuration parameters. The wireless device can determine, for example, the number of search space sets configured on / for the CORESET (e.g., up to 10) based on one or more RRC messages. The wireless device can monitor a set of PDCCH candidates based on the configuration parameters of the search space sets. The wireless device can monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring can include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI format. Monitoring can include decoding the DCI content of one or more PDCCH candidates, which has possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in the common search space, and / or the number of PDCCH candidates in the wireless device-specific search space), and possible (or configured) DCI formats. This decoding can be referred to as blind decoding. For example, after (e.g., based on or in response to) a CRC check (e.g., scrambling bits of the CRC parity bits of the DCI that match the RNTI value), the wireless device can determine that the DCI is valid for the wireless device. The wireless device can process the information included in the DCI (e.g., scheduling allocation, uplink grant, power control, timeslot format indication, downlink pre-occupancy, etc.).

[0182] The wireless device can send / transmit uplink control signaling (e.g., UCI) to the base station. Uplink control signaling may include HARQ acknowledgments for received DL-SCH transport blocks. The wireless device may send / transmit HARQ acknowledgments, for example, after (e.g., based on or in response to) receiving a DL-SCH transport block. Uplink control signaling may include a Channel Quality Indicator (CSI) indicating the channel quality of the physical downlink channel. The wireless device may send / transmit the CSI to the base station. Based on the received CSI, the base station may determine transmission format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission. Uplink control signaling may include a Schedule Request (SR). The wireless device may send / transmit an SR indicating that uplink data is available for transmission to the base station. The wireless device may send / transmit UCIs (e.g., HARQ acknowledgments, CSI reports, SRs, etc.) via PUCCH or PUSCH. The wireless device may use one of several PUCCH formats to send / transmit uplink control signals via PUCCH.

[0183] Multiple PUCCH formats can exist (e.g., five PUCCH formats). A radio device can determine the PUCCH format, for example, based on the size of the UCI (e.g., the amount / number of uplink symbols transmitted in the UCI and the number of UCI bits). PUCCH format 0 can have a length of one or two OFDM symbols and can include two or fewer bits. If the transmission passes through / via one or two symbols and the amount / number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits) is one or two, the radio device can, for example, use PUCCH format 0 to transmit / transmit the UCI via PUCCH resources. PUCCH format 1 can occupy a number of OFDM symbols (e.g., between four and fourteen OFDM symbols) and can include two or fewer bits. For example, if the transmission passes through / via four or more symbols and the number of HARQ-ACK / SR bits is one or two, the radio device can use PUCCH format 1. PUCCH format 2 can occupy one or two OFDM symbols and can include more than two bits. For example, if the transmission passes through / via one or two symbols and the number of UCI bits is two or more, the wireless device can use PUCCH format 2. PUCCH format 3 can occupy a number of OFDM symbols (e.g., between four and fourteen OFDM symbols) and can include more than two bits. For example, if the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal coverage code (OCC), the wireless device can use PUCCH format 3. PUCCH format 4 can occupy a number of OFDM symbols (e.g., between four and fourteen OFDM symbols) and can include more than two bits. For example, if the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource includes an OCC, the wireless device can use PUCCH format 4.

[0184] The base station can, for example, use RRC messages to send / transmit configuration parameters of multiple PUCCH resource sets to the radio device. Multiple PUCCH resource sets can be configured on the cell's uplink BWP (e.g., up to four sets in NR, or up to any other number of sets in other systems). A PUCCH resource set can be configured with a PUCCH resource set index, multiple PUCCH resources identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and / or the number of UCI information bits (e.g., a maximum number) that the radio device can use to send / transmit one of the multiple PUCCH resources in the PUCCH resource set. If multiple PUCCH resource sets are configured, the radio device can, for example, select one of the multiple PUCCH resource sets based on the total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). For example, if the total bit length of the UCI information bits is two or fewer, the radio device can select the first PUCCH resource set with a PUCCH resource set index equal to "0". For example, if the total bit length of the UCI information bits is greater than two and less than or equal to the first configuration value, the radio device can select a second PUCCH resource set with a PUCCH resource set index equal to "1". For example, if the total bit length of the UCI information bits is greater than the first configuration value and less than or equal to the second configuration value, the radio device can select a third PUCCH resource set with a PUCCH resource set index equal to "2". For example, if the total bit length of the UCI information bits is greater than the second configuration value and less than or equal to a third value (e.g., 1406, 1706, or any other number of bits), the radio device can select a fourth PUCCH resource set with a PUCCH resource set index equal to "3".

[0185] A wireless device may, for example, determine a PUCCH resource set from multiple PUCCH resource sets, and then determine the PUCCH resource for UCI (HARQ-ACK, CSI, and / or SR) transmission from the PUCCH resource set. The wireless device may determine the PUCCH resource based, for example, on a PUCCH resource indicator in a DCI (e.g., having DCI format 1_0, or a DCI for 1_1) received on / via the PDCCH. An n-bit (e.g., three-bit) PUCCH resource indicator in the DCI may indicate one of multiple (e.g., eight) PUCCH resources in the PUCCH resource set. The wireless device may, for example, transmit / transmit UCI (HARQ-ACK, CSI, and / or SR) using the PUCCH resource indicated by the PUCCH resource indicator in the DCI.

[0186] Figure 15AAn exemplary communication between a wireless device and a base station is illustrated. The wireless device 1502 and the base station 1504 may be part of a communication network, such as... Figure 1A The communication network 100 shown Figure 1B The communication network 150 shown may be any other communication network. The communication network may include more than one wireless device and / or more than one base station, having [equipment / features] with [other features]. Figure 15A The configurations shown are basically the same or similar.

[0187] Base station 1504 can connect wireless device 1502 to the core network (not shown) via radio communication through air interface (or radio interface) 1506. The communication direction from base station 1504 to wireless device 1502 via air interface 1506 can be referred to as the downlink. The communication direction from wireless device 1502 to base station 1504 via air interface 1506 can be referred to as the uplink. Downlink transmissions and uplink transmissions can be separated, for example, using various duplex schemes (e.g., some combination of FDD, TDD, and / or duplex technologies).

[0188] For the downlink, data transmitted from base station 1504 to wireless device 1502 can be provided / transmitted / sent to processing system 1508 of base station 1504. Data can be provided / transmitted / sent to processing system 1508 by, for example, the core network. For the uplink, data transmitted from wireless device 1502 to base station 1504 can be provided / transmitted / sent to processing system 1518 of wireless device 1502. Processing systems 1508 and 1518 can implement Layer 3 and Layer 2 OSI functions to process the data for transmission. Layer 2 may include SDAP, PDCP, RLC, and MAC layers, for example, regarding... Figure 2A , Figure 2B , Figure 3 and Figure 4A The third layer can include an RRC layer, for example, regarding... Figure 2B Described.

[0189] Data sent to wireless device 1502 may, for example, be provided / transmitted / sent to base station 1504 by transmission processing system 1510 after being processed by processing system 1508. Data sent to base station 1504 may, for example, be provided / transmitted / sent to wireless device 1502 by transmission processing system 1520 after being processed by processing system 1518. Transmission processing systems 1510 and 1520 may implement Layer 1 OSI functions. Layer 1 may include a PHY layer, for example, regarding... Figure 2A , Figure 2B , Figure 3 and Figure 4AThe description states that for transmit / transmission processing, the PHY layer can perform operations such as forward error correction coding of the transport channel, interleaving, rate matching, mapping of the transport channel to the physical channel, modulation of the physical channel, multiple-input multiple-output (MIMO) or multiple-antenna processing, etc.

[0190] The receiving and processing system 1512 of base station 1504 can receive uplink transmissions from wireless device 1502. The receiving and processing system 1512 of base station 1504 may include one or more TRPs. The receiving and processing system 1522 of wireless device 1502 can receive downlink transmissions from base station 1504. The receiving and processing system 1522 of wireless device 1502 may include one or more antenna panels. Receiving and processing systems 1512 and 1522 can implement Layer 1 OSI functions. Layer 1 may include the PHY layer, for example, regarding... Figure 2A , Figure 2B , Figure 3 and Figure 4A The description states that for receive processing, the PHY layer can perform tasks such as error detection, forward error correction decoding, deinterleaving, demapping of the transport channel to the physical channel, demodulation of the physical channel, MIMO or multi-antenna processing, etc.

[0191] Base station 1504 may include multiple antennas (e.g., multiple antenna panels, multiple TRPs, etc.). Wireless device 1502 may include multiple antennas (e.g., multiple antenna panels, etc.). Multiple antennas can be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. Wireless device 1502 and / or base station 1504 may have a single antenna.

[0192] Processing systems 1508 and 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code that may be executed by processing systems 1508 and / or 1518 to perform one or more functions (e.g., one or more functions described herein, and other functions of a general-purpose computer, processor, memory, and / or other peripheral devices). Transmission processing system 1510 and / or reception processing system 1512 may be coupled to memory 1514 and / or another memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or code that may be executed to perform one or more of their respective functions. Transmission processing system 1520 and / or reception processing system 1522 may be coupled to memory 1524 and / or another memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or code that may be executed to perform one or more of their respective functions.

[0193] Processing system 1508 and / or processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may include, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) and / or other programmable logic devices, discrete gate and / or transistor logic, discrete hardware components, on-board units, or any combination thereof. Processing system 1508 and / or processing system 1518 may perform at least one of the following functions: signal encoding / processing, data processing, power control, input / output processing, and / or any other function that enables wireless device 1502 and / or base station 1504 to operate in a wireless environment.

[0194] Processing system 1508 can be connected to one or more peripheral devices 1516. Processing system 1518 can be connected to one or more peripheral devices 1526. The one or more peripheral devices 1516 and one or more peripheral devices 1526 may include software and / or hardware providing features and / or functions, such as speakers, microphones, keypads, displays, touchpads, power supplies, satellite transceivers, universal serial bus (USB) ports, hands-free headsets, frequency modulation (FM) radio units, media players, internet browsers, electronic control units (e.g., for motor vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, lidar sensors, ultrasonic sensors, light sensors, cameras, etc.). Processing system 1508 and / or processing system 1518 can receive input data (e.g., user input data) from one or more peripheral devices 1516 and / or one or more peripheral devices 1526, and / or provide output data (e.g., user output data) to them. The processing system 1518 in the wireless device 1502 can receive power from a power source and / or can be configured to distribute power to other components in the wireless device 1502. The power source may include one or more power sources, such as a battery, solar cell, fuel cell, or any combination thereof. The processing system 1508 may be connected to a Global Positioning System (GPS) chipset 1517. The processing system 1518 may be connected to a Global Positioning System (GPS) chipset 1527. The GPS chipset 1517 and GPS chipset 1527 may be configured to determine and provide geographic location information for the wireless device 1502 and the base station 1504, respectively.

[0195] Figure 15BExemplary elements of a computing device are shown that can be used to implement any of the various devices described herein, including, for example, base stations 160A, 160B, 162A, 162B, 220, and / or 1504, wireless devices 106, 156A, 156B, 210, and / or 1502, or any other base station, wireless device, AMF, UPF, network device, or computing device described herein. The computing device 1530 may include one or more processors 1531 capable of executing instructions stored in random access memory (RAM) 1533, removable media 1534 (e.g., a Universal Serial Bus (USB) drive, optical disc (CD), or digital multi-disk (DVD) or floppy disk drive), or any other desired storage medium. Instructions may also be stored in an attached (or internal) hard disk drive 1535. The computing device 1530 may also include a security processor (not shown) that can execute instructions of one or more computer programs to monitor processes executing on the processor 1531 and any processes requesting access to any hardware and / or software components of the computing device 1530 (e.g., ROM 1532, RAM 1533, removable media 1534, hard disk drive 1535, device controller 1537, network interface 1539, GPS 1541, Bluetooth interface 1542, WiFi interface 1543, etc.). The computing device 1530 may include one or more output devices, such as a display 1536 (e.g., screen, display device, monitor, television, etc.), and may include one or more output device controllers 1537, such as a video processor. One or more user input devices 1538 may also be present, such as a remote control, keyboard, mouse, touchscreen, microphone, etc. The computing device 1530 may also include one or more network interfaces (e.g., network interface 1539), which may be a wired interface, a wireless interface, or a combination of both. Network interface 1539 can provide computing device 1530 with an interface to communicate with network 1540 (e.g., RAN or any other network). Network interface 1539 may include a modem (e.g., a cable modem), and external network 1540 may include a communication link, external network, home network, provider's wireless, coaxial, fiber, or hybrid fiber / coaxial distribution system (e.g., DOCSIS network), or any other desired network. Additionally, computing device 1530 may include a location detection device (e.g., a Global Positioning System (GPS) microprocessor 1541) that can be configured to receive and process GPS signals and determine the geographic location of computing device 1530 with possible assistance from external servers and antennas.

[0196] Figure 15BThe examples shown can be hardware configurations, but the components illustrated can also be implemented as software. Modifications can be made as needed to add, remove, combine, divide, etc., components of computing device 1530. Furthermore, basic computing devices and components can be used to implement components, and the same components (e.g., processor 1531, ROM storage device 1532, display 1536, etc.) can be used to implement any other computing devices and components described herein. For example, the various components described herein can be implemented using a computing device having components such as a processor that execute computer-executable instructions stored on a computer-readable medium, such as... Figure 15B As shown in the diagram. Some or all of the entities described herein may be software-based and may coexist on a common physical platform (e.g., the requesting entity may be a separate software process and program from a subordinate entity, both of which may execute as software on a common computing device).

[0197] Figure 16A An exemplary structure for uplink transmission is shown. Processing of the baseband signal representing the physical uplink shared channel may include / perform one or more functions. These one or more functions may include at least one of the following: scrambling; modulating the scrambling bits to generate complex-valued symbols; mapping the complex-valued modulated symbols onto one or more transport layers; performing transform precoding to generate complex-valued symbols; precoding the complex-valued symbols; mapping the precoded complex-valued symbols to resource elements; generating complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA), CP-OFDM signals, or any other signals for the antenna port; and so on. For example, if transform precoding is enabled, an SC-FDMA signal for uplink transmission can be generated. For example, if transform precoding is not enabled (e.g., as...), Figure 16A As shown in the diagram, CP-OFDM signals for uplink transmission can be generated. These functions are examples, and other mechanisms for uplink transmission can be implemented.

[0198] Figure 16B An exemplary structure for modulating and upconverting a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued SC-FDMA, CP-OFDM baseband signal (or any other baseband signal) and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal for the antenna port. Filtering can be performed / applied, for example, before transmission.

[0199] Figure 16CAn exemplary structure for downlink transmission is shown. Processing of the baseband signal representing the physical downlink channel may include / perform one or more functions. These functions may include: scrambling coded bits in a codeword to be transmitted / via the physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or more transport layers; precoding the complex-valued modulation symbols on the layers for transmission at the antenna port; mapping the complex-valued modulation symbols for the antenna port to resource elements; generating a complex-valued time-domain OFDM signal for the antenna port; and so on. These functions are examples, and other mechanisms for downlink transmission can be implemented.

[0200] Figure 16D An exemplary structure for modulating and upconverting a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued OFDM baseband signal for the antenna port or any other signal. Filtering can be performed / applied, for example, before transmission.

[0201] A wireless device can receive one or more messages (e.g., RRC messages) from a base station that include configuration parameters for multiple cells (e.g., a primary cell, one or more secondary cells). The wireless device can communicate with at least one base station (e.g., two or more base stations in dual connectivity) via the multiple cells. One or more messages (e.g., as part of the configuration parameters) may include parameters for configuring the PHY, MAC, RLC, PCDP, SDAP, and RRC layers of the wireless device. Configuration parameters may include parameters for configuring PHY and MAC layer channels, bearers, etc. Configuration parameters may include parameters indicating the values ​​of timers for the PHY, MAC, RLC, PCDP, SDAP, RRC layers, and / or communication channels.

[0202] For example, if started, a timer can begin running and continue running until it stops or expires. For example, if the timer is not running, it can be started, or if it is running, it can be restarted. A timer can be associated with a value (e.g., a timer can be started or restarted from a certain value, or it can be started from zero and expire if said value is reached). For example, the duration of a timer may not be updated until it stops or expires (e.g., due to a BWP switch). A timer can be used to measure a time period / window of a process. Regarding implementations and / or procedures related to one or more timers or other parameters, it should be understood that there can be multiple ways to implement one or more timers or other parameters. One or more of the multiple ways of implementing a timer can be used to measure a time period / window of a process. A random access response window timer can be used to measure the time window in which a random access response is received. For example, instead of starting a random access response window timer and determining its expiration, the time difference between two timestamps can be used. For example, if the timer is restarted, the process of measuring the time window can be restarted. Other exemplary implementations can be configured / provided to restart the measurement of the time window.

[0203] Wireless communication can utilize complementary access technologies. Complementary access technologies can include a combination of two or more access technologies. At least some types of wireless communication (e.g., compatible with 3GPP Release 16, earlier / later 3GPP releases or generations, and / or other access technologies) can be enabled by networking schemes that allow the use of resources (e.g., unlicensed spectrum) corresponding to other types of wireless communication (e.g., WLAN and / or other access technologies). Complementary access technologies utilizing unlicensed spectrum can be deployed to meet wireless traffic usage and / or growth. Unlicensed spectrum (if available) can be an effective complement to licensed spectrum and / or can help address high traffic in at least some scenarios (e.g., in areas that can be served by hotspots and / or other access points). For example, Licensed Assisted Access (LAA) and / or New Radio over Unlicensed Bands (NR-U) can enable wireless communication using unlicensed spectrum (e.g., using 3GPP Release 16, earlier / later 3GPP releases or generations, LTE access technologies, and / or other access technologies). Using unlicensed spectrum can optimize network efficiency and improve network capacity, among other benefits.

[0204] Wireless devices can use a Listen-Before-Speak (LBT) procedure to communicate in cells configured in unlicensed frequency bands (e.g., which may be referred to as LAA cells and / or NR-U cells) and / or licensed frequency bands. LAA cells and / or NR-U cells can refer to any cell operating in an unlicensed frequency band. The cell can operate as a non-standalone cell including an anchored cell operating in a licensed frequency band, or as a standalone cell without an anchored cell in a licensed frequency band. The LBT procedure may include a Clear Channel Assessment (CCA). Devices (e.g., wireless devices and / or other computing devices) may perform CCA, for example, before using a channel in the LBT procedure. CCA may utilize at least energy detection to determine the presence of other signals on the channel. The presence of other signals on the channel (e.g., an indication that the signal power level is above a threshold) may indicate that the channel is occupied. The absence of other signals on the channel (e.g., an indication that the signal power level is below a threshold) may indicate that the channel is idle. The use of LBT may vary due to country-specific, region-specific, and / or other regional regulations and / or requirements. For example, regulations in Europe and Japan mandate the use of LBTs in unlicensed frequency bands (e.g., the 5 GHz unlicensed band). Carrier sensing using LBTs can be used to fairly share unlicensed spectrum.

[0205] Discontinuous transmission on an unlicensed carrier can be achieved within a limited maximum transmission duration. Certain functions can be supported by one or more signals transmitted (e.g., transmitted) during discontinuous downlink transmission in the unlicensed band (e.g., at the beginning). Channel reservation can be enabled by the NR-U node via a transmitted signal, for example, based on obtaining channel access via a successful LBT procedure (e.g., thereafter). Channel reservation allows other nodes to determine channel occupancy based on receiving a transmitted signal with energy above a certain threshold. Procedures (e.g., functions) for operating in an unlicensed band with discontinuous downlink transmission, which can be supported by one or more signals, may include one or more of the following: detection of downlink transmissions in the unlicensed band by the radio device (including cell identification), time and frequency synchronization of the radio device, etc.

[0206] LBT procedures can be performed on various wireless communications. For example, LBT procedures can be used for the coexistence (e.g., fair and amicable coexistence) of wireless communications (e.g., using multiple different access technologies, such as LTE, NR, and / or any other access technologies) and communications in unlicensed spectrum (e.g., communications corresponding to other operators and / or other access technologies). LBT procedures on nodes attempting to transmit on carriers (or channels) in unlicensed spectrum may require the node to perform CCA to determine whether the channel is freely available. LBT procedures may include at least radio signal energy detection to determine whether the channel is being used. Regulatory requirements in some regions (e.g., Europe) may specify an energy detection threshold such that if the measured energy on the carrier (or channel) is greater than this threshold, the node can assume the channel is not free (e.g., the channel is being used by other nodes). Nodes may optionally use an energy detection threshold lower than the one specified by the regulatory requirements. Some communications (e.g., NR-U communications) can adaptively change the energy detection threshold. For example, a communication (e.g., NR-U communications) can adaptively lower the energy detection threshold from an upper limit. Threshold adjustments may include static and / or semi-static determination of the threshold. Type 4 LBT programs and / or other types of LBT programs can be used.

[0207] Various exemplary LBT procedures can be used. For example, in at least some implementation scenarios, in at least some cases, the transmission entity may not use an LBT procedure for the transmission of some signals and / or for the transmission in at least some frequencies. A Type 1 LBT procedure (CAT1, e.g., no LBT procedure) can be used in one or more cases. For example, if a channel is maintained by a base station for downlink transmission, and a wireless device takes over the channel for uplink transmission, the wireless device can perform uplink transmission in the channel in an unlicensed frequency band without performing an LBT procedure. A Type 2 LBT procedure (CAT2, e.g., an LBT procedure without random backoff) can be used. The duration for which the channel is sensed as idle (e.g., by the wireless device, by the base station) before the transmission entity can send / transmit data can be determined. A Type 3 LBT procedure (CAT3, e.g., an LBT procedure with random backoff having a fixed-size contention window) can be used. An LBT procedure may have at least one of the following as a component: The transmission entity (e.g., the wireless device, the base station) can select a random number N within the contention window. The contention window size can be specified by the minimum and maximum values ​​of N. The contention window size can be fixed. A random number N can be used in the LBT procedure to determine the duration during which the channel will be sensed as idle before the transmitting entity can send / transmit data in the channel. A Type 4 LBT procedure (CAT4, e.g., an LBT procedure with random backoff and a variable-sized contention window) can be used. The transmitting entity (e.g., a wireless device, a base station) can select a random number N within the contention window. The contention window size can be specified by the minimum and maximum values ​​of N. The transmitting entity can change the contention window size and select a random number N within the contention window. The random number N can be used in the LBT procedure to determine the duration during which the channel will be sensed as idle before the transmitting entity can send / transmit data in the channel.

[0208] Wireless devices can perform uplink transmissions on unlicensed frequency bands using uplink LBT procedures. Uplink LBT procedures may differ from downlink LBT procedures. Uplink and downlink LBT procedures may use different LBT protocols and / or parameters. For example, uplink LBT procedures may be based on scheduled access that could affect the channel contention opportunity of wireless devices. Other considerations incentivizing different uplink LBT procedures include, but are not limited to, multiplexing multiple wireless devices within a time period (e.g., subframes, time slots, and / or microslots).

[0209] A downlink transmission burst can be a continuous transmission from a downlink transmission node, where there are no transmissions immediately preceding and / or immediately following that node on the same carrier component (CC). From the perspective of the radio device, an uplink transmission burst can be a continuous transmission from the radio device, where there are no transmissions immediately preceding or immediately following that same radio device on the same CC. Uplink transmission bursts can be defined from the perspective of the radio device. Uplink transmission bursts can also be defined from the perspective of the base station. For example, if a base station operates both downlink and uplink transmissions on the same unlicensed carrier, it can schedule downlink and uplink transmission bursts using TDM on the same unlicensed carrier. A given moment can include both downlink and / or uplink transmission bursts.

[0210] Contention-based random access (CBRA) and / or contention-free random access (CFRA) can be supported. CBRA and / or CFRA can be supported on the primary cell of the primary cell group or the primary cell of the secondary cell group (SpCell). CFRA can be supported on SCell. RAR can be transmitted via SpCell (e.g., in a non-standalone scenario). RAR can be transmitted via SpCell and / or SCell (e.g., in a standalone scenario). Predefined HARQ procedure indicators / identifiers / indexes (IDs) can be used for RAR.

[0211] Carrier aggregation is supported. Carrier aggregation between PCells configured on licensed frequency bands and SCells configured on unlicensed frequency bands is supported. SCells can be configured for both downlink and uplink transmissions, or for downlink transmissions only. Dual connectivity between PCells configured on licensed frequency bands (e.g., LTE cells or any other cells) and PSCells configured on unlicensed frequency bands (e.g., NR-U cells or any other cells) is supported. Independent operation on unlicensed frequency bands is supported, where all carriers are in one or more unlicensed frequency bands. Cells configured to perform downlink transmissions in unlicensed frequency bands and uplink transmissions in licensed frequency bands, or vice versa, are supported. Dual connectivity between PCells on licensed frequency bands (e.g., NR cells or any other cells) and PSCells on unlicensed frequency bands (e.g., NR-U cells or any other cells) is supported.

[0212] Figure 17An example of LBT failure detection is illustrated. Wireless device 1700 can determine that an LBT procedure has failed, for example, based on the presence of a signal on the channel. Wireless device 1700 can use an LBT failure counter (or a similar mechanism / method) to track the number of times a signal is detected on the channel. For example, if the value indicated by the LBT counter exceeds a threshold, wireless device 1700 can determine that an uplink LBT has failed. The LBT failure counter described herein is merely an example, but those skilled in the art will recognize that any similar mechanism can be used for the purposes of this invention.

[0213] The wireless device 1700 can receive one or more messages. The wireless device 1700 can receive one or more messages from a base station. The one or more messages may include one or more configuration parameters. The one or more configuration parameters may be used for a cell. The cell may be a PCell or SCell. The cell may be a SCell configured with a PUCCH (e.g., a PUCCH SCell). The cell may be an unlicensed cell (e.g., a cell operating in an unlicensed frequency band). The cell may be a licensed cell (e.g., a cell operating in a licensed frequency band).

[0214] A cell may include multiple radio resources (e.g., BWPs, frequency bands, sub-bands, and / or any other radio resources). The multiple BWPs may include one or more uplink BWPs, which include the cell's uplink BWPs. The multiple BWPs may include one or more downlink BWPs, which include the cell's downlink BWPs. A BWP among the multiple BWPs may be in an active or inactive state. For example, if a downlink BWP is active, radio device 1700 may monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) in one or more downlink BWPs. For example, if a downlink BWP is active, radio device 1700 may receive downlink transmissions (e.g., PDSCH transmissions) on or via one or more downlink BWPs. For example, if a downlink BWP is inactive, the wireless device 1700 may not monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) in one or more downlink BWPs. For example, if a downlink BWP is inactive, the wireless device 1700 may not receive downlink transmissions (e.g., PDSCH transmissions) on or via one or more downlink BWPs.

[0215] For example, if the uplink BWP is active, the wireless device 1700 can transmit / transmit uplink signals / channels (e.g., PUCCH transmission, preamble, PUSCH transmission, PRACH transmission, SRS transmission, etc.) via one or more uplink BWPs. Conversely, if the uplink BWP is inactive, the wireless device 1700 can transmit / transmit uplink signals / channels (e.g., PUCCH transmission, preamble, PUSCH transmission, PRACH transmission, SRS transmission, etc.) without using one or more uplink BWPs.

[0216] Wireless device 1700 can activate one or more downlink BWPs of a cell. Activating a downlink BWP may include wireless device 1700 setting the downlink BWP as the active downlink BWP of the cell. Activating a downlink BWP may include wireless device 1700 setting the downlink BWP to an active state. Activating a downlink BWP may include switching the downlink BWP from an inactive state to an active state.

[0217] The wireless device 1700 can activate one or more uplink BWPs in a cell. Activating an uplink BWP may include the wireless device 1700 setting the uplink BWP as the active uplink BWP for the cell. Activating an uplink BWP may also include the wireless device 1700 setting the uplink BWP to an active state. Activating an uplink BWP may also include switching the uplink BWP from an inactive state to an active state.

[0218] One or more configuration parameters may include LBT failure detection and recovery configuration parameters. LBT failure detection and recovery configuration parameters can be used for the cell's uplink BWP. One or more configuration parameters may indicate the maximum number (e.g., the number) of LBT failures for the uplink BWP. LBT failure detection and recovery configuration parameters may indicate the maximum number (e.g., the number) of LBT failures. One or more configuration parameters may indicate the maximum number (e.g., the number) of LBT failures for the cell. LBT failure detection and recovery configuration parameters may indicate the maximum number (e.g., the number) of LBT failures.

[0219] One or more configuration parameters can indicate the LBT detection timer for the uplink BWP. One or more configuration parameters can indicate the timer value of the LBT detection timer. One or more configuration parameters can indicate the timer value associated with the LBT detection timer. LBT failure detection and recovery configuration parameters can indicate the LBT detection timer. One or more configuration parameters can indicate the LBT detection timer for the cell.

[0220] The wireless device 1700 can detect uplink LBT failure in the uplink BWP to perform uplink transmission. The wireless device 1700 can detect uplink LBT failure to perform LBT failure detection. Uplink transmission may include random access preamble transmission (e.g., in RACH). Uplink transmission may include PUCCH transmission (e.g., SR, HARQ-ACK, CSI report, UCI, etc.). Uplink transmission may include PUSCH transmission. Uplink transmission may include SRS transmission.

[0221] An uplink BWP can include one or more LBT bandwidths (or one or more sub-bands). The LBT bandwidth of one or more LBT bandwidths can be 20MHz, 10MHz, 50MHz, or any other bandwidth. The LBT bandwidth can be determined based on regulations. An uplink BWP can be 80MHz. For example, if the LBT bandwidth is 20MHz, the uplink BWP can include four LBT bandwidths. For example, if the LBT bandwidth is 10MHz, the uplink BWP can include eight LBT bandwidths.

[0222] The wireless device 1700 can perform LBT procedures in / for uplink transmissions (e.g., PUSCH transmissions, PRACH transmissions, PUCCH transmissions, SRS transmissions) via the uplink BWP. Performing LBT procedures in / for uplink transmissions may include, for example, performing CCA on the uplink resources of the uplink transmission before the uplink transmission. Performing checks on the uplink resources may include performing an energy detection procedure to determine the presence or absence of a signal on the uplink resources.

[0223] The wireless device 1700 can determine (and / or detect) a failure of the LBT procedure in / for uplink transmission based on the execution of the LBT procedure. Determining (and / or detecting) the failure of the LBT procedure can be based on determining the presence of a signal on the uplink resource. Determining the failure of the LBT procedure can be based on determining that the uplink resource for the uplink transmission is busy (or occupied, not idle, unavailable, or not free). The uplink resource may include one or more LBT bandwidths. Determining that the uplink resource for the uplink transmission is busy may include determining that at least one of the one or more LBT bandwidths is busy. Determining that the uplink resource for the uplink transmission is busy may include determining that each of the one or more LBT bandwidths is busy.

[0224] Wireless device 1700 can determine (and / or detect) the success of an uplink transmission / for an uplink transmission's LBT procedure based on the execution of an LBT procedure. Determining (and / or detecting) the success of the LBT procedure can be based on determining the absence of a signal on the uplink resource. Determining the success of the LBT procedure can be based on determining that the uplink resource for the uplink transmission is idle (or unoccupied, vacant, available, or free). The uplink resource may include one or more LBT bandwidths. Determining that the uplink resource for the uplink transmission is idle may include determining that at least one of the one or more LBT bandwidths is idle. Determining that the uplink resource for the uplink transmission is idle may include determining that each of the one or more LBT bandwidths is idle.

[0225] Determining the failure (or success) of an LBT procedure may include determining the failure (or success) of the LBT procedure via the PHY layer 1704 of the wireless device 1700. The wireless device 1700 (or its PHY layer 1704) may determine the failure of the LBT procedure at times T1, T2, T3, T4, and T5. The PHY layer 1704 of the wireless device 1700 may (e.g., at times T1, T2, T3, T4, and T5) send / transmit an LBT failure indication to the MAC layer 1708 of the wireless device 1700. The LBT failure indication may indicate a failure of the LBT procedure in or for the uplink transmission.

[0226] Wireless device 1700 may use at least one wireless device variable for LBT failure detection. The at least one wireless device variable may include an LBT failure counter. The LBT failure counter may be a counter that tracks a quantity that indicates an LBT failure (or an LBT failure instance). Wireless device 1700 may initially set the LBT failure counter to zero (e.g., before time T1).

[0227] MAC layer 1708 can receive LBT failure indications from PHY layer 1704. Wireless device 1700 can increment an LBT failure counter, for example, based on the received LBT failure indication. Wireless device 1700 can increment the LBT failure counter, for example, at times T1, T2, T3, T4, and T5. Incrementing the LBT failure counter can include incrementing the LBT failure counter by MAC layer 1708 of wireless device 1700. The wireless device can increment the LBT failure counter by one. Wireless device 1700 can increment the LBT failure counter by any other amount (e.g., two, three, etc.). The amount (e.g., number) can be fixed, preconfigured, and / or predefined. One or more configuration parameters can indicate the amount. The amount can be based on the number of LBT procedure failures determined / detected. For example, if two LBT procedure failures are determined, the amount can be two, and if four LBT procedure failures are determined, the amount can be four, and so on. Wireless device 1700 can determine multiple LBT procedure failures in parallel (e.g., simultaneously or substantially simultaneously). The wireless device 1700 can identify / detect each failure of the LBT procedure among multiple failures of the LBT procedure on the corresponding LBT bandwidth of one or more LBT bandwidths.

[0228] The MAC layer 1708 can receive an LBT failure indication from the PHY layer 1704. The wireless device 1700 can, for example, start (or restart) the LBT detection timer based on the received LBT failure indication. The wireless device 1700 can (re)start the LBT detection timer at times T1, T2, T3, T4, and T5. Starting (or restarting) the LBT detection timer can include starting (or restarting) the LBT detection timer by the MAC layer 1708 of the wireless device 1700.

[0229] The LBT detection timer may expire (e.g., at time Tk). The wireless device 1700 may, for example, reset the LBT failure counter based on the expiration of the LBT detection timer. Resetting the LBT failure counter may include setting the value of the LBT failure counter to zero. Resetting the LBT failure counter may also include setting the value of the LBT failure counter to any other value. The value may be fixed, preconfigured, and / or predefined. One or more configuration parameters may indicate the value.

[0230] Wireless device 1700 can determine, for example, based on an incrementing LBT failure counter to determine that the value of the LBT failure counter is equal to or greater than the maximum amount (e.g., number) of LBT failures. For example, if the maximum amount of LBT failures is equal to 3, then wireless device 1700 can determine that the value of the LBT failure counter is equal to or greater than the maximum amount of LBT failures at time T5. Wireless device 1700 can detect / determine / announce an uplink LBT failure of the cell's uplink BWP, for example, based on determining that the value of the LBT failure counter is equal to or greater than the maximum amount of LBT failures. Wireless device 1700 can detect / determine / announce an uplink LBT failure of the cell's uplink BWP, for example, based on determining that the value of the LBT failure counter is equal to or greater than the maximum amount (e.g., 3) of LBT failures (e.g., at or after time T5).

[0231] LBT failure can include a consistent failure of the LBT procedure (e.g., the amount of failure that meets a threshold). For example, an uplink LBT failure can include a consistent failure of the LBT procedure on an uplink resource (e.g., an uplink BWP) (e.g., the amount of failure that meets a threshold). For example, a downlink LBT failure can include a consistent failure of the LBT procedure on a downlink resource (e.g., a downlink BWP) (e.g., the amount of failure that meets a threshold). The radio device 1700 can detect / determine / announce an uplink LBT failure of the cell's uplink BWP, for example, based on determining that the amount of LBT failure indication reaches a maximum amount of LBT failure. The LBT failure indication can be continuous. The radio device 1700 can initiate an uplink BWP LBT failure recovery procedure based on detecting / determining / announced an uplink LBT failure of the uplink BWP.

[0232] Figure 18 An example of LBT failure detection is shown. Wireless device 1800 (e.g., the MAC layer 1808 of the wireless device) can increment an LBT failure counter based on (e.g., from the PHY layer 1804 of the wireless device 1800) an LBT failure indication received, for example, as referenced... Figure 17 The LBT failure counter can be used for the cell's uplink BWP. Radio device 1800 can be based on reference... Figure 18 One or more considerations are described to reset the LBT failure counter. Resetting the LBT failure counter may include setting the value of the LBT failure counter to zero. Wireless device 1800 may perform one or more operations as described with reference to wireless device 1700.

[0233] Radio device 1800 can deactivate a cell. Cell deactivation can be based on the expiration of a SCell deactivation timer (e.g., sCellDeactivationTimer). One or more configuration parameters can indicate the SCell deactivation timer for a cell. Cell deactivation can be based on receiving a SCell activation / deactivation MAC CE (e.g., from a base station). Radio device 1800 can reset the LBT failure counter based on a deactivated cell.

[0234] Radio device 1800 can switch from an uplink BWP to a second uplink BWP of one or more uplink BWPs in the cell. Switching from an uplink BWP to a second uplink BWP may include activating the second uplink BWP as the second active uplink BWP of the cell. Activating the second uplink BWP may include radio device 1800 setting the second uplink BWP to an active state. Switching from an uplink BWP to a second uplink BWP may include deactivating the uplink BWP. Deactivating the uplink BWP may include radio device 1800 setting the uplink BWP to an inactive state. Radio device 1800 may switch from an uplink BWP to a second uplink BWP based on the expiration of a BWP inactivity timer. One or more configuration parameters may indicate the cell's BWP inactivity timer. Radio device 1800 may switch from an uplink BWP to a second uplink BWP based on receiving a downlink signal indicating the second uplink BWP (e.g., DCI, RRC message, MAC CE). Downlink signals may include a field indicating the BWP indicator / index (e.g., bwp-Id) of the second uplink BWP. One or more configuration parameters may indicate the BWP index of the second uplink BWP. Radio device 1800 may switch from the uplink BWP to the second uplink BWP based on initiating a random access procedure. A random access procedure may be initiated for the cell. Radio device 1800 may reset the LBT failure counter based on switching from the uplink BWP to the second uplink BWP.

[0235] A higher layer (e.g., the RRC layer) of the wireless device 1800 may request a reset of the MAC layer 1808 (or the MAC entity). The wireless device 1800 may, for example, reset the LBT failure counter based on a higher layer request to reset the MAC layer 1808.

[0236] One or more configuration parameters can instruct the time alignment timer. The time alignment timer can be used for timing advance groups including cells. The radio device 1800 can reset the LBT failure counter based on the expiration of the time alignment timer.

[0237] Wireless device 1800 can release one or more uplink channels / signals (e.g., PUCCH, SRS) of the uplink BWP. Releasing one or more uplink channels / signals can be based on the expiration of a time alignment timer. Releasing one or more uplink channels / signals can be based on a higher-layer request to reset the MAC layer. Releasing one or more uplink channels / signals can be based on the amount of SR transmission reaching (e.g., provided by the higher-layer parameter sr-TransMax) the maximum amount of SR transmission. One or more configuration parameters can indicate the maximum amount of SR transmission. Wireless device 1800 can reset the LBT failure counter based on the amount of SR transmission reaching the maximum amount of SR transmission. Wireless device 1800 can reset the LBT failure counter by releasing one or more uplink channels / signals.

[0238] Wireless device 1800 can clear one or more uplink channels / signals (e.g., PUSCH, configured uplink license) of the uplink BWP. Clearing one or more uplink channels / signals can be based on the expiration of a time alignment timer. Clearing one or more uplink channels / signals can be based on a higher-layer request to reset the MAC layer. Clearing one or more uplink channels / signals can be based on the amount of SR transmission reaching (e.g., provided by the higher-layer parameter sr-TransMax) the maximum amount of SR transmission. One or more configuration parameters can indicate the maximum amount of SR transmission. Wireless device 1800 can reset the LBT failure counter based on clearing one or more uplink channels / signals.

[0239] Clearing the configured uplink license may include allowing the wireless device 1800 to transmit / transmit transport blocks without using at least one uplink radio resource indicated by the configured uplink license. Clearing the configured uplink license may also include allowing the wireless device 1800 to refrain from transmitting / transmitting transport blocks for the configured uplink license. For example, a base station may assign / allocate the configured uplink license (or at least one uplink radio resource indicated by the configured uplink license) to a second wireless device. For example, if the wireless device 1800 does not clear the configured uplink license, the wireless device 1800 may transmit transport blocks via at least one uplink radio resource indicated by the configured uplink license. Transmitting transport blocks via at least one uplink radio resource may result in conflicts with transmissions from the second wireless device. Clearing the configured uplink license may also include allowing the wireless device 1800 to perform uplink transmissions without using the configured uplink license.

[0240] Releasing an uplink channel / signal may include configuring the wireless device 1800 to release an uplink channel / signal. For example, based on releasing an uplink channel / signal, the base station may use messages (e.g., explicit messages, PDCCH signaling, MACCE, RRC messages, etc.) to reconfigure (or reschedule) the uplink channel / signal for the wireless device 1800 so that the wireless device 1800 can (re)use at least one uplink radio resource indicated by the uplink channel / signal.

[0241] The wireless device 1800 may receive one or more second configuration parameters (e.g., reconfiguration parameters in an RRC message) from a base station. The one or more second configuration parameters may include second LBT failure detection and recovery configuration parameters for the cell's uplink BWP.

[0242] The second LBT failure detection and recovery configuration parameter can indicate a second maximum quantity (e.g., number) of LBT failures. This second maximum quantity of LBT failures can include the maximum amount of LBT failures that can be reconfigured / replaced / overridden with the second maximum quantity of LBT failures. The second maximum number of LBT failures can also include the maximum amount of LBT failures that can be reconfigured with the second maximum quantity of LBT failures. The wireless device 1800 can reset the LBT failure counter based on the second maximum quantity of LBT failures indicated by the second LBT failure detection and recovery configuration parameter.

[0243] One or more configuration parameters may indicate a first value representing the maximum amount (e.g., number) of LBT failures. One or more second configuration parameters may indicate a second value different from the first value representing the maximum amount of LBT failures. The wireless device 1800 may reset the LBT failure counter based on the second value indicated by one or more second configuration parameters.

[0244] The second LBT failure detection and recovery configuration parameters can indicate the second LBT detection timer. Indicating the second LBT detection timer using the second LBT failure detection and recovery configuration parameters can include reconfiguring / replacing / overriding the LBT detection timer with the second LBT detection timer. Indicating the second LBT failure detection and recovery configuration parameters can include reconfiguring the LBT detection timer value with the value of the second LBT detection timer. The wireless device 1800 can reset the LBT failure counter based on the second LBT failure detection and recovery configuration parameters indicating the second LBT detection timer.

[0245] One or more configuration parameters can indicate a first value for the LBT detection timer. One or more second configuration parameters can indicate a second value for the LBT detection timer that is different from the first value. The wireless device 1800 can reset the LBT failure counter based on the second value indicated by one or more second configuration parameters that is different from the first value.

[0246] One or more second configuration parameters can instruct / reconfigure the uplink resources (e.g., PUCCH resources, SRS resources, PUSCH resources) of the uplink BWP. The wireless device 1800 can reset the LBT failure counter based on the instruction / reconfiguration of uplink resources using one or more second configuration parameters.

[0247] One or more second configuration parameters can release uplink resources (e.g., PUCCH resources, SRS resources, PUSCH resources) of the uplink BWP. The radio device 1800 can reset the LBT failure counter by releasing uplink resources based on one or more second configuration parameters.

[0248] Figure 19 Exemplary communication for failure recovery is illustrated. The failure recovery procedure may include LBT failure recovery. The wireless device 1900 may detect / determine / declare an uplink LBT failure of the uplink BWP based on determining that the value indicated by the LBT failure counter exceeds the maximum amount of an LBT failure (e.g., as shown in reference). Figure 17 (Described). The LBT failure counter can be incremented based on the receipt of one or more LBT failure indications 1932. The wireless device 1900 can (e.g., at or after time T0) detect / determine / announce an uplink LBT failure of the uplink BWP (e.g., as described in reference). Figure 17 (Described). The PHY layer 1912 of the wireless device 1900 can perform the functions described in the above reference. Figure 17 and 18 The descriptions of PHY layers 1704 and 1804 describe one or more operations. The MAC layer 1908 of the wireless device 1900 can perform operations as described in the above references. Figure 17 and 18 The MAC layer 1708 and MAC layer 1808 describe one or more operations.

[0249] For example, uplink LBT failure based on detecting / determining / announcing uplink BWP (e.g., as referenced). Figure 17As described, the wireless device 1900 can trigger the transmission of an uplink signal 1916 (e.g., SR, random access preamble, MAC CE, PUSCH transmission) for an uplink BWP LBT failure recovery procedure to the base station 1904. Triggering the transmission of the uplink signal 1916 for the LBT failure recovery procedure may include initiating the LBT failure recovery procedure. The wireless device 1900 may initiate the LBT failure recovery procedure based on detecting / determining / announcing an uplink LBT failure of the uplink BWP. The uplink BWP LBT failure recovery procedure may include sending / transmitting the uplink signal 1916, receiving an uplink grant 1920, sending / transmitting a second uplink signal 1924, and / or receiving an uplink grant 1928. The uplink BWP LBT failure recovery procedure may include a time period from time T0 to T4, or a time period from time T1 to time T4.

[0250] The transmission of the uplink signal 1916 for the LBT failure recovery procedure can be further based on the determination that no ongoing LBT failure recovery procedure exists. An ongoing LBT failure recovery procedure may be cell-specific. An ongoing LBT failure recovery procedure may be for a second cell different from the stated cell. For example, at the time when the radio device 1900 detects / determines / announces an uplink LBT failure of the uplink BWP, the radio device 1900 can determine that no ongoing LBT failure recovery procedure exists (e.g., for the cell or a second cell different from the stated cell). The radio device 1900 can, for example, trigger the transmission of the uplink signal 1916 for the uplink BWP's LBT failure recovery procedure based on the determination that no ongoing LBT failure recovery procedure exists. For example, at the time when the radio device 1900 detects / determines / announces an uplink LBT failure of the uplink BWP, the radio device 1900 can determine that an ongoing LBT failure recovery procedure exists (e.g., for the cell or a second cell different from the stated cell). The wireless device 1900 can, for example, determine that an ongoing LBT failure recovery procedure exists without triggering the transmission of the uplink signal 1916 for the uplink BWP LBT failure recovery procedure.

[0251] Initiating an LBT failure recovery procedure can be based on determining that no ongoing LBT failure recovery procedure exists. An ongoing LBT failure recovery procedure can be cell-specific. An ongoing LBT failure recovery procedure can be for a second cell different from the stated cell. For example, at the time when radio device 1900 detects / determines / announces an uplink LBT failure of the uplink BWP, radio device 1900 can determine that no ongoing LBT failure recovery procedure exists (e.g., for the cell or a second cell different from the stated cell). Radio device 1900 can initiate an uplink BWP LBT failure recovery procedure, for example, based on determining that no ongoing LBT failure recovery procedure exists. Alternatively, at the time when radio device 1900 detects / determines / announces an uplink LBT failure of the uplink BWP, radio device 1900 can determine that an ongoing LBT failure recovery procedure exists (e.g., for the cell or a second cell different from the stated cell). Radio device 1900 can, for example, not initiate an uplink BWP LBT failure recovery procedure based on determining that an ongoing LBT failure recovery procedure exists.

[0252] For example, when the wireless device 1900 detects / determines / announces an uplink LBT failure of the uplink BWP, the wireless device 1900 may determine that an ongoing LBT failure recovery procedure exists (e.g., for a cell or a second cell different from that cell). The wireless device 1900 may, for example, stop / abort the ongoing LBT failure recovery procedure based on the determination that an ongoing LBT failure recovery procedure exists. The wireless device 1900 may, for example, trigger the transmission of the uplink signal 1916 for the uplink BWP's LBT failure recovery procedure based on the stop / abort of the ongoing LBT failure recovery procedure.

[0253] For example, when wireless device 1900 detects / determines / announces an uplink LBT failure of the uplink BWP, wireless device 1900 may determine that an ongoing LBT failure recovery procedure exists (e.g., for a cell or a second cell different from that cell). For example, based on the determination that an ongoing LBT failure recovery procedure exists, wireless device 1900 may (e.g., based on the implementation of wireless device 1900) determine whether wireless device 1900 should stop / abort the ongoing LBT failure recovery procedure, or not trigger the transmission of uplink signal 1916 for the uplink BWP's LBT failure recovery procedure (e.g., continue the ongoing LBT failure recovery procedure). For example, based on the determination that an ongoing LBT recovery procedure exists, wireless device 1900 may (e.g., based on the implementation of wireless device 1900) determine whether wireless device 1900 should stop / abort the ongoing LBT failure recovery procedure, or not initiate the uplink BWP's LBT failure recovery procedure (e.g., continue the ongoing LBT failure recovery procedure).

[0254] The wireless device 1900 can perform LBT procedures in / for uplink transmissions (e.g., PUSCH transmission, PRACH transmission, PUCCH transmission, SRS transmission, etc.) via the uplink BWP. The wireless device 1900 can perform LBT failure recovery procedures or during an ongoing LBT failure recovery procedure (e.g., in...). Figure 19 The LBT procedure is executed between time T0 and time T4. The wireless device 1900 can determine the failure of the LBT procedure during / for uplink transmission via the uplink BWP. The wireless device 1900 can determine the failure of the LBT procedure on any LBT bandwidth of one or more LBT bandwidths of the uplink BWP. The wireless device 1900 can determine the failure of the LBT procedure on at least one LBT bandwidth of one or more LBT bandwidths of the uplink BWP.

[0255] The wireless device 1900 can be used during LBT failure recovery procedures or in the process of an ongoing LBT failure recovery procedure (e.g., in...). Figure 19 The failure of the LBT procedure is determined between time T0 and time T4. For example, based on the determination of a failure of the LBT procedure in the uplink transmission during the LBT failure recovery procedure or an ongoing LBT failure recovery procedure, the PHY layer 1908 of the wireless device 1900 may or may not send / transmit an LBT failure indication to the MAC layer 1908 of the wireless device 1900. The LBT failure indication can indicate a failure of the LBT procedure in the uplink transmission / for the uplink transmission.

[0256] Wireless device 1900 can determine the failure of an LBT procedure when there is no ongoing LBT failure recovery procedure. For example, based on the determination of a failure of an LBT procedure in / for uplink transmission during an uplink transmission when there is no ongoing LBT failure recovery procedure, the PHY layer 1912 of wireless device 1900 can send / transmit an LBT failure indication to the MAC layer 1908 of wireless device 1900. The LBT failure indication can indicate the failure of an LBT procedure in / for uplink transmission.

[0257] MAC layer 1908 can receive LBT failure indications from PHY layer 1912. MAC layer 1908 can receive LBT failure indications during LBT failure recovery procedures or during ongoing LBT failure procedures (e.g., in...). Figure 19 The LBT failure indication is received from the PHY layer 1912 between time T0 and time T4. For example, based on receiving the LBT failure indication during an LBT failure recovery procedure or an ongoing LBT failure procedure, the wireless device 1900 may not increment the LBT failure counter.

[0258] The MAC layer 1908 can receive an LBT failure indication from the PHY layer 1912. For example, the MAC layer 1908 can receive an LBT failure indication from the PHY layer 1912 when there is no ongoing LBT failure recovery procedure. For example, based on receiving an LBT failure indication when there is no ongoing LBT failure recovery procedure, the wireless device 1900 can increment the LBT failure counter.

[0259] For example, if wireless device 1900 detects / determines / announces an uplink LBT failure, wireless device 1900 may trigger the transmission of uplink signal 1916 (e.g., SR) for the LBT failure recovery procedure by sending / transmitting a second uplink signal 1924 (e.g., LBT failure recovery MAC CE, PUSCH transmission, transport block, aperiodic CSI-report, UCI, PUCCH transmission) based on the absence of uplink clearance. Uplink clearance may include (e.g., obtained / indicated by DCI) dynamic uplink clearance. Uplink clearance may be configured uplink clearance (e.g., configured clearance type 1, configured clearance type 2). Uplink clearance may be indicated / obtained by a random access response. Uplink clearance may be a PUSCH timing indicated by configuration parameters of a two-step random access procedure.

[0260] For example, if wireless device 1900 detects / determines / announces an uplink LBT failure, wireless device 1900 can send / transmit a second uplink signal 1924 (e.g., LBT failure recovery MAC CE, PUSCH transmission, transport block, aperiodic CSI-report, UCI, PUCCH transmission) without triggering the transmission of uplink signal 1916 (e.g., SR) based on having uplink clearance (e.g., dynamic clearance, configured uplink clearance, uplink clearance obtained from a random access response, etc.). For example, if wireless device 1900 detects / determines / announces an uplink LBT failure, the wireless device can send / transmit a second uplink signal 1924 for the LBT failure recovery procedure based on having uplink clearance.

[0261] One or more configuration parameters may indicate one or more uplink channel resources (e.g., PUCCH resource, SR resource, PRACH resource, PUSCH resource). One or more uplink channel resources may be (dedicated) to the LBT failure recovery procedure of one or more cells (e.g., may not be used for other procedures and / or communications). The one or more cells may include the stated cell. One or more uplink channel resources may be on a second cell (e.g., PCell, PUCCHSCell). The second cell may be different from the stated cell. The second cell and the stated cell may be the same.

[0262] Wireless device 1900 can, for example, transmit based on triggering uplink signal 1916, via one or more uplink channel resources (e.g., in...). Figure 19 The uplink signal 1916 (e.g., SR) is transmitted / transmitted at time T1 or later. The wireless device 1900 can transmit the uplink signal 1916 via the uplink channel resources of the active uplink BWP of the second cell. The uplink channel resources can be PUCCH resources with PUCCH format 0. Alternatively, the uplink channel resources can be PUCCH resources with PUCCH format 1.

[0263] One or more configuration parameters may indicate one or more second uplink channel resources (e.g., PUCCH resource, SR resource, PRACH resource, PUSCH resource). One or more second uplink channel resources may be used to transmit third uplink signals (e.g., SR).

[0264] One or more second uplink channel resources may be (dedicated) for beam failure recovery procedures of one or more cells. One or more second uplink channel resources may be used to transmit third uplink signals for SR during beam failure recovery procedures. One or more cells may or may not include the stated cells. One or more second uplink channel resources may be on a second cell (e.g., PCell, PUCCH SCell). The second cell may be different from the stated cell. The second cell and the stated cell may be the same.

[0265] One or more second uplink channel resources can be used to request UL-SCH resources for uplink transmission (e.g., PUSCH transmission, transport block). One or more second uplink channel resources can be used for SR. One or more second uplink channel resources can be used to transmit a third uplink signal for the SR when requesting UL-SCH resources. The wireless device 1900 can, for example, trigger the transmission of a third uplink signal via one or more second uplink channel resources based on one or more pending SRs.

[0266] The wireless device 1900 can determine that one or more uplink channel resources overlap with one or more second uplink channel resources. The uplink channel resources may overlap with the second uplink channel resources at least partially in time (e.g., at least one symbol, at least one time slot, at least one subframe, etc.). The uplink channel resources may completely overlap with the second uplink channel resources.

[0267] Wireless device 1900 may abandon the transmission of a third uplink signal. Wireless device 1900 may, for example, abandon the transmission of a third uplink signal based on the determination that the uplink channel resources overlap with the second uplink channel resources. Wireless device 1900 may, for example, not perform the transmission of a third uplink signal based on the determination that the uplink channel resources overlap with the second uplink channel resources. Wireless device 1900 may, for example, transmit / transmit uplink signal 1916 based on the determination that the uplink channel resources overlap with the second uplink channel resources. Wireless device 1900 may, for example, perform the transmission of uplink signal 1916 based on the determination that the uplink channel resources overlap with the second uplink channel resources. The second uplink channel resources may be (dedicated) for beam failure recovery procedures for one or more cells. The second uplink channel resources may be used to request UL-SCH resources.

[0268] Wireless device 1900 may, for example, abandon the transmission of uplink signal 1916 based on the determination that the uplink channel resource overlaps with the second uplink channel resource. Wireless device 1900 may, for example, not perform the transmission of uplink signal 1916 based on the determination that the uplink channel resource overlaps with the second uplink channel resource. Wireless device 1900 may, for example, transmit / transmit a third uplink signal via the second uplink channel resource based on the determination that the uplink channel resource overlaps with the second uplink channel resource. Wireless device 1900 may, for example, perform the transmission of a third uplink signal based on the determination that the uplink channel resource overlaps with the second uplink channel resource. The second uplink channel resource may be (dedicated) for beam failure recovery procedures of one or more cells.

[0269] Wireless device 1900 can monitor the DCI indicating / including uplink grant 1920, for example, based on the transmission of uplink signal 1916. Wireless device 1900 can receive the DCI indicating / including uplink grant 1920 (e.g., at or after time T2). Uplink grant 1920 can indicate at least one uplink resource. At least one uplink resource can include at least one time resource. At least one uplink resource can include at least one frequency resource.

[0270] At least one uplink resource indicated (or provided) by Uplink License 1920 may be a resource for transmitting the second uplink signal 1924 (e.g., LBT failure recovery MAC CE). The at least one uplink resource indicated (or provided) by Uplink License 1920 may be adapted to the second uplink signal 1924 and its sub-header. Radio device 1900 may transmit / transmit the second uplink signal 1924 via at least one uplink resource indicated by dynamic license (at or after time T3). The second uplink signal 1924 may include one or more fields. One or more fields may indicate (e.g., provided by the higher-layer parameter servCellIndex) the cell indicator / index of the cell. One or more configuration parameters may indicate the cell index identifying the cell. One or more fields may indicate (e.g., provided by the higher-layer parameter bwp-Id) the BWP indicator / index of the uplink BWP. One or more configuration parameters can indicate the BWP index that can be associated with the uplink BWP (e.g., indicating, identifying, etc. of the uplink BWP).

[0271] One or more fields can indicate (e.g., provided by the higher-layer parameter bwp-Id) the BWP index of the preferred uplink BWP of one or more uplink BWPs in the cell. One or more configuration parameters can indicate the BWP index associated with (indicating, identifying, etc.) the preferred uplink BWP. Base station 1904 can, for example, based on receiving a second uplink signal 1924 having a field indicating the BWP index of the preferred uplink BWP, send / transmit a downlink signal (e.g., DCI, RRC message, MAC CE) that switches radio device 1900 from the uplink BWP to the preferred uplink BWP. Radio device 1900 can execute LBT procedures in one or more uplink BWPs in the cell. Radio device 1900 can execute each LBT procedure for / for the LBT procedure of the corresponding uplink BWP of one or more uplink BWPs. The wireless device 1900 can determine (or detect) the success of the LBT procedure in the preferred uplink BWP / for the preferred uplink BWP.

[0272] One or more fields can indicate at least one LBT bandwidth indicator / index. One or more configuration parameters can indicate at least one LBT bandwidth index. The uplink BWP can include at least one LBT bandwidth. Preferably, the uplink BWP can include at least one LBT bandwidth.

[0273] Wireless device 1900 can transmit a second uplink signal 1924 (e.g., LBT failure recovery MAC CE) having a HARQ procedure indicator / index (ID) equal to a certain value. A DCI indicating / including uplink clearance 1920 can indicate the value of the HARQ procedure ID. A PUSCH transmission including the second uplink signal 1924 (e.g., LBT failure recovery MAC CE) can have a HARQ procedure ID equal to said value. Wireless device 1900 can send / transmit a PUSCH transmission including the second uplink signal 1924 having a HARQ procedure ID equal to said value.

[0274] Wireless device 1900 may (e.g., at or after time T4) receive a second DCI indicating / including a license (e.g., uplink license 1928). The second DCI (or license) may schedule a new transmission (e.g., a new PUSCH transmission). The second DCI may schedule the new transmission via a new and / or different communication channel (e.g., a new uplink BWP) different from the communication channel on which the uplink LBT failure was detected (e.g., uplink BWP). The second DCI may schedule a new transmission with a second HARQ process ID having the same second value as the HARQ process ID of a PUSCH transmission including a second uplink signal 1924 (e.g., with a switched NDI). The second DCI may indicate the second value of the second HARQ process ID. Wireless device 1900 may, for example, complete an LBT failure recovery procedure based on receiving the second DCI indicating / including an uplink license 1928 scheduling a new transmission. Wireless device 1900 can, for example, complete the LBT failure recovery procedure based on receiving an uplink grant 1928 scheduled for a new transmission for a second HARQ procedure ID, which has the same second value as the HARQ procedure ID of a PUSCH transmission including a second uplink signal 1924. Wireless device 1900 can also complete the LBT failure recovery procedure based, for example, on receiving an acknowledgment (ACK) message for the second uplink signal 1924. Wireless device 1924 can receive a second DCI in a CORESET of a second cell (e.g., the same as or different from the stated cell). The CORESET can be different from the BFR CORESET monitored during / for the beam failure recovery procedure.

[0275] The wireless device 1900 can reset the LBT failure counter based on the completion of the LBT failure recovery procedure. The wireless device 1900 can reset the LBT detection timer based on the completion of the LBT failure recovery procedure.

[0276] A wireless device can send / transmit one or more messages based on an uplink license. For example, a wireless device can send / transmit multiple MAC CEs (e.g., BFR MAC CE for beam failure recovery procedures, LBT failure recovery MAC CE for LBT failure recovery procedures, etc.) based on an uplink license. A wireless device can trigger the transmission of signals (e.g., BFR MAC CE) for a beam failure recovery procedure for a cell based on the detection of a beam failure. The wireless device can (e.g., based on a consistent failure of the cell's LBT procedure, such as a reference) Figure 17The description refers to detecting / determining / announcing an uplink LBT failure for a cell's uplink resources (e.g., BWP). The radio device can trigger an uplink LBT failure recovery procedure for the cell (e.g., reference) based on the detection / determination / announcing of the uplink LBT failure. Figure 19 The described LBT failure recovery MAC CE transmission. The wireless device may receive uplink licenses (e.g., uplink license 1920) for transmissions of BFR MAC CE and / or LBT failure recovery MAC CE. Uplink licenses may have a limited size (e.g., 10 bytes, 60 bytes, etc.) and may not be able to accommodate both BFR MAC CE and LBT failure recovery MAC CE.

[0277] In at least some examples, downlink communications that may depend on successful beam failure recovery may be more important (e.g., higher priority, more urgent, higher service level, etc.) than uplink communications that may depend on uplink LBT failure recovery. For example, uplink transmissions may be scheduled by a DCI received in the downlink control channel. The radio device may receive a DCI that, for example, schedules transmissions such as PUSCH transmissions, triggers aperiodic SRS / CSI transmissions, and / or indicates HARQ-ACK transmissions for transport blocks. The base station may send / transmit ACK messages (e.g., ACK messages corresponding to uplink license 1928) via the downlink control channel for uplink transmissions (e.g., random access preamble transmissions, configured license transmissions, etc.). For example, if the beam failure recovery procedure is not successfully completed, the radio device (and / or the base station or other radio devices) may not be able to receive the DCI and / or ACK messages.

[0278] As described herein, the wireless device can determine the priority order of beam failure recovery procedures and LBT failure recovery procedures. For example, if the wireless device must transmit both an LBT failure recovery MAC CE and a BFR MAC CE, the wireless device can determine the priority order of the LBT failure recovery MAC CE and the BFR MAC CE based on uplink clearance (e.g., in the MAC PDU). The wireless device can determine the priority order between the LBT failure recovery MAC CE and the BFR MAC CE and include the higher-priority MAC CE in the MAC PDU, e.g., the first-priority MAC CE and / or the MAC CE preceding the lower priority. For example, if there are several available bits and the MAC PDU can accommodate two MAC CEs, the wireless device can include the lower-priority MAC CE in the MAC PDU, e.g., the MAC CE following the higher priority. The wireless device can prioritize the beam failure recovery procedure to enable the wireless device to access the downlink channel for downlink communication. For example, the BFR MAC CE can take precedence over the LBT failure recovery MAC CE. Prioritizing BFR MAC CE enables successful beam failure recovery procedures and allows the establishment of downlink communication channels. The base station can use the downlink communication channel to redirect radio devices to another BWP or deactivate cells with uplink LBT failures.

[0279] In at least some examples, LBT failure recovery MAC CE may take precedence over BFR MAC CE. For example, for a radio device using a single active cell (e.g., using only a Pcell without carrier aggregation), prioritizing LBT failure recovery MAC CE may be advantageous. Prioritizing LBT failure recovery MAC CE can enable a successful LBT failure recovery procedure and / or allow the establishment of an uplink communication channel. The radio device can use the uplink communication channel to transmit uplink signals for the beam failure recovery procedure.

[0280] Logical Channel (LCH) can be prioritized. The LBT failure recovery MAC CE can have a higher priority than the BFR MAC CE. The LBT failure recovery MAC CE can have a higher priority than the C-RNTI MAC CE or the data transmitted in the uplink CCCH (UL-CCCH). The LBT failure recovery MAC CE can have a higher priority than the configured clearance information MAC CE. The LBT failure recovery MAC CE can have a higher priority than the Buffer Status Report (BSR) MAC CE (e.g., in addition to the MAC CE of the BSR included for filling purposes). For example, based on the fact that the LBT failure recovery MAC CE has a higher priority than the BFR MAC CE, the wireless device 1900 can (e.g., if the wireless device 1900 receives / has an uplink clearance 1920 for the second uplink signal 1924) first (e.g., to the MAC PDU of the second uplink signal 1924) include / add the LBT failure recovery MAC CE, and then (e.g., to the MAC PDU) include / add the BFR MAC CE. A wireless device may include a BFR MAC CE in its MAC PDU only if the bits in the MAC PDU are available to accommodate a BFR MAC CE.

[0281] LCH can be given priority. LBT failure recovery MAC CE can have a lower priority than BFR MAC CE. LBT failure recovery MAC CE can have a lower priority than C-RNTI MAC CE or data transmitted in UL-CCCH. LBT failure recovery MAC CE can have a lower priority than configured license information MAC CE. LBT failure recovery MAC CE can have a lower priority than BSR MAC CE (e.g., MAC CEs of BSRs included for padding purposes). For example, based on the lower priority of LBT failure recovery MAC CE compared to BFR MAC CE, wireless device 1900 can (e.g., if wireless device 1900 has received uplink license 1920 of second uplink signal 1924) first (e.g., to the MAC PDU of second uplink signal 1924) include / add BFR MAC CE, and then (e.g., to the MAC PDU) include / add LBT failure recovery MAC CE. For example, a wireless device may include an LBT failure recovery MAC CE in its MAC PDU only if the bits in the MAC PDU are available to accommodate an LBT failure recovery MAC CE.

[0282] LCH can be given priority. The LBT failure recovery MAC CE can have the same priority as the BFR MAC CE. The LBT failure recovery MAC CE can have the same priority as the C-RNTI MAC CE or data transmitted in the UL-CCCH. The LBT failure recovery MAC CE can have the same priority as the configured license confirmation MAC CE. The LBT failure recovery MAC CE can have the same priority as the BSR (except for BSRs included for padding purposes).

[0283] Figure 20 Exemplary methods for beam failure recovery procedures and LBT failure recovery procedures are shown. Figure 20 The exemplary method 2000 shown can be performed by, for example, a wireless device and / or a base station. In step 2004, the wireless device can detect a beam failure and initiate a beam failure recovery procedure. In step 2008, the wireless device can (e.g., based on the detection of, for example, reference...) Figure 17 The described LBT procedure (consecutive failures) detects an LBT failure and / or initiates an LBT failure recovery procedure. Initiating an LBT failure recovery procedure may include sending an uplink signal (e.g., SR, uplink signal 1916). In step 2012, the wireless device may receive an uplink grant for uplink transmission from the wireless device. The uplink grant may correspond to an LBT failure recovery procedure (e.g., uplink grant 1920). The wireless device may determine an uplink message (e.g., MAC PDU) for transmission based on the uplink grant. The wireless device may prioritize a BFR MAC CE associated with the beam failure recovery procedure for transmission. In step 2016, the wireless device may include a BFR MAC CE in the MAC PDU. In step 2018, the wireless device may determine whether the MAC PDU can accommodate an LBT failure recovery MAC CE. In step 2020, the wireless device may, for example, transmit a MAC PDU comprising both the BFR MAC CE and the LBT failure recovery MAC CE (e.g., associated with an LBT failure recovery procedure) based on the determination that the MAC PDU can accommodate the LBT failure recovery MAC CE (e.g., has enough bits to accommodate the LBT failure recovery MAC CE). In step 2024, the wireless device may, for example, transmit a MAC PDU comprising the BFR MAC CE (but excluding the LBT failure MAC CE) based on the determination that the MAC PDU may not accommodate the LBT failure recovery MAC CE (e.g., may not have enough bits to accommodate both the BFR MAC CE and the LBT failure MAC CE).

[0284] A radio device can initiate an LBT failure recovery procedure for an active uplink BWP in a cell (e.g., based on a determined uplink LBT failure). The base station may be unaware of the ongoing LBT failure recovery procedure and may perform one or more operations and / or transmit one or more signals to the radio device. The base station may (e.g., during an ongoing LBT failure recovery procedure) transmit one or more of the following: a message deactivating the cell (and / or activating a new cell) (e.g., MAC CE), a message indicating a switch to new resources (e.g., switching the uplink BWP to a new uplink BWP) (e.g., DCI, RRC messages), a message updating LBT failure recovery parameters (e.g., relaxing, adjusting, or extending LBT failure recovery parameters) (e.g., including RRC reconfiguration parameters), a request to reset the radio device's layer (e.g., MAC layer), etc. Additionally or alternatively, a deactivation timer (e.g., a SCell deactivation timer) may (e.g., during an ongoing LBT procedure) expire, thereby deactivating the cell. The radio device may continue the LBT failure recovery procedure even under one or more of the above conditions. For example, a radio device may continue an LBT failure recovery procedure for: a cell that may no longer be active; a (previous) active uplink BWP; an LBT failure recovery procedure with strict LBT failure recovery parameters (e.g., even if the RRC reconfiguration parameters have relaxed the LBT failure recovery parameters); and / or an LBT failure recovery procedure at a reset MAC layer. Continuing an LBT failure recovery procedure may result in increased uplink interference to other cells and / or other devices (e.g., the radio device, the base station, etc.), increased power consumption (e.g., at the radio device), and / or overall reduced communication efficiency. Continuing an LBT failure recovery procedure (e.g., on a new uplink BWP of the (previous) uplink BWP) may cause the radio device to send one or more messages (e.g., a first uplink signal 1916, a second uplink signal 2024), which may cause the base station to determine / assume that the radio device has detected an LBT failure on a new radio resource (e.g., a new uplink BWP).

[0285] As described herein, a radio device can (e.g., based on one or more conditions) abort / cancel an ongoing LBT failure recovery procedure to prevent its continuation. For example, if a cell is deactivated, the radio device can abort / cancel the LBT failure recovery procedure. For example, if the active radio resource (e.g., active BWP) of a cell is switched, the radio device can cancel the LBT failure recovery procedure. Canceling / aborting the LBT failure recovery procedure can prevent the radio device from sending one or more messages (e.g., first uplink signal 1916, second uplink signal 1924), which can prevent the base station from determining / assuming that the radio device has detected an LBT failure on a new radio resource (e.g., a new uplink BWP).

[0286] The wireless device can cancel the LBT failure recovery procedure based on one or more conditions. For example, if a message to update LBT failure recovery parameters is received, the wireless device can cancel the LBT failure recovery procedure. For example, if the wireless device's MAC layer (e.g., from the wireless device's RRC layer) receives a request to reset the wireless device's layer (e.g., the MAC layer), the wireless device can cancel the LBT failure recovery procedure. Canceling the LBT failure recovery procedure at the wireless device can provide advantages such as reduced uplink interference to other cells and / or other devices (e.g., the wireless device, base station, etc.) and / or reduced power consumption (e.g., at the wireless device), among other advantages.

[0287] A wireless device can initiate an LBT failure recovery procedure using an LBT failure counter. For example, if the value of the LBT failure counter is equal to or greater than the maximum number of LBT failures, the wireless device can initiate an LBT failure recovery procedure. Canceling an ongoing LBT failure recovery procedure may cause the wireless device to (re-initiate) the LBT failure recovery procedure, for example, based on determining that the value of the LBT failure counter is equal to or greater than the maximum number of LBT failures. Re-initiating an LBT recovery procedure after it has been aborted may result in inefficient communication.

[0288] As described herein, wireless devices can cancel the LBT failure counter reset based on the LBT failure recovery procedure. Resetting the LBT failure counter avoids immediately re-initiating a new LBT failure recovery procedure after cancellation, which can provide advantages such as improved efficiency in wireless communication.

[0289] Figure 21 Exemplary communication for LBT failure recovery is illustrated. Wireless device 2100, base station 2104, PHY layer 2112, and MAC layer 2108 can respectively perform one or more operations described with reference to wireless device 1900, base station 1904, PHY layer 1912, and MAC layer 1908, as described in reference... Figure 19The LBT failure indication 2132, uplink signal 2116, uplink grant 2120, second uplink signal 2114, and uplink grant 2128 in the LBT failure recovery procedure can be similar to those described in the reference. Figure 19 The LBT failure indication 1932, uplink signal 1916, uplink grant 1921, second uplink signal 1914, and uplink grant 1928 are mentioned. Figure 21 The steps at times T0, T1, T2, T3, and T4 can be respectively similar to Figure 19 The steps at times T0, T1, T2, T3, and T4. Wireless device 2100 may cancel the LBT failure recovery procedure based on one or more considerations described herein. Canceling the LBT failure recovery procedure may include avoiding the transmission / reception of one or more signals associated with the LBT failure recovery procedure.

[0290] Wireless device 2100 can deactivate a cell (e.g., based on a SCell activation / deactivation timer, upon receiving a SCell activation / deactivation MAC CE). Wireless device 2100 can deactivate a cell during an ongoing LBT failure recovery procedure (e.g., between time T0 and time T4). Wireless device 2100 can stop / abort / cancel an ongoing LBT failure recovery procedure, for example, based on deactivating a cell during an ongoing LBT failure recovery procedure.

[0291] The wireless device 2100 can switch from an uplink BWP to a second uplink BWP of one or more uplink BWPs in the cell. The wireless device can switch from an uplink BWP to a second uplink BWP, for example, during an ongoing LBT failure recovery procedure (e.g., between time T0 and time T4). The wireless device 2100 can stop / abort / cancel the ongoing LBT failure recovery procedure, for example, based on the switch from an uplink BWP to a second uplink BWP during the ongoing LBT failure recovery procedure.

[0292] A higher layer (e.g., the RRC layer) of the wireless device 2100 may request a reset of the MAC layer 2108 (or MAC entity). The higher layer may request a reset of the MAC layer 2108 (or MAC entity) for example, during an ongoing LBT failure recovery procedure (e.g., between time T0 and time T4). The wireless device 2100 may stop / abort / cancel the ongoing LBT failure recovery procedure, for example, based on a higher layer's request to reset the MAC layer 2108 during the ongoing LBT failure recovery procedure.

[0293] The time alignment timer may expire. The time alignment timer may expire, for example, during an ongoing LBT failure recovery procedure (e.g., between time T0 and time T4). The wireless device 2100 may, for example, stop / abort / cancel an ongoing LBT failure recovery procedure based on the time alignment timer expiring during the procedure.

[0294] Wireless device 2100 can release one or more uplink channels / signals (e.g., PUCCH, SRS) of the uplink BWP. Wireless device 2100 can release one or more uplink channels / signals (e.g., PUCCH, SRS) of the uplink BWP, for example, during an ongoing LBT failure recovery procedure (e.g., between time T0 and time T1). Wireless device 2100 can stop / abort / cancel an ongoing LBT failure recovery procedure based on, for example, releasing one or more uplink channels / signals during an ongoing LBT failure recovery procedure.

[0295] Wireless device 2100 can clear one or more uplink channels / signals (e.g., PUSCH, configured uplink grant) of the uplink BWP. Wireless device 2100 can clear one or more uplink channels / signals (e.g., PUSCH, configured uplink grant) of the uplink BWP, for example, during an ongoing LBT failure recovery procedure (e.g., between time T0 and time T4). Wireless device 2100 can stop / abort / cancel an ongoing LBT failure recovery procedure, for example, based on clearing one or more uplink channels / signals during the ongoing LBT failure recovery procedure.

[0296] Wireless device 2100 may receive one or more second configuration parameters (e.g., reconfiguration parameters) (e.g., from base station 2104). The one or more second configuration parameters may include second LBT failure detection and recovery configuration parameters for the cell's uplink BWP. The second LBT failure detection and recovery configuration parameters may indicate a second maximum number of LBT failures. The second LBT failure detection and recovery configuration parameters may indicate a second LBT detection timer. The one or more second configuration parameters may indicate / reconfigure uplink resources (e.g., PUCCH resources, SRS resources) for the uplink BWP. Wireless device 2100 may receive one or more second configuration parameters during an ongoing LBT failure recovery procedure (e.g., between time T0 and time T4). Wireless device 2100 may, for example, stop / abort / cancel an ongoing LBT failure recovery procedure based on receiving one or more second configuration parameters during the ongoing LBT failure recovery procedure.

[0297] Wireless device 2100 can perform LBT procedures in / for an uplink transmission (e.g., PUSCH transmission, PRACH transmission, PUCCH transmission, SRS transmission) via an uplink BWP. Wireless device 2100 can perform the LBT procedure, for example, during an (ongoing) LBT failure recovery procedure (e.g., between time T0 and time T4). Wireless device 2100 can determine that the LBT procedure in / for an uplink transmission via the uplink BWP is successful. Wireless device 2100 can determine that the LBT procedure is successful on any LBT bandwidth of the uplink BWP. Wireless device 2100 can determine that the LBT procedure is successful on at least one LBT bandwidth of the uplink BWP. Wireless device 2100 can determine that the LBT procedure is successful, for example, during an (ongoing) LBT failure recovery procedure.

[0298] The PHY layer 2112 of the wireless device may, for example, not send / transmit (e.g., avoid transmitting to) an LBT failure indication to the MAC layer 2108 of the wireless device 2100 based on determining that the LBT procedure for / for the uplink transmission is successful. The MAC layer 2108 may, for example, not start (or restart) the LBT detection timer based on not transmitting the LBT failure indication. The LBT detection timer may expire. The LBT detection timer may, for example, expire during an ongoing LBT failure recovery procedure. The LBT detection timer may, for example, expire based on not starting (or restarting) the LBT detection timer. The wireless device 2100 may, for example, stop / abort / cancel an ongoing LBT failure recovery procedure based on the LBT detection timer expiring during an ongoing LBT failure recovery procedure. The wireless device 2100 may, for example, stop / abort / cancel an ongoing LBT failure recovery procedure based on determining that the LBT procedure for / for the uplink transmission is successful.

[0299] Wireless device 2100 can execute one or more LBT procedures in / for one or more uplink transmissions (e.g., PUSCH transmission, PRACH transmission, PUCCH transmission, SRS transmission) via an uplink BWP. Wireless device 2100 can execute one or more LBT procedures, for example, during an ongoing LBT failure recovery procedure (e.g., between time T0 and time T4). A certain number of one or more LBT procedures can succeed. Wireless device 2100 can determine that the number of one or more LBT procedures succeeded. Wireless device 2100 can determine that the number of one or more LBT procedures succeeded, for example, during an ongoing LBT failure recovery procedure. The number can be fixed (e.g., 1, 2, 3, 5, 10, or any other number). The number can be preconfigured. The number can be predefined. One or more configuration parameters can indicate the number. One or more configuration parameters can indicate the number for the uplink BWP. One or more configuration parameters can indicate the number for the cell. The wireless device 2100 can, for example, stop / abort / cancel the (ongoing) LBT failure recovery procedure based on the success of one or more LBT procedures during the (ongoing) LBT failure recovery procedure.

[0300] The wireless device 2100 can reset the LBT failure counter based on stopping / aborting / canceling the (ongoing) LBT failure recovery procedure. Resetting the LBT failure counter may include setting the value of the LBT failure counter to zero (or any other value). The wireless device 2100 can also reset the LBT detection timer based on stopping / aborting / canceling the (ongoing) LBT failure recovery procedure. Resetting the LBT detection timer may include setting the value of the LBT detection timer to zero (or any other value).

[0301] The wireless device may (e.g., to a base station) send / transmit at least one message including capability parameters. The capability parameters may indicate the maximum number of cells for which the wireless device supports LBT failure detection. The capability parameters may also indicate the maximum number of cells for which the wireless device supports LBT failure recovery procedures.

[0302] The wireless device can detect uplink LBT failures in the active uplink BWP of one or more cells to perform LBT failure detection. The number of one or more cells may not exceed the maximum number of cells. The number of one or more cells may be equal to or less than the maximum number of cells.

[0303] A base station may, for example, send / transmit one or more messages including one or more configuration parameters based on receiving at least one message including a capability parameter indicating the maximum amount of a cell. The one or more configuration parameters may indicate LBT failure detection and recovery configuration parameters for one or more cells. Each LBT failure detection and recovery configuration parameter in the LBT failure detection and recovery configuration parameters may be for a corresponding cell of one or more cells. The amount for one or more cells may not exceed the maximum amount of the cell. The amount for one or more cells may be equal to or less than the maximum amount of the cell.

[0304] A wireless device can, for example, monitor uplink LBT failures in the active uplink BWP of one or more cells based on one or more configuration parameters received that indicate LBT failure detection and recovery configuration parameters for one or more cells. Monitoring uplink LBT failures may include performing LBT failure detection (e.g., as referenced...). Figure 17 and 18 (as described) and / or perform LBT failure recovery procedures (e.g., as referenced) Figure 19 (Described). Monitoring uplink LBT failures may include tracking / incrementing the LBT failure counter, starting / restarting the LBT detection timer, sending / receiving LBT failure indications, etc. (e.g., ... Figure 17 (As described in [the document]). Monitoring uplink LBT failure may include initiating an LBT failure recovery procedure (e.g., as described in [the document]). Figure 19 (As described in the text).

[0305] A wireless device can initiate an LBT failure recovery procedure based on one or more uplink LBT failures. The wireless device can initiate a random access procedure (e.g., transmit a random access preamble) in response to the LBT failure recovery procedure. For example, the wireless device can initiate a random access procedure for the LBT failure recovery procedure during an ongoing random access procedure (e.g., initiated for a beam failure recovery procedure or any other procedure). The random access procedure can use one or more counters to track the transmission of the random access preamble (e.g., a random access preamble counter, a power ramp counter). The random access procedure initiated for the LBT failure recovery procedure can use counter values ​​determined based on the ongoing random access procedure. Using counter values ​​(e.g., determined based on the ongoing random access procedure) for a random access procedure initiated for the LBT failure recovery procedure may result in premature termination of the random access procedure and / or increased transmission power of the random access preamble transmission (used for the LBT failure recovery procedure).

[0306] As described herein, for example, if a wireless device determines that one or more uplink LBTs have failed, the wireless device may abort / cancel an ongoing random access procedure and / or initiate an LBT failure recovery procedure. For instance, if the amount of LBT failure indication (e.g., as tracked by an LBT failure counter) reaches the maximum amount of LBT failure, the wireless device may abort / cancel an ongoing random access procedure and / or initiate an LBT failure recovery procedure. Aborting / canceling an ongoing random access procedure may include resetting one or more counter values ​​(e.g., the values ​​of a random access preamble counter, a power ramp counter, etc.). Aborting / canceling an ongoing random access procedure and / or resetting counter values ​​can help ensure the correct operation of the random access procedure used for the LBT failure recovery procedure.

[0307] Figure 22 Exemplary communications for LBT failure recovery and beam failure recovery are illustrated. Wireless device 2200 may be similar to wireless device 1700, wireless device 1800, wireless device 1900, and / or wireless device 2100, and may perform reference... Figure 17-21 One or more operations are described. The PHY layer 2204 of the wireless device 2200 may send one or more beam failure indications 2212 to the MAC layer 2208 of the wireless device 2200. The PHY layer 2204 of the wireless device 2200 may send one or more LBT failure indications 2216 to the MAC layer 2208 of the wireless device 2200 based on the detection of one or more LBT procedure failures.

[0308] Wireless device 2200 can (e.g., in) Figure 22 The radio device 2200 detects beam failure in a second cell (e.g., PCell, SCell, PUCCH SCell) at time T1 or later. The radio device 2200 can detect beam failure of the active downlink BWP of the second cell. The second cell and the stated cell can be the same. The second cell and the stated cell can be different. The radio device 2200 can detect beam failure based on the amount of beam failure indication 2212 (e.g., beam failure instance indication) reaching / exceeding the maximum amount of beam failure defined for a beam failure counter. One or more configuration parameters can indicate the maximum amount of beam failure defined for the beam failure counter of the second cell. One or more configuration parameters can indicate the maximum amount of beam failure defined for the beam failure counter of the active downlink BWP of the second cell.

[0309] The wireless device 2200 can initiate a beam failure recovery procedure (e.g., a PRACH-based beam failure recovery procedure or a PUCCH-based beam failure recovery procedure) based on the detection of a beam failure. The wireless device 2200 can initiate a beam failure recovery procedure for a second cell. The wireless device 2200 can initiate a beam failure recovery procedure for the active downlink BWP of the second cell. Initiating a beam failure recovery procedure may include initiating a random access procedure in response to the beam failure recovery procedure.

[0310] Wireless device 2200 can (e.g., in) Figure 22 The radio device 2200 can detect / determine / declare an uplink LBT failure of the cell's uplink BWP at time T2 or later. The radio device 2200 can detect / declare / declare an uplink LBT failure of the cell's uplink BWP during an ongoing beam failure recovery procedure. The radio device 2200 can, for example, stop / suspend / cancel the ongoing beam failure recovery procedure based on the detection / declare / declare of the uplink LBT failure of the cell's uplink BWP during the ongoing beam failure recovery procedure. Cancelling the ongoing beam failure recovery procedure may include stopping / suspending the random access procedure used for the beam failure recovery procedure. The radio device 2200 can, for example, initiate an uplink LBT failure recovery procedure for the cell's uplink BWP based on the cancellation of the ongoing beam failure recovery procedure. The radio device 2200 can, for example, trigger the transmission of uplink signals (e.g., SR, random access preamble) used for the uplink LBT failure recovery procedure of the cell's uplink BWP based on the cancellation of the ongoing beam failure recovery procedure.

[0311] The wireless device 2200 can, for example, pause the (ongoing) beam failure recovery procedure based on detecting / determining / announcing an uplink LBT failure of the cell's uplink BWP during the (ongoing) beam failure recovery procedure, until the LBT failure recovery procedure is completed (e.g., in...). Figure 19 (At or after time T4). The wireless device 2200 can resume the (ongoing) beam failure recovery procedure based on the completion of the LBT failure recovery procedure (e.g., after the completion of the LBT failure recovery procedure).

[0312] Wireless device 2200 may continue executing the (ongoing) beam failure recovery procedure (e.g., transmitting / transmitting random access preamble, transmitting / transmitting BFR MAC CE, monitoring BFR CORESET, etc.) based on, for example, detecting / determining / announcing an uplink LBT failure of the cell's uplink BWP during the (ongoing) beam failure recovery procedure. Wireless device 2200 may, for example, not initiate an uplink BWP LBT failure recovery procedure based on, detecting / determining / announcing an uplink LBT failure of the cell's uplink BWP during the (ongoing) beam failure recovery procedure. Wireless device 2200 may not initiate an uplink BWP LBT failure recovery procedure, for example, at least until the (ongoing) beam failure recovery procedure is completed. The wireless device 2200 can, for example, detect / determine / announce an uplink LBT failure of the cell's uplink BWP during an (ongoing) beam failure recovery procedure, without triggering the transmission of uplink signals (e.g., SR, random access preamble) for the cell's uplink BWP LBT failure recovery procedure.

[0313] Wireless device 2200 can initiate an uplink LBT failure recovery procedure for the cell's uplink BWP based on detecting / determining / announcing an uplink LBT failure of the cell's uplink BWP. Wireless device 2200 can, for example, initiate an uplink LBT failure recovery procedure for the cell's uplink BWP during an ongoing beam failure recovery procedure. Wireless device 2200 can, for example, cancel an ongoing beam failure recovery procedure based on initiating an LBT failure recovery procedure during an ongoing beam failure recovery procedure. Wireless device 2200 can, for example, trigger the transmission of uplink signals (e.g., SR, random access preamble) for the cell's uplink BWP LBT failure recovery procedure based on canceling an ongoing beam failure recovery procedure. Wireless device 2200 can, for example, suspend an ongoing beam failure recovery procedure based on initiating an LBT failure recovery procedure during an ongoing beam failure recovery procedure until the LBT failure recovery procedure is completed (e.g., ...). Figure 19 (Time T4 in the text). The wireless device 2200 can resume the (ongoing) beam failure recovery procedure based on the LBT failure recovery procedure completion (e.g., after the LBT failure recovery procedure has been completed).

[0314] The wireless device 2200 can, for example, initiate an LBT failure recovery procedure during an ongoing beam failure recovery procedure while maintaining (e.g., continuing) the execution of the ongoing beam failure recovery procedure (e.g., transmitting random access preamble, transmitting BFR MAC CE, monitoring BFR CORESET, etc.). The wireless device 2200 can, for example, initiate an LBT failure recovery procedure during an ongoing beam failure recovery procedure without triggering the transmission of uplink signals (e.g., SR, random access preamble) for the LBT failure recovery procedure of the cell's uplink BWP.

[0315] Wireless device 2200 can trigger the transmission of uplink signals (e.g., SR, random access preamble) for the LBT failure recovery procedure of the cell's uplink BWP based on the detection / determination / announcement of an uplink LBT failure of the cell's uplink BWP. Wireless device 2200 can, for example, trigger the transmission of uplink signals for the LBT failure recovery procedure during an ongoing beam failure recovery procedure. Wireless device 2200 can, for example, cancel an ongoing beam failure recovery procedure based on the triggering of uplink signal transmission during an ongoing beam failure recovery procedure. Wireless device 2200 can, for example, cancel an ongoing beam failure recovery procedure based on the cancellation of an ongoing beam failure recovery procedure (e.g., during an ongoing beam failure recovery procedure). Figure 19 (At or after time T1) uplink signals are transmitted / transmitted via one or more uplink channel resources. Wireless device 2200 may, for example, suspend the (ongoing) beam failure recovery procedure based on triggering uplink signal transmission during the (ongoing) beam failure recovery procedure, until the LBT failure recovery procedure is completed (e.g., in...). Figure 19 (At or after time T4). The wireless device 2200 can resume the (ongoing) beam failure recovery procedure based on the completion of the LBT failure recovery procedure (e.g., after the completion of the LBT failure recovery procedure).

[0316] Wireless device 2200 can, for example, maintain the execution of the (ongoing) beam failure recovery procedure (e.g., transmitting random access preamble, transmitting BFR MAC CE, monitoring BFR CORESET, etc.) by triggering uplink signal transmission during the (ongoing) beam failure recovery procedure. Wireless device 2200 can, for example, transmit / transmit uplink signals without using uplink channel resources via one or more uplink channel resources, by triggering uplink signal transmission during the (ongoing) beam failure recovery procedure.

[0317] Figure 23Exemplary communications for LBT failure recovery and beam failure recovery are illustrated. Wireless device 2300 may be similar to wireless device 1700, wireless device 1800, wireless device 1900, wireless device 2100, and / or wireless device 2100, and may perform reference... Figure 17-21 One or more operations are described. The PHY layer 2304 of the wireless device 2300 may send one or more beam failure indications 2316 to the MAC layer 2308 of the wireless device 2300. The PHY layer 2304 of the wireless device 2300 may send one or more LBT failure indications 2312 to the MAC layer 2308 of the wireless device 2300 based on the detection of one or more failures in the LBT procedure.

[0318] Wireless device 2300 can (e.g., in) Figure 23 At time T1 or later, the uplink LBT failure of the cell's uplink BWP is detected / determined / announced. The radio device 2300 can initiate an uplink BWP LBT failure recovery procedure based on the detection / determination / announcement of the uplink LBT failure. The radio device 2300 can also trigger the transmission of uplink signals (e.g., SR, random access preamble) for the cell's uplink BWP LBT failure recovery procedure based on the detection / determination / announcement of the uplink LBT failure.

[0319] Wireless device 2300 can (e.g., in) Figure 23 The time T2 or later, as referenced Figure 17 (Or as described in 22) Detect beam failure. Wireless device 2300 may detect beam failure during the (ongoing) LBT failure recovery procedure. Wireless device 2300 may, for example, not initiate the beam failure recovery procedure based on the detection of beam failure during the (ongoing) LBT failure recovery procedure. Wireless device 2300 may, for example, suspend initiation of the beam failure recovery procedure based on the detection of beam failure during the (ongoing) LBT failure recovery procedure until the (ongoing) LBT failure recovery procedure is completed. Wireless device 2300 may, for example, initiate the beam failure recovery procedure based on the suspension of initiation, and on the completion of the (ongoing) LBT failure recovery procedure (or after the (ongoing) LBT failure recovery procedure is completed).

[0320] Wireless device 2300 can, for example, stop / abort / cancel the ongoing LBT failure recovery procedure based on the detection of a beam failure during the procedure. Wireless device 2300 can, for example, initiate a beam failure recovery procedure (e.g., sending / transmitting a random access preamble, scheduling request, BFR MAC CE, etc.) based on the cancellation of the ongoing LBT failure recovery procedure. Wireless device 2300 can, for example, pause the ongoing LBT failure recovery procedure based on the detection of a beam failure during the procedure until the procedure is complete. Wireless device 2300 can resume the ongoing LBT failure recovery procedure upon its completion (e.g., after the procedure has been completed).

[0321] The wireless device 2300 can detect / determine / announce an uplink LBT failure of the cell's uplink BWP. The wireless device 2300 can initiate an LBT failure recovery procedure for the cell's uplink BWP based on the detection / determination / announcement of the uplink LBT failure. The wireless device 2300 can trigger the transmission of uplink signals (e.g., SR, random access preamble) for the cell's uplink BWP LBT failure recovery procedure based on the detection / determination / announcement of the uplink LBT failure.

[0322] The wireless device 2300 can detect / determine / announce a second uplink LBT failure of the second uplink BWP in a second cell. The second cell may be different from the stated cell. The second cell may be the same as the stated cell. The second cell may be a primary cell (PCell, SpCell). The stated cell may be a secondary cell (e.g., SCell, PsCell). The second cell may have a higher priority than the stated cell. The second LBT failure recovery procedure of the second cell may have a higher priority than the (ongoing) LBT failure recovery procedure of the stated cell.

[0323] The wireless device 2300 can detect / determine / announce a second uplink LBT failure of the second uplink BWP of the second cell during the (ongoing) LBT failure recovery procedure of the uplink BWP of the second cell. The wireless device 2300 can, for example, cancel the (ongoing) LBT failure recovery procedure based on the detection / determination / announcement of the second uplink LBT failure during the (ongoing) LBT failure recovery procedure. The wireless device 2300 can, for example, initiate a second LBT failure recovery procedure for the second uplink BWP of the second cell based on the cancellation of the (ongoing) LBT failure recovery procedure.

[0324] The wireless device 2300 can initiate a second LBT failure recovery procedure for the second uplink BWP of the second cell based on detecting / determining / announcing a second uplink LBT failure. The wireless device 2300 can initiate a second LBT failure recovery procedure during an ongoing LBT failure recovery procedure for the cell's uplink BWP. The wireless device 2300 can, for example, cancel an ongoing LBT failure recovery procedure for the cell based on initiating a second LBT failure recovery procedure during an ongoing LBT failure recovery procedure.

[0325] The wireless device 2300 can trigger the transmission of a second uplink signal (e.g., SR, random access preamble) for a second uplink BWP in a second cell based on the detection / determination / announcement of a second uplink LBT failure. The wireless device 2300 can, for example, trigger the transmission of the second uplink signal during an ongoing LBT failure recovery procedure of the cell's uplink BWP. The wireless device 2300 can cancel an ongoing LBT failure recovery procedure of the cell based on, for example, triggering the transmission of the second uplink signal during an ongoing LBT failure recovery procedure. The wireless device 2300 can, for example, transmit / transmit the second uplink signal for a second LBT failure recovery procedure of the second cell's second uplink BWP based on canceling an ongoing LBT failure recovery procedure.

[0326] A wireless device can monitor uplink LBT failures in the uplink BWP of a cell. Monitoring uplink LBT failures may include executing one or more LBT procedures in / for an uplink transmission (e.g., PUSCH transmission, PRACH transmission, PUCCH transmission, SRS transmission) via the uplink BWP. The wireless device may determine the failure of at least one LBT procedure in / for the uplink transmission based on the execution of one or more LBT procedures. The one or more LBT procedures may include at least one LBT procedure. The wireless device may increment an LBT failure counter based on determining the failure of at least one LBT procedure. The wireless device may determine a first value for the LBT failure counter based on this increment.

[0327] The wireless device can (e.g., from a base station) receive / detect downlink signals (e.g., reference signals, DMRS via PDCCH, DMRS via GC-PDCCH, PDCCH transmissions, GC-PDCCH transmissions, DCIs (e.g., corresponding to DCI format 2_0 or any other DCI format)). The wireless device can, for example, determine the downlink burst of the base station based on the reception / detection of downlink signals. The wireless device can, for example, determine / assume that the base station has acquired a channel serving the wireless device (e.g., a licensed channel, an unlicensed channel) based on the reception / detection of downlink signals. The wireless device can determine the start of the Channel Occupied Time (COT) based on the reception / detection of downlink signals. The downlink signals can indicate the COT. The downlink signals can be a group common DCI of a group of wireless devices including the wireless device. The downlink signals can be a wireless device-specific DCI. The DCI can indicate COT information (e.g., the duration of the COT, PDCCH monitoring information, etc.).

[0328] The wireless device can initiate a COT (Confirmation of the Occurrence) based, for example, on receiving / detecting a downlink signal. The COT can correspond to a COT duration. The downlink signal can indicate the COT duration. One or more configuration parameters can indicate the COT duration. The wireless device can, for example, stop the LBT (Low Bit Detection) timer based on initiating the COT. The COT can complete / end. The COT can complete / end at the end of its duration. The wireless device can restart the LBT timer based on the end of the COT (e.g., or based on the end of the COT).

[0329] The wireless device may, for example, restart the LBT detection timer based on the start of the COT. The wireless device may or may not reset the first value of the LBT failure counter during the COT (or during the COT duration). The LBT detection timer may expire during the COT duration. Based on the expiration of the LBT detection timer, the wireless device may or may not reset the first value of the LBT failure counter during the COT duration (e.g., reset to zero). The wireless device may, for example, start counting / controlling / managing the LBT failure counter based on the first value based on the end of the COT (e.g., or based on the end of the COT duration). The wireless device may, for example, perform LBT failure detection based on the first value based on the end of the COT (e.g., or based on the end of the COT duration). If the LBT failure counter was equal to a certain value (e.g., 3 or any other value) before the COT duration (e.g., at the start of the COT), the wireless device may, for example, maintain counting / incrementing the LBT failure counter from said value after the COT duration (or at the end of the COT). The wireless device may not, for example, reset the LBT failure counter to zero during the COT duration.

[0330] The wireless device may, for example, monitor or not monitor uplink LBT failures in the cell's uplink BWP based on the activation of COT (or during COT). Not monitoring uplink LBT failures may include not performing one or more LBT procedures in / for an uplink transmission via the uplink BWP. The wireless device may, for example, stop uplink BWP LBT failure detection based on the activation of COT (or during COT).

[0331] Figure 24A and Figure 24B An exemplary data transmission based on LBT failure detection is illustrated. For example, if the LBT procedure is successful on each of the multiple LBT bandwidths, the wireless device can send / transmit data via the multiple LBT bandwidths in the uplink BWP. For example, if the LBT procedure is successful on at least one of the multiple LBT bandwidths, the wireless device can send / transmit data via at least one LBT bandwidth in the multiple LBT bandwidths in the uplink BWP.

[0332] refer to Figure 24A The wireless device can receive DCI. DCI can schedule TB transmissions (e.g., PUSCH transmissions) via uplink BWP 2404. TBs can be scheduled to transmit in one or more LBT bandwidths among a plurality of LBT bandwidths including uplink BWP 2404. A TB including one or more LBT bandwidths may include: frequency resource allocation of the TB (e.g., physical resource blocks, subcarriers) may include one or more LBT bandwidths. The one or more LBT bandwidths of the TB include LBT bandwidth 2412-2, LBT bandwidth 2412-3, and LBT bandwidth 2412-4.

[0333] To transmit a TB, the wireless device may execute one or more LBT programs in / on one or more LBT bandwidths associated with the wireless device and / or the TB. To transmit a TB, the wireless device may execute the corresponding LBT program of one or more LBT programs in / on each of the one or more LBT bandwidths. To transmit a TB, the wireless device may execute each LBT program of one or more LBT programs in / on the corresponding LBT bandwidth of one or more LBT bandwidths. The wireless device may execute a first LBT program in / on LBT bandwidth 2412-2, a second LBT program in / on LBT bandwidth 2412-3, and a third LBT program in / on LBT bandwidth 2412-4.

[0334] The wireless device can (e.g., at time slot 2428-1) determine (or detect) the failure of at least one LBT procedure among one or more LBT procedures. The wireless device can determine (or detect) the failure of a second LBT procedure in / on LBT bandwidth 2412-3. For example, if the wireless device determines the failure of at least one of the one or more LBT procedures, the wireless device may not transmit (e.g., avoid transmitting / transmitting) TB. The wireless device may, for example, avoid transmitting TB at time slot 2428-1 based on determining the failure of a second LBT procedure in / on LBT bandwidth 2412-3.

[0335] For example, if the wireless device determines that all LBT procedures of one or more LBT procedures are successful, the wireless device can send / transmit TB. The wireless device can determine the success of the first LBT procedure in / on LBT bandwidth 2412-2, the success of the second LBT procedure in / on LBT bandwidth 2412-3, and the success of the third LBT procedure in / on LBT bandwidth 2412-4. The wireless device can, for example, based on the determination of the success of the first LBT procedure in LBT bandwidth 2412-2, the second LBT procedure in LBT bandwidth 2412-3, and the third LBT procedure in LBT bandwidth 2412-4, transmit TB (e.g., data 2420) via one or more LBT bandwidths at time slot 2428-2.

[0336] refer to Figure 24B The wireless device can receive DCI. DCI can schedule TB transmissions (e.g., PUSCH transmissions) via uplink BWP 2404. TBs can be scheduled to transmit in one or more LBT bandwidths among a plurality of LBT bandwidths including uplink BWP 2408. A TB including one or more LBT bandwidths may include: frequency resource allocation of the TB (e.g., physical resource blocks, subcarriers) may include one or more LBT bandwidths. The one or more LBT bandwidths of the TB include LBT bandwidth 2416-1, LBT bandwidth 2416-2, LBT bandwidth 2416-3, and LBT bandwidth 2416-4.

[0337] To transmit a TB, the wireless device may execute one or more LBT programs in / on one or more LBT bandwidths associated with the wireless device and / or the TB. To transmit a TB, the wireless device may execute the corresponding LBT program of one or more LBT programs in / on each of the one or more LBT bandwidths. To transmit a TB, the wireless device may execute each LBT program of one or more LBT programs in / on the corresponding LBT bandwidth of one or more LBT bandwidths. The wireless device may execute a first LBT program in / on LBT bandwidth 2416-1, a second LBT program in / on LBT bandwidth 2416-2, a third LBT program in / on LBT bandwidth 2416-3, and a fourth LBT program in / on LBT bandwidth 2416-4.

[0338] The wireless device can, for example, transmit / transmit TB (e.g., data 2422) via LBT bandwidth after a successful LBT procedure. The wireless device can, for example, transmit TB (e.g., data 2422) in time slot 2432-1 via LBT bandwidths 2416-1, 2416-2, and 2416-3 based on the success of the first, second, and third LBT procedures and the failure of the fourth LBT procedure. The wireless device can, for example, transmit / transmit TB (e.g., data 2424) in time slot 2432-2 via LBT bandwidths 2416-3 and 2416-4 based on the success of the third and fourth LBT procedures and the failure of the first and second LBT procedures.

[0339] Figure 25 An exemplary data transmission based on LBT failure detection is illustrated. For example, if the LBT procedure on each of the multiple LBT bandwidths is successful, the wireless device 2500 can send / transmit data via the multiple LBT bandwidths in the uplink BWP. For example, if the LBT procedure on at least one of the multiple LBT bandwidths is unsuccessful, the wireless device 2500 may not send / transmit data.

[0340] Figure 26 An exemplary data transmission based on LBT failure detection is illustrated. For example, if the LBT procedure is successful on at least one of the multiple LBT bandwidths, the wireless device 2600 may send / transmit data via at least one of the multiple LBT bandwidths in the uplink BWP. For example, if the LBT procedure fails on all of the multiple LBT bandwidths, the wireless device 2600 may not send / transmit data.

[0341] A wireless device (e.g., wireless device 2500 and / or wireless device 2600) may receive one or more messages. A wireless device may receive one or more messages from a base station (e.g., base station 2512 and / or base station 2612). One or more messages may include one or more configuration parameters. One or more configuration parameters may be used for a cell. A cell may be a PCell. A cell may be an SCell. A cell may be a PUCCH SCell. A cell may be an unlicensed cell (e.g., a cell operating in an unlicensed frequency band). A cell may be a licensed cell (e.g., a cell operating in a licensed frequency band).

[0342] A cell may include one or more uplink BWPs, such as BWP 2516 or BWP 2616. A radio device may activate an uplink BWP. The radio device may monitor uplink LBT failures of uplink transmissions (e.g., RACH transmissions, SRS transmissions, PUSCH transmissions, PUCCH transmissions, etc.) via an uplink BWP. The radio device may monitor uplink LBT failures detected by the uplink BWP (as per reference). Figure 17 (As described). The uplink BWP can include multiple LBT bandwidths (e.g., LBT bandwidth 1, LBT bandwidth 2, LBT bandwidth 3, LBT bandwidth 4, etc.). Figure 25 and Figure 26 (As described in the text).

[0343] Wireless devices can receive DCI. DCI (e.g., Figure 25 The first DCI at time T0 is 2504, and the second DCI at time T2 is 2508; Figure 26 The first DCI 2604 and the second DCI 2608 can schedule TB transmissions (e.g., PUSCH transmissions) via the uplink BWP. The first DCI and the second DCI can schedule the transmissions of the first TB and the second TB, respectively. The first DCI 2504 and the second DCI 2508 can schedule the transmissions of the first TB 2520 and the second TB 2524, respectively. The first DCI 2604 and the second DCI 2608 can schedule the transmissions of the first TB 2620 and the second TB 2624, respectively.

[0344] TB (for example, Figure 25 The first TB 2520, the second TB 2524; and Figure 26The first TB 2620 and the second TB 2624 may include one or more LBT bandwidths from a plurality of LBT bandwidths. The TB including one or more LBT bandwidths may include: frequency resource allocation (e.g., physical resource blocks, subcarriers) of the TB may include one or more LBT bandwidths. One or more LBT bandwidths of the first TB (e.g., the first TB 2520 or the first TB 2620) (e.g., a first plurality of LBT bandwidths) may include LBT bandwidth 2, LBT bandwidth 3, and LBT bandwidth 4. One or more LBT bandwidths of the second TB (e.g., the second TB 2524 or the second TB 2624) (e.g., a second plurality of LBT bandwidths) may include LBT bandwidth 1, LBT bandwidth 2, and LBT bandwidth 3.

[0345] To transmit a TB, the wireless device may execute one or more LBT programs in / on one or more LBT bandwidths associated with the wireless device and / or the TB. To transmit a TB, the wireless device may execute the corresponding LBT program of one or more LBT programs in / on each of the one or more LBT bandwidths. To transmit a TB, the wireless device may execute each LBT program of one or more LBT programs in / on the corresponding LBT bandwidth of one or more LBT bandwidths. For a first TB (e.g., first TB 2520 and / or first TB 2620), the wireless device may execute the first LBT program in / on LBT bandwidth 2, the second LBT program in / on LBT bandwidth 3, and the third LBT program in / on LBT bandwidth 4. For a second TB (e.g., second TB 2524 and / or second TB 2624), the wireless device may execute the first LBT program in / on LBT bandwidth 1, the second LBT program in / on LBT bandwidth 2, and the third LBT program in / on LBT bandwidth 3.

[0346] The wireless device can execute one or more LBT programs in parallel for a TB. Executing one or more LBT programs in parallel for a TB can include executing one or more LBT programs simultaneously (or substantially simultaneously) for the TB.

[0347] The wireless device may execute one or more LBT procedures for a TB at different times (or at similar times). Executing one or more LBT procedures for a TB at different times may include: executing one or more first LBT procedures from the one or more LBT procedures at a first time for the TB; and executing one or more second LBT procedures from the one or more LBT procedures at a second time. The first time and the second time may be different. The first time and the second time may be the same or substantially the same.

[0348] Wireless devices (e.g., wireless device 2500) can (e.g., in) Figure 25 During time T1, the failure of at least one LBT procedure in one or more LBT procedures is determined (or detected). Determining the failure of at least one LBT procedure may include determining the failure of at least one LBT procedure on at least one LBT bandwidth in one or more LBT bandwidths. The wireless device may execute each of the at least one LBT procedure on the corresponding LBT bandwidth of the at least one LBT bandwidth. Determining the failure of at least one LBT procedure on the at least one LBT bandwidth may include determining the failure of each of the at least one LBT procedure on the corresponding LBT bandwidth of the at least one LBT bandwidth. Determining the failure of at least one LBT procedure may include determining the failure of an LBT procedure on at least one LBT bandwidth in one or more LBT bandwidths. At least one LBT procedure of the first TB may include a second LBT procedure on LBT bandwidth 3, such as... Figure 25 Described.

[0349] The wireless device (e.g., wireless device 2500) may support at least a first type of uplink transmission. The wireless device may be capable of supporting the first type of uplink transmission. The wireless device may send / transmit to the base station at least one message including capability parameters. The capability parameters may indicate that the wireless device supports the first type of uplink transmission. For example, if the wireless device supports the first type of uplink transmission, the wireless device may transmit a TB (e.g., a second TB 2524) based on the first type of uplink transmission.

[0350] One or more configuration parameters may indicate at least a first type of uplink transmission among one or more types of uplink transmissions. The DCI (e.g., a first DCI 2504 and / or a second DCI 2508) may include a field indicating the first type of uplink transmission among one or more types of uplink transmissions. One or more configuration parameters may indicate one or more types of uplink transmissions.

[0351] For example, based on the determination that at least one LBT procedure has failed, the wireless device may abort the transmission of TB (e.g., the first TB 2520 at time T1) in a first type of uplink transmission. For example, based on the determination that at least one LBT procedure has failed, the wireless device may not send / transmit TB (e.g., the first TB 2520 at time T1) in a first type of uplink transmission.

[0352] If the wireless device determines, for example, based on a first type of uplink transmission, that at least one LBT procedure has failed, then the wireless device (e.g., wireless device 2500) can (e.g., in...) Figure 25 The LBT failure counter is incremented at time T1 or later (e.g., reference). Figure 17The LBT failure counter is described. If the wireless device determines that at least one LBT procedure has failed, for example based on capability parameters indicating that the wireless device supports a first type of uplink transmission, the wireless device may increment the LBT failure counter. If the wireless device determines that at least one LBT procedure has failed, for example based on a DCI indicating a first type of uplink transmission, the wireless device may increment the LBT failure counter. If the wireless device determines that at least one LBT procedure has failed, for example based on one or more configuration parameters indicating a first type of uplink transmission, the wireless device may increment the LBT failure counter.

[0353] The wireless device can determine (or detect) the failure and / or success of the LBT procedure. The wireless device can (e.g., in...) Figure 26 At or after time T1, Figure 24B In time slots 2332-1 and 2332-2 (or detection), the failure of at least one first LBT procedure and the success of at least one second LBT procedure among one or more LBT procedures are determined. Determining the failure of at least one first LBT procedure and the success of at least one second LBT procedure may include the wireless device determining that at least one, but not all, of the one or more first LBT procedures has failed. Determining the failure of at least one, but not all, of the one or more first LBT procedures may include determining the failure of at least one first LBT procedure on at least one, but not all, of one or more LBT bandwidths. The wireless device may execute each of the at least one first LBT procedure on the corresponding LBT bandwidth of the at least one first LBT bandwidth. Determining the failure of at least one first LBT procedure on at least one first LBT bandwidth may include determining the failure of each of the at least one first LBT procedure on the corresponding LBT bandwidth of the at least one first LBT bandwidth.

[0354] Determining the failure of at least one first LBT procedure and the success of at least one second LBT procedure may involve the wireless device determining the success, but not all success, of at least one second LBT procedure among one or more LBT procedures. Determining the success, but not all success, of at least one second LBT procedure among one or more LBT procedures may involve determining the success of at least one second LBT procedure on at least one second LBT bandwidth of one or more LBT bandwidths. The wireless device may execute each of the at least one second LBT procedure on the corresponding LBT bandwidth of the at least one second LBT bandwidth. Determining the success of at least one second LBT procedure on at least one second LBT bandwidth may involve determining the success of each LBT procedure on the corresponding LBT bandwidth of the at least one second LBT bandwidth.

[0355] One or more LBT bandwidths may include at least one first LBT bandwidth and at least one second LBT bandwidth. The at least one first LBT bandwidth and at least one second LBT bandwidth may be orthogonal. The at least one first LBT bandwidth and at least one second LBT bandwidth may (or may not) overlap. The at least one first LBT bandwidth may include the LBT bandwidth of one or more LBT bandwidths. For example, based on the fact that the at least one first LBT bandwidth and at least one second LBT bandwidth are orthogonal (or do not overlap), the at least one second LBT bandwidth may not include any LBT bandwidth. The at least one second LBT bandwidth may include the LBT bandwidth of one or more LBT bandwidths. For example, based on the fact that the at least one first LBT bandwidth and at least one second LBT bandwidth are orthogonal (or do not overlap), the at least one first LBT bandwidth may not include any LBT bandwidth.

[0356] At least one second LBT bandwidth can be continuous in frequency (e.g., Figure 24B LBT bandwidths 2416-1, 2416-2, and 2416-3 in time slot 2432-1; Figure 24B In time slot 2432-2, LBT bandwidths 2416-3 and 2416-4 are used. LBT bandwidths 2416-1 and 2416-3 may not be frequency-contiguous. LBT bandwidths 2416-2 and 2416-4 may be frequency-contiguous. LBT bandwidths 2416-1 and 2416-2 may be frequency-contiguous. LBT bandwidths 2416-3 and 2416-4 may be frequency-contiguous.

[0357] 24references Figure 24B At least one first LBT program may include a first LBT program in / on LBT bandwidth 2416-1 and a second LBT program in / on LBT bandwidth 2416-2. At least one second LBT program may include a third LBT program in / on LBT bandwidth 2416-3 and a fourth LBT program in / on LBT bandwidth 2416-4.

[0358] refer to Figure 26 At least one first LBT program in the first TB may include a second LBT program on LBT bandwidth 3. At least one second LBT program in the first TB may include a first LBT program on LBT bandwidth 2 and a third LBT program on LBT bandwidth 4.

[0359] The wireless device (e.g., wireless device 2600) may support at least the second type of uplink transmission. The wireless device may be capable of supporting the second type of uplink transmission. The wireless device may send / transmit to the base station at least one message including capability parameters. The capability parameters may indicate that the wireless device supports the second type of uplink transmission. The wireless device may send / transmit TBs (e.g., first TB 2620 and / or second TB 2624) based on the second type of uplink transmission.

[0360] One or more configuration parameters may indicate at least a second type of uplink transmission among one or more types of uplink transmissions. A DCI (e.g., a first DCI 2604 and / or a second DCI 2608) may include a field indicating a second type of uplink transmission among one or more types of uplink transmissions. One or more configuration parameters may indicate one or more types of uplink transmissions. A base station (e.g., base station 2512 or base station 2612) may indicate a first type of uplink transmission or a second type of uplink transmission based on the cell's deployment scenario. A base station may indicate a second type of uplink transmission in a high-interference environment and a first type of uplink transmission in a low-interference environment, and so on.

[0361] The wireless device (e.g., wireless device 2600) may, for example, in a second type of uplink transmission and based on determining the success of at least one second LBT procedure, (e.g., in...) Figure 26 The transmission of TB is performed via at least one second LBT bandwidth of the uplink BWP (at or after time T1). A wireless device (e.g., wireless device 2600) may, for example, in a second type of uplink transmission and based on the success of determining at least one second LBT procedure, transmit / transmit TB via at least one second LBT bandwidth of the uplink BWP (e.g., in time T1 or later). Figure 26 The first TB (2620) is sent / transmitted at or after time T1.

[0362] Wireless devices supporting (or capable of) the second type of uplink transmission can, for example, modify the format of the TB (e.g., PUSCH transmission) by (e.g., recoding or puncturing, PHY channel reformatting, baseband filtering, adaptive filtering, etc.) based on determining the failure of at least one first LBT procedure and the success of at least one second LBT procedure. Wireless devices supporting (or capable of) the second type of uplink transmission can, for example, modify the format during processing time based on determining the failure of at least one first LBT procedure and the success of at least one second LBT procedure. Wireless devices unable to perform the second type of uplink transmission can, for example, not modify the TB format during processing time based on determining the failure of at least one first LBT procedure and the success of at least one second LBT procedure.

[0363] A wireless device (e.g., wireless device 2600) may, for example, perform a TB transmission via at least one second LBT bandwidth of the uplink BWP based on determining the failure of at least one first LBT procedure on at least one second LBT bandwidth and the success of at least one second LBT procedure (e.g., in a second type of uplink transmission). Figure 26 The first TB 2620 transmission is performed at or after time T1. The wireless device may, for example, in a second type of uplink transmission and based on the success of determining at least one second LBT procedure, transmit / transmit the TB via at least one second LBT bandwidth of the uplink BWP (e.g., in...). Figure 26 The first TB (2620) is sent / transmitted at or after time T1.

[0364] For example, if a wireless device determines, for example, the failure of at least one first LBT procedure and the success of at least one second LBT procedure based on a second type of uplink transmission, then the wireless device (e.g., wireless device 2600) can (e.g., in...) Figure 26 The LBT failure counter is not incremented at time T1 or later (e.g., as referenced). Figure 17 The LBT failure counter is described. If the wireless device determines the failure of at least one first LBT procedure and the success of at least one second LBT procedure based, for example, on a capability parameter indicating that the wireless device supports a second type of uplink transmission, the wireless device may not increment the LBT failure counter. If the wireless device determines the failure of at least one first LBT procedure and the success of at least one second LBT procedure based, for example, on a DCI indicating a second type of uplink transmission, the wireless device may not increment the LBT failure counter. If the wireless device determines the failure of at least one first LBT procedure and the success of at least one second LBT procedure based, for example, on one or more configuration parameters indicating a second type of uplink transmission, the wireless device may not increment the LBT failure counter.

[0365] Wireless devices (e.g., wireless device 2500) can (e.g., in) Figure 25The success of one or more LBT procedures is determined (or detected) at time T3 or later. Determining the success of one or more LBT procedures may include determining the success of each LBT procedure within a corresponding LBT bandwidth in one or more LBT bandwidths. The wireless device may determine the success of a first LBT procedure in / on LBT bandwidth 1, a second LBT procedure in / on LBT bandwidth 2, and a third LBT procedure in / on LBT bandwidth 3 for a second TB (e.g., second TB 2524).

[0366] A wireless device (e.g., wireless device 2500) can perform a TB transmission based on the success of one or more LBT procedures in, for example, a first type of uplink transmission (e.g., in...). Figure 25 The second TB2524 transmission is performed at or after time T3. The wireless device may transmit a TB based on the success of one or more LBT procedures in, for example, a first-type uplink transmission (e.g., in...). Figure 25 The second TB (2524) is transmitted at or after time T3. The wireless device can transmit TB via one or more LBT bandwidths of the uplink BWP.

[0367] If the wireless device determines the success of one or more LBT procedures, for example, based on the first type of uplink transmission, then the wireless device (e.g., wireless device 2500) can (e.g., in...) Figure 25 The LBT failure counter is not incremented at time T3 or later (e.g., as referenced). Figure 17 The LBT failure counter is described. If the wireless device determines the success of one or more LBT procedures, for example, based on capability parameters indicating that the wireless device supports a first type of uplink transmission, the wireless device may not increment the LBT failure counter. If the wireless device determines the success of one or more LBT procedures, for example, based on DCI indicating a first type of uplink transmission, the wireless device may not increment the LBT failure counter. If the wireless device determines the success of one or more LBT procedures, for example, based on one or more configuration parameters indicating a first type of uplink transmission, the wireless device may not increment the LBT failure counter.

[0368] Wireless devices (e.g., wireless device 2600) can (e.g., in) Figure 26The failure of one or more LBT procedures can be determined (or detected) at time T3 or later. Determining the failure of one or more LBT procedures may include determining the failure of each of the one or more LBT procedures on the corresponding LBT bandwidth within one or more LBT bandwidths. The wireless device may (e.g., in...) Figure 26 At time T3 or later, for the second TB (e.g., second TB 2624), the failure of the first LBT procedure in LBT bandwidth 1, the failure of the second LBT procedure in LBT bandwidth 2, and the failure of the third LBT procedure in LBT bandwidth 3 are determined.

[0369] A wireless device (e.g., wireless device 2600) may abandon a TB transmission (e.g., in the case of determining the failure of one or more LBT procedures in, for example, a second type of uplink transmission) based on the fact that such a procedure has failed. Figure 26 The transmission of the second TB2624 may be abandoned at or after time T3. The wireless device may, based on determining the failure of one or more LBT procedures in, for example, a second type of uplink transmission, refrain from sending / transmitting TBs (e.g., in...). Figure 26 No second TB 2624 will be sent / transmitted at or after time T3.

[0370] If the wireless device determines, for example, a failure of one or more LBT procedures based on a second type of uplink transmission, then the wireless device (e.g., wireless device 2600) can (e.g., in...) Figure 26 The LBT failure counter is incremented at time T3 or later (e.g., reference). Figure 17 The LBT failure counter is described. If the wireless device determines that one or more LBT procedures have failed, for example based on capability parameters instructing the wireless device to support a second type of uplink transmission, the wireless device may increment the LBT failure counter. If the wireless device determines that one or more LBT procedures have failed, for example based on a DCI indicating a second type of uplink transmission, the wireless device may increment the LBT failure counter. If the wireless device determines that one or more LBT procedures have failed, for example based on one or more configuration parameters indicating a second type of uplink transmission, the wireless device may increment the LBT failure counter.

[0371] For uplink transmissions, the wireless device may execute a first plurality of LBT procedures within / on the first plurality of LBT bandwidths of the uplink BWP. Uplink transmissions (e.g., PUSCH transmissions, transport blocks, PUCCH transmissions, SRS transmissions, PRACH transmissions) may include the first plurality of LBT bandwidths. For uplink transmissions, the wireless device may execute each of the plurality of first LBT procedures within / on the corresponding LBT bandwidth of the first plurality of LBT bandwidths.

[0372] refer to Figure 24B The first plurality of LBT programs may include a first LBT program, a second LBT program, a third LBT program, and a fourth LBT program. The first plurality of LBT bandwidths may include LBT bandwidth 2416-1, LBT bandwidth 2416-2, LBT bandwidth 2416-3, and LBT bandwidth 2416-4. The wireless device may execute the first LBT program in / on LBT bandwidth 2416-1, execute the second LBT program in / on LBT bandwidth 2416-2, execute the third LBT program in / on LBT bandwidth 2416-3, and execute the fourth LBT program in / on LBT bandwidth 2416-4.

[0373] refer to Figure 26 For the second TB 2624, the first plurality of LBT programs may include a first LBT program, a second LBT program, and a third LBT program. For the second TB 2624, the first plurality of LBT bandwidths may include LBT bandwidth 1, LBT bandwidth 2, and LBT bandwidth 3. A wirel...

Claims

1. A method comprising: The amount of Listen-After-Talk (LBT) failure in the active uplink bandwidth portion (BWP) of the cell is determined by the radio device; Based on the quantity meeting the threshold, an uplink signal associated with the LBT failure recovery procedure of the active uplink BWP of the cell is sent. The LBT failure recovery procedure can be cancelled based on at least one of the following: The LBT failure recovery reconfiguration parameters for the cell are received during the LBT failure recovery procedure; During the LBT failure recovery procedure, downlink information indicating BWP handover for the cell is received; The cell is deactivated during the LBT failure recovery procedure; or The request to reset the MAC layer is received by the Media Access Control (MAC) layer of the wireless device from the Radio Resource Control (RRC) layer of the wireless device and during the LBT failure recovery procedure.

2. The method according to claim 1, further comprising: Based on canceling the LBT failure recovery procedure, the count of the quantity of LBT failure is set to zero.

3. The method according to any one of claims 1 and 2, wherein, The quantity for determining LBT failure includes determining the quantity during the random access procedure associated with the cell.

4. The method according to any one of claims 1 and 2, further comprising: The quantity based on LBT failure cancels the random access procedure associated with the cell, wherein the uplink signal is sent based on the cancellation of the random access procedure.

5. The method according to any one of claims 1 and 2, further comprising: Initiate the beam failure recovery procedure for the aforementioned cell; This enables the transmission of the following items: LBT MAC control element (LBT MACCE) used for the LBT failure recovery procedure; and Beam Failure Recovery MAC Control Element (BFRMAC CE) used in the beam failure recovery procedure; as well as Transmit a MAC Protocol Data Unit (MAC PDU), the MAC Protocol Data Unit being included in the logical channel of the BFR MAC CE preceding the logical channel of the LBT MAC CE.

6. The method according to any one of claims 1 and 2, wherein, Sending the uplink signal includes sending the uplink signal via a second cell different from the cell.

7. The method according to any one of claims 1 and 2, wherein, The uplink signal includes at least one of the following: Random access preamble; Scheduling request; or LBT MAC control element.

8. The method according to any one of claims 1 and 2, further comprising: Based on the determination that the LBT of the cell has failed, increment the LBT counter of the cell; as well as Based on canceling the LBT failure recovery procedure, the LBT counter is set to zero.

9. The method according to any one of claims 1 and 2, wherein, Deactivation of the cell is based on at least one of the following: Received MAC control element; or The timer expired.

10. The method according to any one of claims 1 and 2, wherein, The downlink information includes at least one of the following: Downlink Control Information (DCI); or RRC message.

11. The method according to any one of claims 1 and 2, further comprising receiving one or more messages including one or more configuration parameters of the cell, wherein, The one or more configuration parameters indicate one or more of the following: The maximum LBT failure count of the active uplink BWP of the cell; or The LBT failure detection timer for the active uplink BWP of the cell.

12. The method according to any one of claims 1 and 2, further comprising: The LBT failure was determined based on the fact that the uplink BWP for the activity was occupied.

13. A wireless device, comprising: One or more processors; as well as A memory for storing instructions that, when executed by the one or more processors, cause the wireless device to perform the method according to any one of claims 1-12.

14. A system comprising: A wireless device configured to perform the method according to any one of claims 1-12; as well as A base station configured to receive the uplink signal.

15. A computer-readable medium storing instructions that, when executed, cause the method according to any one of claims 1-12 to be performed.

Images