Beam failure recovery in group-based secondary cell

Abstract

To provide a technique capable of simultaneously recovering from a beam failure in multiple SCells configured to operate within a network.SOLUTION: A communication device includes a receiving unit and a circuit. The receiving unit receives setting information for beam failure recovery (BFR) of multiple secondary cells (SCells) operating in a network. The circuit performs beam fault detection (BFD) based on the setting information and reports the same.SELECTED DRAWING: Figure 9

Description

[Technical field]

[0001] The present disclosure relates generally to communication devices and communication methods for electronic devices and systems, and more particularly to beam failure recovery for multiple secondary cells (SCells) operating on a network. [Background technology]

[0002] Wireless networks, such as millimeter wave (mmWave) communications, operate at higher frequency bands and therefore have large antenna arrays that allow communication devices to transmit signals over a large number of links using very narrow beams. Although such networks offer many advantages over traditional networks, such as the ability to transmit at very high data rates, they also present challenges in managing multi-beam operation and recovery protocols in case of beam failures within the network.

[0003] Currently, only beam failure recovery procedures for Primary Cell (PCell) and Primary Secondary Cell (PsCell) are specified in 3GPP Release (Rel.) 15 for the 5G standard, and there is little discussion on communication devices and methods for beam failure recovery related to group-based Secondary Cell (SCell). Summary of the Invention

[0004] Non-limiting embodiments of the present disclosure contribute to providing an advanced multi-beam operation in a wireless network. As an example, the embodiments include group-based SCell beam failure recovery in a network, providing an effective solution for simultaneously recovering beam failures of multiple SCells configured to operate in the network.

[0005] According to the present disclosure, there is provided a communication device comprising: a receiver that, during operation, receives configuration information for beam failure recovery (BFR) of a plurality of SCells operating within a network; and a circuit that, during operation, performs beam failure detection (BFD) and reporting based on the configuration information.

[0006] These comprehensive or specific aspects may be realized as a system, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium.

[0007] Further advantages and benefits of an embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some of the embodiments and features described in the specification and drawings, respectively, but not necessarily all of them may be provided to obtain one or more identical features. [Brief description of the drawings]

[0008] In the accompanying drawings, where like reference numbers indicate identical or functionally similar elements throughout the various views, the accompanying drawings, together with the following detailed description, are incorporated in and constitute a part of this specification, and serve to illustrate various embodiments and explain various principles and advantages in accordance with the present embodiments. [Figure 1] FIG. 1 is a diagram illustrating an example of the structure of 3GPP NR (New Radio). [Diagram 2] FIG. 1 is a schematic diagram showing the functional division between the Next Generation Radio Access Network (NG-RAN) and the 5G Core Network (5GC). [Diagram 3] FIG. 1 is a sequence diagram showing a procedure for radio resource control (RRC) connection setup / reconfiguration. [Figure 4] FIG. 1 is a schematic diagram showing usage scenarios for Enhanced mobile broadband (emBB), Massive Machine Type Communications (mMTC), and Ultra Reliable and Low Latency Communications (URLLC). [Diagram 5]FIG. 1 is a block diagram showing an example of a 5G system structure for a non-roaming scenario. [Figure 6A] FIG. 1 is a schematic diagram of uplink and downlink MIMO communication between a base station (gNB) and a terminal (UE) in a MIMO (multiple-input multiple-output) wireless network. [Figure 6B] FIG. 1 is a schematic diagram of downlink multi-user MIMO (MU-MIMO) communication between a gNB and multiple UEs in a MIMO wireless network. [Figure 6C] FIG. 1 is a schematic diagram of uplink MU-MIMO communication between a gNB and multiple UEs in a MIMO wireless network. [Figure 7] FIG. 1 illustrates a beam obstruction recovery procedure according to various embodiments. [Figure 8] 1 illustrates a schematic example of a communications device, which may be implemented as a gNB or a UE, and may be configured for beam failure detection and recovery, in accordance with various embodiments of the present disclosure. [Figure 9] A diagram showing a wireless network transmitting a message sequence between one or more UEs and one or more cells or gNBs in accordance with one embodiment. [Figure 10] A diagram showing configuration information for beam failure recovery (BFR) of multiple SCells based on a group-based scenario in one embodiment. [Figure 11] FIG. 11 is a diagram showing a table of BFR configuration information for group-based SCell according to one embodiment. [Figure 12] FIG. 1 illustrates an electronic device in accordance with one embodiment.

[0009] Those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Embodiments of the present disclosure will now be described, by way of example only, with reference to the drawings in which like reference numbers and letters indicate like or equivalent elements.

[0011] <5G NR system structure and protocol stack> 3GPP is working on the next release of the fifth generation of cellular technology (simply called 5G), which includes the development of new radio (NR) access technology that will operate in frequency bands up to 100 GHz. The "Non-Stand-Alone (NSA)" NR specification for the 5G standard was first delivered in late 2017. In 2018, 3GPP Release 15, the first version of the 5G standard, was completed to enable "Stand-alone (SA)" 5G for NR systems. This has allowed for the trial and commercial deployment of smartphones compliant with the 5G NR standard to proceed.

[0012] The overall system architecture is envisaged, inter alia, as NG-RAN (Next Generation - Radio Access Network), which comprises gNBs providing NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and RRC (Radio Resource Control) protocol termination for UEs. The gNBs are interconnected by Xn interfaces. The gNBs are also connected to the Next Generation Core (NGC) by Next Generation (NG) interfaces, more specifically to the Access and Mobility Management Function (AMF) (e.g. a specific core entity running AMF) by NG-C interfaces, and to the User Plane Function (UPF) (e.g. a specific core entity running UPF) by NG-U interfaces. The NG-RAN architecture is shown in Figure 1 (see, for example, section 4 of 3GPP TS 38.300 v15.6.0).

[0013] The NR user plane protocol stack (see, for example, section 4.4.1 of 3GPP TS 38.300) consists of the PDCP (Packet Data Convergence Protocol, see section 6.4 of 3GPP TS 38.300), RLC (Radio Link Control, see section 6.3 of 3GPP TS 38.300), and MAC (Medium Access Control, see section 6.2 of 3GPP TS 38.300) sublayers, which terminate at the gNB on the network side. In addition, a new access stratum (AS) sublayer (SDAP: Service Data Adaptation Protocol) is introduced above PDCP (see, for example, sub-clause 6.5 of 3GPP TS 38.300). NR also defines a control plane protocol stack (see, for example, section 4.4.2 of 3GPP TS 38.300). An overview of Layer 2 functionality is given in sub-clause 6 of 3GPP TS 38.300. The functionality of the PDCP, RLC, and MAC sublayers is given in sections 6.4, 6.3, and 6.2 of 3GPP TS 38.300, respectively. The functionality of the RRC layer is given in sub-clause 7 of 3GPP TS 38.300.

