Management beam failover updates

Abstract

In various embodiments, a method for managing beam failure recovery that may be performed by a processor of a wireless device may include determining that a contention-based random access (CBRA)-based beam failure recovery (BFR) procedure has completed, determining whether a new candidate beam reference signal identifier is identified and included in a BFR medium access control-control element (MAC-CE), updating beam information based on the new candidate beam reference signal identifier in response to determining that the new candidate beam reference signal identifier (RS ID) is identified and included in the BFR MAC-CE in a message to a base station, and updating beam information based on a synchronization signal block selected during the CBRA-based BFR procedure in response to determining that the new candidate beam RS ID is not identified and not included in the BFR MAC-CE in the message to the base station.

Description

Background Art

[0001] Fifth generation (5G) New Radio (NR) systems are capable of providing high data rate communication services to wireless devices. However, the frequency bands used to provide NR services, such as millimeter wave frequencies, are susceptible to rapid channel variations and suffer from free-space path loss and atmospheric absorption. To address these challenges, NR base stations and wireless devices can use highly directional antennas to achieve sufficient link budgets in wide area networks. Such highly directional antennas require, for example, the use of beam management operations to precisely align the transmitter and receiver beams. However, beam management operations may increase the delay in establishing a communication link and may affect control layer procedures such as initial access, switching, and beam tracking.

[0002] If the wireless device determines that the channel condition is below a threshold, the wireless device may determine that a beam failure has occurred. If the wireless device detects a threshold number of beam failures, the wireless device may initiate a beam failure recovery procedure with the base station. Summary of the Invention

[0003] Various aspects include systems and methods for managing beam failure recovery (BFR) performed by a processor of a wireless device. The various aspects may enable the wireless device to determine and update information related to a newly selected beam in a communication link with a base station after the wireless device base station performs a BFR procedure, such as, for example, a contention-based random access (CBRA) procedure.

[0004] Various aspects may include determining that a contention-based random access (CBRA) based beam failure recovery (BFR) procedure has completed, determining whether a new candidate beam reference signal identifier (RS ID) is identified and included in a BFR medium access control-control element (MAC-CE) in a message from the wireless device to the base station, updating beam information based on the new candidate beam reference signal identifier (RS ID) in response to determining that the new candidate beam reference signal identifier (RS ID) is identified and included in the BFR MAC-CE in the message from the wireless device to the base station, and updating beam information based on a synchronization signal block (SSB) selected during the CBRA based BFR procedure in response to determining that the new candidate beam RS ID is not identified and not included in the BFR MAC-CE in the message from the wireless device to the base station.

[0005] In some aspects, updating beam information may include updating one or more control resource sets (CORESETs) and physical downlink shared channels (PDSCHs) for downlink signals. In some aspects, updating beam information may include updating physical uplink control channels (PUCCHs), physical uplink shared channels (PUSCHs), and sounding reference signals (SRSs) for uplink signals. In some aspects, updating beam information may include updating downlink path loss reference signals (DL PLRSs). In some aspects, updating beam information may include resetting one or more power control parameters to default values.

[0006] In some aspects, updating the beam information may include updating the beam information prior to receiving a new activation command or reconfiguration message for the selected beam. In some aspects, determining that the CBRA-based BFR procedure has completed may include receiving a PDCCH including a cell radio network temporary identifier (C-RNTI) from the base station, and determining that the CBRA-based BFR procedure has completed in response to receiving the PDCCH including the C-RNTI from the base station.

[0007] In some aspects, determining that the CBRA-based BFR procedure has completed may include receiving a PDCCH message delivered on a special CORESET or in a search space dedicated to BFR responses. In some aspects, determining that the CBRA-based BFR procedure has completed may include receiving a PDCCH message that schedules a new uplink grant with the same Hybrid Automatic Repeat Request (HARQ) ID used to send messages from the wireless device to the base station. In some aspects, determining that the CBRA-based BFR procedure has completed may include receiving a PDCCH message indicating that the CBRA-based BFR procedure has successfully completed.

[0008] In some aspects, updating the beam information may include determining a timing for updating the beam information, and updating the beam information according to the determined timing. In some aspects, determining the timing for updating the beam information may include determining a number of symbols before the MAC layer delivers an indication to the physical layer (PHY layer) that the CBRA-based BFR procedure has successfully completed after receiving the latest PDCCH with the C-RNTI. In some aspects, determining the timing for updating the beam information may include updating the beam information in response to determining that a PDCCH with the C-RNTI is received within a time window before the MAC layer provides the PHY layer with an indication that the CBRA-based BFR procedure has successfully completed. In some aspects, determining that the CBRA-based BFR procedure has completed may include receiving a PDCCH addressed to the C-RNTI from the base station after transmission of the BFR MAC-CE, and determining that the CBRA-based BFR procedure has completed in response to receiving the PDCCH including the C-RNTI from the base station.

[0009] Additional aspects may include a wireless device having a processor configured to perform one or more operations of any of the methods outlined above. Additional aspects may include a processing device for use in a wireless device, the processing device configured with processor-executable instructions to perform the operations of any of the methods outlined above. Additional aspects may include a non-transitory processor-readable storage medium having processor-executable instructions stored thereon, the processor-executable instructions configured to cause the processor of the wireless device to perform the operations of any of the methods outlined above. Additional aspects include a wireless device having components for performing the functions of any of the methods outlined above. Additional aspects include a system-on-chip for use in a wireless device, the system-on-chip including a processor configured to perform one or more operations of any of the methods outlined above. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a system block diagram illustrating an example communication system suitable for implementing any of the various embodiments.

[0011] Figure 2 is a component block diagram illustrating an example computing system suitable for implementing any of the various embodiments.

[0012] Figure 3 is a component block diagram illustrating a software architecture including a radio protocol stack suitable for implementing user and control planes in wireless communications in accordance with any of the various embodiments.

[0013] Figure 4 is a component block diagram illustrating a system configured for managing beam failure recovery in accordance with various embodiments.

[0014] Figure 5is a process flow diagram illustrating a method for managing beam failure recovery that may be performed by a processor of a wireless device in accordance with various embodiments.

[0015] Figures 6-10 is a process flow diagram illustrating operations that may be performed by a processor of a wireless device as part of a method for managing beam failure recovery in accordance with various embodiments.

[0016] Figure 11 is a process flow diagram illustrating a method for managing beam failure recovery that may be performed by a processor of a base station according to various embodiments.

[0017] Figure 12A is a process flow diagram illustrating a method for managing beam failure recovery that may be performed by a processor of a wireless device in accordance with various embodiments.

[0018] Figure 12B is a timeline diagram illustrating a four-step contention-based random access (CBRA) procedure.

[0019] Figure 12C is a timeline diagram illustrating the two-step CBRA process.

[0020] Figure 12D is a timeline diagram illustrating an embodiment of updating beam information.

[0021] Figure 13 is a process flow diagram illustrating operations that may be performed by a processor of a wireless device as part of a method for managing beam failure recovery in accordance with various embodiments.

[0022] Figure 14A is a process flow diagram illustrating operations that may be performed by a processor of a wireless device as part of a method for managing beam failure recovery in accordance with various embodiments.

[0023] Figure 14B This is a timeline diagram of the timing for updating beam information.

[0024] Figure 15A is a process flow diagram illustrating operations that may be performed by a processor of a wireless device as part of a method for managing beam failure recovery in accordance with various embodiments.

[0025] Figure 15B This is a timeline diagram of the timing for updating beam information.

[0026] Figure 16 is a component block diagram of a network computing device suitable for use with various embodiments.

[0027] Figure 17 is a component block diagram of a wireless communication device suitable for use with various embodiments.

[0028] Specific implementation method

[0029] Various embodiments will be described in detail with reference to the accompanying drawings. Throughout the drawings, the same reference numerals are used to refer to the same or similar parts whenever possible. References to specific examples and implementations are for illustrative purposes only and are not intended to limit the scope of the claims.

[0030] Various embodiments include systems and methods for managing information transmission for wireless communications between devices, such as a base station and a wireless device. Various embodiments include systems and methods for managing beam failure recovery (BFR) performed by a processor of a wireless device. Various embodiments may enable a wireless device to initiate a contention-based random access procedure (CBRA) in the event of a beam failure in a communication link with a base station. Some aspects may enable a wireless device to initiate a CBRA when downlink and / or uplink resources for performing a contention-free random access procedure (CFRA) are unavailable to the wireless device.

[0031] The term "wireless device" as used herein refers to wireless router devices, wireless appliances, cellular phones, smartphones, portable computing devices, personal or mobile multimedia players, laptop computers, tablet computers, smartbooks, ultrabooks, handheld computers, wireless email receivers, multimedia Internet-enabled cellular phones, medical devices and equipment, biosensors / devices, wearable devices including smart watches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings and smart bracelets), entertainment devices (e.g., wireless game controllers, music and video players, satellite radios, etc.), Internet of Things (IoT) devices including smart meters / sensors, industrial manufacturing equipment, large and small machines and appliances used in homes or businesses that support wireless networks, wireless communication elements within autonomous and semi-autonomous vehicles, wireless devices fixed to or incorporated into various mobile platforms, global positioning system devices, and similar electronic devices that include memory, wireless communication components, and programmable processors.

[0032] The term "system on chip" (SOC) as used herein refers to a single integrated circuit (IC) chip that contains multiple resources or processors integrated on a single substrate. A single SOC may contain circuits for digital, analog, mixed-signal, and radio frequency functions. A single SOC may also include any number of general-purpose or special-purpose processors (digital signal processors, modem processors, video processors, etc.), memory blocks (such as ROM, RAM, flash memory, etc.), and resources (such as timers, voltage regulators, oscillators, etc.). The SOC may also include software for controlling the integrated resources and processors and for controlling peripheral devices.

[0033] The term "system-in-package" (SIP) may be used herein to refer to a single module or package that contains multiple resources, computing units, cores, or processors on two or more IC chips, substrates, or SOCs. For example, a SIP may include a single substrate on which multiple IC chips or semiconductor dies are stacked in a vertical configuration. Similarly, a SIP may include one or more multi-chip modules (MCMs) on which multiple ICs or semiconductor dies are packaged into a unified substrate. A SIP may also include multiple independent SOCs that are coupled together via high-speed communication circuits and are tightly packaged, such as on a single motherboard or in a single wireless device. The tightness of the SOCs facilitates high-speed communication and the sharing of memory and resources.

[0034] The NR base station and wireless device perform beam management operations to precisely align the transmitter and receiver beams. If the wireless device determines that the channel conditions are below a threshold, the wireless device can attempt to initiate a beam failure recovery procedure with the base station.

[0035] For example, in NR, a wireless device and a base station (e.g., a gNodeB) can communicate via the beam with the highest signal strength (such as a synchronization signal block). In some embodiments, the base station can transmit P / SP / AP channel state indicator-reference signal (CSI-RS) (e.g., in connected mode) periodically, semi-persistently (AP), or aperiodically (AP) to enable the wireless device to decode the beam specified by the transmission configuration indicator (TCI). The wireless device can report channel conditions, such as received signal strength (e.g., layer 1 reference signal received power (L1-RSRP)) to the base station. The wireless device can also report channel state feedback (CSF) of the serving beam (i.e., the beam currently used for communication between the wireless device and the base station) and one or more neighbor (or candidate) beams to the base station.

[0036] In some embodiments, if the wireless device determines that the channel condition is below a threshold (e.g., L1-RSRP is below a threshold signal strength), the wireless device may start a timer (e.g., T310 timer) to detect beam failure. The wireless device may report the detected beam failure to the network using a beam failure detection resource set, which in some embodiments may be configured by the network in a radio resource control (RRC) reconfiguration message. The wireless device may search for another candidate beam that can provide quality service to the wireless device. If the wireless device determines that a threshold number of beam failure detections have occurred, the wireless device may attempt to initiate a BFR to a candidate beam of the network. BFR requires the wireless device to report the beam failure to the base station on which it is camped. In some embodiments, the wireless device may initiate BFR by attempting a CFRA procedure to communicate with the base station. However, in some cases, the communication resources for performing CFRA may not be available to the wireless device.

[0037] In some embodiments, when a wireless device detects beam failure on at least one serving cell (which may be a secondary cell or a special cell), CBRA-based BFR can be triggered for the secondary cell (SCell) and / or special cell (SpCell). In some embodiments, the wireless device can determine that beam failure has occurred if the number of physical layer (PHY layer) indicators exceeds a threshold number of indicators within a period of time. Each PHY layer indicator can be sent from the PHY layer to the MAC layer to indicate that all monitored beam failure detection (BFD) reference signals (RS) have a BLER greater than a threshold BLER (e.g., 10%). In some embodiments, the BLER can include a hypothetical BLER (e.g., a hypothetical physical downlink control channel (PDCCH) BLER), which can be determined based on the quality of the BFD RS. If resources are not configured for CFRA-based BFR or PUCCH-SR-based BFR, the wireless device can initiate CBRA-based BFR.

[0038] The CBRA-based BFR procedure can adopt a four-step process or a two-step process. In the four-step BFR based on CBRA, first, the wireless device may select a synchronization signal block (SSB) and a preamble associated with the SSB to send a message to the base station (e.g., Msg 1). Second, the wireless device may receive a message from the base station (e.g., Msg 2) including a PDCCH message scrambled with a random access radio network temporary identifier (RA-RNTI) and a physical downlink shared channel (PDSCH) message including a random access preamble ID (RAPID) and a temporary cell RNTI (C-RNTI). Third, the wireless device may send a message to the base station (e.g., Msg 3) including a C-RNTI medium access control-control element (MAC-CE). Msg 3 or other messages to the base station may also include a BFR MAC-CE, which may include a failed serving cell index and may identify a new candidate beam reference signal identifier (RS ID). Fourth, the wireless device may receive a message (e.g., Msg4) from the base station, which may include a PDCCH scrambled with a C-RNTI (e.g., as carried in Msg 3 C-RNTI MAC-CE), which may be a response to the CBRA-based BFR.

[0039] In two-step CBRA-based BFR, first, the wireless device may select an SSB and a preamble associated with the SSB for preamble transmission (e.g., Msg A preamble transmission), and may send a message (e.g., Msg A payload), for example, carried in a Physical Uplink Shared Channel (PUSCH) message to the base station, which may include a C-RNTI MAC-CE. The message may also include a BFR MAC-CE, which may include a failed serving cell index and may also include an identified new candidate beam RS ID. Second, the wireless device may receive a message (e.g., Msg B) from the base station, which may include a PDCCH message scrambled with the C-RNTI conveyed in the C-RNTI MAC-CE (e.g., in the Msg A payload), which may be a response to the CBRA-based BFR.

[0040] Various embodiments enable wireless devices to update information such as beam information, path loss reference signal information, and other information required for communication with a base station after CBRA-based BFR execution. For simplicity, the term "beam information" is used herein to refer to beam information, path loss reference signal information, and / or other information required for communication with a base station.

[0041] In some embodiments, the wireless device may determine that a contention-based random access (CBRA)-based BFR procedure has successfully completed. In some embodiments, the completed CBRA-based BFR procedure may have selected a beam for communication with the base station. The wireless device may determine whether a new candidate beam reference signal identifier (RS ID) is identified and included in a BFR medium access control-control element (MAC-CE) in a message from the wireless device to the base station. In response to determining that the new candidate beam reference signal identifier (RS ID) is identified and included in the BFR MAC-CE in the message from the wireless device to the base station, the wireless device may update beam information based on the new candidate beam RS ID. In response to determining that the new candidate beam RS ID is not identified and not included in the BFR MAC-CE in the message from the wireless device to the base station, the wireless device may update beam information based on the synchronization signal block (SSB) selected during the CBRA-based BFR procedure.

[0042] In some embodiments, the wireless device may update one or more control resource sets (CORESETs) and physical downlink shared channels (PDSCHs) for downlink signals. In some embodiments, the wireless device may update physical uplink control channels (PUCCHs), physical uplink shared channels (PUSCHs), and sounding reference signals (SRSs) for uplink signals. In some embodiments, the wireless device may update downlink path loss reference signals (DL PL RSs). In some embodiments, the wireless device may reset one or more power control parameters to default values. In some embodiments, the wireless device may update beam information before receiving a new activation command or reconfiguration message for a selected beam. In some embodiments, determining completion of a contention-based random access (CBRA) beam failure recovery (BFR) procedure for selecting a beam for communication with a base station may include determining completion of the contention-based random access in response to receiving a PDCCH including a cell radio network temporary identifier (C-RNTI) from the base station.

[0043] In some embodiments, for CBRA-based BFR, the wireless device may send at least one MAC CE in the PUSCH in Msg 3 or Msg A, the MAC CE providing an index for at least one corresponding serving cell with a radio link quality worse than Qout,LR and, if available, an index q_new for the periodic CSI-RS configuration or SS / PBCH block provided by higher layers for the corresponding serving cell (as may be described in the relevant 3GPP technical standard). After successfully completing CBRA-based BFR, 28 symbols after the last symbol received from the Msg4 / B PDCCH, the wireless device may monitor the PDCCH in all CORESETs on the serving cell indicated by the MAC CE using the same antenna port quasi-co-location parameters associated with the corresponding index q_new, if available, where the user equipment (UE) detected a DCI format with a CRC scrambled by the C-RNTI in the Msg4 / B PDCCH reception. If the wireless device is provided with PUCCH-SpatialRelationInfo for PUCCH and / or PUCCH-Cell is included in the serving cell indicated by the MAC-CE, the wireless device may transmit the PUCCH on the PUCCH-Cell using the same spatial domain filter as the spatial domain filter corresponding to q_new received for periodic CSI-RS or SS / PBCH blocks (as may be described in a related 3GPP technical standard) and using a transmit power determined by q_u = 0, q_d = q_new, and l = 0. If the wireless device is provided with spatialRelationInfo for SRS resources, the wireless device may transmit SRS resources with higher layer parameters set to "codebook" and "non-codebook" in SRS-ResourceSet using the same spatial domain filter as the spatial domain filter corresponding to q_new received for periodic CSI-RS or SS / PBCH blocks and using a transmit power determined by q_d = q_new and l = 0 (as may be described in a related 3GPP technical standard). The SCS configuration of 28 symbols is the smallest of the SCS configuration of the active DL BWP for PDCCH reception and the SCS configuration of the active DL BWP of at least one serving cell.

[0044] Various embodiments enable wireless devices to update beam information and / or path loss information, for example, after a CBRA-based BFR procedure has completed. Various embodiments improve the operation of wireless devices and communication networks by enabling wireless devices to update information required to maintain communications after a CBRA-based BFR procedure has completed. Thus, various embodiments improve the operation of wireless devices and communication networks by improving the quality and efficiency of their communication operations.

[0045] Figure 1 A system block diagram illustrating an example communication system is shown. The communication system 100 may be a 5G New Radio (NR) network, or any other suitable network, such as a Long Term Evolution (LTE) network.

