A method and apparatus for transmitting a beam failure recovery request

Abstract

The application discloses a method and device for sending a beam failure recovery request, relates to the field of communication, and solves the problem of long beam failure recovery time delay. The method comprises the following steps: selecting a specific PUSCH resource, and sending at least one beam failure recovery request on the PUSCH resource. Alternatively, at least two beam failure recovery requests are sent on any PUSCH resource. Therefore, by limiting the PUSCH resource of the MAC-CE transmission or by sending multiple same MAC-CEs, the transmission reliability is improved, and the beam failure recovery time delay is reduced.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a method and apparatus for sending a beam failure recovery request. Background Technology

[0002] To cope with the explosive growth of mobile data traffic, massive mobile communication device connections, and the continuous emergence of various new services and application scenarios, the fifth generation (5G) mobile communication system was developed. The 5G mobile communication system is also known as the new radio access technology (NR) system.

[0003] In NR systems, a beamforming-based signal transmission mechanism is introduced. This mechanism increases antenna gain to enhance signal transmission power, thereby compensating for path loss during high-frequency wireless signal transmission between network and terminal devices. However, due to the poor diffraction capability of wireless signals in high-frequency channels, transmission may be blocked. To prevent sudden communication interruptions caused by blocked signals, terminal devices can measure the communication quality of the beam failure detection reference signal (BFD RS) configured by the network device to determine if a beam failure has occurred. When a beam failure is detected by the terminal device, it sends a beam failure recovery request (BFRQ) to the network device on any Physical Uplink Shared Channel (PUSCH) to restore the failed link. If the BFRQ transmission fails, the terminal device needs to retransmit the BFRQ to ensure successful transmission, thus increasing the beam failure recovery delay. Summary of the Invention

[0004] This application provides a method and apparatus for sending beam failure recovery requests, which solves the problem of long beam failure recovery delay.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] Firstly, this application provides a method for transmitting beam failure recovery requests. This method can be applied to a terminal device, or to a communication device that supports the implementation of the method in the terminal device, such as a chip system. The method includes: first determining a first resource, and then transmitting N BFRQs on the first resource, where N is an integer greater than or equal to 1. The method for transmitting beam failure recovery requests provided by this application improves transmission reliability and reduces beam failure recovery latency by limiting the PUSCH resources used for BFRQ transmission or by transmitting multiple identical BFRQs.

[0007] Secondly, this application provides a method for receiving beam failure recovery requests. This method can be applied to a network device, or to a communication device that supports the implementation of the method in the network device, such as a chip system. The method includes: first determining a first resource, and then receiving N BFRQs on the first resource, where N is an integer greater than or equal to 1. The method for receiving beam failure recovery requests provided by this application improves transmission reliability and reduces beam failure recovery latency by limiting the PUSCH resources used for BFRQ transmission or by receiving multiple identical BFRQs.

[0008] In one possible implementation, determining the first resource includes: determining the first resource based on a beam failure instance counter, wherein the beam failure instance counter of the cell to which the first resource belongs is 0. When the beam failure instance counter is 0, it indicates that no beam failure has occurred in the cell or cell group, and the link quality of the cell or cell group is good. Therefore, the terminal device can select the resource of the cell with a beam failure instance counter of 0 as the first resource.

[0009] In another possible implementation, determining the first resource includes: determining the first resource based on the subcarrier spacing, where the first resource has the largest subcarrier spacing among the K resources, where K is an integer, K≥1. Since a larger subcarrier spacing results in a shorter OFDM symbol length, the resource with the largest subcarrier spacing can complete transmission faster. Therefore, the terminal device can select the resource with the largest subcarrier spacing among the K resources as the first resource to complete the beam failure request transmission more quickly.

[0010] In another possible implementation, determining the first resource includes: identifying the first resource based on a duplication identifier, wherein the first resource is configured with a duplication identifier. This duplication identifier indicates that the resource can be used to repeatedly transmit multiple identical pieces of information. Alternatively, resources carrying duplication identifiers have higher transmission reliability, or resources carrying duplication identifiers can be used for URLLC service transmission, and the resources allocated for this service need to guarantee highly reliable and low-latency transmission. Therefore, transmitting beam failure requests on resources carrying duplication identifiers can ensure the reliability of beam failure request transmission, complete beam failure recovery in a timely manner, and reduce beam failure recovery latency.

[0011] In another possible implementation, determining the first resource includes: determining the first resource based on a modulation and coding scheme, wherein the modulation and coding scheme corresponding to the first resource is the smallest among the modulation and coding schemes corresponding to L resources, where L is an integer and L≥1. Because a smaller modulation and coding scheme will employ a low-order modulation scheme and a low-rate channel coding scheme to ensure communication quality, selecting a smaller modulation and coding scheme can ensure the transmission reliability of beam failure recovery requests, thereby avoiding retransmission of beam failure recovery requests and reducing beam failure recovery latency. Optionally, the modulation and coding scheme corresponding to the first resource may refer to the modulation and coding scheme indicated by the indication information of the first resource.

[0012] In another possible implementation, N is predefined or configured.

[0013] In another possible implementation, N is determined based on the modulation and coding scheme (MCS).

[0014] In another possible implementation, N is determined based on the MCS, including: when the MCS is greater than or equal to a preset threshold, N = P; when the MCS is less than the preset threshold, N = Q; where P and Q are both integers, P ≥ 0, Q ≥ 0, and P ≥ Q.

[0015] In another possible implementation, when N>1, the N beam failure recovery requests are encoded independently. By repeatedly sending multiple beam failure recovery requests, the reliability of beam failure recovery request transmission is improved.

[0016] In another possible implementation, when N>1, the N beam failure recovery requests are the same.

[0017] Thirdly, this application provides a method for transmitting beam failure recovery requests. This method can be applied to a terminal device, or to a communication device that supports the implementation of this method in the terminal device, such as a chip system. The method includes: transmitting N BFRQs on a first resource, where N is an integer and N≥2; and receiving beam failure recovery response information (which can be simply referred to as Beam Failure Recovery Response, BFRR). The method for transmitting beam failure recovery requests provided by this application improves transmission reliability and reduces beam failure recovery latency by transmitting multiple identical BFRQs.

[0018] Fourthly, this application provides a method for receiving beam failure recovery requests. This method can be applied to a network device, or to a communication device that supports the implementation of this method in a network device, such as a chip system. The method includes: receiving N BFRQs on a first resource, where N is an integer and N≥2; and transmitting a BFRR. The method for receiving beam failure recovery requests provided by this application improves transmission reliability and reduces beam failure recovery latency by receiving multiple identical BFRQs.

[0019] In one possible implementation, when N>1, the N beam failure recovery requests are encoded independently, and the N beam failure recovery requests are identical.

[0020] Fifthly, this application also provides a communication apparatus for implementing the method described in the first aspect. The communication apparatus is a terminal device or a communication apparatus that supports the implementation of the method described in the first aspect by a terminal device; for example, the communication apparatus includes a chip system. For example, the communication apparatus includes a processing unit and a transmitting unit. The processing unit is used to determine a first resource; the transmitting unit is used to transmit N BFRQs on the first resource, where N is an integer and N≥1.

[0021] Alternatively, the specific methods are the same as those described in the first aspect, and will not be repeated here.

[0022] Sixthly, this application also provides a communication apparatus for implementing the method described in the second aspect above. The communication apparatus is a network device or a communication apparatus that supports the implementation of the method described in the second aspect by a network device; for example, the communication apparatus includes a chip system. For example, the communication apparatus includes a processing unit and a receiving unit. The processing unit is configured to determine a first resource. The receiving unit is configured to receive N BFRQs on the first resource, where N is an integer greater than or equal to 1.

[0023] Alternatively, the specific methods are the same as those described in the second aspect, and will not be repeated here.

[0024] In a seventh aspect, this application also provides a communication apparatus for implementing the method described in the third aspect above. The communication apparatus is a terminal device or a communication apparatus that supports the implementation of the method described in the third aspect by a terminal device, for example, the communication apparatus includes a chip system. For example, the communication apparatus includes: a transmitting unit and a receiving unit. The transmitting unit is used to transmit N BFRQs on a first resource, where N is an integer and N≥2; the receiving unit is used to receive BFRRs.

[0025] Alternatively, the specific methods are the same as those described in the third aspect, and will not be repeated here.

[0026] Eighthly, this application also provides a communication apparatus for implementing the method described in the fourth aspect above. The communication apparatus is a network device or a communication apparatus that supports a network device in implementing the method described in the fourth aspect, for example, the communication apparatus includes a chip system. For example, the communication apparatus includes: a receiving unit and a transmitting unit. The receiving unit is configured to receive N BFRQs on a first resource, where N is an integer and N≥2; the transmitting unit is configured to transmit BFRRs.

[0027] Alternatively, the specific methods are the same as those described in the fourth aspect, and will not be repeated here.

[0028] It should be noted that the functional modules of aspects five and eight above can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. For example, a transceiver performs the functions of a receiving unit and a transmitting unit; a processor performs the functions of a processing unit; and a memory contains program instructions for the processor to process the methods of this application. The processor, transceiver, and memory are connected via a bus and communicate with each other. Specifically, the functions of the terminal device or network device described in aspects one through four can be referred to.

[0029] Ninthly, this application also provides a communication device for implementing the method described in the first aspect. The communication device is a terminal device or a communication device that supports a terminal device in implementing the method described in the first aspect, for example, the communication device includes a chip system. For example, the communication device includes a processor for implementing the functions of the method described in the first aspect. The communication device may also include a memory for storing program instructions and data. The memory is coupled to the processor, and the processor can call and execute the program instructions stored in the memory to implement the functions of the method described in the first aspect. The communication device may also include a communication interface for communicating with other devices. For example, if the communication device is a terminal device, the other device is a network device.

[0030] Optionally, the specific method for sending beam failure recovery requests is the same as described in the first aspect, and will not be repeated here.

[0031] In a tenth aspect, this application also provides a communication device for implementing the method described in the second aspect above. The communication device is a network device or a communication device that supports a network device in implementing the method described in the second aspect, such as a chip system included in the communication device. For example, the communication device includes a processor for implementing the functions in the method described in the second aspect above. The communication device may also include a memory for storing program instructions and data. The memory is coupled to the processor, and the processor can call and execute the program instructions stored in the memory to implement the functions in the method described in the second aspect above. The communication device may also include a communication interface for communicating with other devices. For example, if the communication device is a network device, the other device is a terminal device.

[0032] Optionally, the specific method for receiving beam failure recovery requests is the same as described in the second aspect, and will not be repeated here.

[0033] Eleventhly, this application also provides a communication device for implementing the method described in the third aspect above. The communication device is a terminal device or a communication device that supports a terminal device in implementing the method described in the third aspect, for example, the communication device includes a chip system. For example, the communication device includes a processor for implementing the functions of the method described in the third aspect above. The communication device may also include a memory for storing program instructions and data. The memory is coupled to the processor, and the processor can call and execute the program instructions stored in the memory to implement the functions of the method described in the third aspect above. The communication device may also include a communication interface for communicating with other devices. For example, if the communication device is a terminal device, the other device is a network device.

[0034] Optionally, the specific method for sending beam failure recovery requests is the same as described in the corresponding section of the third aspect, and will not be repeated here.

[0035] In a twelfth aspect, this application also provides a communication device for implementing the method described in the fourth aspect above. The communication device is a network device or a communication device that supports a network device in implementing the method described in the fourth aspect, such as a chip system included in the communication device. For example, the communication device includes a processor for implementing the functions in the method described in the fourth aspect above. The communication device may also include a memory for storing program instructions and data. The memory is coupled to the processor, and the processor can call and execute the program instructions stored in the memory to implement the functions in the method described in the fourth aspect above. The communication device may also include a communication interface for communicating with other devices. For example, if the communication device is a network device, the other device is a terminal device.

[0036] Optionally, the specific method for receiving beam failure recovery requests is the same as described in the corresponding section of the fourth aspect, and will not be repeated here.

[0037] In a thirteenth aspect, this application also provides a computer-readable storage medium, comprising: computer software instructions; when the computer software instructions are executed in a communication device, causing the communication device to perform the method described in any one of the first to fourth aspects.

[0038] In a fourteenth aspect, this application also provides a computer program product containing instructions that, when the computer program product is run in a communication device, cause the communication device to perform the method described in any one of the first to fourth aspects.

[0039] In a fifteenth aspect, this application provides a chip system including a processor and potentially a memory, for implementing the functions of the network device or terminal device described above. The chip system may be composed of chips or may include chips and other discrete components.

[0040] In a sixteenth aspect, this application also provides a communication system, the communication system including a terminal device as described in the fifth aspect or a communication device that supports the terminal device in implementing the method described in the first aspect, and a network device as described in the sixth aspect or a communication device that supports the network device in implementing the method described in the second aspect;

[0041] Alternatively, the communication system may include the terminal device described in the seventh aspect or a communication device that supports the terminal device in implementing the method described in the third aspect, and the network device described in the eighth aspect or a communication device that supports the network device in implementing the method described in the fourth aspect;

[0042] The communication system includes the terminal device described in the ninth aspect or a communication device that supports the terminal device in implementing the method described in the first aspect, and the network device described in the tenth aspect or a communication device that supports the network device in implementing the method described in the second aspect.

[0043] Alternatively, the communication system may include the terminal device described in the eleventh aspect or a communication apparatus that supports the terminal device in implementing the method described in the third aspect, and the network device described in the twelfth aspect or a communication apparatus that supports the network device in implementing the method described in the fourth aspect.

[0044] Furthermore, the technical effects of any of the above design approaches can be found in the technical effects of different design approaches in the first and fourth aspects, and will not be repeated here.

[0045] In this application, the names of terminal devices, network devices, and communication devices do not limit the devices themselves; in actual implementation, these devices may appear under other names. As long as the functions of each device are similar to those in this application, they fall within the scope of the claims of this application and their equivalents. Attached Figure Description

[0046] Figure 1 A schematic flowchart illustrating a beam failure recovery process provided in one embodiment;

[0047] Figure 2 This is a schematic diagram of the architecture of a communication system provided in one embodiment;

[0048] Figure 3 This is a schematic diagram of the architecture of a communication system provided in one embodiment;

[0049] Figure 4 This is a schematic diagram of the architecture of a communication system provided in one embodiment;

[0050] Figure 5 A flowchart of a method for sending a beam failure recovery request provided in one embodiment;

[0051] Figure 6 A flowchart of a method for sending a beam failure recovery request provided in one embodiment;

[0052] Figure 7 A flowchart of a method for sending a beam failure recovery request provided in one embodiment;

[0053] Figure 8 A schematic diagram of the composition of a communication device provided in one embodiment;

[0054] Figure 9 This is a schematic diagram of the composition of a communication device provided in one embodiment. Detailed Implementation

[0055] The terms "first," "second," and "third," etc., used in this application specification, claims, and the aforementioned drawings are used to distinguish different objects, not to limit a specific order.

[0056] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0057] To ensure clarity and conciseness in the description of the following embodiments, a brief introduction to the related technologies is given first:

[0058] 1. Control resource set (CORESET)

[0059] To improve the efficiency of blind detection of control channels by terminal devices, the concept of control resource sets was proposed during the NR standard development process. Network devices can configure one or more resource sets for terminal devices to transmit physical downlink control channels (PDCCHs). Network devices can transmit control channels to terminal devices on any control resource set corresponding to the terminal device. In addition, network devices also need to notify the terminal device of other associated configurations of the control resource set, such as search space sets. The configuration information of each control resource set differs, for example, in frequency domain bandwidth and time domain length. Extendably, the control resource set in this application can be a CORESET or control region defined by a 5G mobile communication system, or a set of enhanced-physical downlink control channels (ePDCCHs).

[0060] The time-frequency position occupied by the PDCCH can be referred to as the downlink control region. In Long Term Evolution (LTE), the PDCCH is always located in the first m symbols of a subframe (m can be 1, 2, 3, or 4). It should be noted that the E-PDCCH and R-PDCCH in LTE are not located in the first m symbols.

[0061] In NR, the downlink control area can be flexibly configured by Radio Resource Control (RRC) signaling through control resource sets and search space sets:

[0062] The control resource set can be configured with information such as the frequency domain position and the number of continuous symbols in the time domain of the PDCCH or control channel element (CCE);

[0063] The search space set can be configured with information such as the detection period and offset of PDCCH, and the starting symbol within a time slot.

[0064] For example, if the search space set can be configured with a PDCCH period of 1 time slot and a time domain start symbol of symbol 0, then the terminal device can detect the PDCCH at the beginning of each time slot.

[0065] 2. Spatial related parameter information

[0066] Spatial correlation parameter information can be quasi-collocation (QCL) information or spatial relation information. Generally, QCL information is used to indicate the spatial correlation parameters (also known as spatial correlation characteristics) of downlink signals (such as PDCCH / PDSCH / CSI-RS / DMRS / TRS), while spatial relation information is used to indicate the spatial correlation parameters (also known as spatial correlation characteristics) of uplink signals (such as PUCCH / PUSCH / SRS / DMRS).

[0067] Quasi-co-location, also known as quasi-co-site or co-location, refers to the use of QCL information, also called QCL assumption information. QCL information is used to assist in describing the terminal equipment's reception of beamforming information and the reception process.

[0068] QCL information can be used to indicate the QCL relationship between two reference signals. The target reference signal can typically be a demodulation reference signal (DMRS), a channel state information reference signal (CSI-RS), etc., while the referenced or source reference signal can typically be a CSI-RS, a synchronous signal / PBCH block (SSB), a sounding reference signal (SRS), etc. It should be understood that a tracking reference signal (TRS) is also a type of CSI-RS. It should be understood that the target reference signal can typically be a downlink signal.

[0069] The signals corresponding to antenna ports with QCL relationship can have the same or similar spatial characteristic parameters (or parameters). Alternatively, the spatial characteristic parameters (or parameters) of one antenna port can be used to determine the spatial characteristic parameters (or parameters) of another antenna port with QCL relationship with that antenna port. Alternatively, two antenna ports have the same or similar spatial characteristic parameters (or parameters). Alternatively, the difference between the spatial characteristic parameters (or parameters) of two antenna ports is less than a certain threshold.

[0070] Spatial-related information is used to help describe the beamforming information and transmission process on the transmitting side of the terminal equipment.

[0071] Space-related information is used to indicate the spatial transmission parameter relationship between two reference signals. The target reference signal can typically be a DMRS, SRS, etc., while the referenced or source reference signal can typically be a CSI-RS, SRS, SSB, etc. It should be understood that the target reference signal can generally be an uplink signal.

[0072] It should be understood that the spatial characteristic parameters of two reference signals or channels that satisfy the QCL relationship are the same (or similar, or nearly similar), and thus the spatial characteristic parameters of the target reference signal can be inferred based on the source reference signal resource index.

[0073] It should also be understood that the spatial characteristic parameters of two reference signals or channels that satisfy spatial correlation information are the same (or similar, or nearly similar), so the spatial characteristic parameters of the target reference signal can be inferred based on the source reference signal resource index.

[0074] The spatial characteristic parameters include one or more of the following parameters:

[0075] Angle of arrival (AoA), dominant angle of arrival (AoA), average angle of arrival, power angular spectrum (PAS) of the angle of arrival, angle of departure (AoD), dominant angle of departure, average angle of departure, power angular spectrum of the angle of departure, terminal equipment transmit beamforming, terminal equipment receive beamforming, spatial channel correlation, network equipment transmit beamforming, network equipment receive beamforming, average channel gain, average channel delay, delay spread, Doppler spread, Doppler shift, spatial Rx parameters, etc.

[0076] The aforementioned angles can be decomposition values ​​of different dimensions, or combinations of decomposition values ​​of different dimensions. Antenna ports can be antenna ports with different antenna port numbers, and / or antenna ports with the same antenna port number that transmit or receive information at different times and / or frequencies and / or code domain resources, and / or antenna ports with different antenna port numbers that transmit or receive information at different times and / or frequencies and / or code domain resources.

[0077] These spatial characteristic parameters describe the spatial channel characteristics between the antenna ports of the source reference signal and the target reference signal, helping the terminal device to complete the receive-side beamforming or reception processing based on the QCL information. It should be understood that the terminal device can receive the target reference signal based on the receive beam information of the source reference signal indicated by the QCL information; these spatial characteristic parameters also help the terminal device to complete the transmit-side beamforming or transmission processing based on the spatially related information. It should be understood that the terminal device can transmit the target reference signal based on the transmit beam information of the source reference signal indicated by the spatially related information.

[0078] To reduce the overhead of network devices indicating QCL information to terminal devices, as an optional implementation, the network device can indicate that the demodulation reference signal of the PDCCH or physical downlink shared channel (PDSCH) satisfies a QCL relationship with one or more of the multiple reference signal resources previously reported by the terminal device. For example, the reference signal can be a CSI-RS. Here, each reported CSI-RS resource index corresponds to a transmit / receive beam pair previously established based on that CSI-RS resource measurement. It should be understood that the receive beam information of the two reference signals or channels that satisfy the QCL relationship is the same, and the terminal device can infer the receive beam information of the received PDCCH or PDSCH based on the reference signal resource index.

[0079] The existing standard defines four types of QCLs. Network devices can configure one or more types of QCLs for terminal devices simultaneously, such as QCL type A+D, C+D:

[0080] QCL types A: Doppler shift, Doppler spread, average delay, delay spread

[0081] QCL types B: Doppler shift, Doppler spread

[0082] QCL types C: average delay, Doppler shift

[0083] QCL types D:Spatial Rx parameter

[0084] When the QCL relationship refers to type D, it can be considered as spatial QCL. When antenna ports satisfy a spatial QCL relationship, it can be a QCL relationship between downlink signal ports or between uplink signal ports (referred to as a spatial relation above). This can mean that the two signals have the same AOA or AOD, indicating they have the same receive or transmit beam. For example, for the QCL relationship between downlink and uplink signals or between ports of uplink and downlink signals, it can mean that the AOA and AOD of the two signals are corresponding, or that the AOD and AOA of the two signals are corresponding. That is, beam reciprocity can be used to determine the uplink transmit beam based on the downlink receive beam, or vice versa.

[0085] From the transmitting end's perspective, if two antenna ports are spatially QCL (Quadrature Coordinated Linearity), it means that the corresponding beam directions of these two antenna ports are spatially aligned. From the receiving end's perspective, if two antenna ports are spatially QCL, it means that the receiving end can receive the signals transmitted by these two antenna ports in the same beam direction.

[0086] Signals transmitted on ports with spatial QCL relationships can also have corresponding beams, which can include at least one of the following: the same receiving beam, the same transmitting beam, the transmitting beam corresponding to the receiving beam (corresponding to reciprocal scenarios), and the receiving beam corresponding to the transmitting beam (corresponding to reciprocal scenarios).

[0087] Signals transmitted on ports with spatial QCL relationships can also be understood as signals received or transmitted using the same spatial filter. The spatial filter can be at least one of the following: precoding, antenna port weighting, antenna port phase deflection, or antenna port amplitude gain.

[0088] Signals transmitted on ports with spatial QCL relationships can also be understood as having corresponding beam pair links (BPLs). A corresponding BPL includes at least one of the following: the same downlink BPL, the same uplink BPL, an uplink BPL corresponding to the downlink BPL, and a downlink BPL corresponding to the uplink BPL.

[0089] Therefore, spatial reception parameters (i.e., QCL of type D) can be understood as parameters used to indicate the direction information of the received beam.

[0090] In the examples of this application, the correspondence of certain parameters can also be applied to scenarios described by QCL.

[0091] It should be understood that the scenarios applicable to the QCL assumption in this application can also be two reference signals, or further, the relationship between transmission objects.

[0092] 3. Transmission Configuration Indicator (TCI) State

[0093] TCI (Transmission Control Index) is used to indicate the QCL (Quality Channel Relationship) of a signal or channel. The channel can be PDCCH / CORESET or PDSCH. The signal can be CSI-RS, DMRS, TRS, or PTRS, etc. TCI information refers to the reference signal included in the TCI satisfying the QCL relationship with the channel or signal. It is mainly used to indicate that when receiving a signal or channel, its spatial characteristic parameters are the same, similar, or nearly identical to the spatial characteristic parameters of the reference signal included in the TCI.

[0094] A TCI state can be configured with one or more referenced signals and their associated QCL types. QCL types are further divided into four categories: A, B, C, and D, which represent different combinations or selections of {Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter}. The TCI state contains QCL information, or the TCI state is used to indicate QCL information.

[0095] 4. Synchronous signal broadcast channel block (SS / PBCH block)

[0096] The SS / PBCH block can also be called the SSB. The SSB contains at least one of the primary synchronization signal (PSS), secondary synchronization signal (SSS), and PBCH. It is primarily used for cell search, cell synchronization, and carrying broadcast information.

[0097] 5. Cell carrier related concepts:

[0098] A component carrier (CC) can also be called a component carrier, a constituent carrier, or a member carrier. Each carrier in multi-carrier aggregation can be called a "CC." Each carrier consists of one or more physical resource blocks (PRBs), and each carrier can have its own corresponding physical downlink control channel (PDCCH), scheduling its own physical downlink shared channel (PDSCH). Alternatively, some carriers may not have a PDCCH; in this case, the carriers can be cross-carrier scheduled, meaning the PDCCH of one CC schedules the PDSCH of another CC. Terminal equipment can receive data on multiple CCs.

[0099] Carrier aggregation (CA) can refer to combining multiple consecutive or non-consecutive unit carriers into a larger bandwidth.

[0100] The primary cell / primary serving cell (PCell) is the cell where the CA UE camps. Generally, only the PCell has a physical uplink control channel (PUCCH).

[0101] A Primary Secondary Cell (PSCell) is a special secondary cell on a secondary eNodeB (SeNB) that is configured by the master eNodeB (MeNB) to the DC UE via RRC connection signaling.

[0102] A secondary cell (SCell) is a cell configured for a CA (Center for Access Control) terminal device via RRC (Remote Control Code) connection signaling. It operates on a secondary carrier (SCC) and can provide more radio resources for the CA terminal device. A SCell can have only downlink or both uplink and downlink capabilities.

[0103] For special cells (SpCell), in dual connectivity (DC) scenarios, SpCell refers to the PCell of the master cell group (MCG) or the PSCell of the secondary cell group (SCG); otherwise, such as in CA scenarios, SpCell refers to the PCell.

[0104] MCG / SCG refers to the group of cells in the primary base station that provide services to terminal devices. In dual-connectivity mode, the MeNB is associated with a group of serving cells, including PCells and one or more SCells.

[0105] SCG refers to the group of cells in a secondary base station that provide services to the UE. In dual-link mode, it includes PSCell and zero or more SCells.

[0106] MeNB is the base station of the cell to which the DC terminal equipment resides.

[0107] SeNB is another base station configured by MeNB to DC UE via RRC connection signaling.

[0108] 6. Beam:

[0109] A beam is a communication resource. A beam can be wide, narrow, or other types of beams. The technology used to form a beam can be beamforming or other techniques. Beamforming technology can specifically be digital beamforming, analog beamforming, or hybrid digital / analog beamforming. Different beams can be considered different resources. The same or different information can be transmitted through different beams. Optionally, multiple beams with the same or similar communication characteristics can be considered as a single beam. A beam can include one or more antenna ports for transmitting data channels, control channels, and detection signals, etc. For example, a transmit beam can refer to the signal strength distribution in different directions of space after a signal is transmitted through an antenna, and a receive beam can refer to the signal strength distribution in different directions of space of the wireless signal received from the antenna. It is understood that one or more antenna ports forming a beam can also be considered as a set of antenna ports.

[0110] Beams can be divided into transmit beams and receive beams of network devices, and transmit beams and receive beams of terminal devices. The transmit beam of a network device describes the beamforming information transmitted by the network device; the receive beam of a base station describes the beamforming information received by the network device; the transmit beam of a terminal device describes the beamforming information transmitted by the terminal device; and the receive beam of a terminal device describes the beamforming information received by the terminal device. In other words, beams are used to describe beamforming information.

[0111] Beams can correspond to time resources and / or spatial resources and / or frequency domain resources.

[0112] Optionally, the beam may also correspond to a reference signal resource (e.g., a beamforming reference signal resource) or beamforming information.

[0113] Optionally, the beam can also correspond to information associated with reference signal resources of the network device. The reference signal can be a channel state information reference signal (CSI-RS), SSB, demodulation reference signal (DMRS), phase tracking reference signal (PTRS), tracking reference signal (TRS), etc. The information associated with the reference signal resource can be a reference signal resource identifier or QCL information (especially type D QCL). The reference signal resource identifier corresponds to a transmit / receive beam pair previously established based on measurements of that reference signal resource. Through this reference signal resource index, the terminal can infer the beam information.

[0114] Alternatively, the beam can also correspond to a spatial filter or spatial domain filter, or a spatial domain transmission filter.

[0115] In this context, the receiving beam can be equivalent to a spatial transmission filter, a spatial domain transmission filter, a spatial domain receiving filter, and a spatial receiving filter; the transmitting beam can be equivalent to a spatial filter, a spatial domain transmission filter, a spatial domain transmitting filter, and a spatial transmitting filter. Information about spatially relevant parameters can be equivalent to a spatial filter (spatial domain transmission / receive filter). Optionally, a spatial filter generally includes a spatial transmitting filter and / or a spatial receiving filter. This spatial filter can also be called a spatial transmitting filter, a spatial receiving filter, a spatial transmission filter, or a spatial transmission filter, etc. The receiving beam on the terminal device side and the transmitting beam on the network device side can be downlink spatial filters, and the transmitting beam on the terminal device side and the receiving beam on the network device side can be uplink spatial filters.

[0116] 7. Antenna port

[0117] An antenna port, also simply called a port, is a transmitting antenna that is recognized by the receiving device, or a spatially distinguishable transmitting antenna. Each virtual antenna can be configured with one antenna port, and each virtual antenna can be a weighted combination of multiple physical antennas. Each antenna port can correspond to a reference signal port.

[0118] 8. Bandwidth Part (BWP)

[0119] Network devices can configure one or more downlink / uplink bandwidth regions for terminal devices. This BWP can consist of consecutive frequency-domain PRBs, and the BWP is a subset of the terminal device's bandwidth. The smallest granularity of this BWP in the frequency domain is one PRB. The system can configure one or more bandwidth regions for terminal devices, and these multiple bandwidth regions can overlap in the frequency domain.

[0120] In a single-carrier scenario, a terminal device can have only one active BWP at any given time. The terminal device can only receive or transmit data / reference signals on the active BWP.

[0121] In this application, when applicable to BWP scenarios, a specific BWP can also be a set of bandwidths on a specific frequency, or a set of multiple RBs.

[0122] 9. Reference signals configured for detecting beam failure and recovering beam failure.

[0123] To detect beam failures, network devices need to indicate beam failure detection reference signal resources (also known as link failure detection reference signal resources) to terminal devices. Beam failure detection reference signal resources can be indicated in several ways. For example, the network device can explicitly configure a beam failure detection reference signal resource set (RS set) for the terminal device (e.g., beam failure detection RSresourceconfig, beam failure detection RS, or failure detection resources). The network device can configure the beam failure detection reference signal resource set through one or more signaling methods such as RRC, MAC-CE, and DCI. Alternatively, the reference signal for beam failure detection can be indicated implicitly, such as using the reference signal associated with the TCI (e.g., type-D QCL) of the PDCCH as the beam failure detection reference signal. This reference signal is one that satisfies the QCL relationship with the DMRS of the PDCCH and is a periodically transmitted reference signal. Optionally, when the network device displays a set of reference signal resources configured for beam failure detection, the terminal device can detect beam failure based on the set of reference signal resources for beam failure detection; when the network device does not display a set of reference signal resources configured for beam failure detection, the terminal device can detect beam failure according to the reference signals indicated in the above implicit manner.

[0124] In this beam failure detection reference signal resource set, the RS and the demodulation reference signal of the downlink physical control channel PDCCH satisfy the QCL relationship or use the same TCI state as the PDCCH. If the channel quality information (such as reference signal receiving power (RSRP), channel quality indicator (CQI), block error ratio (BLER), signal-to-interference plus noise ratio (SINR), signal-to-noise ratio (SNR), etc.) of some or all of the reference signals in this set is lower than a predetermined threshold, then a beam failure is determined. The lowering of the predetermined threshold can be N consecutive times below the predetermined threshold or N times within a certain time period. This predetermined threshold can be called the beam failure detection threshold or simply the beam failure threshold. It should be understood that any threshold used for beam failure detection can be this predetermined threshold, and this application does not limit the name of this predetermined threshold. Optionally, the beam failure detection threshold can be configured by the network device, or it can be the same threshold as the radio link failure out-of-sync (OOS) threshold. Optionally, when the network device is configured with a beam failure detection threshold, this threshold is used to detect beam failure; when the network device is not configured with a beam failure detection threshold, the radio link out-of-sync threshold can be used as the beam failure detection threshold. It should be understood that the beam failure detection reference signal here can be used by the terminal to detect the channel quality of a certain transmitted beam of the network device, which is the beam used by the network device when communicating with the terminal.

[0125] To recover from beam failure, network devices can also instruct terminal devices to use a set of reference signal resources (candidate beam RS list, candidate beam RS identification resource, beam failure candidate beam resource, candidate beam identification RS, or candidate beam list) to restore the link between the terminal device and the network device. After a beam failure, the terminal device needs to select reference signal resources from the candidate reference signal resource set whose channel quality information (such as one or more of the following: RSRP, RSRQ, CQI, SINR, etc.) is higher than a predetermined threshold to restore the communication link. This can also be understood as the candidate beam identification RS being used by the terminal device to initiate link reconfiguration after determining that the network device's transmit beam has failed. For example, the network device can explicitly configure the reference signal resource set for beam failure recovery to the terminal device. The network device can configure the beam failure detection reference signal resource set through one or more signaling methods, such as RRC, MAC-CE, and DCI signaling. The reference signal resource set used for beam failure recovery can also be a default reference signal resource set (e.g., a reference signal resource set for beam management (BM), a reference signal resource set for RRM measurement, a reference signal resource set consisting of all or some SSBs, or a reference signal resource set multiplexed with other functions). The reference signal resource set used for beam management (BM) can be a reference signal resource set with repetition marked "off" (or a reference signal resource set with repetition marked "on"). Optionally, when the network device is configured with candidate reference signal resource sets, reference signals are identified from these sets; when the network device is not configured with candidate reference signal resource sets, reference signals are identified from the default reference signal resource set. The identified reference signals can be used to recover from beam failure. Optionally, the channel quality of the identified reference signals is greater than a preset threshold.

[0126] Optionally, the predetermined threshold used in the process of identifying the reference signal for link recovery described above can be configured by the network device, or it can be a predefined threshold. For example, when the network device does not configure this threshold, the threshold used for mobility measurement is used by default. This predetermined threshold can be called a beam failure recovery threshold or a link recovery threshold. It should be understood that any threshold used for beam failure recovery can be this predetermined threshold, and the present invention does not limit the name of this predetermined threshold.

[0127] It should be understood that, in specific implementations, the two sets of reference signal resources used for beam failure detection and reference signal resource sets used for restoring the link between the terminal device and the network device may have other names, and this application does not specifically limit them.

[0128] In this application embodiment, beam failure can also be referred to as beam failure, link failure, link failure, communication failure, communication link failure, communication link failure, etc. In this application embodiment, these concepts have the same meaning. The communication failure can refer to the signal quality of the reference signal used for beam failure detection of the PDCCH being less than or equal to a preset threshold.

[0129] In this application embodiment, beam failure recovery can also be referred to as restoring communication between network devices and terminal devices, beam failure recovery, beam fault recovery, beam recovery, link failure recovery, link fault recovery, link recovery, communication failure recovery, communication fault recovery, communication link failure recovery, communication link fault recovery, communication recovery, link reconfiguration, etc.

[0130] In this embodiment of the application, the beam failure recovery request may also be referred to as beam failure recovery request information, beam fault recovery request information, beam recovery request information, link failure recovery request information, link fault recovery request information, link recovery request information, communication failure recovery request information, communication recovery request information, communication link failure recovery request information, communication link failure recovery request information, communication link recovery request information, link reconfiguration request information, reconfiguration request information, etc. Optionally, a communication failure recovery request may refer to sending a signal on the resource used to carry the communication failure recovery request.

[0131] It should be understood that "information" in this application may be replaced with "message".

[0132] In this application embodiment, the beam failure recovery response can also be referred to as beam failure recovery response information, beam fault recovery response information, beam failure response information, beam fault response information, beam recovery response, link failure recovery response information, link fault recovery response information, link failure response information, link failure response information, link recovery response information, communication failure recovery response information, communication failure response information, communication failure response information, communication recovery response information, communication link failure recovery response information, communication link failure recovery response information, communication link failure response information, communication link failure response information, communication link failure response information, communication link response information, link reconfiguration response information, reconfiguration response information, etc. It should be understood that in this application, the communication failure recovery response information can be simply referred to as response information.

[0133] In this embodiment of the application, beam failure recovery response information may refer to downlink control information (DCI) scrambled by cell radio network temporary identifier (C-RNTI) and received on the control resource set and / or search space set used to send beam failure recovery response. The beam failure recovery response information may also be DCI scrambled by other information (such as DCI scrambled by BFR-RNTI), data scheduled by the above-mentioned DCI, and ACK of the data scheduled by the above-mentioned DCI. The beam failure recovery response information can also be one of the following: a DCI scrambled with the Cell Radio Network Temporary Identifier (C-RNTI), a DCI scrambled with the Modulation and Coding Scheme Cell-Specific Radio Network Temporary Identifier (MCS-C-RNTI), a downlink control information DCI within the dedicated search space, a DCI scrambled with the Dedicated Radio Network Temporary Identifier (RNTI), a DCI scrambled with the Random Access Radio Network Temporary Identifier (RA-RNTI), a DCI containing a preset state value, a DCI containing Transmission Configuration Indication (TCI) information, a quasi-co-location QCL indication information for the cell where the beam failure occurred, or a DCI indicating newly transmitted data. This application embodiment does not limit this. It should be understood that the DCI indicating newly transmitted data has the same Hybrid Automatic Repeat Request (HARQ) process identifier as the DCI that schedules the resources carrying the beam failure request information; optionally, the new data indicator (NDI) of the two DCIs may be different. It should be understood that when the terminal device receives the beam failure recovery response information, it considers the beam failure recovery successful. It should be understood that after a beam failure recovery is successful, the terminal device may no longer send beam failure recovery request information, and may also stop or reset the beam failure detection counter, the beam failure detection timer, the beam failure recovery counter, and the beam failure recovery timer, etc.

[0134] It should be understood that the names of beam failure, beam failure recovery, beam failure recovery request information and beam failure recovery response information in the embodiments of this application may also be called other names, and this application does not make specific limitations on them.

[0135] It should be understood that in this application, beam recovery failure can be understood as the terminal device no longer sending beam failure recovery request information, or as stopping the beam failure recovery timer (or clock) from counting, or as stopping the beam failure recovery counter from counting, etc.

[0136] It should be understood that in the embodiments of this application, "beam" can be replaced with "link".

[0137] It should also be understood that in the embodiments of this application, "cell" can be understood as "serving cell" or "carrier".

[0138] Optionally, the cell includes at least one of a downlink carrier, an uplink (UL) carrier, and a supplementary uplink (SUL) carrier. Specifically, the cell may include a downlink carrier and an uplink carrier; or the cell may include a downlink carrier and a supplementary uplink carrier; or the cell may include a downlink carrier, an uplink carrier, and a supplementary uplink carrier.

[0139] Optionally, the uplink supplementary carrier has a lower carrier frequency than the uplink carrier in order to improve uplink coverage.

[0140] Optionally, in general, in an FDD system, the uplink carrier and the downlink carrier have different carrier frequencies; in a TDD system, the uplink carrier and the downlink carrier have the same carrier frequency.

[0141] It should also be understood that, in the embodiments of this application, uplink resources are on the uplink carrier; downlink resources are on the downlink carrier.

[0142] It should also be understood that in the embodiments of this application, the uplink carrier can be a normal uplink carrier or a supplementary uplink (SUL) carrier.

[0143] It should be understood that "detection" in the embodiments of this application can be understood as "receiving" or "decoding".

[0144] It should be understood that in this application, the time unit can be one or more radio frames, one or more subframes, one or more time slots, one or more mini slots, one or more orthogonal frequency division multiplexing (OFDM) symbols, etc., as defined in the LTE or 5G NR system, or it can be a time window composed of multiple frames or subframes, such as a system information (SI) window.

[0145] In LTE systems, the smallest time scheduling unit is a 1ms transmission time interval (TTI). 5G supports both time unit-level and micro-time unit-level time domain scheduling granularity to meet the latency requirements of different services. For example, time units are mainly used for eMBB services, while micro-time units are mainly used for URLLC services. It should be noted that the terms "time unit" and "micro-time unit" are general terms. A specific example could be that a time unit can be called a time slot, and a micro-time unit can be called a micro-time slot, non-slot-based, or mini-slot; or, a time unit can be called a subframe, and a micro-time unit can be called a micro-subframe; other similar time domain resource partitioning methods are not limited. The first time unit mentioned in this application can refer to a time slot or a mini-time slot, etc. For example, a time slot may include 14 time-domain symbols, while a mini-time slot may include fewer than 14 time-domain symbols, such as 2, 3, 4, 5, 6, or 7; or, a time slot may include 7 time-domain symbols, while a mini-time slot may include fewer than 7 time-domain symbols, such as 2 or 4, etc. The specific values ​​are not limited. These time-domain symbols can be OFDM symbols. For a time slot with a subcarrier spacing of 15 kilohertz (kHz), including 6 or 7 time-domain symbols corresponds to a time length of 0.5 ms; for a time slot with a subcarrier spacing of 60 kHz, the corresponding time length is shortened to 0.125 ms.

[0146] It should be understood that in this application, "cell identifier" can also be replaced with "cell index".

[0147] It should be understood that in the embodiments of this application, the beam failure event counter can also be called a beam failure event indication counter or a beam failure detection counter.

[0148] It should be understood that in various embodiments of this application, the reference signal information may include a reference signal resource index and / or the channel quality of the reference signal. The channel quality may include one or more of the following: reference signal receiving power (RSRP), signal to interference plus noise ratio (SINR), reference signal receiving quality (RSRQ), channel quality indication (CQI), or signal noise ratio (SNR), etc.

[0149] Communication systems typically use different types of reference signals: one type is used to estimate the channel, enabling coherent demodulation of received signals containing control information or data; another type is used to measure channel state or channel quality, thereby enabling scheduling of terminal devices. Terminal devices obtain Channel State Information (CSI) based on channel quality measurements of the CSI-RS. The CSI includes at least one of the following: Rank Indicator (RI), Precoding Matrix Indicator (PMI), and Channel Quality Indicator (CQI). This CSI information can be transmitted from the terminal device to the network device via PUCCH or PUSCH.

[0150] With the emergence of smart terminals, especially video services, current spectrum resources are insufficient to meet the explosive growth in user demand for capacity. High-frequency bands, particularly millimeter-wave bands, with their greater available bandwidth, are increasingly becoming candidate bands for next-generation communication systems. On the other hand, modern communication systems typically use multi-antenna technology to improve system capacity and coverage or enhance user experience. Another advantage of using high-frequency bands is the significant reduction in the size of multi-antenna configurations, facilitating site acquisition and the deployment of more antennas. However, unlike the operating frequency bands of existing systems such as LTE, high-frequency bands result in greater path loss, especially as atmospheric and vegetation factors further exacerbate wireless propagation losses.

[0151] To overcome the significant propagation loss mentioned above, a signal transmission mechanism based on beamforming technology is employed to compensate for the loss during signal propagation through a larger antenna gain. The beamformed signal may include broadcast signals, synchronization signals, and cell-specific reference signals, etc.

[0152] When signals are transmitted using beamforming technology, if a user moves, the direction of the beamforming beam corresponding to the transmitted signal may no longer match the user's new location, leading to frequent signal interruptions. To track changes in the beamforming beam during signal transmission, a channel quality measurement and result reporting mechanism based on beamforming technology is introduced. The channel quality measurement can be based on the beamformed synchronization signal or a cell-specific reference signal. Compared to cell handover, user switching between different beamforming beams is more dynamic and frequent; therefore, a dynamic measurement and reporting mechanism is needed. Optionally, similar to CSI information reporting, the channel quality results of the beamforming beam can also be reported by the terminal device to the network device via PUCCH or PUSCH.

[0153] The terminal device measures multiple beams transmitted by the network device, selects the N superior beams, and reports the measurement information of the N superior beams to the network device. The beam measurement information mainly includes a reference signal resource index and reference signal quality information. The reference signal quality information can be at least one of the following: L1-reference signal received power (L1-RSRP), L1-signal to interference plus noise ratio (L1-SINR), or channel quality indication (CQI).

[0154] In downlink signal transmission, both the network device's transmit beam and the terminal's receive beam may change dynamically. The terminal device may determine multiple optimal receive beams based on the received signal. To enable the terminal device to determine its own receive beam, it can feed back information from these multiple receive beams to the network device. The network device can then instruct the terminal device to use beam indication information. When the terminal device uses analog domain beamforming, it can accurately determine its receive beam based on the beam indication information sent by the network device, thus saving beam scanning time and power. For example, the network device can configure the PDCCH QCL information to indicate the receiving parameters used by the terminal device. Specifically, the PDCCH QCL information configuration method is as follows: RRC configures K candidate QCL information for the PDCCH, such as K TCI states; MAC-CE indicates the PDCCH QCL information (when K>1).

[0155] Furthermore, the agreement stipulates that before the network device sends RRC and MAC-CE, the terminal device can assume that the DMRS of PDCCH and PDSCH is QCL with the SSB determined at the time of initial access.

[0156] However, due to obstructions during communication and the poor diffraction capability of high-frequency channels, the currently serving beam may be blocked, preventing signal transmission. To prevent sudden communication interruptions in the event of beam obstruction, a mechanism is needed to detect the current link quality and quickly restore the link in the event of obstruction.

[0157] To prevent sudden communication interruptions caused by blocked wireless signals, terminal devices can measure the communication quality of the reference signal configured for beam failure detection in network devices to determine whether a beam failure has occurred. Figure 1 A schematic flowchart of the beam failure recovery process in the prior art is shown, such as... Figure 1 As shown, the beam failure recovery process includes:

[0158] S101, The reference signal resource set for beam failure detection of the terminal device (beam failuredetection RS set) is used to determine the beam failure between the terminal device and the network device.

[0159] In some embodiments, when a terminal device determines that the channel quality information of the beam failure detection reference signal or all or part of the reference signals in the beam failure detection reference signal resource set is less than or equal to the beam failure detection threshold after M consecutive beam failure detection reference signals, the terminal device can determine that a beam failure has occurred between the terminal device and the network device. Specifically, the following steps may be included:

[0160] 1. The terminal equipment measures the channel quality (also known as "signal quality") of the reference signals within the beam failure detection reference signal resource set. For ease of description, the reference signals within the beam failure detection reference signal resource set can be referred to as q0. When the channel quality of all or part of the reference signals in q0 is less than or equal to the link failure detection threshold during the beam failure event reporting period, the physical (PHY) layer of the terminal equipment will report beam failure event indication information to the media access control (MAC) layer.

[0161] The beam failure event reporting period is the period during which the physical (PHY) layer reports beam failure event indication information to the media access control (MAC) layer.

[0162] It should be understood that the reference signal resources in q0 and the CORESET / PDCCH of the SCell configuring the reference signal satisfy a QCL relationship (the beam failure detection reference signal resources and CORESET can have a one-to-one, many-to-one, or one-to-many relationship). For example, the DMRS of the reference signal and PDCCH in the beam failure detection reference signal resource set satisfy a quasi-co-location (QCL) relationship or have the same TCI state as the PDCCH.

[0163] 2. If the terminal device detects N consecutive beam failure instances (which can also be understood as the MAC layer receiving N beam failure instance information while the beam failure detection timer is running), the terminal device determines that the current SCell has experienced a beam failure.

[0164] N is configured through beam failure detection parameters (which can be the beamFailureInstanceMaxCount parameter configured by RRC signaling or MAC-CE signaling).

[0165] Whether N beam failure instances are consecutive, or the count of N beam failure instances, is controlled by the beam failure detection timer in the beam failure detection parameters (which can be the beamFailureDetectionTimer parameter configured in RRC signaling or MAC-CE signaling).

[0166] The beam failure event reporting period is the maximum value between the period of the reference signal with the smallest period in q0 and 2ms. The length of the beam failure detection timer is an integer multiple of the beam failure event reporting period.

[0167] The terminal device maintains a beam failure instance counter (BFI-COUNTER), which is initially set to 0. If the terminal device's MAC layer receives a beam failure instance indication from the PHY layer, the terminal device starts or restarts the beam failure detection timer and increments the BFI-COUNTER. When the BFI-COUNTER count is greater than or equal to N, a beam failure is determined to have occurred in that SCell.

[0168] If the beam failure detection timer times out, or if higher-layer signaling reconfigures any of the beam failure detection parameters, set BFI-COUNTER to 0. If beam failure recovery is successful, also set BFI-COUNTER to 0 and stop the beam failure detection timer.

[0169] It should be understood that in this embodiment, the way the terminal device determines that the beam has failed on a certain carrier with the network device is not limited to the examples above, and can also be determined by other judgment methods. This application does not limit this in any way.

[0170] It should be understood that when a terminal device determines that a beam failure has occurred between it and a network device on a certain carrier, it can be interpreted as the terminal device determining that a link failure has occurred between it and the network device on a certain carrier.

[0171] S102, Terminal equipment identifies new links.

[0172] A terminal device can measure reference signals in a set of reference signal resources to identify the reference signal used to restore the link between the terminal device and the network device. Generally, the channel quality of the reference signal used to restore the link between the terminal device and the network device needs to be greater than or equal to a beam failure recovery threshold. This reference signal can be simply referred to as the first reference signal or the new beam. The first reference signal can be one reference signal or multiple reference signals. These multiple reference signals can be used to restore the carrier link. Each of the multiple reference signals can be used to restore the carrier configured with that reference signal. Alternatively, the multiple reference signals can be used to restore the unit carrier configured with the multiple reference signals.

[0173] In some embodiments, the terminal device can identify a reference signal in a candidate beam identification RS set. The terminal device can restore the link based on the reference signal. Optionally, the channel quality of the identified reference signal is greater than or equal to the beam failure recovery threshold. The process of the terminal device identifying the reference signal can be understood as the terminal device determining a reference signal resource (which may be simply referred to as a new identified beam or new beam) in the candidate reference signal resource set whose channel quality is greater than or equal to the beam failure recovery threshold; this determination process can be determined by measuring the channel quality information of the candidate reference signal resource set.

[0174] It should be understood that, in one possible scenario, the terminal device may not be able to identify a reference signal resource (newly identified beam) with channel quality greater than or equal to the beam failure recovery threshold. In another possible scenario, the terminal device may not execute step S102.

[0175] S103. Network devices configure or instruct PUSCH resources for terminal devices.

[0176] S104. The terminal device receives information from the network device regarding the configuration or indication of PUSCH resources.

[0177] It should be understood that, for ease of description, the PUSCH resources configured by network devices for terminal devices are referred to as the second resource.

[0178] Specifically, the indication method for the second resource can be one or more of the following:

[0179] Method 1: The terminal device sends a first request message to request a second resource. The second resource can be a PUSCH resource indicated by the network device through an uplink grant (or DCI). This uplink grant (or DCI) can be a DCI with CRC scrambled by C-RNTI / MCS-C-RNTI.

[0180] In one implementation, the first request information indicates a beam failure event and is carried on PUCCH or PRACH resources. In another implementation, the first request information can be used to request uplink resources and is carried on PUCCH or PRACH resources. The first request information can also be called a scheduling request information.

[0181] It should be understood that the terminal device can send the first request information after step S101 and before step S104.

[0182] Specifically, the terminal device sends the first request information.

[0183] The first request information may also be referred to as a scheduling request information, or it may use the same format as the scheduling request information. This first request information can be used to request a resource (referred to as the second resource) to carry the second request information.

[0184] It should be understood that the second resource may be indicated or activated by the response information of the first request information.

[0185] Specifically, in one implementation, after receiving the first request information, the network device can also send response information to the first request information.

[0186] The response information to the first request can be used to indicate the allocation of second resources for the terminal, i.e., the network device allocates resources to the terminal. This second resource can be aperiodic (or dynamic) resources. In this method, the network device determines whether to allocate second resources based on whether there are cells with beam failures in the current network (indicated by the first request). If the network device receives the first request, it can know that there are cells with beam failures in the current network, and the network device can dynamically allocate second resources so that the terminal device can further report which cells have experienced beam failures, and / or report information on new links to restore the beam-failed cells. Since beam failure events are sudden events, this method does not require pre-reserving periodic resources for sending beam failure recovery request information, effectively saving resource overhead.

[0187] In another implementation, the response information of the first request can also be used to activate a second resource. That is, the second resource originally allocated to the terminal is activated by the response information of the first request. The activated second resource is a semi-persistent or periodic resource. For example, the second resource can be a semi-persistent or periodic resource activated by the response information of the first request or the DCI signaling after the first request (e.g., PUSCH, PUCCH, or physical random access channel, PRACH). In this method, the network device determines whether to activate the second resource based on whether there are cells with link failures in the current network (indicated by the first request information). If the network device receives the first request information, it can know that there are cells with beam failures in the current network. The network device activates the second resource so that the terminal device can further report which cells have beam failures and / or report information on new links to restore the cells with link failures.

[0188] Optionally, the second resource may be configured by higher-level signaling or system information, or it may be a preset resource.

[0189] Specifically, the second resource may be configured for the terminal by the network device and sent to the terminal via higher-layer signaling or system information. The second resource may also be pre-agreed upon by the network device and the terminal device, or pre-set by the terminal; this application does not limit this.

[0190] Optionally, the second resource may also be a resource associated with the resource used to carry the first request information.

[0191] Specifically, the second resource can be mapped to the resource used to carry the first request information, so that the terminal can determine the second resource once it knows the resource used to carry the first request information. Optionally, the association between the resource used to carry the first request information and the second resource can be configured by system information such as the master information block (MIB) or system information block (SIB), or by signaling from radio resource control (RRC) or media access control (MAC)-control element (CE). This system information or signaling can be sent before sending the first request information. Optionally, the configuration of the resource used to carry the first request information and the second resource can also be configured through the aforementioned system information or signaling. This method eliminates the need to send the second request information through the resource allocated by the response information of the first request information, but instead sends it directly on the second resource, which can effectively reduce beam recovery delay and improve beam recovery speed.

[0192] It should be noted that the network device can configure multiple resources for transmitting first request information and multiple resources for transmitting second request information for the terminal device. The terminal device can select one or more resources from the multiple resources used to transmit the first request information to send the first request information, and can also select one or more resources from the multiple resources used to transmit the second request information as second resources. The multiple resources used to transmit the first request information and the multiple resources used to transmit the second request information can be configured by system information such as the aforementioned MIB or SIB, or by signaling such as RRC or MAC-CE.

[0193] Optionally, the second resource can also be a resource associated with the first request information. Optionally, the network device can configure multiple resources for sending the first request information and multiple resources for sending the second request information, as well as the association relationships between these multiple resources, through system information such as MIB or SIB, or through RRC or MAC-CE signaling. The terminal can select one of the multiple resources for transmitting the first request information to send the first request information, and can also select one of the multiple resources for transmitting the second request information as the second resource. Each resource for transmitting the first request information can be associated with one or more second resources, and the second resources associated with each resource for transmitting the first request information can be of different sizes. The terminal device sends the second request information on the second resource associated with the resource on which the first request information is sent.

[0194] It should be understood that the second resource can be a PUSCH resource or a PUCCH resource.

[0195] It should be understood that the second request information in the embodiment may be a MAC-CE indicating cell information of a beam failure cell. The response information of the first request information may be DCI information.

[0196] The second request information may include the identification information of the beam-failed cell and / or the reference signal information for recovering the beam-failed cell. Alternatively, the cell information of the beam-failed cell may include the identification information of the beam-failed cell and / or the reference signal information for recovering the beam-failed cell. The reference signal information for recovering the beam-failed cell may be an index of a reference signal resource and / or the channel quality information of that reference signal resource (such as one or more of the following: RSRP, SINR, RSRQ, CQI, etc.).

[0197] Method 2: The second resource can also be a PUSCH resource directly indicated by the network device via an uplink grant (or DCI). This uplink grant (or DCI) can be a DCI with CRC scrambled by C-RNTI / MCS-C-RNTI.

[0198] For methods 1 and 2, the second resource can be dynamically allocated by the network device. This method does not require pre-reserving periodic resources, which can effectively save resource overhead.

[0199] Method 3: The second resource can be a semi-persistent or periodic resource activated by the network device via RRC, MAC-CE, or DCI. For example, the second resource can be a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), or a physical random access channel (PRACH).

[0200] Method 4: The second resource can be configured using configuration information or a preset resource.

[0201] Specifically, the second resource may be configured for the terminal by the network device and sent to the terminal via higher-layer signaling or system information. The second resource may also be pre-agreed upon by the network device and the terminal device, or pre-set by the terminal; this application does not limit this.

[0202] Optionally, this configuration information can be configured by system information such as the master information block (MIB) or system information block (SIB), or by signaling from radio resource control (RRC) or media access control (MAC)-control element (CE). This configuration information can also be configured via a configured grant.

[0203] Method 5: The second resource can be a PUSCH resource associated with PRACH or PUCCH. Alternatively, the second resource can be a PUSCH resource in a 2-step PRACH. Understandably, network devices configure associated PRACH and PUSCH resources, and the PUSCH resource does not require DCI indication. In one implementation, the terminal device selects a PRACH resource to initiate a random access procedure and sends other information (such as UE ID) on the PUSCH resource associated with that PRACH resource. In another implementation, the PRACH or PUCCH resource is a resource carrying first request information. The first request information is as described in Method 1 and will not be repeated here.

[0204] For methods 3, 4, and 5, the configuration information of the second resource indicated by the network device can be sent in advance. This configuration information can be sent by the network device to the terminal device before the terminal device determines the beam failure. In this case, after the terminal device discovers the beam failure, it can directly send the beam failure recovery request information on the resource without waiting for the network device to allocate PUSCH resources.

[0205] It should be understood that the terminal device can obtain one or more second resources through any one or more of the methods 1 to 5 described above.

[0206] S105. The terminal device sends a beam failure recovery request to the network device.

[0207] The beam failure recovery request is associated with a reference signal (new identified beam or new beam) identified in S102 whose channel quality is greater than or equal to the beam failure recovery threshold. The terminal device can notify the network device of the new identified beam or reference signal resource either explicitly or implicitly. For example, in an explicit manner, the terminal device can explicitly report the resource index or resource identifier of the newly identified reference signal to the network device. In an implicit manner, the network device pre-configures the association between multiple uplink resources for transmitting BFRQ information and multiple candidate reference signal resources, and the terminal device implicitly indicates the newly identified reference signal resource by selecting the uplink resource for transmitting BFRQ.

[0208] The terminal device can also report at least one of the following through one or more beam failure recovery request messages: new beam information, cell identifier of the beam failure, etc. This can also be understood as the BFRQ indicating one or more of the following: new beam information, cell identifier of the beam failure, beam failure event.

[0209] It should be understood that in this embodiment, the terminal device may send a BFRQ to the network device and recover the beam failure between the terminal device and the network device through the network device, or the terminal device may send a BFRQ to another network device and recover the beam failure between the terminal device and the network device through the other network device.

[0210] In NR, BFRQ information for the PCell can be reported via PRACH resources. The base station configures one or more PRACH resources and associates each PRACH resource with a reference signal used to recover from link failures. This reference signal can be a reference signal from the candidate reference signal resource set configured by the base station. When the terminal device acknowledges beam failure, identifies the new beam, and selects the PRACH resource associated with the new beam to transmit the signal. In this way, the terminal device can implicitly indicate new beam information.

[0211] For example, the set of uplink resources configured by the network device for transmitting beam failure request information for the first cell is called the first uplink resource set. The number of Physical Random Access Channel (PRACH) resources included in this first uplink resource set is equal to the number of downlink reference signals in the candidate reference signal resource set of the first cell; that is, one PRACH resource is associated with one downlink reference signal. The terminal device identifies reference signals in the candidate reference signal resource set that are greater than or equal to the beam failure recovery threshold, and transmits beam failure recovery request information on the PRACH resource associated with that reference signal. Optionally, when uplink and downlink are reciprocal, the transmit beam of the terminal device when transmitting information on a PRACH resource is the transmit beam corresponding to the receive beam of the downlink reference signal associated with that PRACH resource; that is, the terminal device can use the transmit beam corresponding to the receive beam to transmit information on that PRACH resource. When there is no reciprocity between uplink and downlink, one possible implementation is that in the first uplink resource set, a PRACH resource is associated with a downlink reference signal and an uplink reference signal. The terminal device can determine the uplink reference signal associated with the PRACH resource based on the determined downlink reference signal, and then use the transmission beam of the uplink reference signal to transmit information on the PRACH resource.

[0212] In NR, the BFRQ information of a SCell can be reported in one step. This BFRQ information can be carried on PUSCH resources or PUCCH resources; the BFRQ information can indicate the cell identifier of the beam failure and / or newbeam information.

[0213] BFRQ information can also be reported in two steps: BFRQ1 + BFRQ2. BFRQ1 can be carried on PUCCH or PRACH resources, and BFRQ2 can be carried on PUSCH or PUCCH resources. In one implementation, BFRQ1 indicates a beam failure event, and BFRQ2 indicates the cell identifier of the beam failure and / or new beam information. In another implementation, BFRQ1 indicates a beam failure event and / or the cell identifier of the beam failure, and BFRQ2 indicates new beam information.

[0214] It should be understood that the aforementioned BFRQ information is carried on the PUSCH resource, which can be understood as reporting BFRQ information through MAC-CE.

[0215] Optionally, the media access control (MAC) layer of the terminal device maintains a beam failure recovery timer and a beam failure recovery counter. The beam failure recovery timer controls the overall beam failure recovery time, and the beam failure recovery counter limits the number of times the terminal device sends a beam failure recovery request. When the beam failure recovery counter reaches its maximum value, the terminal device considers the beam failure recovery unsuccessful and stops the beam failure recovery process. The recovery time of the recovery timer and the count value of the recovery counter can be configured by the network device or preset values.

[0216] S106. The network device receives a beam failure recovery request sent by the terminal device.

[0217] In some embodiments, after receiving a beam failure recovery request, the network device may also send a beam failure recovery response to the terminal device. The terminal device receives the beam failure recovery response and executes S107 and S108.

[0218] The terminal device can use C-RNTI scrambled or MCS-C-RNTI scrambled DCI within the detection control resource set (CORESET) and search space set as BFRR.

[0219] The CORESET and / or search space set can be a dedicated CORESET and / or search space set configured by the network device for the terminal device, used as downlink control resources for the network device to send response information to the beam failure recovery request after the terminal device sends a beam failure request.

[0220] It should also be understood that, in this embodiment, the time order of S101 and S102 in the beam failure recovery process is not limited. S102 can precede S101, S101 can precede S102, or S102 and S101 can be performed simultaneously. It should also be understood that S107 and S108 are optional steps.

[0221] When a terminal device determines that a beam has failed, it sends a MAC-CE carrying beam failure recovery request information to the network device on any PUSCH. If the MAC-CE carrying beam failure recovery request information can be transmitted on any PUSCH, the reliability of the MAC-CE transmission may be low, and retransmission is required to ensure successful transmission of the MAC-CE, which will increase the beam failure recovery delay.

[0222] For example, if a PUSCH resource is scheduled by an uplink grant (ul grant), and the code rate indicated by the ul grant is high, then the transmission accuracy of BFRQ is low, and retransmission is needed to improve the reliability of BFRQ transmission, thereby increasing the delay of beam failure recovery.

[0223] To address the aforementioned problems, embodiments of this application provide a method for sending beam failure recovery requests. The method includes: selecting a specific PUSCH resource and sending at least one beam failure recovery request on that PUSCH resource; or, sending at least two beam failure recovery requests on any PUSCH resource. Thus, by limiting the PUSCH resources used for BFRQ transmission or by sending multiple identical BFRQs, transmission reliability is improved, and beam failure recovery latency is reduced.

[0224] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0225] The technical solutions of this application can be applied to various communication systems, such as: Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), LTE, LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), future 5th generation (5G) mobile communication systems, or new radio (NR), etc. The 5G mobile communication systems described in this application include non-standalone (NSA) 5G mobile communication systems and / or standalone (SA) 5G mobile communication systems. The technical solutions provided in this application can also be applied to future communication systems, such as 6th generation mobile communication systems. The communication system can also be a PLMN network, a device-to-device (D2D) network, a machine-to-machine (M2M) network, an IoT network, or other networks.

[0226] Figure 2 This is a schematic diagram of the architecture of the communication system used in the embodiments of this application. Figure 2 As shown, the communication system 200 includes a network device 210 and a terminal device 220. The terminal device 220 is wirelessly connected to the network device 210. Figure 2 This is just an illustration; the communication system may also include other devices, such as core network equipment, wireless relay equipment, and wireless backhaul equipment. Figure 2Not shown in the diagram. Core network equipment and network equipment can be independent and different physical devices, or the functions of core network equipment and the logical functions of network equipment can be integrated on the same physical device, or a single physical device can integrate some of the functions of core network equipment and some of the functions of network equipment. Terminal equipment can be fixed in location or mobile. The embodiments of this application do not limit the number of terminal equipment, core network equipment, radio access network equipment, and terminal equipment included in the communication system.

[0227] The communication system 200 operates in a single-carrier or carrier aggregation (CA) scenario. The system includes a network device 210 and a terminal device 220. The network device 210 and terminal device 220 communicate via a wireless network. When terminal device 220 detects a link failure between the network device 210 and terminal device 220, it sends a BFRQ to the network device 210. Optionally, upon receiving the BFRQ, the network device 210 sends a beam failure recovery response (BFRR) or reconfigures the link to the terminal device 220.

[0228] It should be understood that Figure 2 The network device 210 may include one or more cells. For example, it may include a first cell and a second cell. If the link between the terminal device and the network device in the second cell fails, the first cell can assist the second cell in link recovery. For example, the terminal device can send the BFRQ information to the network device on uplink resources belonging to the first cell, and the terminal device can receive the BFRR information sent by the network device on downlink resources belonging to the second cell.

[0229] When the transmission direction of the communication system 200 is uplink, the terminal device 220 is the sender and the network device 210 is the receiver. When the transmission direction of the communication system 200 is downlink, the network device 210 is the sender and the terminal device 220 is the receiver.

[0230] Figure 3This application describes a communication system 300. The communication system 300 operates in a dual connectivity (DC) or coordinated multipoint transmission / reception (CoMP) scenario. The system includes a network device 310, a network device 320, and a terminal device 330. Network device 310 is the network device used when the terminal device 330 initially accesses the system and is responsible for RRC communication with the terminal device 330. Network device 320 is added during RRC reconfiguration to provide additional radio resources. The terminal device 330, configured with carrier aggregation, is connected to network devices 310 and 320. The link between network device 310 and the terminal device 330 can be referred to as the first link, and the link between network device 320 and the terminal device 330 can be referred to as the second link.

[0231] When both network device 310 and network device 320 can configure uplink resources for transmitting BFRQ to terminal device 330, if the first link or the second link fails, terminal device 330 can send a BFRQ to network device 310 or network device 320 on the uplink resources used for transmitting BFRQ. After receiving the BFRQ, network device 310 or network device 320 sends a BFRR to terminal device 330.

[0232] Specifically, if the network device 320 is not configured with uplink resources for transmitting BFRQ, then when the second link fails, the terminal device 330 can restore the second link through the network device 310.

[0233] The communication systems described above are merely illustrative examples, and the communication systems applicable to this application are not limited thereto. For example, the number of network devices and terminal devices included in the communication system may be other numbers, or a single base station, multi-carrier aggregation scenario, dual-link scenario, or device-to-device (D2D) communication scenario may be adopted.

[0234] It should be understood that the technical solutions of this application embodiment can be applied to a carrier aggregation scenario where one cell assists another cell or multiple cells in restoring the link. Alternatively, in a dual-link scenario, one cell within a cell group assists another cell or multiple cells in restoring the link.

[0235] It should be understood that the technical solutions of the embodiments of this application can also be applied to single-carrier, carrier aggregation, or dual-link scenarios, where a cell fails to recover its own beam on the resources of that cell.

[0236] It should be understood that the technical solutions in the embodiments of this application can be applied to situations where the primary cell (Pcell) is high-frequency or low-frequency, and the secondary cell (Scell) is high-frequency or low-frequency. For example, when the Pcell is low-frequency and the Scell ​​is high-frequency. In one possible implementation, for an Scell ​​without configured uplink resources, the uplink resources of the Pcell can be used to assist the Scell ​​in restoring the link. Generally, low-frequency and high-frequency are relative terms, but a specific frequency can also be used as the dividing line, such as 6GHz.

[0237] It should be understood that the technical solutions of this application embodiment can also be applied to the coordinated multipoint transmission / reception (CoMP) scenario, where one TRP assists another TRP in restoring the link. CoMP can be one or more of the following scenarios: non-coherent joint transmission (NCJT), coherent joint transmission (CJT), and joint transmission (JT).

[0238] The terminal device in this application embodiment can refer to user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The terminal device can also be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal device in future 5G networks, or terminal device in future evolved public land mobile networks (PLMNs), etc., and this application embodiment does not limit this to these categories.

[0239] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0240] Furthermore, in this embodiment, the terminal device can also be a terminal device in an Internet of Things (IoT) system. IoT is an important component of future information technology development, and its main technical feature is connecting objects to networks through communication technologies, thereby realizing an intelligent network of human-machine interconnection and machine-to-machine interconnection. In this embodiment, IoT technology can achieve massive connectivity, deep coverage, and low terminal power consumption through technologies such as narrowband (NB) technology.

[0241] In addition, in the embodiments of this application, the terminal device may also include sensors such as smart printers, train detectors, and gas stations. Its main functions include collecting data (for some terminal devices), receiving control information and downlink data from network devices, and sending electromagnetic waves to transmit uplink data to network devices.

[0242] The network device in this application embodiment can be a device for communicating with terminal devices. The network device can be a base station (BTS) in a global system for mobile communications (GSM) or code division multiple access (CDMA) system, a base station (NodeB, NB) in a wideband code division multiple access (WCDMA) system, an evolved base station (eNB, eNodeB) in an LTE system, a radio controller in a cloud radio access network (CRAN) scenario, or a relay station, access point, vehicle-mounted device, wearable device, or a network device in a future 5G network or a network device in a future evolved PLMN network, etc. The embodiments of this application are not limited.

[0243] The network device in this application embodiment can be a device in a wireless network, such as a radio access network (RAN) node that connects a terminal to the wireless network. Examples of RAN nodes include: base stations, next-generation base stations (gNBs), transmission reception points (TRPs), evolved Node Bs (eNBs), home base stations, baseband units (BBUs), or access points (APs) in a WiFi system. In a network architecture, the network device may include a centralized unit (CU) node, a distributed unit (DU) node, or a RAN device comprising both CU and DU nodes.

[0244] This application is primarily applied to 5G NR systems. However, it can also be applied to other communication systems, as long as one entity needs to send transmission direction indication information, and another entity needs to receive this indication information and determine the transmission direction within a certain time period based on it. For example... Figure 4 This is an example diagram of a communication system provided in an embodiment of this application. Figure 3As shown, a base station and terminal devices 1 to 6 form a communication system. In this system, terminal devices 1 to 6 can send uplink data to the base station, and the base station receives the uplink data sent by terminal devices 1 to 6. The base station can also send downlink data to terminal devices 1 to 6, and terminal devices 1 to 6 receive the downlink data. Alternatively, terminal devices 4 to 6 can also form a communication system. In this system, terminal device 5 can receive uplink information sent by terminal device 4 or terminal device 6, and terminal device 5 can send downlink information to terminal device 4 or terminal device 6.

[0245] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and artificial satellites. The embodiments of this application do not limit the application scenarios of the network devices and terminal devices.

[0246] Network devices and terminal devices can communicate using licensed spectrum, unlicensed spectrum, or both simultaneously. They can also communicate using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used between network devices and terminal devices.

[0247] In the embodiments of this application, the time-domain symbol can be an orthogonal frequency division multiplexing (OFDM) symbol or a single carrier-frequency division multiplexing (SC-FDM) symbol. Unless otherwise specified, the symbols in the embodiments of this application refer to time-domain symbols.

[0248] It is understood that in the embodiments of this application, PDSCH, PDCCH and PUSCH are only examples of downlink data channels, downlink control channels and uplink data channels. In different systems and different scenarios, data channels and control channels may have different names, and the embodiments of this application do not limit this.

[0249] Next, the method for sending beam failure recovery requests will be explained in detail. Figure 5This is a flowchart illustrating a method for sending a beam failure recovery request, provided as an embodiment of this application. Figure 5 As shown, the method may include:

[0250] S501, The terminal device determines the first resource.

[0251] After a terminal device determines that a beam has failed, it needs to send a beam failure recovery request to the network device. In some embodiments, the terminal device first determines a first resource for sending the beam failure recovery request, and then sends the beam failure recovery request on the first resource, thereby reducing beam failure recovery latency by limiting the PUSCH resources used for BFRQ transmission.

[0252] It should be understood that the process of the terminal device determining beam failure can be referred to in S101, and will not be repeated here.

[0253] For example, such as Figure 6 As shown, the terminal device can determine the first resource using any one of the following methods S501a to S501d.

[0254] S501a, The terminal device determines the first resource based on the beam failure event counter.

[0255] In some embodiments, network devices can configure beam failure detection parameters for the cell to which the terminal device belongs via RRC signaling or MAC-CE signaling. The beam failure detection parameters include the maximum number of beam failure instances (beamFailureInstanceMaxCount). The terminal device maintains a beam failure instance counter (BFI counter) for a cell or a cell group to detect beam failures. When the BFI counter is 0, it indicates that no beam failures have occurred in that cell or cell group, and the link quality of that cell or cell group is good. Therefore, the terminal device can select the resources of the cell with a beam failure instance counter of 0 as the first resource.

[0256] It should be understood that a cell group may include one or more cells. A cell group may refer to an MCG or an SCG. A cell group may also be configured by network devices, or it may be indicated or determined by other means. There may be other definitions or indication methods for cell groups, and the embodiments of this application do not limit the definition or indication method of cell groups.

[0257] It should be understood that the specific usage of the BFI counter can be found in S101, and will not be repeated here.

[0258] S501b: The terminal device determines the first resource based on the subcarrier spacing.

[0259] In some embodiments, the terminal device may receive one or more indication messages sent by the network device, which indicate K resources, such as PUSCH resources. Alternatively, the network device may pre-configure K resources for the terminal device. Here, K is an integer, K≥1. Optionally, a resource may refer to an orthogonal frequency division multiplexing (OFDM) symbol in a time unit. A time unit may refer to a time slot, sub-time slot, micro-time slot, etc. The K resources may be frequency division multiplexing resources, time division multiplexing resources, or code division multiplexing resources.

[0260] Since a larger subcarrier spacing results in a shorter OFDM symbol length, the resource with the largest subcarrier spacing can complete transmission relatively quickly. Therefore, the terminal device can select the resource with the largest subcarrier spacing among K resources as the first resource to complete the transmission of beam failure requests more quickly.

[0261] The terminal device can determine the first resource based on the subcarrier spacing, and the subcarrier spacing of the first resource is the largest among the subcarrier spacings of the K resources.

[0262] Alternatively, it can be described that the terminal device determines the first resource based on the subcarrier spacing, wherein the subcarrier spacing of the unit carrier to which the first resource belongs is the largest among the subcarrier spacings of the unit carriers to which the K resources belong.

