RU2795935C1 - Wireless communication method, terminal device and network device - Google Patents

Abstract

FIELD: communication technologies.

SUBSTANCE: as part of the wireless communication method, in response to a beam failure occurring in a secondary cell, the terminal device generates a scheduling request to request an uplink resource from the network device. The response message specifies the first resource. The terminal apparatus transmits beam failure information of the secondary cell via a medium access layer (MAC) control element (CE) on the first resource. The scheduling request corresponds to the first configuration, which is the configuration of the scheduling request associated with at least one logical channel. The configuration sent by the network device is the second scheduling request configuration not associated with the logical channel, and the scheduling request ID of the second configuration is different from the scheduling request ID corresponding to the scheduling request configuration associated with the logical channel.

EFFECT: ability to avoid a conflict between the configuration sent by the network device and the configuration of the existing scheduling request SR of the logical channel, thereby simplifying the processing of the configuration and SR.

16 cl, 11 dwg

Description

FIELD OF TECHNOLOGY TO WHICH THE INVENTION RELATES

[0001] Embodiments of the present disclosure relate to the field of communication technologies and, more specifically, to a wireless communication method, a terminal device, and a network device.

BACKGROUND OF THE INVENTION

[0002] In the communication standard, a beam failure recovery (BFR) procedure for a secondary cell (SCell) has not yet been defined.

SUMMARY OF THE INVENTION

[0003] Embodiments of the present disclosure provide a wireless communication method, a terminal device, and a network device that can perform a BFR SCell procedure.

[0004] In a first aspect, a wireless communication method is provided, including: in response to a beam failure occurring in a secondary cell, generating a request message by a terminal device; wherein the request message corresponds to a first configuration or a second configuration, the first configuration is a scheduling request configuration associated with at least one logical channel, and the second configuration is a scheduling request configuration not associated with a logical channel.

[0005] In a second aspect, a wireless communication method is provided, including: receiving, by a network device, a request message transmitted from a terminal device in response to a beam failure occurring in a secondary cell, the request message corresponding to a first configuration or a second configuration, wherein the first configuration is a configuration of a scheduling request associated with at least one logical channel, and the second configuration is a configuration of a scheduling request not associated with a logical channel.

[0006] In a third aspect, a communication device is provided, including a processor and a memory. The memory is adapted to store a computer program, and the processor is configured to call and execute the computer program stored in the memory to perform the method in the first or second aspect, or any of the embodiments described above.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] FIG. 1 is a schematic diagram of an application scenario provided by embodiments of the present disclosure;

[0008] FIG. 2 is a schematic diagram of a wireless communication method provided by one embodiment of the present disclosure;

[0009] Fig. 3 is a schematic diagram of a wireless communication method provided by another embodiment of the present disclosure;

[0010] Fig. 4 is a schematic diagram of a wireless communication method provided by another embodiment of the present disclosure;

[0011] FIG. 5 is a schematic block diagram of a terminal device provided by one embodiment of the present disclosure;

[0012] FIG. 6 is a schematic block diagram of a terminal device provided by another embodiment of the present disclosure;

[0013] FIG. 7 is a schematic block diagram of a network device provided by one embodiment of the present disclosure;

[0014] FIG. 8 is a schematic block diagram of a network device provided by another embodiment of the present disclosure;

[0015] FIG. 9 is a schematic block diagram of a communication device provided by one embodiment of the present disclosure;

[0016] Fig. 10 is a schematic block diagram of a chip according to an embodiment of the present disclosure; And

[0017] FIG. 11 is a schematic block diagram of a communication system provided by one embodiment of the present disclosure.

DETAILED DESCRIPTION

[0018] The technical solutions in the embodiments of the present disclosure will be described below with reference to the accompanying drawings in the embodiments of the present disclosure. Apparently, the described embodiments are part of the embodiments of the present disclosure, but not all embodiments. Based on the embodiments in this disclosure, all other embodiments obtained by one of ordinary skill in the art without creative effort should fall within the scope of protection in this disclosure.

[0019] The technical solutions according to the embodiments of the present disclosure can be applied to various communication systems such as Global System for Mobile Communications (abbreviated as "GSM"), Code Division Multiple Access (abbreviated as "CDMA"), Wideband Multiple Access system Code Division (WCDMA for short), General Packet Radio Service (GPRS for short), Long Term Evolution Standard (LTE for short), LTE Frequency Division Duplex ("FDD" for short), Full Duplex System LTE time division communications (“TDD” for short), universal mobile communication system (“UMTS” for short), worldwide interoperability communication system for microwave access (“WiMAX” for short), 5G system, or the like.

[0020] As shown in FIG. 1, terminal device 110 is connected to a first network device 130 in a first communication system and a second network device 120 in a second communication system. For example, the first network device 130 is a Long Term Evolution (LTE) network device, and the second network device 120 is a new radio (NR) network device.

[0021] Under the first network device 130 and the second network device 120, there are many cells.

[0022] It should be understood that Fig. 1 is an example of a communication system according to an embodiment of the present disclosure, and this embodiment of the present disclosure is not limited to that shown in Fig. 1.

[0023] For example, a communication system to which an embodiment of the present disclosure is adapted may include at least a plurality of network devices within a first communication system and/or a plurality of network devices within a second communication system.

[0024] For example, system 100 shown in FIG. 1 may include a primary network device in a first communication system and at least one secondary network device in a second communication system. The at least one secondary network device is respectively connected to the primary network device to form a plurality of connections, and is accordingly connected to the terminal device 110 to provide services to the terminal device. In particular, the terminal device 110 may simultaneously establish connections through the primary network device and the secondary network device.

[0025] Optionally, a connection established between terminal device 110 and a primary network device is a primary connection, and a connection established between terminal device 110 and a secondary network device is a secondary connection. The control signaling of the terminal device 110 may be transmitted over the primary connection, while the data of the terminal device 110 may be transmitted simultaneously over the primary connection and the secondary connection, or may be transmitted over the secondary connection only.

[0026] As another example, the first communication system and the second communication system in the embodiments of the present disclosure are different, but the specific type of the first communication system and the second communication system is not limited.

[0027] For example, the first communication system and the second communication system may be different communication systems such as: GSM system, CDMA system, WCDMA system, GPRS system, LTE system, TDD and UMTS system, etc.

[0028] The primary network device and the secondary network device may be any access network device.

[0029] Optionally, in some embodiments, the network access device may be a base station (base transceiver station, BTS) in a GSM system or a CDMA system, or a NodeB (NB) in a WCDMA system, or an evolved Node B (eNB or eNodeB) in the LTE system.

[0030] According to some embodiments, the access network device may also be a next generation radio access network (NG RAN), a base station (gNB) in a NR system, or a wireless controller in a cloud radio access network (CRAN). Or, the network access device may be a relay station, an access point, a vehicle-based device, a wearable device, or a network device in a public land mobile network (PLMN) of the future, etc.

[0031] In the system 100 shown in FIG. 1, an implementation is taken as an example in which the first network device 130 serves as the primary network device and the second network device 120 serves as the secondary network device.

[0032] The first network device 130 may be an LTE network device, and the second network device 120 may be an NR network device. Or, the first network device 130 may be an NR network device and the second network device 120 may be an LTE network device. Or, both the first network device 130 and the second network device 120 may be an NR network device. Or, the first network device 130 may be a GSM network device, a CDMA network device, and so on, and the second network device 120 may also be a GSM network device, a CDMA network device, and so on. Or, the first network device 130 may be a macro cell, and the second network device 120 may be a micro cell, pico cell, femto cell, or the like.

[0033] In accordance with some embodiments, terminal device 110 may be any terminal device, and terminal device 110 includes, but is not limited to:

[0034] a device that is capable of receiving or transmitting communication signals over wired connections, such as public switched telephone networks (PSTN), digital subscriber lines (DSL), digital cables, direct cable connections, and/or other connections/networks for data transmission; and/or via wireless interfaces such as wireless interfaces configured for cellular networks, wireless local area networks (WLANs) such as DVB-H digital television networks, satellite networks, AM-FM broadcast transmitters and/or other terminal and/or Internet of Things (IoT) device. A terminal device configured to communicate via a wireless interface may be referred to as a "wireless terminal", "wireless terminal", or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellites or cell phones; personal communication system (PCS) terminals, which may combine cellular radiotelephones with data processing, facsimile and data communication functions; PDA, which includes cordless phones, pagers, Internet/Intranet access, web browser, notepad, calendar and/or global positioning system (GPS) receiver; and conventional portable and/or pocket receivers or other electronic devices, including radiotelephone transceivers. A terminal may refer to access terminals, user equipment (UEs), user devices, user stations, mobile stations, mobile platforms, remote stations, remote terminals, mobile device, user terminals, terminals, wireless communications device, user agents, or user devices. The access terminal may be cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless LAN (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless capabilities, computing devices, or other processing devices connected to a wireless networks. modems, in-vehicle devices, wearable devices, terminals in 5G networks or terminals in the future, advanced PLMNs, etc.

[0035] It should be understood that the terms "system" and "network" in this document can often be used interchangeably. The term "and/or" in this document defines only an association relationship that describes the associated objects, and means that there can be three relationships. For example, A and/or B could mean that: Only A exists, A and B exist at the same time, and only B exists. Also, the "/" character here usually indicates that the first and last associated objects are in an "or" relationship .

[0036] In the system, the beam is realized through the corresponding reference signal resource, for example, by measuring the channel state information (RS-CSI) reference signal resource and/or the synchronization signal/physical broadcast channel block (SS/PBCH block). Therefore, in the preceding and following descriptions, the word beam is often used directly for brevity, but it actually refers to the corresponding RS-CSI resource and/or SS/PBCH block.

[0037] In embodiments of the present disclosure, an appropriate BFR procedure may be designed according to the characteristics of the SCell itself. For example, when the quality of the SCell link deteriorates, a primary cell (PCell) or a primary secondary cell (PSCell) corresponding to the terminal apparatus may be used for communication.

[0038] In embodiments of the present disclosure, the BFR procedure may sometimes be referred to as a Beam Failure Request (BFRQ) procedure.

[0039] Based on this, for example, a message for requesting a resource may be transmitted via the PCell or PSCell of the terminal device or other SCells to the network device to convey beam failure information of the particular SCell on the requested resource. Alternatively, via PCell or PSCell of the terminal device or other SCells, a Physical Uplink Control Channel (PUCCH) resource configured by the network device is used to transmit a request message, or a Physical Uplink Shared Channel (PUSCH) resource is used to transmit a control element. (CE) Media Access Control (MAC). The MAC CE carries information related to the beam failure of a particular SCell and/or corresponding information about a new potentially suitable beam.

[0040] In embodiments of the present disclosure, in the event that a beam failure occurs in a particular SCell, the terminal device may generate a request message that may be used to request an uplink transmission resource from the network device or notify the network device that the beam failure occurs in the SCell of the terminal device. After receiving the request message transmitted from the terminal device, the network device may allocate a resource to the terminal device, so that the terminal device may transmit SCell beam failure information to the network device on the allocated resource. In addition, transmission of beam failure information may take precedence over transmission of other data or information, thereby reducing the delay of the BFR procedure.

[0041] FIG. 2 is a flow diagram of a wireless communication method 200 provided by an embodiment of the present invention. Method 200 may be performed by a terminal device in the communication system shown in FIG. As shown in FIG. 2, method 200 may include step 210.

[0042] In step 210, in response to a beam failure occurring in the secondary cell, the terminal device generates a request message.

[0043] FIG. 3 is a flow diagram of a wireless communication method 300 provided by another embodiment of the present invention. As shown in FIG. 3, method 300 may include steps 310-330.

[0044] In step 310, in response to a beam failure occurring in the secondary cell, the terminal device generates a request message.

[0045] In step 320, the terminal device sends a request message to the network device.

[0046] In step 330, the network device receives a request message.

[0047] The request message corresponds to a first configuration or a second configuration, the first configuration is a scheduling request configuration associated with at least one logical channel, and the second configuration is a scheduling request configuration not associated with a logical channel.

[0048] In embodiments of the present disclosure, the request message generated by the terminal device may be a BFR request message, and the BFR request message is a scheduling request (SR). If a beam failure occurs in the SCell of the terminal device, the terminal device may communicate with the network device based on its SR configuration, and the configuration corresponding to the request message may be the first configuration mentioned above.

[0049] The configuration corresponding to the request message may also be a configuration other than the SR configuration, and may be a configuration further indicated by the network device to the terminal device, and the configuration may not be associated with any logical channel. If a beam failure occurs in the SCell of the terminal device, the terminal device may communicate with the network device based on the configuration, and the configuration corresponding to the request message may be the second configuration mentioned above.

[0050] For PCell or PSCell, if a beam failure occurs in the terminal device's PCell or PSCell, the terminal device may select a Physical Random Access Channel (PRACH) from contention random access resources to initiate transmission.

[0051] Optionally, in some embodiments, the configuration further indicated by the network device to the terminal device may also be referred to as the SR configuration. That is, although the configuration further indicated by the network device to the terminal device may not be associated with a logical channel, some or all types of configuration parameters may be the same as the SR configuration. Therefore, the configuration may also be referred to as an SR configuration, and the terminal device can still communicate with the network device based on this configuration.

[0052] In the wireless communication method provided by the embodiments of the present disclosure, in the case where a beam failure occurs in a SCell, the terminal device may generate a request message according to the first configuration or the second configuration, and may perform the BFR procedure of the secondary cell.

[0053] The first configuration is a scheduling request configuration associated with at least one logical channel, indicating that the request message configuration can reuse the logical channel scheduling request configuration, which can reduce the complexity of communication standards and reduce the implementation complexity of the terminal device.

[0054] Alternatively, the second configuration is a scheduling request configuration not associated with a logical channel, and thus a conflict between the request message configuration and the logical channel scheduling request configuration can be avoided, and the processing of the request message and the scheduling request can be simplified.

[0055] Optionally, in some embodiments, a request message is used to request an uplink transmission resource from a network device and/or notify the network device that a beam failure has occurred in a secondary cell.

[0056] In embodiments of the present disclosure, if the terminal device sends a request message to the network device, in one embodiment, the request message may be used to request an uplink transmission resource from the network device. After receiving the request message, the network device may allocate the resource to the terminal device. The terminal device may transmit SCell beam failure information to the network device based on the allocated resource.

[0057] In another implementation, a request message may be used to notify a network device that a beam failure occurs in the SCell. After receiving the request message, the network device may allocate a resource to the terminal device based on a predetermined rule, so that the terminal device may send SCell failure information to the network device based on the allocated resource. The predetermined rule may be a rule agreed upon in advance by the terminal device and the network device, that is, the network device allocates a resource to the terminal device after receiving a request message informing it that a beam failure has occurred. The predefined rule may also be implemented by the network device itself.

[0058] The uplink transmission resource in embodiments of the present disclosure may be a PUSCH resource. It should be understood that in the case that a beam failure occurs in a SCell of a terminal device, if the terminal device needs to transmit the beam failure information of the SCell to the network device, since the beam failure occurs in the SCell of the terminal device, the terminal device may first send a request message to the network device. through the PUCCH resource based on the PCell or PSCell or other SCell of the terminal device to request the PUSCH resource from the network device. After receiving the request message, the network device may allocate a PUSCH resource to the terminal device, and the terminal device may transmit SCell beam failure information to the network device via the PUSCH resource. Optionally, the step of transmitting the request message to the network device via the PUCCH resource may be omitted.

[0059] Specific SCell beam failure information in embodiments of the present disclosure may be transmitted via a MAC CE. The SCell beam failure information may indicate a cell on which a beam failure occurs, a beam on which a beam failure occurs, or a new beam. The SCell beam failure information may also indicate that the beam does not meet the specified condition.

[0060] As indicated above, the configuration of the request message may correspond to the first configuration or the second configuration. In the following, the corresponding BFR procedures will be presented, respectively, in the case of a request message configuration corresponding to these two configurations.

[0061] Optionally, in the case where the configuration corresponding to the request message is the first configuration, the first configuration may be determined from a set of configurations based on at least one of the following: a network device identifier, a scheduling request identifier corresponding to each configurations in the configuration set, a resource identifier corresponding to each configuration in the configuration set, and a priority order of logical channels corresponding to the corresponding configurations in the configuration set. Alternatively, the first configuration is randomly selected from the set of configurations.

[0062] The set of configurations includes a configuration of at least one scheduling request, and each scheduling request corresponds to at least one logical channel.

[0063] In embodiments of the present disclosure, a request message configuration may be selected from a set of configurations. During the selection process of the first configuration, the selection may be made based on various criteria or rules. For example, the network device indication information may indicate a configuration in a configuration set as a request message configuration; or the request message configuration may also be selected based on the SR ID corresponding to each configuration in the configuration set or the SR resource ID corresponding to each configuration; or the request message configuration may also be selected based on the order of priority of the logical channels corresponding to the corresponding configurations in the configuration set; or the request message configuration may also be a configuration arbitrarily selected by the terminal device from the configuration set.

[0064] In embodiments of the present disclosure, a logical channel corresponding to a configuration may refer to a logical channel associated with a scheduling request configuration.

[0065] The SR identifier or SR resource identifier in embodiments of the present disclosure may be a sequence, and the terminal device may select a request message configuration according to the SR identifier or SR resource identifier.

[0066] It should be understood that in embodiments of the present disclosure, each configuration in a configuration set may be associated with at least one logical channel, and different logical channels may carry different data. Therefore, the first configuration can be determined in accordance with the priorities of the various logical channels.

[0067] In embodiments of the present disclosure, each configuration in a configuration set may include a corresponding SR identifier, a timer, and a maximum number of transmissions. For example, the timer may be used to control the transmission interval of the request message over the PUCCH resource, and the maximum number of transmissions may be the maximum number of transmissions of the request message over the PUCCH resource. The resource configuration corresponding to each configuration in the configuration set may include: what the SR is associated with, the period and location in the time domain, and the PUCCH resource. What the SR is associated with may allow the SR to transmit a message based on the corresponding resource configuration, and the time domain period may be a PUCCH resource usage time interval. If the corresponding resource configuration in the configuration includes one PUCCH resource, the terminal device may use the PUCCH resource to send a request message to the network device.

[0068] It has been briefly explained above that the network device may determine the first configuration from the set of configurations based on various criteria or rules, which will be described in detail below.

[0069] Optionally, in some embodiments, the network device indication information is indicated by configuration information related to the BFR.

[0070] During the BFR, the network device may indicate the configuration of the request message via the BFR configuration information. For example, an information element (IE) (also referred to as a field) in the BFR configuration information may be used to indicate a configuration in a configuration set as a request message configuration, ie, the first configuration.

[0071] For example, if the configuration set includes 5 SR configurations, namely, SR0 configuration, SR1 configuration, SR2 configuration, SR3 configuration, SR4 configuration, the IE in the BFR configuration information may indicate that the configuration corresponding to SR1 is the first configuration, and then the terminal device may generate an appropriate request message based on the SR1 configuration and/or transmit the request message to the network device via its corresponding PUCCH resource.

[0072] It should be understood that the IE in the BFR configuration information indicating that the SR1 configuration is the first configuration is only an example for illustration and should not impose any limitation on the present disclosure, and the configuration corresponding to other SRs as the first can also be indicated. configuration.

[0073] Optionally, the first configuration is a configuration in the configuration set that satisfies the following condition: the scheduling request ID corresponding to the configuration is the largest or the smallest, or the resource ID of the scheduling request corresponding to the configuration is the largest or the smallest.

[0074] In embodiments of the present disclosure according to the SR ID corresponding to the SR configuration, the request message configuration may be determined from a configuration set, i.e., a first configuration. For example, the largest SR ID corresponding to the SR configuration or the smallest SR ID corresponding to the SR configuration may be defined as the first configuration.

[0075] For example, if the configuration set includes 5 SR configurations, namely, SR0 configuration, SR1 configuration, SR2 configuration, SR3 configuration, and SR4 configuration, then the corresponding SR IDs will be 0, 1, 2, 3, 4, respectively. The terminal device may send a request message to the network device based on the SR4 configuration with the highest SR ID, or send a request message to the network device based on the SR0 configuration with the lowest SR ID.

[0076] In embodiments of the present disclosure, an appropriate request message may be generated based on the configuration corresponding to the highest SR ID or the lowest SR ID in the SR configurations, and/or the request message can be sent to the network device. In some cases, the SR ID may also be randomly selected from a set of configurations, and a request message is sent to the network device based on the SR configuration corresponding to the randomly selected SR ID.

[0077] In some embodiments, the highest resource ID or the lowest resource ID corresponding to the SR configuration may also be defined as the first configuration.

[0078] For example, if the configuration set includes 5 SR configurations, namely, the SR0 configuration, the SR1 configuration, the SR2 configuration, the SR3 configuration, and the SR4 configuration, the respective SR resource IDs corresponding to each SR configuration are 1, 2, 3, 4 and 5, respectively. The terminal device may send a request message to a network device based on the configuration corresponding to SR4, which has the largest resource ID among SRs, or send a request message to the network device based on a configuration corresponding to SR0, which has the smallest resource ID among SRs.

[0079] In embodiments of the present disclosure, an appropriate request message may be generated based on the configuration corresponding to the highest SR resource identifier or the lowest SR resource identifier in the SR configuration, and/or the request message may be sent to the network device. In some cases, the SR resource identifier may also be arbitrarily selected from a set of configurations, and a request message is sent to the network device based on the SR configuration corresponding to the arbitrarily selected SR resource identifier.

[0080] Optionally, the first configuration is a configuration in the configuration set that satisfies the following condition: the priority of the logical channel associated with the scheduling request corresponding to the configuration is the highest or the lowest.

[0081] In embodiments of the present disclosure, since the SR pattern in the pattern set may be associated with at least one logical channel, the first pattern may be determined from the pattern set according to the priority of the logical channel associated with the SR pattern. For example, the SR configuration with the highest associated logical channel priority or the SR configuration with the lowest associated logical channel priority may be defined as the first configuration.

[0082] For example, if a configuration set includes 5 SR configurations, namely, an SR0 configuration, an SR1 configuration, an SR2 configuration, an SR3 configuration, and an SR4 configuration, the logical channels associated with the respective SR configurations among these 5 SR configurations may be different. The priority order of the logical channels associated with these 5 SR configurations is assumed to be: logical channel associated with the SR0 configuration > logical channel associated with the SR1 configuration > logical channel associated with the SR2 configuration > logical channel associated with the SR2 configuration. with the SR3 configuration > the logical channel associated with the SR4 configuration, and then the terminal device can select the SR0 configuration corresponding to the highest priority logical channel as the first configuration, or select the SR4 configuration corresponding to the lowest priority logical channel as the first configuration .

[0083] If the terminal device selects the SR0 configuration corresponding to the highest priority logical channel as the first configuration, that is, the terminal device can first transmit beam failure information to the network device based on the first configuration, thereby reducing the delay of the BFR procedure.

[0084] If the terminal device selects the SR4 configuration corresponding to the lowest priority logical channel as the first configuration, the terminal device may later transmit beam failure information to the network device based on the first configuration so that it does not interfere with data or information transmission based on other SR configurations.

[0085] It should be understood that the logical channel priority order associated with the above SR configuration is only an example for illustration, and other orders may also be possible and should not impose any restrictions on the present disclosure.

[0086] Optionally, in some embodiments, the implementation of the first configuration may be selected arbitrarily from a set of configurations.

[0087] In embodiments of the present disclosure, when a beam failure occurs in a SCell of a terminal device, a request message is generated. The request message configuration may be a configuration arbitrarily selected by the terminal device from a set of configurations, and the terminal device may send a request message to the network device based on the arbitrarily selected configuration. Since the first configuration is randomly selected from the configuration set by the terminal device, the configuration selection time can be reduced so that the system delay can be reduced.

[0088] The above describes the case where the request message configuration is the first configuration, the terminal device may generate a request message based on the first configuration and/or transmit a corresponding request message to the network device. In some embodiments, the request message configuration may also be a second configuration, the case where the request message configuration is the second configuration will be presented next.

[0089] Optionally, in some embodiments, the scheduling request ID of the second configuration is different from the scheduling request ID corresponding to the scheduling request configuration associated with the logical channel; and/or the resource identifier of the scheduling request corresponding to the second configuration is different from the resource identifier of the scheduling request corresponding to the configuration of the scheduling request associated with the logical channel.

[0090] In embodiments of the present disclosure, to avoid confusion with the SR configuration, the scheduling request identifier of the second configuration in the embodiments of the present disclosure may be different from the SR identifier corresponding to the SR configuration associated with the logical channel and/or the resource identifier of the scheduling request of the second configuration may be different from the SR resource identifier corresponding to the SR configuration associated with the logical channel. In the case that a beam failure occurs in the SCell of the terminal device, the terminal device may generate a request message based on the second configuration and/or transmit the request message to the network device to avoid affecting the logical channel processing associated with the SR configuration.

[0091] Optionally, in some embodiments, some or all of the second configuration parameter types are the same as some or all of the configuration parameter types of the scheduling request associated with the logical channel.

[0092] In embodiments of the present disclosure, if the request message configuration is a second configuration, although the second configuration may not be associated with a logical channel, some types of message configuration parameters may be the same as some types of SR configuration parameters or all types of configuration parameters messages can be the same as all types of SR configuration parameters. For example, the second configuration may have a corresponding message identifier, and/or the second configuration may have a corresponding message resource identifier, and/or the resource configuration corresponding to the second configuration may also include PUCCH resource indication information.

[0093] Optionally, in some embodiments, the second configuration scheduling request identifier value is an integer greater than or equal to 8.

[0094] In general, the value of the ID of the SR corresponding to the SR configuration associated with the logical channel may be an integer from 0 to 7, and the value of the scheduling request ID of the second configuration in the embodiments of the present disclosure may be an integer greater than or equal to 8 .

[0095] For example, if the SR patterns associated with the logical channel include 8 SR patterns, and their respective SR IDs are sequentially 0, 1, 2, 3, 4, 5, 6, and 7. Then, the scheduling request ID value of the second configuration may be 8, or 9, or 10 if it is an integer greater than or equal to 8, which is not specifically limited in the present disclosure.

[0096] In embodiments of the present disclosure, the value of the SR ID corresponding to the SR configuration associated with the logical channel may be an integer from 0 to 7. If the SR configurations that are associated with the logical channel and configured by the network device for the terminal device are included in 5 SR configurations themselves, their respective SR IDs can be 0, 1, 2, 3, 4 in sequence; its corresponding SR IDs can also be 1, 2, 3, 4, 5 in sequence; its corresponding SR IDs can also be 2, 3, 4, 5, 6 in sequence. The second configuration scheduling request ID value in the embodiments of the present disclosure may still be an integer greater than or equal to 8. That is, regardless of the number of SR configurations that are associated with a logical channel and configured by the network device for the terminal device, the second configuration in embodiments of the present disclosure is still an integer greater than or equal to 8.

[0097] Optionally, in some embodiments, the second configuration scheduling request resource identifier value is an integer greater than or equal to 9 or equal to 0.

[0098] Generally, the value of the SR resource identifier corresponding to the SR configuration associated with the logical channel may be an integer from 1 to 8. The value of the resource identifier of the scheduling request of the second configuration in the embodiments of the present disclosure may be an integer greater than or equal to 9 , or may be 0.

[0099] For example, the SR patterns associated with the logical channels include 8 SR patterns, and the corresponding SR resource IDs for the 8 SR patterns are 1, 2, 3, 4, 5, 6, 7, and 8 in sequence. Then, the resource identifier value of the scheduling request of the second configuration may be 9 or 10 if it is an integer greater than or equal to 9, or may be 0, which is not specifically limited in the present disclosure.

[00100] It should be understood that the value of the SR resource identifier corresponding to the SR configuration associated with the logical channel may be an integer from 1 to 8. If the SR configurations that are associated with the logical channel and configured by the network device for the terminal device include 5 SR configurations, the corresponding SR IDs for the 5 SR configurations may have the sequence 1, 2, 3, 4, 5; the corresponding SR IDs of the 5 SR configurations can also be 2, 3, 4, 5, 6 in sequence; or the corresponding SR IDs of the 5 SR configurations can also be 3, 4, 5, 6, 7 in sequence. The second configuration scheduling request resource ID value is still an integer greater than or equal to 9 or 0 in embodiments of the present disclosure. In other words, regardless of the number of SR configurations that are associated with logical channels and configured by the network device for the terminal device, the second configuration scheduling request ID value in the embodiments of the present disclosure is still an integer greater than or equal to 9 or 0.

[00101] Optionally, in some embodiments, the second configuration indicates a PUCCH resource.

[00102] In embodiments of the present disclosure, the second configuration may indicate a PUCCH resource, and the request message may be transmitted on the PUCCH resource indicated by the second configuration. That is, in a case where a beam failure occurs in a SCell, the terminal device may send a request message to the network device based on the PUCCH resource indicated by the second configuration.

[00103] In general, the SR resource configuration corresponding to the SR configuration associated with the logical channel may or may not include PUCCH resource indication information. In the case where the SR resource configuration corresponding to the SR configuration associated with the logical channel does not include PUCCH resource indication information, it may be necessary to base on the RACH resource for transmission. The second configuration in the embodiments of the present disclosure may indicate a PUCCH resource, and the terminal device may send a request message to the network device based on the PUCCH resource, which avoids delaying the use of the RACH resource for transmission, thereby reducing the delay of the BFR procedure.

[00104] Optionally, in some embodiments, the signaling corresponding to the second configuration includes a mandatory field to indicate the PUCCH resource.

[00105] In embodiments of the present disclosure, a mandatory field may be used to indicate a PUCCH resource. Because the second configuration may include the PUCCH resource indication information, the terminal device may send a request message to the network device via the PUCCH resource indicated by the PUCCH resource indication information, and the PUCCH resource may be indicated by one mandatory field. In this case, since the second configuration may include one mandatory field for specifying the PUCCH resource, delaying the use of the RACH resource for transmission can be avoided, thereby reducing the delay of the BFR procedure.

[00106] Optionally, in some embodiments, the PUCCH format corresponding to the PUCCH resource is PUCCH format 0 or PUCCH format 1.

[00107] In embodiments of the present disclosure, the format corresponding to the PUCCH resource may be PUCCH format 0 or PUCCH format 1. It should be understood that the format corresponding to the PUCCH resource may include format 0, format 1, format 2, format 3 and format 4, the lengths of such formats in orthogonal frequency division multiplexing (OFDM) symbols are respectively 1-2, 4- 14, 1-2, 4-14, 4-14. Among these 5 formats, the number of bits of format 0 and format 1 is less than or equal to 2, and the number of bits of format 2, format 3, and format 4 is greater than 2. Therefore, the PUCCH format corresponding to the PUCCH resource in the embodiments of the present disclosure may be format 0 and format 1, so that the number of transmitted bits during transmission will be small.

[00108] Optionally, the second configuration is indicated by configuration information corresponding to the BFR.

[00109] In embodiments of the present disclosure, the second configuration may also be indicated by configuration information corresponding to the BFR. For example, the second configuration may be indicated via the IE in the configuration information related to the BFR. It should be understood that since the second configuration may be a scheduling request configuration not associated with a logical channel, the IE in the BFR configuration message may indicate the configuration to the terminal device based on this principle, and the terminal device may send the request message to the network device via the PUCCH resource on based on the configuration specified by the IE in the BFR-related configuration message.

[00110] Optionally, to generate a request message based on the second configuration, the subsequent processing procedure may use a similar processing procedure to the scheduling request (eg, how the request message is transmitted to the network, etc.), which will not be repeated here.

[00111] The configuration of the request message has been described above. In some cases, the terminal device needs to transmit data to the network device while a beam failure occurs, and the terminal device needs to transmit beam failure information to the network device, the processing of the terminal device in this case will be described in detail below.

[00112] Optionally, in some embodiments, the information transmission priority may be determined according to one or more of the following rules:

[00113] a1: The transmission priority of the SCell beam failure information is higher than the transmission priority of any logical channel.

[00114] a2: The transmission priority of the SCell beam failure information is higher than the transmission priority of Radio Network Cell Temporary Identifier (C-RNTI) information or data from the Uplink Common Control Channel (UL-CCCH).

[00115] a3: The transmission priority of the SCell beam failure information is lower than the transmission priority of the C-RNTI information or data from the UL-CCCH and higher than the transmission priority of the configured grant confirmation information.

[00116] a4: The transmission priority of the SCell beam failure information is the same as the transmission priority of the C-RNTI information or data from the UL-CCCH.

[00117] a5: SCell beam failure information transmission priority is the same as the configured grant confirmation information transmission priority.

[00118] a6: The transmission priority of SCell beam failure information is lower than the transmission priority of configured grant confirmation information and higher than the buffer status report (BSR) information transmission priority.

[00119] a7: The SCell beam failure information transmission priority is the same as the BSR information transmission priority.

[00120] a8: The transmission priority of the SCell beam failure information is lower than the transmission priority of the BSR information and higher than the transmission priority of one piece of Power Headroom Report (PHR) information or a plurality of pieces of PHR information.

[00121] The configuration of the request message as the first configuration is taken as an example for description. In embodiments of the present disclosure, according to rule a1, when beam failure information and data based on a logical channel are to be transmitted at the same time, beam failure information is transmitted first.

[00122] For example, if 4 SR patterns, namely SR0 pattern, SR1 pattern, SR2 pattern, and SR3 pattern, are associated with a logical channel, different logical channels may transmit different data. For example, logical channel 0 associated with configuration SR0 may carry MAC C-RNTI CE or data from UL-CCCH, logical channel 1 associated with configuration SR1 carries configured grant confirmation information, e.g., MAC CE configured grant confirmation, logical channel 2 associated with the SR2 configuration carries BSR information other than that which includes the padding BSR, and the logical channel 3 associated with the SR3 configuration transmits one PHR information or a plurality of PHR information. Based on rule a1, since all such 4 SR patterns are associated with different logical channels, SCell beam failure information can be preferably transmitted.

[00123] According to rule a2, when the terminal device needs to simultaneously transmit the SCell beam failure information and C-RNTI MAC CE or data from the UL-CCCH to the network device, the SCell beam failure information may be transmitted first.

[00124] In embodiments of the present disclosure, if a terminal device requests an uplink transmission resource from a network device based on the SR0 configuration, the logical channel associated with the SR0 configuration may transmit the C-RNTI MAC CE or data from the UL-CCCH. After the network device allocates resources to the terminal device, if the allocated resources cannot simultaneously transmit the above data, the terminal device can first transmit beam failure information based on the allocated resource, and then transmit the C-RNTI MAC CE or data from the UL-CCCH to network device.

[00125] According to rule a3, when the terminal device needs to transmit the SCell beam failure information and the MAC C-RNTI CE or data from the UL-CCCH to the network device at the same time, it may transmit the MAC C-RNTI CE or data from the UL-CCCH first.

[00126] The specific transmission process may be similar to the rule a2 process, except that other information is preferably transmitted. Reference may be made to the process of applying rule a2, which will not be repeated here.

[00127] According to rule a4, when the terminal device needs to simultaneously transmit beam failure information SCell and MAC C-RNTI CE or data from UL-CCCH to the network device, the terminal device can select any one of them for transmission, i.e. MAC C CE -RNTI or data from UL-CCCH may be preferably transmitted; alternatively, SCell beam failure information may also be preferably transmitted.

[00128] According to rule a5, when the terminal device needs to simultaneously transmit the SCell failure information and the configured grant confirmation information to the network device, the terminal device can select either of them for transmission, that is, the SCell failure information can be transmitted preferentially; alternatively, the configured grant confirmation information may be transmitted first.

[00129] According to rule a6, when the terminal device needs to transmit the SCell beam failure information and the configured grant confirmation information to the network device at the same time, the terminal device may first transmit the configured grant confirmation information.

[00130] According to rule a7, when the terminal device needs to transmit the SCell information and the BSR information to the network device at the same time, the SCell information can be preferably transmitted. The BSR information may be BSR information other than the information including the padding BSR; or BSR information other than that which includes the padding BSR may also be transmitted first.

[00131] According to rule a8, when the terminal device needs to transmit the SCell beam failure information and the BSR information to the network device at the same time, the BSR information can be preferably transmitted. The BSR information may be BSR information other than that which includes the padded BSR.

[00132] In embodiments of the present disclosure, if the network device allocates more resources to the terminal device after the terminal device requests an uplink transmission resource from the network device, multiple types of data or information may also be downloaded to the network device at the same time.

[00133] For example, taking rule a2 as an example, when the terminal device needs to transmit the SCell beam failure information and the C-RNTI MAC CE or data from the UL-CCCH to the network device at the same time, the terminal device may first transmit the SCell beam failure information, and then transmit MAC CE C-RNTI or data from UL-CCCH. If the network device allocates more resources to the terminal device after the terminal device sends a request message to the network device, that is, these resources can be used to transmit beam failure information of SCell and MAC C-RNTI CE or data from UL-CCCH at the same time, the terminal the device may use these resources to simultaneously transmit SCell beam failure information and C-RNTI MAC CE or data from the UL-CCCH to the network device.

[00134] It is understood that if the network device allocates more resources to the terminal device, these resources can simultaneously carry beam failure information SCell, MAC C-RNTI CE or data from UL-CCCH, configured grant confirmation MAC CE, MAC BSR CE, and one chunk PHR information or multiple pieces of PHR information, the terminal device can use the allocated resources to simultaneously transmit the above data or information to the network device.

[00135] Similarly, if other rules are followed, after the network device allocates appropriate resources to the terminal device, the terminal device may also determine the amount of data to be sent according to the amount of allocated resources. For brevity, this will not be repeated here.

[00136] In some embodiments, if there is a resource available for transmitting other data or information, higher priority information may be transmitted with the resource.

[00137] For example, taking rule a2 as an example, if there is an uplink transmission resource for transmitting the MAC C-RNTI CE or data from the UL-CCCH, the beam failure information may be transmitted to the network device along with the MAC C-RNTI CE or data from the UL-CCCH in case a beam failure occurs in the SCell. If there are more uplink transmission resources, configured grant confirmation information, BSR information, and one piece of PHR information or a plurality of pieces of PHR information may also be sent to the network device together. The order of priority for transmission may be beam failure information, grant acknowledgment information, BSR information, and one piece of PHR information, or multiple pieces of PHR information.

[00138] In other words, if the uplink transmission resource can be used to simultaneously transmit 2 pieces of information, C-RNTI MAC CE/data from UL-CCCH and beam failure information can be sent to the network device together; if the uplink transmission resource can be used to simultaneously transmit 3 pieces of information, then the C-RNTI MAC CE/data from UL-CCCH can be sent to the network, the beam failure information and the configuration confirmation information can be sent to the network device together; if the uplink transmission resource can be used to simultaneously transmit 4 pieces of information, C-RNTI MAC CE/data from UL-CCCH can be sent, beam failure information, configuration confirmation information, and BSR information can be sent to the network device together.

[00139] Optionally, in some embodiments, the request message is sent to a specific cell of the terminal device, and the specific cell of the terminal device may include a PCell or a PSCell of the terminal device.

[00140] In embodiments of the present disclosure, in a case where a beam failure occurs in a SCell of a terminal device, the corresponding PCell or PSCell can still normally transmit messages or information. Therefore, in a case where a beam failure occurs in a SCell of a terminal device, the terminal device may send a request message to a network device based on PCell or PSCell.

[00141] Optionally, in some embodiments, the SCell beam failure information is transmitted to a specific cell of the terminal device, and this specific cell may include a PCell or a PSCell of the terminal device.

[00142] Similarly, in the event of a beam failure in a SCell of a terminal device, the corresponding PCell or PSCell can still transmit messages or information normally. Therefore, the terminal device may send a request message to the network device based on its PCell or PSCell. After the network device allocates the resource to the terminal device, the terminal device can also transmit SCell beam failure information to the network device on the allocated resource based on PCell or PSCell.

[00143] Optionally, in some embodiments, the SCell beam failure information is transmitted via the MAC CE.

[00144] In embodiments of the present disclosure, beam failure information sent to a network device from a terminal device may be transmitted via a MAC CE. The MAC CE in the embodiments of the present disclosure may indicate a cell in which a beam failure occurs or indicate a new beam indicated by the RS-CSI resource or the SS/PBCH block, and may also indicate by means of a specific value that no beam meets the predetermined condition.

[00145] Optionally, in some embodiments, beam failure information is transmitted in a first resource, and the first resource is the resource indicated by the response message to the request message.

[00146] In embodiments of the present disclosure, a terminal device may communicate beam failure information to a network device via a first resource, and the first resource may be a resource indicated by a response message to a request message sent to the network device from the terminal device. For example, after the terminal device transmits a request message to the network device, the network device indicates to the terminal device a resource in response to the request message, so that the terminal device can transmit beam failure information on the resource indicated by the network device.

[00147] The above illustrates that the terminal device can send a request message to the network device to request an uplink transmission resource, thereby transmitting SCell beam failure information to the network device via the requested resource. However, BFR SCell will not succeed every time. In some cases, the BFR SCell may also fail, which will be detailed below.

[00148] Optionally, in some embodiments, when the number of transmissions of the request message is greater than or greater than or equal to the maximum number of transmissions indicated by the configuration of the request message, the terminal device confirms that the BFR SCell is unsuccessful; or in a case where the SCell failure information is sent to the network device, and no feedback information or a response message for the SCell information is received, the terminal device confirms that the BFR SCell is unsuccessful.

[00149] As an example, for illustration purposes, the number of request message transmissions is greater than or greater than or equal to the maximum number of request message configuration transmissions. In embodiments of the present disclosure, the request message configuration may be configured with a maximum number of transmissions, and the terminal device transmits the request message to the network device. The network device may not receive the request message due to poor channel quality or other reasons, or the network device receives the request message but cannot allocate a resource to the terminal device due to a channel quality problem. Accordingly, the terminal device may repeatedly transmit request messages to the network device.

[00150] If the number of times the terminal device transmits the request message to the network device exceeds the maximum number of transmissions corresponding to the request message configuration, the terminal device confirms that the BFR SCell is unsuccessful. For example, assuming that the maximum number of transmissions corresponding to the request message configuration is 10, and no resources allocated by the network device are received after the terminal device transmits the request message to the network device for the 10th time, this when the terminal device is again ready to send a request message to the network device because the maximum number of transmissions corresponding to the request message configuration has been exceeded, it can be confirmed that the BFR SCell of the terminal device is unsuccessful.

[00151] The terminal device can also confirm whether the BFR of the terminal device is successful or unsuccessful by whether it receives feedback information or a response message for SCell beam failure information. Specifically, after the terminal device requests the uplink transmission resource from the network device, and the network device allocates the resource to the terminal device, the terminal device can transmit SCell information to the network device based on the resource. If the terminal device does not receive feedback information or a response message for SCell beam failure information, it can be confirmed that the BFR SCell of the terminal device is unsuccessful. For example, the feedback message may be Hybrid Automatic Repeat-Request-Acknowledge (HARQ-ACK) information, and the response message may be configuration signaling related to a beam steering procedure corresponding to the SCell, such as Radio Resource Control (RRC) signaling or MAC CE signaling, or a beam measurement report triggered by downlink control information (DCI); if the terminal device confirms that it receives feedback information or a response message for SCell beam failure information, such as HARQ-ACK information or configuration signaling related to the beam steering procedure corresponding to the SCell, or MAC CE signaling or beam measurement report, initiated by DCI, it can be confirmed that the BFR SCell of the terminal device is successful.

[00152] Optionally, in some embodiments, the terminal device transmits SCell beam failure information to the network device; if feedback information or a response message for SCell beam failure information is not received when the BFR SCell timer ends, the terminal apparatus acknowledges that the BFR SCell is unsuccessful.

[00153] Optionally, if feedback information or a response message for SCell beam failure information has been received before the BFR SCell timer expires, the terminal device acknowledges that the BFR SCell is successful.

[00154] In embodiments of the present disclosure, a BFR-related configuration message or a request message configuration may configure a BFR timer, and the BFR timer may track the entire duration of the BFR procedure. If the terminal device has not received feedback information or a response message for the SCell beam failure information from the time the terminal device sends a request message to the network device until the timer BFR expires, then it can be confirmed that the BFR SCell of the terminal device is unsuccessful; and if the terminal device has received the feedback information or the response message for the SCell beam failure information before the end of the BFR SCell timer, it can be confirmed that the BFR SCell of the terminal device is successful.

[00155] In the wireless communication method of the present disclosure, since the BFR timer is added, the entire time of the BFR procedure can be monitored, so that the delay of the BFR procedure can be better controlled.

[00156] It should be understood that if the BFR timer is not configured, it may take a long time for the terminal device to receive SCell beam failure information because there is no duration limit. In this case, the terminal device's BFR SCell can be considered successful.

[00157] Optionally, in some embodiments, if the terminal device's BFR SCell is confirmed to be unsuccessful, then the terminal device's SCell is terminated.

[00158] In embodiments of the present disclosure, if a terminal device confirms that the BFR of its SCell is unsuccessful, then the terminal device's SCell may expire, ie the SCell is no longer in use.

[00159] Optionally, in some embodiments, in response to the success of the BFR SCell, the BFR SCell timer is stopped.

[00160] Optionally, in some embodiments, in response to the success of the BFR SCell, the counter used to determine the occurrence of a SCell beam failure is reset to 0.

[00161] In embodiments of the present disclosure, when a terminal device confirms that the BFR of its SCell is successful, the BFR SCell timer may be stopped. It should be understood that the BFR SCell timer is used to keep track of the duration of the BFR SCell. Therefore, when the terminal device acknowledges that its SCell's BFR is successful, it may stop the BFR SCell timer in response to the success of the BFR SCell.

[00162] The counter in embodiments of the present disclosure is used to determine the occurrence of a SCell beam failure. That is, during a specific period, if the number of BFIs counted by the counter is within a specific value, it can be considered that no beam failure occurs in the SCell of the terminal device. If the number of BFIs counted by the counter exceeds a certain value, then it can be considered that a beam failure has occurred in the SCell of the terminal device. Therefore, when the terminal device acknowledges the successful execution of the BFR of its SCell, it may reset the counter used to determine the occurrence of a SCell beam failure to 0 in response to the successful execution of the BFR SCell.

[00163] Optionally, in some embodiments, the timer is configured by the network device for the terminal device.

[00164] Optionally, in some embodiments, the timer is configured by the network device to the terminal device via RRC signaling.

[00165] In embodiments of the present disclosure, the BFR SCell timer may be configured by a network device for a terminal device. In addition, the BFR SCell timer may be configured by the network device to the terminal device through RRC signaling. The duration of the configured BFR timer may also be determined by the network device, for example, it may be 100 ms or 1 s, which is not specifically limited in this disclosure.

[00166] Optionally, in some embodiments, the time to start or restart the timer is one of the following times:

[00167] when the terminal device detects that a beam failure occurs in a secondary cell; after the terminal apparatus detects that a beam failure occurs in the secondary cell; when generating a request message; before generating a request message; after generating a request message; when sending a request message; before sending the request message; after the transmission of the request message; when transmitting beam failure information of the secondary cell; before transmitting beam failure information of the secondary cell; and after transmitting the beam failure information of the secondary cell.

[00168] In embodiments of the present disclosure, the terminal device may start a BFR timer upon detecting a beam failure in a SCell, or may start a BFR timer upon detecting a beam failure in a SCell. As to how long the terminal device starts the BFR timer after detecting a beam failure in the SCell, this may be determined by the terminal device. For example, the terminal device may start the BFR timer 2 ms after detecting a beam failure that occurred in a SCell.

[00169] The numerical values in the embodiments of the present disclosure are merely examples, and may also be other numerical values that are not specifically limited in the present disclosure.

[00170] Similarly, the process for starting or restarting the BFR timer is otherwise similar to the process described above and will not be repeated here for brevity.

[00171] Therefore, in accordance with the wireless communication method provided by the present disclosure, in the case where a beam failure occurs in a SCell, the terminal device may generate a request message according to the first configuration or the second configuration, and optionally transmit the request message in the network device to request an uplink transmission resource from the network device, or notifies the network device that a beam failure occurs in the SCell of the terminal device. After receiving the first message or notification transmitted from the terminal device, the network device may allocate a resource to the terminal device so that the terminal device can transmit SCell beam failure information to the network device. In addition, transmission of beam failure information may take precedence over transmission of other data or information, thereby reducing the delay of the BFR procedure.

[00172] FIG. 4 is a flow diagram of a wireless communication method 400 provided by another embodiment of the present invention. As shown in FIG. 4, method 400 may include steps 410-430.

[00173] In step 410, the network device transmits configuration information to the terminal device, and the configuration information is used to configure the PUCCH resource.

[00174] In step 420, the terminal device receives configuration information.

[00175] In step 430, in the case where a beam failure occurs in the SCell, the terminal device uses the PUCCH resource to transmit a report message and/or uses the PUSCH resource to transmit the MAC CE.

[00176] In embodiments of the present disclosure, the terminal device's use of the PUCCH resource to transmit the report message may mean that the terminal device uses the PUCCH resource to transmit the report message to the network device, and the terminal device's use of the PUSCH resource to transmit the MAC CE may mean that the terminal device the device uses the PUSCH resource to send the MAC CE corresponding to the SCell beam failure information to the network device.

[00177] In embodiments of the present disclosure, if a beam failure occurs in a SCell of a terminal device, the terminal device may send a report message to the network device via a PUCCH resource configured by the network device for the terminal device, and/or may send a MAC CE to the network device via the resource PUSCH.

[00178] The SCell beam failure information in embodiments of the present disclosure may indicate a cell on which a beam failure occurs, a beam on which a beam failure occurs, or a new beam. The beam failure information may also indicate that there are no beams that meet the predetermined condition.

[00179] The PUSCH resource in embodiments of the present disclosure may be a resource indicated by a response message to a report message transmitted by the terminal device to the network device, or it may be a periodic or semi-persistent PUSCH resource, or it may be a PUSCH resource used by the terminal device for transmission other data.

[00180] In the wireless communication method of the present disclosure, a network device may transmit configuration information to a terminal device, and the configuration information may be used to configure a PUCCH resource. In the case that a beam failure occurs in the SCell, the terminal device may use the PUCCH resource to transmit the report message and/or use the PUSCH resource to transmit the MAC CE, so that the BFR SCell procedure may be implemented.

[00181] Optionally, in some embodiments, in response to the satisfaction of one or more of the following conditions, the transmission of the reporting message in the current PUCCH resource time spent in transmission is canceled or stopped:

[00182] b1: The first timer corresponding to the PUCCH resource operates at the current transmission time of the PUCCH resource, and the first timer is used to control the transmission interval of the PUCCH resource.

[00183] b2: The current elapsed transmission time of the PUCCH resource overlaps with the first PUSCH resource included in the PUSCH resource.

[00184] b3: The second PUSCH resource included in the PUSCH resource is within the first time period or the second time period, the end time of the first time period is earlier than the current transmission time spent or is within the current transmission time spent, and the start time of the second time period later than the current elapsed transmission time or is a time within the current elapsed transmission time.

[00185] b4: there is downlink control information (DCI) for scheduling the third PUSCH resource included in the PUSCH resource in the third time period or the fourth time period, the end time of the third time period is earlier than the current spent transmission time or is the time within the current elapsed transmission time, and the start time of the fourth time period is later than the current elapsed transmission time, or is a time within the current elapsed transmission time.

[00186] b5: The current elapsed transmission time of the PUCCH resource overlaps with the measurement gap.

[00187] b6: The second timer corresponding to the PUCCH resource configuration stops or expires at the current time spent in transmission of the PUCCH resource, and the second timer is used to control the maximum transmission time for transmitting the PUCCH resource.

[00188] b7: The current time spent in transmission of the PUCCH resource overlaps with the transmission resource carrying HARQ information, and the transmission resource corresponds to the time domain resource used for transmission.

[00189] b8: The current elapsed transmission time of the PUCCH resource overlaps with the transmission resource corresponding to the scheduling request, and the transmission resource corresponds to the time domain resource used for transmission.

[00190] b9: Before the current PUCCH resource expend time, the terminal device receives a DCI for scheduling the fourth PUSCH resource, and the DCI is a response message to the reporting message sent in the previous PUSCH resource expend time.

[00191] b10: before the current elapsed transmission time of the PUCCH resource, the MAC CE is transmitted by the terminal device via the PUSCH resource, or the MAC CE is successfully transmitted by the terminal device via the PUSCH resource.

[00192] In embodiments of the present disclosure, condition b1 is taken as an example for illustration. If the first timer used to control the transmission interval of the PUCCH resource is running at the current effective time of the PUCCH resource, the transmission of the report message at the current transmission time of the PUCCH resource is canceled or stopped.

[00193] In embodiments of the present disclosure, the first timer may be used to control the transmission interval of the PUCCH resource. Assuming that the transmission period of the PUCCH resource is 10 ms, if the 3rd ms is the current elapsed transmission time for transmitting the reporting message through the PUCCH resource, and the first timer is in operation at this point in time (i.e., the timer that controls the interval transmission of the PUCCH resource), then the transmission of the reporting message by the PUCCH resource in 3 ms may be canceled or stopped.

[00194] In the case that transmission of the reporting message at the current PUCCH resource elapsed time is canceled or stopped, if the first timer is in the stopped state at the next PUCCH resource elapsed time, the report message may be transmitted at the next PUCCH resource transmission time. .

[00195] Similarly, the condition b2 is taken as an example for illustration. In embodiments of the present disclosure, if the current PUCCH resource elapsed time overlaps with the first PUSCH resource included in the PUSCH resource, transmission of the reporting message in the current PUCCH resource elapsed time may be canceled or stopped.

[00196] In particular, assuming that the PUCCH resource transmission period is 10 ms, if the 3rd ms is the current elapsed transmission time for transmitting the PUCCH resource while the first PUSCH resource is also transmitted during the 3rd ms, the terminal device may then cancel or stop transmission of the report message in the current PUCCH resource elapsed transmission time.

[00197] Similarly, condition b3 is taken as an example for illustration. In embodiments of the present disclosure, if the second PUSCH resource included in the PUSCH resource is within the first time period or the second time period, transmission of the reporting message in the current transmission time of the PUCCH resource may be canceled or stopped. The end time of the first time period is earlier than the current time spent on transmission or is the time within the current time spent on transmission, and the start time of the second time period is later than the current time spent on transmission or is the time within the current time spent on transmission. the current time spent on transmission.

[00198] In one embodiment, when the terminal device is ready to send a reporting message to the network device in 3 ms using the PUCCH resource, if the transmission of the second PUSCH resource exists in the first time period from the 3 ms, for example, the duration value of the first period time is 2 ms, the terminal device may cancel or stop transmission of the report message at the current transmission time of the PUCCH resource. In other words, if the transmission of the second PUSCH resource exists in the 1st or 2nd ms, the terminal apparatus may cancel or stop transmission of the report message at the current transmission time of the PUCCH resource.

[00199] In another embodiment, when the terminal device is ready to send a reporting message to the network device in 3 ms using the PUCCH resource, if the transmission of the second PUSCH resource exists in the second time period from the 3 ms, for example, the duration value of the second period time is 2 ms, the terminal device may cancel or stop transmission of the report message at the current transmission time of the PUCCH resource. In other words, if the transmission of the second PUSCH resource exists at the 4th or 5th ms, the terminal apparatus may cancel or stop transmission of the report message at the current transmission time of the PUCCH resource.

[00200] The second PUSCH resource in the embodiments of the present disclosure may be the same as or different from the first PUSCH resource mentioned above, which is not specifically limited in the present disclosure.

[00201] Similarly, the condition b4 is taken as an example for illustration. If there is a DCI for scheduling the third PUSCH resource included in the PUSCH resource in the third time period or the fourth time period, the transmission of the report message in the current transmission time spent on the PUCCH resource may be canceled or stopped. The end time of the third time period is earlier than the current spent transmission time or is the time within the current spent transmission time, and the start time of the fourth time period is later than the current spent transmission time or is the time within the current transmission spent time. the current time spent on transmission.

[00202] In one implementation, when the terminal device is ready to send a reporting message to the network device in 3 ms using the PUCCH resource, if there is a DCI that can schedule the third PUSCH resource in the third time period from the 3 ms, for example, the value of the duration of the third time period is 2 ms, then the terminal device may cancel or stop transmission of the report message at the current transmission time of the PUCCH resource. In other words, if there is a DCI that can schedule a third PUSCH resource at 1 ms or 2 ms, the terminal device can cancel or stop transmission of the report message at the current transmission time of the PUCCH resource.

[00203] In another implementation, when the terminal device is ready to send a reporting message to the network device in 3 ms using the PUCCH resource, if there is a DCI that can schedule the third PUSCH resource in the fourth time period from the 3 ms, for example, the duration value of the fourth time period is 2 ms, the terminal device may cancel or stop transmission of the report message at the current transmission time of the PUCCH resource. In other words, if there is a DCI that can schedule a third PUSCH resource at the 4th or 5th ms, then the terminal device can cancel or stop transmission of the report message at the current transmission time of the PUCCH resource.

[00204] It should be understood that the numerical values in the embodiments of the present disclosure are only examples, and may also be other numerical values that should not specifically limit the present disclosure.

[00205] The third PUSCH resource in the embodiments of the present disclosure may be the same or different from the first PUSCH resource and the second PUSCH resource mentioned above, which is not limited to the present disclosure.

[00206] Similarly, condition b5 is taken as an example for illustration. In embodiments of the present disclosure, if the current PUCCH resource elapsed time overlaps with the measurement gap, transmission of the report message in the current PUCCH resource elapsed time may be canceled or stopped.

[00207] In embodiments of the present disclosure, the measurement gap may refer to the following period: during the measurement gap, the terminal device cannot transmit or receive any data, and the receiver tunes to the frequency point of the target cell to perform inter-frequency measurement, when the measurement gap ends, then tuning to the current cell is performed. That is, after a beam failure in the terminal device's SCell, if the terminal device's PCell needs to be used for the measurement gap at that time, the transmission of the report message in the current transmission time of the PUCCH resource can be canceled or stopped. After the end of the measurement gap, if the PUCCH resource is to be used to transmit the report message, the report message may be transmitted at the next transmission time of the PUCCH resource.

[00208] Similarly, condition b6 is taken as an example for illustration. In embodiments of the present disclosure, if the second timer corresponding to the PUCCH resource configuration stops or expires at the current PUCCH resource elapsed time, transmission of the report message at the current PUCCH resource elapsed time may be canceled or stopped.

[00209] In embodiments of the present disclosure, a second timer may be used to control the maximum transmission time for transmitting a report message using PUCCH resources. If the second timer is in a stopped state or expires at the current PUCCH resource elapsed time, then transmission of the report message at the current PUCCH resource elapsed time may be canceled or stopped.

[00210] In the wireless communication method provided by the embodiments of the present disclosure, the second timer can better track the transmission time of the report message using PUCCH resources and can better control the timing of the BFR procedure. Therefore, when the second timer stops or expires, transmission of the report message in the current PUCCH resource time spent on transmission may be canceled or stopped.

[00211] Optionally, when the second timer is stopped, the current elapsed transmission time of the PUCCH resource may also be used to transmit the report message. Although the second timer is in the stopped state, even if the maximum transmission time for transmitting a report message over the PUCCH resource is exceeded, the terminal device may not acknowledge that the BFR SCell is unsuccessful due to expiration. Therefore, the terminal device can still use the PUCCH resource to continue transmitting the report message.

[00212] Similarly, condition b7 is taken as an example for illustration. In embodiments of the present disclosure, if the current PUCCH resource elapsed time overlaps with a transmission resource carrying HARQ information, transmission of the reporting message in the current PUCCH resource elapsed time may be canceled or stopped.

[00213] In embodiments of the present disclosure, assuming that the PUCCH resource transmission period is 10 ms, if the 3 ms is the current elapsed transmission time for transmitting the PUCCH resource, a resource carrying HARQ information is also transmitted at that time. within 3 ms, the terminal device may cancel or stop transmitting the report message during the current PUCCH resource time spent on transmission. In this case, the terminal device may preferably transmit a resource carrying the HARQ information.

[00214] Similarly, condition b8 is taken as an example for illustration. If the current PUCCH resource elapsed transmission time overlaps with the transmission resource corresponding to the scheduling request, transmission of the report message in the current PUCCH resource elapsed transmission time may be canceled or stopped.

[00215] In embodiments of the present disclosure, assuming that the PUCCH resource transmission period is 10 ms, if the 3rd ms is the current elapsed transmission time for transmitting the PUCCH resource, the transmission resource corresponding to the scheduling request is also transmitted in 3- 10 ms, then the terminal device may cancel or stop transmission of the report message using the current time spent on transmission of the PUCCH resource. In this case, the terminal device may preferably send a scheduling request.

[00216] In embodiments of the present disclosure, an uplink transmission carrying HARQ information or an uplink transmission corresponding to a scheduling request may be preferably transmitted, and then a report message is transmitted via a PUCCH resource.

[00217] Similarly, condition b9 is taken as an example for illustration. In embodiments of the present disclosure, if the terminal device receives a DCI to schedule a fourth PUSCH resource included in the PUSCH resource before the current PUCCH resource elapsed transmission time, transmission of the reporting message in the current PUCCH resource elapsed transmission time may be canceled or stopped.

[00218] In embodiments of the present disclosure, a terminal device may send a report message to the terminal device via a PUCCH resource. After receiving the report message, the network device may transmit the DCI to the terminal device based on the report message. The DCI may schedule a fourth PUSCH resource through which the terminal device transmits the MAC CE, and thus the transmission of the report message in the current transmission time of the PUCCH resource may be canceled or stopped.

[00219] In embodiments of the present disclosure, the DCI may be a response message to a report message sent to the network device from the terminal device, or may be a DCI based on normal service scheduling, and the terminal device may transmit a MAC CE based on the fourth PUSCH resource scheduled by DCI.

[00220] Similarly, condition b10 is taken as an example for illustration. If the terminal device transmits the MAC CE over the PUSCH resource or successfully transmits the MAC CE over the PUSCH resource before the current PUCCH resource elapsed time, transmission of the report message in the current PUCCH resource elapsed time may be canceled or stopped.

[00221] In embodiments of the present disclosure, a terminal device may transmit a MAC CE to a network device via a PUSCH resource. If the terminal device transmits the MAC CE over the PUSCH resource or successfully transmits the MAC CE over the PUSCH resource before the current PUCCH resource elapsed time, transmission of the report message in the current PUCCH resource elapsed time may be canceled or stopped.

[00222] In particular, in embodiments of the present disclosure, assuming that the PUCCH resource transmission period is 10 ms, if the 3rd ms is the current elapsed transmission time for PUCCH resource transmission while the MAC CE is transmitted or successfully transmitted through PUSCH resource until the 3rd ms, then transmission of the reporting message at the 3rd ms via the PUCCH resource may be canceled or stopped.

[00223] The above illustrates that, in some cases, the transmission of the report message in the current PUCCH resource elapsed transmission time may be canceled or stopped. Next, transmission of the report message at the current transmission time of the PUCCH resource will be described in some cases, that is, the report message is transmitted at the current transmission time of the PUCCH resource.

[00224] Optionally, in some embodiments, when some or all of the following conditions are met, the report message may be transmitted in the current expended transmission time of the PUCCH resource:

[00225] c1: The first timer corresponding to the PUCCH resource is stopped at the current transmission elapsed time of the PUCCH resource, and the first timer is used to control the transmission interval of the PUCCH resource.

[00226] c2: The current elapsed transmission time of the PUCCH resource does not overlap with the PUSCH resource.

[00227] c3: The current elapsed transmission time of the PUCCH resource does not overlap with the measurement gap.

[00228] c4: The second timer corresponding to the PUCCH resource operates at the current time spent on transmission of the PUCCH resource, and the second timer is used to control the maximum transmission time for transmitting the PUCCH resource.

[00229] c5: The current transmission time of the PUCCH resource does not overlap with the transmission resource carrying HARQ information, and the transmission resource corresponds to the time domain resource used for transmission.

[00230] c6: The current elapsed transmission time of the PUCCH resource does not overlap with the transmission resource corresponding to the scheduling request, and the transmission resource corresponds to the time domain resource used for transmission.

[00231] c7: Before the current PUCCH resource elapsed time, the terminal device does not receive DCI for scheduling the PUSCH resource.

[00232] c8: DCI for PUSCH resource scheduling is not received in the third time period or the fourth time period, the end time of the third time period is earlier than the current spent transmission time or is within the current spent transmission time, and the start time of the fourth time period is later than the current spent transmission time to transmit time, or is the time within the current time spent transmitting.

[00233] c9: Before the current elapsed transmission time of the PUCCH resource, the CE MAC is not transmitted by the terminal device via the PUSCH resource.

[00234] c10: before the current PUCCH resource elapsed time, the terminal device's transmission of the MAC CE over the PUSCH resource is unsuccessful.

[00235] In embodiments of the present disclosure, condition c1 is taken as an example for illustration. If the first timer is in the stopped state at the current PUCCH resource elapsed time, the current PUCCH resource elapsed time may be used to transmit the MAC CE.

[00236] The first timer in embodiments of the present disclosure may be used to control the transmission interval of the PUCCH resource. Assuming that the reporting message transmission period over the PUCCH resource is 10 ms, if the 3rd ms is the current spent transmission time for transmitting the reporting message over the PUCCH resource, the current spent transmission time of the PUCCH resource can be used to transmit the reporting message in the case where the first timer stops or expires, i.e. the PUCCH resource can be used to send a 3 ms report message.

[00237] It is understood that in this case, if the terminal device fails to transmit a report message within the current PUCCH resource elapsed time, it may transmit a report message using the next PUCCH resource elapsed transmission time, i. e. it may send a 13 ms reporting message over the PUCCH resource (provided that the appropriate conditions are satisfied).

[00238] Likewise, condition c2 is taken as an example for illustration. If the current PUCCH resource elapsed time does not overlap with the PUSCH resource, the current PUCCH resource elapsed time may be used to transmit the report message.

[00239] As mentioned above, if the current PUCCH resource elapsed time overlaps with the PUSCH resource, transmission of the reporting message in the current PUCCH resource elapsed time may be canceled or stopped. In this case, for example, the PUSCH resource may be used to transmit the MAC CE, thus the delay of the BFR procedure may be reduced. In embodiments of the present disclosure, if the current PUCCH resource elapsed time does not overlap with the PUSCH resource, the current PUCCH resource elapsed time may be used to transmit a report message so that the terminal device can use the requested resource to transmit the MAC CE, and the success probability BFR can be further increased.

[00240] Likewise, condition c3 is taken as an example for illustration. If the current PUCCH resource elapsed time does not overlap with the measurement gap, the current PUCCH resource elapsed time may be used to transmit the reporting message.

[00241] As mentioned above, if the current PUCCH resource elapsed transmission time overlaps with the measurement gap, transmission of the reporting message in the current PUCCH resource elapsed transmission time may be canceled or stopped. In the embodiments of the present disclosure, if the current elapsed time of the PUCCH resource does not overlap with the measurement gap, that is, the terminal device can normally transmit/receive data or information, so the terminal device can use the current elapsed time of the PUCCH resource to transmit a report message, which can reduce the delay of the BFR procedure.

[00242] Likewise, condition c4 is taken as an example for illustration. If the second timer corresponding to the PUCCH resource configuration is running in the current PUCCH resource elapsed transmission time, the second timer is used to control the maximum transmission time for transmitting the PUCCH resource.

[00243] As mentioned above, if the second timer stops at the current PUCCH resource elapsed time, transmission of the report message at the current PUCCH resource elapsed time may be canceled or stopped. In embodiments of the present disclosure, if the second timer is running in the current expended transmission time of the PUCCH resource, since the second timer can better control the timing when the PUCCH resource is used to transmit the reporting message, the reporting message may be transmitted in the current expiration time of the PUCCH resource.

[00244] Likewise, condition c5 is taken as an example for illustration. If the current elapsed transmission time of the PUCCH resource does not overlap with the transmission resource carrying the HARQ information, the current elapsed transmission time of the PUCCH resource may be used to transmit the reporting message.

[00245] As mentioned above, if the current PUCCH resource elapsed time overlaps with a transmission resource carrying HARQ information, the terminal device may cancel or stop transmission of the reporting message in the current PUCCH resource elapsed time. In embodiments of the present disclosure, if the current elapsed time of the PUCCH resource does not overlap with the transmission resource carrying HARQ information, the terminal device may use the current elapsed time of the PUCCH resource to transmit a report message.

[00246] Likewise, condition c6 is taken as an example for illustration. If the current elapsed transmission time of the PUCCH resource does not overlap with the transmission resource corresponding to the scheduling request, the current elapsed transmission time of the PUCCH resource may be used to transmit the reporting message.

[00247] As mentioned above, if the current PUCCH resource elapsed time overlaps with the transmission resource corresponding to the scheduling request, the terminal device may cancel or stop transmission of the report message in the current PUCCH resource elapsed time. In embodiments of the present disclosure, if the current PUCCH resource elapsed time does not overlap with the transmission resource corresponding to the scheduling request, the terminal device may use the current PUCCH resource elapsed time to transmit a report message.

[00248] Likewise, condition c7 is taken as an example for illustration. If the terminal device does not receive a DCI to schedule a PUSCH resource before the current PUCCH resource elapsed time, it may use the current PUCCH resource elapsed time to transmit a report message.

[00249] As mentioned above, if the terminal device receives a DCI for scheduling a PUSCH resource prior to the current PUCCH resource time spent transmitting, it may cancel or stop transmission of the reporting message in the current PUCCH resource time spent transmitting. In embodiments of the present disclosure, if the terminal device does not receive a DCI for scheduling a PUSCH resource before the current expended PUCCH resource time, i.e., the terminal device does not have a DCI that can schedule a PUSCH resource, the terminal device may send a report message in the current expended transmission time. the PUCCH resource time so that the terminal device can transmit the MAC CE based on the resource requested by the reporting message.

[00250] Likewise, condition c8 is taken as an example for illustration. If the DCI for PUSCH resource scheduling is not received in the third time period or the fourth time period, the current time spent in transmission of the PUCCH resource may be used to transmit the reporting message. The end time of the third time period is earlier than the current time spent on transmission or is the time within the current time spent on transmission, and the start time of the fourth time period is later than the current time spent on transmission or is the time within the current time spent on transmission. the current time spent on transmission.

[00251] In embodiments of the present disclosure, if the terminal device does not receive DCI for scheduling a PUSCH resource in the third time period or the fourth time period, that is, there is no available PUSCH resource to transmit the MAC CE, in which case the current elapsed transmission time of the PUCCH resource is used to send a report message so that the terminal device can send a MAC CE based on the resource requested by the report message.

[00252] Likewise, condition c9 is taken as an example for illustration. If the terminal device does not use the PUSCH resource to transmit the MAC CE before the current PUCCH resource timeout expires, it may use the current PUCCH resource timeout to send a report message.

[00253] As mentioned above, if the terminal device transmits a MAC CE over the PUSCH resource before the current PUCCH resource expended time, it may cancel or stop transmission of the report message in the current PUCCH resource expended time. In embodiments of the present disclosure, if the terminal device does not transmit a MAC CE over the PUSCH resource before the current PUCCH resource elapsed time, the terminal device may send a report message in the current PUCCH resource elapsed time so that the terminal device can transmit the MAC CE based on the resource. requested by the reporting message.

[00254] Likewise, condition c10 is taken as an example for illustration. If the terminal device cannot transmit the MAC CE over the PUSCH resource before the current PUCCH resource timeout expires, it may use the current PUCCH resource timeout to send a report message.

[00255] As mentioned above, if the terminal device successfully transmits the MAC CE over the PUSCH resource before the current PUCCH resource expend time, it may cancel or stop transmission of the report message in the current PUCCH resource expend time. In embodiments of the present disclosure, if the terminal device can transmit the MAC CE over the PUSCH resource before the current PUCCH resource elapsed time, but the transmission of the MAC CE is unsuccessful, the terminal device may send a report message in the current PUCCH resource elapsed time so that the terminal device could send a MAC CE based on the resource requested by the reporting message.

[00256] Optionally, in some embodiments, the PUSCH resource includes a fourth PUSCH resource, and the fourth PUSCH resource is the resource indicated by the response message for the report message.

[00257] In embodiments of the present disclosure, in the case where a beam failure occurs in a SCell, the terminal device sends a report message to the network device to request an uplink transmission resource from the network device. After receiving the report message, the network device may respond to the report message to indicate four PUSCH resources, and the terminal device may transmit a MAC CE based on the fourth PUSCH resource.

[00258] Optionally, in some embodiments, the PUSCH resource includes a first PUSCH resource, and the first PUSCH resource overlaps with the current elapsed transmission time of the PUCCH resource; and/or the PUSCH resource includes a second PUSCH resource, the second PUSCH resource is located in the first time period or in the second time period in the time domain, the end time of the first time period is earlier than the current time spent on transmission or is a time within the current time spent on transmission, and the start time of the second period of time is later than the current elapsed transmission time or is a time within the current elapsed transmission time; and/or the PUSCH resource includes a third PUSCH resource, the DCI for scheduling the third PUSCH resource is in the third time period or the fourth time period in the time domain, the end time of the third time period is earlier than the current spent transmission time or is within the current transmission spent time time, and the start time of the fourth period of time is later than the current elapsed transmission time or is a time within the current elapsed transmission time; and/or the PUSCH resource includes a fifth PUSCH resource, and the fifth PUSCH resource is scheduled by configured grant type 1 or configured grant type 2.

[00259] In embodiments of the present disclosure, if the first PUSCH resource included in the PUSCH resource overlaps with the current elapsed transmission time of the PUCCH resource, the first PUSCH resource may be used to transmit the MAC CE.

[00260] Specifically, assuming that the reporting message transmission period over the PUCCH resource is 10 ms, if the 3rd ms is the current elapsed transmission time for transmitting the PUCCH resource, at this time, the first PUSCH resource is also transmitted in the 3rd ms , then the terminal device cancels or stops transmission of the report message in the current PUCCH resource time spent on transmission, as indicated above. In another embodiment, the terminal device may also use the first PUSCH resource to transmit the 3 ms MAC CE.

[00261] In the wireless communication method of the present disclosure, if the current elapsed transmission time of the PUCCH resource overlaps with the transmission time of the first PUSCH resource included in the PUSCH resource, the terminal device may transmit a MAC CE based on the first PUSCH resource. In this case, the terminal device can no longer request the uplink transmission resource from the network device via the PUCCH resource, so that the delay of the BFR procedure can be reduced.

[00262] In embodiments of the present disclosure, if the second PUSCH resource included in the PUSCH resource is located in the first time period or the second time period in the time domain, the terminal device may use the second PUSCH resource to transmit the MAC CE to the network device. The end time of the first time period is earlier than the current time spent on transmission or is the time within the current time spent on transmission, and the start time of the second time period is later than the current time spent on transmission or is the time within the current time spent on transmission.

[00263] In one embodiment, when the terminal device is ready to send a reporting message to the network device at 3 ms via the PUCCH resource, if transmission of the second PUSCH resource exists during the first time period from the 3 ms, for example, the duration value of the first period time is 2 ms. As mentioned above, the terminal device may cancel or stop transmission of the report message at the current transmission time of the PUCCH resource. In embodiments of the present disclosure, if a transmission of the second PUSCH resource exists at 1 ms or 2 ms, the terminal device may send the MAC CE to the network device via the second PUSCH resource.

[00264] In another embodiment, when the terminal device is ready to send a reporting message to the network device in 3 ms via the PUCCH resource, if the transmission of the second PUSCH resource exists within the second time period from the 3 ms, for example, the duration value of the second time period equals 2 ms. As mentioned above, the terminal device may cancel or stop transmission of the report message at the current transmission time of the PUCCH resource. In embodiments of the present disclosure, if the transmission of the second PUSCH resource is in 4 ms or 5 ms, the terminal device may send the MAC CE to the network device via the second PUSCH resource.

[00265] It should be understood that the above numerical values are only examples and should not specifically limit the present application. The duration value of the first time period is the same as or different from the duration value of the second time period in the embodiments of the present disclosure, which is not specifically limited in the present disclosure.

[00266] Similarly, the PUSCH resource includes a third PUSCH resource. If the DCI for scheduling the third PUSCH resource is located in the third time period or the fourth time period in the time domain, the terminal device may use the third PUSCH resource to transmit the MAC CE to the network device. The end time of the third time period is earlier than the current time spent on transmission or is the time within the current time spent on transmission, and the start time of the fourth time period is later than the current time spent on transmission or is the time within the current time spent on transmission.

[00267] In embodiments of the present disclosure, if there is a DCI that can schedule a third PUSCH resource near the current time-consuming PUCCH resource, in the event that a beam failure occurs in a SCell, the terminal device can use the DCI to schedule the third PUSCH resource to the scheduled third PUSCH resource could be used to transmit the MAC CE.

[00268] The DCI in embodiments of the present disclosure may be transmitted by the PDCCH, and the DCI transmitted from the network device to the terminal device may include uplink and downlink resource allocation, HARQ information, power control, and so on. Therefore, when there is no third PUSCH resource to transmit, if a beam failure occurs in the SCell, the third PUSCH resource can be scheduled based on the DCI, so that the third PUSCH resource can be used to transmit the MAC CE.

[00269] In embodiments of the present disclosure, if there is a fifth PUSCH resource scheduled with type 1 or type 2 of configured grant, the terminal device may use the fifth PUSCH resource to transmit the MAC CE.

[00270] In embodiments of the present disclosure, in configured grant type 1, a fifth PUSCH resource may be periodically scheduled for a specific time period, and a terminal device may use the fifth PUSCH resource to transmit a MAC CE; in configured grant type 2, the fifth PUSCH resource may be continuously scheduled or scheduled at DCI triggered intervals so that the terminal device may use the fifth PUSCH resource to transmit the MAC CE.

[00271] Optionally, in some embodiments, if the terminal device successfully transmits the MAC CE via the PUSCH resource, it no longer transmits a report message via the PUCCH resource.

[00272] Optionally, in some embodiments, in response to a PUSCH resource being used to transmit a MAC CE or received by a DCI to schedule a PUSCH resource, the second timer is stopped. The second timer is used to control the maximum transmission time for transmitting the PUCCH resource.

[00273] In embodiments of the present disclosure, in the case where the terminal device uses the PUSCH resource to transmit the MAC CE, that is, the network device may know that a beam failure occurs in the terminal device's SCell and related information, and the PUCCH resource can no longer be used to transmit reporting message. If the second timer is running, when the terminal device uses the PUSCH resource to transmit the MAC CE or receives a DCI scheduling the PUSCH resource, since the second timer is used to control the maximum transmission time for transmitting the PUCCH resource, in this case, the second timer may be stopped.

[00274] In embodiments of the present disclosure, the end time of the first time period or the third time period is the starting point of the first PUCCH resource symbol.

[00275] In embodiments of the present disclosure, the end time of the first time period or the third time period is the starting point of the first PUCCH resource symbol. That there is a second PUSCH resource in the first time period before the current PUCCH resource elapsed time is taken as an example for illustration, the first time period in embodiments of the present disclosure may mean that there are all or part of the PUSCH resource symbols in the first time period. .

[00276] In embodiments of the present disclosure, the end time of the first time period or the third time period is the start point of the first PUCCH resource symbol, or may also be the end point of the last PUCCH resource symbol, or may also be the midpoint of the middle PUCCH resource symbol, or may also be the start point, end point, or midpoint of another character, which is not specifically limited in the present disclosure.

[00277] In embodiments of the present disclosure, the start time of the second time period or the fourth time period may be the start point of the first symbol or the end point of the last symbol of the PUCCH resource.

[00278] In embodiments of the present disclosure, the start time of the second time period or the fourth time period may be the start point of the first symbol or the end point of the last symbol of the PUCCH resource. That there is a second PUSCH resource in the second time period after the current elapsed transmission time of the PUCCH resource is taken as an example for illustration, the second time period in the embodiments of the present disclosure may mean that there are all or part of the symbols of the second PUSCH resource in second period of time.

[00279] In embodiments of the present disclosure, the start time of the second time period or the fourth time period may be the start point of the first PUCCH resource symbol, or may also be the end point of the last PUCCH resource symbol, or may also be the midpoint of the middle PUCCH resource symbol, or may also be be the start point, end point, or midpoint of another character, which is not specifically limited in the present disclosure.

[00280] The durations of the first time period, the second time period, the third time period, and the fourth time period in the embodiments of the present disclosure may be determined by a protocol prescription, or may be determined by a pre-configuration of a network device, or may be determined according to the messaging capability of the terminal device.

[00281] For example, if the duration value of the first time period is 2 ms, as specified in the protocol or configured in the preconfiguration of the network device, it can be determined that the duration of the first time period is 2 ms; if the value of the duration of the third time period is 3 ms, as specified in the protocol or configured in the preliminary configuration of the network device, it can be determined that the duration of the third time period is 3 ms; alternatively, the duration value of the first time period or the third time period is determined according to the reporting capability of the terminal device. If the terminal device has a better reporting capability, the duration value of the first time period or the third time period may be set to be large. If the terminal device has a lower reporting capability, the duration value of the first time period or the third time period may be set to be smaller.

[00282] Optionally, in some embodiments, the configuration information includes a required field to indicate a PUCCH resource.

[00283] In embodiments of the present disclosure, one mandatory field may be used to indicate a PUCCH resource. Because the second configuration may include the PUCCH resource indication information, the terminal device may transmit the first reporting message to the network device via the PUCCH resource indicated by the PUCCH resource indication information, and the PUCCH resource may be indicated by one mandatory field. In this case, since the second configuration may include one mandatory field for specifying the PUCCH resource, delaying the use of the RACH resource for transmission can be avoided, thereby reducing the delay of the BFR procedure.

[00284] Optionally, in some embodiments, the MAC CE carries SCell beam failure information.

[00285] In embodiments of the present disclosure, the MAC CE may carry SCell beam failure information. The beam failure information may indicate a cell on which a beam failure occurred, a beam on which a beam failure occurred, or a new beam. It may also indicate that there are no beams that meet a predetermined condition.

[00286] Optionally, in some embodiments, the configuration information indicates at least one of the following information: reporting message transmission period over the PUCCH resource, time domain offset of each PUCCH resource period, maximum number of transmissions for reporting message transmissions over the PUCCH resource, a maximum transmission time timer for reporting message transmission over the PUCCH resource, a maximum reporting message transmission time window time over the PUCCH resource, a reporting message transmission interval timer over the PUCCH resource, a cell corresponding to the PUCCH resource, a bandwidth section (BWP) corresponding to the PUCCH resource, and PUCCH format corresponding to the PUCCH resource.

[00287] In embodiments of the present disclosure, the first configuration received by the terminal device may indicate at least one of the above information for configuring a PUCCH resource. For example, this may indicate: a reporting message transmission period over the PUCCH resource, ie, the difference between the current PUCCH resource elapsed time and the next PUCCH resource elapsed time; a time domain offset of each PUCCH resource period; the maximum number of transmissions for reporting message transmissions over the PUCCH resource, i.e., the PUCCH resource may be transmitted periodically, but cannot exceed the maximum number of transmissions for reporting message transmissions over the PUCCH resource.

[00288] The first configuration may also specify a timer or window time to control the maximum transmission time for transmitting the PUCCH resource, i.e., the PUCCH resource may be used to transmit the report message multiple times within the maximum transmission time range configured by the timer or window time. If the maximum transmission time configured by the timer or window time is exceeded and the terminal device has not received the scheduling information related to PUSCH or has not received the feedback information for the MAC CE, the BFR SCell can be considered to be unsuccessful.

[00289] The first configuration may also indicate a timer for controlling the transmission interval of the PUCCH resource, ie, the current time spent transmitting the PUCCH resource may be separated from the start of the next time spent transmitting the PUCCH resource by a period of time. In this case, the duration of this period of time can be of different sizes.

[00290] The first configuration may also indicate the BWP corresponding to the PUCCH resource. If the service volume of the terminal device is large, the BWP corresponding to the PUCCH resource indicated in the first configuration may be wider, for example, it may be 40 MHz; if the amount of service of the terminal device is small, the BWP corresponding to the PUCCH resource indicated in the first configuration may be smaller, for example, may be 10 MHz.

[00291] It should be understood that the numerical values in the embodiments of the present disclosure are only examples, and may also be other numerical values that should not specifically limit the present disclosure.

[00292] Optionally, in some embodiments, the cell that transmits the PUCCH resource may be a PCell, SCell, or SCell that supports the terminal device's PUCCH transmission.

[00293] In embodiments of the present disclosure, since the corresponding PCell or PSCell is still in the normal state in the case where a beam failure occurs in the SCell of the terminal device, the cell transmitting the PUCCH resource may be a PCell or PSCell of the terminal device. In addition, the network device may configure a SCell that can support PUCCH transmission for the terminal device, and in the case where a beam failure occurs in the SCell of the terminal device, a report message can be sent to the network device via the SCell that supports PUCCH resource transmission.

[00294] Optionally, in some embodiments, the PUCCH format corresponding to the PUCCH resource is format 0 or format 1.

[00295] In embodiments of the present disclosure, the format corresponding to the PUCCH resource may be format 0 or format 1. It should be understood that since the format corresponding to the PUCCH resource may include format 0, format 1, format 2, format 3, and format 4, lengths in OFDM symbols are respectively 1-2, 4-14, 1-2, 4-14, 4-14. Among these 5 formats, the bit numbers of format 0 and format 1 are less than or equal to 2, and the numbers of bits of format 2, format 3, and format 4 are greater than 2. Therefore, the PUCCH format corresponding to the PUCCH resource in the embodiments of the present disclosure may be format 0 and format 1, so that the number of transmitted bits during transmission will be small.

[00296] Optionally, in some embodiments, if the PUCCH format corresponding to the PUCCH resource is format 0, the parameter in the PUCCH resource cyclic factor is a specific value.

[00297] Optionally, in some embodiments, if the PUCCH format corresponding to the PUCCH resource is format 1, the bit value of the reporting message sent on the PUCCH resource is a particular value.

[00298] In embodiments of the present disclosure, if the format corresponding to the PUCCH resource is format 0, the parameter in the cyclic coefficient of the PUCCH resource may have a specific value. It should be understood that the PUCCH resource corresponds to a sequence, and different sequences may convey different information. By changing the value of the cyclic coefficient, the PUCCH resource can be used to convey various information.

[00299] In embodiments of the present disclosure, if the format corresponding to the PUCCH resource is format 1, the bit value of the reporting message transmitted on the PUCCH resource may be a specific value, for example, it may be 00, 01, 10, 11, etc. d.

[00300] Optionally, in some embodiments, a specific value is prescribed by a protocol or configured by a network device.

[00301] In embodiments of the present disclosure, the value of the PUCCH resource cyclic factor parameter or the bit value of the reporting message transmitted on the PUCCH resource may be set by a protocol or configured by a network device. For example, in an implementation, the protocol may dictate that the value of the PUCCH resource cyclic coefficient parameter may be 0, or the bit value of the report message transmitted on the PUCCH resource may be 00.

[00302] In another implementation, the network device may configure the PUCCH resource cyclic coefficient parameter to 0 or configure the PUCCH resource reporting message bit value to 01.

[00303] It should be understood that the above numerical values are merely illustrative, and may also be other numerical values that are not specifically limited in the present disclosure.

[00304] Optionally, in some embodiments, the order of priority for information or data transmission may be:

[00305] d1: The transmission priority of the MAC CE is higher than the transmission priority of any logical channel.

[00306] d2: The transmission priority of the MAC CE is higher than the transmission priority of the C-RNTI information or data from the UL-CCCH.

[00307] d3: The transmission priority of the MAC CE is lower than the transmission priority of the C-RNTI information or data from the UL-CCCH and higher than the transmission priority of the configured grant confirmation information.

[00308] d4: The transmission priority of the MAC CE is the same as the transmission priority of the C-RNTI information or data from the UL-CCCH.

[00309] d5: The transmission priority of the MAC CE is the same as the transmission priority of the configured grant confirmation information.

[00310] d6: The transmission priority of the MAC CE is lower than the transmission priority of configured grant confirmation information and higher than the transmission priority of BSR information.

[00311] d7: The transmission priority of the MAC CE is the same as the transmission priority of the BSR information.

[00312] d8: The transmission priority of the MAC CE is lower than the transmission priority of the BSR information and higher than the transmission priority of one piece of PHR information or multiple pieces of PHR information.

[00313] The priority of data or information transmission based on rules d1-d8 is similar to the process of rules a1-a8, and reference can be made to the above process. For brevity, this will not be repeated here.

[00314] Optionally, in some embodiments, in response to the fact that the number of transmissions of the reporting message by the terminal device via the PUCCH resource is greater than or equal to the maximum number of transmissions of the transmission of the reporting message via the PUCCH resource, the terminal device confirms that the BFR SCell is unsuccessful; or in response to the second timer used to control the maximum transmission time for transmitting the PUCCH resource expires, the terminal device confirms that the BFR SCell is unsuccessful; or the MAC CE is not transmitted to the network device via the PUSCH resource by the terminal device, or the DCI for scheduling the PUSCH resource is not received by the terminal device within the first window time, the terminal device confirms that the BFR SCell is unsuccessful; or in the case where the MAC CE is transmitted to the network device by the terminal device, and the feedback information or response message for the MAC CE is not received by the terminal device, the terminal device confirms that the BFR SCell is unsuccessful.

[00315] In one implementation, if the number of uses of the PUCCH resource to provide a message by the terminal device is greater than or equal to the maximum number of transmissions of the reported message transmission over the PUCCH resource, the terminal device confirms that the BFR SCell is unsuccessful. For example, if the maximum number of transmissions when transmitting a report message over a PUCCH resource is 10, after the terminal device uses the PUCCH resource to send a report message to request the resource for the 10th time, but the request was not successful, and when the terminal device uses the PUCCH resource to retransmit the report message, it can be acknowledged that the BFR SCell of the terminal device is unsuccessful in this case because the maximum number of transmissions for transmitting the report message over the PUCCH resource has been exceeded.

[00316] Optionally, the number of transmissions of the reporting message transmission over the PUCCH resource referred to in the embodiments of the present disclosure may be the number of transmissions of the actual reporting message transmissions over the PUCCH resource, or may be the sum of the number of transmissions of the actual reporting message transmissions over the PUCCH resource and the number of actual not transmitting reporting messages with the possibility of transmission.

[00317] As above, if reporting message transmission over the PUCCH resource overlaps with the measurement gap, the terminal device may cancel or stop transmission of the report message in the current PUCCH resource time spent in transmission, or if reporting message transmission over the PUCCH resource overlaps with PUCCH resource transmission , the terminal device cancels or stops transmission of the report message in the current PUCCH resource time spent on transmission. Therefore, in these two cases, the terminal device may transmit the reporting message via the PUCCH resource, but ultimately does not use the current transmission time of the PUCCH resource to transmit the reporting message.

[00318] For example, if the maximum number of transmissions when transmitting a report message over the PUCCH resource is 10, the number of actual transmissions of the report message over the PUCCH resource is 5, the number of actually transmittable report messages not transmitted is 6. In one embodiment, the transmission of the report message may be continued; in another embodiment, the sum of the number of actual report message transmissions via the PUCCH resource and the number of report message transmissions actually not transmitted, with the possibility of transmitting more than the maximum number of report message transmission transmissions via the PUCCH resource, it can be confirmed that the terminal device's BFR SCell is unsuccessful.

[00319] In another implementation, in response to the fact that the second timer used to control the maximum transmission time for transmitting the PUCCH resource expires, the terminal device acknowledges that the BFR SCell is unsuccessful.

[00320] In embodiments of the present disclosure, a second timer may be used to control the maximum transmission time for transmitting a PUCCH resource. For example, assuming that the maximum transmission time of the reporting message via the PUCCH resource is 10 ms, if the terminal device transmits the reporting message to the network device via the PUCCH resource within 10 m and does not receive feedback information or response information for the reporting message, it can be confirmed that BFR SCell is unsuccessful.

[00321] In another implementation, for example, assuming that the maximum transmission time of the MAC CE over the PUSCH resource is 10 ms, if the MAC CE is not transmitted over the PUSCH resource or the DCI for scheduling the PUSCH resource is not received within 10 ms, it can be confirmed, that the BFR SCell is unsuccessful. It should be understood that, in embodiments of the present disclosure, the lack of transmission of the MAC CE over the PUSCH resource may mean that the terminal device transmits the MAC CE to the network device and does not receive feedback information for the MAC CE, or the terminal device does not transmit the MAC CE to the network via the PUSCH.

[00322] In another implementation, if the terminal device transmits the MAC CE to the network device and does not receive feedback information or a response message for the MAC CE, the BFR SCell is confirmed to be unsuccessful.

[00323] In embodiments of the present disclosure, a terminal device may transmit a MAC CE to a network device via a PUSCH resource. After receiving the MAC CE, the network device may send feedback information or a response message for the MAC CE to the terminal device. If the terminal device does not receive feedback information or a response message, the terminal device may acknowledge that the BFR SCell is unsuccessful.

[00324] Optionally, in some embodiments, if the terminal device sends the MAC CE to the network device and receives feedback information or a response message for the MAC CE, the BFR SCell is confirmed to be successful.

[00325] In embodiments of the present disclosure, a terminal device may transmit a MAC CE to a network device via a PUSCH resource. After receiving the MAC CE, the network device may send feedback information for the MAC CE to the terminal device. After receiving the feedback information or response message for the MAC CE, the terminal device may confirm that the BFR SCell is successful.

[00326] Optionally, in some embodiments, when the BFR SCell timer expires, in the case where the terminal device transmits the MAC CE to the network device and does not receive feedback information or a response message for the MAC CE, then it is confirmed that the BFR SCell is unsuccessful.

[00327] Optionally, in some embodiments, before the expiration of the BFR SCell timer, in the case where the terminal device transmits the MAC CE to the network device and receives feedback information or a response message for the MAC CE, the BFR SCell is confirmed to be successful.

[00328] In embodiments of the present disclosure, the BFR timer may track the time of the entire BFR procedure. If the terminal device still has not received the feedback information or response message for the MAC CE from the time the terminal device sends a report message to the network device via the PUCCH resource or transmits the MAC CE via the PUSCH resource until the time the BFR timer expires, you can acknowledge, that the terminal device's BFR SCell is unsuccessful; if the terminal device received the feedback information or the response message for the SCell beam failure information before the end of the BFR SCell timer, it can be confirmed that the BFR SCell of the terminal device is successful.

[00329] The timer in the embodiments of the present disclosure can better control the duration of the BFR. It is understood that if the BFR timer is not configured during the BFR procedure, then there is no duration limit, the terminal device will receive SCell beam failure information until a long time has elapsed. In this case, the terminal device's BFR SCell can be considered successful.

[00330] Optionally, in some embodiments, in response to the success of the BFR SCell, the BFR SCell timer is stopped.

[00331] Optionally, in some embodiments, in response to the success of the BFR SCell, the counter used to determine the occurrence of a SCell beam failure is reset to 0.

[00332] In embodiments of the present disclosure, when a terminal device confirms that the BFR of its SCell is successful, the BFR SCell timer may be stopped. It should be understood that the BFR SCell timer is used to keep track of the duration of the BFR SCell, ie to determine if the BFR SCell is successful for a particular period of time. Therefore, when the terminal device acknowledges that its SCell's BFR is successful, it may stop the BFR SCell timer in response to the success of the BFR SCell.

[00333] The counter in the embodiments of the present disclosure is used to determine the occurrence of a beam failure SCell, that is, for a specific period of time, if the number of BFI counted by the counter is within a specific value, then it can be considered that beam failure does not occur in the SCell of the terminal device . Therefore, when the terminal device acknowledges the successful execution of the BFR of its SCell, it may reset the counter used to determine the occurrence of a SCell beam failure to 0 in response to the successful execution of the BFR SCell.

[00334] Optionally, in some embodiments, the timer is configured by the network device for the terminal device.

[00335] Optionally, in some embodiments, the implementation of the timer is configured by the network device for the terminal device through RRC signaling.

[00336] In embodiments of the present disclosure, the BFR SCell timer may be configured by a network device for a terminal device. In addition, the BFR SCell timer may be configured by the network device to the terminal device through RRC signaling. The duration of the configured BFR timer may also be determined by the network device, for example, it may be 100 ms or 1 s, which is not specifically limited in this disclosure.

[00337] Optionally, in some embodiments, the start or restart time of the BFR timer is one of the following times:

[00338] when the terminal device detects that a beam failure occurs in a secondary cell; after the terminal apparatus detects that a beam failure occurs in the secondary cell; when transmitting a reporting message via the PUCCH resource; before transmitting the reporting message via the PUCCH resource; after transmitting the reporting message via the PUCCH resource; when transmitting the MAC CE of the secondary cell; before transmitting the MAC CE of the secondary cell; and after transmitting the MAC CE of the secondary cell.

[00339] In embodiments of the present disclosure, the description is taken when or after the terminal device detects that a beam failure occurs in a SCell, as an example. When the terminal device detects that a beam failure occurs in the SCell, a BFR timer may be started. Alternatively, after the terminal device detects that a beam failure has occurred in the SCell, a BFR timer may be started. As to how long the terminal device starts the BFR timer after detecting a beam failure in the SCell, this may be determined by the terminal device. For example, the terminal device may start the BFR timer 2 ms after detecting a beam failure that occurred in a SCell.

[00340] The numerical values in the embodiments of the present disclosure are merely examples, and may also be other numerical values that are not specifically limited in the present disclosure.

[00341] Similarly, the process of starting or restarting the BFR timer in other cases will not be repeated here.

[00342] Therefore, according to the wireless communication method of embodiments of the present disclosure, a network device can transmit configuration information to a terminal device. The configuration information may be used to configure the PUCCH resource. After receiving the configuration information, the terminal device may transmit a report message via the PUCCH resource or transmit a MAC CE via the PUSCH resource. In addition, when the PUCCH resource used by the terminal device to transmit the reporting message to the network device overlaps with another resource, such as the first PUSCH resource, the terminal device can transmit the MAC CE through the first PUSCH resource, which can reduce unnecessary transmission of the PUCCH resource, which can reduce the delay of the BFR procedure.

[00343] Embodiments of the method of the present disclosure are detailed above with reference to FIGS. 2-4, and embodiments of the apparatus of the present disclosure are detailed below with reference to FIGS. 5-11. It should be understood that embodiments of the device and embodiments of the method correspond to each other, and a similar description may apply to embodiments of the method.

[00344] FIG. 5 is a schematic block diagram of a terminal device 500, in accordance with some embodiments of the present disclosure.

[00345] As shown in FIG. 5, the terminal apparatus 500 includes: a processing unit 510, configured to generate a request message in response to a beam failure occurring in a secondary cell; and the request message corresponds to the first configuration or the second configuration, the first configuration is a scheduling request configuration associated with at least one logical channel, and the second configuration is a scheduling request configuration not associated with a logical channel.

[00346] Optionally, in some embodiments, a request message is used to request an uplink transmission resource from a network device and/or notify the network device that a beam failure has occurred in a secondary cell.

[00347] Optionally, in some embodiments, in response to the configuration corresponding to the request message being the first configuration, the first configuration is determined from a set of configurations based on at least one of the following: network device identifier, identifier a scheduling request corresponding to each configuration in the configuration set, a resource identifier corresponding to each configuration in the configuration set, and a priority order of logical channels corresponding to the respective configurations in the configuration set; or the first configuration is chosen arbitrarily from the set of configurations; and the configuration set includes a configuration of at least one scheduling request, and each scheduling request corresponds to at least one logical channel.

[00348] Optionally, in some embodiments, the network device indication information is indicated by configuration information corresponding to beam failure recovery (BFR).

[00349] Optionally, in some embodiments, the first configuration is a configuration in the configuration set that satisfies the following condition: the corresponding configuration scheduling request ID is the highest or the lowest, or the resource ID corresponding to the corresponding configuration scheduling request is the highest or the lowest.

[00350] Optionally, in some embodiments, the first configuration is a configuration in the configuration set that satisfies the following condition: the priority of the logical channel associated with the scheduling request corresponding to the configuration is the highest or the lowest.

[00351] Optionally, in some embodiments, the scheduling request ID of the second configuration is different from the scheduling request ID corresponding to the scheduling request configuration associated with the logical channel; and/or the resource identifier of the scheduling request corresponding to the second configuration is different from the resource identifier of the scheduling request corresponding to the configuration of the scheduling request associated with the logical channel.

[00352] Optionally, in some embodiments, the second configuration parameter type is the same as some or all of the logical channel scheduling request configuration parameter types.

[00353] Optionally, in some embodiments, the second configuration scheduling request identifier value is an integer greater than or equal to 8.

[00354] Optionally, in some embodiments, the second configuration scheduling request resource identifier value is an integer greater than or equal to 9 or equal to 0.

[00355] Optionally, in some embodiments, the second configuration indicates a Physical Uplink Control Channel (PUCCH) resource.

[00356] Optionally, in some embodiments, the signaling corresponding to the second configuration includes a mandatory field to indicate the PUCCH resource.

[00357] Optionally, in some embodiments, the PUCCH format corresponding to the PUCCH resource is PUCCH format 0 or PUCCH format 1.

[00358] Optionally, in some embodiments, the second configuration is indicated by a configuration message corresponding to the BFR.

[00359] Optionally, in some embodiments, the transmission priority of beam failure information of the secondary cell is higher than the transmission priority of any logical channel; or the transmission priority of the beam failure information of the secondary cell is higher than the transmission priority of Radio Network Cell Temporary Identifier (C-RNTI) information or data from the Uplink Common Control Channel (UL-CCCH); or the transmission priority of the beam failure information of the secondary cell is lower than the transmission priority of the C-RNTI information or data from the UL-CCCH and higher than the transmission priority of the configured grant confirmation information; or the transmission priority of the beam failure information of the secondary cell is the same as the transmission priority of the C-RNTI information or data from the UL-CCCH; or the beam failure information transmission priority of the secondary cell is the same as the configured grant confirmation information transmission priority; or the transmission priority of beam failure information of the secondary cell is lower than the transmission priority of configured grant confirmation information and higher than the transmission priority of Buffer Status Report (BSR) information; or the beam failure information transmission priority of the secondary cell is the same as the BSR information transmission priority; or the transmission priority of the beam failure information of the secondary cell is lower than the transmission priority of the BSR information and higher than the transmission priority of one piece of Power Headroom Report (PHR) information or a plurality of pieces of PHR information.

[00360] Optionally, in some embodiments, the request message is transmitted to a specific cell of the terminal device, and the specific cell of the terminal device includes a primary cell or a primary secondary cell.

[00361] Optionally, in some embodiments, the terminal device further includes: a communication module configured to transmit beam failure information of the secondary cell to the network device.

[00362] Optionally, in some embodiments, beam failure information of the secondary cell is transmitted to a specific cell of the terminal device, and the specific cell of the terminal device includes a primary cell or a primary secondary cell of the terminal device.

[00363] Optionally, in some embodiments, secondary cell beam failure information is transmitted via a Medium Access Control (MAC) Control Element (CE).

[00364] Optionally, in some embodiments, beam failure information is transmitted in a first resource, and the first resource is the resource indicated by the response message to the request message.

[00365] Optionally, in some embodiments, the processing module 510 is further configured to: in the case where the number of transmissions of the request message is greater than or equal to the maximum number of transmissions indicated by the configuration of the request message, confirm that the BFR of the secondary cell is unsuccessful; or, in response to transmitting the beam failure information of the secondary cell to the network device and not receiving feedback information or a response message for the beam failure information of the secondary cell, confirm that the BFR of the secondary cell is unsuccessful.

[00366] Optionally, in some embodiments, the terminal device further includes: a communication module, configured to transmit beam failure information of the secondary cell to the network device; and the processing unit 510 is further configured to: when the BFR timer of the secondary cell ends, confirm that the BFR of the secondary cell is unsuccessful in response to not receiving feedback information or a response message for the beam failure information of the secondary cell.

[00367] Optionally, in some embodiments, the processing module 510 is further configured to: terminate the secondary cell.

[00368] Optionally, in some embodiments, the terminal device further includes: a communication module, configured to transmit beam failure information of the secondary cell to the network device; and the processing unit 510 is further configured to confirm that the BFR of the secondary cell is successful in response to receiving feedback information or a response message for beam failure information of the secondary cell.

[00369] Optionally, in some embodiments, the processing module 510 is further configured to: before the secondary cell BFR timer expires, confirm that the secondary cell BFR is successful, in response to receiving feedback information or a response message for information about the beam failure of the secondary cell.

[00370] Optionally, in some embodiments, the processing module 510 is further configured to: in response to the BFR of the secondary cell being successful, stop the timer corresponding to the BFR of the secondary cell.

[00371] Optionally, in some embodiments, the processing module 510 is further configured to: in response to the BFR of the secondary cell being successful, reset the counter used to determine the occurrence of a beam failure in the secondary cell to 0.

[00372] Optionally, in some embodiments, the implementation of the timer is configured by the network device for the terminal device.

[00373] Optionally, in some embodiments, the timer is configured by the network device for the terminal device via Radio Resource Control (RRC) signaling.

[00374] Optionally, in some embodiments, the time to start or restart the timer is one of the following times: when the terminal device detects that a beam failure occurs in a secondary cell; after the terminal apparatus detects that a beam failure occurs in the secondary cell; when generating a request message; before generating a request message; after generating a request message; when sending a request message; before sending the request message; after the transmission of the request message; when transmitting beam failure information of the secondary cell; before transmitting beam failure information of the secondary cell; and after transmitting the beam failure information of the secondary cell.

[00375] FIG. 6 is a schematic block diagram of a terminal device 600 according to another embodiment of the present disclosure.

[00376] As shown in FIG. 6, the terminal apparatus 600 includes: a communication unit 610 configured to receive configuration information, and the configuration information is used to configure a Physical Uplink Control Channel (PUCCH) resource; and the communication unit 610 is further configured to: in response to a beam failure occurring in the secondary cell, transmit a report message via the PUCCH resource and/or transmit a Media Access Control (MAC) control element (CE) via the physical uplink shared channel resource communication (PUSCH).

[00377] Optionally, in some embodiments, the terminal device further includes: a processing module configured to cancel or stop transmission of the report message in the current PUCCH resource time spent in transmission in response to satisfaction of one or more of the following conditions: first a timer corresponding to the PUCCH resource operates at the current transmission time of the PUCCH resource, and the first timer is used to control the transmission interval of the PUCCH resource; the current elapsed transmission time of the PUCCH resource overlaps with the first PUSCH resource included in the PUSCH resource; the second PUSCH resource included in the PUSCH resource exists in the first time period or in the second time period, the end time of the first time period is earlier than the current time spent in transmission or is within the current time spent in transmission, and the start time of the second time period is later than the current time spent in transmission. transmission time or is time within the current time spent on transmission; downlink control information (DCI) for scheduling the third PUSCH resource included in the PUSCH resource exists in the third time period or the fourth time period, the end time of the third time period is earlier than the current transmission time spent or is within the current transmission time spent, and the start time of the fourth time period is later than the current spent transmission time or is a time within the current transmission spent time; the current elapsed transmission time of the PUCCH resource overlaps with the measurement gap; a second timer corresponding to the PUCCH resource stops or expires at the current transmission time spent on the PUCCH resource, and the second timer is used to control the maximum transmission time for transmitting the PUCCH resource; the current transmission time of the PUCCH resource overlaps with a transmission resource carrying hybrid automatic repeat request (HARQ) information, and the transmission resource corresponds to the time domain resource used for transmission; the current elapsed transmission time of the PUCCH resource overlaps with the transmission resource corresponding to the scheduling request, and the transmission resource corresponds to the time domain resource used for transmission; before the current spent transmission time of the PUCCH resource, the terminal device receives a DCI for scheduling a fourth PUSCH resource included in the PUSCH resource; before the current elapsed transmission time of the PUCCH resource, the MAC CE is transmitted by the terminal device via the PUSCH resource, or the MAC CE is successfully transmitted by the terminal device via the PUSCH resource.

[00378] Optionally, in some embodiments, in response to the satisfaction of one or more of the following conditions, the report message is transmitted in the current expended transmission time of the PUCCH resource: the first timer corresponding to the PUCCH resource stops or expires in the current expended transmission time of the resource PUCCH, and the first timer is used to control the transmission interval of the PUCCH resource; the current elapsed transmission time of the PUCCH resource does not overlap with the PUSCH resource; the current elapsed transmission time of the PUCCH resource does not overlap with the measurement gap; a second timer corresponding to the PUCCH resource operates at the current transmission time spent on the PUCCH resource, and the second timer is used to control the maximum transmission time for transmitting the PUCCH resource; the current transmission time of the PUCCH resource does not overlap with the transmission resource carrying HARQ information, and the transmission resource corresponds to the time domain resource used for transmission; the current spent transmission time of the PUCCH resource does not overlap with the transmission resource corresponding to the scheduling request, and the transmission resource corresponds to the time domain resource used for transmission; before the current PUCCH resource elapsed time, the terminal device does not receive a DCI for scheduling the PUSCH resource; The DCI for PUSCH resource scheduling is not received in the third time period or the fourth time period, the end time of the third time period is earlier than the current spent transmission time or is within the current spent transmission time, and the start time of the fourth time period is later than the current spent transmission time or is time within the current time spent on transmission; before the current elapsed transmission time of the PUCCH CE resource, the MAC is not transmitted by the terminal device via the PUSCH resource; and before the current PUCCH resource elapsed time, the transmission of the MAC CE over the PUSCH resource by the terminal device is unsuccessful.

[00379] Optionally, in some embodiments, the PUSCH resource includes a fourth PUSCH resource, and the fourth PUSCH resource is the resource indicated by the response message for the report message.

[00380] Optionally, in some embodiments, the PUSCH resource includes a first PUSCH resource, and the first PUSCH resource overlaps with the current elapsed transmission time of the PUCCH resource; and/or the PUSCH resource includes a second PUSCH resource, the second PUSCH resource is located in the first time period or in the second time period in the time domain, the end time of the first time period is earlier than the current time spent on transmission or is a time within the current time spent on transmission, and the start time of the second period of time is later than the current elapsed transmission time or is a time within the current elapsed transmission time; and/or the PUSCH resource includes a third PUSCH resource, the DCI for scheduling the third PUSCH resource is in the third time period or the fourth time period in the time domain, the end time of the third time period is earlier than the current spent transmission time or is within the current transmission spent time time, and the start time of the fourth period of time is later than the current elapsed transmission time or is a time within the current elapsed transmission time; and/or the PUSCH resource includes a fifth PUSCH resource, and the fifth PUSCH resource is scheduled by configured grant type 1 or configured grant type 2.

[00381] Optionally, in some embodiments, the terminal device further includes: a processing module configured to: in response to a successful transmission of the MAC CE by the terminal device via the PUSCH resource, no longer transmit a report message via the PUCCH resource.

[00382] Optionally, in some embodiments, the terminal device further includes: a processing module configured to: stop a second timer in response to the terminal device transmitting a MAC CE over a PUSCH resource or receiving a DCI for scheduling a PUSCH resource, and a second Timer used to control the maximum transmission time for PUCCH resource transmission.

[00383] Optionally, in some embodiments, the end time of the first time period or the third time period is the starting point of the first PUCCH resource symbol.

[00384] Optionally, in some embodiments, the duration value of the first time period or the third time period is determined according to at least one of the following situations: protocol prescription, network device preconfiguration, and terminal device reporting functionality.

[00385] Optionally, in some embodiments, the start time of the second time period or the fourth time period is the end point of the last symbol or the start point of the first symbol of the PUCCH resource.

[00386] Optionally, in some embodiments, the duration value of the second time period or the fourth time period is determined according to at least one of the following situations: protocol prescription, network device preconfiguration, and terminal device reporting functionality.

[00387] Optionally, in some embodiments, the configuration information includes a mandatory field to indicate a PUCCH resource.

[00388] Optionally, in some embodiments, the MAC CE carries beam failure information of the secondary cell.

[00389] Optionally, in some embodiments, the configuration information indicates at least one of the following information: report message transmission period over PUCCH resource, time domain offset of each PUCCH resource period, maximum number of report message transmission transmissions over PUCCH resource, timer maximum transmission time for reporting message transmission over PUCCH resource, maximum reporting message transmission time window time over PUCCH resource, reporting message transmission interval timer over PUCCH resource, cell corresponding to PUCCH resource, bandwidth section (BWP) corresponding to PUCCH resource, and format PUCCH corresponding to the PUCCH resource.

[00390] Optionally, in some embodiments, the cell corresponding to the PUCCH resource is a primary cell, a primary secondary cell, or a secondary cell supporting PUCCH transmission of the terminal device.

[00391] Optionally, in some embodiments, the PUCCH format corresponding to the PUCCH resource is PUCCH format 0 or PUCCH format 1.

[00392] Optionally, in some embodiments, if the PUCCH format corresponding to the PUCCH resource is PUCCH format 0, the parameter in the PUCCH resource cyclic coefficient is a particular value.

[00393] Optionally, in some embodiments, the specific value is prescribed by the protocol or configured by the network device.

[00394] Optionally, in some embodiments, if the PUCCH format corresponding to the PUCCH resource is PUCCH format 1, the bit value of the reporting message sent on the PUCCH resource is a specific value.

[00395] Optionally, in some embodiments, the specific value is prescribed by the protocol or configured by the network device.

[00396] Optionally, in some embodiments, the transmission priority of the MAC CE is higher than the transmission priority of any logical channel; the transmission priority of the MAC CE is higher than the transmission priority of Radio Network Cell Temporary Identifier (C-RNTI) information or data from the Uplink Common Control Channel (UL-CCCH); or the transmission priority of the MAC CE is lower than the transmission priority of Radio Network Cell Temporary Identifier (C-RNTI) information or data from the UL-CCCH and higher than the transmission priority of configured grant confirmation information; or the transmission priority of the MAC CE is the same as the transmission priority of Radio Network Cell Temporary Identifier (C-RNTI) information or data from the UL-CCCH; or the transmission priority of the MAC CE is the same as the transmission priority of the configured grant confirmation information; or the transmission priority of the MAC CE is lower than the transmission priority of the configured grant confirmation information and higher than the transmission priority of Buffer Status Report (BSR) information; or the transmission priority of the MAC CE is the same as the transmission priority of the BSR information; or the transmission priority of the MAC CE is lower than the transmission priority of the BSR information and higher than the transmission priority of one piece of Power Headroom Report (PHR) information or a plurality of pieces of PHR information.

[00397] Optionally, in some embodiments, the terminal device further includes: a processing module configured to: in response to the number of transmissions of the report message by the terminal device via the PUCCH resource being greater than or equal to the maximum number of transmissions, to transmit the report message via the PUCCH resource, confirm that beam failure recovery (BFR) of the secondary cell is unsuccessful; or in response to the second timer used to control the maximum transmission time for transmitting the PUCCH resource expires, confirming that the BFR of the secondary cell is unsuccessful; or if the MAC CE is not transmitted to the network device via the PUSCH resource by the terminal device or the DCI for scheduling the PUSCH resource is not received by the terminal device within the first window time, confirm that the BFR of the secondary cell is unsuccessful; or, in response to the terminal device transmitting the MAC CE to the network device and not receiving feedback information or a response message for the MAC CE, confirm that the BFR of the secondary cell is unsuccessful.

[00398] Optionally, in some embodiments, the number of transmissions of the reporting message by the terminal device via the PUCCH resource is the number of transmissions of the actual transmissions of the reporting message via the PUCCH resource; or the number of transmissions of the report message by the terminal device via the PUCCH resource is the sum of the number of transmissions of the actual transmissions of the report message via the PUCCH resource and the number of times the PUCCH resource is able to transmit but does not transmit the report message.

[00399] Optionally, in some embodiments, the processing module is further configured to: when the timer corresponding to the BFR of the secondary cell expires, confirm that the BFR of the secondary cell is unsuccessful in response to the terminal device transmitting the MAC CE to the device network and did not receive feedback information or a response message for the MAC CE.

[00400] Optionally, in some embodiments, the terminal device further includes: a processing module configured to: in response to the terminal device transmitting the MAC CE to the network device and receiving feedback information or a response message for the MAC CE , confirm that the BFR of the secondary cell is successful.

[00401] Optionally, in some embodiments, the processing module is further configured to: before the secondary cell BFR timer expires, confirm that the secondary cell BFR is successful in response to the terminal device transmitting the MAC CE to the network device and received feedback information or a response message for the MAC CE.

[00402] Optionally, in some embodiments, the processing module is further configured to: in response to the BFR of the secondary cell being successful, stop the timer corresponding to the BFR of the secondary cell.

[00403] Optionally, in some embodiments, the processing module is further configured to: in response to the BFR of the secondary cell being successful, reset the counter used to determine the occurrence of a beam failure in the secondary cell to 0.

[00404] Optionally, in some embodiments, the implementation of the timer is configured by the network device for the terminal device.

[00405] Optionally, in some embodiments, the implementation of the timer is configured by the network device for the terminal device through radio resource control (RRC) signaling.

[00406] Optionally, in some embodiments, the time to start or restart the BFR timer is one of the following times: when the terminal device detects that a beam failure occurs in a secondary cell; after the terminal apparatus detects that a beam failure occurs in the secondary cell; when transmitting a reporting message via the PUCCH resource; before transmitting the reporting message via the PUCCH resource; after transmitting the reporting message via the PUCCH resource; when transmitting the MAC CE of the secondary cell; before transmitting the MAC CE of the secondary cell; and after transmitting the MAC CE of the secondary cell.

[00407] FIG. 7 is a block diagram of a network device 700, in accordance with some embodiments of the present invention.

[00408] As shown in FIG. 7, the network device 700 includes: a communication module 710, configured to receive a request message transmitted from a terminal device in response to a beam failure occurring in a secondary cell; and the request message corresponds to the first configuration or the second configuration, the first configuration is a scheduling request configuration associated with the at least one logical channel, and the second configuration is a scheduling request configuration not associated with the logical channel.

[00409] Optionally, in some embodiments, a request message is used to request an uplink transmission resource from a network device and/or notify the network device that a beam failure has occurred in a secondary cell.

[00410] Optionally, in some embodiments, the scheduling request ID of the second configuration is different from the scheduling request ID corresponding to the scheduling request configuration associated with the logical channel; and/or the resource identifier of the scheduling request corresponding to the second configuration is different from the resource identifier of the scheduling request corresponding to the configuration of the scheduling request associated with the logical channel.

[00411] Optionally, in some embodiments, the second configuration parameter type is the same as some or all of the logical channel scheduling request configuration parameter types.

[00412] Optionally, in some embodiments, the second configuration scheduling request identifier value is an integer greater than or equal to 8.

[00413] Optionally, in some embodiments, the second configuration scheduling request resource identifier value is an integer greater than or equal to 9 or equal to 0.

[00414] Optionally, in some embodiments, the second configuration indicates a Physical Uplink Control Channel (PUCCH) resource.

[00415] Optionally, in some embodiments, the signaling corresponding to the second configuration includes a mandatory field to indicate the PUCCH resource.

[00416] Optionally, in some embodiments, the PUCCH format corresponding to the PUCCH resource is PUCCH format 0 or PUCCH format 1.

[00417] Optionally, in some embodiments, the second configuration is indicated by a beam failure recovery (BFR) configuration message.

[00418] Optionally, in some embodiments, the request message is sent to a specific cell of the terminal device, and the specific cell of the terminal device includes a primary cell or a primary secondary cell.

[00419] Optionally, in some embodiments, communication module 710 is further configured to receive beam failure information of a secondary cell.

[00420] Optionally, in some embodiments, beam failure information of the secondary cell is transmitted to a specific cell of the terminal device, and the specific cell of the terminal device includes a primary cell or a primary secondary cell of the terminal device.

[00421] Optionally, in some embodiments, secondary cell beam failure information is transmitted via a Medium Access Control (MAC) Control Element (CE).

[00422] Optionally, in some embodiments, beam failure information is transmitted in a first resource, and the first resource is the resource indicated by the response message to the request message.

[00423] FIG. 8 is a block diagram of a network device 800 according to another embodiment of the present invention.

[00424] As shown in FIG. 8, the network device 800 includes: a communication unit 810, configured to transmit configuration information to the terminal device, and the configuration information is used to configure a Physical Uplink Control Channel (PUCCH) resource; and the communication unit 810 is further configured to receive a report message sent by the terminal device via the PUCCH resource and/or a Medium Access Control (MAC) control element (CE) sent by the terminal device via the Physical Uplink Shared Channel (PUSCH) resource. , in response to a beam failure occurring in the secondary cell.

[00425] Optionally, in some embodiments, the network device further includes: a processing module, configured to cancel or stop receiving a report message transmitted by the terminal device in the current transmission time of the PUCCH resource in response to satisfying one or more of the following: the first timer corresponding to the PUCCH resource is running in the current transmission time of the PUCCH resource, and the first timer is used to control the transmission interval of the PUCCH resource; the current elapsed transmission time of the PUCCH resource overlaps with the first PUSCH resource included in the PUSCH resource; the second PUSCH resource included in the PUSCH resource exists in the first time period or in the second time period, the end time of the first time period is earlier than the current time spent in transmission or is within the current time spent in transmission, and the start time of the second time period is later than the current time spent in transmission. transmission time or is time within the current time spent on transmission; downlink control information (DCI) for scheduling the third PUSCH resource included in the PUSCH resource exists in the third time period or the fourth time period, the end time of the third time period is earlier than the current transmission time spent or is within the current transmission time spent, and the start time of the fourth time period is later than the current spent transmission time or is a time within the current transmission spent time; the current elapsed transmission time of the PUCCH resource overlaps with the measurement gap; a second timer corresponding to the PUCCH resource stops or expires at the current transmission time spent on the PUCCH resource, and the second timer is used to control the maximum transmission time for transmitting the PUCCH resource; the current transmission time of the PUCCH resource overlaps with a transmission resource carrying hybrid automatic repeat request (HARQ) information, and the transmission resource corresponds to the time domain resource used for transmission; the current elapsed transmission time of the PUCCH resource overlaps with the transmission resource corresponding to the scheduling request, and the transmission resource corresponds to the time domain resource used for transmission; before the current spent transmission time of the PUCCH resource by the network device, a DCI is transmitted to the terminal device to schedule a fourth PUSCH resource included in the PUSCH resource; before the current PUCCH resource elapsed time, the network device receives the MAC CE transmitted by the terminal device via the PUSCH.

[00426] Optionally, in some embodiments, communication module 810 is further configured to: responsive to one or more of the following conditions being met, receive a report message transmitted by the terminal device in the current PUCCH resource time spent transmitting: first timer, corresponding to the PUCCH resource stops or expires at the current transmission elapsed time of the PUCCH resource, and the first timer is used to control the transmission interval of the PUCCH resource; the current elapsed transmission time of the PUCCH resource does not overlap with the PUSCH resource; the current elapsed transmission time of the PUCCH resource does not overlap with the measurement gap; a second timer corresponding to the PUCCH resource operates at the current transmission time spent on the PUCCH resource, and the second timer is used to control the maximum transmission time for transmitting the PUCCH resource; the current transmission time of the PUCCH resource does not overlap with the transmission resource carrying HARQ information, and the transmission resource corresponds to the time domain resource used for transmission; the current spent transmission time of the PUCCH resource does not overlap with the transmission resource corresponding to the scheduling request, and the transmission resource corresponds to the time domain resource used for transmission; before the current PUCCH resource transmission time spent, the DCI for scheduling the PUSCH resource is not transmitted to the terminal device by the network device; The PUSCH resource scheduling DCI is not transmitted to the terminal device in the third time period or the fourth time period, the end time of the third time period is earlier than the current transmission time spent or is within the current transmission time spent, and the start time of the fourth time period is later than the current transmission time spent time or is the time within the current time spent on transmission; and before the current elapsed transmission time of the PUCCH CE resource, the MAC transmitted by the terminal device via the PUSCH resource is not received by the network device.

[00427] Optionally, in some embodiments, the PUSCH resource includes a fourth PUSCH resource, and the fourth PUSCH resource is the resource indicated by the response message for the report message.

[00428] Optionally, in some embodiments, the PUSCH resource includes a first PUSCH resource, and the first PUSCH resource overlaps with the current elapsed transmission time of the PUCCH resource; and/or the PUSCH resource includes a second PUSCH resource, the second PUSCH resource is located in the first time period or in the second time period in the time domain, the end time of the first time period is earlier than the current time spent on transmission or is a time within the current time spent on transmission, and the start time of the second period of time is later than the current elapsed transmission time or is a time within the current elapsed transmission time; and/or the PUSCH resource includes a third PUSCH resource, the DCI for scheduling the third PUSCH resource is in the third time period or the fourth time period in the time domain, the end time of the third time period is earlier than the current spent transmission time or is within the current transmission spent time time, and the start time of the fourth period of time is later than the current elapsed transmission time or is a time within the current elapsed transmission time; and/or the PUSCH resource includes a fifth PUSCH resource, and the fifth PUSCH resource is scheduled by configured grant type 1 or configured grant type 2.

[00429] Optionally, in some embodiments, the end time of the first time period or the third time period is the starting point of the first PUCCH resource symbol.

[00430] Optionally, in some embodiments, the duration value of the first time period or the third time period is determined according to at least one of the following situations: protocol prescription, network device preconfiguration, and terminal device reporting functionality.

[00431] Optionally, in some embodiments, the start time of the second time period or the fourth time period is the end point of the last symbol or the start point of the first symbol of the PUCCH resource.

[00432] Optionally, in some embodiments, the duration value of the second time period or the fourth time period is determined according to at least one of the following situations: protocol prescription, network device preconfiguration, and terminal device reporting capability.

[00433] Optionally, in some embodiments, the configuration information includes a mandatory field to indicate a PUCCH resource.

[00434] Optionally, in some embodiments, the MAC CE carries beam failure information of the secondary cell.

[00435] Optionally, in some embodiments, the configuration information indicates at least one of the following information: report message transmission period over the PUCCH resource, time domain offset of each PUCCH resource period, maximum number of report message transmission transmissions over the PUCCH resource, timer maximum transmission time for reporting message transmission over PUCCH resource, maximum reporting message transmission time window time over PUCCH resource, reporting message transmission interval timer over PUCCH resource, cell corresponding to PUCCH resource, bandwidth section (BWP) corresponding to PUCCH resource, and format PUCCH corresponding to the PUCCH resource.

[00436] Optionally, in some embodiments, the cell corresponding to the PUCCH resource is a primary cell, a primary secondary cell, or a secondary cell supporting PUCCH transmission of the terminal device.

[00437] Optionally, in some embodiments, the PUCCH format corresponding to the PUCCH resource is PUCCH format 0 or PUCCH format 1.

[00438] Optionally, in some embodiments, if the PUCCH format corresponding to the PUCCH resource is PUCCH format 0, the parameter in the PUCCH resource cyclic coefficient is a particular value.

[00439] Optionally, in some embodiments, a particular value is prescribed by a protocol or configured by a network device.

[00440] Optionally, in some embodiments, if the PUCCH format corresponding to the PUCCH resource is PUCCH format 1, the bit value of the report message sent on the PUCCH resource is a particular value.

[00441] Optionally, in some embodiments, a specific value is prescribed by a protocol or configured by a network device.

[00442] Embodiments of the present disclosure also provide a communication device 900. The communication device 900 shown in FIG. 9 includes a processor 910 and a memory 920. The memory 920 is adapted to store a computer program, and the processor 910 is configured to call and execute the computer program stored in the memory to implement the method in the embodiments of the present disclosure.

[00443] The processor 910 may recall the computer program from memory and execute the computer program to implement the method in the embodiments of the present disclosure.

[00444] Memory 920 may be a component independent of processor 910 or may be integrated with processor 910.

[00445] Optionally, as shown in FIG. 9, communication device 900 may further include a transceiver 930. Processor 910 may control transceiver 930 to communicate with another device, and in particular, transceiver 930 may transmit information or data to another device or receive information or data transmitted by another device.

[00446] The transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include an antenna. There may be one or more antennas.

[00447] Optionally, the communication device 900 may be a network device in the embodiments of the present disclosure, and the communication device 900 may implement the corresponding procedures implemented by the network device in various ways in the embodiments of the present disclosure. For brevity, the details are not repeated here.

[00448] Optionally, the communication device 900 may be a mobile terminal/terminal in the embodiments of the present disclosure, and the communication device 900 may implement the corresponding procedures implemented by the terminal device in various ways in the embodiments of the present disclosure. For brevity, the details are not repeated here.

[00449] FIG. 10 is a schematic structural diagram of a chip according to an embodiment of the present disclosure. The chip 1000 shown in FIG. 10 includes a processor 1010. The processor 1010 may recall a computer program from memory and execute the computer program to implement the method in the embodiments of the present disclosure.

[00450] Optionally, as shown in FIG. 10, chip 1000 may further include memory 1020. Processor 1010 may recall a computer program from memory 1020 and execute the computer program to implement the method in the embodiments of the present disclosure.

[00451] Memory 1020 may be a component independent of processor 1010 or may be integrated with processor 1010.

[00452] Optionally, the chip 1000 may further include an input interface 1030. The processor 1010 may control the input interface 1030 to communicate with another device or chip, and in particular, the input interface 1030 may receive information or data transmitted by another device or chip.

[00453] Optionally, chip 1000 may further include an output interface 1040. The processor 1010 may control the output interface 1040 to communicate with another device or chip, and in particular, the output interface 1040 may output information or data to another device or chip.

[00454] Additionally, the chip may be applied in the network device according to the embodiments of the present disclosure, and the chip may implement the corresponding procedures implemented by the network device in various ways in the embodiments of the present disclosure. For brevity, the details are not repeated here.

[00455] Optionally, the chip may be applied to the mobile terminal/terminal device in the embodiments of the present disclosure, and the chip may implement the corresponding procedures implemented by the mobile terminal/terminal device in various ways in the embodiments of the present disclosure. For brevity, the details are not repeated here.

[00456] It should be noted that a chip referred to in embodiments of the present disclosure may also be referred to as a system-level chip, system chip, microchip system, system on a chip, or the like.

[00457] It should be understood that the processor of embodiments of the present disclosure may be an integrated circuit chip, has signal processing capability, the steps of the embodiment of the method described above may be implemented using a hardware integrated logic circuit in the processor and/or implemented using instructions in the form of software security. The above processor may be a general purpose processor, a digital signal processor (DSP), a programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other programmable logic device, transistorized logic device, or discrete hardware component. The aforementioned general purpose processor may be a microprocessor, or may be any conventional processor, or the like. The steps of the methods disclosed with reference to embodiments of the present invention may be executed and completed directly by a hardware decoding processor, or may be performed and completed using a combination of hardware and software modules in a decoding processor. The software module may be located in a storage medium known in the art, such as random access memory, flash memory, read only memory, programmable read only memory, electrically erasable programmable memory, or a register. The storage medium is located in the memory, and the processor reads the information in the memory and performs the steps in the above method embodiments in combination with the processor hardware.

[00458] It should be understood that the memory in embodiments of the present disclosure may be volatile memory or non-volatile memory, or may include both volatile (short-term) memory and non-volatile (long-term) memory. Non-volatile memory can be read only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrical EPROM (EEPROM), or flash memory. The volatile memory may be random access memory (RAM) and is used as an external cache. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM) , enhanced synchronous dynamic random access memory (ESDRAM), dynamic link synchronous random access memory (SLDRAM), direct access random access memory (DR RAM). It should be noted that the memory in the system and method described in this embodiment of the present disclosure includes, but is not limited to, any other suitable type of memory.

