Beam failure recovery based on scheduling request

Abstract

The wireless device transmits a first scheduling request (SR) based on a buffer status reporting procedure. A second SR is triggered in response to an initial beam failure recovery. The second SR is transmitted via an uplink control channel resource configured for the second SR. A first downlink control information is received via a downlink control channel as a response to the second SR. Based on receiving the first downlink control information: keeping the first SR pending, and canceling the second SR for the beam failure recovery.

Description

[0001] Divisional application

[0002] This application is a divisional application of application number 2019800184909, application date April 1, 2019, and titled “Beam Fault Recovery Based on Scheduling Request”.

[0003] CROSS-REFERENCE TO RELATED APPLICATIONS

[0004] This application claims the benefit of U.S. Provisional Application No. 62 / 650,733, filed on March 30, 2018, which is incorporated herein by reference in its entirety. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Examples of several of the various embodiments of the present disclosure are described herein with reference to the drawings.

[0006] Figure 1 is a diagram of an example RAN architecture in accordance with aspects of an embodiment of the present disclosure.

[0007] Figure 2A is a diagram of an example user plane protocol stack according to aspects of an embodiment of the present disclosure.

[0008] Figure 2B is a diagram of an example control plane protocol stack in accordance with aspects of an embodiment of the present disclosure.

[0009] Figure 3 is a diagram of an example wireless device and two base stations in accordance with aspects of an embodiment of the present disclosure.

[0010] Figure 4A , Figure 4B , Figure 4C and Figure 4D is an example diagram of uplink and downlink signal transmission according to aspects of an embodiment of the present disclosure.

[0011] Figure 5A is a diagram of an example uplink channel map and example uplink physical signals according to aspects of an embodiment of the present disclosure.

[0012] Figure 5B is a diagram of an example downlink channel map and example downlink physical signals according to aspects of an embodiment of the present disclosure.

[0013] Figure 6 is a diagram depicting example transmission times or reception times of carriers according to aspects of embodiments of the present disclosure.

[0014] Fig. 7A and Figure 7B is a diagram depicting an example set of OFDM subcarriers in accordance with aspects of an embodiment of the present disclosure.

[0015] Figure 8 is a diagram depicting example OFDM radio resources in accordance with aspects of an embodiment of the present disclosure.

[0016] Fig.9A is a diagram depicting example CSI-RS and / or SS block transmissions in a multi-beam system.

[0017] Fig. 9B is a diagram depicting an example downlink beam management procedure in accordance with aspects of an embodiment of the present disclosure.

[0018] Fig.10 is an example diagram of a configured BWP in accordance with aspects of an embodiment of the present disclosure.

[0019] Fig.11A and Fig. 11B is a diagram of example multiple connectivity according to aspects of an embodiment of the present disclosure.

[0020] Fig.12 is a diagram of an example random access procedure according to aspects of an embodiment of the present disclosure.

[0021] Fig.13 is the structure of an example MAC entity according to aspects of an embodiment of the present disclosure.

[0022] Fig.14 is an example RAN architecture diagram according to aspects of an embodiment of the present disclosure.

[0023] Fig.15 is a diagram of example RRC states in accordance with aspects of an embodiment of the present disclosure.

[0024] Fig.16A and Fig. 16B is an example of a downlink beam failure scenario according to aspects of an embodiment of the present disclosure.

[0025] Fig.17 is an example of a downlink beam failure recovery procedure according to aspects of an embodiment of the present disclosure.

[0026] Fig.18 is an example of a scheduling request procedure according to aspects of an embodiment of the present disclosure.

[0027] Fig.19 is an example of a request configuration for a BFR program according to aspects of an embodiment of the present disclosure.

[0028] Fig. 20 is an example of a flow diagram with an example of requesting configuration according to aspects of an embodiment of the present disclosure.

[0029] Fig.21is an example of a BFR procedure according to aspects of an embodiment of the present disclosure.

[0030] Fig. 22 is an example of a BFR procedure according to aspects of an embodiment of the present disclosure.

[0031] Fig.23 is an example flow chart according to aspects of an embodiment of the present disclosure.

[0032] Fig.24 is an example flow chart according to aspects of an embodiment of the present disclosure.

[0033] Fig.25 is an example flow chart according to aspects of an embodiment of the present disclosure.

[0034] Fig.26 is an example flow chart according to aspects of an embodiment of the present disclosure.

[0035] Fig. 27 is an example flow chart according to aspects of an embodiment of the present disclosure.

[0036] Fig.28 is an example flow chart according to aspects of an embodiment of the present disclosure.

[0037] Fig.29 is an example flow chart according to aspects of an embodiment of the present disclosure.

[0038] Fig.30 is an example flow chart according to aspects of an embodiment of the present disclosure.

[0039] Fig.31 is an example flow chart according to aspects of an embodiment of the present disclosure.

[0040] Fig.32 is an example flow chart according to aspects of an embodiment of the present disclosure.

[0041] Fig.33 is an example flow chart according to aspects of an embodiment of the present disclosure.

[0042] Fig.34 is an example flow chart according to aspects of an embodiment of the present disclosure.

[0043] Fig.35 is an example flow chart according to aspects of an embodiment of the present disclosure. DETAILED DESCRIPTION

[0044] Example embodiments of the present disclosure implement the operation of a beam failure recovery procedure. Embodiments of the technology disclosed herein may be employed in the technical field of multi-carrier communication systems. More specifically, embodiments of the technology disclosed herein may relate to a beam failure recovery procedure in a multi-carrier communication system.

[0045] The following abbreviations are used throughout this disclosure:

[0046] 3GPP Third Generation Partnership Project

[0047] 5GC 5G Core Network

[0048] ACK

[0049] AMF Access and Mobility Management Function

[0050] ARQ Automatic Repeat Request

[0051] AS access layer

[0052] ASIC Application-Specific Integrated Circuit

[0053] BA Bandwidth Adaptation

[0054] BCCH Broadcast Control Channel

[0055] BCH Broadcast Channel

[0056] BPSK Binary Phase Shift Keying

[0057] BWP Bandwidth Part

[0058] BSR Buffer Status Report

[0059] CA Carrier Aggregation

[0060] CC Component Carrier

[0061] CCCH Common Control Channel

[0062] CDMA Code Division Multiple Access

[0063] CN Core Network

[0064] CP Cyclic Prefix

[0065] CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplexing

[0066] C-RNTI Cell-Radio Network Temporary Identifier

[0067] CS Configured Scheduling

[0068] CSI Channel State Information

[0069] CSI-RS Channel State Information-Reference Signal

[0070] CQI Channel Quality Indicator

[0071] CSS Common Search Space

[0072] CU Central Unit

[0073] DC Dual Connectivity

[0074] DCCH Dedicated Control Channel

[0075] DCI Downlink Control Information

[0076] DL Downlink

[0077] DL-SCH Downlink Shared Channel

[0078] DM-RS Demodulation Reference Signal

[0079] DRB Data Radio Bearing

[0080] DRX Discontinuous Reception

[0081] DTCH Dedicated Traffic Channel

[0082] DU Distributed Unit

[0083] EPC Evolved Packet Core

[0084] E-UTRA Evolved UMTS Terrestrial Radio Access

[0085] E-UTRAN Evolved Universal Terrestrial Radio Access Network

[0086] FDD Frequency Division Duplex

[0087] FPGA Field Programmable Gate Array

[0088] F1-C F1-Control Plane

[0089] F1-U F1-User Plane

[0090] gNB Next Generation Node B

[0091] HARQ Hybrid Automatic Repeat Request

[0092] HDL Hardware Description Language

[0093] IE Information Elements

[0094] IP Internet Protocol

[0095] LCID Logical Channel Identifier

[0096] LTE Long Term Evolution

[0097] MAC Media Access Control

[0098] MCG Master Cell Group

[0099] MCS modulation and coding scheme

[0100] MeNB Leading Node B

[0101] MIB Master Information Block

[0102] MME Mobility Management Entity

[0103] MN Master Node

[0104] NACK Negative Acknowledgement

[0105] NAS Non-Access Layer

[0106] NG CP Next Generation Control Plane

[0107] NGC Next Generation Core

[0108] NG-C NG-Control Plane

[0109] ng-eNB Next Generation Evolved Node B

[0110] NG-U NG-User Plane

[0111] NR New Radio

[0112] NR MAC New Radio MAC

[0113] NR PDCP New Radio PDCP

[0114] NR PHY New Radio Physics

[0115] NR RLC New Radio RLC

[0116] NR RRC New Radio RRC

[0117] NSSAI Network Slice Selection Assistant Information

[0118] O&M Operation and Maintenance

[0119] OFDM Orthogonal Frequency Division Multiplexing

[0120] PBCH Physical Broadcast Channel

[0121] PCC Primary Component Carrier

[0122] PCCH Paging Control Channel

[0123] PCell Primary Community

[0124] PCH Paging Channel

[0125] PDCCH Physical Downlink Control Channel

[0126] PDCP Packet Data Convergence Protocol

[0127] PDSCH Physical Downlink Shared Channel

[0128] PDU Protocol Data Unit

[0129] PHICH Physical HARQ Indicator Channel

[0130] PHY

[0131] PLMN Public Land Mobile Network

[0132] PMI Precoding Matrix Indicator

[0133] PRACH Physical Random Access Channel

[0134] PRB Physical Resource Block

[0135] PSCell Primary Secondary Cell

[0136] PSS Primary Synchronization Signal

[0137] pTAG Primary Timing Advance Group

[0138] PT-RS Phase Tracking Reference Signal

[0139] PUCCH Physical Uplink Control Channel

[0140] PUSCH Physical Uplink Shared Channel

[0141] QAM Quadrature Amplitude Modulation

[0142] QFI Quality of Service Indicator

[0143] QoS Quality of Service

[0144] QPSK Quadrature Phase Shift Keying

[0145] RA Random Access

[0146] RACH Random Access Channel

[0147] RAN Radio Access Network

[0148] RAT Radio Access Technology

[0149] RA-RNTI Random Access-Radio Network Temporary Identifier

[0150] RB Resource Block

[0151] RBG Resource Block Group

[0152] RI Rank Indicator

[0153] RLC Radio Link Control

[0154] RRC Radio Resource Control

[0155] RS reference signal

[0156] RSRP Reference Signal Received Power

[0157] SCC Secondary Component Carrier

[0158] SCell Secondary Cell

[0159] SCG Secondary Cell Group

[0160] SC-FDMA Single Carrier Frequency Division Multiple Access

[0161] SDAP Service Data Adaptation Protocol

[0162] SDU Service Data Unit

[0163] SeNB Secondary Evolved Node B

[0164] SFN System Frame Number

[0165] S-GW Service Gateway

[0166] SI System Information

[0167] SIB System Information Block

[0168] SMF session management functions

[0169] SN Secondary Node

[0170] SpCell Special Cell

[0171] SR Scheduling Request

[0172] SRB Signalling Radio Carrier

[0173] SRS Sounding Reference Signal

[0174] SS Sync Signal

[0175] SSS Secondary Sync Signal

[0176] sTAG Secondary Timing Advance Group

[0177] TA Timing Advance

[0178] TAG Timing Advance Group

[0179] TAI Tracking Area Identifier

[0180] TAT Time Alignment Timer

[0181] TB Transfer Block

[0182] TC-RNTI Temporary Cell-Radio Network Temporary Identifier

[0183] TDD Time Division Duplex

[0184] TDMA Time Division Multiple Access

[0185] TTI Transmit Time Interval

[0186] UCI Uplink Control Information

[0187] UE User Equipment

[0188] UL Uplink

[0189] UL-SCH Uplink Shared Channel

[0190] UPF User Plane Function

[0191] UPGW User Plane Gateway

[0192] VHDL VHSIC Hardware Description Language

[0193] Xn-C Xn-Control Plane

[0194] Xn-U Xn-User Plane

[0195] Various physical layer modulation and transmission mechanisms may be used to implement example embodiments of the present disclosure. Example transmission mechanisms may include, but are not limited to, code division multiple access (CDMA), orthogonal frequency division multiple access (OFDMA), time division multiple access (TDMA), wavelet techniques, etc. Hybrid transmission mechanisms such as TDMA / CDMA and OFDM / CDMA may also be employed. Various modulation schemes may be applied to signal transmission in the physical layer. Examples of modulation schemes include, but are not limited to, phase, amplitude, code, combinations of these, and / or the like. Example radio transmission methods may implement quadrature amplitude modulation (QAM) using binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), 16-QAM, 64-QAM, 256-QAM, etc. Physical radio transmission may be enhanced by dynamically or semi-dynamically changing the modulation and coding schemes according to transmission requirements and radio conditions.

[0196] Figure 1is an example radio access network (RAN) architecture in accordance with aspects of an embodiment of the present disclosure. As shown in the example, the RAN node may be a next generation node B (gNB) (e.g., 120A, 120B) that provides a new radio (NR) user plane and control plane protocol termination to a first wireless device (e.g., 110A). In an example, the RAN node may be a next generation evolved node B (ng-eNB) (e.g., 120C, 120D) that provides an evolved UMTS terrestrial radio access (E-UTRA) user plane and control plane protocol termination to a second wireless device (e.g., 110B). The first wireless device may communicate with the gNB via a Uu interface. The second wireless device may communicate with the ng-eNB via a Uu interface.

[0197] The gNB or ng-eNB can host functions such as: radio resource management and scheduling, IP header compression, encryption and integrity protection of data, selection of access and mobility management function (AMF) at the user equipment (UE) attachment, routing of user plane and control plane data, connection setup and release, scheduling and transmission of paging messages (originating from AMF), scheduling and transmission of system broadcast information (originating from AMF or operation and maintenance (O&M)), measurements and measurement report configuration, transport layer packet marking in uplink, session management, network slice support, Quality of Service (QoS) flow management and mapping to data radio bearers, support for UE in RRC_INACTIVE state, distribution function of non-access stratum (NAS) messages, RAN sharing, and dual connectivity or tight interworking between NR and E-UTRA.

[0198] In an instance, one or more gNBs and / or one or more ng-eNBs may be interconnected to each other via an Xn interface. A gNB or ng-eNB may be connected to a 5G core network (5GC) via an NG interface. In an instance, a 5GC may include one or more AMF / User Planning Function (UPF) functions (e.g., 130A or 130B). A gNB or ng-eNB may be connected to the UPF via an NG user plane (NG-U) interface. The NG-U interface may provide delivery of user plane protocol data units (PDUs) (e.g., non-guaranteed delivery) between the RAN node and the UPF. A gNB or ng-eNB may be connected to the AMF via an NG control plane (NG-C) interface. The NG-C interface may provide functions such as NG interface management, UE context management, UE mobility management, transmission of NAS messages, paging, PDU session management, configuration delivery, or warning message transmission.

[0199] In one instance, the UPF may host functions such as an anchor point for intra / inter-radio access technology (RAT) mobility (when applicable), an external PDU session point for interconnection to a data network, packet routing and forwarding, user plane portion of packet inspection and policy rule enforcement, service usage reporting, an uplink classifier to support routing of service flows to the data network, a branch point to support multi-host PDU sessions, QoS processing for the user plane (e.g., packet filtering, gating), uplink (UL) / downlink (DL) rate enforcement, uplink service verification (e.g., service data flow (SDF) to QoS flow mapping), downlink packet buffering and / or downlink data notification triggering.

[0200] In one instance, the AMF may host functions such as NAS signaling termination, NAS signaling security, access layer (AS) security control, core network (CN) inter-node signaling for mobility between 3rd Generation Partnership Project (3GPP) access networks, idle mode UE reachability (e.g., control and execution of paging retransmissions), registration area management, support for intra-system and inter-system mobility, access authentication, access authorization including roaming rights check, mobility management control (subscription and policy), support for network slice and / or session management function (SMF) selection, etc.

[0201] Figure 2Ais an example user plane protocol stack, in which service data adaptation protocol (SDAP) (e.g., 211 and 221), packet data convergence protocol (PDCP) (e.g., 212 and 222), radio link control (RLC) (e.g., 213 and 223), and medium access control (MAC) (e.g., 214 and 224) sublayers and physical (PHY) (e.g., 215 and 225) layers may be terminated in a wireless device (e.g., 110) and a gNB (e.g., 120) on the network side. In an example, the PHY layer provides transport services to higher layers (e.g., MAC, RRC, etc.). In an example, the services and functions of the MAC sublayer may include mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) belonging to one or different logical channels into / demultiplexing of transport blocks (TBs) delivered to / from the PHY layer, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)), priority handling between UEs through dynamic scheduling, priority handling between logical channels of a UE through logical channel prioritization and / or padding. The MAC entity may support one or more parameter sets and / or transmission timings. In an example, mapping restrictions in logical channel prioritization may control which parameter set and / or transmission timing a logical channel may use. In an example, the RLC sublayer may support transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM) transmission modes. The RLC configuration may be based on each logical channel, independent of the parameter set and / or transmission time interval (TTI) duration. In an example, the automatic repeat request (ARQ) can operate on any parameter set and / or TTI duration configured for the logical channel. In an example, the services and functions of the PDCP layer for the user plane may include sequence numbering, header compression and decompression, delivery, reordering and duplication detection of user data, PDCP PDU routing (e.g., in the case of separate carriers), retransmission, encryption, decryption and integrity protection of PDCP SDUs, PDCP SDU discards, PDCP reconstruction and data recovery of RLC AM, and / or duplication of PDCP PDUs. In an example, the services and functions of SDAP may include mapping between QoS flows and data radio bearers. In an example, the services and functions of SDAP may include mapping quality of service indicators (QFIs) in DL and UL packets. In an example, the protocol entities of SDAP may be configured for individual PDU sessions.

[0202] Figure 2Bis an example control plane protocol stack, wherein PDCP (e.g., 233 and 242), RLC (e.g., 234 and 243) and MAC (e.g., 235 and 244) sublayers and PHY (e.g., 236 and 245) layers may terminate in a wireless device (e.g., 110) and a gNB (e.g., 120) on the network side and perform the above services and functions. In an example, RRC (e.g., 232 and 241) may terminate in a wireless device and a gNB on the network side. In an example, the services and functions of RRC may include: broadcasting system information related to AS and NAS, paging initiated by 5GC or RAN, establishment, maintenance and release of an RRC connection between a UE and a RAN, security functions including key management, establishment, configuration, maintenance and release of a signaling radio bearer (SRB) and a data radio bearer (DRB), mobility functions, QoS management functions, UE measurement reporting and control of reporting, detection of recovery from radio link failure, and / or delivery of NAS messages from UE to NAS / from NAS to UE. In an example, the NAS control protocol (e.g., 231 and 251) may be terminated in the wireless device and AMF (e.g., 130) on the network side, and may perform functions such as authentication, mobility management between UE and AMF for 3GPP access and non-3GPP access, and session management between UE and SMF for 3GPP access and non-3GPP access.

[0203] In an example, a base station may configure a plurality of logical channels for a wireless device. A logical channel in the plurality of logical channels may correspond to a radio bearer, and the radio bearer may be associated with a QoS requirement. In an example, the base station may configure a logical channel to be mapped to one or more TTIs / parameter sets in a plurality of TTIs / parameter sets. The wireless device may receive downlink control information (DCI) indicating an uplink grant via a physical downlink control channel (PDCCH). In an example, the uplink grant may be for a first TTI / parameter set and may indicate an uplink resource for transmission of a transport block. The base station may configure each of the plurality of logical channels, wherein one or more parameters will be used by a logical channel prioritization procedure at a MAC layer of the wireless device. The one or more parameters may include a priority, a prioritized bit rate, and the like. A logical channel in the plurality of logical channels may correspond to one or more buffers including data associated with the logical channel. The logical channel prioritization procedure may allocate uplink resources to one or more first logical channels and / or one or more MAC control elements (CEs) in the plurality of logical channels. One or more first logical channels may be mapped to a first TTI / parameter set. The MAC layer at the wireless device may multiplex one or more MAC CEs and / or one or more MAC SDUs (e.g., logical channels) in a MAC PDU (e.g., a transport block). In an example, the MAC PDU may include a MAC header including a plurality of MAC subheaders. A MAC subheader in a plurality of MAC subheaders may correspond to a MAC CE or MAC SUD (logical channel) in one or more MAC CEs and / or one or more MAC SDUs. In an example, a MAC CE or a logical channel may be configured with a logical channel identifier (LCID). In an example, the LCID for a logical channel or MAC CE may be fixed / preconfigured. In an example, the LCID for a logical channel or MAC CE may be configured for the wireless device by the base station. The MAC subheader corresponding to the MAC CE or MAC SDU may include an LCID associated with the MAC CE or MAC SDU.

[0204] In an example, a base station may activate and / or deactivate and / or affect one or more processes at a wireless device (e.g., setting values ​​of one or more parameters of one or more processes or starting and / or stopping one or more timers of one or more processes) by using one or more MAC commands. The one or more MAC commands may include one or more MAC control elements. In an example, one or more processes may include activation and / or deactivation of PDCP packet duplication for one or more radio bearers. The base station may transmit a MAC CE including one or more fields, the values ​​of the fields indicating activation and / or deactivation of PDCP duplication for one or more radio bearers. In an example, one or more processes may include channel state information (CSI) transmission on one or more cells. The base station may transmit one or more MAC CEs indicating activation and / or deactivation of CSI transmission on one or more cells. In an example, one or more processes may include activation or deactivation of one or more secondary cells. In an example, the base station may transmit a MAC CE indicating activation or deactivation of one or more secondary cells. In an example, the base station may transmit one or more MAC CEs indicating starting and / or stopping one or more discontinuous reception (DRX) timers at the wireless device. In an example, the base station may transmit one or more MAC CEs indicating one or more timing advance values ​​for one or more timing advance groups (TAGs).

[0205] Figure 3 1 is a block diagram of a base station (base station 1, 120A and base station 2, 120B) and a wireless device 110. The wireless device may be referred to as a UE. The base station may be referred to as a NB, an eNB, a gNB, and / or an ng-eNB. In an example, the wireless device and / or the base station may act as a relay node. Base station 1, 120A may include at least one communication interface 320A (e.g., a wireless modem, an antenna, a wired modem, etc.), at least one processor 321A, and at least one set of program code instructions 323A, which are stored in a non-transitory memory 322A and can be executed by at least one processor 321A. Base station 2, 120B may include at least one communication interface 320B, at least one processor 321B, and at least one set of program code instructions 323B, which are stored in a non-transitory memory 322B and can be executed by at least one processor 321B.