[0014] For example, the media access control layer is responsible for multiplexing logical channels, as well as scheduling and scheduling-related functions including different numerologies.

[0015] The physical layer (PHY) is responsible for, for example, coding, PHY HARQ processing, modulation, multi-antenna processing, and mapping of signals to appropriate physical time-frequency resources. It also maps transport channels to physical channels. The physical layer provides services to the MAC layer in the form of transport channels. A physical channel corresponds to a set of time-frequency resources used for transmission of a particular transport channel, and each transport channel is mapped to a corresponding physical channel. For example, the physical channels are PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), and PUCCH (Physical Uplink Control Channel) in the uplink, and PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel), and PBCH (Physical Broadcast Channel) in the downlink.

[0016] NR use cases / deployment scenarios include high speed / high capacity (eMBB), ultra-reliable low latency (URLLC), and massive multi-mode connections (mMTC), which have diverse requirements in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20Gbps downlink, 10Gbps uplink) and user-perceived data rates that are about three times higher than those offered in IMT-Advanced. On the other hand, URLLC has more stringent requirements for ultra-low latency (user plane latency of 0.5ms for both UL and DL) and high reliability (1-10-5 within 1ms). Finally, mMTC preferably requires high connection density (1 million devices per square kilometer in urban environments), wide coverage in harsh environments, and ultra-long battery life (15 years) for low-cost equipment.

[0017] Therefore, an OFDM numerology (e.g., subcarrier spacing, OFDM symbol duration, cyclic prefix (CP) duration, number of symbols per scheduling interval) suitable for one use case may not function well for other use cases. For example, low-latency services may preferably require a shorter symbol duration (and thus a larger subcarrier spacing) and / or fewer symbols per scheduling interval (in other words, TTI) than mMTC services. Further, in an introduction scenario with a large channel delay spread, a longer CP duration may preferably be required than in a scenario with a short delay spread. In order to maintain a similar CP overhead, the subcarrier spacing needs to be appropriately optimized. In NR, multiple values of subcarrier spacing may be supported. Correspondingly, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, … are currently being considered. The symbol duration Tu and the subcarrier spacing Δf are directly related by the equation Δf = 1 / Tu. Similar to the LTE system, the term "resource element" can indicate the smallest resource unit composed of one subcarrier corresponding to the length of one OFDM / SC-FDMA symbol.

[0018] In the 5G NR system, for each numerology and carrier, a resource grid of subcarriers and OFDM symbols is defined for the uplink and downlink respectively. Each element in the resource grid is called a resource element and is identified based on the frequency index in the frequency domain and the symbol position in the time domain (see 3GPP TS 38.211 v15.6.0).

[0019] <5G NR Functional Split between NG-RAN and 5GC> Figure 2 shows the functional split between NG-RAN and 5GC. The NG-RAN logical node is gNB or ng-eNB. The 5GC includes logical nodes of AMF, UPF, and SMF.

[0020] Specifically, the gNB and ng-eNB will perform the following main functions: Radio resource management functions such as radio bearer control, radio admission control, connection mobility control, dynamic allocation (scheduling) of resources to UEs in both uplink and downlink IP header compression, data encryption and integrity protection AMF selection at UE attach time if routing to AMF cannot be determined from information provided by the UE Routing user plane data to the UPF Routing of control plane information to AMF Setting up and disconnecting a connection Scheduling and sending paging messages Scheduling and transmission of system broadcast information (originating from AMF or OAM) Mobility and scheduling measurement and measurement reporting settings Transport-level packet marking in the uplink Session Management Support for network slicing QoS flow management and allocation to data radio bearers Support for UEs in RRC_INACTIVE state -NAS message delivery function Wireless connection network sharing Dual Connectivity Close cooperation between NR and E-UTRA

[0021] The Access and Mobility Management Function (AMF) performs the following main functions: Termination of Non-Access Stratum (NAS) signaling NAS signaling security ·Security control of the access stratum (AS) Inter-Core Network (CN) node signaling for mobility between 3GPP access networks Reachability to idle mode UEs (including control and execution of paging retransmissions) ·Registration area management Support for intra-system and inter-system mobility Access authentication Access authorization, including roaming rights checks Mobility management controls (subscriptions and policies) Support for network slicing ·Session Management Function (SMF) selection

[0022] Furthermore, the User Plane Function (UPF) performs the following main functions: Anchor points for intra-RAT / inter-RAT mobility (if applicable) External PDU session points for interconnection to data networks Packet Routing and Forwarding - User plane part for packet inspection and policy rule enforcement Traffic usage report An uplink classifier that supports routing of traffic flows to the data network Branching point supporting multi-homed PDU sessions User plane QoS processing, including packet filtering, gating, and UL / DL rate enforcement -Verification of uplink traffic (SDF to QoS flow allocation) Downlink packet buffering and downlink data notification triggering

[0023] Finally, the Session Management Function (SMF) serves the following main functions: Session Management ·Allocation and management of the UE's IP address ·Selection and control of the UP function ·Configure traffic steering in the User Plane Function (UPF) to route traffic to the appropriate destination ·Policy enforcement and QoS control unit ·Notification of downlink data

[0024] <Procedures for RRC connection setup and reconfiguration> Figure 3 shows a part of the processing between the UE, gNB, and AMF (5GC entity) when the UE transitions from RRC_IDLE to RRC_CONNECTED in the NAS part (see 3GPP TS 38.300 v15.6.0).

[0025] RRC is a higher layer signaling (protocol) used for the configuration of the UE and the gNB. This transition specifically involves the AMF preparing UE context data (e.g., including PDU session context, security keys, UE radio capability, UE security capability, etc.) and sending it to the gNB with an INITIAL CONTEXT SETUP REQUEST. The gNB then activates AS security with the UE. This operation is performed by the gNB sending a Security Mode Command message to the UE and the UE responding with a Security Mode Complete message to the gNB. The gNB then performs reconfiguration to set up a Signaling Radio Bearer 2 (SRB2) and a Data Radio Bearer (DRB) by sending an RRCReconfiguration message to the UE and receiving an RRCReconfigurationComplete message from the UE. In the case of a signaling-only connection, SRB2 and DRB are not configured, so the steps related to RRC reconfiguration are skipped. Finally, the gNB informs the AMF that the setup procedure is complete in an INITIAL CONTEXT SETUP RESPONSE.

[0026] Therefore, in the present disclosure, a fifth generation core (5GC) entity (e.g., AMF, SMF, etc.) is provided, which includes a control circuit that, during operation, establishes a next generation (NG) connection with a gNodeB, and a transmitter that, during operation, transmits an initial context configuration message to the gNodeB via the NG connection to configure a signaling radio bearer between the gNodeB and a terminal (UE). Specifically, the gNodeB transmits Radio Resource Control (RRC) signaling including a resource allocation configuration information element to the UE via the signaling radio bearer. Then, the UE performs uplink transmission or downlink reception based on the resource allocation configuration.

