Method and device for determining uplink resources

By determining the target resources from multiple uplink carriers, and preferring non-contested random access resources for beam failure recovery request message transmission, the problem of determining beam failure recovery resource under multiple uplink carriers of terminal devices is solved, and the efficiency of beam failure recovery is improved. Success rate.

CN119095157APending Publication Date: 2024-12-06CHENGDU HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411347154.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2018-08-22
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In the case where the terminal device has multiple uplink carriers, the prior art fails to effectively determine the resources for beam failure recovery, resulting in low beam failure recovery efficiency.

Method used

By determining the target uplink resource from multiple uplink carriers, the non-contested random access resource is preferred as the transmission resource of the beam failure recovery request message, and the efficiency and success rate of beam failure recovery are improved.

Benefits of technology

By prioritizing non-contested random access resources, the delay of beam failure recovery is reduced, the efficiency and success rate of beam failure recovery is improved, and the delay of data transmission recovery is reduced.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119095157A_ABST
    Figure CN119095157A_ABST
Patent Text Reader

Abstract

The invention provides a method and a device for determining an uplink resource. The method comprises the following steps: determining a target uplink resource from resources on a plurality of uplink carriers; and sending a beam failure recovery request message to the network device by using the target uplink resource. According to the embodiment of the invention, the terminal equipment can determine the resources for beam failure recovery from a plurality of uplink carriers under the condition that the terminal equipment has the plurality of uplink carriers, so as to expect to improve the beam failure recovery efficiency.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application. The application number of the original application is 201810960888.1, and the original application date is August 22, 2018. The entire contents of the original application are incorporated into this application by reference. Technical Field

[0002] The present application relates to the field of communications, and in particular, to a method and device for determining uplink resources. Background Art

[0003] Generally, a cell consists of a downlink carrier and an uplink carrier. When a terminal device performs uplink transmission, it selects resources for uplink transmission from resources on an uplink carrier.

[0004] In some scenarios, the terminal device has multiple uplink carriers for uplink transmission. For example, when deploying high-frequency cells, due to the high operating frequency band and the low transmit power of the terminal device, the terminal device in the edge area of ​​the cell can receive the signal from the network device, but the network device cannot receive the signal from the terminal device. To address this problem, the new radio (NR) system introduces a supplementary uplink (SUL) carrier to assist the terminal device in uplink transmission. That is, in a cell that supports the SUL carrier, the terminal device can have two spectrum segments for uplink transmission, one spectrum segment can be called the NR uplink (NR uplink, NUL) carrier, and the other spectrum segment can be called the SUL carrier.

[0005] Currently, there is no solution for determining resources for uplink transmission when a terminal device has multiple uplink carriers. For example, there is no solution for determining resources for beam failure recovery (BFR) when a terminal device has multiple uplink carriers. Summary of the invention

[0006] The present application provides a method and apparatus for determining uplink resources, which can enable a terminal device to determine resources for uplink transmission from multiple uplink carriers when having multiple uplink carriers, for example, determine resources for BFR to improve the efficiency of BFR.

[0007] In a first aspect, a method for determining uplink resources is provided, the method being executed by a terminal device or a chip for a terminal device. The method comprises: determining a target uplink resource from resources on multiple uplink carriers; and using the target uplink resource to send a beam failure recovery request (BFRQ) message to a network device.

[0008] Multiple uplink carriers are configured with resources for beam failure recovery (BFR) of the current cell, that is, resources for sending BFRQ messages. The current cell represents a cell where beam failure occurs. The uplink resources used for BFR may be random access channel (RACH) resources.

[0009] The target uplink resource is a resource used for BFR on one uplink carrier among the multiple uplink carriers.

[0010] The present application determines a target uplink resource for sending a beam failure recovery request message when there are multiple uplink carriers for beam failure recovery, in the hope of improving the efficiency of beam failure recovery.

[0011] Optionally, the resources for BFR on multiple uplink carriers may be preconfigured by the network device. For example, the network device may preconfigure the resources for BFR on multiple uplink carriers for the terminal device through radio resource control (RRC) signaling. The network device may also preconfigure the resources for BFR on multiple uplink carriers through other downlink signaling, which is not limited in this application.

[0012] Optionally, multiple uplink carriers may all be low-frequency carriers, or may all be high-frequency carriers, or some of them may be high-frequency carriers and the other may be low-frequency carriers. The "high frequency" and "low frequency" mentioned in this document are relative concepts and have no strict limiting meanings. For example, a low-frequency carrier may refer to a carrier operating below 6 GHz, and a high-frequency carrier may refer to a carrier operating at 6 GHz and above. For another example, in future evolving technologies, high-frequency carriers and low-frequency carriers may have new definitions.

[0013] In the scenario where the current cell includes a primary uplink carrier and a supplementary uplink carrier, the multiple uplink carriers include the primary uplink carrier and the supplementary uplink carrier. For example, in the scenario where the cell supports SUL technology, the primary uplink carrier is a NUL carrier and the supplementary uplink carrier is a SUL carrier.

[0014] In the scenario of carrier aggregation, the current cell is the primary cell. In the case where the uplink carrier of the secondary cell is allowed to be used for BFR of the primary cell, the multiple uplink carriers may include the uplink carrier of the primary cell and the uplink carrier of the secondary cell. If the primary cell supports SUL technology, the multiple uplink carriers may include the NUL carrier and SUL carrier of the primary cell, and the uplink carrier of the secondary cell. If the secondary cell also supports SUL technology, the multiple uplink carriers may include the NUL carrier and SUL carrier of the primary cell, and the NUL carrier and SUL carrier of the secondary cell.

[0015] Non-contention resources and / or contention resources may be configured on multiple uplink carriers, wherein the non-contention resources used for BFR may be contention-free RACH resources, and the contention resources used for BFR may be contention-based RACH resources.

[0016] Optionally, multiple uplink carriers may also be configured with resources for sending uplink scheduling requests (SR), preconfigured semi-static or unlicensed uplink resources, physical uplink control channel (PUCCH) resources or other uplink resources. Multiple uplink carriers may also be configured with other non-competitive resources other than non-competitive random access resources, and / or may also be configured with other competitive resources other than competitive random access resources.

[0017] In the present application, there are multiple implementations for determining the target uplink resource from resources on multiple uplink carriers.

[0018] In combination with the first aspect, in a possible implementation method of the first aspect, the target uplink resource is determined from the resources on multiple uplink carriers, including: when at least one uplink carrier among the multiple uplink carriers has non-competitive resources, the non-competitive resources on an uplink carrier Y among the at least one uplink carrier are determined as the target uplink resource.

[0019] In a scenario where the current cell supports the SUL technology, the uplink carrier Y may be a NUL carrier or a SUL carrier.

[0020] In the carrier aggregation scenario, the uplink carrier Y may be an uplink carrier of the primary cell or an uplink carrier of the secondary cell.

[0021] In this implementation, non-contention random access resources are preferentially selected as target uplink resources. In the process of selecting target uplink resources from multiple uplink carriers, it is preferentially determined whether there are available non-contention random access resources on multiple uplink carriers. If so, the non-contention random access resources on one of the uplink carriers are used as the target uplink resources. If not, a contention random access resource on one uplink carrier is selected as the target uplink resource.

[0022] It should be understood that when a terminal device initiates random access using non-competitive random access resources, no conflict (collision) will occur and no conflict resolution is required. Therefore, compared with using competitive random access resources to initiate random access, using non-competitive random access resources to initiate random access, the terminal device has a smaller access delay and a higher access success rate. Therefore, the present application can improve the efficiency and success rate of beam failure recovery by preferentially selecting non-competitive random access resources from multiple uplink carriers to send a beam failure recovery request message.

[0023] In combination with the first aspect, in a possible implementation of the first aspect, the multiple uplink carriers include a main uplink carrier and a supplementary uplink carrier of the current cell; a non-competitive resource on an uplink carrier in at least one uplink carrier is determined as a target uplink resource, including: when at least one uplink carrier includes a main uplink carrier, the non-competitive resource on the main uplink carrier is determined as the target uplink resource.

[0024] In this implementation, non-contention random access resources on the primary uplink carrier are preferentially selected as target uplink resources.

[0025] In combination with the first aspect, in a possible implementation of the first aspect, the multiple uplink carriers include a NUL carrier and a SUL carrier; determining the target uplink resource from the multiple uplink carriers includes: preferentially selecting a non-competitive random access resource on the NUL carrier as the target uplink resource.

[0026] In the process of selecting a target uplink resource from multiple uplink carriers, it can be preferentially determined whether there are available non-competitive random access resources on the NUL carrier. If so, the non-competitive random access resources on the NUL carrier are used as the target uplink resources. If not, the competitive random access resources on the NUL carrier or the random access resources on the SUL carrier are used as the target uplink resources.

[0027] Furthermore, if there are no available non-contention random access resources on the NUL carrier, it is prioritized to determine whether there are non-contention random access resources on the SUL carrier. If so, the non-contention random access resources on the SUL carrier are used as target uplink resources. If not, the contention random access resources on the SUL carrier or the contention random access resources on the NUL carrier are used as target uplink resources.

[0028] It should be understood that since the NUL carrier may operate in a high-frequency frequency band, it can use a larger subcarrier interval defined by the protocol for transmission, and the corresponding time for each symbol (absolute time) is shorter. Therefore, compared with the SUL carrier, the configuration of random access resources on the NUL carrier can be more dense, which can enable terminal devices to have more opportunities to use resources in a relatively short period of time. Therefore, giving priority to non-competitive random access resources on the NUL carrier can reduce transmission delays.

[0029] Therefore, in the present application, when the terminal device has multiple uplink carriers, the non-competitive random access resources on the NUL carrier among the multiple uplink carriers are preferentially selected to send the BFRQ message, which can reduce the BFR delay and thus effectively improve the BFR efficiency.

[0030] In addition, the total number of non-competitive random access resources on the NUL carrier is relatively large, and the associated non-competitive random access resources can be configured for the downlink narrow beam (such as CSI-RS), so that the terminal device does not need to re-perform beam scanning and beam training after completing BFR, so that the terminal device can experience a relatively shorter data transmission recovery delay. Therefore, giving priority to non-competitive random access resources on the NUL carrier can reduce the delay of BFR, thereby improving the efficiency of BFR.

[0031] In combination with the first aspect, in a possible implementation of the first aspect, the multiple uplink carriers include a main uplink carrier and a supplementary uplink carrier of the current cell; a non-competitive resource on an uplink carrier in at least one uplink carrier is determined as a target uplink resource, including: when at least one uplink carrier includes a supplementary uplink carrier, the non-competitive resource on the supplementary uplink carrier is determined as the target uplink resource.

[0032] In this implementation, non-contention random access resources on the supplementary uplink carrier are preferentially selected as target uplink resources.

[0033] In combination with the first aspect, in a possible implementation of the first aspect, the multiple uplink carriers include a NUL carrier and a SUL carrier; determining the target uplink resource from the multiple uplink carriers includes: preferentially selecting a non-competitive random access resource on the SUL carrier as the target uplink resource.

[0034] In the process of selecting a target uplink resource from multiple uplink carriers, it can be preferentially determined whether there are available non-contention random access resources on the SUL carrier. If so, the non-contention random access resources on the SUL carrier are used as the target uplink resources. If not, the contention random access resources on the SUL carrier or the random access resources on the NUL carrier are used as the target uplink resources.

[0035] As an implementation method, if there are no available non-competitive random access resources on the SUL carrier, it is prioritized to determine whether there are competitive random access resources on the SUL carrier. If so, the competitive random access resources on the SUL carrier are used as target uplink resources. If not, the competitive random access resources on the NUL carrier are used (non-competitive random access resources are prioritized) as target uplink resources.

[0036] As another implementation method, if there are no available non-competitive random access resources on the SUL carrier, it is prioritized to determine whether there are non-competitive random access resources on the NUL carrier. If so, the non-competitive random access resources on the NUL carrier are used as target uplink resources. If not, the contention random access resources on the SUL carrier or the contention random access resources on the NUL carrier are used as target uplink resources.

[0037] In other words, the BFRQ message is sent preferentially using non-contention random access resources on an uplink carrier with a relatively low frequency band / center frequency among multiple uplink carriers.

[0038] It should be understood that the terminal device has limited transmission power. When the terminal device uses the same power to send signals, the path loss of low-frequency signals in free space is smaller than that of high-frequency signals. Compared with the NUL carrier, the SUL carrier operates in a lower frequency band, and the SUL carrier has better uplink coverage than the NUL carrier. Therefore, giving priority to using the non-competitive random access resources on the SUL carrier to send BFRQ messages can improve the transmission reliability of the BFRQ messages, thereby increasing the success probability of BFR. For example, in a high-frequency system, when a beam failure occurs, the non-competitive random access resources on the SUL carrier can be used to send BFRQ messages.

[0039] It should be noted that the scheme proposed in the present application of preferentially selecting non-contention random access resources on multiple uplink carriers as target uplink resources does not absolutely limit the use priority of all non-contention random access resources on multiple uplink carriers to be higher than all contention random access resources on multiple uplink carriers. For example, in the scheme of preferentially selecting non-contention random access resources on the SUL carrier as the target uplink resource, the use priority of non-contention random access resources on the NUL carrier may be lower than that of contention random access resources on the SUL carrier.

[0040] Therefore, in the present application, when the terminal device has multiple uplink carriers, the non-competitive random access resources on the SUL carrier among the multiple uplink carriers are preferentially selected to send the BFRQ message. It should be understood that the terminal device has limited transmission power. When the terminal device uses the same power to send a signal, the path loss of the low-frequency signal in free space is smaller than that of the high-frequency signal. Compared with the NUL carrier, the SUL carrier operates in a lower frequency band, and the SUL carrier has better uplink coverage than the NUL carrier. Therefore, giving priority to using the non-competitive random access resources on the SUL carrier to send the BFRQ message can improve the transmission reliability of the BFRQ message, thereby increasing the success probability of the BFR.

[0041] In combination with the first aspect, in a possible implementation of the first aspect, the multiple uplink carriers include a NUL carrier and a SUL carrier; selecting a target uplink resource from the multiple uplink carriers includes: when it is detected that the quality of the candidate beam of the current cell exceeds a threshold, giving priority to selecting a non-competitive random access resource on the NUL carrier as the target uplink resource; when it is detected that the quality of the candidate beam of the current cell is lower than a threshold, giving priority to selecting a non-competitive random access resource on the SUL carrier as the target uplink resource.

[0042] The terminal device can obtain the quality of the candidate beams through measurement.

[0043] The quality of the candidate beam may be a reference signal received power (RSRP) or a reference signal received quality (RSRQ) of the candidate beam.

[0044] The threshold for measuring the quality of the candidate beam may be specified by the protocol. Alternatively, the threshold for measuring the quality of the candidate beam may be configured by the network device. For example, the network device may configure the threshold through RRC signaling or other downlink signaling.

[0045] In combination with the first aspect, in a possible implementation of the first aspect, the target uplink resource is determined from the resources on multiple uplink carriers, including: when there are no available non-competitive resources on multiple uplink carriers, a competitive resource on one of the multiple uplink carriers is determined as the target uplink resource.

[0046] Optionally, in this implementation, determining a contention resource on an uplink carrier among the multiple uplink carriers as a target uplink resource includes: determining a contention resource on a supplementary uplink carrier as a target uplink resource.

[0047] In combination with the first aspect, in a possible implementation of the first aspect, the multiple uplink carriers include a main uplink carrier and a supplementary uplink carrier of the current main cell, and an uplink carrier of the secondary cell; the target uplink resources are determined from the resources on the multiple uplink carriers, including: when there are no available non-competitive resources on the main uplink carrier of the main cell, the non-competitive resources on the uplink carrier of the secondary cell are determined as the target uplink resources; or when there are no available resources on the main uplink carrier and the supplementary uplink carrier of the main cell, the resources on the uplink carrier of the secondary cell are determined as the target uplink resources.

[0048] As an implementation method, in the process of selecting a target uplink resource from multiple uplink carriers, it is preferentially determined whether there are available non-competitive random access resources on the NUL carrier of the primary cell. If so, the non-competitive random access resources on the NUL carrier are used as the target uplink resources. If not, it is determined whether there are available non-competitive random access resources on the uplink carrier of the secondary cell. If there are available non-competitive random access resources on the uplink carrier of the secondary cell, the non-competitive random access resources on the uplink carrier of the secondary cell are selected as the target uplink resources. Otherwise, it is determined whether there are available non-competitive random access resources on the SUL carrier of the primary cell. If so, the non-competitive random access resources on the SUL carrier of the primary cell are used as the target uplink resources. If there are no available non-competitive random access resources on the uplink carriers of both the primary cell and the secondary cell, the competitive random access resources on an uplink carrier of the primary cell or the secondary cell are used as the target uplink resources.

[0049] As an implementation method, in the process of selecting a target uplink resource from multiple uplink carriers, it is preferentially determined whether there are available non-competitive random access resources on the NUL carrier of the primary cell. If so, the non-competitive random access resources on the NUL carrier are used as the target uplink resources. If not, it is determined whether there are available non-competitive random access resources on the SUL carrier of the primary cell; if there are available non-competitive random access resources on the SUL carrier of the primary cell, they are used as the target uplink resources. Otherwise, it is determined whether there are available non-competitive random access resources on the uplink carrier of the secondary cell; if there are available non-competitive random access resources on the uplink carrier of the secondary cell, they are used as the target uplink resources; if there are no available non-competitive random access resources on the uplink carriers of both the primary cell and the secondary cell, the competitive random access resources on an uplink carrier of the primary cell or the secondary cell are used as the target uplink resources.

[0050] In combination with the first aspect, in a possible implementation of the first aspect, a target uplink resource is determined from multiple uplink carriers, including: selecting a target uplink carrier from multiple uplink carriers according to preset priority information, the preset priority information being used to indicate an order of use of resources on multiple uplink carriers; and determining the target uplink resource on the target uplink carrier.

[0051] For example, the resource use priority is: non-contention random access resources of the NUL carrier>non-contention random access resources of the SUL carrier>contention random access resources of the SUL carrier>contention random access resources of the NUL carrier.

[0052] For another example, the resource usage priority is: non-contention random access resources of the SUL carrier > contention random access resources of the SUL carrier > non-contention random access resources of the NUL carrier > contention random access resources of the NUL carrier. Alternatively, the resource usage priority is: non-contention random access resources of the SUL carrier > non-contention random access resources of the NUL carrier > contention random access resources of the SUL carrier > contention random access resources of the NUL carrier.

[0053] For another example, in a carrier aggregation scenario, the resource usage priority is: non-contention random access resources on the NUL carrier of the primary cell > non-contention random access resources on the SUL carrier of the primary cell > non-contention random access resources on the uplink carrier of the secondary cell > contention random access resources on the SUL carrier of the primary cell > contention random access resources on the NUL carrier of the primary cell > contention random access resources on the uplink carrier of the secondary cell. Alternatively, the resource usage priority is: non-contention random access resources on the SUL carrier of the primary cell > non-contention random access resources on the NUL carrier of the primary cell > non-contention random access resources on the uplink carrier of the secondary cell > contention random access resources on the SUL carrier of the primary cell > contention random access resources on the NUL carrier of the primary cell > contention random access resources on the uplink carrier of the secondary cell.

[0054] Optionally, the resource usage priority may indicate the usage priority order of multiple uplink resources, and may also directly indicate the resource type with the highest priority.

[0055] Optionally, the resource usage priority may be specified by a protocol.

[0056] Optionally, the resource usage priority may be preconfigured by the network device. For example, the network device may configure the resource usage priority for the terminal device through RRC signaling or other downlink signaling.

[0057] For example, when there are multiple uplink resources, the network device may configure the priority order of resource usage, or may directly indicate the resource type with the highest priority.

[0058] In combination with the first aspect, in a possible implementation method of the first aspect, in a carrier aggregation scenario, based on the quality of the candidate beam of the primary cell and the quality of the candidate beam of the secondary cell, resources on the uplink carrier of the primary cell or resources on the uplink carrier of the secondary cell are selected as target uplink resources.

[0059] In this implementation, by comparing the quality of the candidate beams of the primary cell with the quality of the candidate beams of the secondary cell, it is determined whether to give priority to using the resources on the uplink carrier of the primary cell or the resources on the uplink carrier of the secondary cell.

[0060] The quality of the candidate beam can be RSRP or RSRQ.

[0061] Optionally, in this implementation, when the sum of the quality of the candidate beam of the primary cell and the preset offset is greater than or equal to the quality of the candidate beam of the secondary cell, the resources on the uplink carrier of the primary cell are selected as the target uplink resources, that is, the resources on the uplink carrier of the primary cell are preferentially used. When the sum of the quality of the candidate beam of the primary cell and the preset offset is less than the quality of the candidate beam of the secondary cell, the resources on the uplink carrier of the secondary cell are selected as the target uplink resources, that is, the resources on the uplink carrier of the secondary cell are preferentially used.

[0062] The preset offset may be preconfigured by the network device. For example, the network device preconfigures the preset offset through RRC signaling or other downlink signaling.

[0063] The preset offset may also be specified by a protocol.

[0064] It should be understood that preferentially selecting the uplink carrier resources in the cell with higher quality of the candidate beam from multiple uplink carriers as the target uplink resources for BFR helps to improve the efficiency of BFR.

[0065] In combination with the first aspect, in a possible implementation method of the first aspect, the target uplink resource is determined from the resources on multiple uplink carriers, including: selecting the target uplink carrier from the multiple uplink carriers according to the beam attributes associated with the resources on the multiple uplink carriers; and determining the resources on the target uplink carrier as the target uplink resource.

[0066] Optionally, this implementation is applied to a scenario where each uplink carrier among multiple uplink carriers has only contention resources, or each uplink carrier has only non-contention resources.

[0067] In combination with the first aspect, in a possible implementation of the first aspect, the multiple uplink carriers include a first carrier and a second carrier, a resource-associated channel state information reference signal CSI-RS on the first carrier, and a resource-associated synchronization signal block SSB on the second carrier. Selecting a target uplink carrier from the multiple uplink carriers according to beam attributes associated with the resources on the multiple uplink carriers, respectively, includes: determining the first carrier as the target uplink carrier.

[0068] It should be understood that SSB is generally considered to be a wide beam and CSI-RS is a narrow beam. For example, multiple CSI-RS can be considered to be quasi-co-location (QCL) to one SSB. If the terminal device fails to restore to communicating through a narrow beam, the beamforming gain can be increased, thereby supporting a higher data rate.

[0069] Therefore, in the embodiment of the present application, among multiple uplink carriers, by preferentially selecting resources on the uplink carrier associated with CSI-RS for BFR, the recovered beam can obtain a higher antenna gain (beamforming gain), thereby supporting a higher data rate.

[0070] In combination with the first aspect, in a possible implementation of the first aspect, the multiple uplink carriers include a third carrier and a fourth carrier, and the number of candidate beams associated with the resources on the third carrier is less than or equal to the number of candidate beams associated with the resources on the fourth carrier; and the target uplink carrier is selected from the multiple uplink carriers according to the beam attributes associated with the resources on the multiple uplink carriers, including: determining the third carrier as the target uplink carrier.

[0071] It should be understood that by preferentially selecting resources on uplink carriers with a smaller number of resource-associated candidate beams for BFR, it is possible to save resource overhead of network equipment and facilitate subsequent beam management.

[0072] In combination with the first aspect, in a possible implementation manner of the first aspect, a beam failure recovery timer is configured on the NUL carrier. If the beam failure recovery timer times out, the non-contention random access resource on the NUL carrier is unavailable.

[0073] In combination with the first aspect, in a possible implementation manner of the first aspect, a beam failure recovery timer is configured on the SUL carrier. If the beam failure recovery timer times out, the non-contention random access resource on the SUL carrier is unavailable.

[0074] The beam failure recovery timer of the NUL carrier and the beam failure recovery timer of the SUL carrier may be configured by the network device. For example, the network device configures the beam failure recovery timer on the NUL carrier and the beam failure recovery timer on the SUL carrier through RRC signaling or other signaling.

[0075] In combination with the first aspect, in a possible implementation of the first aspect, the target uplink resource is a competitive resource; the method also includes: receiving an association relationship between an uplink carrier and a downlink carrier from a network device; using the downlink carrier associated with the uplink carrier where the target uplink resource is located, receiving a beam recovery response message sent by the network device.

[0076] The beam failure recovery request (BFRQ) message in the method provided in the first aspect is replaced by an uplink scheduling request message, and the beam failure recovery (BFR) is replaced by uplink scheduling. Such a scheme can be applied to select resources for uplink scheduling in multiple uplink carriers.

[0077] The beam failure recovery request (BFRQ) message in the method provided in the first aspect is replaced with uplink data, and the beam failure recovery (BFR) is replaced with uplink data transmission. Such a scheme can be applied to select resources for uplink data transmission in multiple uplink carriers.

[0078] In a second aspect, a method for determining uplink resources is provided, the method being executed, for example, by a network device or a chip for a network device. The method comprises: sending configuration information to a terminal device, the configuration information including information for instructing the terminal device to select a target uplink resource for BFR from multiple uplink carriers; and receiving a BFRQ message sent by the terminal device using the target uplink resource.

[0079] The present application determines a target uplink resource for sending a beam failure recovery request message when there are multiple uplink carriers for beam failure recovery, in the hope of improving the efficiency of beam failure recovery.

[0080] Resources for beam failure recovery (BFR) of the current cell, ie, resources for sending a beam failure recovery request (BFRQ) message, are configured on multiple uplink carriers.

[0081] In combination with the second aspect, in a possible implementation manner of the second aspect, the method further includes: the network device configures resources for BFR on multiple uplink carriers for the terminal device.

