CN113615100B

CN113615100B - Method and device for recovering beam failure of second cell, user equipment and network equipment

Info

Publication number: CN113615100B
Application number: CN202080019470.6A
Authority: CN
Inventors: 郭力
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-07-25
Filing date: 2020-07-15
Publication date: 2023-10-10
Anticipated expiration: 2040-07-15
Also published as: CN113615100A; WO2021013017A1

Abstract

A method and apparatus for recovering SCell beam failure, user Equipment (UE), and network equipment are provided. The UE detects that at least one SCell fails in a beam and sends at least one indication message to the network equipment, wherein the at least one indication message is used for indicating the at least one SCell fails in the beam. The UE receives Downlink Control Information (DCI) sent by the network equipment, wherein the DCI is used for requesting the UE to report first Uplink Control Information (UCI) on a first physical channel. The UE reports a first UCI carrying first indication information and/or second indication information to a network device on the first physical channel, where the first indication information is used to indicate an index of each SCell in the at least one SCell, and the second indication information is used to indicate an index of a new Reference Signal (RS) associated with each SCell in the at least one SCell.

Description

Method and device for recovering beam failure of second cell, user equipment and network equipment

Cross Reference to Related Applications

The present application claims priority from U.S. patent application Ser. No. 62/878,460, filed on 7/25 at 2019, the entire contents of which are incorporated herein by reference.

Technical Field

The embodiment of the application relates to the technical field of mobile communication, in particular to a method and a device for recovering beam failure of a second Cell (Scell), UE (user equipment) and network equipment.

Background

A drawback of the medium access control based control element (MAC CE) method for SCell beam failure recovery is the complex Scheduling Request (SR) trigger mechanism and may cause a large delay in the uplink SCell beam failure recovery request message transmission. In the SR mechanism, the UE triggers the SR only when the buffer of the data packet received from the upper layer is not empty. In contrast, when SCell beam failure occurs, the UE generates a MAC CE to report the index of the failed SCell, but the generation of the MAC CE does not trigger the SR. Therefore, MAC CEs transmitted through a Physical Uplink Shared Channel (PUSCH) may wait for a long time.

Disclosure of Invention

The embodiment of the application provides a method and a device for recovering SCell wave beam failure, UE and network equipment.

The SCell beam failure recovery method provided by the embodiment of the application comprises the following operations.

The UE detects that at least one SCell fails in a beam and sends at least one indication message to the network equipment. The at least one indication information is used for indicating that the at least one SCell fails in a beam.

The UE receives Downlink Control Information (DCI) transmitted by a network device. The DCI is used to request the UE to report first Uplink Control Information (UCI) on a first physical channel.

And the UE reports a first UCI to network equipment on the first physical channel. The first UCI carries first indication information for indicating an index of each of the at least one SCell and/or second indication information for indicating an index of a new Reference Signal (RS) associated with each of the at least one SCell.

The network equipment receives at least one indication message sent by the UE. The at least one indication information is used for indicating that beam failure occurs in the at least one Scell;

the network device transmits DCI to the UE, where the DCI is used to request the UE to report first Uplink Control Information (UCI) on a first physical channel.

The network equipment receives a first UCI reported by the UE on the first physical channel, wherein the first UCI carries first indication information and/or second indication information. The first indication information is used to indicate an index of each of the at least one SCell, and the second indication information is used to indicate an index of a new RS associated with each of the at least one SCell.

The SCell beam failure recovery device provided by the embodiment of the application is applied to UE, and comprises a detection unit, a sending unit and a receiving unit.

The detection unit is configured to detect that at least one SCell fails in a beam.

The sending unit is configured to send at least one indication information to a network device, where the at least one indication information is used to indicate that the at least one SCell fails in a beam.

The receiving unit is configured to receive DCI sent by a network device. The DCI is used for requesting the UE to report a first UCI on a first physical channel.

The sending unit is further configured to report a first UCI to a network device on the first physical channel. The first UCI carries first indication information and/or second indication information. The first indication information is used to indicate an index of each of the at least one SCell, and the second indication information is used to indicate an index of a new RS associated with each of the at least one SCell.

The SCell wave beam failure recovery device provided by the embodiment of the application is applied to network equipment and comprises a receiving unit and a sending unit.

The receiving unit is used for receiving at least one indication message sent by the UE. The at least one indication information is used for indicating that the at least one SCell fails in a beam.

The sending unit is configured to send DCI to the UE. The DCI is used for requesting the UE to report a first UCI on a first physical channel.

The receiving unit is further configured to receive a first UCI reported by the UE on the first physical channel. The first UCI carries first indication information and/or second indication information, where the first indication information is used to indicate an index of each SCell in the at least one SCell, and the second indication information is used to indicate an index of a new RS associated with each SCell in the at least one SCell.

The UE provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the SCell beam failure recovery method.

The network equipment provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the SCell beam failure recovery method.

The chip provided by the embodiment of the application is used for realizing the SCell beam failure recovery method.

Specifically, the chip includes: and the processor is used for calling and running the computer program from the memory, so that the device provided with the chip executes the SCell beam failure recovery method.

The computer readable storage medium provided by the embodiment of the application is used for storing a computer program, and the computer program enables a computer to execute the SCell beam failure recovery method.

The embodiment of the application provides a computer program product, which is stored with computer program instructions, and the computer program instructions enable a computer to execute the SCell beam failure recovery method.

The computer program provided by the embodiment of the application, when running on a computer, causes the computer to execute the SCell beam failure recovery method.

According to the method of the embodiment of the application, the beam failure recovery message of the SCell is sent by using 100% physical layer signaling and channels, so that the beam failure recovery operation of the SCell with low delay is obtained, and the dependence on a complex SR trigger mechanism in a higher layer is eliminated.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:

fig. 1 is a schematic diagram of a communication system architecture according to an embodiment of the present application;

Fig. 2 is a flowchart of a SCell beam failure recovery method according to an embodiment of the present application;

fig. 3 is a second flow chart of a SCell beam failure recovery method according to an embodiment of the present application;

fig. 4 is a flowchart of a SCell beam failure recovery method according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of an SCell beam failure recovery apparatus according to an embodiment of the present application;

fig. 6 is a schematic diagram ii of the structural composition of the SCell beam failure recovery apparatus according to the embodiment of the present application;

fig. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 8 is a schematic block diagram of a chip of an embodiment of the application;

fig. 9 is a schematic block diagram of a communication system provided by an embodiment of the present application.

Detailed Description

The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The technical scheme of the embodiment of the application can be applied to various communication systems, such as: long term evolution (Long Term Evolution, LTE) systems, LTE frequency division duplex (Frequency Division Duplex, FDD) systems, LTE time division duplex (Time Division Duplex, TDD) systems, 5G communication systems, future communication systems, or the like.

An exemplary communication system 100 to which embodiments of the present application may be applied is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area. Alternatively, the network device 110 may be an evolved base station (eNB or eNodeB) in an LTE system, or a radio controller in a Cloud Radio Access Network (CRAN). Alternatively, the network device may be a mobile switching center, a relay station, an access point, an in-vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future communication system, or the like.