[0263] Alternatively, it can be described that the terminal device determines the first resource based on the subcarrier spacing, wherein the subcarrier spacing of the cell to which the first resource belongs is the largest among the subcarrier spacings of the cells to which the K resources belong.

[0264] S501c: The terminal device determines the first resource based on the duplicate identifier.

[0265] In some embodiments, the network device configures resources carrying duplicate identifiers for the terminal device via RRC signaling, MAC-CE signaling, or DCI signaling. The terminal device can identify the resource carrying the duplicate identifier as a first resource. The duplicate identifier indicates that the resource can be used to repeatedly transmit multiple identical pieces of information. Alternatively, the resource carrying the duplicate identifier has high transmission reliability, or it can be used for URLLC service transmission, and the resources allocated for this service need to guarantee high reliability and low latency transmission. Therefore, transmitting beam failure requests on resources carrying duplicate identifiers can ensure the reliability of beam failure request transmission, complete beam failure recovery in a timely manner, and reduce beam failure recovery latency.

[0266] Resources carrying duplicate identifiers can also be described as resources configured with duplicate identifiers or resources configured with duplicate identifier parameters. A duplicate identifier can also be called an "aggregation factor".

[0267] In other words, the terminal device can determine the first resource based on the aggregation factor, which is configured with an aggregation factor. This aggregation factor indicates the number of times the data or information carried by the PUSCH resource is repeated. Understandably, this number of repetitions is generally greater than 1.

[0268] S501d: The terminal device determines the first resource according to the modulation and coding scheme.

[0269] In some embodiments, the network device configures L resources for the terminal device via RRC signaling, MAC-CE signaling, or DCI signaling, and also indicates the corresponding modulation and coding schemes for the L resources, where L is an integer and L≥1. The terminal device can select the resource with the smallest modulation and coding scheme among the L resources as the first resource. Since a smaller modulation and coding scheme employs a low-order modulation scheme and a low-rate channel coding scheme to ensure communication quality, selecting a smaller modulation and coding scheme can ensure the transmission reliability of beam failure recovery requests, thereby avoiding retransmission of beam failure recovery requests and reducing beam failure recovery latency. Optionally, the modulation and coding scheme corresponding to the first resource can refer to the modulation and coding scheme indicated by the indication information of the first resource.

[0270] Optionally, the "modulation coding method" in the embodiments of this application can also be replaced by "modulation order" or "code rate".

[0271] It should be noted that the rules described in S501a to S501d above can be used in combination or individually, and this application does not limit them.

[0272] In other embodiments, S501a and S501b can be used in combination. For example, if the terminal device selects resources from two or more cells where the beam failure instance counter is 0, the terminal device can select the resource with the largest subcarrier spacing among the resources of the cells where the beam failure instance counter is 0 as the first resource.

[0273] In some other possible implementations, S501a and S501c can be used in combination. For example, if the terminal device selects resources from two or more cells where the beam failure instance counter is 0, the terminal device can select the resource with the aggregation factor configured among the resources of the cells where the beam failure instance counter is 0 as the first resource.

[0274] In some other possible implementations, S501a and S501d can be used in combination. For example, if the terminal device selects resources of two or more cells with a beam failure instance counter of 0, the terminal device can select the resource with the smallest modulation and coding scheme among the resources of the cells with a beam failure instance counter of 0 as the first resource.

[0275] In other embodiments, any two or three of S501a, S501b, S501c, and S501d can be used in combination, or all four can be used in combination. When multiple rules are used in combination, it is necessary to define which rule takes precedence (i.e., which rule is used first to select resources).

[0276] Optionally, the priority of S501a is higher than the priority of at least one of the following rules: S501b, S501c, and S501d. For example, if S501a, S501b, S501c, and S501d all exist, then S501a has the highest priority.

[0277] Optionally, S501b has a higher priority than S501c and S501d; or S501b has a higher priority than S501c or S501d.

[0278] Optionally, S501c has a higher priority than S501d.

[0279] Terminal devices can first select resources based on the rules with higher priority. If there are multiple resources available for a given resource, then select the resource from among those multiple resources based on the rules with the next higher priority, and so on.

[0280] Examples include: S501a, S501b, and S501c used in combination, or S501a, S501b, and S501d used in combination. For instance, if the terminal device selects two or more resources with the largest subcarrier spacing from the resources of cells with a beam failure event counter of 0, the terminal device can also determine the first resource based on the repetition identifier or modulation coding scheme. For example, the resource with the smallest repetition identifier or modulation coding scheme among the two or more resources with the largest subcarrier spacing is determined as the first resource.

[0281] After the terminal device determines the first resource for sending beam failure recovery request, it executes S502.

[0282] S502, The terminal device sends N beam failure recovery requests on the first resource.

[0283] The terminal device can repeatedly send beam failure recovery requests. This beam failure recovery request information can be carried on the MAC-CE.

[0284] For example, the terminal device sends N identical MAC-CEs carrying beam failure recovery request information on one or more PUSCH resources. Here, N is an integer greater than or equal to 1.

[0285] Understandably, in one possible implementation, the first resource belongs to a first time unit, and the terminal device can repeatedly transmit the first resource N times within the first time unit, with each first resource carrying one or more beam failure recovery requests. For example, the terminal device can repeatedly transmit the first resource N times within N first time units, with each first resource carrying one beam failure recovery request.

[0286] N beam failure recovery requests can be sent simultaneously or in time-division format.

[0287] In one possible implementation, N is an integer greater than 1, and N beam failure recovery requests are sent on a single first resource. In another possible implementation, N is an integer greater than 1, and N beam failure recovery requests are sent on multiple first resources respectively. For example: N beam failure recovery requests are sent on multiple first resources respectively.

[0288] In one embodiment, N>1, and N beam failure recovery requests are independently encoded. By repeatedly sending multiple beam failure recovery requests, the reliability of beam failure recovery request transmission is improved. Independent encoding means that two pieces of information are independently encoded before transmission, resulting in two bit sequences. These two encoded bit sequences are then mapped to different time-frequency-space resources (at least one of the time-domain, frequency-domain, and spatial-domain resources is different), and sent by one device to another. The other device receives these and decodes the two bit sequences on the two resources to obtain the two pieces of information. For example, the first information and the second information. Independent encoding also means that the first and second information are encoded separately. For example, the first information is represented by Q1 bits, and the second information by Q2 bits. The terminal device encodes the Q1 bits to obtain Q1' bits and the Q2 bits to obtain Q2' bits. The terminal device sends the Q1' bits and Q2' bits to the network device. The network device decodes the Q1' bits to obtain the first information and decodes the Q2' bits to obtain the second information.

[0289] In other embodiments, when N>1, the N beam failure recovery requests are identical. The N beam failure recovery requests being identical means that the content of the N beam failure recovery requests is exactly the same.

[0290] It should be understood that in various embodiments of this application, the beam failure recovery request can be used to indicate the cell information of the beam failure cell. The beam failure recovery request may include the identification information of the beam failure cell and / or the reference signal information for recovering the beam failure cell. Alternatively, the cell information of the beam failure cell may include the identification information of the beam failure cell and / or the reference signal information for recovering the beam failure cell. The terminal device can transmit the beam failure recovery request to the network device on the MAC-CE. It should be understood that in various embodiments of this application, the identification information of the beam failure cell may be the identifier of the beam failure cell, or it may be the index of the beam failure cell, or it may be indication information indicating the identifier of the beam failure cell (e.g., indicating the cell identifier through a bitmap, where each bit in the bitmap corresponds to a cell. When the bit is 1, the cell corresponding to that bit has experienced beam failure; when the bit is 0, the cell corresponding to that bit has not experienced beam failure).

[0291] It should be understood that, in the various embodiments of this application, the reference signal information for recovering a beam-failed cell may be a reference signal resource index for recovering a beam-failed cell, or it may be a reference signal resource index for recovering a beam-failed cell and the signal quality of the reference signal resource, or it may be indication information of an unidentified reference signal resource for recovering a beam-failed cell. The reference signal resource for recovering a beam-failed cell may be a CSI-RS resource or an SSB resource.

[0292] In other embodiments, N is predefined or configured. Predefined can be understood as predefined in a standard or protocol. The terminal device and network device can pre-store the predefined value of N, where N is an integer, N≥1. For example, N=2. When the terminal device needs to send a beam failure recovery request, it can obtain N locally to determine the number of times to send the beam failure recovery request. Configuration can be understood as the network device configuring the value of N for the terminal device via signaling. The signaling can be RRC signaling, MAC-CE signaling, or DCI signaling.

[0293] In other embodiments, the terminal device can adjust N according to the transmission code rate of the uplink grant. For example, N is determined based on the MCS. The MCS can be indicated by indication information indicating PUSCH (such as DCI), or by other information such as RRC signaling, MAC-CE, or system information. When the MCS is greater than or equal to a preset threshold, N = P; when the MCS is less than the preset threshold, N = Q; where P and Q are both integers, P ≥ 0, Q ≥ 0, P ≥ Q. For example, P = 2, Q = 1. The preset threshold can be configured by the network device or predefined by the protocol. Optionally, "MCS" in the embodiments of this application can also be replaced by "modulation order" or "code rate".

[0294] S503, network devices determine the primary resource.

[0295] Network devices can determine the first resource based on at least one of the following parameters: beam failure event counter, subcarrier spacing, repetition identifier, and modulation and coding scheme. For a detailed explanation, please refer to the description in S501, which will not be repeated here.

[0296] In some embodiments, determining the first resource is an optional step for the network device.

[0297] S504, The network device receives N beam failure recovery requests on the first resource.

[0298] After receiving N beam failure recovery requests, the network device independently decodes each request. For example, the network device decodes two bit sequences on two resources to obtain two pieces of information, such as the first and second information. Independent encoding means that the first and second information are encoded separately. For example, if the first information is represented by Q1 bits and the second information by Q2 bits, the terminal device encodes the Q1 bits to obtain Q1' bits and the Q2 bits to obtain Q2' bits. The terminal device then sends these Q1' and Q2' bits to the network device. The network device decodes the Q1' bits to obtain the first information and decodes the Q2' bits to obtain the second information.

[0299] The method for transmitting beam failure recovery requests provided in this application improves transmission reliability and reduces beam failure recovery latency by limiting the PUSCH resources for BFRQ transmission or by transmitting multiple identical BFRQs.

[0300] In some embodiments, the terminal device may select a first resource from the second resource to send link failure recovery request information according to the method described above.

[0301] It should be understood that the resources that support N duplicate BFRQs can be generated in the following possible ways:

[0302] Method 1: The terminal device can select one of the PUSCH resources in the network device configuration or instruction in S104 to send N duplicate BFRQs (also known as N identical BFRQ MAC-CEs). Optionally, the N duplicate BFRQ messages are encoded independently.

[0303] Method 2: The terminal device can select multiple PUSCH resources in the network device configuration or instruction in S104 to send N duplicate BFRQs (also known as N identical BFRQ MAC-CEs). For example, the terminal device selects 2 PUSCH resources to carry 2 BFRQ MAC-CEs respectively.

[0304] For both Mode 1 and Mode 2, the step of the terminal device selecting PUSCH resources to send beam failure recovery request information according to preset rules is optional. That is, the terminal device may choose not to perform this step. In this case, the PUSCH resources selected by the terminal device can depend on the implementation of the terminal device.

[0305] Method 3: The terminal device carries the N identical BFRQs on the first resource determined in S501. The first resource may be determined by the terminal device from the second resource according to the method described in S501.

[0306] It should be noted that this embodiment may also include other steps, such as beam failure detection, as detailed in S101. The network device may also configure a second resource for the terminal device, and the terminal device may select one or more resources from the second resource as the first resource, sending N beam failure recovery requests on the first resource. The method by which the terminal device obtains the second resource can be found in the description of S104 in the above embodiment, and will not be repeated here.

[0307] It should be understood that in the various embodiments of this application, "N identical BFRQs", "N beam failure recovery requests" and "N duplicate BFRQs" can be simply referred to as second request information.

[0308] The method for transmitting beam failure recovery requests provided in this application improves the reliability of information transmission and reduces the information transmission latency by limiting the resources used to transmit link failure recovery request information, thereby achieving highly reliable and low-latency link failure recovery.

[0309] Figure 7 This is a flowchart illustrating a method for sending a beam failure recovery request, provided as an embodiment of this application. Figure 7 As shown, the method may include:

[0310] S701, The terminal device determines that the beam connection between the terminal device and the network device has failed.

[0311] In some embodiments, the terminal device can measure the beamfailure detection reference signal resource set (RS set) to determine a beam failure between the terminal device and the network device. A detailed explanation can be found in S101, and will not be repeated here.

[0312] S702, Terminal equipment identifies new links.

[0313] In some embodiments, the terminal device can identify a reference signal in the candidate beam identification RS set. The terminal device can restore the link based on the reference signal. A detailed explanation can be found in S102, and will not be repeated here.

[0314] S703, The terminal device sends N beam failure recovery requests.

[0315] The terminal device may send the beam failure recovery request two or more times. The beam failure recovery request information may be carried on the MAC-CE.

[0316] For example, the terminal device sends N identical MAC-CEs carrying beam failure recovery request information on one or more PUSCH resources. Here, N is an integer greater than or equal to 2. The N beam failure recovery requests are independently encoded. N is predefined or configured. Alternatively, N is determined according to the MCS. A detailed explanation can be found in S502, and will not be repeated here.

[0317] S704, The network device receives N beam failure recovery requests.

[0318] S705, The network device sends a beam failure recovery response to the terminal device.

[0319] S706. The terminal device receives the beam failure recovery response sent by the network device.

[0320] The method for sending beam failure recovery requests provided in this application improves the reliability of the information transmission and reduces the information transmission latency by repeatedly sending the beam failure recovery request information, thereby achieving highly reliable and low-latency link failure recovery.

[0321] It is understood that, in order to achieve the functions in the above embodiments, the network device and terminal device include hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0322] Figure 8 and Figure 9The diagram illustrates the possible structures of communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of terminal devices or network devices in the above method embodiments, and thus also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device may be as follows: Figure 2 The terminal device 220 shown can also be as follows: Figure 2 The network device 210 shown can also be a module (such as a chip) applied to terminal devices or network devices.

[0323] like Figure 8 As shown, the communication device 800 includes a processing unit 810 and a transceiver unit 820. The communication device 800 is used to implement the above-mentioned... Figures 5-7 The methods illustrated in this embodiment demonstrate the functions of the terminal device or network device.

[0324] When the communication device 800 is used to implement Figure 5 In the method embodiment shown, the terminal device functions as follows: the transceiver unit 820 is used to execute S502; the processing unit 810 is used to execute S501.

[0325] When the communication device 800 is used to implement Figure 5 In the method embodiment shown, the network device functions as follows: the transceiver unit 820 is used to execute S504; the processing unit 810 is used to execute S503.

[0326] When the communication device 800 is used to implement Figure 6 In the method embodiment shown, the terminal device functions as follows: the transceiver unit 820 is used to execute S502; the processing unit 810 is used to execute S501a to S501d.

[0327] When the communication device 800 is used to implement Figure 6 In the method embodiment shown, the network device functions as follows: the transceiver unit 820 is used to execute S504; the processing unit 810 is used to execute S503.

[0328] When the communication device 800 is used to implement Figure 7 In the method embodiment shown, the terminal device functions as follows: the transceiver unit 820 is used to execute S703 and S706; the processing unit 810 is used to execute S701 to S702.

[0329] When the communication device 800 is used to implement Figure 7 In the method embodiment shown, the network device functions as follows: the transceiver unit 820 is used to execute S704 and S705.

[0330] For a more detailed description of the processing unit 810 and the transceiver unit 820, please refer to [link / reference needed]. Figures 5-7 The relevant descriptions in the method embodiments shown are directly obtained and will not be repeated here.

[0331] like Figure 9 As shown, the communication device 900 includes a processor 910 and an interface circuit 920. The processor 910 and the interface circuit 920 are coupled to each other. It is understood that the interface circuit 920 can be a transceiver or an input / output interface. Optionally, the communication device 900 may also include a memory 930 for storing instructions executed by the processor 910, or storing input data required by the processor 910 to execute instructions, or storing data generated after the processor 910 executes instructions.

[0332] When the communication device 900 is used to achieve Figures 5-7 In the method shown, the processor 910 is used to perform the functions of the processing unit 810, and the interface circuit 920 is used to perform the functions of the transceiver unit 820.

[0333] When the aforementioned communication device is a chip applied to a terminal device, the terminal device chip implements the functions of the terminal device in the above method embodiments. The terminal device chip receives information from other modules (such as an RF module or antenna) in the terminal device, the information being sent to the terminal device by the network device; or, the terminal device chip sends information to other modules (such as an RF module or antenna) in the terminal device, the information being sent to the network device by the terminal device.

[0334] When the aforementioned communication device is a chip applied to a network device, the network device chip implements the functions of the network device in the above method embodiments. The network device chip receives information from other modules (such as radio frequency modules or antennas) in the network device, which is information sent from the terminal device to the network device; or, the network device chip sends information to other modules (such as radio frequency modules or antennas) in the network device, which is information sent from the network device to the terminal device.

[0335] It is understood that the processor in the embodiments of this application may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0336] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Additionally, the ASIC can reside in a network device or a terminal device. Alternatively, the processor and storage medium can exist as discrete components in the network device or terminal device.

[0337] Through the above description of the implementation methods, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0338] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0339] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0340] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0341] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video disc (DVD); or it can be a semiconductor medium, such as a solid-state drive (SSD).

[0342] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0343] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects.

[0344] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0345] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for sending a beam failure recovery request, characterized in that, include: The first resource, which is the Physical Uplink Shared Channel (PUSCH) resource, is determined through one or more of the following methods: Method 1: Determine the first resource based on the beam failure instance counter, wherein the beam failure instance counter of the cell to which the first resource belongs is 0; Method 2: Determine the first resource based on the subcarrier spacing, wherein the subcarrier spacing of the first resource is the largest among the subcarrier spacings of the K resources, where K is an integer and K≥1; Method 3: Determine the first resource based on the duplicate identifier. The first resource is configured with a duplicate identifier. The duplicate identifier indicates that the first resource configured with the duplicate identifier is used to repeatedly transmit multiple identical pieces of information, or the duplicate identifier indicates that the transmission reliability of the first resource configured with the duplicate identifier is high, or the duplicate identifier indicates that the first resource configured with the duplicate identifier is used for the transmission of URLLC services. Method 4: Determine the first resource based on the modulation and coding scheme, wherein the modulation and coding scheme corresponding to the first resource is the smallest among the modulation and coding schemes corresponding to the L resources, where L is an integer and L≥1; Sending N beam failure recovery requests on the first resource, where N is an integer greater than or equal to 1, wherein when N≥2, sending N beam failure recovery requests on the first resource includes: sending the N beam failure recovery requests on one PUSCH resource included in the first resource, or sending the N beam failure recovery requests on multiple PUSCH resources included in the first resource.

2. The method according to claim 1, characterized in that, The repeat identifier also indicates the number of times the data or information carried by the first resource is repeated.

3. The method according to claim 1, characterized in that, N is either predefined or configured.

4. The method according to claim 1, characterized in that, The N is determined based on the modulation and coding scheme (MCS).

5. The method according to claim 4, characterized in that, The N is determined according to the MCS, including: When the MCS is greater than or equal to a preset threshold, N = P; when the MCS is less than the preset threshold, N = Q; wherein, P and Q are both integers, P ≥ 0, Q ≥ 0, and P ≥ Q.

6. The method according to claim 1, characterized in that, When N>1, the N beam failure recovery requests are independently encoded.

7. The method according to claim 1, characterized in that, When N>1, the N beam failure recovery requests are the same.

8. A method for receiving a beam failure recovery request, characterized in that, include: The first resource, which is the Physical Uplink Shared Channel (PUSCH) resource, is determined through one or more of the following methods: Method 1: Determine the first resource based on the beam failure instance counter, wherein the beam failure instance counter of the cell to which the first resource belongs is 0; Method 2: Determine the first resource based on the subcarrier spacing, wherein the subcarrier spacing of the first resource is the largest among the subcarrier spacings of the K resources, where K is an integer and K≥1; Method 3: Determine the first resource based on the duplicate identifier. The first resource is configured with a duplicate identifier. The duplicate identifier indicates that the first resource configured with the duplicate identifier is used to repeatedly transmit multiple identical pieces of information, or the duplicate identifier indicates that the transmission reliability of the first resource configured with the duplicate identifier is high, or the duplicate identifier indicates that the first resource configured with the duplicate identifier is used for the transmission of URLLC services. Method 4: Determine the first resource based on the modulation and coding scheme, wherein the modulation and coding scheme corresponding to the first resource is the smallest among the modulation and coding schemes corresponding to the L resources, where L is an integer and L≥1; Receiving N beam failure recovery requests on the first resource, where N is an integer greater than or equal to 1, wherein when N≥2, receiving N beam failure recovery requests on the first resource includes: receiving the N beam failure recovery requests on one PUSCH resource included in the first resource, or receiving the N beam failure recovery requests on multiple PUSCH resources included in the first resource.

9. A communication device, characterized in that, include: The processing unit is configured to determine a first resource, wherein the first resource is a Physical Uplink Shared Channel (PUSCH) resource, through one or more of the following methods: Method 1: Determine the first resource based on the beam failure instance counter, wherein the beam failure instance counter of the cell to which the first resource belongs is 0; Method 2: Determine the first resource based on the subcarrier spacing, wherein the subcarrier spacing of the first resource is the largest among the subcarrier spacings of the K resources, where K is an integer and K≥1; Method 3: Determine the first resource based on the duplicate identifier. The first resource is configured with a duplicate identifier. The duplicate identifier indicates that the first resource configured with the duplicate identifier is used to repeatedly transmit multiple identical pieces of information, or the duplicate identifier indicates that the transmission reliability of the first resource configured with the duplicate identifier is high, or the duplicate identifier indicates that the first resource configured with the duplicate identifier is used for the transmission of URLLC services. Method 4: Determine the first resource based on the modulation and coding scheme, wherein the modulation and coding scheme corresponding to the first resource is the smallest among the modulation and coding schemes corresponding to the L resources, where L is an integer and L≥1; The transmitting unit is configured to transmit N beam failure recovery requests on the first resource, where N is an integer greater than or equal to 1. When N ≥ 2, transmitting N beam failure recovery requests on the first resource includes: transmitting the N beam failure recovery requests on one PUSCH resource included in the first resource, or transmitting the N beam failure recovery requests on multiple PUSCH resources included in the first resource.

10. The apparatus according to claim 9, characterized in that, The repeat identifier also indicates the number of times the data or information carried by the first resource is repeated.

11. The apparatus according to claim 9, characterized in that, N is either predefined or configured.

12. The apparatus according to claim 9, characterized in that, The N is determined according to the MCS.

13. The apparatus according to claim 12, characterized in that, The N is determined according to the MCS, including: When the MCS is greater than or equal to a preset threshold, N = P; when the MCS is less than the preset threshold, N = Q; wherein, P and Q are both integers, P ≥ 0, Q ≥ 0, and P ≥ Q.

14. The apparatus according to claim 9, characterized in that, When N>1, the N beam failure recovery requests are independently encoded.

15. The apparatus according to claim 9, characterized in that, When N>1, the N beam failure recovery requests are the same.

16. A communication device, characterized in that, include: The processing unit is configured to determine a first resource, wherein the first resource is a Physical Uplink Shared Channel (PUSCH) resource, through one or more of the following methods: Method 1: Determine the first resource based on the beam failure instance counter, wherein the beam failure instance counter of the cell to which the first resource belongs is 0; Method 2: Determine the first resource based on the subcarrier spacing, wherein the subcarrier spacing of the first resource is the largest among the subcarrier spacings of the K resources, where K is an integer and K≥1; Method 3: Determine the first resource based on the duplicate identifier. The first resource is configured with a duplicate identifier. The duplicate identifier indicates that the first resource configured with the duplicate identifier is used to repeatedly transmit multiple identical pieces of information, or the duplicate identifier indicates that the transmission reliability of the first resource configured with the duplicate identifier is high, or the duplicate identifier indicates that the first resource configured with the duplicate identifier is used for the transmission of URLLC services. Method 4: Determine the first resource based on the modulation and coding scheme, wherein the modulation and coding scheme corresponding to the first resource is the smallest among the modulation and coding schemes corresponding to the L resources, where L is an integer and L≥1; A receiving unit is configured to receive N beam failure recovery requests on the first resource, where N is an integer greater than or equal to 1. Specifically, when N ≥ 2, receiving the N beam failure recovery requests on the first resource includes: receiving the N beam failure recovery requests on one PUSCH resource included in the first resource, or receiving the N beam failure recovery requests on multiple PUSCH resources included in the first resource.

17. A communication device, characterized in that, include: At least one processor, a memory, and a bus, wherein the memory is used to store a computer program such that when the computer program is executed by the at least one processor, it implements the method for transmitting a beam failure recovery request as described in any one of claims 1-7, or implements the method for receiving a beam failure recovery request as described in claim 8.

18. A computer-readable storage medium, characterized in that, include: Computer software instructions; When the computer software instructions are executed in the communication device or in a chip built into the communication device, the communication device performs the method of transmitting beam failure recovery request as described in any one of claims 1-7, or implements the method of receiving beam failure recovery request as described in claim 8.

Images