Group-based sceil beam failure recovery

Abstract

A communication apparatus includes a receiver and a circuit. The receiver receives configuration information for beam failure recovery (BFR) of a plurality of secondary cells (SCells) operating in a network. The circuit performs beam failure detection (BFD) and reporting based on the configuration information.

Description

TECHNICAL FIELD

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

[0002] Due to wireless network operations at higher frequency bands such as millimeter wave (mmWave) communications, the communication apparatus is equipped with large antenna arrays. This enables transmitting signals over multiple links with very narrow beams. These networks provide many advantages over traditional networks, such as very high data rate transmissions, but also include issues related to recovery protocols and management of multi-beam operations when beam failure occurs in the network.

[0003] Currently, only primary cell (PCell) and primary secondary cell (PsCell) beam failure recovery procedures are specified in 3GPP Rel (Release) 15 for 5G standards. Little discussion has been made on communication apparatus and methods for beam failure recovery in a group-based secondary cell (SCell) environment. SUMMARY

[0004] One non-limiting and exemplary embodiment facilitates providing enhancements for multi-beam operations in wireless networks. By way of example, the embodiment includes group-based SCell beam failure recovery in a network. It provides an efficient solution to simultaneously recover beam failures for multiple SCells configured to operate in the network.

[0005] According to the present disclosure, a communication apparatus is provided, comprising a receiver that receives configuration information for beam failure recovery (BFR) for multiple SCells operating in a network; and a circuit that performs beam failure detection (BFD) and reporting based on the configuration information.

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

[0007] Additional benefits and advantages of the disclosed embodiments will become apparent to those of ordinary skill in the art, upon perusal of the specification and drawings. Benefits and / or advantages can be attained by one or more of the embodiments and features described in the specification and drawings, but not necessarily by all of them. Not all possible embodiments can be realized and some embodiments can be practiced without all of these benefits and / or advantages. BRIEF DESCRIPTION OF DRAWINGS

[0008] The accompanying drawings are used to illustrate various embodiments and to explain various principles and advantages in accordance with various embodiments, in which like reference numerals refer to like elements throughout the several views, and the accompanying drawings are incorporated in and constitute a part of the specification.

[0009] Figure 1 An exemplary architecture of a 3GPP New Radio (NR) system is shown.

[0010] Figure 2 is a diagram illustrating the functional split between the Next Generation Radio Access Network (NG-RAN) and the 5G Core Network (5GC).

[0011] Figure 3 is a sequence diagram of a radio resource control (RRC) connection establishment / reconfiguration procedure.

[0012] Figure 4 is a diagram illustrating enhanced mobile broadband (eMBB), massive machine type communication (mMTC) and ultra-reliable low-latency communication (URLLC) usage scenarios.

[0013] Figure 5 is a block diagram illustrating an exemplary 5G system architecture for non-roaming scenarios.

[0014] Figure 6A depicts a diagram of uplink and downlink multiple-input multiple-output (MIMO) communication between a base station (gNB) and a user equipment (UE) in a MIMO wireless network.

[0015] Figure 6B depicts a diagram of downlink multi-user MIMO (MU-MIMO) communication between a gNB and multiple UEs in a MIMO wireless network.

[0016] Figure 6C depicts a diagram of uplink MU-MIMO communication between a gNB and multiple UEs in a MIMO wireless network.

[0017] Figure 7 depicts a beam failure recovery procedure according to various embodiments.

[0018] Figure 8 a schematic example of a communication apparatus according to various embodiments is shown. According to various embodiments of the present disclosure, the communication apparatus can be implemented as a gNB or a UE and configured for beam failure detection and recovery.

[0019] Figure 9 a wireless network according to example embodiments is shown having one or more UEs and one or more cells or gNBs that transmit a sequence of messages.

[0020] Figure 10 configuration information for beam failure recovery (BFR) of multiple SCells based on a group basic scenario according to example embodiments is shown.

[0021] Figure 11 A table showing group-based SCell BFR configuration information according to example embodiments is shown.

[0022] Figure 12 An electronic device according to example embodiments is shown.

[0023] Those skilled in the art will understand that the elements in the figures are shown for the purpose of simplicity and clarity and are not necessarily drawn to scale. DETAILED DESCRIPTION

[0024] Some embodiments of the disclosure will be described by way of example only with reference to the attached drawings. In the drawings, the same reference numbers and characters indicate the same elements or parts throughout the several views.

[0025] 5G NR System Architecture and Protocol Stack

[0026] 3GPP has been working on the next release of the fifth generation cellular technology (5G) including the development of New Radio (NR) access technology operating at frequencies as high as 100 GHz. The “non-standalone” (NSA) NR specification for 5G standards was initially delivered in late 2017. In 2018, 3GPP Release 15, the first version of the 5G standard, was completed, covering “standalone” (SA) 5G with new radio systems, which allowed for trials and commercial deployments of 5G NR-compliant smartphones.

[0027] In which the overall system architecture assumes a NG-RAN (Next Generation - Radio Access Network) including gNBs providing NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and radio resource control (RRC) protocol terminations to UEs. GNBs are connected to each other over an Xn interface. The gNBs are also connected to the NGC (Next Generation Core) over a Next Generation (NG) interface, more specifically, to an AMF (Access and Mobility Management Function) over an NG-C interface (e.g., a specific core entity performing the AMF) and to a UPF (User Plane Function) over an NG-U interface (e.g., a specific core entity performing the UPF). The NG-RAN architecture is shown in Figure 1 (e.g., see 3GPP TS 38.300 v15.6.0 section 4).

[0028] The user plane protocol stack for NR (see e.g. 3GPP TS 38.300, section 4.4.1) includes the PDCP (Packet Data Convergence Protocol, see TS 38.300 section 6.4), RLC (Radio Link Control, see TS 38.300 section 6.3) and MAC (Medium Access Control, see TS 38.300 section 6.2) sub-layers, which terminate at the gNB on the network side. In addition, a new Access Stratum (AS) sub-layer (SDAP, Service Data Adaptation Protocol) is introduced on top of PDCP (see e.g. 3GPP TS 38.300 subclause 6.5). A control plane protocol stack is also defined for NR (see e.g. TS 38.300, section 4.4.2). An overview of the layer 2 functionality is given in subclause 6 of TS 38.300. The functionality of the PDCP, RLC and MAC sub-layers is listed in sections 6.4, 6.3 and 6.2 of TS 38.300, respectively. The functionality of the RRC layer is listed in subclause 7 of TS 38.300.

[0029] For example, the medium access control layer handles logical channel multiplexing, as well as scheduling and scheduling-related functions, including handling of different numerologies.

[0030] The physical layer (PHY) is, for example, responsible for the codec, the PHY HARQ processing, the modulation, the multi-antenna processing, and the mapping of signals to the appropriate physical time-frequency resources. It also handles the mapping of 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 the 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) for the uplink and PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel) and PBCH (Physical Broadcast Channel) for the downlink.