[0082] For example, the network device may pre-configure resources for BFR on multiple uplink carriers for the terminal device through radio resource control (RRC) signaling. The network device may also pre-configure resources for BFR on multiple uplink carriers through other downlink signaling, which is not limited in this application.

[0083] In combination with the second aspect, in a possible implementation manner of the second aspect, the configuration information sent to the terminal device includes a resource usage priority, and the resource usage priority is used to indicate an order of resource usage on multiple uplink carriers.

[0084] For example, the resource use priority is: non-contention random access resources of the NUL carrier>non-contention random access resources of the SUL carrier>contention random access resources of the SUL carrier>contention random access resources of the NUL carrier.

[0085] For another example, the resource usage priority is: non-contention random access resources of the SUL carrier > contention random access resources of the SUL carrier > non-contention random access resources of the NUL carrier > contention random access resources of the NUL carrier. Alternatively, the resource usage priority is: non-contention random access resources of the SUL carrier > non-contention random access resources of the NUL carrier > contention random access resources of the SUL carrier > contention random access resources of the NUL carrier.

[0086] For another example, in a carrier aggregation scenario, the resource usage priority is: non-contention random access resources on the NUL carrier of the primary cell > non-contention random access resources on the SUL carrier of the primary cell > non-contention random access resources on the uplink carrier of the secondary cell > contention random access resources on the SUL carrier of the primary cell > contention random access resources on the NUL carrier of the primary cell > contention random access resources on the uplink carrier of the secondary cell. Alternatively, the resource usage priority is: non-contention random access resources on the SUL carrier of the primary cell > non-contention random access resources on the NUL carrier of the primary cell > non-contention random access resources on the uplink carrier of the secondary cell > contention random access resources on the SUL carrier of the primary cell > contention random access resources on the NUL carrier of the primary cell > contention random access resources on the uplink carrier of the secondary cell.

[0087] In combination with the second aspect, in a possible implementation of the second aspect, the configuration information sent to the terminal device includes configuration information of a beam failure recovery timer on the NUL carrier. If the beam failure recovery timer times out, the non-competitive random access resources on the NUL carrier are unavailable.

[0088] In combination with the second aspect, in a possible implementation of the second aspect, the configuration information sent to the terminal device includes configuration information of a beam failure recovery timer on the SUL carrier. If the beam failure recovery timer times out, the non-contention random access resource on the SUL carrier is unavailable.

[0089] In combination with the second aspect, in a possible implementation of the second aspect, the configuration information sent to the terminal device includes a threshold for the quality of the candidate beam, which is used by the terminal device to measure the quality of the candidate beam, so that resources for BFR can be selected from multiple uplink carriers based on the quality of the candidate beam.

[0090] In combination with the second aspect, in a possible implementation method of the second aspect, the configuration information sent to the terminal device includes an offset of the candidate beam quality, and the offset is used by the terminal device in a carrier aggregation scenario to select the resources on the uplink carrier of the main cell or the uplink carrier of the secondary cell for BFR by comparing the quality of the candidate beam of the main cell and the sum of the offset and the quality of the candidate beam of the secondary cell.

[0091] The quality of the candidate beam can be RSRP or RSRQ.

[0092] In combination with the second aspect, in a possible implementation manner of the second aspect, the network device sends resource selection information to the terminal device through RRC signaling or other downlink signaling.

[0093] In a third aspect, a communication device is provided, the communication device being used to execute the method in the first aspect or any possible implementation of the first aspect. Optionally, the communication device may include a module for executing the method in the first aspect or any possible implementation of the first aspect.

[0094] In a fourth aspect, a communication device is provided, the communication device being used to execute the method in the second aspect or any possible implementation of the second aspect. Optionally, the communication device may include a module for executing the method in the second aspect or any possible implementation of the second aspect.

[0095] In a fifth aspect, a communication device is provided, comprising a memory and a processor, the memory being used to store instructions, the processor being used to execute the instructions stored in the memory, and the execution of the instructions stored in the memory causing the processor to execute the method in the first aspect or any possible implementation of the first aspect.

[0096] In a sixth aspect, a communication device is provided, comprising a memory and a processor, the memory being used to store instructions, the processor being used to execute the instructions stored in the memory, and the execution of the instructions stored in the memory causing the processor to execute the method in the second aspect or any possible implementation of the second aspect.

[0097] In the seventh aspect, a chip is provided, which includes a processing module and a communication interface. The processing module is used to control the communication interface to communicate with the outside. The processing module is also used to implement the method in the first aspect or any possible implementation of the first aspect.

[0098] In an eighth aspect, a chip is provided, the chip comprising a processing module and a communication interface, the processing module is used to control the communication interface to communicate with the outside, and the processing module is also used to implement the method in the second aspect or any possible implementation manner of the second aspect.

[0099] In a ninth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a computer, the computer implements the method in the first aspect or any possible implementation manner of the first aspect.

[0100] In a tenth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a computer, the computer implements the method in the second aspect or any possible implementation manner of the second aspect.

[0101] In an eleventh aspect, a computer program product comprising instructions is provided, and when the instructions are executed by a computer, the computer implements the method in the first aspect or any possible implementation manner of the first aspect.

[0102] In a twelfth aspect, a computer program product comprising instructions is provided, and when the instructions are executed by a computer, the computer implements the method in the second aspect or any possible implementation manner of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0103] Figure 1 It is a schematic diagram of an application scenario of an embodiment of the present application.

[0104] Figure 2 It is a schematic flow chart of beam failure recovery.

[0105] Figure 3 It is a schematic flowchart of a method for determining uplink resources provided in an embodiment of the present application.

[0106] Figure 4 It is another schematic flowchart of the method for determining uplink resources provided in an embodiment of the present application.

[0107] Figure 5 This is another schematic flowchart of the method for determining uplink resources provided in an embodiment of the present application.

[0108] Figure 6 It is a schematic flowchart of a method for determining downlink resources provided by another embodiment of the present application.

[0109] Figure 7 It is a schematic diagram of the association relationship between resources on an uplink carrier and resources on a downlink carrier.

[0110] Figure 8 It is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0111] Fig. 9 It is another schematic block diagram of the communication device provided in an embodiment of the present application.

[0112] Fig.10 This is another schematic block diagram of the communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0113] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0114] The technical solutions of the embodiments of the present application can be applied to various communication systems, for example, the fifth generation (5G) system, the new radio (NR) system, the machine to machine (M2M) system, or other communication systems that will evolve in the future, but the embodiments of the present application are not limited to this.

[0115] The terminal device in the embodiments of the present application may refer to user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, or a terminal device in a future-evolved public land mobile communication network (PLMN), etc., and the embodiments of the present application are not limited to this.

[0116] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may be any device with a wireless transceiver function or a chip that can be arranged in the device. The network device may be a base station, and the base station may be used to communicate with one or more terminal devices, or may be used to communicate with one or more base stations having some terminal device functions (such as macro base stations and micro base stations). The network device may be a base station in a 5G system, an NR system, an M2M system, or other communication systems that will evolve in the future. In addition, the network device may also be an access point (AP), a transmission / reception point (TRP), a central unit (CU), or other network entities, and may include some or all of the functions of the above network entities, which is not limited in the embodiments of the present application.

[0117] The solution provided in the embodiment of the present application can be applied to a scenario where a terminal device has multiple uplink carriers. Figure 1 As shown, the terminal device can communicate with the network device through uplink carrier 1 and uplink carrier 2. It should be understood that Figure 1 This is only an example and not a limitation. For example, a terminal device may have more than two uplink carriers.

[0118] There may be various scenarios in which a terminal device has multiple uplink carriers.

[0119] Scenario 1: A cell supporting configuration of a supplementary uplink carrier (SUL carrier).

[0120] The carrier frequency band that can be used for uplink transmission in the working frequency band supported by the NR system can be called the NR uplink carrier (NRuplink carrier, NUL carrier) (hereinafter referred to as the NUL carrier). When deploying high-frequency cells, since the operating frequency band of the cell is high and the transmit power of the terminal device is low, the terminal device in the edge area of ​​the cell can receive the signal of the network device, but the network device may not be able to receive the signal of the terminal device. To address this problem, the NR system introduces a supplementary uplink carrier (supplementary uplink carrier, SUL carrier) (hereinafter referred to as the SUL carrier) to assist the terminal device in uplink transmission. That is, in a cell that supports SUL carrier configuration, there are two uplink carriers, namely the NUL carrier and the SUL carrier, which can be used for uplink transmission by terminal devices.

[0121] The frequency of the NUL carrier is higher than the frequency of the SUL carrier. The NUL carrier may be a high frequency carrier, such as the FR1 band or the FR2 band in the 3GPP standard. The SUL carrier may be a low frequency carrier, such as the long term evolution (LTE) band.

[0122] As an example, Table 1 shows frequency bands of a SUL carrier (frequency bands n80 to n86 shown in Table 1), and Table 2 shows frequency bands n257 to n261 of a NUL carrier.

[0123] Table 1

[0124]

[0125] Table 2

[0126]

[0127] It should be noted that the "high frequency" and "low frequency" mentioned in this article are relative concepts and do not have strict restrictive meanings.

[0128] For example, a low-frequency carrier may refer to a carrier operating below 6 GHz, and a high-frequency carrier may refer to a carrier operating at 6 GHz and above.

[0129] Scenario 2: Carrier aggregation scenario: The terminal device can use the uplink carrier of the primary cell and the uplink carrier of the secondary cell for uplink transmission.

[0130] The primary cell may support SUL configuration, that is, the primary cell has a NUL carrier and a SUL carrier; or the secondary cell may also support SUL configuration, that is, the secondary cell has a NUL carrier and a SUL carrier. That is, the multiple uplink carriers of the terminal device may include the NUL carrier and the SUL carrier of the primary cell, and the uplink carrier of the secondary cell (for example, the NUL carrier and the SUL carrier of the secondary cell).

[0131] The primary cell may be a primary cell (PCell) or a primary secondary cell (PSCell). The secondary cell may be denoted as SCell (secondary cell).

[0132] Uplink resources used for uplink transmission by terminal devices are configured on multiple uplink carriers.

[0133] For example, when a terminal device wants to report a beam failure recovery request (BFRQ) message to a network device, uplink resources for sending the BFRQ message, such as random access channel (RACH) resources, are configured on multiple uplink carriers.

[0134] For another example, when the terminal device wants to send an uplink scheduling request (SR) message to the network device, resources for sending the uplink scheduling request are configured on multiple uplink carriers.

[0135] For another example, when the terminal device has uplink data to report to the network device, uplink resources for transmitting the uplink data are configured on multiple uplink carriers.

[0136] Other uplink resources such as a physical uplink control channel (PUCCH) may also be configured on multiple uplink carriers.

[0137] The present application proposes a solution for determining a target uplink resource for uplink transmission from resources on multiple uplink carriers when a terminal device has multiple uplink carriers.

[0138] When the terminal device wants to send an uplink scheduling request message to the network device, the solution of the present application can be adopted to determine the target uplink resource for transmitting the uplink scheduling request message from multiple uplink carriers.

[0139] When the terminal device wants to send a BFRQ message to the network device, the solution of the present application can be adopted to determine the target uplink resource for transmitting the beam failure recovery request message from multiple uplink carriers.

[0140] If uplink data arrives at the terminal device, the solution of the present application can be used to determine the target uplink resource for transmitting the uplink data from multiple uplink carriers.

[0141] For ease of understanding and description, the following description is given by taking the application of the solution provided by the present application to the case where a terminal device sends a BFRQ message to a network device as an example, but the present application is not limited thereto.

[0142] By replacing the beam failure recovery request (BFRQ) message in the following embodiment with an uplink scheduling request message, and replacing the beam failure recovery (BFR) with uplink scheduling, it is possible to determine the target uplink resources for transmitting the uplink scheduling request message among multiple uplink carriers.

[0143] By replacing the beam failure recovery request (BFRQ) message in the following embodiment with uplink data, and replacing the beam failure recovery (BFR) with uplink data transmission, it is possible to determine the target uplink resources for transmitting uplink data from multiple uplink carriers.

[0144] In order to better understand the embodiments of the present application, Figure 2 The following is a schematic introduction to the concepts related to beam failure recovery.

[0145] like Figure 2 As shown, the beam failure recovery process includes the following four parts.

[0146] 1. Beam Failure Detection

[0147] The terminal device is based on the beam failure detection reference signal (BFD RS), that is, Figure 2 The service beam q0 shown in FIG. 1 performs beam failure detection. When the terminal device detects that the quality of the BFDRS is lower than the threshold, it determines that the beam has failed.

[0148] 2. New available beam discovery

[0149] The terminal device selects a candidate beam with a beam quality higher than a threshold from a candidate beam set; and selects one from the selected candidate beams as a new available beam (which can be denoted as q_new).

[0150] The candidate beam set may be configured in advance to the terminal device by the network device.

[0151] 3. Sending of beam failure recovery request (BFRQ) message

[0152] The terminal device sends a BFRQ message to the network device using the newly available beam on the physical random access channel (PRACH) resource associated with the newly available beam (q_new).

