WO2020077600A1

WO2020077600A1 - Method and device for triggering beam failure recovery, and terminal

Info

Publication number: WO2020077600A1
Application number: PCT/CN2018/110896
Authority: WO
Inventors: 石聪; 尤心
Original assignee: Oppo广东移动通信有限公司
Priority date: 2018-10-18
Filing date: 2018-10-18
Publication date: 2020-04-23
Also published as: CN111869313B; CN111869313A

Abstract

Provided are a method and device for triggering BFR, and a terminal. The method comprises: a terminal detecting a beam failure at a first time under a discontinuous reception (DRX) inactive state; and the terminal initiating a beam recovery procedure at a second time after the first time.

Description

Method, device and terminal for triggering beam failure recovery

Technical field

The embodiments of the present application relate to the technical field of mobile communications, and in particular, to a method, device, and terminal for triggering beam failure recovery.

Background technique

In the relevant protocol, the terminal may also receive beam failure event indication information (Beam Failure Failure Instance indication) in the non-continuous reception (DRX, Discontinuous Reception) inactive state, which may trigger beam failure recovery (BFR, Beam Failure Failure Recovery) )Process. However, the BFR process triggered in the DRX inactive state is not good for the terminal, because the DRX inactive time (that is, the time corresponding to the DRX inactive state) the network does not expect the terminal to receive data, and triggering the BFR process will result in additional charges for the terminal Electricity.

Summary of the invention

Embodiments of the present application provide a method, device, and terminal for triggering BFR.

The method for triggering BFR provided by the embodiment of the present application includes:

In the DRX inactive state, the terminal detects the beam failure at the first time;

The terminal initiates a beam recovery process at a second time after the first time.

The device for triggering BFR provided by the embodiment of the present application includes:

The detection unit is used to detect the beam failure in the first time in the DRX inactive state;

The recovery unit is configured to initiate a beam recovery process at a second time after the first time.

The terminal provided by the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above method of triggering BFR.

The chip provided by the embodiment of the present application is used to implement the above method for triggering BFR.

Specifically, the chip includes: a processor for calling and running a computer program from the memory, so that the device installed with the chip executes the above-mentioned method of triggering BFR.

The computer-readable storage medium provided by the embodiments of the present application is used to store a computer program, and the computer program enables the computer to execute the above method for triggering BFR.

The computer program product provided by the embodiment of the present application includes computer program instructions, and the computer program instructions enable the computer to execute the above method for triggering BFR.

The computer program provided by the embodiment of the present application causes the computer to execute the above method for triggering BFR when it is run on the computer.

Through the above technical solution, when the terminal detects a beam failure (beam failure) in the DRX inactive state, the beam recovery process is delayed and triggered, where the beam recovery process is used to recover the failed beam, thereby delaying the time for the terminal to receive data on the network side , Saving power consumption of the terminal. Further, the terminal can use the BFR process to request uplink resources from the network, so as to achieve the purpose of recovering the beam and requesting the uplink resource; or, the terminal can use the scheduling request (SR, Scheduling Request) to recover the beam, thereby requesting the uplink resource and recovering the beam Purpose; or, the terminal separately uses the BFR process to recover the beam, and uses the SR to request uplink resources from the network.

BRIEF DESCRIPTION

The drawings described here are used to provide a further understanding of the present application and form a part of the present application. The schematic embodiments and descriptions of the present application are used to explain the present application and do not constitute an undue limitation on the present application. In the drawings:

1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

2 is a schematic flowchart of a method for triggering BFR provided by an embodiment of the present application;

3 (a) is a schematic diagram 1 of the principle of delayed triggering BFR provided by an embodiment of the present application;

3 (b) is a second schematic diagram of the principle of delayed triggering BFR provided by an embodiment of the present application;

3 (c) is a schematic diagram 3 of the principle of delay triggering BFR provided by an embodiment of the present application;

FIG. 3 (d) is a schematic diagram 4 of the principle of delay triggering BFR provided by an embodiment of the present application;

FIG. 3 (e) is a schematic diagram 5 of the principle of delay triggering BFR provided by an embodiment of the present application;

FIG. 3 (f) is a schematic diagram 6 of the principle of delay triggering BFR provided by an embodiment of the present application;

3 (g) is a schematic diagram 7 of the principle of delay triggering BFR provided by an embodiment of the present application;

FIG. 3 (h) is a schematic diagram 8 of the principle of delay triggering BFR provided by an embodiment of the present application;

FIG. 3 (i) is a schematic diagram 9 of the principle of delay triggering BFR provided by an embodiment of the present application;

FIG. 3 (j) is a schematic diagram 10 of the principle of delay triggering BFR provided by an embodiment of the present application;

4 is a schematic structural composition diagram of a device for triggering BFR provided by an embodiment of the present application;

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

6 is a schematic structural diagram of a chip according to an embodiment of the present application;

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

