RU2802829C1 - Group-based secondary cell beam recovery - Google Patents

Abstract

FIELD: communications.

SUBSTANCE: communication apparatus comprises: a receiver that, during operation, receives group information and configuration information for a BFR of a group of secondary cells (SCells), the group information indicating one or more carrier components included in the SCells; and a transmitter that, during operation, transmits reporting information based on the BFR configuration information, the reporting information including at least one of a beam failure detection (BFD) result of the SCells and new beam information of the SCells.

EFFECT: reducing the resource consumption for the beam failure detection reference signal (BFD RS) of the downlink and reducing resource consumption in radio communication over the uplink, as well as reducing the cost of measuring BFD for user equipment (UE) and simplifying the procedure of beam failure recovery (BFR).

34 cl, 14 dwg

Description

TECHNICAL FIELD

[1] The present invention generally relates to communications apparatus and methods for electronic devices and systems, and more particularly relates to beam failure recovery of multiple secondary cells (SCells) operating in a network.

BACKGROUND OF THE ART

[2] Because wireless networks operate in high frequency bands, such as millimeter wave communications (mmWave), communications devices are equipped with large antenna arrays. This allows signals to be transmitted over multiple communication lines using very narrow beams. These networks have many advantages over traditional networks, such as very high data rates, but they also have challenges associated with managing multipath operation and recovery protocols when a path fails in the network.

[3] Currently, 3GPP Edition 15 for 5G standards only specifies the beam failure recovery procedure for the primary cell (PCell) and primary secondary cell (PsCell). Communications equipment and beam failure recovery techniques have been largely undiscussed in the context of group-based secondary cells (SCells).

DISCLOSURE OF THE INVENTION

[4] One non-limiting and exemplary embodiment provides improvements to multipath modes of operation in wireless networks. As an example, this embodiment includes group-based SCell spoke failure recovery in the network. It proposes efficient solutions for simultaneous beam failure recovery of multiple network-enabled SCells.

[5] The present invention provides a communications apparatus comprising a receiver that, in operation, receives configuration information for beam failure recovery (BFR) of a plurality of SCells operating in a network, and circuitry that, in operation, performs failure detection beam failure detection (BFD) and produces a report based on configuration information.

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

[7] Additional advantages and disadvantages of the disclosed embodiments will become apparent from the description and drawings. Such features and/or advantages may be separately obtained by various embodiments and features of the specification and drawings, all of which need not be present to obtain one or more of such features and/or advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

[8] The accompanying drawings, in which like reference numerals refer to identical or functionally similar elements in separate illustrations and which, together with the detailed description provided below, are incorporated in and constitute a part of the present invention, serve to illustrate various embodiments and to explain various principles and advantages of the present embodiments.

[9] In FIG. 1 shows an example architecture of the 3GPP New Radio (NR) system.

[10] In FIG. Figure 2 is a schematic diagram showing the functional separation between the Next Generation - radio access network (NG-RAN) and the 5G core network (5GC).

[11] In FIG. 3 shows a sequence diagram for the radio resource control (RRC) connection setup/reconfiguration procedures.

[12] In FIG. Figure 4 shows a schematic diagram of use cases for Enhanced mobile broadband (eMBB), Massive Machine Type Communications (mMTC), and Ultra Reliable and Low Latency Communications (URLC).

[13] In FIG. 5 is a block diagram depicting an exemplary 5G system architecture for a non-roaming scenario.

[14] In FIG. 6A is a schematic diagram of multiple-input multiple-output (MIMO) uplink and downlink communication between a base station (gNB) and a user equipment (UE) in a MIMO wireless network.

[15] In FIG. 6B is a schematic diagram of implementing multi-user MIMO downlink communication (multi-user MIMO (MU-MIMO)) between a gNB and multiple UEs in a wireless MIMO network.

[16] In FIG. 6C is a schematic diagram of uplink MU-MIMO communication between a gNB and a plurality of UEs in a wireless MIMO network.

[17] In FIG. 7 illustrates a beam failure recovery procedure according to various embodiments.

[18] In FIG. 8 is a schematic diagram of an exemplary communication apparatus according to various embodiments. The communication apparatus may be implemented as a gNB or UE and is configured to detect and recover a beam failure according to various embodiments of the present invention.

[19] In FIG. 9 shows a wireless network with one or more UEs and one or more cells or gNBs transmitting a sequence of messages according to the exemplary embodiment.

[20] In FIG. 10 shows configuration information for beam failure recovery (BFR) for a plurality of SCells based on a base case for a group according to the exemplary embodiment.

[21] In FIG. 11 is a table with group-based BFR SCell configuration information according to the exemplary embodiment.

[22] In FIG. 12 shows an electronic device according to an exemplary embodiment.

[23] Those skilled in the art will appreciate that elements in the figures are shown for simplicity and clarity, and are not necessarily drawn to scale.

IMPLEMENTATION OF THE INVENTION

[24] In the following, by way of example only and with reference to the drawings, certain embodiments of the present invention will be described. Like reference numbers and symbols shown in the drawings refer to like items or equivalents.

[25] 5G NR system architecture and protocol stacks

[26] 3GPP is working on the next edition of 5th generation cellular technology, simply called 5G, including the development of new radio access (NR) technology operating at frequencies up to 100 GHz. Non-Stand-Alone (NSA) NR radio specifications for 5G standards were originally introduced in late 2017. In 2018, 3GPP Edition 15 was completed, the first version of 5G standards to cover stand-alone (SA) 5G communications with a new radio system, allowing for 5G NR compliance testing and commercial deployment on smartphones.

[27] Among other things, the overall system architecture assumes the use of the Next Generation - Radio Access Network (NG-RAN), which contains the gNB and ensures the end of the use of the user plane protocol for NG radio access (SDAP/PDCP/RLC/MAC/PHY) and the protocol radio resource control (RRC) for the UE. The gNBs are connected to each other via the Xn interface. In addition, gNBs are connected via a Next Generation (NG) interface to a Next Generation Core (NGC), and more specifically to an Access and Mobility Management Function (AMF) (e.g., a specific a kernel object that performs AMF) via the NG-C interface, and a User Plane Function (UPF) (for example, a specific kernel object that performs UPF) via the NG-U interface. The NG-RAN architecture is shown in FIG. 1 (see, for example, 3GPP TS 38.300 version 15.6.0, section 4).

[28] The user plane protocol stack for NR (see, for example, 3GPP TS 38.300, section 4.4.1) contains sublayers of the Packet Data Convergence Protocol (PDCP, see TS 38.300 section 6.4), radio link control (Radio Link Control (RLC), see section 6.3 of TS 38.300) and Medium Access Control (MAC), see section 6.2 of TS 38.300), the use of which is discontinued in the gNB on the network side. In addition, a new access stratum (AS) sublayer (Service Data Adaptation Protocol (SDAP)) has been introduced above PDCP (see, for example, subclause 6.5 of 3GPP TS 38.300). A control plane protocol stack is also defined for NR (see, for example, TS 38.300, section 4.4.2). An overview of level 2 functions is given in subclause 6 of TS 38.300. The functions of the PDCP, RLC and MAC sublayers are listed in sections 6.4, 6.3 and 6.2 of TS 38.300, respectively. The functions of the RRC level are listed in subclause 7 of TS 38.300.

