[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

CN114073146A - Method and device for sending beam failure recovery request - Google Patents

Method and device for sending beam failure recovery request Download PDF

Info

Publication number
CN114073146A
CN114073146A CN201980098115.XA CN201980098115A CN114073146A CN 114073146 A CN114073146 A CN 114073146A CN 201980098115 A CN201980098115 A CN 201980098115A CN 114073146 A CN114073146 A CN 114073146A
Authority
CN
China
Prior art keywords
resource
beam failure
failure recovery
terminal device
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN201980098115.XA
Other languages
Chinese (zh)
Inventor
张荻
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of CN114073146A publication Critical patent/CN114073146A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Disclosed are a method and a device for sending a beam failure recovery request, relating to the field of communication and solving the problem of long time delay of beam failure recovery. The method comprises the following steps: a specific PUSCH resource is selected on which to transmit at least one beam failure recovery request. Or, at least two beam failure recovery requests are transmitted on any PUSCH resource. Therefore, the PUSCH resource transmitted by the MAC-CE is limited or the transmission reliability is improved by transmitting a plurality of same MAC-CEs, and the beam failure recovery time delay is reduced.

Description

Method and device for sending beam failure recovery request Technical Field
The embodiment of the application relates to the field of communication, in particular to a method and a device for sending a beam failure recovery request.
Background
In order to cope with explosive mobile data traffic increase, massive mobile communication device connection, and various new services and application scenarios which are continuously emerging in the future, the fifth generation (5G) mobile communication system is produced, and the 5G mobile communication system is also called a new radio access technology (NR) system.
In the NR system, a signal transmission mechanism based on a beamforming technology is introduced, that is, the signal transmission power is increased by increasing the antenna gain, so as to compensate for the path loss of a wireless signal in the process of transmitting the wireless signal between the network device and the terminal device in a high-frequency band. However, due to poor diffraction capability of the wireless signal in the high frequency channel, there may be a case where the wireless signal is blocked and cannot be transmitted further. In order to prevent a case where a wireless signal is blocked to cause a sudden interruption of communication from occurring, the terminal device may measure the communication quality of a beam failure detection reference signal (BFD RS) configured by the network device to determine whether a beam failure occurs. When the terminal device determines that a beam fails, a beam failure recovery request (BFRQ) is sent to the network device on an arbitrary Physical Uplink Shared Channel (PUSCH) so as to recover a failed link. If the BFRQ transmission fails, the terminal equipment needs to retransmit the BFRQ to ensure the BFRQ transmission is successful, so that the beam failure recovery time delay is increased.
Disclosure of Invention
The embodiment of the application provides a method and a device for sending a beam failure recovery request, which solve the problem of long time delay of beam failure recovery.
In order to achieve the purpose, the technical scheme is as follows:
in a first aspect, the present application provides a method for sending a beam failure recovery request, where the method is applicable to a terminal device, or the method is applicable to a communication apparatus that can support the terminal device to implement the method, for example, the communication apparatus includes a chip system, and the method includes: first, a first resource is determined, and N BFRQ are sent on the first resource, wherein N is an integer greater than 1 or equal to 1. According to the method for sending the beam failure recovery request, the transmission reliability is improved by limiting the PUSCH resource transmitted by the BFRQ or sending a plurality of same BFRQ, and the beam failure recovery time delay is reduced.
In a second aspect, the present application provides a method for receiving a beam failure recovery request, where the method is applicable to a network device, or the method is applicable to a communication apparatus that can support the network device to implement the method, for example, the communication apparatus includes a chip system, and the method includes: first, a first resource is determined, and N BFRQ are received on the first resource, wherein N is an integer greater than 1 or equal to 1. According to the method for receiving the beam failure recovery request, the transmission reliability is improved by limiting the PUSCH resource transmitted by the BFRQ or receiving a plurality of same BFRQ, and the beam failure recovery time delay is reduced.
In one possible implementation, determining the first resource includes: and determining the first resource according to the beam failure case counter, wherein the beam failure case counter of the cell to which the first resource belongs is 0. When the beam failure case counter is 0, the situation that the beam failure does not occur in the cell or the cell group is shown, and the link quality of the cell or the cell group is good, so the terminal device can select the resource of the cell with the beam failure case counter of 0 to determine as the first resource.
In another possible implementation, determining the first resource includes: and determining a first resource according to the subcarrier interval, wherein the subcarrier interval of the first resource is the largest among the subcarrier intervals of K resources, K is an integer and is more than or equal to 1. Since the larger the subcarrier spacing, the shorter one OFDM symbol length. The resources of the largest subcarrier spacing can be transmitted faster. Therefore, the terminal device may select the resource of the largest subcarrier interval among the subcarrier intervals of the K resources to determine as the first resource, so as to complete transmission of the beam failure request more quickly.
In another possible implementation, determining the first resource includes: and determining a first resource according to the repeated identifier, wherein the repeated identifier is configured for the first resource. The duplicate identification indicates that the resource can be used to repeatedly transmit multiple identical information. Or the transmission reliability of the resource carrying the repeated identifier is higher, or the resource carrying the repeated identifier can be used for the transmission of the URLLC service, and the resource allocated for the service needs to ensure the transmission with high reliability and low delay. Therefore, the beam failure request is transmitted on the resource carrying the repeated identification, so that the reliability of the transmission of the beam failure request can be ensured, the beam failure recovery can be completed in time, and the beam failure recovery time delay can be reduced.
In another possible implementation, determining the first resource includes: and determining a first resource according to the modulation coding mode, wherein the modulation coding mode corresponding to the first resource is the smallest among the modulation coding modes corresponding to the L resources, L is an integer and is more than or equal to 1. Due to the small modulation and coding mode, a low-order modulation mode and a low-rate channel coding scheme are adopted to ensure the communication quality, the transmission reliability of the beam failure recovery request can be ensured by selecting the small modulation and coding mode, the retransmission of the beam failure recovery request is further avoided, and the time delay of the beam failure recovery is reduced. Optionally, the modulation and coding scheme corresponding to the first resource may refer to a modulation and coding scheme indicated by the indication information of the first resource.
In another possible implementation, N is predefined or configured.
In another possible implementation, N is determined according to a Modulation and Coding Scheme (MCS).
In another possible implementation, N is determined according to the MCS, including: when the MCS is greater than or equal to a preset threshold, N is equal to P; when the MCS is smaller than a preset threshold, N is Q; wherein P and Q are integers, P is not less than 0, Q is not less than 0, and P is not less than Q.
In another possible implementation, when N >1, the N beam failure recovery requests are independently coded. By repeatedly transmitting a plurality of beam failure recovery requests, the reliability of beam failure recovery request transmission is improved.
In another possible implementation, when N >1, the N beam failure recovery requests are the same.
In a third aspect, the present application provides a method for sending a beam failure recovery request, where the method is applicable to a terminal device, or the method is applicable to a communication apparatus that can support the terminal device to implement the method, for example, the communication apparatus includes a chip system, and the method includes: sending N BFRQ on the first resource, wherein N is an integer and is more than or equal to 2, and receiving Beam failure recovery response information (which may be called as Beam failure recovery response, BFRR for short). According to the method for sending the beam failure recovery request, the transmission reliability is improved by sending the plurality of same BFRQ, and the beam failure recovery time delay is reduced.
In a fourth aspect, the present application provides a method for receiving a beam failure recovery request, where the method is applicable to a network device, or the method is applicable to a communication apparatus that can support the network device to implement the method, for example, the communication apparatus includes a chip system, and the method includes: receiving N BFRQ on a first resource, wherein N is an integer and is more than or equal to 2; the BFRR is sent. According to the method for receiving the beam failure recovery request, the transmission reliability is improved by receiving a plurality of same BFRQ, and the beam failure recovery time delay is reduced.
In one possible implementation, when N >1, the N beam failure recovery requests are independently encoded, and the N beam failure recovery requests are the same.
In a fifth aspect, the present application further provides a communication device for implementing the method described in the first aspect. The communication apparatus is a communication apparatus that implements the method described in the first aspect for a terminal device or a support terminal device, for example, the communication apparatus includes a system-on-chip. For example, the communication apparatus includes: a processing unit and a transmitting unit. The processing unit is used for determining a first resource; and the sending unit is used for sending N BFRQ on the first resource, wherein N is an integer and is more than or equal to 1.
Optionally, the specific method is the same as that described in the first aspect, and is not described herein again.
In a sixth aspect, the present application further provides a communication device for implementing the method described in the second aspect. The communication apparatus is a network device or a communication apparatus supporting the network device to implement the method described in the second aspect, and for example, the communication apparatus includes a system-on-chip. 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 1 or equal to 1.
Optionally, the specific method is as described in the second aspect, and is not described herein again.
In a seventh aspect, the present application further provides a communication device for implementing the method described in the third aspect. The communication apparatus is a communication apparatus for implementing the method described in the third aspect for a terminal device or a terminal device, for example, the communication apparatus includes a system-on-chip. For example, the communication apparatus includes: a transmitting unit and a receiving unit. The sending unit is used for sending N BFRQ on the first resource, wherein N is an integer and is more than or equal to 2; a receiving unit, configured to receive the BFRR.
Optionally, the specific method is as described in the third aspect, and is not described herein again.
In an eighth aspect, the present application further provides a communication apparatus for implementing the method described in the fourth aspect. The communication apparatus is a network device or a communication apparatus supporting the network device to implement the method described in the fourth aspect, and for example, the communication apparatus includes a system-on-chip. For example, the communication apparatus includes: a receiving unit and a transmitting unit. The receiving unit is used for receiving N BFRQ on the first resource, wherein N is an integer and is more than or equal to 2; the sending unit is configured to send the BFRR.
Optionally, the specific method is the same as that described in the fourth aspect, and is not described herein again.
It should be noted that the functional modules in the fifth aspect and the eighth aspect may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions. E.g. a transceiver for performing the functions of the receiving unit and the transmitting unit, a processor for performing the functions of the processing unit, a memory for the processor to process the program instructions of the methods of the present application. The processor, transceiver and memory are connected by a bus and communicate with each other. In particular, reference may be made to the functionality of the behavior of the terminal device or the network device in the method of the first aspect to the method of the fourth aspect.
In a ninth aspect, the present application further provides a communication device for implementing the method described in the first aspect. The communication apparatus is a terminal device or a communication apparatus supporting the terminal device to implement the method described in the first aspect, and for example, the communication apparatus includes a chip system. For example the communication device comprises a processor for implementing the functionality of the method described in the first 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 may call and execute the program instructions stored in the memory, so as to implement the functions of the method described in the above first aspect. The communication device may further comprise a communication interface for the communication device to communicate with other devices. Illustratively, if the communication device is a terminal device, the other device is a network device.
Optionally, the specific method for sending the beam failure recovery request is the same as that described in the first aspect, and is not described herein again.
In a tenth aspect, the present application further provides a communication device for implementing the method described in the second aspect. The communication apparatus is a network device or a communication apparatus supporting the network device to implement the method described in the second aspect, for example, a system-on-chip included in the communication apparatus. For example the communication device comprises 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, so as to implement the functions in the method described in the second aspect. The communication device may further comprise a communication interface for the communication device to communicate with other devices. Illustratively, if the communication device is a network device, the other device is a terminal device.
Optionally, the specific method for receiving the beam failure recovery request is as described in the second aspect, and is not described herein again.
In an eleventh aspect, the present application further provides a communication device for implementing the method described in the third aspect. The communication apparatus is a terminal device or a communication apparatus supporting the terminal device to implement the method described in the third aspect, and for example, the communication apparatus includes a chip system. For example the communication device comprises a processor for implementing the functionality 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 may call and execute the program instructions stored in the memory for implementing the functions in the method described in the third aspect. The communication device may further comprise a communication interface for the communication device to communicate with other devices. Illustratively, if the communication device is a terminal device, the other device is a network device.
Optionally, the specific method for sending the beam failure recovery request is as described in the third aspect, and is not described herein again.
In a twelfth aspect, the present application further provides a communication apparatus for implementing the method described in the fourth aspect. The communication apparatus is a network device or a communication apparatus supporting the network device to implement the method described in the fourth aspect, for example, a system-on-chip included in the communication apparatus. For example, the communication device comprises 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, so as to implement the functions in the method described in the above fourth aspect. The communication device may further comprise a communication interface for the communication device to communicate with other devices. Illustratively, if the communication device is a network device, the other device is a terminal device.
Optionally, a specific method for receiving the beam failure recovery request is as described in the fourth aspect, and is not described herein again.
In a thirteenth aspect, the present application further provides a computer-readable storage medium comprising: computer software instructions; the computer software instructions, when executed in the communication device, cause the communication device to perform the method of any of the first to fourth aspects described above.
In a fourteenth aspect, the present application also provides a computer program product comprising instructions which, when run in a communication apparatus, causes the communication apparatus to perform the method of any of the first to fourth aspects described above.
In a fifteenth aspect, the present application provides a chip system, where the chip system includes a processor and may further include a memory, and is configured to implement the functions of the network device or the terminal device in the foregoing method. The chip system may be composed of a chip, and may also include a chip and other discrete devices.
In a sixteenth aspect, the present application further provides a communication system, where the communication system includes the terminal device described in the fifth aspect or a communication apparatus supporting the terminal device to implement the method described in the first aspect, and the network device described in the sixth aspect or a communication apparatus supporting the network device to implement the method described in the second aspect;
or the communication system comprises the terminal device described in the seventh aspect or a communication apparatus supporting the terminal device to implement the method described in the third aspect, and the network device described in the eighth aspect or a communication apparatus supporting the network device to implement the method described in the fourth aspect;
the communication system comprises the terminal device described in the ninth aspect or a communication apparatus supporting the terminal device to implement the method described in the first aspect, and the network device described in the tenth aspect or a communication apparatus supporting the network device to implement the method described in the second aspect;
or the communication system comprises the terminal device described in the eleventh aspect or a communication apparatus supporting the terminal device to implement the method described in the third aspect, and the network device described in the twelfth aspect or a communication apparatus supporting the network device to implement the method described in the fourth aspect.
In addition, the technical effects brought by the design manners of any aspect can be referred to the technical effects brought by different design manners in the first aspect and the fourth aspect, and are not described herein again.
In the present application, the names of the terminal device, the network device and the communication apparatus do not limit the devices themselves, and in actual implementation, the devices may appear by other names. Provided that the function of each device is similar to that of the present application, and that the devices are within the scope of the claims of the present application and their equivalents.
Drawings
Fig. 1 is a schematic flow chart of a beam failure recovery procedure according to an embodiment;
fig. 2 is a block diagram of a communication system according to an embodiment;
FIG. 3 is a block diagram of a communication system according to an embodiment;
FIG. 4 is a block diagram of a communication system according to an embodiment;
fig. 5 is a flowchart of a method for transmitting a beam failure recovery request according to an embodiment;
fig. 6 is a flowchart of a method for transmitting a beam failure recovery request according to an embodiment;
fig. 7 is a flowchart of a method for transmitting a beam failure recovery request according to an embodiment;
fig. 8 is a schematic diagram illustrating an exemplary communication device;
fig. 9 is a schematic diagram illustrating a communication device according to an embodiment.
Detailed Description
The terms "first," "second," and "third," etc. in the description and claims of this application and the above-described drawings are used for distinguishing between different objects and not for limiting a particular order.
In the embodiments of the present application, words such as "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.
For clarity and conciseness of the following descriptions of the various embodiments, a brief introduction to the related art is first given:
1. control resource set (CORESET)
In order to improve the efficiency of blind detection of a control channel by terminal equipment, a concept of a control resource set is provided in the process of formulating an NR standard. The network device may configure one or more resource sets for the terminal device, and is configured to send a Physical Downlink Control Channel (PDCCH). The network device may send a control channel to the terminal device on any control resource set corresponding to the terminal device. In addition, the network device needs to inform the terminal device of the associated other configurations of the control resource set, such as a search space set. There are differences in configuration information of each control resource set, such as frequency domain width difference, time domain length difference, and the like. The control resource set in the present application may be a core set or a control area (control region) or an enhanced-physical downlink control channel (ePDCCH) set (set) defined by the 5G mobile communication system.
The time-frequency position occupied by the PDCCH may be referred to as a downlink control region. In Long Term Evolution (LTE), the PDCCH is always located in the first m (m may take values of 1, 2, 3, and 4) symbols of a subframe. It should be noted that the positions of the E-PDCCH and the R-PDCCH in LTE are not in the first m symbols.
In NR, a downlink Control region may be flexibly configured by Radio Resource Control (RRC) signaling through a Control Resource set and a search space set:
the control resource set may configure information such as a frequency domain position of a PDCCH or a Control Channel Element (CCE), and a number of persistent symbols in a time domain;
the search space set can configure the detection period and offset of the PDCCH, the initial symbol in a time slot and other information.
For example, the search space set may configure the PDCCH period to be 1 slot, and the time domain start symbol is symbol 0, then the terminal device may detect the PDCCH at the start position of each slot.
2. Spatial correlation parameter information
The spatial-dependent parameter information may be quasi-co-location (QCL) information or spatial-dependent information (spatial correlation). In general, the QCL information is used to indicate spatial correlation parameters (also referred to as spatial correlation characteristics) of downlink signals (such as PDCCH/PDSCH/CSI-RS/DMRS/TRS), and the spatial correlation information is used to indicate spatial correlation parameters (also referred to as spatial correlation characteristics) of uplink signals (such as PUCCH/PUSCH/SRS/DMRS).
Quasi co-location, also referred to as quasi co-sited, co-located. The QCL information may also be referred to as QCL hypothesis information. The QCL information is used to assist in describing the terminal device receiving beamforming information and receiving procedures.
The QCL information may be used to indicate a QCL relationship between two reference signals, where the target reference signal may generally be a demodulation reference signal (DMRS), a channel state information reference signal (CSI-RS), etc., and the referenced reference signal or source reference signal may generally be a CSI-RS, a synchronization signal broadcast channel block (SSB)), a Sounding Reference Signal (SRS), etc. It should be understood that a Tracking Reference Signal (TRS) is also one of the CSI-RSs. It should be understood that the target reference signal may generally be a downlink signal.
The signals corresponding to the antenna ports having the QCL relationship may have the same or similar spatial characteristic parameters (or called parameters), or the spatial characteristic parameters (or called parameters) of one antenna port may be used to determine the spatial characteristic parameters (or called parameters) of another antenna port having the QCL relationship with the antenna port, or two antenna ports have the same or similar spatial characteristic parameters (or called parameters), or the difference between the spatial characteristic parameters (or called parameters) of the two antenna ports is smaller than a certain threshold.
The spatial correlation information is used for assisting in describing beamforming information and a transmitting process of a transmitting side of the terminal equipment.
The spatial correlation information is used to indicate a spatial transmission parameter relationship between two reference signals, where the target reference signal may be generally a DMRS, SRS, etc., and the referenced reference signal or source reference signal may be generally a CSI-RS, SRS, SSB, etc. It should be understood that the target reference signal may generally be an uplink signal.
It is to be understood that the spatial characteristic parameters of two reference signals or channels satisfying the QCL relationship are the same (or similar ), so that the spatial characteristic parameter of the target reference signal can be inferred based on the source reference signal resource index.
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 ), such that the spatial characteristic parameter of the target reference signal can be inferred based on the source reference signal resource index.
Wherein the spatial characteristic parameters comprise one or more of the following parameters:
an incident angle (angle of arrival, AoA), a main (dominant) incident angle AoA, an average incident angle, a power angle spectrum of incident angles (PAS), an emergence angle (angle of departure, AoD), a main emergence angle, an average emergence angle, a power angle spectrum of emergence angles, terminal device transmit beamforming, terminal device receive beamforming, spatial channel correlation, network device transmit beamforming, network device receive beamforming, average channel gain, average channel delay (average delay), delay spread (delay spread), Doppler spread (Doppler spread), Doppler shift (Doppler shift), spatial receive parameters (spatial Rx parameters), and the like.
The angle may be a decomposition value of different dimensions, or a combination of decomposition values of different dimensions. The antenna ports may be antenna ports with different antenna port numbers, and/or antenna ports with the same antenna port number for transmitting or receiving information in different time and/or frequency and/or code domain resources, and/or antenna ports with different antenna port numbers for transmitting or receiving information in different time and/or frequency and/or code domain resources.
The spatial characteristic parameters describe spatial channel characteristics between antenna ports of the source reference signal and the target reference signal, and are helpful for the terminal device to complete the beamforming or receiving process at the receiving side according to the QCL information. It should be understood that the terminal device may receive the target reference signal according to the receiving beam information of the source reference signal indicated by the QCL information; the spatial characteristic parameters also help the terminal device to complete the beam forming or the transmission processing process at the transmitting side according to the spatial correlation information, and it should be understood that the terminal device can transmit the target reference signal according to the transmission beam information of the source reference signal indicated by the spatial correlation information.
As an optional implementation manner, in order to save QCL information indication overhead of the network device for the terminal device, the network device may indicate that a demodulation reference signal of a PDCCH or a Physical Downlink Shared Channel (PDSCH) and one or more of a plurality of reference signal resources reported by the terminal device before satisfy a QCL relationship, for example, the reference signal may be a CSI-RS. Here, each reported CSI-RS resource index corresponds to a transmit-receive beam pair previously established based on the CSI-RS resource measurement. It should be understood that the reception beam information of two reference signals or channels satisfying the QCL relationship is the same, and the terminal device may infer the reception beam information of receiving the PDCCH or PDSCH from the reference signal resource index.
Four types of QCLs are defined in the existing standard, and the network device may configure one or more types of QCLs, such as QCL type a + D, C + D:
QCL types A:Doppler shift,Doppler spread,average delay,delay spread
QCL types B:Doppler shift,Doppler spread
QCL types C:average delay,Doppler shift
QCL types D:Spatial Rx parameter
when a QCL relationship refers to a QCL relationship of type D, it may be considered a spatial QCL. When the antenna ports satisfy the spatial-domain QCL relationship, the QCL relationship (referred to as spatial relationship) between the ports of the downlink signals and the ports of the downlink signals, or between the ports of the uplink signals and the ports of the uplink signals may be that the two signals have the same AOA or AOD, which means that the two signals have the same receive beam or transmit beam. For another example, for QCL relationship between downlink signals and uplink signals or between ports of uplink signals and downlink signals, AOAs and AODs of two signals may have a corresponding relationship, or AODs and AOAs of two signals have a corresponding relationship, that is, an uplink transmit beam may be determined according to a downlink receive beam or a downlink receive beam may be determined according to an uplink transmit beam by using beam reciprocity.
From the transmitting end, if it is said that two antenna ports are spatial QCL, it may be said that the corresponding beam directions of the two antenna ports are spatially consistent. From the perspective of the receiving end, if it is said that the two antenna ports are spatial QCL, it may mean that the receiving end can receive signals transmitted by the two antenna ports in the same beam direction.
Signals transmitted on ports having spatial QCL relationships may also have corresponding beams, which may include at least one of: the same receive beam, the same transmit beam, a transmit beam corresponding to the receive beam (corresponding to a reciprocal scene), a receive beam corresponding to the transmit beam (corresponding to a reciprocal scene).
A signal transmitted on a port having a spatial QCL relationship may also be understood as a signal received or transmitted using the same spatial filter. The spatial filter may be at least one of: precoding, weight of antenna port, phase deflection of antenna port, and amplitude gain of antenna port.
Signals transmitted on ports having spatial QCL relationships may also be understood as having corresponding Beam Pair Links (BPLs) including at least one of: the same downlink BPL, the same uplink BPL, the uplink BPL corresponding to the downlink BPL, and the downlink BPL corresponding to the uplink BPL.
Accordingly, the spatial reception parameter (i.e., QCL of type D) may be understood as a parameter for indicating direction information of a reception beam.
In the examples of the present application, the correspondence of certain parameters may also be applied to the scenario described by QCL.
It should be understood that the context applicable to QCL assumption in the present application may also be an association between two reference signals, further or between transmission objects.
3. Transmission Configuration Indicator (TCI) status (state)
The TCI is used to indicate QCL information of a signal or channel. Wherein the channel may be PDCCH/core set or PDSCH. The signal may be a CSI-RS, DMRS, TRS, PTRS, or the like. The TCI information indicates that the reference signal included in the TCI and the channel or the signal satisfy the QCL relationship, and is mainly used for indicating that when the signal or the channel is received, information such as the spatial characteristic parameter of the TCI information is the same as, similar to, or close to information such as the spatial characteristic parameter of the reference signal included in the TCI.
A TCI state (TCI state) may configure one or more referenced reference signals, and associated QCL types. The QCL types may be further classified into A, B, C and D categories, which are different combinations or choices of { Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter }. The TCI status includes QCL information, or the TCI status is used to indicate QCL information.
4. Synchronous signal broadcast channel block (PBCH) block, SS/PBCH block)
The SS/PBCH block may also be referred to as an SSB. Wherein the SSB includes at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a PBCH. The method is mainly used for cell search, cell synchronization and broadcast information bearing signals.
5. Cell carrier correlation concept:
a Component Carrier (CC) may also be referred to as a component carrier, or a component carrier, etc. Each carrier in the multi-carrier aggregation may be referred to as a "CC", each carrier is composed of one or more Physical Resource Blocks (PRBs), and each carrier may have a Physical Downlink Control Channel (PDCCH) corresponding thereto, and schedules a Physical Downlink Shared Channel (PDSCH) of each CC; or, some carriers do not have a PDCCH, and at this time, the carriers may perform cross-carrier scheduling, that is, the PDCCH of one CC schedules the PDSCH of another CC. A terminal device may receive data on multiple CCs.
Carrier Aggregation (CA) may refer to aggregation of a plurality of contiguous or non-contiguous element carriers into a larger bandwidth.
Primary cell/primary serving cell (PCell) is a cell where the CA UE resides. Generally, only the PCell has a Physical Uplink Control Channel (PUCCH).
A Primary Secondary Cell (PSCell) is a special Secondary Cell on a Secondary base station (Secondary eNodeB, SeNB) that a Primary base station (master eNodeB, MeNB) configures to a DC UE through RRC connection signaling.
A Secondary Cell (SCell) refers to a Cell configured to a terminal device of a CA through an RRC connection signaling, and operates on an SCC (Secondary carrier) to provide more radio resources for the CA terminal device. The SCell may have downlink only or may exist in both uplink and downlink.
A Special Cell (SpCell), wherein for a Dual Connectivity (DC) scenario, the SpCell refers to a PCell of a Master Cell Group (MCG) or a PSCell of a Slave Cell Group (SCG); otherwise, like the CA scenario, SpCell refers to PCell.
MCG/SCG means that the group in which the cell providing service for the terminal equipment in the main base station is located is a main cell group. In dual connectivity mode, the MeNB is associated with a set of serving cells, including the PCell and one or more scells.
The SCG means that a group in which a cell providing service for the UE is located in the secondary base station is a secondary cell group. In dual linked mode, includes PSCell and 0 or more scells.
The MeNB is a base station to which the DC terminal device resides.
The SeNB is another base station that the MeNB configures to the DC UE through RRC connection signaling.
6. Beam (beam):
a beam is a communication resource. The beam may be a wide beam, or a narrow beam, or other type of beam. The technique of forming the beam may be a beamforming technique or other technical means. The beamforming technology may be embodied as a digital beamforming technology, an analog beamforming technology, or a hybrid digital/analog beamforming technology. Different beams may be considered different resources. The same information or different information may be transmitted through different beams. Alternatively, a plurality of beams having the same or similar communication characteristics may be regarded as one beam. One beam may include one or more antenna ports for transmitting data channels, control channels, sounding signals, and the like, for example, a transmission beam may refer to the distribution of signal strength formed in different spatial directions after signals are transmitted through the antenna, and a reception beam may refer to the distribution of signal strength in different spatial directions of wireless signals received from the antenna. It is to be understood that the one or more antenna ports forming one beam may also be seen as one set of antenna ports.
The beams may be divided into a transmission beam and a reception beam of the network device and a transmission beam and a reception beam of the terminal device. The sending beam of the network equipment is used for describing the beam forming information of the sending side of the network equipment, the receiving beam of the base station is used for describing the beam forming information of the receiving side of the network equipment, the sending beam of the terminal equipment is used for describing the beam forming information of the sending side of the terminal equipment, and the receiving beam of the terminal is used for describing the beam forming information of the receiving side of the terminal equipment. I.e. the beams are used to describe the beamforming information.
The beams may correspond to time resources and/or spatial resources and/or frequency domain resources.
Alternatively, the beams may also correspond to reference signal resources (e.g., beamformed reference signal resources), or beamforming information.
Alternatively, the beam may also correspond to information associated with a reference signal resource of the network device, where the reference signal may be a channel state information reference signal (CSI-RS), an SSB, a demodulation reference signal (DMRS), a phase tracking signal (PTRS) tracking signal (TRS), or the like, and the information associated with the reference signal resource may be a reference signal resource identifier, or QCL information (especially, a QCL of type D type), or the like. The reference signal resource identifier corresponds to a transceiving beam pair established in the previous measurement based on the reference signal resource, and the terminal can deduce beam information through the reference signal resource index.
Alternatively, the beam may correspond to a spatial filter (spatial domain filter) or a spatial domain transmission filter (spatial domain transmission filter).
Wherein, the receiving wave beam can be equivalent to a space transmission filter, a space receiving filter and a space receiving filter; the transmission beam may be equivalent to a spatial filter, a spatial transmission filter, and a spatial transmission filter. The information of the spatial correlation parameter may be equivalent to a spatial filter (spatial direct transmission/receive filter). Optionally, the spatial filter generally includes a spatial transmit filter, and/or a spatial receive filter. The spatial filter may also be referred to as a spatial transmit filter, a spatial receive filter, a spatial transmit filter, etc. The receiving beam at the terminal device side and the transmitting beam at the network device side may be downlink spatial filters, and the transmitting beam at the terminal device side and the receiving beam at the network device side may be uplink spatial filters.
7. Antenna port (antenna port)
An antenna port may also be referred to simply as a port. A transmit antenna identified by the receiving end device, or a spatially distinguishable transmit antenna. One antenna port may be configured for each virtual antenna, each virtual antenna may be a weighted combination of multiple physical antennas, and each antenna port may correspond to one reference signal port.
8. Bandwidth region (BWP)
The network device may configure one or more downlink/uplink bandwidth regions for the terminal device, and the BWP may be composed of PRBs contiguous in the frequency domain, and the BWP is a subset of the bandwidth of the terminal device. The minimum granularity of BWP in the frequency domain is 1 PRB. The system may configure one or more bandwidth regions for the terminal device, and the plurality of bandwidth regions may overlap (overlap) in the frequency domain.
In a single carrier scenario, a terminal device may have only one active BWP at a time, and the terminal device can only receive data/reference signals or transmit data/reference signals on the active BWP (active BWP).
In the present application, in case of being applicable to a BWP scenario, a specific BWP may also be a bandwidth set on a specific frequency, or a set consisting of multiple RBs.
9. Reference signals configured for detecting beam failure and recovering beam failure
In order to detect the beam failure, the network device needs to indicate the beam failure detection reference signal resource (which may also be referred to as a link failure detection reference signal resource) to the terminal device. The beam failure detection reference signal resource may have the following possible indication modes. For example, the network device may display a set of beam failure detection reference signal resources (beam failure detection RS sets) (e.g., beam failure detection RS resource configuration or beam failure detection RS or failure detection resources) configured for beam failure detection to the terminal device (which may also be referred to as a beam failure detection reference signal resource set). The network device configuration beam failure detection reference signal resource set may be indicated by one or more of RRC, MAC-CE, DCI signaling. For another example, the reference signal for beam failure detection may also be implicitly indicated, such as using a reference signal associated in a TCI (e.g., type-D QCL) indicating the PDCCH as the reference signal for beam failure detection, where the reference signal is a reference signal that satisfies a QCL relationship with a DMRS of the PDCCH and is a reference signal that is periodically transmitted. Optionally, when the network device displays that a set of reference signal resources for beam failure detection is configured, the terminal device may detect a beam failure according to the set of reference signal resources for beam failure detection; when the network device does not display the set of reference signal resources configured for beam failure detection, the terminal device may detect the beam failure according to the reference signal indicated in the above implicit manner.
Wherein, the RS in the beam failure detection reference signal resource set and the demodulation reference signal of the downlink physical control channel PDCCH satisfy a QCL relationship or use the same TCI state as the PDCCH, and when channel quality information (such as Reference Signal Receiving Power (RSRP), Channel Quality Indicator (CQI), block error rate (BLER), signal to Interference plus noise ratio (SINR), signal to noise ratio (SNR), and the like) of some or all reference signals in the set is lower than a predetermined threshold, it is determined that the beam fails. Wherein the falling below the predetermined threshold may be N consecutive times below the predetermined threshold or N times below the predetermined threshold for a certain period of time. The predetermined threshold may be referred to as a beam failure detection threshold, and may also be referred to as a beam failure threshold. It should be understood that the predetermined threshold may be any threshold used for detecting a beam failure, and the name of the predetermined threshold is not limited in the present application. Optionally, the beam failure detection threshold may be configured by the network device, and may also be the same threshold as a radio link failure out-of-synchronization threshold (out of sync). Optionally, when the network device configures a beam failure detection threshold, detecting a beam failure using the beam failure detection threshold; when the network device does not configure the beam failure detection threshold, the radio link out-of-step threshold may be used as the beam failure detection threshold to detect the beam failure. It should be understood that the beam failure detection reference signal here may be a channel quality of a certain transmission beam used for the terminal to detect the network device, the transmission beam being a beam used when the network device communicates with the terminal.
In order to recover the beam failure, the network device may further indicate, to the terminal device, a reference signal resource set (also referred to as a candidate reference signal resource set or a beam failure recovery reference signal resource set) for recovering a link between the terminal device and the network device (a candidate beam RS resource set or a beam failure recovery reference signal resource set). After the beam fails, the terminal device needs to select a reference signal resource whose channel quality information (such as one or more of RSRP, RSRQ, CQI, SINR, etc.) is higher than a predetermined threshold from the candidate reference signal resource set, so as to recover the communication link. It can also be understood as a reference signal set used by the terminal device to initiate link reconfiguration after determining that the beam failure occurs in the transmission beam of the network device. For example, the network device may display to the terminal device a set of reference signal resources configured for beam failure recovery. The network device configuration beam failure detection reference signal resource set may be indicated by one or more of RRC, MAC-CE, DCI signaling. The set of reference signal resources used for beam failure recovery may also be some default set of reference signal resources, (e.g. a set of reference signal resources used for beam management BM or for RRM measurements, a set of reference signal resources made up of all or part of SSBs, or some set of reference signal resources multiplexing other functions). Wherein, the reference signal resource set for Beam Management (BM) may be a reference signal resource set whose repeption is identified as "off" (and may also be a reference signal resource set whose repeption is identified as "on"). Optionally, when the network device configures a set of candidate reference signal resources, identifying a reference signal in the set of reference signal resources; when the network device is not configured with the candidate set of reference signal resources, a reference signal is identified in the default set of reference signal resources. The identified reference signal may be used to recover the beam failure. Optionally, the channel quality of the identified reference signal is greater than a preset threshold.
Optionally, the predetermined threshold used in identifying the reference signal for recovering the link may be configured by the network device, or may also be a predefined threshold. For example, when the network device is not configured with the threshold, the threshold for mobility measurement is used by default. The predetermined threshold may be referred to as a beam failure recovery threshold and may also be referred to as a link recovery threshold. It should be understood that the name of the predetermined threshold is not limited by the present invention as long as the threshold for the beam failure recovery can be the predetermined threshold.
It should be understood that in a specific implementation, the names of the two sets, i.e., the set of reference signal resources for beam failure detection and the set of reference signal resources for recovering the link between the terminal device and the network device, may also be called other names, and this application is not limited to this.
In the embodiment of the present application, a beam failure may also be referred to as a beam failure, a link failure, a communication link failure, or the like. In the embodiments of the present application, these concepts are the same meaning. The communication failure may refer to that the signal quality of a reference signal used for beam failure detection of the PDCCH is less than or equal to a preset threshold.
In this embodiment, the beam failure recovery may also be referred to as recovering the network device to communicate with the terminal device, and the beam failure recovery, the beam recovery, the link failure recovery, the link recovery, the communication failure recovery, the communication link failure recovery, the communication recovery, the link reconfiguration, and the like.
In this embodiment, the beam failure recovery request may also be referred to as beam failure recovery request information, beam recovery request information, link failure recovery request information, link recovery request information, communication failure recovery request information, communication link failure recovery request information, communication link recovery request information, link reconfiguration request information, and the like. Alternatively, the communication failure recovery request may refer to a signal being sent on a resource used to carry the communication failure recovery request.
It should be understood that "information" in the present application may be replaced with "messages".
In this embodiment, the beam failure recovery response may also be referred to as beam failure recovery response information, beam failure response information, beam recovery response, link failure recovery response information, link failure response information, link recovery response information, communication failure response information, communication recovery response information, communication link failure response information, link reconfiguration response information, and the like. It should be understood that, in the present application, the communication failure recovery response information may be simply referred to as response information.
In this embodiment of the present application, the beam failure recovery response information may refer to Downlink Control Information (DCI) that is received on a control resource set and/or a search space set for sending a beam failure recovery response and is scrambled by a cell radio network temporary identifier (C-RNTI), where the beam failure recovery response information may also be DCI scrambled by other information (e.g., a BFR-RNTI), the beam failure recovery response information may also be data scheduled by the DCI, and the beam failure recovery response information may also be ACK of the data scheduled by the DCI. The beam failure recovery response information may also be one of the following information: the method comprises the steps of DCI scrambled by a cell radio network temporary identifier C-RNTI, DCI scrambled by a modulation coding mode cell specific radio network temporary identifier MCS-C-RNTI, DCI of downlink control information in a special search space, DCI scrambled by a special radio network temporary identifier RNTI, DCI scrambled by a random access radio network temporary identifier RA-RNTI, DCI containing a preset state value, DCI containing transmission configuration indication TCI information, quasi co-location QCL indication information of a cell in which a wave beam fails or DCI indicating newly transmitted data. The embodiments of the present application do not limit this. It should be understood that the DCI indicating newly transmitted data and the DCI scheduling bearer beam failure request information resource have the same hybrid automatic repeat request (HARQ) process identifier (process identifier), and optionally, the New Data Indicators (NDIs) of the two DCIs are different. It should be understood that when the terminal device receives the beam failure recovery response information, the beam failure recovery is considered to be successful. It should be understood that after the beam failure recovery is successful, the terminal device may not send the beam failure recovery request information any more, may also stop or reset the counter of the beam failure detection, may also stop or reset the timer of the beam failure detection, may also stop or reset the beam failure recovery counter, may also stop or reset the beam failure recovery timer, and the like.
It should be understood that the names of the beam failure, the beam failure recovery request information, and the beam failure recovery response information in the embodiments of the present application may also be called as other names, and this is not particularly limited in this application.
It should be understood that, in the present application, the beam failure recovery may be understood as that the terminal device does not send the beam failure recovery request information any more, may also be understood as stopping the timing of the beam failure recovery timer (or referred to as a clock), may also be understood as stopping the counting of the beam failure recovery counter, and the like.
It should be understood that in the embodiments of the present application, "beam" may be replaced with "link".
It should also be understood that in the present embodiment, "cell" may be understood as "serving cell" or "carrier.
Optionally, the cell includes at least one of a downlink carrier, an Uplink (UL) carrier, and a Supplemental Uplink (SUL) carrier. Specifically, a cell may include a downlink carrier and an uplink carrier; or the cell may include a downlink carrier and an uplink supplementary carrier; or the cell comprises a downlink carrier, an uplink carrier and an uplink supplementary carrier.
Optionally, the carrier frequency of the uplink supplemental carrier is lower than the uplink carrier, so as to improve uplink coverage.
Optionally, in general, in an FDD system, carrier frequencies of an uplink carrier and a downlink carrier are different; in the TDD system, the carrier frequencies of the uplink carrier and the downlink carrier are the same.
It should also be understood that, in the embodiment of the present application, the uplink resource is on an uplink carrier; the downlink resource is on a downlink carrier.
It should be further understood that, in the embodiment of the present application, the uplink carrier may be a normal uplink carrier, and may also be a Supplemental Uplink (SUL) carrier.
It should be understood that "detection" in the embodiments of the present application may be understood as "reception" and may also be understood as "decoding".
It should be understood that, in the present application, a time unit may be one or more radio frames, one or more subframes, one or more slots, one or more minislots (mini slots), one or more Orthogonal Frequency Division Multiplexing (OFDM) symbols, etc. defined in the LTE or 5G NR system, and may also be a time window formed by a plurality of frames or subframes, such as a System Information (SI) window.
In the LTE system, the minimum time scheduling unit is a Transmission Time Interval (TTI) of 1ms duration. The 5G supports the time domain scheduling granularity of a time unit level, also supports the time domain scheduling granularity of a micro time unit, and meets the time delay requirements of different services. For example, time units are mainly used for eMBB traffic and micro-time units are mainly used for URLLC traffic. It should be noted that the time units and the micro time units are general terms, and a specific example may be that the time units may be referred to as slots, and the micro time units may be referred to as micro slots, non-slots (non-slot-based), or mini-slots (mini-slots); alternatively, a time unit may be referred to as a subframe, and a micro-time unit may be referred to as a micro-subframe; other similar time domain resource division modes are not limited. The first time unit described herein may refer to a timeslot or mini-timeslot, etc. For example, a slot may include, for example, 14 time domain symbols, and a mini-slot may include less than 14 time domain symbols, such as 2, 3, 4, 5, 6, or 7, etc.; or, for example, a timeslot may include 7 time domain symbols, and a mini timeslot includes time domain symbols less than 7, such as 2 or 4, and the specific value is not limited. The time domain symbols here may be OFDM symbols. For a timeslot with subcarrier spacing of 15 kilohertz (kHz), including 6 or 7 time domain symbols, the corresponding time length is 0.5 ms; for a time slot with a subcarrier spacing of 60kHz, the corresponding time length is shortened to 0.125 ms.
It should be understood that in the present application, "cell identification" may also be replaced by "cell index".
It should be understood that, in the embodiment of the present application, the beam failure case counter may also be referred to as a beam failure case indication counter, and may also be referred to as a beam failure detection counter.
It should be understood that, in various embodiments of the present application, the reference signal information may include a reference signal resource index and/or a channel quality of a reference signal. Wherein the channel quality may include one or more of: reference Signal Received Power (RSRP), signal to interference plus noise ratio (SINR), Reference Signal Received Quality (RSRQ), Channel Quality Indication (CQI), or signal to noise ratio (SNR), among others.
Communication systems typically use different kinds of reference signals: one type of reference signal is used to estimate the channel so that a received signal containing control information or data can be coherently demodulated; another type is used for measurement of channel state or channel quality, enabling scheduling of terminal devices. And the terminal equipment obtains the CSI based on the CSI-RS channel quality measurement. The CSI includes at least one of Rank Indicator (RI), Precoding Matrix Indicator (PMI), Channel Quality Indicator (CQI), and the like. The CSI information may be sent by the terminal device to the network device via PUCCH or PUSCH.
With the advent of intelligent terminals, particularly video services, it has been difficult for current spectrum resources to meet the explosive growth of users' demand for capacity. High frequency bands, particularly millimeter wave bands, having larger available bandwidths are increasingly becoming candidates for next generation communication systems. On the other hand, modern communication systems usually use multi-antenna technology to improve the capacity and coverage of the system or improve the user experience, and another benefit from using high frequency band is that the size of the multi-antenna configuration can be greatly reduced, thereby facilitating site acquisition and deployment of more antennas. However, unlike the working frequency band of the existing LTE system, the high frequency band will cause larger path loss, and especially the influence of factors such as atmosphere and vegetation will further increase the loss of wireless propagation.
To overcome the large propagation loss, a signal transmission mechanism based on beamforming technology is adopted to compensate the loss in signal propagation process by large antenna gain. The beamformed signals may include broadcast signals, synchronization signals, cell-specific reference signals, and the like.
When signals are transmitted based on the beam forming technology, once a user moves, the direction of a formed beam corresponding to the transmitted signals is not matched with the position of the moved user any more, so that the received signals are frequently interrupted. In order to track the change of the shaped beam in the signal transmission process, a channel quality measurement and result reporting based on the beam forming technology is introduced. The channel quality measurement may be based on a beamformed synchronization signal or a cell-specific reference signal. Compared with cell switching, the switching of users among different shaped beams is more dynamic and frequent, so a dynamic measurement reporting mechanism is needed. Optionally, similar to the reporting of CSI information, the reporting of the channel quality result of the shaped beam may also be sent to the network device by the terminal device through a PUCCH or a PUSCH.
The terminal equipment selects the N optimal wave beams by measuring the plurality of wave beams sent by the network equipment and reports the N optimal wave beam measurement information to the network equipment. The beam measurement information mainly includes reference signal resource index and reference signal quality information. The reference signal quality information may be at least one of channel quality information of the reference signal, such as a received power (L1-reference signal received power, L1-RSRP) of the reference signal, a signal to interference plus noise ratio (L1-signal to interference plus noise ratio, L1-SINR) of the reference signal, a signal to interference plus noise ratio (SINR) of the reference signal, or a Channel Quality Indication (CQI) of the reference signal.
In the transmission of downlink signals, both a network device transmitting beam and a terminal receiving beam may dynamically change, a plurality of better receiving beams determined by the terminal device based on the receiving signals may be included, in order to enable the terminal device to determine its own receiving beam, the terminal device may feed back information of the plurality of receiving beams to the network device, and the network device may indicate the terminal receiving beam to the terminal device by sending beam indication information to the terminal device. When the terminal equipment adopts the beam forming in the analog domain, the terminal equipment can accurately determine the terminal to receive the beam based on the beam indication information sent by the network equipment, so that the beam scanning time of the terminal equipment can be saved, and the effect of saving power is achieved. For example, the network device may indicate the reception parameters employed by the terminal device through QCL information configuring the PDCCH. Specifically, the QCL information configuration method of the PDCCH is as follows: the RRC configures K candidate QCL information of the PDCCH, such as K TCI states; the MAC-CE indicates QCL information of the PDCCH (when K > 1).
The protocol also provides that the network device can assume that the DMRS of PDCCH and PDSCH is QCL with the SSB determined at initial access before RRC and MAC-CE are not transmitted.
However, due to the occlusion in the communication process, the diffraction capability under the high-frequency channel is poor, so that the currently served beam is blocked, and the signal cannot be transmitted continuously. In order to prevent communication from being suddenly interrupted in the case of blocked beams, a corresponding mechanism needs to be introduced to detect the current link quality and quickly recover the link in the case of blocked beams.
In order to prevent a situation where a wireless signal is blocked to cause a sudden interruption of communication from occurring, the terminal device may measure the communication quality of a reference signal for beam failure detection configured by the network device to determine whether a beam failure occurs. Fig. 1 shows a schematic flow chart of a beam failure recovery procedure in the prior art, and as shown in fig. 1, the beam failure recovery procedure includes:
s101, the terminal device measures a reference signal resource set (beam failure detection RS set) of beam failure detection, and determines beam failure between the terminal device and the network device.
In some embodiments, when the terminal device determines that the channel quality information of M consecutive beam failure detection reference signals 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, the terminal device may determine that a beam between the terminal device and the network device fails. Specifically, there may be the following steps:
1. the terminal device measures the channel quality (also referred to as "signal quality") of the reference signals within the set of beam failure detection reference signal resources. For convenience of description, a reference signal within a set of beam failure detection reference signal resources may be referred to as q 0. When the channel quality of all or part of the reference signals in q0 in the beam failure case reporting period is less than or equal to the link failure detection threshold, the Physical (PHY) layer of the terminal device reports the beam failure case indication information to a Medium Access Control (MAC) layer.
The reporting period of the beam failure case is a period in which a Physical (PHY) layer reports beam failure case indication information to a Medium Access Control (MAC) layer.
It should be understood that the reference signal resource in q0 satisfies a QCL relationship with the CORESET/PDCCH of the SCell in which the reference signal is configured (the beam failure detection reference signal resource and CORESET may be in a one-to-one relationship, or a many-to-one relationship, or a one-to-many relationship). For example, DMRSs of reference signals and a PDCCH in a beam failure detection reference signal resource set satisfy a quasi co-location (QCL) relationship or have the same TCI state as the PDCCH.
2. If the terminal device detects N consecutive beam failure cases (it can also be understood that the MAC layer receives N beam failure case information when the beam failure detection timer runs), the terminal device determines that the current SCell has a beam failure.
Wherein, N is configured by a beam failure detection parameter (which may be a beamfailure probability max count parameter configured by RRC signaling or MAC-CE signaling).
Whether the N times of beam failure cases are continuous or the count of the N times of beam failure cases is controlled by a beam failure detection timer (which may be a beamfailure detectiontimer parameter configured by RRC signaling or MAC-CE signaling) in the beam failure detection parameter.
The reporting period of the beam failure case is the period of the reference signal with the minimum period in q0 and the maximum value in 2 ms. The length of the beam failure detection timer is integral multiple of the reporting period of the beam failure case.
The terminal device maintains a beam failure case COUNTER (BFI-COUNTER) with an initial value of 0. If the MAC layer of the terminal device receives the beam failure instance indication information (beam failure instance indication) transmitted by the PHY layer, the terminal device starts or restarts the beam failure detection timer and increments the BFI-COUNTER by one. And when the BFI-COUNTER counting value is larger than or equal to N, determining that the SCell fails to generate the beam.
If the beam failure detection timer times out, or if any one of the beam failure detection parameters is reconfigured by the higher layer signaling, the BFI-COUNTER is set to 0. If the beam failure recovery is successful, the BFI-COUNTER is also set to 0, and the beam failure detection timer is stopped.
It should be understood that, in this embodiment, the method for determining, by the terminal device, that a beam on a certain carrier fails to occur with the network device is not limited to the above example, and may also be determined by other determination methods, which is not limited in this application.
It should be understood that the terminal device determines that a beam on a certain carrier between the terminal device and the network device fails, and may be understood as that the terminal device determines that a link on a certain carrier between the terminal device and the network device fails.
And S102, the terminal equipment identifies the new link.
The terminal device may measure the reference signals in a certain set of reference signal resources and identify the reference signals for recovering the link between the terminal device and the network device. Generally, the channel quality of the reference signal used to recover the link between the terminal device and the network device needs to be greater than or equal to the beam failure recovery threshold. The reference signal may be referred to simply as the first reference signal or the new beam. The first reference signal may be one reference signal or may also be a plurality of reference signals. The multiple reference signals may be used to recover the link of carriers. Each of the plurality of reference signals may be used to recover a carrier configuring the reference signal. Alternatively, the plurality of reference signals may be used to recover the element carriers configuring the plurality of reference signals.
In some embodiments, the terminal device may identify reference signals in a candidate set of reference signal resources (candidate beam identification RS sets). The terminal device may recover the link based on the reference signal. Optionally, the channel quality of the identified reference signal is greater than or equal to a beam failure recovery threshold. The process of identifying the reference signal by the terminal device may be understood as that the terminal device determines, in the candidate reference signal resource set, a reference signal resource (which may be referred to as a new identified beam or a new beam for short) whose channel quality is greater than or equal to a beam failure recovery threshold; the determination process herein may be determined by measuring channel quality information of the candidate set of reference signal resources.
It should be appreciated that in one possible scenario, the terminal device may not identify a reference signal resource (new identified beam) having a channel quality greater than or equal to the beam failure recovery threshold. In another possible case, the terminal device does not perform step S102.
S103, the network equipment configures or indicates PUSCH resources for the terminal equipment.
And S104, the terminal equipment receives the configuration or information indicating the PUSCH resource sent by the network equipment.
It should be understood that, for convenience of description, the PUSCH resource configured for the terminal device by the network device is simply referred to as the second resource.
The specific indication manner of the second resource may be one or more of the following manners:
mode 1: the terminal equipment sends the first request information to request the second resource. The second resource may be a PUSCH resource indicated by the network device through an uplink grant (or DCI). The uplink grant (or DCI) may be a DCI with a CRC scrambled by a C-RNTI/MCS-C-RNTI.
In one implementation, the first request information indicates a beam failure event and is carried on a PUCCH resource or a PRACH resource. In another implementation, the first request message may be used to request an uplink resource and is carried on a PUCCH resource or a PRACH resource. The first request information may also be referred to as scheduling request information.
It should be understood that the terminal device transmitting the first request message may be performed after step S101 and before step S104.
Specifically, the terminal device sends first request information.
The first request information may also be referred to as scheduling request information or the first request information and the scheduling request information are in the same format. The first request information may be used to request a resource for carrying the second request information (referred to as a second resource for short).
It is to be understood that the second resource may be indicated or activated by the response information of the first request information.
Specifically, in one embodiment, after receiving the first request message, the network device may further send a response message of the first request message.
The response information of the first request information may be used to indicate the second resource allocated to the terminal, that is, the network device allocates the resource to the terminal. The second resource may be an aperiodic resource (or referred to as a dynamic resource), in the method, the network device determines whether to allocate the second resource according to whether there is a cell with beam failure in the current network (indicated by the first request information), and if the network device receives the first request information, it may know that there is a cell with beam failure in the current network, and the network device may dynamically allocate the second resource, so that the terminal device further reports which cells have beam failure, and/or reports information of recovering a new link of the cell with beam failure. Because the beam failure event is an emergency event, the method does not need to reserve the periodic resource for sending the beam failure recovery request information in advance, and can effectively save the resource overhead.
In another embodiment, the response information of the first request message may also be used to activate a second resource, that is, a second resource originally allocated to the terminal, and the activation is triggered by the response information of the first request message, where the activated second resource is a semi-persistent resource (semi-persistent) or a persistent resource (persistent). For example, the second resource may be a semi-static resource or a static resource (e.g., PUSCH, PUCCH, or Physical Random Access Channel (PRACH)) activated by response information of the first request information after the first request information or DCI signaling after the first request information. In the method, the network device determines whether to activate the second resource according to whether a cell with a link failure (indicated by the first request information) exists in the current network, and if the network device receives the first request information, it can know that the cell with the beam failure exists in the current network, and the network device activates the second resource, so that the terminal device further reports which cells have the beam failure and/or reports information of a new link for recovering the cell with the link failure.
Optionally, the second resource may be configured by higher layer signaling or system information, or be a preset resource.
Specifically, the second resource may be configured for the terminal by the network device and sent to the terminal through higher layer signaling or system information. The second resource may also be pre-agreed by the network device and the terminal device, or set by the terminal in advance, which is not limited in this application.
Optionally, the second resource may also be a resource having an association relationship with the resource for carrying the first request information.
Specifically, the second resource may have a mapping relationship with a resource used for carrying the first request information, so that the terminal may determine the second resource when knowing the resource used for carrying the first request information. Optionally, the association relationship between the resource for carrying the first request information and the second resource may be configured by system information such as a Master Information Block (MIB) or a System Information Block (SIB), or configured by Radio Resource Control (RRC) or Medium Access Control (MAC) -Control Element (CE) signaling. The system information or signaling may be sent prior to sending the first request information. Optionally, the configuration of the resource for carrying the first request information and the second resource may also be configured through the system information or the signaling. The method can directly send the second request information on the second resource without sending the second request information through the resource allocated by the response information of the first request information, thereby effectively reducing the beam recovery time delay and improving the beam recovery speed.
It should be noted that, the network device may configure a plurality of resources for the terminal device to transmit the first request information and configure a plurality of resources for the terminal device to transmit the second request information, and the terminal device may select one or more resources from the plurality of resources for transmitting the first request information to send the first request information, and may also select one or more resources from the plurality of resources for transmitting the second request information as the second resources. The plurality of resources for transmitting the first request information and the plurality of resources for transmitting the second request information may be configured by the system information such as the MIB or SIB, or configured by signaling such as RRC or MAC-CE, respectively.
Optionally, the second resource may also be a resource associated with the first request information. Optionally, the network device may configure, through system information such as MIB or SIB, or through RRC or MAC-CE signaling, a plurality of resources for transmitting the first request information and a plurality of resources for transmitting the second request information, and an association relationship between the plurality of resources for transmitting the first request information and the plurality of resources for transmitting the second request information, and the terminal may select one of the plurality of resources for transmitting the first request information to transmit the first request information, and may also select one of the plurality of resources for transmitting the second request information as the second resource. One or more second resources may be associated with each resource for transmitting the first request information, and the second resources associated with each resource for transmitting the first request information may be different in size. In which resource the terminal device sends the first request information, the terminal device sends the second request information on a second resource associated with the resource sending the first request information.
It is to be understood that the second resource may be a PUSCH resource or may be a PUCCH resource.
It should be understood that the second request information of the embodiment may be a MAC-CE indicating cell information of the beam failure cell. The response information of the first request information may be DCI information.
The second request information may include identification information of the beam failed cell and/or reference signal information of the recovery beam failed cell. Or, the cell information of the beam failed cell may include identification information of the beam failed cell and/or reference signal information of the recovery beam failed cell. The reference signal information of the cell with failed beam recovery may be an index of a reference signal resource and/or channel quality information of the reference signal resource (such as one or more of RSRP, SINR, RSRQ, CQI, etc. below).
Mode 2: the second resource may also be a PUSCH resource indicated directly by the network device through an uplink grant (or DCI). The uplink grant (or DCI) may be a DCI with a CRC scrambled by a C-RNTI/MCS-C-RNTI.
For modes 1 and 2, the second resource may be a resource dynamically allocated by the network device. The method does not need to reserve periodic resources in advance, and can effectively save the resource overhead.
Mode 3: the second resource may be a semi-static resource (semi-persistent) or a static resource (periodic) that the network device activates through RRC or MAC-CE or DCI. For example, the second resource may be a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), or a Physical Random Access Channel (PRACH).
Mode 4: the second resource may be configured by the configuration information or be a preset resource.
Specifically, the second resource may be configured for the terminal by the network device and sent to the terminal through higher layer signaling or system information. The second resource may also be pre-agreed by the network device and the terminal device, or set by the terminal in advance, which is not limited in this application.
Alternatively, the configuration information may be configured by system information such as a Master Information Block (MIB) or a System Information Block (SIB), or configured by Radio Resource Control (RRC) or Medium Access Control (MAC) -Control Element (CE) signaling. The configuration information may be configurable grant configured.
Mode 5: the second resource may be a PUSCH resource associated with a PRACH or a PUCCH. Alternatively, the second resource may be a PUSCH resource in a 2step PRACH. Understandably, the network device configures the PRACH resource and the PUSCH resource with an association relationship, and the PUSCH resource does not need DCI indication. In one implementation, the terminal device selects one PRACH resource to initiate a random access procedure, and sends other information (e.g., a UE ID) on a PUSCH resource associated with the PRACH resource. In another implementation, the PRACH resource or the PUCCH resource is a resource that carries the first request information. The first request information is described in manner 1, and is not described herein again.
With regard to methods 3, 4 and 5, the configuration information indicating the second resource by the network device may be sent in advance, where the configuration information may be sent to the terminal device by the network device before determining that the beam fails, and then the terminal device directly sends the beam failure recovery request information on the resource after finding the beam failure without waiting for the network device to allocate the PUSCH resource.
It should be understood that in any one or more of the manners 1 to 5, the terminal device may obtain one or more second resources.
S105, the terminal equipment sends a beam failure recovery request to the network equipment.
The beam failure recovery request is associated with a reference signal (new identified beam or new beam) whose channel quality is greater than or equal to the beam failure recovery threshold, which is identified in S102, and the terminal device may notify the network device of the new identified beam or the reference signal resource in a display manner or an implicit manner. For example, for the display mode, the terminal device may report the resource index or the resource identifier display of the newly identified reference signal to the network device. For example, for an implicit mode, the network device configures association relations between a plurality of uplink resources for transmitting BFRQ information and a plurality of candidate reference signal resources in advance, and the terminal device implicitly indicates to newly identify the reference signal resources by selecting the uplink resources for transmitting BFRQ.
The terminal device may also report at least one of new beam (new beam) information, cell identifiers of beam failures, and the like through one or more beam failure recovery request messages. And may also be understood as BFRQ indicating one or more of new beam information, cell identification of beam failure, beam failure event.
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.
The BFRQ information of the PCell in the NR can be reported through the PRACH resource. The base station configures one or more PRACH resources, and configures each PRACH resource to be associated with a reference signal, wherein the reference signal is a reference signal used for recovering link failure. The reference signal may be a reference signal in a candidate reference signal resource set configured by a base station. And the terminal equipment confirms the failure of the beam, 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 the new beam information.
For example, an uplink resource set configured for the first cell by the network device for transmitting the beam failure request information of the first cell is referred to as a first uplink resource set. The number of Physical Random Access Channel (PRACH) resources included in the 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 equipment identifies the reference signal which is greater than or equal to the beam failure recovery threshold in the candidate reference signal resource set, and sends the beam failure recovery request information on the PRACH resource associated with the reference signal. Optionally, when there is reciprocity between uplink and downlink, a transmission beam when the terminal device transmits information on one PRACH resource is a transmission beam corresponding to a reception beam of a downlink reference signal associated with the PRACH resource, that is, the terminal device may transmit information on the PRACH resource by using the transmission beam corresponding to the reception beam. When there is no reciprocity between uplink and downlink, an optional implementation manner is that, in the first uplink resource set, one PRACH resource is associated with one downlink reference signal and one uplink reference signal, and the terminal device may further determine, according to the PRACH resource associated with the determined downlink reference signal, the uplink reference signal associated with the PRACH resource, so as to transmit information on the PRACH resource by using a transmission beam of the uplink reference signal.
And the BFRQ information of the SCell in the NR can be reported in one step. The BFRQ information may be carried on PUSCH resources; may also be carried on PUCCH resources; wherein the BFRQ information may indicate a cell identity for a beam failure, and/or new beam information.
The BFRQ message may also be reported in two steps, BFRQ1+ BFRQ 2. The BFRQ1 may be carried on PUCCH resources or PRACH resources, and the BFRQ2 may be carried on PUSCH resources or PUCCH resources. In one implementation, BFRQ1 indicates a beam failure event, and BFRQ2 indicates cell identification and/or new beam information for the beam failure. In another implementation, BFRQ1 indicates a beam failure event and/or cell identification of a beam failure, and BFRQ2 indicates new beam information.
It should be understood that the BFRQ information described above is carried on PUSCH resources, which may be understood as reporting BFRQ information through MAC-CE.
Optionally, a Media Access Control (MAC) layer of the terminal device may maintain a beam failure recovery timer (beam failure recovery timer) and a beam failure recovery counter (beam failure recovery counter). The beam failure recovery timer is used for controlling the time of the whole beam failure recovery, and the beam failure recovery counter is used for limiting the times of sending beam failure recovery requests by the terminal equipment. And when the beam failure recovery counter reaches the maximum value, the terminal equipment considers that the beam failure recovery is unsuccessful, and stops the beam failure recovery process. The recovery time of the recovery timer and the count value of the recovery counter may be configured by the network device, or may be preset values.
S106, the network equipment receives the beam failure recovery request sent by the terminal equipment.
In some embodiments, after receiving the beam failure recovery request, the network device may further transmit a beam failure recovery response to the terminal device, and the terminal device receives the beam failure recovery response, that is, performs S107 and S108.
The terminal device can detect DCI scrambled by C-RNTI or MCS-C-RNTI in a control resource set (CORESET) and a search space set (search space set) as BFRR.
The core space set and/or the search space set may be a dedicated core space set and/or a search space set configured by the network device for the terminal device, and are used for the network device to send downlink control resources of response information to the beam failure recovery request information after the terminal device sends the beam failure request.
It should also be understood that, in this embodiment, the time sequence of S101 and S102 in the beam failure recovery flow is not limited, S102 may precede S101, S101 may precede S102, or S102 and S101 may be performed simultaneously. It should also be understood that S107 and S108 are optional steps.
When the terminal equipment determines that the beam fails, the MAC-CE used for bearing the beam failure recovery request information is sent to the network equipment on any PUSCH, if the MAC-CE used for bearing the beam failure recovery request information can be transmitted on any PUSCH, the reliability of one-time transmission of the MAC-CE is possibly low, the MAC-CE is required to be ensured to be successfully transmitted by means of retransmission, and the beam failure recovery delay is increased.
For example, if a certain PUSCH resource is scheduled by a certain uplink grant (ul grant), and if the code rate indicated by the ul grant is higher, the transmission accuracy of the BFRQ is lower, and the reliability of BFRQ transmission needs to be improved by retransmission, thereby increasing the delay of beam failure recovery.
In order to solve the above problem, an embodiment of the present application provides a method for sending a beam failure recovery request, where the method includes: a specific PUSCH resource is selected on which to transmit at least one beam failure recovery request. Or, at least two beam failure recovery requests are transmitted on any PUSCH resource. Therefore, the transmission reliability is improved by limiting PUSCH resources transmitted by BFRQ or sending a plurality of same BFRQ, and the time delay of beam failure recovery is reduced.
Embodiments of the present application will be described in detail below with reference to the accompanying drawings.
The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a global system for mobile communications (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS), an LTE system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a universal microwave access (WiMAX) communication system, a future fifth generation (5G) mobile communication system or a New Radio (NR), etc., the 5G mobile communication system described in the present application includes a non-standalone (NSA) 5G mobile communication system and/or a Standalone (SA) 5G mobile communication system. The technical scheme provided by the application can also be applied to future communication systems, such as a sixth generation mobile communication system. The communication system may also be a PLMN network, a device-to-device (D2D) network, a machine-to-machine (M2M) network, an IoT network, or other network.
Fig. 2 is a schematic architecture diagram of a communication system applied to an embodiment of the present application. As shown in fig. 2, the communication system 200 includes a network device 210 and a terminal device 220. The terminal device 220 is connected to the network device 210 in a wireless manner. Fig. 2 is a schematic diagram, and the communication system may further include other devices, such as a core network device, a wireless relay device, and a wireless backhaul device, which are not shown in fig. 2. The core network device and the network device may be separate physical devices, or the function of the core network device and the logic function of the network device may be integrated on the same physical device, or a physical device may be integrated with a part of the function of the core network device and a part of the function of the network device. The terminal equipment may be fixed or mobile. The embodiments of the present application do not limit the number of terminal devices, core network devices, radio access network devices, and terminal devices included in the communication system.
The communication system 200 is in a single Carrier Aggregation (CA) scenario, the communication system 200 includes a network device 210 and a terminal device 220, the network device 210 and the terminal device 220 communicate via a wireless network, and when the terminal device 220 detects that a link between the network device 210 and the terminal device 220 fails, the terminal device 220 sends a BFRQ to the network device 210. Optionally, after receiving the BFRQ, the network device 210 sends a Beam Failure Recovery Response (BFRR) or a reconfiguration link to the terminal device 220.
It should be understood that one or more cells may be included under network device 210 in fig. 2. For example, the network device may include a first cell and a second cell, and if a link between the terminal device and the network device in the second cell fails, the first cell may assist the second cell in performing link recovery, for example, the terminal device may send the BFRQ information to the network device on an uplink resource belonging to the first cell, and the terminal device may receive the BFRR information sent by the network device on a downlink resource belonging to the second cell.
When the transmission direction of the communication system 200 is uplink transmission, the terminal device 220 is a sending end, and the network device 210 is a receiving end, and when the transmission direction of the communication system 200 is downlink transmission, the network device 210 is a sending end, and the terminal device 220 is a receiving end.
Fig. 3 is a communication system 300 to which the present application is applicable. The communication system 300 is in a Dual Connectivity (DC) or coordinated multipoint transmission/reception (CoMP) scenario, the communication system 300 includes a network device 310, a network device 320, and a terminal device 330, the network device 310 is a network device at the time of initial access of the terminal device 330 and is responsible for RRC communication with the terminal device 330, and the network device 320 is added during RRC reconfiguration and is used to provide additional radio resources. The terminal device 330 configured with carrier aggregation is connected to the network device 310 and the network device 320, a link between the network device 310 and the terminal device 330 may be referred to as a first link, and a link between the network device 320 and the terminal device 330 may be referred to as a second link.
When both network device 310 and network device 320 may configure an uplink resource for transmitting a BFRQ to terminal device 330, and when the first link or the second link fails, terminal device 330 may send a BFRQ to network device 310 or network device 320 on the uplink resource for transmitting the BFRQ, and after receiving the BFRQ, network device 310 or network device 320 sends a BFRR to terminal device 330.
In particular, if the network device 320 is not configured with uplink resources for transmitting BFRQ, the terminal device 330 may recover the second link through the network device 310 when the second link fails.
The above-mentioned communication system applicable to the present application is only an example, and the communication system applicable to the present application is not limited thereto, for example, the number of network devices and terminal devices included in the communication system may also be other numbers, or a single base station, a multi-carrier aggregation scenario, a dual-link scenario, or a device to device (D2D) communication scenario may be adopted.
It should be understood that the technical solution of the embodiment of the present application may be applied to a cell assisting another cell or multiple cells in a carrier aggregation scenario to recover a link. Or under the double-link scene, one cell in one cell group assists another cell or a plurality of cells to recover the link.
It should be understood that the technical solution of the embodiment of the present application may also be applied to a single carrier or carrier aggregation or dual link scenario, where a cell fails to recover a beam of the cell on resources of the cell.
It should be understood that the technical solution in the embodiment of the present application may be applicable to a case 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, the Scell is high frequency. In a possible implementation manner, for an Scell without uplink resource configuration, the uplink resource of the Pcell may be used to assist the Scell in recovering a link. Typically, the low and high frequencies are relative and may be bounded by a particular frequency, such as 6 GHz.
It should be understood that the technical solution of the embodiment of the present application may also be applied to a coordinated multipoint transmission/reception (CoMP) scenario, where one TRP assists another TRP in recovering a link. The CoMP may be one or more of non-coherent joint transmission (NCJT), Coherent Joint Transmission (CJT), Joint Transmission (JT), and the like.
Terminal equipment in the embodiments of the present application may refer to user equipment, access terminals, subscriber units, subscriber stations, mobile stations, remote terminals, mobile devices, user terminals, wireless communication devices, user agents, or user devices. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G network or a terminal device in a future evolved Public Land Mobile Network (PLMN), and the like, which are not limited in this embodiment.
By way of example and not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable equipment can also be called wearing formula smart machine, is to use wearing formula technique to carry out intelligent design, develop the general term of the equipment that can wear to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. A wearable device is either worn directly on the body or is a portable device that is integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.
In addition, in the embodiment of the present application, the terminal device may also be a terminal device in an internet of things (IoT) system, where IoT is an important component of future information technology development, and a main technical feature of the present application is to connect an article with a network through a communication technology, so as to implement an intelligent network with interconnected human-computer and interconnected objects. In the embodiment of the present application, the IOT technology may achieve massive connection, deep coverage, and power saving for the terminal through, for example, a Narrowband (NB) technology.
In addition, in this embodiment of the application, the terminal device may further include sensors such as an intelligent printer, a train detector, and a gas station, and the main functions include collecting data (part of the terminal device), receiving control information and downlink data of the network device, and sending electromagnetic waves to transmit uplink data to the network device.
The network device in this embodiment may be a device for communicating with a terminal device, where the network device may be a Base Transceiver Station (BTS) in a global system for mobile communications (GSM) system or a Code Division Multiple Access (CDMA) system, may also be a base station (NodeB) in a Wideband Code Division Multiple Access (WCDMA) system, may also be an evolved NodeB (eNB) or eNodeB) in an LTE system, may also be a wireless controller in a Cloud Radio Access Network (CRAN) scenario, or may be a relay station, an access point, a vehicle-mounted device, a wearable device, a network device in a future 5G network, or a network device in a future evolved PLMN network, and the like, and the present embodiment is not limited.
The network device in this embodiment may be a device in a wireless network, for example, a Radio Access Network (RAN) node that accesses a terminal to the wireless network. Currently, some examples of RAN nodes are: a base station, a next generation base station gNB, a Transmission Reception Point (TRP), an evolved Node B (eNB), a home base station, a baseband unit (BBU), or an Access Point (AP) in a WiFi system. In one network configuration, a network device may include a Centralized Unit (CU) node, or a Distributed Unit (DU) node, or a RAN device including a CU node and a DU node.
The application is mainly applied to a 5G NR system. The present application can also be applied to other communication systems, as long as the existing entity in the communication system needs to send the indication information of the transmission direction, and another entity needs to receive the indication information and determine the transmission direction within a certain time according to the indication information. Fig. 4 is a diagram illustrating an example of a communication system according to an embodiment of the present application. As shown in fig. 3, the base station and the terminal apparatuses 1 to 6 constitute a communication system. In this communication system, terminal apparatuses 1 to 6 can transmit uplink data to a base station, and the base station receives the uplink data transmitted from terminal apparatuses 1 to 6. The base station may transmit downlink data to the terminal apparatuses 1 to 6, and the terminal apparatuses 1 to 6 may receive the downlink data. Further, the terminal apparatuses 4 to 6 may constitute one communication system. In the communication system, terminal device 5 may receive uplink information transmitted by terminal device 4 or terminal device 6, and terminal device 5 may transmit downlink information to terminal device 4 or terminal device 6.
The network equipment and the terminal equipment can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; can also be deployed on the water surface; it may also be deployed on airborne airplanes, balloons and satellite vehicles. The embodiment of the application does not limit the application scenarios of the network device and the terminal device.
The network device and the terminal device may communicate with each other through a licensed spectrum (licensed spectrum), may communicate with each other through an unlicensed spectrum (unlicensed spectrum), or may communicate with each other through both the licensed spectrum and the unlicensed spectrum. The network device and the terminal device may communicate with each other through a frequency spectrum of 6 gigahertz (GHz) or less, through a frequency spectrum of 6GHz or more, or through both a frequency spectrum of 6GHz or less and a frequency spectrum of 6GHz or more. The embodiments of the present application do not limit the spectrum resources used between the network device and the terminal device.
In the embodiment of the present application, the time domain symbol may be an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a single carrier-frequency division multiplexing (SC-FDM) symbol. The symbols in the embodiments of the present application all refer to time domain symbols, if not otherwise specified.
It can be understood that, in the embodiment of the present application, the PDSCH, the PDCCH, and the PUSCH are only used as examples of the downlink data channel, the downlink control channel, and the uplink data channel, and in different systems and different scenarios, the data channel and the control channel may have different names, which is not limited in the embodiment of the present application.
Next, a method of transmitting a beam failure recovery request will be described in detail. Fig. 5 is a flowchart of a method for sending a beam failure recovery request according to an embodiment of the present application. As shown in fig. 5, the method may include:
s501, the terminal device determines a first resource.
After the terminal device determines that the beam fails, it needs to send a beam failure recovery request to the network device. In some embodiments, the terminal device determines a first resource for sending the beam failure recovery request, and sends the beam failure recovery request on the first resource, so as to reduce the beam failure recovery delay by limiting the PUSCH resource transmitted by the BFRQ.
It should be understood that the process of the terminal device determining the beam failure may refer to S101, which is not described herein again.
For example, as shown in fig. 6, the terminal device may determine the first resource in any one of the following manners S501a to S501 d.
S501a, the terminal device determines the first resource according to the beam failure case counter.
In some embodiments, the network device may configure the beam failure detection parameter for the cell to which the terminal device belongs through RRC signaling or MAC-CE signaling. The beam failure detection parameter includes a beam failure case maximum number (beamfailurelnstancememax count). The terminal device maintains a beam failure instance counter (BFI counter) for one cell or one cell group to realize beam failure detection. When the BFI counter is 0, it indicates that the cell or the cell group has no beam failure, and the link quality of the cell or the cell group is good, so the terminal device may select the resource of the cell with the beam failure case counter of 0 to determine as the first resource.
It should be understood that one cell group may include one or more cells. The cell group may be referred to as MCG or SCG. The group of cells may also be configured by the network device or may be indicated or determined in other ways. The cell group may have other definition or indication methods, and the definition or indication method of the cell group is not limited in the embodiments of the present application.
It should be understood that the specific use method of the BFI counter may refer to S101, and is not described herein again.
S501b, the terminal device determines the first resource according to the subcarrier spacing.
In some embodiments, the terminal device may receive one or more indication information sent by the network device, where the one or more indication information indicates K resources, and the K resources may be PUSCH resources. Or, the network device configures K resources for the terminal device in advance. Wherein K is an integer, and K is more than or equal to 1. Alternatively, the resource may refer to an Orthogonal Frequency Division Multiplexing (OFDM) symbol over a time unit. A time unit may refer to a time slot, a sub-slot, a micro-slot, etc. The K resources may be frequency division multiplexed resources, or may be time division multiplexed resources, or may be code division multiplexed resources.
Since the larger the subcarrier spacing, the shorter one OFDM symbol length. The resources of the largest subcarrier spacing can be transmitted faster. Therefore, the terminal device may select the resource of the largest subcarrier interval among the subcarrier intervals of the K resources to determine as the first resource, so as to complete transmission of the beam failure request more quickly.
The terminal device may determine the first resource according to a subcarrier spacing, where the subcarrier spacing of the first resource is largest among subcarrier spacings of K resources.
Or it may be described that the terminal device determines the first resource according to the subcarrier spacing, and 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.
Or it may be described that the terminal device determines the first resource according to the subcarrier spacing, and 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.
S501c, the terminal device determines the first resource according to the repeated identification.
In some embodiments, the network device configures the terminal device with the resource carrying the repeated identifier through RRC signaling or MAC-CE signaling or DCI signaling. The terminal device may determine the resource carrying the duplicate identifier as the first resource. The duplicate identification indicates that the resource can be used to repeatedly transmit multiple identical information. Or the transmission reliability of the resource carrying the repeated identifier is higher, or the resource carrying the repeated identifier can be used for the transmission of the URLLC service, and the resource allocated for the service needs to ensure the transmission with high reliability and low delay. Therefore, the beam failure request is transmitted on the resource carrying the repeated identification, so that the reliability of the transmission of the beam failure request can be ensured, the beam failure recovery can be completed in time, and the beam failure recovery time delay can be reduced.
The resource carrying the duplicate identifier may also be described as a resource configured with the duplicate identifier or a resource configured with the duplicate identifier parameter. The duplicate identification may also be referred to as an "aggregation factor".
That is, the terminal device may determine the first resource configured with the Aggregation Factor according to the Aggregation Factor (Aggregation Factor). The aggregation factor indicates the number of repetitions of data or information carried by the PUSCH resources. Understandably, the number of repetitions is generally greater than 1.
S501d, the terminal equipment determines the first resource according to the modulation and coding mode.
In some embodiments, the network device configures L resources for the terminal device through RRC signaling or MAC-CE signaling or DCI signaling, and further indicates corresponding modulation and coding schemes for the L resources, where L is an integer and is greater than or equal to 1. The terminal device may select a resource of a minimum modulation and coding scheme among modulation and coding schemes corresponding to the L resources to determine as the first resource. Due to the small modulation and coding mode, a low-order modulation mode and a low-rate channel coding scheme are adopted to ensure the communication quality, the transmission reliability of the beam failure recovery request can be ensured by selecting the small modulation and coding mode, the retransmission of the beam failure recovery request is further avoided, and the time delay of the beam failure recovery is reduced. Optionally, the modulation and coding scheme corresponding to the first resource may refer to a modulation and coding scheme indicated by the indication information of the first resource.
Optionally, the "modulation and coding scheme" in the embodiment of the present application may also be replaced by a "modulation order", and may also be replaced by a "code rate".
It should be noted that, the rules described in S501a to S501d may be used in combination or individually, and the present application is not limited thereto.
In other embodiments, S501a and S501b may be used in combination. For example, the terminal device may select, as the first resource, a resource having a largest subcarrier spacing in the resource of the cell in which the beam failure case counter is 0, where the terminal device selects the resource of the cell in which the beam failure case counter is 0.
In other possible embodiments, S501a and S501c may be used in combination. For example, the terminal device may select, as the first resource, a resource in which the aggregation factor is configured from the resources of the cells in which the beam failure case counters are 0.
In other possible embodiments, S501a and S501d may be used in combination. For example, the terminal device may select, as the first resource, a resource with the smallest modulation and coding scheme from among the resources of the cells with the beam failure case counters of 0.
In other embodiments, any two or any three of S501a, S501b, S501c, and S501d may be used in combination or any four may be used in combination. When a plurality of rules are used in combination, it is necessary to define which rule is preferentially used (i.e., which rule is preferentially used for selecting resources).
Optionally, the priority of S501a is greater than the priority of at least one of the following rules: s501b, S501c, and S501 d. Such as: s501a, S501b, S501c, and S501d all exist, then the priority of S501a is highest.
Optionally, the priority of S501b is greater than the priorities of S501c and S501 d; or the priority of S501b is greater than the priority of S501c or S501 d.
Optionally the priority of S501c is greater than the priority of S501 d.
The terminal device may select the resource according to the rule with the higher priority, and when there are multiple resources in the resource, the terminal device may select the resource from the multiple resources according to the rule with the second highest priority, and so on.
The following are exemplary: s501a, S501b, and S501c are used in combination, or S501a, S501b, and S501d are used in combination. For example: if the terminal equipment selects the resource with the maximum interval of more than two subcarriers from the resources of the cell with the beam failure case counter of 0, the terminal equipment can also determine the first resource according to the repeated identifier or the modulation coding mode. For example, the resource carrying the repetition identifier or the modulation coding scheme with the minimum size among the resources with the maximum subcarrier spacing is determined as the first resource.
After the terminal device determines the first resource for transmitting the beam failure recovery request, S502 is performed.
S502, the terminal equipment sends N wave beam failure recovery requests on the first resource.
The terminal device may repeatedly transmit the beam failure recovery request a plurality of times. The beam failure recovery request information may be carried on the MAC-CE.
Illustratively, the terminal device transmits N identical MAC-CEs carrying beam failure recovery request information on one or more PUSCH resources. Wherein N is an integer greater than or equal to 1.
It is to be understood that in one possible implementation, the first resource belongs to a first time unit, and the terminal device may repeatedly transmit the first resource N times in the first time unit, where each first resource carries one or more beam failure recovery requests. For example, the terminal device may repeatedly transmit the first resources N times in N first time units, where each first resource carries one beam failure recovery request.
The N beam failure recovery requests may be sent simultaneously or in a time-shared manner.
In one possible implementation, N is an integer greater than 1, and N beam failure recovery requests are sent on one first resource. In another possible implementation manner, N is an integer greater than 1, and the N beam failure recovery requests are respectively transmitted on the plurality of first resources. For example: the N beam failure recovery requests are transmitted on a plurality of first resources, respectively.
In one embodiment, N >1, N beam failure recovery requests are independently encoded. By repeatedly transmitting a plurality of beam failure recovery requests, the reliability of beam failure recovery request transmission is improved. The independent coding means that two pieces of information are independently coded before being sent, two bit sequences are generated after coding, the two coded bit sequences are respectively mapped to different time-frequency space resources (at least one of the time-frequency resources, the frequency-domain resources and the space-domain resources is different), and one device sends the two bit sequences to the other device. After receiving, the other device decodes the two bit sequences on the two resources respectively to obtain the two pieces of information. For example: the first information and the second information. The independent coding means that the first information and the second information are obtained by coding respectively. For example, the first information is represented by Q1 bits, the second information is represented 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 transmits the Q1 'bits and Q2' bits to the network device. The network equipment decodes the Q1' bits to obtain the first information; the Q2' bits are decoded to obtain the second information.
In other embodiments, when N >1, the N beam failure recovery requests are the same. The N beam failure recovery requests are identical, which means that the N beam failure recovery requests include completely identical content.
It should be understood that, in the embodiments of the present application, the beam failure recovery request may be used to indicate cell information of the beam failure cell. The beam failure recovery request may include identification information of the beam failure cell and/or reference signal information of the recovery beam failure cell. Or, the cell information of the beam failed cell may include identification information of the beam failed cell and/or reference signal information of the recovery beam failed cell. The terminal device may send the beam failure recovery request to the network device carried on the MAC-CE. It should be understood that, in the embodiments of the present application, the identification information of the beam failure cell may be an identification of the beam failure cell, or may be an index of the beam failure cell, or may be indication information indicating an identification of the beam failure cell (for example, a cell identification is indicated by a bitmap, where each bit in the bitmap corresponds to a cell, when the bit is 1, the cell corresponding to the bit has a beam failure, and when the bit is 0, the cell corresponding to the bit has no beam failure).
It should be understood that, in the embodiments of the present application, the reference signal information of the cell with the failed beam recovery may be a reference signal resource index of the cell with the failed beam recovery, may also be a reference signal resource index of the cell with the failed beam recovery and a signal quality of the reference signal resource, and may also be indication information that the reference signal resource of the cell with the failed beam recovery is not identified. The reference signal resource of the cell with failed beam recovery may be a CSI-RS resource or an SSB resource.
In other embodiments, N is predefined or configured. By predefined is understood predefined in a standard or protocol. The terminal device and the network device may pre-store the predefined value of N, where N is an integer and N is greater than or equal to 1. For example, N ═ 2. When the terminal device needs to send a beam failure recovery request, N may be locally obtained, and the number of times of sending the beam failure recovery request is determined. The configuration may be understood as that the network device configures the value of N for the terminal device through signaling. The signaling may be RRC signaling, MAC-CE signaling, or DCI signaling.
In other embodiments, the terminal device may adjust N according to a transmission code rate of an uplink grant (ul grant). For example, N is determined according to MCS. The MCS may be indicated by indication information indicating PUSCH (such as DCI), or may be indicated by RRC signaling or other information such as MAC-CE or system information. When the MCS is greater than or equal to a preset threshold, N is equal to P; when the MCS is smaller than a preset threshold, N is Q; wherein P and Q are integers, P is not less than 0, Q is not less than 0, and P is not less than Q. For example, P is 2 and Q is 1. The preset threshold may be configured by the network device or may be predefined by the protocol. Optionally, the "MCS" in the embodiment of the present application may also be replaced by a "modulation order", and may also be replaced by a "code rate".
S503, the network equipment determines the first resource.
The network device may determine the first resource according to at least one parameter of a beam failure case counter, a subcarrier spacing, a repetition identification, and a modulation coding scheme. For a detailed explanation, reference may be made to the description of S501, which is not repeated.
In some embodiments, the network device determining the first resource is an optional step.
S504, the network device receives N wave beam failure recovery requests on the first resource.
After receiving the N beam failure recovery requests, the network device independently decodes the N beam failure recovery requests. For example, the network device receives and decodes two bit sequences on two resources to obtain the two pieces of information. For example: the first information and the second information. The independent coding means that the first information and the second information are obtained by coding respectively. For example, the first information is represented by Q1 bits, the second information is represented 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 transmits the Q1 'bits and Q2' bits to the network device. The network equipment decodes the Q1' bits to obtain the first information; the Q2' bits are decoded to obtain the second information.
According to the method for sending the beam failure recovery request, the PUSCH resource transmitted by the BFRQ is limited, or the transmission reliability is improved by sending a plurality of same BFRQ, so that the beam failure recovery time delay is reduced.
In some embodiments, the terminal device may select the first resource from the second resources to transmit the link failure recovery request information according to the method described above.
It should be understood that the resources carrying N repeated BFRQs may be made in several possible ways:
mode 1: the terminal device may select S104 to configure or instruct a PUSCH resource in the PUSCH to transmit N repeated BFRQs (which may also be referred to as N identical BFRQ MAC-CEs). Optionally, the N repeated BFRQ information is independently encoded.
Mode 2: the terminal device may select S104 that the network device configures or instructs multiple PUSCH resources in the PUSCH to transmit N repeated BFRQs (which may also be referred to as N identical BFRQ MAC-CEs). For example, the terminal device selects 2 PUSCH resources to respectively carry 2 BFRQ MAC-CEs.
As for the mode 1 and the mode 2, it is an optional step that the terminal device selects the PUSCH resource to transmit the beam failure recovery request information according to the preset rule. That is, the terminal device may not perform the selection of the PUSCH resource by the terminal device according to the preset rule to transmit the beam failure recovery request information. The PUSCH resources selected by the terminal device at this time may depend on the implementation of the terminal device.
Mode 3: the terminal device carries the N identical BFRQs on the first resource determined in S501. The first resource may be determined from the second resource by the terminal device according to the method described in S501.
It should be noted that the present embodiment may further include other steps, such as beam failure detection, which is specifically described with reference to S101. The network device may also configure second resources for the terminal device, and the terminal device selects one or more resources from the second resources as first resources and sends the N beam failure recovery requests on the first resources. For details, reference may be made to the description of the above embodiment S104 for a method for obtaining the second resource by the terminal device, which is not described in detail.
It should be understood that in the embodiments of the present application, the "N identical BFRQs", "N beam failure recovery requests", and "N repeated BFRQs" may be simply referred to as second request information.
According to the method for sending the beam failure recovery request, the information transmission reliability is improved by limiting the resource for sending the link failure recovery request information, the information transmission time delay is reduced, and the link failure recovery with high reliability and low time delay is realized.
Fig. 7 is a flowchart of a method for sending a beam failure recovery request according to an embodiment of the present application. As shown in fig. 7, the method may include:
s701, the terminal device determines that the beam between the terminal device and the network device fails.
In some embodiments, the terminal device may measure a beam failure detection reference signal resource set (beam failure detection RS set), and determine a beam failure between the terminal device and the network device. The detailed explanation can refer to the explanation of S101 and is not repeated.
S702, the terminal equipment identifies the new link.
In some embodiments, the terminal device may identify reference signals in a candidate set of reference signal resources (candidate beam identification RS sets). The terminal device may recover the link based on the reference signal. The detailed explanation can refer to the explanation of S102, and is not repeated.
S703, the terminal equipment sends N wave beam failure recovery requests.
The terminal device may repeat the beam failure recovery request twice or more. The beam failure recovery request information may be carried on the MAC-CE.
Illustratively, the terminal device transmits N identical MAC-CEs carrying beam failure recovery request information on one or more PUSCH resources. Wherein N is an integer greater than or equal to 2. The N beam failure recovery requests are independently coded. N is predefined or configured. Alternatively, N is determined from the MCS. The detailed explanation can refer to the explanation of S502, which is not repeated.
S704, the network equipment receives the N wave beam failure recovery requests.
S705, the network device sends a beam failure recovery response to the terminal device.
S706, the terminal device receives the beam failure recovery response sent by the network device.
According to the method for sending the beam failure recovery request, the beam failure recovery request information is repeatedly sent for multiple times, so that the information transmission reliability is improved, the information transmission time delay is reduced, and the link failure recovery with high reliability and low time delay is realized.
It is to be understood that, in order to implement the functions in the above embodiments, the network device and the terminal device include hardware structures and/or software modules for performing the respective functions. Those of skill in the art will readily appreciate that the various illustrative elements and method steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software driven hardware depends on the particular application scenario and design constraints imposed on the solution.
Fig. 8 and 9 are schematic structural diagrams of a possible communication device provided in an embodiment of the present application. These communication devices can be used to implement the functions of the terminal device or the network device in the above method embodiments, so that the beneficial effects of the above method embodiments can also be achieved. In the embodiment of the present application, the communication apparatus may be the terminal device 220 shown in fig. 2, the network device 210 shown in fig. 2, or a module (e.g., a chip) applied to the terminal device or the network device.
As shown in fig. 8, the communication device 800 includes a processing unit 810 and a transceiving unit 820. The communication apparatus 800 is used to implement the functions of the terminal device or the network device in the method embodiments shown in fig. 5 to 7.
When the communication apparatus 800 is used to implement the functions of the terminal device in the method embodiment shown in fig. 5: the transceiving unit 820 is configured to perform S502; the processing unit 810 is configured to execute S501.
When the communication apparatus 800 is used to implement the functions of the network device in the method embodiment shown in fig. 5: the transceiving unit 820 is configured to perform S504; the processing unit 810 is configured to execute S503.
When the communication apparatus 800 is used to implement the functions of the terminal device in the method embodiment shown in fig. 6: the transceiving unit 820 is configured to perform S502; the processing unit 810 is configured to execute S501 a-S501 d.
When the communication apparatus 800 is used to implement the functions of the network device in the method embodiment shown in fig. 6: the transceiving unit 820 is configured to perform S504; the processing unit 810 is configured to execute S503.
When the communication apparatus 800 is used to implement the functions of the terminal device in the method embodiment shown in fig. 7: the transceiving unit 820 is configured to perform S703 and S706; the processing unit 810 is configured to execute S701 to S702.
When the communication apparatus 800 is used to implement the functions of the network device in the method embodiment shown in fig. 7: the transceiving unit 820 is configured to perform S704 and S705.
More detailed descriptions about the processing unit 810 and the transceiver 820 can be directly obtained by referring to the related descriptions in the method embodiments shown in fig. 5 to fig. 7, which are not repeated herein.
As shown in fig. 9, 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 may be a transceiver or an input-output interface. Optionally, the communication device 900 may further include a memory 930 for storing instructions to be executed by the processor 910 or for storing input data required by the processor 910 to execute the instructions or for storing data generated by the processor 910 after executing the instructions.
When the communication device 900 is configured to implement the methods shown in fig. 5 to 7, the processor 910 is configured to perform the functions of the processing unit 810, and the interface circuit 920 is configured to perform the functions of the transceiving unit 820.
When the 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 embodiment. The terminal device chip receives information from other modules (such as a radio frequency module or an antenna) in the terminal device, wherein the information is sent to the terminal device by the network device; or, the terminal device chip sends information to other modules (such as a radio frequency module or an antenna) in the terminal device, where the information is sent by the terminal device to the network device.
When the 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 a radio frequency module or an antenna) in the network device, wherein the information is sent to the network device by the terminal device; alternatively, the network device chip sends information to other modules (such as a radio frequency module or an antenna) in the network device, and the information is sent by the network device to the terminal device.
It is understood that the Processor in the embodiments of the present Application may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The general purpose processor may be a microprocessor, but may be any conventional processor.
The method steps in the embodiments of the present application may be implemented by hardware, or may be implemented by software instructions executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash Memory, Read-Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may reside in a network device or a terminal device. Of course, the processor and the storage medium may reside as discrete components in a network device or a terminal device.
Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical functional division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, that is, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part 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 the present application are performed in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, a network appliance, a user device, or other programmable apparatus. The computer program or instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer program or instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire or wirelessly. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that integrates one or more available media. The usable medium may be a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape; or optical media such as Digital Video Disks (DVDs); it may also be a semiconductor medium, such as a Solid State Drive (SSD).
In the embodiments of the present application, unless otherwise specified or conflicting with respect to logic, the terms and/or descriptions in different embodiments have consistency and may be mutually cited, and technical features in different embodiments may be combined to form a new embodiment according to their inherent logic relationship.
In the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. In the description of the text of the present application, the character "/" generally indicates that the former and latter associated objects are in an "or" relationship; in the formula of the present application, the character "/" indicates that the preceding and following related objects are in a relationship of "division".
It is to be understood that the various numerical references referred to in the embodiments of the present application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of the present application. The sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of the processes should be determined by their functions and inherent logic.
The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (30)

  1. A method of transmitting a beam failure recovery request, comprising:
    determining a first resource;
    and sending N beam failure recovery requests on the first resource, wherein N is an integer greater than 1 or equal to 1.
  2. A method for receiving a beam failure recovery request, comprising:
    determining a first resource;
    receiving N beam failure recovery requests on the first resource, where N is an integer greater than 1 or equal to 1.
  3. The method of claim 1 or 2, wherein the determining the first resource comprises:
    and determining the first resource according to the beam failure case counter, wherein the beam failure case counter of the cell to which the first resource belongs is 0.
  4. The method of any of claims 1-3, wherein the determining the first resource comprises:
    and determining the first resource according to the subcarrier spacing, wherein the subcarrier spacing of the first resource is the largest in the subcarrier spacing of K resources, K is an integer and is more than or equal to 1.
  5. The method of any of claims 1-4, wherein the determining the first resource comprises:
    and determining the first resource according to the repeated identifier, wherein the repeated identifier is configured for the first resource.
  6. The method of any of claims 1-5, wherein the determining the first resource comprises:
    and determining the first resource according to a modulation coding mode, wherein the modulation coding mode corresponding to the first resource is the smallest in the modulation coding modes corresponding to the L resources, L is an integer and is more than or equal to 1.
  7. The method according to any of claims 1-6, wherein N is predefined or configured.
  8. The method according to any of claims 1-6, wherein N is determined according to a modulation and coding scheme, MCS.
  9. The method of claim 8, wherein the N is determined according to an MCS, comprising:
    when the MCS is greater than or equal to a preset threshold, the N is equal to P; when the MCS is smaller than a preset threshold, the N is Q; wherein P and Q are integers, P is not less than 0, Q is not less than 0, and P is not less than Q.
  10. The method according to any of claims 1-9, wherein the N beam failure recovery requests are independently coded when N > 1.
  11. The method according to any of claims 1-10, wherein the N beam failure recovery requests are the same when N > 1.
  12. A method of transmitting a beam failure recovery request, comprising:
    sending N wave beam failure recovery requests on a first resource, wherein N is an integer and is more than or equal to 2;
    receive beam failure recovery response BFRR.
  13. A method for receiving a beam failure recovery request, comprising:
    receiving N wave beam failure recovery requests on a first resource, wherein N is an integer and is more than or equal to 2;
    a beam failure recovery response BFRR is transmitted.
  14. The method of claim 12 or 13, wherein the N beam failure recovery requests are independently encoded, and wherein the N beam failure recovery requests are the same.
  15. A communications apparatus, comprising:
    a processing unit for determining a first resource;
    a sending unit, configured to send N beam failure recovery requests on the first resource, where N is an integer greater than 1 or equal to 1.
  16. A communications apparatus, comprising:
    a processing unit for determining a first resource;
    a receiving unit, configured to receive N beam failure recovery requests on the first resource, where N is an integer greater than 1 or equal to 1.
  17. The apparatus according to claim 15 or 16, wherein the processing unit is configured to:
    and determining the first resource according to the beam failure case counter, wherein the beam failure case counter of the cell to which the first resource belongs is 0.
  18. The apparatus according to any of claims 15-17, wherein the processing unit is configured to:
    and determining the first resource according to the subcarrier spacing, wherein the subcarrier spacing of the first resource is the largest in the subcarrier spacing of K resources, K is an integer and is more than or equal to 1.
  19. The apparatus according to any of claims 15-18, wherein the processing unit is configured to:
    and determining the first resource according to the repeated identifier, wherein the repeated identifier is configured for the first resource.
  20. The apparatus according to any of claims 15-19, wherein the processing unit is configured to:
    and determining the first resource according to a modulation coding mode, wherein the modulation coding mode corresponding to the first resource is the smallest in the modulation coding modes corresponding to the L resources, L is an integer and is more than or equal to 1.
  21. The apparatus according to any of claims 15-20, wherein N is predefined or configured.
  22. The apparatus of any of claims 15-20, wherein the N is determined according to an MCS.
  23. The apparatus of claim 22, wherein the N is determined according to an MCS, comprising:
    when the MCS is greater than or equal to a preset threshold, the N is equal to P; when the MCS is smaller than a preset threshold, the N is Q; wherein P and Q are integers, P is not less than 0, Q is not less than 0, and P is not less than Q.
  24. The apparatus according to any of claims 15-23, wherein the N beam failure recovery requests are independently coded when N > 1.
  25. The apparatus according to any of claims 15-24, wherein the N beam failure recovery requests are the same when N > 1.
  26. A communications apparatus, comprising:
    a sending unit, configured to send N beam failure recovery requests on a first resource, where N is an integer and is greater than or equal to 2;
    a receiving unit, configured to receive a beam failure recovery response BFRR.
  27. A communications apparatus, comprising:
    a receiving unit, configured to receive N beam failure recovery requests on a first resource, where N is an integer and is greater than or equal to 2;
    a transmitting unit, configured to transmit a beam failure recovery response BFRR.
  28. The apparatus of claim 26 or 27, wherein the N beam failure recovery requests are independently encoded, and wherein the N beam failure recovery requests are the same.
  29. A communications apparatus, comprising: at least one processor, memory and a bus, wherein the memory is for storing a computer program such that, when executed by the at least one processor, the computer program implements the method of transmitting a beam failure recovery request of any of claims 1, 3-11, 12 and 14 or implements the method of receiving a beam failure recovery request of any of claims 2, 3-11, 13 and 14.
  30. A computer-readable storage medium, comprising: computer software instructions;
    the computer software instructions, when run in a communication device or a chip built in a communication device, cause the communication device to perform the method of transmitting a beam failure recovery request according to any one of claims 1, 3-11, 12 and 14 or to implement the method of receiving a beam failure recovery request according to any one of claims 2, 3-11, 13 and 14.
