Electronic devices and methods for wireless communication, computer-readable storage medium

Abstract

The present disclosure provides an electronic device, a method and a computer readable storage medium for wireless communication, the electronic device comprising: processing circuitry configured to: obtain, from a base station, configuration information for beam failure recovery of a user equipment in multi-transmission and reception point (TRP) communication, wherein the configuration information comprises a first configuration and / or a second configuration, the first configuration is used for determination of a beam failure event for each of a plurality of TRPs, and the second configuration is used for joint determination of a beam failure event for the plurality of TRPs; and report a beam failure event to the base station based on the configuration information.

Description

[0001] This application claims priority to Chinese Patent Application No. 202010392038.3, filed on May 11, 2020, entitled "Electronic Device and Method for Wireless Communication, Computer-Readable Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication technology, and more specifically to a beam failure recovery mechanism. More specifically, it relates to an electronic device and method for wireless communication, as well as a computer-readable storage medium. Background Technology

[0003] In the Beam Failure Recovery (BFR) procedure in Rel-15, a set of periodic Channel State Information Reference Signal (CSI-RS) resource indices for beam failure detection is defined. gather It can contain at most two reference signal index values. Furthermore, a consensus has been reached in the beam failure detection process that when the set... When the Block Error Rate (BLER) value corresponding to all Beam Failure Detecting Reference Signals (BFD-RS) exceeds a threshold, the UE will determine that a beam failure event has occurred. Since the BFR procedure in Rel-15 is for a single Transceiving and Receiving Point (TRP) scenario, although the set... It contains two BFD-RS, but in reality, the directions of the two beams corresponding to the reference signal are usually the same. When one beam fails, the other beam will also fail.

[0004] However, when considering a multi-TRP scenario, since the multiple TRPs are located in different places, their reference signals correspond to different beam directions. It's possible that one TRP might experience beam failure while the others function normally. Therefore, different beamforming strategies should be applied for multi-TRP scenarios. Summary of the Invention

[0005] A brief overview of the invention is given below to provide a basic understanding of certain aspects of it. It should be understood that this overview is not an exhaustive summary of the invention. It is not intended to identify key or essential parts of the invention, nor is it intended to limit the scope of the invention. Its purpose is merely to present certain concepts in a simplified form as a prelude to the more detailed description that follows.

[0006] According to one aspect of this application, an electronic device for wireless communication is provided, comprising: a processing circuit configured to: obtain configuration information from a base station for beam failure recovery of a user equipment in multiple transmit and receive point (TRP) communication, wherein the configuration information includes a first configuration and / or a second configuration, the first configuration being used for determining beam failure events for each of a plurality of TRPs, and the second configuration being used for jointly determining beam failure events for a plurality of TRPs; and reporting beam failure events to the base station based on the configuration information.

[0007] According to one aspect of this application, a method for wireless communication is provided, comprising: obtaining from a base station configuration information for beam failure recovery of a user equipment in multi-TRP communication, wherein the configuration information includes a first configuration and / or a second configuration, the first configuration being used for determining beam failure events for each of the multiple TRPs, and the second configuration being used for jointly determining beam failure events for the multiple TRPs; and reporting beam failure events to the base station based on the configuration information.

[0008] According to another aspect of this application, an electronic device for wireless communication is provided, comprising: a processing circuit configured to: send configuration information to a user equipment for beam failure recovery of the user equipment in multi-TRP communication, wherein the configuration information includes a first configuration and / or a second configuration, the first configuration being used for determining beam failure events for each of the multiple TRPs, and the second configuration being used for jointly determining beam failure events for the multiple TRPs; and obtaining, from the user equipment, a report of beam failure events by the user equipment based on the configuration information.

[0009] According to another aspect of this application, a method for wireless communication is provided, comprising: sending configuration information to a user equipment for beam failure recovery in multi-TRP communication, wherein the configuration information includes a first configuration and / or a second configuration, the first configuration being used for determining beam failure events for each of the multiple TRPs, and the second configuration being used for jointly determining beam failure events for the multiple TRPs; and obtaining, from the user equipment, a report of beam failure events by the user equipment based on the configuration information.

[0010] The electronic device and method of this application propose criteria for beam failure determination and a beam failure event notification mechanism for multi-TRP scenarios, which can better ensure the reliability of transmission and reduce latency in multi-TRP scenarios.

[0011] According to other aspects of the present invention, computer program code and computer program product for implementing the above-described method for wireless communication, as well as a computer-readable storage medium having the computer program code for implementing the above-described method for wireless communication recorded thereon, are also provided.

[0012] These and other advantages of the invention will become more apparent from the following detailed description of preferred embodiments of the invention in conjunction with the accompanying drawings. Attached Figure Description

[0013] To further illustrate the above and other advantages and features of the present invention, specific embodiments of the present invention will be described in further detail below with reference to the accompanying drawings. These drawings, together with the following detailed description, are included in and form a part of this specification. Elements having the same function and structure are indicated by the same reference numerals. It should be understood that these drawings only depict typical examples of the invention and should not be construed as limiting the scope of the invention. In the drawings:

[0014] Figure 1 A functional block diagram of an electronic device for wireless communication according to an embodiment of this application is shown;

[0015] Figure 2a and Figure 2b An example of beam failure in a multi-TRP scenario is shown;

[0016] Figure 3 A functional block diagram of an electronic device for wireless communication according to an embodiment of this application is shown;

[0017] Figure 4 An example of how the detected BLER changes over time is shown;

[0018] Figure 5 Another example of the detected BLER changing over time is shown;

[0019] Figure 6 Another example of the detected BLER changing over time is shown;

[0020] Figure 7 A functional block diagram of an electronic device for wireless communication according to another embodiment of this application is shown;

[0021] Figure 8 This illustrates an example of the information flow between a base station and a user equipment.

[0022] Figure 9 A flowchart of a method for wireless communication according to an embodiment of this application is shown;

[0023] Figure 10 A flowchart of a method for wireless communication according to another embodiment of this application is shown;

[0024] Figure 11 This is a block diagram illustrating a first example of a schematic configuration of an eNB or gNB to which the technologies of this disclosure can be applied;

[0025] Figure 12 This is a block diagram illustrating a second example of a schematic configuration of an eNB or gNB to which the technologies of this disclosure can be applied;

[0026] Figure 13 This is a block diagram illustrating an example of a schematic configuration of a smartphone to which the technologies of this disclosure can be applied;

[0027] Figure 14 This is a block diagram illustrating an example of a schematic configuration of a car navigation device to which the technology of this disclosure can be applied; and

[0028] Figure 15 This is a block diagram of an exemplary structure of a general-purpose personal computer in which methods and / or apparatus and / or systems according to embodiments of the present invention can be implemented. Detailed Implementation

[0029] Exemplary embodiments of the invention will be described below with reference to the accompanying drawings. For clarity and brevity, not all features of actual implementations are described in the specification. However, it should be understood that many implementation-specific decisions must be made in the development of any such actual embodiment to achieve the developer's specific goals, such as complying with constraints related to the system and business, and these constraints may vary depending on the implementation. Furthermore, it should be understood that while development work can be very complex and time-consuming, such development work is merely a routine task for those skilled in the art who benefit from this disclosure.

[0030] It should also be noted that, in order to avoid obscuring the invention with unnecessary details, only the device structure and / or processing steps closely related to the solution according to the invention are shown in the accompanying drawings, while other details that are not closely related to the invention are omitted.

[0031] <First Embodiment>

[0032] Figure 1A functional block diagram of an electronic device 100 for wireless communication according to an embodiment of this application is shown, such as... Figure 1 As shown, the electronic device 100 includes: an acquisition unit 101 configured to acquire configuration information of the beam failure event (BFR) of the user equipment (UE) in multi-TRP communication from a base station, wherein the configuration information includes a first configuration and / or a second configuration, the first configuration being used for determining the beam failure event of each of the multiple TRPs, and the second configuration being used for the joint determination of the beam failure events of the multiple TRPs; and a reporting unit 102 configured to report the beam failure event to the base station based on the configuration information.

[0033] The acquisition unit 101 and the reporting unit 102 can be implemented by one or more processing circuits, such as chips. Furthermore, it should be understood that... Figure 1 The functional units in the device shown are logical modules divided according to the specific functions they implement, rather than being used to restrict the specific implementation method.

[0034] Electronic device 100 may be located on the user equipment (UE) side or communicatively connected to the UE. It should also be noted that electronic device 100 may be implemented at the chip level or at the device level. For example, electronic device 100 may function as the user equipment itself and may also include external devices such as memory and transceivers (not shown). Memory may be used to store programs and related data information that the user equipment needs to execute to perform various functions. Transceivers may include one or more communication interfaces to support communication with different devices (e.g., base stations, other user equipment, etc.), and there is no specific limitation on the implementation of the transceiver. This also applies to the subsequent description of other configuration examples of electronic devices on the user equipment side.

[0035] Furthermore, it should be noted that the terms "first," "second," ... in this article are for distinction purposes only and do not imply any order.