[0031] Use cases / deployment scenarios for NR can include enhanced mobile broadband (eMBB), ultra-reliable low-latency Communication (URLLC), massive Machine Type Communication (mMTC), which have different requirements in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20 Gbps for downlink and 10 Gbps for uplink) and user experienced data rates that are about three times the user experienced data rates provided by IMT-Advanced. On the other hand, in the case of URLLC, more stringent requirements are placed on ultra-low latency (0.5 ms for user plane latency for both UL and DL) and high reliability (1-10-5 within 1 ms). Finally, mMTC can best require high connection density (1,000,000 devices / square kilometer in urban environment), large coverage in poor environments, and ultra-long battery life for low-cost devices (15 years).

[0032] Accordingly, OFDM numerology (e.g., subcarrier spacing, OFDM symbol duration, cyclic prefix (CP) duration, number of symbols per scheduling interval) that is suitable for one use case can not be suitable for another use case. For example, a low latency service can prefer a shorter symbol duration (and thus a larger subcarrier spacing) and / or fewer symbols per scheduling interval (i.e., TTI) than a mMTC service. Furthermore, a deployment scenario with large channel delay spread can prefer a longer CP duration than a scenario with short delay spread. The subcarrier spacing should be optimized accordingly to maintain similar CP overhead. NR can support more than one subcarrier spacing value. Accordingly, subcarrier spacing of 15 kHz, 30 kHz, 60 kHz,... are currently under consideration. The symbol duration Tu and the subcarrier spacing Af are directly related by the equation Af = 1 / Tu. In a similar manner as in the LTE system, the term "resource element" can be used to denote the smallest resource unit that includes one subcarrier of length one OFDM / SC-FDMA symbol.

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

[0034] 5G NR functional split between NG-RAN and 5GC

[0035] Figure 2This section explains the functional division between NG-RAN and 5GC. NG-RAN logical nodes are either gNBs or ng-eNBs. 5GC has logical nodes AMF, UPF, and SMF.

[0036] Specifically, gNB and ng-eNB host the following main functions:

[0037] - Functions for radio resource management, such as radio bearer control, radio access control, connection mobility control, and dynamic allocation (scheduling) of resources to the UE in the uplink and downlink;

[0038] - Data IP header compression, encryption, and integrity protection;

[0039] - When a route to the AMF cannot be determined based on the information provided by the UE, in the UE attachment

[0040] Select AMF in the component selection;

[0041] - Routing user plane data to UPF;

[0042] - Routing control plane information to AMF;

[0043] - Connection establishment and release;

[0044] - Scheduling and transmission of paging messages;

[0045] - Scheduling and transmission of system broadcast information (originating from AMF or OAM);

[0046] - Mobility and scheduling measurement and measurement reporting configuration;

[0047] -Transmission-level packet markings in the uplink;

[0048] -Session management;

[0049] -Support for network slicing;

[0050] - QoS flow management and mapping to data radio bearers;

[0051] - Supports UEs in the RRC_INACTIVE state;

[0052] -NAS message distribution functionality;

[0053] - Radio access network sharing;

[0054] - Dual connectivity;

[0055] -Close interoperability between NR and E-UTRA.

[0056] The Access and Mobility Management Function (AMF) hosts the following key functions:

[0057] - Non-Access Stratum, NAS, signaling termination;

[0058] - NAS signaling security;

[0059] - Access Stratum, AS, security control;

[0060] - Core Network, CN, inter-node signaling for mobility between 3GPP access networks;

[0061] - Idle mode UE reachability (including control and execution of paging retransmission);

[0062] - Registration area management;

[0063] - Support of intra- and inter-system mobility;

[0064] - Access authentication;

[0065] - Access authorization, including check on roaming permission;

[0066] - Mobility management control (subscription and policies);

[0067] - Support of network slicing;

[0068] - Session Management Function, SMF, selection.

[0069] Furthermore, the User Plane Function, UPF, hosts the following main functions:

[0070] - Anchor point for intra- / inter-RAT mobility (as applicable);

[0071] - External PDU session point of interconnect to data networks;

[0072] - Packet routing and forwarding;

[0073] - Packet inspection and user plane part of policy rule enforcement;

[0074] - Traffic usage reporting;

[0075] - Uplink classifier to support routing traffic flows to data networks;

[0076] - Branching point to support multi-homed PDU sessions;

[0077] - QoS handling for user plane, e.g., packet filtering, gating, UL / DL

[0078] - Uplink traffic verification (SDF to QoS flow mapping);

[0079] - Downlink packet buffering and downlink data notification triggering.

[0080] Finally, the Session Management Function, SMF, hosts the following main functions:

[0081] - Session management;

[0082] - UE IP address allocation and management;

[0083] - Selection and control of UP functions;

[0084] - Configuration of traffic handling at User Plane Function, UPF, to route traffic to the right destination;

[0085] - Control part of policy enforcement and QoS;

[0086] - Downlink data notification.

[0087] RRC connection establishment and reconfiguration procedure

[0088] Figure 3 Some interactions between the UE, gNB and AMF (5GC entities) in the context of the transition of the UE from RRC_IDLE to RRC_CONNECTED are illustrated (see TS 38.300 v15.6.0).

[0089] RRC is the higher layer signaling (protocol) used for UE and gNB configuration. Specifically, this transition involves the AMF preparing UE context data (including, for example, PDU session context, security keys, UE radio capabilities and UE security capabilities, etc.) and sending it to the gNB with an INITIAL CONTEXT SETUP REQUEST. Then, the gNB activates AS security with the UE, which is performed by the gNB sending a SecurityModeCommand message to the UE and the UE responding to the gNB with a SecurityModeComplete message. After that, the gNB performs reconfiguration to establish Signaling Radio Bearer 2, SRB2, and Data Radio Bearers, DRBs, by sending an RRCReconfiguration message to the UE and, in response, the gNB receives an RRCReconfigurationComplete from the UE. For a signaling-only connection, the steps related to RRCReconfiguration are skipped since no SRB2 and DRBs are established. Finally, the gNB informs the AMF that the setup procedure has been completed with an INITIAL CONTEXT SETUP RESPONSE.

[0090] Accordingly, in the present disclosure, an entity of a Fifth Generation Core (5GC) (e.g., AMF, SMF, etc.) is provided that includes control circuitry that establishes a Next Generation (NG) connection with a gNodeB, and a transmitter that transmits, to the gNodeB via the NG connection, an initial context setup message to cause signaling radio bearer setup between the gNodeB and a user equipment (UE). Specifically, the gNB transmits, to the UE via the signaling radio bearer, a radio resource control (RRC) signaling containing a resource allocation configuration information element. The UE then performs uplink transmission or downlink reception based on the resource allocation configuration.

[0091] Use scenarios for IMT in 2020 and beyond

[0092] Figure 4 Some use cases for 5G NR are illustrated. Three use cases are being considered in the Third Generation Partnership Project New Radio (3GPP NR) with the expectation that IMT will support a wide variety of services and applications by 2020. The first phase of specification for enhanced mobile broadband (eMBB) has been completed. In addition to further extending eMBB support, current and future work will involve standardization of ultra-reliable and low-latency communications (URLLC) and massive machine type communications. Figure 4 Some envisioned usage scenarios for IMT in 2020 and beyond are illustrated (see, e.g., ITU-R M.2083 Figure 2 ) for example.