[0206] A base station may include many sectors, for example: 1, 2, 3, 4 or 6 sectors. A base station may include many cells, for example, ranging from 1 to 50 cells or more. Cells may be classified as, for example, primary cells or secondary cells. During radio resource control (RRC) connection establishment / reconstruction / handover, a serving cell may provide NAS (non-access layer) mobility information (e.g., tracking area identifier (TAI)). During RRC connection reconstruction / handover, a serving cell may provide security input. The cell may be referred to as a primary cell (PCell). In the downlink, the carrier corresponding to the PCell may be a DL primary component carrier (PCC), and in the uplink, the carrier may be a UL PCC. Depending on the wireless device capabilities, a secondary cell (SCell) may be configured to form a group of serving cells together with the PCell. In the downlink, the carrier corresponding to the SCell may be a downlink secondary component carrier (DL SCC), and in the uplink, the carrier may be an uplink secondary component carrier (UL SCC). The SCell may or may not have an uplink carrier.

[0207] A physical cell ID and a cell index may be assigned to a cell including a downlink carrier and an optional uplink carrier. A carrier (downlink or uplink) may belong to a cell. A cell ID or a cell index may also identify a downlink carrier or an uplink carrier of a cell (depending on the context in which it is used). In the present disclosure, a cell ID may refer to a carrier ID equivalently, and a cell index may be referred to as a carrier index. In an embodiment, a physical cell ID or a cell index may be assigned to a cell. A synchronization signal transmitted on a downlink carrier may be used to determine the cell ID. An RRC message may be used to determine the cell index. For example, when the present disclosure relates to a first physical cell ID of a first downlink carrier, the present disclosure may mean that the first physical cell ID is used for a cell including a first downlink carrier. The same concept may be applied, for example, to carrier activation. When the present disclosure indicates that a first carrier is activated, the designation may also mean activating a cell including the first carrier.

[0208] The base station may transmit one or more messages (e.g., RRC messages) including multiple configuration parameters of one or more cells to the wireless device. The one or more cells may include at least one primary cell and at least one secondary cell. In an example, the RRC message may be broadcast or unicast to the wireless device. In an example, the configuration parameters may include common parameters and dedicated parameters.

[0209] The services and / or functions of the RRC sublayer may include at least one of the following: broadcasting system information related to AS and NAS; paging initiated by 5GC and / or NG-RAN; establishment, maintenance and / or release of an RRC connection between a wireless device and NG-RAN, which may include at least one of the addition, modification and release of carrier aggregation; or the addition, modification and / or release of dual connectivity in NR or between E-UTRA and NR. The services and / or functions of the RRC sublayer may further include at least one of the following security functions: key management; establishment, configuration, maintenance and / or release of signaling radio bearers (SRBs) and / or data radio bearers (DRBs); mobility functions, which may include at least one of handover (e.g., intra-NR mobility or inter-RAT mobility) and context transfer; or wireless device cell selection and reselection and control of cell selection and reselection. The services and / or functions of the RRC sublayer may further include at least one of: QoS management functions; wireless device measurement configuration / reporting; detection and / or recovery from radio link failures; or delivery of NAS messages from the wireless device to a core network entity (e.g., AMF, Mobility Management Entity (MME)) / from a core network entity to the wireless device.

[0210] The RRC sublayer may support the RRC_Idle state, RRC_Inactive state, and / or RRC_Connected state of the wireless device. In the RRC_Idle state, the wireless device may perform at least one of the following: public land mobile network (PLMN) selection; receiving broadcast system information; cell selection / reselection; monitoring / receiving paging of mobile terminated data initiated by 5GC; paging of mobile terminated data area managed by 5GC; or DRX for CN paging configured via NAS. In the RRC_Inactive state, the wireless device may perform at least one of the following: receiving broadcast system information; cell selection / reselection; monitoring / receiving RAN / CN paging initiated by NG-RAN / 5GC; RAN-based notification area (RNA) managed by NG-RAN; or DRX for RAN / CN paging configured by NG-RAN / NAS. In the RRC_Idle state of the wireless device, the base station (e.g., NG-RAN) may maintain a 5GC-NG-RAN connection (both C / U planes) for the wireless device; and / or store a UE AS context for the wireless device. In the RRC_Connected state of the wireless device, the base station (e.g., NG-RAN) may perform at least one of the following: establishing a 5GC-NG-RAN connection (both C / U planes) for the wireless device; storing a UE AS context for the wireless device; transmitting / receiving unicast data to / from the wireless device; or network-controlled mobility based on measurement results received from the wireless device. In the RRC_Connected state of the wireless device, the NG-RAN may know the cell to which the wireless device belongs.

[0211] System information (SI) can be divided into minimum SI and other SI. Minimum SI can be broadcast periodically. Minimum SI may include basic information required for initial access and information for obtaining any other SI that is broadcast periodically or provided on demand, i.e., scheduling information. Other SI may be broadcast, or provided in a dedicated manner, or triggered by the network, or upon request by a wireless device. Minimum SI may be transmitted via two different downlink channels using different messages (e.g., MasterInformationBlock and SystemInformationBlockType1). Another SI may be transmitted via SystemInformationBlockType2. For wireless devices in the RRC_Connected state, dedicated RRC signaling may be used for requesting and delivering other SI. For wireless devices in the RRC_Idle state and / or the RRC_Inactive state, the request may trigger a random access procedure.

[0212] The wireless device may report radio access capability information which may be static. The base station may request what capabilities the wireless device reports based on the band information. When the network allows, the wireless device may send a temporary capability restriction request to signal the limited availability of certain capabilities to the base station (e.g., due to hardware sharing, interference, or overheating). The base station may confirm or deny the request. Temporary capability restrictions may be transparent to the 5GC (e.g., static capabilities may be stored in the 5GC).

[0213] When CA is configured, the wireless device may have an RRC connection with the network. During the RRC connection establishment / reestablishment / handover procedure, one serving cell may provide NAS mobility information, and during RRC connection establishment / handover, one serving cell may provide security input. This cell may be referred to as a PCell. Depending on the capabilities of the wireless device, an SCell may be configured to form a group of serving cells together with the PCell. The configured serving cell group for the wireless device may include one PCell and one or more SCells.

[0214] Reconfiguration, addition and removal of SCells may be performed by RRC. RRC may also add, remove or reconfigure SCells for use with the target PCell during intra-NR handover. When adding a new SCell, dedicated RRC signaling may be used to send all required system information for the SCell, i.e., when in connected mode, the wireless device may not need to obtain broadcast system information directly from the SCell.

[0215] The purpose of the RRC connection reconfiguration procedure may be to modify the RRC connection, (e.g., establish, modify and / or release RBs, perform handover, set, modify and / or release measurements, add, modify and / or release SCells and cell groups). As part of the RRC connection reconfiguration procedure, NAS-specific information may be delivered from the network to the wireless device. The RRCConnectionReconfiguration message may be a command to modify the RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (e.g., RBs, MAC primary configuration, and physical channel configuration), including any associated dedicated NAS information and security configuration. If the received RRC connection reconfiguration message contains sCellToReleaseList, the wireless device may perform an SCell release. If the received RRC connection reconfiguration message contains sCellToAddModList, the wireless device may perform an SCell addition or modification.

[0216] The RRC connection establishment (or reestablishment, restoration) procedure may be to establish (or reestablish, restore) an RRC connection. The RRC connection establishment procedure may include SRB1 establishment. The RRC connection establishment procedure may be used to transfer initial NAS dedicated information / messages from the wireless device to the E-UTRAN. The RRCConnectionReestablishment message may be used to reestablish SRB1.

[0217] The measurement report procedure may be to transfer the measurement results from the wireless device to the NG-RAN. After successful security activation, the wireless device may initiate the measurement report procedure. The measurement results may be transmitted using a measurement report message.

[0218] The wireless device 110 may include at least one communication interface 310 (e.g., a wireless modem, an antenna, etc.), at least one processor 314, and at least one set of program code instructions 316 stored in a non-transitory memory 315 and executable by the at least one processor 314. The wireless device 110 may further include at least one of at least one speaker / microphone 311, at least one keypad 312, at least one display / touchpad 313, at least one power supply 317, at least one global positioning system (GPS) chipset 318, and other peripherals 319.

[0219] The processor 314 of the wireless device 110, the processor 321A of the base station 1 120A, and / or the processor 321B of the base station 2 120B may include at least one of a general purpose processor, a digital signal processor (DSP), a controller, 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, etc. The processor 314 of the wireless device 110, the processor 321A in the base station 1 120A, and / or the processor 321B in the base station 2 120B may perform at least one of signal decoding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable the wireless device 110, the base station 1 120A, and / or the base station 2 120B to operate in a wireless environment.

[0220] The processor 314 of the wireless device 110 may be connected to the speaker / microphone 311, the keypad 312, and / or the display / touchpad 313. The processor 314 may receive user input data from the speaker / microphone 311, the keypad 312, and / or the display / touchpad 313, and / or provide user output data to the speaker / microphone 311, the keypad 312, and / or the display / touchpad 313. The processor 314 in the wireless device 110 may receive power from the power supply 317, and / or may be configured to distribute power to other components in the wireless device 110. The power supply 317 may include at least one of one or more dry cell batteries, solar cells, fuel cells, etc. The processor 314 may be connected to the GPS chipset 318. The GPS chipset 318 may be configured to provide geographic location information of the wireless device 110.

[0221] The processor 314 of the wireless device 110 may further be connected to other peripherals 319, which may include one or more software and / or hardware modules that provide additional features and / or functionality. For example, the peripherals 319 may include at least one of an accelerometer, a satellite transceiver, a digital camera, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an Internet browser, etc.

[0222] The communication interface 320A of base station 1, 120A and / or the communication interface 320B of base station 2, 120B may be configured to communicate with the communication interface 310 of the wireless device 110 via the wireless link 330A and / or the wireless link 330B, respectively. In an example, the communication interface 320A of base station 1, 120A may communicate with the communication interface 320B of base station 2 and other RAN and core network nodes.

[0223] The wireless link 330A and / or the wireless link 330B may include at least one of a bidirectional link and / or a directional link. The communication interface 310 of the wireless device 110 may be configured to communicate with the communication interface 320A of the base station 1 120A and / or with the communication interface 320B of the base station 2 120B. The base station 1 120A and the wireless device 110 and / or the base station 2 120B and the wireless device 110 may be configured to send and receive transport blocks via the wireless link 330A and / or via the wireless link 330B, respectively. The wireless link 330A and / or the wireless link 330B may employ at least one frequency carrier. According to some different aspects of the embodiments, a transceiver may be employed. A transceiver may be a device that includes both a transmitter and a receiver. A transceiver may be used in devices such as wireless devices, base stations, relay nodes, etc. In Figure 4A , Figure 4B , Figure 4C , Figure 4D , Figure 6 , Fig. 7A , Figure 7B , Figure 8 Example embodiments of radio technologies implemented in the communication interfaces 310, 320A, 320B and wireless links 330A, 330B are shown in EMBODIMENTS and related text.

[0224] In an example, other nodes in the wireless network (eg, AMF, UPF, SMF, etc.) may include one or more communication interfaces, one or more processors, and a memory for storing instructions.

[0225] A node (e.g., a wireless device, a base station, an AMF, an SMF, an UPF, a server, a switch, an antenna, etc.) may include one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the node to perform certain processes and / or functions. Example embodiments may implement operations of single carrier and / or multi-carrier communications. Other example embodiments may include a non-transitory tangible computer-readable medium that includes instructions that can be executed by one or more processors to cause operations of single carrier and / or multi-carrier communications. Other example embodiments may include an article of manufacture that includes a non-transitory tangible computer-readable machine-accessible medium on which instructions are encoded for enabling programmable hardware to enable a node to implement operations of single carrier and / or multi-carrier communications. A node may include a processor, a memory, an interface, etc.

[0226] The interface may include at least one of a hardware interface, a firmware interface, a software interface, and / or a combination thereof. The hardware interface may include connectors, wires, electronic devices such as drivers, amplifiers, etc. The software interface may include code stored in a memory device to implement a protocol, a protocol layer, a communication device, a device driver, a combination thereof, etc. The firmware interface may include a combination of embedded hardware and code stored in and / or in communication with a memory device to implement a connection, an electronic device operation, a protocol, a protocol layer, a communication driver, a device driver, a hardware operation, a combination thereof, etc.

[0227] Figure 4A , Figure 4B , Figure 4C and Figure 4D is an example diagram of uplink and downlink signal transmission according to aspects of an embodiment of the present disclosure. Figure 4AAn example uplink transmitter for at least one physical channel is shown. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may include at least one of: scrambling; modulating scrambled bits to generate complex-valued symbols; mapping complex-valued modulation symbols to one or several transmission layers; transform pre-decoding to generate complex-valued symbols; pre-decoding of complex-valued symbols; mapping of pre-decoded complex-valued symbols to resource elements; generating a complex-valued time-domain single carrier frequency division multiple access (SC-FDMA) or CP-OFDM signal for an antenna port; and the like. In an example, when transform pre-decoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In an example, when transform pre-decoding is not enabled, the uplink transmission may be performed by Figure 4A Generate a CP-OFDM signal for uplink transmission. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0228] Example structures for modulation and up-conversion of the carrier frequency of a complex-valued SC-FDMA or CP-OFDM baseband signal and / or a complex-valued physical random access channel (PRACH) baseband signal for an antenna port are shown in Figure 4B In. Filtering can be applied before transmission.

[0229] Figure 4C An example structure for downlink transmission is shown in . A baseband signal representing a downlink physical channel may perform one or more functions. The one or more functions may include: scrambling the decoded bits in a codeword to be transmitted on a physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols to one or several transmission layers; pre-decoding of complex-valued modulation symbols on layers for transmission on antenna ports; mapping complex-valued modulation symbols for antenna ports to resource elements; generating complex-valued time-domain OFDM signals for antenna ports; and the like. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0230] In an example, a gNB may transmit a first symbol and a second symbol to a wireless device on an antenna port. The wireless device may infer a channel (e.g., fading gain, multipath delay, etc.) used to communicate the second symbol on the antenna port from the channel used to communicate the first symbol on the antenna port. In an example, the first antenna port and the second antenna port may be quasi-co-located if one or more large-scale properties of a channel on which the first symbol on the first antenna port is communicated may be inferred from a channel on which the second symbol on the second antenna port is communicated. The one or more large-scale properties may include at least one of: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial receive (Rx) parameters.

[0231] Example modulation and up-conversion of the carrier frequency of a complex-valued OFDM baseband signal for an antenna port Figure 4D Filtering can be applied before transmission.

[0232] Figure 5A is a diagram of an example uplink channel map and an example uplink physical signal. Figure 5B is a diagram of an example downlink channel mapping and downlink physical signals. In an example, the physical layer may provide one or more information transfer services to the MAC and / or one or more higher layers. For example, the physical layer may provide the one or more information transfer services to the MAC via one or more transport channels. The information transfer service may indicate the manner and characteristics of transferring data over the radio interface.

[0233] In an example embodiment, the radio network may include one or more downlink and / or uplink transmission channels. Figure 5A The figure in shows an example uplink transport channel including an uplink shared channel (UL-SCH) 501 and a random access channel (RACH) 502. Figure 5B The figure in shows an example downlink transport channel including a downlink shared channel (DL-SCH) 511, a paging channel (PCH) 512, and a broadcast channel (BCH) 513. The transport channels can be mapped to one or more corresponding physical channels. For example, UL-SCH 501 can be mapped to a physical uplink shared channel (PUSCH) 503. RACH 502 can be mapped to PRACH 505. DL-SCH 511 and PCH 512 can be mapped to a physical downlink shared channel (PDSCH) 514. BCH 513 can be mapped to a physical broadcast channel (PBCH) 516.

[0234] There may be one or more physical channels without corresponding transport channels. The one or more physical channels may be used for uplink control information (UCI) 509 and / or downlink control information (DCI) 517. For example, a physical uplink control channel (PUCCH) 504 may carry UCI 509 from a UE to a base station. For example, a physical downlink control channel (PDCCH) 515 may carry DCI 517 from a base station to a UE. When UCI 509 and PUSCH 503 transmissions may overlap at least partially in a time slot, NR may support UCI 509 multiplexing in PUSCH 503. UCI 509 may include at least one of CSI, acknowledgment (ACK) / negative acknowledgment (NACK), and / or a scheduling request. DCI 517 on PDCCH 515 may indicate at least one of: one or more downlink assignments and / or one or more uplink scheduling grants.

[0235] In the uplink, the UE may transmit one or more reference signals (RS) to the base station. For example, the one or more RSs may be at least one of a demodulation-RS (DM-RS) 506, a phase tracking-RS (PT-RS) 507, and / or a sounding RS (SRS) 508. In the downlink, the base station may transmit (e.g., unicast, multicast, and / or broadcast) one or more RSs to the UE. For example, the one or more RSs may be at least one of a primary synchronization signal (PSS) / secondary synchronization signal (SSS) 521, a CSI-RS 522, a DM-RS 523, and / or a PT-RS 524.

[0236] In an example, the UE may transmit one or more uplink DM-RS 506 to the base station for channel estimation, for example, for coherent demodulation of one or more uplink physical channels (e.g., PUSCH 503 and / or PUCCH 504). For example, the UE may transmit at least one uplink DM-RS 506 to the base station using PUSCH 503 and / or PUCCH 504, wherein the at least one uplink DM-RS 506 may span the same frequency range as the corresponding physical channel. In an example, the base station may configure the UE using one or more uplink DM-RS configurations. At least one DM-RS configuration may support a front-loaded DM-RS pattern. The front-loaded DM-RS may be mapped on one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may be configured to be transmitted at one or more symbols of PUSCH and / or PUCCH. The base station may semi-statistically configure the UE using the maximum number of front-loaded DM-RS symbols for PUSCH and / or PUCCH. For example, the UE may schedule single-symbol DM-RS and / or dual-symbol DM-RS based on the maximum number of front-loaded DM-RS symbols, wherein the base station may configure the UE with one or more additional uplink DM-RS for PUSCH and / or PUCCH. The new radio network may, for example, support a common DM-RS structure for DL ​​and UL at least for CP-OFDM, wherein the DM-RS position, DM-RS pattern and / or scrambling sequence may be the same or different.

[0237] In an example, whether the uplink PT-RS 507 is present may depend on the RRC configuration. For example, the presence of the uplink PT-RS may be UE-specifically configured. For example, the presence and / or pattern of the uplink PT-RS 507 in the scheduled resources may be UE-specifically configured by a combination of RRC signaling and / or an association with one or more parameters (e.g., modulation and coding scheme (MCS)) for other purposes that may be indicated by the DCI. When configured, the dynamic presence of the uplink PT-RS 507 may be associated with one or more DCI parameters including at least the MCS. The radio network may support multiple uplink PT-RS densities defined in the time / frequency domain. When present, the frequency domain density may be associated with at least one configuration of the scheduled bandwidth. The UE may use the same precoding for the DMRS port and the PT-RS port. The number of PT-RS ports may be less than the number of DM-RS ports in the scheduled resources. For example, the uplink PT-RS 507 may be limited to the scheduled time / frequency duration of the UE.

[0238] In an example, the UE may transmit SRS 508 to a base station for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. For example, the SRS 508 transmitted by the UE may allow the base station to estimate the uplink channel state at one or more different frequencies. The base station scheduler may use the uplink channel state to assign one or more resource blocks of high quality for uplink PUSCH transmission from the UE. The base station may semi-statistically configure the UE using one or more SRS resource sets. For the SRS resource set, the base station may configure the UE using one or more SRS resources. The applicability of the SRS resource set may be configured by a higher layer (e.g., RRC) parameter. For example, when the higher layer parameter indicates beam management, the SRS resources in each of the one or more SRS resource sets may be transmitted at a certain moment. The UE may transmit one or more SRS resources in different SRS resource sets at the same time. The new radio network may support non-periodic, periodic, and / or semi-persistent SRS transmissions. The UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may include higher layer signaling (e.g., RRC) and / or one or more DCI formats (e.g., at least one DCI format may be used for the UE to select at least one of one or more configured SRS resource sets. 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. In an example, when PUSCH 503 and SRS 508 are transmitted in the same time slot, the UE may be configured to transmit SRS 508 after transmission of PUSCH 503 and the corresponding uplink DM-RS 506.

[0239] In an instance, the base station may semi-statistically configure the UE using one or more SRS configuration parameters indicating at least one of: an SRS resource configuration identifier, a number of SRS ports, a time domain behavior of the SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS), a slot (mini-slot and / or subframe) level periodicity and / or offset of periodic and / or aperiodic SRS resources, a number of OFDM symbols in an SRS resource, a starting OFDM symbol of an SRS resource, an SRS bandwidth, a frequency hopping bandwidth, a cyclic shift, and / or an SRS sequence ID.

[0240] In an example, in the time domain, the SS / PBCH block may include one or more OFDM symbols within the SS / PBCH block (e.g., 4 OFDM symbols numbered in increasing order from 0 to 3). The SS / PBCH block may include a PSS / SSS 521 and a PBCH 516. In an example, in the frequency domain, the SS / PBCH block may include one or more consecutive subcarriers within the SS / PBCH block (e.g., 240 consecutive subcarriers, the subcarriers are numbered in increasing order from 0 to 239). For example, the PSS / SSS 521 may occupy 1 OFDM symbol and 127 subcarriers. For example, the PBCH 516 may span 3 OFDM symbols and 240 subcarriers. The UE may assume that one or more SS / PBCH blocks transmitted using the same block index may be quasi-co-located, for example, with respect to Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. The UE may not assume quasi-co-location of other SS / PBCH block transmissions. The periodicity of the SS / PBCH blocks may be configured by the radio network (e.g., via RRC signaling), and the subcarrier spacing may determine the one or more time locations at which the SS / PBCH blocks may be sent. In an example, the UE may assume a band-specific subcarrier spacing for the SS / PBCH blocks unless the radio network has configured the UE to assume a different subcarrier spacing.

