CN108811092B - Beam failure recovery processing method, terminal and network side equipment - Google Patents

Beam failure recovery processing method, terminal and network side equipment Download PDF

Info

Publication number
CN108811092B
CN108811092B CN201710296835.XA CN201710296835A CN108811092B CN 108811092 B CN108811092 B CN 108811092B CN 201710296835 A CN201710296835 A CN 201710296835A CN 108811092 B CN108811092 B CN 108811092B
Authority
CN
China
Prior art keywords
terminal
network side
candidate
preset time
timer
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.)
Active
Application number
CN201710296835.XA
Other languages
Chinese (zh)
Other versions
CN108811092A (en
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.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication 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 Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Priority to CN201710296835.XA priority Critical patent/CN108811092B/en
Publication of CN108811092A publication Critical patent/CN108811092A/en
Application granted granted Critical
Publication of CN108811092B publication Critical patent/CN108811092B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation based on the type of the allocated resource
    • H04W72/046Wireless resource allocation based on the type of the allocated resource the resource being in the space domain, e.g. beams
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/54Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/542Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality

Abstract

The application provides a beam failure recovery processing method, a terminal and network side equipment, wherein the method comprises the following steps: the terminal sends a beam failure recovery request to the network side equipment; and if the terminal determines that no available candidate beam exists, the terminal performs candidate beam measurement within a first preset time. That is, after the terminal measures the beam failure, if there is no available candidate beam, the terminal does not report the link failure, but waits for a period of time, and performs the candidate beam measurement in the period of time, so as to ensure the physical layer interactive between the terminal and the network side to recover the beam as much as possible, and reduce unnecessary recovery delay.

Description

Beam failure recovery processing method, terminal and network side equipment
Technical Field
The present application relates to wireless communication technologies, and in particular, to a beam failure recovery processing method, a terminal, and a network device.
Background
In future 5G (5Generation, fifth Generation) mobile communication systems, high frequency communication and large-scale antenna technology will be introduced to achieve the target of downlink transmission rate of 20 megabits per second (Gbps) and uplink transmission rate of 10 Gbps. In particular, high frequency communication can provide wider system bandwidth, and the antenna size can be smaller, which is more beneficial to the deployment of large-scale antennas in base stations and terminals. However, high frequency communication has the disadvantages of large path loss, easy interference, weak link, etc., and large-scale antenna technology can provide large antenna gain, so that the combination of high frequency communication and large-scale antenna is a necessary trend of future 5G mobile communication systems.
However, the problem of link vulnerability in high frequency communications still exists. In the prior art, when a signal is blocked in high-frequency communication, a beam failure recovery mechanism may be used to switch a beam, so as to switch a communication link from a poor beam to a candidate beam with a good communication link. However, if the beam failure recovery mechanism is started, if there is no suitable candidate beam, it may trigger the connection failure of the high-level radio link, and further generate a larger link recovery delay.
Disclosure of Invention
The application provides a beam failure recovery processing method, a terminal and network side equipment, which are used for providing a method for how to process a proper candidate beam if the proper candidate beam does not exist when a beam failure recovery mechanism is started.
A first aspect of the present application provides a beam failure recovery processing method, including:
the terminal sends a beam failure recovery request to the network side equipment;
and if the terminal determines that no available candidate beam exists, the terminal performs candidate beam measurement within a first preset time.
A second aspect of the present application provides a beam failure recovery processing method, including:
the method comprises the steps that network side equipment receives a beam failure recovery request sent by a terminal;
if the network side device determines that there is no available candidate beam, the network side device sends a second radio link failure message to a core network device if the network side device still does not receive beam reporting information containing the candidate beam sent by the terminal within a second preset time or the network side device receives a first radio link failure message sent by the terminal within the second preset time.
A third aspect of the present application provides a terminal, comprising:
a sending module, configured to send a beam failure recovery request to a network side device;
a determination module to determine that there are no available candidate beams;
and the measurement module is used for measuring the candidate beams in a first preset time.
A fourth aspect of the present application provides a network side device, including:
a receiving module, configured to receive a beam failure recovery request sent by a terminal;
a determination module to determine that there are no available candidate beams;
a sending module, configured to send a second radio link failure message to a core network device when the determining module determines that the beam reporting information including the candidate beam sent by the terminal is not received within a second preset time or the receiving module receives a first radio link failure message sent by the terminal within the second preset time.
A fifth aspect of the present application provides a terminal, where the network-side device includes a processor and a memory, where the memory is used to store a program, and the processor calls the program stored in the memory to execute the method provided in the first aspect of the present application.
A sixth aspect of the present application provides a network-side device, where the terminal includes a processor and a memory, where the memory is used to store a program, and the processor calls the program stored in the memory to execute the method provided in the second aspect of the present application.
A seventh aspect of the present application provides a terminal comprising at least one processing element (or chip) for performing the method of the above first aspect.
An eighth aspect of the present application provides a network-side device, comprising at least one processing element (or chip) for performing the method of the second aspect above.
A ninth aspect of the present application provides a program for performing the method of the above first aspect when executed by a processor.
A tenth aspect of the present application provides a program product, such as a computer readable storage medium, comprising the program of the ninth aspect.
An eleventh aspect of the present application provides a program for performing the method of the above second aspect when executed by a processor.
A twelfth aspect of the application provides a program product, such as a computer readable storage medium, comprising the program of the eleventh aspect.
A thirteenth aspect of the present application provides a computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the beam failure recovery processing method according to the first aspect.
A fourteenth aspect of the present application provides a computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the beam failure recovery processing method according to the second aspect.
In the beam failure recovery processing method, the terminal and the network side device provided by the application, based on the terminal side, after the terminal sends the beam failure recovery request to the network side device, if it is determined that no available candidate beam exists, the terminal performs candidate beam measurement within a first preset time. That is, after the terminal measures the beam failure, if there is no available candidate beam, the terminal does not report the link failure, but waits for a period of time, and performs the candidate beam measurement during the period of time. Based on the network side, after receiving a beam failure recovery request sent by the terminal, the network side equipment determines that there is no available candidate beam, and waits for a second preset time, and does not report link failure to the core network equipment within the second preset time unless the network side equipment does not receive beam report information containing the candidate beam sent by the terminal within the second preset time or receives a first radio link failure message sent by the terminal within the second preset time, and then sends a second radio link failure message to the core network equipment. The physical layer of the interaction between the terminal and the network side can be ensured to recover the wave beam as much as possible, and unnecessary recovery time delay is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to these drawings without inventive exercise.
FIG. 1 is a system architecture diagram according to an embodiment of the present disclosure;
fig. 2 is a schematic flow chart of a beam failure recovery processing method according to an embodiment of the present application;
fig. 3 is a schematic flow chart of a beam failure recovery processing method according to another embodiment of the present application;
fig. 4 is a schematic flow chart of a beam failure recovery processing method according to another embodiment of the present application;
fig. 5 is a schematic flow chart of a beam failure recovery processing method according to yet another embodiment of the present application;
fig. 6 is a schematic flow chart of a beam failure recovery processing method according to another embodiment of the present application;
fig. 7 is a schematic flow chart of a beam failure recovery processing method according to another embodiment of the present application;
fig. 8 is a schematic flow chart of a beam failure recovery processing method according to another embodiment of the present application;
fig. 9 is a schematic structural diagram of a terminal according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of a terminal according to another embodiment of the present application;
fig. 11 is a schematic structural diagram of a terminal according to another embodiment of the present application;
fig. 12 is a schematic structural diagram of a terminal according to still another embodiment of the present application;
fig. 13 is a schematic structural diagram of a terminal according to another embodiment of the present application;
fig. 14 is a schematic structural diagram of a network-side device according to an embodiment of the present application;
fig. 15 is a schematic structural diagram of a terminal according to another embodiment of the present application;
fig. 16 is a schematic structural diagram of a network-side device according to another embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Fig. 1 is a schematic diagram of a system architecture according to an embodiment of the present disclosure, and as shown in fig. 1, the system includes: network side device 01 and terminal 02.
The network side device 01 may be a Base Transceiver Station (BTS) in Global System for mobile communications (GSM) or Code Division Multiple Access (CDMA), a Base Station (NodeB, NB) in Wideband Code Division Multiple Access (WCDMA), an evolved Node B (evolved Node B, eNB or eNodeB) in LTE, a relay Station or Access point, or a Base Station in a future 5G network, and the like, which are not limited herein.
Terminal 02 can be a wireless terminal, which can be a device that provides voice and/or other traffic data connectivity to a user, a handheld device having wireless connection capability, or other processing device connected to a wireless modem, or can be a wired terminal. A wireless terminal, which may be a mobile terminal such as a mobile telephone (or "cellular" telephone) and a computer having a mobile terminal, e.g., a portable, pocket, hand-held, computer-included, or vehicle-mounted mobile device, may communicate with one or more core networks via a Radio Access Network (RAN), and may exchange language and/or data with the RAN. For example, devices such as Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs) are used. A wireless Terminal may also be referred to as a system, a Subscriber Unit (Subscriber Unit), a Subscriber Station (Subscriber Station), a Mobile Station (Mobile), a Remote Station (Remote Station), a Remote Terminal (Remote Terminal), an access Terminal (access Terminal), a User Terminal (User Terminal), a User Agent (User Agent), and a User Equipment (User device User Equipment), which are not limited herein.
In the scenario shown in fig. 1, signal transmission is implemented between the network-side device 01 and the terminal 02 through an antenna beam. Both the network side device 01 and the terminal 02 may include a plurality of beams, and for example, in fig. 1, it is assumed that the network side device 01 includes N beams and the terminal 02 includes M beams, where N, M are integers greater than 1. N and M may be the same or different, and the application is not limited.
It should be noted that, a situation that a connection failure may occur in a beam for performing signal transmission between the terminal and the network side device, and if there is no available candidate beam when starting beam recovery due to the connection failure, a link failure may be reported to the core network side by the network side device. Once link failure is reported to the core network, the core network may participate in the following process, that is, the core network device may first instruct the network side device to recover the link, and then the network side device and the terminal negotiate to recover the link, so that a large recovery delay may be generated. The method provided by the application solves the problem of beam connection failure on the premise of not reporting the core network as much as possible.
Fig. 2 is a schematic flow chart of a beam failure recovery processing method according to an embodiment of the present application, and as shown in fig. 2, this embodiment is mainly implemented from a terminal perspective: if there is no technical improvement of available candidate beams after the terminal sends the beam failure recovery request, the method comprises the following steps:
s201, the terminal sends a beam failure recovery request to the network side equipment.
In the process of signal transmission between the terminal and the network side device, a problem of connection failure may occur in a currently used beam, so that a signal cannot be normally transmitted.
The terminal may perform beam measurements to determine whether the beam connection is normal. Specifically, the signal transmission quality may be measured according to a reference signal sent by the network side, or the reference signal may be sent to the network side device to obtain the signal transmission quality measured by the network side device. For the beam currently in use, if the obtained signal transmission quality is lower than the preset threshold, the beam is considered to be failed. Similarly, if the measured signal transmission quality of one or more beams is greater than or equal to a predetermined threshold, the beam may be used as a candidate beam.
After detecting the beam failure, the terminal sends a beam failure recovery request to the network side device, so as to negotiate with the network side device to switch the candidate beam for signal transmission.
S202, if the terminal determines that no available candidate beam exists, the terminal performs candidate beam measurement within a first preset time.
Optionally, if the terminal determines that there is a candidate beam after measuring the beam failure, the terminal may notify the network side device of the fact that the candidate beam identifier is carried in the beam failure recovery request, so that the network side device switches the candidate beam to transmit the signal.
If the terminal determines that no available candidate beam exists after determining that the beam fails, the terminal performs candidate beam measurement within a certain time, that is, whether a beam with a signal transmission quality meeting a preset threshold is measured to be a candidate beam.
It should be noted that the absence of available candidate beams may include at least two layers: (1) there is no candidate beam currently, for example, the signal transmission quality calculated by the terminal according to the reference signal does not meet the preset threshold. (2) And the terminal acquires the candidate wave beam through measurement, and the network side equipment replies unavailable after reporting to the network side equipment. Optionally, it may be found by the network side device that the candidate beam is already occupied, for example, for transmitting other signals, and the application is not particularly limited.
In this embodiment, after the terminal sends the beam failure recovery request to the network side device, if it is determined that there is no available candidate beam, the terminal performs candidate beam measurement within a first preset time. That is, after the terminal measures the beam failure, if there is no available candidate beam, the terminal does not report the link failure, but waits for a period of time, and performs the candidate beam measurement in the period of time, so as to ensure the physical layer interactive between the terminal and the network side to recover the beam as much as possible, and reduce unnecessary recovery delay.
Fig. 3 is a schematic flow chart of a beam failure recovery processing method according to another embodiment of the present application, and as shown in fig. 3, the difference between the embodiment and the embodiment shown in fig. 2 is that the embodiment is mainly implemented from the perspective of a network side device: if there is no technical improvement of available candidate beams after receiving a beam failure recovery request sent by a terminal, the method comprises the following steps:
s301, the network side equipment receives a beam failure recovery request sent by the terminal.
Similar to the foregoing S201, after detecting the beam failure, the terminal may send a beam failure recovery request to the network side device.
S302, the network side equipment determines that no available candidate beam exists.
Alternatively, one possibility is that there is currently no candidate beam. Specifically, the network side device may determine that no candidate beam is reported by the terminal within a third preset time before the beam failure recovery request is received, and the beam failure recovery request does not carry the candidate beam, so that the network side device considers that there is no candidate beam. Another possibility is that the network side device receives the candidate beam reported by the terminal within the third preset time, or the candidate beam is carried in the beam failure recovery request, but the network side device finds that the candidate beam is currently unavailable.
Optionally, if the network side device finds that the candidate beam is not available, the terminal is notified that the candidate beam is not available.
S303, the network side device does not receive the beam report information including the candidate beam sent by the terminal within the second preset time, or receives the first radio link failure message sent by the terminal within the second preset time, and the network side device sends the second radio link failure message to the core network device.
After receiving the beam failure recovery request, the network side device waits for a period of time if it is determined that there is no available candidate beam, the terminal can perform candidate beam measurement within the period of time, and if the terminal measures for a period of time or does not find a suitable candidate beam, the terminal sends a first radio link failure message to the network side device, that is, the network side device informs the network side device of the link failure, and then the network side device sends a second radio link failure message to the core network device to report the core network device of the link failure.
It is also possible that after the network side device waits for a period of time, the terminal does not send the first radio link failure message, but does not report the candidate beam, that is, there is still no available candidate beam, and then the network side device sends the second radio link failure message to the core network device to report the core network device link failure.
In this embodiment, after receiving a beam failure recovery request sent by a terminal, a network side device determines that there is no available candidate beam, and waits for a second preset time, and does not report a link failure to a core network device in this time unless the network side device does not receive beam report information containing the candidate beam sent by the terminal within the second preset time or receives a first radio link failure message sent by the terminal within the second preset time, and then sends a second radio link failure message to the core network device. The physical layer of the interaction between the terminal and the network side can be ensured to recover the wave beam as much as possible, and unnecessary recovery time delay is reduced.
It should be noted that, in the above different embodiments, the second preset time and the first preset time may refer to the same preset time or different preset times, and specific examples are described below.
The candidate beams according to the above embodiments may refer to: at least 1 transmitting beam of the terminal and at least 1 receiving beam paired with the transmitting beam in the network side equipment; it can also refer to at least 1 receiving beam of the terminal and at least 1 transmitting beam paired with the receiving beam by the network side device; both of these cases may be included.
In one implementation scenario: if the candidate beams include at least 1 transmit beam of the terminal and at least 1 receive beam paired with the transmit beam in the network side device, the terminal may respectively transmit a reference signal using each transmit beam in a preset range of the terminal in the process of measuring the candidate beams. Accordingly, each receiving beam within the preset range of the network side device receives the reference signals sent by all the transmitting beams. One or more pairs of candidate beams with signal transmission quality meeting a preset threshold can be further determined. Specifically, if only one pair of candidate beams is needed, a pair of candidate beams with the best signal transmission quality, that is, the transmitting antenna with the best transmission quality and the receiving antenna with the best signal transmission from the transmitting antenna, may be selected from the beams satisfying the preset threshold, and is not particularly limited herein.
Similarly, in another implementation scenario, if the candidate beams include at least 1 receiving beam of the terminal and at least 1 transmitting beam paired with the receiving beam by the network-side device, the network-side device transmits the reference signal using each transmitting antenna within the preset range, and the terminal receives the reference signal transmitted by all transmitting antennas using each receiving antenna within the preset range. Further determining one or more pairs of candidate beams with signal transmission quality meeting a preset threshold
It should be noted that the preset range of beams may refer to one or more beams within the device beam management range, and these beams may be some or all of the beams of the device. Assuming that the terminal has 8 transmitting and receiving beams, and after 2 transmitting beams for transmitting data fail, the terminal measures and selects candidate beams among 4 transmitting beams in a preset range, and of course, without being limited thereto, the candidate beams may be measured and selected among all beams except the failed beams.
For the case that the terminal determines that the beam fails and has no available candidate beam, the scheme of the application waits for a period of time instead of directly reporting the link failure to the core network device, and in the period of time, the terminal can measure and search for the candidate beam to find the candidate beam in the prolonged period of time as far as possible so as to complete beam recovery. This time may be monitored by the terminal, such as described in the embodiment of fig. 2; or may be monitored by a network-side device as described in the embodiment shown in fig. 3; or may be monitored by both the terminal and the network side device.
In addition, after the terminal sends the beam failure recovery request to the network side device, the network side device replies a beam failure recovery response. The terminal may also perform candidate beam measurement for a period of time, with the time when the beam failure recovery response is received as a starting point. The candidate beam measurement may be performed for a period of time with the time when the beam failure recovery request is issued as a starting point. The period of time may be the first predetermined time or the second predetermined time.
Hereinafter, different implementations of candidate beam measurement timing, duration control, and the like after a beam failure will be described separately.
Alternatively, the first preset time may be preset in the terminal. The terminal may also receive configuration information including the first preset time, which is sent by the network side device, before performing the candidate beam measurement within the first preset time. Specifically, the configuration information including the first preset time may be sent by the network side device when the terminal accesses, or may be sent in a subsequent signal transmission process, which is not limited in this application.
In one mode, the terminal and the network side device are configured in advance with a time when the terminal sends out the beam failure recovery request as a first preset time starting point, or with a time when the terminal receives the beam failure recovery response as the first preset time starting point. The terminal may determine the length of the first preset time according to the configuration information including the first preset time. That is, the network side device indicates the length of the first preset time in the configuration information containing the first preset time.
In another mode, the network side device indicates the length and the starting time of the first preset time in the configuration information containing the first preset time. For example: the configuration information including the first preset time indicates the length of the first preset time, and the terminal takes the moment of sending the beam failure recovery request as the starting point of the first preset time. Or, the configuration information including the first preset time indicates the length of the first preset time, and the terminal takes the time when the beam failure recovery response is received as the starting point of the first preset time.
Alternatively, the first preset time may be pre-configured in the terminal, and no special configuration information is transmitted.
In one embodiment, the first preset time is timing time information of a first timer. I.e. the first preset time is realized by the first timer.
Correspondingly, the terminal receives the timing time information of the first timer sent by the network side equipment before the candidate beam measurement is carried out within the first preset time. Similarly to the above-described embodiment, the network-side device may indicate the timing length of the first timer, or indicate both the timing length of the first timer and the start time of the timing time of the first timer, depending on the specific situation.
Specifically, the terminal starts a first timer and performs candidate beam measurement within a timing time of the first timer.
Based on the foregoing embodiment, the network side device may not separately set the second preset time, and then the network side device may perform waiting without reporting the second radio link failure message until the terminal reports the candidate beam or sends the first radio link failure message.
Fig. 4 is a schematic flow chart of a beam failure recovery processing method according to another embodiment of the present application, and fig. 4 illustrates a beam failure recovery processing flow by taking an example of a terminal starting a first timer. As shown in fig. 4, the method includes:
s401, the terminal determines that the current beam connection fails.
S402, the terminal sends a beam failure recovery request to the network side equipment.
And S403, the terminal receives the beam failure recovery response sent by the network side equipment.
S404, the terminal determines that no available candidate beam exists.
S405, the terminal starts a first timer and performs candidate beam measurement within the timing time of the first timer.
It should be noted that the terminal itself knows that there is no candidate beam, and it may not take time to determine that there is no available candidate beam, that is, the terminal may start the first timer at the time when the beam failure recovery response is received.
If the terminal does not measure the candidate beam within the first preset time, S406 to S407 are performed. If the terminal measures the candidate beam within the first preset time, S408 to S409 are performed.
S406, the terminal sends a first radio link failure message to the network side equipment.
S407, the network side device sends a second radio link failure message to the core network device.
S408, the terminal sends the beam reporting information containing the candidate beams to the network side equipment.
S409, after determining that the candidate beam is available, the network side device enables the candidate beam and the terminal to transmit signals.
In this embodiment, after receiving the beam failure recovery response, if it is determined that there is no available candidate beam, the terminal starts the first timer, and performs candidate beam measurement within the timing time of the first timer, that is, the link failure is not reported temporarily, but the candidate beam measurement is continued for a certain time, so as to increase the chance of acquiring the candidate beam, thereby ensuring that the physical layer recovery beam interacted between the terminal and the network side is ensured as much as possible, and reducing unnecessary recovery delay.
On the basis of the embodiment of fig. 3, the network side device may send configuration information including the second preset time to the terminal. Specifically, the configuration information including the second preset time may be sent by the network side device when the terminal accesses, or may be sent in a subsequent signal transmission process, which is not limited in this application.
The second preset time may be a timing time of the first timer, or may be a timing time of the second timer.
Taking the first preset time as an example, the first preset time is a timing time of a second timer started by the network side device after receiving the beam failure recovery request. Namely, the network side device performs timing control.
Fig. 5 is a schematic flow chart of a beam failure recovery processing method according to still another embodiment of the present application, and fig. 5 illustrates a beam failure recovery processing flow by taking an example of a network side starting a second timer. As shown in fig. 5, the method includes:
s501, the terminal determines that the current beam connection fails.
S502, the terminal sends a beam failure recovery request to the network side equipment.
S503, the network side equipment determines that no available candidate beam exists, and starts a second timer.
Optionally, before S503, the network side device sends a beam measurement instruction to the terminal.
The beam measurement indication indicates a timing time of the second timer, and specifically may indicate a timing time length of the second timer, or indicate a timing time and a start time of the second timer. The terminal may know to perform candidate beam measurements within the timing time of the second timer according to a pre-configuration.
It should be noted that the network side device may know that there is no candidate beam, and may determine that there is no available candidate beam to occupy no time, that is, may start the second timer at the time of receiving the beam failure recovery request.
S504, the terminal receives the beam failure recovery response sent by the network side equipment.
If the terminal does not measure the candidate beam within the timing time of the second timer, S505 to S506 are performed. If the terminal measures the candidate beam within the timing time of the second timer, S507 to S508 are performed.
And S505, the terminal sends a first radio link failure message to the network side equipment.
S506, the network side equipment sends a second radio link failure message to the core network equipment.
S507, the terminal sends the beam reporting information containing the candidate beams to the network side equipment.
And S508, after determining that the candidate beam is available, the network side device enables the candidate beam and the terminal to transmit signals.
Fig. 6 is a schematic flow chart of a beam failure recovery processing method according to another embodiment of the present application, and fig. 6 illustrates a beam failure recovery processing flow by taking a second timer started by a network side as an example.
S601-S604 are the same as S501-S504, and are not described again. In this embodiment, the difference from the embodiment shown in fig. 5 is that the terminal may not know the timing time of the second timer, and only continue to perform the candidate beam measurement after receiving the beam failure recovery response. The timing time of the second timer is the second preset time.
Optionally, the network side device sends a beam measurement instruction to the terminal, and instructs the terminal to continuously perform candidate beam measurement.
S605, the network side device determines that the beam report information including the candidate beam sent by the terminal is not received within the timing time of the second timer.
And S606, the network side equipment sends a second radio link failure message to the core network equipment.
Fig. 7 is a schematic flow chart of a beam failure recovery processing method according to another embodiment of the present application, and fig. 7 illustrates a beam failure recovery processing flow by taking an example in which a terminal starts a first timer and a network side starts a second timer.
S701, the terminal determines that the current beam connection fails.
S702, the terminal sends a beam failure recovery request to the network side equipment.
And S703, the network side equipment determines that no available candidate beam exists, and starts a second timer.
S704, the terminal receives the beam failure recovery response sent by the network side equipment.
S705, the terminal determines that no available candidate beam exists, starts a first timer, and performs candidate beam measurement within the timing time of the first timer.
It should be noted that the network side device may know that there is no candidate beam, and may determine that there is no available candidate beam to occupy no time, that is, may start the second timer at the time of receiving the beam failure recovery request.
In an alternative embodiment, S706-S707 are performed.
S706, the terminal does not measure the candidate beam within the timing time of the first timer, and sends a first radio link failure message to the network side device.
In this embodiment, when the network side device receives the first radio link failure message, the timing time of the second timer is not yet ended.
And S707, the network side device sends a second radio link failure message to the core network device.
In another alternative embodiment, steps S708 to S709 are performed.
And S708, the terminal measures the candidate beams within the timing time of the first timer, and sends beam reporting information containing the candidate beams to the network side equipment.
In this embodiment, when the network side device receives the beam report information, the timing time of the second timer is not yet ended.
S709, after determining that the candidate beam is available, the network side device enables the candidate beam and the terminal to transmit signals.
Fig. 8 is a schematic flow chart of a beam failure recovery processing method according to another embodiment of the present application, where fig. 8 illustrates a beam failure recovery processing flow by taking an example in which a terminal starts a first timer and a network side starts a second timer.
S801 to S805 are the same as S701 to S705, and are not described again. In this embodiment, the difference from the embodiment shown in fig. 7 is that when the timing time of the second timer is over, the network side device does not receive the beam report information including the candidate beam transmitted by the terminal, and does not receive the first radio link failure message transmitted by the terminal.
S806, the network side device determines that the beam report information including the candidate beam sent by the terminal is not received within the timing time of the second timer.
S807, the network side device sends a second radio link failure message to the core network device.
Considering that the transmission of the signal needs to occupy time, the timing time of the second timer may be configured to be longer than the timing time of the first timer during configuration, and the specific duration is not limited in the present application.
Optionally, on the basis of the foregoing embodiment, the network side device may further send reporting configuration information to the terminal, where the reporting configuration information is used to configure a resource for sending the beam reporting information. Specifically, the reporting configuration information may indicate resources that the beam reporting information needs to occupy, a used information format, and the like.
The network side device may send the reporting configuration information after receiving the beam failure recovery request, or may send the reporting configuration information when the terminal accesses the network side device, which is not particularly limited herein.
Fig. 9 is a schematic structural diagram of a terminal according to an embodiment of the present application, and as shown in fig. 9, the terminal includes: a sending module 900, a determining module 901 and a measuring module 902, wherein:
a sending module 900, configured to send a beam failure recovery request to a network side device.
A determining module 901 for determining that there are no available candidate beams.
A measurement module 902, configured to perform candidate beam measurement within a first preset time.
In this embodiment, after the sending module sends the beam failure recovery request to the network side device, if the determining module determines that there is no available candidate beam, the measuring module performs candidate beam measurement within a first preset time. That is, after the terminal measures the beam failure, if there is no available candidate beam, the terminal does not report the link failure, but waits for a period of time, and performs the candidate beam measurement in the period of time, so as to ensure the physical layer interactive between the terminal and the network side to recover the beam as much as possible, and reduce unnecessary recovery delay.
Fig. 10 is a schematic structural diagram of a terminal according to another embodiment of the present application, and based on fig. 9, the terminal may further include: a first receiving module 903, configured to receive a beam failure recovery response sent by the network side device according to the beam failure recovery request before the measurement module 902 performs candidate beam measurement within a first preset time.
Fig. 11 is a schematic structural diagram of a terminal according to another embodiment of the present application, and on the basis of fig. 9, the terminal may further include: the second receiving module 111 is configured to receive, before the measurement module 902 performs candidate beam measurement within a first preset time, configuration information that includes the first preset time and is sent by the network side device.
Optionally, the first preset time is timing time information of a first timer. In another embodiment, the measurement module 902 starts a first timer, and performs the candidate beam measurement within a timing time of the first timer, where the timing time of the first timer is the first preset time.
Correspondingly, the second receiving module 111 is configured to receive the timing time information of the first timer, which is sent by the network side device, before the measurement module 902 performs candidate beam measurement within a first preset time.
In yet another embodiment, the first preset time is a timing time of a second timer started by the network side device after receiving the beam failure recovery request.
Fig. 12 is a schematic structural diagram of a terminal according to still another embodiment of the present application, and on the basis of fig. 9, the terminal may further include: a third receiving module 121, configured to receive a beam measurement instruction sent by the network side device, where the beam measurement instruction is used to instruct the terminal to continuously perform candidate beam measurement; or, the beam measurement indication is used to instruct the terminal to perform candidate beam measurement within the timing time of the second timer.
Further, the sending module 900 is further configured to send a first radio link failure message to the network side device when the candidate beam is not measured within the first preset time; or when the candidate beam is measured within the first preset time, sending beam reporting information to the network side device, where the beam reporting information includes an identifier of the candidate beam.
Fig. 13 is a schematic structural diagram of a terminal according to another embodiment of the present application, and based on fig. 9, the terminal may further include: a fourth receiving module 131, configured to receive reporting configuration information sent by the network side device, where the reporting configuration information is used to configure a resource for sending the beam reporting information.
On the basis of this embodiment, the sending module 900 is specifically configured to send the beam reporting information including the candidate beam to the network side device according to the reporting configuration information.
Optionally, the candidate beam comprises: at least 1 transmitting beam of the terminal and at least 1 receiving beam paired with the transmitting beam in the network side equipment; and/or at least 1 receiving beam of the terminal and at least 1 transmitting beam paired with the receiving beam in the network side equipment.
It should be noted that, for clarity, different receiving modules are respectively labeled for illustrating different embodiments, and all or part of the receiving operations may be performed by one receiving module in an actual terminal.
The terminal in this embodiment is used to execute the foregoing method embodiments, and the implementation principle and technical effect are similar, which are not described herein again.
Fig. 14 is a schematic structural diagram of a network-side device according to an embodiment of the present application, and as shown in fig. 14, the network-side device includes: a receiving module 141, a determining module 142, and a transmitting module 143, wherein:
the receiving module 141 is configured to receive a beam failure recovery request sent by the terminal.
A determination module 142 for determining that there are no available candidate beams.
A sending module 143, configured to send a second radio link failure message to a core network device when the determining module determines that the beam reporting information including the candidate beam sent by the terminal is not received within a second preset time, or the receiving module receives a first radio link failure message sent by the terminal within the second preset time.
In this embodiment, after the receiving module receives a beam failure recovery request sent by the terminal, the determining module determines that there is no available candidate beam, and waits for a second preset time, and the network side device does not report a link failure to the core network device in this period of time unless it receives no beam report information containing the candidate beam sent by the terminal within the second preset time or receives a first radio link failure message sent by the terminal within the second preset time, and the sending module sends a second radio link failure message to the core network device. The physical layer of the interaction between the terminal and the network side can be ensured to recover the wave beam as much as possible, and unnecessary recovery time delay is reduced.
Further, the transmitting module 143 is further configured to transmit a beam failure recovery response to the terminal before the determining module determines that there is no available candidate beam.
In an embodiment, the sending module 143 is further configured to send configuration information including the second preset time to the terminal.
In another embodiment, the sending module 143 is further configured to send timing time information of a first timer to the terminal, where the timing time information of the first timer is used to instruct the terminal to start the first timer, and perform candidate beam measurement within the timing time of the first timer.
The receiving module 141 is specifically configured to send the first radio link failure message when it is received within the second preset time that the terminal does not measure the candidate beam within the timing time of the first timer.
In one embodiment, the second preset time is a timing time of the second timer.
Based on the above embodiment, the sending module 143 is further configured to send a beam measurement instruction to the terminal, where the beam measurement instruction is used to instruct the terminal to continuously perform candidate beam measurement; or, the beam measurement indication is used to instruct the terminal to perform candidate beam measurement within the timing time of the second timer.
In addition, in an optional embodiment, the determining module 142 is specifically configured to determine whether the candidate beam is available when the receiving module receives, within the second preset time, beam reporting information that includes a candidate beam identifier and is sent by the terminal; enabling the candidate beam to transmit signals with the terminal upon determining that the candidate beam is available.
Correspondingly, the sending module 143 is further configured to send reporting configuration information to the terminal, where the reporting configuration information is used to configure a resource for sending the beam reporting information.
On the basis of the above embodiment, the candidate beams include: at least 1 transmitting beam of the terminal and at least 1 receiving beam paired with the transmitting beam in the network side equipment; and/or at least 1 receiving beam of the terminal and at least 1 transmitting beam paired with the receiving beam in the network side equipment.
The network side device in this embodiment is configured to execute the foregoing method embodiments, and the implementation principle and the technical effect are similar, which are not described herein again.
It should be noted that the division of each module of the network side device and the terminal is only a division of a logical function, and all or part of the actual implementation may be integrated into one physical entity, or may be physically separated. And these modules can be realized in the form of software called by processing element; or may be implemented entirely in hardware; and part of the modules can be realized in the form of calling software by the processing element, and part of the modules can be realized in the form of hardware. For example, the determining module may be a processing element separately set up, or may be implemented by being integrated in a chip of the apparatus, or may be stored in a memory of the apparatus in the form of program code, and the function of the determining module is called and executed by a processing element of the apparatus. Other modules are implemented similarly. In addition, all or part of the modules can be integrated together or can be independently realized. The processing element described herein may be an integrated circuit having signal processing capabilities. In implementation, each step of the above method or each module above may be implemented by an integrated logic circuit of hardware in a processor element or an instruction in the form of software.
For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), among others. For another example, when one of the above modules is implemented in the form of a Processing element scheduler code, the Processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).
Fig. 15 is a schematic structural diagram of a terminal according to another embodiment of the present application, and as shown in fig. 15, the terminal includes: a processor 171, a memory 172, a network interface 173, and a user interface 174.
The above-mentioned components in the terminal are coupled by a bus system 175. It will be appreciated that the bus system 175 is used to enable connective communication between these components. The bus system 175 may include a power bus, a control bus, and a status signal bus in addition to the data lines. For clarity of illustration, however, the various buses are labeled as the bus system 175 in fig. 15.
Alternatively, part or all of the above components may be implemented by embedding a Field Programmable Gate Array (FPGA) on a chip of the terminal. And they may be implemented separately or integrated together.
The user interface 174 is used for connecting peripheral devices or interface circuits connected with peripheral devices, respectively. May include interfaces for devices such as a display, keyboard, or pointing device, such as a mouse, trackball (trackball), touch pad, or touch screen.
The processor 171 herein may be a general purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), among others. The storage element may be a single storage device or may be a collective term for a plurality of storage elements.
The memory 172 may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. The volatile Memory may be a Random Access Memory (RAM) which serves as an external cache. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (static RAM, SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double data rate SDRAM (DDRSD RAM), Enhanced SDRAM (ESDRAM), SLDRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 172 described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
Optionally, memory 172 stores elements, executable modules or data structures, or a subset thereof, or an expanded set thereof: an operating system 1721 and application programs 1722.
The operating system 1721 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, and is used for implementing various basic services and processing hardware-based tasks.
The application 1722 includes various applications, such as a media player (MediaPlayer), a Browser (Browser), and the like, for implementing various application services. A program implementing the method of an embodiment of the present invention may also be included in application 1722.
Specifically, the processor 171 calls the program in the memory 172 to execute the method executed by each module shown in fig. 9-13, which is not described herein again.
Fig. 16 is a schematic structural diagram of a network-side device according to another embodiment of the present application. As shown in fig. 16, the network-side device includes: antenna 11, radio frequency device 12, baseband device 13. The antenna 11 is connected to a radio frequency device 12. In the uplink direction, the rf device 12 receives information via the antenna 11 and sends the received information to the baseband device 13 for processing. In the downlink direction, the baseband device 13 processes information to be transmitted and transmits the information to the radio frequency device 12, and the radio frequency device 12 processes the received information and transmits the processed information through the antenna 11.
The above-mentioned band processing means may be located in the baseband apparatus 13, and the method performed by the network side device in the above embodiment may be implemented in the baseband apparatus 13, where the baseband apparatus 13 includes the processor 181 and the memory 182.
The baseband device 13 may include at least one baseband board, for example, and a plurality of chips are disposed on the baseband board, as shown in fig. 16, wherein one chip, for example, the processor 181, is connected to the memory 182, and is used for calling the program in the memory 182 to perform the network-side device operation shown in the above method embodiment.
The baseband device 13 may further include a network interface 183 for exchanging information with the radio frequency device 12, for example, a Common Public Radio Interface (CPRI).
The processor may be a single processor or a combination of multiple processing elements, for example, the processor may be a CPU, an ASIC, or one or more integrated circuits configured to implement the method performed by the above network-side device, for example: one or more microprocessors DSP, or one or more field programmable gate arrays FPGA, or the like. The storage element may be a memory or a combination of a plurality of storage elements.
The memory 182 may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. The volatile Memory may be a Random Access Memory (RAM) which serves as an external cache. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double data rate Synchronous dynamic random access memory (ddr DRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 182 described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
Specifically, the processor 181 calls the program in the memory 182 to execute the method executed by each module shown in fig. 14, which is not described herein again.
Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims (44)

1. A method for processing beam failure recovery, comprising:
the terminal sends a beam failure recovery request to the network side equipment;
if the terminal determines that no available candidate beam exists, the terminal performs candidate beam measurement within a first preset time;
the first preset time is timing time information of a first timer;
alternatively, the first and second electrodes may be,
the first preset time is a timing time of a second timer started by the network side device after receiving the beam failure recovery request.
2. The method of claim 1, wherein before the terminal performs the candidate beam measurement within the first preset time, the method further comprises:
and the terminal receives a beam failure recovery response sent by the network side equipment according to the beam failure recovery request.
3. The method of claim 1, wherein before the terminal performs the candidate beam measurement within the first preset time, the method further comprises:
and the terminal receives the configuration information which is sent by the network side equipment and contains the first preset time.
4. The method of claim 2, wherein before the terminal performs the candidate beam measurement within the first preset time, the method further comprises:
and the terminal receives the configuration information which is sent by the network side equipment and contains the first preset time.
5. The method according to claim 1, wherein when the first preset time is a timing time of a second timer started by the network-side device after receiving the beam failure recovery request; the method further comprises the following steps:
the terminal receives a beam measurement instruction sent by the network side equipment, wherein the beam measurement instruction is used for instructing the terminal to continuously perform candidate beam measurement; or, the beam measurement indication is used to instruct the terminal to perform candidate beam measurement within the timing time of the second timer.
6. The method according to any one of claims 1-5, further comprising:
if the candidate beam is not measured within the first preset time, the terminal sends a first radio link failure message to the network side equipment; alternatively, the first and second electrodes may be,
and if the candidate wave beam is measured in the first preset time, the terminal sends wave beam reporting information to the network side equipment, wherein the wave beam reporting information comprises the identifier of the candidate wave beam.
7. The method of claim 6, further comprising:
the terminal receives reporting configuration information sent by the network side equipment, wherein the reporting configuration information is used for configuring resources for sending the beam reporting information;
the terminal sends the beam reporting information to the network side equipment, and the beam reporting information comprises the following steps:
and the terminal sends the beam reporting information to the network side equipment according to the reporting configuration information.
8. The method according to any of claims 1-5, 7, wherein the candidate beams comprise: at least 1 transmitting beam of the terminal and at least 1 receiving beam paired with the transmitting beam in the network side equipment; and/or at least 1 receiving beam of the terminal and at least 1 transmitting beam paired with the receiving beam in the network side equipment.
9. The method of claim 6, wherein the candidate beams comprise: at least 1 transmitting beam of the terminal and at least 1 receiving beam paired with the transmitting beam in the network side equipment; and/or at least 1 receiving beam of the terminal and at least 1 transmitting beam paired with the receiving beam in the network side equipment.
10. A method for processing beam failure recovery, comprising:
the method comprises the steps that network side equipment receives a beam failure recovery request sent by a terminal;
if the network side equipment determines that no available candidate beam exists, if the network side equipment still does not receive beam reporting information which is sent by the terminal and contains the candidate beam within second preset time, or the network side equipment receives a first radio link failure message sent by the terminal within the second preset time, the network side equipment sends a second radio link failure message to core network equipment;
the second preset time is the timing time of the second timer.
11. The method of claim 10, wherein before the network-side device determines that there are no available candidate beams, the method further comprises:
and the network side equipment sends a beam failure recovery response to the terminal.
12. The method of claim 10, further comprising:
and the network side equipment sends configuration information containing the second preset time to the terminal.
13. The method of claim 11, further comprising:
and the network side equipment sends configuration information containing the second preset time to the terminal.
14. The method of claim 10, further comprising:
the network side equipment sends timing time information of a first timer to the terminal, wherein the timing time information of the first timer is used for indicating the terminal to start the first timer and carry out candidate beam measurement within the timing time of the first timer.
15. The method of claim 11, further comprising:
the network side equipment sends timing time information of a first timer to the terminal, wherein the timing time information of the first timer is used for indicating the terminal to start the first timer and carry out candidate beam measurement within the timing time of the first timer.
16. The method according to claim 14, wherein the receiving, by the network side device, the first radio link failure message sent by the terminal within the second preset time includes:
and the network side equipment sends the first radio link failure message when receiving that the terminal does not measure the candidate beam within the timing time of the first timer within the second preset time.
17. The method according to claim 15, wherein the receiving, by the network side device, the first radio link failure message sent by the terminal within the second preset time includes:
and the network side equipment sends the first radio link failure message when receiving that the terminal does not measure the candidate beam within the timing time of the first timer within the second preset time.
18. The method of claim 10, further comprising:
the network side device sends a beam measurement instruction to the terminal, where the beam measurement instruction is used to instruct the terminal to continuously perform candidate beam measurement, or the beam measurement instruction is used to instruct the terminal to perform candidate beam measurement within the timing time of the second timer.
19. The method according to any one of claims 10-18, further comprising:
if the network side equipment receives the beam reporting information which is sent by the terminal and contains the candidate beam identifier within the second preset time, the network side equipment determines whether the candidate beam is available;
and after determining that the candidate beam is available, the network side equipment enables the candidate beam and the terminal to transmit signals.
20. The method of claim 19, further comprising:
and the network side equipment sends reporting configuration information to the terminal, wherein the reporting configuration information is used for configuring resources for sending the beam reporting information.
21. The method according to any of claims 10-18, 20, wherein the candidate beams comprise: at least 1 transmitting beam of the terminal and at least 1 receiving beam paired with the transmitting beam in the network side equipment; and/or at least 1 receiving beam of the terminal and at least 1 transmitting beam paired with the receiving beam in the network side equipment.
22. The method of claim 19, wherein the candidate beams comprise: at least 1 transmitting beam of the terminal and at least 1 receiving beam paired with the transmitting beam in the network side equipment; and/or at least 1 receiving beam of the terminal and at least 1 transmitting beam paired with the receiving beam in the network side equipment.
23. A terminal, comprising:
a sending module, configured to send a beam failure recovery request to a network side device;
a determination module to determine that there are no available candidate beams;
the measurement module is used for measuring candidate beams in a first preset time;
the first preset time is timing time information of a first timer;
alternatively, the first and second electrodes may be,
the first preset time is a timing time of a second timer started by the network side device after receiving the beam failure recovery request.
24. The terminal of claim 23, further comprising:
a first receiving module, configured to receive a beam failure recovery response sent by the network side device according to the beam failure recovery request before the measurement module performs candidate beam measurement within a first preset time.
25. The terminal of claim 23, further comprising:
a second receiving module, configured to receive, before the measurement module performs candidate beam measurement within a first preset time, configuration information that includes the first preset time and is sent by the network side device.
26. The terminal of claim 24, further comprising:
a second receiving module, configured to receive, before the measurement module performs candidate beam measurement within a first preset time, configuration information that includes the first preset time and is sent by the network side device.
27. The terminal of claim 23,
the terminal further comprises: a third receiving module, configured to receive a beam measurement instruction sent by the network side device, where the beam measurement instruction is used to instruct the terminal to continuously perform candidate beam measurement; or, the beam measurement indication is used to instruct the terminal to perform candidate beam measurement within the timing time of the second timer.
28. The terminal of any one of claims 23 to 27, wherein the sending module is further configured to send a first radio link failure message to the network side device when no candidate beam is measured within the first preset time, or send beam reporting information to the network side device when a candidate beam is measured within the first preset time, where the beam reporting information includes an identifier of the candidate beam.
29. The terminal of claim 28, further comprising:
a fourth receiving module, configured to receive reporting configuration information sent by the network side device, where the reporting configuration information is used to configure a resource for sending the beam reporting information;
correspondingly, the sending module is specifically configured to send the beam reporting information to the network side device according to the reporting configuration information.
30. The terminal according to any of claims 23-27, 29, wherein the candidate beams comprise: at least 1 transmitting beam of the terminal and at least 1 receiving beam paired with the transmitting beam in the network side equipment; and/or at least 1 receiving beam of the terminal and at least 1 transmitting beam paired with the receiving beam in the network side equipment.
31. The terminal of claim 28, wherein the candidate beams comprise: at least 1 transmitting beam of the terminal and at least 1 receiving beam paired with the transmitting beam in the network side equipment; and/or at least 1 receiving beam of the terminal and at least 1 transmitting beam paired with the receiving beam in the network side equipment.
32. A network-side device, comprising:
a receiving module, configured to receive a beam failure recovery request sent by a terminal;
a determination module to determine that there are no available candidate beams;
a sending module, configured to send a second radio link failure message to a core network device when the determining module determines that the beam reporting information including the candidate beam sent by the terminal is not received within a second preset time or the receiving module receives a first radio link failure message sent by the terminal within the second preset time;
the second preset time is the timing time of the second timer.
33. The network-side device of claim 32, wherein the sending module is further configured to send a beam failure recovery response to the terminal before the determining module determines that there are no available candidate beams.
34. The network-side device of claim 32, wherein the sending module is further configured to send configuration information including the second preset time to the terminal.
35. The network-side device of claim 33, wherein the sending module is further configured to send configuration information including the second preset time to the terminal.
36. The network-side device of claim 32, wherein the sending module is further configured to send timing time information of a first timer to the terminal, where the timing time information of the first timer is used to instruct the terminal to start the first timer, and perform candidate beam measurement within a timing time of the first timer.
37. The network-side device of claim 33, wherein the sending module is further configured to send timing time information of a first timer to the terminal, where the timing time information of the first timer is used to instruct the terminal to start the first timer, and perform candidate beam measurement within a timing time of the first timer.
38. The network-side device of claim 36, wherein the receiving module is specifically configured to send the first radio link failure message when it is received within the second preset time that the terminal does not measure the candidate beam within the timing time of the first timer.
39. The network-side device of claim 37, wherein the receiving module is specifically configured to send the first radio link failure message when it is received within the second preset time that the terminal does not measure the candidate beam within the timing time of the first timer.
40. The network-side device of claim 32, wherein the sending module is further configured to send a beam measurement indication to the terminal, where the beam measurement indication is used to indicate that the terminal continuously performs candidate beam measurement, or the beam measurement indication is used to indicate that the terminal performs candidate beam measurement within a timing time of the second timer.
41. The network-side device of any one of claims 32 to 40, wherein the determining module is specifically configured to determine whether the candidate beam is available when the receiving module receives, within the second preset time, beam reporting information that includes an identifier of the candidate beam and is sent by the terminal; enabling the candidate beam to transmit signals with the terminal upon determining that the candidate beam is available.
42. The network-side device of claim 41, wherein the sending module is further configured to send reporting configuration information to the terminal, where the reporting configuration information is used to configure a resource for sending the beam reporting information.
43. The network-side device of any one of claims 32-40, 42, wherein the candidate beam comprises: at least 1 transmitting beam of the terminal and at least 1 receiving beam paired with the transmitting beam in the network side equipment; and/or at least 1 receiving beam of the terminal and at least 1 transmitting beam paired with the receiving beam in the network side equipment.
44. The network-side device of any one of claims 41, wherein the candidate beams comprise: at least 1 transmitting beam of the terminal and at least 1 receiving beam paired with the transmitting beam in the network side equipment; and/or at least 1 receiving beam of the terminal and at least 1 transmitting beam paired with the receiving beam in the network side equipment.
CN201710296835.XA 2017-04-28 2017-04-28 Beam failure recovery processing method, terminal and network side equipment Active CN108811092B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710296835.XA CN108811092B (en) 2017-04-28 2017-04-28 Beam failure recovery processing method, terminal and network side equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710296835.XA CN108811092B (en) 2017-04-28 2017-04-28 Beam failure recovery processing method, terminal and network side equipment

Publications (2)

Publication Number Publication Date
CN108811092A CN108811092A (en) 2018-11-13
CN108811092B true CN108811092B (en) 2020-10-27

Family

ID=64053284

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710296835.XA Active CN108811092B (en) 2017-04-28 2017-04-28 Beam failure recovery processing method, terminal and network side equipment

Country Status (1)

Country Link
CN (1) CN108811092B (en)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019137472A1 (en) * 2018-01-11 2019-07-18 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for beam failure recovery
CN111225406B (en) * 2018-11-27 2022-02-18 华为技术有限公司 Timing measurement method and related equipment
CN111385890B (en) * 2018-12-29 2023-05-02 成都华为技术有限公司 Beam failure recovery method and device
CN111479289B (en) * 2019-01-24 2023-01-13 中国移动通信有限公司研究院 Cell switching method, device and readable medium
CN111479326B (en) * 2019-01-24 2022-09-16 大唐移动通信设备有限公司 Information sending and detecting method and device
CN111278122B (en) * 2019-01-25 2023-03-24 维沃移动通信有限公司 Beam failure recovery method, processing method, terminal and network side equipment
CN114145066A (en) * 2019-08-01 2022-03-04 鸿颖创新有限公司 Transmission method of secondary cell beam fault recovery request information and related equipment
CN112399592A (en) * 2019-08-16 2021-02-23 中国移动通信有限公司研究院 Information sending method, information receiving method, terminal and network equipment
WO2022000446A1 (en) * 2020-07-03 2022-01-06 Qualcomm Incorporated Techniques for mitigating redundant beam failure recovery medium access signaling
WO2022027254A1 (en) * 2020-08-04 2022-02-10 Apple Inc. Cross-cell beam failure recovery
CN114079940B (en) * 2020-08-14 2024-02-13 维沃移动通信有限公司 Candidate beam measurement method, device and terminal
WO2024031535A1 (en) * 2022-08-11 2024-02-15 Oppo广东移动通信有限公司 Wireless communication method, terminal device, and network device

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012167232A1 (en) * 2011-06-02 2012-12-06 Qualcomm Incorporated System, apparatus, and method for reducing recovery failure delay in wireless communication systems
WO2016127403A1 (en) * 2015-02-13 2016-08-18 Mediatek Singapore Pte. Ltd. Handling of intermittent disconnection in a millimeter wave (mmw) system
CN106452674A (en) * 2016-09-30 2017-02-22 西安交通大学 Actual data packet restoration method based on 802.11ac

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012167232A1 (en) * 2011-06-02 2012-12-06 Qualcomm Incorporated System, apparatus, and method for reducing recovery failure delay in wireless communication systems
WO2016127403A1 (en) * 2015-02-13 2016-08-18 Mediatek Singapore Pte. Ltd. Handling of intermittent disconnection in a millimeter wave (mmw) system
CN106452674A (en) * 2016-09-30 2017-02-22 西安交通大学 Actual data packet restoration method based on 802.11ac

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
Considerations on Beam Recovery for NR;InterDigital Communications;《3GPP TSG RAN WG1 Meeting #88 R1-1702325》;20170217;正文第1-2节 *
Discussion on beam recovery;vivo;《3GPP TSG RAN WG1 Meeting #88 R1- 1703389》;20170217;正文第2节 *
vivo.Discussion on beam recovery.《3GPP TSG RAN WG1 Meeting #88 R1- 1703389》.2017,正文第2节. *

Also Published As

Publication number Publication date
CN108811092A (en) 2018-11-13

Similar Documents

Publication Publication Date Title
CN108811092B (en) Beam failure recovery processing method, terminal and network side equipment
CN109089322B (en) Uplink multi-beam transmission method, terminal and network equipment
CN109151869B (en) Configuration method of random access resource, terminal and network equipment
RU2767981C2 (en) Information processing method and corresponding device
EP3796729A1 (en) Iab node switching method, iab node and host base station
CN109151884B (en) Measurement configuration method, terminal and base station
US11129068B2 (en) Network device and terminal device applied for cell handover
US11051215B2 (en) Switching method, terminal device, and network device
CN109392186B (en) Random access method, terminal, network device and computer readable storage medium
US11419111B2 (en) Data transmission method, terminal device, and network device
JP2021517751A (en) Methods, devices and computer storage media for configuring secondary cells
US20200205124A1 (en) Paging Method, Terminal Device, and Network Device
JP2021528894A (en) Ability interaction method and related equipment
JP7213950B2 (en) Information configuration method and device, terminal, network equipment
EP3668148B1 (en) Data transmission method and terminal device
CN108810961B (en) Measurement information processing method, terminal and access network node
CN108810953B (en) Processing method for measurement report, network side equipment and user equipment
WO2021027660A1 (en) Radio communication method and communication apparatus
JP7279039B2 (en) METHOD OF SETTING MEASUREMENT INTERVAL, NETWORK DEVICE AND TERMINAL DEVICE
US20210153084A1 (en) Wireless communication method, terminal device, and network device
KR20200033883A (en) Communication method, network device and terminal device
WO2021031004A1 (en) Carrier measurement method and apparatus
EP3826405A1 (en) Information transmission method and apparatus, and terminal and network device
CN109716822B (en) Method for controlling terminal equipment to generate uplink signaling, terminal equipment and network equipment
CN115967995A (en) Cell switching method and device

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
GR01 Patent grant
GR01 Patent grant