[0093] URLLC use cases have stringent requirements on capabilities such as throughput, latency, and availability, and are envisioned to be one of the drivers for future vertical applications such as wireless control of industrial manufacturing or production processes, remote medical surgery, distribution automation in smart grids, transportation safety, etc. Ultra-reliability is supported for URLLC by identifying techniques that meet the requirements specified in TR 38.913. Key requirements for NR URLLC in Release 15 include a target user plane latency of 0.5 ms for UL (uplink) and a target user plane latency of 0.5 ms for DL (downlink). A general URLLC requirement for one transmission of a packet is a BLER (block error rate) of 1E-5 for a packet size of 32 bytes and a user plane latency of 1 ms.

[0094] From a physical layer perspective, reliability can be improved in a number of possible ways. The current scope of improving reliability involves defining separate CQI tables for URLLC, more compact DCI formats, repetition of PDCCH, etc. However, as NR becomes more stable and developed, the scope of achieving ultra-reliability can expand (a key requirement for NR URLLC). Specific use cases for NR URLLC in Rel. 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission critical applications.

[0095] In addition, the technical enhancements targeted by NR URLLC aim at latency improvement and reliability improvement. Technical enhancements for latency improvement include configurable numerology, non-slot-based scheduling with flexible mapping, grant-free (configured grant) uplink, slot-level repetition for data channels, and downlink pre-emption. Pre-emption means that a transmission that has been allocated resources is stopped, and the already allocated resources are used for another transmission requested later, but with lower latency / higher priority requirements. Thus, a transmission that has been granted is pre-empted by a later transmission. Pre-emption applies regardless of the specific service type. For example, a transmission of service type A (URLLC) can be pre-empted by a transmission of service type B (such as eMBB). Technical enhancements for reliability improvement include dedicated CQI / MCS tables for a target BLER of 1E-5.

[0096] The use cases for mMTC (massive machine type communication) are characterized by a large number of connected devices that typically transmit a relatively small amount of non-delay-sensitive data. The devices require low cost and long battery life. From the perspective of NR, utilizing very narrow bandwidth parts is one possible solution that can save power from the perspective of the UE and extend battery life.

[0097] As mentioned above, the scope of reliability for NR is expected to become broader. One key requirement for all these cases is high reliability or ultra-reliability, which is especially necessary for URLLC and mMTC. From a radio perspective and a network perspective, several mechanisms can be considered to improve reliability. In general, there are several key potential areas that can help improve reliability. These areas include compact control channel information, data / control channel repetition, and diversity in the frequency, time, and / or spatial domains. These areas are generally applicable to reliability regardless of the specific communication scenario.