[0241] In an example, a downlink CSI-RS 522 may be used for the UE to obtain channel state information. The radio network may support periodic, aperiodic and / or semi-persistent transmission of the downlink CSI-RS 522. For example, the base station may semi-statistically configure and / or reconfigure the UE using the periodic transmission of the downlink CSI-RS 522. The configured CSI-RS resources may be activated / deactivated. For semi-persistent transmission, the activation and / or deactivation of the CSI-RS resources may be dynamically triggered. In an example, the CSI-RS configuration may include one or more parameters indicating the number of at least antenna ports. For example, the base station may configure the UE using 32 ports. The base station may semi-statistically configure the UE using one or more CSI-RS resource sets. One or more CSI-RS resources may be allocated to one or more UEs from one or more CSI-RS resource sets. For example, the base station may semi-statistically configure one or more parameters indicating CSI RS resource mapping, such as the time domain position of one or more CSI-RS resources, the bandwidth of the CSI-RS resources, and / or periodicity. In an example, the UE may be configured to use the same OFDM symbol for the downlink CSI-RS 522 and the control resource set (core set) when the downlink CSI-RS 522 and the core set are quasi-co-located in space and the resource elements associated with the downlink CSI-RS 522 are outside the PRB configured for the core set. In an example, the UE may be configured to use the same OFDM symbol for the downlink CSI-RS 522 and the SSB / PBCH when the downlink CSI-RS 522 and the SSB / PBCH are quasi-co-located in space and the resource elements associated with the downlink CSI-RS 522 are outside the PRB configured for the SSB / PBCH.

[0242] In an example, the UE may transmit one or more downlink DM-RS 523 to a base station for channel estimation, e.g., for coherent demodulation of one or more downlink physical channels (e.g., PDSCH 514). For example, the radio network may support one or more variable and / or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration may support a front-load DM-RS pattern. The front-load DM-RS may be mapped on one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). The base station may semi-statistically configure the UE with a maximum number of front-load DM-RS symbols for PDSCH 514. For example, the DM-RS configuration may support one or more DM-RS ports. For example, for single-user-MIMO, the DM-RS configuration may support at least 8 orthogonal downlink DM-RS ports. For example, for multi-user-MIMO, the DM-RS configuration may support 12 orthogonal downlink DM-RS ports. The radio network may support a common DM-RS structure for DL ​​and UL, for example, at least for CP-OFDM, where the DM-RS positions, DM-RS patterns and / or scrambling sequences may be the same or different.

[0243] In an example, whether a downlink PT-RS 524 exists may depend on an RRC configuration. For example, the presence of a downlink PT-RS 524 may be UE-specifically configured. For example, the presence and / or pattern of a downlink PT-RS 524 in a scheduled resource may be UE-specifically configured by a combination of RRC signaling and / or association with one or more parameters (e.g., MCS) for other purposes that may be indicated by a DCI. When configured, the dynamic presence of a downlink PT-RS 524 may be associated with one or more DCI parameters including at least an MCS. A radio network may support multiple PT-RS densities defined in a time / frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may use the same precoding for a DMRS port and a PT-RS port. The number of PT-RS ports may be less than the number of DM-RS ports in the scheduled resource. For example, a downlink PT-RS 524 may be limited to a scheduled time / frequency duration of the UE.

[0244] Figure 6 is a diagram depicting example transmit times and receive times for carriers according to aspects of embodiments of the present disclosure. A multi-carrier OFDM communication system may include one or more carriers, for example, ranging from 1 to 32 carriers in the case of carrier aggregation, or ranging from 1 to 64 carriers in the case of dual connectivity. Different radio frame structures may be supported (e.g., for FDD and for TDD duplexing schemes). Figure 6Example frame timing is shown. Downlink and uplink transmissions may be organized into radio frames 601. In this example, the radio frame duration is 10 ms. In this example, the 10 ms radio frame 601 may be divided into ten equally sized subframes 602 having a duration of 1 ms. A subframe may include one or more time slots (e.g., time slots 603 and 605), depending on the subcarrier spacing and / or CP length. For example, subframes with 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, and 480 kHz subcarrier spacing may include one, two, four, eight, sixteen, and thirty-two time slots, respectively. Figure 6 In the embodiment of the present invention, a subframe may be divided into two equally sized time slots 603 with a duration of 0.5 ms. For example, at an interval of 10 ms, 10 subframes may be used for downlink transmission and 10 subframes may be used for uplink transmission. Uplink and downlink transmissions may be separated in the frequency domain. A time slot may contain a plurality of OFDM symbols 604. The number of OFDM symbols 604 in a time slot 605 may depend on the cyclic prefix length. For example, for the same subcarrier spacing of up to 480 kHz with normal CP, a time slot may be 14 OFDM symbols. For the same subcarrier spacing of 60 kHz with extended CP, a time slot may be 12 OFDM symbols. A time slot may contain a downlink, an uplink, or a downlink portion and an uplink portion, etc.

[0245] Fig. 7A700. The diagram depicts an example OFDM subcarrier set according to aspects of an embodiment of the present disclosure. In this example, a gNB may communicate with a wireless device using a carrier having an example channel bandwidth 700. The arrows in the diagram may depict subcarriers in a multi-carrier OFDM system. The OFDM system may use technologies such as OFDM technology, SC-FDMA technology, etc. In the example, arrow 701 shows a subcarrier on which an information symbol is transmitted. In the example, a subcarrier spacing 702 between two consecutive subcarriers in a carrier may be any one of 15KHz, 30KHz, 60KHz, 120KHz, 240KHz, etc. In the example, different subcarrier spacings may correspond to different transmission parameter sets. In the example, the transmission parameter set may include at least: a parameter set index; a value of the subcarrier spacing; a type of cyclic prefix (CP). In the example, the gNB may transmit to / receive from a UE on several subcarriers 703 in the carrier. In the example, due to the guard bands 704 and 705, the bandwidth occupied by the several subcarriers 703 (transmission bandwidth) may be less than the channel bandwidth 700 of the carrier. In an example, guard bands 704 and 705 may be used to reduce interference to and from one or more adjacent carriers. The number of subcarriers in a carrier (transmit bandwidth) may depend on the channel bandwidth and subcarrier spacing of the carrier. For example, for a carrier with a 20 MHz channel bandwidth and a 15 KHz subcarrier spacing, the transmit bandwidth may be the number of 1024 subcarriers.

[0246] In an example, when CA configuration is utilized, the gNB and wireless device may communicate with multiple CCs. In an example, if CA is supported, different component carriers may have different bandwidths and / or subcarrier spacings. In an example, the gNB may transmit a first type of service to the UE on a first component carrier. The gNB may transmit a second type of service to the UE on a second component carrier. Different types of services may have different service requirements (e.g., data rate, latency, reliability), which may be suitable for transmission via different component carriers with different subcarrier spacings and / or bandwidths. Figure 7B An example embodiment is shown. The first component carrier may include a first number of subcarriers 706 having a first subcarrier spacing 709. The second component carrier may include a second number of subcarriers 707 having a second subcarrier spacing 710. The third component carrier may include a third number of subcarriers 708 having a third subcarrier spacing 711. The carriers in a multi-carrier OFDM communication system may be contiguous carriers, non-contiguous carriers, or a combination of contiguous and non-contiguous carriers.

[0247] Figure 8801. In an example, a carrier may have a transmission bandwidth 801. In an example, a resource grid may be in a frequency domain 802 and a time domain 803 structure. In an example, the resource grid may include a first number of OFDM symbols and a second number of resource blocks in a subframe, starting from a common resource block for transmitting a parameter set and a carrier indicated by higher layer signaling (e.g., RRC signaling). In an example, in the resource grid, a resource unit identified by a subcarrier index and a symbol index may be a resource element 805. In an example, depending on a parameter set associated with a carrier, a subframe may include a first number of OFDM symbols 807. For example, when the subcarrier spacing of the parameter set of the carrier is 15KHz, the subframe may have 14 OFDM symbols for the carrier. When the subcarrier spacing of the parameter set is 30KHz, the subframe may have 28 OFDM symbols. When the subcarrier spacing of the parameter set is 60Khz, the subframe may have 56 OFDM symbols, etc. In an example, the second number of resource blocks included in the resource grid of the carrier may depend on the bandwidth and the numerology of the carrier.

[0248] like Figure 8 As shown, resource block 806 may include 12 subcarriers. In an example, multiple resource blocks may be grouped into resource block groups (RBGs) 804. In an example, the size of the RBG may depend on at least one of: an RRC message indicating an RBG size configuration; the size of the carrier bandwidth; or the size of a bandwidth portion of the carrier. In an example, the carrier may include multiple bandwidth portions. A first bandwidth portion of the carrier may have a different frequency location and / or bandwidth than a second bandwidth portion of the carrier.

[0249] In an example, the gNB may transmit downlink control information including downlink or uplink resource block assignments to the wireless device. The base station may transmit to or receive from the wireless device a data packet (e.g., a transport block) scheduled and transmitted via one or more resource blocks and one or more time slots according to the downlink control information and / or parameters in the RRC message. In an example, a starting symbol of a first time slot relative to the one or more time slots may be indicated to the wireless device. In an example, the gNB may transmit to or receive from the wireless device a data packet scheduled on one or more RBGs and one or more time slots.

[0250] In an example, the gNB may transmit downlink control information including a downlink assignment to the wireless device via one or more PDCCHs. The downlink assignment may include parameters indicating at least a modulation and coding format; a resource allocation; and / or HARQ information related to the DL-SCH. In an example, the resource allocation may include parameters for a resource block allocation; and / or a time slot allocation. In an example, the gNB may dynamically allocate resources to the wireless device via a cell-radio network temporary identifier (C-RNTI) on one or more PDCCHs. The wireless device may monitor the one or more PDCCHs to find possible allocations when its downlink reception is enabled. When the one or more PDCCHs are successfully detected, the wireless device may receive one or more downlink data packets on one or more PDSCHs scheduled by the one or more PDCCHs.

[0251] In an example, the gNB may allocate configured scheduled (CS) resources for downlink transmission to the wireless device. The gNB may transmit one or more RRC messages indicating the periodicity of the CS grant. The gNB may transmit the DCI via a PDCCH addressed to a configured scheduled-RNTI (CS-RNTI) that activates the CS resources. The DCI may include a parameter indicating that the downlink grant is a CS grant. The CS grant may be implicitly reused according to the periodicity defined by the one or more RRC messages until deactivated.

[0252] In an example, the gNB may transmit downlink control information including an uplink grant to the wireless device via one or more PDCCHs. The uplink grant may include parameters indicating at least a modulation and coding format; a resource allocation; and / or HARQ information related to the UL-SCH. In an example, the resource allocation may include parameters for a resource block allocation; and / or a time slot allocation. In an example, the gNB may dynamically allocate resources to the wireless device via a C-RNTI on one or more PDCCHs. The wireless device may monitor the one or more PDCCHs for possible resource allocations. Upon successful detection of the one or more PDCCHs, the wireless device may transmit one or more uplink data packets via one or more PUSCHs scheduled by the one or more PDCCHs.

[0253] In an example, the gNB may allocate CS resources for uplink data transmission to the wireless device. The gNB may transmit one or more RRC messages indicating the periodicity of the CS grant. The gNB may transmit a DCI via a PDCCH addressed to the CS-RNTI that activated the CS resources. The DCI may include a parameter indicating that the uplink grant is a CS grant. The CS grant may be implicitly reused according to the periodicity defined by the one or more RRC messages until deactivated.

[0254] In an example, a base station may transmit DCI / control signaling via a PDCCH. DCI may adopt a format in a variety of formats. DCI may include downlink and / or uplink scheduling information (e.g., resource allocation information, HARQ related parameters, MCS), a request for CSI (e.g., aperiodic CQI report), a request for SRS, an uplink power control command for one or more cells, one or more timing information (e.g., TB transmission / reception timing, HARQ feedback timing, etc.), etc. In an example, DCI may indicate an uplink grant including transmission parameters for one or more transport blocks. In an example, DCI may indicate a downlink assignment indicating parameters for receiving one or more transport blocks. In an example, a base station may use DCI to initiate contention-free random access at a wireless device. In an example, a base station may transmit a DCI including a slot format indicator (SFI) that notifies a slot format. In an example, a base station may transmit a DCI including a preemptive indication of a notification PRB and / or OFDM symbol, wherein the UE may assume that there is no transmission intended for the UE. In an example, a base station may transmit a DCI for group power control of a PUCCH or PUSCH or SRS. In an example, the DCI may correspond to an RNTI. In an example, a wireless device may obtain an RNTI (e.g., C-RNTI) in response to completing initial access. In an example, a base station may configure an RNTI (e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI) for wireless. In an example, a wireless device may calculate an RNTI (e.g., a wireless device may calculate an RA-RNTI based on resources used to transmit a preamble). In an example, the RNTI may have a preconfigured value (e.g., P-RNTI or SI-RNTI). In an example, a wireless device may monitor a group common search space, which may be used by a base station to transmit a DCI intended for a group of UEs. In an example, a group common DCI may correspond to an RNTI configured for a group of UEs. In an example, a wireless device may monitor a UE-specific search space. In an example, the UE-specific DCI may correspond to the RNTI configured for the wireless device.

[0255] The NR system may support single beam operation and / or multi-beam operation. In multi-beam operation, the base station may perform downlink beam sweeping to provide coverage for a common control channel and / or downlink SS block that may include at least PSS, SSS and / or PBCH. The wireless device may use one or more RSs to measure the quality of the beam to the link. One or more SS blocks, or one or more CSI-RS resources associated with a CSI-RS resource index (CRI), or one or more DM-RSs of the PBCH may be used as RSs for measuring the quality of the beam to the link. The quality of the beam to the link may be defined as a reference signal received power (RSRP) value, or a reference signal received quality (RSRQ) value, and / or a CSI value measured on the RS resource. The base station may indicate whether the RS resource used to measure the quality of the beam to the link is quasi-co-located (QCL) with the DM-RS of the control channel. When the channel characteristics of the transmission from the RS to the wireless device and the transmission from the control channel to the wireless device are similar or identical under the configured criteria, the RS resources and DM-RS of the control channel may be referred to as QCL. In multi-beam operation, a wireless device may perform uplink beam sweeping to access a cell.

[0256] In one example, the wireless device may be configured to monitor PDCCH on one or more beam pair links simultaneously depending on the capabilities of the wireless device. This may increase robustness against beam pair link blocking. The base station may transmit one or more messages to configure the wireless device to monitor PDCCH on one or more beam pair links in different PDCCH OFDM symbols. For example, the base station may transmit higher layer signaling (e.g., RRC signaling) or MAC CE, which includes parameters for Rx beam settings of the wireless device for monitoring PDCCH on one or more beam pair links. The base station may transmit an indication of the spatial QCL assumption between the DL RS antenna port (e.g., cell-specific CSI-RS, or wireless device-specific CSI-RS, or SS block, or PBCH with or without DM-RS of PBCH) and the DL RS antenna port for demodulating the DL control channel. The signaling for the beam indication for PDCCH may be MAC CE signaling, or RRC signaling, or DCI signaling, or a specification transparent and / or implicit method, and a combination of these signaling methods.

[0257] For reception of unicast DL data channels, the base station may indicate spatial QCL parameters between the DL RS antenna ports and the DM-RS antenna ports of the DL data channel. The base station may transmit a DCI (e.g., a downlink grant) including information indicating the RS antenna ports. The information may indicate the RS antenna ports that may be QCLed with the DM-RS antenna ports. Different sets of DM-RS antenna ports for DL ​​data channels may be indicated as different sets of QCLed with the RS antenna ports.

[0258] Fig.9A is an example of beam sweeping in a DL channel. In the RRC_INACTIVE state or the RRC_IDLE state, the wireless device may assume that the SS blocks form an SS burst 940 and an SS burst set 950. The SS burst set 950 may have a given periodicity. For example, in multi-beam operation, the base station 120 may transmit SS blocks in multiple beams, thereby forming an SS burst 940 together. One or more SS blocks may be transmitted on one beam. If multiple SS bursts 940 are transmitted with multiple beams, the SS bursts together may form an SS burst set 950.

[0259] The wireless device may further use CSI-RS in multi-beam operation to estimate the beam quality of the link between the wireless device and the base station. A beam may be associated with a CSI-RS. For example, the wireless device may report a beam index as indicated in the CRI for downlink beam selection and associated with the RSRP value of the beam based on the RSRP measurement report on the CSI-RS. The CSI-RS may be transmitted on a CSI-RS resource that includes at least one of one or more antenna ports, one or more time or frequency radio resources. The CSI-RS resources may be configured in a cell-specific manner by common RRC signaling or in a wireless device-specific manner by dedicated RRC signaling and / or L1 / L2 signaling. Multiple wireless devices covered by a cell may measure cell-specific CSI-RS resources. A dedicated subset of wireless devices covered by a cell may measure wireless device-specific CSI-RS resources.

[0260] The CSI-RS resources may be transmitted periodically or using aperiodic transmission or using multiple or semi-continuous transmission. Fig.9A In periodic transmission in the time domain, the base station 120 may periodically transmit the configured CSI-RS resources 940 using the configured periodicity. In aperiodic transmission, the configured CSI-RS resources may be transmitted in a dedicated time slot. In multiple or semi-continuous transmission, the configured CSI-RS resources may be transmitted within a configured period. The beam used for CSI-RS transmission may have a different beamwidth than the beam used for SS block transmission.

[0261] Fig. 9Bis an example of a beam management procedure in an example new radio network. The base station 120 and / or the wireless device 110 may perform a downlink L1 / L2 beam management procedure. One or more of the following downlink L1 / L2 beam management procedures may be performed in one or more wireless devices 110 and one or more base stations 120. In one example, the P-1 procedure 910 may be used to enable the wireless device 110 to measure one or more transmit (Tx) beams associated with the base station 120 to support the selection of a first set of Tx beams associated with the base station 120 and a first set of Rx beams associated with the wireless device 110. In order to perform beamforming at the base station 120, the base station 120 may sweep a set of different TX beams. In order to perform beamforming at the wireless device 110, the wireless device 110 may sweep a set of different Rx beams. In one example, the P-2 procedure 920 may be used to enable the wireless device 110 to measure one or more Tx beams associated with the base station 120 to possibly change the first set of Tx beams associated with the base station 120. The P-2 procedure 920 may be performed on a potentially smaller set of beams for beam optimization than in the P-1 procedure 910. The P-2 procedure 920 may be a special case of the P-1 procedure 910. In one example, the P-3 procedure 930 may be used to enable the wireless device 110 to measure at least one Tx beam associated with the base station 120 to change a first set of Rx beams associated with the wireless device 110.

[0262] The wireless device 110 may transmit one or more beam management reports to the base station 120. In the one or more beam management reports, the wireless device 110 may indicate some beam pair quality parameters, including at least: one or more beam identities of a subset of configured beams; RSRP; precoding matrix indicator (PMI) / channel quality indicator (CQI) / rank indicator (RI). Based on the one or more beam management reports, the base station 120 may transmit a signal to the wireless device 110 indicating that the one or more beam pair links are one or more service beams. The base station 120 may transmit PDCCH and PDSCH for the wireless device 110 using one or more service beams.

[0263] In an example embodiment, the new radio network may support bandwidth adaptation (BA). In an example, the receive and / or transmit bandwidth configured by a UE employing BA may not be large. For example, the receive and / or transmit bandwidth may not be as large as the bandwidth of the cell. The receive and / or transmit bandwidth may be adjustable. For example, the UE may change the receive and / or transmit bandwidth, for example, shrink during low activity periods to save power. For example, the UE may change the location of the receive and / or transmit bandwidth in the frequency domain, for example, to increase scheduling flexibility. For example, the UE may change the subcarrier spacing, for example, to allow different services.

[0264] In an example embodiment, a subset of the total cell bandwidth of a cell may be referred to as a bandwidth part (BWP). The base station may configure the UE with one or more BWPs to implement BA. For example, the base station may indicate to the UE which of the one or more (configured) BWPs is the active BWP.

[0265] Fig.10 This is an example diagram of 3 configured BWPs: BWP1 (1010 and 1050) with a width of 40MHz and a subcarrier spacing of 15kHz; BWP2 (1020 and 1040) with a width of 10MHz and a subcarrier spacing of 15kHz; BWP3 1030 with a width of 20MHz and a subcarrier spacing of 60kHz.

[0266] In an instance, a UE configured to operate in one or more BWPs of a cell may be configured by one or more higher layers (e.g., an RRC layer) of the cell with a set of one or more BWPs (e.g., up to four BWPs) for the UE (DL BWP set) to receive in a DL bandwidth via at least one parameter DL-BWP, and a set of one or more BWPs (e.g., up to four BWPs) for the UE (UL BWP set) to transmit in a UL bandwidth via at least one parameter UL-BWP for the cell.

[0267] To enable BA on PCell, the base station may configure the UE with one or more UL and DL BWP pairs. To enable BA on SCell (e.g., in case of CA), the base station may configure the UE with at least one or more DL BWPs (e.g., possibly none in UL).

[0268] In an example, the initial active DL BWP may be defined by at least one of the position and number of consecutive PRBs of a control resource set for at least one common search space, a subcarrier spacing, or a cyclic prefix. For operation on a PCell, one or more higher layer parameters may indicate at least one initial UL BWP for a random access procedure. If the UE is configured with a secondary carrier on a primary cell, the UE may be configured with an initial BWP for a random access procedure on the secondary carrier.

[0269] In an example, for unpaired spectrum operation, the UE may expect that the center frequency of the DL BWP may be the same as the center frequency of the UL BWP.

[0270] For example, for a DL BWP or ULBWP in a set of one or more DL BWPs or one or more UL BWPs, respectively, the base station can semi-statistically configure the UE for the cell using one or more parameters, wherein the one or more parameters indicate at least one of the following: subcarrier spacing; cyclic prefix; number of consecutive PRBs; index in a set of one or more DL BWPs and / or one or more UL BWPs; link between a DL BWP and a UL BWP from a set of configured DL BWPs and UL BWPs; DCI detection to PDSCH reception timing; PDSCH reception to HARQ-ACK transmission timing value; DCI detection to PUSCH transmission timing value; offset of the first PRB of the DL bandwidth or the UL bandwidth relative to the first PRB of the bandwidth, respectively.