[29] For example, the media access control layer performs processing in the form of logical channel multiplexing, as well as scheduling and scheduling-related functions, including processing of various numerical values.

[30] The physical layer (PHY), for example, performs encoding, HARQ PHY processing, modulation, multi-antenna processing, and mapping the signal to associated 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 to transmit a particular transport channel, and each transport channel is associated with a corresponding physical channel. For example, physical channels include the Physical Random Access Channel (PRACH), the Physical Uplink Shared Channel (PUSCH), and the Physical Uplink Control Channel. Control Channel (PUCCH) for uplink and Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH) and physical broadcast channel (Physical Broadcast Channel (PBCH)) for the downlink.

[31] NR use cases/deployment scenarios may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLC), 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 downlink and 10 Gbps uplink) and user data rates that are three times those provided by IMT-Advanced technology. On the other hand, URLLC has more stringent requirements in terms of ultra-low latency (0.5 ms for both UL and DL for user plane latency) and high reliability (1-10-5 within 1 ms). Finally, mMTC may preferably require high connection density (1,000,000 devices/km2 in an urban environment), large coverage in harsh climates, and an extremely long battery life for low-cost devices (15 years).

[32] Thus, an OFDM numerical value (eg, subcarrier spacing, OFDM symbol duration, cyclic prefix (CP) duration, number of symbols per scheduling interval) that is appropriate for one use case may not be appropriate for another. For example, low latency services may preferably require shorter symbol duration (and therefore larger subcarrier spacing) and/or fewer symbols per scheduling interval (also referred to as TTI) compared to mMTC service. Additionally, deployment scenarios with a wide range of link delays may preferably require longer CP durations than a scenario with a small range of delays. Subcarrier spacing must be optimized accordingly to maintain similar resource consumption to CP. NR can support more than one subcarrier spacing. Accordingly, subcarrier spacing values of 15 kHz, 30 kHz, 60 kHz… are currently being considered. The symbol duration Tu and subcarrier spacing Δf are directly related by the formula Δf = 1 / Tu. Similarly, as in LTE systems, the term "resource element" can be used to refer to the minimum resource unit consisting of one subcarrier for the length of one OFDM/SC-FDMA symbol.

[33] In the new 5G radio communication system, for each numerical value 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 a frequency index in the frequency domain and a symbol position in the time domain (see 3GPP TS 38.211 version 15.6.0).

[34] 5G NR functional separation between NG-RAN and 5GC

[35] In FIG. Figure 2 shows the functional separation between NG-RAN and 5GC. An NG-RAN logical node is a gNB or ng-eNB. 5GC has logical nodes AMF, UPF and SMF.

[36] In particular, gNB and ng-eNB perform the following main functions:

- functions for radio resource management such as radio channel management, radio connection creation management, mobility management for the connection, dynamic resource allocation for UEs in both uplink and downlink (scheduling);

- IP header compression, encryption and data integrity protection;

- selection of AMF when UE connects when routing to AMF cannot be determined based on information provided by the UE;

- user plane data routing for UPF;

- routing of control plane information for AMF;

- setting up and releasing the connection;

- planning and transmission of paging messages;

- scheduling and transmission of system broadcast information (emanating from AMF or OAM);

- measurements and configuration of measurement reports for mobility and planning;

- marking of transport layer packets in the uplink;

- session management;

- support for network segmentation;

- QoS flow control and mapping to radio data channels;

- support for UE in RRC_INACTIVE state;

- NAS message distribution function;

- sharing of a radio access network;

- possibility of establishing a double connection;

- tight interaction between NR and E-UTRA.

[37] The Access and Mobility Management Function (AMF) includes the following core functions:

- provision of a layer not related to the provision of access, NAS, termination of signaling;

- NAS alarm protection;

- providing an access layer, AS, security control;

- use of intermediate core network, CN, nodal signaling to ensure mobility between 3GPP access networks;

- idle mode reachability for the UE (including control and execution of retransmission for paging);

- registration area management;

- support for intra-system and inter-system mobility;

- access authorization;

- access authorization, including checking rights in roaming;

- control of mobility management (subscription and policies);

- support for network segmentation;

- session management function, SMF, selection.

In addition, the user plane function, UPF, includes the following core functions:

- creating an anchor point for mobility when using internal/mutual RAT (if applicable);

- creation of an external PDU session point to connect to the data network;

- packet routing and forwarding;

- packet and user plane verification to ensure compliance with policy rules;

- creating reports on traffic usage;

- uplink classifier to support routing traffic flows in the data network;

- creation of a branch point to support a multi-interface PDU session;

- QoS processing for the user plane, e.g. packet filtering, gating, UL/DL rate enforcement;

- uplink traffic inspection (matching SDF to QoS flow);

- Initiating buffering of downlink packets and notification of downlink data.

Finally, the session management function, SMF, includes the following core functions:

- session management;

- allocation and management of the UE IP address;

- selection of the UP function and its control;

- configuring traffic control in the user plane function, UPF, to route traffic to the appropriate destination;

- part regarding control of policy implementation and QoS;

- downlink data notification.

[38] Procedures for setting up and changing the RRC connection configuration

[39] In FIG. 3 shows some aspects of the interaction between the UE, gNB and AMF (5GC entity) in the context of the UE transitioning from RRC_IDLE mode to RRC_CONNECTED mode for the NAS part (see TS 38.300 version 15.6.0).