[0046] The communication system 100 may include a heterogeneous network architecture including a core network 140 and various wireless devices (in Figure 1 120e). The communication system 100 may also include multiple base stations (illustrated as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station is an entity that communicates with wireless devices and may also be referred to as a computing platform B, computing platform B, LTE evolved computing platform B (eNB), access point (AP), radio head, transmit receive point (TRP), new radio base station (NR BS), 5G computing platform B (NB), next generation computing platform B (gNB), etc. Each base station can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to the coverage area of ​​a base station, a base station subsystem serving the coverage area, or a combination thereof, depending on the context in which the term is used.

[0047] The base stations 110a-110d may provide communication coverage for a macro cell, a pico cell, a femto cell, another type of cell, or a combination thereof. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to wireless devices with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access to wireless devices with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to wireless devices associated with the femto cell (e.g., wireless devices in a closed subscriber group (CSG)). The base station of a macro cell may be referred to as a macro BS. The base station of a pico cell may be referred to as a pico BS. The base station of a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown, base station 110a may be a macro BS for macrocell 102a, base station 110b may be a pico BS for picocell 102b, and base station 110c may be a femto BS for femtocell 102c. Base stations 110a-110d may support one or more (e.g., three) cells. The terms "eNB," "base station," "NR BS," "gNB," "TRP," "AP," "computing platform B," "5G NB," and "cell" may be used interchangeably herein.

[0048] In some examples, the cells may not be fixed, and the geographic area of ​​the cells may move depending on the location of the mobile base station. In some examples, base stations 110a-110d may be interconnected to each other and to one or more other base stations or network computing platforms (not shown) in communication system 100 via various types of backhaul interfaces, such as direct physical connections, virtual networks, or a combination thereof using any suitable transport network.

[0049] The base stations 110a-110d may communicate with the core network 140 via wired or wireless communication links 126. The wireless devices 120a-120e may communicate with the base stations 110a-110d via wireless communication links 122.

[0050] The wired communication link 126 may use various wired networks (such as Ethernet, TV cable, telephone, fiber optic, and other forms of physical network connections) that may use one or more wired communication protocols such as Ethernet, Point-to-Point Protocol, High-Level Data Link Control (HDLC), Advanced Data Communications Control Protocol (ADCCP), and Transmission Control Protocol / Internet Protocol (TCP / IP).

[0051] The communication system 100 may also include a relay station (such as relay BS 110d). A relay station is an entity that can receive data transmissions from an upstream station (e.g., a base station or wireless device) and send data transmissions to a downstream station (e.g., a wireless device or base station). A relay station may also be a wireless device that can relay transmissions for other wireless devices. Figure 1 In the example shown, a relay station 110d can communicate with the macro base station 110a and the wireless device 120d to facilitate communication between the base station 110a and the wireless device 120d. A relay station may also be referred to as a relay base station, relay base station, relay, etc.

[0052] The communication system 100 may be a heterogeneous network that includes different types of base stations, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations may have different transmit power levels, different coverage areas, and different impacts on interference in the communication system 100. For example, a macro base station may have a transmit power level (e.g., 5 to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0053] A network controller 130 may be coupled to a set of base stations and may provide coordination and control for these base stations. The network controller 130 may communicate with the base stations via a backhaul. The base stations may also communicate with each other directly or indirectly, for example, via a wireless or wired backhaul.

[0054] Wireless devices 120a, 120b, 120c may be dispersed throughout the communication system 100, and each wireless device may be fixed or mobile. A wireless device may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc.

[0055] The macro base station 110a may communicate with the communication network 140 via a wired or wireless communication link 126. The wireless devices 120a, 120b, 120c may communicate with the base stations 110a-110d via a wireless communication link 122.

[0056] The wireless communication links 122 and 124 may include multiple carrier signals, frequencies, or frequency bands, each of which may include multiple logical channels. The wireless communication links 122 and 124 may utilize one or more radio access technologies (RATs). Examples of RATs that may be used in the wireless communication links include 3GPP LTE, 3G, 4G, 5G (such as NR), GSM, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMAX), Time Division Multiple Access (TDMA), and other mobile phone communication technology cellular RATs. Additional examples of RATs that may be used in one or more of the various wireless communication links within the communication system 100 include medium-range protocols such as Wi-Fi, LTE-U, LTE-Direct, LAA, MuLTEfire, and relatively short-range RATs such as ZigBee, Bluetooth, and Bluetooth Low Energy (LE).

[0057] Some wireless networks, such as LTE, utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kHz, and the minimum resource allocation (called a "resource block") can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal fast file transfer (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband may cover 1.08 MHz (ie, 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0058] Although the description of some implementations may use terminology and examples associated with LTE technology, some implementations may be applicable to other wireless communication systems, such as New Radio (NR) or 5G networks. NR can utilize OFDM with a cyclic prefix (CP) on the uplink (UL) and downlink (DL) and includes support for half-duplex operation using time division duplexing (TDD). A single component carrier bandwidth of 100 MHz can be supported. An NR resource block can span 12 subcarriers in a duration of 0.1 milliseconds (ms) with a subcarrier bandwidth of 75 kHz. Each radio frame can consist of 50 subframes of 10 ms in length. Therefore, each subframe can have a length of 0.2 ms. Each subframe can indicate the link direction (i.e., DL or UL) used for data transmission, and the link direction of each subframe can be switched dynamically. Each subframe can include DL / UL data and DL / UL control data. Beamforming can be supported, and the beam direction can be dynamically configured. Multiple-input multiple-output (MIMO) transmission with precoding can also be supported. MIMO configurations in the DL can support up to eight transmit antennas with multi-layer DL transmissions of up to eight streams and up to two streams per wireless device. Multi-layer transmissions of up to two streams per wireless device can be supported.

[0059] Aggregation of multiple cells up to eight cells can be supported. Alternatively, NR can support a different air interface instead of an OFDM-based air interface.

[0060] Some wireless devices may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) wireless devices. MTC and eMTC wireless devices include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which may communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless computing platform may provide connectivity to or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some wireless devices may be considered Internet of Things (IoT) devices, or may be implemented as NB-IoT (Narrowband Internet of Things) devices. The wireless devices 120a-120e may be included in a housing that houses components of the wireless devices 120a-120e, such as a processor component, a memory component, the like, or a combination thereof.

[0061] Generally, any number of communication systems and any number of wireless networks can be deployed in a given geographic area. Each communication system and wireless network can support a specific radio access technology (RAT) and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, channel, etc. Each frequency can support a single RAT in a given geographic area to avoid interference between communication systems of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0062] In some implementations, two or more wireless devices (e.g., shown as wireless device 120a and wireless device 120e) may communicate directly using one or more sidelink channels (e.g., without using base stations 110a-d as an intermediary for communicating with each other). For example, the wireless devices 120a-e may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or similar protocols), mesh networks, or similar networks, or a combination thereof. In this case, the wireless devices 120a-120e may perform scheduling operations, resource selection operations, and other operations performed by the base stations 110a-110d described elsewhere herein.

[0063] Figure 2 is a component block diagram illustrating an example computing and wireless modem system 200 suitable for implementing any of the various embodiments. The various embodiments may be implemented on a variety of single-processor and multi-processor computer systems, including system-on-chip (SOC) or system-in-package (SIP).

[0064] refer to Figure 1 and Figure 2 , the illustrated example computing system 200 (which may be a SIP in some embodiments) includes two SOCs 202, 204 coupled to a clock 206, a voltage regulator 208, and a wireless transceiver 266, the wireless transceiver 266 being configured to transmit / receive wireless communications to / from a wireless device such as the base station 110a via an antenna (not shown). In some implementations, the first SOC 202 may operate as a central processing unit (CPU) of the wireless device, executing instructions of a software application by performing arithmetic, logic, control, and input / output (I / O) operations specified by the instructions. In some implementations, the second SOC 204 may operate as a dedicated processing unit. For example, the second SOC 204 may operate as a dedicated 5G processing unit responsible for managing high-capacity, high-speed (such as 5 Gbps), or very high frequency short wavelength (such as 28 GHz millimeter wave spectrum) communications.

[0065] The first SOC 202 may include a digital signal processor (DSP) 210, a modem processor 212, a graphics processor 214, an application processor 216, one or more coprocessors 218 (such as a vector coprocessor) connected to one or more of the processors, memory 220, custom circuitry 222, system components and resources 224, an interconnect / bus module 226, one or more temperature sensors 230, a thermal management unit 232, and a thermal power envelope (TPE) component 234. The second SOC 204 may include a 5G modem processor 252, a power management unit 254, an interconnect / bus module 264, multiple mmWave transceivers 256, memory 258, and various additional processors 260, such as an application processor, a packet processor, and the like.

[0066] Each processor 210, 212, 214, 216, 218, 252, 260 may include one or more cores, and each processor / core may perform operations independently of the other processors / cores. For example, the first SOC 202 may include a processor running a first type of operating system (such as FreeBSD, LINUX, OS X, etc.) and a processor running a second type of operating system (such as MICROSOFT WINDOWS 10). In addition, any or all of the processors 210, 212, 214, 216, 218, 252, 260 may be included as part of a processor cluster architecture (such as a synchronous processor cluster architecture, an asynchronous or heterogeneous processor cluster architecture, etc.).

[0067] The first SOC 202 and the second SOC 204 may include various system components, resources, and custom circuits for managing sensor data, analog-to-digital conversion, wireless data transmission, and for performing other specialized operations, such as decoding data packets and processing encoded audio and video signals for presentation in a web browser. For example, the system components and resources 224 of the first SOC 202 may include power amplifiers, voltage regulators, oscillators, phase-locked loops, peripheral bridges, data controllers, memory controllers, system controllers, access ports, timers, and other similar components for supporting processors and software clients running on the wireless device. The system components and resources 224 or custom circuits 222 may also include circuits for interfacing with peripheral devices such as, for example, cameras, electronic displays, wireless communication devices, external memory chips, and the like.

[0068] The first SOC 202 and the second SOC 204 can communicate via an interconnect / bus module 250. The various processors 210, 212, 214, 216, 218 can be interconnected to one or more memory elements 220, system components and resources 224, custom circuits 222, and a thermal management unit 232 via an interconnect / bus module 226. Similarly, the processor 252 can be interconnected to a power management unit 254, a millimeter wave transceiver 256, a memory 258, and various additional processors 260 via an interconnect / bus module 264. The interconnect / bus modules 226, 250, 264 may include an array of reconfigurable logic gates or may implement a bus architecture (such as CoreConnect, AMBA, etc.). Communication may be provided by an advanced interconnect such as a high-performance network on chip (NOC).

[0069] The first SOC 202 or the second SOC 204 may also include an input / output module (not shown) for communicating with resources external to the SOC, such as a clock 206 and a voltage regulator 208. Resources external to the SOC (such as the clock 206 and the voltage regulator 208) may be shared by two or more internal SOC processors / cores.

[0070] In addition to the example SIP 200 discussed above, some implementations may be implemented in a variety of computing systems that may include a single processor, multiple processors, multi-core processors, or any combination thereof.

[0071] Figure 3 is a component block diagram illustrating a software architecture 300 including a radio protocol stack suitable for implementing user and control planes in wireless communications in accordance with any of the various embodiments. Figure 1-Figure 3 Wireless device 320 may implement software architecture 300 to facilitate communication between wireless device 320 (e.g., wireless devices 120a-120e, 200) and base station 350 (e.g., base station 110a) of a communication system (e.g., 100). In various embodiments, the layers in software architecture 300 may form logical connections with corresponding layers in the software of base station 350. Software architecture 300 may be distributed across one or more processors (e.g., processors 212, 214, 216, 218, 252, 260). Although described with respect to a single radio protocol stack, in a multi-SIM (Subscriber Identity Module) wireless device, software architecture 300 may include multiple protocol stacks, each associated with a different SIM (e.g., two protocol stacks associated with each SIM in a dual-SIM wireless communication device). Although described below with reference to LTE communication layers, software architecture 300 may support any of a variety of standards and protocols for wireless communication and / or may include additional protocol stacks that support any of a variety of standards and protocols for wireless communication.

[0072] The software architecture 300 may include a non-access stratum (NAS) 302 and an access stratum (AS) 304. The NAS 302 may include functions and protocols that support packet filtering, security management, mobility control, session management, and traffic and signaling between a wireless device's SIM (such as SIM 204) and its core network 140. The AS 304 may include functions and protocols that support communication between a SIM (such as SIM 204) and supported access network entities (such as base stations). Specifically, the AS 304 may include at least three layers (Layer 1, Layer 2, and Layer 3), each of which may contain various sublayers.

[0073] In the user plane and control plane, Layer 1 (L1) of the AS 304 may be a physical layer (PHY) 306, which may oversee functions capable of transmitting or receiving over an air interface via a wireless transceiver (e.g., 266). Examples of such physical layer 306 functions may include cyclic redundancy check (CRC) attachment, coding blocks, scrambling and descrambling, modulation and demodulation, signal measurement, MIMO, etc. The physical layer may include various logical channels, including a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH).

[0074] In the user plane and control plane, Layer 2 (L2) of AS 304 may be responsible for the link between wireless device 320 and base station 350 on physical layer 306. In some implementations, Layer 2 may include a medium access control (MAC) sublayer 308, a radio link control (RLC) sublayer 310, and a packet data convergence protocol (PDCP) 312 sublayer, each of which forms a logical connection that terminates at base station 350.

[0075] In the control plane, Layer 3 (L3) of AS 304 may include a radio resource control (RRC) sublayer 3. Although not shown, software architecture 300 may include additional Layer 3 sublayers, as well as various upper layers above Layer 3. In some implementations, RRC sublayer 313 may provide functionality including broadcasting system information, paging, and establishing and releasing RRC signaling connections between wireless devices 320 and base stations 350.

[0076] In some implementations, the PDCP sublayer 312 can provide uplink functions, including multiplexing between different radio bearers and logical channels, sequence number addition, handover data processing, integrity protection, ciphering, and header compression. In the downlink, the PDCP sublayer 312 can provide functions including in-order delivery of data packets, duplicate data packet detection, integrity verification, decryption, and header decompression.

[0077] In the uplink, the RLC sublayer 310 may provide segmentation and concatenation of upper layer data packets, retransmission of lost data packets, and automatic repeat request (ARQ). In the downlink, the functions of the RLC sublayer 310 may include reordering of data packets to compensate for out-of-order reception, reassembly of upper layer data packets, and ARQ.

[0078] In the uplink, the MAC sublayer 308 may provide functions including multiplexing between logical and transport channels, random access procedures, logical channel priority, and hybrid ARQ (HARQ) operations. In the downlink, MAC layer functions may include intra-cell channel mapping, demultiplexing, discontinuous reception (DRX), and HARQ operations.

[0079] While the software architecture 300 may provide functionality for sending data over a physical medium, the software architecture 300 may also include at least one host layer 314 to provide data transfer services to various applications in the wireless device 320. In some implementations, the application-specific functionality provided by the at least one host layer 314 may provide an interface between the software architecture and the general-purpose processor 206.

[0080] In other implementations, the software architecture 300 may include one or more higher logical layers (such as transport, session, presentation, application, etc.) that provide host layer functionality. For example, in some implementations, the software architecture 300 may include a network layer (such as an Internet Protocol (IP) layer), where the logical connection terminates at a packet data network (PDN) gateway (PGW). In some implementations, the software architecture 300 may include an application layer, where the logical connection terminates at another device (such as an end-user device, a server, etc.). In some implementations, the software architecture 300 may also include a hardware interface 316 between the physical layer 306 and communication hardware (such as one or more radio frequency (RF) transceivers) in the AS 304.

[0081] Figure 4 is a component block diagram illustrating a system 400 configured for managing beam failure recovery according to various embodiments. Figures 1-4 , system 400 may include a wireless device 402 (e.g., 120a-120e, 200, 320) and a base station 404 (e.g., 110-110d, 200, 350). The wireless device 402 and the base station 404 may communicate via a wireless communication network 424 (aspects of which are described in detail in the accompanying drawings). Figure 1 shown in ).

[0082] The wireless device 402 may include one or more processors 428 coupled to electronic memory 426 and a wireless transceiver (e.g., 266). The wireless transceiver 266 may be configured to receive messages to be sent in uplink transmissions from the processor 428 and transmit these messages via an antenna (not shown) to the wireless communication network 424 for relaying to the base station 404. Similarly, the wireless transceiver 266 may be configured to receive messages from the base station 404 in downlink transmissions from the wireless communication network 424 and pass these messages to the one or more processors 428 (e.g., via a modem (e.g., 252) which demodulates these messages).

[0083] The processor 428 may be configured by machine-readable instructions 406. The machine-readable instructions 406 may include one or more instruction modules. The instruction modules may include computer program modules. The instruction modules may include one or more of the CBRA BFR completion module 408, the candidate beam RS ID module 410, the beam information update module 412, or other instruction modules.

[0084] The CBRA BFR completion module 408 may be configured to determine that the CBRA-based BFR procedure has been completed.

[0085] The candidate beam RS ID module 410 may be configured to determine whether a new candidate beam reference signal identifier (RS ID) is identified and included in a BFR medium access control-control element (MAC-CE) in a message from the wireless device to the base station.

[0086] The beam information update module 412 may be configured to, in response to determining that a new candidate beam reference signal identifier (RS ID) is identified and included in a BFR MAC-CE in a message from the wireless device to the base station, update the beam information based on the new candidate beam RS ID. The beam information update module 412 may be configured to, in response to determining that the new candidate beam RS ID is not identified and not included in a BFR MAC-CE in a message from the wireless device to the base station, update the beam information based on a synchronization signal block (SSB) selected during the CBRA BFR procedure.

[0087] Electronic storage 426 may include non-transitory storage media that electronically stores information. The storage media of electronic storage 426 may include one or both of system memory provided integrally with wireless device 402 (i.e., substantially non-removable) and / or removable memory that is removably connected to wireless device 402 via, for example, a port (e.g., a Universal Serial Bus (USB) port, a FireWire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage 426 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, a magnetic hard drive, a floppy disk drive, etc.), charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drives, etc.), and / or other electronically readable storage media. Electronic storage 426 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and / or other virtual storage resources). Electronic storage 426 may store software algorithms, information determined by processor 420, information received from wireless device 402, or other information that enables wireless device 402 to function as described herein.

[0088] Processor 428 may be configured to provide information processing capabilities within wireless device 402. Thus, processor 428 may include one or more of a digital processor, an analog processor, digital circuitry designed to process information, analog circuitry designed to process information, a state machine, and / or other mechanisms for electronically processing information. Although processor 428 is illustrated as a single entity, this is for illustrative purposes only. In some implementations, processor 428 may include multiple processing units and / or processor cores. The processing units may be physically located within the same device, or processor 428 may represent processing functionality from multiple devices operating in coordination. Processor 428 may be configured to execute modules 408-412 and / or other modules. Processor 428 may be configured to execute modules 408-412 and / or other modules via software; hardware; firmware; some combination of software, hardware, and / or firmware; and / or other mechanisms for configuring processing capabilities within processor 428. As used herein, the term "module" may refer to any component or collection of components that performs the functionality attributed to that module. This may include one or more physical processors, processor readable instructions, circuitry, hardware, storage media, or any other component during execution of processor readable instructions.

[0089] The description of the functionality provided by the different modules 408-412 described below is for purposes of illustration and not limitation, as any module 408-412 may provide more or less functionality than described. For example, one or more of the modules 408-412 may be removed, and some or all of their functionality may be provided by other modules 408-412. As another example, the processor 428 may be configured to execute one or more additional modules that may perform some or all of the functionality attributed below to one of the modules 408-412. Figure 5 is a process flow diagram illustrating a method 500 for managing beam failure recovery that may be performed by a processor of a wireless device according to various embodiments. Figure 1-Figure 5 The operations of method 500 may be performed by a processor (such as processors 210, 212, 214, 216, 218, 252, 260, 428) of a wireless device (such as wireless devices 120a-120e, 200, 320, 402).

[0090] In determination block 502, the processor may determine whether a beam failure of a communication link with a base station has occurred. Means for performing the operations of determination block 502 may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 428) coupled to a wireless transceiver (e.g., 266).

[0091] In response to determining that beam failure has not occurred (ie, determination block 502 = "No"), the processor may repeat the operations of determination block 502.

[0092] In response to determining that beam failure has occurred (i.e., determination block 502 = "Yes"), the processor may identify a random access channel (RACH) opportunity in response to determining that beam failure has occurred in block 504. For example, the processor may determine that a channel condition (such as RSRP) is below a threshold (such as a signal strength threshold). Means for performing the operations of determination block 504 may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 428) coupled to a wireless transceiver (e.g., 266).

[0093] In determination block 506, the processor may determine whether contention-free random access (CFRA) resources have been configured. In some embodiments, the processor may determine whether a downlink beam has been mapped to the selected RACH opportunity. In some embodiments, the processor may determine whether a quasi-co-location (QCL) hypothesis has been mapped to the selected RACH opportunity. For example, two antenna ports are said to be quasi-coordinated if the properties of the channel transmitting symbols on one antenna port can be inferred from the channel transmitting symbols on the other antenna port. In some embodiments, the base station may send the QCL hypothesis to the wireless device via downlink control information (DCI). In some embodiments, the processor may determine whether the downlink reference signal (DL RS) mapped to the selected RACH opportunity (or physical RACH (PRACH) opportunity) is different from any active downlink beam or QCL hypothesis. The means for performing the operations of determination block 506 may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 428) coupled to a wireless transceiver (e.g., 266).

[0094] In response to determining that CFRA resources have been configured (i.e., determination block 506 = "Yes"), the processor may initiate CFRA in block 508. Means for performing the operations of determination block 508 may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 428) coupled to a wireless transceiver (e.g., 266).

[0095] In block 516, the processor may perform one or more beam failure recovery operations. Means for performing the operations of determination block 510 may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 428) coupled to a wireless transceiver (e.g., 266).

[0096] In response to determining that CFRA resources have not been configured (i.e., determination block 506 = "No"), the processor may initiate CBRA in block 510. In some embodiments, initiating CBRA may include performing one or more operations to begin a CBRA procedure. In some embodiments, initiating CBRA may include delivering a PRACH transmission, such as a random access preamble or another suitable message, to a base station. Means for performing the operations of determination block 510 may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 428) coupled to a wireless transceiver (e.g., 266).

[0097] In block 512, the processor may perform one or more beam failure recovery operations. Means for performing the operations of determination block 510 may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 428) coupled to a wireless transceiver (e.g., 266).

[0098] In block 514, the processor may transmit a PUCCH on the same cell as the PRACH transmission. In some embodiments, the processor may determine to reset the PUCCH beam to a PRACH beam based on one or more PRACH characteristics and one or more other conditions. In some embodiments, after successfully completing CBRA beam failure recovery, the processor may transmit the PUCCH on the same cell as the PRACH transmission. In some embodiments, the processor may transmit the PUCCH to a primary cell (PCell) or a primary secondary cell (PSCell). In some embodiments, for a PCell or PSCell, after successfully completing a contention-based random access procedure for beam failure recovery, the wireless device may transmit the PUCCH on the same cell as the PRACH transmission 28 symbols after the last symbol of the first PDCCH reception in a DCI format with a CRC scrambled by the C-RNTI after the wireless device detects the CRC, and until the wireless device receives an activation command for PUCCH-SpatialRelationInfo or is provided with PUCCH-SpatialRelationInfo for one or more PUCCH resources, using one or more of the same spatial filter and the determined power as the last PRACH transmission. In some embodiments, the power may be determined based on one or more parameters, including, for example, q_u=0, q_d=q_newCBRA, l=0, where q_newCBRA is an SS / PBCH block index provided by higher layers.

[0099] After the operations of block 514 or block 516 , the processor may again perform the operations of determination block 502 as described above.

[0100] Figures 6-10 is a process flow diagram illustrating operations 600-1000 that may be performed by a processor of a wireless device as part of a method 500 for managing beam failure recovery in accordance with various embodiments. Figures 1-10 , operations 600-1000 may be performed by a processor of a wireless device (such as wireless devices 120a-120e, 200, 320, 402).

[0101] Reference Figure 6 , in execution block 504 ( Figure 5), the processor may determine whether the downlink beam or quasi co-location (QCL) hypothesis mapped to the downlink reference signal (DL RS) of the selected RACH opportunity is different from any active downlink beam or quasi co-location (QCL) hypothesis in determination block 602. Means for performing the operations of determination block 602 may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 428) coupled to a wireless transceiver (e.g., 266).

[0102] In response to determining that the downlink beam or QCL hypothesis mapped to the DL RS of the selected RACH opportunity is not different from any active downlink beam or quasi co-located (QCL) hypothesis (ie, determination block 602 = "No"), the processor may perform the steps described with reference to Figure 5 The operations of block 508 are described (ie, initiating CFRA).

[0103] In response to determining that the downlink beam or QCL hypothesis mapped to the DL RS of the selected RACH opportunity is different from any active downlink beam or quasi co-location (QCL) hypothesis (ie, determination block 602 = "Yes"), the processor may perform the steps described with reference to Figure 5 The operations of block 510 (i.e., initiating CBRA) are described. In some embodiments, such a determination by the processor may imply that all active downlink transmit and receive (Tx / Rx) beam pairs have failed (e.g., the block error rate (BLER) of all active downlink Tx / Rx beam pairs exceeds a BLER threshold).

[0104] Reference Figure 7 , in execution block 504 ( Figure 5), in determination block 702, the processor may determine whether the downlink beam or QCL assumption of the DL RS mapped to the selected RACH opportunity is different from any activated transmission configuration indicator (TCI) state of one or more of a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH). In some embodiments, one or more TCI states may be delivered from the base station to the wireless device via a DCI message, which may include configurations such as QCL relationships between downlink reference signals (DL RSs) in a channel state indicator reference signal (CSI-RS) set and one or more PDSCH demodulation reference signal (DMRS) ports. In some embodiments, the TCI state may include parameters for configuring a quasi-co-located relationship between one or two downlink reference signals and a DMRS port of a PDSCH, a DMRS port of a PDCCH, or a CSI-RS port of a CSI-RS resource. Means for performing the operations of determination block 702 may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 428) coupled to a wireless transceiver (e.g., 266).

[0105] In response to determining that the downlink beam or QCL assumption mapped to the selected RACH opportunity does not have any activated TCI state other than one or more of the PDCCH and PDSCH (ie, determination block 702 = "No"), the processor may perform as described with reference to Figure 5 The operations of block 508 are described (ie, initiating CFRA).

[0106] In response to determining that the downlink beam or QCL assumption mapped to the DL RS of the selected RACH opportunity is different from any activated TCI state of one or more of the PDCCH and PDSCH (ie, determination block 702 = "Yes"), the processor may perform as described with reference to Figure 5 The operations of block 510 are described (ie, initiating CBRA).

[0107] Reference Figure 8 , in execution block 504 ( Figure 5 ), in determination block 802, the processor may determine whether the downlink beam or QCL hypothesis mapped to the DL RS of the selected RACH opportunity is different from any activated TCI state of the PDCCH having a control resource set (CORESET) monitored for beam failure detection. Means for performing the operations of determination block 802 may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 428) coupled to a wireless transceiver (e.g., 266).

[0108] In response to determining that the downlink beam or QCL assumption mapped to the selected RACH opportunity does not have any activated TCI state other than the PDCCH with the control resource set (CORESET) monitored for beam failure detection, the processor may perform the steps described with reference to Figure 5 The operations of block 508 are described (ie, initiating CFRA).

[0109] In response to determining that the downlink beam or QCL assumption mapped to the DL RS of the selected RACH opportunity is different from any activated TCI state of the PDCCH with the control resource set (ie, determination block 802 = "Yes"), the processor may perform as described with reference to Figure 5 The operations of block 510 are described (ie, initiating CBRA).

[0110] Reference Figure 9 , in execution block 504 ( Figure 5 ), in determination block 902, the processor may determine whether the downlink beam or QCL hypothesis of the DL RS mapped to the selected RACH opportunity is different from any active downlink beam or QCL hypothesis, and whether the uplink beam or spatial relationship of the PRACH is different from any active uplink beam or spatial relationship. In some embodiments, one or more PUCCH resource sets may be configured with a set of candidate spatial relationship signals via, for example, a radio resource control (RRC) message from a base station. Means for performing the operations of determination block 902 may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 428) coupled to a wireless transceiver (e.g., 266).

[0111] In response to determining that the downlink beam or QCL assumption of the DL RS mapped to the selected RACH opportunity is not different from any active downlink beam or QCL assumption, and the uplink beam or spatial relationship of the PRACH is different from any active uplink beam or spatial (i.e., determination block 902 = "No"), the processor may perform as described with reference to Figure 5 The operations of block 508 are described (ie, initiating CFRA).

[0112] In response to determining that the downlink beam or QCL hypothesis of the DL RS mapped to the selected RACH opportunity is different from any active downlink beam or QCL hypothesis, and the uplink beam or spatial relationship of the PRACH is different from any active uplink beam or spatial relationship (i.e., determination block 902 = "Yes"), the processor may perform as described with reference to Figure 5The operations of block 510 (i.e., initiating CBRA) are described. In some embodiments, such a determination by the processor may imply that all active downlink and uplink transmit and receive (Tx / Rx) beam pairs have failed (e.g., the block error rate (BLER) of all active downlink and uplink Tx / Rx beam pairs exceeds a BLER threshold).

[0113] Reference Figure 10 , in execution block 504 ( Figure 5 ), the processor may determine whether the uplink beam or spatial relationship of the PRACH is different from any active uplink beam or spatial relationship in determination block 1002. In some embodiments, the processor may perform the operations of determination block 1002 without regard to whether an active downlink beam or QCL hypothesis is associated with the selected RACH opportunity.

[0114] In response to determining that the uplink beam or spatial relationship of the PRACH is not different from any active uplink beam or spatial relationship (ie, determination block 1002 = "No"), the processor may perform a reference to Figure 5 The operations of block 508 are described (ie, initiating CFRA).

[0115] In response to determining that the uplink beam or spatial relationship of the PRACH is different from any active uplink beam or spatial relationship (ie, determination block 1002 = "Yes"), the processor may perform a reference to Figure 5 The operations of block 510 (i.e., initiating CBRA) are described. In some embodiments, such a determination by the processor may imply that all active uplink transmit and receive (Tx / Rx) beam pairs have failed (e.g., the block error rate (BLER) of all active uplink Tx / Rx beam pairs exceeds a BLER threshold).

[0116] Figure 11 is a process flow diagram illustrating a method 1100 for managing beam failure recovery that may be performed by a processor of a base station according to various embodiments. Figures 1-11 The operations of method 1100 may be performed by a processor (such as processors 210, 212, 214, 216, 218, 252, 260, 432) of a base station (such as base stations 110a-120d, 200, 350, 404).

[0117] In block 1102, the processor may receive a message from a wireless device initiating a contention-based random access (CBRA) based on the fact that no contention-free random access (CFRA) resources are configured for the wireless device. In some embodiments, the message may include a random access preamble. In some embodiments, the processor may determine a beam to be used by the wireless device, e.g., for a physical uplink control channel (PUCCH). Means for performing the operations of block 1102 may include a processor (such as processors 210, 212, 214, 216, 218, 252, 260, 432) coupled to a wireless transceiver (e.g., 266).

[0118] In determination block 1104, the processor may determine whether the downlink beam or QCL assumption for the downlink resources of the PRACH is different from any active downlink beam or QCL assumption. Means for performing the operations of determination block 1104 may include a processor (such as processors 210, 212, 214, 216, 218, 252, 260, 432) coupled to a wireless transceiver (e.g., 266).

[0119] In response to determining that the downlink beam or QCL hypothesis for the downlink resources of the PRACH is not different from any active downlink beam or QCL hypothesis (i.e., determination block 1104 = "No"), the processor may perform CFRA (e.g., with the wireless device) in block 1106. Means for performing the operations of determination block 1106 may include a processor (e.g., processors 210, 212, 214, 216, 218, 252, 260, 432) coupled to a wireless transceiver (e.g., 266).

[0120] In block 1108, the processor may perform one or more beam failure recovery operations. Means for performing the operations of determination block 1108 may include a processor (such as processors 210, 212, 214, 216, 218, 252, 260, 432) coupled to a wireless transceiver (e.g., 266).

[0121] In response to determining that the downlink beam or QCL hypothesis for the downlink resources of the PRACH is different from any active downlink beam or QCL hypothesis (i.e., determination block 1104 = "Yes"), the processor may perform CBRA (e.g., with the wireless device) in block 1110. Means for performing the operations of determination block 1110 may include a processor (such as processors 210, 212, 214, 216, 218, 252, 260, 432) coupled to a wireless transceiver (e.g., 266).

[0122] In block 1112, the processor may perform one or more beam failure recovery operations. Means for performing the operations of determining block 1112 may include a processor (such as processors 210, 212, 214, 216, 218, 252, 260, 432) coupled to a wireless transceiver (e.g., 266).