[0036] The BFR mechanism executed on the UE side may include several stages, such as beam failure determination, candidate beam identification, beam failure recovery request (BFRQ) transmission, and beam failure recovery request response (BFRR) acquisition. Specifically, in the beam failure determination stage, the UE checks the beam quality of the current serving beam to determine if the beam failure triggering conditions are met; for example, it can compare the BLER of the serving beam with a BLER threshold to determine if beam failure has occurred. In the candidate beam identification stage, candidate beams that can be used as replacements for the current serving beam are selected from other beams. In the BFRQ transmission stage, the BFRQ is transmitted to the base station (e.g., gNB). In the BFRR acquisition stage, the UE monitors the BFRR response from the base station within a specific time window.

[0037] As mentioned earlier, in a multi-TRP scenario, there may be a situation where one TRP experiences beam failure while the other TRPs function normally. Figure 2a and Figure 2b An example of beam failure in a multi-TRP scenario is shown. Figure 2a Only TRP0 experienced beam failure, while Figure 2b Beam failures occurred in both TRP0 and TRP1.

[0038] Under existing BFR mechanisms, the UE will not report a beam failure event to the base station if only one TRP experiences beam failure. However, in multi-TRP scenarios, failure to perform beam failure recovery may impact UE performance. Furthermore, since multiple TRPs perform joint transmission, there may be situations where multiple TRPs experience beam failure but the UE's transmission performance remains acceptable. To provide a BFR mechanism suitable for multi-TRP scenarios, this embodiment provides a first configuration and a second configuration to perform beam failure determination for each TRP and a joint beam failure determination for multiple TRPs, respectively.

[0039] The acquisition unit 101 acquires a first configuration and / or a second configuration from the base station. For example, the acquisition unit 101 may acquire configuration information via Radio Resource Control (RRC) signaling.

[0040] The following will describe examples of the first and second configurations. Figure 3 As shown, the electronic device 100 further includes a determination unit 103, configured to determine a beam failure event based on configuration information. The determination unit 103 may also be implemented as a processing circuit, for example.

[0041] For example, the first configuration includes one or more of the following: a BLER threshold for each TRP, a first counter for counting the number of physical layer beam failures for each TRP, and a first maximum count threshold for the first counter. The determination unit 103 is configured, in response to the first configuration, to increment the first counter of a TRP by 1 when a physical layer beam failure occurs in one of the plurality of TRPs, and to determine that a beam failure event has occurred in the TRP when the count value of the first counter reaches the first maximum count threshold. The reporting unit 102 then reports the beam failure event to the base station. For example, when the BLER of a TRP is higher than the BLER threshold of that TRP, the determination unit 103 determines that a physical layer beam failure has occurred in that TRP, i.e., an instance of a beam failure event has been generated, and the UE reports the beam failure event to its higher layers. For example, the determination unit 103 can detect the BLER of the beam failure detection reference signal (BFD-RS) configured for each TRP as the BLER of the TRP. This detection can be periodic.

[0042] As can be seen, according to the first configuration, when a beam failure event occurs in some TRPs, it will be reported and the BFR procedure will be triggered. Therefore, the failed beam can be recovered as soon as possible, ensuring the reliability of transmission. If the determination unit 103 determines that more than one TRP has experienced a beam failure event, the reporting unit 102 reports the beam failure events of these more than one TRP to the base station respectively. The reporting of beam failure events for different TRPs is independent of each other.

[0043] For ease of understanding, the following description uses a scenario with two TRPs (TRP0 and TRP1) as an example, where each TRP is configured with a reference signal (i.e., corresponding to a beam). In this example, BLER thresholds BLER0 and BLER1 are configured for TRP0 and TRP1 respectively. For example, if at a certain moment the BLER of TRP0 is detected to be greater than BLER0, a physical layer beam failure event is considered to have occurred. The first counter of TRP0 is started and incremented by 1. Subsequently, each time the BLER of TRP0 is detected to be greater than BLER0, the first counter of TRP0 is incremented by 1. Similarly, if at a certain moment the BLER of TRP1 is detected to be greater than BLER1, a physical layer beam failure event is considered to have occurred. The first counter of TRP1 is started and incremented by 1. Subsequently, each time the BLER of TRP1 is detected to be greater than BLER1, the first counter of TRP1 is incremented by 1. The first counters of TRP0 and TRP1 count independently, and a beam failure event is considered to have occurred for the corresponding TRP when the count of the corresponding first counter exceeds a first maximum count threshold.

[0044] The BLER thresholds for each TRP can be the same or different. The first maximum count thresholds for the first counters of each TRP can also be the same or different. These can all be configured by the base station.

[0045] It should be understood that, according to existing standards, two reference signals are configured in a BFD-RS set. In a multi-TRP scenario, one reference signal can be configured for each TRP (as described in the example above). However, this application is not limited to this and can also be applied to situations where a TRP is configured with multiple reference signals. In such cases, for example, when all beams corresponding to the reference signals of a TRP experience a physical layer beam failure event, the TRP is determined to have experienced a physical layer beam failure event. Specifically, a first counter is still set for each TRP. When the BLER values ​​of the beams corresponding to all the reference signals of a TRP are greater than the corresponding BLER threshold, the TRP is considered to have experienced a physical layer beam failure event, and the first counter of the TRP is incremented by 1. If only the BLER values ​​of the beams corresponding to some of the reference signals exceed the corresponding BLER threshold, the first counter of the TRP is not incremented by 1. Furthermore, when the first counter of a TRP reaches a first maximum counting threshold, the TRP is considered to have experienced a beam failure event.

[0046] Alternatively, a first counter can be set for each beam of each TRP. Furthermore, for multiple beams within a TRP, the same BLER threshold can be configured, or different BLER thresholds can be configured. A beam failure event is considered to have occurred when the first counter of a beam reaches a first maximum count threshold, and a beam failure event is considered to have occurred for the TRP when the first counters of all beams within a TRP reach the first maximum count threshold.

[0047] Of course, the relationship between beam failure events of individual beams of a TRP and the beam failure event of the TRP can also be defined in another way. For example, the BLER of all reference signals of a TRP can be averaged, and this average BLER can be used as the BLER of the TRP to determine whether a beam failure event has occurred in the TRP.

[0048] On the other hand, for example, the second configuration may include one or more of the following: a weighting parameter for calculating the joint BLER of multiple TRPs, a threshold for the joint BLER, a second counter for counting the number of joint physical layer beam failures of multiple TRPs, and a second maximum count threshold for the second counter. The determination unit 103 is configured, in response to the second configuration, to increment the second counter by 1 when a joint physical layer beam failure event occurs in multiple TRPs, and to determine that a joint beam failure event has occurred in multiple TRPs when the count value of the second counter reaches the second maximum count threshold. The reporting unit 102 then reports the joint beam failure event to the base station. For example, when the joint BLER of multiple TRPs is higher than the joint BLER threshold, the determination unit 103 determines that a joint physical layer beam failure has occurred in multiple TRPs, i.e., an instance of a joint beam failure event is generated. The UE reports this instance of the joint beam failure event to its upper layer.

[0049] When the number of instances of joint beam failure events exceeds the second maximum counting threshold, the determination unit 103 determines that a joint beam failure event has occurred in the corresponding TRP. The reporting unit 102 reports to the base station to trigger the BFR procedure.

[0050] According to the second configuration, beam failure events are determined based on the joint BLER of multiple TRPs. Since the UE's performance is determined by the joint transmission performance of multiple TRPs in a multi-TRP scenario, beam failure determination based on joint BLER can accurately reflect the degradation of UE performance and improve reliability.

[0051] For example, decision unit 103 can perform a weighted summation of the BLER of each of the multiple TRPs based on the weighting parameters, and use the result as the joint BLER. The weighting parameters are set for each TRP and can be constants in the range of 0 to 1, with the sum of all weighting parameters being 1.

[0052] For ease of understanding, we will still use the scenario of two TRPs (TRP0 and TRP1) as an example, where each TRP is configured with a reference signal (i.e., corresponding to a beam). In such an example, the joint BLER is obtained by weighted summation of the BLERs of the two TRPs, with the weighting parameters obtained from the second configuration. For example, the joint BLER can be calculated using the following equation (1).

[0053] BLER joint =w0BLER0+w1BLER1 (1)

[0054] Where BLER0 is the BLER of TRP0, BLER1 is the BLER of TRP1, and w0 and w1 are the weighting parameters corresponding to TRP0 and TRP1, respectively. jointThe calculated joint BLER. When BLER joint If the value exceeds the joint BLER threshold, a joint physical layer beam failure event is considered to have occurred, i.e., an instance of a joint beam failure event has been generated. The second counter counts the number of such instances, and when the count value reaches the second maximum count threshold, the determination unit 103 determines that a joint beam failure event has occurred.

[0055] Similarly, this embodiment can also be applied to situations where a TRP is configured with multiple reference signals. In such cases, for example, for multiple beams of a TRP, weighting parameters are set separately, and the BLERs of all beams across all TRPs are weighted and summed. When the final BLER exceeds the joint BLER threshold, a joint physical layer beam failure event is considered to have occurred, i.e., an instance of a joint beam failure event has been generated. Of course, the same weighting parameters can also be set for multiple beams of the same TRP; this is not a limitation.

[0056] The UE can operate with one of the first configuration and the second configuration, or it can operate by combining the first configuration and the second configuration. In the former case, the acquisition unit 101 can acquire information about only one of the first configuration and the second configuration from the base station.