[0098] For NR URLLC, other use cases have been identified that have more stringent requirements, such as factory automation, transportation industry, and power distribution, including factory automation, transportation industry, and power distribution. The more stringent requirements are higher reliability (up to 10 -6higher availability, packet sizes up to 256 bytes, time synchronization in the order of a few ps (where this value can be one or a few ps depending on the frequency range), and short latency in the order of 0.5 to 1 ms (with a target user plane latency of 0.5 ms depending on the use case).

[0099] In addition, for NR URLLC, several technical enhancements were identified from a physical layer perspective. These include PDCCH (Physical Downlink Control Channel) enhancements related to compact DCI, PDCCH repetition, increased PDCCH monitoring. In addition, UCI (Uplink Control Information) enhancements are related to enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback enhancements. PUSCH enhancements related to mini-slot level hopping and retransmission / repetition enhancements were also identified. The term "mini-slot" refers to a transmission time interval (TTI) that includes a smaller number of symbols than a slot (a slot includes fourteen symbols).

[0100] QoS Control

[0101] The 5G QoS (Quality of Service) model is based on QoS Flows, and supports QoS Flows that require a guaranteed bit rate (GBR QoS Flows) and QoS Flows that do not require a guaranteed bit rate (non-GBR QoS Flows). Therefore, at the NAS level, the QoS Flow is the finest granularity of QoS differentiation in a PDU Session. A QoS Flow is identified in a PDU Session by a QoS Flow ID (QFI) carried in encapsulation headers over the NG-U interface.

[0102] For each UE, the 5GC establishes one or more PDU Sessions. For each one, the NG-RAN establishes at least one Data Radio Bearer (DRB) together with the PDU Session, and can subsequently configure additional DRBs for the QoS Flows of that PDU Session (when this is done depends on the NG-RAN), e.g. as shown above with reference to Figure 3 The NG-RAN maps packets belonging to different PDU Sessions to different DRBs. NAS level packet filters in the UE and 5GC associate UL and DL packets with QoS Flows, while AS level mapping rules in the UE and NG-RAN associate UL and DL QoS Flows with DRBs.

[0103] Figure 5 A 5G NR non-roaming reference architecture is illustrated (see TS 23.501 v16.1.0 section 4.23). Application Functions (AFs), such as Figure 4The externally hosted 5G service application server, exemplarily described, interacts with the 3GPP core network in order to provide services, e.g. support application influence on traffic routing, access to a network exposure function (NEF) or interact with a policy framework for policy control (see policy control function, PCF), e.g. QoS control. Based on operator deployment, application functions considered to be trusted by the operator can be allowed to interact directly with the relevant network functions. Application functions not allowed direct access to network functions interact via the NEF with the relevant network functions using the external exposure framework.

[0104] Figure 5 Further functional units of the 5G architecture are shown, namely the network slice selection function (NSSF), the network repository function (NRF), the unified data management (UDM), the authentication server function (AUSF), the access and mobility management function (AMF), the session management function (SMF) and the data network (DN), e.g. operator services, internet access or third party services. All or parts of the core network functions and application services can be deployed and run in a cloud computing environment.

[0105] Therefore, in the present disclosure, an application server (e.g. AF of the 5G architecture) is provided, comprising a transmitter which transmits a request containing QoS requirements to at least one function of the 5GC (e.g. NEF, AMF, SMF, PCF, UPF, etc.) to establish a PDU session comprising a radio bearer between a gNodeB and a UE, For QoS requirements for at least one of URLLC, eMMB, and mMTC services . And control circuitry to perform services using the established PDU session .

[0106] In the following paragraphs, certain exemplary embodiments are explained with reference to a gNB and a UE for a beam failure recovery operation, in particular in a MIMO wireless network.

[0107] In a MIMO wireless network, “multiple” refers to multiple antennas used for transmission at the same time and multiple antennas used for reception at the same time on a radio channel. In this regard, “multiple input” refers to multiple transmitter antennas inputting a radio signal into a channel, and “multiple output” refers to multiple receiver antennas receiving a radio signal from the channel and inputting it into a receiver. For example, in a NxM MIMO network system, N is the number of transmitter antennas and M is the number of receiver antennas, and N can or can not be equal to M. For the sake of simplicity, the respective number of transmitter antennas and receiver antennas is not further discussed in the present disclosure. Figure 6AA diagram depicting single-user (SU) MIMO communication 100 between a base station (gNB) 602 and a user equipment (UE) 604 in a MIMO wireless network is depicted. As shown, the MIMO wireless network can include one or more UEs (e.g., UE 604, UE 606, etc.). In the SU-MIMO communication 600, the gNB 602 transmits multiple space-time streams using multiple antennas (e.g., four antennas as shown) where all space-time streams are directed to a single communication device, i.e., the UE 604. For simplicity, the multiple space-time streams directed to the UE 104 are shown as grouped data transmission arrows 108 directed to the UE 604. Figure 6A

[0108] The SU-MIMO communication 600 can be configured for bidirectional transmission. As shown, in the SU-MIMO communication 100, the UE 604 can transmit multiple space-time streams using multiple antennas (e.g., two antennas as shown) where all space-time streams are directed to the gNB 602. For simplicity, the multiple space-time streams directed to the gNB 602 are shown as grouped data transmission arrows 110 directed to the gNB 602. Figure 6A Figure 6A

[0109] In this way, the SU-MIMO communication 600 described in FIG. 6 enables uplink and downlink SU transmission in a MIMO wireless network.

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

[0111] Figure 6C ​​​A diagram depicting uplink MU-MIMO communication 628 between a gNB 630 and multiple UEs 632, 634, 636 in a MIMO wireless network is illustrated. The MIMO wireless network can include one or more UEs (e.g., UE 632, UE 634, UE 636, etc.). In the uplink MU-MIMO communication 628, the UEs 632, 634, 636 simultaneously transmit respective streams to the gNB 630 in the network via spatial mapping or precoding techniques using respective antennas. For example, two space-time streams can be directed from the UE 634 to the gNB 630, another space-time stream can be directed from the UE 632 to the gNB 630, and yet another space-time stream can 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 arrows 640, the space-time stream directed from the UE 632 to the gNB 630 is shown as a data transmission arrow 168, and the space-time stream directed from the UE 636 to the gNB 630 is shown as a data transmission arrow 642.

[0112] Beamforming is a signal processing technique that antenna arrays use to direct the signaling in a wireless network to and from electronic devices and to identify the most effective data transfer path from a base station (gNB) to a UE. Signals at certain angles are constructively interfered with, while signals at other angles are destructively interfered with. Beamforming can help with massive MIMO arrays, where MIMO uses large-scale antenna arrays at one or more electronic devices (e.g., gNBs) to simultaneously transmit to multiple autonomous UEs. MIMO enables a wireless network to send and receive more than one data signal at the same time on the same radio channel via multiple antennas and / or antenna arrays.

[0113] Due to the high propagation loss associated with millimeter waves used for signaling, some networks perform beamforming and massive MIMO techniques. In networks that use beamforming for transmissions, technical problems arise when establishing and maintaining a beam pair, in which a transmitter-side beam direction and a receiver-side beam direction exist with sufficient connectivity. More problems arise when connectivity is interrupted or becomes insufficient. For example, an obstacle can block the direct path between the transmitter and the receiver, or a change in the environment can disrupt the beam pair. Beam failure occurs, for example, when an event blocks or prohibits an established beam pair (e.g., a UE moves to a location that blocks wireless transmissions or moves to a location outside the current serving cell coverage). Beam recovery is then performed to reestablish connectivity with the beam pair.

[0114] Example embodiments address these and other technical problems in networks that perform beamforming. These embodiments include, but are not limited to, apparatuses and methods that perform BFR. Advantages of these solutions include, but are not limited to, reducing uplink radio overhead, reducing measurement effort for BFD, simplifying the performance of the BFR procedure, and speeding up the reestablishment of beam pair connectivity in the network.

[0115] Example embodiments include BFR for PCell, SCell, and groups of more than one cell, such as groups of PCell and SCell, groups of only SCell, or group-based SCell. A PCell refers to a cell that operates on a primary frequency. For example, the cell includes a cell in which a UE performs an initial connection establishment procedure, initiates a connection reestablishment procedure, or is indicated as a primary cell in a handover procedure. An SCell refers to a cell that operates on a secondary frequency. For example, the cell is configured once a radio resource control (RRC) connection is established, and the cell can be used to provide additional radio resources. According to various embodiments, the term “secondary cell” (or “SCell”) can be used interchangeably with the term “component carrier” (or “CC”).

[0116] Example embodiments also include BFR for downlink (DL), uplink (UL), and both DL and UL. For example, example embodiments specify BFR for SCells with both DL and UL, and DL only (e.g., where a PCell operates in frequency range 1 (FR1) and FR2). In embodiments, FR1 includes sub-6 GHz frequency bands, and FR2 includes frequency bands from approximately 24 GHz to 52 GHz.

[0117] Figure 7 A beam failure recovery (BFR) procedure 700 is depicted in accordance with various embodiments. The procedure 700 is a high level diagram showing the detection of a beam failure and recovery from the failure. 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).

[0118] Block 702 represents performing BFD. Beam failure can occur for various reasons. The UE can obtain radio-level link quality of periodic channel state information reference signals (CSI-RS) to detect beam failure of an SCell. When the link quality level of all corresponding CSI-RS resources in a time instance exceeds a threshold value (defined as a level at which the downlink radio link cannot be reliably received, and it corresponds to a block error rate outage (BLER_out) of a hypothetical downlink control channel (PDCCH) transmission), a beam failure instance (BFI) can be identified. The physical layer (PHY) provides a BFI indication to the medium access control (MAC) layer. The BFD procedure in the MAC is dictated by a timer and a counter that counts the number of BFI indications (BFII). Each time a BFI indication is received, the timer is restarted, and if the timer expires, the counter is reset. On the other hand, upon detecting N max (beamFailureInstanceMaxCount) consecutive BFII, the UE can declare that beam failure has occurred within the SCell. The CSI-RS can be explicitly configured to measure BFD through radio resource control protocol messages or implicitly configured through higher layer parameters transmission configuration indicator (TCI) states used for PDCCH reception. Channel state information (CSI) is a set of spatial transfer functions between each antenna in a base station antenna array and the UE. The CSI information is stored, for example, in a matrix, and used to encode and decode data transmitted from and received by the antenna array.

[0119] Block 704 represents performing NBI. Example embodiments determine a new beam or a new beam pair to reestablish or restore connectivity between the UE and the cell. Consider example embodiments that include a set or series of CSI-RS or synchronization signal (SS) blocks used to reestablish connectivity. Consider example embodiments that transmit these signals within a downlink beam. These signals represent a set of candidate beams. For example, example embodiments measure the L1 reference signal received power (L1-RSRP) on the reference signals of multiple candidate beams. When the measured value of L1-RSRP exceeds a predetermined value, connectivity is restored because the reference signal corresponds to a new beam.

[0120] Block 706 represents performing BFRQ. Because beam failure is declared at the MAC layer before the BFRQ is transmitted. For traditional per single SCell BFR, the BFRQ is transmitted after N max BFIs are received from the PHY within a timer duration of N max BFIs are received from the PHY within a timer duration of N maxAnd the BFD RS periodicity T (beamFailureDetectionTimer) is a separately configurable number. The device transmits a BFRQ to the network or device (e.g. cell) and informs the network or device that it has detected a beam failure. The information provided according to the BFRQ can include information about the candidate beam.

