WO2020077600A1 - Procédé et dispositif pour le déclenchement de procédure de reprise après défaillance de faisceau, et terminal - Google Patents

Procédé et dispositif pour le déclenchement de procédure de reprise après défaillance de faisceau, et terminal Download PDF

Info

Publication number
WO2020077600A1
WO2020077600A1 PCT/CN2018/110896 CN2018110896W WO2020077600A1 WO 2020077600 A1 WO2020077600 A1 WO 2020077600A1 CN 2018110896 W CN2018110896 W CN 2018110896W WO 2020077600 A1 WO2020077600 A1 WO 2020077600A1
Authority
WO
WIPO (PCT)
Prior art keywords
time
bfr
terminal
scheduling request
timer
Prior art date
Application number
PCT/CN2018/110896
Other languages
English (en)
Chinese (zh)
Inventor
石聪
尤心
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2018/110896 priority Critical patent/WO2020077600A1/fr
Priority to CN201880091260.0A priority patent/CN111869313B/zh
Publication of WO2020077600A1 publication Critical patent/WO2020077600A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]

Definitions

  • 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.
  • 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.
  • Beam Failure Failure Instance indication Beam Failure Failure Instance indication
  • BFR Beam Failure Failure Recovery
  • 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.
  • Embodiments of the present application provide a method, device, and terminal for triggering BFR.
  • the terminal 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 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
  • 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.
  • 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.
  • the terminal 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.
  • 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.
  • SR Scheduling Request
  • FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a method for triggering BFR provided by an embodiment of the present application
  • FIG. 3 (a) is a schematic diagram 1 of the principle of delayed triggering BFR provided by an embodiment of the present application;
  • FIG. 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.
  • FIG. 4 is a schematic structural composition diagram of a device for triggering BFR provided by an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a communication system provided by an embodiment of the present application.
  • GSM Global System of Mobile
  • CDMA Code Division Multiple Access
  • WCDMA Broadband Code Division Multiple Access
  • GSM Global System of Mobile
  • CDMA Code Division Multiple Access
  • WCDMA Broadband Code Division Multiple Access
  • GSM Global System of Mobile
  • CDMA Code Division Multiple Access
  • WCDMA Broadband Code Division Multiple Access
  • GSM Global System of Mobile
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Communication System
  • WiMAX Global Interoperability for Microwave Access
  • 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.
  • 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.
  • BTS Base Transceiver Station
  • NodeB, NB base station
  • LTE Long Term Evolutional Node B, eNB or eNodeB
  • CRAN Cloud Radio Access Network
  • the network equipment can be a mobile switching center, a relay station, an access point, an on-board device, Wearable
  • the communication system 100 also includes at least one terminal 120 located within the coverage of the network device 110.
  • 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.
  • PSTN Public Switched Telephone Networks
  • DSL Digital Subscriber Lines
  • WLAN wireless local area networks
  • TV networks such as DVB-H networks, satellite networks, AM-FM A broadcast transmitter
  • IoT Internet of Things
  • a terminal configured to communicate through a wireless interface may be referred to as a "wireless communication terminal", “wireless terminal”, or “mobile terminal”.
  • 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.
  • PCS Personal Communication Systems
  • GPS Global Positioning System
  • 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.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • 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.
  • terminal 120 may perform terminal direct connection (Device to Device, D2D) communication.
  • D2D Terminal Direct connection
  • the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.
  • NR New Radio
  • FIG. 1 exemplarily shows one network device and two terminals.
  • 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.
  • 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.
  • network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.
  • the devices with communication functions in the network / system in the embodiments of the present application may be referred to as communication devices.
  • 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.
  • 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.
  • 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.
  • 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.
  • RNTI Radio Network Tempory Identity
  • a DRX cycle includes two time periods, one is DRX activation time, and the other is DRX inactivity time.
  • DRX Active Time includes the following situations:
  • drx-InactivityTimer or drx-RetransmissionTimerDL, or drx-RetransmissionTimerUL, or ra-ContentionResolutionTimer, it belongs to the DRX activation time.
  • the time after the terminal sends the scheduling request is the DRX activation time.
  • 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.
  • 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.
  • 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.
  • BFI_COUNTER beam failure event counter
  • the terminal in the DRX inactive state, may also receive Beam Failure Instance indication, which may trigger the beam recovery process.
  • the terminal receives a Beam Failure Failure Instance indication in the DRX inactive state, it will increase the BFI_COUNTER by 1.
  • 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.
  • the terminal 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.
  • 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.
  • 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.
  • 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.
  • the start time of the second timer is configured by the network.
  • the second timer is Onduration timer.
  • the MAC entity of the terminal 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:
  • 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 .
  • 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)
  • the terminal initiates the BFR process at time t2.
  • 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)
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • time t2 If the difference is T offset (that is, the first offset time), the terminal initiates the BFR process at time t3.
  • 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
  • T offset that is, the first offset time
  • 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.
  • 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.
  • 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.
  • 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)
  • the terminal starts the first timer at time t1
  • the first timer times out at time t4 is before t2, and the terminal initiates the BFR process at time t4.
  • 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)
  • the terminal starts the first timer at time t1
  • the first timer times out at time t4 is located after t2, and the terminal initiates the BFR process at time t2.
  • 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.
  • 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.
  • 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.
  • 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)
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 specific transmission resource and / or specific preamble of the MSG1 is configured by the network.
  • 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)
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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)
  • 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.
  • 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.
  • 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)
  • 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.
  • the terminal 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).
  • the successful beam recovery refers to:
  • the terminal 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,
  • 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,
  • 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 .
  • PDSCH Physical Downlink Shared Channel
  • the PUCCH resources (time-frequency resources, period, etc.) for the scheduling request for beam recovery are configured by the network.
  • the terminal 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.
  • 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.
  • 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.
  • 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.
  • the second time is determined based on the third time, including:
  • the second time is equal to the third time.
  • 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 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.
  • 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 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 first offset time is configured by the network; or,
  • the first offset time is agreed by the agreement.
  • the first offset time is configured by the network and includes:
  • the first offset time is configured by the network through RRC signaling.
  • 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.
  • the second time is determined based on the end time of the first timer, including:
  • the second time is the end time of the first timer
  • 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 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.
  • the start time of the second timer is configured by the network.
  • 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.
  • the device further includes a determination unit 403;
  • 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.
  • 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.
  • the device further includes a determination unit 403;
  • 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 the BFR process is used to perform beam recovery and request uplink resources.
  • 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.
  • 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 specific transmission resource and / or specific preamble of the MSG1 is configured by the network.
  • the device further includes a determination unit 403;
  • 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 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 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.
  • the device further includes a determination unit 403;
  • 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 sends a scheduling request after the fourth time, where the scheduling request is used to request uplink resources and perform beam recovery.
  • 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.
  • the successful beam recovery refers to:
  • the beam recovery After sending the scheduling request, if the PDCCH is detected, the beam recovery is successful; or,
  • the beam recovery After sending the scheduling request, if the downlink data channel PDSCH is detected, the beam recovery is successful.
  • the PUCCH resource used for the scheduling request for beam recovery is configured by the network.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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. .
  • 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.
  • FIG. 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the communication system 900 includes a terminal 910 and a network device 920.
  • the terminal 910 may be used to implement the corresponding functions implemented by the terminal in the above method
  • the network device 920 may be used to implement the corresponding functions implemented by the network device in the above method.
  • the processor in the embodiment of the present application may be an integrated circuit chip, which has signal processing capabilities.
  • 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.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • 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.
  • 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.
  • 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.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • Synchlink DRAM SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • 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.
  • static random access memory static random access memory
  • DRAM dynamic random access memory
  • SDRAM Synchronous dynamic random access memory
  • DDR SDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • synchronous connection Dynamic random access memory switch link DRAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • Embodiments of the present application also provide a computer-readable storage medium for storing computer programs.
  • 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.
  • 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.
  • 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.
  • 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.
  • the computer program can be applied to the network device in the embodiments of the present application.
  • 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.
  • 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.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a division of logical functions.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 .