detailed description

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are a part of the embodiments of the present application, but not all the embodiments. Based on the embodiments in this application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the scope of protection of this application.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile (GSM) system, Code Division Multiple Access (CDMA) system, and Broadband Code Division Multiple Access (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (General Packet Radio Service, GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (Time Division Duplex, TDD), Universal Mobile Communication System (Universal Mobile Telecommunication System, UMTS), Global Interoperability for Microwave Access (WiMAX) communication system or 5G system, etc.

Exemplarily, the communication system 100 applied in the embodiment of the present application is shown in FIG. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or referred to as a communication terminal, terminal). The network device 110 can provide communication coverage for a specific geographic area, and can communicate with terminals located within the coverage area. Optionally, the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system (Evolutional Node B, eNB or eNodeB), or a wireless controller in the cloud radio access network (Cloud Radio Access Network, CRAN), or the network equipment can be a mobile switching center, a relay station, an access point, an on-board device, Wearable devices, hubs, switches, bridges, routers, network-side devices in 5G networks or network devices in future public land mobile networks (Public Land Mobile Network, PLMN), etc.

The communication system 100 also includes at least one terminal 120 located within the coverage of the network device 110. As used herein, "terminals" include, but are not limited to, connections via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Lines (DSL), digital cables, and direct cable connections; And / or another data connection / network; and / or via a wireless interface, eg, for cellular networks, wireless local area networks (Wireless Local Area Network, WLAN), digital TV networks such as DVB-H networks, satellite networks, AM-FM A broadcast transmitter; and / or another terminal device configured to receive / transmit communication signals; and / or Internet of Things (IoT) equipment. A terminal configured to communicate through a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal", or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular phones; Personal Communication Systems (PCS) terminals that can combine cellular radiotelephones with data processing, fax, and data communication capabilities; can include radiotelephones, pagers, Internet / internal PDA with networked access, web browser, notepad, calendar, and / or Global Positioning System (GPS) receiver; and conventional laptop and / or palm-type receivers or others including radiotelephone transceivers Electronic device. Terminal can refer to access terminal, user equipment (User Equipment, UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user Device. Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, wireless local loop (Wireless Local Loop, WLL) stations, personal digital processing (Personal Digital Assistant (PDA), wireless communication Functional handheld devices, computing devices, or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in 5G networks, or terminals in future evolved PLMNs, etc.

Optionally, terminal 120 may perform terminal direct connection (Device to Device, D2D) communication.

Alternatively, the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.

FIG. 1 exemplarily shows one network device and two terminals. Optionally, the communication system 100 may include multiple network devices and each network device may include other numbers of terminals within the coverage area. Embodiments of the present application There is no restriction on this.

Optionally, the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.

It should be understood that the devices with communication functions in the network / system in the embodiments of the present application may be referred to as communication devices. Taking the communication system 100 shown in FIG. 1 as an example, the communication device may include a network device 110 and a terminal 120 having a communication function, and the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here; communication The device may also include other devices in the communication system 100, such as network controllers, mobility management entities, and other network entities, which are not limited in the embodiments of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" in this article is just an association relationship that describes an associated object, indicating that there can be three relationships, for example, A and / or B, which can mean: A exists alone, A and B exist at the same time, exist alone B these three cases. In addition, the character “/” in this article generally indicates that the related objects before and after are in an “or” relationship.

FIG. 2 is a schematic flowchart of a method for triggering BFR according to an embodiment of the present application. As shown in FIG. 2, the method for touching BFR includes the following steps:

Step 201: In the DRX inactive state, the terminal detects the beam failure at the first time.

In the embodiment of the present application, the terminal may be any device capable of communicating with a network, such as a mobile phone, a tablet computer, a vehicle-mounted terminal, a notebook, a wearable device.

In New Radio (NR, New Radio), the terminal's Media Access Control (MAC, Media Access Control) entity is configured with DRX, then at the DRX activation time (DRX Active Time), the terminal needs to monitor the downlink control channel (PDCCH, Physical Downlink Control Channel), here, the PDCCH monitored by the terminal is scrambled by some wireless network temporary identifiers (RNTI, Radio Network Tempory Identity), such as: C-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI- RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI.

A DRX cycle includes two time periods, one is DRX activation time, and the other is DRX inactivity time. DRX Active Time (DRX Active Time) includes the following situations:

1) During the operation of drx-InactivityTimer, or drx-RetransmissionTimerDL, or drx-RetransmissionTimerUL, or ra-ContentionResolutionTimer, it belongs to the DRX activation time.

2) The time after the terminal sends the scheduling request is the DRX activation time.

3) The time before the terminal fails to receive the PDCCH after successfully receiving the random access response (RAR) belongs to the DRX activation time, where the PDCCH is scrambled by the C-RNTI.

In the embodiment of the present application, the terminal in the DRX activated state means that the MAC entity of the terminal is in DRX Active Time. The terminal in the DRX inactive state means that the MAC entity of the terminal is in the non-DRX Active Time.

In the embodiment of the present application, beam failure detection (Beam Failure Detection) can be implemented by the following process: The MAC entity of the terminal maintains a counter called a beam failure event counter (BFI_COUNTER). If the MAC entity receives Beam Failure from the physical layer Instance indication, the terminal increments the counter by one, and if the counter reaches a preset threshold, it determines that a beam failure has been detected. After the beam fails, the failed beam needs to be recovered.

In the embodiment of the present application, in the DRX inactive state, the terminal may also receive Beam Failure Instance indication, which may trigger the beam recovery process.