[00459] It should be understood that memory is an example and not a limitation. For example, memory in embodiments of the present disclosure may alternatively be static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), DRAM with synchronous link (SLDRAM), direct access RAM (DR RAM) and the like. In other words, the memory described in this embodiment of the present disclosure includes, but is not limited to, any other suitable type of memory.

[00460] FIG. 11 is a schematic block diagram of a communications system 1100 in accordance with an embodiment of the present disclosure. The communication system 1100 shown in FIG. 11 includes a terminal device 1110 and a network device 1120.

[00461] The terminal device 1110 may implement the respective functions implemented by the terminal device in the above method, and the network device 1120 may implement the corresponding functions implemented by the network device in the above method. For brevity, the details are not repeated here.

[00462] An embodiment of the present disclosure further provides a computer-readable storage medium. The computer-readable storage medium is configured to store a computer program.

[00463] Optionally, a computer-readable storage medium may be applied to a network device in the embodiments of the present disclosure, and a computer program causes the computer to execute the appropriate procedure implemented by the network device in the methods of the embodiments of the present disclosure. For brevity, the details are not repeated here.

[00464] Optionally, a computer-readable storage medium may be applied to a mobile terminal/terminal device in the embodiments of the present disclosure, and a computer program causes the computer to execute the corresponding procedure implemented by the mobile terminal/terminal device in the methods of the embodiments of the present disclosure. For brevity, the details are not repeated here.