[40] RRC is a higher layer signaling (protocol) used to configure the UE and gNB. Specifically, this transition involves preparing the AMF of UE context data (including, for example, PDU session context, security key, 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 on the UE by sending a SecurityModeCommand message from the gNB to the UE and receiving a response from the UE by the gNB with a SecurityModeComplete message. The gNB then performs a configuration change to configure Signaling Radio Bearer (SRB2) and Data Radio Bearer (DRB) by sending an RRCReconfiguration message to the UE and receiving the gNB in response with an RRCReconfigurationComplete message from the UE. In a signaling-only connection, the steps associated with sending the RRCReconfiguration message are skipped because SRB2 and DRB are not configured. Finally, the gNB informs the AMF that the setup procedure is completed by receiving the INITIAL CONTEXT SETUP RESPONSE.

[41] Thus, the present invention provides an object (eg, AMF, SMF, etc.) of a 5th generation core (5GC) containing a control circuit that, during operation, establishes a Next Generation (NG) connection. with the gNodeB, and a transmitter that, in operation, transmits an initial context setup message via an NG connection to the gNodeB to enable setup of a radio signaling link between the gNodeB and the user equipment (UE). Specifically, the gNodeB transmits radio resource control signaling, RRC, containing a resource allocation configuration information element to the UE via a radio signaling channel. The UE then performs uplink transmission or downlink reception based on the resource allocation configuration.

[42] IMT use cases for 2020 and beyond

[43] In FIG. Figure 4 shows some of the 5G NR use cases. For new radio technology, the 3rd generation partnership project new radio (3GPP NR) explores three use cases that have been proposed to support IMT-2020's wide range of services and applications. The specification for Phase 1 of the enhanced mobile broadband (eMBB) network has been completed. In addition to further expanding eMBB support, current and future work will include standardization for ultra-reliable and low-latency communication (URLC) and machine-type streaming communications. In fig. Figure 4 shows some exemplary expected IMT use cases for 2020 and beyond (see, for example, ITU-R M.2083, Figure 2).

[44] The URLLC use case has stringent requirements for capabilities such as throughput, latency, and availability, and it has been envisioned as one of the enablers for future vertical applications such as wireless industrial manufacturing or process control, telemedicine surgery, automation smart grid distributions, transport security, etc. Ultra-reliability for URLLC must be maintained by identifying technologies that meet the requirements defined in TR 38.913. For URLLC NR in Edition 15, key requirements include a user plane delay target of 0.5 ms for UL (uplink) and 0.5 ms for DL (downlink). The general URLLC requirement for a single packet transmission is a Block Error Rate (BLER) of 1E-5 for a packet size of 32 bytes with a user plane latency of 1 ms.

[45] From a physical layer perspective, reliability can be improved in a variety of possible ways. Current capabilities to improve reliability include the definition of separate CQI tables for URLLC, more compact DCI formats, PDCCH repetition, etc. However, these capabilities can be expanded to achieve ultra-reliability as NR becomes more stable and mature (based on key URLLC requirements NR). Specific use cases for URLLC NR in Edition 15 include Augmented Reality/Virtual Reality (AR/VR), e-health, e-security, and mission-critical applications.

[46] In addition, technological improvements related to URLLC NR are aimed at improving latency and increasing reliability. Technological improvements to improve latency include the use of a configurable numerical value, slotless scheduling with flexible mapping, provisioning of the uplink free (configurable allocation), slot-level repetition for data channels, and release of the downlink for priority use. Release for priority use means that a transfer for which resources have already been allocated is terminated and those already allocated resources are used for another transfer that was requested later but which requires lower latency/has a higher priority. Accordingly, a transmission for which resources have already been allocated is preempted by a later transmission. The priority use exemption applies regardless of the specific type of service. For example, a transmission for service type A (URLLC) may be preempted by a transmission for service type B (such as eMBB). Technology improvements to improve reliability include dedicated CQI/MCS tables for target BLER 1E-5.

[47] The Massive Machine Type Communications (mMTC) use case is characterized by a very large number of connected devices, typically transmitting a relatively small amount of latency-sensitive data. The devices must be inexpensive and must have a very long battery life. From the NR point of view, using very narrow parts of the bandwidth is one of the possible solutions to save energy from the UE point of view and provide very long battery life.

[48] As mentioned above, reliability capabilities in NR are expected to become more extensive. One of the key requirements in all of these options, and in particular mandatory for URLLC and mMTC, is high reliability or ultra-reliability. Several mechanisms can be considered to improve reliability from a radio and network perspective. Overall, there are several key potential aspects that could improve reliability. These aspects include compact control channel information, data/control channel repetition, and frequency, time and/or spatial domain diversity. These aspects apply to reliability in general, regardless of specific communication scenarios.

[49] Additional use cases with more stringent requirements have been identified for URLLC NR, including manufacturing automation, transportation, and power distribution. These more stringent requirements include higher reliability (up to 10 ^-6 level), higher availability, packet sizes up to 256 bytes, time synchronization down to the order of several microseconds, which can be one or several microseconds depending on the frequency range and short latencies are on the order of 0.5-1 µs, in particular the delay in the user's target plane can be 0.5 µs, depending on the use cases.

[50] In addition, several technological improvements related to the physical layer have been identified for URLLC NR. These include improvements to the Physical Downlink Control Channel (PDCCH), namely compact DCI, PDCCH repetition, and improved PDCCH control. In addition, Uplink Control Information (UCI) enhancements include enhancements to the Hybrid Automatic Repeat Request (HARQ) and CSI feedback. Additionally, PUSCH enhancements have been identified including mini-slot hopping and retransmission/repetition enhancements. The term "mini-interval" means a Transmission Time Interval (TTI) containing fewer symbols than a slot (an interval containing fourteen symbols).

[51] QoS Management

[52] The 5G Quality of Service (QoS) model is based on QoS flows and supports both QoS flows that require a guaranteed flow rate (QoS flows with GBR (flow bit rate)) and QoS flows that do not require a guaranteed flow bit rate. flow rates (QoS streams without GBR). At the NAS level, the QoS flow is thus the smallest granularity in differentiating QoS within a PDU session. A QoS flow is identified in a PDU session by a QoS flow ID (QFI) carried in an encapsulating header over the NG-U interface.

[53] For each UE, the 5GC creates one or more PDU sessions. For each UE, NG-RAN creates at least one Data Radio Bearer (DRB) along with the PDU session and additional DRB(s) for the QoS flow(s) of that PDU session can be subsequently configured (NG-RAN decides when necessary), for example as shown above with reference to FIG. 3. NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS layer packet filters in the UE and in 5GC associate UL and DL packets with QoS flows, and AS layer matching rules in the UE and in NG-RAN associate UL and DL QoS flows with DRBs.

[54] In FIG. Figure 5 shows the 5G NR reference architecture without roaming (see TS 23.501 v. 16.1.0, section 4.23). An Application Function (AF), such as an external application server hosting 5G services, as described for example in FIG. 4, interfaces with the 3GPP core network to provide services, such as providing application influence on traffic routing, accessing the Network Exposure Function (NEF), or interacting with the policy system to manage policy (see Policy Control Function (PCF)), for example, QoS control. Depending on the operator's deployment, application functions that are considered trusted by the operator may be allowed to directly interact with the corresponding network functions. Application functions that are not allowed direct access to network functions by the operator use an external influence system via NEF to interact with the corresponding network functions.

[55] In FIG. Figure 5 shows additional functional blocks of the 5G architecture, namely: Network Slice Selection Function (NSSF), Network Repository Function (NRF), Unified Data Management (UDM), Authorization Server function ( Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF) and Data Network (DN), such as operator services, access to Internet or third party services. All or part of the core network functions and application services can be deployed and run in cloud computing environments.

[56] Thus, the present invention provides an application server (eg, AF in a 5G architecture) that includes a transmitter that, in operation, transmits a request containing a QoS requirement for at least one of URLLC, eMMB and mMTC services , at least at least one of the functions (e.g. NEF, AMF, SMF, PCF, UPF, etc.) of the 5GC to create a PDU session, including the creation of a radio bearer between the gNodeB and the UE in accordance with the QoS requirement, and a control scheme that, during operation, ensures services using the created PDU session.

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

[58] For a MIMO wireless network, the term “multiple” refers to a plurality of antennas used simultaneously for transmission and a plurality of antennas used simultaneously for reception over a radio channel. In this regard, the term "multiple inputs" refers to a plurality of transmitting antennas from which a radio signal is input to a channel, and the term "multiple outputs" refers to a plurality of receiving antennas that receive a radio signal from a channel and transmit it to a receiver. For example, in an N × M MIMO network system, N represents the number of transmit antennas, M represents the number of receive antennas, and N may or may not be equal to M. For simplicity, the respective numbers of transmit antennas and receive antennas are not further discussed in the present description. In fig. 6A is a schematic diagram of a single user (SU) MIMO communication 100 between a base station (gNB) 602 and a user equipment (UE) 604 in a wireless MIMO network. As shown in the drawing, a MIMO wireless network may include one or more UEs (eg, UE 604, UE 606, etc.). In SU-MIMO communication 600, gNB 602 transmits multiple space-time streams using multiple antennas (e.g., four antennas as shown in FIG. 6A), with all space-time streams dedicated to a single communication device, i.e. UE 604 For simplicity, the plurality of spatiotemporal streams directed to the UE 104 are shown as a grouped data transmission arrow 108 directed to the UE 604.

[59] SU-MIMO communication 600 can be configured for bidirectional transmissions. As shown in FIG. 6A, in SU-MIMO communication 100, the UE 604 may transmit multiple space-time streams using multiple antennas (e.g., two antennas as shown in FIG. 6A) across all space-time streams directed to the gNB 602. For simplicity, multiple spatio-temporal streams directed to the gNB 602 are shown as a grouped data transmission arrow 110 directed to the gNB 602.

[60] Thus, SU-MIMO communication 600 depicted in FIG. 6 provides SU transmissions on both uplink and downlink in a MIMO wireless network.

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

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

[63] Beamforming is a signal processing technique in which an antenna array directs the transmitted and/or received signal in a wireless network to electronic devices and determines the most efficient route to deliver data from a base station (gNB) to the UE. Signals at certain angles are subject to reinforcing interference, while signals at other angles are subject to weakening interference. Beamforming may allow large-array MIMO (in which MIMO uses a large-scale antenna array in one or more electronic devices (eg, gNBs)) to transmit simultaneously to multiple autonomous UEs. MIMO allows more than one data signal to be transmitted and received simultaneously in a wireless network over the same radio channel through multiple antennas and/or antenna arrays.

[64] Some networks use beamforming and large MIMO techniques due to the high propagation loss associated with using millimeter waves for signal transmission. In networks that transmit using beamforming, technical problems arise in creating and maintaining a pair of beams in which the beam direction on the transmitter side and the beam direction on the receive side are provided with appropriate communication capability. Additional problems arise when this connectivity is disrupted or becomes insufficient. For example, an obstacle may block the direct path between transmitter and receiver, or changes in the environment may distort a pair of beams. For example, a beam failure occurs when some event causes a created beam pair to be blocked or interfered with (eg, the UE moves to a location where wireless transmission is being blocked, or moves to a location not covered by the current serving cell). A beam recovery is then performed to restore connectivity for the beam pair.

[65] The exemplary embodiments address these technical problems and other problems in beamforming networks. These embodiments include, but are not limited to, apparatus and methods that perform BFR. The benefits of these solutions include, but are not limited to, reduced uplink radio resource consumption, reduced BFD measurement costs, simplified BFR execution, and faster recovery of beam-pair connectivity in the network.

[66] Exemplary embodiments include BFR for PCell, SCell, and a group consisting of more than one cell, eg, a group of PCells and SCells, a group consisting of only SCells, or a group-based SCell. PCell is a cell operating on the primary frequency. For example, this cell is a cell in which the UE either performs an initial connection establishment procedure, initiates a connection restoration procedure, or a cell designated as a primary cell in a handover procedure. SCell is a cell operating on a secondary frequency. For example, this cell is configured after establishing a Radio Resource Control (RRC) connection and can be used to provide additional radio resources. In accordance with various embodiments, the term "secondary cell" (or "SCell") may be used interchangeably with the term "component carrier" (or "component carrier (CC)").

[67] Exemplary embodiments further include BFR for downlink (DL), uplink (UL), as well as for DL and UL. For example, in the exemplary embodiment, BFR is defined for SCell with DL and UL, as well as with DL only (eg, when the PCell operates in frequency band 1 (FR1) and FR2). In one embodiment, FR1 includes frequency bands below 6 GHz, and FR2 includes frequency bands from approximately 24 GHz to 52 GHz.

[68] In FIG. 7 illustrates a beam failure recovery (BFR) procedure 700 according to various embodiments. Procedure 700 is presented as a high-level diagram depicting beam failure detection and recovery from that failure. This 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 (BFRQ). beam failure recovery response (BFRR).

[69] At block 702, a BFD is performed. Beam failure can occur for various reasons. To detect beam failure, the SCell UE may obtain link quality data at a certain radio layer to transmit a periodic link-state information reference signal (CSI-RS). If the link quality at a certain link level for all relevant CSI-RS resources exceeds a threshold value at some point in time (this threshold value is defined as the level at which reliable reception cannot be achieved on the downlink radio link and corresponds to the termination of frequency detection block errors (BLER_out) for a hypothetical downlink control channel (PDCCH) transmission), a beam fault instance (BFI) can be identified. The physical layer (PHY) passes the BFI indication to the media access control (MAC) layer. The BFD procedure in the MAC is defined by a timer and a counter that calculates the number of BFI indications (BFIIs). Each time a BFI instruction is received, the timer is restarted, and if the timer expires, the counter is reset. On the other hand, after discovering consecutive BFII ( beamFailureInstanceMaxCount ) the UE may announce that a beam failure has occurred in the SCell. The CSI-RS may be explicitly configured to provide measurement for the BFD using a Radio Resource Control Protocol message, or configured implicitly using the state of the transmission configuration indicator (TCI) of a higher layer parameter on PDCCH reception. . Channel state information (CSI) is a collection of spatial transfer functions between each antenna in the base station antenna array and the UE. The CSI information is stored, for example, in a matrix, and is used to encode and decode data transmitted and received using the antenna array.

[70] At step 704, NBI is performed. In an exemplary embodiment, a new beam or a new pair of beams is defined to restore or resume connectivity between the UE and the cell. Consider an exemplary embodiment that includes a set or series of CSI-RS blocks or synchronization signals (SS) to restore callability. Consider an exemplary embodiment that provides transmission of these signals within a downlink beam. These signals are a set of candidate beams. For example, according to an exemplary embodiment of the reference signals, the L1 reference signal received power (L1-RSRP) for a plurality of candidate beams is measured. If the measured L1-RSRP value exceeds the specified value, connectivity is restored as the reference signal corresponds to the new beam.

[71] At block 706, a BFRQ is transmitted. BFRQ is not transmitted until a beam failure is declared at the MAC layer. For normal BFR in one SCell, a beam failure at the MAC level is declared after receiving from PHY for the duration of the timer , Where and frequency RS BFD ( beamFailureDetectionTimer ) are separately configurable values. The device transmits a BFRQ to the network or device (e.g., cell) and informs the network or device that a beam failure has been detected. The information provided in the BFRQ may include candidate beam information.

[72] At block 708, a BFRR is transmitted. After performing the BFRQ, according to the exemplary embodiment, downlink snooping is performed to detect the network or device's response to the BFRQ. For example, the response conveys the quasi co-location (QCL) of the PDCCH with the resource set associated with the candidate beam included in the BFRQ. Two antenna ports are designated as quasi-common (QCL) if the properties of the channel carrying the symbol to one antenna port can be determined by the channel carrying the symbol to the other antenna port. After transmitting a BFRQ, if a response is not received within the specified time interval or window, the device retransmits the BFRQ.

[73] In general, BFD SCell is based on periodic transmission of CSI-RS. After reception BFII The UE advertises the BF, then transmits the BFRQ. During BRFQ transmission, the UE transmits the BF event and reports the failed SCell indices, i.e. the index(es) of the failed CC, as well as the new beam if present, with the UE reporting only one new beam present for each SCell . However, communication apparatuses and beam failure recovery techniques have been largely undiscussed in the context of group-based SCell.

[74] A group of SCells may have similar beam failure conditions, such as channel/beam statistical properties (statistical properties of large-scale parameters), so BFD for a group of SCells can be implemented based on a single failure of one of the SCells. This can simplify BFD and BFR when multiple SCells are configured. In addition, BFR procedures pose other technical challenges and issues associated with networks performing beamforming with SCell on a group basis. As an example, these problems relate to the way the UE is notified of the execution of BFR in a SCell on a group basis and the way the UE determines and reports a beam failure of multiple SCells based on a single identifier. The exemplary embodiments also provide technical solutions to these problems.

[75] According to one exemplary embodiment, a communications apparatus is provided, comprising a receiver that receives configuration information for the BFR of a plurality of SCells operating in a network, and circuitry that performs beam BFD and generates a report based on said configuration information.

[76] According to yet another exemplary embodiment, a method is provided that includes receiving, by a communication apparatus, configuration information for the BFR of a plurality of SCells operating in a network; The communication device performs BFD and generates a report based on the specified configuration information.

[77] In FIG. 8 is a schematic, partially exploded view of a communications apparatus 800 according to various embodiments. The communications apparatus 800 may be implemented as a gNB or UE according to various embodiments and provide functions for recovery from a beam failure. As shown in FIG. 8, communications apparatus 800 may include circuitry 814 including at least one receive signal generator, at least one radio transmitter 802, at least one radio receiver 304, and at least one antenna 812 (for simplicity, FIG. 8 is illustrative only one antenna is shown). At least one radio receiver 804 is configured to receive configuration information for the BFD and BFR of a plurality of SCells operating on the network, which may include group information containing lists of the carrier constituents of each group (either explicitly or implicitly), BFD configuration information and beam failure (BF) report configuration information containing at least a group identifier for each group for which the report is generated. Circuitry 814 may also include at least one processor 808 for processing the transmit signal. Circuitry 814 may also include at least one controller 806 for use in performing software and hardware tasks, wherein the at least one controller 806 is configured to perform those tasks including controlling communication with one or more other devices. communication in a MIMO wireless network. At least one controller 806 is configured to control a processor 810 for processing a receive signal and a transmit signal generator 808 . At least one controller 806 is configured to control the processor 810 to process the receive signal to receive configuration information. At least one controller 806 in circuit 814 is configured to perform beam failure detection and reporting based on the received configuration information. At least one radio transmitter 802 is configured to report a beam failure.

[78] In FIG. 9 shows a wireless network 900 with one or more UEs 902 and one or more cells or base stations (gNBs) 904 transmitting a message sequence 906 according to an exemplary 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.

[79] During initial access procedures, the UE finds a base station (eg, a cell), receives system information, and requests a connection to the cell. By way of example, this procedure involves transmitting a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) that enable the UE to locate, identify, and synchronize with a network and/or cell.