[0271] In an example, for a DL BWP in a set of one or more DL BWPs on a PCell, the base station may configure the UE with one or more control resource sets for at least one type of common search space and / or one UE-specific search space. For example, the base station may not configure the UE without a common search space on a PCell or on a PSCell in an active DL BWP.

[0272] For a UL BWP in a set of one or more UL BWPs, the base station may configure the UE with one or more resource sets for one or more PUCCH transmissions.

[0273] In an example, if the DCI includes a BWP indicator field, the BWP indicator field value may indicate an active DL BWP from a configured DL BWP set for one or more DL receptions. If the DCI includes a BWP indicator field, the BWP indicator field value may indicate an active UL BWP from a configured UL BWP set for one or more UL transmissions.

[0274] In an example, for PCell, the base station may semi-statistically configure the UE with a default DL BWP among the configured DL BWPs. If a default DL BWP is not provided to the UE, the default BWP may be the initial active DL BWP.

[0275] In an example, the base station may configure the UE with a timer value for the PCell. For example, when the UE detects a DCI indicating an active DL BWP other than the default DL BWP for paired spectrum operation or when the UE detects a DCI indicating an active DL BWP or UL BWP other than the default DL BWP or UL BWP for unpaired spectrum operation, the UE may start a timer called a BWP inactivity timer. If the UE does not detect a DCI during an interval for paired spectrum operation or for unpaired spectrum operation, the UE may increment the timer by an interval of a first value (e.g., the first value may be 1 millisecond or 0.5 milliseconds). In an example, the timer may expire when the timer is equal to the timer value. When the timer expires, the UE may switch from the active DL BWP to the default DL BWP.

[0276] In an example, the base station may semi-statistically configure the UE with one or more BWPs. The UE may switch the active BWP from the first BWP to the second BWP (e.g., the second BWP may be the default BWP) in response to receiving a DCI indicating that the second BWP is the active BWP and / or in response to expiration of a BWP inactivity timer. For example, Fig.10 1050 . FIG. 106 is an example diagram of three configured BWPs: BWP1 (1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) may be default BWPs. BWP1 (1010) may be the initial active BWP. In an example, the UE may switch the active BWP from BWP1 1010 to BWP2 1020 in response to expiration of a BWP inactivity timer. For example, the UE may switch the active BWP from BWP2 1020 to BWP3 1030 in response to receiving a DCI indicating BWP3 1030 as the active BWP. Switching the active BWP from BWP3 1030 to BWP2 1040 and / or from BWP2 1040 to BWP1 1050 may be in response to receiving a DCI indicating an active BWP and / or in response to expiration of a BWP inactivity timer.

[0277] In an example, if the UE is configured with a default DL BWP and timer value among configured DL BWPs for a secondary cell, the UE procedure on the secondary cell may be the same as the UE procedure on the primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell.

[0278] In an example, if the base station configures the UE with a first active DL BWP and a first active UL BWP on a secondary cell or carrier, the UE may use the indicated DL BWP and the indicated UL BWP on the secondary cell as the respective first active DL BWP and first active UL BWP on the secondary cell or carrier.

[0279] Fig.11A and Fig. 11B Packet flows employing multiple connectivity (eg, dual connectivity, multiple connectivity, tight interworking, etc.) are shown. Fig.11A is an example diagram of a protocol structure for a wireless device 110 (eg, UE) with CA and / or multiple connectivity according to aspects of the embodiments. Fig. 11B 1 is an example diagram of a protocol structure of multiple base stations with CA and / or multiple connectivity according to aspects of an embodiment. The multiple base stations may include a master node MN 1130 (e.g., a master node, a master base station, a master gNB, a master eNB, etc.) and a secondary node SN 1150 (e.g., a secondary node, a secondary base station, a secondary gNB, a secondary eNB, etc.). The master node 1130 and the secondary node 1150 may work together to communicate with the wireless device 110.

[0280] When multiple connections are configured for the wireless device 110, the wireless device 110 that can support multiple receive / transmit functions in the RRC connection state can be configured to utilize radio resources provided by multiple schedulers of multiple base stations. Multiple base stations can be interconnected through non-ideal or ideal backhauls (e.g., Xn interface, X2 interface, etc.). The base stations involved in the multiple connectivity for a certain wireless device can perform at least one of two different roles: the base station can act as a primary base station or a secondary base station. In multiple connectivity, the wireless device can be connected to a primary base station and one or more secondary base stations. In an example, a primary base station (e.g., MN 1130) can provide a wireless device (e.g., wireless device 110) with a primary cell group (MCG) including a primary cell and / or one or more secondary cells. A secondary base station (e.g., SN 1150) can provide a secondary cell group (SCG) including a primary secondary cell (PSCell) and / or one or more secondary cells for a wireless device (e.g., wireless device 110).

[0281] In multiple connectivity, the radio protocol architecture used for the bearer may depend on how the bearer is set up. In an example, three different types of bearer setting options may be supported: MCG bearer, SCG bearer, and / or separate bearer. The wireless device may receive / transmit packets carried by the MCG via one or more cells of the MCG, and / or may receive / transmit packets carried by the SCG via one or more cells of the SCG. Multiple connectivity may also be described as having at least one bearer that is configured to use radio resources provided by a secondary base station. Multiple connectivity may or may not be configured / implemented in some example embodiments.

[0282] In an example, a wireless device (e.g., wireless device 110) may transmit and / or receive packets carried by the MCG via an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC 1114), and a MAC layer (e.g., MN MAC 1118); transmit and / or receive packets carried by the MCG via an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112), one of the primary or secondary RLC layers (e.g., MN RLC 1115, SN RLC 1116), and one of the primary or secondary MAC layers (e.g., MN MAC 1118, SN MAC 1119); and / or transmit and / or receive packets carried by the MCG via an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC 1117) and MAC layer (e.g., MNMAC 1119) to transmit and / or receive packets carried by the SCG.

[0283] In an example, a primary base station (e.g., MN 1130) and / or a secondary base station (e.g., SN 1150) may transmit / receive packets carried by the MCG via a primary or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), a primary or secondary node PDCP layer (e.g., NR PDCP 1121, NR PDCP 1142), a primary node RLC layer (e.g., MN RLC 1124, MN RLC 1125), and a primary node MAC layer (e.g., MN MAC 1128); and may transmit / receive packets carried by the MCG via a primary or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), a primary or secondary node PDCP layer (e.g., NR PDCP 1122, NR PDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147), and a secondary node MAC layer (e.g., SN MAC 1128). 1148) transmits / receives packets carried by SCG; transmits / receives packets carried separately via the primary or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), the primary or secondary node PDCP layer (e.g., NR PDCP 1123, NR PDCP 1141), the primary or secondary node RLC layer (e.g., MN RLC 1126, SN RLC 1144, SN RLC 1145, MN RLC 1127) and the primary or secondary node MAC layer (e.g., MN MAC 1128, SN MAC 1148).

[0284] In multiple connectivity, the wireless device may configure multiple MAC entities: one MAC entity for the primary base station (e.g., MN MAC 1118), and other MAC entities for the secondary base stations (e.g., SN MAC 1119). In multiple connectivity, the configured service cell set for the wireless device may include two subsets: an MCG including service cells of the primary base station, and an SCG including service cells of the secondary base stations. For SCG, one or more of the following configurations may apply: at least one cell of the SCG has a configured UL CC, and at least one cell of the SCG, referred to as a primary secondary cell (PSCell, PCell of the SCG, or sometimes referred to as PCell) is configured with PUCCH resources; when the SCG is configured, there may be at least one SCG bearer or one split bearer; after a physical layer problem or random access problem is detected on the PSCell, or after a number of NR RLC retransmissions associated with the SCG have been reached, or after an access problem is detected on the PSCell during SCG addition or SCG change: the RRC connection reestablishment procedure may not be triggered, UL transmission to the cells of the SCG may be stopped, the primary base station may be notified of the SCG failure type by the wireless device, and for a split bearer, DL data delivery on the primary base station may be maintained; NR may be configured for a split bearer RLC Acknowledged Mode (AM) carriage; PCell and / or PSCell cannot be deactivated; SCG change procedures can be used to change PSCell (e.g., using security key change and RACH procedures); and / or carriage type change between separate carriage and SCG carriage, or simultaneous configuration of SCG and separate carriage may or may not be supported.

[0285] Regarding the interaction between the primary base station and the secondary base station for multiple connectivity, one or more of the following may be applied: the primary base station and / or the secondary base station may maintain the RRM measurement configuration of the wireless device; the primary base station may (for example, based on the received measurement report, traffic conditions and / or carrier type) decide to request the secondary base station to provide additional resources (for example, service cells) for the wireless device; upon receiving the request from the primary base station, the secondary base station may create / modify a container, which may result in the configuration of additional service cells for the wireless device (or determine that the secondary base station has no available resources to do so); for UE capability coordination, the primary base station may provide (partial) AS configuration and UE capabilities to the secondary base station; the primary base station and the secondary base station may exchange information about UE configuration by adopting an RRC container (inter-node message) carried via an Xn message; the secondary base station may initiate reconfiguration of the secondary base station's existing service cell (for example, towards the PUCCH of the secondary base station); the secondary base station may decide which cell is the PSCell within the SCG; the primary base station may change or not change the content of the RRC configuration provided by the secondary base station; adding and / or re-adding a secondary base station to the SCG In the case of adding an SCell, the primary base station can provide the most recent (or latest) measurement results for the SCG cell; the primary base station and the secondary base station can receive information about SFN and / or each other's subframe offsets from OAM and / or via the Xn interface (for example, for the purpose of DRX alignment and / or identification of measurement gaps). In an example, when a new SCG SCell is added, dedicated RRC signaling can be used to send the required system information of the cell of the CA, except for the SFN obtained from the MIB of the PSCell of the SCG.

[0286] Fig.12 is an example diagram of a random access procedure. One or more events may trigger the random access procedure. For example, the one or more events may be at least one of: initial access from RRC_IDLE, RRC connection reestablishment procedure, handover, DL or UL data arrival during RRC_CONNECTED when the UL synchronization state is asynchronous, transition from RRC_Inactive, and / or a request for other system information. For example, a PDCCH command, a MAC entity, and / or a beam failure indication may initiate the random access procedure.

[0287] In an example embodiment, the random access procedure may be at least one of a contention-based random access procedure and a contention-free random access procedure. For example, the contention-based random access procedure may include one or more Msg 1 1220 transmissions, one or more Msg2 1230 transmissions, one or more Msg3 1240 transmissions, and contention resolution 1250. For example, the contention-free random access procedure may include one or more Msg 1 1220 transmissions and one or more Msg2 1230 transmissions.

[0288] In an example, the base station may transmit (e.g., unicast, multicast, or broadcast) a RACH configuration 1210 to the UE via one or more beams. The RACH configuration 1210 may include one or more parameters indicating at least one of: a set of available PRACH resources for transmission of a random access preamble, an initial preamble power (e.g., a random access preamble initial reception target power), an RSRP threshold for selecting an SS block and a corresponding PRACH resource, a power ramp factor (e.g., a random access preamble power ramp step size), a random access preamble index, a maximum number of preamble transmissions, preamble groups A and B, a threshold (e.g., a message size) for determining a random access preamble group, a set of one or more random access preambles and corresponding PRACH resources (if any) for system information request, a set of one or more random access preambles and corresponding PRACH resources (if any) for a beam failure recovery procedure, a time window for monitoring a RA response, a time window for monitoring a response regarding a beam failure recovery procedure, and / or a contention resolution timer.

[0289] In an example, Msg1 1220 may be one or more transmissions of a random access preamble. For a contention-based random access procedure, the UE may select an SS block with an RSRP above an RSRP threshold. If there is a random access preamble group B, the UE may select one or more random access preambles from group A or group B based on the potential Msg3 1240 size. If there is no random access preamble group B, the UE may select one or more random access preambles from group A. The UE may randomly (e.g., with equal probability or normal distribution) select a random access preamble index from one or more random access preambles associated with the selected group. If the base station semi-statistically configures the UE with an association between the random access preamble and the SS block, the UE may randomly select a random access preamble index from one or more random access preambles associated with the selected SS block and the selected group with equal probability.

[0290] For example, the UE may initiate a contention-free random access procedure based on a beam failure indication from a lower layer. For example, the base station may semi-statistically configure the UE with one or more contention-free PRACH resources for a beam failure recovery procedure associated with at least one of the SS blocks and / or CSI-RS. If at least one of the SS blocks having an RSRP higher than a first RSRP threshold among the associated SS blocks or at least one of the CSI-RS having an RSRP higher than a second RSRP threshold among the associated CSI-RS is available, the UE may select a random access preamble index corresponding to the selected SS block or CSI-RS from a set of one or more random access preambles for the beam failure recovery procedure.

[0291] For example, the UE may receive a random access preamble index from the base station via PDCCH or RRC for a contention-free random access procedure. If the base station does not configure the UE with at least one contention-free PRACH resource associated with an SS block or CSI-RS, the UE may select a random access preamble index. If the base station configures the UE with one or more contention-free PRACH resources associated with an SS block, and at least one SS block with an RSRP higher than a first RSRP threshold is available among the associated SS blocks, the UE may select the at least one SS block and select a random access preamble corresponding to the at least one SS block. If the base station configures the UE with one or more contention-free PRACH resources associated with a CSI-RS, and at least one CSI-RS with an RSRP higher than a second RSPR threshold is available among the associated CSI-RS, the UE may select the at least one CSI-RS and select a random access preamble corresponding to the at least one CSI-RS.

[0292] The UE may perform one or more Msg1 1220 transmissions by transmitting a selected random access preamble. For example, if the UE selects an SS block and is configured with an association between one or more PRACH opportunities and one or more SS blocks, the UE may determine a PRACH opportunity from one or more PRACH opportunities corresponding to the selected SS block. For example, if the UE selects a CSI-RS and is configured with an association between one or more PRACH opportunities and one or more CSI-RS, the UE may determine a PRACH opportunity from one or more PRACH opportunities corresponding to the selected CSI-RS. The UE may transmit the selected random access preamble to the base station via the selected PRACH opportunity. The UE may determine a transmit power for transmitting the selected random access preamble based at least on an initial preamble power and a power ramp factor. The UE may determine a RA-RNTI associated with a selected PRACH opportunity in which the selected random access preamble is transmitted. For example, the UE may not determine a RA-RNTI for a beam failure recovery procedure. The UE may determine the RA-RNTI based at least on an index of the first OFDM symbol and an index of a first slot of a selected PRACH opportunity and / or an uplink carrier index used for transmission of Msg11220.

[0293] In an example, the UE may receive a random access response Msg 2 1230 from the base station. The UE may start a time window (e.g., ra-ResponseWindow) to monitor the random access response. For a beam failure recovery procedure, the base station may configure the UE with a different time window (e.g., bfr-ResponseWindow) to monitor the response to the beam failure recovery procedure. For example, the UE may start the time window (e.g., ra-ResponseWindow or bfr-ResponseWindow) at the beginning of the first PDCCH opportunity after a fixed duration of one or more symbols from the end of the preamble transmission. If the UE transmits multiple preambles, the UE may start the time window at the beginning of the first PDCCH opportunity after a fixed duration of one or more symbols from the end of the first preamble transmission. The UE may monitor the PDCCH of the cell to view at least one random access response identified by the RA-RNTI or at least one response to the beam failure recovery procedure identified by the C-RNTI while the timer of the time window is running.

[0294] In an example, if at least one random access response includes a random access preamble identifier corresponding to a random access preamble transmitted by the UE, the UE may consider that the reception of the random access response is successful. If the reception of the random access response is successful, the UE may consider that the contention-free random access procedure is successfully completed. If the contention-free random access procedure is triggered for a beam failure recovery procedure, the UE may consider that the contention-free random access procedure is successfully completed if the PDCCH transmission is addressed to the C-RNTI. In an example, if at least one random access response includes a random access preamble identifier, the UE may consider that the random access procedure is successfully completed and may indicate receipt of an acknowledgment of a system information request for an upper layer. If the UE has signaled multiple preamble transmissions, the UE may stop transmitting the remaining preambles (if any) in response to successfully receiving the corresponding random access responses.

[0295] In an example, the UE may perform one or more Msg 3 1240 transmissions (e.g., for a contention-based random access procedure) in response to successful reception of a random access response. The UE may adjust the uplink transmission timing based on a timing advance command indicated by the random access response, and may transmit one or more transport blocks based on an uplink grant indicated by the random access response. The subcarrier spacing for PUSCH transmission of Msg3 1240 may be provided by at least one higher layer (e.g., RRC) parameter. The UE may transmit a random access preamble via PRACH and transmit Msg3 1240 via PUSCH on the same cell. The base station may indicate the UL BWP for PUSCH transmission of Msg3 1240 via a system information block. The UE may retransmit Msg 3 1240 using HARQ.

[0296] In an example, multiple UEs may perform Msg 1 1220 by transmitting the same preamble to the base station and receiving the same random access response including an identity (e.g., TC-RNTI) from the base station. Contention resolution 1250 may ensure that the UE does not mistakenly use the identity of another UE. For example, contention resolution 1250 may be based on a C-RNTI on a PDCCH or a UE contention resolution identity on a DL-SCH. For example, if a base station assigns a C-RNTI to a UE, the UE may perform contention resolution 1250 based on the reception of a PDCCH transmission addressed to the C-RNTI. In response to detecting the C-RNTI on the PDCCH, the UE may deem contention resolution 1250 successful and may deem the random access procedure to have been successfully completed. If the UE does not have a valid C-RNTI, contention resolution may be addressed by adopting the TC-RNTI. For example, if the MAC PDU is successfully decoded and the MAC PDU includes a UE contention resolution identity MAC CE that matches the CCCH SDU transmitted in Msg3 1250, the UE may consider contention resolution 1250 to be successful and the random access procedure to be successfully completed.

[0297] Fig.13 It is an example structure of a MAC entity according to aspects of an embodiment. In an example, a wireless device may be configured to operate in a multiple connectivity mode. A wireless device in RRC_CONNECTED with multiple RX / TX may be configured to utilize radio resources provided by multiple schedulers located in multiple base stations. Multiple base stations may be connected via non-ideal or ideal backhaul on an Xn interface. In an example, a base station among multiple base stations may act as a primary base station or a secondary base station. The wireless device may be connected to a primary base station and one or more secondary base stations. The wireless device may be configured with multiple MAC entities, for example, one MAC entity for a primary base station, and one or more other MAC entities for a secondary base station. In an example, a configured service cell set for a wireless device may include two subsets: an MCG, which includes service cells of a primary base station; and one or more SCGs, which include service cells of secondary base stations. Fig.13 An example structure of a MAC entity when MCG and SCG are configured for a wireless device is shown.

[0298] In an instance, at least one cell in an SCG may have a configured UL CC, where the cell of at least one cell may be referred to as a PSCell or a PCell of the SCG, or sometimes simply referred to as a PCell. The PSCell may be configured with PUCCH resources. In an instance, when an SCG is configured, there may be at least one SCG bearer or one separate bearer. In an instance, after a physical layer problem or a random access problem is detected on the PSCell, or after the number of RLC retransmissions associated with the SCG is reached, or after an access problem is detected on the PSCell during an SCG addition or SCG change: the RRC connection reestablishment procedure may not be triggered, UL transmission to the cells of the SCG may be stopped, the UE may notify the primary base station of the SCG failure type, and DL data delivery on the primary base station may be maintained.

[0299] In an example, the MAC sublayer can provide services such as data transfer and radio resource allocation to an upper layer (e.g., 1310 or 1320). The MAC sublayer can include multiple MAC entities (e.g., 1350 and 1360). The MAC sublayer can provide data transfer services on logical channels. In order to accommodate different types of data transfer services, multiple types of logical channels can be defined. Logical channels can support the transfer of specific types of information. The logical channel type can be defined by what type of information (e.g., control or data) is transferred. For example, BCCH, PCCH, CCCH and DCCH can be control channels, and DTCH can be a traffic channel. In an example, a first MAC entity (e.g., 1310) can provide services on PCCH, BCCH, CCCH, DCCH, DTCH and MAC control elements. In an example, a second MAC entity (e.g., 1320) can provide services on BCCH, DCCH, DTCH and MAC control elements.

[0300] The MAC sublayer may expect services from the physical layer (e.g., 1330 or 1340), such as data transfer services, signaling of HARQ feedback, scheduling requests, or signaling of measurement values ​​(e.g., CQI). In an instance, in dual connectivity, two MAC entities may be configured for the wireless device: one for the MCG and one for the SCG. The MAC entity of the wireless device may process multiple transport channels. In an instance, a first MAC entity may process a first transport channel, including a PCCH of the MCG, a first BCH of the MCG, one or more first DL-SCHs of the MCG, one or more first UL-SCHs of the MCG, and one or more first RACHs of the MCG. In an instance, a second MAC entity may process a second transport channel, including a second BCH of the SCG, one or more second DL-SCHs of the SCG, one or more second UL-SCHs of the SCG, and one or more second RACHs of the SCG.

[0301] In an example, if the MAC entity is configured with one or more SCells, there can be multiple DL-SCHs per MAC entity, and there can be multiple UL-SCHs as well as multiple RACHs. In an example, there can be one DL-SCH and UL-SCH on the SpCell. In an example, for a SCell, there can be one DL-SCH, zero or one UL-SCH, and zero or one RACH. The DL-SCH can support reception using different parameter sets and / or TTI durations within the MAC entity. The UL-SCH can also support transmission using different parameter sets and / or TTI durations within the MAC entity.

[0302] In an example, the MAC sublayer may support different functions and these functions may be controlled using control (e.g., 1355 or 1365) elements. Functions performed by the MAC entity may include mapping between logical channels and transport channels (e.g., in uplink or downlink), multiplexing (e.g., 1352 or 1362) MAC SDUs from one or different logical channels to a transport block (TB) to be delivered to a physical layer on a transport channel (e.g., in uplink), demultiplexing (e.g., 1352 or 1362) MAC SDUs from a transport block (TB) delivered from a physical layer on a transport channel to one or different logical channels (e.g., in downlink), scheduling information reporting (e.g., in uplink), error correction by HARQ in uplink or downlink (e.g., 1363), and logical channel prioritization in uplink (e.g., 1351 or 1361). The MAC entity may handle a random access procedure (e.g., 1354 or 1364).