[0123] In block 1114, the processor may receive a PUCCH message on the same beam as the PRACH transmission. For example, the processor may receive a PUCCH message from the wireless device on the same beam on which the processor received the message initiating CBRA (e.g., block 1102). In some embodiments, the processor may switch the receive beam (Rx beam). In some embodiments, the processor may set the PUCCH beam to the PRACH beam. In some embodiments, the processor may determine to reset the PUCCH beam to the PRACH beam based on one or more PRACH characteristics and one or more other conditions. In some embodiments, after successfully completing CBRA beam failure recovery, the processor may receive the PUCCH on the same beam as the PRACH transmission (e.g., block 1112). In some embodiments, (for a PCell or PSCell), after 28 symbols after the last symbol of the first PDCCH reception in which the wireless device may detect a DCI format with a CRC scrambled by a C-RNTI and / or until the processor delivers an activation command of a PUCCH-SpatialRelationInfo to the wireless device or is provided with a PUCCH-SpatialRelationInfo for one or more PUCCH resources, the processor may reset the PUCCH beam to a PRACH beam. In this case, the processor may expect the wireless device to transmit the PUCCH on the same cell as the PRACH transmission, for example, using one or more of the same spatial filter and determined power as the last PRACH transmission. Means for performing the operations of block 1102 may include a processor (e.g., processors 210, 212, 214, 216, 218, 252, 260, 432) coupled to a wireless transceiver (e.g., 266).

[0124] After the operations of block 1108 or block 1114 , the processor may again perform the operations of block 1102 .

[0125] Figure 12A is a process flow diagram illustrating a method 1200 for managing beam failure recovery that may be performed by a processor of a wireless device in accordance with various embodiments; Figure 12B is a timeline diagram illustrating the four-step CBRA process. Figure 12C is a timeline diagram illustrating the two-step CBRA process. Figure 12DFIG12 is a timeline diagram 1270 illustrating an embodiment of updating information. Figure 1-12D The operations of method 1200 may be performed by a processor (such as processors 210, 212, 214, 216, 218, 252, 260, 428) of a wireless device (such as wireless devices 120a-120e, 200, 320, 402).

[0126] In block 512 ( Figure 5 ), in block 1202, the processor may determine that a CBRA-based BFR procedure for selecting a beam for communicating with a base station has been completed.

[0127] In determination block 1204, the processor may determine whether a new candidate beam reference signal identifier (RS ID) is identified and included in a BFR medium access control-control element (MAC-CE) in a message from the wireless device to the base station. In some embodiments, the new candidate beam RS ID may be included in Msg 3 of the four-step CBRA procedure. For example, referring to Figure 12B In the four-step CBRA procedure 1250, Msg 3 may include a BFR MAC-CE. In some embodiments, the BFR MAC-CE may or may not include new candidate beam information (NBI). As another example, refer to Figure 12C In the two-step CBRA procedure 1260, the Msg A PUSCH may include a BFR MAC-CE. In some embodiments, the BFR MAC-CE in the Msg A PUSCH may or may not include new candidate beam information (NBI).

[0128] Back to Figure 12A In response to determining that a new candidate beam RS ID is identified and included in the BFR MAC-CE in the message from the wireless device to the base station (i.e., determination block 1204 = "Yes"), the processor may update the beam information based on the new candidate beam RS ID in block 1206.

[0129] In response to determining that the new candidate beam RS ID was not identified and was not included in the BFR MAC-CE in the message from the wireless device to the base station (i.e., determination block 1204 = "No"), at block 1208, the processor may update the beam information based on the SSB selected during the CBRA-based BFR procedure. In some embodiments, the SSB beam may be a receive beam on which the wireless device receives messages from the base station in the CBRA procedure, and a transmit beam on which the wireless device transmits messages to the base station in the CBRA procedure (e.g., Msg 1 and / or Msg 3 of the four-step CBRA procedure, or Msg A of the two-step CBRA procedure). For example, in the CBRA procedure, the receive beam on which the wireless device receives messages from the base station may include Msg 2 and / or Msg 4 of the four-step CBRA procedure 1250 ( Figure 12B ), or Msg B of the two-step CBRA procedure 1260 ( Figure 12C As another example, in the CBRA process, the transmit beam on which the wireless device transmits a message to the base station may include Msg 1 and / or Msg 3 of the four-step CBRA procedure 1250, or Msg A of the two-step CBRA procedure 1260.

[0130] In various embodiments, updating beam information may include updating beam-specific information (such as QCL assumptions or TCI states) for downlink signals, and updating beam information may include updating beam-specific information (such as spatial filters, spatial relations, or TCI states) for uplink signals and / or updating path loss reference signals (PL RSs). As described above, in some embodiments, the processor may update beam information based on the SSB selected during the CBRA procedure, or based on a new candidate beam RS ID (if carried in a BFR MAC-CE in, for example, a Msg 3 or Msg A payload). In some embodiments, updating beam information may include updating downlink signals and / or beam information about uplink signals. In some embodiments, updating beam information may include updating downlink signals, such as one or more control resource sets (CORESETs) and a physical downlink shared channel (PDSCH). In some embodiments, updating beam information may include updating uplink signals, such as a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), and codebook and non-codebook sounding reference signals (SRSs).

[0131] In some embodiments, if a new candidate beam RS ID is identified during the CBRA procedure and a BFR MAC-CE is carried in Msg3 / A, the processor may update the beam information and PL RS based on the new candidate beam RS ID. If no new candidate beam RS ID is identified and / or the BFR MAC-CE is not carried in Msg3 / A, the processor may update the beam information and PL RS based on the SSB selected during the CBRA procedure, where the SSB beam is the receive beam for receiving Msg2 / 4 / B in the downlink and the transmit beam for sending Msg1 / 3 / A in the uplink.

[0132] In some embodiments, updating the beam information may include updating a downlink path loss reference signal (DL PL RS) for the uplink signal. In some embodiments, updating the beam information may include resetting one or more power control parameters to default values ​​for transmitting the uplink signal. In some embodiments, the power control parameters for transmitting the uplink signal may include one or more of P0 (transmit power target), alpha (path loss compensation factor), a closed loop index, and / or a power control adjustment state index.

[0133] After performing the operations of block 1206 or block 1208, the processor may receive a new activation command or reconfiguration message for the selected beam in block 1210. Thus, after successfully completing CBRA-based BFR and before receiving a new activation command or reconfiguration message (e.g., an RRC reconfiguration message) for the selected beam, the processor may update the beam information of the downlink or uplink signal.

[0134] In various embodiments, the processor may determine that the CBRA-based BFR procedure has successfully completed based on receipt of a message, such as a PDCCH message. Figure 12D In some embodiments, the processor may receive a PDCCH message 1272 delivered on a special CORESET or in a dedicated search space dedicated to BFR responses. In some embodiments, the processor may receive a PDCCH message 1274 scheduling a new uplink grant having the same parameters as those used to send, for example, the four-step CBRA procedure 1250 ( Figure 12B ) in Msg 3PUSCH or two-step CBRA procedure 1260 ( Figure 12C) in the Msg APUSCH, which already carries the BFR MAC-CE. In some embodiments, the processor may receive a PDCCH message 1276 carrying an indicator notifying the wireless device that CBRA-based BFR has successfully completed. In various embodiments, after successfully completing CBRA-based BFR and before receiving a new activation command or reconfiguration message 1278, the processor may update the beam information.

[0135] In some embodiments, the processor may determine the timing for updating the beam information. In some embodiments, the processor may update the beam information and PL RS after a number of symbols (e.g., X symbols, e.g., 28 symbols) after receiving a PDCCH message (e.g., 1272, 1274, 1276). In some embodiments, the symbol subcarrier spacing (SCS) may be the smaller of the PDCCH SCS and the scheduled transmission (Tx) SCS. In some embodiments, the processor may update the beam information and PL RS for the currently active downlink and uplink bandwidth parts (BWPs). In some embodiments, the processor may update the beam information and PL RS for all BWPs configured for transmission (Tx) of uplink signals and reception (Rx) of downlink signals.

[0136] The processor may continue to execute the method 500 as described above ( Figure 5 ) operation of box 510.

[0137] Figure 13 is a process flow diagram illustrating operations 1300 that may be performed by a processor of a wireless device as part of a method 1200 for managing beam failure recovery in accordance with various embodiments. Figures 1-13 , operations 1300 may be performed by a processor of a wireless device (such as wireless devices 120a - 120e , 200 , 320 , 402 ).

[0138] Reference Figure 13 After performing the operations of block 1210 ( FIG. 12 ), in determination block 1302 , the processor may determine whether a PDCCH including a cell radio network temporary identifier (C-RNTI) is received from a base station.

[0139] In response to determining that a PDCCH including a C-RNTI is received from the base station (ie, determination block 1302 = "Yes"), the processor may determine in block 1304 that the CBRA-based BFR procedure has completed.

[0140] The processor may continue to perform the operations of determination block 1204 ( FIG. 12 ).

[0141] In response to determining that a PDCCH including a C-RNTI was not received from the base station (ie, determination block 1302 = "No"), the processor may determine in block 1306 that the CBRA-based BFR procedure has not completed.

[0142] The processor may then proceed to execute (or continue) block 512 ( Figure 5 ) operation.

[0143] Figure 14A is a process flow diagram illustrating operations 1400 that may be performed by a processor of a wireless device as part of the method 1200 for managing beam failure recovery in accordance with various embodiments. Figure 14B FIG1 is a timeline diagram of the timing 1450 of updating beam information. Figure 1-14B The operations 1400 may be performed by a processor (such as the processors 210, 212, 214, 216, 218, 252, 260, 428) of a wireless device (such as the wireless devices 120a-120e, 200, 320, 402). The following description relates to the MAC layer and the PHY layer of the wireless device, and operations of both layers are implemented by the processor of the wireless device.

[0144] At block 1208 ( Figure 12A ), in determination block 1402, the MAC layer may determine whether CBRA is initiated for the purpose of performing BFR. In various embodiments, the wireless device may initiate a random access procedure for various purposes, including initial network access, base station handover, and desynchronization in uplink or downlink data transmission, as well as for the purpose of BFR.

[0145] In response to determining that the CBRA was initiated for the purpose of performing BFR (i.e., determination block 1402 = "Yes"), in determination block 1404, the MAC layer may determine whether a message delivered from the wireless device to the base station as part of the CBRA procedure (e.g., Msg 3 or Msg A) includes a C-RNTI MAC-CE or a BFR MAC-CE.