[00465] The present disclosure further provides a computer program product. A computer program product includes computer program instructions.

[00466] Optionally, a computer program product may be applied to a network device in the embodiments of the present disclosure, and computer program instructions cause the computer to execute the appropriate procedure implemented by the network device in the methods of the embodiments of the present disclosure. For brevity, the details are not repeated here.

[00467] Optionally, a computer program product may be applied to a mobile terminal/terminal device in the embodiments of the present disclosure, and computer program instructions cause the computer to execute the appropriate procedure implemented by the mobile terminal/terminal device in the methods of the embodiments of the present disclosure. For brevity, the details are not repeated here.

[00468] The present disclosure further provides a computer program.

[00469] Optionally, a computer program may be applied to a network device in the embodiments of the present disclosure, and when executed on the computer, the computer program instructions cause the computer to execute the appropriate procedure implemented by the network device in the methods of the embodiments of the present disclosure. For brevity, the details are not repeated here.

[00470] Optionally, a computer program may be applied to the mobile terminal/terminal device in the embodiments of the present disclosure, and when executed on the computer, the computer program instructions cause the computer to execute the appropriate procedure implemented by the mobile terminal/terminal device in the methods of the embodiments of this disclosure. For brevity, the details are not repeated here.

[00471] One skilled in the art may be aware that, in conjunction with the examples described in the embodiments disclosed in this specification, the blocks and steps of an algorithm may be implemented using electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed by hardware or software depends on particular applications and design constraints. A person skilled in the art may use other methods to implement the described functions for each particular application, but such an implementation should not be considered outside the scope of this disclosure.