[0121] Block 708 represents performing the BFRR. After the performance of the BFRQ, the example embodiments monitor the downlink for a response to the BFRQ by the network or device. For example, the response transmits a PDCCH quasi co-located (QCL) with the resource set associated with the candidate beam included in the BFRQ. Two antenna ports are said to be quasi co-located (QCL) if the properties of the channel that carries the symbols on one antenna port can be inferred from the channel that carries the symbols on the other antenna port. If no response is received within a predetermined time frame or window after the BFRQ transmission, the device retransmits the BFRQ.

[0122] In general, SCell BFD is based on periodic CSI-RS. Upon receiving N max BFII, the UE declares a BF and then transmits a BFRQ. During the BRFQ, the UE transmits the BF event and reports the failed SCell index, i.e. the failed CC index, and the new beam (if present), where the UE reports only one new beam information per SCell. However, there are few discussions on communication apparatus and methods for beam failure recovery in the context of group-based SCells.

[0123] A group of SCells can share similar beam failure conditions, such as statistical channel / beam properties (statistical properties of large-scale parameters), and thus the BFD of a group of SCells can be determined based on a failure of one of the SCells. This can simplify the BFD and BFR when multiple SCells are configured. In addition, the BFR procedure also includes technical challenges and problems for networks that perform beamforming with group-based SCells. For example, these problems include how to inform the UE to perform group-based SCell BFR, and how the UE determines and reports beam failure of multiple SCells based on a single identifier. The example embodiments also provide technical solutions to these problems.

[0124] One example embodiment is a communication apparatus comprising a receiver that receives configuration information of BFR of a plurality of SCells operating in a network, and a circuit that performs beam BFD and reporting based on the configuration information.

[0125] Another example embodiment is a method comprising receiving, at a communication device, configuration information for BFR of a plurality of SCells operating in a network; and performing, by the communication device, BFD and reporting based on the configuration information.

[0126] Figure 8 A schematic partial cutaway view of a communication device 800 is shown in accordance with various embodiments. The communication device 800 can be implemented as a gNB or a UE and provide functionality for beam failure recovery in accordance with various embodiments. As shown, the communication device 800 can include circuitry 814 including at least one radio transmitter 802 and at least one radio receiver 804, and at least one antenna 812 (only one antenna is depicted in the interest of simplicity for the purpose of illustration, in the interest of simplicity for the purpose of illustration, only one antenna is depicted in Figure 8 Figure 8 The at least one radio receiver 804 can receive configuration information for BFD and BFR of a plurality of SCells operating in a network, which can include group information (explicit or implicit) including 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 circuitry 814 can also include at least one transmit signal processor 808. The circuitry 814 can also include at least one controller 806 for software and hardware aided execution of the tasks the at least one controller 806 is designed to perform, including controlling communications with one or more other communication devices in a MIMO wireless network. The at least one controller 806 can control the receive signal processor 810 and the transmit signal processor 808. The at least one controller 806 can control the receive signal processor 810 to receive the configuration information. The at least one controller 806 in the circuitry 814 can perform beam failure detection and reporting based on the received configuration information. The at least one radio transmitter 802 can transmit the beam failure report.

[0127] Figure 9 A wireless network 900 is shown in accordance with example embodiments, having one or more UEs 902 and one or more cells or base stations (gNBs) 904, which transmit a sequence of messages 906. 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.

[0128] In an initial access procedure, a UE finds a gNB (e.g., a cell), receives system information, and requests to connect to the cell. By way of example, the procedure includes a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), which enable the UE to find, identify, and synchronize to the network and / or cell.

[0129] ​Signal transmissions between a UE and a cell occur via multiple antennas and / or antenna arrays performing beamforming. With the large number of antennas and / or antenna arrays in a given network, beams are narrow, beam tracking or beam pair connections can fail. When a beam failure occurs, example embodiments perform a message sequence 906 as a beam recovery procedure or BFR to reestablish connectivity and a beam pair.

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

[0131] In example embodiments, a UE receives configuration information for beam failure recovery for multiple base stations or cells, such as multiple SCells and / or multiple groups of cells. The UE performs BFD on these multiple cells, generates a report, and sends the report to one or more base stations or cells (e.g., the base station that provided the configuration information or another base station).

[0132] Consider example embodiments in which the multiple cells include multiple groups of SCells. The UE receives a new indication from the gNB that informs the UE to perform BFR for multiple SCells based on a group-based scenario (e.g., a group of SCells and a PCell or just a group of SCells). This new indication points to group-based SCell BFR configuration information (configurable per UE).

[0133] The configuration information includes a list of one or more component carriers (CCs) that include group information. By way of example, the group information includes one or more of an indication of a number of groups to measure and / or report and an indication of the groups to measure and / or report.

[0134] The configuration information can also include BFD configuration information for determining the BF of a group. For example, this information is based on a minimum number of SCells within a group that have a failure condition (n min ) or a BFII threshold value per group

[0135] The BFD can be performed based on at least one of: (1) a number of SCells within a group that are identified as failed (s bf ) > a first threshold value (n min ), or (2) a sum of beam failure instance indications (BFII) for all SCells within a group Here, n min is a minimum number of SCells within a group that have a failure condition, where N iis the value of BFII for the ith SCell, n is the number of SCells within the group, and is the maximum number of BFII for all SCells within the group.

[0136] In an example embodiment, n min has a (pre-)fixed value equal to one, where the pre-fixed value can be configured according to a standard protocol or by the gNB. Here, the UE counts the BFII to detect the BF of each individual SCell within the group. For example, upon receiving n max consecutive BFII for an SCell, the UE determines the BF for that SCell. If any SCell within the group is identified as faulty, the BF for the group is declared. No further BFII counting for other SCells within the group is performed. When n min has a pre-fixed value of one, several advantages are produced. If the channel / beam properties of different SCells within the group are almost the same, the BFD measurement effort of the UE is reduced. Fixing the value of n min also has the benefit of reducing the dependency of the BFD computation time and computation (BFD TCC) on n max .

[0137] In another example embodiment, n min has a pre-fixed value greater than one, where the pre-fixed value can be configured according to a standard protocol or by the gNB. Here, the UE counts the BFII to detect the BF of each individual SCell within the group and s bf . When s bf ≥ n min , the UE declares that all SCells within the group are considered as faulty condition. No further BFII counting is performed in the group. When n min has a pre-fixed value greater than one, several advantages are produced. The set value of n min is consistent throughout the network. In addition, if the channel / beam properties of different SCells within the group are almost the same but still have some differences, this embodiment reduces the BFD measurement effort of the UE and enhances the decision to declare the group BF. In addition, another benefit includes reducing the dependency of the BFD TCC on n max and n min .