[0027] <IMT usage scenarios after 2020> Figure 4 shows some of the use cases for 5G NR. The 3rd Generation Partnership Project NR (3GPP NR) is considering three use cases that are expected to support a wide variety of services and applications with IMT-2020. The specifications for Phase 1 of enhanced Multimedia Broadcasting (eMBB) have been finalized. In addition to further expanding eMBB support, current and future research is also being conducted on the standardization of ultra-reliable low latency (URLLC) and multiple simultaneous connections. Figure 4 shows examples of usage scenarios that are expected for IMT beyond 2020 (see, for example, Figure 2 in ITU-R M.2083).

[0028] URLLC use cases have stringent requirements for capabilities such as throughput, latency, and availability, and are envisioned as one of the enablers of future vertical applications such as wireless control of industrial production and manufacturing processes, remote medical surgery, power distribution automation for smart grids, and road safety. URLLC's ultra-high reliability is supported by identifying technologies that meet the requirements set by TR 38.913. For NR URLLC in Release 15, the key requirement is to target user plane latency of 0.5 ms UL (uplink) and 0.5 ms DL (downlink). Typical URLLC requirements for a single packet transmission are a user plane latency of 1 ms and a block error rate (BLER) of 1E-5 for a packet size of 32 bytes.

[0029] From a physical layer perspective, there are various ways to improve reliability. Currently, possible ways to improve reliability include the definition of a separate CQI table for URLLC, more compact DCI formats, PDCCH repetition, etc. However, as NR becomes more stable and develops (for the main requirement of NR URLC), the scope of possibilities to achieve ultra-high reliability may expand. Specific use cases for NR URLLC in Release 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.

[0030] Additionally, NR URLLC targets technology enhancements for improved latency and improved reliability. Technology enhancements for improved latency include configurable numerology, non-slot-based scheduling with flexible mapping, grant-free uplink, slot-level repetition of data channels, and pre-emption for downlink. Pre-emption means stopping a transmission that already has resources allocated and using the already allocated resources for another transmission that requires less latency or higher priority, which is requested later. Thus, a transmission that has already been granted is preempted by a later transmission. Pre-emption can be applied independently of the specific service type. For example, a transmission of service type A (URLC) may be preempted by a transmission of service type B (e.g., eMBB). Technology enhancements for improved reliability include dedicated CQI / MCS tables for a target BLER of 1E-5.

[0031] mMTC (Massively Simultaneous Connections) use cases are typically characterized by a very large number of connected devices transmitting relatively small amounts of non-delay sensitive data. The devices are required to be low cost and have a very long battery life. From an NR perspective, utilizing a very narrow bandwidth portion is one way to enable power savings and long battery life for the UE.

[0032] As mentioned above, the reliability range in NR is expected to be wider. One of the key requirements common to all cases, and especially required for URLLC and mMTC, is high or ultra-high reliability. To improve reliability, several mechanisms are possible from a radio perspective and a network perspective. In general, there are several key areas that help improve reliability. These areas include compact control channel information, repetition of data / control channels, diversity in frequency, time and space domains, etc. These areas generally apply to reliability, regardless of the specific communication scenario.

[0033] For NR URLLC, additional use cases with more stringent requirements have been identified, such as factory automation, the transportation industry, and power distribution. The more stringent requirements include high reliability (up to level 10), high availability, a packet size of up to 256 bytes, time synchronization on the order of several μs (1 μs or several μs depending on the frequency range), and a short delay on the order of 0.5 to 1 ms (in particular, a target user plane delay of 0.5 ms), depending on the use case. -6 Furthermore, in NR URLLC, several technical enhancements have been identified from the perspective of the physical layer. These include enhancements related to compact DCI, repetition of the PDCCH (Physical Downlink Control Channel), increased PDCCH monitoring, and enhanced PDCCH. In addition, the enhancement of uplink control information (UCI) is related to the enhancement of extended HARQ (Hybrid Automatic Repeat Request) and CSI feedback. Also, enhancements to the PUSCH related to hopping and retransmission / repetition at the mini-slot level have been identified. A "mini-slot" represents a transmission time interval (TTI) that contains fewer symbols than a slot (a slot consisting of 14 symbols).

[0034]

[0035] <QoS Control> The 5G QoS (Quality of Service) model is based on QoS flows and caters to both QoS flows that require a guaranteed flow bit rate (GBR QoS flows) and those that do not (non-GBR QoS flows). Therefore, at the NAS level, QoS flows represent the finest granularity for QoS differentiation within a PDU session. QoS flows are identified within a PDU session by a QoS flow ID (QFI) contained in the encapsulation header on the NG-U interface.

[0036] For each UE, the 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes at least one Data Radio Bearer (DRB) with the PDU session, and additional DRBs for the QoS flows of that PDU session may be configured subsequently (when it is up to the NG-RAN), e.g. as described above with reference to Figure 3. The NG-RAN places packets belonging to different PDU sessions in different DRBs. UE and 5GC NAS level packet filters associate UL and DL packets with QoS flows, while UE and NG-RAN AS level mapping rules associate UL and DL QoS flows with DRBs.

[0037] Figure 5 shows the non-roaming reference structure for 5G NR (see 3GPP TS 23.501 v16.1.0, section 4.23). In Figure 5, an application function (AF), such as an external application server hosting 5G services, interacts with the 3GPP core network to provide the service, for example to support application influence on traffic routing, to access the Network Exposure Function (NEF), and to interact with the policy framework for policy control such as QoS control (see Policy Control Function (PCF)). Based on the operator's deployment, application functions that are considered trusted by the operator can interact directly with the relevant network function. Application functions that are not allowed to directly access the network function by the operator use the external contact framework via the NEF to interact with the relevant network function.

[0038] Figure 5 shows further functional units of the 5G architecture, namely Network Slice Selection Function (NSSF), Network Repository Function (NRF), Unified Data Management (UDM), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF) and Data Network (DN) (operator services, internet access, third party services, etc.). All or some of the core network functions and application services may be deployed and executed on a cloud computing environment.

[0039] Therefore, in the present disclosure, there is provided an application server (e.g., an AF in a 5G architecture) comprising: a transmitter unit that, during operation, sends a request including QoS requirements for at least one of URLLC, eMMB, and mMTC services to at least one of the 5GC functions (e.g., NEF, AMF, SMF, PCF, UPF, etc.) to establish a PDU session including a radio bearer between a gNodeB and a UE in accordance with the QoS requirements; and a control circuit that, during operation, performs a service using the established PDU session.

