Event reporting for beam failure recovery

Abstract

Example embodiments of the present disclosure relate to an apparatus, method, and computer-readable storage medium for event reporting of beam failure recovery. In an example embodiment, if a beam failure of one or more beams is detected, a first device determines a new beam and uses the new beam to perform a first type of random access or a second type of random access to recover the beam failure. In addition, the first device sends at least a first event indication of at least one of the following to the second device: a use event that the first type of random access has been performed to recover the beam failure, and a recovery event that the beam failure is recovered using the first type of random access.

Description

Technical Field

[0001] Example embodiments of the present disclosure relate generally to the field of communications, and in particular to an apparatus, method, and computer-readable storage medium for event reporting of beam failure restoration (BFR). Background Art

[0002] Beam Failure Recovery (BFR) has been developed in New Radio (NR). For example, if a user equipment (UE) detects a beam failure, the UE can trigger BFR by initiating a random access procedure. After the random access procedure is completed, beam failure recovery is considered complete. Therefore, BFR delay may be affected by the random access channel (RACH) configuration.

[0003] RACH configuration has a critical impact on user experience and overall network performance. For example, RACH collision probability and therefore access setup delay, data recovery delay, handover delay, transition delay, and beam failure recovery delay may be affected by RACH configuration. In NR, RACH optimization is required to minimize access delay, imbalance of access delay on uplink (UL) and supplementary uplink (SUL) channels, failed / unnecessary RACH attempts on RACH resources before success, and beam failure recovery delay. Summary of the invention

[0004] In general, example embodiments of the present disclosure provide an apparatus, method, and computer-readable storage medium for event reporting for beam failure restoration (BFR).

[0005] In a first aspect, a first device is provided, the first device comprising at least one processor and at least one memory comprising computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, cause the first device to: determine a new beam based on detection of a beam failure of one or more beams, and perform a first type of random access or a second type of random access using the new beam to recover the beam failure. The first device is also caused to send at least a first event indication of at least one of the following to a second device: a use event that the first type of random access has been performed to recover the beam failure, and a recovery event that the beam failure is recovered using the first type of random access.

[0006] In a second aspect, a second device is provided, the second device comprising at least one processor and at least one memory comprising computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, cause the second device to: receive at least a first event indication of at least one of the following from a first device: a use event that a first type of random access has been performed by the first device to recover a beam failure, and a recovery event that a beam failure is recovered by the first device using the first type of random access; wherein the first device has determined a new beam based on detection of a beam failure of one or more beams, and has performed the first type of random access or the second type of random access using the new beam to recover the beam failure.

[0007] In a third aspect, a method is provided. In the method, if a beam failure for one or more beams is detected, a first device determines a new beam and performs a first type of random access or a second type of random access using the new beam to recover the beam failure. In addition, the first device sends to the second device at least a first event indication of at least one of the following: a use event that the first type of random access has been performed to recover the beam failure, and a recovery event that the beam failure is recovered using the first type of random access.

[0008] In a fourth aspect, a method is provided. In the method, a second device receives from a first device at least a first event indication of at least one of the following: a use event that a first type of random access has been performed by the first device to recover from a beam failure, and a recovery event that the beam failure is recovered by the first device using the first type of random access. The first device has determined a new beam based on detection of a beam failure of one or more beams, and has performed the first type of random access or the second type of random access using the new beam to recover from the beam failure.

[0009] In a fifth aspect, an apparatus is provided, the apparatus comprising means for performing the method according to the third aspect or the fourth aspect.

[0010] In a sixth aspect, a computer-readable storage medium comprising program instructions stored thereon is provided. The instructions, when executed by a processor of a device, cause the device to perform the method according to the third aspect or the fourth aspect.

[0011] It should be understood that the invention summary is not intended to identify the key or essential features of the exemplary embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0013] Figure 1 An example environment in which example embodiments of the present disclosure may be implemented is set forth;

[0014] Figure 2 A flowchart illustrating an example method according to some example embodiments of the present disclosure;

[0015] Figure 3 illustrates an example process of reporting BFR information according to some example embodiments of the present disclosure; and

[0016] Figure 4 A flowchart illustrating an example method according to some other example embodiments of the present disclosure;

[0017] Figure 5 A simplified block diagram of an apparatus suitable for implementing an example embodiment of the present disclosure is shown.

[0018] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0019] The principle of the present disclosure will now be described with reference to some example embodiments. It should be understood that these example embodiments are described only to illustrate and help those skilled in the art understand and implement the present disclosure, and do not represent any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various other ways except the way described below.

[0020] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0021] As used herein, the term "terminal device" or "user equipment" (UE) refers to any terminal device capable of wireless communication with each other or with a base station. Communication may involve the transmission and / or reception of wireless signals using electromagnetic signals, radio waves, infrared signals, and / or other types of signals suitable for transmitting information over the air. In some example embodiments, the UE may be configured to transmit and / or receive information without direct human-computer interaction. For example, when triggered by an internal or external event, or in response to a request from the network side, the UE may transmit information to the base station according to a predetermined schedule.

[0022] Examples of UE include, but are not limited to, smartphones, wireless-enabled tablets, laptop embedded devices (LEEs), laptop mounted devices (LMEs), wireless client equipment (CPEs), sensors, metering devices, personal wearable devices such as watches, and / or vehicles capable of communication. For the purposes of discussion, some example embodiments will be described with reference to UE as an example of a terminal device, and the terms "terminal device" and "user equipment" (UE) may be used interchangeably in the context of the present disclosure. A UE may also correspond to the mobile terminating (MT) portion of an integrated access and backhaul (IAB) node (also referred to as a relay node).

[0023] As used herein, the term "network device" refers to a device via which a service can be provided to a terminal device in a communication network. As an example, a network device may include a base station. As used herein, the term "base station" (BS) refers to a network device via which a service can be provided to a terminal device in a communication network. A base station may include any suitable device via which a terminal device or UE can access a communication network. Examples of base stations include relays, access points (APs), transmission points (TRPs), node Bs (NodeBs or NBs), evolved NodeBs (eNodeBs or eNBs), new radio (NR) NodeBs (gNBs), remote radio modules (RRUs), radio headers (RHs), remote radio heads (RRHs), low power nodes such as femto, micro, etc. A relay node may correspond to a distributed unit (DU) portion of an IAB node.

[0024] As used herein, the term "circuitry" may refer to one or more or all of the following:

[0025] (a) a pure hardware circuit implementation (such as an implementation using only analog and / or digital circuitry), and

[0026] (b) a combination of hardware circuitry and software such as (where applicable):

[0027] (i) a combination of analog and / or digital hardware circuits and software / firmware, and

[0028] (ii) any portion of hardware processor(s) (including digital signal processor(s)) with software, software and memory(s) that work together to enable a device (such as a mobile phone or server) to perform various functions, and

[0029] (c) Hardware circuit(s) and / or processor(s), such as microprocessor(s) or portion(s) of microprocessor(s), which requires software (e.g., firmware)

[0030] The software can be saved when no operation is needed.

[0031] This definition of circuitry applies to all uses of the term in this application, including in any claims. As another example, as used in this application, the term circuitry also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. For example, if applicable to a particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular base station, or other computing or base station.

[0032] As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "including" and its variations should be understood as open terms meaning "including but not limited to." The term "based on" should be understood as "based at least in part on." The terms "one embodiment" and "embodiment" should be understood as "at least one embodiment." The term "another embodiment" should be understood as "at least one other embodiment." Other definitions (explicit and implicit) may be included below.

[0033] As used herein, the terms "first", "second", etc. may be used herein to describe various elements, which should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any one of the listed terms and all combinations of one or more.

[0034] Beam Failure Recovery (BFR) has been specified in Release 15 (Rel-15) using the Random Access (RA) procedure as described in 3rd Generation Partnership Project (3GPP) TS 38.300. A UE may be provided with dedicated RA resources for a specific beam. In this case, the UE may use the RA resources to initiate a Contention Free Random Access (CFRA). Therefore, BFR latency may be affected by RACH settings.

[0035] In NR, RACH optimization is needed to minimize access delay, access delay imbalance on UL and SUL channels, failed / unnecessary RACH attempts on RACH resources before success, and beam failure recovery delay. The inventors note that RACH optimization mainly focuses on the configuration of RACH itself on the cell, but does not consider the configuration for BFR or the configuration of dedicated random access (RA) resources for BFR (or generally the configuration of CFRA for BFR).

[0036] Continuous beam failure will result in radio link failure (RLF). When the UE detects RLF, the UE can report its location as specified in 3GPP TS 38.331. RLF can trigger a Minimization of Drive Test (MDT) report. There are two modes of MDT measurements, including logged MDT measurements and immediate MDT measurements. In Long Term Evolution (LTE), the network uses the LoggedMeasurementConfiguration message to configure logged MDT measurements for UEs in the Radio Resource Control (RRC) connected state. In logged MDT, the UE performs measurements and records them in the report. In the case where immediate MDT is available at the UE, immediate MDT also allows detailed location information reporting. The inventors also noted that the BFR configuration does not take into account the configuration of RLF and / or MDT.

[0037] An exemplary embodiment of the present disclosure proposes a scheme for reporting information about beam failure recovery (BFR). With this scheme, if a device such as a UE detects a beam failure on one or more beams such as one or more serving beams, the device determines a new beam and performs random access on the new beam to recover the beam failure. The random access may be contention-free random access (CFRA) or contention-based random access (CBRA). The device reports a usage event of a certain type of random access (such as CBRA) and / or a recovery event of a beam failure using this type of random access.

[0038] In this way, the network will be able to optimize the configuration of random access resources for BFR based on reports from the device. It will allow the allocation of fewer dedicated resources to the UE to maximize resource usage. The UE has dedicated CFRA resources that it can use at the time of a BFR event, and therefore delays in the BFR process can be reduced.

[0039] Figure 1 An example environment 100 is shown in which example embodiments of the present disclosure may be implemented.

[0040] Environment 100, which may be part of a communication network, includes devices 110 and 120 that communicate with each other. For the purposes of discussion, devices 110 and 120 will be referred to as first device 110 and second device 120, respectively. Figure 2 The number of devices shown is for illustration purposes only and does not imply any limitation. Environment 100 may include any suitable number of devices capable of communicating with each other.

[0041] The first device 110 and the second device 120 may be implemented by any suitable device. For example, one device 110 or 120 may be implemented by a terminal device such as a UE, and the other device 120 or 110 may be implemented by a network device such as a base station. As another example, both the first device 110 and the second device 120 may be implemented by a terminal device.

[0042] Communications in environment 100 may follow any suitable communication standard or protocol already in existence or developed in the future, such as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Advanced LTE (LTE-A), Fifth Generation (5G) New Radio (NR), Wireless Fidelity (Wi-Fi), and Worldwide Interoperability for Microwave Access (WiMAX) standards, and employ any suitable communication technology, including, for example, Multiple Input Multiple Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), Code Division Multiplexing (CDM), Bluetooth, ZigBee, Machine Type Communication (MTC), Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), Ultra-Reliable Low Latency Communication (URLLC), Carrier Aggregation (CA), Dual Connectivity (DC), and New Radio License-Unlicensed (NR-U) technology.

[0043] The first device 110 may communicate with the second device 120 or other devices (not shown) on multiple beams and detect beam failures on the beams. If a beam failure is detected on one or more beams, the first device 110 determines a new beam and performs a random access such as CFRA or CBRA on the new beam to recover the beam failure. According to an example embodiment of the present disclosure, the first device 110 sends an indication of an event in which a certain type of random access has been used to recover a beam failure and / or an event in which a beam failure is recovered using a certain type of random access. Therefore, this can be used by the network to optimize the BFR configuration.

[0044] Figure 2 2 shows a flow chart of an example method 200 according to some example embodiments of the present disclosure. The method 200 may be performed as follows: Figure 1 For the purpose of discussion, reference will be made to Figure 1 Method 200 is described.

[0045] At block 205, the first device 110 detects a beam failure of one or more beams. For purposes of discussion, a beam in which a beam failure is detected is also referred to as a failed beam. The one or more failed beams may include one or more serving beams on which the first device 110 is served.

[0046] Any beam failure detection method may be used, including existing or future developed methods. As an example, the network may provide the first device 110 with a configuration for beam failure detection, which may include reference signals such as synchronization signal blocks (SSBs) or channel station information reference signals (CSI-RS). The first device 110 may monitor the reference signal. If the reference signal received power (RSRP) or reference signal received quality (RSRQ) of the reference signal is lower than, for example, a threshold, a beam failure instance may be determined. If the assumed physical downlink control channel (PDCCH) block error rate (e.g., PDCCH block error rate, BLER) estimated on one or more beams of the serving cell is lower than, for example, a threshold, a beam failure instance may be determined. If the number of beam failure instances reaches a configured threshold before the configured timer expires, the first device 110 may determine that a beam used for communication has failed. Thresholds and timers may also be included in the configuration for beam failure detection provided by the network.

[0047] Upon detecting a beam failure, at block 210, first device 110 determines a new beam to replace one or more failed beams. In some example embodiments, where first device 110 is configured with multiple beams for communication, first device 110 may select a new beam from the multiple beams. The selection of the new beam may be based on a measurement of RSRP or RSRQ at first device 110.

[0048] In some example embodiments, one or more candidate beams (also referred to as candidate beam sets) may be configured for beam failure recovery (BFR). Dedicated random access (RA) resources or contention-free random access (CFRA) resources may be configured for the candidate beam set. RA resources include time resources such as subframes or symbols, frequency resources such as subcarriers or physical resource blocks (PRBs), code resources such as preambles, and the like. In this example, the first device 110 may prioritize selecting a new beam from the candidate beam set. For example, the first device 110 may prioritize selecting a beam from the candidate beam set to further facilitate beam failure recovery. By prioritizing the configured candidate beams, the efficiency of BFR may be improved.

[0049] If the candidate beam set is not available to recover the beam failure, the first device 110 may select a new beam not included in the candidate beam set. For example, if the measurements of RSRP or RSRQ of all candidate beams are very low, such as by comparing with a threshold, the first device 110 may determine that the candidate beam set is not available.

[0050] After the new beam is determined, at block 215, the first device 110 performs random access (RA) using the new beam to recover the beam failure. Any method of RA-based BFR may be employed, including existing or future-developed methods. The scope of the present disclosure shall not be limited in this regard.

[0051] RA is one of two types of random access (referred to as first type of random access and second type of random access, respectively). In some example embodiments, the first type of random access may include CBRA or other random access without dedicated random access resources, and the second type of random access may include CFRA or other random access configured with dedicated random access resources. The first type of random access and the second type of random access may be classified according to any other suitable criteria for BFR.

[0052] The first type of random access or the second type of random access may be selected based on whether the new beam is selected from the candidate beam set configured for BFR. For example, if the new beam is included in the configured candidate beam set, the first device 110 may initiate CFRA using the dedicated RA resources configured for the new beam. If the new beam is not included in the configured candidate beam set, the first device 110 may initiate CBRA for BFR.

[0053] The BFR process may continue until the beam failure is recovered using a beam. For example, if the beam failure cannot be recovered using a new beam, the first device 110 may determine another new beam and initiate a corresponding random access to recover the beam failure. Preferably, one or more continuous new beams may also be selected from a candidate beam set configured with dedicated random access resources for BFR. If the beam failure cannot be recovered using the candidate beam set, the first device 110 may determine an additional new beam that is not included in the candidate beam set. Recovery of the beam failure may be determined based on any suitable criteria. For example, in the case where BFR is based on random access, recovery of the beam failure may be determined after the RA process is completed.

[0054] At block 220, the first device 110 sends an event indication (referred to as a first event indication) to the second device 120 regarding a use event of a certain type of random access (such as a first type of random access) having been performed to recover a beam failure, and / or regarding a recovery event of a beam failure being recovered using a certain type of random access. The event indication may be sent after the beam failure is recovered. Alternatively or additionally, the first device 110 may log or record (multiple) events and report (multiple) events based on a request or instruction from the network, or based on an event or timer trigger.

[0055] For example, if the new beam determined at block 210 is used to initiate a first type of random access (such as CBRA), the first device 110 may record or document a usage event that the first type of random access is performed for BFR. If a beam failure is recovered using a new beam, the first device 110 may record or document a recovery event that the beam failure is recovered using the first type of random access. If another new beam is used to initiate the first type of random access and / or recover the beam failure, the first device 110 may also record or document a usage event that the first type of random access is performed for BFR, and / or a recovery event that the beam failure is recovered using the first type of random access. After the BFR or other trigger is completed, the first device 110 may send an event indication for the usage event and / or the recovery event.

[0056] Through the event indication, the network will optimize the configuration for BFR. For example, in an embodiment where the first type of random access includes CBRA and the second type of random access includes CFRA configured with dedicated random access resources for a specific beam, the network will be able to optimize the configuration of dedicated CFRA resources for BFR based on the CBRA process.

[0057] In addition to the first event indication related to the first type of random access (such as CBRA), in some example embodiments, the first device 110 may send an event indication (referred to as a second event indication) to the second device 220 regarding a usage event that the second type of random access (such as CFRA) has been performed to recover the beam failure. For example, if the second type of random access is performed for BFR, the first device 210 may record the use of the second type of random access. When the beam failure is recovered using the first type of random access (such as CBRA), the first device 210 may send a second event indication to the second device 220 regarding a usage event that the second type of random access is used during the RA process. In this way, in an example embodiment where the first type of random access is not configured with dedicated random access resources and the second type of random access is configured with dedicated random access resources, the network will know that the dedicated RA resources configured for some beams may not be able to recover the beam failure of some service beams, and thus optimize the configuration of the dedicated RA resources for BFR.

[0058] In some example embodiments, the first device 110 may additionally send an indication of a beam, resources (such as time and frequency resources and a preamble), power, and / or location during the second type of random access. For example, when the second type of random access is performed, the first device 110 may record information about at least one of the beam, resources (such as time and frequency resources and a preamble), power, or location, and may report the recorded information upon completion of BFR or certain triggers. In this way, the network is allowed to allocate specific resources that are most likely to be used for BFR. Therefore, fewer dedicated resources can be allocated to the UE to maximize resource usage. In addition, since the UE has dedicated RA resources that may be used during a BFR event, delays in the BFR process can be reduced.

[0059] In some example embodiments, first device 110 may send a beam indication of at least one of one or more failed beams and a beam allowed to recover from a beam failure to second device 120. For discussion purposes, a beam that completes BFR is also referred to as a recovery beam.

[0060] For example, after detecting a beam failure on one or more beams, the first device 110 may record the (multiple) failed beams. After the beam failure is restored using a new beam, the first device 110 may record the new beam as a restored beam. When necessary, the first device 110 may send beam indications of one or more failed beams and restored beams to the second device 120. The association of (multiple) failed beams and restored beams may be used by the network for BFR configuration to improve the efficiency of BFR. For example, in the case where dedicated RA resources are configured for BFR, the network will be able to optimize the configuration of dedicated RA resources for BFR based on the association of (multiple) failed beams and restored beams. For example, the network will know that the candidate beams configured for BFR cannot restore beam failures of certain beams, and therefore configure beams that are more useful to BFR.

[0061] In some example embodiments, the first device 110 may send a location indication of the location of the first device 110 to the second device 120. The location indication may be implemented in any suitable manner. For example, the location indication may indicate a detailed or precise location of the first device 110 detected or determined based on a global navigation satellite system (GNSS) or other positioning system or device. Alternatively or additionally, the location indication may indicate a relative location of the first device 110 based on a measurement of a signal received by a receiver at the first device 110 or sensed by a sensor at the first device 110. Thus, the network may optimize the BFR configuration based on location or in a region.

[0062] Event indications, beam indications, position indications, and other indications may be sent by the first device 110 in any suitable form. For example, the indications may be sent together or jointly in one message, or may be sent separately in different messages. Any suitable message may be used to carry the information. For example, one or more indications may be included in the BFR information carried in the BFR request from the first device 110 to the second device 120. For example, one or more indications may be sent together with RRC signaling.

[0063] Figure 3 An example process 300 for reporting BFR information according to some example embodiments of the present disclosure is shown. In this example, the first device 110 is implemented by a UE 305, and the second device 120 is implemented by a gNB 310. In addition, the first type of random access and the second type of random access are implemented by CBRA and CFRA, respectively.

[0064] UE 305 receives (315) configurations for both beam failure detection and beam failure recovery from gNB 310. In this example, the BFR configuration may include a dedicated CFRA resource configuration for BFR. UE 305 detects (320) a beam failure based on the configuration for beam failure detection. UE 305 records (325) one or more beams in which the failure was detected (which indicates that the beam(s) experienced a beam failure).

[0065] UE 305 performs (330) random access to recover from beam failure. UE 305 records (335) a usage event used by CBRA and / or a recovery event using CBRA to recover from beam failure, and the recovery beam from which the failure was recovered, as BFR information. If multiple CBRAs are performed, UE 305 may record multiple usage events used by CBRA and the associated beams. UE 305 reports (340) the recorded BFR information to gNB 310. In this example, reporting is triggered when CBRA is used during a RA procedure for BFR and BFR is completed using CBRA.

[0066] Figure 4 400 according to some example embodiments of the present disclosure. Figure 1 The first device 120 is shown as being implemented. For the purpose of discussion, reference will be made to Figure 1 Method 400 is described.

[0067] At block 405, second device 120 receives from first device 110 at least a first event indication of at least one of: a use event that a first type of random access has been performed by the first device to recover a beam failure, and a recovery event that a beam failure is recovered by the first device using the first type of random access. First device 110 has determined a new beam based on detection of a beam failure of one or more beams, and has performed the first type of random access or the second type of random access using the new beam to recover the beam failure. In some example embodiments, first device 110 may use the new beam to perform the first type of random access instead of the second type of random access.

[0068] As referenced above Figures 1 to 3 All operations and features described are equally applicable to method 400 and have similar effects. For the sake of simplicity, details will be omitted.

[0069] Figure 5 is a simplified block diagram of a device 500 suitable for implementing an example embodiment of the present disclosure. The device 500 may be configured as follows: Figure 1 The illustrated first device 110 or second device 120 is implemented at or as a part thereof.