[0153] The PRACH resources associated with each candidate beam in the candidate beam set (including the newly available beam) can be configured in advance to the terminal device by the network device.

[0154] 4. Receiving the response of the network device to the BFRQ message

[0155] For example, starting from the 4th time slot after sending the BFRQ message, the terminal device uses the newly available beam (q_new) to monitor the dedicated control channel resource set (CORESET) and its corresponding search space to obtain a response from the network device to the BFRQ message. For example, the response is a physical downlink control channel (PDCCH).

[0156] It should be understood that the above Figure 2 The description is for example only and not limiting.

[0157] Figure 3 A schematic flow chart of a method for determining uplink resources provided in an embodiment of the present application. The method can be implemented by a terminal device, or can also be implemented by a chip that can be used for a terminal device. The following description is taken as an example that the execution subject is a terminal device. Figure 3 As shown, the method includes the following steps.

[0158] S310, the terminal device determines a target uplink resource from resources on multiple uplink carriers.

[0159] Multiple uplink carriers are configured with resources for beam failure recovery (BFR) of the current cell, that is, resources for sending a beam failure recovery request (BFRQ) message. The current cell represents a cell where a beam failure occurs. The target uplink resource is a resource for BFR on one of the multiple uplink carriers.

[0160] The resources for BFR on multiple uplink carriers may be preconfigured by the network device. For example, the network device may preconfigure the resources for BFR on multiple uplink carriers for the terminal device through radio resource control (RRC) signaling. The network device may also preconfigure the resources for BFR on multiple uplink carriers through other downlink signaling, which is not limited in this application.

[0161] The uplink resources used for BFR may be random access channel (RACH) resources.

[0162] S320, the terminal device uses the target uplink resources to send a BFRQ message to the network device.

[0163] Assuming that the target uplink resource is a resource on uplink beam X, in S320, the terminal device uses uplink beam X on the target uplink resource to send a BFRQ message to the network device.

[0164] In an embodiment of the present application, when there are multiple uplink carriers for beam failure recovery, a target uplink resource for sending a beam failure recovery request message is determined in the hope of improving the efficiency of beam failure recovery.

[0165] Multiple uplink carriers may all be low-frequency carriers, or may all be high-frequency carriers, or some of them may be high-frequency carriers and others may be low-frequency carriers. The "high frequency" and "low frequency" mentioned in this document are relative concepts and have no strict limiting meanings. For example, a low-frequency carrier may refer to a carrier operating below 6 GHz, and a high-frequency carrier may refer to a carrier operating at 6 GHz and above. For another example, in future evolving technologies, high-frequency carriers and low-frequency carriers may have new definitions.

[0166] In a scenario where the current cell includes a primary uplink carrier and a supplementary uplink carrier, the multiple uplink carriers include the primary uplink carrier and the supplementary uplink carrier. The primary uplink carrier may be an uplink carrier mainly used by the current cell, and the supplementary uplink carrier may be used as a supplement to the primary uplink carrier, for example, the supplementary uplink carrier is used when the primary uplink carrier fails to transmit.

[0167] The primary uplink carrier and the supplementary uplink carrier may both be high frequency carriers, or both be low frequency carriers, or the primary uplink carrier may be a high frequency carrier and the supplementary uplink carrier may be a low frequency carrier. For example, in a high frequency cell, the primary uplink carrier may be a high frequency carrier and the supplementary uplink carrier may be a low frequency carrier.

[0168] It should be understood that the primary uplink carrier and the supplementary uplink carrier are only for distinction and not for limitation. For example, other names may be used to distinguish multiple different uplink carriers in the same cell. This application does not limit this.

[0169] For example, the scenario in which the current cell includes a primary uplink carrier and a supplementary uplink carrier may be the SUL scenario described above, wherein the NUL carrier corresponds to the primary uplink carrier, and the SUL carrier corresponds to the supplementary uplink carrier.

[0170] For ease of description and understanding, the following description is made by taking the primary uplink carrier as the NUL carrier and the supplementary downlink carrier as the SUL carrier as an example.

[0171] In the scenario of carrier aggregation, the current cell is the primary cell. In the case where the uplink carrier of the secondary cell is allowed to be used for BFR of the primary cell, the multiple uplink carriers may include the uplink carrier of the primary cell and the uplink carrier of the secondary cell. If the primary cell supports SUL technology, the multiple uplink carriers may include the NUL carrier and SUL carrier of the primary cell, and the uplink carrier of the secondary cell. If the secondary cell also supports SUL technology, the multiple uplink carriers may include the NUL carrier and SUL carrier of the primary cell, and the NUL carrier and SUL carrier of the secondary cell.

[0172] Non-contention resources and / or contention resources may be configured on multiple uplink carriers, wherein the non-contention resources used for BFR may be contention-free RACH resources, and the contention resources used for BFR may be contention-based RACH resources.

[0173] Optionally, multiple uplink carriers may be configured with uplink scheduling (RS) resources, PUCCH resources or other uplink resources. Multiple uplink carriers may be configured with other non-contention resources other than non-contention random access resources, and / or may be configured with other contention resources other than contention random access resources.

[0174] In the following embodiments, description is given by taking the non-contention resource as a non-contention random access resource and the contention resource as a contention random access resource as an example.

[0175] In the present application, there are multiple implementations for determining the target uplink resource for sending the BFRQ message from resources on multiple uplink carriers.

[0176] For example, non-competitive random access resources on multiple uplink carriers may be preferentially selected as target uplink resources. For another example, resources on a NUL carrier among multiple uplink carriers (non-competitive random access resources are prioritized) may be preferentially selected as target uplink resources. For another example, resources on a SUL carrier among multiple uplink carriers (non-competitive random access resources are prioritized) may be preferentially selected as target uplink resources. For another example, based on the beam attributes respectively associated with the resources on multiple uplink carriers, a target uplink carrier is selected from multiple uplink carriers, and the target uplink resource is determined from the resources on the target uplink carrier (prioritized non-competitive random access resources). For another example, in a carrier aggregation scenario, based on the candidate beam qualities of the primary cell and the secondary cell, an uplink carrier of one cell (primary cell or secondary cell) is selected from multiple uplink carriers, and the target uplink resource is selected from the resources on the uplink carrier of the selected cell (non-competitive random access resources are prioritized).

[0177] It should be noted that each of the above implementations of determining the target uplink resource for sending the BFRQ message from the resources on multiple uplink carriers may be used independently or in combination based on internal logic.

[0178] Various implementations of determining a target uplink resource from resources on multiple uplink carriers will be described below.

[0179] A solution that gives priority to selecting non-contention random access resources as target uplink resources.

[0180] In the process of selecting a target uplink resource from multiple uplink carriers, it is first determined whether there are available non-competitive random access resources on the multiple uplink carriers. If so, the non-competitive random access resources on one of the uplink carriers are used as the target uplink resource. If not, a competitive random access resource on one uplink carrier is selected as the target uplink resource.

[0181] For example, when at least one uplink carrier among the multiple uplink carriers has a non-contention random access resource, the non-contention random access resource on one uplink carrier among the at least one uplink carrier (recorded as uplink carrier Y) is determined as the target uplink resource.

[0182] In a scenario where the current cell supports the SUL technology, the uplink carrier Y may be a NUL carrier or a SUL carrier.

[0183] In the carrier aggregation scenario, the uplink carrier Y may be an uplink carrier of the primary cell or an uplink carrier of the secondary cell.

[0184] It should be understood that when a terminal device initiates random access using non-competitive random access resources, no conflict (collision) will occur and no conflict resolution is required. Therefore, compared with using competitive random access resources to initiate random access, using non-competitive random access resources to initiate random access, the terminal device has a smaller access delay and a higher access success rate. Therefore, the present application can improve the efficiency and success rate of beam failure recovery by preferentially selecting non-competitive random access resources from multiple uplink carriers to send a beam failure recovery request message.

[0185] Optionally, when at least one uplink carrier among the multiple uplink carriers has non-contention random access resources, one uplink carrier may be randomly selected from the at least one uplink carrier, and the non-contention random access resources on the selected uplink carrier are used as target uplink resources.

[0186] Optionally, when at least one uplink carrier among the multiple uplink carriers has non-contention random access resources, a certain uplink carrier may be preferentially selected from the at least one uplink carrier, and the non-contention random access resources on the selected uplink carrier may be used as target uplink resources.

[0187] For example, the multiple uplink carriers include a NUL carrier and a SUL carrier. A non-contention random access resource on the NUL carrier may be preferentially selected from at least one uplink carrier as the target uplink resource, or a non-contention random access resource on the SUL carrier may be preferentially selected from at least one uplink carrier as the target uplink resource.

[0188] The following will describe a scheme of preferentially selecting non-contention random access resources on a NUL carrier and a scheme of preferentially selecting non-contention random access resources on a SUL carrier respectively.

[0189] A solution in which non-contention random access resources on the NUL carrier are preferentially selected as target uplink resources.

[0190] In the process of selecting the target uplink resource from multiple uplink carriers, it is first determined whether there are available non-contention random access resources on the NUL carrier. If so, the non-contention random access resources on the NUL carrier are used as the target uplink resources, that is, the BFRQ message is sent using the non-contention random access resources on the NUL carrier.

[0191] It should be understood that since the NUL carrier may operate in a high-frequency frequency band, it can use a larger subcarrier interval defined by the protocol for transmission, and the corresponding time per symbol (absolute time) is shorter. Therefore, compared with the SUL carrier, the configuration of random access resources on the NUL carrier can be more dense, which can enable terminal devices to have more opportunities to use resources in a relatively short period of time, and can effectively reduce transmission delays.

[0192] Therefore, in the present application, when the terminal device has multiple uplink carriers, the non-competitive random access resources on the NUL carrier among the multiple uplink carriers are preferentially selected to send the BFRQ message, which can reduce the BFR delay and thus effectively improve the BFR efficiency.

[0193] In the process of prioritizing the non-competitive random access resources on the NUL carrier as the target uplink resources, if there are no available non-competitive random access resources on the NUL carrier, or the sending of the BFRQ message using the non-competitive random access resources on the NUL carrier fails, determine whether there are non-competitive random access resources on other carriers. If so, use them to send the BFRQ message. If not, use the competitive random access resources on multiple uplink carriers to send the BFRQ message.

[0194] For example, when there are no available non-competitive random access resources on the NUL carrier, or when sending the BFRQ message using the non-competitive random access resources on the NUL carrier fails, determine whether there are available non-competitive random access resources on the SUL carrier. If there are available non-competitive random access resources on the SUL carrier, use the non-competitive random access resources on the SUL carrier to send the BFRQ message; if there are no available non-competitive random access resources on both the NUL carrier and the SUL carrier, or when sending the BFRQ message using the non-competitive random access resources fails, consider using the competitive random access resources on multiple uplink carriers to send the BFRQ message.

[0195] Optionally, in some embodiments, a beam failure recovery timer is configured on the NUL carrier. If the beam failure recovery timer times out, the non-contention random access resources on the NUL carrier are unavailable.

[0196] The absence of available non-contention random access resources on the NUL carrier mentioned in the above embodiment means that no non-contention random access resources are configured on the NUL carrier, or the beam failure recovery timer on the NUL carrier times out.

[0197] Optionally, in some embodiments, a beam failure recovery timer is configured on the SUL carrier. If the beam failure recovery timer times out, the non-contention random access resources on the SUL carrier are unavailable.

[0198] The absence of available non-contention random access resources on the SUL carrier mentioned in the above embodiment means that no non-contention random access resources are configured on the SUL carrier, or the beam failure recovery timer on the SUL carrier times out.

[0199] The beam failure recovery timer of the NUL carrier and the beam failure recovery timer of the SUL carrier may be configured by the network device.

[0200] For example, the network device may define the beam failure recovery timer of the NUL carrier and the beam failure recovery timer of the SUL carrier through the following configuration information ( / / is followed by a comment). The following configuration information may be carried in RRC signaling or other downlink signaling.

[0201] beamFailureRecoveryTimer-CFRA-NUL / / Configure the beam failure recovery timer for the NUL carrier.

[0202] Timer for beam failure recovery timer on NUL.Upon expiration of the timer the UE does not use CFRA on NUL for BFR. / / Function of configuring the beam failure recovery timer on NUL carrier.

[0203] beamFailureRecoveryTimer-CFRA-SUL / / Configure the beam failure recovery timer for the SUL carrier.

[0204] Timer for beam failure recovery timer on SUL.Upon expiration of the timer the UE does not use CFRA on SUL for BFR. / / Function of configuring the beam failure recovery timer of the SUL carrier.

[0205] For another example, the network device may define the method of using the beam failure recovery timer of the NUL carrier and the method of using the beam failure recovery timer of the SUL carrier through the following configuration information ( / / is followed by a comment). The following configuration information may be carried in RRC signaling or other downlink signaling.

[0206] XXXX condition, the MAC entity shall:

[0207] 1>if the contention-free Random Access Preamble for beam failurerecovery request was configured on NUL:

[0208] 2>start beamFailureRecoveryTimer-CFRA-NUL timer and start RAprocedure on NUL;

[0209] 3>Till expiration of the timer, BFR is not successfully completed; / / If non-contention random access resources are configured on the NUL carrier, when the non-contention random access resources on the NUL carrier are used for random access, the beam failure recovery timer of the NUL carrier starts timing. Until the timer expires, if random access is not successful, the BFRQ fails to be sent using the non-contention random access resources on the NUL carrier.

[0210] 4>if the contention-free Random Access Preamble for beam failurerecovery request was configured on SUL:

[0211] 5>start beamFailureRecoveryTimer-CFRA-SUL timer. / / If non-contention random access resources are configured on the SUL carrier, when random access starts using the non-contention random access resources on the SUL carrier, the beam failure recovery timer of the SUL carrier starts timing.

[0212] As an example and not a limitation, the following Figure 4 , describes the specific process of the terminal device preferentially selecting the non-contention random access resource on the NUL carrier as the target uplink resource. Figure 4 As shown, the following steps are included.

[0213] S401, detecting the beam of the current cell fails, and the current cell has a NUL carrier and a SUL carrier.

[0214] S402, determine whether non-contention random access resources are configured on the NUL carrier, if so, go to S403, if not, go to S406.

[0215] S403, determine whether the beam failure recovery timer of the NUL carrier has timed out, if so, go to S406, if not, go to S404.

[0216] S404: Send a BFRQ message using non-contention random access resources on the NUL carrier.

[0217] S405, detecting whether the sending of the BFRQ message using the non-contention random access resources on the NUL carrier is successful, if so, going to S414, if not, going to S406.

[0218] S406, determine whether non-contention random access resources are configured on the SUL carrier, if so, go to S407, if not, go to S410.

[0219] S407, determine whether the beam failure recovery timer of the SUL carrier has timed out, if so, go to S410, if not, go to S408.

[0220] S408: Send a BFRQ message using non-contention random access resources on the SUL carrier.

[0221] S409, detecting whether the sending of the BFRQ message using the non-contention random access resources on the SUL carrier is successful, if so, going to S414, if not, going to S410.

[0222] S410, determine whether contention random access resources are configured on the SUL carrier, if so, go to S411, if not, go to S413.

[0223] S411, sending a BFRQ message using contention random access resources on the SUL carrier.

[0224] S412, detecting whether sending the BFRQ message using the contention random access resource on the SUL carrier is successful, if so, going to S414, if not, going to S413.

[0225] S413: Send a BFRQ message using contention random access resources on the NUL carrier.

[0226] S414, receiving a beam failure recovery response message sent by the network device.

[0227] The above steps S403 and S407 are optional, that is, step S404 can be directly executed after step S402 is executed, and step S408 can be directly executed after step S406 is executed.

[0228] Optionally, the terminal device may select a target uplink resource (ie, an uplink resource for sending BFRQ) from resources on multiple uplink carriers according to a preset resource usage priority, where the resource usage priority indicates an order of usage priority of resources on multiple uplink carriers.

[0229] For example, the resource usage priority is: non-contention random access resources of NUL carrier>non-contention random access resources of SUL carrier>contention random access resources of SUL carrier>contention random access resources of NUL carrier, and the terminal device can use the resource usage priority as follows: Figure 4The operation flow shown is used to determine the target uplink resource from multiple uplink carriers according to the resource usage priority.

[0230] Optionally, the resource usage priority may be specified by a protocol.

[0231] Optionally, the resource usage priority may be preconfigured by the network device. For example, the network device may configure the resource usage priority for the terminal device through RRC signaling or other downlink signaling.

[0232] It should be understood that since the NUL carrier may operate in a high-frequency frequency band, it can use a larger subcarrier interval defined by the protocol for transmission, and the corresponding time per symbol (absolute time) is shorter. Therefore, compared with the SUL carrier, the configuration of random access resources on the NUL carrier can be more dense, which can enable terminal devices to have more opportunities to use resources in a relatively short period of time, and can effectively reduce transmission delays.

[0233] Therefore, in the present application, when the terminal device has multiple uplink carriers, the non-competitive random access resources on the NUL carrier among the multiple uplink carriers are preferentially selected to send the BFRQ message, which can reduce the BFR delay and thus effectively improve the BFR efficiency.

[0234] In addition, the total number of non-competitive random access resources on the NUL carrier is relatively large, and the associated non-competitive random access resources can be configured for the downlink narrow beam (such as CSI-RS), so that the terminal device does not need to re-perform beam scanning and beam training after completing BFR, so that the terminal device can experience a relatively shorter data transmission recovery delay. Therefore, giving priority to non-competitive random access resources on the NUL carrier can reduce the delay of BFR, thereby improving the efficiency of BFR.

[0235] A solution in which non-contention random access resources on the SUL carrier are preferentially selected as target uplink resources.

[0236] In the process of selecting the target uplink resource from multiple uplink carriers, it is first determined whether there are available non-contention random access resources on the SUL carrier. If so, the non-contention random access resources on the SUL carrier are used as the target uplink resources, that is, the BFRQ message is sent using the non-contention random access resources on the SUL carrier.

[0237] In other words, the non-competitive random access resources on the uplink carrier with relatively low frequency band / center frequency in multiple uplink carriers are preferentially used to send BFRQ messages. For example, if the terminal device is configured with multiple uplink carriers by the network device, one of which operates at 28 GHz and another operates at 39 GHz, the terminal device can preferentially select the resources on the uplink carrier operating at 28 GHz for BFR.

[0238] It should be understood that the terminal device has limited transmission power. When the terminal device uses the same power to send signals, the path loss of low-frequency signals in free space is smaller than that of high-frequency signals. Compared with the NUL carrier, the SUL carrier operates in a lower frequency band, and the SUL carrier has better uplink coverage than the NUL carrier. Therefore, giving priority to using non-competitive random access resources on the SUL carrier to send BFRQ messages can improve the transmission reliability of the BFRQ messages, thereby increasing the success probability of BFR.

[0239] For example, in a high frequency system, when a beam failure occurs, the non-contention random access resources on the SUL carrier may be preferentially used to send a BFRQ message.

[0240] It should be noted that the scheme proposed in the present application of preferentially selecting non-contention random access resources on multiple uplink carriers as target uplink resources does not absolutely limit the use priority of all non-contention random access resources on multiple uplink carriers to be higher than all contention random access resources on multiple uplink carriers. For example, in the scheme of preferentially selecting non-contention random access resources on the SUL carrier as the target uplink resource, the use priority of non-contention random access resources on the NUL carrier may be lower than that of contention random access resources on the SUL carrier.

[0241] For example, in the process of prioritizing the non-contention random access resources on the SUL carrier as the target uplink resources, if there are no available non-contention random access resources on the SUL carrier, or the sending of the BFRQ message using the non-contention random access resources on the SUL carrier fails, the contention random access resources on the SUL carrier or the non-contention random access resources on the NUL carrier can be used to send the BFRQ message.

[0242] Optionally, in a scheme of prioritizing non-competitive random access resources on a SUL carrier as target uplink resources, a beam failure recovery timer may also be configured on the SUL carrier. If the beam failure recovery timer times out, the non-competitive random access resources on the SUL carrier are unavailable; a beam failure recovery timer may also be configured on the NUL carrier. If the beam failure recovery timer times out, the non-competitive random access resources on the NUL carrier are unavailable.

[0243] The absence of available non-contention random access resources on the SUL carrier mentioned in the above embodiment means that no non-contention random access resources are configured on the SUL carrier, or the beam failure recovery timer on the SUL carrier has timed out. The absence of available non-contention random access resources on the NUL carrier mentioned in the above embodiment means that no non-contention random access resources are configured on the NUL carrier, or the beam failure recovery timer on the NUL carrier has timed out.

[0244] The configuration method of the beam failure recovery timer on the NUL carrier and the beam failure recovery timer on the SUL carrier has been described above and will not be repeated here for the sake of brevity.

[0245] As an example and not a limitation, the following Figure 5 , describes the specific process of the terminal device preferentially selecting the non-contention random access resource on the SUL carrier as the target uplink resource. Figure 5 As shown, the following steps are included.

[0246] S501, detecting the beam of the current cell fails, and the current cell has a NUL carrier and a SUL carrier.

[0247] S502, determine whether non-contention random access resources are configured on the SUL carrier, if so, go to S503, if not, go to S506.

[0248] S503, determine whether the beam failure recovery timer of the SUL carrier has timed out, if so, go to S506, if not, go to S504.

[0249] S504: Send a BFRQ message using non-contention random access resources on the SUL carrier.

[0250] S505, detecting whether the sending of the BFRQ message using the non-contention random access resources on the SUL carrier is successful, if so, going to S514, if not, going to S506.

[0251] S506, determine whether the SUL carrier is configured with contention random access resources, if so, go to S507, if not, go to S509.

[0252] S507: Send a BFRQ message using contention random access resources on the SUL carrier.

[0253] S508, detecting whether the sending of the BFRQ message using the contention random access resource on the SUL carrier is successful, if so, go to S514, if not, go to S509.

[0254] S509, determine whether non-contention random access resources are configured on the NUL carrier, if so, go to S510, if not, go to S513.

[0255] S510, determine whether the beam failure recovery timer of the NUL carrier has timed out, if so, go to S513, if not, go to S511.

[0256] S511: Send a BFRQ message using non-contention random access resources on the NUL carrier.

[0257] S512, detecting whether the sending of the BFRQ message using the non-contention random access resources on the NUL carrier is successful, if so, going to S514, if not, going to S513.

[0258] S513: Send a BFRQ message using contention random access resources on the NUL carrier.

[0259] S514, receiving a beam failure recovery response message sent by the network device.

[0260] The above steps S503 and S510 are optional, that is, step S504 may be directly executed after step S502 is executed, and step S511 may be directly executed after step S509 is executed.

[0261] exist Figure 5 In the present invention, the priority of using the contention random access resources on the SUL carrier is higher than the priority of using the non-contention random access resources on the NUL carrier.

[0262] Optionally, the priority of using the non-contention random access resources on the NUL carrier may be higher than the priority of using the contention random access resources on the SUL carrier. For example, when there are no available non-contention random access resources on the SUL carrier, or when sending a BFRQ message using the non-contention random access resources on the SUL carrier fails, the non-contention random access resources on the NUL carrier are used first, and the contention random access resources on the SUL carrier are used secondarily.

[0263] Optionally, the terminal device may select a target uplink resource (ie, an uplink resource for sending BFRQ) from resources on multiple uplink carriers according to a preset resource usage priority, where the resource usage priority indicates an order of usage priority of resources on multiple uplink carriers.

[0264] For example, the resource usage priority is: non-contention random access resources of the SUL carrier > contention random access resources of the SUL carrier > non-contention random access resources of the NUL carrier > contention random access resources of the NUL carrier. Alternatively, the resource usage priority is: non-contention random access resources of the SUL carrier > non-contention random access resources of the NUL carrier > contention random access resources of the SUL carrier > contention random access resources of the NUL carrier.

[0265] Optionally, the resource usage priority may indicate the usage priority order of multiple uplink resources, and may also directly indicate the resource type with the highest priority.

[0266] Optionally, the resource usage priority may be specified by a protocol.

[0267] Optionally, the resource usage priority may be preconfigured by the network device. For example, the network device may configure the resource usage priority for the terminal device through RRC signaling or other downlink signaling.

[0268] In an embodiment of the present application, when a terminal device has multiple uplink carriers, non-competitive random access resources on a SUL carrier among multiple uplink carriers are preferentially selected to send a BFRQ message. It should be understood that the transmission power of the terminal device is limited. When the terminal device uses the same power to send a signal, the path loss of a low-frequency signal in free space is smaller than that of a high-frequency signal. Compared with the NUL carrier, the SUL carrier operates in a lower frequency band, and the SUL carrier has better uplink coverage than the NUL carrier. Therefore, giving priority to using non-competitive random access resources on the SUL carrier to send a BFRQ message can improve the transmission reliability of the BFRQ message, thereby increasing the success probability of the BFR.

[0269] The above describes a scheme of preferentially selecting non-contention random access resources on a NUL carrier as target uplink resources and a scheme of preferentially selecting non-contention random access resources on a SUL carrier as target uplink resources.

[0270] Optionally, in some embodiments, when it is detected that the quality of the candidate beam of the current cell exceeds a threshold, non-competitive random access resources on the NUL carrier are preferentially selected as target uplink resources; when it is detected that the quality of the candidate beam of the current cell is lower than a threshold, non-competitive random access resources on the SUL carrier are preferentially selected as target uplink resources.

[0271] The terminal device can obtain the quality of the candidate beams through measurement.

[0272] For example, the quality of the candidate beam may be a reference signal received power (RSRP) or a reference signal received quality (RSRQ) of the candidate beam corresponding to the candidate beam measured at the physical layer.

[0273] The threshold used to measure the quality of the candidate beam may be specified by a protocol or may be configured by a network device.