For example, if the terminal receives a Beam Failure Failure Instance indication in the DRX inactive state, it will increase the BFI_COUNTER by 1. During the operation of the beam failure recovery timer, if the BFI_COUNTER reaches the preset threshold, the beam is considered to have failed. The time when the BFI_COUNTER reaches the preset threshold is also the time when the beam failure is detected, which is called the first time in the embodiment of the present application.

Step 202: The terminal initiates a beam recovery process at a second time after the first time.

In the embodiment of the present application, when the terminal detects that the beam fails at the first time, it will delay to initiate the beam recovery process until the second time, where the beam recovery process is used to recover the failed beam.

In the embodiment of the present application, the terminal delays initiating the beam recovery process in any one of the following ways.

Manner 1: The terminal initiates a BFR process at a second time after the first time, and the BFR process is used for beam recovery. The second time is determined based on a third time, which is the time when the terminal enters the DRX active state from the DRX inactive state.

In one embodiment, the second time is equal to the third time. In another embodiment, the second time is any time between the first time and the third time.

In the above solution, the third time is the start time of the second timer, and the terminal enters the DRX active state from the DRX inactive state when the second timer is started.

Further, the start time of the second timer is configured by the network. For example, the second timer is Onduration timer. In a DRX cycle, the MAC entity of the terminal is in DRX Active Time during the Onduration timer operation, and the MAC entity of the terminal is in non-DRX Active Time during the rest of the time. The startup time of On Duration timer is configured by the network. The startup time of On Duration timer is determined by the following conditions:

For the case of a short DRX cycle (Short DRX Cycle): [(SFN × 10) + subframe number] modulo (drx-ShortCycle) = (drx-StartOffset) modulo (drx-ShortCycle). Among them, SFN is the system frame number, subframe numbe is the subframe number, modulo is the modulo operation, drx-ShortCycle is the short DRX cycle, drx-StartOffset is the offset of the start time of Onduration timer relative to the start position of the subframe .

For the case of long DRX cycle (Long DRX Cycle): [(SFN × 0) + subframe number] modulo (drx-LongCycle) = drx-StartOffset. Among them, SFN is the system frame number, subframe numbe is the subframe number, modulo is the modulo operation, drx-LongCycle is the long DRX cycle, drx-StartOffset is the offset of the start time of Onduration timer relative to the start position of the subframe .

For example, referring to FIG. 3 (a), time t1 is the time when the terminal detects the beam failure, time t2 is the start time of the Ontimer (that is, the second timer), and the terminal initiates the BFR process at time t2.

Another example: referring to FIG. 3 (b), time t1 is the time when the terminal detects the failure of the beam, time t2 is the start time of the Onduration timer (that is, the second timer), and the terminal is between time t1 and time t2 Initiate the BFR process at any moment.

Manner 2: The terminal initiates a BFR process at a second time after the first time, and the BFR process is used for beam recovery. The second time is determined based on a third time and a first offset time, where the third time is the time when the terminal enters the DRX active state from the DRX inactive state.

In one embodiment, the second time is equal to the third time minus the first offset time. In another embodiment, the second time is any time between the first time and the fourth time, and the fourth time is equal to the third time minus the first offset time.

In the above solution, the first offset time is configured by the network (for example, the first offset time is configured by the network through RRC signaling.); Or, the first offset time is agreed by the protocol.

In the above solution, the third time is the start time of the second timer, and the terminal enters the DRX active state from the DRX inactive state when the second timer is started. Further, the start time of the second timer is configured by the network.

For example, referring to FIG. 3 (c), time t1 is the time when the terminal detects the failure of the beam, time t2 is the start time of the On duration timer (that is, the second timer), time t3 is located before time t2, and time t2 If the difference is T _offset (that is, the first offset time), the terminal initiates the BFR process at time t3.

Another example: referring to FIG. 3 (d), time t1 is the time when the terminal detects the failure of the beam, time t2 is the start time of the On duration timer (that is, the second timer), time t3 is located before time t2 and t2 When the time difference is T _offset (that is, the first offset time), the terminal initiates the BFR process at any time between time t1 and time t3.

Manner 3: The terminal initiates a BFR process at a second time after the first time, and the BFR process is used for beam recovery. The second time is determined based on the end time of the first timer, and the start time of the first timer is the first time.

In an embodiment, if the end time of the first timer is before the third time, the second time is the end time of the first timer. In another embodiment, if the end time of the first timer is after a third time, the second time is equal to the three times. The third time is the time when the terminal enters the DRX activated state from the DRX inactive state.

For example, referring to FIG. 3 (e), time t1 is the time when the terminal detects the failure of the beam, time t2 is the start time of the Ontimer (that is, the second timer), and the terminal starts the first timer at time t1, The first timer times out at time t4, time t4 is before t2, and the terminal initiates the BFR process at time t4.

As another example: referring to FIG. 3 (f), time t1 is the time when the terminal detects the beam failure, time t2 is the start time of the Ontimer (that is, the second timer), and the terminal starts the first timer at time t1 , The first timer times out at time t4, time t4 is located after t2, and the terminal initiates the BFR process at time t2.

Manner 4: The second time is determined based on a fourth time, which is the time when the terminal decides to send a scheduling request in the DRX inactive state.