[0303] Fig.14 is an example diagram of a RAN architecture including one or more base stations. In an example, a protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and PHY) can be supported at the node. A base station (e.g., gNB 120A or 120B) may include a base station central unit (CU) (e.g., gNB-CU 1420A or 1420B) and at least one base station distributed unit (DU) (e.g., gNB-DU 1430A, 1430B, 1430C, or 1430D) (if functional division is configured). The upper protocol layers of the base station may be located in the base station CU, and the lower layers of the base station may be located in the base station DU. The F1 interface (e.g., CU-DU interface) connecting the base station CU and the base station DU may be an ideal or non-ideal backhaul. F1-C may provide a control plane connection via the F1 interface, and F1-U may provide a user plane connection via the F1 interface. In an example, an Xn interface may be configured between the base station CUs.

[0304] In an example, the base station CU may include an RRC function, an SDAP layer, and a PDCP layer, and the base station DU may include an RLC layer, a MAC layer, and a PHY layer. In an example, various functional division options between the base station CU and the base station DU are possible by locating different combinations of upper protocol layers (RAN functions) in the base station CU and different combinations of lower protocol layers (RAN functions) in the base station DU. The functional division may support the flexibility of moving protocol layers between the base station CU and the base station DU according to service requirements and / or network environment.

[0305] In an instance, the functional partitioning options can be configured for each base station, each base station CU, each base station DU, each UE, each carrier, each slice layer, or at other granularity. In each base station CU partition, the base station CU can have a fixed partitioning option, and the base station DU can be configured to match the partitioning option of the base station CU. In each base station DU partition, the base station DU can be configured with different partitioning options, and the base station CU can provide different partitioning options for different base station DUs. In the per-UE partition, the base station (base station CU and at least one base station DU) can provide different partitioning options for different wireless devices. In each carrier partition, different partitioning options can be used for different carriers. In each slice layer splicing, different splitting options can be applied to different slice layers.

[0306] Fig.15is an example diagram showing RRC state transitions of a wireless device. In an example, the wireless device may be in at least one of an RRC connected state (e.g., RRC connected 1530, RRC_Connected), an RRC idle state (e.g., RRC idle 1510, RRC_Idle), and / or an RRC inactive state (e.g., RRC inactive 1520, RRC_Inactive). In an example, in the RRC connected state, the wireless device may have at least one RRC connection with at least one base station (e.g., gNB and / or eNB), which may have a UE context of the wireless device. The UE context (e.g., wireless device context) may include at least one of an access layer context, one or more radio link configuration parameters, a bearer (e.g., a data radio bearer (DRB), a signaling radio bearer (SRB), a logical channel, a QoS flow, a PDU session, etc.), configuration information, security information, PHY / MAC / RLC / PDCP / SDAP layer configuration information, and / or similar configuration information for the wireless device. In an example, in the RRC idle state, the wireless device may not have an RRC connection with the base station, and the UE context of the wireless device may not be stored in the base station. In an example, in the RRC inactive state, the wireless device may not have an RRC connection with the base station. The UE context of the wireless device may be stored in the base station, which may be referred to as an anchor base station (e.g., a last serving base station).

[0307] In an example, the wireless device may transition the UE RRC state between the RRC idle state and the RRC connected state in two ways (e.g., connection release 1540 or connection establishment 1550; or connection reestablishment) and / or between the RRC inactive state and the RRC connected state in two ways (e.g., connection deactivation 1570 or connection recovery 1580). In an example, the wireless device may transition its RRC state from the RRC inactive state to the RRC idle state (e.g., connection release 1560).

[0308] In an example, an anchor base station may be a base station that maintains a UE context (wireless device context) of a wireless device at least during a time period that the wireless device stays in a RAN notification area (RNA) of the anchor base station and / or the wireless device stays in an RRC inactive state. In an example, an anchor base station may be a base station to which a wireless device in an RRC inactive state was last connected in the latest RRC connected state, or a base station where the wireless device last performed an RNA update procedure. In an example, an RNA may include one or more cells operated by one or more base stations. In an example, a base station may belong to one or more RNAs. In an example, a cell may belong to one or more RNAs.

[0309] In an example, the wireless device may transition the UE RRC state from the RRC connected state to the RRC inactive state in the base station. The wireless device may receive RNA information from the base station. The RNA information may include at least one of an RNA identifier, one or more cell identifiers of one or more cells of the RNA, a base station identifier, an IP address of the base station, an AS context identifier of the wireless device, a recovery identifier, etc.

[0310] In an instance, an anchor base station may broadcast a message (e.g., a RAN paging message) to a base station of the RNA to reach a wireless device in an RRC inactive state, and / or a base station receiving a message from the anchor base station may broadcast and / or multicast another message (e.g., a paging message) over an air interface to wireless devices in its coverage area, a cell coverage area, and / or a beam coverage area associated with the RNA.

[0311] In an example, when a wireless device in an RRC inactive state moves to a new RNA, the wireless device may perform an RNA update (RNAU) procedure, which may include a random access procedure and / or a UE context retrieval procedure for the wireless device. The UE context retrieval may include: a base station receiving a random access preamble from the wireless device; and the base station extracting a UE context of the wireless device from an old anchor base station. The extraction may include: sending a retrieve UE context request message including a recovery identifier to the old anchor base station, and receiving a retrieve UE context response message including the UE context of the wireless device from the old anchor base station.

[0312] In an example embodiment, a wireless device in an RRC inactive state may select a cell to camp on based on measurement results of at least one or more cells, cells that the wireless device may monitor RNA paging messages, and / or core network paging messages from a base station. In an example, a wireless device in an RRC inactive state may select a cell to perform a random access procedure to restore an RRC connection and / or transmit one or more packets to a base station (e.g., to a network). In an example, if the selected cell belongs to an RNA different from the RNA of the wireless device in an RRC inactive state, the wireless device may initiate a random access procedure to perform an RNA update procedure. In an example, if the wireless device in an RRC inactive state has one or more packets in a buffer to transmit to the network, the wireless device may initiate a random access procedure to transmit one or more packets to a base station of a cell selected by the wireless device. The random access procedure may be performed using two messages (e.g., level 2 random access) and / or four messages (e.g., level 4 random access) between the wireless device and the base station.

[0313] In an example embodiment, a base station receiving one or more uplink packets from a wireless device in an RRC inactive state may extract a UE context for the wireless device based on at least one of an AS context identifier, an RNA identifier, a base station identifier, a recovery identifier, and / or a cell identifier received from the wireless device by transmitting a retrieve UE context request message for the wireless device to an anchor base station of the wireless device. In response to extracting the UE context, the base station may transmit a path switch request for the wireless device to a core network entity (e.g., AMF, MME, etc.). The core network entity may update a downlink tunnel endpoint identifier of one or more bearers established between a user plane core network entity (e.g., UPF, S-GW, etc.) and a RAN node (e.g., a base station) for the wireless device, for example, changing the downlink tunnel endpoint identifier from an address of the anchor base station to an address of the base station.

[0314] The gNB may communicate with the wireless device via a wireless network that employs one or more new radio technologies. The one or more radio technologies may include at least one of: multiple technologies associated with a physical layer; multiple technologies associated with a media access control layer; and / or multiple technologies associated with a radio resource control layer. Example embodiments that enhance the one or more radio technologies may improve the performance of the wireless network. Example embodiments may increase system throughput or data transmission rate. Example embodiments may reduce battery consumption of the wireless device. Example embodiments may improve latency of data transmission between the gNB and the wireless device. Example embodiments may improve network coverage of the wireless network. Example embodiments may increase transmission efficiency of the wireless network.

[0315] The gNB and / or wireless device may have multiple antennas to support the high data rate transmission in the NR system. When configured with multiple antennas, the wireless device may perform one or more beam management procedures, such as Fig. 9B shown.

[0316] The wireless device may perform downlink beam management based on one or more CSI-RS and / or one or more SSBs. During the beam management procedure, the wireless device may measure the channel quality of a beam pair link. The beam pair link may include a transmit beam from the gNB and a receive beam at the wireless device. When multiple beams associated with multiple CSI-RS or SSBs are configured, the wireless device may measure multiple beam pair links between the gNB and the wireless device.

[0317] In one example, the wireless device may transmit one or more beam management reports to the gNB. In the beam management report, the wireless device may indicate one or more beam pair quality parameters, including at least: one or more beam identities; RSRP; PMI / CQI / RI of at least a subset of the configured multiple beams.

[0318] In one example, the gNB and / or wireless device may perform downlink beam management procedures on one or more transmit and receive points (TRPs), such as Fig. 9B Based on the beam management report of the wireless device, the gNB may transmit a signal to the wireless device indicating that the new beam pair link is the serving beam. The gNB may transmit the PDCCH and PDSCH to the wireless device using the serving beam.

[0319] In one example, the wireless device or the gNB may trigger a beam failure recovery mechanism. The wireless device may trigger a beam failure recovery (BFR) procedure, for example, when at least one beam failure occurs. In one example, a beam failure may occur when the quality of the beam pair link of at least one PDCCH falls below a threshold. The threshold may be an RSRP value (e.g., -140 dBm, -110 dBm) or an SINR value (e.g., -3 dB, -1 dB), which may be configured in an RRC message.

[0320] Fig.16A An example of a first beam failure scenario is shown. In the example, the gNB may transmit a PDCCH from a transmit (Tx) beam from a TRP to a receive (Rx) beam of a wireless device. When the PDCCH on the beam-pair link (between the gNB's Tx beam and the wireless device's Rx beam) has a value lower than a threshold RSRP / SINR value due to the beam-pair link being blocked (e.g., by a moving car or building), the gNB and the wireless device may start a beam failure recovery procedure on the TRP.

[0321] Fig. 16B An example of a second beam failure scenario is shown. In the example, the gNB may transmit the PDCCH from the beam from the first TRP to the wireless device. When the PDCCH on the beam is blocked, the gNB and the wireless device may start the beam failure recovery procedure on the new beam on the second TRP.

[0322] In one example, the wireless device may measure the quality of a beam-to-link using one or more RSs. The one or more RSs may be one or more SSBs, or one or more CSI-RS resources. The CSI-RS resources may be identified by a CSI-RS resource index (CRI). In one example, the quality of a beam-to-link may be defined as an RSRP value, or a reference signal received quality (e.g., RSRQ) value, and / or a CSI (e.g., SINR) value measured on an RS resource. In one example, the gNB may indicate whether the RS resource used to measure the quality of a beam-to-link is QCL (quasi co-located) with the DM-RS of the PDCCH. When the channel characteristics of the transmission from the RS to the wireless device and the transmission from the PDCCH to the wireless device are similar or identical under the configured standard, the RS resource and the DM-RS of the PDCCH may be referred to as QCL. In one example, when the Doppler shift and / or Doppler shift of the channel of the transmission from the RS to the wireless device and the transmission from the PDCCH to the wireless device are the same, the RS resource and the DM-RS of the PDCCH may be referred to as QCL.

[0323] In an example, the wireless device may monitor PDCCH on M beam pair links simultaneously, where M≥1 and the value of M may depend at least on the capability of the wireless device. In an example, monitoring PDCCH may include detecting DCI via PDCCH transmitted on a common search space and / or a wireless device specific search space. In an example, monitoring multiple beam pair links may increase robustness to beam pair link blocking. In an example, the gNB may transmit one or more messages including parameters that instruct the wireless device to monitor PDCCH on different beam pair links in different OFDM symbols.

[0324] In one example, the gNB may transmit one or more RRC messages or MAC CEs including parameters indicating the Rx beam settings of the wireless device to monitor the PDCCH on multiple beam pair links. The gNB may transmit an indication of the spatial QCL between the DL RS antenna port and the DL RS antenna port for demodulating the DL control channel. In one example, the indication may be a parameter in a MAC CE or an RRC message or a DCI and / or a combination of these signalings.

[0325] In one example, to receive a data packet on the PDSCH, the gNB may indicate spatial QCL parameters between the DL RS antenna port and the DM-RS antenna port of the DL data channel. The gNB may transmit a DCI including parameters indicating the RS antenna port and DM-RS antenna port QCL.

[0326] In one example, when the gNB transmits a signal indicating a QCL parameter between the CSI-RS and the DM-RS for the PDCCH, the wireless device may measure the beam pair link quality based on the CSI-RS and the DM-RS for the PDCCH QCL. In one example, when multiple adjacent beam failures occur, the wireless device may start a BFR procedure.

[0327] In one example, when the BFR procedure is started, the wireless device transmits a BFR signal on an uplink physical channel to the gNB. The gNB may transmit a DCI via the PDCCH in the core set in response to receiving the BFR signal on the uplink physical channel. When the DCI is received via the PDCCH in the core set, the wireless device may consider the BFR procedure to be successfully completed.

[0328] In one example, the gNB may transmit one or more messages including configuration parameters for an uplink physical channel or a signal for transmitting a beam failure recovery request. The uplink physical channel or signal may be based on one of: contention-free PRACH (BFR-PRACH), which may be a resource orthogonal to resources of other PRACH transmissions; PUCCH (BFR-PUCCH); and / or contention-based PRACH resources (CF-PRACH). The combination of these candidate signals / channels may be configured by the gNB. In one example, when multiple resources for BFR signals are configured, the wireless device may autonomously select a first resource for transmitting the BFR signal. In one example, when BFR-PRACH resources, BFR-PUCCH resources, and CF-PRACH resources are configured, the wireless device may select a BFR-PRACH resource for transmitting the BFR signal. In one example, when BFR-PRACH resources, BFR-PUCCH resources, and CF-PRACH resources are configured, a message indicating the resources for transmitting the BFR signal may be transmitted to the wireless device.

[0329] In one example, the gNB may transmit a response to the wireless device after receiving the one or more BFR signals. The response may include a CRI associated with the candidate beam indicated by the wireless device in the one or more BFR signals.

[0330] In an example, the gNB may transmit DCI via PDCCH for at least one of: scheduling assignment / grant; slot format notification; preemption indication; and / or power control command. More specifically, the DCI may include at least one of: an identifier of a DCI format; a downlink scheduling assignment; an uplink scheduling grant; a slot format indicator; a preemption indication; power control for PUCCH / PUSCH; and / or power control for SRS.

[0331] In an example, the downlink scheduling assignment DCI may include parameters indicating at least one of: an identifier of a DCI format; a PDSCH resource indication; a transmission format; HARQ information; control information regarding a multiple antenna scheme; and / or a command for power control of a PUCCH.

[0332] In one example, the uplink scheduling grant DCI may include parameters indicating at least one of: an identifier of a DCI format; a PUSCH resource indication; a transmission format; HARQ related information; and / or a power control command for the PUSCH.

[0333] In one example, different types of control information may correspond to different DCI message sizes. For example, supporting multiple beams and / or spatial multiplexing in the spatial domain and non-contiguous allocation of RBs in the frequency domain may require a larger scheduling message than an uplink grant that takes into account frequency-contiguous allocations. DCI may be categorized into different DCI formats, where a format corresponds to a certain message size and / or usage.

[0334] In one example, the wireless device may monitor one or more PDCCHs for detecting one or more DCIs having one or more DCI formats in a common search space or a wireless device specific search space. In one example, the wireless device may monitor the PDCCH with a limited set of DCI formats to save power consumption. The more DCI formats to be detected, the more power is consumed at the wireless device.

[0335] In one example, the information in the DCI format for downlink scheduling may include at least one of the following: an identifier of the DCI format; a carrier indicator; an RB allocation; a time resource allocation; a bandwidth portion indicator; a number of HARQ processes; one or more MCSs; one or more NDIs; one or more RVs; MIMO-related information; a downlink assignment index (DAI); TPC for PUCCH; an SRS request; and padding (if necessary). In one example, the MIMO-related information may include at least one of the following: a PMI; precoding information; a transport block swap flag; a power offset between a PDSCH and a reference signal; a reference signal scrambling sequence; the number of layers and / or antenna ports used for transmission; and / or a transmit configuration indication (TCI).

[0336] In one instance, the information in the DCI format for uplink scheduling may include at least one of the following: an identifier of the DCI format; a carrier indicator; a bandwidth part indication; a resource allocation type; an RB allocation; a time resource allocation; an MCS; an NDI; a phase rotation of the uplink DMRS; precoding information; a CSI request; an SRS request; an uplink index / DAI; a TPC for the PUSCH; and / or padding (if necessary).

[0337] In an example, the gNB may perform CRC scrambling for the DCI before transmitting the DCI via the PDCCH. The gNB may perform CRC scrambling by adding a plurality of bits of at least one wireless device identifier (e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SP CSI C-RNTI, SRS-TPC-RNTI, INT-RNTI, SFI-RNTI) in a binary manner on the CRC bits of the DCI. When detecting the DCI, the wireless device may check the CRC bits of the DCI. The wireless device may receive the DCI when the CRC is scrambled by the same bit sequence as the at least one wireless device identifier.

[0338] In one example, to support wide bandwidth operation, the gNB may transmit one or more PDCCHs in different control resource sets (core sets). The gNB may transmit one or more RRC messages including configuration parameters for one or more core sets. A core set may include at least one of: a first OFDM symbol; a number of consecutive OFDM symbols; a group of resource blocks; CCE to REG mapping. In one example, the gNB may transmit PDCCHs in a sub-dedicated core set for a specific purpose (e.g., for beam failure recovery confirmation).

[0339] In an example, a wireless device can monitor the PDCCH for detecting DCI in one or more configured core sets to reduce power consumption.

[0340] In NR systems, when multiple beams are configured, the gNB and / or the wireless device may perform one or more beam management procedures. For example, if one or more beam pair links between the gNB and the wireless device fail, the wireless device may perform a BFR procedure.

[0341] Fig.17An example of a BFR procedure for a cell (e.g., a PCell or SCell) is shown. The wireless device may receive one or more RRC messages including BFR parameters 1701. The one or more RRC messages may include an RRC message (e.g., an RRC connection reconfiguration message, or an RRC connection reestablishment message, or an RRC connection setup message). The wireless device may detect at least one beam failure based on at least one of the BFR parameters 1702. If configured in response to detecting the at least one beam failure, the wireless device may start a first timer. The wireless device may select a selected beam in response to detecting the at least one beam failure 1703. The selected beam may be a beam with good channel quality (e.g., RSRP, SINR, or BLER) from a set of candidate beams. The candidate beams may be identified by a set of reference signals (e.g., SSB or CSI-RS). The wireless device may transmit at least one first BFR signal to the gNB in ​​response to selecting the selected beam 1704. The at least first BFR signal may be associated with the selected beam. The at least first BFR signal may be a preamble transmitted on a PRACH resource, or an SR signal transmitted on a PUCCH resource, or a beam indication transmitted on a PUCCH / PUSCH resource. The wireless device may transmit the at least first BFR signal using a transmit beam corresponding to a receive beam associated with a selected beam. The wireless device may initiate a response window in response to transmitting the at least first BFR signal. In one example, the response window may be a timer having a value configured by the gNB. When the response window is in operation, the wireless device may monitor the PDCCH in the first core set 1705. The first core set may be associated with a BFR procedure. In one example, the wireless device may monitor the PDCCH in the first core set under the condition that the at least first BFR signal is transmitted. The wireless device may receive the first DCI 1706 via the PDCCH in the first core set while the response window is in operation. The wireless device may consider the BFR procedure 1707 to be successfully completed when the first DCI is received via the PDCCH in the first core set before the expiration of the response window. If configured in response to the BFR procedure successfully completing, the wireless device may stop the first timer.The wireless device may stop the response window in response to the BFR procedure successfully completing.

[0342] In one example, when the response window expires and the wireless device does not receive DCI, the wireless device may increment the number of transmissions, where the number of transmissions is initialized to a first number (e.g., 0) before the BFR procedure is triggered. If the number of transmissions indicates a number less than the configured maximum number of transmissions 1708, the wireless device may repeat one or more actions including at least one of the following: BFR signal transmission; initiating a response window; monitoring the PDCCH; incrementing the number of transmissions if no response is received while the response window is in progress. If the number of transmissions indicates a number equal to or greater than the configured maximum number of transmissions, the wireless device may declare that the BFR procedure was not successfully completed 1709.

[0343] In an example, when the wireless device has a new transmission, the wireless device may trigger an SR for requesting UL-SCH resources. The gNB may transmit at least one message including parameters indicating zero, one or more SR configurations to the wireless device. The SR configuration may include a set of PUCCH resources for SR on one or more BWPs and / or one or more cells. On a BWP, at most one PUCCH resource for SR may be configured. Each SR configuration may correspond to one or more logical channels. Each logical channel may be mapped to zero or one SR configuration configured by the at least one message. The SR configuration of the logical channel (LCH) that triggered the buffer status report (BSR) may be considered as the corresponding SR configuration for the triggered SR.

[0344] In an example, for each SR configuration, the at least one message may further include one or more parameters indicating at least one of: an SR prohibit timer; a maximum number of SR transmissions; a parameter indicating a periodicity and an offset of SR transmissions; and / or a PUCCH resource. In an example, the SR prohibit timer may be a duration during which the wireless device may not be allowed to transmit an SR. In an example, the maximum number of SR transmissions may be a number of transmissions for which the wireless device may be allowed to transmit an SR at most.

[0345] In one example, a PUCCH resource may be identified by at least: a frequency position (e.g., a starting PRB); a PUCCH format and a time domain position (e.g., a starting symbol index) associated with an initial cyclic shift of a base sequence. In one example, the PUCCH format may be PUCCH format 0 or PUCCH format 1 or PUCCH format 2 or PUCCH format 3 or PUCCH format 4. PUCCH format 0 may have a length of 1 or 2 OFDM symbols, and is less than or equal to 2 bits. PUCCH format 1 may occupy a number of OFDM symbols between 4 and 14, and is less than or equal to 2 bits. PUCCH format 2 may occupy 1 or 2 OFDM symbols and is greater than 2 bits. PUCCH format 3 may occupy a number of OFDM symbols between 4 and 14, and is greater than 2 bits. PUCCH format 4 may occupy a number of OFDM symbols between 4 and 14, and is greater than 2 bits.

