WO2019184716A1 - 波束失败处理方法、终端及网络设备 - Google Patents

波束失败处理方法、终端及网络设备 Download PDF

Info

Publication number
WO2019184716A1
WO2019184716A1 PCT/CN2019/078116 CN2019078116W WO2019184716A1 WO 2019184716 A1 WO2019184716 A1 WO 2019184716A1 CN 2019078116 W CN2019078116 W CN 2019078116W WO 2019184716 A1 WO2019184716 A1 WO 2019184716A1
Authority
WO
WIPO (PCT)
Prior art keywords
beam failure
random access
scell
access resource
network device
Prior art date
Application number
PCT/CN2019/078116
Other languages
English (en)
French (fr)
Inventor
吴昱民
陈力
Original Assignee
维沃移动通信有限公司
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 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2019184716A1 publication Critical patent/WO2019184716A1/zh
Priority to US17/035,213 priority Critical patent/US20210058285A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/08—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the receiving station
    • H04B7/0868—Hybrid systems, i.e. switching and combining
    • H04B7/088—Hybrid systems, i.e. switching and combining using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a beam failure processing method, a terminal, and a network device.
  • a dual connectivity (DC) architecture including a primary cell group (MCG) and a secondary cell group (SCG).
  • MCG corresponds to a master node (MN) on the network device side
  • SCG corresponds to a secondary node (SN) on the network device side.
  • MCG includes a Primary Cell (PCell) and a Secondary Cell (SCell)
  • PCell and PSCell can also be collectively referred to as SpCell.
  • the terminal When the downlink beam of the PCell of the terminal fails, the terminal triggers a beam failure recovery request procedure.
  • the terminal sends a random access preamble (preamble) on the PCell, and waits on the PCell to receive feedback information on the network device side.
  • the feedback information is the physicality of the Cell Radio Network Temporary Identifier (C-RNTI) scheduling.
  • the downlink control channel Physical Downlink Control Channel, PDCCH). After receiving the feedback information of the network device for the beam failure recovery request, the terminal determines that the beam (or service) corresponding to the cell is successfully restored.
  • the terminal fails to generate a beam failure in the SCell, if both the SCell and the Pcell are configured with contention-based random access resources, the terminal does not know how to notify the cell that the network device fails the beam, and cannot determine which contention-based random access resource to select for beam recovery. .
  • the embodiments of the present disclosure provide a beam failure processing method, a terminal, and a network device, to solve the problem that the terminal cannot determine how to perform processing when the terminal fails in the SCell in the related art.
  • an embodiment of the present disclosure provides a beam failure processing method, which is applied to a terminal side, and includes:
  • an embodiment of the present disclosure further provides a terminal, including:
  • a first receiving module configured to receive, by the network device side, configuration information of a random access resource used for transmitting a beam failure recovery request message, where the configuration information is used to indicate whether the network device configures a random access resource for the secondary cell SCell;
  • the processing module is configured to determine, according to the indication of the configuration information, whether to send a beam failure recovery request message to the network device, where the beam failure occurs in the SCell.
  • an embodiment of the present disclosure provides a terminal, where the terminal includes a processor, a memory, and a computer program stored on the memory and operable on the processor, where the computer program is executed by the processor to implement the beam failure processing method. A step of.
  • an embodiment of the present disclosure provides a method for processing a beam failure, which is applied to a network device side, and includes:
  • the configuration information of the random access resource used for transmitting the beam failure recovery request message is sent to the terminal, where the configuration information is used to indicate whether the random access resource is configured for the secondary cell SCell of the terminal.
  • an embodiment of the present disclosure provides a network device, including:
  • the first sending module is configured to send, to the terminal, configuration information of a random access resource for transmitting a beam failure recovery request message, where the configuration information is used to indicate whether a random access resource is configured for the secondary cell SCell of the terminal.
  • an embodiment of the present disclosure further provides a network device, where the network device includes a processor, a memory, and a computer program stored on the memory and operable on the processor, where the processor implements the beam failure when executing the computer program. The steps of the processing method.
  • an embodiment of the present disclosure provides a computer readable storage medium, where a computer program is stored, and the computer program is executed by a processor to implement the step of the beam failure processing method.
  • the embodiment of the present disclosure indicates whether the random access resource of the beam failure recovery is configured for the SCell by using the configuration information.
  • the beam failure recovery process is initiated according to the indication of the configuration information, so that the terminal and the network device side The beam failure recovery is consistent, and the beam failure recovery of the SCell is completed.
  • FIG. 1 is a schematic flowchart diagram of a method for processing a beam failure on a terminal side according to an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of a beam failure recovery process based on non-contention random access according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram of a beam failure recovery process based on contention random access according to an embodiment of the present disclosure
  • FIG. 4 is a schematic structural diagram of a module of a terminal according to an embodiment of the present disclosure.
  • Figure 5 is a block diagram showing a terminal of an embodiment of the present disclosure.
  • FIG. 6 is a schematic flowchart diagram of a method for processing a beam failure on a network device side according to an embodiment of the present disclosure
  • FIG. 7 is a schematic structural diagram of a module of a network device according to an embodiment of the present disclosure.
  • Figure 8 shows a block diagram of a network device in accordance with an embodiment of the present disclosure.
  • the embodiment of the present disclosure provides a beam failure processing method, which is applied to a terminal side. As shown in FIG. 1 , the method includes the following steps:
  • Step 11 Receive configuration information of a random access resource for transmitting a beam failure recovery request message from the network device side.
  • the configuration information is used to indicate whether the network device configures a random access resource for the secondary cell SCell, and the network device configures, for the one or more SCells of the terminal, resources for the beam failure recovery request message.
  • the random access resource referred to herein includes a physical random access channel (PRACH) resource reserved by the network device for transmitting a beam failure recovery request. It is worth noting that some of the resources of the PRACH resources configured by the network device are used for ordinary random access of the terminal except for beam failure recovery, and another part of resources are used for failure of the terminal to transmit the beam when the beam fails.
  • PRACH physical random access channel
  • the random access resources mentioned herein may be non-contention random access resources (such as dedicated PRACH-Config PRACH resources), or may be competing random access resources (such as PRACH resources configured by common PRACH-Config).
  • Step 12 In the case that a beam failure occurs in the SCell, determine whether to send a beam failure recovery request message to the network device according to the indication of the configuration information.
  • the beam failure recovery request message is sent to the network device according to the indication of the configuration information. If not, the beam failure recovery process is started. If not, the beam failure processing flow is triggered. In this way, when the beam fails in the SCell, the terminal can initiate a beam failure recovery process according to the configuration information, so that the terminal and the network device side fail to recover, and complete the beam failure recovery of the SCell.
  • the configuration information includes at least one of the following:
  • the cell identification information corresponding to the random access resource such as the PCell identifier, the SCell identifier, or the Serving Cell identifier corresponding to the PRACH resource;
  • BWP Bandwidth Part
  • the beam identification information corresponding to the random access resource is the beam identification information corresponding to the random access resource.
  • the configuration information further includes: resource location information used to transmit beam recovery information. That is, the network device can configure the location of the received resource of the beam recovery information, for example, the resource location of the physical downlink control channel (PDCCH) that receives the beam recovery information.
  • the network device can configure the location of the received resource of the beam recovery information, for example, the resource location of the physical downlink control channel (PDCCH) that receives the beam recovery information.
  • PDCCH physical downlink control channel
  • step 12 includes: when the SCell fails to generate a random access resource for beam failure recovery, if the configuration information indicates that the network device configures the random access resource for beam failure recovery for the SCell, Sending a beam failure recovery request message to the network device.
  • the terminal When detecting a beam failure of a certain SCell, the terminal triggers a beam failure recovery process of the SCell. Based on the configuration information of step 11, the terminal selects a target random access resource (such as a PRACH) of the request message of the beam failure recovery process. The transmission beam fails to recover the request message.
  • a target random access resource such as a PRACH
  • the determination of the target random access resource includes but is not limited to the following scenarios:
  • Scenario 1 When the random access resource corresponding to the SCell includes the non-contention random access resource and the contention random access resource, the beam failure recovery request message is sent to the network device by using the non-contention random access resource. That is, if the random access resources configured by the network device for the SCell for the transmission beam failure recovery request message include: contention-based random access resources, and non-contention based random access resources, the terminal preferentially adopts Non-contention based random access resources.
  • Scenario 2 When the random access resource is configured on the SCell and the target cell, the beam failure recovery request is sent to the network device by using the first random access resource corresponding to the SCell.
  • the target cell includes at least one of a primary cell PCell and a primary secondary cell PSCell.
  • the network device is a random access resource configured for the SCell to transmit a beam failure recovery request message, and is configured on both the sPCell and the SCell, the terminal preferentially uses the random access resource on the SCell where the beam failure occurs.
  • the first random access resource includes: a non-contention random access resource or a competitive random access resource.
  • the terminal preferentially adopts the "contention-based random access resource" on the SCell where the beam failure occurs.
  • the terminal preferentially adopts the "non-contention based random access resource" on the SCell where the beam failure occurs.
  • Scenario 3 When the random access resource is configured on the SCell and the target cell, detecting whether the first random access resource corresponding to the SCell is available, and when the target random access resource is unavailable, the second random access corresponding to the target cell The resource sends a beam failure recovery request to the network device.
  • the target cell includes: a primary cell PCell and a primary secondary cell PSCell.
  • the terminal needs to detect whether the first random access resource on the SCell is available, if the network device is configured with the random access resource for transmitting the beam failure recovery request message, and is configured on the sPCell and the SCell. If available, the first random access resource is preferentially used.
  • the beam failure recovery request is sent to the network device by using the second random access resource corresponding to the target cell.
  • the detecting whether the first random access resource is available may be implemented by referring to, but not limited to, measuring a beam corresponding to the first random access resource on the SCell, for example, a measurement result of a Synchronous Signal Block (SSB), For example, if the reference signal received power (RSRP) is higher than the threshold value configured by the network device, if it is higher, the first random access resource is determined to be available. If not, the first random access resource is determined to be unavailable. use.
  • RSRP reference signal received power
  • the first random access resource includes: a non-contention random access resource or a contention random access resource
  • the second random access resource includes: a non-contention random access resource or a contention random access resource.
  • the terminal preferentially adopts the "non-contention based random access resource" on the SCell where the beam failure occurs, if the UE If no "non-contention based random access resource" is available on the SCell, the terminal sends a beam failure recovery request to the network device by using the "non-contention based random access resource” configured by the SpCell.
  • the method further includes:
  • the data is transmitted by the target beam indicated by the beam recovery indication information.
  • the terminal is in conflict resolution, if the beam recovery indication information (such as C-RNTI) sent by the network device is received, the terminal performs data transmission and reception according to the target beam (new beam) indicated by the beam recovery indication information, and completes beam recovery.
  • the beam recovery indication information such as C-RNTI
  • the beam failure recovery request message is resent to the network device until the beam recovery indication information is received or the number of transmissions reaches a preset threshold.
  • the preset time period can be protocol defined or configured by the network device. If the terminal does not receive the beam recovery indication information sent by the network device in the preset time period (such as the ra-Response Window configured by the network device), the terminal may resend the beam failure recovery request message.
  • the SCell beam failure recovery counter is incremented by one. Until the terminal receives the beam recovery indication information sent by the network device, or the number of times the beam failure recovery request message is sent reaches a preset threshold (the SCell beam failure recovery counter reaches a preset threshold).
  • the terminal determines that the SCell beam recovery fails, and automatically triggers the beam recovery failure processing behavior of the SCell.
  • step 12 further includes:
  • the configuration information indicates that the network device configures the random access resource for the beam failure recovery for the SCell
  • the random access resource corresponding to the SCell is unavailable, it is determined that the beam failure recovery request message is not sent to the network device, and is triggered.
  • SCell's beam recovery failure processing behavior In this scenario, the network device configures the random access resource for beam failure recovery for the SCell.
  • the terminal detects that the random access resource is unavailable the device fails to start the beam failure recovery process of the SCell and determines that the SCell beam recovery fails. The beam recovery failure processing behavior of the SCell is triggered.
  • the configuration information indicates that the network device does not configure the random access resource for beam failure recovery for the SCell
  • the network device does not configure the random access resource for the beam failure recovery of the SCell.
  • the terminal fails to start the beam failure recovery process of the SCell, determines that the SCell beam recovery fails, and triggers the beam recovery failure processing behavior of the SCell.
  • the foregoing beam recovery failure processing behavior includes at least one of the following:
  • the MAC of the terminal indicates to the upper layer (such as the RRC layer) that the beam recovery of the SCell fails, or the random access procedure of the SCell fails;
  • the MAC of the terminal indicates to the lower layer (such as the physical PHY layer) that the beam recovery of the SCell fails, or the random access procedure of the SCell fails;
  • the upper layer of the terminal (such as the RRC layer) initiates an RRC connection re-establishment process
  • the measurement corresponding to the failure detection of the SCell beam is stopped.
  • the bottom layer of the terminal (such as the physical PHY layer) stops the measurement corresponding to the failure detection of the SCell beam, such as the channel state indication reference signal corresponding to the beam failure detection of the SCell. Measurement of Reference Signal, CSI-RS).
  • the beam failure information includes at least one of the following:
  • the cell identity of the SCell that is, the cell identity of the SCell where the beam failure occurs.
  • the cell measurement result of the SCell that is, the cell measurement result of the SCell where the beam failure occurs, such as Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal to Noise Ratio (Signal to Interference and Noise Ratio, SINR), etc.
  • RSRP Reference Signal Received Power
  • RSRQ Reference Signal Received Quality
  • SINR Signal to Noise Ratio
  • the beam measurement result of the SCell is one or more beam measurement results of the SCell in which the beam failure occurs, such as RSRP of a certain SSB, reference signal received quality RSRQ, signal to noise ratio SINR, and the like.
  • Measured cell measurement results of other serving cells where other serving cells include: other serving cells except the SCell, or other than the SCell belonging to the same cell group (such as MCG or SCG) Other service areas.
  • the cell measurement results of other serving cells such as RSRP, reference signal reception quality RSRQ, signal to noise ratio SINR, and the like.
  • the measured beam measurement results of other serving cells where the other serving cells include: other serving cells except the SCell, or other than the SCell belonging to the same cell group (such as MCG or SCG) Other service communities.
  • the other serving cells include: other serving cells except the SCell, or other than the SCell belonging to the same cell group (such as MCG or SCG) Other service communities.
  • one or more beam measurement results of other serving cells such as RSRP of a certain SSB, reference signal received quality RSRQ, signal to noise ratio SINR, and the like.
  • the measured cell measurement results of other non-serving cells such as neighboring cells, etc.
  • cell measurement results of neighboring cells such as RSRP, reference signal receiving quality RSRQ, signal-to-noise ratio SINR, and the like.
  • the measured beam measurement results of other non-serving cells such as one or more beam measurement results of the neighboring cell, such as RSRP of a certain SSB, reference signal received quality RSRQ, signal to noise ratio SINR, and the like.
  • the beam failure recovery request message mentioned above includes at least one of the following:
  • the cell identification information of the beam failure such as the SCell identifier
  • the beam information includes at least one of beam identification information (such as an SSB identifier, a CSI-RS identifier, and the like) and beam measurement information (such as RSRP, RSRQ, SINR, etc.).
  • beam identification information such as an SSB identifier, a CSI-RS identifier, and the like
  • beam measurement information such as RSRP, RSRQ, SINR, etc.
  • the beam recovery process of the SCell in which the beam failure occurs is further described in conjunction with a specific process.
  • the method includes the following steps:
  • Step 21 The terminal receives the configuration information of the random access resource used for transmitting the beam failure recovery request message from the network device side, where the configuration information is used to indicate the non-contention random access resource configured by the network device for the SCell.
  • Step 22 The terminal sends a message (Msg1) to the network device by using the non-contention random access resource indicated by the configuration information, and the Msg1 includes: Random Access Preambles. And beam failure recovery request message.
  • the terminal calculates the identifier information of the network device scheduling message 2 (Msg2) according to the sending time and the frequency position of the Msg1, such as a Random Access Radio Network Temporary Identity (RA-RNTI).
  • RA-RNTI Random Access Radio Network Temporary Identity
  • RA-RNTI 1+t id +10*f id ;
  • t id is a time domain identifier of the random access signal, such as a subframe identifier
  • f id is a frequency domain identifier of the random access signal.
  • the terminal After transmitting the Msg1, the terminal monitors the downlink channel to obtain the feedback information Msg2 of the network device in a fixed window, such as a random access response window (RAR window).
  • a fixed window such as a random access response window (RAR window).
  • the starting position of the RAR window is the subframe in which the Msg1 transmission ends, plus 3 subframes, and the length is the length of the network device configuration.
  • Step 23 The network device sends a random access response (RAR), that is, message two, to the terminal.
  • Message 2 includes: Msg1 identification information, Timing Advance Command (TAC), uplink grant authorization information (UL Grant), back off indicator (Back Off Indicator), and temporary terminal identification information (Temporary C-RNTI).
  • TAC Timing Advance Command
  • UL Grant uplink grant authorization information
  • Back Off Indicator Back Off Indicator
  • Temporal C-RNTI temporary terminal identification information
  • Beam recovery indication information If the terminal receives the RAR successfully, the beam is restored according to the RAR, and the data is transmitted and received in the target beam indicated by the RAR. Specifically, the terminal, according to the beam recovery indication information of the network device, uses the new beam to perform data transmission and reception according to the beam recovery indication information after the collision is resolved (such as receiving the terminal identifier C-RNTI indicated by the network side), and the beam recovery is successfully completed. .
  • the terminal determines the time of the next random access transmission according to the backoff information indicated in the RAR. Specifically, the terminal does not receive the RAR sent by the network device in the preset time period specified by the protocol (such as the RAR Window configured by the network device), and the terminal resends the beam failure recovery request message according to step 22, and the SCell beam fails to recover.
  • the counter is incremented by 1.
  • the method includes the following steps:
  • Step 31 The terminal receives the configuration information of the random access resource used for transmitting the beam failure recovery request message from the network device side, where the configuration information is used to indicate the contention random access resource configured by the network device for the SCell.
  • Step 32 When detecting that the SCell fails to generate a beam, the terminal selects a random access resource in the contention random access resource indicated by the configuration information, and sends a message one (Msg1) to the network device by using the selected random access resource. After transmitting the Msg1, the terminal calculates the identifier information of the network device scheduling message 2 (Msg2) according to the sending time and the frequency position of the Msg1, such as the RA-RNT.
  • Msg2 the identifier information of the network device scheduling message 2
  • Step 33 After receiving the Msg1, the network device calculates the timing advance TA according to the Msg1, and sends a random access response RAR to the terminal, where the random access response includes at least the timing advance information and the UL grant for the message three (Msg3). .
  • Step 34 The terminal sends an uplink transmission on the UL grant specified by the Msg2, where the content of the uplink transmission of the Msg3 is different for different random accesses, for example, for the initial access, the Msg3 transmits an RRC connection establishment request.
  • the Msg3 includes: a beam failure recovery request message.
  • Step 35 After receiving the Msg3, the network device responds to the service request carried in the Msg3, and feeds back the solution result to the terminal, that is, message four (Msg4). Specifically, the beam recovery indication information is included in the Msg4. The terminal, according to the beam recovery indication information of the network device, uses the new beam to perform data transmission and reception according to the beam recovery indication information after the collision is resolved (such as receiving the terminal identifier C-RNTI indicated by the network side), and the beam recovery is successfully completed. If the terminal fails to receive the RAR, it determines the time of the next random access transmission according to the backoff information indicated in the RAR.
  • Msg4 message four
  • the terminal does not receive the RAR sent by the network device in the preset time period specified by the protocol (such as the RAR Window configured by the network device), and the terminal resends the beam failure recovery request message according to step 22, and the SCell beam fails to recover.
  • the counter is incremented by 1.
  • the network device indicates, by using the configuration information, whether the random access resource of the beam failure recovery is configured for the SCell of the terminal, and the terminal initiates the beam according to the indication of the configuration information when detecting that the SCell fails to generate the beam.
  • the failure recovery process is consistent with the failure recovery of the beam on the network device side, and the beam failure recovery of the SCell is completed.
  • the terminal 400 of the embodiment of the present disclosure can implement configuration information of receiving a random access resource for transmitting a beam failure recovery request message from a network device side in the foregoing embodiment; in the case that a beam failure occurs in the SCell, And determining, according to the indication of the configuration information, whether to send the beam failure recovery request message method to the network device, and achieving the same effect, the terminal 400 specifically includes the following functional modules:
  • the first receiving module 410 is configured to receive configuration information of a random access resource used for transmitting a beam failure recovery request message from the network device side, where the configuration information is used to indicate whether the network device configures a random access resource for the secondary cell SCell;
  • the processing module 420 is configured to determine, according to the indication of the configuration information, whether to send a beam failure recovery request message to the network device, if the SCell fails to generate a beam.
  • the configuration information includes at least one of the following:
  • the beam identification information corresponding to the random access resource is the beam identification information corresponding to the random access resource.
  • the configuration information further includes: resource location information used for transmitting beam recovery information.
  • the processing module 420 includes:
  • a first processing submodule configured to send, by the target random access resource, a beam failure recovery request message to the network device, if the configuration information indicates that the network device configures the random access resource for beam failure recovery for the SCell.
  • the first processing submodule includes:
  • a first processing unit configured to send a beam failure recovery request message to the network device by using the non-contention random access resource when the random access resource corresponding to the SCell includes: the non-contention random access resource and the contention random access resource;
  • a second processing unit configured to: when the random access resource is configured on the SCell and the target cell, send a beam failure recovery request to the network device by using the first random access resource corresponding to the SCell;
  • the target cell includes: the primary cell At least one of a PCell and a primary and secondary cell PSCell;
  • a third processing unit configured to detect, when the random access resource is configured on the SCell and the target cell, whether the first random access resource corresponding to the SCell is available, and when the target random access resource is unavailable, the third corresponding to the target cell
  • the second random access resource sends a beam failure recovery request to the network device.
  • the first random access resource includes: a non-contention random access resource or a contention random access resource
  • the second random access resource includes: a non-contention random access resource or a contention random access resource.
  • the processing module 420 further includes:
  • a second processing submodule configured to: if the beam recovery indication information fed back by the network device is received within a preset time period, transmit the data by using the target beam indicated by the beam recovery indication information;
  • the third processing submodule is configured to resend the beam failure recovery request message to the network device if the beam recovery indication information fed back by the network device is not received within the preset time period, until the beam recovery indication information is received or the number of transmissions reaches Preset threshold.
  • the terminal further includes:
  • the triggering module is configured to trigger a beam recovery failure processing behavior of the SCell after the number of transmissions reaches a preset threshold.
  • the processing module further includes:
  • a fourth processing submodule configured to: if the configuration information indicates that the network device configures the random access resource for beam failure recovery for the SCell, if the random access resource corresponding to the SCell is unavailable, determining that the network device does not send the random access resource to the network device The beam fails to recover the request message and triggers the beam recovery failure processing behavior of the SCell;
  • a fifth processing submodule configured to: when the configuration information indicates that the network device does not configure the random access resource for the beam failure recovery for the SCell, determine that the beam failure recovery request message is not sent to the network device, and trigger the beam recovery of the SCell. Failure processing behavior.
  • the beam recovery failure processing behavior includes at least one of the following:
  • the beam failure information includes at least one of the following:
  • the other serving cells include: other serving cells that belong to the same cell group as the SCell.
  • the beam failure recovery request message includes at least one of the following:
  • the beam information includes at least one of beam identification information and beam measurement information.
  • the terminal in the embodiment of the present disclosure receives the configuration information sent by the network device to determine whether the random access resource for the beam failure recovery is configured for the SCell, and the terminal detects the failure of the SCell beam, according to the configuration information.
  • the indication initiates a beam failure recovery process, so that the terminal and the network device side beam failure recovery are consistent, and the SCell beam failure recovery is completed.
  • FIG. 5 is a schematic diagram of a hardware structure of a terminal that implements various embodiments of the present disclosure, including but not limited to: a radio frequency unit 51, a network module 52, and an audio output unit 53, The input unit 54, the sensor 55, the display unit 56, the user input unit 57, the interface unit 58, the memory 59, the processor 510, and the power source 511 and the like.
  • the terminal structure shown in FIG. 5 does not constitute a limitation of the terminal, and the terminal may include more or less components than those illustrated, or combine some components, or different component arrangements.
  • the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palmtop computer, an in-vehicle terminal, a wearable device, and a pedometer.
  • the radio frequency unit 51 is configured to receive configuration information of a random access resource used for transmitting a beam failure recovery request message from the network device side, where the configuration information is used to indicate whether the network device configures a random access resource for the secondary cell SCell.
  • the processor 510 is configured to determine, according to the indication of the configuration information, whether to send a beam failure recovery request message to the network device, where the beam failure occurs in the SCell;
  • the terminal of the embodiment of the present disclosure receives the configuration information sent by the network device to determine whether the random access resource for the beam failure recovery is configured for the SCell.
  • the terminal fails to detect the beam failure of the SCell, the terminal initiates the beam failure according to the indication of the configuration information.
  • the recovery process is consistent with the failure recovery of the beam on the network device side to complete the beam failure recovery of the SCell.
  • the radio frequency unit 51 can be used for receiving and transmitting signals during and after receiving or transmitting information, and specifically, receiving downlink data from the base station, and then processing the data to the processor 510; The uplink data is sent to the base station.
  • radio frequency unit 51 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • the radio unit 51 can also communicate with the network and other devices through a wireless communication system.
  • the terminal provides the user with wireless broadband Internet access through the network module 52, such as helping the user to send and receive emails, browse web pages, and access streaming media.
  • the audio output unit 53 can convert the audio data received by the radio frequency unit 51 or the network module 52 or stored in the memory 59 into an audio signal and output as sound. Moreover, the audio output unit 53 can also provide audio output (eg, call signal reception sound, message reception sound, etc.) associated with a particular function performed by the terminal 50.
  • the audio output unit 53 includes a speaker, a buzzer, a receiver, and the like.
  • the input unit 54 is for receiving an audio or video signal.
  • the input unit 54 may include a graphics processing unit (GPU) 541 and a microphone 542 that images an still picture or video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode.
  • the data is processed.
  • the processed image frame can be displayed on the display unit 56.
  • the image frames processed by the graphics processor 541 may be stored in the memory 59 (or other storage medium) or transmitted via the radio unit 51 or the network module 52.
  • the microphone 542 can receive sound and can process such sound as audio data.
  • the processed audio data can be converted to a format output that can be transmitted to the mobile communication base station via the radio unit 51 in the case of a telephone call mode.
  • Terminal 50 also includes at least one type of sensor 55, such as a light sensor, motion sensor, and other sensors.
  • the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 561 according to the brightness of the ambient light, and the proximity sensor can close the display panel 561 and/or when the terminal 50 moves to the ear. Or backlight.
  • the accelerometer sensor can detect the magnitude of acceleration in all directions (usually three axes). When it is stationary, it can detect the magnitude and direction of gravity.
  • sensor 55 may also include fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, thermometer, infrared Sensors, etc., will not be described here.
  • the display unit 56 is for displaying information input by the user or information provided to the user.
  • the display unit 56 can include a display panel 561.
  • the display panel 561 can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.
  • the user input unit 57 can be used to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the terminal.
  • the user input unit 57 includes a touch panel 571 and other input devices 572.
  • the touch panel 571 also referred to as a touch screen, can collect touch operations on or near the user (such as a user using a finger, a stylus, or the like on the touch panel 571 or near the touch panel 571. operating).
  • the touch panel 571 may include two parts of a touch detection device and a touch controller.
  • the touch detection device detects the touch orientation of the user, and detects a signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into contact coordinates, and sends the touch information.
  • the processor 510 receives the commands from the processor 510 and executes them.
  • the touch panel 571 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves.
  • the user input unit 57 may also include other input devices 572.
  • other input devices 572 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, switch buttons, etc.), trackballs, mice, and joysticks, and are not described herein again.
  • the touch panel 571 can be overlaid on the display panel 561.
  • the touch panel 571 detects a touch operation on or near the touch panel 571, it is transmitted to the processor 510 to determine the type of the touch event, and then the processor 510 according to the touch.
  • the type of event provides a corresponding visual output on display panel 561.
  • the touch panel 571 and the display panel 561 are two independent components to implement the input and output functions of the terminal, in some embodiments, the touch panel 571 may be integrated with the display panel 561.
  • the input and output functions of the terminal are implemented, and are not limited herein.
  • the interface unit 58 is an interface in which an external device is connected to the terminal 50.
  • the external device may include a wired or wireless headset port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, and an audio input/output. (I/O) port, video I/O port, headphone port, and more.
  • Interface unit 58 may be operable to receive input from an external device (eg, data information, power, etc.) and transmit the received input to one or more components within terminal 50 or may be used at terminal 50 and external devices Transfer data between.
  • the memory 59 can be used to store software programs as well as various data.
  • the memory 59 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored according to Data created by the use of the mobile phone (such as audio data, phone book, etc.).
  • the memory 59 may include a high speed random access memory, and may also include a nonvolatile memory such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
  • the processor 510 is the control center of the terminal, which connects various parts of the entire terminal using various interfaces and lines, and executes by executing or executing software programs and/or modules stored in the memory 59, and calling data stored in the memory 59.
  • the processor 510 may include one or more processing units; preferably, the processor 510 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, an application, etc., and performs modulation and demodulation.
  • the processor primarily handles wireless communications. It can be understood that the above modem processor may not be integrated into the processor 510.
  • the terminal 50 may further include a power source 511 (such as a battery) for supplying power to the respective components.
  • a power source 511 such as a battery
  • the power source 511 may be logically connected to the processor 510 through the power management system to manage charging, discharging, power consumption management, etc. through the power management system.
  • terminal 50 includes some functional modules not shown, and details are not described herein again.
  • an embodiment of the present disclosure further provides a terminal, including a processor 510, a memory 59, a computer program stored on the memory 59 and executable on the processor 510, and the computer program is implemented by the processor 510.
  • the processes of the foregoing beam failure processing method embodiments can achieve the same technical effects. To avoid repetition, details are not described herein again.
  • the terminal may be a wireless terminal or a wired terminal, and the wireless terminal may be a device that provides voice and/or other service data connectivity to the user, a handheld device with a wireless connection function, or other processing device connected to the wireless modem. .
  • the wireless terminal can communicate with one or more core networks via a Radio Access Network (RAN), which can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a mobile terminal.
  • RAN Radio Access Network
  • the computer for example, can be a portable, pocket, handheld, computer built-in or in-vehicle mobile device that exchanges language and/or data with the wireless access network.
  • PCS Personal Communication Service
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal digital assistant
  • the wireless terminal may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, and a remote terminal.
  • the access terminal, the user terminal (User Terminal), the user agent (User Agent), and the user device (User Device or User Equipment) are not limited herein.
  • the embodiment of the present disclosure further provides a computer readable storage medium.
  • the computer readable storage medium stores a computer program, where the computer program is executed by the processor to implement various processes of the beam failure processing method embodiment, and can achieve the same Technical effects, to avoid repetition, will not be repeated here.
  • the computer readable storage medium such as a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
  • the beam failure processing method of the embodiment of the present disclosure is applied to the network device side, and includes the following steps:
  • Step 61 Send configuration information of a random access resource for transmitting a beam failure recovery request message to the terminal.
  • the configuration information is used to indicate whether a random access resource is configured for the secondary cell SCell of the terminal.
  • the configuration information includes at least one of the following:
  • the beam identification information corresponding to the random access resource is the beam identification information corresponding to the random access resource.
  • the configuration information further includes: resource location information used for transmitting beam recovery information, and the network device configures, for the one or more SCells of the terminal, resources for the beam failure recovery request message.
  • the random access resource referred to herein includes a PRACH resource reserved for the terminal by the network device for transmitting a beam failure recovery request.
  • the random access resource may be a non-contention random access resource (such as a dedicated PRACH-Config PRACH resource), or may be a contentive random access resource (such as a PRACH resource configured by a common PRACH-Config).
  • the method further includes: receiving a beam failure recovery request for the SCell sent by the terminal by using the target random access resource.
  • the beam failure recovery request message includes at least one of the following:
  • the cell identification information of the beam failure such as the SCell identifier
  • the beam information includes at least one of beam identification information (such as an SSB identifier, a CSI-RS identifier, and the like) and beam measurement information (such as RSRP, RSRQ, SINR, etc.).
  • beam identification information such as an SSB identifier, a CSI-RS identifier, and the like
  • beam measurement information such as RSRP, RSRQ, SINR, etc.
  • the method further includes: determining, according to the beam failure recovery request, whether to send the beam recovery indication information to the terminal.
  • the terminal receives the beam recovery indication information fed back by the network device within a preset time period, the terminal transmits the data through the target beam indicated by the beam recovery indication information. If the beam recovery indication information fed back by the network device is not received within the preset time period, the beam failure recovery request message is resent to the network device until the beam recovery indication information is received or the number of transmissions reaches a preset threshold. If the beam failure recovery request message is sent to the preset threshold, the beam recovery indication information sent by the network device is not received. Then, the terminal determines that the SCell beam recovery fails, and automatically triggers the beam recovery failure processing behavior of the SCell.
  • the method further includes: receiving, by the terminal side, beam failure information of the SCell.
  • the upper layer of the terminal (such as the RRC layer) reports the beam failure information of the SCell to the network device.
  • the beam failure information includes at least one of the following:
  • the other serving cells include: other serving cells that belong to the same cell group as the SCell.
  • the network device indicates, by using the configuration information, whether the random access resource of the beam failure recovery is configured for the SCell of the terminal, and the terminal initiates the beam according to the indication of the configuration information when detecting that the SCell fails to generate the beam.
  • the failure recovery process is consistent with the failure recovery of the beam on the network device side, and the beam failure recovery of the SCell is completed.
  • the network device 600 of the embodiment of the present disclosure can implement the configuration information of the random access resource used for transmitting the beam failure recovery request message to the terminal in the foregoing embodiment, and the method has the same effect.
  • the configuration information is used to indicate whether a random access resource is configured for the secondary cell SCell of the terminal.
  • the network device 600 specifically includes the following functional modules:
  • the first sending module is configured to send, to the terminal, configuration information of a random access resource for transmitting a beam failure recovery request message, where the configuration information is used to indicate whether a random access resource is configured for the secondary cell SCell of the terminal.
  • the configuration information includes at least one of the following:
  • the beam identification information corresponding to the random access resource is the beam identification information corresponding to the random access resource.
  • the configuration information further includes: resource location information used for transmitting beam recovery information.
  • the method further includes:
  • the method further includes:
  • the beam failure recovery request it is determined whether the beam recovery indication information is fed back to the terminal.
  • the method further includes:
  • the beam failure information of the SCell is received from the terminal side.
  • the beam failure information includes at least one of the following:
  • the other serving cells include: other serving cells that belong to the same cell group as the SCell.
  • the beam failure recovery request message includes at least one of the following:
  • the beam information includes at least one of beam identification information and beam measurement information.
  • each module of the above network device and terminal is only a division of logical functions. In actual implementation, it may be integrated into one physical entity in whole or in part, or may be physically separated. And these modules can all be implemented by software in the form of processing component calls; or all of them can be implemented in hardware form; some modules can be realized by processing component calling software, and some modules are realized by hardware.
  • the determining module may be a separately set processing element, or may be integrated in one of the above-mentioned devices, or may be stored in the memory of the above device in the form of program code, by a processing element of the above device. Call and execute the functions of the above determination module.
  • the implementation of other modules is similar.
  • each step of the above method or each of the above modules may be completed by an integrated logic circuit of hardware in the processor element or an instruction in the form of software.
  • the above modules may be one or more integrated circuits configured to implement the above method, such as one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors ( A digital signal processor (DSP), or one or more Field Programmable Gate Arrays (FPGAs).
  • ASICs Application Specific Integrated Circuits
  • DSP digital signal processor
  • FPGAs Field Programmable Gate Arrays
  • the processing component may be a general purpose processor, such as a central processing unit (CPU) or other processor that can call the program code.
  • CPU central processing unit
  • these modules can be integrated and implemented in the form of a system-on-a-chip (SOC).
  • SOC system-on-a-chip
  • the network device of the embodiment of the present disclosure indicates, by using the configuration information, whether the random access resource of the beam failure recovery is configured for the SCell of the terminal, and the terminal initiates the beam failure according to the indication of the configuration information when detecting that the SCell fails to generate the beam.
  • the recovery process is consistent with the failure recovery of the beam on the network device side to complete the beam failure recovery of the SCell.
  • an embodiment of the present disclosure further provides a network device, including a processor, a memory, and a computer program stored on the memory and operable on the processor, the processor executing the computer program
  • a network device including a processor, a memory, and a computer program stored on the memory and operable on the processor, the processor executing the computer program
  • the steps in the beam failure processing method as described above are implemented.
  • Embodiments of the invention also provide a computer readable storage medium having stored thereon a computer program that, when executed by a processor, implements the steps of the beam failure processing method as described above.
  • the network device 800 includes an antenna 81, a radio frequency device 82, and a baseband device 83.
  • the antenna 81 is connected to the radio frequency device 82.
  • the radio frequency device 82 receives information through the antenna 81 and transmits the received information to the baseband device 83 for processing.
  • the baseband device 83 processes the information to be transmitted and transmits it to the radio frequency device 82.
  • the radio frequency device 82 processes the received information and transmits it via the antenna 81.
  • the above-described band processing device may be located in the baseband device 83, and the method performed by the network device in the above embodiment may be implemented in the baseband device 83, which includes the processor 84 and the memory 85.
  • the baseband device 83 may include, for example, at least one baseband board on which a plurality of chips are disposed, as shown in FIG. 8, one of which is, for example, a processor 84, connected to the memory 85 to call a program in the memory 85 to execute The network device operation shown in the above method embodiment.
  • the baseband device 83 can also include a network interface 86 for interacting with the radio frequency device 82, such as a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the processor here may be a processor or a collective name of multiple processing elements.
  • the processor may be a CPU, an ASIC, or one or more configured to implement the method performed by the above network device.
  • An integrated circuit such as one or more microprocessor DSPs, or one or more field programmable gate array FPGAs.
  • the storage element can be a memory or a collective name for a plurality of storage elements.
  • Memory 85 can be either volatile memory or non-volatile memory, or can include both volatile and non-volatile memory.
  • the non-volatile memory may be a Read-Only Memory (ROM), a Programmable ROM (Programmable ROM), or an Erasable PROM (EPROM). , electrically erasable programmable read only memory (EEPROM) or flash memory.
  • the volatile memory may be a Random Access Memory (RAM), which is used as an external cache.
  • RAM Random Access Memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous).
  • DRAM double data rate synchronous dynamic random access memory
  • DDRSDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM Synch link DRAM
  • DRRAM Direct Memory Bus
  • the network device of the embodiment of the present disclosure further includes: a computer program stored on the memory 85 and operable on the processor 84, and the processor 84 calls a computer program in the memory 85 to execute the method executed by each module shown in FIG. .
  • the configuration may be performed to: send configuration information of a random access resource for transmitting a beam failure recovery request message to the terminal, where the configuration information is used to indicate whether the secondary cell SCell of the terminal is configured with random Access resources.
  • the configuration information includes at least one of the following:
  • the beam identification information corresponding to the random access resource is the beam identification information corresponding to the random access resource.
  • the configuration information further includes: resource location information used for transmitting beam recovery information.
  • the computer program when called by the processor 84, it can be used to: receive a beam failure recovery request for the SCell sent by the terminal through the target random access resource.
  • the computer program when called by the processor 84, it can be used to perform: determining, according to the beam failure recovery request, whether to feed back the beam recovery indication information to the terminal.
  • the computer program when called by the processor 84, it can be used to perform: receiving beam failure information of the SCell from the terminal side.
  • the beam failure information includes at least one of the following:
  • the other serving cells include: other serving cells that belong to the same cell group as the SCell.
  • the beam failure recovery request message includes at least one of the following:
  • the beam information includes at least one of beam identification information and beam measurement information.
  • the network device may be a Global System of Mobile communication (GSM) or a Code Division Multiple Access (CDMA) base station (Base Transceiver Station, BTS for short) or a wideband code.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • BTS Base Transceiver Station
  • WCDMA Wideband Code Division Multiple Access
  • eNB or eNodeB evolved Node B
  • eNodeB evolved Node B
  • a base station or the like in a future 5G network is not limited herein.
  • the network device in the embodiment of the present disclosure indicates whether the random access resource of the beam failure recovery is configured for the SCell of the terminal, and the terminal initiates a beam failure recovery process according to the indication of the configuration information when detecting that the SCell has failed to generate a beam.
  • the beam failure recovery of the terminal is consistent with that of the network device, and the beam failure recovery of the SCell is completed.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • 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, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solution of the embodiment.
  • each functional unit in various embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, a portion of the technical solution of the present disclosure that contributes in essence or to the related art or a part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several The instructions are for causing 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 various embodiments of the present disclosure.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
  • the objects of the present disclosure can also be achieved by running a program or a set of programs on any computing device.
  • the computing device can be a well-known general purpose device.
  • the objects of the present disclosure may also be realized by merely providing a program product including program code for implementing the method or apparatus. That is to say, such a program product also constitutes the present disclosure, and a storage medium storing such a program product also constitutes the present disclosure.
  • the storage medium may be any known storage medium or any storage medium developed in the future.
  • various components or steps may be decomposed and/or recombined.