1) When the terminal decides to send a scheduling request at the fourth time, if it is determined that a beam failure has been detected, then: the terminal initiates a BFR process after the fourth time, and sends a scheduling request after the BFR succeeds. The BFR process is used to perform beam recovery, and the scheduling request is used to request uplink resources.

Specifically, the terminal initiates a BFR process on the first available BFR resource after the fourth time, and sends a scheduling request on the first available uplink control channel PUCCH resource after BFR success.

For example, referring to FIG. 3 (g), time t1 is the time when the terminal detects the beam failure, time t2 is the start time of the Ontimer (that is, the second timer), and time t5 is the time when the terminal decides to send the scheduling request , The terminal initiates the BFR process on the first available BFR resource after time t5, and sends a scheduling request on the first available PUCCH resource after the BFR succeeds.

It should be noted that the time when the terminal decides to send the scheduling request is different from the time when the terminal actually sends the scheduling request. After the terminal decides to send the scheduling request, if there is available PUCCH resource, the scheduling request is sent on the PUCCH resource that has become available.

2) When the terminal decides to send a scheduling request at the fourth time, if it is determined that a beam failure has been detected, the terminal initiates a BFR process after the fourth time, and the BFR process is used for beam recovery And request uplink resources.

During specific implementation, the random access process corresponding to the BFR process is used to indicate that the BFR process is used to perform beam recovery and request uplink resources. For example, the specific transmission resource and / or specific preamble of MSG1 in the random access process corresponding to the BFR process is used to indicate that the BFR process is used for beam recovery and requesting uplink resources. Further, the specific transmission resource and / or specific preamble of the MSG1 is configured by the network.

For example: referring to FIG. 3 (h), time t1 is the time when the terminal detects the failure of the beam, time t2 is the start time of the Onduration timer (that is, the second timer), and time t5 is the time when the terminal decides to send the scheduling request , The terminal initiates a BFR process on the first available BFR resource after time t5, and the BFR process is used to perform beam recovery and request uplink resources. Here, the terminal replaces the SR transmission with a BFR process, and the random access process corresponding to the BFR process can be used to distinguish whether the BFR process recovers the beam failure BFR or the BFR that can recover the beam failure and request the uplink resource. One implementation manner is that the network can configure the terminal with specific MSG1 resources, such as time-frequency transmission resources or preamble resources, to distinguish which BFR is the BFR.

3) When the terminal decides to send a scheduling request at the fourth time, if it is determined that a beam failure has been detected, then: the terminal initiates a BFR process after the fourth time and sends a scheduling request, the BFR process Used for beam recovery, the scheduling request is used to request uplink resources.

Specifically, the terminal initiates a BFR process on the first available BFR resource after the fourth time, and sends a scheduling request on the first available PUCCH resource after the fourth time.

For example, referring to FIG. 3 (i), time t1 is the time when the terminal detects the beam failure, time t2 is the start time of the Ontimer (that is, the second timer), and time t5 is the time when the terminal decides to send the scheduling request , The terminal initiates the BFR process on the first available BFR resource after time t5, and also sends the scheduling request on the available PUCCH resource. The sequence of the time when the BFR process is initiated and the time when the scheduling request is sent is based on the respective first available resource It is determined that FIG. 3 (i) takes the process of sending a scheduling request first and then initiating the BFR as an example. It is not limited to this, and it is also possible to initiate BFR first and then send the scheduling request.

4) When the terminal decides to send a scheduling request at the fourth time, if it is determined that a beam failure has been detected, the terminal sends a scheduling request after the fourth time, and the scheduling request is used to request uplink resources And perform beam recovery.

For example, referring to FIG. 3 (j), time t1 is the time when the terminal detects the failure of the beam, time t2 is the start time of the Ontimer (that is, the second timer), and time t5 is the time when the terminal decides to send the scheduling request , The terminal sends a scheduling request on the first available PUCCH resource after time t5, where the scheduling request is used to request uplink resources and perform beam recovery.

In the embodiment of the present application, if the terminal successfully restores the beam through the scheduling request, the terminal sets the first counter to 0 and stops the third timer. The first counter refers to a BFI counter (BFI_COUNTER) The third timer refers to a beam failure recovery timer (beamFailureRecoveryTimer).

In the above solution, the successful beam recovery refers to:

After the terminal sends a scheduling request, if a downlink control channel PDCCH is detected in the BFR search space and the PDCCH schedules data transmission, beam recovery is successful, for example: the terminal detects the PDCCH in bfrSearchSpace configured in the configured beamFailureRecoveryConfig , The PDCCH is scrambled by C-RNTI, and the downlink or uplink data is scheduled, the beam recovery is successful; or,

After the terminal sends the scheduling request, if the PDCCH is detected, the beam recovery is successful. For example, if the terminal detects the PDCCH and the PDCCH is received on a new beam, the beam recovery is successful; or,

After the terminal sends the scheduling request, if a downlink data channel (PDSCH, Physical Downlink Shared Channel) is detected, the beam recovery is successful; for example: the terminal receives the PDSCH, and the PDSCH is received on a new beam, the beam recovery is successful .

In the above solution, the PUCCH resources (time-frequency resources, period, etc.) for the scheduling request for beam recovery are configured by the network.

