Method and apparatus for beam failure detection and recovery process in the case of deactivated SN.

By handling the beam failure detection and recovery process of deactivating the signal receiver (SN) in the MR-DC scenario, the problem of low efficiency in the existing technology is solved, more efficient SN state management and power consumption optimization are achieved, and system performance is improved.

CN116746220BActive Publication Date: 2026-11-17LENOVO (BEIJING) LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202180091246.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-01-21
Publication Date
2026-11-17
Estimated Expiration
2041-01-21

AI Technical Summary

Technical Problem

In MR-DC scenarios, the details of beam failure detection and recovery processes in the case of deactivated auxiliary nodes (SNs) have not been fully discussed in 3GPP 5G technology, leading to power consumption issues and inefficiency.

Method used

A method and apparatus are provided to process deactivation indications or timer expiration by receiving configuration information related to beam failure detection (BFD) and recovery (BFR) procedures, adjust the behavior of the UE to efficiently transmit and receive BFR MAC CE, and optimize the activation and deactivation state transitions of the SN.

Benefits of technology

It improves the efficiency of SN activation and deactivation processes in MR-DC scenarios, reduces UE power consumption, optimizes beam failure detection and recovery processes, and enhances system performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116746220B_ABST
    Figure CN116746220B_ABST
Patent Text Reader

Abstract

Embodiments of this application relate to a method and apparatus for beam failure detection and recovery procedures in the case of a deactivated auxiliary node (SN) in a multi-radio dual connectivity (MR-DC) scenario under a 3GPP 5G system, etc. According to an embodiment of this application, a method may include: receiving configuration information related to at least one of a beam failure detection (BFD) procedure and a beam failure recovery (BFR) procedure; and receiving a deactivation indication associated with a UE's SN, or determining the expiration of a timer associated with deactivating the UE's SN, wherein the deactivation indication is included in at least one of: a radio resource control (RRC) message; and a deactivation media access control (MAC) control element (CE).
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of this application generally relate to wireless communication technology, and more particularly to a method and apparatus for beam failure detection and recovery in the case of a deactivated auxiliary node (SN) in a multi-radio dual-connectivity (MR-DC) scenario. Background Technology

[0002] Next-Generation Radio Access Network (NG-RAN) supports MR-DC scenarios. In MR-DC scenarios, User Equipment (UE) with multiple transceivers can be configured to utilize resources provided by two different nodes via a non-ideal backhaul connection. One node can provide New Radio (NR) access, while the other can provide Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) (E-UTRA) or NR access. One node can act as the primary node (MN), and the other can act as the secondary node (SN). The MN and SN are connected via a network interface (e.g., the Xn interface as specified in the 3GPP standards document), and at least the MN is connected to the core network.

[0003] Generally, in MR-DC scenarios, three types of states are defined for the SN: active state, deactivated state, and dormant state. In some cases, the deactivated state and the dormant state refer to the same SN state. Currently, details regarding beam failure detection and recovery processes in the deactivated SN scenario within MR-DC scenarios have not been discussed in 3GPP 5G technical specifications. Summary of the Invention

[0004] Some embodiments of this application provide a method for wireless communication. The method can be performed by a UE. The method includes: receiving configuration information related to at least one of a beam failure detection (BFD) process and a beam failure recovery (BFR) process; and receiving a deactivation indication associated with an auxiliary node (SN) of the UE, or determining the expiration of a timer associated with deactivating the SN of the UE, wherein the deactivation indication is included in at least one of: a radio resource control (RRC) message; and a deactivation of a media access control (MAC) control element (CE).

[0005] Some embodiments of this application also provide an apparatus for wireless communication. The apparatus includes: a non-transitory computer-readable medium having computer-executable instructions stored thereon; a receiving circuitry; a transmitting circuitry; and a processor coupled to the non-transitory computer-readable medium, the receiving circuitry, and the transmitting circuitry, wherein the computer-executable instructions cause the processor to implement the methods mentioned above performed by a UE.

[0006] Details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the specification, drawings, and claims. Attached Figure Description

[0007] To describe the advantages and features of this application, the description of the application is presented with reference to specific embodiments illustrated in the accompanying drawings. These drawings depict only exemplary embodiments of the application and should therefore not be construed as limiting its scope.

[0008] Figure 1 This application illustrates a schematic diagram of a wireless communication system according to some embodiments of the present application.

[0009] Figure 2 This document describes the network-side protocol termination options for MCG, SCG, and decoupled bearers in MR-DC scenarios (NGEN-DC, NE-DC, and NR-DC) with 5GC, based on 3GPP standard document TS37.340.

[0010] Figure 3 and 4 This section describes two exemplary format diagrams for BFR MAC CE based on 3GPP standard document TS38.321.

[0011] Figure 5 A flowchart illustrating a method for deactivating a UE's SN according to some embodiments of this application; and

[0012] Figure 6 Exemplary block diagrams illustrating some embodiments of the device according to this application. Detailed Implementation

[0013] The detailed description of the accompanying drawings is intended to illustrate preferred embodiments of the present application and is not intended to represent the only form in which the present application may be practiced. It should be understood that the same or equivalent functionality may be achieved through different embodiments intended to be covered within the spirit and scope of the present application.

[0014] Reference will now be made to some embodiments of this application, examples of which are illustrated in the accompanying drawings. For ease of understanding, embodiments are provided under specific network architectures and new service scenarios (e.g., 3GPP 5G, 3GPP LTE Release 8, etc.). It has been considered that, with the development of network architectures and new service scenarios, all embodiments of this application are also applicable to similar technical problems; furthermore, the terminology stated in this application may be changed without affecting the principles of this application.

[0015] Figure 1 A schematic diagram illustrating a wireless communication system according to some embodiments of this application.

[0016] like Figure 1 As shown, the wireless communication system 100 can be a dual-connectivity system 100, comprising at least one UE 101, at least one MN 102, and at least one SN 103. Specifically, for illustrative purposes, Figure 1 The dual connectivity system 100 includes a UE 101 shown, an MN 102 shown, and an SN 103 shown. Although in Figure 1 A specific number of UEs 101, MN 102 and SN 103 are depicted, but it is understood that the wireless communication system 100 may include any number of UEs 101, MN 102 and SN 103.

[0017] refer to Figure 1 UE 101 can connect to MN 102 and SN 103 via a network interface (e.g., the Uu interface as specified in the 3GPP standard document). MN 102 and SN 103 can connect to each other via a network interface (e.g., the Xn interface as specified in the 3GPP standard document). MN 102 can connect to MN 102 and SN 103 via a network interface (e.g., the Xn interface as specified in the 3GPP standard document). Figure 1 (Not shown in the image) Connects to the core network. UE 102 can be configured to utilize resources provided by MN 102 and SN 103 to perform data transmission.

[0018] MN 102 may refer to a radio access node that provides a control plane connection to the core network. In an embodiment of this application, in an E-UTRA-NR dual connectivity (EN-DC) scenario, MN 102 may be an eNB. In another embodiment of this application, in a next-generation E-UTRA-NR dual connectivity (NGEN-DC) scenario, MN 102 may be an ng-eNB. In yet another embodiment of this application, in an NR-E-UTRA dual connectivity (NE-DC) scenario or an NR-NR dual connectivity (NR-DC) scenario, MN 102 may be a gNB.

[0019] MN 102 may be associated with a primary cell group (MCG). An MCG may refer to a group of serving cells associated with MN 102, and may include the primary cell (PCell) of the MCG and one or more optional secondary cells (SCells). The PCell may provide control plane connectivity to UE 101.

[0020] SN 103 may refer to a radio access node that does not have a control plane connection to the core network but provides additional resources to UE 101. In an embodiment of this application, in an EN-DC scenario, SN 103 may be an en-gNB. In another embodiment of this application, in an NE-DC scenario, SN 103 may be an ng-eNB. In yet another embodiment of this application, in an NR-DC scenario or an NGEN-DC scenario, SN 103 may be a gNB.

[0021] SN 103 may be associated with a secondary cell group (SCG). An SCG may refer to a group of serving cells associated with SN 103, and may include a primary secondary cell (PSCell) and one or more optional SCells. The Pcell of the MCG and the PSCell of the SCG may also be referred to as a special cell (SpCell).

[0022] In some embodiments of this application, UE 101 may include computing devices such as desktop computers, laptop computers, personal digital assistants (PDAs), tablet computers, smart TVs (e.g., TVs connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, and modems), etc. In some other embodiments of this application, UE 101 may include portable wireless communication devices, smartphones, cellular phones, flip phones, devices with subscriber identity modules, personal computers, selective call reception circuitry systems, or any other devices capable of transmitting and receiving communication signals on a wireless network. In some other embodiments of this application, UE 101 may include wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, UE 101 may be referred to as a subscriber unit, mobile station, mobile base station, user, terminal, mobile terminal, wireless terminal, fixed terminal, subscriber station, user terminal, or device, or described using other terms used in the art.

[0023] From a network perspective, each bearer (MCG bearer, SCG bearer, and decoupled bearer) can be terminated in either the MN or SN. As specified in 3GPP standard document TS37.340, Figure 2The diagram illustrates network-side protocol termination options for MR-DC (NGEN-DC, NE-DC, and NR-DC) with 5GC. Generally, radio bearers configured with Service Data Adaptation Protocol (SDAP) and Packet Data Convergence Protocol (PDCP) entities located in the MN or SN are considered "MN-terminated radio bearers" or "SN-terminated radio bearers". Radio bearers configured with Radio Link Control (RLC) and Media Access Control (MAC) entities located in the MN or SN are considered MCG bearers or SCG bearers. Therefore, there are six configurable types of radio bearers in the MR-DC scenario: (1) SN-terminated MCG bearers; (2) SN-terminated SCG bearers; (3) MN-terminated MCG bearers; (4) MN-terminated SCG bearers; (5) MN-terminated decoupled bearers; and (6) SN-terminated decoupled bearers.

[0024] Figure 2 This describes the network-side protocol termination options for MCG, SCG, and decoupled bearers in MR-DC scenarios (NGEN-DC, NE-DC, and NR-DC) with 5GC, according to 3GPP standard document TS37.340. For example... Figure 2 As shown, in the MR-DC scenario with 5GC (5G core network), there are six configurable types of radio bearers:

[0025] (1) The MCG bearer terminated at MN, wherein SDAP and PDCP, RLC and MAC are located at MN.

[0026] (2) SCG bearer terminated at MN, where SDAP and PDCP are located at MN, while RLC and MAC are located at SN.

[0027] (3) The MN-terminated separate bearers, wherein SDAP and PDCP are located at MN, and one RLC branch is located at MN and another RLC branch is located at SN.

[0028] (4) Separate bearers terminated at SN, wherein (SDAP and) PDCP are located at SN, and one RLC branch is located at MN and another RLC branch is located at SN.

[0029] (5) The MCG bearer terminated at SN, wherein SDAP and PDCP are located at SN, while RLC and MAC are located at MN.

[0030] (6) SCG bearer terminated at SN, wherein SDAP and PDCP, RLC and MAC are located at SN.

[0031] Generally, the 3GPP standard documents regarding the SN activation or deactivation process agree as follows: To achieve reasonable UE battery consumption when configuring carrier aggregation (CA), a cell activation / deactivation mechanism is supported. When the SN is deactivated, the UE does not need to receive the corresponding Physical Downlink Control Channel (PDCCH) or Physical Downlink Shared Channel (PDSCH), cannot transmit in the corresponding uplink, and does not need to perform Channel Quality Indicator (CQI) measurements. Conversely, when the SN is active, the UE will receive both PDSCH and PDCCH (if the UE is configured to monitor PDCCH from this SN) and is expected to be able to perform CQI measurements.

[0032] As specified in 3GPP Release 17 work item regarding NR support for efficient SN activation or deactivation processes in MR-DC scenarios, power consumption for both the UE and network is a significant issue in EN-DC deployments due to the simultaneous maintenance of two radio links. In some cases, the power consumption of an NR UE is 3 to 4 times that of an LTE UE. In EN-DC deployments, the MN provides basic coverage. When UE data rate requirements change dynamically (e.g., from high to low), it is worth considering SN (deactivation) to conserve network and UE power.

[0033] The SN (deactivation) process can be triggered by the MN, SN, or UE. There are three options for activating and deactivating the SN.

[0034] Option 1: The SN can be activated or deactivated during SCell configuration. In Option 1, on one hand, the MN can configure the UE to set the SN's state in the SN-related configuration information of the UE to an activated or deactivated state, and then the MN notifies the SN. On the other hand, the SN can configure the UE. Specifically, if SRB3 is configured, then the SN directly sends an activation (deactivation) indication to the UE; and if SRB3 is not configured and the SN sends an activation (deactivation) indication to the UE to set the SN's state in the SN-related configuration information of the UE to an activated state, then the SN needs to send an RRCReconfiguration message contained in the DLInformationTransferMRDC message via the MN.

[0035] Option 2: The SN can be activated or deactivated via the SN to activate or deactivate the MAC CE. SN-activated MAC CE is emitted only by the MN. SN-deactivated MAC CE can be emitted by both the MN and SN.

[0036] Option 3: The SN can be deactivated when the timer used to deactivate or hibernate the SN expires.

[0037] Currently, further details regarding beam failure detection and recovery processes in deactivated SN scenarios within MR-DC scenarios are unclear, and specific enhancement mechanisms for beam failure detection (BFD) and beam failure recovery (BFR) are required in an efficient manner. Embodiments of this application provide enhancement mechanisms for BFD and BFR to efficiently support SCG deactivation in MR-DC scenarios such as 3GPP 5G systems.

[0038] Specifically, some embodiments of this application handle ongoing or triggered BFR MACCEs when the UE receives an RRC message or MAC CE for deactivating the UE's SN, or when a timer associated with deactivating the UE's SN expires. Further embodiments of this application handle ongoing or triggered RA procedures on the PSCell for BFR purposes when the UE receives an RRC message or MAC CE for deactivating the UE's SN, or when a timer associated with deactivating the UE's SN expires. Other embodiments of this application provide solutions related to new UE behaviors associated with BFD and BFR procedures when the UE's SN is in a deactivated state.

[0039] Further details regarding embodiments of this application will be described below in conjunction with the accompanying drawings. The following definitions are assumed in the embodiments of this application:

[0040] • Fast MCG Link Recovery: In MR-DC scenarios, an RRC procedure is used where, after detecting a radio link failure on the MCG, the UE sends an MCG failure information message to the MN via the SCG.

[0041] • Primary Cell Group: In the MR-DC scenario, a group of serving cells associated with the primary node, consisting of SpCell (PCell) and one or more optional SCells.

[0042] • Secondary Cell Group: In the MR-DC scenario, a group of serving cells associated with the secondary node, consisting of SpCell (PSCell) and one or more optional SCells.

[0043] • Auxiliary Node: In MR-DC scenarios, a radio access node that does not have a control plane connection to the core network provides additional resources to the UE. It can be an en-gNB (in EN-DC), an auxiliary ng-eNB (in NE-DC), or an auxiliary gNB (in NR-DC and NGEN-DC).

[0044] • SCG Bearer: In MR-DC scenarios, a radio bearer with only one RLC bearer in the SCG (or two RLC bearers in the case of duplicate CA packets in the E-UTRAN cell group, or up to four RLC bearers in the case of duplicate CA packets in the NR cell group).

[0045] •SpCell: The primary cell in a primary or secondary cell group.

[0046] • Signaling Radio Bearer (SRB) 3: Direct SRB between SN and UE in EN-DC, NGEN-DC and NR-DC.

[0047] • Separate bearer: In the MR-DC scenario, both the MCG and SCG have radio bearers with RLC bearers.

[0048] As specified in 3GPP standard document TS38.321, regarding the beam failure detection and recovery process, the MAC entity can be configured by the RRC according to a serving cell with a beam failure detection (BFD) procedure, which is used to indicate to the serving BS of a new SSB or CSI-RS when a beam failure is detected on the serving SSB or CSI-RS. Beam failures are detected by counting beam failure instance indications from lower layers to the MAC entity. The RRC configures the beam failure detection and recovery process with the following parameters in BeamFailureRecoveryConfig and RadioLinkMonitoringConfig:

[0049] - beamFailureInstanceMaxCount for beam failure detection;

[0050] -BFI_COUNTER (per serving cell): A counter initially set to 0 for indicating beam failure examples.

[0051] -BFD's beamFailureDetectionTimer.

[0052] According to the 3GPP standard document TS38.321, for the BFR procedure of a SCell, if a beam failure instance indication has been received from the physical layer, the UE starts or restarts the beamFailureDetectionTimer and increments BFI_COUNTER by 1. If BFI_COUNTER >= beamFailureInstanceMaxCount and the serving cell is a SCell, the UE triggers the BFR procedure for this serving cell. The UE will then transmit a BFR MAC CE to the serving BS.

[0053] Figure 3and 4 This section describes two exemplary format diagrams for BFR MAC CE based on the 3GPP standard document TS38.321.

[0054] exist Figure 3 and 4 In this embodiment, the fields in BFR MAC CE are defined as follows:

[0055] -SP (for example, respectively) Figure 3 and 4 The field “SP” shown in the first row, eighth column: This field indicates beam failure detection of the SpCell for this MAC entity. The SP field is set to 1 to indicate that beam failure of the SpCell is detected only if the BFR MAC CE is included in the MAC PDU as part of the random access (RA) procedure; otherwise, the SP field is set to 0.

[0056] -C i (BFR MAC CE) (For example, such as) Figure 3 The numbers “C1” to “C7” shown in the document; and as shown in the document. Figure 4 The numbers "C1" to "C" shown in the image 31 "): This field indicates the presence of BFD and an octet containing the AC field of the SCell with ServCellIndex i as specified in the 3GPP standard document TS38.331. A C field set to 1..." i The field indicates that a beam failure was detected and that an octet containing the AC field exists in an SCell with ServCellIndex i. A C field set to 0... i The field indicates that no beam failure was detected and that there is no octet containing the AC field for an SCell with ServCellIndex i. Octets containing the AC field exist in ascending order based on ServCellIndex.

[0057] -AC (for example, such as) Figure 3 The "AC" displayed in the first column, second row to the bottom row; and as shown in the following text. Figure 4The "AC" field (shown in the first column, fifth row, to the bottom row) indicates the presence of a candidate RS ID field in this octet. The AC field is set to 1 if at least one of the SSBs in the candidateBeamRSSCellList with an SS-RSRP higher than rsrp-ThresholdBFR or a CSI-RS in the candidateBeamRSSCellList with a CSI-RSRP higher than rsrp-ThresholdBFR is available; otherwise, the AC field is set to 0. If the AC field is set to 1, a candidate RS ID field is present. If the AC field is set to 0, R bits are present instead.

[0058] - Candidate RS ID (e.g., such as Figure 3 The "Candidate RS IDs" shown in the second to bottom rows; and as... Figure 4 The "Candidate RS ID" field (shown in rows 5 through 1) is set to the index of the SSB in the candidateBeamRSSCellList that has an SS-RSRP higher than rsrp-ThresholdBFR, or the index of the CSI-RS in the candidateBeamRSSCellList that has a CSI-RSRP higher than rsrp-ThresholdBFR. The SSB or CSI-RS index corresponds to the index of the entry in the candidateBeamRSSCellList for that SSB or CSI-RS. Index 0 corresponds to the first entry in the candidateBeamRSSCellList, and index 1 corresponds to the second entry, and so on. This field is 6 bits long.

[0059] -R (for example, such as) Figure 3 The "R" shown in the second to the bottom row; and as... Figure 4 The "R" shown in the fifth to bottom rows: This field is a reserved bit and it is set to 0.

[0060] According to the 3GPP standard document TS38.321, for BFR on a PSCell, if a beam failure instance indication has been received from the physical layer, the UE starts or restarts the beamFailureDetectionTimer and increments BFI_COUNTER by 1. If BFI_COUNTER >= beamFailureInstanceMaxCount and the serving cell is a PSCell or PCell, the UE triggers the RA procedure on the SpCell. The UE selects an appropriate beam to perform the BFR procedure (if the BS has provided dedicated RA resources for certain beams, those beams will be prioritized by the UE). The BFR procedure is considered complete when the RA procedure is completed.

[0061] Figure 5 A flowchart illustrating a method for deactivating the SN of a UE according to some embodiments of this application.

[0062] Figure 5 The exemplary method 500 in the embodiments can be executed by the UE, for example, as... Figure 1 The UE101 shown and described herein. Although described with respect to a UE, it should be understood that other devices may be configured to perform such actions. Figure 5 The methods shown and explained in the document. Figure 5 The embodiments assume that MN and SN in the MR-DC scenario in these embodiments can be combined in any of the EN-DC, NGEN-DC, NE-DC and NR-DC scenarios.

[0063] In such Figure 5 In the exemplary method 500 shown, in operation 501, the UE receives configuration information related to at least one of the BFD and BFR procedures. In operation 502, the UE receives a deactivation indication associated with the UE's SN, or determines the expiration of a timer associated with the SN of the deactivated UE. The deactivation indication may be included in an RRC message and / or a deactivation MAC CE. For example, the RRC message may be an RRCreconfiguration message as specified in the 3GPP standard document. The timer associated with the SN of the deactivated UE may be an sNodeDeactivationTimer. The deactivation MAC CE may also be referred to as a MAC CE for deactivation, a hibernation MAC CE, a hibernation MAC CE, and a hibernation MAC CE, etc.

[0064] According to some embodiments, if the UE receives a deactivation indication or determines that the timer associated with the SN of the deactivated UE has expired and if the BFR procedure of the secondary cell (SCell) has been triggered, then the UE cancels the BFR procedure for the SCell.

[0065] According to some further embodiments, if the UE receives a deactivation indication or determines that the timer associated with the SN of the deactivated UE has expired and if the BFR procedure of the SCell has been triggered, then the UE suspends the BFR MACCE associated with the UE's SN.

[0066] In an embodiment, if the UE's SN (i.e., the SN status in the SN-related configuration information of the UE) is in an active state, then the UE transmits a BFR MAC CE containing the latest beam information to the SN.

[0067] In some additional embodiments, if the UE receives a deactivation indication or determines that a timer associated with the SN of the deactivated UE has expired and if a BFR procedure for the SCell has been triggered, then the UE configures its SN to a deactivated state; and the UE transmits a BFR MAC CE for the SCell to the MN via the link between the UE and the MN. A beam failure has been detected in the SCell. For example, the BFR MAC CE contains the updated beam of the primary secondary cell (PSCell).

[0068] In this embodiment, after receiving the BFR MAC CE from the UE, the MN forwards the received BFR MAC CE and its timestamp to the SN.

[0069] In some other embodiments, if the UE receives a deactivation indication or determines that a timer associated with the SN of the deactivated UE has expired, and if a random access (RA) procedure on the PSCell associated with the BFR procedure is in progress, then the UE configures its SN to a deactivated state; and the UE transmits a BFR MAC CE for the PSCell to the MN via the link between the UE and the MN. A beam failure has been detected in the PSCell. For example, the BFR MAC CE contains the updated beam for the PSCell.

[0070] In some other embodiments, if the UE receives a deactivation indication or determines that the timer associated with the SN of the deactivated UE has expired and if the RA procedure on the PSCell associated with the BFR procedure is in progress, then the UE stops the RA procedure on the PSCell.

[0071] In some other embodiments, if the UE receives a deactivation indication or determines that a timer associated with the SN of the deactivating UE has expired, and if the RA procedure on the PSCell associated with the BFR procedure is in progress, then the UE skips the activation indication and continues to perform the RA procedure on the PSCell. In one embodiment, the UE transmits information to the MN to indicate that the activation indication has been skipped. In a further embodiment, if the SN receives information from the UE during the RA procedure, then the SN transmits information to the MN indicating that the activation indication has been skipped.

[0072] In some other embodiments, if the UE determines that the timer associated with the SN of the deactivated UE has expired and if the RA procedure on the PSCell associated with the BFR procedure is in progress, then the UE continues to keep the SN of the UE active and transmits information indicating the expiration of the timer mentioned above.

[0073] In some other embodiments, if the UE receives a deactivation indication and if the RA procedure on the PSCell associated with the BFR procedure is in progress, then the UE suspends the deactivation indication and continues executing the RA procedure. In some embodiments, if the RA procedure completes successfully, then the UE autonomously configures its SN to a deactivated state.

[0074] In some additional embodiments, if the UE detects a beam failure and if the UE's SN is in a deactivated state, then the UE may perform at least one of the following:

[0075] (1) Pause the BFR process of SCell;

[0076] (2) Pause the RA process on PSCell; and

[0077] (3) Configure the UE's SN to be deactivated.

[0078] In these embodiments, if the UE's SN is configured to be active, the UE performs a BFR procedure on the SCell and an RA procedure on the PSCell. In these embodiments, if the UE detects a beam failure on the PSCell, the RA procedure on the PSCell is performed before the BFR procedure on the SCell.

[0079] In some additional embodiments, if the UE's SN is in a deactivated state and if the UE detects a beam failure in the PSCell or SCell, then the UE transmits an updated BFR MAC CE to the MN via the link between the UE and the MN. Specifically, the MN may forward the updated BFR MAC CE to the SN.

[0080] In some additional embodiments, if the UE receives a deactivation indication or determines that a timer associated with the SN of the deactivated UE has expired, the UE sets the value of the beam failure example counter (e.g., BFI_COUNTER) to zero and stops the beam failure detection timer (e.g., beamFailureDetectionTimer).

[0081] In some additional embodiments, after the UE's SN is configured to be in an inactive state, the BFD and BFR procedures are executed in the PSCell, while the BFD and BFR procedures are not executed in the SCell.

[0082] In some additional embodiments, if a timer associated with the SN of the deactivated UE is running, the UE stops the timer associated with the SN of the deactivated UE if the UE receives an RRC message or a deactivation MAC CE containing a deactivation indication.

[0083] The following text describes... Figure 5 Specific embodiments 1 to 3 of the methods shown and described herein.

[0084] According to embodiments 1 to 3, the UE and BS (e.g., MN or SN) can perform the following operations. The UE can be as follows: Figure 1 The UE 101 shown and described herein. MN may be as follows: Figure 1 The MN 102 shown and described herein. SN may be as follows: Figure 1 SN 103 as shown and described in the document.

[0085] Example 1: This example handles the ongoing or triggered BFR MAC CE when the UE receives an RRC message (e.g., RRCreconfiguration message) or MAC CE for deactivating the UE's SN, or when a timer (e.g., sNodeDeactivationTimer) associated with deactivating the UE's SN expires. Specifically, in Case A-1 of Example 1, the UE's BFR MAC CE can be skipped when the UE's SN is in a deactivated state. In Case A-2 of Example 1, the UE should perform a BFR MAC CE when the UE's SN is in a deactivated state.

[0086] (1) Step 1: UE accesses BS. SN is configured to UE.

[0087] - Parameters for BFD and BFR (e.g., BeamFailureRecoveryConfig and RadioLinkMonitoringConfig) are configured to the UE.

[0088] (2) Step 2: The UE triggers the BFR MAC CE of the SCell.

[0089] For example, when COUNTER >= beamFailureInstanceMaxCount, the UE triggers a BFR procedure for a SCell. After triggering the BFR procedure, the UE will generate a BFR MAC CE for transmission using any available serving cell associated with the SN configured to the UE.

[0090] (3) Step 3: Before transmitting the BFR MAC CE, the UE may receive a deactivation indication from the MN or SN, or a timer (e.g., sNodeDeactivationTimer) associated with the SN of the deactivated UE may expire.

[0091] - The deactivation indication received from the MN or SN is used to deactivate the SN of the UE (i.e., the SN status in the SN-related configuration information of the UE) and may be included in an RRC message (e.g., an RRCreconfiguration message) or a MAC CE.

[0092] (4) Step 4: The UE can adopt Case A-1 or Case A-2 of Example 1 according to different scenarios or implementation schemes.

[0093] 1. Case A-1: ​​When the UE's SN is in a deactivated state, the UE's BFR MAC CE can be skipped. Specifically, in step 4, the UE will switch to option 1 or option 2, as follows:

[0094] - Option 1: When the UE receives an RRC message (e.g., RRCreconfiguration message) or MAC CE for deactivating the UE's SN, or when a timer (e.g., sNodeDeactivationTimer) associated with the SN of the deactivating UE expires, the UE cancels any triggered BFR procedure of the SCell.

[0095] - If the SN status (i.e., the SN of the UE) in the SN-related configuration information of the UE is configured to be deactivated, then the UE can set all beam failure example counters (e.g., BFI_COUNTER) to 0 and stop all beam failure detection timers (e.g., beamFailureDetectionTimer).

[0096] Option 2: When the UE receives an RRC message (e.g., RRCreconfiguration message) or MAC CE for deactivating the UE's SN, or when a timer (e.g., sNodeDeactivationTimer) associated with the deactivating UE's SN expires, the UE suspends the BFR MAC CE associated with the SN. When the UE's SN is active, the UE transmits a pending BFR MAC CE containing the latest new beam.

[0097] - For example, when activating the SN of the UE, the latest new beam in the pending BFR MAC CE is the "good" beam.

[0098] Specifically, pending BFR MAC CE documents may have the following formats: (Reference) Figure 3 and 4 In any of the embodiments, the "SP" field can be used to carry the identity (ID) of the PSCell, and C i The field can be used to carry the ID of the SCell.

[0099] - If the SN status in the SN-related configuration information of the UE is configured to be deactivated, then the UE can set all beam failure example counters (e.g., BFI_COUNTER) to 0 and stop all beam failure detection timers (e.g., beamFailureDetectionTimer).

[0100] 2. Case A-2: When the UE's SN is in a deactivated state, a BFR MAC CE should be performed on the UE. Specifically, in step 4, the UE will proceed to option (1), as follows:

[0101] - Option (1): After the UE receives a deactivation indication or determines that the timer associated with the SN of the deactivated UE has expired, and after triggering the BFR procedure of the SCell, the UE configures the UE's SN to a deactivated state. Then, while the UE's SN is in a deactivated state, the UE uses the MN link to transmit a BFR MAC CE for the SCell in which a beam failure has been detected to the MN. The MN may then transmit new beam information to the SN.

[0102] - In one instance, the UE transmits a new enhanced BFR MAC CE to the MN, which includes a new beam for the PSCell. (Reference) Figure 3 and 4 In any of the embodiments, the “SP” field of the new enhanced BFR MAC CE can be used to carry the ID of the PSCell.

[0103] - In a further example, when the MN transmits information contained in the BFR MAC CE (e.g., the new enhanced BFR MAC CE) to the SN, for example via the Xn interface, the MN also transmits the timestamp of the BFR MAC CE received from the UE. The SN can then be aware of whether the UE has applied this new beam.

[0104] Example 2: When the UE receives an RRC message (e.g., RRCreconfiguration message) or MAC CE for deactivating the UE's SN, or when a timer associated with deactivating the UE's SN (e.g., sNodeDeactivationTimer) expires, this example handles the ongoing or triggered RA procedure on the PSCell for BFR purposes. Specifically, in Case B-1 of Example 2, when the UE's SN is in a deactivated state, the RA procedure on the PSCell for BFR purposes can be skipped. In Case B-2 of Example 2, when the UE's SN is in a deactivated state, the RA procedure on the PSCell for BFR purposes should be performed on the UE.

[0105] (1) Step 1: UE accesses the base station. SN is configured to UE.

[0106] - Parameters for BFD and BFR (e.g., BeamFailureRecoveryConfig and RadioLinkMonitoringConfig) are configured to the UE.

[0107] (2) Step 2: The UE triggers the RA procedure on the PSCell for BFR purposes.

[0108] - In an instance, if BFI_COUNTER >= beamFailureInstanceMaxCount and the serving cell is PSCell, then the UE triggers the RA procedure on the PSCell.

[0109] - In a further example, the BFD and BFR procedures are performed in the PSCell only when the UE's SN is in a deactivated state. When the UE's SN is in a deactivated state, the BFD and BFR procedures are not performed in the SCell.

[0110] (3) Step 3: Before the UE transmits a preamble during an ongoing or triggered RA process, the UE may receive a deactivation indication from the MN or SN, or a timer (e.g., sNodeDeactivationTimer) associated with the SN of the deactivating UE may expire.

[0111] - Deactivation instructions received from MN or SN can be included in RRC messages or MAC CE.

[0112] (4) Step 4: The UE can adopt Case B-1 or Case B-2 of Example 2 according to different scenarios or implementation schemes.

[0113] 1. Case B-1: When the UE's SN is in a deactivated state, the ongoing or triggered RA procedure of the UE can be skipped. Specifically, in step 4, the UE will proceed to option (A) or option (B) as follows:

[0114] - Option (A): If an ongoing or triggered RA procedure exists on the PSCell (where beam failure has been detected) for BFR purposes, the UE may stop the RA procedure when it receives an RRCreconfiguration message or MAC CE to deactivate the UE's SN, or when the sNodeDeactivationTimer expires. When the UE's SN is active, the UE performs the RA procedure first.

[0115] - Option (B): If an ongoing or triggered RA procedure exists on the PSCell for BFR purposes, then after the UE receives a deactivation indication or determines that the timer associated with the SN of the deactivated UE has expired, the UE configures the UE's SN to a deactivated state. That is, the UE sets the SN state in the SN-related configuration information of the UE to deactivated. Then, the UE transmits the BFR MAC CE of the PSCell to the MN via the link between the MN and the UE.

[0116] - In one instance, the UE transmits a new enhanced BFR MAC CE to the MN, which includes a new beam for the PSCell. (Reference) Figure 3 and 4 In any of the embodiments, the “SP” field of the new enhanced BFR MAC CE can be used to carry the ID of the PSCell.

[0117] - In a further example, the BFR MAC CE contains an updated beam of the PSCell.

[0118] 2. Scenario B-2: When the UE's SN is in a deactivated state, the ongoing or triggered RA procedure should be performed on the UE. Specifically, in step 4, the UE will proceed to option (a), option (b), or option (c), as follows:

[0119] - Option (a) (related to the deactivation instructions included in the RRC message and MAC CE):

[0120] - If an ongoing or triggered RA procedure exists on the PSCell for BFR purposes and the UE receives an RRC message (e.g., an RRCreconfiguration message) or MAC CE containing a deactivation indication, the UE can skip the deactivation indication in the RRC message or MAC CE. The BS can configure the UE to deactivate the SN to a deactivated state after the RA procedure has successfully completed.

[0121] If the UE skips the deactivation instruction received from the MN, then the SN needs to indicate to the MN when the SN received the information during the UE's RA procedure. Alternatively, the UE can indicate to the MN that the UE has skipped the activation instruction.

[0122] - Option (b) (associated with the timer associated with the SN of the UE for deactivation):

[0123] If an ongoing or triggered RA procedure exists on the PSCell for BFR purposes and a timer (e.g., sNodeDeactivationTimer) associated with deactivating the UE's SN expires, the UE may not stop the ongoing RA procedure and may report the timer's expiration. Specifically, for example, the UE may continue to keep its SN active and transmit a message indicating the timer's expiration. The BS may configure the UE to deactivate the SN to a deactivated state after the RA procedure has successfully completed.

[0124] • In one instance, the UE can restart a timer (e.g., sNodeDeactivationTimer) associated with the SN of the deactivated UE, as the UE may receive or transmit data.

[0125] In a further example, the UE can trigger the RA procedure when the sNodeDeactivationTimer expires. Then, the UE continues the RA procedure without activating the UE's SN.

[0126] • In another instance, when the UE receives an RRC message or MAC CE for deactivating the UE's SN, if this timer is running, then the UE should stop the sNodeDeactivationTimer.

[0127] Option (c): If an ongoing or triggered RA procedure exists on the PSCell for BFR purposes and the UE receives an RRC message (e.g., an RRCreconfiguration message) or MAC CE containing a deactivation indication, the UE may continue the ongoing RA procedure and pause the deactivation indication in the RRC message or MAC CE. After the RA procedure is successfully completed, the UE autonomously deactivates the SN (i.e., autonomously sets the SN status in the SN-related configuration information of the UE to deactivation). If a timer (e.g., sNodeDeactivationTimer) associated with deactivating the UE's SN expires, the UE autonomously deactivates the SN after the RA procedure is successfully completed.

[0128] Example 3: This example defines the behavior of the UE when its SN is in a deactivated state. Specifically, in case C-1 of Example 3, a BFD procedure is required, but a BFR procedure is not required when the UE's SN is in a deactivated state. In case C-2 of Example 3, both BFD and BFR procedures are required when the UE's SN is in a deactivated state. In case C-3 of Example 3, neither BFD nor BFR procedures are required when the UE's SN is in a deactivated state.

[0129] (1) Step 1: UE accesses BS. SN is configured to UE.

[0130] - Parameters for BFD and BFR (e.g., BeamFailureRecoveryConfig and RadioLinkMonitoringConfig) are configured to the UE.

[0131] (2) Step 2: The UE may receive a deactivation indication from the MN or SN, or a timer (e.g., sNodeDeactivationTimer) associated with the SN of the deactivated UE may expire.

[0132] - Deactivation instructions received from MN or SN can be included in RRC messages or MAC CE.

[0133] (3) Step 3: The UE can adopt Case C-1, Case C-2 or Case C-3 of Example 3 according to different scenarios or implementation schemes.

[0134] 1. Case C-1: A BFD procedure is required, but a BFR procedure is not required when the UE's SN is in an inactive state. Specifically, in step 3, if a beam failure is detected and the UE's SN is in an inactive state, the UE may suspend the BFR procedure on the SCell, suspend the RA procedure on the PSCell for BFR purposes, and / or configure the UE's SN to be in an inactive state. When the UE's SN is in an active state, the UE may perform a BFR procedure on the SCell for BFR purposes and perform an RA procedure on the PSCell. If a beam failure is detected on the PSCell, the RA procedure on the PSCell for BFR purposes may be performed first.

[0135] 2. Case C-2: When the UE's SN is in a deactivated state, both BFD and BFR procedures are required. Specifically, in step 3, if the UE's SN is in a deactivated state and the UE detects a beam failure in either PSCell or SCell, then if a beam failure is detected in either PSCell or SCell, the UE uses the MN link to transmit an updated BFR MAC CE (e.g., a new enhanced BFR MAC CE) to the MN. Then, the MN transmits new beam information to the SN.

[0136] - In one instance, the UE transmits a new enhanced BFR MAC CE to the MN, which includes a new beam for the PSCell. (Reference) Figure 3 and 4 In any of the embodiments, the “SP” field of the new enhanced BFR MAC CE can be used to carry the ID of the PSCell.

[0137] - In a further example, when the MN transmits information to the SN contained in an updated BFR MAC CE (e.g., a new enhanced BFR MAC CE), the MN also transmits a timestamp of receiving the updated BFR MAC CE. The SN can then be aware of whether the UE has applied this new beam.

[0138] - In another instance, when a beam failure is detected in a PSCell or SCell, the UE directly executes the RA procedure.

[0139] 3. Case C-3: When the UE's SN is in a deactivated state, neither the BFD nor BFR procedures are required. Specifically, in step 3, if the UE receives a deactivation indication or determines that the timer associated with the deactivated UE's SN has expired, then the UE sets the beam failure instance counter (e.g., BFI_COUNTER) to 0 and stops the beam failure detection timer (e.g., BeamFailureDetectionTimer).

[0140] The details described in all other embodiments of this application (e.g., details of the deactivation indication or timer associated with the SN of the deactivating UE) are applicable. Figure 5 Examples of implementations. Furthermore, Figure 5 The details described in the embodiments are applicable to Figures 1 to 4 All embodiments of 6.

[0141] Figure 6 This application illustrates exemplary block diagrams of a device according to some embodiments of the present application. In some embodiments of the present application, device 600 may be a UE, which is at least capable of performing... Figure 5 The method described in the document.

[0142] like Figure 6 As shown, device 600 may include at least one receiver 602, at least one transmitter 604, at least one non-transitory computer-readable medium 606, and at least one processor 608 coupled to at least one receiver 602, at least one transmitter 604 and at least one non-transitory computer-readable medium 606.

[0143] Despite Figure 6 In this application, elements such as at least one receiver 602, at least one transmitter 604, at least one non-transitory computer-readable medium 606, and at least one processor 608 are described in the singular, but the plural form may be considered unless explicitly stated to be limited to the singular. In some embodiments of this application, at least one receiver 602 and at least one transmitter 604 are combined into a single device, such as a transceiver. In some embodiments of this application, device 600 may further include input devices, memory, and / or other components.

[0144] In some embodiments of this application, at least one non-transitory computer-readable medium 606 may have computer-executable instructions stored thereon, which are programmed to be implemented using at least one receiver 602, at least one transmitter 604, and at least one processor 608, for example, given... Figure 5 The operation of the described method.

[0145] Those skilled in the art will understand that the steps of the methods described in connection with the aspects disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or a combination of both. The software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. Furthermore, in some aspects, the steps of the method can reside as one or any combination or set of code and / or instructions on a non-transitory computer-readable medium that can be incorporated into a computer program product.

[0146] Although this disclosure has been described with reference to specific embodiments, it will be apparent to those skilled in the art that many alternatives, modifications, and variations may be readily apparent. For example, various components of the embodiments may be interchanged, added, or substituted in other embodiments. Furthermore, not all elements in each figure are essential for the operation of the disclosed embodiments. For example, those skilled in the art will be able to make and use the teachings of this disclosure by simply employing the elements of the independent claims. Therefore, the embodiments of this disclosure as described herein are intended to be illustrative and not restrictive. Various changes may be made without departing from the spirit and scope of this disclosure.

[0147] In this document, the term "includes / including" or any other variation thereof is intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements may include not only said elements but also other elements not expressly listed or inherent to such process, method, article, or apparatus. Unless otherwise specified, an element beginning with "a / an" or the like does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element. Furthermore, the term "another" is defined as at least a second or more. The terms "having" and the like, as used herein, are defined as "includes".

Claims

1. A user equipment (UE) for wireless communication, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory and configured such that the UE: In the first Radio Resource Control (RRC) message, configuration information is received, wherein the configuration information is related to the Beam Failure Recovery (BFR) procedure. Receive a deactivation indication associated with the auxiliary node SN of the UE, wherein the deactivation indication is included in a second RRC message; and In response to receiving the deactivation instruction and in response to the BFR procedure of the secondary cell SCell being triggered, the BFR procedure of the SCell is cancelled.

2. The UE of claim 1, wherein the at least one processor is configured such that the UE: Start or restart the timer associated with deactivating the SN; and In response to the timer associated with deactivating the SN being running and in response to receiving the second RRC message, the timer associated with deactivating the SN is stopped.

3. The UE of claim 1, wherein the at least one processor is configured such that the UE: In response to receiving the deactivation instruction and in response to the BFR procedure being triggered for the secondary cell SCell, the BFR MAC CE associated with the SN is suspended.

4. The UE of claim 3, wherein the at least one processor is configured such that the UE: In response to the SN being active, a BFR MAC CE containing beam information is transmitted to the SN.

5. The UE of claim 1, wherein the at least one processor is configured to cause the UE to: In response to receiving the deactivation indication and in response to the BFR procedure that has been triggered in the secondary cell SCell, the SN is configured to a deactivation state; and The BFR MAC CE of the SCell is transmitted to the MN via the link between the master node MN and the UE, wherein a beam failure has been detected in the SCell.

6. The UE according to claim 5, wherein the BFR MAC CE and the timestamp for receiving the BFR MAC CE are forwarded by the MN to the SN.

7. The UE of claim 1, wherein the at least one processor is configured to cause the UE to: In response to receiving the deactivation indication and in response to the random access RA procedure on the primary auxiliary cell PSCell associated with the BFR procedure being in progress, the SN is configured to a deactivation state; The BFR MAC CE of the PSCell is transmitted to the MN via the link between the master node MN and the UE, wherein a beam failure has been detected in the PSCell.

8. The UE of claim 1, wherein the at least one processor is configured such that the UE: In response to receiving the deactivation instruction and in response to the radio access RA process being performed on the primary auxiliary cell PSCell associated with the BFR process, the RA process is stopped.

9. The UE of claim 1, wherein the at least one processor is configured such that the UE: In response to receiving the deactivation indication and in response to the radio access RA procedure being performed on the primary auxiliary cell PSCell associated with the BFR procedure, the deactivation indication is skipped and the RA procedure continues.

10. The UE of claim 1, wherein the at least one processor is configured such that the UE: Start or restart the timer associated with deactivating the SN; and In response to determining that the timer associated with deactivating the SN has expired and in response to the RA process on the primary auxiliary cell PSCell associated with the BFR process being in progress, the SN remains active and transmits information indicating the expiration of the timer associated with deactivating the SN.

11. The UE of claim 1, wherein the at least one processor is configured such that the UE, in response to detecting a beam failure and in response to the SN being in a deactivated state, performs: Suspend the BFR process of the auxiliary cell SCell; Suspend the radio access RA process on the primary and secondary cells PSCell; Configure the SN to a deactivated state; Or a combination thereof.

12. The UE of claim 1, wherein the at least one processor is configured such that the UE: In response to the SN being in an inactive state and in response to the detection of beam failure of the primary and secondary cell PSCell, the secondary cell SCell or a combination thereof, an updated BFR MAC CE is transmitted to the MN via the link between the primary node MN and the UE.

13. The UE of claim 1, wherein the at least one processor is configured such that the UE: In response to receiving the deactivation instruction, the value of the beam failure example counter is set to zero and the beam failure detection timer is stopped.

14. A method performed by a user equipment (UE), comprising: In the first Radio Resource Control (RRC) message, configuration information is received, wherein the configuration information is related to the Beam Failure Recovery (BFR) procedure. Receive a deactivation indication associated with the auxiliary node SN of the UE, wherein the deactivation indication is included in a second RRC message; and In response to receiving the deactivation instruction and in response to the BFR procedure of the secondary cell SCell being triggered, the BFR procedure of the SCell is cancelled.

15. The method of claim 14, further comprising: In response to receiving the deactivation instruction and in response to the BFR procedure being triggered for the secondary cell SCell, the BFR MAC CE associated with the SN is suspended.

16. The method of claim 15, further comprising: In response to the SN being active, a BFR MAC CE containing beam information is transmitted to the SN.

17. The method of claim 14, further comprising: In response to receiving the deactivation indication and in response to the BFR procedure that has been triggered in the secondary cell SCell, the SN is configured to a deactivation state; and The BFR MAC CE of the SCell is transmitted to the MN via the link between the master node MN and the UE, wherein a beam failure has been detected in the SCell.

18. A user equipment (UE) for wireless communication, comprising: A non-transitory computer-readable medium having computer-executable instructions stored thereon; Receiver circuit system; Transmitting circuitry system; and A processor coupled to the non-transitory computer-readable medium, the receiving circuitry, and the transmitting circuitry. The computer-executable instructions wherein the processor: In the first Radio Resource Control (RRC) message, configuration information is received, wherein the configuration information is related to the Beam Failure Recovery (BFR) procedure. Receive a deactivation indication associated with the auxiliary node SN of the UE, wherein the deactivation indication is included in a second RRC message; and In response to receiving the deactivation instruction and in response to the BFR procedure of the secondary cell SCell being triggered, the BFR procedure of the SCell is cancelled.

Citation Information

Patent Citations

  • Beam Failure Recovery Procedures

    US20200100311A1

  • Beam failure recovery for secondary cell

    WO2020258279A1