The communication system 100 further includes at least one terminal 120 located within the coverage area of the network device 110. "terminal" as used herein includes, but is not limited to, connection via a wireline, such as via a public-switched telephone network (PSTN), digital Subscriber Line (DSL), digital cable, direct cable connection; and/or another data connection/network; and/or via a wireless interface, e.g., an amplitude modulation-frequency modulation (AM-FM) broadcast transmitter for a cellular network, a Wireless Local Area Network (WLAN), a digital television network such as a digital video broadcasting-handheld (DVB-H) network, a satellite network, a network; and/or means of the other terminal arranged to receive/transmit communication signals; and/or internet of things (IoT) devices. Terminals arranged to communicate over a wireless interface may be referred to as "wireless communication terminals", "wireless terminals" or "mobile terminals". Examples of mobile terminals include, but are not limited to, satellites or cellular telephones; a Personal Communications System (PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA that can include a radiotelephone, pager, internet/intranet access, web browser, organizer, calendar, and/or a Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal in a 5G network, or a terminal in a future evolved PLMN, etc.

Alternatively, direct terminal (D2D) communication may be performed between terminals 120.

Alternatively, the 5G communication system or 5G network may also be referred to as a new wireless (NR) system or NR network.

Fig. 1 exemplarily shows one network device and two terminals. Alternatively, the communication system 100 may include a plurality of network devices and each network device may include other numbers of terminals within a coverage area of the network device, which is not limited by the embodiment of the present application.

Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited by the embodiment of the present application.

It should be understood that a device having a communication function in a network/system according to an embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal 120 with communication functions, where the network device 110 and the terminal 120 may be specific devices described above, and are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following describes the technical solutions related to the embodiments of the present application.

In 5G NR version 15, a multi-beam based system is supported. Base Stations (BS) and/or UEs use multiplexed Tx and Rx analog beams to combat large path loss in the high frequency band. In high-band systems such as millimeter wave (mmWave) systems, BSs and UEs are deployed with a large number of antennas so that large-gain beamforming can be used to overcome large path loss and signal blockage. Due to hardware limitations and costs, BSs and UEs may be equipped with only a limited number of transmit and receive units (TXRUs). Thus, a hybrid beamforming mechanism may be utilized in both the BS and the UE. In order to obtain the best link quality between the BS and the UE, the BS and the UE need to align the analog beam directions for a particular downlink or uplink transmission. For downlink transmission, an optimal BS Tx beam and UE Rx beam pair is required, while for uplink transmission, an optimal UE Tx beam and BS Rx beam pair is required. In the 3gpp 5g specification, the following functions are defined to support such multi-beam based operation: beam measurement and reporting, beam indication and beam switching.

The current NR specifications support only the beam failure recovery function of the primary cell (PCell). The function of PCell beam failure recovery is based on uplink Random Access Channel (RACH) transmissions. For beam failure detection, the UE is configured with a set q of beam failure detection Reference Signals (RSs) ₀ . UE measurement set q ₀ A hypothetical block error rate (BLER) on each Reference Signal (RS). When set q ₀ When the assumed BLER of all RSs in (a) is above a certain threshold, the UE declares a beam failure event for the PCell, and then the UE may transmit RACH configured for beam failure recovery. After transmitting RACH, UE monitors a dedicated control resource set (CORESET) for beam failure recovery to detect a response from a next generation base station (gNB).

For beam failure recovery in scells, it is currently designed to use MAC CE messages to report the ID of one SCell where beam failure occurred. The UE may also report the ID of the new beam through a MAC CE message.

The drawback of the MAC CE-based approach for SCell beam failure recovery is the complex Scheduling Request (SR) trigger mechanism and may cause a large delay in the uplink SCell beam failure recovery request message transmission. In the SR mechanism, the UE triggers the SR only when the buffer of the data packet received from the upper layer is not empty. In contrast, when SCell beam failure occurs, the UE generates a MAC CE to report the index of the failed SCell, but the generation of the MAC CE does not trigger the SR. Therefore, MAC CEs transmitted through a Physical Uplink Shared Channel (PUSCH) may wait for a long time.

For this reason, the following technical solutions of the embodiments of the present application are provided. In the present application, an SCell beam failure recovery method based on a Physical Uplink Control Channel (PUCCH) is provided.

Fig. 2 is a flowchart of an SCell beam failure recovery method according to an embodiment of the present application, as shown in fig. 2, where the SCell beam failure recovery method includes the following steps 201 to 203.

Step 201: the UE detects that at least one SCell fails in a beam and sends at least one indication message to the network equipment. The at least one indication information is used for indicating that the at least one SCell fails in a beam.

In the embodiment of the application, the UE detects that at least one SCell fails in wave beam, at least one indication information is sent to the network equipment, and the network equipment receives the at least one indication information sent by the UE. The at least one indication information is used for indicating that the at least one SCell fails in a beam. Here, the network device may be a base station, such as a gNB.

In the embodiment of the present application, the network device sends third configuration information to the UE, and the UE receives the third configuration information sent by the network device, where the third configuration information is used to determine at least one SCell configuration. The UE detects whether a beam failure occurs for each of the at least one SCell based on the at least one SCell configuration.

In the above solution, each SCell configuration includes at least one of the following information: configuration information of the beam failure detection RS, configuration information of the new beam identification RS set, threshold information for identifying the new RS.

In embodiments of the present application, the UE may be configured to perform beam failure recovery for one or more given scells. For each SCell configured for beam failure recovery, the UE monitors a beam failure detection RS associated with the SCell to detect a beam failure event on the SCell. When a beam failure event is detected on a given SCell, the UE may report information of the beam failure event of the SCell to the serving gNB using PUCCH, and then wait for a response from the gNB.

In an alternative manner, when the UE detects that at least one SCell fails in a beam, the UE sends an indication message to the network device, where the indication message is used to indicate that the at least one SCell fails in a beam.

Here, the one indication information may be transmitted through a PUCCH. Specifically, the network device sends first configuration information to the UE, and the UE receives the first configuration information sent by the network device, where the first configuration information is used to determine PUCCH configuration corresponding to the first PUCCH resource. The UE sends third indication information to the network equipment on the first PUCCH resource based on the first configuration information, and the network equipment receives the third indication information sent by the UE on the first PUCCH resource, wherein the third indication information is used for indicating the at least one SCell to generate beam failure.

The UE sending, based on the first configuration information, third indication information to the network device on the first PUCCH resource means that the UE sends, based on the first configuration information, a PUCCH on the first PUCCH resource, where the PUCCH carries the third indication information.

In another alternative, the UE detects that a plurality of scells fail in beam, and sends a plurality of indication information to the network device, where each indication information in the plurality of indication information is used to indicate that one SCell in the plurality of scells fails in beam.

Here, each of the plurality of indication information may be transmitted through a PUCCH. Specifically, taking two scells as an example, the at least one SCell includes a first SCell and a second SCell. The network device sends first configuration information and second configuration information to the UE, the UE receives the first configuration information and the second configuration information sent by the network device, the first configuration information is used for determining PUCCH configuration corresponding to the first PUCCH resource, and the second configuration information is used for determining PUCCH configuration corresponding to the second PUCCH resource. The UE sends third indication information to the network device on the first PUCCH resource based on the first configuration information and fourth indication information to the network device on the second PUCCH resource based on the second configuration information. The network device receives third indication information sent by the UE on the first PUCCH resource and fourth indication information sent by the UE on the second PUCCH resource. The third indication information is used for indicating the first SCell to generate beam failure, and the fourth indication information is used for indicating the second SCell to generate beam failure.

It should be noted that, the technical solution of the embodiment of the present application is not limited to the above-mentioned two scells, and other scells with larger numbers are also applicable to the technical solution of the embodiment of the present application.

In the foregoing aspect, in an optional embodiment, the PUCCH configuration includes at least one of the following information: the method comprises the steps of identifying the PUCCH resource, the period of the PUCCH resource, the bias of the PUCCH resource in one period and the index of the first resource unit of the PUCCH resource in one period.

In the above solution, in another alternative, the PUCCH configuration is determined based on a specific SR configuration, where the specific SR configuration refers to an SR configuration used for the SCell beam failure event reporting request. The PUCCH configuration determined based on the specific SR configuration cannot be used to transmit an SR request for an uplink shared channel (UL-SCH) requesting a new transmission.

Step 202: the UE receives Downlink Control Information (DCI) sent by a network device, where the DCI is used to request the UE to report first Uplink Control Information (UCI) on a first physical channel.

In the embodiment of the application, the network equipment sends DCI to the UE, and the UE receives the DCI sent by the network equipment, wherein the DCI is used for requesting the UE to report a first UCI on a first physical channel.

In the embodiment of the present application, the first UCI refers to UCI of an SCell beam failure recovery request; or, the first UCI refers to UCI of an SCell link recovery request.

In an alternative manner, the DCI carries fifth indication information, where the fifth indication information is used to indicate the first physical channel, and the first physical channel belongs to a PUCCH.

In another alternative, the DCI carries fifth indication information, where the fifth indication information is used to schedule transmission of the first physical channel, and the first physical channel belongs to PUSCH.

In one example, the at least one indication information in the above scheme is sent in a time slot n, where n is a positive integer. And the UE receives DCI sent by the network equipment in a time window, wherein the starting time slot of the time window is a time slot n+1. Further, if the UE does not receive DCI transmitted by the network device within the time window, the UE retransmits the at least one indication information to the network device.

Step 203: the UE reports a first UCI carrying first indication information and/or second indication information to a network device on the first physical channel, where the first indication information is used to indicate an index of each SCell in the at least one SCell, and the second indication information is used to indicate an index of a new RS associated with each SCell in the at least one SCell.

In the embodiment of the application, the UE reports the first UCI to the network equipment on the first physical channel, and the network equipment receives the first UCI reported by the UE on the first physical channel. The first UCI carries first indication information and/or second indication information, where the first indication information is used to indicate an index of each SCell in the at least one SCell, and the second indication information is used to indicate an index of a new RS associated with each SCell in the at least one SCell.

In an alternative manner, the DCI carries fifth indication information, where the fifth indication information is used to indicate the first physical channel, and the first physical channel belongs to a PUCCH. And the UE sends the first UCI to a network device through a PUCCH based on the fifth indication information, and the network device receives the first UCI sent by the UE on the PUCCH resource.

In another alternative, the DCI carries fifth indication information, where the fifth indication information is used to schedule transmission of the first physical channel, and the first physical channel belongs to PUSCH. And the UE sends the first UCI to network equipment through the PUSCH based on the fifth indication information, and the network equipment receives the first UCI sent by the UE on the PUSCH resource.

The technical scheme of the embodiment of the application comprises the following two parts.

In the first part, referring to step 201 above, the UE is configured with PUCCH resource configuration, and using this PUCCH resource configuration, the UE reports an event of SCell beam failure. When the UE detects beam failure in one SCell, the UE reports a positive indicator in PUCCH resources to inform the gNB.

In the second part, referring to steps 203 and 203, a new UCI format (referred to as a first UCI) is defined for the SCell beam failure recovery function. In one example, the UCI may be referred to as UCI of an SCell beam failure recovery request. In one example, the UCI may be referred to as UCI of the SCell link recovery request. The gNB may use DCI to trigger aperiodic reporting of UCI for SCell link recovery requests. In an alternative manner, the UCI of the SCell beam failure recovery request may be carried in PUSCH transmission, and the gNB may request the UCI of the SCell beam failure recovery request using DCI and grant PUSCH transmission. In another alternative example, UCI of the SCell beam failure recovery request may be carried in PUCCH transmission, wherein the gNB may request UCI of the SCell beam failure recovery request using DCI and indicate one PUCCH resource to be used for the UCI transmission.

For the first part of the above-described scheme, the following two ways are further proposed.

In a first manner, a first configured Physical Uplink Control Channel (PUCCH) resource is configured for the UE to report an event of beam failure occurring in some scells, and then the gNB triggers an aperiodic UCI report in which the UE reports the ID of the SCell in which beam failure occurs and/or the ID of a new beam. The UCI report is carried in PUSCH. The UCI report may be carried on PUCCH. An example of the PUCCH resource of the first configuration is that the gNB explicitly configures the UE to report a beam failure event using SR configuration, rather than for UL-SCH resource request.

In a second manner, for each SCell configured for beam failure recovery, the UE configures a dedicated PUCCH resource, and when beam failure occurs in the SCell, the UE reports UCI of 1 bit in the configured PUCCH to report a beam failure event for the SCell to the gNB. The gNB may explicitly configure the UE to report beam failure events using a specific SR configuration, rather than for the UL-SCH.

The first and second modes described above will be described in detail below with reference to fig. 3 and 4, respectively.

Fig. 3 is a second flowchart of an SCell beam failure recovery method according to an embodiment of the present application, as shown in fig. 3, where the SCell beam failure recovery method includes the following steps 301 to 307.

Step 301: the serving gNB sends configuration information to the UE.

Here, the configuration information includes the following: configuration of beam failure recovery for one or more scells. PUCCH for the first configuration of the beam failure event reporting request, and configuration of UCI for the Scell beam failure recovery request, e.g., a Bateoffset value and PUCCH resources.

Specifically, the UE receives configuration information about Scell beam failure recovery from the serving gNB. The configuration information includes the following: configuration of beam failure recovery of the first Scell, which includes configuration of beam failure detection RS, configuration of new beam identification RS set and configuration of threshold identifying new RS; configuration of beam failure recovery of the second Scell, comprising configuration of beam failure detection RS, configuration of new beam identification RS set and configuration of threshold identifying new RS; the first configured PUCCH for the Scell beam failure event reporting request may include, in one example, a PUCCH resource ID, a period of a slot, which may be in symbols, and a slot offset, and in this case the configuration includes a starting symbol index; the configuration list of PUCCH resources and time offset information can be used for the UE to report the aperiodic UCI of the SCell beam failure recovery request; and a betaOffset value of UCI of the SCell beam failure recovery request when UCI is multiplexed in PUSCH transmission.

Step 302: for each Scell configured for beam failure recovery, the UE measures a beam failure detection RS to detect a beam failure based on the configuration information.

Here, taking two scells as an example, the UE monitors a beam failure detection RS corresponding to the first SCell and a beam failure detection RS corresponding to the second SCell according to configuration information to detect a beam failure in the first SCell and a beam failure in the second SCell.

Step 303: the UE determines a beam failure event on at least one Scell.

Step 304: the UE transmits a positive indicator on PUCCH resources of the first configured PUCCH configuration.

Step 305: the UE starts detecting DCI of the gNB to trigger the aperiodic UCI of the Scell beam failure recovery request.

In the above steps 303 to 305, when a beam failure is detected in the first Scell and/or the second Scell, the UE reports the positive indicator on the PUCCH resources of the PUCCH configuration of the first configuration. After transmitting the positive indicator in slot n, the UE starts monitoring the PDCCH of DCI that triggers the UCI of the transmission of the Scell beam failure recovery request on PUSCH or PUCCH.

After transmitting the positive indicator of the Scell beam failure event on slot n, the UE may monitor the PDCCH of the DCI that triggers the UCI of the transmission of the Scell beam failure recovery request during the time window starting from slot n+1. If the UE does not receive DCI within the time window, the UE may retransmit the positive indicator on PUCCH resources of the first configured PUCCH configuration.

Step 306: the serving gNB transmits DCI on the PDCCH to trigger UCI reporting a Scell beam failure recovery request in, e.g., PUSCH or PUCCH.

In an alternative manner, the serving gNB sends DCI to trigger the UE to report UCI of the Scell beam failure recovery request in PUSCH transmission. The DCI includes a 1-bit field (e.g., referred to as an SCell link recovery request) to indicate UCI requesting the UE to report a SCell beam failure recovery request in a scheduled PUSCH.

In another alternative, the serving gNB sends DCI to trigger the UE to report UCI of the Scell beam failure recovery request on the indicated PUCCH resources. The DCI includes a bit field (e.g., referred to as a Scell link recovery request) to indicate UCI reporting a Scell beam failure recovery request in a PUCCH of a given slot. Information of PUCCH resources and indexes of slots may be configured by a higher layer and indicated by DCI.

Step 307: the UE reports UCI of the Scell beam failure recovery request requested by the gNB. Examples of UCI content include an indicator of a failed Scell.

According to DCI received from the serving gNB, the UE transmits UCI of the Scell beam failure recovery request in a scheduled PUSCH or an indicated PUCCH resource. The UE may report one or more of the following information in UCI of the Scell beam failure recovery request: a SCell indicator for the SCell indicating the occurrence of the beam failure event; and an indicator of channel state information reference information (CSI-RS) or Synchronization Signal (SS) or Physical Broadcast Channel (PBCH) block selected from a new set of beam-identifying RSs for beam failure recovery for the reported Scell.

In one method, the UE may be configured to perform beam failure recovery for one or more scells. For a given Scell, higher layer parameters may be provided to the UE to explicitly configure the UE for beam failure recovery for the Scell. In one example, for scells with index ScellIndex, if the UE is configured with higher layer parameters scellbeam failure recovery config, the UE may assume that the gNB configures the UE to perform beam failure recovery for scells with index ScellIndex. Examples of parameters ScellIndex are shown in table 1 below.

TABLE 1

Another example of the parameter scellbeam failurerecoverccofig is shown in table 2 below.

TABLE 2

In one approach, the UE may be configured with a configuration to report the request in PUCCH transmission Scell beam failure event with PUCCH format 0 or PUCCH format 1. In one example, the UE may be configured by the higher layer parameters scellbeamfailureeventreportrequest config, which include: PUCCH resource ID, PUCCH _SCellBFR1 The method comprises the steps of carrying out a first treatment on the surface of the Periodic Period of PUCCH transmission in slot _SCellBFR1 The method comprises the steps of carrying out a first treatment on the surface of the And slot Offset, SCellBFR1, of PUCCH transmission.

When the UE detects a beam failure in at least one of the scells configured as SCell beam failure recovery, the UE determines a positive indicator of the SCell beam failure event reporting request. Then, the UE transmits PUCCH in PUCCH resources configured in the configuration of the SCell beam failure event reporting request. If the UE does not detect a beam failure in any SCell configured for SCell beam failure recovery, the UE will not transmit in PUCCH resources configured in the configuration of SCell beam failure event reporting request.

If the PUCCH transmission occasion of the SCell beam failure event reporting request overlaps with another UCI transmission occasion, i.e., the PUCCH resource used by one SCell beam failure event reporting request transmission overlaps with at least one PUCCH resource used by another UCI transmission, the UE is requested to perform one or more of the following operations.

If the transmission opportunity of the PUCCH requested by the SCell beam failure event report overlaps with the SR transmission opportunity, the UE is requested to perform: the UE may discard the transmission of the SCell beam failure event reporting request; or the UE may discard the SR transmission.

If the SR transmission is associated with URLLC, the UE may discard the transmission of the SCell beam failure event reporting request. If the SR transmission is associated with eMBB, the UE will discard the SR transmission.

The UE multiplexes the bits of the SR with the bits of the SCell beam failure event reporting request. The value of each bit in the SR may represent a positive SR or a negative SR. The value of the SCell beam failure event reporting request may be positive or negative.

If the PUCCH transmission of the Scell beam failure event reporting request overlaps with the PUCCH of one or more CSI reports, the UE may perform the following operations: 1 bit representing a negative or positive SCell beam failure event reporting request is appended to the CSI reporting bit.

If the PUCCH transmission of the Scell beam failure event reporting request overlaps with the PUCCH of the HARQ-ACK information, the following operation is performed.

If the PUCCH for HARQ-ACK information is transmitted on PUCCH resources using PUCCH format 2 or format 3 or format 4, 1 bit representing a negative or positive SCell beam failure event reporting request is appended to the bits of HARQ-ACK information, and the UE transmits the combined bits on PUCCH resources using format 2 or format 3 or format 4, which is determined by the UE according to the size of UCI.

Note that in one example, the PUCCH configuration for the SCell beam failure event reporting request may be one specific SR configuration. In this case, the rule on how to multiplex HARQ-ACKs with SCell beam failure event reports may be the same as the rule on how to multiplex HARQ-ACKs with SRs.

In one example, the PUCCH of the first configuration for the SCell beam failure event reporting request may be configured as one specific SR configuration. The higher layer parameter schedulingRequestResourceConfig configures the UE with a set of K.gtoreq.1 SR configurations in PUCCH transmissions using either PUCCH format 0 or PUCCH format 1. The gNB may configure the UE to use one specific SR configuration as a configuration for the SCell beam failure event reporting request. The UE must not use the configuration of the SR to request UL-SCH resources for the new transmission. In one example, a UE is configured with a configuration ID: { SR ₁ ，SR ₂ ，…，SR _K A set of SR configurations. gNB configuration UE will have configuration ID SR ₁ Is configured for SCell beam failure event reporting requests. Then, the UE should perform toThe operation is carried out in a lower mode,

the UE will use the SR configuration { SR ₂ ，…，SR _K PUCCH resources configured in } to transmit an SR request to request UL-SCH resources for a new transmission.

The UE may configure SR using the SR ₁ The configured PUCCH resource in (a) transmits a positive indicator for an SCell beam failure event reporting request. Requesting the UE not to configure SR at SR ₁ And transmitting on the PUCCH resource configured in the step (2) and used for requesting the UL-SCH resource of the new transmission.

Two examples of RRC signaling design of the present method include a first example and a second example.

The first example is shown in table 3.

TABLE 3 Table 3

The parameter scellBFR-schedulingRequest indicates one SR configuration ID to configure a UE for an SCell Beam failure event reporting request

The second example is shown in table 4 below.

TABLE 4 Table 4

The parameter SCell-BFR configured in the SR configuration indicates whether this SR configuration applies to SCell beam failure event reporting requests.

In one method, the UE may be requested to report UCI for SCell beam failure recovery request. In the transmission of the UCI of the SCell beam failure recovery request, the UE may report the first indicator and the second indicator in the UCI of the SCell beam failure recovery request.

The first indicator indicates SCel that a beam failure was detected.

In one example, the first indicator may be a value of an ID of one SCell, i.e., SCellIndex configured for the SCell.

In one example, the UE is configured for beam failure recovery on 4 scells. The first indicator may be a 2-bit value. A value of 00 indicates the SCell having the lowest SCellIndex among all scells configured for beam failure recovery, and a value of 01 indicates the SCell having the next lowest SCellIndex among all scells configured for beam failure recovery. The benefit of this example is a reduction in UCI payload size.

In one example, the first indicator may be a bitmap, and each bit in the bitmap corresponds to one SCell configured for beam failure recovery. For example, the UE is configured for beam failure recovery on 4 scells, so the bitmap is b ₀ b ₁ b ₂ b ₃ . Bit b ₀ 、b ₁ 、b ₂ And b ₃ Corresponding to the SCell with the lowest, next lowest, third lowest, and maximum SCellIndex of all 4 scells configured for beam failure recovery.

If only one SCell is configured for beam failure recovery, the first indicator may be omitted in the UCI report.

The second indicator indicates CSI-RS resources or SS/PBCH in the candidate beam SR set configured for beam failure recovery of the SCell indicated by the first indicator.

In one example, if all scells configured for beam failure recovery are not configured with the set of candidate beams SR, the length of the second indicator is zero.

In one example, the number of bits in the second indicator may beWhere L represents a set of candidate beam RSs configured to all scells configured for beam failure recoveryMaximum number of RSs.

In one example, in a given UCI report, the number of bits in the second indicator may depend on the value of the first indicator. That is, the number of bits of the second indicator depends on SCellIndex reported in the same UCI. For example, in a given UCI report, the first indicator indicates that a beam failure occurs for an SCell with SCellIndex. Then the number of bits of the second indicator in the same UCI isWhere l denotes the number of RSs included in the set of candidate beam RSs configured for scells with SCellIndex.

In the method, the gNB may trigger the UE to report UCI of the SCell beam failure recovery request in PUSCH transmission.

The DCI format carries a field scell_link_recovery_request to trigger the UE to report UCI of the SCell beam failure Recovery Request in PUSCH transmission. The scell_link_recovery_request field may be 1 bit in length. If a bit in the scell_link_recovery_request field is set to zero, UCI of the SCell beam failure Recovery Request is not requested. If a bit in the scell_link_recovery_request field is set to 1, UCI requesting transmission of the SCell beam failure Recovery Request is requested.

If the DCI requests to transmit UCI of the SCell beam failure recovery request, the UE should multiplex UCI of the SCell beam failure recovery request in the scheduled PUSCH transmission.

A beta_offset value is defined for the UE to determine the number of resources for UCI for multiplexing SCell beam failure recovery requests in PUSCH transmissions.

In one example, for UCI of the SCell beam failure recovery request, the beta_offset value may be configured for the UE by higher layer parameters.

UCI for providing a UE with an SCell Beam failure recovery request on a PUSCH transmission by higher layer parametersValue, and UE is according to beta_offset and +.>The mapping between the values determines the beta_offset value.

In one example, the DCI triggering the UCI transmission of the SCell beam failure recovery request may include one beta_offset value for the UCI of the SCell beam failure recovery request.

In this example, the UE configures one or more beta_offset values for UCI of the SCell beam failure recovery request. The indicator field in the DCI indicates one of those configured beta_offset values that the UE will use to multiplex UCI of the SCell beam failure recovery request in PUSCH scheduled by the DCI.

In one example, a "beta_offset_indicator" field in DCI format 0_1 may be used to indicate one of UCI of SCell beam failure recovery requests multiplexed in PUSCH The value, then the UE is based on the beta_offse value and +.>The mapping between values determines the beta_offset value. beta_offset valueThe mapping of the values is as follows:

TABLE 5

UCI of the SCell beam failure recovery request is mapped to REs following the CSI part II mapped REs in the same PUSCH. UCI of the SCell beam failure recovery request is first mapped along the frequency domain and then mapped along the time domain.

In one method, the gNB may trigger the UE to report UCI of the SCell beam failure recovery request in PUCCH transmission.

The DCI format carries a field scell_link_recovery_request to trigger the UE to report UCI of the SCell beam failure Recovery Request in PUCCH transmission. A value of the field scell_link_recovery_request may indicate a configuration of one aperiodic report of UCI of the SCell beam failure Recovery Request configured by higher layer parameters.

The UE may be configured with a set of aperiodic reported configurations of UCI of the SCell beam failure recovery request by higher layer parameters. Each configuration contains the following information: an ID of PUCCH resource for UCI transmission, pucchId; slot offset, k for PUCCH transmission occasion _SCell 。

The UE is configured with a mapping between the value of the field scell_link_recovery_request and the configuration of the aperiodic report of UCI of the SCell beam failure Recovery Request. Table 6 below shows one example.

TABLE 6

Requesting the UE to request the UE in slot n+k if the UE detects DCI of UCI triggering the SCell beam failure recovery request at slot n _Scell UCI reporting SCell beam failure recovery in PUCCH transmission in PUCCH resource with pucchId. pucchId and k _SCell Is the ID and slot offset of the PUCCH resource configured in the configuration of the aperiodic report of UCI indicated in the field scell_link_recovery_request in the detected DCI.

In one example, if the UE receives DCI triggering UCI reporting SCell beam failure recovery, but the UE does not detect any SCell beam failure recovery, the UE may perform the following operations.

The UE reports an invalid combination of the value of the first indicator and the value of the second indicator for the SCell index. For example, the UE may report a value of a second indicator that is not a valid indicator for the CIS-RS or SS/PBCH block of the SCell indicated by the first indicator in the same UCI report.

The UE may set all bits in UCI to a special value, e.g., all bits are set to 1.

In this case, the bit value in the reported UCI should indicate to the gNB that no SCell beam failure event occurs.

In one embodiment, the UE may be configured to perform beam failure recovery on one or more scells. For each of the scells, the dedicated configured PUCCH resources are configured for the UE to report beam failure events for that SCell. For the first SCell, the UE is configured with dedicated configured PUCCH resources. Only when the UE detects a beam failure on the first SCell, the UE generates a positive indicator for the first SCell and then transmits PUCCH in PUCCH resources configured in a dedicated configuration for beam failure recovery of the first SCell.

Fig. 4 is a flowchart third of an SCell beam failure recovery method according to an embodiment of the present application, as shown in fig. 4, where the SCell beam failure recovery method includes the following steps 401 to 406.

Step 401: the serving gNB sends configuration information to the UE.

Here, the configuration information includes the following: configuration of beam failure recovery of the first Scell and the second Scell; PUCCH of the first configuration for the first Scell; and a PUCCH of a second configuration for a second Scell.

In step 403, the ue determines a beam failure event on the first Scell.

In step 404, the ue transmits a positive indicator on PUCCH resources configured by the first configured PUCCH.

In step 405, the ue determines a beam failure event on the second Scell.

In step 406, the ue transmits a positive indicator on PUCCH resources configured by the second configured PUCCH.

It should be noted that, steps 305 to 307 in the above-described scheme may be performed after step 406.

As shown in fig. 4, the serving gcb transmits configuration information for beam failure recovery to the UE, the configuration information including beam failure recovery configurations of the first Scell and the second Scell. The serving gNB configures a first configured PUCCH of the first SCell and a second configured PUCCH of the second SCell. Based on the configuration information, the UE measures a beam failure detection RS associated with the first SCell to detect a beam failure of the first SCell. If the UE determines a beam failure event on the first SCell, the UE transmits a positive indicator in PUCCH resources in a first configured PUCCH corresponding to beam failure recovery of the first SCell to indicate to the serving gNB that beam failure occurred in the first SCell. If the UE determines a beam failure event on the second SCell, the UE transmits a positive indicator in PUCCH resources in a second configured PUCCH corresponding to beam failure recovery of the second SCell to indicate to the serving gNB that beam failure occurred in the second SCell.

In one example, a PUCCH of a first configuration for first SCell beam failure recovery and a PUCCH of a second configuration for second SCell beam failure recovery may be implemented by a specific SR configuration. The UE is configured with a set of k≡1 SR configuration in PUCCH transmission using PUCCH format 0 or PUCCH format 1 by the higher layer parameter SchedulingRequestResourceConfig. The gNB may configure the UE to use a particular SR configuration as a first configuration for first SCell beam failure recovery and another particular SR configuration as a second configuration for second SCell beam failure recovery. With this configuration, the UE will not use both SR configurations to request UL-SCH resources for the new transmission. In one example, a UE is configured with a configuration ID: { SR ₁ ，SR ₂ ，…，SR _K A set of SR configurations. gNB configures the UE to configure ID as SR ₁ Is configured for first SCell beam failure recovery and the configuration ID is set as SR ₂ Is configured for second SCell beam failure recovery. Then, the UE should perform the following operations:

UE use in SR configuration { SR ₃ ，…，SR _K PUCCH resources configured in } to transmit an SR request for requesting UL-SCH resources for new transmission.

When the UE determines that the beam in the first SCell fails, the UE uses the configuration ID as SR ₁ Configured PUCCH resources are configured to send a positive indicator to the gNB. Requesting the UE not to configure ID as SR ₁ PUCCH resources configured for SR configuration of (2)A PUCCH for requesting UL-SCH resources for new transmission is transmitted in a source.

When the UE determines that the beam in the second SCell fails, the UE may use the configuration ID as SR ₂ The configured PUCCH resources of the SR configuration of (a) transmit a positive indicator to the gNB. Requesting the UE not to configure ID as SR ₂ A PUCCH for requesting a newly transmitted UL-SCH resource is transmitted from among the configured PUCCH resources by SR configuration of (a).

Two RRC signaling design examples for the present method include a first example and a second example.

The first example is shown in table 7.

TABLE 7

The parameter SCell-SR configures an association between the SR configuration ID and the SCell. The UE is configured to use an SR configuration associated with the Scell for beam failure recovery of the Scell.

The second example is shown in table 8.

TABLE 8

The parameter SCell-BFR configured by the SR configuration indicates the SCell associated with the SR configuration, and the UE will use the SR configuration associated with the SCell for beam failure recovery of the SCell.

The method of Scell Beam Failure Recovery (BFR) based on the physical layer is presented in the above scheme according to an embodiment of the present application. The application discloses the method. The information of the Scell beam failure includes an index satisfying the beam failure and an index of a new beam, and the information is reported as a new UCI format.

Fig. 5 is a schematic block diagram of an SCell beam failure recovery apparatus provided in an embodiment of the present application. The SCell beam failure recovery apparatus is applied to a UE, and as shown in fig. 5, the SCell beam failure recovery apparatus includes a detection unit 501, a transmission unit 502, and a reception unit 503.

The detecting unit 501 is configured to detect that at least one SCell fails in a beam.

The sending unit 502 is configured to send at least one indication information to the network device, where the at least one indication information is used to indicate that the at least one SCell fails in a beam.

The receiving unit 503 is configured to receive DCI sent by a network device, where the DCI is used to request the UE to report a first UCI on a first physical channel.

The sending unit 502 is further configured to report a first UCI to a network device on the first physical channel, where the first UCI carries first indication information and/or second indication information. The first indication information is used to indicate an index of each SCell of the at least one SCell, and the second indication information is used to indicate an index of a new RS associated with each SCell of the at least one SCell.

In an alternative manner, the receiving unit 503 is further configured to receive the first configuration information sent by the network device. The first configuration information is used for determining PUCCH configuration corresponding to the first PUCCH resource.

The sending unit 502 is configured to send third indication information to a network device on the first PUCCH resource based on the first configuration information. The third indication information is used for indicating that the at least one SCell fails in a beam.

In an alternative, the at least one SCell comprises a first SCell and a second SCell.

The receiving unit 503 is further configured to receive first configuration information and second configuration information sent by the network device, where the first configuration information is used to determine PUCCH configuration corresponding to the first PUCCH resource, and the second configuration information is used to determine PUCCH configuration corresponding to the second PUCCH resource.

The sending unit 502 is configured to send third indication information to a network device on the first PUCCH resource based on the first configuration information, and send fourth indication information to the network device on the second PUCCH resource based on the second configuration information. The third indication information is used for indicating the first SCell to generate beam failure, and the fourth indication information is used for indicating the second SCell to generate beam failure.

In an alternative manner, the PUCCH configuration includes at least one of the following information: the identification of the PUCCH resource, the period of the PUCCH resource, the offset of the PUCCH resource within one period, the index of the first resource unit of the PUCCH resource within one period.

In an alternative manner, the PUCCH configuration is determined based on a specific SR configuration, where the specific SR configuration refers to an SR configuration for the SCell beam failure event reporting request.

In an alternative manner, the receiving unit 503 is further configured to receive third configuration information sent by the network device, where the third configuration information is used to determine at least one SCell configuration.

The detecting unit 501 is configured to detect whether a beam failure occurs for each SCell in the at least one SCell based on the at least one SCell configuration.

In an alternative manner, each SCell configuration includes at least one of the following information: configuration information of the beam failure detection RS, configuration information of the new beam identification RS set, threshold information for identifying the new RS.

In an alternative manner, the first UCI refers to UCI of an SCell beam failure recovery request; or, the first UCI refers to UCI of an SCell link recovery request.

In an alternative manner, the sending unit 502 is configured to send the first UCI to a network device through PUCCH based on the fifth indication information.

In an alternative manner, the DCI carries fifth indication information, where the fifth indication information is used to schedule transmission of the first physical channel, and the first physical channel belongs to PUSCH.

In an alternative manner, the sending unit 502 is configured to send the first UCI to a network device through the PUSCH based on the fifth indication information.

In an alternative manner, the at least one indication message is sent in a time slot n, where n is a positive integer.

The receiving unit 503 is configured to receive DCI sent by a network device in a time window, where a starting time slot of the time window is a time slot n+1.

In an alternative manner, if the receiving unit 503 does not receive DCI transmitted by the network device within the time window, the transmitting unit 502 retransmits the at least one indication information to the network device.

Those skilled in the art will understand that the above description of the SCell beam failure recovery apparatus according to the embodiment of the present application may be understood with reference to the description of the SCell beam failure recovery method according to the embodiment of the present application.

Fig. 6 is a schematic diagram ii of the structural composition of an SCell beam failure recovery apparatus provided by the embodiment of the present application, where the SCell beam failure recovery apparatus is applied to a network device, and as shown in fig. 6, the SCell beam failure recovery apparatus includes a receiving unit 601 and a transmitting unit 602.

The receiving unit 601 is configured to receive at least one indication information sent by a UE, where the at least one indication information is used to indicate that the at least one SCell fails in a beam.

The sending unit 602 is configured to send DCI to the UE, where the DCI is configured to request the UE to report a first UCI on a first physical channel.

The receiving unit 601 is further configured to receive a first UCI reported by the UE on the first physical channel, where the first UCI carries first indication information and/or second indication information, the first indication information is used to indicate an index of each SCell in the at least one SCell, and the second indication information is used to indicate an index of a new RS associated with each SCell in the at least one SCell.

In an optional manner, the sending unit 602 is further configured to send first configuration information to the UE, where the first configuration information is used to determine a PUCCH configuration corresponding to the first PUCCH resource.

The receiving unit 601 is configured to receive third indication information sent by the UE on the first PUCCH resource, where the third indication information is used to indicate that the at least one SCell fails in a beam.

In an alternative manner, the at least one SCell comprises a first SCell and a second SCell;

The sending unit 602 is further configured to send first configuration information and second configuration information to the UE, where the first configuration information is used to determine a PUCCH configuration corresponding to the first PUCCH resource, and the second configuration information is used to determine a PUCCH configuration corresponding to the second PUCCH resource.

The receiving unit 601 is configured to receive third indication information sent by the UE on the first PUCCH resource and fourth indication information sent by the UE on the second PUCCH resource. The third indication information is used for indicating the first SCell to generate beam failure, and the fourth indication information is used for indicating the second SCell to generate beam failure.

In an alternative manner, the sending unit 602 is further configured to send third configuration information to the UE, where the third configuration information is used to determine at least one SCell configuration.

The third configuration information is used for the UE to detect whether each SCell in the at least one SCell fails in a beam.

In an optional manner, the receiving unit 601 is configured to receive a first UCI sent by the UE on the PUCCH resource.

In an optional manner, the receiving unit 601 is configured to receive a first UCI sent by the UE on the PUSCH resource.

Fig. 7 is a schematic block diagram of a communication device 700 according to an embodiment of the present application. The communication device may be a UE or a network device, and the communication device 700 shown in fig. 7 includes a processor 710, where the processor 710 may call and execute a computer program from a memory to implement the method according to the embodiments of the present application.

Optionally, as shown in fig. 7, the communication device 700 may further comprise a memory 720. Wherein the processor 710 may call and run a computer program from the memory 720 to implement the method in an embodiment of the application.

Wherein the memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.

Optionally, as shown in fig. 7, the communication device 700 may further include a transceiver 730, and the processor 710 may control the transceiver 730 to communicate with other devices, and in particular, may send information or data to other devices or receive information or data sent by other devices.

Among other things, transceiver 730 may include a transmitter and a receiver. Transceiver 730 may further include antennas, the number of which may be one or more.

Optionally, the communication device 700 may be specifically a network device according to an embodiment of the present application, and the communication device 700 may implement a corresponding flow implemented by the network device in each method according to an embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 700 may be specifically a mobile terminal/UE according to an embodiment of the present application, and the communication device 700 may implement a corresponding flow implemented by the mobile terminal/UE in each method according to the embodiment of the present application, which is not described herein for brevity.

Fig. 8 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 800 shown in fig. 8 includes a processor 810, and the processor 810 may call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 8, chip 800 may also include memory 820. Wherein the processor 810 may call and run a computer program from the memory 820 to implement the method in embodiments of the present application.

Wherein the memory 820 may be a separate device from the processor 810 or may be integrated into the processor 810.

Optionally, the chip 800 may also include an input interface 830. The processor 810 may control the input interface 830 to communicate with other devices or chips, and in particular, may obtain information or data sent by other devices or chips.

Optionally, the chip 800 may further include an output interface 840. The processor 810 may control the output interface 840 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the chip may be applied to the mobile terminal/UE in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the mobile terminal/UE in each method in the embodiment of the present application, which is not described herein for brevity.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

Fig. 9 is a schematic block diagram of a communication system 900 provided by an embodiment of the present application. As shown in fig. 9, the communication system 900 includes a UE 910 and a network device 920.

The UE 910 may be configured to implement the corresponding functions implemented by the UE in the above method, and the network device 920 may be configured to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be Read Only Memory (ROM), programmable Read Only Memory (PROM), erasable Programmable Read Only Memory (EPROM), electrically Erasable Programmable Read Only Memory (EEPROM), or flash memory, among others. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced Synchronous Dynamic Random Access Memory (ESDRAM), synchronous Link Dynamic Random Access Memory (SLDRAM), and direct memory bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is illustrative but not limiting, and for example, the memory in the embodiments of the present application may be Static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced Synchronous Dynamic Random Access Memory (ESDRAM), synchronous Link Dynamic Random Access Memory (SLDRAM), direct memory bus random access memory (DR RAM), etc. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a network device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a mobile terminal/UE in the embodiment of the present application, and the computer program causes a computer to execute corresponding processes implemented by the mobile terminal/UE in each method in the embodiment of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to a network device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the network device in each method in the embodiment of the present application, which are not described herein for brevity.

Optionally, the computer program product may be applied to a mobile terminal/UE in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/UE in each method in the embodiment of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to the mobile terminal/UE in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute corresponding processes implemented by the mobile terminal/UE in each method in the embodiment of the present application, which is not described herein for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a read-only memory (ROM), a random-access memory (RAM), a magnetic disk, or an optical disk, etc.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A second cell (SCell) beam failure recovery method, the method comprising:

user Equipment (UE) detects that at least one SCell fails in a beam, and sends at least one indication message to network equipment, where the at least one indication message is used to indicate the at least one SCell fails in a beam;

the UE receives Downlink Control Information (DCI) sent by the network equipment, so as to request the UE to report first Uplink Control Information (UCI) on a first physical channel; wherein, the first UCI is UCI of an SCell beam failure recovery request; or, the first UCI is UCI of an SCell link recovery request; and

the UE reports the first UCI to the network device on the first physical channel, where the first UCI carries at least one of first indication information or second indication information, where the first indication information is used to indicate an index of each SCell in the at least one SCell, and the second indication information is used to indicate an index of a new Reference Signal (RS) of each SCell in the at least one SCell.

2. The method of claim 1, wherein the method further comprises:

the UE receives first configuration information sent by network equipment, wherein the first configuration information is used for determining Physical Uplink Control Channel (PUCCH) configuration corresponding to PUCCH resources; and

The UE sending at least one indication information to a network device, comprising: the UE sends third indication information to the network equipment on the first PUCCH resource based on the first configuration information, wherein the third indication information is used for indicating the at least one SCell to generate beam failure.

3. The method of claim 1, wherein the at least one SCell comprises a first SCell and a second SCell,

the method further comprises the steps of: the UE receives first configuration information and second configuration information sent by the network equipment, wherein the first configuration information is used for determining Physical Uplink Control Channel (PUCCH) configuration corresponding to PUCCH resources, and the second configuration information is used for determining PUCCH configuration corresponding to second PUCCH resources;

the UE sending the at least one indication information to the network device, including: the UE sends third indication information to the network equipment on the first PUCCH resource based on the first configuration information, and sends fourth indication information to the network equipment on the second PUCCH resource based on the second configuration information, wherein the third indication information is used for indicating the first SCell to generate beam failure, and the fourth indication information is used for indicating the second SCell to generate beam failure.

4. A method according to claim 2 or 3, wherein the PUCCH configuration comprises at least one of the following information: the identification of the PUCCH resource, the period of the PUCCH resource, the offset of the PUCCH resource within one period, the index of the first resource unit of the PUCCH resource within one period.

5. A method according to claim 2 or 3, wherein the PUCCH configuration is determined based on a specific SR configuration, the specific SR configuration referring to an SR configuration for an SCell beam failure event reporting request.

6. The method of any one of claims 1 to 5, further comprising:

the UE receives third configuration information sent by the network equipment, wherein the third configuration information is used for determining at least one SCell configuration; and

the UE detects whether a beam failure occurs for each of the at least one SCell based on the at least one SCell configuration.

7. The method of claim 6, wherein the each SCell configuration comprises at least one of: configuration information of the beam failure detection RS, configuration information of the new beam identification RS set, threshold information for identifying the new RS.

8. The method of any of claims 1-7, wherein the DCI carries fifth indication information indicating the first physical channel, the first physical channel belonging to a Physical Uplink Control Channel (PUCCH).

9. The method of claim 8, wherein the UE reporting the first UCI to the network device on the first physical channel comprises: the UE transmits the first UCI to the network device over the PUCCH based on the fifth indication information.

10. The method of any of claims 1-7, wherein the DCI carries fifth indication information for scheduling transmission of the first physical channel, the first physical channel belonging to a Physical Uplink Shared Channel (PUSCH).

11. The method of claim 10, wherein the UE reporting the first UCI to the network device on the first physical channel comprises: the UE sends the first UCI to the network equipment through the PUSCH based on the fifth indication information.

12. The method of any one of claims 1 to 11, wherein the at least one indication information is transmitted in a time slot n, n being a positive integer;

the UE receiving the DCI transmitted by the network device includes: and the UE receives the DCI sent by the network equipment in a time window, wherein the starting time slot of the time window is a time slot n+1.

13. The method of claim 12, further comprising:

and when the UE does not receive the DCI transmitted by the network equipment in the time window, the UE retransmits the at least one indication information to the network equipment.

14. A second cell (SCell) beam failure recovery method, comprising:

the method comprises the steps that network equipment receives at least one piece of indication information sent by User Equipment (UE), wherein the at least one piece of indication information is used for indicating the at least one SCell to generate beam failure;

the network device sends Downlink Control Information (DCI) to the UE to request the UE to report first Uplink Control Information (UCI) on a first physical channel; wherein, the first UCI is UCI of an SCell beam failure recovery request; or, the first UCI is UCI of an SCell link recovery request; and

the network device receives a first UCI reported by the UE on the first physical channel, where the first UCI carries at least one of first indication information or second indication information, where the first indication information is used to indicate an index of each SCell in the at least one SCell, and the second indication information is used to indicate an index of a new Reference Signal (RS) of each SCell in the at least one SCell.

15. The method of claim 14, further comprising:

the network device sends first configuration information to the UE, wherein the first configuration information is used for determining Physical Uplink Control Channel (PUCCH) configuration corresponding to PUCCH resources;

the network device receiving at least one indication message sent by the UE includes: the network device receives third indication information sent by the UE on the first PUCCH resource, where the third indication information is used to indicate that the at least one SCell fails in a beam.

16. The method of claim 14, wherein the at least one SCell comprises a first SCell and a second SCell,

the method further comprises the steps of: the network device sends first configuration information and second configuration information to the UE, the first configuration information being used to determine a Physical Uplink Control Channel (PUCCH) configuration corresponding to a first PUCCH resource, the second configuration information being used to determine a PUCCH configuration corresponding to a second PUCCH resource, and

the network device receiving at least one indication message sent by the UE includes: the network device receives third indication information sent by the UE on the first PUCCH resource, and the network device receives fourth indication information sent by the UE on the second PUCCH resource, where the third indication information is used to indicate that the first SCell fails in a beam, and the fourth indication information is used to indicate that the second SCell fails in a beam.

17. The method of claim 15 or 16, wherein the PUCCH configuration includes at least one of the following information: the identification of the PUCCH resource, the period of the PUCCH resource, the offset of the PUCCH resource within one period, the index of the first resource unit of the PUCCH resource within one period.

18. The method of claim 15 or 16, wherein the PUCCH configuration is determined based on a specific SR configuration, the specific SR configuration being an SR configuration for an SCell beam failure event reporting request.

19. The method of any of claims 14 to 18, further comprising:

the network device sends third configuration information to the UE, the third configuration information being used to determine at least one SCell configuration,

the third configuration information is used for detecting whether each SCell in the at least one SCell has beam failure or not by the UE.

20. The method of claim 19, wherein the each SCell configuration comprises at least one of: configuration information of the beam failure detection RS, configuration information of the new beam identification RS set, threshold information for identifying the new RS.

21. The method of any of claims 14-20, wherein the DCI carries fifth indication information indicating the first physical channel, the first physical channel belonging to a Physical Uplink Control Channel (PUCCH).

22. The method of claim 21, wherein the network device receiving the first UCI reported by the UE on the first physical channel comprises: the network equipment receives the first UCI sent by the UE on the PUCCH.

23. The method of any of claims 14-21, wherein the DCI carries fifth indication information for scheduling transmission of the first physical channel, the first physical channel belonging to a Physical Uplink Shared Channel (PUSCH).

24. The method of claim 23, wherein the network device receiving the first UCI reported by the UE on the first physical channel comprises: and the network equipment receives the first UCI sent by the UE on the PUSCH.

25. A second cell (SCell) beam failure recovery apparatus for use with a User Equipment (UE), the apparatus comprising:

a detection unit, configured to detect that at least one SCell fails in a beam;

a sending unit, configured to send at least one indication information to a network device, where the at least one indication information is used to indicate that the at least one SCell fails in a beam; and

a receiving unit, configured to receive Downlink Control Information (DCI) sent by the network device, so as to request the UE to report first Uplink Control Information (UCI) on a first physical channel, where the first UCI is UCI of an SCell beam failure recovery request; or, the first UCI is UCI of an SCell link recovery request;

The sending unit is further configured to report a first UCI to the network device on the first physical channel, where the first UCI carries at least one of first indication information or second indication information, where the first indication information is used to indicate an index of each SCell in the at least one SCell, and the second indication information is used to indicate an index of a new Reference Signal (RS) of each SCell in the at least one SCell.

26. The apparatus of claim 25, wherein,

the receiving unit is further configured to receive first configuration information sent by the network device, where the first configuration information is used to determine a Physical Uplink Control Channel (PUCCH) configuration corresponding to a PUCCH resource;

the sending unit is configured to send third indication information to a network device on the first PUCCH resource based on the first configuration information, where the third indication information is used to indicate that the at least one SCell fails in a beam.

27. The apparatus of claim 25, wherein the at least one SCell comprises a first SCell and a second SCell,

the receiving unit is further configured to receive first configuration information and second configuration information sent by the network device, where the first configuration information is used to determine a Physical Uplink Control Channel (PUCCH) configuration corresponding to a first PUCCH resource, and the second configuration information is used to determine a PUCCH configuration corresponding to a second PUCCH resource;

The sending unit is configured to send third indication information to the network device on the first PUCCH resource based on the first configuration information, and send fourth indication information to the network device on the second PUCCH resource based on the second configuration information, where the third indication information is used to indicate that the first SCell fails in a beam, and the fourth indication information is used to indicate that the second SCell fails in a beam.

28. The apparatus of claim 26 or 27, wherein the PUCCH configuration comprises at least one of the following information: the identification of the PUCCH resource, the period of the PUCCH resource, the offset of the PUCCH resource within one period, the index of the first resource unit of the PUCCH resource within one period.

29. The apparatus of claim 26 or 27, wherein the PUCCH configuration is determined based on a specific SR configuration, the specific SR configuration being an SR configuration for an SCell beam failure event reporting request.

30. The apparatus of any one of claims 25 to 29, wherein,

the receiving unit is further configured to receive third configuration information sent by the network device, where the third configuration information is used to determine at least one SCell configuration; and is also provided with

The detecting unit is configured to detect whether each SCell in the at least one SCell has a beam failure based on the at least one SCell configuration.

31. The apparatus of claim 30, wherein the each SCell configuration comprises at least one of: configuration information of the beam failure detection RS, configuration information of the new beam identification RS set, threshold information for identifying the new RS.

32. The apparatus of any one of claims 25-31, wherein the DCI carries fifth indication information indicating the first physical channel, the first physical channel belonging to a Physical Uplink Control Channel (PUCCH).

33. The apparatus of claim 32, wherein the means for transmitting is configured to transmit the first UCI to the network device over the PUCCH based on the fifth indication information.

34. The apparatus of any of claims 25-31, wherein the DCI carries fifth indication information for scheduling transmission of the first physical channel, the first physical channel belonging to a Physical Uplink Shared Channel (PUSCH).

35. The apparatus of claim 34, wherein the means for transmitting is configured to transmit the first UCI to the network device over the PUSCH based on the fifth indication information.

36. The apparatus of any one of claims 25 to 35, wherein the at least one indication information is transmitted in a time slot n, n being a positive integer;

the receiving unit is configured to receive DCI sent by the network device in a time window, where a starting time slot of the time window is a time slot n+1.

37. The apparatus of claim 36, wherein the transmitting unit retransmits the at least one indication information to a network device if the receiving unit does not receive the DCI transmitted by the network device within the time window.

38. A second cell (SCell) beam failure recovery apparatus for use with a network device, the apparatus comprising:

a receiving unit, configured to receive at least one indication information sent by a User Equipment (UE), where the at least one indication information is used to indicate that the at least one SCell fails in a beam; and

a sending unit, configured to send Downlink Control Information (DCI) to the UE, so as to request the UE to report first Uplink Control Information (UCI) on a first physical channel, where the first UCI is UCI of an SCell beam failure recovery request; or, the first UCI is UCI of an SCell link recovery request;

The receiving unit is further configured to receive a first UCI reported by the UE on the first physical channel, where the first UCI carries at least one of first indication information or second indication information, where the first indication information is used to indicate an index of each SCell in the at least one SCell, and the second indication information is used to indicate an index of a new Reference Signal (RS) of each SCell in the at least one SCell.

39. The apparatus of claim 38, wherein,

the sending unit is further configured to send first configuration information to the UE, where the first configuration information is used to determine a Physical Uplink Control Channel (PUCCH) configuration corresponding to a PUCCH resource; and

the receiving unit is configured to receive third indication information sent by the UE on the first PUCCH resource, where the third indication information is used to indicate that the at least one SCell fails in a beam.

40. The apparatus of claim 38, wherein the at least one SCell comprises a first SCell and a second SCell,

the sending unit is further configured to send first configuration information and second configuration information to the UE, where the first configuration information is used to determine a Physical Uplink Control Channel (PUCCH) configuration corresponding to a first PUCCH resource, and the second configuration information is used to determine a PUCCH configuration corresponding to a second PUCCH resource; and

The receiving unit is configured to receive third indication information sent by the UE on the first PUCCH resource, and fourth indication information sent by the UE on the second PUCCH resource, where the third indication information is used to indicate that the first SCell fails in a beam, and the fourth indication information is used to indicate that the second SCell fails in a beam.

41. The apparatus of claim 39 or 40, wherein the PUCCH configuration comprises at least one of the following information: the identification of the PUCCH resource, the period of the PUCCH resource, the offset of the PUCCH resource within one period, the index of the first resource unit of the PUCCH resource within one period.

42. The apparatus of claim 39 or 40, wherein the PUCCH configuration is determined based on a specific SR configuration, the specific SR configuration being an SR configuration for an SCell beam failure event reporting request.

43. The apparatus of any one of claims 38 to 42, wherein the transmitting unit is further configured to transmit third configuration information to the UE, the third configuration information being used to determine at least one SCell configuration,

44. The apparatus of claim 43, wherein each SCell configuration comprises at least one of: configuration information of the beam failure detection RS, configuration information of the new beam identification RS set, threshold information for identifying the new RS.

45. The apparatus of any one of claims 38 to 44, wherein the DCI carries fifth indication information indicating the first physical channel, the first physical channel belonging to a Physical Uplink Control Channel (PUCCH).

46. The apparatus of claim 45, wherein the receiving unit is configured to receive the first UCI sent by the UE on the PUCCH resource.

47. The apparatus of any one of claims 38 to 44, wherein the DCI carries fifth indication information for scheduling transmission of the first physical channel, the first physical channel belonging to a Physical Uplink Shared Channel (PUSCH).

48. The apparatus of claim 47, wherein the means for receiving is configured to receive the first UCI transmitted by the UE on the PUSCH resource.

49. A User Equipment (UE), comprising: a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory, performing the method of any of claims 1 to 13.

50. A network device, comprising: a processor and a memory for storing a computer program, the processor for invoking and running the computer program stored in the memory to perform the method of any of claims 14 to 24.

51. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 13.

52. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 14 to 24.

53. A computer readable storage medium storing a computer program which, when executed by a computer, causes the computer to perform the method of any one of claims 1 to 13.

54. A computer readable storage medium storing a computer program which, when executed by a computer, causes the computer to perform the method of any one of claims 14 to 24.