[80] Signal transmission between the UE and the cell(s) is carried out through a plurality of antennas and/or antenna arrays to perform beamforming. Due to the large number of antennas and/or antenna arrays in a network, the beams are narrow and failure may occur when tracking a beam or providing connectivity to a pair of beams. When a beam failure occurs, according to the exemplary embodiment, a messaging sequence 900 is executed as a beam recovery procedure or BFR to restore connectivity and create a beam pair.

[81] As shown by step 908, the gNB 904 transmits configuration information to the UE 902. After receiving the configuration information, the UE performs BFD based on the configuration information received from the gNB, as shown by step 910. The UE generates a BF report based on the received configuration information and transmits this report to the base station, as shown by step 912.

[82] In one exemplary embodiment, the UE receives configuration information for beam recovery of a plurality of base stations or cells, such as a plurality of SCells and/or a plurality of cell groups. The UE performs BFD on a specified plurality of cells, generates a report, and transmits the report to one or more base stations or cells (eg, the base station that provided the configuration information or another base station).

[83] Consider an exemplary embodiment in which a plurality of cells include a plurality of SCells. The UE receives a new indication from the gNB directing the UE to perform BFR for a plurality of SCells based on a base case for the group (eg, a group of SCells and PCells or a group of SCells only). This new indication contains group-based BFR SCell configuration information (configurable for the base UE).