[00472] A person skilled in the art can clearly understand that for a simple and clear description of the specific working processes of the above system, device and unit, reference can be made to the corresponding process in the above method embodiments, and the details are not repeated here.

[00473] In several embodiments provided in the present disclosure, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the device embodiments described above are merely examples. For example, the division into blocks is a simple division of logical functions, and there may be other ways of division in the actual implementation. For example, many blocks or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the interconnections or direct links or communication connections shown or described may be implemented using certain interfaces. Indirect connections or communication connections between devices or units can be implemented electrically, mechanically, or take other forms.

[00474] Blocks described as separate parts may or may not be physically separable, and parts shown as blocks may or may not be physical blocks, may be located in a single location, or may be distributed across multiple network blocks. Some or all of the blocks may be selected according to actual needs in order to achieve the goals of the solutions of the embodiments.

[00475] In addition, the functional blocks in the embodiments of the present disclosure may be integrated into one processing unit, or each of the units may exist physically separately, or two or more units may be integrated into one unit.

[00476] When the functions are implemented in the form of a software functional block and sold or used as a standalone product, the functions may be stored on a computer-readable storage medium. Based on this understanding, the technical solutions of the present disclosure as such, or a portion contributing to the prior art, or some of the technical solutions may be implemented in the form of a software product. The software product is stored on a storage medium and includes several instructions for causing a computing device (which may be a personal computer, a server, or a network device) to perform all or some of the steps of the methods described in the embodiments of the present disclosure. The aforementioned storage medium includes: any medium that can store program code such as a USB flash drive, removable hard disk, read only memory (ROM), random access memory (RAM), magnetic disk or optical disk.