[0346] In an example, the PUCCH format for SR transmission may be PUCCH format 0 or PUCCH format 1. The wireless device may transmit PUCCH in the PUCCH resources for the corresponding SR configuration only when the wireless device transmits a positive SR. For a positive SR transmission using PUCCH format 0, the wireless device may transmit PUCCH by setting the cyclic shift to a first value (e.g., 0). For a positive SR transmission using PUCCH format 1, the wireless device may transmit PUCCH by setting the first bit before the BPSK modulated on the sequence to a first value (e.g., 0).

[0347] In one example, the SR may be multiplexed with HARQ-ACK or CSI on a PUCCH format. When a positive SR is multiplexed with HARQ-ACK, the wireless device may determine a cyclic shift of the basis sequence based on an initial cyclic shift and a first cyclic shift based on one or more values ​​of one or more HARQ-ACK bits. When a negative SR is multiplexed with HARQ-ACK, the wireless device may determine a cyclic shift of the basis sequence based on an initial cyclic shift and a second cyclic shift based on one or more values ​​of the one or more HARQ-ACK bits. The first cyclic shift is different from the second cyclic shift.

[0348] In an example, the wireless device may maintain a SR transmit counter (eg, SR_COUNTER) associated with the SR configuration.

[0349] In an example, if an SR of an SR configuration is triggered, and there are no other SRs pending corresponding to the same SR configuration, the wireless device may set the SR_COUNTER of the SR configuration to a first value (eg, 0).

[0350] In one example, when a SR is triggered, the wireless device may consider the SR pending until it is cancelled. In one example, when one or more UL grants accommodate all pending data available for transmission, all pending SRs may be cancelled.

[0351] In an example, the wireless device may determine one or more PUCCH resources on the active BWP as valid PUCCH resources at the time of the SR transmission opportunity.

[0352] In an example, when the wireless device transmits a positive SR, the wireless device may transmit the PUCCH in the PUCCH resources associated with the SR configuration. In an example, the wireless device may transmit the PUCCH using PUCCH format 0 or PUCCH format 1 according to the PUCCH configuration.

[0353] Fig.18 An example of an embodiment is shown. In the example, a wireless device may receive one or more RRC messages including parameters of one or more SR configurations. In an example, for each of the one or more SR configurations, the parameters may indicate at least one of: an SR prohibit timer; a maximum number of SR transmissions; a parameter indicating a periodicity and offset of SR transmissions; and / or a PUCCH resource identified by a PUCCH resource index. In an example, when an SR of an SR configuration is triggered (and therefore now pending) in response to triggering a BSR on an LCH corresponding to the SR configuration, if there are no other pending SRs corresponding to the SR configuration, the wireless device may set the SR_COUNTER to a first value (e.g., 0).

[0354] In one example, the wireless device may determine whether there is at least one valid PUCCH resource for a pending SR at the time of the SR transmission opportunity. If there is no valid PUCCH resource for the pending SR, the wireless device may initiate a random access procedure on the PCell. The wireless device may cancel the pending SR in response to the absence of a valid PUCCH resource for the pending SR.

[0355] In an example, if there is at least one valid PUCCH resource for a pending SR, the wireless device may determine an SR transmission opportunity on the at least one valid PUCCH resource based on the periodicity and offset of the SR transmission. In an example, if the SR prohibit timer is running, the wireless device may wait for another SR transmission opportunity. In an example, if the SR prohibit timer is not running and the SR_COUNTER is less than the maximum number of SR transmissions, the wireless device may increment the SR_COUNTER (e.g., by one), instructing the physical layer of the wireless device to signal the SR on at least one valid PUCCH resource for the SR. The physical layer of the wireless device may transmit the PUCCH on the at least one valid PUCCH resource for the SR. The wireless device may monitor the PDCCH for detecting the DCI for the uplink grant in response to transmitting the PUCCH.

[0356] In an example, if the wireless device receives one or more uplink grants that can accommodate all pending data available for transmission, the wireless device can cancel the pending SR, and / or stop the SR prohibit timer.

[0357] In one example, if the wireless device does not receive one or more uplink grants that can accommodate all pending data available for transmission, the wireless device may repeat one or more actions including: determining the at least one valid PUCCH resource; checking whether the SR prohibit timer is running; whether the SR_COUNTER is equal to or greater than the maximum number of SR transmissions; incrementing the SR_COUNTER, transmitting the SR and starting the SR prohibit timer; monitoring the PDCCH for uplink grants.

[0358] In one instance, if the SR_COUNTER indicates a number equal to or greater than the maximum number of SR transmissions, the wireless device may release the PUCCH for one or more serving cells, and / or release the SRS for the one or more serving cells, and / or clear one or more configured downlink assignments and uplink grants, and / or initiate a random access procedure on the PCell, and / or cancel a pending SR.

[0359] In one example, when at least one beam failure instance is identified in the presence of beam correspondence between the gNB and the wireless device, the gNB and the wireless device may perform a PRACH-based BFR procedure. In one example, when the wireless device transmits an uplink signal using a transmit beam corresponding to a receive beam for receiving a downlink signal from the gNB, beam correspondence may exist. When the wireless device identifies a receive beam, for example, by determining RF and / or digital beamforming parameters for receiving a downlink signal from the gNB, the wireless device may determine the transmit beam by using RF and / or digital beamforming parameters corresponding to the beamforming parameters of the receive beam. For example, the beamforming parameters of the transmit beam (e.g., beam weighting factors on antenna elements) may be the same as the beamforming parameters of the receive beam in the presence of beam correspondence. The presence of beam correspondence may simplify transceiver design in some cases because the wireless device may determine the transmit beam based on the receive beam. In one example, with beam correspondence, the gNB may not have to indicate the transmit beam for downlink or uplink transmission, thus reducing signaling overhead. In one example, with beam correspondence, the wireless device may avoid uplink beam sweeping to help the gNB find the appropriate uplink beam, thus reducing power consumption of the wireless device. In one example, the appropriate beam may be in the direction of the wireless device. Beam correspondence may exist in some scenarios, such as in TDD cases, or when transmit and receive share the same set of physical antenna elements, and / or when transmit and receive have the same or similar beamwidths.

[0360] In one example, when the physical antenna used for transmission is separated from the physical antenna used for reception and / or the beam widths used for transmission and reception are different, there may be no beam correspondence. In one example, the wireless device may not determine the transmit beam based on the receive beam. The receive beam may be used to receive downlink signals. In this case, the gNB may explicitly indicate the transmit beam for PUCCH / PUSCH transmission, for example, through an RRC message or MAC CE or DCI. In one example, when at least one beam failure instance is identified in the absence of beam correspondence, the gNB and the wireless device may not perform the PRACH-based BFR procedure.

[0361] When beam correspondence does not exist, in the existing PRACH-based BFR procedure, the wireless device may determine the transmit beam associated with the receive beam for receiving the candidate beam for the PRACH preamble transmission. However, the gNB may not detect the PRACH preamble because the gNB may not expect the presence of an uplink transmission by the wireless device on the transmit beam on which the PRACH preamble is transmitted due to the absence of beam correspondence between the transmit beam and the receive beam in the gNB and / or the wireless device. In this case, the PRACH-based BFR procedure may result in unsuccessful beam failure recovery. The unsuccessful beam failure recovery may further result in a radio link failure.

[0362] In one example, when beam correspondence does not exist, the wireless device may transmit a PUCCH signal indicating a triggering of a BFR procedure to the gNB upon identifying at least one beam failure instance. The transmit beam for the PUCCH signal may be indicated by an RRC message or a MACCE or a DCI. In one example, HARQ is not supported in the existing PUCCH transmission. By implementing the existing PUCCH-based transmission technology, it may be difficult for the wireless device to determine whether the gNB receives the PUCCH signal for the BFR procedure. In one example, the wireless device may adopt an SR-based BFR procedure, which may be based on Fig.18 By implementing the SR-based BFR procedure, the wireless device may receive a response from the gNB after transmitting the SR for the BFR procedure.

[0363] In many scenarios, the wireless device may perform multiple PUCCH-based procedures that overlap in time. In one example, the wireless device may trigger one or more first SRs based on a buffer status report procedure. For example, each of the one or more first SRs may be associated with a logical channel. When the wireless device initiates beam failure recovery (e.g., by implementing Fig.17In an instance of initiating beam failure recovery), the wireless device may trigger a second SR. The wireless device may receive DCI via PDCCH while executing multiple PUCCH-based procedures. By implementing existing SR techniques, the wireless device may cancel all pending SRs (e.g., the one or more first SRs and the second SR) together. For example, an uplink grant may be received in response to one of the SRs. For example, in conventional techniques, if a wireless device receives a DCI including one or more uplink grants (e.g., which may accommodate available uplink data transmission), all SR procedures may be canceled. In one instance, the DCI may not be a response to the transmission of the second SR (e.g., when the DCI is not transmitted in a dedicated control resource set for beam failure recovery). Implementing existing techniques (e.g., canceling all SR procedures) may reduce uplink transmission spectral efficiency, increase the waiting time for beam failure recovery, increase uplink transmission power, and / or increase uplink transmission interference. In one example, implementing existing SR techniques, if the DCI includes an uplink grant or the DCI is not received in a dedicated control resource set, the wireless device may cancel the second SR. This may result in a failure of the beam failure recovery procedure. By implementing existing SR techniques, if the DCI is a response to the second SR, the wireless device may cancel the one or more first SRs. The SR process may be terminated / canceled, resulting in inefficient uplink scheduling. There is a need to improve existing SR techniques for BFR procedures. Example embodiments provide enhanced mechanisms when multiple PUCCH-based procedures overlap in time. For example, when one or more beam failure recovery procedures (e.g., PUCCH-based / SR-based beam failure recovery) and SR procedures overlap in time, the enhanced embodiments improve uplink and / or downlink radio link performance. Example embodiments may include keeping the first SR for the buffer status reporting procedure pending, and / or canceling the second SR for beam failure recovery based on receiving a response to the second SR.

[0364] In existing SR techniques, PUCCH-based beam failure recovery can be implemented using a transmitted SR request. The wireless device can transmit an SR based on a buffer status reporting procedure (e.g., in one or two bits of information via PUCCH). For example, the SR can be transmitted based on an on-off-keying (OOK) technique. In OOK technology, the wireless device can transmit a signal (indicating "on") via a configured PUCCH resource to indicate that uplink data is available for transmission. In OOK technology, the wireless device can skip transmitting a signal (indicating "off") via a configured PUCCH resource to indicate that no uplink data is available. For example, a base station can determine whether to transmit an uplink grant request based on whether a signal exists on the configured PUCCH resource. Existing implementations of SR-based beam failure recovery techniques cannot provide the base station with sufficient information to recover from a beam failure. For example, a wireless device may not be able to provide the information required by the base station to resolve a beam failure. It is necessary to improve the existing SR procedure and signal format to implement a PUCH-based beam failure recovery procedure. Example embodiments provide an enhanced SR procedure and signal format to implement a PUCCH-based beam failure resilience procedure. Example embodiments may include transmitting candidate beam information (e.g., candidate beams and channel quality of candidate beams) via PUCCH resources for SR associated with beam failure resilience.

[0365] In conventional techniques, a wireless device cannot receive a response from a base station for one or more first SRs (for uplink grant requests) or second SRs (for BFR procedures), and may reach a maximum number of SR transmissions. In existing SR techniques, if the wireless device reaches the maximum number of SR transmissions, the wireless device may cancel all pending SRs (e.g., the one or more first SRs and the second SR). By implementing existing SR techniques, when an SR transmission counter reaches the maximum number of SR transmissions, the wireless device may cancel all pending SRs. In one example, the SR transmission counter may be used for the second SR of a beam failure recovery procedure, thereby canceling all SR procedures. The SR procedure may be terminated / cancelled, resulting in inefficient uplink scheduling. Implementing existing techniques (e.g., canceling all SR procedures) may reduce uplink transmission spectral efficiency, increase the waiting time for beam failure recovery, increase uplink transmission power, and / or increase uplink transmission interference. This may result in failure of the beam failure recovery procedure. The SR procedure may be terminated / cancelled, resulting in inefficient uplink scheduling. There is a need to improve existing SR techniques for BFR procedures. Example embodiments provide enhanced mechanisms when multiple PUCCH-based procedures overlap in time. For example, when one or more beam failure recovery procedures (e.g., PUCCH-based / SR-based beam failure recovery) and SR procedures overlap in time, the enhanced embodiments improve uplink and / or downlink radio link performance. Example embodiments may include canceling SRs for beam failure recovery and keeping other SRs for buffer status reporting procedures pending when the wireless device reaches a maximum number of SR transmissions for beam failure recovery.

[0366] In one example, a wireless device may be configured with an SR for beam failure recovery and one or more RACH resources for beam failure recovery. In conventional techniques, the wireless device may trigger an SR when the wireless device initiates beam failure recovery. Alternatively, the wireless device may initiate random access-based beam failure recovery on one of the one or more RACH resources. By implementing an existing beam failure recovery procedure, the wireless device may select an uplink resource, i.e., an SR or RACH resource, for performing beam failure recovery. For example, limiting one type of uplink resource (SR or RACH) used for beam failure recovery may reduce uplink transmission spectrum efficiency, increase the waiting time for beam failure recovery, increase uplink transmission power, and / or increase uplink transmission interference. Therefore, it is necessary to improve the existing BFR procedure when both SR resources and RACH resources are configured for use in the BFR procedure. An example embodiment may implement an enhanced beam failure recovery procedure, including selecting an SR resource or a RACH resource for beam failure recovery request message transmission or retransmission. For example, the selection for beam failure recovery request message transmission or retransmission may be based on the availability of SR resources and / or RACH resources for beam failure recovery. Example embodiments may include performing a beam failure recovery procedure by treating SR-based beam failure recovery and RACH-based beam failure recovery as a single process (e.g., maintaining retransmission counters for both RACH-based beam failure recovery and SR-based beam failure recovery).

[0367] Example embodiments may improve existing SR techniques for beam failure recovery. Example embodiments may include keeping a first SR pending for a buffer status reporting procedure, and / or canceling a second SR for beam failure recovery based on receiving a response to a second SR. Example embodiments may include transmitting candidate beam information via a PUCCH resource for an SR associated with beam failure recovery. Example embodiments may include monitoring a dedicated control resource set to see a response to the transmission of candidate beam information via a PUCCH resource. Example embodiments may include canceling an SR for beam failure recovery when a wireless device reaches a maximum number of SR transmissions for beam failure recovery and keeping other SRs pending for a buffer status reporting procedure. Example embodiments may include performing a beam failure recovery procedure by selecting an SR resource or a RACH resource for beam failure recovery request message transmission or retransmission. Example embodiments may include performing a beam failure recovery procedure by treating SR-based beam failure recovery and RACH-based beam failure recovery as a single process (e.g., maintaining retransmission counters for both RACH-based beam failure recovery and SR-based beam failure recovery). Example embodiments may increase uplink transmit spectral efficiency, reduce latency for beam failure recovery, reduce uplink transmit power, and / or reduce uplink transmit interference.

[0368] In the SR configuration, the SR configuration may correspond to at least one logical channel. The SR configuration may be associated with a plurality of parameters, the plurality of parameters including at least one of: an SR prohibit timer; a maximum number of SR transmissions; a parameter indicating a periodicity and an offset of SR transmissions; and / or a PUCCH resource.

[0369] In one example, when the SR procedure is used for the BFR procedure, the SR configuration for the BFR procedure may be different from the SR configuration associated with at least one logical channel. For example, the wireless device may transmit a pending SR up to 64 times for the SR configuration associated with the at least one logical channel. In one example, the wireless device may transmit an SR up to 200 times for the SR configuration for the BFR procedure, for example, assuming that there may be no beam correspondence. In one example, the response window for the BFR procedure may be shorter than the response window for the SR for requesting UL-SCH resources. For example, the response timer associated with the BFR procedure may be up to 80 time slots. The SR prohibit timer for the SR configuration for requesting UL-SCH resources may be up to 128ms. Therefore, the SR configuration for the BFR procedure may be configured separately or independently from the SR configuration for requesting UL-SCH resources. Example embodiments may provide a method for defining an SR configuration for a BFR procedure.

[0370] In one example, when the SR procedure is for a BFR procedure, the SR procedure triggered by the BFR procedure may be different from the SR procedure triggered by requesting UL-SCH resources (e.g., triggered by a BSR). In one example, when there are multiple pending SRs including a pending SR for a BFR procedure and one or more pending SRs for requesting one or more UL-SCH resources, it is necessary to improve the existing SR procedure for the multiple pending SRs (including an SR for a buffer status report, and an SR for beam failure recovery). If the existing SR procedure is implemented, the wireless device and the gNB may perform misalignment actions with respect to the multiple pending SRs. When multiple SRs (e.g., for a BFR procedure and for requesting UL-SCH resources) are pending, the example embodiment may improve the misalignment between the gNB and the wireless device.

[0371] Fig.19An example of an embodiment is shown. The gNB may transmit at least one message including a parameter indicating a first group of RSs (e.g., RS 0) and a second group of RSs (e.g., RS 1, RS 2, and RS 3). The at least one message may be an RRC message (e.g., an RRC connection reconfiguration message, or an RRC connection reestablishment message, or an RRC connection setup message). The first group of RSs may identify one or more beams with a beam QCL on which the gNB transmits a PDCCH / PDSCH. The second group of RSs may identify one or more candidate beams from which the wireless device may select a candidate beam having a quality better than a first threshold when the one or more beams associated with the first group of RSs fail. In an example, each of the first / second group of RSs may be an SSB or a CSI-RS. The first threshold may be a value configured based on BLER or SINR or L1-RSRP. In an example, when a measurement value on the first group of RSs is worse than a configured second threshold (e.g., RSRP or BLER), the one or more beams associated with the first group of RSs fail.

[0372] In one instance, the at least one message may include configuration parameters. In one instance, the configuration parameters may indicate a first request (e.g., a scheduling request, or a beam failure request, or a beam request) configuration, and at least one second SR (e.g., a scheduling request) configuration. The first request configuration may be associated with at least one of: a first PUCCH resource; a first timer having a first value; a first number of transmissions; a first periodicity for transmissions of the first request; and / or a first offset for transmissions of the first request. In one instance, the at least second SR configuration may be associated with at least one of: a second PUCCH resource; a second timer having a second value; a second number of transmissions; a second periodicity; and / or a second offset. In one instance, the at least second SR configuration may be associated with at least one logical channel.

[0373] In the present specification, the wireless device may transmit a request signal via PUCCH in response to initiating beam failure recovery. This process may be referred to as SR-based beam failure recovery. This process may be referred to equally by different names, such as PUCCH-based beam failure recovery, control channel-based beam failure recovery, SR-based beam failure recovery, etc. A request for beam failure recovery may be referred to as an SR request, a beam failure request, a PUCCH beam request, or a beam request, etc. For example, in the present specification, when a base station transmits at least one message (e.g., RRC) including configuration parameters of an SR for beam failure recovery to a wireless device, the configuration parameters may be referred to as PUCCH-based beam failure recovery configuration parameters, SR parameters for beam failure recovery, or PUCCH request parameters for beam failure recovery, etc.

[0374] In an example, the first value of the first timer may be different from the second value of the second timer. In an example, the first number of transmissions may be different from the second number of transmissions. In an example, the first periodicity may be different from the second periodicity. In an example, the first offset may be different from the second offset. In an example, the first PUCCH resource may be different from the second PUCCH resource.

[0375] In an example, the wireless device may maintain a first counter for the first request configuration. In an example, the wireless device may maintain a second counter for each of the at least second SR configurations.

[0376] In one example, the at least one message may include a parameter indicating a first control resource set and at least one second control resource set. The first control resource set may be associated with a first request configuration. In one example, when the wireless device transmits a first request on a first PUCCH resource for a BFR procedure, the wireless device may monitor a first PDCCH on the first control resource set. In one example, when the wireless device transmits a second SR of the at least second SR configuration, the wireless device may monitor a second PDCCH on the at least second control resource set. By way of example embodiments, the wireless device may determine whether the received DCI is for beam failure recovery or for an uplink grant request based on the control resource set on which the wireless device receives the DCI. Example embodiments may increase uplink transmission spectrum efficiency, shorten the waiting time for beam failure recovery, reduce uplink transmission power, and / or reduce uplink transmission interference.

[0377] Fig. 20 An example embodiment of a flow chart for a BFR procedure is shown. In one example, the BFR procedure may be triggered when the wireless device identifies at least one beam failure instance on a first set of RSs. The wireless device may select a candidate beam from a second set of RSs. The wireless device may trigger a first request associated with a first request configuration in response to selecting the candidate beam. In one example, when a logical channel triggers a BSR, the wireless device may trigger a second SR associated with the at least second SR configuration corresponding to the logical channel. In one example, the wireless device may perform a normal SR procedure for the second SR based on configuration parameters for the at least second SR configuration. In one example, the normal SR procedure may include requesting an uplink grant for an uplink transmission (e.g., a PUSCH).

[0378] In one example, the first request may remain pending until it is cancelled when the first request is triggered. In one example, the second SR may remain pending until it is cancelled when the second SR is triggered.

[0379] In one example, when the wireless device triggers the first request configured by the first request, the wireless device may determine the first PUCCH resource as a valid PUCCH resource at the time of the first request transmission. The valid PUCCH resource may be a PUCCH resource on the BWP that is active at the time of the request transmission. The timing of the first request transmission may depend on the first periodicity and / or the first offset configured by the at least one message and / or the time of triggering the first request.