Abstract

L'invention concerne un procédé et un dispositif pour le déclenchement de procédure de reprise après défaillance de faisceau (BFR), et un terminal. Le procédé comprend les étapes suivantes : un terminal détecte une défaillance de faisceau à un premier instant dans un état inactif de réception discontinue (DRX) ; et le terminal initie une procédure de reprise après défaillance de faisceau à un second instant postérieur au premier instant.
PCT/CN2018/110896 2018-10-18 2018-10-18 Procédé et dispositif pour le déclenchement de procédure de reprise après défaillance de faisceau, et terminal WO2020077600A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2018/110896 WO2020077600A1 (fr) 2018-10-18 2018-10-18 Procédé et dispositif pour le déclenchement de procédure de reprise après défaillance de faisceau, et terminal
CN201880091260.0A CN111869313B (zh) 2018-10-18 2018-10-18 一种触发波束失败恢复的方法及装置、终端

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/110896 WO2020077600A1 (fr) 2018-10-18 2018-10-18 Procédé et dispositif pour le déclenchement de procédure de reprise après défaillance de faisceau, et terminal

Publications (1)

Publication Number Publication Date
WO2020077600A1 true WO2020077600A1 (fr) 2020-04-23

Family

ID=70284416

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/110896 WO2020077600A1 (fr) 2018-10-18 2018-10-18 Procédé et dispositif pour le déclenchement de procédure de reprise après défaillance de faisceau, et terminal