[0057] In the latter case, i.e., when both the first configuration and the second configuration are configured simultaneously, the acquisition unit 101 can acquire information from both the first configuration and the second configuration. In other words, the acquisition unit 101 can acquire one or more of the following: a first counter for counting the number of physical layer beam failures for each TRP, a first maximum count threshold of the first counter, a weighting parameter for calculating the joint BLER of multiple TRPs, a threshold for the joint BLER, a second counter for counting the number of joint physical layer beam failures for multiple TRPs, and a second maximum count threshold of the second counter.

[0058] The determination unit 103 can be configured to perform the following operations in response to a first configuration and a second configuration: when a physical layer beam failure occurs in one of a plurality of TRPs, increment a first counter of that TRP by 1; when a joint physical layer beam failure occurs in a plurality of TRPs, increment a second counter by 1; and when the count value of any one of the plurality of first counters first reaches a first maximum count threshold, determine that a beam failure event has occurred in the TRP corresponding to that first counter and report it to the base station; and when the count value of the second counter first reaches a second maximum count threshold, determine that a joint beam failure event has occurred in a plurality of TRPs and report it to the base station. For example, when the BLER of one of the plurality of TRPs is higher than the BLER threshold, it is considered that the TRP has experienced a physical layer beam failure; when the joint BLER of a plurality of TRPs is higher than the joint BLER threshold, it is considered that a joint physical layer beam failure has occurred in a plurality of TRPs.

[0059] As can be seen, in this scenario, a second counter and multiple first counters are used to count instances of joint beam failure and instances of beam failure for each individual TRP, respectively. When any counter reaches its threshold, the corresponding beam failure event is reported to the base station. That is, regardless of whether a beam failure event occurs for an individual TRP or a joint beam failure event, the reporting unit 102 sends a report to the base station to trigger the BFR procedure. This further improves transmission reliability and reduces latency.

[0060] The following description continues using a scenario with two TRPs (TRP0 and TRP1) as an example, where each TRP is configured with a reference signal (i.e., corresponding to a beam). Two first counters and one second counter are configured to count instances of beam failure events for TRP0 and TRP1, and instances of joint beam failure events, respectively. These three counters operate independently and are denoted as Counter_0, Counter_1, and Counter_m below, with corresponding maximum counting thresholds of MaxCount_Num_0, MaxCount_Num_1, and MaxCount_Num_m.

[0061] Figure 4 An example of how detected BLERs change over time is shown. The horizontal axis represents time, and the vertical axis represents detected BLERs. Dashed lines represent the BLER of TRP0 (BLER0), solid lines represent the BLER of TRP1 (BLER1), and dotted lines represent the joint BLER (BLER...). joint The vertical axis represents the joint BLER threshold, and BLER_s represents the BLER threshold for TRP0 and TRP1. In this example, the BLER thresholds for the two TRPs are the same, but this is not restrictive and they can be different.

[0062] like Figure 4 As shown, since the detected BLER does not exceed its corresponding threshold, the three counters do not start counting, the determination unit 103 will not determine that a beam failure event has occurred, and therefore the BFR process will not be triggered.

[0063] Figure 5 Another example of the detected BLER changing over time is shown. The coordinates and the meanings of the curves are as follows: Figure 4 The same points mentioned above will not be repeated here. Figure 5 As shown, at point A, the detected BLER0 exceeds the threshold BLER_s, therefore TRP0 experiences a physical layer beam failure, and counter Counter_0 starts and increments by 1. At point B, assuming the counter Counter_0's count reaches its first maximum count threshold MaxCount_Num_0 (Count_Num_0 in the figure represents the current value of counter Counter_0), a beam failure event is determined to have occurred in TRP0, triggering the BFR procedure. Therefore, in Figure 5 In the example, to ensure transmission reliability, the UE will restore the TRP where beam failure occurred as soon as possible, regardless of the joint transmission performance.

[0064] Figure 6 Another example of the detected BLER changing over time is shown. The coordinates and the meanings of the curves are as follows: Figure 4 The same points mentioned above will not be repeated here. Figure 6 As shown, at point A, the joint BLER is detected to exceed the threshold BLER_m, indicating a joint physical layer beamforming failure. The counter Counter_m is then started and incremented by 1. At point B, assuming the counter Counter_m reaches the second maximum count threshold MaxCount_Num_m, a joint beamforming failure event is confirmed, triggering the BFR procedure. Note that in... Figure 6 In the example, it is assumed that the counter Counter_m corresponding to multiple TRPs reaches its maximum count threshold before the counters Counter_0 and Counter_1 corresponding to a single TRP. Therefore, in Figure 6 In the example, when the joint transmission performance is poor, the UE will execute the BFR procedure as soon as possible, regardless of the performance of the individual TRP, to ensure the reliability of the transmission.

[0065] In 5G communication, three main transmission scenario types are defined: enhanced mobile bandwidth (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mTTC). eMBB provides high-bandwidth mobile services, while URLLC provides low-latency, highly reliable services. For example, in multi-TRP scenarios, for eMBB, different TRPs can transmit different transport blocks to improve transmission rates; for URLLC, different TRPs can transmit the same transport blocks to reduce transmission latency and increase reliability.

[0066] Therefore, for eMBB, since different TRPs transmit different transport blocks, it is desirable to recover the failed beam as quickly as possible even when partial beam failure occurs; for example, the first configuration can be used. For URLLC scenarios, since different TRPs transmit the same transport blocks, the need for BFR can be determined based on the joint transmission performance of multiple TRPs. Furthermore, if a TRP experiences a beam failure event, BFR is executed immediately, further improving transmission reliability; therefore, the second configuration or a combination of the first and second configurations can be used.

[0067] In other words, the beam failure recovery configuration adopted by the UE can be determined based on the transmission scenario type. In one example, the base station determines the transmission scenario type and provides the corresponding beam failure recovery configuration to the UE according to that transmission scenario type. For example, in the eMBB scenario, the base station provides the UE with a first configuration, that is, the configuration information obtained by the acquisition unit 101 includes the first configuration; in the URLLC scenario, the base station provides the UE with a first configuration and a second configuration, that is, the configuration information obtained by the acquisition unit 101 includes the first configuration and the second configuration; in the URLLC scenario, the base station provides the UE with a second configuration, that is, the configuration information obtained by the acquisition unit 101 includes the second configuration, and so on.

[0068] In another example, the configuration information also includes information indicating the transmission scenario type, which includes either eMBB or URLLC. The determination unit 103 is configured to determine, based on the indicated transmission scenario type, whether to report a beam failure event based on a first configuration and / or a second configuration. Similarly, for example, in an eMBB scenario, beam failure events are reported based on the first configuration; in a URLLC scenario, beam failure events are reported based on the second configuration or a combination of both.

[0069] As mentioned earlier, the BFR procedure also includes the identification of new candidate beams and the transmission of BFRQs. This embodiment proposes a new method for transmitting BFRQs in a multi-TPR scenario.

[0070] For example, reporting unit 102 is configured to report beam failure events to the base station via a Link Recovery Request (LRR). An LRR is a special physical layer message carried by the Physical Uplink Control Channel (PUCCH) and used by the UE to request an uplink grant (ULgrant) from the network side so that the UE can send a Physical Uplink Shared Channel (PUSCH). Therefore, an LRR is a message that can be triggered by the UE at any time, and reporting beam failure events via LRR ensures timely reporting.

[0071] In one example, the LRR can have a specific sequence format to indicate that a beam failure event has occurred. This specific sequence format can be, for example, an all-zero sequence or an all-one sequence. In this case, the reporting unit 102 is also configured to send information about the TRP indicating the beam failure event and the candidate beams of the TRP that caused the beam failure event to the base station via the MAC CE. That is, the transmission of the BFRQ includes two steps: first, transmitting the specific sequence LRR indicating the occurrence of the beam failure event; and second, transmitting the MAC CE indicating the relevant TRP and the corresponding candidate beams. The MAC CE is, for example, carried on the PUSCH resource.

[0072] The control resource set pool index (CORESETPoolIndex) can be used to indicate the TRP that experienced a beam failure event. CORESETPoolIndex is a concept proposed for multi-TRP scenarios, configured on the control resource set to distinguish different TRPs with the same cell ID. In multi-TRP scenarios, the Scell ​​index reported in the second step of the BFRQ process in Rel-16 is unnecessary; therefore, these bits can be reused to send the CORESETPoolIndex of the TRP that experienced a beam failure event.

[0073] For example, in the event of a joint beam failure, the reporting unit 102 may first send a special sequence of all 0s or all 1s to the base station, and then send the information of the two CORESETPoolIndex corresponding to TRP0 and TRP1 and their respective candidate beams to the base station.

[0074] In another example, the LRR may include information indicating the TRP where a beam failure event occurred. For example, the CORESETPoolIndex could be used to indicate the TRP where a beam failure event occurred. The reporting unit 102 is also configured to send information about the candidate beams of the TRP where the beam failure event occurred to the base station via the MAC CE.

[0075] As can be seen, in this example, the transmission of BFRQ also includes two steps: first, information indicating the TRP where a beam failure event has occurred (LRR); and second, information about the candidate beams of the TRP involved (MAC CE). Specifically, the information indicating the TRP where a beam failure event has occurred is transmitted via PUCCH, and the information about the candidate beams is transmitted via PUSCH.