[0380] Fig.21 The example of the embodiment is shown. The wireless device may receive one or more RRC messages, which include configuration parameters of a first SR associated with a buffer status report and a second SR associated with beam failure recovery on a cell. The one or more RRC messages may include an RRC connection reconfiguration message, an RRC connection reestablishment message, and / or an RRC connection setup message. In one example, the cell may be a PCell or an SCell. In one example, the wireless device may trigger a first request (e.g., such as Fig.21 The wireless device may trigger a second SR for a beam failure recovery procedure (e.g., as shown in FIG. Fig.21 The second SR shown).

[0381] When the wireless device triggers the second request, the wireless device may set the first counter to a first value (e.g., 0). When the wireless device determines a valid PUCCH resource at the time of the opportunity for the second request transmission, if the first counter indicates a value less than the first number of transmissions, the wireless device may trigger the second request on the valid PUCCH resource.

[0382] In one example, the wireless device may transmit a PUCCH signal on the valid PUCCH resource when the second request is triggered. For example, unlike the PUCCH transmission (OOK) of the existing SR technology, the PUCCH signal for beam failure recovery may include at least one parameter indicating one of the following: an RS index identifying a candidate beam, and / or a measurement quality (e.g., RSRP) of the candidate beam. Through an example embodiment, the wireless device may transmit candidate beam information via a PUCCH resource for an SR associated with beam failure recovery. Example embodiments may increase uplink transmission spectrum efficiency, shorten the waiting time for beam failure recovery, reduce uplink transmission power, and / or reduce uplink transmission interference.

[0383] In one example, the second request may be configured with multiple PUCCH resources in the at least one message. Each PUCCH resource may be associated with one of the second set of RSs. When the BFR procedure is triggered, the wireless device may select a candidate beam from the second set of RSs. The wireless device may determine a PUCCH resource from a plurality of PUCCH resources associated with the candidate beam. In one example, the wireless device may transmit a PUCCH signal on the PUCCH resource. In one example, the PUCCH signal may be a bit. In one example, the bit may be set to a first value (e.g., one) to indicate: triggering the BFR procedure; and / or identifying a candidate beam associated with the PUCCH resource.

[0384] In one example, the wireless device may increment a first counter (e.g., increment by one) in response to transmitting a second request, and / or start a first timer with a first value. In one example, the wireless device may monitor a PDCCH on a first set of control resources while the first timer is running. In one example, when the wireless device detects a DCI via the PDCCH while the first timer is running, the wireless device may successfully complete a BFR procedure. The wireless device may cancel a second request (pending) associated with a second request configuration. The wireless device may keep a first SR associated with at least a first SR configuration pending. The first SR may be triggered based on a buffer status report. The wireless device may stop the first timer and / or reset the first counter in response to successfully completing the BFR procedure. By way of example embodiments, the wireless device may keep a first SR pending for a buffer status report procedure and / or cancel a second SR for beam failure recovery based on receiving a response to a second SR. Example embodiments may increase uplink transmit spectral efficiency, shorten wait time for beam failure recovery, reduce uplink transmit power, and / or reduce uplink transmit interference.

[0385] In one example, the wireless device detects DCI via the PDCCH on a first control resource set different from a second control resource set for beam failure resilience. The DCI may include an uplink grant. In response to receiving the DCI, the wireless device may maintain a pending request for beam failure resilience and / or cancel an SR for a buffer status report.

[0386] In an example, when the DCI received on the PDCCH includes one or more uplink grants, the wireless device may cancel a first (pending) request associated with the first request configuration, and a second (pending) SR associated with the at least second SR configuration. In an example, the one or more uplink grants may accommodate pending data available for transmission. In an example, when the DCI received on the PDCCH includes one or more downlink assignments, the wireless device may cancel the first (pending) request associated with the first request configuration, and keep the second SR associated with the at least second SR configuration pending. The first SR may be triggered based on a buffer status report.

[0387] In one example, when the wireless device does not identify a valid PUCCH resource for the second request transmission according to the configuration parameters of the second request configuration (e.g., the first PUCCH resource has been released), the wireless device may initiate a random access procedure for beam failure recovery, or an initial random access procedure. The wireless device may keep the first request associated with the first request configuration pending. The first SR may be triggered based on the buffer status report. The wireless device may cancel the second SR associated with the at least second SR configuration.

[0388] In an example, when the first counter indicates a number equal to or greater than the first number of transmissions, the wireless device may not successfully complete the BFR procedure. In an example, a lower layer (e.g., a MAC layer or a PHY layer) of the wireless device may indicate a failure of the BFR procedure to a higher layer (e.g., an RRC layer) of the wireless device. In an example, the wireless device may cancel a second request associated with a second request configuration. In an example, the wireless device may cancel a first (pending) SR associated with the at least first SR configuration. The first SR may be triggered based on a buffer status report.

[0389] In one example, when the first counter indicates a number equal to or greater than the first transmission number, the wireless device may initiate a random access procedure for beam failure recovery. For example, the random access procedure for beam failure recovery may be initiated by Fig.17An example implementation of. In one example, in response to the first counter indicating a number equal to or greater than the first number of transmissions, the wireless device may cancel the second request associated with the second request configuration. In one example, unlike existing SR techniques, the wireless device may keep a first SR pending associated with the at least first SR configuration in response to the first counter indicating a number equal to or greater than the first number of transmissions. The first SR may be triggered based on a buffer status report. By way of an example embodiment, when the wireless device reaches a maximum number of SR transmissions for beam failure recovery, the wireless device may keep a first SR pending for a buffer status reporting procedure and / or cancel a second SR for beam failure recovery. Example embodiments may increase uplink transmission spectrum efficiency, shorten the waiting time for beam failure recovery, reduce uplink transmission power, and / or reduce uplink transmission interference.

[0390] In an example, when the first counter indicates a number equal to or greater than the first number of transmissions, the wireless device may notify a higher layer (e.g., RRC) of the wireless device to release the first PUCCH resource and all PUCCH resources for all serving cells including at least the second PUCCH resource. The wireless device may notify a higher layer of the wireless device to release the SRS for all serving cells. The wireless device may clear any configured downlink assignments and uplink grants.

[0391] In one example, the gNB may transmit at least one message including a parameter indicating a first set of RSs and a second set of RSs. The first set of RSs may identify one or more beams with beam QCL on which the gNB transmits PDCCH / PDSCH. The second set of RSs may identify one or more candidate beams from which the wireless device may select a candidate beam having a quality better than a threshold when the one or more beams associated with the first set of RSs fail.

[0392] In an example, the at least one message may include configuration parameters of a first requested configuration associated with the BFR procedure. The first requested configuration may be associated with at least one of: a first PUCCH resource; a first periodicity of requested transmission; and / or a first offset of requested transmission.

[0393] In an example, the at least one message may include configuration parameters of a PRACH configuration associated with the BFR procedure. The configuration parameters may include at least one of: an RS index from the second set of RSs; a preamble index; a time resource index; and a frequency resource index.

[0394] In one example, the at least one message may include at least one of: a first timer having a first value; a first transmission number; a first set of control resources. In one example, the wireless device may maintain a first counter associated with the BFR program. The first counter may be initialized to a first value (e.g., zero).

[0395] In one example, when the wireless device identifies at least one beam failure instance on the first set of RSs, the wireless device may select a candidate beam from the second set of RSs. In one example, the wireless device may determine whether to (re)transmit the first request or the PRACH based on the availability of the first PUCCH resource for the first request and the PRACH resource of the PRACH configuration. The PRACH resource may include a preamble index, a time resource index, and a frequency resource index.

[0396] Fig. 22 An example of an embodiment is shown. When selecting a candidate beam in response to triggering a BFR procedure, if a first PUCCH resource configured by a first request is available first in time compared to a PRACH resource associated with the candidate beam, the wireless device may determine to (re)transmit the first request configured by the first request. For example, if the PRACH resource associated with the candidate beam is available first in time compared to the first PUCCH resource configured by the first request, the wireless device may determine to (re)transmit the preamble via the PRACH resource. Through an example embodiment, the wireless device may perform a beam failure recovery procedure by selecting an SR resource or a RACH resource for beam failure recovery request message transmission or retransmission. Example embodiments may increase uplink transmission spectrum efficiency, shorten the waiting time for beam failure recovery, reduce uplink transmission power, and / or reduce uplink transmission interference.

[0397] In one example, when the wireless device transmits a first request or PRACH for a first request configuration, the wireless device may increment a first counter (e.g., by one) and start a first timer. In one example, while the first timer is running, the wireless device may monitor a PDCCH on a first set of control resources. When a DCI is detected on the PDCCH, the wireless device may successfully complete the BFR procedure.

[0398] In one example, when no DCI is detected while the first timer is running, the wireless device may determine the next transmission opportunity based on the availability of the PRACH resources of the first PUCCH resource and the PRACH configuration. For example, when the first PUCCH resource for the first request is first available in time compared to the PRACH resource, the wireless device may determine to transmit the PUCCH signal at the next transmission opportunity. For example, when the PRACH resource is first available in time compared to the first PUCCH resource for the first request, the wireless device may determine to transmit the PRACH at the next transmission opportunity. In one example, the wireless device may increment a first counter (e.g., increment by one) in response to transmitting a PUCCH signal or PRACH. By way of an example embodiment, the wireless device may perform a beam failure recovery procedure by treating SR-based beam failure recovery and RACH-based beam failure recovery as a single process (e.g., maintaining a single retransmission counter for both RACH-based beam failure recovery and SR-based beam failure recovery). Example embodiments may increase uplink transmit spectral efficiency, reduce latency for beam failure recovery, reduce uplink transmit power, and / or reduce uplink transmit interference.

[0399] In an example, when the first counter indicates a value equal to or greater than the first number of transmissions, the wireless device may not have successfully completed the BFR procedure. The wireless device may cancel the pending request of the first request configuration. The wireless device may indicate the failure of the BFR to a higher layer (e.g., an RRC layer). By implementing an embodiment, the wireless device may improve the latency of the BFR procedure. The wireless device may select an uplink resource (e.g., a PUCCH resource or a PRACH resource) that is available earlier in time to transmit a BFR signal.

[0400] In one example, a wireless device may receive at least one message including configuration parameters of a cell (e.g., a PCell or an Scell) from a base station. The configuration parameters may indicate at least one first request configuration, and at least one second SR configuration. In one example, the at least first request configuration may be identified by one or more first PUCCH resources. The at least second SR configuration may be identified by one or more second PUCCH resources. In one example, the at least first request configuration may be associated with a BFR procedure. In one example, the at least second SR configuration may be associated with a logical channel.

[0401] In one example, the wireless device may trigger a first request for the at least first SR configuration in response to initiating a BFR procedure on a cell (e.g., a PCell or SCell). In one example, the wireless device may trigger a second SR for the at least second SR configuration associated with a logical channel that triggers the BSR.

[0402] In one example, the wireless device may transmit the first request via one of the one or more first PUCCH resources in response to triggering the first request. In one example, the wireless device may transmit the second SR via one of the one or more second PUCCH resources in response to triggering the second SR.

[0403] In one example, the wireless device may cancel the first request in response to receiving the first downlink control information. In one example, the wireless device may keep the second SR pending in response to receiving the first downlink control information.

[0404] In an example, the at least one message may further include at least: one or more first RS resources; and / or one or more second RS resources. Each of the one or more second RS resources may be associated with each of the one or more first PUCCH resources.

[0405] In one example, the at least first request configuration may be associated with at least: a first timer; a first number of transmissions; a first request resource configuration index identified by a first periodicity and a first offset. In one example, the at least second SR configuration may be associated with at least: a second timer; a second number of transmissions; an associated second SR resource configuration index identified by a second periodicity and a second offset.

[0406] In one example, initiating the BFR procedure may include: measuring at least one downlink control channel based on the one or more first RS resources having signal strengths below a first threshold; and selecting a selected RS from among the one or more second RSs based on a second threshold.

[0407] In one example, the first PUCCH resource may be a PUCCH resource associated with the selected RS.

[0408] Embodiments may be configured to operate as desired. When certain criteria are met, such as in a wireless device, a base station, a radio environment, a network, a combination of the above, etc., the disclosed mechanisms may be performed. Example criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. When one or more criteria are met, various example embodiments may be applied. Thus, it is possible to implement example embodiments that selectively implement the disclosed protocol.

[0409] A base station may communicate with a mixture of wireless devices. A wireless device and / or a base station may support multiple technologies and / or multiple versions of the same technology. A wireless device may have certain specific capabilities, depending on the wireless device category and / or capabilities. A base station may include multiple sectors. When the present disclosure refers to a base station communicating with multiple wireless devices, the present disclosure may refer to a subset of the total wireless devices in the coverage area. For example, the present disclosure may refer to multiple wireless devices of a given LTE or 5G version with a given capability and in a given sector of a base station. The multiple wireless devices in the present disclosure may refer to a selected plurality of wireless devices, and / or a subset of the total wireless devices in the coverage area that perform according to the disclosed method, etc. There may be multiple base stations or multiple wireless devices in the coverage area that do not comply with the disclosed method because, for example, these wireless devices or base stations perform based on older versions of LTE or 5G technology.

[0410] According to various embodiments, a device (e.g., a wireless device, an off-grid wireless device, a base station, etc.) may include one or more processors and a memory. The memory may store instructions that, when executed by the one or more processors, cause the device to perform a series of actions. Examples of examples of actions are described in the drawings and the specification. Features from various embodiments may be combined to create additional embodiments.

[0411] Fig.23 is an example flow chart in accordance with aspects of an embodiment of the present disclosure. At 2310, a wireless device may transmit a first scheduling request (SR) based on a buffer status reporting procedure. At 2330, a second SR may be triggered in response to initiating beam failure recovery (2320). At 2340, the second SR may be transmitted via an uplink control channel resource configured for the second SR. At 2350, first downlink control information may be received via a downlink control channel as a response to the second SR. Based on receiving the first downlink control information: the first SR may be kept pending at 2360, and the second SR for beam failure recovery may be canceled at 2370. According to an example embodiment, beam failure recovery may be completed at 2380 in response to canceling the second SR (2370).

[0412] According to an example embodiment, the uplink control channel resources include frequency radio resources. According to an example embodiment, the uplink control channel resources include uplink control channel formats. According to an example embodiment, the uplink control channel resources include cyclic shifts of a base sequence. According to an example embodiment, the uplink control channel resources include time radio resources. According to an example embodiment, the first downlink control information may include a downlink assignment. According to an example embodiment, the first downlink control information may include an uplink grant. According to an example embodiment, one or more messages including a first configuration parameter of a first plurality of SRs including a first SR may be received. According to an example embodiment, one or more messages including a second configuration parameter of a second SR may be received. According to an example embodiment, the wireless device may trigger a second SR based on the second configuration parameter. According to an example embodiment, the second configuration parameter may indicate an uplink control channel resource for the second SR. According to an example embodiment, the wireless device may initiate beam failure recovery in response to detecting a number of beam failure instances. According to an example embodiment, the wireless device may detect the number of beam failure instances in response to a channel quality of one or more reference signal resources being below one or more first thresholds. According to an example embodiment, the wireless device may further select the first reference signal from the plurality of reference signals based on one or more second thresholds in response to initiating beam failure recovery. According to an example embodiment, the second SR may indicate a reference signal received power value of the first reference signal. According to an example embodiment, the second SR may indicate that the number of beam failure instances are detected. According to an example embodiment, the second SR may indicate the selection of the first reference signal. According to an example embodiment, the downlink control channel may be monitored to view the first downlink control information. According to an example embodiment, the wireless device may monitor the downlink control channel on at least one control resource set of the downlink control channel. According to an example embodiment, the wireless device may monitor the downlink control channel on at least one search space of the downlink control channel. According to an example embodiment, the downlink control channel may be associated with the second SR. According to an example embodiment, the downlink control channel associated with the second SR may include at least one control resource set of the downlink control channel determined based on the second SR. According to an example embodiment, the downlink control channel associated with the second SR may include at least one search space of the downlink control channel determined based on the second SR. According to an example embodiment, in response to keeping the first SR pending, the first SR may be transmitted via the second uplink control channel resource configured for the first SR. According to an example embodiment, further comprising receiving one or more second downlink control information including one or more uplink grants via a second downlink control channel. According to an example embodiment, the first SR may be cancelled in response to the one or more uplink grants accommodating data available for uplink transmission.

[0413] Fig.24is an example flow chart in accordance with aspects of embodiments of the present disclosure. At 2410, the wireless device may transmit a first scheduling request (SR) based on a buffer status reporting procedure. At 2430, a second SR may be triggered based on the initial beam failure recovery (2420). At 2440, the second SR may be transmitted. At 2450, first downlink control information may be received in response to the second SR. Based on receiving the first downlink control information: the first SR may be kept pending at 2460, and the second SR may be cancelled at 2470.

[0414] Fig.25 is an example flow chart according to aspects of an embodiment of the present disclosure. At 2510, a base station may transmit one or more radio resource control messages. The one or more radio resource control messages may include configuration parameters of a cell. The cell may be a PCell or an SCell. The configuration parameters may indicate a first scheduling request (SR) configuration associated with a logical channel. The configuration parameters may indicate a second SR configuration associated with beam failure recovery. At 2520, a first SR based on the first SR configuration may be received via a first uplink control resource based on a buffer status reporting procedure. At 2530, a second SR based on the second SR configuration may be received via a second uplink control resource for beam failure recovery. At 2540, a control resource set for transmission of downlink control information may be determined as a response to the second SR. At 2550, downlink control information including one or more uplink grants may be transmitted based on the first SR and the second SR and via a downlink control channel on the control resource set.

[0415] According to an example embodiment, the first SR configuration may include a first uplink control resource. According to an example embodiment, the second SR configuration may include a second uplink control resource. According to an example embodiment, the first uplink control resource may include a first frequency radio resource. According to an example embodiment, the first uplink control resource may include a first uplink control channel format. According to an example embodiment, the first uplink control resource may include a first cyclic shift of a base sequence. According to an example embodiment, the first uplink control resource may include a first time radio resource. According to an example embodiment, the second uplink control resource may include a second frequency radio resource. According to an example embodiment, the second uplink control resource may include a second uplink control channel format. According to an example embodiment, the second uplink control resource may include a second cyclic shift of a base sequence. According to an example embodiment, the second uplink control resource may include a second time radio resource. According to an example embodiment, the second SR may indicate a reference signal received power value of the first reference signal. According to an example embodiment, the second SR may indicate that a number of beam failure instances are detected. According to an example embodiment, the second SR may indicate selection of the first reference signal. According to an example embodiment, the wireless device may initiate beam failure recovery in response to detecting a number of beam failure instances. According to an example embodiment, the wireless device may detect the number of beam failure instances in response to a channel quality of one or more reference signal resources being below one or more first thresholds. According to an example embodiment, a first reference signal may be selected from a plurality of reference signals based on one or more second thresholds in response to initiating beam failure recovery. According to an example embodiment, the second SR may indicate a reference signal received power value of the first reference signal. According to an example embodiment, the second SR may indicate that the number of beam failure instances were detected. According to an example embodiment, the second SR may indicate that the first reference signal was selected.

[0416] Fig.26 is an example flow chart according to aspects of an embodiment of the present disclosure. At 2610, a first SR based on a first SR configuration associated with a logical channel may be received via a first uplink control resource based on a buffer status reporting procedure. At 2620, a second SR based on a second SR configuration associated with beam failure resilience may be received via a second uplink control resource for beam failure resilience. At 2630, a control resource set for transmission of downlink control information may be determined as a response to the second SR. At 2640, downlink control information including an uplink grant may be transmitted via the control resource set based on the first SR and the second SR.

[0417] Fig. 27is an example flow chart according to aspects of an embodiment of the present disclosure. At 2720, the wireless device may trigger a scheduling request in response to initiating beam failure recovery (2710). At 2730, a reference signal may be determined from multiple reference signals. At 2740, uplink control information for the scheduling request may be transmitted via uplink control channel resources. The uplink control information may include a reference signal identifier indicating the reference signal. The uplink control information may include a reference signal received power value of the reference signal. At 2750, downlink control information may be received via a downlink control channel on a control resource set associated with beam failure recovery as a response to the uplink control information. At 2760, the scheduling request may be canceled based on the downlink control information. At 2785, the beam failure recovery may be completed in response to canceling the scheduling request.

[0418] According to an example embodiment, the wireless device may determine the reference signal based on one or more thresholds. According to an example embodiment, one or more messages including a first configuration parameter of a scheduling request configuration associated with beam failure recovery may be received. The first configuration parameter may indicate an uplink control channel resource for the scheduling request. According to an example embodiment, the one or more configuration parameters of the uplink control channel resource may include a frequency radio resource. According to an example embodiment, the one or more configuration parameters of the uplink control channel resource may include an uplink control channel format. According to an example embodiment, the one or more configuration parameters of the uplink control channel resource may include a cyclic shift of a base sequence. According to an example embodiment, the one or more configuration parameters of the uplink control channel resource may include a time radio resource. According to an example embodiment, the one or more configuration parameters of a control resource set may include a control resource set index. According to an example embodiment, the one or more configuration parameters of a control resource set may include a number of symbols. According to an example embodiment, the one or more configuration parameters of a control resource set may include a group of resource blocks. According to an example embodiment, the one or more configuration parameters of a control resource set may include a control channel element to resource element group mapping indication. According to an example embodiment, the downlink control information may include a downlink radio resource assignment for downlink transport block transmission. According to an example embodiment, the downlink control information may include an uplink grant for uplink transport block transmission. According to an example embodiment, the wireless device may initiate beam failure recovery in response to detecting a number of beam failure instances. According to an example embodiment, the wireless device may detect the number of beam failure instances in response to a channel quality of one or more reference signal resources being below one or more thresholds. According to an example embodiment, one or more messages may be received including a first configuration parameter of a scheduling request configuration associated with beam failure recovery, wherein the first configuration parameter indicates a control resource set for beam failure recovery. According to an example embodiment, the one or more messages may include a second configuration parameter of at least one second scheduling request configuration associated with a logical channel, wherein the second configuration parameter indicates a second uplink control channel resource. According to an example embodiment, a second scheduling request may be transmitted based on the at least second scheduling request configuration for a buffer status reporting procedure of the logical channel. According to an example embodiment, the wireless device may transmit the second scheduling request via a second uplink control channel resource. According to an example embodiment, a downlink control channel may be monitored in a response window on the control resource set in response to transmitting uplink control information for beam failure recovery. According to an example embodiment, a duration of the response window may be configured in the radio resource control message. According to an example embodiment, the response window may include a timer having a timer value. According to an example embodiment, the response window may be initiated in response to transmitting the uplink control information. According to an example embodiment, the uplink control information may be retransmitted in response to not receiving a response within the response window.According to an example embodiment, a request counter may be incremented in response to not receiving a response within a response window. According to an example embodiment, a scheduling request may be cancelled in response to the request counter being greater than or equal to a first value. According to an example embodiment, beam failover may be completed in response to canceling the scheduling request.

[0419] Fig.28 is an example flow chart in accordance with aspects of an embodiment of the present disclosure. At 2820, the wireless device may trigger a scheduling request based on the initiation beam failure recovery (2810). At 2830, a reference signal may be determined from a plurality of reference signals. At 2840, uplink control information for the scheduling request may be transmitted via uplink control channel resources. At 2850, downlink control information based on the uplink control information may be received via a control resource set associated with the beam failure recovery. At 2860, the scheduling request may be canceled based on the downlink control information. At 2870, the beam failure recovery may be completed in response to the cancellation of the scheduling request.

[0420] Fig.29 is an example flow chart in accordance with aspects of an embodiment of the present disclosure. At 2910, a wireless device may transmit a first scheduling request (SR) based on a buffer status reporting procedure. At 2930, a second SR may be triggered in response to initiating beam failure recovery (2920). At 2940, the second SR may be transmitted via uplink resources configured for the second SR. At 2950, ​​first downlink control information may be received in response to the second SR. Based on the first downlink control information (2960) including an uplink grant: the first SR may be canceled at 2970, and the second SR for beam failure recovery may be canceled at 2980.

[0421] According to an example embodiment, the uplink resource may include a frequency radio resource. According to an example embodiment, the uplink resource may include an uplink control channel format. According to an example embodiment, the uplink resource may include a cyclic shift of a base sequence. According to an example embodiment, the uplink resource may include a time radio resource. According to an example embodiment, beam failure recovery may be completed in response to canceling the second SR. According to an example embodiment, one or more messages including a first configuration parameter of a first plurality of SRs including a first SR may be received. According to an example embodiment, one or more messages including a second configuration parameter of a second SR may be received. According to an example embodiment, the wireless device may trigger the second SR based on the second configuration parameter. According to an example embodiment, the second configuration parameter may indicate an uplink resource for an uplink control channel of the second SR. According to an example embodiment, the wireless device may initiate beam failure recovery in response to detecting a number of beam failure instances. According to an example embodiment, the wireless device may detect the number of beam failure instances in response to a channel quality of one or more reference signal resources being below one or more first thresholds. According to an example embodiment, a first reference signal may be selected from a plurality of reference signals based on one or more second thresholds in response to initiating beam failure recovery. According to an example embodiment, the second SR may indicate a reference signal received power value of the first reference signal. According to an example embodiment, the second SR may indicate that the number of beam failure instances are detected. According to an example embodiment, the second SR may indicate the selection of the first reference signal. According to an example embodiment, the downlink control channel may be monitored to view the first downlink control information. According to an example embodiment, the wireless device may monitor the downlink control channel on at least one control resource set of the downlink control channel. According to an example embodiment, the wireless device may monitor the downlink control channel on at least one search space of the downlink control channel. According to an example embodiment, the downlink control channel may be associated with the second SR. According to an example embodiment, the downlink control channel may be associated with the second SR including at least one control resource set of the downlink control channel determined based on the second SR. According to an example embodiment, the downlink control channel may be associated with the second SR including at least one search space of the downlink control channel determined based on the second SR.

[0422] Fig.30is an example flow chart in accordance with aspects of an embodiment of the present disclosure. At 3010, a wireless device may transmit a first scheduling request (SR) based on a buffer status reporting procedure. At 3030, a second SR may be triggered in response to the initiation of beam failure recovery (3020). At 3040, the second SR may be transmitted via uplink resources configured for the second SR. At 3050, first downlink control information may be received in response to the second SR. Based on the first downlink control information (3060) including a downlink assignment: the first SR may be kept pending at 3070, and the second SR for beam failure recovery may be canceled at 3080.

[0423] According to an example embodiment, the uplink resource may include a frequency radio resource. According to an example embodiment, the uplink resource may include an uplink control channel format. According to an example embodiment, the uplink resource may include a cyclic shift of a base sequence. According to an example embodiment, the uplink resource may include a time radio resource. According to an example embodiment, beam failure recovery may be completed in response to canceling the second SR. According to an example embodiment, one or more messages including a first configuration parameter of a first plurality of SRs including a first SR may be received. According to an example embodiment, one or more messages including a second configuration parameter of a second SR may be received. According to an example embodiment, the wireless device may trigger the second SR based on the second configuration parameter. According to an example embodiment, the second configuration parameter may indicate an uplink resource for an uplink control channel of the second SR. According to an example embodiment, the wireless device may initiate beam failure recovery in response to detecting a number of beam failure instances. According to an example embodiment, the wireless device may detect the number of beam failure instances in response to a channel quality of one or more reference signal resources being below one or more first thresholds. According to an example embodiment, further comprising selecting a first reference signal based on one or more second thresholds from a plurality of reference signals in response to initiating beam failure recovery. According to an example embodiment, the second SR may indicate a reference signal received power value of the first reference signal. According to an example embodiment, the second SR may indicate that the number of beam failure instances are detected. According to an example embodiment, the second SR may indicate the selection of the first reference signal. According to an example embodiment, the downlink control channel may be monitored to view the first downlink control information. According to an example embodiment, the wireless device may monitor the downlink control channel on at least one control resource set of the downlink control channel. According to an example embodiment, the wireless device may monitor the downlink control channel on at least one search space of the downlink control channel. According to an example embodiment, the downlink control channel may be associated with the second SR. According to an example embodiment, the downlink control channel associated with the second SR may include at least one control resource set for determining the downlink control channel based on the second SR. According to an example embodiment, the downlink control channel associated with the second SR may include at least one search space for determining the downlink control channel based on the second SR. According to an example embodiment, in response to keeping the first SR pending, the first SR may be transmitted via a second uplink control channel resource configured for the first SR. According to an example embodiment, one or more second downlink control information including one or more uplink grants may be received via the second downlink control channel. According to an example embodiment, the first SR may be cancelled in response to the one or more uplink grants accommodating data available for uplink transmission.

[0424] Fig.31is an example flow chart in accordance with aspects of an embodiment of the present disclosure. At 3110, the wireless device may transmit a first scheduling request (SR) based on a buffer status reporting procedure. At 3130, a second SR may be triggered based on initiating beam failure recovery (3120). At 3140, the second SR may be transmitted via uplink resources associated with the second SR. At 3150, a downlink control channel may be monitored for a response to the second SR. Based on the SR counter being equal to or greater than a first value (3160): the second SR may be canceled at 3170, the first SR may be kept pending at 3180, and a random access procedure for beam failure recovery may be initiated at 3190.

[0425] According to an example embodiment, the uplink resource comprises a frequency radio resource. According to an example embodiment, the uplink resource comprises an uplink control channel format. According to an example embodiment, the uplink resource comprises a cyclic shift of a base sequence. According to an example embodiment, the uplink resource comprises a time radio resource. According to an example embodiment, further comprising that beam failure recovery may be completed in response to canceling the second SR. According to an example embodiment, one or more messages may be received including a first configuration parameter of a first plurality of SRs including the first SR. According to an example embodiment, one or more messages may be received including a second configuration parameter of the second SR. According to an example embodiment, the wireless device may trigger the second SR based on the second configuration parameter. According to an example embodiment, the second configuration parameter may indicate an uplink resource of an uplink control channel for the second SR. According to an example embodiment, the wireless device may initiate beam failure recovery in response to detecting a number of beam failure instances. According to an example embodiment, the wireless device may detect the number of beam failure instances in response to a channel quality of one or more reference signal resources being lower than one or more first thresholds. According to an example embodiment, a first reference signal may be selected from a plurality of reference signals based on one or more second thresholds in response to initiating beam failure recovery. According to an example embodiment, the second SR may indicate a reference signal received power value of the first reference signal. According to an example embodiment, the second SR may indicate that the number of beam failure instances are detected. According to an example embodiment, the second SR may indicate the selection of the first reference signal. According to an example embodiment, the downlink control channel or the response may be monitored. According to an example embodiment, the wireless device may monitor the downlink control channel on at least one control resource set of the downlink control channel. According to an example embodiment, the wireless device may monitor the downlink control channel on at least one search space of the downlink control channel. According to an example embodiment, the downlink control channel may be associated with the second SR. According to an example embodiment, the downlink control channel may be associated with the second SR including at least one control resource set of the downlink control channel determined based on the second SR. According to an example embodiment, the downlink control channel may be associated with the second SR including at least one search space of the downlink control channel determined based on the second SR. According to an example embodiment, the wireless device may monitor the downlink control channel in a response window. According to an example embodiment, the size of the response window may be configured in the RRC message. According to an example embodiment, the SR counter may be incremented based on not receiving a response in the response window. According to an example embodiment, in response to keeping the first SR pending, the first SR may be transmitted via a second uplink control channel resource configured for the first SR. According to an example embodiment, one or more second downlink control information including one or more uplink grants may be received via a second downlink control channel. According to an example embodiment, the first SR may be canceled in response to the one or more uplink grants accommodating data available for uplink transmission.

[0426] Fig.32 is an example flow chart according to aspects of an embodiment of the present disclosure. At 3220, the wireless device may initiate beam failure recovery based on detecting a number of beam failure instances (3210). At 3230, a preamble may be transmitted via a random access channel resource and in response to initiating beam failure recovery. At 3245, a request transmission counter may be incremented in response to a first response (3240) in which a preamble is not received. At 3250, uplink control information for beam failure recovery may be transmitted via an uplink control channel resource. At 3270, a request transmission counter may be incremented in response to a second response (3260) in which uplink control information is not received. At 3290, beam failure recovery may be completed in response to the request transmission counter being equal to or greater than the first value (3280).

[0427] According to an example embodiment, the wireless device may detect the number of beam failure instances in response to a channel quality of one or more reference signal resources being below one or more first thresholds. According to an example embodiment, the uplink control channel resources may include frequency radio resources. According to an example embodiment, the uplink control channel resources may include uplink control channel formats. According to an example embodiment, the uplink control channel resources may include cyclic shifts of a base sequence. According to an example embodiment, the uplink control channel resources may include time radio resources. According to an example embodiment, a first reference signal based on one or more second thresholds may be selected from a plurality of reference signals in response to initiating beam failure recovery. According to an example embodiment, a random access channel resource may be associated with the first reference signal. According to an example embodiment, a response window may be initiated with a first time value based on transmitting a preamble. According to an example embodiment, the wireless device may increment a request transmission counter in response to not receiving a first response to the preamble when the response window expires. According to an example embodiment, the response window may be initiated with a time value in response to transmitting uplink control information. According to an example embodiment, the wireless device may increment a request transmission counter in response to not receiving a second response to the uplink control information when the response window expires.

[0428] Fig.33 is an example flow chart in accordance with aspects of an embodiment of the present disclosure. At 3320, a preamble may be transmitted via a random access channel resource based on the initiation of beam failure recovery (3310). At 3340, a request transmission counter may be incremented based on the first response (3330) not receiving the preamble. At 3350, uplink control information for beam failure recovery may be transmitted via an uplink control channel resource. At 3370, beam failure recovery may be completed based on the request transmission counter being equal to or greater than the first value (3360).

[0429] Fig.34is an example flow chart according to aspects of embodiments of the present disclosure. At 3420, a preamble for beam failure recovery may be transmitted via a first random access channel resource based on the first random access channel resource being earlier than a first uplink control channel resource (3410). At 3450, uplink control information for beam failure recovery may be transmitted via a second uplink control channel resource based on the following situations: no response to the preamble is received during a response window (3430), and the second uplink control channel resource is earlier than a second random access channel resource (3440).

[0430] According to an example embodiment, the first uplink control channel resource may include a frequency radio resource. According to an example embodiment, the first uplink control channel resource may include an uplink control channel format. According to an example embodiment, the first uplink control channel resource may include a cyclic shift of a base sequence. According to an example embodiment, the first uplink control channel resource may include a time radio resource. According to an example embodiment, a response window may be initiated in response to transmitting a preamble. According to an example embodiment, a response window may be initiated in response to transmitting uplink control information. According to an example embodiment, beam failure recovery may be initiated based on detecting a number of beam failure instances. According to an example embodiment, the wireless device may detect the number of beam failure instances in response to a channel quality of one or more reference signal resources being below one or more first thresholds. According to an example embodiment, a first reference signal based on one or more second thresholds may be selected from a plurality of reference signals in response to initiating beam failure recovery. According to an example embodiment, the first random access channel resource may be associated with the first reference signal. According to an example embodiment, the first uplink control channel resource may be associated with the first reference signal.

[0431] Fig.35 is an example flow chart according to aspects of an embodiment of the present disclosure. At 3520, the wireless device may initiate beam failure recovery based on detecting a number of beam failure instances (3510). At 3530, a determination may be made that the first random access channel resource is earlier than the first uplink control channel resource in response to initiating beam failure recovery (3520). At 3540, a preamble for beam failure recovery may be transmitted via the first random access channel resource. At 3550, a downlink control channel may be monitored to see a response to the preamble. At 3570, a determination may be made that the second uplink control channel resource is earlier than the second random access channel resource in response to not receiving a response (3560). At 3580, uplink control information for beam failure recovery may be transmitted via the second uplink control channel resource.

[0432] In this disclosure, "a" and similar phrases should be interpreted as "at least one" and "one or more". Similarly, any plural terms should be interpreted as "at least one" and "one or more". In this disclosure, the term "may" should be interpreted as "for example, may". In other words, the term "may" indicates that the phrase following the term "may" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments.

[0433] If A and B are sets, and each element of A is also an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, the possible subsets of B={cell 1, cell 2} are: {cell 1}, {cell 2}, and {cell 1, cell 2}. The phrase "based on" (or equivalently "at least based on") indicates that the phrase after the term "based on" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase after the phrase "in response to" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "depends on" (or equivalently "at least depends on") indicates that the phrase after the phrase "depends on" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "adopt / use" (or equivalently "at least adopt / use") indicates that the phrase after the phrase "adopt / use" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments.

[0434] The term configured may relate to the capabilities of a device, whether the device is in an operational state or a non-operational state. "Configured" may also mean a specific setting in a device that affects the operational characteristics of the device, whether the device is in an operational state or a non-operational state. In other words, hardware, software, firmware, registers, memory values, etc. may be "configured" within a device to provide specific characteristics to the device, whether the device is in an operational state or a non-operational state. For example, a term such as "a control message caused in a device" may mean that the control message has parameters that can be used to configure specific characteristics in the device or parameters that can be used to implement certain actions in the device, whether the device is in an operational state or a non-operational state.

[0435] In the present disclosure, various embodiments are disclosed. Limitations, features and / or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the present disclosure.

[0436] In the present disclosure, a parameter (or equivalently referred to as a field or information element: IE) may include one or more information objects, and an information object may include one or more other objects. For example, if parameter (IE) N includes parameter (IE) M, and parameter (IE) M includes parameter (IE) K, and parameter (IE) K includes parameter (information element) J. Then, for example, N includes K, and N includes J. In an example embodiment, when one or more messages include multiple parameters, it means that a parameter of the multiple parameters is in at least one of the one or more messages, but not necessarily in each of the one or more messages.

[0437] In addition, many of the features set forth above are described as optional through the use of "may" or the use of parentheses. For the sake of brevity and readability, the present disclosure does not explicitly recite every permutation that can be obtained by selecting from the set of optional features. However, the present disclosure should be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features can be embodied in seven different ways, namely, having only one of the three possible features, having any two of the three possible features, or having all three of the three possible features.

[0438] Many elements described in the disclosed embodiments can be implemented as modules.Modules are defined here as elements that perform defined functions and have defined interfaces to other elements.Modules described in the present disclosure can be implemented with hardware, software, firmware, wetware (i.e., hardware with biological elements) in combination with hardware, or a combination thereof, all of which can be equivalent in behavior.For example, a module can be implemented as a software routine written in a computer language, which is configured to be executed by a hardware machine (e.g., C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (e.g., Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). In addition, it is possible to implement a module using physical hardware that is incorporated with discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include: computers, microcontrollers, microprocessors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, C++, etc. FPGAs, ASICs, and CPLDs are often programmed using a hardware description language (HDL), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configures the connections between the internal hardware blocks with fewer functions on the programmable device. The above mentioned techniques are often used in combination to achieve the results of the functional blocks.

[0439] The disclosure of this patent document incorporates material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, for the limited purpose of requiring by law, but otherwise reserves all copyright rights whatsoever.

[0440] Although various embodiments have been described above, it should be understood that they are presented by way of example and not limitation. It will be apparent to those skilled in the relevant art that various changes in form and detail may be made therein without departing from the scope of the present invention. Indeed, after reading the above description, it will be apparent to those skilled in the relevant art how to implement alternative embodiments. Therefore, the present embodiments should not be limited by any of the above exemplary embodiments.

[0441] In addition, it should be understood that any diagrams highlighting functionality and advantages are provided for example purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in a manner other than that shown. For example, the actions listed in any flow chart may be reordered or only optionally used in certain embodiments.

[0442] In addition, the purpose of the Abstract of the Disclosure is to generally enable the U.S. Patent and Trademark Office and the public, especially scientists, engineers, and practitioners in the field who are not familiar with patent or legal terms or phraseology, to quickly determine the nature and substance of the technical disclosure of the application through a cursory review. The Abstract of the Disclosure is not intended to limit the scope in any way.

[0443] Finally, it is Applicant's intent that only claims containing the express language "means for" or "step for" be interpreted under 35 U.S.C. § 112. Claims that do not expressly include the phrase "means for" or "step for" should not be interpreted under 35 U.S.C. § 112.

Claims

1. A wireless device, comprising: one or more processors; as well as a memory storing instructions that, when executed by the one or more processors, cause the wireless device to: Transmitting a first scheduling request SR based on a buffer status reporting procedure; triggering a second SR in response to an initial beam failure recovery; transmitting the second SR via an uplink control channel resource configured for the second SR; receiving first downlink control information via a downlink control channel; as well as Based on the first downlink control information: keeping the first SR pending; and The second SR used for the beam failure recovery is canceled.

2. The wireless device of claim 1 , wherein the uplink control channel resources include at least one of: frequency radio resources; Uplink control channel format; cyclic shifts of the basis sequence; and Time radio resources. The wireless device of claim 1 , wherein the first downlink control information comprises a downlink assignment or an uplink grant. 4 . The wireless device of claim 1 , wherein the instructions, when executed by the one or more processors, further cause the wireless device to complete the beam failure recovery in response to canceling the second SR.

5. The wireless device of claim 1 , wherein the instructions, when executed by the one or more processors, further cause the wireless device to receive one or more messages comprising at least one of: first configuration parameters of a first plurality of SRs including the first SR; and The second configuration parameter of the second SR.

6. The wireless device of claim 1, wherein the beam failure recovery is initiated in response to detecting a number of beam failure instances.

7. The wireless device of claim 6, wherein the number of beam failure instances are detected in response to a channel quality of one or more reference signal resources being below one or more first thresholds.

8. The wireless device of claim 6, wherein the instructions, when executed by the one or more processors, further cause the wireless device to select a first reference signal from a plurality of reference signals based on one or more second thresholds in response to initiating the beam failure recovery.

9. The wireless device of claim 8, wherein the second SR indicates at least one of: detecting the number of beam failure instances; and The first reference signal is selected.

10. The wireless device of claim 1, wherein the instructions, when executed by the one or more processors, further cause the wireless device to monitor a downlink control channel for the first downlink control information; The following items of the downlink control channel are monitored: at least one control resource set of the downlink control channel; and At least one search space of the downlink control channel.

11. The wireless device of claim 1 , wherein the instructions, when executed by the one or more processors, further cause the wireless device to monitor a downlink control channel for the first downlink control information; The downlink control channel is associated with the second SR and includes at least one of the following: at least one control resource set of the downlink control channel determined based on the second SR; and At least one search space of the downlink control channel is determined based on the second SR.

12. The wireless device of claim 1, wherein the instructions, when executed by the one or more processors, further cause the wireless device to transmit the first SR via a second uplink control channel resource configured for the first SR in response to keeping the first SR pending.

13. The wireless device of claim 1 , wherein the instructions, when executed by the one or more processors, further cause the wireless device to: receiving, via a second downlink control channel, second downlink control information including one or more uplink grants; and The first SR is canceled in response to the one or more uplink grants accommodating data available for uplink transmission.

14. A computer-readable storage medium comprising instructions that, when executed by one or more processors of a wireless device, cause the wireless device to: Transmitting a first scheduling request SR based on a buffer status reporting procedure; triggering a second SR in response to an initial beam failure recovery; transmitting the second SR via an uplink control channel resource configured for the second SR; receiving first downlink control information via a downlink control channel; and Based on the first downlink control information: keeping the first SR pending; and The second SR used for the beam failure recovery is canceled.

15. A wireless method comprising the following steps performed by a base station: Receiving a first scheduling request SR based on a buffer status reporting procedure; receiving a second SR triggered in response to an initial beam failure recovery; transmitting first downlink control information via a downlink control channel; and based on the first downlink control information; keeping the first SR pending; and The second SR used for the beam failure recovery is canceled. 16 . The method of claim 15 , further comprising completing the beam failover in response to canceling the second SR.

17. The method of claim 15, further comprising sending one or more messages comprising at least one of: first configuration parameters of a first plurality of SRs including the first SR; and The second configuration parameter of the second SR.

18. The method of claim 15, wherein the beam failure recovery is initiated in response to detecting a number of beam failure instances.

19. The method of claim 15, further comprising: sending, via a second downlink control channel, second downlink control information including one or more uplink grants; as well as The first SR is canceled in response to the one or more uplink grants accommodating data available for uplink transmission.

20. A base station, comprising: one or more processors; as well as a memory storing instructions that, when executed by the one or more processors, cause the base station to: Receiving a first scheduling request SR based on a buffer status reporting procedure; receiving a second SR triggered in response to an initial beam failure recovery; transmitting first downlink control information via a downlink control channel; as well as based on the first downlink control information; keeping the first SR pending; and The second SR used for the beam failure recovery is canceled.

21. The base station of claim 20, wherein the instructions, when executed by the one or more processors, further cause the base station to send one or more messages comprising at least one of: first configuration parameters of a first plurality of SRs including the first SR; and The second configuration parameter of the second SR.

22. A computer-readable storage medium comprising instructions which, when executed by one or more processors of a base station, cause the base station to perform the method according to any one of claims 15 to 19.

Images