[0040] In the following paragraphs, some example embodiments for beam failure recovery operations in particular in MIMO wireless networks are described with reference to gNBs and UEs.

[0041] In a MIMO wireless network, "multiple" refers to multiple antennas used simultaneously for transmission and multiple antennas used simultaneously for reception on a wireless channel. In this regard, "multiple-input" refers to multiple transmit antennas that input wireless signals to a channel, and "multiple-output" refers to multiple receive antennas that receive wireless signals from the channel and feed them into a receiver. For example, in an N×M MIMO network system, N is the number of transmit antennas and M is the number of receive antennas, where N and M may or may not be equal. For simplicity, the respective numbers of transmit and receive antennas will not be further described in this disclosure. FIG. 6A illustrates a schematic diagram of single-user (SU) MIMO communication 600 between a base station (gNB) 602 and a terminal (UE) 604 in a MIMO wireless network. As illustrated, the MIMO wireless network may include one or more UEs (e.g., UE 604, UE 606, etc.). In SU-MIMO communication 600, the gNB 602 transmits multiple space-time streams using multiple antennas (e.g., four antennas as shown in FIG. 6A ), with all space-time streams directed to one communication device, i.e., the UE 604. For simplicity, the multiple space-time streams directed to the UE 604 are shown as a grouped data transmission arrow 608 directed to the UE 604.

[0042] The SU-MIMO communication 600 can be configured to allow bidirectional transmission. As shown in FIG. 6A, in the SU-MIMO communication 600, the UE 604 transmits multiple space-time streams using multiple antennas (e.g., two antennas as shown in FIG. 6A) with all space-time streams directed to the gNB 602. For simplicity, the multiple space-time streams directed to the gNB 602 are shown as a grouped data transmission arrow 610 directed to the gNB 602.

[0043] Thus, the SU-MIMO communication 600 shown in FIG. 6 enables both uplink and downlink SU transmissions in a MIMO wireless network.

[0044] 6B is a schematic diagram of downlink MU-MIMO communication 612 between a gNB 614 and multiple UEs 616, 618, 620 in a MIMO wireless network. The MIMO wireless network may include one or more UEs (e.g., UE 616, UE 618, UE 620, etc.). In downlink MU-MIMO communication 612, the gNB 614 transmits multiple streams simultaneously to the UEs 616, 618, 620 in the network using multiple antennas through spatial mapping or precoding techniques. For example, two space-time streams may be directed to the UE 618, another space-time stream may be directed to the UE 616, and yet another space-time stream may be directed to the UE 620. For simplicity, the two space-time streams directed to UE 618 are shown as grouped data transmission arrow 624, the space-time stream directed to UE 616 is shown as data transmission arrow 622, and the space-time stream directed to UE 620 is shown as data transmission arrow 626.

[0045] 6C is a schematic diagram of uplink MU-MIMO communication 628 between a gNB 630 and multiple UEs 632, 634, 636 in a MIMO wireless network. The MIMO wireless network may include one or more UEs (e.g., UE 632, UE 634, UE 636, etc.). In uplink MU-MIMO communication 628, the UEs 632, 634, 636 simultaneously transmit respective streams to a gNB 630 in the network using respective antennas through spatial mapping or precoding techniques. For example, two space-time streams may be directed from the UE 634 to the gNB 630, another space-time stream may be directed from the UE 632 to the gNB 630, and yet another space-time stream may be directed from the UE 636 to the gNB 630. For simplicity, the two space-time streams directed from the UE 634 to the gNB 630 are shown as grouped data transmission arrow 640, the space-time stream directed from the UE 632 to the gNB 630 is shown as data transmission arrow 638, and the space-time stream directed from the UE 636 to the gNB 630 is shown as data transmission arrow 642.

[0046] Beamforming is a signal processing technique that directs wireless network signal transmission and reception electronics through an array of antennas to identify the most efficient data transport path from the base station (gNB) to the UE. Signals at certain angles experience constructive interference, while signals at other angles experience destructive interference. Beamforming is useful for massive MIMO arrangements, where MIMO uses large antenna arrays at one or more electronics (e.g., gNBs) to transmit simultaneously to many autonomous UEs. MIMO allows wireless networks to simultaneously transmit and receive multiple data signals over the same radio channel via many antennas and / or antenna arrays.

[0047] Due to the large propagation losses associated with the millimeter waves used to transmit signals, some networks use beamforming and massive MIMO techniques. In networks that transmit using beamforming, technical challenges arise in establishing and maintaining a beam pair with sufficient connectivity between the transmitting beam direction and the receiving beam direction. Furthermore, problems arise when this connectivity is interrupted or insufficient. For example, an obstacle may block the direct path between the transmitter and receiver, or a change in the environment may disrupt the beam pair. For example, beam failure occurs when an event blocks or disturbs an established beam pair (e.g., when the UE moves to a location that blocks radio transmissions or moves to a location outside the coverage of the current serving cell). Beam recovery is then performed to re-establish the connection of the beam pair.

[0048] Exemplary embodiments solve these and other technical problems in networks performing beamforming. These embodiments include, but are not limited to, apparatus and methods for performing BFR. Advantages of these solutions include, but are not limited to, reduced uplink radio overhead, reduced measurement effort for BFD, simplified BFR procedure execution, and faster re-establishment of beam pair connectivity in the network.

[0049] Exemplary embodiments include BFR for a PCell, a SCell, and a group of cells (e.g., a group of PCell and SCell, a group of SCells only, or a group-based SCell). A PCell represents a cell operating on a primary frequency. For example, this includes a cell where the UE has either performed an initial connection establishment procedure or initiated a connection re-establishment procedure, or a cell that has been indicated as a primary cell in a handover procedure. A SCell represents a cell operating on a secondary frequency. For example, this cell may be configured when a radio resource control (RRC) connection is established and may be used to provide additional radio resources. According to various embodiments, a "secondary cell" (or "SCell") may be used interchangeably with a "component carrier" (or "CC").

[0050] Exemplary embodiments further include BFRs for downlink (DL), uplink (UL), and DL and UL. For example, exemplary embodiments include BFRs for SCells that support both DL and UL, as well as DL only (e.g., when PCells operate in Frequency Range 1 (FR1) and FR2). In one embodiment, FR1 includes sub-6 GHz frequency bands, and FR2 includes frequency bands from about 24 GHz to 52 GHz.

[0051] 7 illustrates a Beam Failure Recovery (BFR) procedure 700 according to various embodiments. The procedure 700 is a high-level diagram illustrating detection of and recovery from beam failures. The procedure includes one or more of the following steps: Beam Failure Detection (BFD), New Beam Identification (NBI), Beam Failure Recovery Request (BFRQ), and Beam Failure Recovery Response (BFRR).