[0076] For example, if only TRP0 experiences a beam failure event, the reporting unit 102 first transmits the CORESETPoolIndex (e.g., 0) corresponding to TRP0 to the base station in the LRR, and then transmits the candidate beam information of TRP0 to the base station in the MAC CE.

[0077] In summary, the electronic device 100 according to this embodiment provides criteria for beam failure determination and a beam failure event notification mechanism for multi-TRP scenarios, which can better ensure the reliability of transmission and reduce latency in multi-TRP scenarios.

[0078] <Second Embodiment>

[0079] Figure 7 A functional block diagram of an electronic device 200 according to another embodiment of this application is shown, such as Figure 7 As shown, the electronic device 200 includes: a transmitting unit 201 configured to transmit configuration information to the UE for beam failure recovery in multi-TRP communication, wherein the configuration information includes a first configuration and / or a second configuration, the first configuration being used for determining beam failure events for each of the multiple TRPs, and the second configuration being used for jointly determining beam failure events for the multiple TRPs; and an acquiring unit 202 configured to acquire from the UE the UE's reporting of beam failure events based on the configuration information.

[0080] The sending unit 201 and the acquiring unit 202 can be implemented by one or more processing circuits, such as chips. Furthermore, it should be understood that... Figure 7 The functional units in the device shown are logical modules divided according to the specific functions they implement, rather than being used to restrict the specific implementation method.

[0081] Electronic device 200 may be disposed on the base station side or communicatively connected to the base station. It should also be noted that electronic device 200 may be implemented at the chip level or at the device level. For example, electronic device 200 may function as the base station itself and may also include external devices such as memory and transceivers (not shown). The memory may be used to store programs and related data information that the base station needs to execute to perform various functions. The transceiver may include one or more communication interfaces to support communication with different devices (e.g., user equipment, other base stations, etc.), and the specific implementation of the transceiver is not limited here.

[0082] As mentioned earlier, in multi-TRP scenarios, there exists a situation where one TRP experiences beam failure while the others function normally. According to the existing BFR mechanism, the UE will not report a beam failure event to the base station if only one TRP experiences beam failure. However, in multi-TRP scenarios, failure to perform beam failure recovery may impact UE performance. Furthermore, since multiple TRPs perform joint transmission, it is possible for multiple TRPs to experience beam failure while the UE's transmission performance remains acceptable. Therefore, for multi-TRP scenarios, a first configuration and a second configuration are provided to perform beam failure determination for each TRP and a joint beam failure determination for multiple TRPs, respectively.

[0083] The sending unit 201 sends a first configuration and / or a second configuration to the UE. For example, the sending unit 201 may send this information via RRC signaling so that the UE can determine the beam failure event and trigger the BFR procedure based on the first configuration and / or the second configuration.

[0084] For example, the first configuration includes one or more of the following: a BLER threshold for each TRP, a first counter for counting the number of physical layer beam failures for each TRP, and a first maximum count threshold for the first counter. For example, the BLER thresholds for each TRP may be the same or different, and the first maximum count thresholds for the first counters for each TRP may be the same or different.

[0085] According to the first configuration, the UE performs beam failure event determination and reporting for each TRP, thereby enabling partial beam failure recovery. The specific operations on the UE side have been described in detail in the first embodiment and will not be repeated here.

[0086] For example, if a beam failure event occurs at more than one TRP, the acquisition unit 202 acquires reports of beam failure events for more than one TRP from the UE. The reporting of beam failure events for different TRPs is independent of each other.

[0087] It should be understood that in a TRP configured with multiple reference signals, a physical layer beam failure event is determined to have occurred if all beams corresponding to the reference signals of that TRP experience physical layer beam failure. Specifically, a first counter is still set for each TRP. When the BLER values ​​of all beams corresponding to the reference signals of a TRP are greater than the corresponding BLER threshold, the TRP is considered to have experienced a physical layer beam failure event, and the first counter of that TRP is incremented by 1. If only the BLER values ​​of the beams corresponding to some reference signals exceed the corresponding BLER threshold, the first counter of the TRP is not incremented by 1. Furthermore, when the first counter of a TRP reaches a first maximum counting threshold, the TRP is considered to have experienced a beam failure event.

[0088] Furthermore, as described in the first embodiment, a first counter can be set for each beam of each TRP, and for multiple beams of a TRP, the same BLER threshold can be configured, or different BLER thresholds can be configured. For example, when all beams of a TRP experience beam failure events, the TRP is considered to have experienced a beam failure event. Alternatively, the relationship between the beam failure events of each beam of a TRP and the beam failure event of the TRP can be defined in another way. For example, the UE can average the BLER of the beams corresponding to all reference signals of a TRP and use the average BLER as the BLER of the TRP to determine whether a beam failure event has occurred in the TRP.

[0089] On the other hand, for example, the second configuration may include one or more of the following: a weighting parameter for calculating the joint BLER of multiple TRPs, a threshold for the joint BLER, a second counter for counting the number of joint physical layer beam failures of multiple TRPs, and a second maximum count threshold for the second counter.

[0090] According to the second configuration, the UE determines beam failure events based on the joint BLER of multiple TRPs. Since the UE's performance is determined by the joint transmission performance of multiple TRPs in a multi-TRP scenario, beam failure determination based on joint BLER can accurately reflect the degradation of UE performance and improve reliability.

[0091] Similarly, for a TRP configured with multiple reference signals, weighting parameters for the BLER of the beam corresponding to each reference signal can be set separately. The UE performs a weighted sum of the BLERs of all beams across all TRPs. When the final BLER exceeds the joint BLER threshold, a joint physical layer beam failure event is considered to have occurred, i.e., an instance of a joint beam failure event has been generated.

[0092] For example, the base station can configure the UE to operate in one of the first configuration and the second configuration, or it can configure the UE to operate in a combination of the first configuration and the second configuration.

[0093] In one example, the base station can determine the transmission scenario type and provide the UE with a corresponding beam failure recovery configuration based on that transmission scenario type, i.e., providing one of a first configuration and a second configuration, or both. For example, in an eMBB scenario, the base station provides the UE with a first configuration, i.e., the configuration information sent by the transmitting unit 201 includes the first configuration; in an URLLC scenario, the base station provides the UE with both a first and a second configuration, i.e., the configuration information sent by the transmitting unit 201 includes both the first and the second configuration; in an URLLC scenario, the base station provides the UE with a second configuration, i.e., the configuration information sent by the transmitting unit 201 includes the second configuration, and so on.

[0094] In another example, the configuration information also includes information indicating the transmission scenario type, which includes either eMBB or URLLC. The UE determines the configuration to use based on this transmission scenario type information.

[0095] Furthermore, the acquisition unit 202 is configured to acquire the UE's report via LRR. In one example, the LRR may have a specific sequence format to indicate that a beam failure event has occurred. This specific sequence format may be, for example, an all-zero sequence or an all-one sequence. In this case, the acquisition unit 202 is also configured to acquire information about the TRP indicating the beam failure event and the candidate beams of the TRP that caused the beam failure event from the UE via the MAC CE.

[0096] The CORESETPoolIndex can be used to indicate the TRP where a beam failure event occurred. For example, in the case of a joint beam failure, the acquisition unit 202 first receives a special sequence of all 0s or all 1s from the UE, and then receives the two CORESETPoolIndex corresponding to TRP0 and TRP1 and the information of their respective candidate beams.

[0097] In another example, the LRR may include information indicating the TRP where a beam failure event occurred. For example, the CORESETPoolIndex could be used to indicate the TRP where a beam failure event occurred. The acquisition unit 202 is also configured to acquire candidate beam information of the TRP where the beam failure event occurred from the UE via the MAC CE. Here, the LRR is carried on the PUCCH, and the MAC CE is carried on the PUSCH.

[0098] For example, in the case where only TRP0 experiences a beam failure event, the acquisition unit 202 first obtains the CORESETPoolIndex (e.g., 0) corresponding to TRP0 carried in the LRR from the UE, and then obtains the candidate beam information of TRP0 carried on the MAC CE.

[0099] In summary, the electronic device 200 according to this embodiment provides a criterion for beam failure determination and a beam failure event notification mechanism for multi-TRP scenarios, which can better ensure the reliability of transmission and reduce latency in multi-TRP scenarios.

[0100] For ease of understanding, Figure 8 The information flow of the BFR mechanism between the base station (gNodeB) and user equipment (UE) in a multi-TRP scenario is illustrated. For example... Figure 8 As shown, firstly, the gNB sends configuration information for BFR to the base station via RRC signaling, for example. This configuration information may include the aforementioned first configuration and / or second configuration, specifically, various BLER threshold parameters, counters, counter threshold parameters, etc. Furthermore, the configuration information may also include information indicating the transmission scenario type. Next, the UE performs beam quality detection and beam failure event determination, for example, according to the corresponding configuration indicated by the configuration information. When a beam failure event (a beam failure event of a single TRP or a joint beam failure event) is determined to have occurred, the UE sends an LRR to the base station on the PUCCH. The LRR can be used to indicate that a beam failure event has occurred, for example, by sending a special sequence of all 0s or all 1s. The LRR can also be used to send information about the TRP where the beam failure event occurred, such as the corresponding CORESETPoolIndex. After receiving the LRR, the gNB sends an uplink grant to the UE. Based on this uplink grant, the UE sends a MAC CE to the base station on the corresponding PUSCH resource. The MAC CE may include information about the candidate beams of the TRP where the beam failure event occurred. In cases where LRR includes a special sequence, MAC CE may also include information about the TRP where a beam failure event occurred, such as the corresponding CORESETPoolIndex.