[00477] The above information describes only specific implementations of the present disclosure, but the scope of protection of the present disclosure is not limited to this. Changes or substitutions that can easily be understood by any person skilled in the art within the technical scope disclosed in this disclosure should be covered by the scope of this disclosure. Therefore, the scope of protection of the present disclosure is the scope of protection defined by the claims.

Claims (90)

1. A wireless communication method comprising the steps of: receiving, by the terminal device, a configuration sent by the network device; in response to a beam failure occurring in the secondary cell, generating (210) by the terminal device a scheduling request, the scheduling request being used to request an uplink resource from the network device; receiving, by the terminal device, a scheduling request response message sent by the network device, the response message indicating a first resource; transmitting by the terminal device the beam failure information of the secondary cell through a control element (CE) of the medium access layer (MAC), the beam failure information being carried on the first resource, wherein, in response to the fact that the configuration sent by the network device is the first configuration, the scheduling request corresponds to the first configuration, and the first configuration is the configuration of the scheduling request associated with at least one logical channel, and wherein, in response to the configuration sent by the network device being the second configuration, the scheduling request corresponds to the second configuration, the second configuration is a scheduling request configuration not associated with the logical channel, and the scheduling request ID of the second configuration is different from the scheduling request ID , corresponding to the configuration of the scheduling request associated with the logical channel. 2. The method of claim 1, wherein in response to the configuration being the first configuration, the first configuration is determined from a set of configurations based on at least one of the following: the network device guide information, a scheduling request identifier corresponding to each configuration in the configuration set, a resource identifier corresponding to each configuration in the configuration set, and a priority order of logical channels corresponding to respective configurations in the configuration set; or the first configuration is chosen arbitrarily from the set of configurations; wherein the configuration set comprises a configuration of at least one scheduling request, and each scheduling request corresponds to at least one logical channel. 3. The method according to claim 1 or 2, in which: the transmission priority of beam failure information of the secondary cell is higher than the transmission priority of any logical channel; or the transmission priority of beam failure information of the secondary cell is higher than the transmission priority of Radio Network Cell Temporary Identifier (C-RNTI) information or data from the Uplink Common Control Channel (UL-CCCH); or the transmission priority of the beam failure information of the secondary cell is lower than the transmission priority of the C-RNTI information or data from the UL-CCCH and higher than the transmission priority of the configured grant confirmation information; or the transmission priority of the beam failure information of the secondary cell is the same as the transmission priority of the C-RNTI information or data from the UL-CCCH; or the beam failure information transmission priority of the secondary cell is the same as the configured grant confirmation information transmission priority; or the transmission priority of beam failure information of the secondary cell is lower than the transmission priority of configured grant confirmation information and higher than the transmission priority of Buffer Status Report (BSR) information; or the beam failure information transmission priority of the secondary cell is the same as the transmission priority of the BSR information; or the transmission priority of the beam failure information of the secondary cell is lower than the transmission priority of the BSR information and higher than the transmission priority of one piece of Power Headroom Report (PHR) information or a plurality of pieces of PHR information. 4. The method according to claim 1 or 2, further comprising the steps of: transmitting, by the terminal device, beam failure information of the secondary cell to the network device; And confirming by the terminal device that beam failure recovery (BFR) of the secondary cell is successful, in response to receiving the beam failure information response message of the secondary cell. 5. A wireless communication method comprising the steps of: transmitting, via the network device, the configuration to the terminal device; receiving (330) by the network device a scheduling request transmitted from the terminal device in response to a beam failure occurring in the secondary cell, the scheduling request being used to request an uplink resource from the network device; transmitting, via the network device, to the terminal device a scheduling request response message, the response message indicating the first resource; receiving, by the network device, beam failure information of the secondary cell via a medium access layer (MAC) control element (CE), the beam failure information being carried on the first resource, wherein, in response to the fact that the configuration sent by the network device is the first configuration, the scheduling request corresponds to the first configuration, and the first configuration is the configuration of the scheduling request associated with at least one logical channel, and wherein, in response to the configuration sent by the network device being the second configuration, the scheduling request corresponds to the second configuration, the second configuration is a scheduling request configuration not associated with the logical channel, and the scheduling request ID of the second configuration is different from the scheduling request ID , corresponding to the configuration of the scheduling request associated with the logical channel. 6. The method of claim 5, wherein in response to the configuration being the first configuration, the first configuration is determined from a set of configurations based on at least one of the following: the network device guide information, a scheduling request identifier corresponding to each configuration in the configuration set, a resource identifier corresponding to each configuration in the configuration set, and a priority order of logical channels corresponding to respective configurations in the configuration set; or the first configuration is chosen arbitrarily from the set of configurations; wherein the configuration set comprises a configuration of at least one scheduling request, and each scheduling request corresponds to at least one logical channel. 7. The method according to claim 5 or 6, in which: the transmission priority of beam failure information of the secondary cell is higher than the transmission priority of any logical channel; or the transmission priority of beam failure information of the secondary cell is higher than the transmission priority of Radio Network Cell Temporary Identifier (C-RNTI) information or data from the Uplink Common Control Channel (UL-CCCH); or the transmission priority of the beam failure information of the secondary cell is lower than the transmission priority of the C-RNTI information or data from the UL-CCCH and higher than the transmission priority of the configured grant confirmation information; or the transmission priority of the beam failure information of the secondary cell is the same as the transmission priority of the C-RNTI information or data from the UL-CCCH; or the beam failure information transmission priority of the secondary cell is the same as the configured grant confirmation information transmission priority; or the transmission priority of beam failure information of the secondary cell is lower than the transmission priority of configured grant confirmation information and higher than the transmission priority of Buffer Status Report (BSR) information; or the beam failure information transmission priority of the secondary cell is the same as the transmission priority of the BSR information; or the transmission priority of the beam failure information of the secondary cell is lower than the transmission priority of the BSR information and higher than the transmission priority of one piece of Power Headroom Report (PHR) information or a plurality of pieces of PHR information. 8. The method according to claim 5 or 6, comprising sending, by the network device, to the terminal device a beam failure information response message of the secondary cell to confirm by the terminal device that the beam failure recovery (BFR) of the secondary cell is successful. 9. A communication terminal device, comprising: a communication module configured to receive the configuration sent by the network device; a processing module, configured, in response to a beam failure occurring in the secondary cell, to generate a scheduling request, the scheduling request being used to request an uplink resource from the network device; wherein the communication module is additionally configured to: receive a scheduling request response message sent by the network device, the response message indicating the first resource, and transmit beam failure information of the secondary cell via a medium access layer (MAC) control element (CE), wherein the beam failure information is carried on the first resource, wherein, in response to the fact that the configuration sent by the network device is the first configuration, the scheduling request corresponds to the first configuration, and the first configuration is the configuration of the scheduling request associated with at least one logical channel, and wherein, in response to the configuration sent by the network device being the second configuration, the scheduling request corresponds to the second configuration, the second configuration is a scheduling request configuration not associated with the logical channel, and the scheduling request ID of the second configuration is different from the scheduling request ID , corresponding to the configuration of the scheduling request associated with the logical channel. 10. The communication terminal apparatus of claim 9, wherein in response to the configuration being the first configuration, the first configuration is determined from the set of configurations based on at least one of the following: the network device guide information, a scheduling request identifier corresponding to each configuration in the configuration set, a resource identifier corresponding to each configuration in the configuration set, and a priority order of logical channels corresponding to respective configurations in the configuration set; or the first configuration is chosen arbitrarily from the set of configurations; wherein the configuration set comprises a configuration of at least one scheduling request, and each scheduling request corresponds to at least one logical channel. 11. Terminal communication device according to claim 9 or 10, while: the transmission priority of beam failure information of the secondary cell is higher than the transmission priority of any logical channel; or the transmission priority of beam failure information of the secondary cell is higher than the transmission priority of Radio Network Cell Temporary Identifier (C-RNTI) information or data from the Uplink Common Control Channel (UL-CCCH); or the transmission priority of the beam failure information of the secondary cell is lower than the transmission priority of the C-RNTI information or data from the UL-CCCH and higher than the transmission priority of the configured grant confirmation information; or the transmission priority of the beam failure information of the secondary cell is the same as the transmission priority of the C-RNTI information or data from the UL-CCCH; or the beam failure information transmission priority of the secondary cell is the same as the configured grant confirmation information transmission priority; or the transmission priority of beam failure information of the secondary cell is lower than the transmission priority of configured grant confirmation information and higher than the transmission priority of Buffer Status Report (BSR) information; or the beam failure information transmission priority of the secondary cell is the same as the transmission priority of the BSR information; or the transmission priority of the beam failure information of the secondary cell is lower than the transmission priority of the BSR information and higher than the transmission priority of one piece of Power Headroom Report (PHR) information or a plurality of pieces of PHR information. 12. The communication terminal device according to claim 9 or 10, wherein the communication module is further configured to transmit beam failure information of the secondary cell to the network device; And the processing module is further configured to confirm that beam failure recovery (BFR) of the secondary cell is successful, in response to receiving the beam failure information response message of the secondary cell. 13. A network communication device, comprising: communication module configured to: transfer the configuration to the terminal device, receive a scheduling request transmitted from the terminal device in response to a beam failure occurring in a secondary cell, the scheduling request being used to request an uplink resource from the network communication device, transmit to the terminal device a scheduling request response message, the response message indicating the first resource, and receive beam failure information of the secondary cell via a medium access layer (MAC) control element (CE), wherein the beam failure information is carried on the first resource, wherein, in response to the fact that the configuration sent by the network communication device is the first configuration, the scheduling request corresponds to the first configuration, and the first configuration is the configuration of the scheduling request associated with at least one logical channel, wherein, in response to the configuration sent by the network communication device being the second configuration, the scheduling request corresponds to the second configuration, the second configuration is a scheduling request configuration not associated with the logical channel, and the scheduling request ID of the second configuration is different from the request ID scheduling corresponding to the configuration of the scheduling request associated with the logical channel. 14. The network communication device of claim 13, wherein, in response to the configuration being the first configuration, the first configuration is determined from a set of configurations based on at least one of the following: indication information of the network communication device, a scheduling request identifier corresponding to each configuration in the configuration set, a resource identifier corresponding to each configuration in the configuration set, and a priority order of logical channels corresponding to the respective configurations in the configuration set; or the first configuration is chosen arbitrarily from the set of configurations; wherein the configuration set comprises a configuration of at least one scheduling request, and each scheduling request corresponds to at least one logical channel. 15. Network communication device according to claim 13 or 14, while: the transmission priority of beam failure information of the secondary cell is higher than the transmission priority of any logical channel; or the transmission priority of beam failure information of the secondary cell is higher than the transmission priority of Radio Network Cell Temporary Identifier (C-RNTI) information or data from the Uplink Common Control Channel (UL-CCCH); or the transmission priority of the beam failure information of the secondary cell is lower than the transmission priority of the C-RNTI information or data from the UL-CCCH and higher than the transmission priority of the configured grant confirmation information; or the transmission priority of the beam failure information of the secondary cell is the same as the transmission priority of the C-RNTI information or data from the UL-CCCH; or the beam failure information transmission priority of the secondary cell is the same as the configured grant confirmation information transmission priority; or the transmission priority of beam failure information of the secondary cell is lower than the transmission priority of configured grant confirmation information and higher than the transmission priority of Buffer Status Report (BSR) information; or the beam failure information transmission priority of the secondary cell is the same as the transmission priority of the BSR information; or the transmission priority of the beam failure information of the secondary cell is lower than the transmission priority of the BSR information and higher than the transmission priority of one piece of Power Headroom Report (PHR) information or a plurality of pieces of PHR information. 16. The network communication device according to claim 13 or 14, wherein the communication module is further configured to send to the terminal device a beam failure information response message of the secondary cell to confirm by the terminal device that the beam failure recovery (BFR) of the secondary cell is successful.

Images