In the embodiment of the present application, if the terminal fails to request beam restoration through the scheduling, the terminal retransmits the scheduling request, or performs beam restoration through a BFR process.

It should be noted that the above technical solutions of the embodiments of the present application are implemented at the MAC layer of the terminal, and the above technical solutions are executed by the MAC entity of the terminal.

FIG. 4 is a schematic structural composition diagram of an apparatus for triggering BFR provided by an embodiment of the present application. As shown in FIG. 4, the apparatus includes:

The detection unit 401 is configured to detect the beam failure at the first time in the DRX inactive state;

The recovery unit 402 is configured to initiate a beam recovery process at a second time after the first time.

In an embodiment, the recovery unit 402 is configured to initiate a BFR process at a second time after the first time, and the BFR process is used to perform beam recovery.

In one embodiment, the second time is determined based on a third time, which is the time when the terminal enters the DRX active state from the DRX inactive state.

In an embodiment, the second time is determined based on the third time, including:

The second time is equal to the third time.

The second time is any time between the first time and the third time.

In an embodiment, the second time is determined based on a third time and a first offset time, where the third time is the time when the terminal enters the DRX active state from the DRX inactive state.

In an embodiment, the second time is determined based on the third time and the first offset time, including:

The second time is equal to the third time minus the first offset time.

The second time is any time between the first time and the fourth time, and the fourth time is equal to the third time minus the first offset time.

In an embodiment, the first offset time is configured by the network; or,

The first offset time is agreed by the agreement.

In one embodiment, the first offset time is configured by the network and includes:

The first offset time is configured by the network through RRC signaling.

In one embodiment, the second time is determined based on the end time of the first timer, and the start time of the first timer is the first time.

In an embodiment, the second time is determined based on the end time of the first timer, including:

If the end time of the first timer is before the third time, the second time is the end time of the first timer;

If the end time of the first timer is after the third time, the second time is equal to the three times;

The third time is the time when the terminal enters the DRX activated state from the DRX inactive state.

In one embodiment, the third time is the start time of the second timer, and the terminal enters the DRX active state from the DRX inactive state when the second timer is started.

In one embodiment, the start time of the second timer is configured by the network.

In an embodiment, the second time is determined based on a fourth time, which is the time when the terminal decides to send a scheduling request in a DRX inactive state.

In an embodiment, the device further includes a determination unit 403;

When the determining unit 403 determines to send the scheduling request at the fourth time, if it is determined that the beam failure has been detected, then:

The recovery unit 402 initiates a BFR process after the fourth time, and sends a scheduling request after the BFR is successful. The BFR process is used to perform beam recovery, and the scheduling request is used to request uplink resources.

In an embodiment, the recovery unit 402 initiates a BFR process on the first available BFR resource after the fourth time, and sends a scheduling request on the first available PUCCH resource after the BFR succeeds.

In an embodiment, the device further includes a determination unit 403;

The recovery unit 402 initiates a BFR process after the fourth time, and the BFR process is used to perform beam recovery and request uplink resources.

In an embodiment, the random access process corresponding to the BFR process is used to indicate that the BFR process is used to perform beam recovery and request uplink resources.

In an embodiment, the random access process corresponding to the BFR process is used to indicate that the BFR process is used to perform beam recovery and request uplink resources, including:

The specific transmission resource and / or specific preamble of MSG1 in the random access process corresponding to the BFR process is used to indicate that the BFR process is used for beam recovery and requesting uplink resources.

In an embodiment, the specific transmission resource and / or specific preamble of the MSG1 is configured by the network.

In an embodiment, the device further includes a determination unit 403;

The recovery unit 402 initiates a BFR process and sends a scheduling request after the fourth time. The BFR process is used to perform beam recovery, and the scheduling request is used to request uplink resources.

In an embodiment, the recovery unit 402 initiates a BFR process on the first available BFR resource after the fourth time, and sends a scheduling request on the first available PUCCH resource after the fourth time.

In an embodiment, the device further includes a determination unit 403;

The recovery unit 402 sends a scheduling request after the fourth time, where the scheduling request is used to request uplink resources and perform beam recovery.

In an embodiment, the device further includes: a setting unit 404;

The setting unit 404 is configured to set the first counter to 0 and stop the third timer if the beam recovery is successful through the scheduling request, and the first counter refers to a BFI counter and the third timer Refers to the beam failure recovery timer.

In an embodiment, the successful beam recovery refers to:

After sending the scheduling request, if a downlink control channel PDCCH is detected in the BFR search space, and the PDCCH schedules data transmission, the beam recovery is successful; or,

After sending the scheduling request, if the PDCCH is detected, the beam recovery is successful; or,

After sending the scheduling request, if the downlink data channel PDSCH is detected, the beam recovery is successful.

In one embodiment, the PUCCH resource used for the scheduling request for beam recovery is configured by the network.

In an embodiment, the restoration unit 402 is further configured to: if the beam restoration fails through the scheduling request, then: retransmit the scheduling request, or perform beam restoration through a BFR process.

Those skilled in the art should understand that the relevant description of the above apparatus for triggering BFR in the embodiments of the present application can be understood with reference to the relevant description of the method for triggering BFR in the embodiments of the present application.