[0101] It should be noted that Figure 8 The information flow described is merely illustrative and does not constitute a limitation on this application.

[0102] <Third Embodiment>

[0103] In the process of describing the electronic device for wireless communication in the above embodiments, some processes or methods have obviously been disclosed. Hereinafter, without repeating some details already discussed above, a summary of these methods is given. However, it should be noted that although these methods are disclosed in the description of the electronic device for wireless communication, they do not necessarily employ or are performed by the components described. For example, the embodiments of the electronic device for wireless communication may be implemented partially or entirely using hardware and / or firmware, while the methods for wireless communication discussed below may be implemented entirely by computer-executable programs, although these methods may also employ the hardware and / or firmware of the electronic device for wireless communication.

[0104] Figure 9 A flowchart of a method for wireless communication according to an embodiment of this application is shown. The method includes: obtaining configuration information from a base station for beam failure recovery of a UE in multi-TRP communication (S11), wherein the configuration information includes a first configuration and / or a second configuration, the first configuration being used for determining beam failure events for each of the plurality of TRPs, and the second configuration being used for jointly determining beam failure events for the plurality of TRPs; and reporting beam failure events to the base station based on the configuration information (S12). This method can be performed, for example, on the UE side.

[0105] For example, the configuration information may also include information indicating the transmission scenario type, which may include one of enhanced mobile bandwidth and ultra-reliable low-latency communication. The method described above may also include, for example, determining, based on the indicated transmission scenario type, to report beam failure events based on a first configuration and / or a second configuration.

[0106] In addition, although not shown in the figure, the above method also includes the step of determining the occurrence of a beam failure event based on a first configuration and / or a second configuration.

[0107] For example, the first configuration may include one or more of the following: a BLER threshold for each TRP, a first counter for counting the number of physical layer beam failures for each TRP, and a first maximum count threshold for the first counter. The BLER thresholds for each TRP may be the same or different, and / or the first maximum count thresholds for the first counters for each TRP may be the same or different. For example, the BLER of the beam failure detection reference signal configured for each TRP can be used as the BLER of that TRP.

[0108] The method includes: in response to a first configuration, when a physical layer beam failure event occurs in one of a plurality of TRPs, incrementing the first counter of that TRP by 1, and when the count value of the first counter reaches the first maximum count threshold, determining that a beam failure event has occurred in that TRP and reporting it to the base station in step S12. Wherein, if more than one TRP is determined to have experienced a beam failure event, the beam failure events of more than one TRP are reported to the base station respectively.

[0109] For example, the second configuration includes one or more of the following: weighting parameters for calculating the joint BLER of multiple TRPs, a joint BLER threshold, a second counter for counting the number of joint physical layer beam failures of the multiple TRPs, and a second maximum count threshold for the second counter. For example, the BLER of each of the multiple TRPs can be weighted and summed according to the weighting parameters, and the result can be used as the joint BLER. Exemplarily, the weighting parameters are set for each TRP and are constants in the range of 0 to 1, and the sum of all weighting parameters is 1.

[0110] The above method includes: in response to the second configuration, when a joint physical layer beam failure event occurs in multiple TRPs, incrementing a second counter by 1, and when the count value of the second counter reaches a second maximum count threshold, determining that a joint beam failure event has occurred in multiple TRPs and reporting it to the base station in step S12.

[0111] Furthermore, the first configuration and the second configuration can also be used in combination. The above method includes: in response to the first configuration and the second configuration, when a physical layer beam failure event occurs in one of the plurality of TRPs, incrementing the first counter of that TRP by 1; when a joint physical layer beam failure event occurs in the plurality of TRPs, incrementing the second counter by 1; and when the count value of any one of the plurality of first counters first reaches a first maximum count threshold, determining that the TRP corresponding to the first counter has experienced a beam failure event and reporting it to the base station, and when the count value of the second counter first reaches a second maximum count threshold, determining that a joint beam failure event has occurred in the plurality of TRPs and reporting it to the base station.

[0112] For example, in step S12, the beam failure event can be reported to the base station via LRR.

[0113] In one example, the LRR may have a specific sequence format to indicate that a beam failure event has occurred. Step S12 may also include sending information about the TRP indicating the beam failure event and the candidate beam information of the TRP that caused the beam failure event to the base station via the MAC CE.

[0114] in,

[0115] In another example, the LRR includes information indicating the TRP where a beam failure event occurred. Similarly, the CORESETPoolIndex can be used to indicate the TRP where a beam failure event occurred. Step S12 also includes sending candidate beam information for the TRP where the beam failure event occurred to the base station via the MAC CE.

[0116] Figure 10 A flowchart of a method for wireless communication according to another embodiment of this application is shown. The method includes: sending configuration information for beam failure recovery of the UE in multi-TRP communication (S21), wherein the configuration information includes a first configuration and / or a second configuration, the first configuration being used for determining beam failure events for each of the multiple TRPs, and the second configuration being used for jointly determining beam failure events for the multiple TRPs; and obtaining from the UE a report of beam failure events based on the configuration information (S22). This method can be performed, for example, at the base station side.

[0117] For example, the configuration information may also include information indicating the type of transmission scenario, which may include one of enhanced mobile bandwidth and ultra-reliable low latency communication.

[0118] Similarly, the first configuration may include one or more of the following: a block error rate (BLER) threshold for each TRP, a first counter for counting the number of physical layer beam failures for each TRP, and a first maximum count threshold for the first counter. The BLER thresholds for each TRP may be the same or different, and / or the first maximum count thresholds for the first counters for each TRP may be the same or different.

[0119] In the event of a beam failure event occurring in more than one TRP, obtain reports of beam failure events for more than one TRP from the UE.

[0120] The second configuration may include one or more of the following: a weighting parameter for calculating the joint BLER of multiple TRPs, a joint BLER threshold, a second counter for counting the number of joint physical layer beam failures of multiple TRPs, and a second maximum count threshold for the second counter.

[0121] In step S22, the reported signal can be obtained via the LRR. In one example, the LRR has a specific sequence format to indicate that a beam failure event has occurred. Step S22 also includes obtaining information about the TRP indicating the beam failure event and candidate beam information of the TRP from the UE via the MAC CE. The TRP experiencing the beam failure event can be indicated using the CORESETPoolIndex. In another example, the LRR may include information about the TRP indicating the beam failure event, such as the CORESETPoolIndex of the TRP experiencing the beam failure event. Step S22 also includes obtaining information about candidate beams of the TRP experiencing the beam failure event from the UE via the MAC CE.

[0122] Note that the above methods can be used in combination or individually, and the details have been described in detail in the first and second embodiments, and will not be repeated here.

[0123] The technology disclosed herein can be applied to a variety of products.

[0124] For example, electronic device 200 can be implemented as various base stations. A base station can be implemented as any type of evolved NodeB (eNB) or gNB (5G base station). eNBs include, for example, macro eNBs and small eNBs. A small eNB can be an eNB covering a cell smaller than a macro cell, such as a pico eNB, micro eNB, and femtocell eNB. A similar situation can occur with gNBs. Alternatively, a base station can be implemented as any other type of base station, such as a NodeB and a Base Transceiver Station (BTS). A base station can include: a subject configured to control wireless communication (also called base station equipment); and one or more remote radio heads (RRHs) located in a different location from the subject. Furthermore, various types of user equipment can operate as base stations by temporarily or semi-persistently performing base station functions.

[0125] Electronic device 100 can be implemented as various user devices. User devices can be implemented as mobile terminals (such as smartphones, tablet PCs, laptop PCs, portable gaming terminals, portable / dongle-type mobile routers, and digital camera devices) or in-vehicle terminals (such as car navigation devices). User devices can also be implemented as terminals performing machine-to-machine (M2M) communication (also known as machine-type communication (MTC) terminals). Furthermore, user devices can be wireless communication modules (such as integrated circuit modules comprising a single chip) installed on each of the aforementioned terminals.

[0126] [Application examples of base stations]

[0127] (First application example)

[0128] Figure 11 This is a block diagram illustrating a first example of a schematic configuration of an eNB or gNB to which the technologies of this disclosure can be applied. Note that the following description uses an eNB as an example, but it can also be applied to a gNB. The eNB 800 includes one or more antennas 810 and a base station device 820. The base station device 820 and each antenna 810 can be connected to each other via RF cables.

[0129] Each of the antennas 810 includes one or more antenna elements (such as multiple antenna elements included in a multiple-input multiple-output (MIMO) antenna) and is used by the base station equipment 820 to transmit and receive wireless signals. Figure 11 As shown, the eNB 800 may include multiple antennas 810. For example, the multiple antennas 810 may be compatible with multiple frequency bands used by the eNB 800. Although Figure 11 An example is shown in which the eNB 800 includes multiple antennas 810, but the eNB 800 may also include a single antenna 810.

[0130] The base station equipment 820 includes a controller 821, a memory 822, a network interface 823, and a wireless communication interface 825.