CN201980098115.XA 2019-09-30 2019-09-30 Method and device for sending beam failure recovery request Pending CN114073146A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/109540 WO2021062672A1 (en) 2019-09-30 2019-09-30 Method and device for sending beam failure recovery request

Publications (1)

Publication Number Publication Date
CN114073146A true CN114073146A (en) 2022-02-18

Family

ID=75337625

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201980098115.XA Pending CN114073146A (en) 2019-09-30 2019-09-30 Method and device for sending beam failure recovery request

Country Status (2)

Country Link
CN (1) CN114073146A (en)
WO (1) WO2021062672A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110034844B (en) * 2018-01-12 2021-03-09 电信科学技术研究院有限公司 Information transmission method and device, first equipment and second equipment

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210204346A1 (en) * 2017-05-03 2021-07-01 Idac Holdings, Inc. Beam recovery mechanism
CN109039408B (en) * 2017-06-09 2021-07-13 维沃移动通信有限公司 Beam failure processing method, terminal and network equipment
CN113630900B (en) * 2017-06-26 2023-10-20 北京三星通信技术研究有限公司 Random access method, user equipment and base station equipment
US10779350B2 (en) * 2017-08-10 2020-09-15 Futurewei Technologies, Inc. Beam failure recovery request

Also Published As