[0052] Block 702 states performing BFD. Beam failure may occur for various reasons. The UE may obtain radio level link quality of periodic channel state information reference signal (CSI-RS) to detect beam failure of SCell. If the level link quality of all corresponding CSI-RS resources exceeds a threshold at a certain time instance (this threshold is defined as a level at which the downlink radio link cannot be reliably received, and corresponds to the block error rate outage (BLER_out) of the virtual downlink control channel (PDCCH) transmission), a beam failure instance (BFI) may be identified. The physical layer (PHY) issues a BFI indication to the media access control (MAC) layer. The BFD procedure in MAC is defined by a timer and a counter that calculates the number of BFI indications (BFII). Each time a BFI indication is received, the timer is restarted and the counter is reset when the timer expires. On the other hand, if N consecutive BFIIs are received, the BFII may be detected. max When the UE detects (beamFailureInstanceMaxCount) times, it can declare that a beam failure has occurred on the SCell. The CSI-RS can be explicitly configured to measure BFD by a radio resource control protocol message or can be implicitly configured by the transmission configuration indicator (TCI) state of the higher layer parameters for PDCCH reception. The channel state information (CSI) is a collection of spatial transfer functions between each antenna of the base station's antenna array and the UE. The CSI information is stored, for example, in a matrix and is used for encoding and decoding data transmitted and received by the antenna array.

[0053] Block 704 recites performing NBI. In an exemplary embodiment, a new beam or a new beam pair is determined to re-establish or restore connectivity between the UE and the cell. Consider an exemplary embodiment that includes a set or series of CSI-RS or Synchronization Signal (SS) blocks to re-establish connectivity. Consider an exemplary embodiment that transmits these signals in downlink beams. These signals represent a set of candidate beams. For example, in an exemplary embodiment, the L1 reference signal received power (L1-RSRP) of a reference signal for multiple candidate beams is measured. When the measured L1-RSRP exceeds a predefined value, connectivity is restored because the reference signal corresponds to a new beam.

[0054] Block 706 describes execution of BFRQ. BFRQ is not transmitted until a beam failure is declared in the MAC layer. In the conventional BFR for each SCell, max N from PHY within the timer duration of ×T max A MAC layer beam failure is declared after receiving (N max and the periodicity T of the BFD RS (beamFailureDetectionTimer) are separately configurable values). The device transmits a BFRQ to a network or device (e.g., a cell) to inform the network or device that a beam failure has been detected. The information provided with each BFRQ may include information about the candidate beams.

[0055] Block 708 states perform BFRR. After performing the BFRQ, the exemplary embodiment monitors the downlink for a network or device response to the BFRQ. For example, the response may be a quasi co-location (QCL) of the PDCCH using a resource set associated with the candidate beam included in the BFRQ. Two antenna ports are considered quasi co-located (QCL) if the characteristics of the channel over which symbols on one antenna port are conveyed can be inferred from the channel over which symbols on the other antenna port are conveyed. After the BFRQ is transmitted, if no response is received within a predefined time frame or window, the device retransmits the BFRQ.

[0056] Generally, BFD for SCell is based on periodic CSI-RS. UE transmits BFII to N max After receiving the group-based SCell, the UE declares BF and transmits BFRQ. During BFRQ, the UE conveys the BF event and reports the index of the failed SCell (in other words, the index of the failed CC) and the new beam (if any), but the UE reports only one new beam information per SCell. However, there is little discussion on communication devices and methods for beam failure recovery in relation to group-based SCell.

[0057] Since a group of SCells may share similar beam failure conditions, such as statistical channel / beam characteristics (large-scale parameter statistical characteristics), the BFD of a group of SCells can be determined based on one failure of one of them. This can simplify the BFD and BFR when multiple SCells are configured. The BFR procedure also poses additional technical challenges and problems for networks that perform beamforming using group-based SCells. As an example, there are problems of how a UE is informed of the execution of BFR of a group-based SCell, and how a UE determines and reports beam failures of multiple SCells based on one identifier. The exemplary embodiment also provides technical solutions to these problems.

[0058] One example embodiment is a communications device comprising: a receiver for receiving configuration information for BFR for a plurality of SCells operating in a network; and a circuit for performing BFD and reporting based on the configuration information.

[0059] Another example embodiment is a method in which a communications device receives configuration information for BFR for multiple SCells operating in a network, and the communications device performs BFD and reporting based on the configuration information.

[0060] FIG. 8 illustrates a schematic partial cross-sectional view of a communication device 800 according to various embodiments. The communication device 800 may be implemented as a gNB or a UE according to various embodiments and may provide functionality for beam failure recovery. As shown in FIG. 8, the communication device 800 may include a circuit 814 including at least one receiving signal processing unit 810, at least one radio transmitting unit 802, at least one radio receiving unit 804, and at least one antenna 812 (for simplicity, only one antenna is illustrated in FIG. 8 for illustrative purposes). The at least one radio receiving unit 804 may receive BFD and BFR configuration information for multiple SCells operating in the network, which may include group information including (explicitly or implicitly) a list of component carriers for each group, BFD configuration information, and beam failure (BF) reporting configuration information including at least a group identifier for each group to be reported. The circuit 814 may further include at least one transmitting signal processing unit 808. The circuit 814 may also include at least one controller (processor) 806, which is used to execute the tasks it is designed to perform (including controlling communication with one or more other communication devices in the MIMO wireless network) with the aid of software and hardware. The at least one controller 806 may control the receive signal processor 810 and the transmit signal processor 808. The at least one controller 806 may control the receive signal processor 810 to receive configuration information. The at least one controller 806 in the circuit 814 may perform beam failure detection and reporting based on the received configuration information. The at least one wireless transmitter 802 may transmit a beam failure report.

[0061] 9 illustrates a wireless network 900 transmitting a message sequence 906 between one or more UEs 902 and one or more cell or base station (gNB) 904 according to one embodiment. The sequence includes the UE receiving configuration information from the gNB, the UE performing BFD, and the UE generating and transmitting a beam failure report to the gNB.

[0062] In the initial access procedure, the UE finds a base station (e.g., a cell), receives system information, and requests a connection with the cell. As an example, this procedure includes a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), which allow the UE to find, identify, and synchronize with a network and / or cell.

[0063] The transmission of signals between the UE and the cell is via multiple antennas and / or antenna arrays, and beamforming is performed. Considering the large number of antennas and / or antenna arrays in the network, the beams are narrow and beam tracking or beam pair connection may fail. When a beam failure occurs, in an exemplary embodiment, a message sequence 906 is performed as a beam recovery procedure or BFR to re-establish connectivity and beam pairing.

[0064] The gNB 904 sends the configuration information to the UE 902, as shown at 908. After receiving the configuration information, the UE performs BFD based on the configuration information received from the gNB, as shown at 910. The UE generates a BF report based on the received configuration information and sends the report to the base station, as shown at 912.