Landscapes

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

Abstract

本公开公开了一种波束失败处理方法、终端及网络设备，其方法包括：从网络设备侧接收用于传输波束失败恢复请求消息的随机接入资源的配置信息，配置信息用于指示网络设备是否为辅小区SCell配置了随机接入资源；在SCell发生波束失败的情况下，根据配置信息的指示，确定是否向网络设备发送波束失败恢复请求消息。

Description

波束失败处理方法、终端及网络设备
相关申请的交叉引用
本申请主张在2018年3月28日在中国提交的中国专利申请号No.201810266184.4的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种波束失败处理方法、终端及网络设备。
背景技术
在第五代(5Generation，5G)移动通信系统中，采用了双连接(Dual Connectivity，DC)架构，包括主小区组(Master Cell Group，MCG)和辅小区组(Secondary Cell Group，SCG)。其中，MCG对应于网络设备侧的主节点(Master Node，MN)，SCG对应于网络设备侧的辅节点(Secondary Node，SN)。MCG包括主小区(Primary Cell，PCell)和辅小区(Secondary Cell，SCell)，SCG包括主辅小区(Primary/Secondary Cell，PSCell)和辅小区SCell。其中，PCell和PSCell也可统称为SpCell。
当终端的PCell的下行波束发生失败的时候，终端会触发波束失败恢复请求过程(beam failure recovery request procedure)。终端会在PCell发送随机接入前导码(preamble)，并在PCell上等待接收网络设备侧的反馈信息，该反馈信息为小区无线网络临时标识(Cell Radio Network Temporary Identifier，C-RNTI)调度的物理下行控制信道(Physical Downlink Control Channel，PDCCH)。当终端接收到网络设备对于该波束失败恢复请求的反馈信息后，终端判断该小区对应的波束(或服务)恢复成功。但是当终端在SCell发生波束失败时，如果SCell和Pcell都配置基于竞争的随机接入资源，终端不知如何通知网络设备波束失败的小区，也无法确定选择哪个基于竞争的随机接入资源进行波束恢复。
发明内容
本公开实施例提供了一种波束失败处理方法、终端及网络设备，以解决相关技术中终端在SCell发生波束失败时，终端无法确定如何进行处理的问题。
第一方面，本公开实施例提供了一种波束失败处理方法，应用于终端侧，包括：
从网络设备侧接收用于传输波束失败恢复请求消息的随机接入资源的配置信息，配置信息用于指示网络设备是否为辅小区SCell配置了随机接入资源；
在SCell发生波束失败的情况下，根据配置信息的指示，确定是否向网络设备发送波束失败恢复请求消息。
第二方面，本公开实施例还提供了一种终端，包括：
第一接收模块，用于从网络设备侧接收用于传输波束失败恢复请求消息的随机接入资源的配置信息，配置信息用于指示网络设备是否为辅小区SCell配置了随机接入资源；
处理模块，用于在SCell发生波束失败的情况下，根据配置信息的指示，确定是否向网络设备发送波束失败恢复请求消息。
第三方面，本公开实施例提供了一种终端，终端包括处理器、存储器以及存储于存储器上并可在处理器上运行的计算机程序，计算机程序被处理器执行时实现上述的波束失败处理方法的步骤。
第四方面，本公开实施例提供了一种波束失败处理方法，应用于网络设备侧，包括：
向终端发送用于传输波束失败恢复请求消息的随机接入资源的配置信息，配置信息用于指示是否为终端的辅小区SCell配置了随机接入资源。
第五方面，本公开实施例提供了一种网络设备，包括：
第一发送模块，用于向终端发送用于传输波束失败恢复请求消息的随机接入资源的配置信息，配置信息用于指示是否为终端的辅小区SCell配置了随机接入资源。
第六方面，本公开实施例还提供了一种网络设备，网络设备包括处理器、 存储器以及存储于存储器上并可在处理器上运行的计算机程序，处理器执行计算机程序时实现上述的波束失败处理方法的步骤。
第七方面，本公开实施例提供了一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，计算机程序被处理器执行时实现上述的波束失败处理方法的步骤。
这样，本公开的实施例通过配置信息指示是否为SCell配置了波束失败恢复的随机接入资源，在SCell发生波束失败时，根据配置信息的指示发起波束失败恢复流程，使终端与网络设备侧的波束失败恢复保持一致，完成SCell的波束失败恢复。
附图说明
为了更清楚地说明本公开实施例的技术方案，下面将对本公开实施例的描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1表示本公开实施例终端侧的波束失败处理方法的流程示意图；
图2表示本公开实施例基于非竞争随机接入的波束失败恢复流程示意图；
图3表示本公开实施例基于竞争随机接入的波束失败恢复流程示意图；
图4表示本公开实施例终端的模块结构示意图；
图5表示本公开实施例的终端框图；
图6表示本公开实施例网络设备侧的波束失败处理方法的流程示意图；
图7表示本公开实施例网络设备的模块结构示意图；
图8表示本公开实施例的网络设备框图。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例例如能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本公开实施例提供了一种波束失败处理方法，应用于终端侧，如图1所示，该方法包括以下步骤：
步骤11：从网络设备侧接收用于传输波束失败恢复请求消息的随机接入资源的配置信息。
其中，配置信息用于指示网络设备是否为辅小区SCell配置了随机接入资源，网络设备给终端的一个或多个SCell配置用于波束失败恢复请求消息的资源。这里所说的随机接入资源包括网络设备为终端预留的、用于传输波束失败恢复请求的物理随机接入信道(Physical Random Access Channel，PRACH)资源。值得指出的是，网络设备配置的PRACH资源中，一部分资源用于终端的除用于波束失败恢复外的其它目的的普通随机接入，另一部分资源用于在波束失败时供终端发送波束失败恢复请求，且这两部分资源正交，即，用于发送波束失败恢复请求的PRACH资源与用于普通随机接入的PRACH资源正交(包括时域正交、频域正交和/或码域正交)。这里所说的随机接入资源可以是非竞争的随机接入资源(如dedicated PRACH-Config PRACH资源)，亦可以是竞争的随机接入资源(如common PRACH-Config配置的PRACH资源)。
步骤12：在SCell发生波束失败的情况下，根据配置信息的指示，确定是否向网络设备发送波束失败恢复请求消息。
在SCell发生波束失败的情况下，根据上述配置信息的指示，确定是否向网络设备发送波束失败恢复请求消息，若发送，则启动波束失败恢复流程，若不发送，则触发波束失败处理流程。这样，终端在SCell发生波束失败时，能够根据配置信息的指示发起波束失败恢复流程，使终端与网络设备侧的波 束失败恢复保持一致，完成SCell的波束失败恢复。
其中，配置信息包括以下至少一项：
随机接入资源对应的小区标识信息，如：PRACH资源对应的PCell标识、SCell标识或Serving Cell标识等；
随机接入资源对应的带宽部分(Bandwidth Part，BWP)标识信息；以及
随机接入资源对应的波束标识信息。
可选地，配置信息还包括：用于传输波束恢复信息的资源位置信息。也就是说，网络设备可以配置波束恢复信息的接收资源位置，例如，接收波束恢复信息的物理下行控制信道(Physical Downlink Control Channel，PDCCH)的资源位置等。
一种优选实施例中，步骤12包括：在SCell发生波束失败的情况下，在配置信息指示网络设备为SCell配置了用于波束失败恢复的随机接入资源的情况下，通过目标随机接入资源，向网络设备发送波束失败恢复请求消息。终端在检测到某个SCell发生波束失败的时候，触发该SCell的波束失败恢复过程，基于步骤11的配置信息，终端选择该波束失败恢复过程的请求消息的目标随机接入资源(如PRACH)，以发送波束失败恢复请求消息。
其中，目标随机接入资源的确定包括但不限于以下场景：
场景一、当SCell对应的随机接入资源包括：非竞争随机接入资源和竞争随机接入资源时，通过非竞争随机接入资源，向网络设备发送波束失败恢复请求消息。也就是说，如果网络设备为该SCell配置的、用于传输波束失败恢复请求消息的随机接入资源包括：基于竞争的随机接入资源，以及基于非竞争的随机接入资源，那么终端优先采用基于非竞争的随机接入资源。
场景二、当随机接入资源同时配置在SCell和目标小区上时，通过SCell对应的第一随机接入资源，向网络设备发送波束失败恢复请求。其中，目标小区包括：主小区PCell和主辅小区PSCell中的至少一项。这里是说，如果网络设备为该SCell配置的、用于传输波束失败恢复请求消息的随机接入资源，同时配置在sPCell和SCell上，终端优先采用发生波束失败的该SCell上的随机接入资源。其中，第一随机接入资源包括：非竞争随机接入资源或 竞争随机接入资源。具体地，如果该SCell的波束失败恢复过程的“基于竞争的随机接入资源”同时配置在SpCell和SCell，终端优先采用该发生波束失败的SCell上的“基于竞争的随机接入资源”。如果该SCell的波束失败恢复过程的“基于非竞争的随机接入资源”同时配置在SpCell和SCell，终端优先采用该发生波束失败的SCell上的“基于非竞争的随机接入资源”。
场景三、当随机接入资源同时配置在SCell和目标小区上时，检测SCell对应的第一随机接入资源是否可用，在目标随机接入资源不可用时，通过目标小区对应的第二随机接入资源，向网络设备发送波束失败恢复请求。其中，目标小区包括：主小区PCell和主辅小区PSCell。这里是说，如果网络设备为该SCell配置的、用于传输波束失败恢复请求消息的随机接入资源，同时配置在sPCell和SCell上，终端需要检测SCell上的第一随机接入资源是否可用，若可用，则优先采用第一随机接入资源，若不可用，则通过目标小区对应的第二随机接入资源，向网络设备发送波束失败恢复请求。其中，检测第一随机接入资源是否可用可参照但不限于以下方式实现：测量该SCell上的第一随机接入资源对应的波束，例如同步信号块(Synchronous Signal Block，SSB)的测量结果，例如参考信号接收功率(Reference Symbol Received Power，RSRP)是否高于网络设备配置的门限值，若高于则确定第一随机接入资源可用，若不高于则确定第一随机接入资源不可用。
其中，第一随机接入资源包括：非竞争随机接入资源或竞争随机接入资源，所述第二随机接入资源包括：非竞争随机接入资源或竞争随机接入资源。具体地，如果该SCell的波束失败恢复过程的“基于竞争的随机接入资源”同时配置在SpCell和SCell，终端优先采用该发生波束失败的SCell上的“基于竞争的随机接入资源”，如果终端在该SCell上没有检测到可用的“基于竞争的随机接入资源”，则终端采用SpCell配置的“基于竞争的随机接入资源”向网络设备发送波束失败恢复请求。如果该SCell的波束失败恢复过程的“基于非竞争的随机接入资源”同时配置在SpCell和SCell，终端优先采用该发生波束失败的SCell上的“基于非竞争的随机接入资源”，如果UE在该SCell上没有检测到可用的“基于非竞争的随机接入资源”，则终端采用SpCell配置的“基于非竞争的随机接入资源”向网络设备发送波束失败恢复请求。
在一种较佳实施例中，通过目标随机接入资源，向网络设备发送波束失败恢复请求消息的步骤之后，该方法还包括：
若在预设时间段内接收到网络设备反馈的波束恢复指示信息，则通过波束恢复指示信息指示的目标波束进行数据的传输。终端在冲突解决时，如接收到网络设备发送的波束恢复指示信息(如C-RNTI)后，根据波束恢复指示信息指示的目标波束(新的波束)进行数据收发，完成波束恢复。
若在预设时间段内未接收到网络设备反馈的波束恢复指示信息，则向网络设备重新发送波束失败恢复请求消息，直至接收到波束恢复指示信息或发送次数达到预设阈值。该预设时间段可以是协议定义的或网络设备配置的。若终端在预设时间段(如网络设备配置的随机接入响应接收窗口ra-Response Window)内，没有接收到网络设备下发的波束恢复指示信息，终端可重新发送波束失败恢复请求消息，同时该SCell波束失败恢复计数器加1。直至终端接收到网络设备发送的波束恢复指示信息，或者波束失败恢复请求消息发送次数达到预设阈值(该SCell波束失败恢复计数器达到预设阈值)。
若波束失败恢复请求消息发送次数达到预设阈值后，仍未收到网络设备发送的波束恢复指示信息，这时终端确定SCell波束恢复失败，自动触发SCell的波束恢复失败处理行为。
另外，步骤12还包括：
在配置信息指示网络设备为SCell配置了用于波束失败恢复的随机接入资源的情况下，若SCell对应的随机接入资源不可用，则确定不向网络设备发送波束失败恢复请求消息，并触发SCell的波束恢复失败处理行为。这种场景下，虽然网络设备为SCell配置了波束失败恢复用的随机接入资源，但当终端检测到该随机接入资源不可用时，无法启动SCell的波束失败恢复流程，确定SCell波束恢复失败，触发SCell的波束恢复失败处理行为。
或者，在配置信息指示网络设备未为SCell配置用于波束失败恢复的随机接入资源的情况下，确定不向网络设备发送波束失败恢复请求消息，并触发SCell的波束恢复失败处理行为。这种场景下，网络设备未为SCell配置波束失败恢复用的随机接入资源，终端无法启动SCell的波束失败恢复流程，确定SCell波束恢复失败，触发SCell的波束恢复失败处理行为。
优选地，上述波束恢复失败处理行为包括以下至少一项：
向高层指示波束恢复失败，其中，终端的MAC指示给高层(如RRC层)该SCell的波束恢复失败，或该SCell的随机接入过程失败；
向底层指示波束恢复失败，其中，终端的MAC指示给低层(如物理PHY层)该SCell的波束恢复失败，或该SCell的随机接入过程失败；
去激活所述SCell，具体地，终端的MAC层去激活该SCell；
发起无线资源控制RRC连接的重建流程，具体地，终端的高层(如RRC层)发起RRC连接重建立过程；
向网络设备发送SCell的波束失败信息，具体地，终端的高层(如RRC层)上报该SCell的波束失败信息给网络设备；
停止对SCell波束失败检测对应的测量，具体地，终端的底层(如物理PHY层)停止该SCell波束失败检测对应的测量，如该SCell的波束失败检测对应的信道状态指示参考信号(Channel State Information Reference Signal，CSI-RS)的测量。
其中，波束失败信息包括以下至少一项：
波束失败指示信息。
波束恢复失败指示信息。
SCell的小区标识，即发生波束失败的SCell的小区标识。
SCell的小区测量结果，即发生波束失败的SCell的小区测量结果，如参考信号接收功率(Reference Signal Received Power，RSRP)、参考信号接收质量(Reference Signal Received Quality，RSRQ)、信号噪声比(Signal to Interference and Noise Ratio，SINR)等。
SCell的波束测量结果，即发生波束失败的SCell的一个或多个波束测量结果，如某个SSB的RSRP、参考信号接收质量RSRQ、信号噪声比SINR等。
测量到的其他服务小区的小区测量结果，其中，其他服务小区包括：除该SCell之外的其他服务小区，或者，与SCell属于相同小区组(如MCG或SCG)内的除该SCell之外的其他服务小区。这里是指，其他服务小区的小区测量结果，如RSRP、参考信号接收质量RSRQ、信号噪声比SINR等。
测量到的其他服务小区对应的波束测量结果，其中，其他服务小区包括： 除该SCell之外的其他服务小区，或者，与SCell属于相同小区组(如MCG或SCG)内的除该SCell之外的其他服务小区。这里是指，其他服务小区的一个或多个波束测量结果，如某个SSB的RSRP、参考信号接收质量RSRQ、信号噪声比SINR等。
测量到的其他非服务小区(如邻小区等)的小区测量结果，如：邻小区的小区测量结果，如RSRP、参考信号接收质量RSRQ、信号噪声比SINR等。
测量到的其他非服务小区对应的波束测量结果，如：邻小区的一个或多个波束测量结果，如某个SSB的RSRP、参考信号接收质量RSRQ、信号噪声比SINR等。
上述提及的波束失败恢复请求消息，包括以下至少一项：
波束失败的指示信息；
发生波束失败的小区标识信息，如SCell标识；
发生波束失败恢复的波束信息。
其中，波束信息包括：波束标识信息(如SSB标识、CSI-RS标识等)和波束测量信息(如RSRP、RSRQ、SINR等)中的至少一项。
下面本实施例将结合具体流程对发生波束失败的SCell的波束恢复流程做进一步说明。
以基于非竞争随机接入资源为例，如图2所示，该方法包括以下步骤：
步骤21：终端从网络设备侧接收用于传输波束失败恢复请求消息的随机接入资源的配置信息，该配置信息用于指示网络设备为SCell配置的非竞争随机接入资源。
步骤22：终端在检测到SCell发生波束失败时，通过配置信息指示的非竞争随机接入资源，向网络设备发送消息一(Msg1)，该Msg1中包括：随机接入前导码(Random Access Preambles)，以及波束失败恢复请求消息。终端在发送Msg1后，根据Msg1的发送时间和频率位置计算网络设备调度消息二(Msg2)的标识信息，如随机接入无线网络临时标识(Random Access Radio Network Temporary Identity，RA-RNTI)。具体计算方式如下：
RA-RNTI＝1+t id+10*f id；
其中：t id是随机接入信号的时域标识，如子帧标识；f id是随机接入信号 的频域标识。
终端在发送Msg1后，在一个固定窗口内，如随机接入响应窗口(Random Access Response window，RAR window)，监听下行信道以获取网络设备的反馈信息Msg2。该RAR window的开始位置为Msg1发送结束的子帧加上3个子帧，长度为网络设备配置的长度。
步骤23：网络设备向终端发送随机接入响应(Random Access Response，RAR)，即消息二。消息二中包含：Msg1标识信息、上行定时提前量信息(Timing Advance Command，TAC)、上行发送授权信息(UL Grant)、回退信息(Back off Indicator)、临时终端标识信息(Temporary C-RNTI)，以及波束恢复指示信息。如果终端接收RAR成功，则按照RAR进行波束恢复，并在RAR指示的目标波束进行数据的收发。具体地，终端根据网络设备的波束恢复指示信息，在冲突解决(如接收到网络侧指示的终端标识C-RNTI)后，根据波束恢复指示信息，采用新的波束进行数据收发，成功完成波束恢复。如果终端接收RAR失败，则根据RAR中指示的回退信息确定下次发送随机接入的时刻。具体地，终端在协议规定的预设时间段(如网络设备配置的RAR Window)内没有收到该网络设备发送的RAR，终端根据步骤22重新发送波束失败恢复请求消息，同时该SCell波束失败恢复计数器加1。
以基于竞争的随机接入资源为例，如图3所示，该方法包括以下步骤：
步骤31：终端从网络设备侧接收用于传输波束失败恢复请求消息的随机接入资源的配置信息，该配置信息用于指示网络设备为SCell配置的竞争随机接入资源。
步骤32：终端在检测到SCell发生波束失败时，终端在配置信息指示的竞争随机接入资源中选择随机接入资源，并利用选择的随机接入资源向网络设备发送消息一(Msg1)。终端在发送Msg1后，根据Msg1的发送时间和频率位置计算网络设备调度消息二(Msg2)的标识信息，如RA-RNT。其中，RA-RNTI和RAR window的计算方式与非竞争随机接入过程相似，故不再赘述。
步骤33：网络设备接收到Msg1后，根据Msg1计算定时提前量TA，并向终端发送随机接入响应RAR，随机接入响应中至少包含该定时提前量信息和针对消息三(Msg3)的UL grant。
步骤34：终端在Msg2指定的UL grant上发送上行传输，其中，对于不同作用的随机接入，Msg3上行传输的内容不同，例如对于初始接入，Msg3传输的是RRC连接建立请求。对于波束失败恢复流程，该Msg3中包括：波束失败恢复请求消息。
步骤35：网络设备在接收到Msg3后，响应Msg3中携带的业务请求，并向终端反馈解决结果，即消息四(Msg4)。具体地，Msg4中包括波束恢复指示信息。终端根据网络设备的波束恢复指示信息，在冲突解决(如接收到网络侧指示的终端标识C-RNTI)后，根据波束恢复指示信息，采用新的波束进行数据收发，成功完成波束恢复。如果终端接收RAR失败，则根据RAR中指示的回退信息确定下次发送随机接入的时刻。具体地，终端在协议规定的预设时间段(如网络设备配置的RAR Window)内没有收到该网络设备发送的RAR，终端根据步骤22重新发送波束失败恢复请求消息，同时该SCell波束失败恢复计数器加1。
本公开实施例的波束失败处理方法中，网络设备通过配置信息指示是否为终端的SCell配置了波束失败恢复的随机接入资源，终端在检测到SCell发生波束失败时，根据配置信息的指示发起波束失败恢复流程，使终端与网络设备侧的波束失败恢复保持一致，完成SCell的波束失败恢复。
以上实施例介绍了不同场景下的波束失败处理方法，下面将结合附图对与其对应的终端做进一步介绍。
如图4所示，本公开实施例的终端400，能实现上述实施例中从网络设备侧接收用于传输波束失败恢复请求消息的随机接入资源的配置信息；在SCell发生波束失败的情况下，根据配置信息的指示，确定是否向网络设备发送波束失败恢复请求消息方法的细节，并达到相同的效果，该终端400具体包括以下功能模块：
第一接收模块410，用于从网络设备侧接收用于传输波束失败恢复请求消息的随机接入资源的配置信息，配置信息用于指示网络设备是否为辅小区SCell配置了随机接入资源；
处理模块420，用于在SCell发生波束失败的情况下，根据配置信息的指示，确定是否向网络设备发送波束失败恢复请求消息。
其中，配置信息包括以下至少一项：
随机接入资源对应的小区标识信息；
随机接入资源对应的带宽部分BWP标识信息；以及
随机接入资源对应的波束标识信息。
其中，配置信息还包括：用于传输波束恢复信息的资源位置信息。
其中，处理模块420包括：
第一处理子模块，用于在配置信息指示网络设备为SCell配置了用于波束失败恢复的随机接入资源的情况下，通过目标随机接入资源，向网络设备发送波束失败恢复请求消息。
其中，第一处理子模块包括：
第一处理单元，用于当SCell对应的随机接入资源包括：非竞争随机接入资源和竞争随机接入资源时，通过非竞争随机接入资源，向网络设备发送波束失败恢复请求消息；
或者，
第二处理单元，用于当随机接入资源同时配置在SCell和目标小区上时，通过SCell对应的第一随机接入资源，向网络设备发送波束失败恢复请求；其中，目标小区包括：主小区PCell和主辅小区PSCell中的至少一项；
或者，
第三处理单元，用于当随机接入资源同时配置在SCell和目标小区上时，检测SCell对应的第一随机接入资源是否可用，在目标随机接入资源不可用时，通过目标小区对应的第二随机接入资源，向网络设备发送波束失败恢复请求。
其中，第一随机接入资源包括：非竞争随机接入资源或竞争随机接入资源，第二随机接入资源包括：非竞争随机接入资源或竞争随机接入资源。
其中，处理模块420还包括：
第二处理子模块，用于若在预设时间段内接收到网络设备反馈的波束恢复指示信息，则通过波束恢复指示信息指示的目标波束进行数据的传输；
第三处理子模块，用于若在预设时间段内未接收到网络设备反馈的波束恢复指示信息，则向网络设备重新发送波束失败恢复请求消息，直至接收到 波束恢复指示信息或发送次数达到预设阈值。
其中，终端还包括：
触发模块，用于当发送次数达到预设阈值之后，触发SCell的波束恢复失败处理行为。
其中，处理模块还包括：
第四处理子模块，用于在配置信息指示网络设备为SCell配置了用于波束失败恢复的随机接入资源的情况下，若SCell对应的随机接入资源不可用，则确定不向网络设备发送波束失败恢复请求消息，并触发SCell的波束恢复失败处理行为；
或者，
第五处理子模块，用于在配置信息指示网络设备未为SCell配置用于波束失败恢复的随机接入资源的情况下，确定不向网络设备发送波束失败恢复请求消息，并触发SCell的波束恢复失败处理行为。
其中，波束恢复失败处理行为包括以下至少一项：
向高层指示波束恢复失败；
向底层指示波束恢复失败；
去激活SCell；
发起无线资源控制RRC连接的重建流程；
向网络设备发送SCell的波束失败信息；
停止对SCell波束失败检测对应的测量。
其中，波束失败信息包括以下至少一项：
波束失败指示信息；
波束恢复失败指示信息；
SCell的小区标识；
SCell的小区测量结果；
SCell的波束测量结果；
测量到的其他服务小区的小区测量结果；
测量到的其他服务小区对应的波束测量结果；
测量到的其他非服务小区的小区测量结果；
测量到的其他非服务小区对应的波束测量结果。
其中，其他服务小区包括：与SCell属于相同小区组的其他服务小区。
其中，波束失败恢复请求消息包括以下至少一项：
波束失败的指示信息；
发生波束失败的小区标识信息；
发生波束失败恢复的波束信息。
其中，波束信息包括：波束标识信息和波束测量信息中的至少一项。
值得指出的是，本公开实施例的终端，通过接收网络设备发送的配置信息，以确定是否为SCell配置了波束失败恢复的随机接入资源，终端在检测到SCell发生波束失败时，根据配置信息的指示发起波束失败恢复流程，使终端与网络设备侧的波束失败恢复保持一致，完成SCell的波束失败恢复。
为了更好的实现上述目的，进一步地，图5为实现本公开各个实施例的一种终端的硬件结构示意图，该终端50包括但不限于：射频单元51、网络模块52、音频输出单元53、输入单元54、传感器55、显示单元56、用户输入单元57、接口单元58、存储器59、处理器510、以及电源511等部件。本领域技术人员可以理解，图5中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。在本公开实施例中，终端包括但不限于手机、平板电脑、笔记本电脑、掌上电脑、车载终端、可穿戴设备、以及计步器等。
其中，射频单元51，用于从网络设备侧接收用于传输波束失败恢复请求消息的随机接入资源的配置信息，配置信息用于指示网络设备是否为辅小区SCell配置了随机接入资源；
处理器510，用于在SCell发生波束失败的情况下，根据配置信息的指示，确定是否向网络设备发送波束失败恢复请求消息；
本公开实施例的终端，通过接收网络设备发送的配置信息，以确定是否为SCell配置了波束失败恢复的随机接入资源，终端在检测到SCell发生波束失败时，根据配置信息的指示发起波束失败恢复流程，使终端与网络设备侧的波束失败恢复保持一致，完成SCell的波束失败恢复。
应理解的是，本公开实施例中，射频单元51可用于收发信息或通话过程 中，信号的接收和发送，具体的，将来自基站的下行数据接收后，给处理器510处理；另外，将上行的数据发送给基站。通常，射频单元51包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。此外，射频单元51还可以通过无线通信系统与网络和其他设备通信。
终端通过网络模块52为用户提供了无线的宽带互联网访问，如帮助用户收发电子邮件、浏览网页和访问流式媒体等。
音频输出单元53可以将射频单元51或网络模块52接收的或者在存储器59中存储的音频数据转换成音频信号并且输出为声音。而且，音频输出单元53还可以提供与终端50执行的特定功能相关的音频输出(例如，呼叫信号接收声音、消息接收声音等等)。音频输出单元53包括扬声器、蜂鸣器以及受话器等。
输入单元54用于接收音频或视频信号。输入单元54可以包括图形处理器(Graphics Processing Unit，GPU)541和麦克风542，图形处理器541对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。处理后的图像帧可以显示在显示单元56上。经图形处理器541处理后的图像帧可以存储在存储器59(或其它存储介质)中或者经由射频单元51或网络模块52进行发送。麦克风542可以接收声音，并且能够将这样的声音处理为音频数据。处理后的音频数据可以在电话通话模式的情况下转换为可经由射频单元51发送到移动通信基站的格式输出。
终端50还包括至少一种传感器55，比如光传感器、运动传感器以及其他传感器。具体地，光传感器包括环境光传感器及接近传感器，其中，环境光传感器可根据环境光线的明暗来调节显示面板561的亮度，接近传感器可在终端50移动到耳边时，关闭显示面板561和/或背光。作为运动传感器的一种，加速计传感器可检测各个方向上(一般为三轴)加速度的大小，静止时可检测出重力的大小及方向，可用于识别终端姿态(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等；传感器55还可以包括指纹传感器、压力传感器、虹膜传感器、分子传感器、陀螺仪、气压计、湿度计、温度计、红外线传感器等，在此不再赘述。
显示单元56用于显示由用户输入的信息或提供给用户的信息。显示单元56可包括显示面板561，可以采用液晶显示器(Liquid Crystal Display，LCD)、有机发光二极管(Organic Light-Emitting Diode，OLED)等形式来配置显示面板561。
用户输入单元57可用于接收输入的数字或字符信息，以及产生与终端的用户设置以及功能控制有关的键信号输入。具体地，用户输入单元57包括触控面板571以及其他输入设备572。触控面板571，也称为触摸屏，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板571上或在触控面板571附近的操作)。触控面板571可包括触摸检测装置和触摸控制器两个部分。其中，触摸检测装置检测用户的触摸方位，并检测触摸操作带来的信号，将信号传送给触摸控制器；触摸控制器从触摸检测装置上接收触摸信息，并将它转换成触点坐标，再送给处理器510，接收处理器510发来的命令并加以执行。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板571。除了触控面板571，用户输入单元57还可以包括其他输入设备572。具体地，其他输入设备572可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
进一步的，触控面板571可覆盖在显示面板561上，当触控面板571检测到在其上或附近的触摸操作后，传送给处理器510以确定触摸事件的类型，随后处理器510根据触摸事件的类型在显示面板561上提供相应的视觉输出。虽然在图5中，触控面板571与显示面板561是作为两个独立的部件来实现终端的输入和输出功能，但是在某些实施例中，可以将触控面板571与显示面板561集成而实现终端的输入和输出功能，具体此处不做限定。
接口单元58为外部装置与终端50连接的接口。例如，外部装置可以包括有线或无线头戴式耳机端口、外部电源(或电池充电器)端口、有线或无线数据端口、存储卡端口、用于连接具有识别模块的装置的端口、音频输入/输出(I/O)端口、视频I/O端口、耳机端口等等。接口单元58可以用于接收来自外部装置的输入(例如，数据信息、电力等等)并且将接收到的输入传输到终端50内的一个或多个元件或者可以用于在终端50和外部装置之间传输 数据。
存储器59可用于存储软件程序以及各种数据。存储器59可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据区可存储根据手机的使用所创建的数据(比如音频数据、电话本等)等。此外，存储器59可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
处理器510是终端的控制中心，利用各种接口和线路连接整个终端的各个部分，通过运行或执行存储在存储器59内的软件程序和/或模块，以及调用存储在存储器59内的数据，执行终端的各种功能和处理数据，从而对终端进行整体监控。处理器510可包括一个或多个处理单元；优选的，处理器510可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序等，调制解调处理器主要处理无线通信。可以理解的是，上述调制解调处理器也可以不集成到处理器510中。
终端50还可以包括给各个部件供电的电源511(比如电池)，优选的，电源511可以通过电源管理系统与处理器510逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
另外，终端50包括一些未示出的功能模块，在此不再赘述。
优选的，本公开实施例还提供一种终端，包括处理器510，存储器59，存储在存储器59上并可在所述处理器510上运行的计算机程序，该计算机程序被处理器510执行时实现上述波束失败处理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，终端可以是无线终端也可以是有线终端，无线终端可以是指向用户提供语音和/或其他业务数据连通性的设备，具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。无线终端可以经无线接入网(Radio Access Network，简称RAN)与一个或多个核心网进行通信，无线终端可以是移动终端，如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。例如，个人通信业务(Personal Communication  Service，简称PCS)电话、无绳电话、会话发起协议(Session Initiation Protocol，简称SIP)话机、无线本地环路(Wireless Local Loop，简称WLL)站、个人数字助理(Personal Digital Assistant，简称PDA)等设备。无线终端也可以称为系统、订户单元(Subscriber Unit)、订户站(Subscriber Station)，移动站(Mobile Station)、移动台(Mobile)、远程站(Remote Station)、远程终端(Remote Terminal)、接入终端(Access Terminal)、用户终端(User Terminal)、用户代理(User Agent)、用户设备(User Device or User Equipment)，在此不作限定。
本公开实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述波束失败处理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等。
以上实施例从终端侧介绍了本公开的波束失败处理方法，下面本实施例将结合附图对网络设备侧的波束失败处理方法做进一步介绍。
如图6所示，本公开实施例的波束失败处理方法，应用于网络设备侧，包括以下步骤：
步骤61：向终端发送用于传输波束失败恢复请求消息的随机接入资源的配置信息。
其中，配置信息用于指示是否为终端的辅小区SCell配置了随机接入资源。
其中，配置信息包括以下至少一项：
随机接入资源对应的小区标识信息；
随机接入资源对应的带宽部分BWP标识信息；以及
随机接入资源对应的波束标识信息。
其中，配置信息还包括：用于传输波束恢复信息的资源位置信息，网络设备给终端的一个或多个SCell配置用于波束失败恢复请求消息的资源。这里所说的随机接入资源包括网络设备为终端预留的、用于传输波束失败恢复 请求的PRACH资源。其中，随机接入资源可以是非竞争的随机接入资源(如dedicated PRACH-Config PRACH资源)，亦可以是竞争的随机接入资源(如common PRACH-Config配置的PRACH资源)。
步骤61之后，该方法还包括：接收终端通过目标随机接入资源发送的针对SCell的波束失败恢复请求。
其中，波束失败恢复请求消息包括以下至少一项：
波束失败的指示信息；
发生波束失败的小区标识信息，如SCell标识；
发生波束失败恢复的波束信息。
其中，波束信息包括：波束标识信息(如SSB标识、CSI-RS标识等)和波束测量信息(如RSRP、RSRQ、SINR等)中的至少一项。
接收终端通过目标随机接入资源发送的针对SCell的波束失败恢复请求的步骤之后还包括：根据波束失败恢复请求，确定是否向终端反馈波束恢复指示信息。相应地，终端若在预设时间段内接收到网络设备反馈的波束恢复指示信息，则通过波束恢复指示信息指示的目标波束进行数据的传输。若在预设时间段内未接收到网络设备反馈的波束恢复指示信息，则向网络设备重新发送波束失败恢复请求消息，直至接收到波束恢复指示信息或发送次数达到预设阈值。若波束失败恢复请求消息发送次数达到预设阈值后，仍未收到网络设备发送的波束恢复指示信息，这时终端确定SCell波束恢复失败，自动触发SCell的波束恢复失败处理行为。
步骤61之后，还包括：从终端侧接收SCell的波束失败信息。其中，终端的高层(如RRC层)上报该SCell的波束失败信息给网络设备。
其中，波束失败信息包括以下至少一项：
波束失败指示信息；
波束恢复失败指示信息；
SCell的小区标识；
SCell的小区测量结果；
SCell的波束测量结果；
测量到的其他服务小区的小区测量结果；
测量到的其他服务小区对应的波束测量结果；
测量到的其他非服务小区的小区测量结果；
测量到的其他非服务小区对应的波束测量结果。
其中，其他服务小区包括：与SCell属于相同小区组的其他服务小区。
本公开实施例的波束失败处理方法中，网络设备通过配置信息指示是否为终端的SCell配置了波束失败恢复的随机接入资源，终端在检测到SCell发生波束失败时，根据配置信息的指示发起波束失败恢复流程，使终端与网络设备侧的波束失败恢复保持一致，完成SCell的波束失败恢复。
以上实施例分别详细介绍了不同场景下的波束失败处理方法，下面本实施例将结合附图对其对应的网络设备做进一步介绍。
如图7所示，本公开实施例的网络设备600，能实现上述实施例中向终端发送用于传输波束失败恢复请求消息的随机接入资源的配置信息，方法的细节，并达到相同的效果，其中，配置信息用于指示是否为终端的辅小区SCell配置了随机接入资源。该网络设备600具体包括以下功能模块：
第一发送模块，用于向终端发送用于传输波束失败恢复请求消息的随机接入资源的配置信息，配置信息用于指示是否为终端的辅小区SCell配置了随机接入资源。
其中，配置信息包括以下至少一项：
随机接入资源对应的小区标识信息；
随机接入资源对应的带宽部分BWP标识信息；以及
随机接入资源对应的波束标识信息。
其中，配置信息还包括：用于传输波束恢复信息的资源位置信息。
其中，向终端发送用于传输波束失败恢复请求消息的随机接入资源的配置信息的步骤之后，还包括：
接收终端通过目标随机接入资源发送的针对SCell的波束失败恢复请求。
其中，接收终端通过目标随机接入资源发送的针对SCell的波束失败恢复请求的步骤之后，还包括：
根据波束失败恢复请求，确定是否向终端反馈波束恢复指示信息。
其中，向终端发送用于传输波束失败恢复请求消息的随机接入资源的配 置信息的步骤之后，还包括：
从终端侧接收SCell的波束失败信息。
其中，波束失败信息包括以下至少一项：
波束失败指示信息；
波束恢复失败指示信息；
SCell的小区标识；
SCell的小区测量结果；
SCell的波束测量结果；
测量到的其他服务小区的小区测量结果；
测量到的其他服务小区对应的波束测量结果；
测量到的其他非服务小区的小区测量结果；
测量到的其他非服务小区对应的波束测量结果。
其中，其他服务小区包括：与SCell属于相同小区组的其他服务小区。
其中，波束失败恢复请求消息包括以下至少一项：
波束失败的指示信息；
发生波束失败的小区标识信息；
发生波束失败恢复的波束信息。
其中，波束信息包括：波束标识信息和波束测量信息中的至少一项。
需要说明的是，应理解以上网络设备和终端的各个模块的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且这些模块可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分模块通过处理元件调用软件的形式实现，部分模块通过硬件的形式实现。例如，确定模块可以为单独设立的处理元件，也可以集成在上述装置的某一个芯片中实现，此外，也可以以程序代码的形式存储于上述装置的存储器中，由上述装置的某一个处理元件调用并执行以上确定模块的功能。其它模块的实现与之类似。此外这些模块全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件可以是一种集成电路，具有信号的处理能力。在实现过程中，上述方法的各步骤或以上各个模块可以通过处理器元件中的硬件的集成逻辑电路或者软件形式的指 令完成。
例如，以上这些模块可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(Application Specific Integrated Circuit，简称ASIC)，或，一个或多个微处理器(digital signal processor，简称DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，简称FPGA)等。再如，当以上某个模块通过处理元件调度程序代码的形式实现时，该处理元件可以是通用处理器，例如中央处理器(Central Processing Unit，简称CPU)或其它可以调用程序代码的处理器。再如，这些模块可以集成在一起，以片上系统(system-on-a-chip，简称SOC)的形式实现。
值得指出的是，本公开实施例的网络设备通过配置信息指示是否为终端的SCell配置了波束失败恢复的随机接入资源，终端在检测到SCell发生波束失败时，根据配置信息的指示发起波束失败恢复流程，使终端与网络设备侧的波束失败恢复保持一致，完成SCell的波束失败恢复。
为了更好的实现上述目的，本公开的实施例还提供了一种网络设备，该网络设备包括处理器、存储器以及存储于存储器上并可在处理器上运行的计算机程序，处理器执行计算机程序时实现如上所述的波束失败处理方法中的步骤。发明实施例还提供了一种计算机可读存储介质，该计算机可读存储介质上存储有计算机程序，计算机程序被处理器执行时实现如上所述的波束失败处理方法的步骤。
具体地，本公开的实施例还提供了一种网络设备。如图8所示，该网络设备800包括：天线81、射频装置82、基带装置83。天线81与射频装置82连接。在上行方向上，射频装置82通过天线81接收信息，将接收的信息发送给基带装置83进行处理。在下行方向上，基带装置83对要发送的信息进行处理，并发送给射频装置82，射频装置82对收到的信息进行处理后经过天线81发送出去。
上述频带处理装置可以位于基带装置83中，以上实施例中网络设备执行的方法可以在基带装置83中实现，该基带装置83包括处理器84和存储器85。
基带装置83例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图8所示，其中一个芯片例如为处理器84，与存储器85连接，以调用存储器85中的程序，执行以上方法实施例中所示的网络设备操作。
该基带装置83还可以包括网络接口86，用于与射频装置82交互信息，该接口例如为通用公共无线接口(common public radio interface，简称CPRI)。
这里的处理器可以是一个处理器，也可以是多个处理元件的统称，例如，该处理器可以是CPU，也可以是ASIC，或者是被配置成实施以上网络设备所执行方法的一个或多个集成电路，例如：一个或多个微处理器DSP，或，一个或者多个现场可编程门阵列FPGA等。存储元件可以是一个存储器，也可以是多个存储元件的统称。
存储器85可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，简称ROM)、可编程只读存储器(Programmable ROM，简称PROM)、可擦除可编程只读存储器(Erasable PROM，简称EPROM)、电可擦除可编程只读存储器(Electrically EPROM，简称EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，简称RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，简称SRAM)、动态随机存取存储器(Dynamic RAM，简称DRAM)、同步动态随机存取存储器(Synchronous DRAM，简称SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，简称DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，简称ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，简称SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，简称DRRAM)。本申请描述的存储器85旨在包括但不限于这些和任意其它适合类型的存储器。
具体地，本公开实施例的网络设备还包括：存储在存储器85上并可在处理器84上运行的计算机程序，处理器84调用存储器85中的计算机程序执行图7所示各模块执行的方法。
具体地，计算机程序被处理器84调用时可用于执行：向终端发送用于传 输波束失败恢复请求消息的随机接入资源的配置信息，配置信息用于指示是否为终端的辅小区SCell配置了随机接入资源。
其中，配置信息包括以下至少一项：
随机接入资源对应的小区标识信息；
随机接入资源对应的带宽部分BWP标识信息；以及
随机接入资源对应的波束标识信息。
其中，配置信息还包括：用于传输波束恢复信息的资源位置信息。
具体地，计算机程序被处理器84调用时可用于执行：接收终端通过目标随机接入资源发送的针对SCell的波束失败恢复请求。
具体地，计算机程序被处理器84调用时可用于执行：根据波束失败恢复请求，确定是否向终端反馈波束恢复指示信息。
具体地，计算机程序被处理器84调用时可用于执行：从终端侧接收SCell的波束失败信息。
其中，波束失败信息包括以下至少一项：
波束失败指示信息；
波束恢复失败指示信息；
SCell的小区标识；
SCell的小区测量结果；
SCell的波束测量结果；
测量到的其他服务小区的小区测量结果；
测量到的其他服务小区对应的波束测量结果；
测量到的其他非服务小区的小区测量结果；
测量到的其他非服务小区对应的波束测量结果。
其中，其他服务小区包括：与SCell属于相同小区组的其他服务小区。
其中，波束失败恢复请求消息包括以下至少一项：
波束失败的指示信息；
发生波束失败的小区标识信息；
发生波束失败恢复的波束信息。
其中，波束信息包括：波束标识信息和波束测量信息中的至少一项。
其中，网络设备可以是全球移动通讯(Global System of Mobile communication，简称GSM)或码分多址(Code Division Multiple Access，简称CDMA)中的基站(Base Transceiver Station，简称BTS)，也可以是宽带码分多址(Wideband Code Division Multiple Access，简称WCDMA)中的基站(NodeB，简称NB)，还可以是LTE中的演进型基站(Evolutional Node B，简称eNB或eNodeB)，或者中继站或接入点，或者未来5G网络中的基站等，在此并不限定。
本公开实施例中的网络设备，通过配置信息指示是否为终端的SCell配置了波束失败恢复的随机接入资源，终端在检测到SCell发生波束失败时，根据配置信息的指示发起波束失败恢复流程，使终端与网络设备侧的波束失败恢复保持一致，完成SCell的波束失败恢复。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或 者全部单元来实现本实施例方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
此外，需要指出的是，在本公开的装置和方法中，显然，各部件或各步骤是可以分解和/或重新组合的。这些分解和/或重新组合应视为本公开的等效方案。并且，执行上述系列处理的步骤可以自然地按照说明的顺序按时间顺序执行，但是并不需要一定按照时间顺序执行，某些步骤可以并行或彼此独立地执行。对本领域的普通技术人员而言，能够理解本公开的方法和装置的全部或者任何步骤或者部件，可以在任何计算装置(包括处理器、存储介质等)或者计算装置的网络中，以硬件、固件、软件或者它们的组合加以实现，这是本领域普通技术人员在阅读了本公开的说明的情况下运用他们的基本编程技能就能实现的。
因此，本公开的目的还可以通过在任何计算装置上运行一个程序或者一组程序来实现。所述计算装置可以是公知的通用装置。因此，本公开的目的也可以仅仅通过提供包含实现所述方法或者装置的程序代码的程序产品来实现。也就是说，这样的程序产品也构成本公开，并且存储有这样的程序产品的存储介质也构成本公开。显然，所述存储介质可以是任何公知的存储介质或者将来所开发出来的任何存储介质。还需要指出的是，在本公开的装置和方法中，显然，各部件或各步骤是可以分解和/或重新组合的。这些分解和/或重新组合应视为本公开的等效方案。并且，执行上述系列处理的步骤可以 自然地按照说明的顺序按时间顺序执行，但是并不需要一定按照时间顺序执行。某些步骤可以并行或彼此独立地执行。
以上所述的是本公开的优选实施方式，应当指出对于本技术领域的普通人员来说，在不脱离本公开所述的原理前提下还可以作出若干改进和润饰，这些改进和润饰也在本公开的保护范围内。