[0146] In response to determining that the message delivered from the wireless device to the base station as part of the CBRA procedure (e.g., Msg 3 or Msg A) includes a C-RNTI MAC-CE and / or a BFR MAC-CE (i.e., determination block 1404 = "Yes"), in determination block 1406, the MAC layer may determine whether the C-RNTI of the PDCCH received subsequent to the message to the base station matches the C-RNTI MAC-CE of the message to the base station.

[0147] In response to determining that CBRA was not initiated for the purpose of performing BFR (i.e., determination block 1402 = "No"), or that the message delivered from the wireless device to the base station as part of the CBRA procedure (e.g., Msg 3 or Msg A) was neither a C-RNTI MAC-CE nor a BFR MAC-CE (i.e., determination block 1404 = "No"), or that the C-RNTI of the PDCCH received subsequent to the message to the base station does not match the C-RNTI MAC-CE of the message to the base station (i.e., determination block 1406 = "No"), then in block 1408, the MAC layer may provide an indication to the PHY layer that BFR over CBRA did not complete successfully.

[0148] In response to determining that the C-RNTI of the PDCCH received after the message to the base station matches the C-RNTI MAC-CE of the message to the base station (i.e., determination block 1406 = "Yes"), the MAC layer may provide an indication to the PHY layer in block 1410 that the CBRA-based BFR was successfully completed.

[0149] In block 1412, the PHY layer may determine the timing for updating beam information. Figure 14B In some embodiments, the PHY layer may determine the timing for updating beam information 1450 based on the number X of symbols before the MAC layer delivers an indication of successful completion of a CBRA-based BFR procedure to the PHY layer after receiving the latest PDCCH with the C-RNTI. In some embodiments, the PHY layer may determine whether a PDCCH with the C-RNTI is received within a window of Y milliseconds (ms) before the MAC layer delivers an indication of successful completion of a CBRA-based BFR procedure to the PHY layer. In response to determining that a PDCCH with the C-RNTI is received within a window of Y milliseconds (ms) before the MAC layer delivers an indication of successful completion of a CBRA-based BFR procedure to the PHY layer, the PHY layer may initiate updating the beam information. In some embodiments, the value of Y ms may be a predetermined value. In some embodiments, the value of Y ms may be indicated by the MAC layer to the PHY layer.

[0150] Figure 15A is a process flow diagram illustrating operations 1500 that may be performed by a processor of a wireless device as part of the method 1200 for managing beam failure recovery in accordance with various embodiments. Figure 15B This is a timeline diagram of the timing for updating beam information. Figure 1-15BThe operations 1400 may be performed by a processor (such as the processors 210, 212, 214, 216, 218, 252, 260, 428) of a wireless device (such as the wireless devices 120a-120e, 200, 320, 402). The following description relates to the MAC layer and the PHY layer of the wireless device, and operations of both layers are implemented by the processor of the wireless device.

[0151] In determination block 1502, the MAC layer may determine whether a PDCCH addressed to the C-RNTI is received after transmission of a BFR MAC-CE. In various embodiments, a BFR MAC-CE (e.g., 1552) may be sent in any PUSCH, including a new uplink grant requested by a beam failure recovery request of a wireless device delivered in a PUCCH BFR, a semi-statically configured uplink grant, or an uplink grant for transmission of a message to a base station (e.g., Msg 3 or Msg A during a CBRA procedure).

[0152] In response to determining that a PDCCH addressed to the C-RNTI was not received after transmission of the BFR MAC-CE (i.e., determination block 1502 = "No"), in block 1504, the MAC layer may provide an indicator to the PHY layer that the BFR MAC-CE was not successfully sent to the base station.

[0153] In response to determining that a PDCCH addressed to the C-RNTI was received after the transmission of the BFR MAC-CE (i.e., determination block 1502 = "Yes"), the MAC layer may provide an indicator to the PHY layer that the BFR MAC-CE was successfully sent to the base station in block 1506. In some embodiments, the MAC layer may receive the PDCCH addressed to the C-RNTI on a special CORESET or in a dedicated search space dedicated for BFR responses (e.g., Figure 12D In some embodiments, the MAC layer may send a PDCCH message (e.g., 1274, Figure 12D ) receives a PDCCH addressed to the C-RNTI, which schedules a new uplink grant with the same information as that used to send, for example, the four-step CBRA procedure 1250 ( Figure 12B ) in Msg 3 or the two-step CBRA procedure 1260 ( Figure 12C ) in the same Hybrid Automatic Repeat Request (HARQ) ID as in Msg A. In some embodiments, the MAC layer may include the same Hybrid Automatic Repeat Request (HARQ) ID as in the PDCCH message (e.g., 1276, Figure 12D ) receives a PDCCH addressed to the C-RNTI, the message carrying an indicator notifying the wireless device that the BFR MAC-CE transmission is successful.

[0154] In some embodiments, providing an indicator of successful transmission of a BFR MAC-CE from the MAC layer to the PHY layer may trigger the PHY layer to update the beam information. In some embodiments, the PHY layer may perform as described ( Figure 14A ) The operations of blocks 1412 and 1414 are to determine the timing for updating the beam and the PL RS information addressed to the PDCCH of the C-RNTI instead of the PDCCH with the C-RNTI.

[0155] Figure 16 is a component block diagram of a network computing device suitable for various embodiments. Such a network computing device (e.g., base stations 110a-110d, 404) may include at least Figure 16 Components shown in . Reference Figures 1-16 , the network computing device 1600 may generally include a processor 1601 coupled to volatile memory 1602 and a large non-volatile memory such as a disk drive 1608. The network computing device 1600 may also include a peripheral memory access device 1606 coupled to the processor 1601, such as a floppy disk drive, a compact disk (CD), or a digital video disk (DVD) drive. The network computing device 1600 may also include a network access port 1604 (or interface) coupled to the processor 432 for establishing a data connection to a network, such as the Internet or a local area network coupled to other system computers and servers. The network computing device 1600 may include one or more antennas 1607 for sending and receiving electromagnetic radiation, which may be connected to a wireless communication link. The network computing device 1600 may include additional access ports, such as USB, Firewire, Thunderbolt, etc., for coupling to peripherals, external memory, or other devices.

[0156] Figure 17 is a block diagram of components of a wireless device 1700 suitable for use with various embodiments. Figures 1-17 , various embodiments may be implemented on various wireless devices 1700 (e.g., wireless devices 120a-120e, 200, 320, 402), Figure 17An example is shown in the form of a smartphone. The wireless device 1700 may include a first SOC 202 (e.g., a SOC-CPU) coupled to a second SOC 204 (e.g., a 5G-capable SOC). The first SOC 202 and the second SOC 204 may be coupled to internal memory 426, 1716 (e.g., 426), a display 1712, and a speaker 1714. In addition, the wireless device 1700 may include an antenna 1704 for transmitting and receiving electromagnetic radiation, which may be connected to a wireless transceiver 266 coupled to one or more processors in the first SOC 202 or the second SOC 204. The smartphone 1700 also typically includes a menu selection button or rocker switch 1720 for receiving user input.

[0157] The wireless device 1700 may also include a sound coding / decoding (CODEC) circuit 1710 that digitizes sound received from a microphone into data packets suitable for wireless transmission and decodes the received sound data packets to generate an analog signal, which is provided to a speaker to generate sound. The first SOC 202 and the second SOC 204, the wireless transceiver 266, and one or more processors in the CODEC 1710 may include a digital signal processor (DSP) circuit (not separately shown).

[0158] The processors of the network computing device 1600 and the wireless device 1700 may be any programmable microprocessor, microcomputer, or multi-processor chip, or chips thereof that can be configured by software instructions (applications) to perform various functions, including some of the functions described below. In some wireless devices, multiple processors may be provided, such as one processor in the SOC 204 dedicated to wireless communication functions and one processor in the SOC 202 dedicated to running other applications. Software applications may be stored in the memory 1606, 426 before being accessed and loaded into the processor. The processor may include internal memory sufficient to store the application software instructions.

[0159] As used in this application, the terms "component," "module," "system," and the like are intended to include computer-related entities such as, but not limited to, hardware, firmware, a combination of hardware and software, software, or software in operation, that are configured to perform a particular operation or function. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable program, an operating thread, a program, or a computer. For example, both an application running on a wireless device and the wireless device can be referred to as a component. One or more components can reside in a running process or thread, and a component can be located on one processor or core, or distributed between two or more processors or cores. In addition, these components can run from various non-transitory computer-readable media having various instructions or data structures stored thereon. Components can communicate via local or remote processes, function or program calls, electronic signals, data packets, memory reads / writes, and other known network, computer, processor, or process-related communication methods.

[0160] A number of different cellular and mobile communication services and standards are available or anticipated in the future, all of which can be implemented and benefit from the various embodiments. Such services and standards include, for example, the Third Generation Partnership Project (3GPP), Long Term Evolution (LTE) systems, third generation wireless mobile communication technology (3G), fourth generation wireless mobile communication technology (4G), fifth generation wireless mobile communication technology (5G), Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), 3GSM, General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA) systems (e.g., cdmaOne, CDMA1020™), Enhanced Data Rates for GSM Evolution (EDGE), Advanced Mobile Phone System (AMPS), Digital AMPS (IS-136 / TDMA), Evolution-Data Optimized (EV-DO), Digital Enhanced Cordless Telecommunications (DECT), Worldwide Interoperability for Microwave Access (WiMAX), Wireless Local Area Networks (WLAN), Wi-Fi Protected Access I & II (WPA, WPA2), and Integrated Digital Enhanced Network (iDEN). Each of these technologies involves, for example, the transmission and reception of voice, data, signaling, and / or content messages. It should be understood that any reference to terminology and / or technical details related to a single telecommunications standard or technology is for illustrative purposes only and is not intended to limit the scope of the claims to a particular communication system or technology unless specifically stated in the claim language.

[0161] The various embodiments shown and described are provided merely as examples to illustrate various features of the claims. However, the features shown and described with respect to any given embodiment are not necessarily limited to that embodiment and may be used or combined with other embodiments shown and described. Furthermore, the claims are not intended to be limited by any one exemplary embodiment. For example, one or more operations of methods 500-1500 may be substituted for or combined with one or more operations of methods 500-1500.

[0162] The foregoing method descriptions and process flow charts are provided as illustrative examples only and are not intended to require or imply that the operations of the various embodiments must be performed in the order presented. As will be understood by those skilled in the art, the order of operations in the foregoing embodiments may be performed in any order. Words such as "thereafter," "then," and "next" are not intended to limit the order of operations; these words are used to guide the reader through the description of these methods. In addition, any reference to a claim element in the singular, such as the use of the article "a," "an," or "the," should not be construed as limiting the element to the singular.