[84] The configuration information includes one or more carrier component (CC) lists, which include group information. By way of example, this group information includes one or more of indicating the number of groups to be measured and/or reported and indicating which of the groups to be measured and/or reported.

[85] The configuration information may also include BFD configuration information for determining the group BF. For example, this information is based on the minimum number of SCells having a failure condition ( ) in a group, or based on the group's BFII threshold ( ).

[86] BFD may be performed based on at least one of (1) number of SCells that have detected a failure in the group first threshold value , or (2) the sum of the beam failure instance indications (BFII) of all SCells in the group second threshold value ). In this case represents the minimum number of SCells having a failure condition within the group, , Where represents the BFII value th SCell, represents the number of SCells in the group, and represents the maximum number of BFIIs of all SCells in the group.

[87] In one exemplary embodiment has a (predefined) fixed value of one, wherein the specified (predefined) fixed value can be configured according to a standard protocol or using the gNB. Here, the UE counts BFII to detect BFs in each individual SCell in the group. For example, after taking successive BFII SCell UE determines the BF SCell. When a failure is detected in any of the SCells in the group, a group BF is declared. No further BFII calculation is performed for other SCells in this group. If The (preset) fixed value is one, which has several advantages. The cost for the UE to perform measurements for BFD is reduced if the channel/beam properties of different SCells in a group are almost the same. Fixing the value also provides the advantage of reducing the dependence of BFD computation and computation time (TCC BFD) on.

[88] In yet another exemplary embodiment has a (predefined) fixed value that is greater than one, wherein the specified (predefined) fixed value can be configured according to a standard protocol or using the gNB. In this case, the UE calculates the BFII to detect the BF for each individual SCell in the group and . If ,The UE declares that processing for all SCells in the group is ,under failure conditions. No further calculation of BFII is performed in this group. If has a (predefined) fixed value greater than one, this has several advantages. Set value is the same for the entire network. In addition, this embodiment reduces the cost for the UE to perform measurements for BFD and facilitates the decision to declare a group BF if the channel/beam properties of different SCells in the group are almost the same but still have some differences. Additionally, another benefit includes the reduction of TCC BFD depending on And .

[89] In yet another embodiment has a flexibly assigned meaning. For example, flexibly indicated in the control information depending on the capabilities of the UE, such as higher layer signaling or downlink control indication. For example, the value flexibly indicated in the information element (IE) of the UE capabilities. If has a flexibly assigned value, this provides several advantages. Set value is flexibly assignable and may depend on one or more factors, such as the capabilities of the UE. The present embodiment reduces the cost for the UE to perform measurements for BFD and facilitates the decision to declare a group BF when the channel/beam properties of different SCells in the group are almost the same but still have some differences. Additionally, another benefit includes the reduction of TCC BFD depending on And .

[90] In one exemplary embodiment has a (predefined) fixed value, wherein the specified (predefined) fixed value can be configured according to a standard protocol or using the gNB. If has a fixed value, this provides several advantages. This is the set value is the same for the entire network. This embodiment provides a reduction in the cost for the UE to perform measurements for BFD if the channel/beam properties of different SCells in a group are nearly the same. Additionally, another benefit includes the reduction of TCC BFD depending on .