Claims (27)

  1. 一种波束失败处理方法，应用于终端侧，包括：
    从网络设备侧接收用于传输波束失败恢复请求消息的随机接入资源的配置信息，所述配置信息用于指示所述网络设备是否为辅小区SCell配置了所述随机接入资源；
    在所述SCell发生波束失败的情况下，根据所述配置信息的指示，确定是否向所述网络设备发送波束失败恢复请求消息。
  2. 根据权利要求1所述的波束失败处理方法，其中，根据所述配置信息的指示，确定是否向所述网络设备发送波束失败恢复请求消息的步骤，包括：
    在所述配置信息指示所述网络设备为SCell配置了用于波束失败恢复的随机接入资源的情况下，通过目标随机接入资源，向所述网络设备发送波束失败恢复请求消息。
  3. 根据权利要求2所述的波束失败处理方法，其中，通过目标随机接入资源，向所述网络设备发送波束失败恢复请求消息的步骤，包括：
    当所述SCell对应的随机接入资源包括：非竞争随机接入资源和竞争随机接入资源时，通过非竞争随机接入资源，向所述网络设备发送波束失败恢复请求消息；
    或者，
    当随机接入资源同时配置在所述SCell和目标小区上时，通过所述SCell对应的第一随机接入资源，向所述网络设备发送波束失败恢复请求；其中，所述目标小区包括：主小区PCell和主辅小区PSCell中的至少一项；
    或者，
    当随机接入资源同时配置在所述SCell和所述目标小区上时，检测所述SCell对应的第一随机接入资源是否可用，在所述目标随机接入资源不可用时，通过所述目标小区对应的第二随机接入资源，向所述网络设备发送波束失败恢复请求。
  4. 根据权利要求3所述的波束失败处理方法，其中，所述第一随机接入资源包括：非竞争随机接入资源或竞争随机接入资源，所述第二随机接入资 源包括：非竞争随机接入资源或竞争随机接入资源。
  5. 根据权利要求2所述的波束失败处理方法，其中，通过目标随机接入资源，向所述网络设备发送波束失败恢复请求消息的步骤之后，还包括：
    若在预设时间段内接收到网络设备反馈的波束恢复指示信息，则通过所述波束恢复指示信息对应的目标波束进行数据的收发；
    若在所述预设时间段内未接收到网络设备反馈的所述波束恢复指示信息，则向所述网络设备重新发送所述波束失败恢复请求消息，直至接收到所述波束恢复指示信息或发送次数达到预设阈值。
  6. 根据权利要求5所述的波束失败处理方法，其中，当发送次数达到预设阈值之后，所述波束失败处理方法还包括：
    触发所述SCell的波束恢复失败处理行为。
  7. 根据权利要求1所述的波束失败处理方法，其中，根据所述配置信息的指示，确定是否向所述网络设备发送波束失败恢复请求消息的步骤，包括：
    在所述配置信息指示所述网络设备为SCell配置了用于波束失败恢复的随机接入资源的情况下，若所述SCell对应的随机接入资源不可用，则确定不向所述网络设备发送波束失败恢复请求消息，并触发所述SCell的波束恢复失败处理行为；
    或者，
    在所述配置信息指示所述网络设备未为SCell配置用于波束失败恢复的随机接入资源的情况下，确定不向所述网络设备发送波束失败恢复请求消息，并触发所述SCell的波束恢复失败处理行为。
  8. 根据权利要求6或7所述的波束失败处理方法，其中，所述波束恢复失败处理行为包括以下至少一项：
    向高层指示波束恢复失败；
    向底层指示波束恢复失败；
    去激活所述SCell；
    发起无线资源控制RRC连接的重建流程；
    向所述网络设备发送所述SCell的波束失败信息；
    停止对所述SCell波束失败检测对应的测量。
  9. 根据权利要求8所述的波束失败处理方法，其中，所述波束失败信息包括以下至少一项：
    波束失败指示信息；
    波束恢复失败指示信息；
    所述SCell的小区标识；
    所述SCell的小区测量结果；
    所述SCell的波束测量结果；
    测量到的其他服务小区的小区测量结果；
    测量到的所述其他服务小区对应的波束测量结果；
    测量到的其他非服务小区的小区测量结果；
    测量到的其他非服务小区对应的波束测量结果。
  10. 根据权利要求9所述的波束失败处理方法，其中，其他服务小区包括：与所述SCell属于相同小区组的其他服务小区。
  11. 根据权利要求1所述的波束失败处理方法，其中，所述配置信息包括以下至少一项：
    所述随机接入资源对应的小区标识信息；
    所述随机接入资源对应的带宽部分BWP标识信息；
    所述随机接入资源对应的波束标识信息；以及
    用于传输波束恢复信息的资源位置信息。
  12. 根据权利要求1所述的波束失败处理方法，其中，所述波束失败恢复请求消息包括以下至少一项：
    波束失败的指示信息；
    发生波束失败的小区标识信息；
    发生波束失败恢复的波束信息。
  13. 根据权利要求12所述的波束失败处理方法，其中，所述波束信息包括：波束标识信息和波束测量信息中的至少一项。
  14. 一种终端，包括：
    第一接收模块，用于从网络设备侧接收用于传输波束失败恢复请求消息的随机接入资源的配置信息，所述配置信息用于指示所述网络设备是否为辅 小区SCell配置了所述随机接入资源；
    处理模块，用于在所述SCell发生波束失败的情况下，根据所述配置信息的指示，确定是否向所述网络设备发送波束失败恢复请求消息。
  15. 一种终端，包括处理器、存储器以及存储于所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至13中任一项所述的波束失败处理方法的步骤。
  16. 一种波束失败处理方法，应用于网络设备侧，包括：
    向终端发送用于传输波束失败恢复请求消息的随机接入资源的配置信息，所述配置信息用于指示是否为所述终端的辅小区SCell配置了所述随机接入资源。
  17. 根据权利要求16所述的波束失败处理方法，其中，向终端发送用于传输波束失败恢复请求消息的随机接入资源的配置信息的步骤之后，还包括：
    接收所述终端通过目标随机接入资源发送的针对所述SCell的波束失败恢复请求。
  18. 根据权利要求17所述的波束失败处理方法，其中，接收所述终端通过目标随机接入资源发送的针对所述SCell的波束失败恢复请求的步骤之后，还包括：
    根据所述波束失败恢复请求，确定是否向所述终端反馈波束恢复指示信息。
  19. 根据权利要求16所述的波束失败处理方法，其中，向终端发送用于传输波束失败恢复请求消息的随机接入资源的配置信息的步骤之后，还包括：
    从所述终端侧接收所述SCell的波束失败信息。
  20. 根据权利要求19所述的波束失败处理方法，其中，所述波束失败信息包括以下至少一项：
    波束失败指示信息；
    波束恢复失败指示信息；
    所述SCell的小区标识；
    所述SCell的小区测量结果；
    所述SCell的波束测量结果；
    测量到的其他服务小区的小区测量结果；
    测量到的所述其他服务小区对应的波束测量结果；
    测量到的其他非服务小区的小区测量结果；
    测量到的其他非服务小区对应的波束测量结果。
  21. 根据权利要求20所述的波束失败处理方法，其中，其他服务小区包括：与所述SCell属于相同小区组的其他服务小区。
  22. 根据权利要求16所述的波束失败处理方法，其中，所述配置信息包括以下至少一项：
    所述随机接入资源对应的小区标识信息；
    所述随机接入资源对应的带宽部分BWP标识信息；
    所述随机接入资源对应的波束标识信息；以及
    用于传输波束恢复信息的资源位置信息。
  23. 根据权利要求16所述的波束失败处理方法，其中，所述波束失败恢复请求消息包括以下至少一项：
    波束失败的指示信息；
    发生波束失败的小区标识信息；
    发生波束失败恢复的波束信息。
  24. 根据权利要求23所述的波束失败处理方法，其中，所述波束信息包括：波束标识信息和波束测量信息中的至少一项。
  25. 一种网络设备，包括：
    第一发送模块，用于向终端发送用于传输波束失败恢复请求消息的随机接入资源的配置信息，所述配置信息用于指示是否为所述终端的辅小区SCell配置了所述随机接入资源。
  26. 一种网络设备，包括处理器、存储器以及存储于所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如权利要求16至24任一项所述的波束失败处理方法的步骤。
  27. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至13、16至24中任一项所述的波束失败处理方法的步骤。