FIG. 5 is a schematic structural diagram of a communication device 600 provided by an embodiment of the present application. The communication device may be a terminal. The communication device 600 shown in FIG. 5 includes a processor 610. The processor 610 may call and run a computer program from a memory to implement the method in the embodiments of the present application.

Optionally, as shown in FIG. 5, the communication device 600 may further include a memory 620. The processor 610 can call and run a computer program from the memory 620 to implement the method in the embodiments of the present application.

The memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.

Optionally, as shown in FIG. 5, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive other Information or data sent by the device.

Among them, the transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include antennas, and the number of antennas may be one or more.

Optionally, the communication device 600 may specifically be a network device according to an embodiment of the present application, and the communication device 600 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application. .

Optionally, the communication device 600 may specifically be the mobile terminal / terminal of the embodiment of the present application, and the communication device 600 may implement the corresponding process implemented by the mobile terminal / terminal in each method of the embodiment of the present application. This will not be repeated here.

6 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 700 shown in FIG. 6 includes a processor 710, and the processor 710 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 6, the chip 700 may further include a memory 720. The processor 710 can call and run a computer program from the memory 720 to implement the method in the embodiments of the present application.

The memory 720 may be a separate device independent of the processor 710, or may be integrated in the processor 710.

Optionally, the chip 700 may further include an input interface 730. The processor 710 can control the input interface 730 to communicate with other devices or chips. Specifically, it can obtain information or data sent by other devices or chips.

Optionally, the chip 700 may further include an output interface 740. The processor 710 can control the output interface 740 to communicate with other devices or chips. Specifically, it can output information or data to other devices or chips.

Optionally, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.

Optionally, the chip can be applied to the mobile terminal / terminal in the embodiments of the present application, and the chip can implement the corresponding process implemented by the mobile terminal / terminal in each method of the embodiments of the present application. Repeat.

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

7 is a schematic block diagram of a communication system 900 provided by an embodiment of the present application. As shown in FIG. 7, the communication system 900 includes a terminal 910 and a network device 920.

Wherein, the terminal 910 may be used to implement the corresponding functions implemented by the terminal in the above method, and the network device 920 may be used to implement the corresponding functions implemented by the network device in the above method.

It should be understood that the processor in the embodiment of the present application may be an integrated circuit chip, which has signal processing capabilities. In the implementation process, each step of the foregoing method embodiment may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software. The above-mentioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an existing programmable gate array (Field Programmable Gate Array, FPGA), or other available Programming logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application may be implemented or executed. The general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware decoding processor, or may be executed and completed by a combination of hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art, such as a random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, and register. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electronic Erasable programmable read only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synchlink DRAM, SLDRAM) ) And direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to these and any other suitable types of memories.