[0131] The controller 821 can be, for example, a CPU or a DSP, and operates various higher-level functions of the base station equipment 820. For example, the controller 821 generates data packets based on data in signals processed by the wireless communication interface 825, and transmits the generated packets via the network interface 823. The controller 821 can bundle data from multiple baseband processors to generate bundled packets and transmit the generated bundled packets. The controller 821 may have logical functions that perform controls such as radio resource control, radio bearer control, mobility management, admission control, and scheduling. This control can be performed in conjunction with nearby eNBs or core network nodes. The memory 822 includes RAM and ROM, and stores programs executed by the controller 821 and various types of control data (such as terminal lists, transmission power data, and scheduling data).

[0132] Network interface 823 is a communication interface used to connect base station equipment 820 to core network 824. Controller 821 can communicate with core network nodes or other eNBs via network interface 823. In this case, eNB 800 and core network nodes or other eNBs can be connected to each other through logical interfaces (such as S1 and X2 interfaces). Network interface 823 can also be a wired communication interface or a wireless communication interface for wireless backhaul. If network interface 823 is a wireless communication interface, it can use a higher frequency band for wireless communication compared to the frequency band used by wireless communication interface 825.

[0133] The wireless communication interface 825 supports any cellular communication scheme (such as LTE and LTE-Advanced) and provides wireless connectivity to terminals located in the cell of eNB 800 via antenna 810. The wireless communication interface 825 typically includes, for example, a baseband (BB) processor 826 and RF circuitry 827. The BB processor 826 can perform, for example, encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and performs various types of signal processing at layers such as L1, Media Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP). Instead of controller 821, the BB processor 826 may have some or all of the above-described logical functions. The BB processor 826 may be a memory storing communication control programs, or a module including a processor and associated circuitry configured to execute programs. Updates can change the functionality of the BB processor 826. The module may be a card or blade inserted into a slot in base station equipment 820. Alternatively, the module may be a chip mounted on a card or blade. Meanwhile, the RF circuit 827 may include, for example, a mixer, a filter, and an amplifier, and transmits and receives wireless signals via the antenna 810.

[0134] like Figure 11 As shown, the wireless communication interface 825 may include multiple BB processors 826. For example, the multiple BB processors 826 may be compatible with multiple frequency bands used by the eNB 800. Figure 11 As shown, the wireless communication interface 825 may include multiple RF circuits 827. For example, the multiple RF circuits 827 may be compatible with multiple antenna elements. Although Figure 11 An example is shown in which the wireless communication interface 825 includes multiple BB processors 826 and multiple RF circuits 827, but the wireless communication interface 825 may also include a single BB processor 826 or a single RF circuit 827.

[0135] exist Figure 11 In the eNB 800 shown, the transmitting unit 201, acquiring unit 202, and transceiver of the electronic device 200 can be implemented by the wireless communication interface 825. At least some of the functions can also be implemented by the controller 821. For example, the controller 821 can configure the UE's BFR mechanism for multi-TRP scenarios and acquire the reporting of UE beam failure events by executing the functions of the transmitting unit 201 and the acquiring unit 202.

[0136] (Second application example)

[0137] Figure 12This is a block diagram illustrating a second example of a schematic configuration of an eNB or gNB to which the technologies of this disclosure can be applied. Note that, similarly, the following description uses an eNB as an example, but it can also be applied to a gNB. The eNB 830 includes one or more antennas 840, a base station device 850, and an RRH 860. The RRH 860 and each antenna 840 can be connected to each other via RF cables. The base station device 850 and the RRH 860 can be connected to each other via high-speed lines such as fiber optic cables.

[0138] Each of the antennas 840 includes one or more antenna elements (such as multiple antenna elements included in a MIMO antenna) and is used by the RRH 860 to transmit and receive wireless signals. Figure 12 As shown, the eNB 830 may include multiple antennas 840. For example, the multiple antennas 840 may be compatible with multiple frequency bands used by the eNB 830. Although Figure 12 An example is shown in which the eNB 830 includes multiple antennas 840, but the eNB 830 may also include a single antenna 840.

[0139] The base station equipment 850 includes a controller 851, a memory 852, a network interface 853, a wireless communication interface 855, and a connection interface 857. The controller 851, memory 852, and network interface 853 are connected to a reference... Figure 11 The controller 821, memory 822, and network interface 823 described are the same.

[0140] The wireless communication interface 855 supports any cellular communication scheme (such as LTE and LTE-Advanced) and provides wireless communication to terminals located in the sector corresponding to the RRH 860 via the RRH 860 and antenna 840. The wireless communication interface 855 may typically include, for example, a BB processor 856. In addition to the BB processor 856 being connected to the RF circuitry 864 of the RRH 860 via a connection interface 857, the BB processor 856 is connected to the reference... Figure 11 The described BB processor 826 is the same. Figure 12 As shown, the wireless communication interface 855 may include multiple BB processors 856. For example, the multiple BB processors 856 may be compatible with multiple frequency bands used by the eNB 830. Although Figure 12 An example is shown in which the wireless communication interface 855 includes multiple BB processors 856, but the wireless communication interface 855 may also include a single BB processor 856.

[0141] Connection interface 857 is an interface for connecting base station device 850 (wireless communication interface 855) to RRH860. Connection interface 857 can also be a communication module for connecting base station device 850 (wireless communication interface 855) to the aforementioned high-speed line of RRH 860.

[0142] The RRH 860 includes a connectivity interface 861 and a wireless communication interface 863.

[0143] Connection interface 861 is an interface for connecting RRH 860 (wireless communication interface 863) to base station equipment 850. Connection interface 861 can also be a communication module for communication in the aforementioned high-speed line.

[0144] The wireless communication interface 863 transmits and receives wireless signals via antenna 840. The wireless communication interface 863 typically includes, for example, RF circuitry 864. RF circuitry 864 may include, for example, a mixer, a filter, and an amplifier, and transmits and receives wireless signals via antenna 840. Figure 12 As shown, the wireless communication interface 863 may include multiple RF circuits 864. For example, the multiple RF circuits 864 may support multiple antenna elements. Although Figure 12 An example is shown in which the wireless communication interface 863 includes multiple RF circuits 864, but the wireless communication interface 863 may also include a single RF circuit 864.

[0145] exist Figure 12 In the eNB 830 shown, the transmitting unit 201, acquiring unit 202, and transceiver of the electronic device 200 can be implemented by the wireless communication interface 855 and / or the wireless communication interface 863. At least some of the functions can also be implemented by the controller 851. For example, the controller 851 can configure the UE's BFR mechanism for multi-TRP scenarios and acquire the reporting of UE beam failure events by executing the functions of the transmitting unit 201 and the acquiring unit 202.

[0146] [Application examples related to user equipment]

[0147] (First application example)

[0148] Figure 13 This is a block diagram illustrating an example of a schematic configuration of a smartphone 900 to which the technologies of this disclosure can be applied. The smartphone 900 includes a processor 901, a memory 902, a storage device 903, an external connection interface 904, a camera device 906, a sensor 907, a microphone 908, an input device 909, a display device 910, a speaker 911, a wireless communication interface 912, one or more antenna switches 915, one or more antennas 916, a bus 917, a battery 918, and an auxiliary controller 919.

[0149] The processor 901 can be, for example, a CPU or a system-on-a-chip (SoC), and controls the application layer and other functions of the smartphone 900. The memory 902 includes RAM and ROM, and stores data and programs executed by the processor 901. The storage device 903 can include storage media such as semiconductor memory and hard disks. The external connectivity interface 904 is an interface for connecting external devices, such as memory cards and Universal Serial Bus (USB) devices, to the smartphone 900.

[0150] The camera device 906 includes an image sensor (such as a charge-coupled device (CCD) and complementary metal-oxide-semiconductor (CMOS)) and generates captured images. The sensor 907 may include a set of sensors, such as a measurement sensor, a gyroscope sensor, a magnetometer sensor, and an accelerometer sensor. The microphone 908 converts sound input to the smartphone 900 into an audio signal. The input device 909 includes, for example, a touch sensor, keypad, keyboard, buttons, or switches configured to detect touches on the screen of the display device 910 and receives operations or information input from the user. The display device 910 includes a screen (such as a liquid crystal display (LCD) and an organic light-emitting diode (OLED) display) and displays the output image of the smartphone 900. The speaker 911 converts the audio signal output from the smartphone 900 into sound.

[0151] The wireless communication interface 912 supports any cellular communication scheme (such as LTE and LTE-Advanced) and performs wireless communication. The wireless communication interface 912 typically includes, for example, a BB processor 913 and RF circuitry 914. The BB processor 913 can perform, for example, encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and performs various types of signal processing for wireless communication. Meanwhile, the RF circuitry 914 can include, for example, mixers, filters, and amplifiers, and transmits and receives wireless signals via antenna 916. Note that although the figure shows a scenario where one RF link is connected to one antenna, this is only illustrative; scenarios where an RF link is connected to multiple antennas via multiple phase shifters are also included. The wireless communication interface 912 can be a single chip module on which the BB processor 913 and RF circuitry 914 are integrated. Figure 13 As shown, the wireless communication interface 912 may include multiple BB processors 913 and multiple RF circuits 914. Although Figure 13 An example is shown in which the wireless communication interface 912 includes multiple BB processors 913 and multiple RF circuits 914, but the wireless communication interface 912 may also include a single BB processor 913 or a single RF circuit 914.

[0152] In addition to cellular communication schemes, the wireless communication interface 912 can support other types of wireless communication schemes, such as short-range wireless communication schemes, near-field communication schemes, and wireless local area network (LAN) schemes. In this case, the wireless communication interface 912 may include a BB processor 913 and RF circuitry 914 for each wireless communication scheme.

[0153] Each of the antenna switches 915 switches the connection destination of the antenna 916 among multiple circuits (e.g., circuits for different wireless communication schemes) included in the wireless communication interface 912.

[0154] Each of the antennas 916 includes one or more antenna elements (such as multiple antenna elements included in a MIMO antenna) and is used by the wireless communication interface 912 to transmit and receive wireless signals. Figure 13 As shown, the smartphone 900 may include multiple antennas 916. Although Figure 13 An example is shown in which the smartphone 900 includes multiple antennas 916, but the smartphone 900 may also include a single antenna 916.

[0155] Furthermore, the smartphone 900 may include an antenna 916 for each wireless communication scheme. In this case, the antenna switch 915 can be omitted from the configuration of the smartphone 900.

[0156] Bus 917 connects processor 901, memory 902, storage device 903, external connection interface 904, camera device 906, sensor 907, microphone 908, input device 909, display device 910, speaker 911, wireless communication interface 912, and auxiliary controller 919 to each other. Battery 918 supplies power to... Figure 13 The various blocks of the smartphone 900 shown are powered, and the feeders are partially shown as dashed lines in the figure. The auxiliary controller 919 operates the minimum necessary functions of the smartphone 900, for example, in sleep mode.

[0157] exist Figure 13 In the illustrated smartphone 900, the acquisition unit 101, reporting unit 102, and transceiver of the electronic device 100 can be implemented by the wireless communication interface 912. At least a portion of the functions can also be implemented by the processor 901 or the auxiliary controller 919. For example, the processor 901 or the auxiliary controller 919 can execute the functions of the acquisition unit 101, the reporting unit 102, and the determination unit 103 to determine and report beam failure events according to the BFR configuration for multi-TRP scenarios.

[0158] (Second application example)

[0159] Figure 14This is a block diagram illustrating an example of a schematic configuration of a car navigation device 920 to which the technology of this disclosure can be applied. The car navigation device 920 includes a processor 921, a memory 922, a Global Positioning System (GPS) module 924, a sensor 925, a data interface 926, a content player 927, a storage medium interface 928, an input device 929, a display device 930, a speaker 931, a wireless communication interface 933, one or more antenna switches 936, one or more antennas 937, and a battery 938.

[0160] The processor 921 can be, for example, a CPU or a SoC, and controls the navigation functions and other functions of the car navigation device 920. The memory 922 includes RAM and ROM, and stores data and programs executed by the processor 921.

[0161] GPS module 924 uses GPS signals received from GPS satellites to measure the location (such as latitude, longitude, and altitude) of car navigation device 920. Sensor 925 may include a set of sensors, such as a gyroscope sensor, a geomagnetic sensor, and an air pressure sensor. Data interface 926 is connected to, for example, an in-vehicle network 941 via a terminal not shown, and acquires data generated by the vehicle (such as vehicle speed data).

[0162] Content player 927 reproduces content stored on storage media (such as CDs and DVDs), which is inserted into storage media interface 928. Input device 929 includes, for example, a touch sensor, button, or switch configured to detect touch on the screen of display device 930, and receives operations or information input from the user. Display device 930 includes a screen such as an LCD or OLED display and displays images or reproduced content for navigation functions. Speaker 931 outputs sound for navigation functions or reproduced content.

[0163] The wireless communication interface 933 supports any cellular communication scheme (such as LTE and LTE-Advanced) and performs wireless communication. The wireless communication interface 933 typically includes, for example, a BB processor 934 and RF circuitry 935. The BB processor 934 can perform, for example, encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and performs various types of signal processing for wireless communication. Meanwhile, the RF circuitry 935 can include, for example, a mixer, filters, and amplifiers, and transmits and receives wireless signals via an antenna 937. The wireless communication interface 933 can also be a chip module on which the BB processor 934 and RF circuitry 935 are integrated. Figure 14 As shown, the wireless communication interface 933 may include multiple BB processors 934 and multiple RF circuits 935. Although Figure 14An example is shown in which the wireless communication interface 933 includes multiple BB processors 934 and multiple RF circuits 935, but the wireless communication interface 933 may also include a single BB processor 934 or a single RF circuit 935.

[0164] In addition to cellular communication schemes, the wireless communication interface 933 can support other types of wireless communication schemes, such as short-range wireless communication schemes, near-field communication schemes, and wireless LAN schemes. In this case, for each wireless communication scheme, the wireless communication interface 933 may include a BB processor 934 and an RF circuit 935.

[0165] Each of the antenna switches 936 switches the connection destination of the antenna 937 among multiple circuits (such as circuits for different wireless communication schemes) included in the wireless communication interface 933.

[0166] Each of the antennas 937 includes one or more antenna elements (such as multiple antenna elements included in a MIMO antenna) and is used by the wireless communication interface 933 to transmit and receive wireless signals. Figure 14 As shown, the car navigation device 920 may include multiple antennas 937. Although Figure 14 An example is shown in which the car navigation device 920 includes multiple antennas 937, but the car navigation device 920 may also include a single antenna 937.

[0167] Furthermore, the car navigation device 920 may include an antenna 937 for each wireless communication scheme. In this case, the antenna switch 936 can be omitted from the configuration of the car navigation device 920.

[0168] Battery 938 via feeder to Figure 14 The various blocks of the car navigation device 920 shown are powered, and the feeders are partially shown as dashed lines in the figure. Battery 938 accumulates the power supplied from the vehicle.

[0169] exist Figure 14 In the illustrated car navigation device 920, the acquisition unit 101, reporting unit 102, and transceiver of the electronic device 100 can be implemented by the wireless communication interface 933. At least a portion of the functions can also be implemented by the processor 921. For example, the processor 921 can execute the functions of the acquisition unit 101, reporting unit 102, and determination unit 103 to determine and report beam failure events according to the BFR configuration for multi-TRP scenarios.

[0170] The technology disclosed herein can also be implemented as an in-vehicle system (or vehicle) 940 comprising one or more of the following blocks: a car navigation device 920, an in-vehicle network 941, and a vehicle module 942. The vehicle module 942 generates vehicle data (such as vehicle speed, engine speed, and fault information) and outputs the generated data to the in-vehicle network 941.

[0171] The basic principles of the present invention have been described above in conjunction with specific embodiments. However, it should be noted that those skilled in the art will understand that all or any step or component of the method and apparatus of the present invention can be implemented in any computing device (including processors, storage media, etc.) or network of computing devices, in the form of hardware, firmware, software or a combination thereof. This can be achieved by those skilled in the art using their basic circuit design knowledge or basic programming skills after reading the description of the present invention.

[0172] Furthermore, the present invention also proposes a program product storing machine-readable instruction code. When the instruction code is read and executed by a machine, the method described above according to embodiments of the present invention can be performed.

[0173] Accordingly, the storage medium used to carry the program product storing machine-readable instruction code is also included in the disclosure of this invention. The storage medium includes, but is not limited to, floppy disks, optical disks, magneto-optical disks, memory cards, memory sticks, etc.