[0138] In another example embodiment, n min has a flexible value. For example, n min is flexibly indicated by control information depending on the UE capability, such as higher layer signaling or downlink control indication. For example, the value of n min is flexibly indicated by an information element (IE) of the UE capability. When n minHaving flexible values ​​offers several advantages. min The settings are flexible and may depend on one or more factors, such as the UE's capabilities. If the channel / beam properties of different SCells within a group are nearly identical, but still have some differences, this implementation reduces the UE's BFD measurement workload and enhances the decision-making process for claiming group BF. Furthermore, another benefit includes reduced BFD TCC for N. max and n min Dependence.

[0139] In the example embodiment, It has pre-fixed values, which can be configured according to standard protocols or via gNB. When Having a fixed value has several advantages. This setting is consistent across the entire network. If the channel / beam properties of different SCells within a group are nearly identical, this implementation reduces the UE's BFD measurement workload. Furthermore, another benefit includes reduced reliance on TCC for BFD TCC.

[0140] In the example embodiment, It has a flexible value. This flexible value is indicated by control information and can depend on one or more factors, such as UE capabilities, like higher-layer signaling or downlink control indications. For example, The value is flexibly indicated by the IE capability of the UE. When Having flexible values ​​offers several advantages. The settings are flexible and may depend on one or more factors, such as the UE's capabilities. This implementation reduces the UE's BFD measurement workload if the channel / beam properties of different SCells within a group are nearly identical. Furthermore, another benefit includes reduced BFD TCC requirements. Dependence.

[0141] In example embodiments, BFD operations can be based on other methods or combinations of methods. For example, the UE is instructed to use a method to perform BFD operations for each individual group (e.g., based on n). min or (combination).

[0142] Consider an example where the BFD operation for each group is based on one or more of the following five operation options: (1) n equal to 1 min (1) a fixed value; (2) n greater than 1 min (3) n min (4) Flexible value; The fixed value; and (5) The flexibility of the value.

[0143] Consider an example with three groups. Here, there are multiple possibilities or options to configure the BFD operation for each individual group. For example, these options include a fixed value of n min equal to 1, a fixed value of n mim greater than 1, and a fixed value of n applied to the first, second, and third groups, respectively. The second option (i.e., a fixed value of n min greater than 1) is applied to the first and second groups, while the third option (i.e., a flexible value of n min ) is applied to the third group, and so on. Subsequently, according to the received configuration information for each group, the UE uses the corresponding BFD method to perform the BFD operation to determine the beam failure for a particular group. This embodiment reduces the BFD measurement effort of the UE and the BFD TCC dependency on n max , n min , and .

[0144] In example embodiments, the configuration information includes information of a BF report generated by the UE and transmitted to the cell. By way of example, this information includes a group identifier (such as a group ID, an indicated CC index, or a configured index order) for each individual group. The BF report configuration information can include an indication of reporting a BF event via a PCell (or PsCell) UL or an SCell UL (if the SCell has a DL and an UL). This information can also include an indication of reporting new beam information, if such new beam information exists. Furthermore, this information can include one or more of the following: (1) an indication of a type of measurement information (MI) (e.g., RSRP, signal-to-interference noise ratio (SINR)) of a failed group to be reported, and (2) an indication of a cause of reporting a BF event, if the cause is known.

[0145] The indication of the configuration information can be explicitly and / or implicitly signaled to the UE. Consider an example of an implicit method via a (pre-)configured rule. For example, in the same frequency band, if CC1 is configured for cross-carrier scheduling of CC3 and CC5, the list of CCs is implicitly defined as CC1, CC3, and CC5, and CC1 is considered as the group identifier. Consider an example of an explicit method via control information. For example, such a method occurs at least via a physical downlink control channel downlink control information (PDCCH DCI), a MAC control element (MAC CE), or an RRC message.

[0146] The content of the BF report can include various information. For example, the UE generates and sends a BF report that includes at least the group identifier of each individual group indicated by the configuration information. If the number of simultaneously faulty groups is greater than the number of useful groups, the UE reports the useful group identifiers. Otherwise, the UE reports the faulty group identifiers. This embodiment reduces the uplink radio overhead.

[0147] The configuration information can also be updated or changed. For example, the UE provides new beam information, including CC index, spatial Rx parameters, and angle of arrival (AoA) to the gNB if present. By way of example, the gNB will assign the new beam to an existing group or a new group by comparing its own large-scale properties with the properties of the indicated SCells representing their groups. The gNB updates the UE with the configuration information. In embodiments, the group-based SCell beam failure recovery configuration information can be updated periodically or aperiodically.

[0148] In an example embodiment, the configuration information shows that only the indicated SCell (i.e., not all SCells within the group) is explicitly or implicitly configured with a BFD reference signal (BFD RS) for each individual group. Here, the UE receives a new indication from the gNB that informs the UE to perform BFR for multiple SCells based on the group-based scenario. This new indication points to the group-based SCell BFR configuration information.

[0149] The group-based SCell BFR configuration information includes the indicated CC (SCell) that is configured to perform BFD and reporting for each individual group. Here, only the indicated SCell (i.e., not all SCells within the group) is explicitly or implicitly configured with a BFD reference signal (BFD RS) for each individual group. By doing so, the downlink BFD RS can be reduced. In addition, other BFR resources can also be saved because the gNB only needs to locate the BFR resources on one of the CCs in the CC group. In this case, the UE can not need to know the list of CCs, and the group identifier can be the indicated CC index or the configuration index order. Similarly, the gNB can also configure SCell BFD RS on more than one CC within the CC group, and the configuration information can indicate which CC performs BFD and reporting based on UE capability and / or channel conditions.

[0150] According to the group-based SCell BFR configuration information pointed to by the received new indication, the UE only counts the BFII for the indicated SCell of each individual group. If the indicated SCell is identified as faulty, the BF of the group is declared. All SCells within the group are treated under this faulty condition.

[0151] According to the received new indication pointed to the group-based SCell BFR configuration information, if the number of simultaneous failed groups is greater than the number of useful groups, the UE reports the useful group identifiers. Otherwise, the UE reports the failed group identifiers. This example embodiment has several advantages. For example, this embodiment reduces the downlink BFD RS overhead and reduces the uplink radio overhead. This embodiment also reduces the BFD measurement work of the UE and simplifies the BFR procedure.

[0152] In example embodiments, all SCells of different groups can be explicitly or implicitly configured with their own BFD RS, while in certain cases only the indicated SCells of each individual group can be explicitly or implicitly configured with BFD RS.

[0153] Example embodiments include different group-based SCell BFR configuration information. Figure 10 Configuration information 1000 for BFR of multiple SCells based on group basic scenario according to example embodiments is shown. Figure 11 Table 1100 of group-based SCell BFR configuration information according to example embodiments is shown.

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

[0155] Those of ordinary skill in the art will understand that Figure 10 and Figure 11 The data in

[0156] ENUMERATED{SCell-basedBFRInfo,Group-basedSCellBFRInfo,both},

[0157] wherein "SCell-based BFR Info" indicates that the UE supports single SCell based BFR; "Group-based SCell BFR Info" indicates that the UE supports group based SCell BFR; and "both" indicates that the UE supports per SCell BFR and group based SCell BFR.