[0274] For example, the network device may configure the threshold through RRC signaling or other downlink signaling.

[0275] Optionally, in a carrier aggregation scenario, if the uplink carrier of the secondary cell is also allowed to be used for the BFR of the current cell, the multiple uplink carriers include not only the NUL carrier and the SUL carrier of the primary cell (i.e., the current cell), but also the uplink carrier of the secondary cell. In this case, the terminal device determines the target uplink resource for sending the BFRQ message from the resources on the multiple uplink carriers in the following manner.

[0276] Method 1) gives priority to using non-competitive random access resources on multiple uplink carriers. When there are no available non-competitive random access resources on multiple uplink carriers, or when sending a BFRQ message using non-competitive random access resources on multiple uplink carriers fails, use competitive random access resources on multiple uplink carriers to send a BFRQ message.

[0277] For example, the resource usage priority is: non-contention random access resources on the NUL carrier of the primary cell > non-contention random access resources on the SUL carrier of the primary cell > non-contention random access resources on the uplink carrier of the secondary cell > contention random access resources on the SUL carrier of the primary cell > contention random access resources on the NUL carrier of the primary cell > contention random access resources on the uplink carrier of the secondary cell.

[0278] For another example, the resource usage priority is: non-competitive random access resources on the SUL carrier of the primary cell > non-competitive random access resources on the NUL carrier of the primary cell > non-competitive random access resources on the uplink carrier of the secondary cell > competitive random access resources on the SUL carrier of the primary cell > competitive random access resources on the NUL carrier of the primary cell > competitive random access resources on the uplink carrier of the secondary cell.

[0279] Method 2) Prioritize the use of resources on the uplink carrier of the primary cell. When there are no resources available for sending the BFRQ message on the uplink carrier of the primary cell, or when sending the BFRQ message using the resources on the uplink carrier of the primary cell fails, use the resources on the uplink carrier of the secondary cell (prioritize non-competitive random access resources) to send the BFRQ message.

[0280] Any of the schemes described above of prioritizing non-competitive random access resources as target uplink resources, prioritizing non-competitive random access resources on NUL carriers as target uplink resources, or prioritizing non-competitive random access resources on SUL carriers as target uplink resources can be adopted, and resources on the uplink carrier of the primary cell are preferentially used.

[0281] Optionally, in a carrier aggregation scenario, resources on the uplink carrier of the primary cell or resources on the uplink carrier of the secondary cell are selected as target uplink resources based on the quality of the candidate beams of the primary cell and the quality of the candidate beams of the secondary cell.

[0282] In other words, by comparing the quality of the candidate beams of the primary cell with the quality of the candidate beams of the secondary cell, it is determined whether to give priority to using the resources on the uplink carrier of the primary cell or to give priority to using the resources on the uplink carrier of the secondary cell.

[0283] The quality of the candidate beam may be a reference signal received power (RSRP) or a reference signal received quality (RSRQ).

[0284] Optionally, when the sum of the quality of the candidate beam of the primary cell and the preset offset is greater than or equal to the quality of the candidate beam of the secondary cell, the resources on the uplink carrier of the primary cell are selected as the target uplink resources, that is, the resources on the uplink carrier of the primary cell are preferentially used.

[0285] When the sum of the quality of the candidate beam of the primary cell and the preset offset is less than the quality of the candidate beam of the secondary cell, the resources on the uplink carrier of the secondary cell are selected as the target uplink resources, that is, the resources on the uplink carrier of the secondary cell are preferentially used.

[0286] The preset offset may be preconfigured by the network device. For example, the network device preconfigures the preset offset through RRC signaling or other downlink signaling.

[0287] The preset offset may also be specified by a protocol.

[0288] Optionally, it may also be determined in other ways based on the quality of the candidate beams of the primary cell and the quality of the candidate beams of the secondary cell to give priority to using resources on the uplink carrier of the primary cell or resources on the uplink carrier of the secondary cell. This application does not limit this.

[0289] It should be understood that in a carrier aggregation scenario, after determining to give priority to using the uplink resources of one of the primary cell and the secondary cell, any of the target uplink resource selection methods provided above can be used to determine the target uplink resources from the resources of the uplink carrier of the selected cell.

[0290] The present application also proposes a solution for determining a target uplink resource from multiple uplink carriers according to a beam attribute associated with a resource on the uplink carrier.

[0291] Optionally, in some embodiments, step 310 includes: selecting a target uplink carrier from multiple uplink carriers according to beam properties associated with resources on the multiple uplink carriers; and determining the resources on the target uplink carrier as the target uplink resources.

[0292] Optionally, the multiple uplink carriers include a first carrier and a second carrier, the resources on the first carrier are associated with a channel state information-reference signal (CSI-RS), and the resources on the second carrier are associated with a synchronization signal block (SSB), and the first carrier is selected as the target uplink carrier.

[0293] In other words, among multiple uplink carriers, the resource utilization priority of any uplink carrier whose resources are associated with the CSI-RS is higher than the resource utilization priority of the uplink carrier associated with the SSB.

[0294] The first carrier and the second carrier are only for distinction and not limitation. The first carrier represents a carrier whose resources are associated with CSI-RS in any one of multiple uplink carriers, and the second carrier represents a carrier whose resources are associated with SSB in any one of multiple uplink carriers.

[0295] For example, the first carrier and the second carrier are respectively a NUL carrier and a SUL carrier of the same cell. For another example, the first carrier and the second carrier are respectively an uplink carrier of a primary cell and an uplink carrier of a secondary cell.

[0296] It should be understood that SSB is generally considered to be a wide beam and CSI-RS is a narrow beam. For example, multiple CSI-RS can be considered to be quasi-co-location (QCL) to one SSB. If the terminal device fails to restore to communicating through a narrow beam, the beamforming gain can be increased, thereby supporting a higher data rate.

[0297] Therefore, in the embodiment of the present application, among multiple uplink carriers, by preferentially selecting resources on the uplink carrier associated with CSI-RS for BFR, the recovered beam can obtain a higher antenna gain (beamforming gain), thereby supporting a higher data rate.

[0298] Optionally, the solution of preferentially selecting resources on an uplink carrier associated with a CSI-RS for BFR can be applied to a scenario where both compared carriers have non-contention random access resources or both have contention random access resources.

[0299] Optionally, a solution of preferentially selecting resources on an uplink carrier associated with a CSI-RS for BFR can be applied to various scenarios in which a terminal device has multiple uplink carriers for BFR.

[0300] Optionally, the solution of preferentially selecting resources on an uplink carrier associated with a CSI-RS for BFR may also be applied to some of the above embodiments.

[0301] For example, in a solution that preferentially selects non-competitive random access resources on multiple uplink carriers for BFR, if it is detected that there are available non-competitive random access resources on both of two uplink carriers, at this time, if the resources on one uplink carrier are associated with CSI-RS and the resources on the other uplink carrier are associated with SSB, then the non-competitive random access resources on the uplink carrier associated with CSI-RS are preferentially selected for BFR.

[0302] Optionally, the multiple uplink carriers include a third carrier and a fourth carrier, and the number of candidate beams associated with the resources on the third carrier is less than or equal to the number of candidate beams associated with the resources on the fourth carrier; the third carrier is determined as the target uplink carrier.

[0303] In other words, the uplink carrier with a smaller number of associated candidate beams is preferentially used for BFR.

[0304] The third carrier and the fourth carrier are only for distinction rather than limitation. The third carrier and the fourth carrier represent any two uplink carriers among the multiple uplink carriers with different numbers of candidate beams associated with the resources.

[0305] For example, if the random access resources on one uplink carrier (which can be denoted as the third carrier) among the multiple uplink carriers are associated with X candidate beams, and the random access resources on another uplink carrier (which can be denoted as the fourth carrier) are associated with Y candidate beams, and X < Y, then the terminal device preferentially performs BFR on the third carrier associated with X candidate beams.

[0306] Taking X as 2 and Y as 4 as an example. If the terminal device uses the random access resources on the third carrier for BFR, the network device needs to perform beam failure recovery response in 2 beam directions; if the terminal device uses the random access resources on the fourth carrier for BFR, the network device needs to perform beam failure recovery response in 4 beam directions. Therefore, compared with using the resources on the fourth carrier for BFR, when the terminal device uses the resources on the third carrier for BFR, it can indicate a smaller beam failure recovery response beam range for the network device, thereby saving the resource overhead of the network device and being beneficial to subsequent beam management.

[0307] Therefore, in the embodiments of the present application among multiple uplink carriers, by preferentially selecting the resources on the uplink carrier with a smaller number of candidate beams associated with the resources for BFR, it can save the resource overhead of the network device and is also beneficial to subsequent beam management.

[0308] Optionally, the solution of preferentially selecting the resources on the uplink carrier with a smaller number of candidate beams associated with the resources for BFR can be applied to the scenario where both of the two carriers for comparison have non-competitive random access resources or both have competitive random access resources.

[0309] Optionally, a solution of preferentially selecting resources on an uplink carrier with a smaller number of candidate beams associated with the resources for BFR can be applied to various scenarios in which a terminal device has multiple uplink carriers for BFR.

[0310] Optionally, a solution of preferentially selecting resources on uplink carriers with a smaller number of candidate beams associated with the resources for BFR may also be applied to some of the above embodiments.

[0311] For example, in a scheme of preferentially selecting non-competitive random access resources on multiple uplink carriers for BFR, if it is detected that there are available non-competitive random access resources on two uplink carriers, at this time, if the number of candidate beams associated with the resources on the two uplink carriers is different, the non-competitive random access resources on the uplink carrier associated with a smaller number of candidate beams are preferentially selected for BFR.

[0312] As can be seen from the above, in the embodiment of the present application, when there are multiple uplink carriers for BFR, a plurality of implementation methods for selecting target uplink resources for sending BFRQ messages from resources on multiple uplink carriers are proposed. For example, non-competitive random access resources on multiple uplink carriers may be preferentially selected as target uplink resources. For another example, resources on NUL carriers among multiple uplink carriers (non-competitive random access resources are preferred) may be preferentially selected as target uplink resources. For another example, resources on SUL carriers among multiple uplink carriers (non-competitive random access resources are preferred) may be preferentially selected as target uplink resources. For another example, resources on uplink carriers whose resources are associated with CSI-RS among multiple uplink carriers are preferentially selected as target uplink resources. For another example, resources on uplink carriers with a smaller number of candidate beams associated with resources among multiple uplink carriers are preferentially selected as target uplink resources. For another example, in a carrier aggregation scenario, among the uplink carriers of the primary cell and the secondary cell, resources on the uplink carriers of cells with higher quality of candidate beams are preferentially selected as target uplink resources (non-competitive random access resources are preferred). Each of these implementations can be used independently or in combination based on internal logic. Some of these implementations can improve the efficiency and success rate of BFR, some can increase the data rate of the restored beam, and some can save the resource overhead of network equipment.

[0313] In summary, the embodiments of the present application propose a resource selection scheme that helps to recover from beam failure when there are multiple uplink carriers used for BFR.

[0314] The above describes a method for selecting a target uplink resource from multiple uplink carriers for uplink transmission, taking the beam failure recovery (BFR) scenario as an example. However, the present application is not limited to this. The scheme for determining uplink resources from multiple uplink carriers provided in the present application can also be applied to other uplink transmission scenarios, for example, a scenario in which a terminal device reports a scheduling request message to a network device, and another example, a scenario in which a terminal device reports uplink data to a network device.

[0315] By replacing the beam failure recovery request (BFRQ) message in the above embodiments with an uplink scheduling request message, and replacing the beam failure recovery (BFR) with uplink scheduling, it is possible to determine the target uplink resources for transmitting the uplink scheduling request message among multiple uplink carriers.

[0316] Optionally, the non-competitive random access resources in the above embodiments are replaced with uplink scheduling resources. In this case, the uplink scheduling resources on the NUL carrier can be preferentially selected to send an uplink scheduling request message, or the uplink scheduling resources on the SUL carrier can be preferentially selected to send an uplink scheduling request message, or, based on the beam attributes associated with the resources on the uplink carrier, a target uplink carrier can be selected from multiple carriers, and the uplink scheduling resource on the target uplink carrier can be used to send an uplink scheduling request message.

[0317] By replacing the beam failure recovery request (BFRQ) message in the above embodiment with uplink data, and replacing the beam failure recovery (BFR) with uplink data transmission, it is possible to determine the target uplink resources for transmitting uplink data from multiple uplink carriers.

[0318] Optionally, the non-competitive random access resources in the above embodiments are replaced with uplink resources. In this case, the uplink resources on the NUL carrier can be preferentially selected to send uplink data, or the uplink resources on the SUL carrier can be preferentially selected to send uplink data, or, based on the beam attributes associated with the resources on the uplink carrier, a target uplink carrier can be selected from multiple carriers, and the uplink data can be sent using the uplink resources on the target uplink carrier.