[91] In one embodiment has a flexibly assigned meaning. This flexible value is indicated in the control information and may depend on one or more factors, for example, UE capabilities such as higher layer signaling or downlink control indication. For example, the value flexibly indicated in the UE capabilities IE. If has a flexibly assigned value, this provides several advantages. Set value is flexibly assignable and may depend on one or more factors, such as the capabilities of the UE. This embodiment provides a reduction in the cost for the UE to perform measurements for BFD if the channel/beam properties of different SCells in a group are nearly the same. Additionally, another benefit includes the reduction of TCC BFD depending on .

[92] In one exemplary embodiment, the BFD operation may be based on other methods or combinations of methods. For example, the UE may be directed to use some method to perform BFD operation for each individual group (eg, based on a combination or ).

[93] Consider an example in which the BFD operation for each group is based on one or more of the following five operating options: (1) fixed value equal to one; (2) fixed value exceeds one; (3) flexible value ; (4) fixed value ; and (5) flexible value assignment .

[94] Consider an example with three groups. In this case, there are many possibilities or options for configuring the BFD operation for each individual group. For example, these options include fixed value , equal to one, fixed value , greater than one, and a fixed value , applied to the first, second and third groups, respectively. Second option (i.e. fixed value , exceeding one) is used for the first and second groups, and the third option (i.e., a flexible value ) used for the third group; etc. Subsequently, according to the received configuration information for each group, the UE uses the corresponding BFD method to perform a BFD operation to determine the beam failure in a particular group. This embodiment reduces the cost for the UE to perform measurements for BFD and the dependence of BFD TCC on , And .

[95] In one exemplary embodiment, the configuration information includes information for a BF report that is generated by the UE and transmitted to the cell. By way of example, this information includes a group identifier (such as the group identifier specified in the CC index or configuration index order) for each individual group. The configuration information in the BF report may include an indication to report the BF event via the PCell UL (or PsCell) or the SCell UL (if the SCell has both a DL and a UL). This information may also include instructions to report new beam information if such new information exists. In addition, this information may include one or more of the following: (1) an indication as to what type of measurement information (MI) for the group in which the failure occurred is to be transmitted (e.g., RSRP, signal to interference plus noise ratio (SINR)), and (2) a statement regarding the reporting of the cause of the BF event, if that cause is known.

[96] Indications with configuration information may be transmitted explicitly and/or implicitly to the UE. Consider the example of an implicit approach that is implemented using (pre-)configured rules. For example, in the same band, if CC1 provides cross-carrier scheduling configuration for CC3 and CC5, then the list of CCs is defined implicitly as CC1, CC3 and CC5, and CC1 is treated as a group identifier. Consider the example of an explicit approach that is carried out using control information. For example, this approach is implemented using at least Physical Downlink Control Channel Downlink Control Information (PDCCH DCI), MAC Control Elements (MAC CE), or an RRC message.

[97] The BF report may include a variety of information. For example, the UE generates and transmits a BF report that includes at least a group identifier for each individual group specified in the configuration information. If the number of failed groups exceeds the number of non-faulted groups at the same point in time, the UE reports the identifier(s) of the non-faulted group. Otherwise, the UE reports the group identifier(s) that failed. This embodiment makes it possible to reduce resource consumption when performing radio communications on the uplink.

[98] In addition, configuration information may be updated or changed. For example, the UE provides information about the new beam, including the CC index, Rx spatial parameter, and angle of arrival (AoA) to the gNB (if present). As an example, gNB assigns a new beam to existing groups or a new group by comparing its own large-scale properties with the properties of the specified SCells representing their groups. The gNB updates the configuration information to the UE. In one embodiment, group-based SCell spoke failover configuration information may be updated periodically or aperiodically.

[99] In one exemplary embodiment, according to the configuration information, only the specified SCell for each individual group is configured using the BFD reference signal(s) (RS BFD) either explicitly or implicitly (i.e., not all SCells in the group) . In this case, the UE receives a new instruction from the gNB directing the UE to perform BFR for a plurality of SCells based on a baseline scenario for the group. This new indication contains group-based BFR SCell configuration information.

[100] Group-based BFR SCell configuration information includes a specified CC (SCell) configured to perform BFD and report for each individual group. In this case, only that specified SCell will be configured using the BFD reference signal(s) (RS BFD) either explicitly or implicitly for each individual group (ie, not all SCells in the group). In this way, the downlink RS BFD can be reduced. In addition, other BFR resources can also be saved since the gNB only needs to allocate BFR resources to one CC in a group of CCs. In this case, the list of CCs does not need to be known to the UE and the group identifier may be the index of the specified CC or the order of the configuration index. Likewise, the gNB may also configure the RS BFD SCell for more than one CC in a CC group, and the configuration information may indicate on which CC the BFD should be performed and report based on the UE's capabilities and/or link state.

[101] According to the received group-based BFR SCell configuration information contained in the new indication, the UE counts only the BFII in the specified SCell for each individual group. If the specified SCell is identified as the failed cell, a group BF is declared. Processing for all SCells in the group occurs under failure conditions.

[102] According to the received group-based BFR SCell configuration information contained in the new indication, if the number of failed groups exceeds the number of non-faulted groups at the same point in time, the UE reports the identifier(s) of the non-faulted group. Otherwise, the UE reports the group identifier(s) that failed. This exemplary embodiment has several advantages. For example, the present embodiment can reduce resource consumption on the downlink RS BFD and reduce resource consumption in uplink radio communications. The present embodiment also reduces the cost for the UE to perform measurements for BFD and simplifies the BFR procedure.

[103] In one exemplary embodiment, all SCells from different groups may be configured with their own RS BFDs, either explicitly or implicitly, while it is possible that a specified SCell from each individual group will be configured with RS BFDs explicitly or implicitly only in specific cases.

[104] Exemplary embodiments include various group-based BFR SCell configuration information. In fig. 10 shows configuration information 1000 for BFR for a plurality of SCells based on a baseline scenario for a group according to an exemplary embodiment. In fig. 11 is a table 1100 with group-based BFR SCell configuration information according to an exemplary embodiment.

[105] As shown in FIG. 10 and 11, group-based BFR SCell configuration information is specified explicitly in SCellBFRConfigInfo IE and Group-basedSCellBFRInfo-IE as follows: Where maxGroupNr represents the maximum number of groups, maxNrofSCell represents the maximum number of SCells, and RSRP-Range represents the RSRP range . The results are presented in Table 1100.

[106] It will be apparent to one skilled in the art that the data shown in FIG. 10 and 11 are illustrative. Depending on the capabilities of the UE, the table size, data presented, etc. may be different. In the UE context, an example group-based BFR SCell operation capability IE can be represented as follows

ENUMERATED {SCell-basedBFRInfo, Group-basedSCellBFRInfo, both}

where the value " SCell-basedBFRInfo " indicates that the UE supports BFR for one base SCell; the value " Group-basedSCellBFRInfo " indicates that the UE supports group-based BFR SCell; and the value "both" indicates that the UE supports both BFR for SCell and BFR SCell based on group.

[107] The exemplary embodiments can be applied to various scenarios in which BFR reference signals are configured explicitly using RRC or implicitly using TCI state. For example, when explicitly configured using RRC, the RS BFD is transmitted in the current SCell. For example, in implicit state-based configuration of the TCI RS, the BFD is transmitted in the active bandwidth part (BWP) of either the current SCell or another SCell.

[108] In FIG. 12 shows an example of an electronic device 700 according to the exemplary embodiment.

[109] Electronic device 1200 includes power supply 1202, memory 1204, central processing unit (CPU) 1206, data storage 1208, wireless transmitter and/or receiver 1210, antennas 1212 (e.g., one or more antenna arrays or multiple antennas for perform beamforming) and a BFR block 1214 (eg, hardware and/or software for performing one or more of the exemplary embodiments discussed with respect to FIGS. 6-11).

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

[111] The BFR block 1214 of the electronic device 1200 contains hardware (e.g., circuitry) and/or software (e.g., code, instructions, or data) that is used to perform one or more of receiving configuration information for the BFR of a plurality of SCells operating on the 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 block 1214 is also configured to implement one or more of BFD, NBI, BFRQ, and BFRR.

[112] The exemplary embodiments may be implemented in various types of wireless networks that perform beamforming, such as 5G New Radio (NR), mobile networks, etc. Such networks include multiple transmitters and/or receiving antennas for beamforming. Channel state information is obtained by transmitting CSI reports based on CSI reference signals in the downlink and uplink.

[113] The present invention may be implemented by software, hardware, or software in conjunction with hardware. Each functional block used in the description of each embodiment set forth above may be partially or fully implemented using large-scale integration (LSI), such as an integrated circuit, and controls each process described in each embodiment. implementation may be partially or fully implemented using a specified LSI or combination of LSIs. LSI is a method of integrating a large number of transistors on a silicon semiconductor chip or microchip, and can include very large scale integration (VLSI) and ultra large scale integration (ULSI). The LSI chip may be formed separately as microchips, or a single microchip may be formed to include a portion of the functional blocks or all of the functional blocks. The LSI chip may include data input and output coupled thereto. The LSI chip herein may be referred to as an integrated circuit, a system large-scale integrated circuit, a super-large-scale integrated circuit, or a very large-scale integrated circuit depending on the degree of integration. However, the implementation method of an integrated circuit is not limited to a large-scale integrated circuit, and may be implemented using an application-specific circuit, a general-purpose processor, or a special-purpose processor. In addition, an FPGA (Field Programmable Gate Array) can be used, which can be programmed after the large integrated circuit has been manufactured, or a reconfigurable processor, in which the connection configuration and settings of circuit elements located inside a large integrated circuit. The present invention may be implemented as digital data processing or analog data processing. If future integrated circuit technology replaces large scale integrated circuits as a result of developments in semiconductor technology or other derivative technology, the functional blocks may be integrated using the future integrated circuit technology. In addition, biotechnology can be applied.

[114] The present invention can be implemented using any type of apparatus, device or system having a communication function, which are referred to as communication devices. The communication device may include a transceiver and processing/control circuitry. The transceiver may include a receiver and a transmitter and/or function as a receiver and a transmitter. The transmitter-receiver transceiver may include a radio frequency (RF) module including amplifiers, RF modulators/demodulators, etc., and one or more amplifiers, RF modulators/demodulators, etc., and one or more antennas. The processing/control circuitry may include power management circuitry, which may include dedicated circuitry, a processor, and power management instructions in the form of firmware or instructions stored in a memory device coupled to the processor.

[115] Non-limiting examples of such communication devices include telephone (e.g., cell phone, smartphone), tablet, personal computer (PC) (e.g., laptop, desktop, netbook), camera (e.g., digital camera/ video camera), digital player (e.g. digital audio/video player), wearable device (e.g. wearable camera, smart watch, tracking device), game console, digital book reader, remote diagnostic and treatment device/telemedicine ( remote health diagnostics and medical services) and a vehicle with communication functionality (for example, a car, an aircraft, a ship), as well as various combinations thereof.

[116] A communications apparatus is not limited to a portable or wearable apparatus and may also include any type of apparatus, device, or system that is not portable or stationary, such as a smart home device (e.g., appliance, lighting fixture, smart meter, control panel ), a vending machine and any other “physical objects” in the “Internet of Things (IoT)” network. Communication may include the exchange of data through, for example, a cellular system, a wireless LAN system, a satellite system, etc., as well as various combinations thereof.

[117] A communication device may comprise a device, such as a controller or sensor, that is coupled to a communication device performing the communication function described in the present disclosure. For example, the communication device may include a controller or sensor that generates control signals or data signals used by the communication device to perform the communication function of the communication device.

[118] A communications apparatus may also include an infrastructure entity such as a base station, an access point, and any other apparatus, device, or system that communicates with or controls apparatuses, such as those mentioned in the non-limiting examples above.

[119] Although exemplary embodiments have been presented in the foregoing detailed description of the present invention, it should be understood that a wide variety of variations exist. Additionally, it should be understood that the exemplary embodiments are exemplary only and are not intended in any way to limit the scope, applicability, operation, or configuration of the present invention. In contrast, the foregoing detailed description provides those skilled in the art with a convenient roadmap for implementing the exemplary embodiments, and it should be understood that the function and relative location of the network and/or UE described in the exemplary embodiments may Various changes may be made without departing from the scope of the present invention as set forth in the appended claims.

[120] Other exemplary embodiments include, without limitation, the following examples:

[121] A communications apparatus comprising: a receiver that, in operation, receives configuration information for the BFR of a plurality of SCells operating in the network; and a circuit that, at runtime, performs BFD and generates a report based on the specified configuration information.

[122] According to the exemplary embodiment, the configuration information includes a CC list.

[123] According to an exemplary embodiment, BFD is performed based on at least one of: (1) the number of multiple SCells in which a failure has been detected in the group threshold value , Where represents the minimum number of SCells having a failure condition in the group; or (2) the amount of BFII SCell in the group threshold value ), Where , represents the BFII value th SCell, represents the number of SCells in the group, and represents the maximum number of BFII SCells in the group.

[124] According to the exemplary embodiment, the threshold value is a (predefined) fixed value of one and is further configured to count the BFII for each of the SCells in the group and declare a beam failure (BF) of the group if a failure is detected in any of the SCells in the group.

[125] According to the exemplary embodiment, the threshold value is a (predefined) fixed value greater than one, and is further configured to be able to count BFII to detect a BF for each of the SCells in the group and declare that the SCell is in the group under failure conditions if .

[126] According to the exemplary embodiment, the threshold value flexibly indicated in the control information depending on the capabilities of the communication apparatus, which include higher layer signaling or downlink control indication.

[127] According to the exemplary embodiment represents a (predefined) fixed value.

[128] According to the exemplary embodiment is a flexibly assignable value indicated in the control information depending on the capabilities of the communication apparatus, which include higher layer signaling or downlink control indication.

[129] According to the exemplary embodiment, a method based on or ,to perform BFD for each group.

[130] According to an exemplary embodiment, the configuration information includes a group identifier comprising a group identity (ID), a specified CC index, or a configuration index order for each group.

[131] According to an exemplary embodiment, instructions with configuration information are transmitted based on at least one of the following methods: by using a (pre)configured rule, control information by at least a physical PDCCH DCI, a MAC CE, or an RRC message.

[132] According to the exemplary embodiment, the content of the BF report includes at least a group ID for each group specified in the configuration information.

[133] According to the exemplary embodiment, the communication apparatus is also configured to provide information about the new beam, including a CC index, a spatial parameter Rx and AoA.

[134] In an exemplary embodiment, the configuration information includes at least a specified SCell to perform BFD and a report for each individual group, wherein only the specified SCell(s) can be configured with the BFD reference signal(s) explicitly or implicitly.

[135] According to the exemplary embodiment, if the number of groups in which a failure has occurred exceeds the number of groups without failures at the same time, the communication apparatus reports the IDs of the groups without failures; otherwise, the communication device reports the groups that have failed.

[136] According to yet another exemplary embodiment, a method is provided that includes: receiving, by a communication apparatus, configuration information for the BFR of a plurality of SCells operating in a network; The communication device performs BFD and generates a report based on the specified configuration information.

[137] Although exemplary embodiments have been presented in the foregoing detailed description of embodiments, it should be understood that a wide variety of variations exist. In addition, it should be understood that the exemplary embodiments are exemplary only and are not intended in any way to limit the scope, applicability, operation, or configuration of the present invention. On the contrary, the foregoing detailed description provides those skilled in the art with a convenient roadmap for implementing the exemplary embodiments according to the present invention, and it should be understood that the functions and arrangements of steps, as well as the method of operation, described in the exemplary embodiments may be different. Various changes have been made without departing from the scope of the present invention as set forth in the appended claims.

Claims (50)

1. Communication device containing: A receiver that, in operation, receives group information and configuration information for beam failure recovery (BFR) of a group of secondary cells (SCells), wherein the group information indicates one or more carriers included in SCells group; And a transmitter that, in operation, transmits reporting information based on BFR configuration information, wherein the reporting information includes at least one of a beam failure detection (BFD) result of a group of SCells and information about a new beam of a group of SCells. 2. The communication apparatus of claim 1, wherein the reporting information includes indexes of each of the failed SCells that are identified as failed by BFD. 3. The communications apparatus of claim 2, wherein the reporting information includes new beam information for each of the failed SCells that are identified as failed by the BFD. 4. The communications apparatus of claim 1, wherein the reporting information is transmitted if the number of beam failure instances (BFIs) of any SCell from the group of SCells is equal to or greater than the first threshold specified by the base station. 5. The communication device according to claim 1, in which the reporting information is transmitted if the number of SCells from the group of SCells that are identified as faulty during BFD is equal to one or more than one. 6. The communication apparatus of claim 1, wherein the reporting information is transmitted if the number of SCells from the group of SCells that are identified as failed by BFD is equal to or greater than a second threshold value specified by the base station. 7. The communication device according to claim 1, in which the configuration information indicates the implementation of BFR of a plurality of SCells included in the group of SCells. 8. The communications apparatus of claim 1, wherein the BFR configuration information is indicated by user equipment (UE)-specific signaling. 9. The communications apparatus of claim 1, wherein beam failure detection is performed for each SCell in the group of SCells. 10. Communication method, including: receiving group information and configuration information for beam failure recovery (BFR) of a group of secondary cells (SCells), the group information indicating one or more carriers included in the group of SCells; And transmitting reporting information based on the BFR configuration information, wherein the reporting information includes at least one of a beam failure detection (BFD) result of the group of SCells and information about a new beam of the group of SCells. 11. The communication method as set forth in claim 10, wherein the reporting information includes indexes of each of the failed SCells that are identified as failed by BFD. 12. The communication method of claim 11, wherein the reporting information includes information about a new beam for each of the failed SCells that are identified as failed by the BFD. 13. The communication method of claim 10, whereby reporting information is transmitted if the number of beam failure instances (BFIs) of any SCell from the group of SCells is equal to or greater than the first threshold specified by the base station. 14. The communication method according to claim 10, according to which the reporting information is transmitted if the number of SCells from the group of SCells that are identified as faulty during BFD is equal to one or more than one. 15. The communication method of claim 10, wherein the reporting information is transmitted if the number of SCells from a group of SCells that are identified as failed by BFD is equal to or greater than a second threshold specified by the base station. 16. The communication method according to claim 10, according to which the configuration information indicates the implementation of BFR of a plurality of SCells included in the group of SCells. 17. Communication device containing: a transmitter that, in operation, transmits group information and configuration information for beam failure recovery (BFR) of a group of secondary cells (SCells), the group information indicating one or more carrier components included in the group of SCells; And a receiver that, in operation, receives reporting information based on the BFR configuration information, wherein the reporting information includes at least one of a beam failure detection (BFD) result of a group of SCells and information about a new beam of a group of SCells. 18. The communications apparatus of claim 17, wherein the reporting information includes indices of each of the failed SCells that are identified as failed by the BFD. 19. The communications apparatus of claim 18, wherein the reporting information includes new beam information for each of the failed SCells that are identified as failed by the BFD. 20. The communications apparatus of claim 17, wherein the reporting information is transmitted if the number of beam failure instances (BFIs) of any SCell from the group of SCells is equal to or greater than a first threshold specified by the base station. 21. The communication device according to claim 17, in which the reporting information is transmitted if the number of SCells from the group of SCells that are identified as faulty during BFD is equal to one or more than one. 22. The communication apparatus of claim 17, wherein the reporting information is transmitted if the number of SCells from the group of SCells that are identified as failed by BFD is equal to or greater than a second threshold specified by the base station. 23. The communication device according to claim 17, in which the configuration information indicates the implementation of BFR of a plurality of SCells included in the group of SCells. 24. The communications apparatus of claim 17, wherein the BFR configuration information is indicated by user equipment (UE)-specific signaling. 25. The communications apparatus of claim 17, wherein beam failure detection is performed for each SCell in the group of SCells. 26. Communication method, including: transmitting group information and configuration information for beam failure recovery (BFR) of a group of secondary cells (SCells), wherein the group information indicates one or more carrier components included in the group of SCells; And receiving reporting information based on the BFR configuration information, wherein the reporting information includes at least one of a beam failure detection (BFD) result of the group of SCells and information about a new beam of the group of SCells. 27. The communication method of claim 26, wherein the reporting information includes indexes of each of the failed SCells that are identified as failed by the BFD. 28. The communication method of claim 27, wherein the reporting information includes new beam information for each of the failed SCells that are identified as failed by the BFD. 29. The communication method of claim 26, wherein the reporting information is transmitted if the number of Beam Failure Instances (BFIs) of any SCell from the group of SCells is equal to or greater than the first threshold specified by the base station. 30. The communication method according to clause 26, according to which reporting information is transmitted if the number of SCells from the group of SCells that are identified as faulty during BFD is equal to one or more than one. 31. The communication method of claim 26, wherein the reporting information is transmitted if the number of SCells from a group of SCells that are identified as failed by BFD is equal to or greater than a second threshold specified by the base station. 32. The communication method according to claim 26, according to which the configuration information indicates the implementation of BFR of a plurality of SCells included in the group of SCells. 33. Integrated communication circuit containing: a receiving circuit that, during operation, controls: receiving group information and configuration information for beam failure recovery (BFR) of a group of secondary cells (SCells), the group information indicating one or more carrier components included in the group of SCells; And transmission circuit, which during operation controls: transmitting reporting information based on the BFR configuration information, wherein the reporting information includes at least one of a beam failure detection (BFD) result of the group of SCells and information about a new beam of the group of SCells. 34. Integrated communication circuit containing: transmission circuit, which during operation controls: transmitting group information and configuration information for beam failure recovery (BFR) of a group of secondary cells (SCells), the group information indicating one or more carrier components included in the group of SCells; And a receiving circuit that, during operation, controls: receiving reporting information based on the BFR configuration information, wherein the reporting information includes at least one of a beam failure detection (BFD) result of the group of SCells and information about a new beam of the group of SCells.