[0158] Example embodiments can apply to various scenarios where the BFR reference signal is explicitly configured by RRC or implicitly configured by TCI state. For example, by explicit configuration by RRC, the BFD RS is transmitted in the current SCell. For example, by implicit configuration by TCI state, the BFD RS is transmitted in the active bandwidth part (BWP) of the current SCell or another SCell.

[0159] Figure 12 An example of an electronic device 1200 is shown in accordance with an example embodiment.

[0160] The electronic device 1200 includes a power supply 1202, a memory 1204, a central processing unit (CPU) 1206, a storage 1208, a wireless transmitter and / or receiver 1210, an antenna 1212 (such as one or more antenna arrays for performing beamforming), and a BFR 1214 (such as for performing one or more of the example embodiments discussed in connection with FIG. 6- Figure 11 and / or software of one or more example embodiments discussed).

[0161] Consider the electronic device 1200 to be an example embodiment of a UE, an AP, a STA, a base station, a cell, or other electronic device.

[0162] The BFR 1214 of the electronic device 1200 includes hardware (e.g., circuitry) and / or software (e.g., code, instructions, or data) operative to perform one or more of: receiving configuration information for BFR of a plurality of SCells operating in a network, performing BFD based on the configuration information, generating a BF report based on the configuration information, and transmitting the BF report to another electronic device. The BFR 1214 is also operative to perform one or more of BFD, NBI, BFRQ, and BFRR.

[0163] Example embodiments can be implemented in various types of wireless networks that perform beamforming, such as 5G New Radio, mobile networks, and the like. Such networks include multiple transmit and / or receive antennas for beamforming. Channel state information is obtained via transmission of CSI reports based on CSI reference signals in the downlink and uplink.

[0164] The present disclosure can be implemented by software, hardware, or software in cooperation with hardware. Each functional block used in the description of each embodiment described above can be implemented in part or all by a large scale integration (LSI), such as an integrated circuit, and each process described in each embodiment can be controlled in part or all by the same LSI or a combination of LSIs. The LSI is a process of integrating a large number of transistors on a silicon semiconductor microchip or chip, and can include a very large scale integration (VLSI) and an ultra large scale integration (ULSI). The LSI can be formed into a chip individually, or one chip can be formed to include part or all of the functional blocks. The LSI can include a data input and output coupled thereto. Depending on the degree of integration, the LSI here can be referred to as an IC, a system LSI, a super LSI, or a ultra LSI. However, the implementation technology of integrated circuits is not limited to the LSI and can be realized by using a dedicated circuit, a general purpose processor, or a special purpose processor. Further, a FPGA (Field Programmable Gate Array) that can be programmed after manufacturing the LSI or a reconfigurable processor in which the connection and the setting of circuit cells disposed inside the LSI can be reconfigured can be used. The present disclosure can be implemented as a digital processing or an analog processing. If future integrated circuit technologies replace LSIs due to advances in semiconductor technology or other derivative technologies, the functional blocks can be integrated using the future integrated circuit technologies. Biotechnology can also be applied.

[0165] The present disclosure can be implemented by any kind of apparatus, device, or system having a communication function, which is referred to as a communication apparatus. The communication apparatus can include a transceiver and a processing / control circuit. The transceiver can include and / or function as a receiver and a transmitter. As the transmitter and the receiver, the transceiver can include a radio frequency (RF) module including an amplifier, an RF modulator / demodulator, and the like, and one or more amplifiers, RF modulators / demodulators, and one or more antennas. The processing / control circuit can include a power management circuit, which can include a dedicated circuit, a processor, and instructions for power management control, as firmware or instructions stored in a memory coupled to the processor.

[0166] Some non-limiting examples of such communication apparatuses include a telephone (e.g., cellular (small area) telephone, smart phone), a tablet, a personal computer (PC) (e.g., laptop, desktop, netbook), a camera (e.g., digital still / video camera), a digital player (e.g., digital audio / video player), a wearable device (e.g., wearable camera, smart watch, tracking device), a game console, a digital book reader, a remote healthcare / telemedicine (remote healthcare and medicine) device, and a vehicle (e.g., automobile, airplane, ship) that provides a communication function, and various combinations thereof.

[0167] The communication devices are not limited to portable or movable, and can also include any kind of non-portable or stationary devices, apparatuses, or systems, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, and any other "things" in an "Internet of Things" (IoT) network. The communication can include exchanging data through, for example, a cellular system, a wireless LAN system, a satellite system, and the like, as well as various combinations thereof.

[0168] The communication devices can include apparatuses such as controllers or sensors coupled to the communication devices that perform the communication functions described in the present disclosure. For example, the communication devices can include controllers or sensors that generate control signals or data signals used by the communication devices that perform the communication functions of the communication devices.

[0169] The communication devices can also include infrastructure such as base stations, access points, and any other devices, apparatuses, or systems that communicate with or control devices such as in the non-limiting examples provided herein.

[0170] While example embodiments have been presented in the foregoing detailed description of the application, it should be appreciated that a wide variety of modifications exist. It should also be appreciated that the example embodiments are by way of example only and are not intended to limit the applicability, operation, or configuration of the present disclosure in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient road map for implementing an example embodiment, it being understood that various changes can be made in the function and arrangement of the network and / or UE transceiver apparatuses described in the example embodiments without departing from the scope of the present disclosure as set forth in the appended claims.

[0171] Other example embodiments include, but are not limited to, the following examples:

[0172] A communication device comprising: a receiver that receives configuration information of BFRs of a plurality of SCells operating in a network; and circuitry that performs BFD and reporting based on the configuration information.

[0173] According to an example embodiment, the configuration information includes a list of CCs.

[0174] According to an example embodiment, the BFD is performed based on at least one of: (1) a number of the plurality of SCells that have been identified as failed within a group (s bf ) ≥ a threshold (n min ), where n min is a minimum number of the plurality of SCells having a failure condition within the group; or (2) a sum of BFII of the SCells within the group where N iis the value of BFII of the ith SCell, n is the number of SCells within the group, and is the maximum number of BFII of SCells within the group.

[0175] According to example embodiments, the threshold (n min ) is (pre-) fixed to 1, the BFII of each SCell within the group is further configured to be counted, and a beam failure (BF) of the group is declared if any SCell within the group is identified as failed.

[0176] According to example embodiments, the threshold (n min ) is (pre-) fixed to more than 1, the BFII is further configured to be counted to detect the BF of each SCell within the group, and when s bf ≥ n min , the SCell within the group is declared to be in a failed state.

[0177] According to example embodiments, the threshold (n min ) is flexibly indicated by control information depending on the capability of the communication device, which includes higher layer signaling or downlink control indication.

[0178] According to example embodiments, is a (pre-) fixed value.

[0179] According to example embodiments, is a flexible value indicated by control information depending on the capability of the communication device, which includes higher layer signaling or downlink control indication.

[0180] According to example embodiments, a method of performing BFD of each group based on n min or is indicated.

[0181] According to example embodiments, the configuration information includes a group identifier, which includes a group identity (ID), an indicated CC index, or a configuration index order of each group.