[0319] In some scenarios, the uplink carrier where the target uplink resource for the terminal device to send the BFRQ message corresponds to multiple downlink carriers. For example, the terminal device uses the non-competitive random access resource on the SUL carrier to send the BFRQ message, and the SUL carrier corresponds to multiple downlink carriers. In this scenario, the terminal device needs to determine the target downlink carrier for receiving the BFR response message sent by the network device from multiple downlink carriers, and determine the target BWP for receiving the BFR response message in the carrier bandwidth part (bandwidthpart, BWP) on the target downlink carrier.

[0320] Currently, there is no solution for determining downlink resources that can be applied to the above scenario.

[0321] The present application proposes a method for determining downlink resources. The method can also be applied to a scenario where the uplink carrier to which the terminal device sends a BFRQ message corresponds to multiple downlink carriers. Figure 6 As shown, the method includes the following steps.

[0322] S610, the terminal device sends a BFRQ message to the network device using the target uplink resources on the target uplink carrier.

[0323] For example, the target uplink resource is a contention random access resource.

[0324] Optionally, the target uplink carrier corresponds to multiple downlink carriers. Each downlink carrier may have multiple BWPs, for example, 4 BWPs.

[0325] S620, the terminal device obtains an uplink and downlink carrier association relationship, where the uplink and downlink carrier association relationship includes an association relationship between the target uplink carrier and the target downlink carrier.

[0326] The association relationship between the target uplink carrier and the target downlink carrier may be specified by a protocol or configured by a network device.

[0327] S630, the terminal device uses the target downlink carrier to receive a beam failure recovery response message (referred to as a BFR response message) sent by the network device.

[0328] The solution provided in this application helps the terminal device to effectively determine the downlink resources used to monitor the BFR response message.

[0329] The terminal device can obtain the association relationship between the uplink and downlink carriers, that is, obtain the target downlink carrier, through a variety of implementation methods.

[0330] Optionally, the uplink and downlink carrier association relationship is specified by a protocol, or may be called a default one.

[0331] For example, the terminal device sends a BFRQ message using random access resources on a SUL carrier, the SUL carrier corresponds to multiple downlink carriers, and the terminal device monitors the BFR response message on a downlink carrier of the primary cell by default. The primary cell is a PCell or a PSCell. In other words, by default, the SUL carrier is associated with a downlink carrier of the primary cell.

[0332] For another example, the terminal device sends a BFRQ message using random access resources on a SUL carrier, the SUL carrier corresponds to multiple downlink carriers, and the terminal device monitors the BFR response message on a downlink carrier of the cell where the SUL carrier is located by default. In other words, by default, the SUL carrier is associated with a downlink carrier of the same cell.

[0333] Optionally, the uplink and downlink carrier association relationship is preconfigured by the network device.

[0334] For example, the network device sends configuration information to the terminal device, and the configuration information carries information about the association relationship between the uplink and downlink carriers.

[0335] For example, the association relationship between the uplink and downlink carriers is indicated by the index of the cell where the carrier is located. For example, the association relationship between the uplink carrier and the downlink carrier is indicated by the ServCellIndex or SCellIndex of an uplink carrier and the ServCellIndex or SCellIndex of a downlink carrier.

[0336] Optionally, the uplink and downlink carrier association relationship refers to an association relationship between an uplink carrier and a downlink carrier determined by the network device when configuring non-contention random access resources.

[0337] The above describes that the terminal device determines the target downlink carrier for receiving the BFR response message through the uplink and downlink carrier association relationship.

[0338] It should be understood that one downlink carrier may include multiple BWPs, for example, 4 BWPs. After determining the target downlink carrier, the terminal device also needs to determine a target BWP on the target downlink carrier for receiving the BFR response message.

[0339] The terminal device may determine a target BWP for receiving a BFR response message on a target downlink carrier through a variety of implementation methods.

[0340] Optionally, a BWP whose index on the target downlink carrier is the same as the index of the BWP for sending the BFRQ message is used as the target BWP.

[0341] For example, the terminal device sends a BFRQ message using random access resources on a SUL carrier using BWP x (x is the index of the BWP), and can monitor a BFR response message on BWP x of the target downlink carrier.

[0342] Optionally, in some scenarios, the downlink carrier has only one BWP. In this case, after determining the target downlink carrier, the BFR response message may be monitored directly on the one BWP of the target downlink carrier.

[0343] For example, there are random access resources on BWP 0 to 3 of the SUL carrier, and there is only BWP 0 on the downlink carrier. No matter which BWP of the SUL carrier the terminal device sends the BFRQ message on, after the terminal device determines the target downlink carrier, it listens for the BFR response message on BWP 0 of the target downlink carrier.

[0344] Optionally, according to the association relationship between the BWP in the downlink carrier and the BWP in the uplink carrier, a target BWP for receiving the BFR response message on the target downlink carrier is determined.

[0345] For example, the association relationship between the BWP in the downlink carrier and the BWP in the uplink carrier refers to an ascending association relationship between the index of the BWP in the downlink carrier and the index of the BWP in the uplink carrier.

[0346] like Figure 7 As shown, the SUL carrier includes BWP 0-3, among which BWP 0 and BWP 1 have no random access resources, BWP 2 and BWP 3 have random access resources, and the downlink carrier has BWP 0 and BWP 1. Figure 7 In the example, the association relationship between the BWP in the downlink carrier and the BWP in the uplink carrier is that BWP 2 of the SUL carrier is associated with BWP 0 of the downlink carrier, and BWP 3 of the SUL carrier is associated with BWP 1 of the downlink carrier. Figure 7 The terminal device uses the random access resource on BWP 2 on the SUL carrier to send a BFRQ message, and the terminal device uses BWP 0 on the target downlink carrier to monitor the BFR response message. For another example, the terminal device uses Figure 7 The terminal device sends a BFRQ message using the random access resources on BWP 3 on the SUL carrier obtained from the transmission, and the terminal device uses BWP 1 on the target downlink carrier to monitor the BFR response message.

[0347] Optionally, the terminal device determines the target BWP for receiving the BFR response message on the target downlink carrier through the configuration information of the network device, and the configuration information includes information for indicating the association relationship between the BWP in the target uplink carrier and the BWP in the target downlink carrier, or the configuration information includes information for indicating the location of the BWP for the terminal device to receive the BFR response message.

[0348] Optionally, in this embodiment, the target downlink carrier for monitoring the BFR response message and the target BWP on the target downlink carrier for monitoring the BFR response message can both be configured by the network device for the terminal device, and can be configured separately or together.

[0349] For example, the network device sends configuration information to the terminal device, which carries an uplink and downlink carrier association relationship, including an association relationship between a target uplink carrier and a target downlink carrier, and also includes an association relationship between a BWP on the target uplink carrier and a BWP on the target downlink carrier.

[0350] Therefore, in the embodiment of the present application, even when the uplink carrier on which the BFRQ message is sent corresponds to multiple downlink carriers, the terminal device can also determine the downlink carrier for monitoring the BFR response message.

[0351] Optionally, in some embodiments, if the two uplink carriers of the terminal device are not QCL, for example, carrier 1 is a low-frequency carrier and carrier 2 is a high-frequency carrier, the beam failure recovery in this case can be called cross-carrier beam failure recovery. Cross-carrier beam failure recovery can be performed according to the following process.

[0352] 1) The network equipment configures the association between the downlink carrier and the uplink RACH resources.

[0353] For example, the network device configures the association relationship between the RACH resource on carrier 1 and the downlink signal (candidate beam) of carrier 2. The network device may configure the association relationship through an RRC message.

[0354] 2) Beam failure occurred on carrier 2.

[0355] 3) The terminal device searches for a new candidate beam on carrier 2. The physical layer of the terminal device reports the beam that meets the conditions to the MAC (medium access control) layer of the terminal device.

[0356] 4) The terminal device initiates a BFRQ message using the RACH resource on carrier 1. Four time slots after sending the BFRQ message, the terminal device starts to listen to the response of the network device on carrier 2, that is, a PDCCH in a window on carrier 2, where the cyclic redundancy code (CRC) is scrambled using the cell radio network temporary identifier (C-RNTI).

[0357] 5) When the network device receives the BFRQ message from the terminal device on carrier 1, it can be determined that a beam failure has occurred in the terminal device on carrier 2, and the new beam requested by the terminal device can be determined by the previous association between the RACH resource and the beam.

[0358] Therefore, this embodiment proposes a beam failure recovery solution that sends a BFRQ message on a high frequency carrier (or a low frequency carrier) and detects a BFR response message on a low frequency carrier (or a high frequency carrier).

[0359] The above cross-carrier beam failure recovery process can be applied to the following two scenarios.

[0360] 1) Carrier 2 has no associated or corresponding uplink carrier; or has no corresponding uplink transmission resources or PRACH resources.

[0361] 2) Carrier 1 is a low-frequency uplink carrier. Since the low-frequency uplink coverage is better, the corresponding RACH success rate is higher.

[0362] Optionally, in some embodiments, if the two uplink carriers of the terminal device are QCL, for example, carrier 1 and carrier 2 are QCL, and carrier 1 and carrier 2 operate in a high frequency band, the beam failure recovery in this case can also be referred to as cross-carrier beam failure recovery. The cross-carrier beam failure recovery can be performed according to the following process.

[0363] 1) The network equipment configures the association between the downlink carrier and the uplink RACH resources.

[0364] For example, the network device configures the association relationship between the RACH resource on carrier 1 and the downlink signal (candidate beam) of carrier 2. The network device may configure the association relationship through an RRC message.

[0365] 2) If the reference signals for beam failure detection (BFD) on carrier 1 and carrier 2 have a QCL relationship, then beam failure detection can be performed on both carrier 1 and carrier 2. The calculation of beam failure instance should include the beam failure detection results on both carriers.

[0366] 3) When the result of the beam failure detection is beam failure, the terminal device can perform candidate beam detection on both carrier 1 and carrier 2.

[0367] 4) The MAC layer of the terminal device selects the corresponding RACH resource.

[0368] Optionally, if there are multiple beams that meet the conditions, the terminal device can select the random access resource (RACH occasion, RO) that is closest in time, which can speed up the BFR process.

[0369] 5) Based on the configuration of its own MAC layer, the physical layer of the terminal device can send RACH msg1 on carrier 1 to request beam failure recovery. After 4 time slots, the terminal device starts to receive the BFR response message from the network device on the same carrier.

[0370] For example, the BFR response message of the network device may be a PDCCH, where the CRC is scrambled by the C-RNTI.

[0371] Therefore, this embodiment proposes a beam failure recovery solution that sends a BFRQ message on a high frequency carrier and detects a BFR response message on a high frequency carrier.

[0372] The various embodiments described herein may be independent solutions or may be combined according to internal logic, and all of these solutions fall within the protection scope of this application.

[0373] It can be understood that in the above-mentioned method embodiments, the methods and operations implemented by the terminal device can also be implemented by components that can be used for the terminal device (such as chips or circuits), and the methods and operations implemented by the network device can also be implemented by components that can be used for the network device (such as chips or circuits).

[0374] The above describes the method embodiment provided by the embodiment of the present application, and the following describes the device embodiment provided by the embodiment of the present application. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment, so the content not described in detail can be referred to the method embodiment above, and for the sake of brevity, it will not be repeated here.

[0375] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of interaction between various network elements. It can be understood that each network element, such as a transmitting device or a receiving device. In order to achieve the above functions, it includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed in this document, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0376] The embodiment of the present application can divide the functional modules of the transmitting end device or the receiving end device according to the above method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module corresponding to each function.

[0377] like Figure 8 As shown, the embodiment of the present application further provides a communication device 800, which can be a terminal device or a component (such as a chip or circuit) that can be used for a terminal device. The communication device 800 includes a processing unit 810 and a sending unit 820, the processing unit 810 is used to execute the processing steps on the terminal device side in the above method embodiment, and the sending unit 820 is used to execute the sending steps on the terminal device side in the uplink method embodiment.

[0378] The operations or implementations of the processing unit 810 and the sending unit 820 may refer to the relevant descriptions in the method embodiments, which will not be repeated here.

[0379] The processing unit 810 may be implemented by a processor or a processor-related circuit.

[0380] The sending unit 820 may be implemented by a transmitter or a transmitter-related circuit.

[0381] Optionally, the communication device 800 may further include a receiving unit, which is used to perform the receiving step on the terminal device side in the above method embodiment. The receiving unit may be implemented by a receiver or a receiver-related circuit.

[0382] The sending unit 820 and the receiving unit in the communication device 800 can be integrated into a transceiver unit, which is not limited in the embodiment of the present application.

[0383] The embodiment of the present application further provides a first communication device, which can be a terminal device or a chip. The first communication device can be used to execute the action executed by the terminal device in the above method embodiment.