[0163] The various illustrative logic blocks, modules, components, circuits, and algorithmic operations described in conjunction with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and operations have been generally described above in terms of their functions. Whether such functions are implemented as hardware or software depends on the specific application and the design constraints on the entire system. A skilled person can implement the described functions in different ways for each specific application, but such embodiment decisions should not be interpreted as resulting in a departure from the scope of the claims.

[0164] The hardware used to implement the various illustrative logics, logic blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of receiver smart objects, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration. Alternatively, some operations or methods may be performed by circuits specific to a given function.

[0165] In one or more embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or codes on a non-transitory computer-readable storage medium or a non-transitory processor-readable storage medium. The operations of the methods or algorithms disclosed herein may be embodied in a processor-executable software module or processor-executable instructions that may reside on a non-transitory computer-readable storage medium or a non-transitory processor-readable storage medium. A non-transitory computer-readable medium or a non-transitory processor-readable storage medium may be any storage medium that can be accessed by a computer or processor. As an example and not limitation, such non-transitory computer-readable or processor-readable storage medium may include RAM, ROM, EEPROM, flash memory, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage agents, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. The disks and optical disks used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), hard disks, solid-state drives, floppy disks, and Blu-ray discs, wherein disks typically reproduce data magnetically, while optical discs reproduce data optically with lasers. The above combinations should also be included within the scope of computer-readable media. Furthermore, the operations of a method or algorithm may reside as one or any combination or set of codes and / or instructions on a machine-readable medium and computer-readable media, which may be incorporated into a computer program product.

[0166] The foregoing description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the claims. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of the claims. Therefore, the present disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the following claims and the principles and novel features disclosed herein.

Claims

1. A method for managing beam failure recovery (BFR) performed by one or more processors of a wireless device, comprising: Selecting synchronization signal blocks (SSBs) in beam failure recovery (BFR) procedures based on contention-based random access (CBRA); Determining that the CBRA-based BFR procedures have been completed; as well as, In response to determining that a new candidate beam reference signal identifier (RS ID) is not identified and is not included in a BFR medium access control (MAC-CE) in a message from the wireless device to a base station, updating beam information based on the SSB selected during the CBRA-based BFR procedure.

2. The method according to claim 1, wherein Updating the beam information includes updating one or more control resource sets (CORESETs) and physical downlink shared channels (PDSCHs) of the downlink signal.

3. The method according to claim 1, wherein Updating the beam information includes updating the physical uplink control channel PUCCH, the physical uplink shared channel PUSCH, and the sounding reference signal SRS of the uplink signal.

4. The method according to claim 1, wherein Updating the beam information includes updating a downlink path loss reference signal DL PL RS.

5. The method according to claim 1, wherein Updating the beam information includes resetting one or more power control parameters to default values.

6. The method according to claim 1, wherein Determining that the CBRA-based BFR process has been completed includes: receiving a physical downlink control channel (PDCCH) including a cell radio network temporary identifier (C-RNTI) from a base station; and In response to receiving a PDCCH including the C-RNTI from the base station, it is determined that the CBRA-based BFR procedure has been completed.

7. The method according to claim 1, wherein Determining that the CBRA-based BFR procedure has completed includes receiving a Physical Downlink Control Channel (PDCCH) message delivered on a special CORESET or in a search space dedicated to BFR responses.

8. The method according to claim 1, wherein Updated beam information includes: determining timing for updating beam information; and The beam information is updated according to the determined timing.

9. The method according to claim 8, wherein Determining the timing for updating beam information includes determining the number of symbols before the MAC layer delivers an indication to the physical layer (PHY layer) that a CBRA-based BFR procedure has been successfully completed after receiving the latest physical downlink control channel (PDCCH) with the C-RNTI.

10. The method according to claim 1, wherein Determining that the CBRA-based BFR process has been completed includes: receiving, after transmission of the BFR MAC-CE, a Physical Downlink Control Channel (PDCCH) addressed to a Cell Radio Network Temporary Identifier (C-RNTI) from the base station; and In response to receiving the PDCCH including the C-RNTI from the base station, it is determined that the CBRA-based BFR procedure has been completed.

11. A wireless device comprising: One or more processors configured with processor-executable instructions to perform operations comprising: Selecting synchronization signal blocks (SSBs) in beam failure recovery (BFR) procedures based on contention-based random access (CBRA); Determining that the CBRA-based BFR process has been completed; and, In response to determining that a new candidate beam reference signal identifier (RS ID) is not identified and is not included in a BFR medium access control (MAC-CE) in a message from the wireless device to a base station, updating beam information based on the SSB selected during the CBRA-based BFR procedure.

12. The wireless device of claim 11, wherein: The one or more processors are configured with processor-executable instructions to perform operations such that updating beam information includes updating one or more control resource sets (CORESETs) and physical downlink shared channels (PDSCHs) of downlink signals.

13. The wireless device of claim 11, wherein: The one or more processors are configured with processor-executable instructions to perform operations such that updating beam information includes updating a physical uplink control channel PUCCH, a physical uplink shared channel PUSCH, and a sounding reference signal SRS of an uplink signal.

14. The wireless device of claim 11, wherein: The one or more processors are configured with processor-executable instructions to perform operations such that updating the beam information includes updating a downlink path loss reference signal (DL PL RS).

15. The wireless device of claim 11, wherein The one or more processors are configured with processor-executable instructions to perform operations such that updating beam information includes resetting one or more power control parameters to default values.

16. The wireless device of claim 11, wherein The one or more processors are configured with processor-executable instructions to perform operations such that determining that the CBRA-based BFR program has been completed comprises: receiving a physical downlink control channel (PDCCH) including a cell radio network temporary identifier (C-RNTI) from a base station; and In response to receiving the PDCCH including the C-RNTI from the base station, it is determined that the CBRA-based BFR procedure has been completed.

17. The wireless device of claim 11, wherein: The one or more processors are configured with processor-executable instructions to perform operations such that determining that the CBRA-based BFR procedure has completed includes receiving a Physical Downlink Control Channel (PDCCH) message delivered on a special CORESET or in a search space dedicated to BFR responses.

18. The wireless device of claim 11, wherein: The one or more processors are configured with processor-executable instructions to perform operations such that updating beam information comprises: determining timing for updating beam information; and The beam information is updated according to the determined timing.

19. The wireless device of claim 18, wherein: The one or more processors are configured with processor-executable instructions to perform operations such that determining the timing for updating beam information includes determining the number of symbols after receiving the latest physical downlink control channel (PDCCH) with a cell radio network temporary identifier (C-RNTI) before the MAC layer delivers an indication to the physical layer (PHY layer) that a CBRA-based BFR procedure has been successfully completed.

20. The wireless device of claim 11, wherein The one or more processors are configured with processor-executable instructions to perform operations such that determining that the CBRA-based BFR program has been completed comprises: receiving, after transmission of the BFR MAC-CE, a Physical Downlink Control Channel (PDCCH) addressed to a Cell Radio Network Temporary Identifier (C-RNTI) from the base station; and In response to receiving the PDCCH including the C-RNTI from the base station, it is determined that the CBRA-based BFR procedure has been completed.

21. A non-transitory processor-readable medium having stored thereon processor-executable instructions configured to cause a processing device in a wireless device to perform operations comprising: Selecting synchronization signal blocks (SSBs) in beam failure recovery (BFR) procedures based on contention-based random access (CBRA); Determining that the CBRA-based BFR procedures have been completed; as well as, In response to determining that a new candidate beam reference signal identifier (RS ID) is not identified and is not included in a BFR medium access control (MAC-CE) in a message from the wireless device to a base station, updating beam information based on the SSB selected during the CBRA-based BFR procedure.

22. The non-transitory processor-readable medium of claim 21, wherein: The stored processor-executable instructions are configured to cause one or more processors of the wireless device to perform operations such that updating beam information includes updating one or more control resource sets (CORESETs) and physical downlink shared channels (PDSCHs) of downlink signals.

23. The non-transitory processor-readable medium of claim 21, wherein: The stored processor-executable instructions are configured to cause one or more processors of the wireless device to perform operations such that updating beam information includes updating a physical uplink control channel PUCCH, a physical uplink shared channel PUSCH, and a sounding reference signal SRS of an uplink signal.

24. The non-transitory processor-readable medium of claim 21, wherein: The stored processor-executable instructions are configured to cause one or more processors of the wireless device to perform operations such that updating beam information includes updating a downlink path loss reference signal (DL PL RS).

25. The non-transitory processor-readable medium of claim 21, wherein: The stored processor-executable instructions are configured to cause one or more processors of the wireless device to perform operations such that updating beam information includes resetting one or more power control parameters to default values.

26. The non-transitory processor-readable medium of claim 21, wherein: The stored processor-executable instructions are configured to cause one or more processors of the wireless device to perform operations such that determining that the CBRA-based BFR procedure has completed comprises: receiving a physical downlink control channel (PDCCH) including a cell radio network temporary identifier (C-RNTI) from a base station; and In response to receiving the PDCCH including the C-RNTI from the base station, it is determined that the CBRA-based BFR procedure has been completed.

27. The non-transitory processor-readable medium of claim 21, wherein: The stored processor-executable instructions are configured to cause one or more processors of the wireless device to perform operations such that determining that a CBRA-based BFR procedure has completed includes receiving a Physical Downlink Control Channel (PDCCH) message delivered on a special CORESET or in a search space dedicated to BFR responses.

28. The non-transitory processor-readable medium of claim 21, wherein: The stored processor-executable instructions are configured to cause one or more processors of the wireless device to perform operations such that updating beam information comprises: determining timing for updating beam information; and The beam information is updated according to the determined timing.

29. The non-transitory processor-readable medium of claim 28, wherein: The stored processor-executable instructions are configured to cause one or more processors of the wireless device to perform operations such that determining the timing for updating beam information includes: determining the number of symbols before the MAC layer delivers an indication to the physical layer (PHY layer) that a CBRA-based BFR procedure has been successfully completed after receiving the latest physical downlink control channel (PDCCH) with a cell radio network temporary identifier (C-RNTI).

30. A wireless device comprising: means for selecting a synchronization signal block (SSB) in a beam failure recovery (BFR) procedure based on contention-based random access (CBRA); Components used to determine that the CBRA-based BFR procedures have been completed; as well as, means for updating beam information based on the SSB selected during the CBRA-based BFR procedure in response to determining that a new candidate beam reference signal identifier, RS ID, was not identified and was not included in a BFR medium access control - control element, MAC-CE, in a message from the wireless device to a base station.

Images