[0065] In an example embodiment, a UE receives beam failure recovery configuration information for multiple base stations or cells, such as multiple SCells and / or multiple cell groups, and performs BFD for these multiple cells, generates a report, and transmits the report to one or more base stations or cells (e.g., the base station providing the configuration information or another base station).

[0066] Consider an example embodiment in which multiple cells include multiple groups of SCells. The UE receives a new notification from the gNB informing the UE to perform BFR for multiple SCells based on a group-based scenario (e.g., a group of SCells and PCells or a group of SCells only). The new notification points to group-based SCell BFR configuration information (configurable per UE).

[0067] The configuration information includes one or more lists of component carriers (CCs) including group information, such as one or more of an indication of the number of groups to measure and / or report on, and an indication of which groups to measure and / or report on.

[0068] The configuration information may also include BFD configuration information for determining the BF of the group. For example, this information may include the minimum number of SCells in a failed state in the group (n min ) and the BFII threshold for each group (

number

[0069] BFD is a method to determine the number of SCells (s bf ) ≧ first threshold (n min ), or (2) the sum of BFIIs of all SCells in the group (M) ≧ the second threshold (

number

number

number

[0070] In an exemplary embodiment, n min has a (pre)fixed value equal to 1, which may be set according to a standard protocol or by the gNB. Here, the UE counts the BFII to detect the BF for each individual SCell in the group. For example, the UE counts the BFII of an SCell consecutively for N max After receiving n times, the BF of the SCell is determined. If any SCell in the group is identified as faulty, the BF of the group is declared. No further counting of BFII of other SCells in this group is performed. min If n has a (pre)fixed value of 1, several advantages arise: if the channel / beam characteristics of different SCells in a group are almost the same, the BFD measurement effort of the UE is reduced. min By fixing the value of,N,, the BFD calculation time and computational complexity (BFD TCC) max Another advantage is that it reduces dependency on

[0071] In another exemplary embodiment, n min has a (pre)fixed value greater than 1, which may be set according to a standard protocol or by the gNB. Here, the UE uses BFII and s to detect the BF of each SCell in the group. bf Count and. bf n min In this case, the UE declares that all SCells in the group are treated as failed. No further BFII counting is performed for this group. min Several advantages arise if n has a fixed (a priori) value greater than 1. minThe set value of is consistent across the network. This embodiment also reduces the BFD measurement effort of the UE and expedites the decision operation of declaring the BF for the group when the channel / beam characteristics of different SCells in the group are almost the same but still have some differences. In addition, another advantage is that the BFD TCC can be used to max and n min The benefits include reduced dependency on

[0072] In another exemplary embodiment, n min has a flexible value. For example, n min is flexibly notified by control information depending on the UE's capabilities, such as higher layer signaling or downlink control notification. For example, min The value of is flexibly signaled by the UE Capability Information Element (IE). min Several advantages arise if n has a flexible value. min The configured value of may be flexible and depend on one or more factors, e.g., UE capabilities. This embodiment reduces the BFD measurement effort of the UE and expedites the decision operation of declaring BF for the group when the channel / beam characteristics of different SCells in the group are almost the same but still have some differences. In addition, another advantage is that the BFD TCC can be used to determine the BF of the group. max and n min The benefits include reduced dependency on

[0073] In an exemplary embodiment,

number

number

number

number

[0074] In an exemplary embodiment,

number

number

number

number

number

[0075] In an exemplary embodiment, the BFD operation may be based on other methods or combinations of methods. For example, the UE may min or

number

[0076] Each group's BFD behavior can be set to one of five behavior options: min (2) A fixed value n greater than 1 min (3) Flexible value n min (4) Fixed value

number

number

[0077] Consider an example where there are three groups, where there are multiple possibilities or options to configure the BFD behavior for each individual group. For example, these options include a fixed value n equal to 1 that applies to the first, second, and third groups, respectively. min , a fixed value n greater than 1 min , fixed value

number

number

[0078] In an exemplary embodiment, the configuration information includes information of a BF report generated by the UE and transmitted to the cell. As an example, the information includes a group identifier (such as a group ID, a signaled CC index, or a configuration index order) for each individual group. The BF report configuration information may include a notification to report a BF event via the UL of the PCell (or PsCell) or the UL of the SCell (if the SCell supports both DL and UL). The information may also include a notification to report new beam information, if any. Furthermore, the information may include one or more of (1) a notification of the type of measurement information (MI) of the failure group to be reported (e.g., RSRP, SINR (Signal to Interference Plus Noise Ratio)), and (2) a notification to report the reason for the BF event, if known.

[0079] Notification of configuration information can be signaled explicitly and / or implicitly to the UE. Consider an example of an implicit approach that occurs via (pre)configured rules. For example, if CC1 configures cross-carrier scheduling with CC3 and CC5 in the same band, the list of CCs is implicitly defined as CC1, CC3 and CC5, and CC1 is considered as a group identifier. Consider an example of an explicit approach that occurs via control information. For example, this approach occurs at least via PDCCH DCI (Physical Downlink Control Channel Downlink Control Information), MAC CE (MAC Control Element) or RRC messages.

[0080] The content of the BF report may include various information. For example, the UE generates and transmits a BF report including at least a group identifier for each group notified by the configuration information. If the number of failure groups is greater than the number of useful groups at that time, the UE reports the useful group identifier. Otherwise, the UE reports the identifier of the failure group. According to this embodiment, the radio overhead of the uplink is reduced.

[0081] The configuration information may also be updated or changed. For example, the UE provides new beam information to the gNB, including CC index, spatial Rx parameters, and angle of arrival (AoA), if any. As an example, the gNB assigns new beams to an existing or new group by comparing its own large-scale properties with the properties of the notified SCell that represents the group. The gNB updates the configuration information to the UE. In one embodiment, the beam failure recovery configuration information of group-based SCells may be updated periodically or aperiodically.

[0082] In an example embodiment, the configuration information indicates that only the notified SCells of each group are explicitly or implicitly configured with BFD Reference Signals (BFD RS) (i.e., not all SCells in the group). Here, the UE receives a new notification from the gNB informing the UE to perform BFR for multiple SCells based on a group-based scenario. The new notification refers to the BFR configuration information of the group-based SCells.

[0083] The BFR configuration information for group-based SCell includes that the notified CC (SCell) is configured to perform and report BFD for each individual group. Here, only this notified SCell is configured with BFD Reference Signal (BFD RS) for each individual group, either explicitly or implicitly (i.e., not for all SCells in the group). This allows for a reduction in the BFD RS in the downlink. Furthermore, the gNB only needs to place BFR resources on one CC in the CC group, so other BFR resources can also be saved. In this case, the list of CCs does not need to be known to the UE, and the group identifier can be the order of the notified CC index or configuration index. Similarly, the gNB can also configure the BFD RS for the SCell on multiple CCs in the CC group, and the configuration information can indicate which CC performs and reports BFD based on UE capabilities and / or channel conditions.

[0084] According to the received group-based SCell BFR configuration information indicated by the new indication, the UE counts only the BFII of the notified SCell for each individual group. If the notified SCell is identified as faulty, BF for that group is declared. All SCells in the group are treated as faulty.

[0085] According to the received group-based SCell BFR configuration information indicated by the new indication, if the number of failure groups is greater than the number of useful groups at that time, the UE reports the useful group identifier. Otherwise, the UE reports the identifier of the failure group. This exemplary embodiment has several advantages. For example, according to this embodiment, the overhead of the BFD RS in the downlink and the radio overhead in the uplink are reduced. Also, according to this embodiment, the BFD measurement effort of the UE is reduced and the BFR procedure is simplified.

[0086] In an exemplary embodiment, in certain cases only the notified SCells of individual groups may explicitly or implicitly configure the BFD RS, and all SCells of different groups may explicitly or implicitly configure their respective BFD RS.

[0087] Exemplary embodiments include different group-based SCell BFR configuration information. Figure 10 illustrates configuration information 1000 for BFR of multiple SCells based on a group-based scenario according to an exemplary embodiment. Figure 11 illustrates a table 1100 of group-based SCell BFR configuration information according to an exemplary embodiment.

[0088] As shown in Figure 10 and Figure 11, the BFR configuration information of the group-based SCell is explicitly indicated in the following SCellBFRConfigInfo IE and Group-basedSCellBFRInfo-IE, where maxGroupNr indicates the maximum number of groups, maxNrofSCell indicates the maximum number of SCells, and RSRP-Range indicates the range of RSRP. The result is shown in Table 1100.

[0089] Those skilled in the art will understand that the data in Figures 10 and 11 are exemplary. Depending on the UE capabilities, there may be various other possibilities regarding the size of the tables, the data presented, etc. From the UE perspective, the capability IE for group-based SCell BFR operation may be exemplarily indicated as ENUMERATED {SCell-basedBFRInfo, Group-basedSCellBFRInfo, both}, where "SCell-basedBFRInfo" indicates that the UE supports BFR per SCell, "Group-basedSCellBFRInfo" indicates that the UE supports BFR for group-based SCell, and "both" indicates that the UE supports both BFR per SCell and BFR for group-based SCell.

[0090] Exemplary embodiments may be applied to various scenarios when the BFR reference signal is explicitly configured by RRC or implicitly configured by the TCI state. For example, in the case of an explicit configuration by RRC, the BFD RS is transmitted on the current SCell. For example, in the case of an implicit configuration by the TCI state, the BFD RS is transmitted on the active bandwidth part (BWP) of either the current SCell or another SCell.

[0091] FIG. 12 illustrates an example of an electronic device 1200 in accordance with an exemplary embodiment.

[0092] The electronic device 1200 includes a power source 1202, a memory 1204, a central processing unit (CPU) 1206, storage 1208, a wireless transmitter and / or receiver 1210, an antenna 1212 (e.g., one or more antenna arrays or multiple antennas for performing beamforming), and a BFR 1214 (e.g., hardware and / or software for implementing one or more exemplary embodiments described in connection with Figures 6 to 11).

[0093] Consider an example embodiment in which the electronic device 1200 is a UE, an AP, a STA, a base station, a cell, or other electronic device.

[0094] The BFR 1214 of the electronic device 1200 includes hardware (e.g., circuitry) and / or software (e.g., code, instructions, or data) that operates to perform one or more of receiving BFR configuration information of multiple SCells operating in the network, performing BFD based on the configuration information, generating a BF report based on the configuration information, and transmitting the BF report to other electronic devices. The BFR 1214 also operates to perform one or more of BFD, NBI, BFRQ, and BFRR.

[0095] Exemplary embodiments may be implemented in various types of wireless networks that perform beamforming, such as 5G New Radio (NR) and mobile networks. Such networks include multiple transmit and / or receive antennas for beamforming. Channel state information may be obtained through transmission of CSI reports based on CSI reference signals in downlink and uplink.

[0096] The present disclosure can be realized by software, hardware, or software linked to hardware. Each functional block used in the description of the above embodiment may be realized partially or entirely as an LSI, which is an integrated circuit, and each process described in the above embodiment may be controlled partially or entirely by one LSI or a combination of LSIs. LSI is a process of integrating a large number of transistors on a silicon semiconductor microchip or chip, and includes VLSI (very large scale integrated circuit) and ULSI (ultra large scale integrated circuit). LSI may be composed of individual chips, or may be composed of one chip to include some or all of the functional blocks. LSI may have input and output of data. LSI may be called IC, system LSI, super LSI, or ultra LSI depending on the degree of integration. The method of integration is not limited to LSI, and may be realized by a dedicated circuit, a general-purpose processor, or a dedicated processor. In addition, FPGA (Field Programmable Gate Array) that can be programmed after LSI manufacture, or a reconfigurable processor that can reconfigure the connection and settings of the circuit cells inside the LSI may be used. The present disclosure may be realized as digital processing or analog processing. Furthermore, if an integrated circuit technology that replaces LSI appears due to the progress of semiconductor technology or a different derived technology, the integration of functional blocks may be performed using that technology. Application of biotechnology, etc. is also possible.

[0097] The present disclosure may be implemented in any type of apparatus, device, or system having a communication function (collectively referred to as a communication apparatus). The communication apparatus may include a radio transceiver and a processing / control circuit. The radio transceiver may include a receiver and a transmitter, or both as functions. The radio transceiver (transmitter, receiver) may include a radio frequency (RF) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or the like. The processing / control circuit may include a power management circuit, which may include dedicated circuitry, a processor, and instructions for power management control, either as firmware or instructions stored in a memory provided by the processor.

[0098] Non-limiting examples of communication devices include telephones (e.g., cell phones, smartphones, etc.), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks, etc.), cameras (e.g., digital still / video cameras), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices, etc.), game consoles, digital book readers, telehealth and telemedicine devices, communication-enabled vehicles or mobile conveyances (e.g., cars, airplanes, boats, etc.), and combinations of the above devices.

[0099] Communication equipment includes not only portable or mobile equipment, but also non-portable or fixed equipment, devices, and systems of any kind, such as smart home devices (home appliances, lighting equipment, smart meters or measuring devices, control panels, etc.), vending machines, and any other "things" that may exist on an IoT (Internet of Things) network. Communication includes data communication via cellular systems, wireless LAN systems, communication satellite systems, etc., as well as data communication via combinations of these.

[0100] A communications apparatus also includes devices, such as controllers and sensors, connected or coupled to a communications device that performs the communications functions described in this disclosure, such as controllers and sensors that generate control and data signals used by the communications device to perform the communications functions of the communications apparatus.

[0101] The communication apparatus also includes infrastructure facilities, such as base stations, access points, and any other apparatus, device, or system that communicates with or controls the various apparatuses listed above, but are not limited to these.

[0102] While exemplary embodiments have been set forth in the foregoing detailed description of the invention, it should be understood that numerous variations exist. It should also be understood that the exemplary embodiments are merely examples and are not intended to limit the scope, applicability, operation, or configuration of the present disclosure in any manner. Rather, the foregoing detailed description provides those skilled in the art with a useful road map for implementing the exemplary embodiments, and it should be understood that various modifications may be made to the functionality and arrangement of the network and / or UE transceiver apparatus described in the exemplary embodiments without departing from the scope of the present disclosure as set forth in the appended claims.

[0103] Other exemplary embodiments include, but are not limited to, the following examples.

[0104] A communication device comprising: a receiving unit that, during operation, receives configuration information for BFR of a plurality of SCells operating within a network; and a circuit that, during operation, performs BFD and reporting based on the configuration information.

[0105] In one embodiment, the configuration information includes a list of CCs.

[0106] In one embodiment, the BFD determines (1) the number of the plurality of SCells identified as faulty in a group (s bf ) is the threshold (n min) or more (however, n min is the minimum number of the plurality of SCells in a failure state in the group), or (2) the sum (M) of the BFIIs of the SCells in the group is greater than or equal to a threshold (

number

number

number

[0107] In one embodiment, the threshold (n min ) is a (pre) fixed value of 1, and the communication device is further configured to count the BFII for each SCell in the group and declare a beam failure (BF) for the group if any of the SCells in the group is identified as failing.

[0108] In one embodiment, the threshold (n min ) is a (pre) fixed value greater than 1, and the communication device counts the BFII to detect a beam failure (BF) for each SCell in the group, and s bf ≧n min if so, declare the SCell in the group to be in a failed state.

[0109] In one embodiment, the threshold (n min ) is flexibly notified by higher layer signaling or control information including downlink control notification depending on the capabilities of the communication device.

[0110] In one embodiment,

number

[0111] In one embodiment,

number

[0112] In one embodiment, n min or

number

[0113] In one embodiment, the configuration information includes a group identifier comprising a group ID, a signaled component carrier (CC) index, or a configuration index order per group.

[0114] In one embodiment, the notification of the configuration information is signaled based on (pre-)configured rules or at least one of the following control information via PDCCH DCI, MAC CE or RRC messages.

[0115] In one embodiment, the content of the BF report includes at least the group identifier for each group notified by the configuration information.

[0116] In one embodiment, the communication device is further configured to provide new beam information including a CC index, spatial Rx parameters, and AoA.

[0117] In one embodiment, the configuration information includes at least the indicated SCells which perform the BFD and reporting for each group, and only the indicated SCells can explicitly or implicitly configure BFD reference signals.

[0118] In one embodiment, if the number of failed groups is greater than the number of currently useful groups, the communication device reports the identifiers of the useful groups, otherwise the communication device reports the failed groups.

[0119] Another embodiment is a communication method in which a communication device receives configuration information for beam failure recovery (BFR) of multiple SCells operating in a network, and performs beam failure detection (BFD) and reporting based on the configuration information.

[0120] Although exemplary embodiments have been described in the detailed description of the examples above, it should be understood that there are numerous variations. It should also be understood that the exemplary embodiments are merely examples and are not intended to limit the scope, applicability, operation, or configuration of the present disclosure in any manner. Rather, the detailed description above provides those skilled in the art with a road map useful for implementing the exemplary embodiments, and it should be understood that various changes can be made in the functions, procedure arrangements, and operation methods described in the exemplary embodiments without departing from the scope of the present disclosure as set forth in the appended claims.

Claims

1. A transmitter that transmits beam failure recovery configuration information for a group of secondary cells, group information indicating one or more secondary cells included in the group of secondary cells, and a group identifier of the secondary cells; and a receiver configured to receive, based on the configuration information, the group information, and a group identifier of the secondary cell, report information including at least one of a result of beam failure detection in the group of the secondary cell identified and new beam information in the group of the secondary cell, in one resource configured for the group of the secondary cell. Communications equipment.

2. The report information includes the number of each secondary cell identified as having a beam failure in the beam failure detection, The communication device according to claim 1 .

3. The report information includes new beam information for each secondary cell identified as having a beam failure in the beam failure detection. The communication device according to claim 2 .

4. When the number of beam failure instances in any of the secondary cells in the group of secondary cells is equal to or greater than a first threshold indicated by a base station, the report information is transmitted. The communication device according to claim 1 .

5. When the number of secondary cells identified as having a beam failure in the beam failure detection in the group of secondary cells is one or more, the report information is transmitted. The communication device according to claim 1 .

6. When the number of secondary cells identified as having a beam failure in the beam failure detection in the group of secondary cells is equal to or greater than a second threshold instructed by a base station, the report information is transmitted. The communication device according to claim 1 .

7. The setting information indicates a setting regarding reporting of the beam obstruction detection. The communication device according to claim 1 .

8. Transmitting beam failure recovery configuration information for a group of secondary cells, group information indicating one or more secondary cells included in the group of secondary cells, and a group identifier of the secondary cells; receiving report information including at least one of a result of beam failure detection in the group of secondary cells identified based on the setting information, the group information, and a group identifier of the secondary cell and new beam information in the group of secondary cells, in one resource configured for the group of secondary cells; Communication methods.

9. The report information includes the number of each secondary cell identified as having a beam failure in the beam failure detection, The communication method according to claim 8.

10. The report information includes new beam information for each secondary cell identified as having a beam failure in the beam failure detection. The communication method according to claim 9.

11. When the number of beam failure instances in any of the secondary cells in the group of secondary cells is equal to or greater than a first threshold indicated by a base station, the report information is transmitted. The communication method according to claim 8.

12. When the number of secondary cells identified as having a beam failure in the beam failure detection in the group of secondary cells is one or more, the report information is transmitted. The communication method according to claim 8.

13. When the number of secondary cells identified as having a beam failure in the beam failure detection in the group of secondary cells is equal to or greater than a second threshold instructed by a base station, the report information is transmitted. The communication method according to claim 8.

14. The setting information indicates a setting regarding reporting of the beam obstruction detection. The communication method according to claim 8.

15. A process of transmitting beam failure recovery configuration information for a group of secondary cells, group information indicating one or more secondary cells included in the group of secondary cells, and a group identifier of the secondary cells; and receiving, via one resource configured for the group of secondary cells, report information including at least one of a result of beam failure detection in the group of secondary cells identified based on the configuration information, the group information, and a group identifier of the secondary cells. Integrated circuits.

Images