PCT/CN2019/078116 2018-03-28 2019-03-14 波束失败处理方法、终端及网络设备 WO2019184716A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/035,213 US20210058285A1 (en) 2018-03-28 2020-09-28 Beam failure processing method, terminal, and network device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810266184.4A CN110324908B (zh) 2018-03-28 2018-03-28 波束失败处理方法、终端及网络设备
CN201810266184.4 2018-03-28

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/035,213 Continuation US20210058285A1 (en) 2018-03-28 2020-09-28 Beam failure processing method, terminal, and network device

Publications (1)

Publication Number Publication Date
WO2019184716A1 true WO2019184716A1 (zh) 2019-10-03

Family

ID=68060908

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/078116 WO2019184716A1 (zh) 2018-03-28 2019-03-14 波束失败处理方法、终端及网络设备

Country Status (3)

Country Link
US (1) US20210058285A1 (zh)
CN (1) CN110324908B (zh)
WO (1) WO2019184716A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112788642A (zh) * 2019-11-07 2021-05-11 联发科技股份有限公司 一种波束故障恢复方法及用户设备
CN115190473A (zh) * 2021-04-02 2022-10-14 大唐移动通信设备有限公司 一种去激活辅节点sn波束失败的处理方法及装置
RU2791059C1 (ru) * 2019-11-05 2023-03-02 Бейдзин Сяоми Мобайл Софтвэр Ко., Лтд. Способ и устройство для выделения ресурсов для запроса при отказе луча

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112640347B (zh) * 2018-09-14 2023-04-28 Oppo广东移动通信有限公司 无线通信的方法、终端设备和网络设备
WO2020088771A1 (en) * 2018-11-01 2020-05-07 Nokia Technologies Oy Apparatus, method and computer program
US11245510B2 (en) * 2019-05-02 2022-02-08 Ofinno, Llc Beam failure recovery procedure for bandwidth parts
WO2021087786A1 (zh) * 2019-11-05 2021-05-14 北京小米移动软件有限公司 波束失败请求资源分配方法、装置及存储介质
CN112788772B (zh) * 2019-11-07 2023-05-26 维沃移动通信有限公司 波束失败恢复的确认方法、终端设备及存储介质
US11696333B2 (en) * 2019-12-20 2023-07-04 Qualcomm Incorporated Beam sweep based random access msg 1 and msg 2
CN113225839B (zh) * 2020-01-21 2023-06-30 维沃移动通信有限公司 一种无线链路恢复方法及设备
KR20220127288A (ko) * 2020-02-12 2022-09-19 애플 인크. 업링크 리슨-비포-토크 실패 보고
WO2021164030A1 (en) 2020-02-21 2021-08-26 Nokia Shanghai Bell Co., Ltd. Beam failure recovery mechanism
CN115642939A (zh) * 2020-03-25 2023-01-24 华为技术有限公司 信号传输方法及装置
US11743742B2 (en) 2020-03-31 2023-08-29 Qualcomm Incorporated Beam sweep based random access msg 3 and msg 4
CN113709823B (zh) * 2020-05-21 2023-03-31 维沃移动通信有限公司 检测失败处理方法、装置及终端
CN115136538B (zh) * 2022-05-23 2024-02-09 北京小米移动软件有限公司 多prach传输配置方法、装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018017840A1 (en) * 2016-07-20 2018-01-25 Convida Wireless, Llc Mobility for radio devices using beamforming and selection

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111492684B (zh) * 2017-11-02 2023-10-24 株式会社Ntt都科摩 用户终端以及无线通信方法
CN111758276B (zh) * 2017-12-27 2024-03-01 株式会社Ntt都科摩 用户终端以及无线通信方法
CN111837346B (zh) * 2018-03-16 2023-03-21 联想(北京)有限公司 波束故障恢复

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018017840A1 (en) * 2016-07-20 2018-01-25 Convida Wireless, Llc Mobility for radio devices using beamforming and selection

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LENOVO: "Dedicated PRACH Resource for Beam Failure Recovery", 3GPP TSG-RAN WG2 MEETING#101 R2-1803060, 2 March 2018 (2018-03-02), XP051399666 *
VIVO: "Discussion on Beam Failure Recovery Procedure", 3GPP TSG RAN WG1 NR AD HOC #3 R1-1715620, 21 September 2017 (2017-09-21), XP051339087 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU2791059C1 (ru) * 2019-11-05 2023-03-02 Бейдзин Сяоми Мобайл Софтвэр Ко., Лтд. Способ и устройство для выделения ресурсов для запроса при отказе луча
CN112788642A (zh) * 2019-11-07 2021-05-11 联发科技股份有限公司 一种波束故障恢复方法及用户设备
CN112788642B (zh) * 2019-11-07 2024-02-27 联发科技股份有限公司 一种波束故障恢复方法及用户设备
CN115190473A (zh) * 2021-04-02 2022-10-14 大唐移动通信设备有限公司 一种去激活辅节点sn波束失败的处理方法及装置