It should be understood that the foregoing memory is exemplary but not limiting. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data) SDRAM (DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is to say, the memories in the embodiments of the present application are intended to include but are not limited to these and any other suitable types of memories.

Embodiments of the present application also provide a computer-readable storage medium for storing computer programs.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiments of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiments of the present application. No longer.

Optionally, the computer-readable storage medium may be applied to the mobile terminal / terminal in the embodiments of the present application, and the computer program causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal in each method of the embodiments of the present application, in order to It is concise and will not be repeated here.

An embodiment of the present application also provides a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. Repeat again.

Optionally, the computer program product can be applied to the mobile terminal / terminal in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal / terminal in each method of the embodiments of the present application, for simplicity And will not be repeated here.

The embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on the computer, the computer is allowed to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. And will not be repeated here.

Optionally, the computer program can be applied to the mobile terminal / terminal in the embodiments of the present application, and when the computer program runs on the computer, the computer is allowed to execute the corresponding implementation of the mobile terminal / terminal in each method of the embodiments of the present application For the sake of brevity, I will not repeat them here.

Those of ordinary skill in the art may realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application of the technical solution and design constraints. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and conciseness of the description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a division of logical functions. In actual implementation, there may be other divisions, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment 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.

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application essentially or part of the contribution to the existing technology or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to enable a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

The above is only the specific implementation of this application, but the scope of protection of this application is not limited to this, any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in this application. It should be covered by the scope of protection of this application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method for triggering beam failure to recover BFR, the method includes:

In the inactive state of DRX receiving discontinuously, the terminal detects beam failure at the first time;

The terminal initiates a beam recovery process at a second time after the first time.
The method according to claim 1, wherein the terminal initiating the beam recovery process at a second time after the first time includes:

The terminal initiates a BFR process at a second time after the first time, and the BFR process is used for beam recovery.
The method according to claim 2, wherein the second time is determined based on a third time, the third time being the time when the terminal enters the DRX active state from the DRX inactive state.
The method of claim 3, wherein the second time is determined based on the third time, including:

The second time is equal to the third time.
The method of claim 3, wherein the second time is determined based on the third time, including:

The second time is any time between the first time and the third time.
The method according to claim 2, wherein the second time is determined based on a third time and a first offset time, the third time is a time when the terminal enters the DRX active state from the DRX inactive state.
The method of claim 6, wherein the second time is determined based on the third time and the first offset time, including:

The second time is equal to the third time minus the first offset time.
The method of claim 6, wherein the second time is determined based on the third time and the first offset time, including:

The second time is any time between the first time and the fourth time, and the fourth time is equal to the third time minus the first offset time.
The method according to any one of claims 6 to 8, wherein

The first offset time is configured by the network; or,

The first offset time is agreed by the agreement.
The method of claim 9, wherein the first offset time is configured by the network and includes:

The first offset time is configured by the network through unlimited resource control RRC signaling.
The method according to claim 2, wherein the second time is determined based on an end time of a first timer, and a start time of the first timer is the first time.
The method according to claim 11, wherein the second time is determined based on an end time of the first timer, including:

If the end time of the first timer is before the third time, the second time is the end time of the first timer;

If the end time of the first timer is after the third time, the second time is equal to the three times;

The third time is the time when the terminal enters the DRX activated state from the DRX inactive state.
The method according to any one of claims 3 to 12, wherein the third time is a start time of a second timer, and when the second timer starts, the terminal enters DRX activation from a DRX inactive state status.
The method according to claim 13, wherein the start time of the second timer is configured by a network.
The method according to claim 1, wherein the second time is determined based on a fourth time, the fourth time being a time when the terminal decides to send a scheduling request in a DRX inactive state.
The method of claim 15, wherein the method further comprises:

When the terminal decides to send the scheduling request at the fourth time, if it is determined that the beam failure has been detected, then:

The terminal initiates a BFR process after the fourth time, and sends a scheduling request after the BFR is successful. The BFR process is used for beam recovery, and the scheduling request is used to request uplink resources.
The method according to claim 16, wherein the terminal initiates a BFR process after the fourth time, and sends a scheduling request after the BFR succeeds, including:

The terminal initiates a BFR process on the first available BFR resource after the fourth time, and sends a scheduling request on the first available uplink control channel PUCCH resource after the BFR succeeds.
The method of claim 15, wherein the method further comprises:

When the terminal decides to send the scheduling request at the fourth time, if it is determined that the beam failure has been detected, then:

The terminal initiates a BFR process after the fourth time, and the BFR process is used to perform beam recovery and request uplink resources.
The method according to claim 18, wherein the random access procedure corresponding to the BFR procedure is used to indicate that the BFR procedure is used to perform beam recovery and request uplink resources.
The method according to claim 19, wherein the random access flow corresponding to the BFR flow is used to indicate that the BFR flow is used to perform beam recovery and request uplink resources, including:

The specific transmission resource and / or specific preamble of MSG1 in the random access process corresponding to the BFR process is used to indicate that the BFR process is used for beam recovery and requesting uplink resources.
The method according to claim 20, wherein the specific transmission resource and / or the specific preamble of the MSG1 is configured by a network.
The method of claim 15, wherein the method further comprises:

When the terminal decides to send the scheduling request at the fourth time, if it is determined that the beam failure has been detected, then:

The terminal initiates a BFR process and sends a scheduling request after the fourth time. The BFR process is used to perform beam recovery, and the scheduling request is used to request uplink resources.
The method according to claim 22, wherein the terminal initiating the BFR process and sending the scheduling request after the fourth time includes:

The terminal initiates a BFR process on the first available BFR resource after the fourth time, and sends a scheduling request on the first available PUCCH resource after the fourth time.
The method of claim 15, wherein the method further comprises:

When the terminal decides to send the scheduling request at the fourth time, if it is determined that the beam failure has been detected, then:

The terminal sends a scheduling request after the fourth time, where the scheduling request is used to request uplink resources and perform beam recovery.
The method according to claim 24, wherein if the terminal successfully restores the beam through the scheduling request, the terminal sets a first counter to 0 and stops a third timer, the first counter means A beam failure event BFI counter. The third timer refers to a beam failure recovery timer.
The method according to claim 25, wherein the successful beam recovery means:

After the terminal sends a scheduling request, if a downlink control channel PDCCH is detected in the BFR search space and the PDCCH schedules data transmission, the beam recovery is successful; or,

After the terminal sends the scheduling request, if the PDCCH is detected, the beam recovery is successful; or,

After the terminal sends the scheduling request, if the downlink data channel PDSCH is detected, the beam recovery is successful.
The method according to any one of claims 24 to 26, wherein the PUCCH resource for scheduling request for beam recovery is configured by a network.
The method according to any one of claims 24 to 27, wherein the method further comprises:

If the terminal fails to recover the beam through the scheduling request, the terminal retransmits the scheduling request, or performs the beam recovery through the BFR process.
A device for triggering BFR, the device comprising:

The detection unit is used to detect the beam failure in the first time in the DRX inactive state;

The recovery unit is configured to initiate a beam recovery process at a second time after the first time.
The apparatus according to claim 29, wherein the recovery unit is configured to initiate a BFR process at a second time after the first time, and the BFR process is used to perform beam recovery.
The apparatus according to claim 30, wherein the second time is determined based on a third time, the third time being the time when the terminal enters the DRX active state from the DRX inactive state.
The apparatus according to claim 31, wherein the second time is determined based on the third time, including:

The second time is equal to the third time.
The apparatus according to claim 31, wherein the second time is determined based on the third time, including:

The second time is any time between the first time and the third time.
The apparatus of claim 30, wherein the second time is determined based on a third time and a first offset time, the third time being a time when the terminal enters the DRX inactive state from the DRX inactive state.
The apparatus of claim 34, wherein the second time is determined based on the third time and the first offset time, including:

The second time is equal to the third time minus the first offset time.
The apparatus of claim 34, wherein the second time is determined based on the third time and the first offset time, including:

The second time is any time between the first time and the fourth time, and the fourth time is equal to the third time minus the first offset time.
The device according to any one of claims 34 to 36, wherein

The first offset time is configured by the network; or,

The first offset time is agreed by the agreement.
The apparatus of claim 37, wherein the first offset time is configured by a network and includes:

The first offset time is configured by the network through RRC signaling.
The apparatus according to claim 30, wherein the second time is determined based on an end time of a first timer, and a start time of the first timer is the first time.
The apparatus of claim 39, wherein the second time is determined based on an end time of the first timer, including:

If the end time of the first timer is before the third time, the second time is the end time of the first timer;

If the end time of the first timer is after the third time, the second time is equal to the three times;

The third time is the time when the terminal enters the DRX activated state from the DRX inactive state.
The apparatus according to any one of claims 31 to 40, wherein the third time is a start time of a second timer, and when the second timer starts, the terminal enters DRX activation from a DRX inactive state status.
The apparatus according to claim 41, wherein the start time of the second timer is configured by a network.
The apparatus according to claim 29, wherein the second time is determined based on a fourth time, the fourth time being a time when the terminal decides to send a scheduling request in a DRX inactive state.
The apparatus according to claim 43, wherein the apparatus further comprises a determination unit;

When the determining unit determines to send the scheduling request at the fourth time, if it is determined that the beam failure has been detected, then:

The recovery unit initiates a BFR process after the fourth time, and sends a scheduling request after the BFR is successful. The BFR process is used for beam recovery, and the scheduling request is used to request uplink resources.
The apparatus of claim 44, wherein the recovery unit initiates a BFR process on the first available BFR resource after the fourth time, and sends a scheduling request on the first available PUCCH resource after the BFR succeeds.
The apparatus according to claim 43, wherein the apparatus further comprises a determination unit;

When the determining unit determines to send the scheduling request at the fourth time, if it is determined that the beam failure has been detected, then:

The recovery unit initiates a BFR process after the fourth time, and the BFR process is used to perform beam recovery and request uplink resources.
The apparatus according to claim 46, wherein the random access flow corresponding to the BFR flow is used to indicate that the BFR flow is used to perform beam recovery and request uplink resources.
The apparatus according to claim 47, wherein the random access process corresponding to the BFR process is used to indicate that the BFR process is used to perform beam recovery and request uplink resources, including:

The specific transmission resource and / or specific preamble of MSG1 in the random access process corresponding to the BFR process is used to indicate that the BFR process is used for beam recovery and requesting uplink resources.
The apparatus according to claim 48, wherein the specific transmission resource and / or the specific preamble of the MSG1 is configured by a network.
The apparatus according to claim 43, wherein the apparatus further comprises a determination unit;

When the determining unit determines to send the scheduling request at the fourth time, if it is determined that the beam failure has been detected, then:

The restoration unit initiates a BFR process and sends a scheduling request after the fourth time. The BFR process is used to perform beam restoration, and the scheduling request is used to request uplink resources.
The apparatus of claim 50, wherein the restoration unit initiates a BFR process on the first available BFR resource after the fourth time, and sends a scheduling request on the first available PUCCH resource after the fourth time .
The apparatus according to claim 43, wherein the apparatus further comprises a determination unit;

When the determining unit determines to send the scheduling request at the fourth time, if it is determined that the beam failure has been detected, then:

The recovery unit sends a scheduling request after the fourth time, where the scheduling request is used to request uplink resources and perform beam recovery.
The apparatus according to claim 52, wherein the apparatus further comprises: a setting unit;

The setting unit is configured to set the first counter to 0 and stop the third timer if the beam recovery is successful through the scheduling request, the first counter refers to a BFI counter, and the third timer is Refers to the beam failure recovery timer.
The apparatus according to claim 53, wherein the successful beam recovery means:

After sending the scheduling request, if a downlink control channel PDCCH is detected in the BFR search space, and the PDCCH schedules data transmission, the beam recovery is successful; or,

After sending the scheduling request, if the PDCCH is detected, the beam recovery is successful; or,

After sending the scheduling request, if the downlink data channel PDSCH is detected, the beam recovery is successful.
The apparatus according to any one of claims 52 to 54, wherein the PUCCH resource for scheduling request for beam recovery is configured by a network.
The apparatus according to any one of claims 52 to 55, wherein the restoration unit is further configured to: if the beam restoration fails through the scheduling request, then: retransmit the scheduling request, or perform the beam through the BFR process restore.
A terminal includes: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 1 to 28 method.
A chip, including: a processor, for calling and running a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1 to 28.
A computer-readable storage medium for storing a computer program that causes a computer to perform the method according to any one of claims 1 to 28.
A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method according to any one of claims 1 to 28.
A computer program that causes a computer to execute the method according to any one of claims 1 to 28.