Resource allocation for beam failure recovery procedures.

Abstract

To provide a mobile terminal, a base station, and a method that facilitate initiating a beam failure recovery procedure.SOLUTION: A mobile terminal includes a transceiver that receives a configuration of a PRACH resource for transmitting a beam failure recovery signal, and a processor that detects a downlink beam failure event and initiates a beam failure recovery procedure in response, and the beam failure recovery procedure includes transmitting a beam failure recovery signal using a PRACH resource by the transceiver. The configuration includes a timer that indicates a period of time that the PRACH resource is valid and an indicator that indicates the number of PRACH resources in the subset of the plurality of PRACH resources.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present disclosure relates to uplink resource allocation for transmitting a beam failure recovery signal in response to a mobile terminal detecting a downlink beam failure event while communicating with a base station in a mobile communication system. [Background technology]

[0002] Currently, the 3rd Generation Partnership Project (3GPP®) is focused on its next release (Release 15) of technical specifications for next generation cellular technology, also known as the fifth generation (5G).

[0003] At the 3GPP Technical Specification Group (TSG) Radio Access Network (RAN) Meeting #71 (Gothenburg, March 2016), the first 5G study item, "Study on New Radio Access Technology", which includes RAN1, RAN2, RAN3, and RAN4, was approved, and is expected to become the Release 15 Work Item (WI) that will define the first 5G standards.

[0004] One of the objectives of 5G New Radio (NR) is to provide a single technical framework that addresses all usage scenarios, requirements, and deployment scenarios defined in 3GPP Standards and Practices (SPSE) 2013-01-13 (available at www.3gpp.org and incorporated herein by reference in its entirety), including at least enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), and massive machine type communications (mMTC).

[0005] For example, eMBB deployment scenarios may include indoor hotspots, dense urban, suburban, urban wide area, and high speed. URLLC deployment scenarios may include industrial control systems, mobile healthcare (remote monitoring, diagnosis, and treatment), real-time control of vehicles, wide area supervisory control systems for smart grids. mMTC may include scenarios involving a large number of devices with non-time critical data transfer, such as smart wearables and sensor networks.

[0006] Another objective is forward compatibility in anticipation of future use cases / deployment scenarios: backward compatibility for Long Term Evolution (LTE) is not required, which facilitates completely new system designs and / or the introduction of new features.

[0007] As summarized in one of the technical reports on the NR study items (Non-Patent Document 2), the basic physical layer signal waveform will be based on Orthogonal Frequency Division Multiplexing (OFDM). Cyclic prefix OFDM (CP-OFDM) based waveforms will be supported for both downlink and uplink. For eMBB uplink up to at least 40 GHz, Discrete Fourier Transform (DFT) Spread OFDM (DFT-S-OFDM) based waveforms will also be supported as a complement to the CP-OFDM waveform.

[0008] As summarized in another technical report on the NR study item (Non-Patent Document 3), multi-antenna schemes rely on a set of beam management procedures that allow a transmitting / receiving point (TRP) and / or a UE to acquire and maintain a set of beams that can be used for DL ​​and UL transmission / reception, including beam determination, beam measurement, beam reporting, and beam sweeping.

[0009] One of the design targets for NR is to utilize the basic physical layer signal waveforms for communication while increasing the coverage of base stations supporting single-user and multi-user MIMO in both downlink and uplink. To this end, it was agreed at 3GPP TSG RAN1 WG1 Meeting #89 (Hangzhou, People's Republic of China, May 15-19, 2017) to adopt beam management procedures that include a beam failure recovery mechanism when a beam failure is detected. This mechanism is separate from the radio link failure procedures at higher layers.

[0010] The term "downlink" refers to communication from a higher level node to a lower level node (e.g., from a base station to a relay node or UE, from a relay node to a UE, etc.). The term "uplink" refers to communication from a lower level node to a higher level node (e.g., from a UE to a relay node or base station, from a relay node to a base station, etc.). The term "sidelink" refers to communication between nodes at the same level (e.g., between two EUs, or between two relay nodes, or between two base stations). [Prior art documents] [Non-patent literature]

[0011] [Non-Patent Document 1] 3GPP TSG RAN TR 38.913 v14.1.0, "Study on Scenarios and Requirements for Next Generation Access Technologies", Dec. 2016 [Non-Patent Document 2] 3GPP TSG TR 38.801 v2.0.0, "Study on New Radio Access Technology; Radio Access Architecture and Interfaces", March 2017 [Non-Patent Document 3] 3GPP TSG TR 38.802 V2.0.0, "Study on New Radio (NR) Access Technology; Physical Layer Aspects" Summary of the Invention [Problem to be solved by the invention]

[0012] Certain non-limiting exemplary embodiments facilitate beam failure recovery procedures to be initiated in a robust (reliable) manner, i.e., by utilizing individual uplink radio resources more efficiently (context-dependently). [Means for solving the problem]

[0013] In one general aspect, the techniques disclosed herein feature a mobile terminal for communicating with a base station in a mobile communication system using at least one of a plurality of downlink beams and at least one of a plurality of uplink beams, each of the downlink beams having a different directivity and / or coverage. The mobile terminal includes a transceiver that, in operation, receives an assignment of dedicated uplink radio resources for transmitting a beam failure recovery signal for a beam failure recovery (BFR) procedure, and a processor that, in operation, detects a downlink beam failure event and responsively initiates a beam failure recovery procedure, the beam failure recovery procedure including the transceiver transmitting the beam failure recovery signal using the dedicated uplink radio resources from the assignment. The dedicated uplink radio resources restrict transmission to a subset of the plurality of uplink beams that may be exclusively assigned by the base station to the mobile terminal.

[0014] It should be noted that the general or specific embodiments may be implemented as a system, a method, an integrated circuit, a computer program, a storage medium, or any selective combination thereof.

[0015] Additional benefits and advantages of the disclosed embodiments will be apparent from the specification and drawings. These benefits and / or advantages may be obtained individually by the various embodiments and features of the specification and drawings, and it is not necessary for all of the embodiments and features to be provided in order to obtain one or more of such benefits and / or advantages. [Brief description of the drawings]

[0016] [Figure 1] FIG. 2 is a block diagram showing the structure of a mobile terminal and a base station; [Diagram 2] FIG. 1 is a schematic diagram illustrating beam failure recovery procedure initiation in the context of a four-step beam failure recovery procedure in a typical deployment scenario. [Diagram 3] FIG. 1 is a schematic diagram illustrating beam failure recovery procedure initiation in the context of a four-step beam failure recovery procedure in a 3GPP NR deployment scenario. [Figure 4] FIG. 1 is a schematic diagram illustrating beam failure recovery procedure initiation in the context of a two-step beam failure recovery procedure in a 3GPP NR deployment scenario. [Diagram 5] FIG. 13 is a diagram illustrating a schematic of dedicated uplink radio resources in a Physical Random Access Channel (PRACH) for initiation of a beam failure recovery procedure. [Figure 6] FIG. 13 is a diagram illustrating a schematic diagram of dedicated uplink radio resources in a physical uplink control channel (PUCCH) for initiation of a beam failure recovery procedure. [Figure 7a] FIG. 1 is a schematic diagram illustrating the main causes of downlink beam obstruction in a 3GPP NR deployment scenario. [Figure 7b] FIG. 1 is a schematic diagram illustrating the main causes of downlink beam obstruction in a 3GPP NR deployment scenario. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] In another general aspect, the techniques disclosed herein feature another mobile terminal for communicating with a base station in a mobile communication system using at least one of a plurality of downlink beams and at least one of a plurality of uplink beams, each of the downlink beam and the uplink beam having a different directivity. The mobile terminal includes a transceiver that, in operation, receives an assignment of dedicated uplink radio resources for transmitting a beam failure recovery signal for a beam failure recovery (BFR) procedure, and a processor that, in operation, detects a downlink beam failure event and responsively initiates a beam failure recovery procedure, the beam failure recovery procedure including the transceiver transmitting the beam failure recovery signal using the dedicated uplink radio resources of the assignment. The dedicated uplink radio resources restrict transmission to a subset of the plurality of uplink beams that can be non-exclusively assigned by the base station to the mobile terminal.

[0018] In yet another general aspect, the techniques disclosed herein feature a method for initiating a beam failure recovery procedure implemented by a mobile terminal configured to communicate with a base station in a mobile communication system using at least one of a plurality of downlink beams and at least one of a plurality of uplink beams, each of the downlink beam and the uplink beam having a different directivity and / or coverage. The method includes receiving an assignment of dedicated uplink radio resources for transmitting a beam failure recovery signal for a beam failure recovery (BFR) procedure, detecting a downlink beam failure event and initiating the beam failure recovery procedure in response thereto, the beam failure recovery procedure including transmitting the beam failure recovery signal using the dedicated uplink radio resources from the assignment. The dedicated uplink radio resources restrict the transmission to a subset of the plurality of uplink beams that can be exclusively assigned by the base station to the mobile terminal.

[0019] In yet another general aspect, the techniques disclosed herein feature another method for initiating a beam failure recovery procedure implemented by a mobile terminal configured to communicate with a base station using at least one of a plurality of downlink beams and at least one of a plurality of uplink beams, each of the uplink and downlink beams having different directivities. The method includes receiving an assignment of dedicated uplink radio resources for a beam failure recovery signal for a beam failure recovery (BFR) procedure, and detecting a downlink beam failure event and initiating a beam failure recovery procedure in response thereto, the beam failure recovery procedure including transmitting the beam failure recovery signal using the dedicated uplink radio resources of the assignment. The dedicated uplink radio resources restrict transmission to a subset of the plurality of uplink beams that can be non-exclusively assigned by the base station to the mobile terminal.

[0020] As identified in TR38.913, various use cases / deployment scenarios for NR have different requirements in terms of data rates, latency, and coverage. With these requirements in mind, NR should aim for even higher coverage compared to LTE.

[0021] In 3GPP RAN1#85, beam-based transmission was extensively discussed for NR as a key technique to ensure coverage. For beam management, it was agreed that both intra-TRP and inter-TRP beamforming procedures are considered, with / without TRP beamforming / beam sweeping and with / without UE beamforming / beam sweeping, according to the following potential use cases: UE movement, UE rotation, beam blocking (change of beam at TRP and same beam at UE, same beam at TRP and change of beam at UE, or change of beam at TRP and change of beam at UE), but other cases are not excluded. Furthermore, it was also agreed to consider beam (e.g., TRP beam and / or UE beam) management procedures (e.g., beam determination and change procedures), i.e., procedures for both data and control transmission / reception, with / without pre-acquired beam information. The procedures may or may not be the same for data and control.

[0022] Subsequently, in RAN1#88, the following was agreed upon: A beam failure event occurs when the quality of the beam pair link of the associated control channel degrades sufficiently (e.g., comparison with a threshold, expiration of an associated timer); When a beam failure occurs, a mechanism to recover from the beam failure is triggered. Note: Beam pair link is used for convenience and may or may not be used in the specification. The following items remained FFS (for further study): whether the quality can additionally include the quality of the beam pair link associated with the NR-PDSCH; when multiple Y beam pair links are configured, beam failure can be declared if X (≦Y) of the Y beam pair links fall below a certain threshold to satisfy a beam failure condition; the search space of the associated NR-PDCCH (UE-specific vs. common); what is the signaling mechanism for the NR-PDCCH when the UE is configured to monitor multiple beam pair links for the NR-PDCCH. Furthermore, the exact definition of such threshold is FFS, and other conditions for triggering such mechanisms are not excluded.

[0023] It was also agreed that the following signals can be configured for detecting beam failure by the UE and for identifying new potential beams by the UE, but the reference to the signals remains FFS. The signals are e.g. RS for beam management, RS for fine timing / frequency tracking, SS block, DM-RS for PDCCH (including group-common PDCCH and / or UE-specific PDCCH), DM-RS for PDSCH. If a beam failure event occurs and no new potential beam is detected by the UE in the serving cell, it remains FFS whether the UE provides an indication to L3 and whether this indication links to a radio link failure event. Note: The criteria for declaring radio link failure is for RAN2 to decide. The necessity of such an indication is also FFS. NR supports configuring resources for sending requests for recovery purposes in symbols containing RACH and / or FFS scheduling requests or in other indicated symbols.

[0024] Then, in RAN1#88Bis, it was agreed that the UE beam failure recovery mechanism includes the following aspects: beam failure detection, identification of new candidate beams, sending a beam failure recovery request, and the UE monitors the gNB's response to the beam failure recovery request. For beam failure detection, the UE monitors the beam failure detection RS to evaluate whether the beam failure trigger conditions are met. The beam failure detection RS includes at least a periodic CSI-RS for beam management, and if sounding signal SS-blocks are also used in beam management, the SS-blocks in the serving cell can be taken into account. However, it is left to FFS what the trigger conditions are to declare beam failure.

[0025] Regarding the identification of new candidate beams, it was also agreed that the UE monitors the beam identification RS to find new candidate beams, which includes a periodic CSI-RS for beam management if configured by the NW, and / or includes the periodic CSI-RS and the SS-block in the serving cell if the SS-block is also used in beam management.

[0026] Regarding the transmission of the beam failure recovery request, it was also agreed that the information carried by the beam failure recovery request includes at least one of the following: explicit / implicit information on identifying the UE and new gNB TX beam information, and / or explicit / implicit information on identifying the UE and whether a new candidate beam exists. The information indicating the UE beam failure and additional information, e.g. the quality of the new beam, were left FFS. It was agreed that the selection range limitation between channels for the transmission of the beam failure recovery request includes PRACH, PUCCH, PRACH-like (e.g. the parameters of the preamble sequence are different from PRACH). The beam failure recovery request resource / signal may additionally be used for the scheduling request.

[0027] In this regard, the UE monitors the control channel search space to receive the gNB's response to the beam failure recovery request, however, it is FFS whether the control channel search space may be the same as or different from the current control channel search space associated with the serving BPL and / or what the UE's further reaction is if the gNB does not receive the beam failure recovery request transmission.

[0028] It may thus be concluded that the beam failure recovery procedure discussed above facilitates an efficient way of re-establishing a connection between a UE and a gNB (i.e., a TRP) after a downlink beam failure event, i.e., without the need to declare a radio link failure to higher layers. However, it has been recognized that this beam failure recovery procedure will only be successful if the procedure provides a means to enable the UE to act quickly before a radio link failure event is triggered.

[0029] In other words, the concept of recovery after beam failure is based on a procedure whereby the UE indicates to the gNB alternative (i.e., candidate) downlink beams that can be used to restore communication between the gNB and the UE after the UE detects a beam failure for a downlink beam. Thus, this procedure relies on the UE still being able to indicate alternative (i.e., candidate) downlink beams to the gNB. However, this is only possible for a short period of time after the downlink beam failure occurs.

[0030] Therefore, one non-limiting exemplary embodiment of the present disclosure proposes a robust mechanism that would enable the UE to respond to a beam failure detection event by initiating a beam failure recovery procedure as quickly as possible to avoid any detrimental effects that arise as a result of the inherent correspondence between downlink and uplink beams.

[0031] The proposed robust mechanism can be further better understood when looking at the sources or causes of beam impairments in the communication between gNBs and UEs. This understanding is generally based on 3GPP NR deployment scenarios, but is not limited to the following scenarios, i.e., scenarios where the concept of beams is introduced to improve directionality and / or coverage. This is particularly advantageous in view of the envisaged very high frequency bands (mmWave) in which 3GPP NR is intended to operate.

[0032] As shown in Figures 7a and 7b, a gNB can be configured to communicate on multiple beams (e.g., beam #0 to beam #4). This is necessary for initial access by the UE. After establishing a connection between the gNB and the UE, the gNB serves the UE with a downlink on a single beam (referred to as a "downlink serving beam" or "downlink beam"). However, it should be understood that a multiple beam scenario, i.e., a scenario in which the gNB serves the UE with a downlink via two or more separate beams, e.g., to increase capacity, may also be envisioned.

[0033] Similarly, the UE can be configured to communicate on multiple beams (e.g., beam #0 to beam #4), which is equally necessary for initial access by the UE. After establishing a connection, the UE still sends uplink traffic to the gNB using the uplink on a single beam (referred to as the "uplink serving beam" or "uplink beam"). However, this single uplink serving beam is not necessarily the same as the beam on which the downlink is served. Multiple beam scenarios may also be envisaged for the uplink, and thus the present disclosure should not be construed as limiting in any respect.

[0034] In general, it can be assumed that a downlink and uplink serving beam pair has suitable characteristics for downlink and uplink communication between a gNB and a UE. It can be easily seen that in many cases, there is a directional correspondence between the downlink and uplink serving beam pairs, i.e., the downlink and uplink serving beam pairs are beams with opposite directions and similar coverage.

[0035] In this context, it shall be mentioned that a gNB in ​​3GPP NR is configured with one or more TRPs (Transmit / Receive Points, or Tx / Rx points), each TRP linked to a downlink and / or uplink serving beam with a particular direction and a particular coverage. Thus, in a multi-beam configuration, a gNB will necessarily be configured with more than one TRP, i.e. configured to be able to transmit / receive beams with different directions and / or coverage.

[0036] Returning to the sources or causes of beam obstruction, it can be quickly derived from the diagram that one of the main causes of beam obstruction (see Fig. 7a) is an obstacle that prevents the serving beam from propagating between the gNB and the UE and vice versa. Another main cause of beam obstruction (see Fig. 7b) is the UE moving relative to the gNB, resulting in the beam propagating in an inappropriate direction.

[0037] With this understanding, however, it can be appreciated that both of these major causes do not necessarily affect a downlink and uplink serving beam pair in the same way: In other words, if downlink communications are served on a beam in a direction other than that of the beam serving the uplink communications, it is quite possible that only one of the downlink and uplink beams suffers from beam obstruction.

[0038] Furthermore, when the distance between the obstacle and the UE is closer than the distance between the obstacle and the gNB, it may be the case that the uplink serving beam does not suffer from beam obstruction at close distances, but the downlink serving beam suffers from beam obstruction at farther distances.

[0039] Thus, it was readily recognized that there is a need for a beam failure recovery procedure, i.e., in situations where a downlink serving beam suffers from beam failure but the uplink serving beam still operates, in which a beam failure recovery request may be sent by the UE indicating an alternative (i.e., candidate) downlink beam for serving downlink communications.

[0040] The present disclosure provides a robust mechanism that enables a UE to respond to detection of a downlink beam failure event while reducing the amount of uplink radio resources that are blocked (allocated) for initiation of a beam failure recovery procedure, which is particularly suited for the proposed scenario in 3GPP NR when the beam failure recovery procedure relies on contention-free physical random access channel (PRACH) or contention-free physical uplink control channel (PUCCH) resources.

[0041] As is evident from this scenario, using contention-free PRACH or PUCCH resources for beam failure recovery procedures has advantages as well as disadvantages. Relying on contention-free resources on the uplink beam facilitates quick access by the UE to signal to the gNB that a beam failure event has been detected for the downlink beam. However, since it is uncertain when and under what directional conditions a radio link failure will be detected, the UE will have to be assigned all potentially available combinations for the UE to successfully initiate a beam failure recovery procedure.

[0042] This uncertainty results in each UE blocking a huge amount of dedicated uplink radio resources, especially in the case of the proposed contention-free physical random access channel (PRACH) or contention-free physical uplink control channel (PUCCH) resources. In view of the expected large number of UEs to be served by each gNB, this results in a large overhead of dedicated uplink radio resources that cannot be used for other purposes. This approach is therefore in clear conflict with existing design principles, where resources (especially scarce resources) are allocated (and therefore blocked) by the gNB only if they are needed and expected to be used in the UE in the near future.

[0043] The present disclosure provides a solution to mitigate these drawbacks, yet still allowing beam failure recovery procedures to be initiated in a robust manner, i.e., by making more efficient (context-dependent) use of dedicated uplink radio resources.

[0044] In general, the present disclosure provides devices and methods for initiating beam failure recovery procedures utilizing dedicated uplink radio resources not for all potentially available constellations, but only for relevant constellations that are (actually) expected to be encountered when a beam failure is detected. Since the relevant constellations may change over time, the dedicated uplink radio resources can be flexibly (re)assigned without incurring large signaling overhead.

[0045] For this purpose, it is proposed that the gNB restrictively but efficiently assigns uplink radio resources dedicated to the initiation of beam failure recovery procedures to the UE, i.e. by restricting the signaling of beam failure recovery signals to only a subset of all potentially available uplink beams that can be exclusively or non-exclusively assigned by the gNB to the UE. After restricting the individual uplink radio resources to a subset, e.g. one, two or three uplink beams out of a maximum of ten potentially available uplink beams, blocking these individual uplink radio resources is much less likely to impair the operation of the wireless communication system.

[0046] Notably, this contrasts effectively with an alternative approach to beam failure recovery procedures in which the beam failure recovery signal is transmitted in a full beam-sweeping manner (i.e., successively utilizing all potentially available uplink beams for transmitting the beam failure recovery signal), which would require allocating (and therefore blocking) dedicated uplink radio resources on all potentially available uplink beams.

[0047] In addition, it is proposed to adopt an efficient mechanism for (re)allocating these dedicated uplink radio resources, which can ensure that the gNB allocates only the most suitable dedicated uplink radio resources to the UE. For each (real) situation, the UE must still be able to initiate a beam failure recovery procedure upon detection of a downlink beam failure event. In this context, it may be advantageous to reduce blocking if the (re)allocation of dedicated uplink radio resources expires after a given period of time or if the (re)allocation of dedicated uplink radio resources is updated periodically.

[0048] 1 illustrates a block diagram of a wireless communication system including a mobile terminal 110 and a base station 160 that communicate with each other using at least one of multiple downlink beams and at least one of multiple uplink beams. In other words, communication between the mobile terminal 110 and the base station 160 is carried out over a downlink and uplink (serving) beam pair 150.

[0049] In the context of this disclosure, the term beam should be interpreted as having a specific (predetermined) directivity and / or coverage. Each uplink beam and each downlink beam has a different directivity and / or coverage, so that the transmitter can transmit a signal to a receiver at a different (spatial) location. In other words, each uplink beam and each downlink beam has a different spatial parameter (e.g., gain and / or beam width).

[0050] The mobile terminal 110 comprises a transceiver 120 that, in operation, receives from a base station 160 an assignment of dedicated uplink radio resources for sending a beam failure recovery signal for a beam failure recovery (BFR) procedure. The mobile terminal 110 further comprises a processor 130 that, in operation, detects a downlink beam failure event and, in response, initiates a beam failure recovery procedure. The beam failure recovery procedure includes the transceiver 120 transmitting a beam failure recovery signal to the base station 160 using a dedicated uplink radio resource from the assignment.

[0051] In particular, the dedicated uplink radio resources assigned to the mobile terminal 110 restrict transmission to a subset of multiple uplink beams that may be exclusively assigned by the base station 160. This ensures that only a subset, and not all, of the dedicated uplink radio resources are used in an exclusive manner by another mobile terminal.

[0052] Alternatively, the dedicated uplink radio resources assigned to the mobile terminal 110 restrict transmission to a subset of multiple uplink beams that may be assigned in a non-exclusive manner by the base station 160. Again, this ensures that only a subset, and not all, of the dedicated uplink radio resources are used in a non-exclusive manner by another mobile terminal.

[0053] In the context of this disclosure, a distinction is made between exclusive and non-exclusive allocation of dedicated uplink radio resources on an uplink beam. An exclusive allocation should be interpreted in the sense that the same dedicated uplink radio resources, including the same uplink beam, are not assigned to any other mobile terminal for the same time period. In contrast, a non-exclusive allocation should be interpreted in the sense that the same dedicated uplink radio resources, including the same uplink beam, may be assigned to other mobile terminals for the same time period.

[0054] The base station 160 comprises a transceiver 170 that, in operation, transmits to the mobile terminal 110 an allocation of dedicated uplink radio resources for a beam failure recovery (BFR) procedure for the mobile terminal 110 to send a beam failure recovery signal. Moreover, the base station 160 comprises a processor 180 that, in operation, performs the beam failure recovery procedure in response to the transceiver 170 receiving from the mobile terminal 110 a beam failure recovery signal using the dedicated uplink radio resources from the allocation.

[0055] Notably, again, the dedicated uplink radio resources assigned by the base station 160 restrict transmission to a subset of the multiple uplink beams that may be exclusively assigned to the mobile terminal 110. This ensures that only a subset, and not all, of the dedicated uplink radio resources are used in an exclusive manner by another mobile terminal.

[0056] Alternatively, the dedicated uplink radio resources assigned by the base station 160 restrict transmission to a subset of the multiple uplink beams that may be assigned in a non-exclusive manner to the mobile terminal 110. Again, this prevents only a subset, and not all, of the dedicated uplink radio resources from being used in a non-exclusive manner by another mobile terminal.

[0057] The initiation of the beam failure recovery procedure, in particular the allocation of dedicated uplink radio resources, is described in further detail with respect to Fig. 2. In particular, this figure presents the present disclosure in the context of an exemplary four-step beam failure recovery procedure. Notably, the present disclosure should not be construed as limiting in any respect.

[0058] 2, a mobile terminal 110 (also referred to as a UE) and a base station 160 (also referred to as a gNB) communicate in a wireless communication network using a pair of downlink and uplink (serving) beams 150. In particular, the downlink and uplink beam pair is one of multiple downlink beams and one of multiple uplink beams that can be configured in the mobile terminal 110 by the base station 160.

[0059] For beam failure recovery procedures, dedicated uplink radio resources are allocated to the mobile terminal 110 by the base station 160 (FIG. 2 S01). As mentioned before, the allocation of these uplink radio resources is dedicated for use with beam failure recovery signaling. In other words, such dedication of the uplink radio resources can prevent the uplink radio resources from being used in a different context. In any case, dedicating the uplink radio resources allows the base station 160 to identify and initiate the relevant functions (i.e., initiate the beam failure recovery procedure) when it receives beam failure recovery signaling on the dedicated uplink radio resources.

[0060] Additionally, the allocation of dedicated uplink radio resources may include instructions from the base station 160 instructing the mobile terminal 110 to include an identification (e.g., a Radio Network Terminal Identifier (RNTI)) of the mobile terminal 110 in subsequent messages of the beam failure recovery procedure for purposes of the beam failure recovery procedure. This may be particularly advantageous when dedicated uplink radio resources are assigned non-exclusively rather than exclusively to the mobile terminal 110, as will be discussed further below.

[0061] The mobile terminal 110 then detects a downlink (also referred to as DL) beam failure event, i.e., beam failure for the downlink (serving) beam of the beam pair 150 through which the base station 160 and the mobile terminal 110 communicate with each other. The two main causes of beam failure, i.e., obstructions and UE movement, have already been discussed above.

[0062] Furthermore, there are many ways for the mobile terminal 110 to detect a beam failure event for a downlink (serving) beam, for example, by measuring the reference signal received power RSRP or the reference signal received quality RSRQ on this (serving) downlink beam and determining that the measurement falls below a given threshold. Other ways for the mobile terminal 110 to detect a beam failure event for a downlink (serving) beam may include the expiration of a given (countdown) timer, i.e., when periodic control data and / or user data are not received within a time period defined by the given (countdown) timer.

[0063] In this regard, a beam failure event may be understood as an event that may be detected in the mobile terminal 110 directly (ie, by measurement) or indirectly (ie, by the expiration of a timer).

[0064] In response to the detection of the downlink beam failure event, the mobile terminal 110 transmits a beam failure recovery signal to the base station 160 (FIG. 2 S02). In particular, the beam failure recovery signal uses the assigned dedicated uplink radio resource mentioned above. As already mentioned before, the dedicated uplink radio resource is used so that the base station 160 can immediately identify and initiate the relevant function (i.e., initiate the beam failure recovery procedure).

[0065] If the number of uplink beams is greater than the number of uplink beams that form the subset through which the fault recovery signal is transmitted, the mobile terminal 110 may transmit this signal in a beam-sweeping manner, which is however more efficient than a beam fault recovery signal transmitted in a full (not partial) beam-sweeping manner due to the restriction to a subset of all uplink beams that may be available.

[0066] Most importantly, the assignment of the dedicated uplink radio resources restricts the transmission to a subset of the potentially available uplink beams. This restriction to the subset of uplink beams is enforced regardless of whether the dedicated uplink radio resources are assigned exclusively or non-exclusively to the mobile terminal 110 by the base station 160. The dedicated uplink radio resources may be restricted to a subset, e.g., one, two, or three uplink beams, such as up to ten, of the potentially available uplink beams.

[0067] However, after receiving the beam failure recovery signal, the base station 160 is not (yet) ready to complete the beam failure recovery procedure for the downlink beam in which the mobile terminal 110 detected the mobile beam failure. As previously discussed, the beam failure recovery procedure also includes transmitting messages that enable the mobile terminal 110 to explicitly or implicitly indicate to the base station 160 alternative (candidate) downlink beams that can be used to recover from the beam failure.

[0068] For this purpose, the base station 160 transmits a beam failure recovery control signal to the mobile terminal 110 (FIG. 2, S03). This control signal most likely includes an uplink grant that enables the mobile terminal 110 to transmit in an alternative (candidate) downlink beam. However, this control signal is not limited to only an uplink grant.

[0069] Additionally, the control signal may also include instructions from the base station 160 instructing the mobile terminal 110 to include an identity (e.g., a Radio Network Terminal Identifier (RNTI)) of the mobile terminal 110 in subsequent messages of the beam failure recovery procedure for purposes of the beam failure recovery procedure. This may be particularly advantageous when dedicated uplink radio resources are assigned non-exclusively rather than exclusively to the mobile terminal 110, as will be discussed further below.

[0070] The mobile terminal 110 transmits a beam failure recovery request to the base station 160 by referring to the received uplink grant (FIG. 2, S04). This request includes at least one of explicit or implicit information regarding identification of the mobile terminal 110 and new downlink beam candidate information for the base station 160, and explicit or implicit information regarding identification of the mobile terminal 110 and whether or not a new downlink beam candidate exists.

[0071] Using this information, the base station 170 can recover from a beam failure on a downlink beam, i.e., by reverting to one of the explicitly or implicitly indicated new downlink beam candidate information. This information on new downlink candidate beams can be obtained, for example, from downlink reference signals continuously transmitted by the base station 160 on all potentially available downlink beams. The mobile terminal 110 can identify new downlink beam candidates by measuring these downlink reference signals.

[0072] In response to the beam failure recovery request, the base station 160 transmits a beam failure recovery response to the mobile terminal 110 (FIG. 2, S05). This response is a response to the beam failure recovery request previously transmitted by the mobile terminal 110. In particular, only when this response is received by the mobile terminal 110 does the mobile terminal 110 know that the information indicating the new downlink beam candidate has been successfully received and put into action.

[0073] In particular, successful beam failure recovery is possible even when the beam failure recovery request sent from the mobile terminal 110 to the base station 160-170 does not include any new downlink beam candidate information for the base station 160 (instead, the request includes information that no new downlink beam candidate exists). In this case, a new downlink (serving) beam is determined by the base station 160-170 itself.

[0074] In particular, when the mobile terminal 110 has not proposed any new downlink beam candidates, the base station 160 may instead decide on which downlink beam to restore its communication with the mobile terminal 110. For this purpose, the base station may refer to reports on measurements of downlink reference signals (e.g., CSI-RS in 3GPP NR terminology) (previously) obtained from the mobile terminal 110.

[0075] After determining the new downlink beam, the base station 160 must also inform the mobile station 110 of the new downlink beam. Only then can both the base station 160 and the mobile terminal 110 return to the same new pair of the new downlink (serving) beam and the current uplink (serving) beam. Therefore, after determining the new downlink beam, the base station 160 also includes information about the new downlink beam in the beam failure recovery response to the mobile terminal 110.

[0076] For example, the beam failure recovery response from the base station 160 may mark the point in time when the mobile terminal 110 switches communication to a new beam pair that includes the new downlink beam as the new downlink (serving) beam. In yet another example, if there is no beam failure response from the base station 160 within a given period of time, the mobile terminal 110 will determine that the beam failure recovery procedure was not successful and will therefore signal a radio link failure event to higher layers.

[0077] In summary, a description of the four-step beam failure recovery procedure is provided in conjunction with Fig. 2. That is, steps S02, S03, S04, and S05 of the figure resemble four individual steps of the procedure. In other words, step S01 of the figure is more preparatory in nature and in this sense is not considered part of the four-step beam failure recovery procedure.

[0078] Regardless of this complete presentation of the beam failure recovery procedure, it is emphasized again that the present disclosure is focused on proposing a robust and efficient mechanism for initiating (not terminating) the beam failure recovery procedure. Due to this narrow focus, steps S03, S04, and S05 of the figure must be considered as options to achieve this effect. Whether or not the procedure is successfully completed does not make the initiation of the beam failure recovery procedure more robust or efficient and is in no way relevant to the focus described herein.

[0079] Exclusive and Non-Exclusive Allocations As mentioned above, the base station 160 can assign dedicated uplink radio resources to the mobile terminal 110 in an exclusive or non-exclusive manner. This may seem trivial, but as will become clear below, it has a large impact on the beam failure recovery procedure.

[0080] Considering the exclusive allocation, after the base station 160 receives the beam failure recovery signal in S02 in Fig. 2, it knows exactly which mobile terminal it should send the control signal to in S03 in Fig. 2. Since the dedicated uplink radio resource is exclusively assigned to only one mobile terminal 110, the base station 160 can derive from the dedicated uplink radio resource the mobile terminal 110 that has been using it. Therefore, the base station 160 can send the subsequent control signal 110 to this mobile terminal 110 as well.

[0081] Considering a non-exclusive allocation, the base station 160, after receiving the beam failure recovery signal in S02 in Fig. 2, does not (and therefore) know to which mobile terminal it has to send the control signal in S03 in Fig. 2. For this purpose, it is proposed that the base station 160 examines the context in which the beam failure recovery signal is received and tries to deduce from which mobile terminal the signal was received. As will be immediately clear, if only a few mobile terminals, e.g. two mobile terminals, are assigned dedicated uplink radio resources, even if non-exclusively, the context makes it easier to determine from which mobile terminal the signal was received.

[0082] One possibility is associated with only a subset of all potentially available uplink beams being assigned to the base station as individual uplink radio resources for beam failure recovery signals, where, for example, one uplink beam is assigned to each of, say, two mobile terminals as a subset in a non-exclusive manner, reducing the number of mobile terminals that may be the source of a signal.

[0083] However, for this possibility, the base station still has to predict, based on the context, e.g., on the most recent beam status update, which mobile terminals out of the reduced number of mobile terminals have used the non-exclusively assigned dedicated uplink radio resources and (actually) transmitted a beam failure recovery signal on said resources. It will already be seen here that the subset still allows the base station to better identify the mobile terminal that is the source of the signal.

[0084] If the base station is unable or fails to predict (with reasonable certainty) which mobile terminal the signal originates from, the base station may decide to transmit the beam failure recovery control signal of S02 in Fig. 2 to more than one mobile terminal. In the above example, it may decide to transmit to two mobile terminals, both of which are assigned the same dedicated uplink radio resource in a non-exclusive manner.

[0085] In this case, as discussed above, it is advantageous if the mobile terminal is instructed to include its identification information in the subsequent message, i.e., the beam failure recovery request (i.e., in S04 of FIG. 2). From this identification information included in the beam failure recovery request, the base station can infer the correct mobile terminal for which the beam failure recovery procedure should be performed. For other mobile terminals that were not predicted correctly, the base station will stop the beam failure recovery procedure.

[0086] Another possibility lies in that the beam failure recovery signal can be transmitted on a dedicated uplink radio resource which itself requires additional control information to be added, which the base station can use to identify the mobile terminal as the source of the signal.

[0087] This is the case, for example, when the beam failure recovery signal is transmitted via a Physical Uplink Control Channel (PUCCH), for which the 3GPP NR specification specifies that the mobile terminal not only transmits Uplink Control Information (UCI) of a given format, but also appends to it a transmission demodulation reference signal DM-RS that is uniquely assigned to each mobile terminal.

[0088] Therefore, when the base station receives a beam failure recovery signal in the UCI on the PUCCH, it can identify the mobile terminal that transmitted this signal from the DM-RS. Again, the context is crucial for the base station to identify the mobile terminal so as to direct the subsequent beam failure recovery control signal to the correct mobile terminal in S03 of FIG. 2.

[0089] Now, in Figure 3, a 3GPP NR deployment scenario is assumed. More specifically, the figure illustrates the initiation of a beam failure recovery procedure in the context of a four-step beam failure recovery procedure, where the UE and the gNB communicate via a downlink beam and uplink beam pair. Again, the downlink and uplink (serving) beam pair is one of multiple downlink beams and one of the uplink beam pairs that can be configured in the UE by the gNB.

[0090] For the beam failure recovery procedure, a dedicated uplink radio resource is allocated to the UE by the gNB (FIG. 3 S11). As mentioned before, the allocation of the uplink radio resource is dedicated to be used with the beam failure recovery signaling. For this purpose, the gNB sends a Radio Resource Configuration (RRC) Connection Reconfiguration message to the UE. Alternatively, the RRC Connection Setup message may be used for the allocation purpose.

[0091] In another example, dedicated uplink radio resources are assigned to the UE via a downlink medium access control (MAC) control element (CE), a downlink control information (DCI), and a control protocol data unit (PDU) of the Packet Data Convergence Protocol (PDCP). In particular, the PDCP control PDU also has the advantage of slightly lower overhead compared to the RRC connection reconfiguration message. This can therefore result in a further increase in signaling speed.

[0092] Apart from allocation via a single message, the allocation can also be achieved by a first message configuring the dedicated uplink radio resources and a second subsequent message activating the configuration, in which case the UE receives the configuration of the dedicated uplink radio resources from the gNB via an RRC connection setup or reconfiguration message and (subsequently) receives activation of the dedicated uplink radio resources from the configuration via one of a MAC CE, a DCI and a PDCP control PDU.

[0093] This message may contain a reference to a dedicated uplink radio resource of the Physical Random Access Channel (PRACH), i.e. one of the contention-free resources, preferably a contention-free preamble sequence with time and frequency reference on the uplink beam.

[0094] Only contention-free preamble sequences are mentioned because in 3GPP NR, the gNB only (actively) allocates these types of preamble sequences to the UE. In contrast, for non-contention-free (contention-based) preamble sequences, the gNB cannot distinguish whether these sequences are used by the UE for initiating a beam failure recovery procedure or whether a (conventional) time alignment procedure is being performed. This rules out any use of non-contention-free (contention-based) preamble sequences as dedicated uplink radio resources for initiating a beam failure recovery procedure.

[0095] For example, assuming the configuration shown in Figure 5, the message may include a reference to a PRACH with preamble sequence index S1, time reference T1, and frequency reference F1 on uplink beam #1. This allocates a dedicated uplink radio resource to the UE that the UE can use to initiate a beam failure recovery procedure. In this example, the time reference T1 may be understood as an offset indicating a slot offset in time from the respective radio frame boundary. Additionally, the frequency reference F1 may be understood as an index of a resource block.

[0096] Alternatively, the message may also include a reference to a dedicated uplink radio resource of the Physical Uplink Control Channel (PUCCH), i.e. a reference to a contention-free uplink control information (UCI) of a given format with time and frequency reference on an uplink beam. For example, assuming the configuration shown in Figure 6, the message may include a reference to a PUCCH with time reference T1 and frequency reference F1 on beam #1.

[0097] In both instances, i.e., contention-free PRACH or PUCCH, dedicating uplink radio resources can prevent them from being used in different contexts. In either case, dedicating uplink radio resources allows the gNB to identify and initiate relevant functions (i.e., initiate beam failure recovery procedures) upon receiving beam failure recovery signaling on a dedicated uplink radio resource.

[0098] In response to the detection of a beam failure event, the UE transmits a beam failure recovery signal to the gNB (FIG. 3 S12). In particular, the beam failure recovery signal uses a pre-allocated dedicated uplink radio resource, i.e., a contention-free PRACH or PUCCH. As already mentioned before, the dedicated uplink radio resource is used so that the gNB can immediately identify and initiate the relevant functions (i.e., initiate the beam failure recovery procedure). In particular, the PRACH resource implicitly indicates a scheduling request (SR), whereas the UCI of a given format may include the SR explicitly or implicitly.

[0099] Upon receiving a dedicated PRACH or PUCCH resource, the gNB initiates a beam failure recovery procedure. As part of this procedure, the gNB transmits a Physical Downlink Control Channel (PDCCH) Downlink Control Information (DCI) containing an uplink grant (Figure 3 S13). The DCI on the PDCCH also includes a Cyclic Redundancy Check (CRC) field scrambled with the UE's Radio Network Temporary Identifier (RNTI). This allows the UE to detect whether the gNB intended the DCI for the UE to be used in the beam failure recovery procedure.

[0100] Assuming that the UE has received the uplink grant, the mobile terminal 110 sends a beam failure recovery request in the form of an uplink MAC control element to the gNB (FIG. 3 S14). The request includes at least one of explicit or implicit information regarding the identification of the UE and new downlink beam candidate information to the gNB, and explicit or implicit information regarding the identification of the UE and whether new downlink beam candidates exist.

[0101] Finally, in response to the beam failure recovery request, the gNB transmits a beam failure recovery response in the form of a PDCCH DCI including an acknowledgement (e.g., a response acknowledgement) to the UE (FIG. 3 S15). This response is a response to the beam failure recovery request previously transmitted by the UE. In particular, only after this response is received by the UE does the UE know that the information indicating the new downlink beam candidate has been successfully received and put into action.

[0102] Alternatively, if the mobile terminal did not propose any new downlink beam candidates, the gNB may include information about the new downlink beam in the beam failure recovery response to the UE. Depending on the number of potentially available downlink beams, this information may also be carried in the response in the form of a PDCCH DCI. And both the gNB and the UE can then revert to the same pair of new downlink (serving) beam and current uplink (serving) beam, thereby successfully completing the beam failure recovery procedure.

[0103] Next, in FIG. 4, another 3GPP NR deployment scenario is assumed. More specifically, the figure illustrates the initiation of a two-step beam failure recovery procedure in the context of a UE and a gNB communicating via a downlink and uplink (serving) beam pair. Again, the downlink and uplink (serving) beam is one of multiple downlink beams and one of a pair of uplink beams that can be configured for the UE by the gNB. Notably, the two-step beam failure recovery procedure is restricted to only dedicated uplink radio resources from the Physical Uplink Control Channel (PUCCH).

[0104] This procedure is very similar to the four-step beam failure recovery procedure shown in the previous figure. The transmission between the UE and the gNB for the allocation of dedicated uplink resources (Fig. 4 S21) and the transmission of the beam failure recovery response (Fig. 4 S23) correspond to the respective steps in the previous procedure. Moreover, the only difference is in the format of the beam failure recovery signal (Fig. 4 S22).

[0105] Here, it is utilized that the uplink control information (UCI) on the PUCCH depending on a given format can contain a sufficient number of bits, for example 1 or 2 bits in PUCCH format 1a / 1b, 20 coded bits in PUCCH format 2 / 2a / 2b, or even 48 coded bits in PUCCH format 3.

[0106] Therefore, in this example, it is proposed that the UE not only transmits UCI of the PUCCH, which is similar to a dedicated uplink radio resource, as a beam failure recovery signal to the gNB, but also conveys at least one of the following beam failure recovery request information, i.e., explicit or implicit information regarding identifying the UE and new downlink beam candidate information to the gNB, and explicit or implicit information regarding identifying the UE and whether a new downlink beam candidate exists.

[0107] A robust allocation mechanism. As previously discussed, the present disclosure focuses on robust mechanisms that enable base stations to respond to detection of downlink beam failure events while reducing the amount of uplink radio resources that are blocked (allocated) for initiation of beam failure recovery procedures. However, reducing the amount of uplink radio resources requires, in one example, that the base station carefully select the individual uplink radio resources that are allocated.

[0108] For this purpose, the base station may determine a subset of all potentially available uplink beams based on the most recent quality and / or power measurements. In this context, it may be advantageous to refer to reference signals signaled either on all potentially available downlink or uplink beams. From this, the base station can then select the subset with reference to the measured quality and / or power values.

[0109] Assuming a 3GPP NR deployment scenario, the base station may refer to all potentially available uplink reference signals, preferably Sounding Reference Signals (SRS), transmitted by the mobile terminal on potentially available or at least the most relevant uplink beams for the determination of the subset of uplink beams.

[0110] For this uplink beam subset decision, the base station may also refer to reports (preferably Channel Status Information (CSI) reports) made by the mobile terminal on measurements of downlink reference signals (preferably CSI-RS) transmitted by the base station on all potentially available downlink beams.

[0111] Either method can ensure that the subset of uplink resources meets the objective of allowing the mobile terminal to respond robustly to the detection of a downlink beam failure event (i.e., without the risk that the base station will not be able to receive the beam failure recovery signal).

[0112] Mobility State In one exemplary implementation, the focus is on an efficient mechanism for allocating individual uplink radio resources on a subset of uplink beams. To achieve this, the base station varies the number of uplink beams that form the subset from which individual uplink radio resources are allocated to the mobile terminal. In particular, by varying the number of uplink beams, the base station strives to reflect the varying (actual) situation at the mobile terminal (e.g., minor or major position changes).

[0113] As can be seen from the above discussion, one of the main causes of beam failure is the mobility (i.e., varying spatial location) of mobile terminals. If a mobile terminal changes its location at a high rate, it is difficult for the base station to predict which will be the most suitable individual uplink radio resource in the event of downlink beam failure. In other words, when the location of a mobile terminal changes rapidly, it becomes difficult for the base station to allocate individual uplink radio resources on a subset of uplink beams that still meets the requirements of a reliable beam failure recovery procedure.

[0114] With these difficulties in mind, the present disclosure proposes that the base station maintain a mobility state for each mobile terminal. The mobility state distinguishes between a small number of location changes and a large number of location changes during a given time period for each mobile terminal. In other words, based on the mobility state, the base station can know whether location changes have (in the past) occurred at a low or high rate for each mobile terminal.

[0115] This mobility state is then used by the base station to predict the number of uplink beams in the subset, thereby ensuring a reliable beam failure recovery procedure. Thus, the number of uplink beams forming a subset of all potentially available uplink beams may be determined by the base station corresponding to the mobility state of the respective mobile terminal.

[0116] In one example, i.e., for a mobile terminal having a mobility state corresponding to a low rate of location change, the base station may reasonably predict that the mobile terminal's location will not change frequently in the future, and therefore it is sufficient to allocate dedicated uplink radio resources on a small number of uplink beams (e.g., one or two uplink beams). In a different example, i.e., for a mobile terminal having a mobility state corresponding to a high rate of location change, the base station may in contrast reasonably predict that the mobile terminal's location will change frequently in the future, and therefore it becomes necessary to allocate dedicated uplink radio resources on a large number of uplink beams (e.g., three or more).

[0117] As an example, the mobility state and therefore the position change rate can be determined by both the base station and the mobile terminal based on the number of reconfiguration commands (beam steering) for downlink beams sent from the base station to the mobile terminal. Even though the reconfiguration of the downlink beams is performed in the base station, the mobile terminal will take this into account in the form of a reconfiguration command, i.e. a reconfiguration command instructing the mobile terminal to reconfigure its beam pair to include the new downlink beam.

[0118] Also by way of example, the mobility state and thus the location change rate can be determined based on the number of location changes, which are preferably determined from positioning measurements in the mobile terminal over a given period of time and then signaled to the base station. In other words, the mobile terminal itself determines its location change rate by performing positioning measurements, including for example checking if there are new downlink beams, and then signals this location change rate to the base station.

[0119] In both cases, the mobility state facilitates the selection of a sufficient number of uplink beams for the mobile terminal to respond robustly to the detection of a downlink beam failure event (i.e., without the risk that the base station will not be able to receive the beam failure recovery signal).

[0120] Recentness of allocation In another exemplary implementation, the focus is again on an efficient mechanism for allocating dedicated uplink radio resources on a subset of uplink radio beams. To achieve this, each allocation of dedicated uplink radio resources to a mobile terminal has an expiration time. This can ensure the freshness of the allocation of dedicated uplink radio resources as well as that resources are blocked for only a limited amount of time.

[0121] As is evident from the above discussion, a base station allocating dedicated uplink radio resources to a mobile station cannot always cope well with changing (real-world) conditions at the mobile terminal (e.g., location change): an allocation on an uplink beam subset may be valid for a mobile terminal at one location, but not for the same mobile terminal after it has moved to another location.

[0122] Therefore, the present disclosure proposes that each assignment is only valid for a given (short) period of time and, in exceptional cases, until a new (re)assignment is received. In other words, regardless of whether a mobile station receives an exclusive or non-exclusive assignment of dedicated uplink resources for a beam failure recovery procedure from a base station, these resources are blocked only for a limited amount of time.

[0123] This can be guaranteed by the base station 160 when it transmits an assignment to the mobile station 110 (see FIG. 2 S01) that also indicates the time period for which the dedicated uplink radio resource is valid. For example, together with the assignment of the dedicated uplink radio resource, both the base station and the mobile terminal can start a countdown timer. When this timer expires, the base station as well as the mobile terminal know that the dedicated uplink radio resource is no longer available and therefore cannot be blocked any more.

[0124] However, to avoid the case of no allocation or only a stale allocation, the mobile terminal may send an indication to the base station for the base station to (re)initiate allocation of dedicated uplink radio resources for the beam failure recovery procedure.

[0125] Assuming a NR deployment scenario, the indication to (re)initiate the allocation of dedicated uplink radio resources is either an (implicit) Channel Status Information (CSI) report signaling the quality or power of the serving downlink beam below a given threshold, or a dedicated transmission (preferably in the form of either an RRC message or an uplink MAC CE) signaling an explicit request to (re)initiate the allocation of dedicated uplink radio resources.

[0126] In summary, revocation of the allocation of dedicated uplink radio resources further improves the efficient use of these resources: revocation of the allocation of resources not only promotes the up-to-dateness that is anyway necessary for the allocation to reflect the actual (current) situation of the mobile station, but also prevents the resources from being blocked, which is particularly advantageous when these resources are allocated in an exclusive manner.

[0127] The present disclosure can be realized by software, hardware, or software in cooperation with hardware. Each functional block used in the description of each embodiment above can be partially or entirely realized by an LSI such as an integrated circuit, and each process described in each embodiment can be partially or entirely controlled by the same LSI or a combination of LSIs. The LSI may be formed individually as a chip, or one chip may be formed to include some or all of the functional blocks. The LSI may have data inputs and outputs coupled thereto. The LSI here may be called an IC, a system LSI, a super LSI, or an ultra LSI depending on the degree of integration. However, the technique of implementing the integrated circuit is not limited to an LSI, and may be realized using a dedicated circuit, a general-purpose processor, or a dedicated processor. In addition, an FPGA (field programmable gate array) that can be programmed after the LSI is manufactured, or a reconfigurable processor that can reconfigure the connections and settings of circuit cells arranged inside the LSI may be used. The present disclosure can be realized as digital processing or analog processing. The functional blocks may also be integrated using future integrated circuit technologies if they replace LSI as a result of advances in semiconductor technology or other derived technologies. Biotechnology may also be applied.

[0128] According to a first aspect, a mobile terminal is proposed for communicating with a base station in a mobile communication system using at least one of a plurality of downlink beams and at least one of a plurality of uplink beams, each of the downlink beam and the uplink beam having a different directivity and / or coverage. The mobile terminal comprises a transceiver that, in operation, receives an allocation of dedicated uplink radio resources for transmitting a beam failure recovery signal for a beam failure recovery (BFR) procedure, and a processor that, in operation, detects a downlink beam failure event and responsively initiates a beam failure recovery procedure, the beam failure recovery procedure including the transceiver transmitting the beam failure recovery signal using the dedicated uplink radio resources from the allocation. The dedicated uplink radio resources restrict the transmission to a subset of the plurality of uplink beams that can be exclusively assigned by the base station to the mobile terminal.

[0129] According to a second aspect, which can be combined with the first aspect, a subset of the multiple uplink beams is exclusively assigned to a mobile terminal based on uplink reference signals (preferably Sounding Reference Signals (SRS)) transmitted by the mobile terminal on the multiple uplink beams or based on reports (preferably Channel Status Information (CSI) reports) by the mobile terminal on measurements of downlink reference signals (preferably CSI-RS) transmitted by the base station on the multiple downlink beams.

[0130] According to a third aspect, which may be combined with the first or second aspect, the number of uplink beams forming the subset of the multiple uplink beams corresponds to one, two or three uplink beams.

[0131] According to a fourth aspect, which can be combined with one of the first to third aspects, the number of uplink beams forming a subset of the multiple uplink beams corresponds to a mobility state of the mobile terminal, which distinguishes between a low rate of position change and a high rate of position change of the mobile terminal.

[0132] According to a fifth aspect which can be combined with the fourth aspect, the mobility state of the mobile terminal is determined based on the number of reconfiguration commands for downlink beams transmitted by the base station to the mobile terminal over a time period or based on the number of position changes which are preferably determined from positioning measurements in the mobile terminal over a time period and signaled to the base station.

[0133] According to a sixth aspect, which can be combined with one of the first to fifth aspects, in operation, the transceiver additionally receives an indication for a beam failure recovery procedure indicating the number of uplink beams in a subset of a plurality of uplink beams to be used in the beam failure recovery procedure.

[0134] According to a seventh aspect, which can be combined with the first to sixth aspects, an indication of the number of uplink beams in a subset of multiple uplink beams to be used is received in a Radio Resource Configuration (RRC) message, or a Medium Access Control (MAC) control element (CE), or a Downlink Control Information (DCI).

[0135] According to an eighth aspect, another mobile terminal is proposed for communicating with a base station in a mobile communication system using at least one of a plurality of downlink beams and at least one of a plurality of uplink beams, each of the downlink beam and the uplink beam having a different directivity. The mobile terminal comprises a transceiver that, in operation, receives an assignment of dedicated uplink radio resources for transmitting a beam failure recovery signal for a beam failure recovery (BFR) procedure, and a processor that, in operation, detects a downlink beam failure event and responsively initiates a beam failure recovery procedure, the beam failure recovery procedure including the transceiver transmitting the beam failure recovery signal using the dedicated uplink radio resources of the assignment. The dedicated uplink radio resources restrict transmission to a subset of the plurality of uplink beams that can be non-exclusively assigned by the base station to the mobile terminal.

[0136] According to a ninth aspect, which can be combined with the eighth aspect, transmitting a beam failure recovery signal on an individual uplink radio resource on a subset of a plurality of uplink beams that is restricted enables the base station to identify the mobile terminal.

[0137] According to a tenth aspect, which can be combined with the eighth or ninth aspect, when the dedicated uplink radio resource includes a physical uplink control channel (PUCCH), transmitting a demodulation reference signal DM-RS together with a beam failure recovery signal in the PUCCH enables the base station to identify the mobile terminal.

[0138] According to an eleventh aspect, which may be combined with one of the eighth to tenth aspects, the allocation of the dedicated uplink radio resource includes an instruction to the mobile terminal to include identification information of the mobile terminal in a subsequent message of the beam failure recovery procedure.

[0139] According to a twelfth aspect, which can be combined with the first to eleventh aspects, the dedicated uplink radio resource corresponds to one of a contention-free resource of a physical random access channel (PRACH) (preferably a contention-free preamble sequence including a time and frequency reference) and a contention-free resource of a physical uplink control channel (PUCCH) (preferably an uplink control information (UCI) including a time and frequency reference).

[0140] According to a thirteenth aspect which may be combined with one of the first to twelfth aspects, the allocation of dedicated uplink radio resources is received via one of a Radio Resource Configuration (RRC) connection reconfiguration or an RRC connection setup message, a downlink medium access control (MAC) control element (CE), a downlink control information (DCI), and a Packet Data Convergence Protocol (PDCP) control protocol data unit (PDU).

[0141] According to a fourteenth aspect which may be combined with one of the first to twelfth aspects, the allocation of the dedicated uplink radio resources includes, during operation of the transceiver, receiving a configuration of the dedicated uplink radio resources via an RRC connection setup or reconfiguration message and an activation of the dedicated uplink radio resources from the configuration via one of a MAC CE, a DCI, and a PDCP control PDU.

[0142] According to a 15th aspect, which may be combined with one of the 1st to 14th aspects, an allocation of dedicated uplink radio resources is valid either for a period of time or until a new allocation is received.

[0143] According to a sixteenth aspect which may be combined with one of the fifteenth aspects, a time period during which an assignment of dedicated uplink resources is valid is indicated in the assignment.

[0144] According to a 17th aspect, which may be combined with one of the 1st to 16th aspects, the transceiver, in operation, transmits an indication for a base station to (re)initiate allocation of dedicated uplink radio resources for a beam failure recovery procedure.

[0145] According to an 18th aspect which may be combined with the 17th aspect, the indication to (re)initiate allocation of dedicated uplink radio resources is a Channel Status Information (CSI) report signaling a quality or power of the serving downlink beam below a threshold, or a dedicated transmission (preferably in the form of either an RRC message or an uplink MAC CE) signaling an explicit request to (re)initiate allocation of dedicated uplink radio resources.

[0146] According to a nineteenth aspect, a method is proposed for initiating a beam failure recovery procedure, implemented by a mobile terminal configured to communicate with a base station in a mobile communication system using at least one of a plurality of downlink beams and at least one of a plurality of uplink beams, each of the downlink beam and the uplink beam having a different directivity and / or coverage. The method includes receiving an assignment of dedicated uplink radio resources for transmitting a beam failure recovery signal for a beam failure recovery (BFR) procedure, detecting a downlink beam failure event and initiating a beam failure recovery procedure in response thereto, the beam failure recovery procedure including transmitting the beam failure recovery signal using the dedicated uplink radio resources from the assignment. The dedicated uplink radio resources restrict the transmission to a subset of the plurality of uplink beams that can be exclusively assigned by the base station to the mobile terminal.

[0147] According to a twentieth aspect which may be combined with the nineteenth aspect, a subset of the multiple uplink beams is exclusively assigned to a mobile terminal based on uplink reference signals (preferably Sounding Reference Signals (SRS)) transmitted by the mobile terminal on the multiple uplink beams or based on reports (preferably Channel Status Information (CSI) reports) by the mobile terminal on measurements of downlink reference signals (preferably CSI-RS) transmitted by the base station on the multiple downlink beams.

[0148] According to a 21st aspect, which may be combined with the 19th or 20th aspects, the number of uplink beams forming the subset of the multiple uplink beams corresponds to one, two, or three uplink beams.

[0149] According to a 22nd aspect, which can be combined with one of the 19th to 21st aspects, the number of uplink beams forming a subset of the multiple uplink beams corresponds to a mobility state of the mobile terminal, which distinguishes between a low rate of position change and a high rate of position change of the mobile terminal.

[0150] According to a 23rd aspect which can be combined with one of the 19th to 22nd aspects, the mobility state of the mobile terminal is determined based on a number of reconfiguration commands for downlink beams transmitted by the base station to the mobile terminal over a time period or based on a number of position changes which are preferably determined from positioning measurements in the mobile terminal over a time period and signaled to the base station.

[0151] According to a 24th aspect, which may be combined with one of the 19th to 23rd aspects, the method includes additionally receiving an indication for the beam failure recovery procedure indicating the number of uplink beams in a subset of a plurality of uplink beams to be used in the beam failure recovery procedure.

[0152] According to a 25th aspect, which may be combined with the 24th aspect, an indication of the number of uplink beams in a subset of multiple uplink beams to be used is received in a Radio Resource Configuration (RRC) message, or a Medium Access Control (MAC) control element (CE), or a Downlink Control Information (DCI).

[0153] According to a 26th aspect, another method is proposed for initiating a beam failure recovery procedure, implemented by a mobile terminal configured to communicate with a base station using at least one of a plurality of downlink beams and at least one of a plurality of uplink beams, each of the uplink and downlink beams having different directivities. The method includes receiving an assignment of dedicated uplink radio resources for a beam failure recovery signal for a beam failure recovery (BFR) procedure, detecting a downlink beam failure event and initiating a beam failure recovery procedure in response thereto, the beam failure recovery procedure including transmitting a beam failure recovery signal using the dedicated uplink radio resources of the assignment. The dedicated uplink radio resources restrict transmission to a subset of the plurality of uplink beams that can be non-exclusively assigned by the base station to the mobile terminal.

[0154] According to a 27th aspect, which may be combined with the 26th aspect, transmitting a beam failure recovery signal on an individual uplink radio resource on a subset of a plurality of uplink beams that is restricted enables the base station to identify the mobile terminal.

[0155] According to a 28th aspect, which can be combined with the 26th or 27th aspects, when the dedicated uplink radio resource includes a physical uplink control channel (PUCCH), transmitting a demodulation reference signal (DM-RS) together with a beam failure recovery signal in the PUCCH enables the base station to identify the mobile terminal.

[0156] According to a 29th aspect, which may be combined with one of the 26th to 28th aspects, the allocation of the dedicated uplink radio resource includes an instruction to the mobile terminal to include identification information of the mobile terminal in a subsequent message of the beam failure recovery procedure.

[0157] According to a 30th aspect, which can be combined with one of the 19th to 29th aspects, the dedicated uplink radio resource corresponds to one of a contention-free resource of a Physical Uplink Control Channel (PUCCH) and an Uplink Control Information (UCI) including a time and frequency reference.

[0158] According to a 31st aspect which may be combined with one of the 19th to 30th aspects, the allocation of dedicated uplink radio resources is received via one of a Radio Resource Configuration (RRC) connection reconfiguration or an RRC connection setup message, a downlink medium access control (MAC) control element (CE), a downlink control information (DCI), and a Packet Data Convergence Protocol (PDCP) control protocol data unit (PDU).

[0159] According to a 32nd aspect which may be combined with one of the 19th to 30th aspects, allocating the dedicated uplink radio resources includes receiving a configuration of the dedicated uplink radio resources via an RRC connection establishment or reconfiguration message and activating the dedicated uplink radio resources from the configuration via one of a MAC CE, a DCI, and a PDCP control PDU.

[0160] According to a 33rd aspect which may be combined with one of the 19th to 32nd aspects, an allocation of dedicated uplink radio resources is valid either for a period of time or until a new allocation is received.

[0161] According to a thirty-fourth aspect which may be combined with the thirty-third aspect, a time period during which an allocation of dedicated uplink resources is valid is indicated in the allocation.

[0162] According to a 35th aspect which may be combined with one of the 19th to 34th aspects, the method includes a step of transmitting an indication for the base station to (re)initiate allocation of dedicated uplink radio resources for a beam failure recovery procedure.

[0163] According to a 36th aspect which may be combined with the 35th aspect, the indication to (re)initiate allocation of dedicated uplink radio resources is a Channel Status Information (CSI) report signaling a quality or power of the serving downlink beam below a threshold, or a dedicated transmission (preferably in the form of either an RRC message or an uplink MAC CE) signaling an explicit request to (re)initiate allocation of dedicated uplink radio resources.

[0164] According to a 37th aspect, a base station is proposed for communicating with a mobile terminal in a mobile communication system using at least one of a plurality of downlink beams and at least one of a plurality of uplink beams, each of the downlink beam and the uplink beam having a different directivity and / or coverage. The base station comprises a processor that, in operation, performs a beam failure recovery procedure, the beam failure recovery procedure including a transceiver receiving from the mobile terminal a beam failure recovery signal using a dedicated uplink radio resource from an assignment. The dedicated uplink radio resource restricts transmission to a subset of the plurality of uplink beams that can be exclusively assigned by the base station to the mobile terminal.

[0165] According to a 38th aspect, another base station is proposed for communicating with a mobile terminal in a mobile communication system using at least one of a plurality of downlink beams and at least one of a plurality of uplink beams, each of the downlink beam and the uplink beam having a different directivity and / or coverage. The base station comprises a processor that, in operation, initiates a beam failure recovery procedure, the beam failure recovery procedure including a transceiver receiving from the mobile terminal a beam failure recovery signal using a dedicated uplink radio resource from an assignment. The dedicated uplink radio resource restricts transmission to a subset of the plurality of uplink beams that can be non-exclusively assigned by the base station to the mobile terminal.

[0166] According to a thirty-ninth aspect, a method is proposed for initiating a beam failure recovery procedure, implemented by a base station configured to communicate with a mobile terminal in a mobile communication system using at least one of a plurality of downlink beams and at least one of a plurality of uplink beams, each of the downlink beam and the uplink beam having a different directivity and / or coverage, comprising initiating the beam failure recovery procedure in response to receiving from the mobile terminal a beam failure recovery signal using dedicated uplink radio resources from an assignment, the dedicated uplink radio resources restricting transmission to a subset of the plurality of uplink beams that can be exclusively assigned by the base station to the mobile terminal.

[0167] According to a fortieth aspect, another method is proposed for initiating a beam failure recovery procedure, implemented by a base station configured to communicate with a mobile terminal in a mobile communication system using at least one of a plurality of downlink beams and at least one of a plurality of uplink beams, each of the downlink beam and the uplink beam having a different directivity and / or coverage, comprising initiating a beam failure recovery procedure in response to receiving from the mobile terminal a beam failure recovery signal using dedicated uplink radio resources from an assignment, the dedicated uplink radio resources restricting transmission to a subset of the plurality of uplink beams that can be non-exclusively assigned by the base station to the mobile terminal.

Claims

1. a transceiver that, in operation, receives a configuration of physical random access channel (PRACH) resources for transmitting beam failure recovery signals; a processor that, during operation, detects a downlink beam failure event and initiates a beam failure recovery procedure (BFR) in response thereto; Equipped with the beam failure recovery procedure includes the transceiver transmitting the beam failure recovery signal using the PRACH resource; The configuration includes a timer indicating a time period for which the PRACH resource is valid, and an indicator indicating a number of PRACH resources in a subset of a plurality of PRACH resources; In operation, the transceiver restricts the PRACH resources used for the transmission to the subset of the plurality of PRACH resources exclusively assigned by a base station to a mobile terminal based on the indicator; When the timer expires as a result of counting down, the PRACH resource cannot be used. Mobile terminal.

2. the subset of the plurality of PRACH resources uplink reference signals or sounding reference signals (SRS) transmitted by the mobile terminal on the multiple uplink beams; and reporting or Channel Status Information (CSI) reporting by the mobile terminal on measurements of downlink reference signals or CSI-RS transmitted by the base station on the multiple downlink beams; and is exclusively assigned to the mobile terminal based on at least one of The mobile terminal of claim 1.

3. the number of PRACH resources forming the subset of the plurality of PRACH resources corresponds to one, two, or three PRACH resources; A mobile terminal according to claim 1 or 2.

4. a number of PRACH resources forming the subset of the plurality of PRACH resources corresponds to a mobility state of the mobile terminal that distinguishes between a low rate of location change and a high rate of location change of the mobile terminal; A mobile terminal according to claim 1 or 2.

5. The mobility state of the mobile terminal is the number of reconfiguration commands for the downlink beam transmitted by the base station to the mobile terminal over a period of time; and a number of location changes determined from positioning measurements in the mobile terminal over a period of time and signalled to the base station; and is determined based on at least one of The mobile terminal according to claim 4.

6. The label is Radio Resource Configuration (RRC) messages; and A Medium Access Control (MAC) Control Element (CE); Downlink Control Information (DCI); and 2. The mobile terminal of claim 1, wherein the signal is received in at least one of:

7. The configuration of the PRACH resources: a Radio Resource Configuration (RRC) Connection Reconfiguration or RRC Connection Setup message; and A downlink Medium Access Control (MAC) Control Element (CE); Downlink Control Information (DCI); and Packet Data Convergence Protocol (PDCP) Control Protocol Data Units (PDUs); receiving the signal via one of A mobile terminal according to any one of claims 1 to 6.

8. the configuration of PRACH resources remains valid until a new configuration is received. The mobile terminal of claim 1.

9. The transceiver, in operation, transmits an indication for the base station to (re)initiate configuration of a PRACH resource for the beam failure recovery procedure, the indication for (re)initiating configuration of the PRACH resource comprising: Channel Status Information (CSI) reports signaling the quality or power of a serving downlink beam below a threshold; a dedicated transmission, either in the form of an RRC message or an uplink MAC CE, signaling an explicit request to (re)initiate the configuration of said PRACH resources; At least one of The mobile terminal of claim 1.

10. receiving a configuration of Physical Random Access Channel (PRACH) resources for transmitting beam failure recovery signals; detecting a downlink beam failure event and initiating a beam failure recovery procedure (BFR) in response thereto, the beam failure recovery procedure including transmitting the beam failure recovery signal using the PRACH resource; the configuration includes a timer indicating a time period for which the PRACH resource is valid and an indicator indicating a number of PRACH resources in a subset of a plurality of PRACH resources; restricting the PRACH resources used for the transmission to the subset of the plurality of PRACH resources exclusively assigned by a base station to a mobile terminal based on the indicator; When the timer expires as a result of counting down, the PRACH resource cannot be used. method.

11. a transceiver configured, in operation, to transmit a configuration of Physical Random Access Channel (PRACH) resources for a mobile terminal to transmit beam failure recovery signals; and a processor that, during operation, performs a beam failure recovery procedure (BFR), the beam failure recovery procedure including the transceiver receiving from the mobile terminal the beam failure recovery signal using the PRACH resource; the configuration includes a timer indicating a time period for which the PRACH resource is valid and an indicator indicating a number of PRACH resources in a subset of a plurality of PRACH resources; the PRACH resources are restricted to the subset based on the indication of the plurality of PRACH resources exclusively assigned by a base station to the mobile terminal; When the timer expires as a result of counting down, the PRACH resource cannot be used. Base station.

12. In operation, transmitting a configuration of Physical Random Access Channel (PRACH) resources for a mobile terminal to transmit a beam failure recovery signal; and performing a beam failure recovery procedure (BFR) during operation, the beam failure recovery procedure including receiving the beam failure recovery signal from the mobile terminal using the PRACH resource; the configuration includes a timer indicating a time period for which the PRACH resource is valid and an indicator indicating a number of PRACH resources in a subset of a plurality of PRACH resources; the PRACH resource is restricted to the subset of the plurality of PRACH resources exclusively assigned by a base station to the mobile terminal based on the indicator; When the timer expires as a result of counting down, the PRACH resource cannot be used. method.

13. An integrated circuit for controlling processing of a mobile terminal, the processing comprising, in operation: receiving a configuration of physical random access channel (PRACH) resources for transmitting beam failure recovery signals; detecting a downlink beam failure event and initiating a beam failure recovery procedure (BFR) in response thereto, the beam failure recovery procedure including transmitting the beam failure recovery signal using the PRACH resource; the configuration includes a timer indicating a time period for which the PRACH resource is valid and an indicator indicating a number of PRACH resources in a subset of a plurality of PRACH resources; limiting the PRACH resources used for the transmission to the subset of the plurality of PRACH resources exclusively assigned to the mobile terminal by a base station based on the indicator; When the timer expires as a result of counting down, the PRACH resource cannot be used. Integrated circuits.

14. An integrated circuit for controlling processing of a base station, the processing comprising, in operation: In operation, transmitting a configuration of Physical Random Access Channel (PRACH) resources for a mobile terminal to transmit a beam failure recovery signal; and performing a beam failure recovery procedure (BFR), the beam failure recovery procedure including receiving the beam failure recovery signal from the mobile terminal using the PRACH resource; the configuration includes a timer indicating a time period for which the PRACH resource is valid and an indicator indicating a number of PRACH resources in a subset of a plurality of PRACH resources; the PRACH resource is restricted to the subset of the plurality of PRACH resources exclusively assigned by the base station to the mobile terminal based on the indicator; When the timer expires as a result of counting down, the PRACH resource cannot be used. Integrated circuits.

Images