Also Published As

Publication number Publication date
CN110324908B (zh) 2022-08-02
CN110324908A (zh) 2019-10-11
US20210058285A1 (en) 2021-02-25

Similar Documents

Publication Publication Date Title
WO2019184716A1 (zh) 波束失败处理方法、终端及网络设备
WO2020020212A1 (zh) 随机接入方法、终端及网络设备
WO2020151472A1 (zh) 波束失败恢复方法、处理方法、终端及网络侧设备
WO2019184692A1 (zh) 波束失败处理方法、终端及网络设备
US11343855B2 (en) Method and device for random access and terminal
WO2020151743A1 (zh) 随机接入方法及终端
WO2019137276A1 (zh) 通信业务过程冲突的处理方法及终端
US20210250991A1 (en) Random access resource determining method, terminal, and network device
US11606831B2 (en) Radio link recovery method and terminal
WO2019192472A1 (zh) 信道传输方法、终端及网络设备
WO2019214664A1 (zh) 传输资源指示方法、网络设备及终端
WO2019134659A1 (zh) 信息传输方法、终端及网络设备
WO2019214663A1 (zh) 准共址配置方法、终端及网络设备
WO2019076171A1 (zh) 非授权频段下的信息传输方法、终端及网络设备
WO2019174446A1 (zh) 测量方法、测量配置方法、终端及网络设备
WO2019192473A1 (zh) 波束失败恢复方法、终端及网络设备
WO2019076169A1 (zh) 同步信号块的处理方法、同步信号块的指示方法及装置
KR20210036956A (ko) 재구성 방법 및 단말
EP3706486B1 (en) Random access method and user terminal
WO2019080656A1 (zh) 丢包率计算方法、网络设备及终端
US20220272585A1 (en) Method for reporting state information, terminal, and network device
WO2019076170A1 (zh) 非授权频段下的信息传输方法、网络设备及终端
US20230300897A1 (en) Random access method, terminal, and network device
WO2019141182A1 (zh) 波束失败恢复方法及终端
JP7210755B2 (ja) ランダムアクセス方法及び機器

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: 19777490

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: 19777490

Country of ref document: EP

Kind code of ref document: A1