Country Status (2)

Country Link
CN (1) CN111869313B (fr)
WO (1) WO2020077600A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117751683A (zh) * 2022-07-19 2024-03-22 北京小米移动软件有限公司 信息处理方法及装置、通信设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180138962A1 (en) * 2016-04-13 2018-05-17 Qualcomm Incorporated System and method for beam adjustment request
CN108513737A (zh) * 2018-03-28 2018-09-07 北京小米移动软件有限公司 信息传输方法和信息传输装置
CN108632007A (zh) * 2017-03-22 2018-10-09 华为技术有限公司 用于传输数据的方法和终端设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9801232B2 (en) * 2013-04-15 2017-10-24 Idac Holdings, Inc. Discontinuous reception (DRX) schemes for millimeter wavelength (MMW) dual connectivity
ES2955591T3 (es) * 2016-07-01 2023-12-04 Asustek Comp Inc Procedimiento y aparato para gestionar la comunicación cuando un haz de servicio deja de ser válido en un sistema de comunicación inalámbrica
US10264622B2 (en) * 2017-03-17 2019-04-16 Ofinno Technologies, Llc Inactive state data forwarding

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180138962A1 (en) * 2016-04-13 2018-05-17 Qualcomm Incorporated System and method for beam adjustment request
CN108632007A (zh) * 2017-03-22 2018-10-09 华为技术有限公司 用于传输数据的方法和终端设备
CN108513737A (zh) * 2018-03-28 2018-09-07 北京小米移动软件有限公司 信息传输方法和信息传输装置

Also Published As

Publication number Publication date
CN111869313B (zh) 2022-03-11
CN111869313A (zh) 2020-10-30

Similar Documents

Publication Publication Date Title
TWI821368B (zh) 非連續傳輸的方法和設備
WO2020019187A1 (fr) Procédé et appareil de surveillance de canal, dispositif terminal et dispositif de réseau
WO2020019756A1 (fr) Procédé et appareil de détermination de ressource de transmission, et dispositif terminal
WO2021120013A1 (fr) Procédé de surveillance d'un signal de réveil, dispositif terminal et dispositif de réseau
WO2021082012A1 (fr) Procédé pour déterminer l'état de démarrage d'un temporisateur continu de réception discontinue et dispositifs
WO2021081838A1 (fr) Procédé et appareil de configuration drx, dispositif terminal et dispositif de réseau
WO2020087369A1 (fr) Procédé de comptage, dispositif terminal et appareil
WO2021217351A1 (fr) Procédé de surveillance de canal, dispositif électronique et support de stockage
WO2021087675A1 (fr) Procédé de surveillance d'un signal de réveil, dispositif électronique et support de stockage
WO2020001123A1 (fr) Appareil et procédé de détection de canal de commande de liaison descendante, et dispositif terminal
US20240080699A1 (en) Sdt failure reporting method, terminal device, and network device
WO2020077667A1 (fr) Procédé et dispositif d'activation de temporisateur, et terminal
WO2021068173A1 (fr) Procédé et appareil de transmission de signal ainsi que dispositif terminal
WO2021092861A1 (fr) Procédé de communication sans fil, dispositif de terminal et dispositif de réseau
WO2020258192A1 (fr) Procédé et appareil de transmission de données, ainsi que terminal
WO2020077600A1 (fr) Procédé et dispositif pour le déclenchement de procédure de reprise après défaillance de faisceau, et terminal
WO2021000320A1 (fr) Procédé et appareil de transmission de données, dispositif réseau et terminal
WO2020024611A1 (fr) Procédé et dispositif de transmission d'informations, et support de stockage informatique
WO2020191592A1 (fr) Procédé et appareil de configuration d'occasion de radiorecherche, et terminal et dispositif de réseau
WO2020206643A1 (fr) Procédé d'accès aléatoire, dispositif, et support d'enregistrement
WO2022236835A1 (fr) Procédé et appareil de détermination d'un comportement d'un dispositif terminal, dispositif terminal et dispositif de réseau
US11963255B2 (en) Method and apparatus for determining eDRX configuration parameters, and terminal
WO2022021023A1 (fr) Procédé et appareil d'indication d'informations, dispositif terminal et dispositif de réseau
WO2020191760A1 (fr) Procédé de transmission de canal, dispositif, et support de stockage
WO2020186467A1 (fr) Procédé et appareil pour réception discontinue sur spectre sans licence

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18937225

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18937225

Country of ref document: EP

Kind code of ref document: A1