[0070] As shown, the device 500 includes a processor 510, a memory 520 coupled to the processor 510, a communication module 530 coupled to the processor 510, and a communication interface (not shown) coupled to the communication module 530. The memory 520 stores at least a program 540. The communication module 530 is used for two-way communication, for example, via multiple antennas. The communication interface can represent any interface required for communication.

[0071] Assume that program 540 includes program instructions that, when executed by associated processor 510, enable device 500 to operate in accordance with example embodiments of the present disclosure, as referred to herein. Figures 1 to 4 The example embodiments herein may be implemented by computer software executable by the processor 510 of the device 500, or by hardware, or by a combination of software and hardware. The processor 510 may be configured to implement various example embodiments of the present disclosure.

[0072] The memory 520 may be of any type suitable for the local technology network and may be implemented using any suitable data storage technology, such as, as non-limiting examples, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 520 is shown in the device 500, there may be several physically different memory modules in the device 500. The processor 510 may be of any type suitable for the local technology network and, as non-limiting examples, may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 500 may have multiple processors, such as a dedicated integrated circuit chip that is time-slave to a clock synchronized with a main processor.

[0073] When the device 500 acts as the first device 110, the processor 510 may implement the above-mentioned Figures 1 to 3 When the device 500 acts as the second device 120, the processor 510 may implement the method 200 and the process 300 described above. Figure 4 The method 400 described above is as described in Figures 1 to 4 All operations and features described are equally applicable to the device 500 and have similar effects. For the sake of simplicity, the details will be omitted.

[0074] Generally, various example embodiments of the present disclosure may be implemented using hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented using hardware, while other aspects may be implemented using firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the example embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented using hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.

[0075] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer executable instructions, such as instructions included in a program module, which are executed in a device on a target real or virtual processor to perform the above referenced Figures 1 to 4Method 200 and process 300 and method 400 described. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functions of program modules can be combined or split between program modules as needed. The machine executable instructions of program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in both local and remote storage media.

[0076] The program code for executing the disclosed method can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code is implemented when executed by the processor or controller in the flow chart and / or the block diagram. The program code can be executed completely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.

[0077] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform various processes and operations as described above. Examples of carriers include signals and computer-readable media.

[0078] The computer readable medium can be a computer readable signal medium or a computer readable storage medium. The computer readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. More specific examples of computer readable storage media will include electrical connections with one or more wires, portable computer floppy disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), digital versatile disks (DVD), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0079] In addition, although operations are described in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown or in sequence or performing all of the operations shown to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to a particular example embodiment. Certain features described in the context of a separate example embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple example embodiments individually or in any suitable sub-combination.

[0080] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Instead, the specific features and acts described above are disclosed as example forms of implementing the claims.

[0081] Various example embodiments of the technology have been described. In addition to or in lieu of the above, the following embodiments are described. Features described in any of the following examples may be used with any other examples described herein.

[0082] In some aspects, a first device includes: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the first device to: determine a new beam based on detection of a beam failure of one or more beams; perform a first type of random access or a second type of random access using the new beam to recover the beam failure; and send at least a first event indication of at least one of the following to a second device: a usage event in which the first type of random access has been performed to recover the beam failure, and a recovery event in which the beam failure is recovered using the first type of random access.

[0083] In some example embodiments, the first type of random access comprises contention-based random access and the second type of random access comprises contention-free random access.

[0084] In some example embodiments, the first device is caused to perform the first type of random access or the second type of random access in the following manner: if the new beam is included in a candidate beam set configured with random access resources dedicated to beam failure recovery, the second type of random access is performed using the new beam to recover the beam failure.

[0085] In some example embodiments, the first device is caused to perform the first type of random access or the second type of random access in the following manner: if the new beam is not included in a set of candidate beams configured with random access resources dedicated to beam failure recovery, then using the new beam to perform the first type of random access to recover the beam failure.

[0086] In some example embodiments, the first device is caused to determine a new beam by: determining whether a candidate beam set can be used to recover a beam failure; and determining a new beam not included in the candidate beam set based on determining that the candidate beam set is not available to recover the beam failure.

[0087] In some example embodiments, the first device is further caused to: determine another new beam based on determining that the beam failure is not recovered using the new beam, and use the another new beam to perform the first type of random access or the second type of random access to recover the beam failure.

[0088] In some example embodiments, the first device is further caused to: based on performing the first type of random access to recover from the beam failure, record a usage event that the first type of random access has been performed to recover from the beam failure.

[0089] In some example embodiments, the first device is further caused to: based on determining that the beam failure is recovered using the first type of random access, record a recovery event that the beam failure is recovered using the first type of random access.

[0090] In some example embodiments, the first device is caused to send at least the first event indication by sending at least the first event indication and a second event indication that a second type of random access has been performed to recover from a use event of a beam failure to a second device.

[0091] In some example embodiments, the first device is caused to send at least a first event indication and a second event indication by sending the first event indication and the second event indication to the second device, as well as an indication of at least one of a beam, a resource, or a power used by the first device during a second type of random access.

[0092] In some example embodiments, the first device is caused to send at least the first event indication by sending the first event indication and a beam indication of at least one of one or more beams and a beam allowing recovery from a beam failure to the second device.

[0093] In some example embodiments, the first device is further caused to: record the one or more beams.

[0094] In some example embodiments, the first device is caused to send at least the first event indication by sending the first event indication and a location indication of the location of the first device to the second device.

[0095] In some aspects, a second device includes: at least one processor; and at least one memory, including computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the second device to: receive at least a first event indication of at least one of the following from a first device: a usage event in which a first type of random access has been performed by the first device to recover a beam failure, and a recovery event in which the beam failure is recovered by the first device using the first type of random access; wherein the first device has determined a new beam based on detection of a beam failure of one or more beams, and has performed the first type of random access or the second type of random access using the new beam to recover the beam failure.

[0096] In some aspects, a method includes: determining, by a first device, a new beam based on detection of a beam failure of one or more beams; performing, by the first device, a first type of random access or a second type of random access to recover from the beam failure using the new beam; and sending, by the first device to a second device, at least a first event indication of at least one of the following: a usage event in which the first type of random access has been performed to recover from the beam failure, and a recovery event in which the beam failure is recovered using the first type of random access.

[0097] In some example embodiments, the first type of random access comprises contention-based random access and the second type of random access comprises contention-free random access.

[0098] In some example embodiments, performing the first type of random access or the second type of random access includes: if the new beam is included in a candidate beam set configured with random access resources dedicated to beam failure recovery, performing the second type of random access by the first device using the new beam to recover the beam failure.

[0099] In some example embodiments, performing the first type of random access or the second type of random access includes: if the new beam is not included in a candidate beam set configured with random access resources dedicated to beam failure recovery, performing the first type of random access by the first device using the new beam to recover the beam failure.

[0100] In some example embodiments, determining a new beam includes: determining, by the first device, whether a candidate beam set can be used to recover a beam failure; and determining, by the first device, a new beam that is not included in the candidate beam set based on determining that the candidate beam set is not available to recover the beam failure.

[0101] In some example embodiments, the method further includes: determining, by the first device, another new beam based on determining that the beam failure is not recovered using the new beam, and performing the first type of random access or the second type of random access using the other new beam to recover the beam failure.

[0102] In some example embodiments, the method further comprises: in accordance with performing the first type of random access to recover from the beam failure, recording, by the first device, a usage event that the first type of random access has been performed to recover from the beam failure.

[0103] In some example embodiments, the method further comprises: based on determining that the beam failure is recovered using the first type of random access, recording, by the first device, a recovery event that the beam failure is recovered using the first type of random access.

[0104] In some example embodiments, sending at least the first event indication comprises sending, by the first device to the second device, at least the first event indication and a second event indication that a second type of random access has been performed to recover from a use event of a beam failure.

[0105] In some example embodiments, sending at least a first event indication and a second event indication includes sending, by the first device to the second device, the first event indication and the second event indication, and an indication of at least one of a beam, a resource, or a power used by the first device during the second type of random access.

[0106] In some example embodiments, sending at least the first event indication comprises sending, by the first device to the second device, the first event indication and a beam indication of at least one of the one or more beams and a beam allowing recovery from a beam failure.

[0107] In some example embodiments, the method further comprises recording, by the first device, the one or more beams.

[0108] In some example embodiments, sending at least the first event indication comprises sending, by the first device to the second device, the first event indication and a location indication of the location of the first device.

[0109] In some aspects, a method includes: receiving, by a second device, from a first device, at least a first event indication of at least one of the following: a usage event in which a first type of random access has been performed by the first device to recover from a beam failure, and a recovery event in which the beam failure is recovered by the first device using the first type of random access; wherein the first device has determined a new beam based on detection of a beam failure of one or more beams, and has performed the first type of random access or the second type of random access using the new beam to recover from the beam failure.

[0110] In some aspects, an apparatus includes: a component for determining, by a first device, a new beam based on detection of a beam failure of one or more beams; a component for performing, by the first device, a first type of random access or a second type of random access to recover from the beam failure using the new beam; and a component for sending, by the first device, at least a first event indication of at least one of the following: a usage event in which the first type of random access has been performed to recover from the beam failure, and a recovery event in which the beam failure is recovered using the first type of random access.

[0111] In some example embodiments, the first type of random access comprises contention-based random access and the second type of random access comprises contention-free random access.

[0112] In some example embodiments, the component for performing the first type of random access or the second type of random access includes: a component for performing the second type of random access to recover a beam failure by the first device using the new beam if the new beam is included in a set of candidate beams configured with random access resources dedicated to beam failure recovery.

[0113] In some example embodiments, the component for performing the first type of random access or the second type of random access includes: a component for performing the first type of random access to recover a beam failure by the first device using a new beam if the new beam is not included in a set of candidate beams configured with random access resources dedicated to beam failure recovery.

[0114] In some example embodiments, the component for determining a new beam includes: a component for determining, by the first device, whether a candidate beam set can be used to recover a beam failure; and a component for determining, by the first device, a new beam that is not included in the candidate beam set based on determining that the candidate beam set is not available to recover the beam failure.

[0115] In some example embodiments, the apparatus further comprises: a component for determining, by the first device, an additional new beam based on determining that the beam failure is not recovered using the new beam, and using the additional new beam to perform the first type of random access or the second type of random access to recover the beam failure.

[0116] In some example embodiments, the apparatus further comprises means for recording, by the first device, a usage event that the first type of random access has been performed to recover from the beam failure in response to performing the first type of random access to recover from the beam failure.

[0117] In some example embodiments, the apparatus further comprises means for recording, by the first device, a recovery event that the beam failure is recovered using the first type of random access in response to determining that the beam failure is recovered using the first type of random access.

[0118] In some example embodiments, means for sending at least the first event indication includes means for sending, by the first device to the second device, at least the first event indication and a second event indication of an event that a second type of random access has been performed to recover from a use event of a beam failure.

[0119] In some example embodiments, the components for sending at least a first event indication and a second event indication include: components for sending the first event indication and the second event indication by the first device to the second device, and an indication of at least one of a beam, a resource, or a power used by the first device during a second type of random access.

[0120] In some example embodiments, means for sending at least a first event indication includes means for sending, by a first device to a second device, the first event indication and a beam indication of at least one of one or more beams and a beam allowing recovery from a beam failure.

[0121] In some example embodiments, the apparatus further comprises means for recording, by the first device, the one or more beams.

[0122] In some example embodiments, means for sending at least the first event indication comprises means for sending, by the first device to the second device, the first event indication and a location indication of the location of the first device.

[0123] In some aspects, an apparatus includes: a component for receiving, by a second device, at least a first event indication of at least one of the following from a first device: a usage event in which a first type of random access has been performed by the first device to recover from a beam failure, and a recovery event in which the beam failure is recovered by the first device using the first type of random access; wherein the first device has determined a new beam based on detection of a beam failure of one or more beams, and has performed the first type of random access or the second type of random access using the new beam to recover from the beam failure.

[0124] In some aspects, a computer-readable storage medium includes program instructions stored thereon, which, when executed by a processor of a device, cause the device to perform methods according to some example embodiments of the present disclosure.

Claims

1. A first device, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the first device to: determining a new beam based on detection of a beam failure of one or more beams, wherein the one or more beams experiencing the beam failure are recorded as one or more failed beams; performing a first type or a second type of random access using the new beam to recover from the beam failure; In response to unsuccessful recovery of the beam failure using the new beam, determining another new beam; In response to the another new beam not being included in the candidate beam set configured with random access resources dedicated to beam failure recovery, performing a first type of random access using the another new beam to recover the beam failure; In response to the another new beam being included in the candidate beam set configured with random access resources dedicated to beam failure recovery, performing a second type of random access using the another new beam to recover the beam failure; In response to successfully restoring the beam failure using the another new beam, recording the another new beam as a restored beam; Sending a report to a second device, the report indicating the one or more associated failure beams and the recovery beam, the report further indicating a use event of a random access type used to recover the beam failure, and a recovery event of a random access type used to recover the beam failure, wherein the use event indicates that the first type of random access and / or the second type of random access has been performed, and the recovery event indicates that the beam failure is recovered through the first type of random access or the second type of random access; as well as receiving an optimized configuration for beam failure recovery from the second device, wherein the second device optimizes the configuration for beam failure recovery based on the report to obtain the optimized configuration. 2 . The first device of claim 1 , wherein the first type of random access comprises contention-based random access, and the second type of random access comprises contention-free random access. 3 . The first device of claim 2 , wherein the second type of random access comprises contention-free random access configured with dedicated random access resources for a specific beam.

4. The first device of claim 1 , wherein the first device is configured to determine the new beam by: determining whether the candidate beam set can be used to recover the beam failure; and Based on determining that the candidate beam set is not available for recovering the beam failure, determining the new beam that is not included in the candidate beam set.

5. The first device of claim 1 , wherein the first device is caused to perform a first type or a second type of random access using the new beam to recover from the beam failure by: In response to the new beam not being included in the candidate beam set configured with random access resources dedicated to beam failure recovery, performing a first type of random access using the new beam to recover the beam failure; In response to the new beam being included in the candidate beam set configured with random access resources dedicated to beam failure recovery, a second type of random access is performed using the new beam to recover from the beam failure.

6. The first device according to claim 1, wherein the first device is further configured to: According to performing the first type of random access using the new beam or the another new beam to recover the beam failure, recording the use event that the first type of random access has been performed to recover the beam failure; According to performing the second type of random access using the new beam or the another new beam to recover the beam failure, the use event that the second type of random access has been performed to recover the beam failure is recorded.

7. The first device according to claim 1, wherein the first device is further configured to: According to determining that the beam failure is recovered by using the first type of random access, recording the recovery event that the beam failure is recovered by using the first type of random access; or According to determining that the beam failure is recovered by using the second type of random access, recording the recovery event that the beam failure is recovered by using the second type of random access.

8. The first device of claim 1, wherein the report further comprises: An indication of at least one of a beam, a resource, or a power used by the first device during the second type of random access.

9. The first device according to claim 1, wherein the first device is further caused to: In response to successfully recovering the beam failure using the new beam, the new beam is recorded as a recovery beam without determining the another new beam.

10. The first device of claim 1, wherein the report further comprises: A location indication of the location of the first device.

11. A second device, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the second device to: receiving a report from a first device, the report indicating one or more associated failed beams and a restored beam, the report further indicating a use event of a random access type used to restore the beam failure, and a restore event of a random access type used to restore the beam failure, wherein the use event indicates that a first type of random access and / or a second type of random access has been performed, wherein the restore event indicates that the beam failure is restored by the first type of random access or the second type of random access; optimizing a configuration for beam failure recovery based on the report to obtain an optimized configuration for beam failure recovery; as well as sending the optimized configuration for beam failure recovery to the first device, The first device has performed the first type of random access or the second type of random access using the recovery beam to successfully recover from the beam failure based on detection of the beam failure of one or more beams.

12. A method for communication, comprising: determining, by the first device, a new beam based on detection of a beam failure of one or more beams, wherein the one or more beams having the beam failure are recorded as one or more failed beams; performing, by the first device, a first type or a second type of random access using the new beam to recover from the beam failure; determining, by the first device, another new beam in response to unsuccessful recovery of the beam failure using the new beam; In response to the another new beam not being included in a candidate beam set configured with random access resources dedicated to beam failure recovery, the first device performs a first type of random access using the another new beam to recover the beam failure; In response to the another new beam being included in the candidate beam set configured with random access resources dedicated to beam failure recovery, the first device performs a second type of random access using the another new beam to recover the beam failure; In response to successfully recovering the beam failure by using the another new beam, the first device records the another new beam as a recovery beam; The first device sends a report to the second device, the report indicating the one or more associated failure beams and the recovery beam, the report further indicating a use event of a random access type used to recover the beam failure, and a recovery event of a random access type used to recover the beam failure, wherein the use event indicates that the first type of random access and / or the second type of random access has been performed, and the recovery event indicates that the beam failure is recovered through the first type of random access or the second type of random access; as well as An optimized configuration for beam failure recovery is received by the first device from the second device, wherein the second device optimizes the configuration for beam failure recovery based on the report to obtain the optimized configuration.

13. The method of claim 12, wherein the first type of random access comprises contention-based random access, and the second type of random access comprises contention-free random access.

14. The method of claim 13, wherein the second type of random access comprises contention-free random access configured with dedicated random access resources for a specific beam.

15. The method of claim 12, wherein determining the new beam comprises: Determining, by the first device, whether the candidate beam set can be used to recover the beam failure; as well as Based on determining that the candidate beam set is not available for recovering the beam failure, the first device determines the new beam that is not included in the candidate beam set.

16. The method of claim 12, wherein performing, by the first device, a first type or a second type of random access using the new beam to recover from the beam failure comprises: In response to the new beam not being included in the candidate beam set configured with random access resources dedicated to beam failure recovery, the first device performs a first type of random access using the new beam to recover the beam failure; In response to the new beam being included in the candidate beam set configured with random access resources dedicated to beam failure recovery, the first device performs a second type of random access using the new beam to recover from the beam failure.

17. The method according to claim 12, further comprising: According to performing the first type of random access using the new beam or the another new beam to recover the beam failure, recording, by the first device, the usage event that the first type of random access has been performed to recover the beam failure; According to performing the second type of random access using the new beam or the another new beam to recover the beam failure, the use event that the second type of random access has been performed to recover the beam failure is recorded by the first device.

18. The method according to claim 12, further comprising: According to determining that the beam failure is recovered by using the first type of random access, recording, by the first device, the recovery event that the beam failure is recovered by using the first type of random access; or According to determining that the beam failure is recovered using the second type of random access, the first device records the recovery event that the beam failure is recovered using the second type of random access.

19. The method of claim 12, wherein the report further comprises: An indication of at least one of a beam, a resource, or a power used by the first device during the second type of random access.

20. The method of claim 12, further comprising: In response to successfully recovering the beam failure using the new beam, the first device records the new beam as a recovery beam without determining the another new beam.

21. The method of claim 12, wherein the report further comprises: A location indication of the location of the first device.

22. A method for communication, comprising: Receiving, by the second device, a report from the first device, the report indicating one or more associated failed beams and a restored beam, the report further indicating a use event of a random access type for recovering the beam failure, and a recovery event of a random access type for recovering the beam failure, wherein the use event indicates that a first type of random access and / or a second type of random access has been performed, wherein the recovery event indicates that the beam failure is recovered by the first type of random access or the second type of random access; optimizing, by the second device, a configuration for beam failure recovery based on the report to obtain an optimized configuration for beam failure recovery; as well as sending, by the second device, the optimized configuration for beam failure recovery to the first device, The first device has performed the first type of random access or the second type of random access using the recovery beam to successfully recover from the beam failure based on detection of the beam failure of one or more beams.

23. An apparatus for communication, comprising: means for determining, by the first device, a new beam based on detection of a beam failure of one or more beams, wherein the one or more beams experiencing the beam failure are recorded as one or more failed beams; means for performing, by the first device, a first type or a second type of random access using the new beam to recover from the beam failure; means for determining, by the first device, in response to unsuccessful recovery of the beam failure using the new beam, another new beam; means for performing, by the first device, a first type of random access using the other new beam to recover the beam failure in response to the other new beam not being included in a set of candidate beams configured with random access resources dedicated to beam failure recovery; means for performing, by the first device, a second type of random access using the other new beam to recover the beam failure in response to the other new beam being included in the candidate beam set configured with random access resources dedicated to beam failure recovery; means for recording, by the first device, the another new beam as a restored beam in response to successfully restoring the beam failure using the another new beam; means for sending a report by the first device to a second device, the report indicating the one or more associated failed beams and the restored beam, the report further indicating a use event of a random access type for recovering the beam failure and a restore event of a random access type for recovering the beam failure, wherein the use event indicates that the first type of random access and / or the second type of random access has been performed, wherein the restore event indicates that the beam failure is restored by the first type of random access or the second type of random access; as well as means for receiving, by the first device, an optimized configuration for beam failure recovery from the second device, wherein the second device optimizes the configuration for beam failure recovery based on the report to obtain the optimized configuration.

24. An apparatus for communication, comprising: means for receiving, by the second device, a report from the first device, the report indicating one or more associated failed beams and a restored beam, the report further indicating a usage event of a random access type used to restore the beam failure, and a restoration event of a random access type used to restore the beam failure, wherein the usage event indicates that a first type of random access and / or a second type of random access has been performed, wherein the restoration event indicates that the beam failure is restored by the first type of random access or the second type of random access; means for optimizing, by the second device, a configuration for beam failure recovery based on the report to obtain an optimized configuration for beam failure recovery; as well as means for transmitting, by the second device to the first device, the optimized configuration for beam failure recovery, The first device has performed the first type of random access or the second type of random access using the recovery beam to successfully recover from the beam failure based on detection of the beam failure of one or more beams.

25. A computer-readable storage medium comprising program instructions stored thereon, which instructions, when executed by a processor of a device, cause the device to perform the method of any one of claims 12 to 21.

26. A computer-readable storage medium comprising program instructions stored thereon, which instructions, when executed by a processor of a device, cause the device to perform the method of claim 22.

Images