[0182] According to example embodiments, the indication of the configuration information is signaled based on at least one of: by (pre-) configured rules, by control information of at least physical PDCCH DCI, MAC CE, or RRC message.

[0183] According to example embodiments, the BF report content includes at least a group identifier of each group indicated by the configuration information.

[0184] According to example embodiments, the communication device is further configured to provide new beam information including a CC index, a spatial Rx parameter, and an AoA.

[0185] According to an example embodiment, the configuration information includes at least indicated SCells to perform BFD and reporting for each individual group, where only the indicated SCells can be explicitly or implicitly configured with BFD reference signals.

[0186] According to an example embodiment, if the number of simultaneously failed groups is greater than the number of useful groups, the communication device reports the identifiers of the useful groups; otherwise, the communication device reports the failed groups.

[0187] Another example embodiment is a communication method, comprising: receiving, at a communication device, configuration information of BFRs for a plurality of SCells operating in a network; and performing, by the communication device, BFD and reporting based on the configuration information.

[0188] While example embodiments have been presented in the foregoing detailed description of the present embodiments, it should be appreciated that a wide variety of modifications exist. It should also be appreciated that the example embodiments are by way of example only and are not intended to limit the scope, applicability, operation or configuration of the present disclosure in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient road map for implementing an example embodiment of the present disclosure, it being understood that various changes can be made without departing from the scope of the present disclosure as set forth in the appended claims.

Claims

1. A communication device, comprising: The receiver receives (1) group information indicating one or more component carriers included in the secondary cell SCell group, (2) configuration information for beam fault recovery (BFR) of the SCell group, and (3) the identifier of the SCell group; and The transmitter, based on the group information (1), the configuration information (2), and the identifier of the SCell group (3), sends report information including the results of beam fault detection (BFD).

2. The communication device according to claim 1, wherein, The reporting information includes an index of each fault SCell that is identified as a fault in BFD.

3. The communication device according to claim 2, wherein, The reporting information includes new beam information for each faulty SCell identified as faulty in BFD.

4. The communication device according to claim 1, wherein, The reporting information is sent when the number of beam fault instances (BFIs) in any SCell in the SCell group is equal to or greater than a first threshold indicated by the base station.

5. The communication device according to claim 1, wherein, The report information is sent when the number of SCells in the SCell group that are identified as faulty in BFD is equal to or greater than one.

6. The communication device according to claim 1, wherein, The reporting information is sent when the number of SCells in the SCell group that are identified as faulty in BFD is equal to or greater than a second threshold indicated by the base station.

7. The communication device according to claim 1, wherein, The configuration information indicates the reporting configuration of BFD.

8. A communication method, comprising: Receive (1) group information indicating one or more component carriers included in the secondary cell SCell group, (2) configuration information for beam fault recovery (BFR) of the SCell group, and (3) the identifier of the SCell group; as well as Based on the group information (1), the configuration information (2), and the identifier of the SCell group (3), a report information is sent, which includes the results of beam fault detection (BFD).

9. The communication method according to claim 8, wherein, The reporting information includes an index of each fault SCell that is identified as a fault in BFD.

10. The communication method according to claim 9, wherein, The reporting information includes new beam information for each faulty SCell identified as faulty in BFD.

11. The communication method according to claim 8, wherein, The reporting information is sent when the number of beam fault instances (BFIs) in any SCell in the SCell group is equal to or greater than a first threshold indicated by the base station.

12. The communication method according to claim 8, wherein, The report information is sent when the number of SCells in the SCell group that are identified as faulty in BFD is equal to or greater than one.

13. The communication method according to claim 8, wherein, The reporting information is sent when the number of SCells in the SCell group that are identified as faulty in BFD is equal to or greater than a second threshold indicated by the base station.

14. The communication method according to claim 8, wherein, The configuration information indicates the reporting configuration of BFD.

15. A communication device, comprising: The transmitter transmits (1) group information indicating one or more component carriers included in the secondary cell SCell group, (2) configuration information for beam fault recovery (BFR) of the SCell group, and (3) the identifier of the SCell group. and The receiver receives report information, which includes the results of beam fault detection (BFD), based on the group information (1), the configuration information (2), and the identifier of the SCell group (3).

16. The communication device according to claim 15, wherein, The reporting information includes an index of each fault SCell that is identified as a fault in BFD.

17. The communication device according to claim 16, wherein, The reporting information includes new beam information for each faulty SCell identified as faulty in BFD.

18. The communication device according to claim 15, wherein, The reporting information is sent when the number of beam fault instances (BFIs) in any SCell in the SCell group is equal to or greater than a first threshold indicated by the base station.

19. The communication device according to claim 15, wherein, The report information is sent when the number of SCells in the SCell group that are identified as faulty in BFD is equal to or greater than one.

20. The communication device according to claim 15, wherein, The reporting information is sent when the number of SCells in the SCell group that are identified as faulty in BFD is equal to or greater than a second threshold indicated by the base station.

21. The communication device according to claim 15, wherein, The configuration information indicates the reporting configuration of BFD.

22. A communication method, comprising: Send (1) group information of one or more component carriers included in the secondary cell SCell group, (2) configuration information for beam fault recovery (BFR) of the SCell group, and (3) the identifier of the SCell group; as well as Based on the group information (1), the configuration information (2), and the identifier of the SCell group (3), report information is received, the report information including the results of beam fault detection (BFD).

23. The communication method according to claim 22, wherein, The reporting information includes an index of each fault SCell that is identified as a fault in BFD.

24. The communication method according to claim 23, wherein, The reporting information includes new beam information for each faulty SCell identified as faulty in BFD.

25. The communication method according to claim 22, wherein, The reporting information is sent when the number of beam fault instances (BFIs) in any SCell in the SCell group is equal to or greater than a first threshold indicated by the base station.

26. The communication method according to claim 22, wherein, The report information is sent when the number of SCells in the SCell group that are identified as faulty in BFD is equal to or greater than one.

27. The communication method according to claim 22, wherein, The reporting information is sent when the number of SCells in the SCell group that are identified as faulty in BFD is equal to or greater than a second threshold indicated by the base station.

28. The communication method according to claim 22, wherein, The configuration information indicates the reporting configuration of BFD.

29. An integrated circuit, comprising: Receiver circuit, control: Receive (1) group information indicating one or more component carriers included in the secondary cell SCell group, (2) configuration information for beam fault recovery (BFR) of the SCell group, and (3) the identifier of the SCell group; and Transmitting circuit, control: Based on the group information (1), the configuration information (2), and the identifier of the SCell group (3), a report information is sent, which includes the results of beam fault detection (BFD).

30. An integrated circuit, comprising: Transmitting circuit, control: Send (1) group information of one or more component carriers included in the secondary cell SCell group, (2) configuration information for beam fault recovery (BFR) of the SCell group, and (3) the identifier of the SCell group; and Receiver circuit, control: Based on the group information (1), the configuration information (2), and the identifier of the SCell group (3), report information is received, the report information including the results of beam fault detection (BFD).

Images