[0384] When the first communication device is a terminal device, Fig. 9 A simplified schematic diagram of the structure of a terminal device is shown. For ease of understanding and illustration, Fig. 9 In this article, a mobile phone is used as an example of a terminal device. Fig. 9As shown, the terminal device includes a processor, a memory, a radio frequency circuit, an antenna, and an input-output device. The processor is mainly used to process communication protocols and communication data, as well as to control the terminal device, execute software programs, or process the data of software programs. The memory is mainly used to store software programs and data. The radio frequency circuit is mainly used for converting baseband signals and radio frequency signals and processing radio frequency signals. The antenna is mainly used to send and receive radio frequency signals in the form of electromagnetic waves. Input-output devices, such as touch screens, display screens, keyboards, etc., are mainly used to receive data input by users and output data to users. It should be noted that some types of terminal devices may not have input-output devices.

[0385] When data needs to be sent, the processor performs baseband processing on the data to be sent and outputs the baseband signal to the RF circuit. The RF circuit performs RF processing on the baseband signal and then sends the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the terminal device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data. For ease of explanation, Fig. 9 Only one memory and processor are shown. In an actual terminal device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device. The memory may be set independently of the processor or may be integrated with the processor, and the embodiments of the present application do not limit this.

[0386] In the embodiment of the present application, the antenna and the radio frequency circuit with transceiver functions can be regarded as the transceiver unit of the terminal device, and the processor with processing function can be regarded as the processing unit of the terminal device.

[0387] like Fig. 9 As shown, the terminal device includes a transceiver unit 901 and a processing unit 902. The transceiver unit 902 may also be referred to as a transceiver, a transceiver, a transceiver device, etc. The processing unit 901 may also be referred to as a processor, a processing board, a processing module, a processing device, etc. Optionally, the memory may be located in the processing unit 901, and may be independent of the processing unit 901 (for example, in Fig. 9 In the embodiment of the present invention, the memory is independent of the processing unit 901). Optionally, the device used to implement the receiving function in the transceiver unit 901 can be regarded as a receiving unit, and the device used to implement the sending function in the transceiver unit 901 can be regarded as a sending unit, that is, the transceiver unit 901 includes a receiving unit and a sending unit. The transceiver unit may also be sometimes referred to as a transceiver, a transceiver, or a transceiver circuit. The receiving unit may also be sometimes referred to as a receiver, a receiver, or a receiving circuit. The sending unit may also be sometimes referred to as a transmitter, a transmitter, or a transmitting circuit.

[0388] For example, in one implementation, the processing unit 902 is configured to execute Figure 3 The step S310 in the embodiment of the present application and / or the processing unit 902 is also used to execute other processing steps on the terminal device side. The transceiver unit 901 is used to execute Figure 3 Step S320 in the embodiment of the present application, and / or the transceiver unit 901 is also used to execute other transceiver steps on the terminal device side.

[0389] For another example, in another implementation, the transceiver unit 901 is used to execute Figure 4 In step S404, or step S408, or step S411, or the sending operation on the terminal device side in step S413, the transceiver unit 901 is used to perform Figure 4 The terminal device receives the operation in step S414, and / or the transceiver unit 901 is also used to perform other transceiver steps on the terminal device side in the embodiment of the present application. The processing unit 902 is used to perform Figure 4 Processing operations on the terminal device side, for example, steps S401, S402 and other processing steps.

[0390] For example, in another implementation, the transceiver unit 901 is used to execute Figure 5 In step S504, or S507, or S511, or the sending step of the terminal device side in S513, the transceiver unit 901 is also used to perform Figure 5 The receiving step on the terminal device side in step S514 in the above, and / or the transceiver unit 901 is also used to perform other transceiver steps on the terminal device side in the embodiment of the present application. The processing unit 902 is used to perform Figure 5 Other processing steps on the terminal device side in.

[0391] For example, in another implementation, the transceiver unit 901 is used to execute Figure 6 In the step S610 of the terminal device side, the transceiver unit 901 is also used to perform Figure 6 The receiving step on the terminal device side in step S630 in the above, and / or the transceiver unit 901 is also used to perform other transceiver steps on the terminal device side in the embodiment of the present application. The processing unit 902 is used to execute Figure 6 The processing steps of step S620 in the process, and / or other processing steps on the terminal device side of the processing unit 902.

[0392] It is understandable that the terminal device including the transceiver unit and the processing unit may not rely on Fig. 9 The structure shown.

[0393] When the first communication device is a chip, the chip includes a transceiver unit and a processing unit, wherein the transceiver unit may be an input / output circuit or a communication interface; and the processing unit may be a processor or a microprocessor or an integrated circuit integrated on the chip.

[0394] It should be understood that Fig. 9 This is for illustration only and not limitation.

[0395] It can be understood that the operation or implementation of each unit / module in the above communication device can further refer to the relevant description in the method embodiment, which will not be repeated here.

[0396] The present application also provides a communication device, which may be a network device or a chip. Figure 8 The structure (will Figure 8 The sending unit in the communication device is replaced by a transceiver unit), and the communication device includes a processing unit and a transceiver unit. The processing unit is used to execute the processing steps on the network device side in the above method embodiment, for example, generating configuration information on the terminal device side. The transceiver unit is used to execute the receiving and sending steps on the network device side in the above method embodiment, for example, receiving a BFRQ message sent by the terminal device, sending a BFR response message to the terminal device, or sending uplink resource configuration information to the terminal device. Among them, the processing unit can be implemented by a processor or a processor-related circuit. The transceiver unit can be implemented by a transceiver or a transceiver-related circuit.

[0397] The embodiment of the present application further provides a second communication device, which can be a network device or a chip. The second communication device can be used to execute the action executed by the network device in the above method embodiment.

[0398] When the second communication device is a network device, for example, it is a base station. Fig.10 A simplified schematic diagram of the base station structure is shown. The base station includes part 1001 and part 1002. Part 1001 is mainly used for receiving and transmitting radio frequency signals and converting radio frequency signals into baseband signals; part 1002 is mainly used for baseband processing, controlling the base station, etc. Part 1001 can generally be referred to as a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, etc. Part 1002 is generally the control center of the base station, which can generally be referred to as a processing unit, and is used to control the base station to execute the action of the network device generating the first message in the above method embodiment. For details, please refer to the description of the above relevant parts.

[0399] Optionally, the memory may be integrated into the processing unit, i.e., integrated into Fig.10 1002 shown in the Fig.10 Alternatively, the memory may be independent of the processing unit, that is, independent of Fig.10Outside of the 1002 portion shown.

[0400] The transceiver unit of part 1001 may also be referred to as a transceiver, or a transceiver, etc., which includes an antenna and a radio frequency unit, wherein the radio frequency unit is mainly used for radio frequency processing. Optionally, the device used to implement the receiving function in part 1001 may be regarded as a receiving unit, and the device used to implement the sending function may be regarded as a sending unit, that is, part 1001 includes a receiving unit and a sending unit. The receiving unit may also be referred to as a receiver, a receiver, or a receiving circuit, etc., and the sending unit may be referred to as a transmitter, a transmitter, or a transmitting circuit, etc.

[0401] Part 1002 may include one or more boards, each of which may include one or more processors and one or more memories, and the processor is used to read and execute the program in the memory to realize the baseband processing function and the control of the base station. If there are multiple boards, each board can be interconnected to increase the processing capacity. As an optional implementation, multiple boards may share one or more processors, or multiple boards may share one or more memories, or multiple boards may share one or more processors at the same time.

[0402] For example, in one implementation, the transceiver unit is used to execute Figure 3 The receiving operation on the network device side in step 320, and / or the transceiver unit is also used to perform other transceiver steps on the network device side in the embodiment of the present application. The processing unit is used to perform other processing steps on the network device side in the embodiment of the present application.

[0403] For another example, in another implementation, the transceiver unit is used to execute Figure 4 The receiving operation on the network device side in step S404, or step S408, or step S411, or step S413 in the above step, the transceiver unit is also used to perform Figure 4 The sending operation on the network device side in step S414, and / or other steps in the present application. The processing unit is used to execute the processing steps on the network device side in the embodiment of the present application, such as generating configuration information of the terminal device.

[0404] For example, in another implementation, the transceiver unit is used to execute Figure 5 The receiving operation on the network device side in S504, or S507, or S511, or S513 in the above, the transceiver unit is also used to perform Figure 5 The sending operation on the network device side in step S514, and / or other steps in the present application. The processing unit is used to execute the processing steps on the network device side in the embodiment of the present application, such as generating configuration information of the terminal device.

[0405] For example, in another implementation, the transceiver unit is used to execute Figure 6The receiving operation on the network device side in S610, the transceiver unit is also used to perform Figure 6 The sending operation on the network device side in step S630, and / or other steps in the present application. The processing unit is used to execute the processing steps on the network device side in the embodiment of the present application, such as generating configuration information of the terminal device.

[0406] It is understandable that the network device including the transceiver unit and the processing unit may not rely on Fig.10 The structure shown.

[0407] When the second communication device is a chip, the chip includes a transceiver unit and a processing unit, wherein the transceiver unit may be an input / output circuit or a communication interface; and the processing unit may be a processor or a microprocessor or an integrated circuit integrated on the chip.

[0408] It can be understood that the operation or implementation of each module in the above communication device can further refer to the relevant description in the method embodiment, which will not be repeated here.

[0409] In an embodiment of the present application, a terminal device or a network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through a process, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. The application layer includes applications such as a browser, an address book, a word processing software, and an instant messaging software. In addition, the embodiment of the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application, as long as it can communicate according to the method provided in the embodiment of the present application by running a program that records the code of the method provided in the embodiment of the present application, for example, the execution subject of the method provided in the embodiment of the present application can be a terminal device or a network device, or a functional module in a terminal device or a network device that can call a program and execute a program.

[0410] In addition, various aspects or features of the present application can be implemented as methods, devices or products using standard programming and / or engineering techniques. The term "product" used in this application covers computer programs that can be accessed from any computer-readable device, carrier or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks or tapes, etc.), optical disks (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards and flash memory devices (e.g., erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.). In addition, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing and / or carrying instructions and / or data.

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

[0412] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0413] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0415] In addition, each functional unit in each embodiment of the present application 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.

[0416] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks or optical disks.

[0417] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for determining uplink resources, characterized in that: The method is applied to a new air interface system, the system supports a supplementary uplink carrier technology, and the method includes: Determine a target uplink resource from resources on multiple uplink carriers; Using the target uplink resource, sending a beam recovery request to a network device; The determining the target uplink resource from the resources on the multiple uplink carriers includes: When at least one uplink carrier among the multiple uplink carriers has a non-contention resource, determining the non-contention resource on the uplink carrier as the target uplink resource; The multiple uplink carriers include a primary uplink carrier and a supplementary uplink carrier of the current cell, the primary uplink carrier is a high frequency uplink carrier of the new air interface system, and the frequency of the primary uplink carrier is higher than the frequency of the supplementary uplink carrier; When at least one uplink carrier among the multiple uplink carriers has a non-contention resource, determining the non-contention resource on the uplink carrier as the target uplink resource includes: When the at least one uplink carrier includes the primary uplink carrier, a non-contention resource on the primary uplink carrier is determined as the target uplink resource.

2. The method according to claim 1, characterized in that The multiple uplink carriers include a currently operating primary uplink carrier and a supplementary uplink carrier; and determining a target uplink resource from resources on the multiple uplink carriers includes: When there are no available non-contention resources on the multiple uplink carriers, the contention resources on the supplementary uplink carrier are determined as the target uplink resources.

3. The method according to claim 1, characterized in that The multiple uplink carriers include a primary uplink carrier and a supplementary uplink carrier of the current primary cell, and an uplink carrier of the secondary cell; The determining the target uplink resource from the resources on the multiple uplink carriers includes: When there is no available non-contention resource on the primary uplink carrier of the primary cell, determining the non-contention resource on the uplink carrier of the secondary cell as the target uplink resource; or When neither the primary uplink carrier nor the supplementary uplink carrier of the primary cell has available non-contention resources, resources on the uplink carrier of the secondary cell are determined as the target uplink resources.

4. The method according to any one of claims 1 to 3, characterized in that The target uplink resource includes a contention resource, and the method further includes: receiving an association relationship between an uplink carrier and a downlink carrier from the network device; Using the downlink carrier associated with the uplink carrier where the target uplink resource is located, receiving the beam recovery response message sent by the network device.

5. The method according to any one of claims 1 to 4, characterized in that The non-contention resources include uplink resources used to transmit uplink data.

6. The method according to claim 4, characterized in that include: A target downlink carrier for receiving a beam failure recovery response message is determined according to an index of a cell where the uplink carrier is located or an index of a cell where the downlink carrier is located.

7. A communication device, characterized in that: The method comprises a unit for implementing the method according to any one of claims 1 to 6.

8. A communication device, characterized in that: The invention comprises a memory and a processor, wherein the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory, and the execution of the instructions stored in the memory enables the processor to execute the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a computer, the computer is caused to execute the method according to any one of claims 1 to 6.

10. A communication device, characterized in that: The method comprises a processor configured to execute the method as claimed in any one of claims 1 to 6.

11. A computer program product, characterized in that The invention comprises instructions, which, when executed by a computer, enable the method according to any one of claims 1 to 6 to be performed.