[0174] When the present invention is implemented via software or firmware, the transmission from a storage medium or network to a computer with a dedicated hardware architecture (e.g., Figure 15 The general-purpose computer 1500 shown is equipped with the programs that constitute the software, and when various programs are installed, the computer is able to perform various functions, etc.

[0175] exist Figure 15 In this system, the Central Processing Unit (CPU) 1501 performs various processes based on programs stored in the Read-Only Memory (ROM) 1502 or programs loaded into the Random Access Memory (RAM) 1503 from the Storage Section 1508. The RAM 1503 also stores data required as needed when the CPU 1501 performs various processes, etc. The CPU 1501, ROM 1502, and RAM 1503 are interconnected via a bus 1504. An input / output interface 1505 is also connected to the bus 1504.

[0176] The following components are connected to the input / output interface 1505: input section 1506 (including keyboard, mouse, etc.), output section 1507 (including display, such as cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.), storage section 1508 (including hard disk, etc.), and communication section 1509 (including network interface card, such as LAN card, modem, etc.). The communication section 1509 performs communication processing via a network, such as the Internet. If necessary, a drive 1510 may also be connected to the input / output interface 1505. Removable media 1511, such as disks, optical disks, magneto-optical disks, semiconductor memories, etc., are installed on the drive 1510 as needed, so that computer programs read from them can be installed into the storage section 1508 as needed.

[0177] When the above series of processes are implemented by software, the program constituting the software is installed from a network such as the Internet or a storage medium such as removable media 1511.

[0178] Those skilled in the art will understand that such storage media are not limited to Figure 15 The illustration shows a removable medium 1511 containing a program, distributed separately from the device to provide the program to the user. Examples of removable media 1511 include disks (including floppy disks (registered trademark)), optical disks (including optical disc read-only memory (CD-ROM) and digital versatile disks (DVD)), magneto-optical disks (including mini-discs (MD) (registered trademark)), and semiconductor memory. Alternatively, the storage medium may be ROM 1502, a hard disk included in storage section 1508, etc., containing programs and distributed to the user along with the device containing them.

[0179] It should also be noted that in the apparatus, method, and system of the present invention, the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered equivalent solutions of the present invention. Furthermore, the steps performing the above series of processes can naturally be executed in the order described, but are not necessarily required to be executed in chronological order. Some steps can be performed in parallel or independently of each other.

[0180] Finally, it should be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Furthermore, unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element. While embodiments of the present invention have been described in detail above with reference to the accompanying drawings, it should be understood that the embodiments described above are merely illustrative and do not constitute a limitation thereof. Various modifications and changes can be made to the above embodiments by those skilled in the art without departing from the spirit and scope of the present invention. Therefore, the scope of the present invention is defined only by the appended claims and their equivalents.

Claims

1. An electronic device for wireless communication, comprising: The processing circuit is configured as follows: Configuration information for beam failure recovery of user equipment in multi-transmitter and receiver point (TRP) communication is obtained from the base station. This configuration information includes a first configuration and / or a second configuration. The first configuration is used for determining beam failure events for each of the multiple TRPs, and the second configuration is used for the joint determination of beam failure events for the multiple TRPs. Based on the configuration information, a beam failure event is reported to the base station. The second configuration includes one or more of the following: a weighting parameter for calculating the joint BLER of the plurality of TRPs, a joint BLER threshold, a second counter for counting the number of joint physical layer beam failures of the plurality of TRPs, and a second maximum count threshold for the second counter. In response to the second configuration, the processing circuit is configured to increment the second counter by 1 when a joint physical layer beam failure event occurs in the plurality of TRPs, and to determine that a joint beam failure event has occurred in the plurality of TRPs and report it to the base station when the count value of the second counter reaches the second maximum count threshold.

2. The electronic device according to claim 1, wherein, The configuration information also includes information indicating the transmission scenario type, which includes either enhanced mobile bandwidth or ultra-reliable low latency communication.

3. The electronic device according to claim 2, wherein, The processing circuitry is configured to determine, based on the indicated transmission scenario type, whether to report the beam failure event using the first configuration and / or the second configuration.

4. The electronic device according to claim 1, wherein, The first configuration includes one or more of the following: a first counter for counting the number of physical layer beam failures for each TRP, a block error rate (BLER) threshold for each TRP, and a first maximum count threshold for the first counter. In response to the first configuration, the processing circuit is configured to increment the first counter of one of the plurality of TRPs by 1 when a physical layer beam failure event occurs, and to determine that a beam failure event has occurred in the TRP and report it to the base station when the count value of the first counter reaches the first maximum count threshold.

5. The electronic device according to claim 4, wherein, The processing circuit is configured to report the beam failure events of more than one TRP to the base station, respectively, when it is determined that more than one TRP has experienced a beam failure event.

6. The electronic device according to claim 4, wherein, The BLER thresholds of each TRP are the same, and / or the first maximum count thresholds of the first counters of each TRP are the same.

7. The electronic device according to claim 1, wherein, The processing circuit is configured to perform a weighted summation of the BLER of each of the plurality of TRPs according to the weighting parameters, and use the result as the joint BLER.

8. The electronic device according to claim 7, wherein, The weighting parameters are set for each TRP and are constants in the range of 0 to 1, with the sum of all weighting parameters being 1.

9. The electronic device according to claim 1, wherein, The first configuration includes one or more of the following: a first counter for counting the number of physical layer beam failures for each TRP, for a BLER threshold of each TRP, and a first maximum count threshold for the first counter. In response to the first configuration and the second configuration, the processing circuit is configured to: When a physical layer beam failure event occurs in one of the plurality of TRPs, the first counter of that TRP is incremented by 1; When a joint physical layer beam failure event occurs in the plurality of TRPs, the second counter is incremented by 1; as well as When the count value of any one of the first counters reaches the first maximum count threshold first, a beam failure event is determined to have occurred in the TRP corresponding to the first counter and reported to the base station. When the count value of the second counter reaches the second maximum count threshold first, a joint beam failure event is determined to have occurred in the multiple TRPs and reported to the base station.

10. The electronic device according to claim 4, wherein, The processing circuit is configured to detect the BLER of the beam failure detection reference signal configured for each TRP as the BLER of the TRP.

11. The electronic device according to claim 1, wherein, The processing circuit is configured to report the beam failure event to the base station via a Link Recovery Request (LRR).

12. The electronic device according to claim 11, wherein, The LRR has a specific sequence format to indicate that the beam failure event has occurred.

13. The electronic device according to claim 12, wherein, The processing circuit is also configured to send information about the TRP that has experienced a beam failure event and information about the candidate beams of the TRP that has experienced the beam failure event to the base station via the MAC CE.

14. The electronic device according to claim 13, wherein, The processing circuitry is configured to use the control resource set pool index CORESETPoolIndex to indicate the TRP where a beam failure event has occurred.

15. The electronic device according to claim 11, wherein, The LRR includes information indicating the TRP that has occurred during a beam failure event.

16. The electronic device according to claim 15, wherein, The processing circuit is configured to use CORESETPoolIndex to indicate the TRP where a beam failure event has occurred.

17. The electronic device according to claim 15, wherein, The processing circuit is also configured to send information about the candidate beams of the TRP that experienced the beam failure event to the base station via a MAC CE.

18. An electronic device for wireless communication, comprising: The processing circuit is configured as follows: Sending configuration information to the user equipment for beam failure recovery in multi-TRP communication, wherein the configuration information includes a first configuration and / or a second configuration, the first configuration being used for determining beam failure events for each of the multiple TRPs, and the second configuration being used for the joint determination of beam failure events for the multiple TRPs; and Obtain the user equipment's report on beam failure events based on the configuration information. The second configuration includes one or more of the following: a weighting parameter for calculating the joint BLER of the plurality of TRPs, a joint BLER threshold, a second counter for counting the number of joint physical layer beam failures of the plurality of TRPs, and a second maximum count threshold for the second counter.

19. The electronic device according to claim 18, wherein, The configuration information also includes information indicating the transmission scenario type, which includes either enhanced mobile bandwidth or ultra-reliable low latency communication.

20. The electronic device according to claim 18, wherein, The first configuration includes one or more of the following: a block error rate (BLER) threshold for each TRP, a first counter for counting the number of physical layer beam failures for each TRP, and a first maximum count threshold for the first counter.

21. The electronic device according to claim 20, wherein, In the event of a beam failure event occurring at more than one TRP, the processing circuitry obtains a report of the beam failure event for the more than one TRP from the user equipment.

22. The electronic device according to claim 20, wherein, The BLER thresholds of each TRP are the same, and / or the first maximum count thresholds of the first counters of each TRP are the same.

23. The electronic device according to claim 18, wherein, The processing circuit is configured to obtain the report via a Link Recovery Request (LRR).

24. The electronic device according to claim 23, wherein, The LRR has a specific sequence format to indicate that the beam failure event has occurred.

25. The electronic device according to claim 24, wherein, The processing circuit is also configured to obtain information about the TRP indicating a beam failure event and information about the candidate beams of the TRP that caused the beam failure event from the user equipment via the MAC CE.

26. The electronic device according to claim 25, wherein, The TRP that experiences a beam failure event is indicated by the control resource set pool index CORESETPoolIndex.

27. The electronic device according to claim 23, wherein, The LRR includes information indicating the TRP that has occurred during a beam failure event.

28. The electronic device according to claim 27, wherein, The TRP that causes a beam failure event is indicated by CORESETPoolIndex.

29. The electronic device according to claim 27, wherein, The processing circuit is also configured to obtain information about the candidate beams of the TRP that experienced the beam failure event from the user equipment via the MAC CE.

30. A method for wireless communication, comprising: Configuration information for beam failure recovery of user equipment in multi-transmitter and receiver point (TRP) communication is obtained from the base station. This configuration information includes a first configuration and / or a second configuration. The first configuration is used for determining beam failure events for each of the multiple TRPs, and the second configuration is used for the joint determination of beam failure events for the multiple TRPs. Based on the configuration information, a beam failure event is reported to the base station. The second configuration includes one or more of the following: a weighting parameter for calculating the joint BLER of the plurality of TRPs, a joint BLER threshold, a second counter for counting the number of joint physical layer beam failures of the plurality of TRPs, and a second maximum count threshold for the second counter. The method further includes: in response to the second configuration, incrementing the second counter by 1 when a joint physical layer beam failure event occurs in the plurality of TRPs, and determining that a joint beam failure event has occurred in the plurality of TRPs and reporting it to the base station when the count value of the second counter reaches the second maximum count threshold.

31. A method for wireless communication, comprising: Sending configuration information to the user equipment for beam failure recovery in multi-TRP communication, wherein the configuration information includes a first configuration and / or a second configuration, the first configuration being used for determining beam failure events for each of the multiple TRPs, and the second configuration being used for the joint determination of beam failure events for the multiple TRPs; and Obtain the user equipment's report on beam failure events based on the configuration information. The second configuration includes one or more of the following: a weighting parameter for calculating the joint BLER of the plurality of TRPs, a joint BLER threshold, a second counter for counting the number of joint physical layer beam failures of the plurality of TRPs, and a second maximum count threshold for the second counter.

32. A computer-readable storage medium having stored thereon computer-executable instructions that, when executed, perform the method for wireless communication according to claim 30 or 31.

33. A computer program product comprising a computer program / instructions, wherein, When the computer program / instructions are executed by the processor, they implement the steps of the method for wireless communication as described in claim 30 or 31.

Images