Publication number Publication date
WO2021062672A1 (en) 2021-04-08

Similar Documents

Publication Publication Date Title
CN111586862B (en) Information indication method and device
US20220060302A1 (en) Communication method and communications apparatus
EP3195688B1 (en) Drx cycle configuration in dual connectivity
CN112312419B (en) Information reporting method and device
EP2939485B1 (en) Method and apparatus for measurement procedures with composite dynamic subframes in dynamic tdd
WO2018171006A1 (en) Interference measurement method and related device
CN110971361B (en) Control channel beam indication method and equipment
EP2995113B1 (en) Measurements in a wireless system
CN112567776A (en) System and method for communicating with a multiple antenna panel device
CN109287000B (en) Apparatus and method for setting secondary node and reporting in dual connectivity
CN112368969A (en) Device-to-device (D2D) channel measurement techniques
CN112087291B (en) Method and communication device for updating Transmission Configuration Indication (TCI) information
CN115175340A (en) Communication method and communication device
CN116112105A (en) Method, user equipment and network node for performing channel state measurements
US20220022274A1 (en) Link failure recovery method and apparatus
JP2019537885A (en) On / off time mask for short TTI
CN114041321A (en) Beam failure detection method and device
US20230137907A1 (en) Wireless communication method, terminal device, and network device
EP3817269A1 (en) Resource management method and device
CN110798900A (en) Method and device for recovering communication failure
CN114073146A (en) Method and device for sending beam failure recovery request
WO2020143053A1 (en) Method, device and computer readable medium for measuring sidelink received signal strength
US20220159767A1 (en) Communication Method And Communications Apparatus
WO2018202077A1 (en) Interference measurement method and device
CN116250194A (en) Wireless communication method, device and system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination