Communication method, communication device, communication system, storage medium and program product

By performing beam failure detection and recovery on multiple active frequency domain resources, the problem of improper beam failure control in the prior art is solved, the transmission rate and scheduling efficiency of the terminal are improved, and reliable communication of frequency domain resources is realized.

WO2026237082A1PCT designated stage Publication Date: 2026-11-19BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/095562
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-16
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

In scenarios where multiple frequency domain resources are activated, existing technologies struggle to effectively control beam failure detection and recovery, leading to a decrease in terminal transmission rate and scheduling efficiency.

Method used

Beam Failure Detection (BFD) is performed on multiple active frequency domain resources, and Beam Failure Recovery (BFR) is triggered when the number of beam failures reaches a threshold. The network device sends indication information to configure the BFD and BFR parameters, and the terminal performs the corresponding detection and recovery.

Benefits of technology

It achieves reliable control in scenarios with multiple active frequency domain resources, improves the terminal's transmission rate and scheduling efficiency, and ensures reliable communication between multiple active frequency domain resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025095562_19112026_PF_FP_ABST
    Figure CN2025095562_19112026_PF_FP_ABST
Patent Text Reader

Abstract

Disclosed in the present application are a communication method, a communication device, a communication system, a storage medium and a program product. The method executed by a terminal comprises: respectively performing beam failure detection (BFD) on a plurality of activated frequency domain resources; and when a beam failure is detected on an activated frequency domain resource and the number of beam failures reaches a count threshold, triggering beam failure recovery (BFR) for the activated frequency domain resource. Thus, when multiple frequency domain resources are activated, reliable control over BFD and BFR is implemented.
Need to check novelty before this filing date? Find Prior Art

Description

Communication methods, communication equipment, communication systems, storage media and software products Technical Field

[0001] This application relates to the field of communication technology, and in particular to communication methods, communication equipment, communication systems, storage media, and program products. Background Technology

[0002] In communication systems, multiple discontinuous spectrum resources in multiple frequency domains can be aggregated into a single serving cell. Each spectrum resource can define one or more bandwidth parts (BWPs), and multiple BWPs may be activated simultaneously to improve terminal transmission rates and network scheduling efficiency. Summary of the Invention

[0003] This application provides communication methods, communication devices, communication systems, storage media, and program products.

[0004] A first aspect of this application provides a communication method, which is executed by a terminal, and the method includes:

[0005] Beam Failure Detection (BFD) is performed on multiple active frequency domain resources.

[0006] If a beam failure is detected on an active frequency domain resource and the number of beam failures reaches a threshold, a beam failure recovery (BFR) is triggered for the active frequency domain resource.

[0007] A second aspect of this application provides a communication method, which is executed by a network device, and the method includes:

[0008] Sending indication information, wherein the indication information is configured to configure at least one of the following:

[0009] Identifiers of multiple active frequency domain resources for beam failure detection (BFD) to be performed;

[0010] The BFD parameters associated with the multiple activated frequency domain resources;

[0011] The beam failure recovery BFR parameters associated with the multiple activated frequency domain resources.

[0012] A third aspect of this application provides a communication method for use in a communication system, the communication system including a terminal and a network device, the method comprising:

[0013] The network device sends indication information to the terminal, wherein the indication information is used to configure at least one of the following:

[0014] Identifiers of multiple active frequency domain resources for beam failure detection (BFD) to be performed;

[0015] The BFD parameters associated with the multiple activated frequency domain resources;

[0016] Beam Failure Recovery (BFR) parameters associated with the multiple activated frequency domain resources;

[0017] The terminal performs beam failure detection (BFD) on multiple active frequency domain resources respectively;

[0018] If a beam failure is detected on an active frequency domain resource and the number of beam failures reaches a threshold, a beam failure recovery (BFR) is triggered for the active frequency domain resource.

[0019] A fourth aspect of this application provides a terminal, which includes a processing module and a transceiver module.

[0020] The aforementioned processing module is used to perform beam failure detection (BFD) on multiple active frequency domain resources respectively.

[0021] If a beam failure is detected on an active frequency domain resource and the number of beam failures reaches a threshold, the aforementioned processing module is further configured to trigger a beam failure recovery (BFR) for the active frequency domain resource.

[0022] A fifth aspect of this application provides a network device, which includes a processing module and a transceiver module.

[0023] The aforementioned transceiver module is used to send indication information, wherein the indication information is used to configure at least one of the following:

[0024] Identifiers of multiple active frequency domain resources for beam failure detection (BFD) to be performed;

[0025] The BFD parameters associated with the multiple activated frequency domain resources;

[0026] The beam failure recovery BFR parameters associated with the multiple activated frequency domain resources.

[0027] The solution proposed in this application involves the terminal performing BFD on multiple active frequency domain resources and triggering BFR on an active frequency domain resource when the active frequency domain resource satisfies BFR. This achieves reliable control of BFD and BFR in scenarios with multiple active frequency domain resources, improving the terminal's transmission rate and scheduling efficiency while ensuring reliable control of multiple active frequency domain resources and enhancing the terminal's communication performance. Attached Figure Description

[0028] To more clearly illustrate the technical solutions in the embodiments or background art of this application, the following description of the accompanying drawings is provided. The following drawings are merely some embodiments of this application and do not impose specific limitations on the scope of protection of this application.

[0029] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of this application;

[0030] Figure 2A is an interactive schematic diagram of a communication method provided in an embodiment of this application;

[0031] Figure 2B is an interactive schematic diagram of a communication method provided in an embodiment of this application;

[0032] Figure 2C is an interactive schematic diagram of a communication method provided in an embodiment of this application;

[0033] Figure 3A is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0034] Figure 3B is a schematic diagram of the structure of a network device provided in an embodiment of this application;

[0035] Figure 4A is a schematic diagram of the structure of the communication device proposed in an embodiment of this application;

[0036] Figure 4B is a schematic diagram of the chip structure proposed in an embodiment of this application. Detailed Implementation

[0037] This application provides communication methods, communication devices, communication systems, storage media, and program products.

[0038] In a first aspect, embodiments of this application propose a communication method, which is executed by a terminal, and the method includes:

[0039] Beam Failure Detection (BFD) is performed on multiple active frequency domain resources.

[0040] If a beam failure is detected on an active frequency domain resource and the number of beam failures reaches a threshold, a beam failure recovery (BFR) is triggered for the active frequency domain resource.

[0041] In the above embodiments, the terminal performs BFD on multiple active frequency domain resources respectively, and triggers BFR for an active frequency domain resource when the active frequency domain resource satisfies BFR. This achieves reliable control of BFD and BFR in scenarios with multiple active frequency domain resources, improving the terminal's transmission rate and scheduling efficiency while ensuring reliable control of multiple active frequency domain resources and enhancing the terminal's communication performance.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0043] Receive indication information, wherein the indication information is used to configure at least one of the following:

[0044] The identifiers of the multiple activated frequency domain resources;

[0045] BFD parameters associated with each of the activated frequency domain resources;

[0046] The BFR parameters associated with each of the activated frequency domain resources.

[0047] In the above embodiments, the network device can instruct the terminal which active frequency domain resources to perform BFD, thereby ensuring that the terminal and the network device have a consistent understanding of the frequency domain resources to be BFD in the case of multiple active frequency domain resources.

[0048] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes:

[0049] If a beam failure is detected for the first time in an active frequency domain resource, the BFD timer associated with the active frequency domain resource is started or restarted.

[0050] Increment the BFR counter associated with the active frequency domain resource.

[0051] In the above embodiments, the terminal can maintain a beam failure detection timer and a BFR counter for each active frequency domain resource, thereby ensuring the accuracy and reliability of BFD and BFR control for each active frequency domain resource.

[0052] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0053] When the BFD timer associated with an active frequency domain resource times out, the value of the BFR counter associated with the active frequency domain resource is reset to a specified value.

[0054] In the above embodiments, when the BFD timer associated with an active frequency domain resource times out, the terminal can reset the value of its associated BFR counter to a specified value, thereby avoiding triggering BFR on the frequency domain resources for beam recovery and avoiding resource waste.

[0055] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0056] A BFR report is sent using the available Physical Uplink Shared Channel (PUSCH) resource, the BFR report including beam failure information for the active frequency domain resource.

[0057] In the above embodiments, the terminal can use the available PUSCH resources to indicate the beam failure information of the active frequency domain resource that has experienced beam failure to the network device, thereby providing conditions for the reliable recovery of the active frequency domain resource.

[0058] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0059] The BFR report is sent via a Media Access Control (MAC) CE, wherein the MAC CE also includes BFR reports for other active frequency domain resources.

[0060] In the above embodiments, the terminal can send BFR reports of multiple active frequency domain resources through MAC CE, thereby realizing BFR reporting of multiple active frequency domain resources.

[0061] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0062] No PUSCH resources are available for sending BFR reports. Send a scheduling request (SR).

[0063] In the above embodiments, when there is no available PUSCH resource for sending BFR reports, the terminal can trigger SR, thereby achieving reliable reporting of BFR in the case of multiple active frequency domain resources.

[0064] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0065] If no uplink resources are available in the terminal, a BFR is triggered for the activated frequency domain resource, and a random access procedure is initiated.

[0066] In the above embodiments, when one of the multiple active frequency domain resources satisfies BFR and there is no available uplink resource in the terminal, the terminal can trigger the BFR of the active frequency domain resource and start the random access procedure, thereby ensuring reliable control of BFD and BFR when there is no available uplink resource in the case of multiple active frequency domain resources.

[0067] In conjunction with some embodiments of the first aspect, in some embodiments, the above-described initiation of the random access procedure includes:

[0068] Initiate the random access procedure based on any of the following frequency domain resources:

[0069] Primary frequency domain resources, initial frequency domain resources, default frequency domain resources, and frequency domain resources indicated by the network device.

[0070] In the above embodiments, the terminal can complete the random access procedure triggered by BFR under multiple active frequency domain resources based on multiple resources, thereby improving the reliability of BFD and BFR under multiple active frequency domain resources.

[0071] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0072] Random access complete; cancel the BFR of the frequency domain resources used for random access.

[0073] Set the value of the BFR counter associated with the frequency domain resources used by the random access to the specified value.

[0074] In the above embodiments, the terminal can cancel the BFR of the frequency domain resources used for random access after the random access is completed, thus avoiding the waste of resources and power consumption.

[0075] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0076] The terminal contains other active frequency domain resources that trigger BFRs that have not been canceled, generating a BFR report. However, the BFR report does not include BFR reports for the frequency domain resources used by the random access procedure.

[0077] In the above embodiments, the terminal may not generate a BFR report for the frequency domain resources used in the random access procedure, which reduces the amount of information transmitted in the random access procedure triggered in scenarios with multiple active frequency domain resources and avoids resource waste.

[0078] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0079] The activated frequency domain resource is deactivated, and the BFR for the activated frequency domain resource is cancelled.

[0080] Set the value of the BFR counter associated with the active frequency domain resource to the specified value.

[0081] In the above embodiments, the terminal can cancel the BFR of the deactivated frequency domain resources, thus avoiding resource waste.

[0082] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0083] Send Media Access Control (MAC) Protocol Data Unit (PDU);

[0084] The MAC PDU includes a BFR report for the active frequency domain resource, and cancels the BFR for the active frequency domain resource.

[0085] In the above embodiments, when multiple frequency domain resources are active, after the terminal sends a BFR report for an active frequency domain resource, it can cancel the BFR for that active frequency domain resource, thereby avoiding repeated execution of BFR and reducing the probability of wasting resources.

[0086] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0087] Receive Physical Downlink Control Channel (PDCCH) information;

[0088] The uplink new transmission scheduled by the PDCCH includes a BFR report for the active frequency domain resource, and sets the value of the BFR counter associated with the active frequency domain resource to a specified value.

[0089] In the above embodiments, in a multi-active frequency domain resource scenario, after receiving the PDCCH information of the BFR report for scheduling an active frequency domain resource, the terminal can set the value of the BFR counter of that active frequency domain resource to a specified value, thereby avoiding the BFR counter from repeatedly triggering the BFR report and avoiding resource waste.

[0090] Secondly, embodiments of this application propose a communication method, which is executed by a network device, and the method includes:

[0091] Sending indication information, wherein the indication information is configured to configure at least one of the following:

[0092] Identifiers of multiple active frequency domain resources for beam failure detection (BFD) to be performed;

[0093] The BFD parameters associated with the multiple activated frequency domain resources;

[0094] The beam failure recovery BFR parameters associated with the multiple activated frequency domain resources.

[0095] In conjunction with some embodiments of the second aspect, in some embodiments the above method further includes:

[0096] Receive a BFR report, wherein the BFR report includes beam failure information for at least one of the plurality of active frequency domain resources.

[0097] Thirdly, embodiments of this application propose a communication method for use in a communication system, the communication system including a terminal and network equipment, the method comprising:

[0098] The network device sends indication information to the terminal, wherein the indication information is used to configure at least one of the following:

[0099] Identifiers of multiple active frequency domain resources for beam failure detection (BFD) to be performed;

[0100] The BFD parameters associated with the multiple activated frequency domain resources;

[0101] Beam Failure Recovery (BFR) parameters associated with the multiple activated frequency domain resources;

[0102] The terminal performs beam failure detection (BFD) on multiple active frequency domain resources respectively;

[0103] If a beam failure is detected on an active frequency domain resource and the number of beam failures reaches a threshold, a beam failure recovery (BFR) is triggered for the active frequency domain resource.

[0104] Fourthly, embodiments of this application propose a terminal, which includes a transceiver module and a processing module; wherein,

[0105] The aforementioned processing module is used to perform beam failure detection (BFD) on multiple active frequency domain resources respectively.

[0106] If a beam failure is detected on an active frequency domain resource and the number of beam failures reaches a threshold, the aforementioned processing module is further configured to trigger a beam failure recovery (BFR) for the active frequency domain resource.

[0107] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-described transceiver module is configured to receive indication information, wherein the indication information is configured to configure at least one of the following:

[0108] The identifiers of the multiple activated frequency domain resources;

[0109] BFD parameters associated with each of the activated frequency domain resources;

[0110] The BFR parameters associated with each of the activated frequency domain resources.

[0111] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-described processing module is further configured to:

[0112] If a beam failure is detected for the first time in an active frequency domain resource, the BFD timer associated with the active frequency domain resource is started or restarted.

[0113] Increment the BFR counter associated with the active frequency domain resource.

[0114] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-described processing module is further configured to:

[0115] When the BFD timer associated with an active frequency domain resource times out, the value of the BFR counter associated with the active frequency domain resource is set to a specified value.

[0116] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module described above is further configured to send a BFR report via available Physical Uplink Shared Channel (PUSCH) resources, the BFR report including beam failure information of the activated frequency domain resource.

[0117] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module described above is further configured to send the BFR report through a Media Access Control (MAC) CE, wherein the MAC CE also includes BFR reports for other active frequency domain resources.

[0118] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-described transceiver module is further configured to send a scheduling request (SR) when there is no available PUSCH resource for sending BFR reports.

[0119] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-mentioned processing module is further configured to trigger a BFR for the activated frequency domain resource and initiate a random access procedure when there are no available uplink resources in the terminal.

[0120] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-described processing module is further configured to initiate a random access procedure based on any of the following frequency domain resources:

[0121] Primary frequency domain resources, initial frequency domain resources, default frequency domain resources, and frequency domain resources indicated by the network device.

[0122] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-described processing module is further configured to:

[0123] Random access is completed; the BFR of the frequency domain resources used by the random access is cancelled.

[0124] Set the value of the BFR counter associated with the frequency domain resources used by the random access to the specified value.

[0125] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-described processing module is further configured to:

[0126] The terminal contains other active frequency domain resources that trigger BFRs that have not been canceled, generating a BFR report. However, the BFR report does not include BFR reports for the frequency domain resources used by the random access procedure.

[0127] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-described processing module is further configured to:

[0128] The activated frequency domain resource is deactivated, and the BFR for the activated frequency domain resource is cancelled.

[0129] Set the value of the BFR counter associated with the active frequency domain resource to the specified value.

[0130] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module described above is also used to send Media Access Control (MAC) Protocol Data Unit (PDU);

[0131] The aforementioned processing module is also used to include a BFR report for the active frequency domain resource in the MAC PDU, and to cancel the BFR for the active frequency domain resource.

[0132] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module described above is also used to receive physical downlink control channel (PDCCH) information;

[0133] The aforementioned processing module is further configured to include a BFR report for an activated frequency domain resource in the uplink new transmission scheduled by the PDCCH, and to set the value of the BFR counter associated with the activated frequency domain resource to a specified value.

[0134] Fifthly, embodiments of this application propose a network device, which includes a transceiver module and a processing module; wherein the transceiver module is used to send indication information, wherein the indication information is used to configure at least one of the following:

[0135] Identifiers of multiple active frequency domain resources for beam failure detection (BFD) to be performed;

[0136] The BFD parameters associated with the multiple activated frequency domain resources;

[0137] The beam failure recovery BFR parameters associated with the multiple activated frequency domain resources.

[0138] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module described above is further configured to receive a BFR report, wherein the BFR report includes beam failure information for at least one of the plurality of active frequency domain resources.

[0139] In a sixth aspect, embodiments of this application provide a terminal, which includes one or more processors; wherein the terminal is used to execute the first aspect and optional implementations of the first aspect.

[0140] In a seventh aspect, embodiments of this application provide a network device comprising: one or more processors; wherein the network device is configured to execute the second aspect and optional implementations thereof.

[0141] Eighthly, embodiments of this application provide a communication device, which is used to execute the first aspect and optional implementations of the first aspect, or to execute the second aspect and optional implementations of the second aspect.

[0142] Ninthly, embodiments of this application propose a communication system, which includes: a terminal and a network device; wherein the terminal is configured to perform the method described in the first aspect and the optional implementation of the first aspect, and the network device is configured to perform the method described in the second aspect and the optional implementation of the second aspect.

[0143] In a tenth aspect, embodiments of this application provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect and its optional implementation, or the method described in the second aspect and its optional implementation.

[0144] In the eleventh aspect, embodiments of this application provide a program product that, when executed by a communication device, causes the communication device to perform the method described in the first aspect and its optional implementation, or the method described in the second aspect and its optional implementation.

[0145] In a twelfth aspect, embodiments of this application provide a computer program that, when run on a computer, causes the computer to perform the methods described in the first aspect and its optional implementations, or to perform the methods described in the second aspect and its optional implementations.

[0146] In a thirteenth aspect, embodiments of this application provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described in the first aspect and its optional implementations, or to perform the methods described in the second aspect and its optional implementations.

[0147] It is understood that the aforementioned terminals, network devices, communication devices, communication systems, storage media, and program products are all used to execute the methods proposed in the embodiments of this application. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0148] This application provides communication methods, communication devices, communication systems, storage media, and program products. In some embodiments, the terms "communication method," "information processing method," and "data processing method" can be used interchangeably.

[0149] The embodiments in this application are not exhaustive, but merely illustrative of some embodiments, and are not intended to limit the scope of protection of this application. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In the embodiments of this application, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0150] The terminology used in the embodiments of this application is for the purpose of describing specific embodiments only and is not intended to limit the scope of this application.

[0151] In the embodiments of this application, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun after the article can be understood as either a singular expression or a plural expression.

[0152] In the embodiments of this application, "multiple" refers to two or more.

[0153] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0154] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0155] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0156] The prefixes "first," "second," etc., used in the embodiments of this application are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0157] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0158] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0159] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0160] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0161] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0162] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0163] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0164] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0165] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, various embodiments of this application can also be applied to structures that replace communication between access network devices, core network devices, or network devices and terminals with communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, uplink link, downlink link, etc., can be replaced with sidelink link.

[0166] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0167] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0168] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0169] Furthermore, each element, each row, or each column in the table of this application embodiment can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0170] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of this application.

[0171] As shown in Figure 1, the communication system 100 includes a terminal 101 and a network device 102.

[0172] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things (IoT) device, narrowband Internet of Things (NB-IoT) device, satellite communication device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, wireless terminal device in smart home, and red-capped terminal, but is not limited thereto.

[0173] In some embodiments, network device 102 may be a node or device that connects a terminal to a wireless network. The network device may include, but is not limited to, nodes such as satellites or drones in non-terrestrial networks, evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), next-generation RAN node (NG-RAN node), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in Wi-Fi system.

[0174] In some embodiments, the technical solutions of this application can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this application can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0175] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0176] It is understood that the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions proposed in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in the embodiments of this application are also applicable to similar technical problems.

[0177] The following embodiments of this application can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0178] The embodiments of this application can be applied to Non-terrestrial Networks (NTN), Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), 6th generation mobile communication system (6G), 6G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), and IEEE IEEE 802.11 (Wi-Fi, registered trademark), IEEE 802.16 (WiMAX, registered trademark), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Narrow Band-IoT (NB-IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G / 6G).

[0179] In some embodiments, the bandwidth of a carrier can be divided into multiple bandwidth parts (BWPs). A terminal can be configured with multiple BWPs on a carrier simultaneously, but at any given time, the terminal can have at most one active downlink (DL) BWP and one active uplink (UL) BWP on a carrier. If the terminal is configured with multiple carriers, then each carrier can have one active uplink BWP and one active downlink BWP.

[0180] In some embodiments, for the spectrum of paired frequency division duplexing (FDD) that includes uplink and downlink carriers (i.e., uplink and downlink carriers at different frequencies), the UL BWP and DL BWP are configured independently.

[0181] In some embodiments, for unpaired time division duplex (TDD) spectrum where uplink and downlink are on the same carrier, UL BWP and DL BWP are physically the same bandwidth portion, with uplink and downlink transmissions distinguished by different time slices.

[0182] In some embodiments, during initial access, the terminal uses the initial BWP defined in the system information.

[0183] In some embodiments, beam failure detection (BFD) and beam failure recovery (BFR) are performed to restore the beam of the Physical Downlink Control Channel (PDCCH) channel and end the beam failure recovery process by successfully receiving the PDCCH on the new beam.

[0184] In some embodiments, beam failure detection can be based on the block error rate (BLER) of the reference signal corresponding to the explicitly configured reference signal (RS) or the implicitly configured PDCCH transmission configuration indication (TCI) state. Since the UE can perform beam failure detection on a maximum of two RSs, a beam failure is considered to have occurred only when the BLER on both RSs is higher than a threshold. Each time the physical layer detects a beam failure, it indicates the beam failure to the media access control (MAC) layer. The MAC layer then starts or restarts the beam failure detection timer, and the beam failure recovery counter (BFR_COUNTER) is incremented. If BFR_COUNTER reaches its maximum value, the beam failure recovery procedure is triggered. If no beam failure indication is received from the physical layer within a certain period of time, and the beam failure detection timer times out, then BFR_COUNTER is reset.

[0185] In some embodiments, the beam failure recovery procedure may employ a random access procedure. If the beam failure recovery procedure fails, a radio link failure (RLF) is triggered. At this point, the network device can determine that the terminal's current radio link is no longer functioning properly and may take measures such as triggering a handover to another cell or re-establishing a connection to restore communication services.

[0186] In some embodiments, multiple discontinuous spectrum resources in the frequency domain can be aggregated into a single serving cell. One or more Block Window (BWP) can be defined on each spectrum resource segment, and multiple BWPs may be activated simultaneously to improve terminal transmission rates and network scheduling efficiency. However, existing mechanisms such as Block Window (BFD) and Block Window Flight (BFR) present problems when multiple BWPs are activated.

[0187] This disclosure provides a method for handling a terminal with multiple active frequency domain resources when a beam failure is detected.

[0188] The communication method, communication equipment, communication system, storage medium, and program products provided in this application will be described in detail below with reference to the accompanying drawings.

[0189] Figure 2A is an interactive schematic diagram of a communication method according to an embodiment of this application. As shown in Figure 2A, the embodiment of this application relates to a communication method, which includes:

[0190] Step S2101: The network device sends an instruction message.

[0191] The aforementioned indication information is used to indicate at least one of the following: the identifiers of multiple active frequency domain resources; the beam failure detection (BFD) parameters associated with each active frequency domain resource; and the beam failure recovery (BFR) parameters associated with each active frequency domain resource.

[0192] In some embodiments, a network device may configure and activate multiple frequency domain resources for a terminal, and indicate which activated frequency domain resources can be used for BFD through indication information.

[0193] In some embodiments, frequency domain resources, such as bandwidth parts (BWPs), can be used to activate multiple BWPs for a terminal on a single spectrum resource, thereby improving the terminal's transmission rate and the network's scheduling efficiency.

[0194] In some embodiments, the frequency domain resource can also be a carrier. That is, within a cell, multiple carriers can be activated for the terminal to improve the terminal's transmission rate in that cell and the network's scheduling efficiency.

[0195] In some embodiments, multiple BWPs and multiple carriers can be activated simultaneously for the terminal, etc., but this disclosure does not limit this.

[0196] In some embodiments, BFD parameters include, for example, the reference signal for beam failure detection, the reference signal received power (RSRP) threshold, and the beam failure detection timer (such as the timer's timing value).

[0197] In some embodiments, the BFD parameters associated with different frequency domain resources may be the same, different, or partially the same, and this disclosure does not limit this.

[0198] In some embodiments, BFR parameters include, for example, Random Access Channel (RACH) resources, candidate beam reference signal (RS) list, and beam failure recovery counter parameters (such as a threshold number of times).

[0199] In some embodiments, the BFR parameters associated with different frequency domain resources may be the same, different, or partially the same, and this disclosure does not limit this.

[0200] In some embodiments, the terminal receives instruction information.

[0201] In step S2102, the terminal performs BFD on the multiple active frequency domain resources respectively.

[0202] In some embodiments, the terminal may perform BFD on the frequency domain resource based on the BFD parameters associated with each frequency domain resource.

[0203] In some embodiments, the terminal can monitor the signal quality of the reference signal (such as the Synchronization Signal and Physical Broadcast Channel Block, SSB) or Channel State Information-Reference Signal (CSI-RS) associated with each frequency domain resource. When the signal strength (such as the RSRP of Layer (L)1) is lower than a certain threshold and lasts for a certain period of time (defined by the beam failure detection timer), it is considered that a beam failure has occurred.

[0204] In some embodiments, terms such as "system information block," "system signal block," "synchronization signal and physical broadcast channel block," and "synchronization block" can all refer to information blocks used to achieve synchronization between terminals and network devices, and in some scenarios, the above terms can be used interchangeably.

[0205] Step S2103: If a beam failure is detected on an active frequency domain resource, start or restart the BFD timer associated with that active frequency domain resource and increment the associated BFR counter.

[0206] In some embodiments, an active frequency domain resource can be any one of a plurality of active frequency domain resources. That is, after a beam failure is detected on any active frequency domain resource, its associated BFD timer can be started or restarted, and the associated BFR counter can be incremented by one.

[0207] In some embodiments, an active frequency domain resource may be a single active frequency domain resource specified among multiple active frequency domain resources. For example, it may be a specific active frequency domain resource indicated by a network device, or a specific active frequency domain resource determined by a terminal, etc. This disclosure does not limit the scope of the embodiments.

[0208] In some embodiments, an active frequency domain resource can also be one (or several) active frequency domain resources determined by the terminal based on certain rules. For example, the terminal can determine one (or several) specific active frequency domain resources based on one or more of the following: current remaining battery power, network status, running services, etc. This disclosure does not limit this. In some embodiments, each active frequency domain resource is associated with a beam failure detection timer and a beam failure recovery counter. When a beam failure is detected for the first time for an active frequency domain resource, its associated beam failure detection timer can be started (or restarted), and its beam failure recovery counter can be incremented by one.

[0209] In the above embodiments, the terminal can maintain a beam failure detection timer and a BFR counter for each active frequency domain resource, thereby ensuring the accuracy and reliability of BFD and BFR control for each active frequency domain resource.

[0210] In some embodiments, after the terminal's physical layer detects a beam failure, it sends a Beam Failure Indication (BFI) to the Medium Access Control Layer (MAC). Upon receiving the BFI, the MAC layer can start or restart the beam failure detection timer and increment the beam failure recovery counter. During the beam failure detection timer's operation, if the terminal continues to detect BFIs, the beam failure recovery counter will continue to accumulate. If no new BFI is detected before the timer expires, the beam failure recovery counter is reset to 0.

[0211] In some embodiments, terms such as "beam failure recovery counter" and "beam failure counter" can be used to count the number of beam failures detected within a certain period of time (e.g., the timing period of a beam failure detection timer). In some scenarios, the above terms can be used interchangeably.

[0212] In some embodiments, when the physical layer of the terminal detects a beam failure on the frequency domain resource, the physical layer of the terminal can indicate to the Medium Access Control Layer (MAC) layer that a beam failure has been detected on the frequency domain resource. The MAC layer of the terminal can start or restart the beam failure detection timer associated with the frequency domain resource and increment the count value of the beam failure recovery counter associated with the frequency domain resource.

[0213] In some embodiments, when the beam failure detection timer associated with an active frequency domain resource times out, it indicates that the beam quality of the frequency domain resource may have recovered on its own, and the value of the beam failure recovery counter associated with an active frequency domain resource can be reset to a specified value.

[0214] In some embodiments, the specified value can be, for example, 0.

[0215] In some embodiments, if the count value of the beam failure recovery counter associated with an active frequency domain resource reaches a threshold number, it indicates that the active frequency domain resource meets the beam recovery triggering condition, thereby triggering BFR for the active frequency domain resource.

[0216] In step S2104, when the count value of the BFR counter associated with an active frequency domain resource reaches the number of times threshold, the terminal sends a BFR report through the available PUSCH resources.

[0217] The BFR report includes beam failure information for the active frequency domain resource.

[0218] In some embodiments, beam failure information may include, for example, an identifier of an active frequency domain resource on which beam failure was detected, such as a BWP identifier, carrier identifier, or cell identifier. Alternatively, the beam failure information may also include the reference signal type on which the beam failure detection is based, such as indicating whether the beam failure detection is based on SSB or CSI-RS, to assist the network device in determining the basis and conditions for detection. Alternatively, the beam failure information may also include the degree or parameters of the beam failure, such as a threshold below which the beam's RSRP falls, the Block Error Rate (BLER) of the Physical Downlink Control Channel (PDCCH), etc., to quantify the degree of beam failure. Alternatively, the beam failure information may also include indication information for indicating whether a new beam can be found, such as indicating to the network device whether a new beam has been found through the relevant identifier or parameters of the new beam, etc. This disclosure does not limit this aspect.

[0219] In some embodiments, the available PUSCH resources can be resources associated with other active frequency domain resources that have not triggered beam failure recovery.

[0220] In some embodiments, if there are other active frequency domain resources in the terminal that trigger BFR reports that have not been cancelled, the terminal can also send BFR reports for other active frequency domain resources simultaneously through the PUSCH resource.

[0221] In some embodiments, although the terminal detects a beam failure and triggers a BFR (Band Frame Reset) procedure, if during the BFR procedure the terminal detects that the beam quality has recovered to an acceptable level, or the network device sends a command to cancel the BFR, the BFR procedure will be canceled, and no BFR reporting will be performed. For example, if the terminal moves to an area with better signal during the BFR procedure and the quality of its current serving beam suddenly improves to meet communication requirements, the terminal may cancel the BFR procedure and stop reporting.

[0222] In some embodiments, if the PUSCH resource used to send the BFR report is a resource associated with the activated frequency domain resource #1, the activated frequency domain resource #1 also triggers beam failure recovery. Since the PUSCH resource itself identifies that BFR is associated with the activated frequency domain resource #1, the terminal may not send the BFR report for the activated frequency domain resource #1, thereby avoiding information duplication and saving the uplink resources occupied by the BFR report.

[0223] In some embodiments, the terminal may send a BFR report through a Medium Access Control Element (MAC CE), wherein the MAC CE may also include BFR reports associated with other active frequency domain resources.

[0224] In some embodiments, the terminal can insert the MAC CE containing the BFR report into the MAC Protocol Data Unit (PDU) and then transmit it using available PUSCH resources or other uplink channel resources, thereby improving the flexibility of BFR report transmission.

[0225] In some embodiments, if the terminal sends a MAC PDU that includes a BFR report for an active frequency domain resource, the terminal can cancel the BFR for that active frequency domain resource.

[0226] In the above embodiment, since the terminal has already sent a BFR report containing an active frequency domain resource, that is, it has already indicated the beam failure information of the active frequency domain resource to the network device, the purpose of the previously triggered BFR has been completed. If the BFR is not cancelled, the terminal may continue to perform BFD and / or BFR operations, resulting in wasted resources and confusion in the processing flow. Therefore, after sending a BFR report for an active frequency domain resource, the terminal can cancel the BFR triggered by that active frequency domain resource.

[0227] In some embodiments, if no PUSCH resources are available for sending BFR reports, a scheduling request (SR) is sent.

[0228] In some embodiments, the SR may include a BFR report of the frequency domain resource that triggered the BFR.

[0229] In this embodiment of the disclosure, when the terminal has no available PUSCH resources, the terminal can request uplink resource scheduling from the network device via SR, and simultaneously send a BFR report for the active frequency domain resources that meet the requirements for beam detection failure recovery to the network device. This achieves reliable transmission of the BFR report.

[0230] In some embodiments, if an active frequency domain resource is deactivated, the terminal can cancel the beam failure recovery counter (BFR) for that active frequency domain resource and set the value of the beam failure recovery counter associated with the active frequency domain resource to a specified value.

[0231] In this embodiment of the disclosure, if an active frequency domain resource is deactivated, it means that the terminal is no longer allowed to use that frequency domain resource for communication. At this time, the uplink resource associated with the deactivated frequency domain resource is also unavailable, and the terminal cannot use it to send a BFR report or perform beam failure recovery operation. In order to avoid the terminal wasting resources by still performing unnecessary beam failure recovery operations based on the BFR triggered by the frequency domain resource, after determining that an active frequency domain resource has been deactivated, the terminal can promptly cancel the BFR triggered by it and set the value of its associated beam failure recovery counter to a specified value.

[0232] In some embodiments, terms such as "deactivate" and "disable" can be used to describe changing the state of a frequency domain resource from an active state to an inactive state. In some scenarios, these terms can be used interchangeably.

[0233] In some embodiments, if a terminal receives PDCCH information and the uplink new transmission scheduled by the PDCCH includes a BFR report for an active frequency domain resource, the terminal can set the value of the BFR counter associated with the active frequency domain resource to a specified value.

[0234] In some embodiments, the PDCCH information received by the terminal may be PDCCH information addressed by the Cell-Radio Network Temporary Identifier (C-RNTI) associated with the terminal.

[0235] In the above embodiments, if the uplink new transmission scheduled by the PDCCH information received by the terminal includes a BFR report for an active frequency domain resource, it means that the terminal can reliably send the BFR report of that active frequency domain resource to the network device. At this time, to avoid the BFR of that active frequency domain resource triggering unnecessary BFR procedures again, such as triggering BFR report upload again or triggering a random access procedure, which could lead to resource waste or signaling errors, the terminal can set the value of the BFR counter associated with that active frequency domain resource to a specified value, that is, cancel the BFR of that frequency domain resource.

[0236] In some embodiments, the terms “eNB”, “gNB”, “base station”, and “NG-RAN node” can be used interchangeably.

[0237] In some embodiments, the terms "carrier," "band," and "frequency" can be used interchangeably.

[0238] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0239] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0240] In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.

[0241] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

[0242] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0243] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0244] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data and / or instructions received; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0245] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc. from one subject to another passes through other subjects, it can be interpreted as the information being forwarded from one subject to another via other subjects, or it can be interpreted as the information being sent from one subject to another without passing through other subjects.

[0246] The communication method involved in the embodiments of this application may include at least one of steps S2101 to S2104. For example, step S2101 may be implemented as a standalone embodiment, step S2102 may be implemented as a standalone embodiment, step S2103 may be implemented as a standalone embodiment, step S2103+S2104 may be implemented as a standalone embodiment, etc., but is not limited thereto.

[0247] The communication method described in this application allows a terminal to perform beam failure detection on each of multiple active frequency domain resources. When an active frequency domain resource meets the beam recovery conditions, a beam fault response (BFR) can be triggered for that active frequency domain resource. Furthermore, if a PUSCH is available, a BFR report for that active frequency domain resource is submitted. This achieves beam fault detection (BFD) and beam fault response (BFR) in scenarios with multiple active frequency domain resources. While improving the terminal's transmission rate and network scheduling rate, it also ensures the reliability and accuracy of BFD and BFR, avoiding resource waste.

[0248] Figure 2B is an interactive schematic diagram of a communication method according to an embodiment of this application. As shown in Figure 2B, the embodiment of this application relates to a communication method, which includes:

[0249] Step S2201: The network device sends an instruction message.

[0250] In step S2202, the terminal performs BFD on the multiple active frequency domain resources respectively.

[0251] Step S2203: If a beam failure is detected on an active frequency domain resource, start or restart the BFD timer associated with that active frequency domain resource and increment the associated BFR counter.

[0252] In some embodiments, the above steps S2201-S2203 and their optional implementations can be referred to in the detailed description of the above steps S2101-S2103, which will not be repeated here.

[0253] In step S2204, the count value of the beam failure recovery counter associated with an active frequency domain resource reaches the number of times thresholded, and there are no available uplink resources in the terminal. This triggers a BFR for an active frequency domain resource and initiates a random access procedure.

[0254] In some embodiments, when the count value of the beam failure recovery counter associated with an active frequency domain resource reaches a threshold, it indicates that the active frequency domain resource meets the beam failure recovery condition. If there are no available uplink resources in the terminal, such as when other frequency domain resources have experienced BFR, and / or when other active frequency domain resources are not configured with uplink resources, the terminal can initiate a random access procedure to re-establish synchronization with the network device, obtain a new beam or configuration for communication, etc.

[0255] In some embodiments, a terminal may determine that there are no available uplink resources when no other active frequency domain resources trigger and cancel the BFR.

[0256] In some embodiments, when the count value of the beam failure recovery counter associated with an active frequency domain resource reaches a threshold number, and the terminal contains other active frequency domain resources that have triggered BFRs that have not been canceled, it can be determined that the BFR process triggered by other frequency domain resources has not yet ended. At this time, since the terminal contains at least two frequency domain resources that have triggered BFRs, in order to indicate the BFD status of each active frequency domain resource on the terminal side to the network device, the terminal can generate a BFR report and send the BFR report through a random access request.

[0257] In some embodiments, if the frequency domain resource used in the random access procedure is the active frequency domain resource #2 where BFD has occurred, since the network device can determine that BFD has occurred in the active frequency domain resource #2 after receiving the random access request, the terminal may not generate a BFR report for the active frequency domain resource #2 in order to save resources and power consumption.

[0258] In some embodiments, the terminal may use a MAC CE to carry BFR reports. A single MAC CE may carry BFR reports for multiple active frequency domain resources.

[0259] In some embodiments, the BFR report may carry the identifier of the active frequency domain resource, such as the identifier (ID) of the BWP, etc., but this disclosure does not limit this.

[0260] In some embodiments, a terminal may initiate a random access procedure based on any of the following frequency domain resources: primary frequency domain resources, initial frequency domain resources, default frequency domain resources, or frequency domain resources indicated by the network device.

[0261] In some embodiments, the primary frequency domain resources can be the default operating frequency domain resources configured by the terminal in the Radio Resource Control (RRC) connected state.

[0262] In some embodiments, the primary frequency domain resource can be configured by the network device. Alternatively, the primary frequency domain resource can be determined by the terminal based on protocol agreements. For example, the terminal can determine a certain frequency domain resource (such as a certain BWP) in the serving cell as the primary frequency domain resource, or the terminal can determine a frequency domain resource that meets specific requirements (configured by the network device or agreed by the protocol) based on one or more of the corresponding parameters, such as the length of the Cyclic Prefix (CP), the position of the starting PRB (Physical Resource Block), the number of consecutive RBs used, etc., as the primary frequency domain resource. This disclosure does not limit this aspect.

[0263] In some embodiments, the initial frequency domain resources may be the frequency domain resources used by the terminal for cell search, system message reception, and random access when the terminal is in the RRC Idle state or the RRC Inactive state.

[0264] In some embodiments, the default frequency domain resource can be a frequency domain resource that is not explicitly configured or automatically used by the terminal in a specific state. For example, the default frequency domain resource in the RRC connected state can be the main frequency domain resource, and in the RRC idle state (or inactive state), the default frequency domain resource can be the initial frequency domain resource, and so on.

[0265] In some embodiments, the network device may also configure dedicated frequency domain resources for the terminal to be used in the random access procedure triggered by beam failure recovery. This increases the probability of successful beam failure recovery and improves the performance of the terminal.

[0266] Step S2205: Random access completed. Canceling the BFR for the frequency domain resources used for random access.

[0267] Step S2206: Set the value of the beam failure recovery counter associated with the frequency domain resources used for random access to a specified value.

[0268] In some embodiments, if random access is completed, it indicates that the terminal has re-established uplink synchronization with the network device and may have acquired a new beam (such as the optimal beam selected through the random access procedure) or resource (such as switching to a new frequency domain resource). At this point, if the BFR (Band Failure Recovery) of the frequency domain resource used for random access is not cancelled, the terminal may continue to detect the failure of the old beam on the recovered frequency domain resource (even though it has actually switched to a new beam), leading to false triggering of random access or beam failure recovery reports and interfering with normal communication. Therefore, by cancelling the BFR of the Pinyin resource used for random access, invalid signaling overhead and terminal power consumption can be avoided.

[0269] In some embodiments, after successful random access, the terminal may use a new beam or frequency domain resource (such as switching to the primary BWP or a dedicated BWP allocated by the network device). At this time, since the BFR process of the frequency domain resource used by the random access has ended, the value of the beam failure recovery counter that triggers BFR will be set to a specified value (such as 0 or the initial value preset by the protocol) to restart monitoring and counting the number of beam failures based on the new beam.

[0270] The communication method involved in the embodiments of this application may include at least one of steps S2201 to S2206. For example, step S2201 may be implemented as an independent embodiment, step S2202 may be implemented as an independent embodiment, step S2203 may be implemented as an independent embodiment, step S2203+S2204 may be implemented as an independent embodiment, step S2203+S2204+S2205 may be implemented as an independent embodiment, step S2203+S2204+S2205+S2206 may be implemented as an independent embodiment, etc., but not limited thereto.

[0271] The communication method described in this application allows a terminal to perform beam failure detection on each of multiple active frequency domain resources. When any active frequency domain resource meets the beam recovery conditions, beam fracturing (BFR) can be triggered for that resource. If no PUSCH is available, a random access procedure can be triggered to perform BFR. This achieves beam fracturing (BFD) and beam fracturing (BFR) in scenarios with multiple active frequency domain resources, improving the terminal's transmission rate and network scheduling rate while ensuring the reliability and accuracy of BFD and BFR, and avoiding resource waste.

[0272] Figure 2C is an interactive schematic diagram of a communication method according to an embodiment of this application. As shown in Figure 2C, the embodiment of this application relates to a communication method, which includes:

[0273] Step S2301: The network device sends an instruction message.

[0274] In step S2302, the terminal performs BFD on the multiple active frequency domain resources respectively.

[0275] Step S2303: If a beam failure is detected on any active frequency domain resource and the number of beam failures reaches a threshold, a BFR is triggered for any active frequency domain resource.

[0276] In some embodiments, the above steps S2301-S2303 and their optional implementations can be referred to in the detailed description of the above steps S2101-S2104, which will not be repeated here.

[0277] The communication method involved in the embodiments of this application may include at least one of steps S2301 to S2303. For example, step S2301 may be implemented as a standalone embodiment, steps S2302+S2303 may be implemented as standalone embodiments, etc., but are not limited thereto.

[0278] The following is an exemplary description of the methods described in the above embodiments. The following embodiments of this disclosure use the Frequency Domain Resource Plane (BWP) as an example to provide a detailed description of the communication methods proposed in this disclosure.

[0279] In some embodiments, the UE performs beam failure detection on multiple active BWPs respectively. If a beam failure is detected on one of the active BWPs and reaches a certain number of times (e.g., a number threshold), the BFR of that active BWP is triggered.

[0280] In some embodiments, the network device can configure which BWPs the UE performs beam failure detection on, and configure the corresponding beam failure detection parameters and beam failure recovery parameters.

[0281] In some embodiments, the network device can be configured with reference signals, RSRP thresholds, etc., for beam failure detection on the BWP. Beam failure recovery parameters include RACH resources, candidate beam RS list, beam failure recovery timer, etc.

[0282] In some embodiments, for an active BWP configured with beam failure detection, when the UE's physical layer detects a beam failure on the BWP, the UE's physical layer indicates to the MAC layer that a beam failure has been detected on the BWP. The UE's MAC layer starts or restarts the beam failure detection timer specific to the BWP and increments the beam failure recovery counter value specific to the BWP by 1.

[0283] In some embodiments, when a beam failure detection timer for an active BWP times out, the UE resets the beam failure recovery counter value for that BWP to 0.

[0284] In some embodiments, when the beam failure recovery counter value of an active BWP reaches its maximum value, the UE triggers the BFR on that BWP.

[0285] In some embodiments, if there are currently available PUSCH uplink resources for sending beam failure recovery reports, beam failure recovery reports are sent via PUSCH.

[0286] In some embodiments, the beam failure recovery report is transmitted using a MAC CE, and a single MAC CE can carry beam failure recovery reports from multiple BWPs.

[0287] In some embodiments, the beam failure recovery report carries a BWP ID.

[0288] In some embodiments, if no PUSCH uplink resources are currently available for sending a beam failure recovery report, an SR is triggered.

[0289] In some embodiments, when the beam failure recovery counter value of an active BWP reaches its maximum value, and the UE currently has no other active BWPs with no triggered and canceled BFRs, the UE triggers a BFR and initiates a random access procedure.

[0290] Optionally, the above random access procedure is performed on the main BWP, initial BWP, default BWP, or the BWP specified by the network device.

[0291] Optionally, the network device can be configured to specify which BWP is the primary BWP, or the network device can be configured with a designated BWP.

[0292] In some embodiments, when the UE triggers the beam failure recovery procedure, if there is a triggered and uncancelled BFR on another active BWP, a beam failure report is generated.

[0293] Optionally, the terminal does not generate a beam failure recovery report on the BWP that initiated the beam failure recovery. The beam failure recovery report does not include the beam failure recovery report on the BWP that initiated the beam failure recovery.

[0294] In some embodiments, the beam failure report is implemented using a MAC CE, and a single MAC CE can carry multiple beam failure recovery reports from the BWP.

[0295] In some embodiments, the beam failure recovery report carries a BWP ID.

[0296] In some embodiments, when a BWP is deactivated, the BFR triggered on that BWP is canceled, and the beam failure recovery counter corresponding to that BWP is set to 0.

[0297] In some embodiments, when a random access triggered by beam failure recovery is successful, the BFR triggered on the BWP that triggered the random access is canceled, and the beam failure recovery counter corresponding to the BWP is set to 0.

[0298] In some embodiments, when the UE sends a MAC PDU containing a beam failure recovery report on a BWP, the BFR triggered on that BWP is cancelled.

[0299] In some embodiments, when a UE receives a C-RNTI-addressed PDCCH, it schedules an uplink new transmission containing a BFR report, and sets the beam failure recovery counter corresponding to the BWP contained in the BFR report to 0.

[0300] In some embodiments, unless contradictory, the optional implementations in this embodiment can be implemented as independent embodiments, and the optional implementations in this embodiment can also be combined arbitrarily. The technical features of different feasible implementations in this embodiment can be combined to form new optional implementations based on their inherent logical relationships.

[0301] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0302] This application also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed, which includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed, which includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0303] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0304] In this application embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0305] Figure 3A is a schematic diagram of the structure of a terminal provided in an embodiment of this application. The terminal 3100 is used to execute any of the above methods. In some embodiments, as shown in Figure 3A, the terminal 3100 may include at least one of a transceiver module 3101, a processing module 3102, etc. In some embodiments, the processing module is used to perform beam failure detection (BFD) on multiple active frequency domain resources respectively; if a beam failure is detected on an active frequency domain resource and the number of beam failures reaches a threshold, the processing module is further used to trigger beam failure recovery (BFR) for the active frequency domain resource.

[0306] Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by terminal 101 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps performed by terminal 101 in any of the above methods, which will not be elaborated here.

[0307] Figure 3B is a schematic diagram of the network device proposed in an embodiment of this application. The network device 3200 is used to perform any of the above methods. In some embodiments, as shown in Figure 3B, the network device 3200 may include at least one of a transceiver module 3201, a processing module 3202, etc. In some embodiments, the transceiver module 3201 is used to send indication information, wherein the indication information is used to configure at least one of the following: identifiers of multiple active frequency domain resources to be subjected to beam failure detection (BFD); BFD parameters associated with the multiple active frequency domain resources; and beam failure recovery (BFR) parameters associated with the multiple active frequency domain resources.

[0308] Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the network device in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps performed by the network device in any of the above methods, which will not be elaborated here.

[0309] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0310] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0311] In some embodiments, the processing module can be interchanged with the processor, and the transceiver module can be interchanged with the transceiver.

[0312] Figure 4A is a schematic diagram of the structure of the communication device 4100 provided in an embodiment of this application. The communication device 4100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 4100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0313] As shown in Figure 4A, the communication device 4100 is used to execute any of the above methods. In some embodiments, the communication device 4100 includes one or more processors 4101. The processor 4101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 4100 is used to execute any of the above methods. Optionally, one or more processors 4101 are used to invoke instructions to cause the communication device 4100 to execute any of the above methods.

[0314] In some embodiments, the communication device 4100 further includes one or more transceivers 4102. When the communication device 4100 includes one or more transceivers 4102, the transceiver 4102 performs at least one of the communication steps such as sending and / or receiving in the above-described method, and the processor 4101 performs at least one of the other steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, sending unit, transmitter, sending circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0315] In some embodiments, the communication device 4100 further includes one or more memories 4103 for storing data and / or instructions. Optionally, one or more processors 4101 are used to invoke instructions stored in the memory 4103 to cause the communication device 4100 to perform any of the above methods. Optionally, all or part of the memory 4103 may also be located outside the communication device 4100. In an optional embodiment, the communication device 4100 may include one or more interface circuits 4104. Optionally, the interface circuit 4104 is connected to the memory 4102 and can be used to receive data and / or instructions from the memory 4102 or other devices, and can be used to send data and / or instructions to the memory 4102 or other devices. For example, the interface circuit 4104 can read data and / or instructions stored in the memory 4102 and send the data and / or instructions to the processor 4101.

[0316] The communication device 4100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 4100 described in this application is not limited thereto, and the structure of the communication device 4100 may not be limited by FIG4A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0317] Figure 4B is a schematic diagram of the structure of chip 4200 according to an embodiment of this application. For cases where the communication device 4100 can be a chip or a chip system, please refer to the schematic diagram of chip 4200 shown in Figure 4B, but it is not limited thereto.

[0318] Chip 4200 includes one or more processors 4201. Chip 4200 is used to perform any of the above methods.

[0319] In some embodiments, chip 4200 further includes one or more interface circuits 4202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 4200 further includes one or more memories 4203 for storing data and / or instructions. Optionally, all or part of the memories 4203 may be located outside of chip 4200. Optionally, the interface circuits 4202 are connected to the memories 4203, and the interface circuits 4202 can be used to receive data and / or instructions from the memories 4203 or other devices, and can be used to send data and / or instructions to the memories 4203 or other devices. For example, the interface circuits 4202 can read data and / or instructions stored in the memories 4203 and send the data and / or instructions to the processor 4201.

[0320] In some embodiments, the interface circuit 4202 performs at least one of the communication steps (e.g., S2101, but not limited thereto) in the above-described method, such as sending and / or receiving. For example, the interface circuit 4202 performing the communication steps (e.g., sending and / or receiving) in the above-described method means that the interface circuit 4202 performs data and / or instruction interaction between the processor 4201, the chip 4200, the memory 4203, or the transceiver device. In some embodiments, the processor 4201 performs at least one of the other steps.

[0321] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0322] This application also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0323] This application also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0324] This application also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication method characterized by comprising: The method, executed by a terminal, includes: Beam Failure Detection (BFD) is performed on multiple active frequency domain resources. If a beam failure is detected on an active frequency domain resource and the number of beam failures reaches a threshold, a beam failure recovery (BFR) is triggered for the active frequency domain resource.

2. The method of claim 1, wherein, The method further includes: Receive indication information, wherein the indication information is used to configure at least one of the following: The identifiers of the multiple activated frequency domain resources; BFD parameters associated with each of the activated frequency domain resources; The BFR parameters associated with each of the activated frequency domain resources.

3. The method of claim 1, wherein, The method further includes: If a beam failure is detected for the first time in an active frequency domain resource, the BFD timer associated with the active frequency domain resource is started or restarted. Increment the BFR counter associated with the active frequency domain resource.

4. The method of claim 3, wherein, The method further includes: When the BFD timer associated with an active frequency domain resource times out, the value of the BFR counter associated with the active frequency domain resource is set to a specified value.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: A BFR report is sent using the available Physical Uplink Shared Channel (PUSCH) resource, the BFR report including beam failure information for the active frequency domain resource.

6. The method of claim 5, wherein, The method further includes: The BFR report is sent via a Media Access Control (MAC) CE, wherein the MAC CE also includes BFR reports for other active frequency domain resources.

7. The method of any one of claims 1-4, wherein, The method further includes: No PUSCH resources are available for sending BFR reports. Send a scheduling request (SR).

8. The method of any one of claims 1-7, wherein, The method further includes: If no uplink resources are available in the terminal, a BFR is triggered for the activated frequency domain resource, and a random access procedure is initiated.

9. The method of claim 8, wherein, The process of initiating random access includes: Initiate the random access procedure based on any of the following frequency domain resources: Primary frequency domain resources, initial frequency domain resources, default frequency domain resources, and frequency domain resources indicated by the network device.

10. The method of claim 9, wherein, The method further includes: Random access is completed; the BFR of the frequency domain resources used by the random access is cancelled. Set the value of the BFR counter associated with the frequency domain resources used by the random access to the specified value.

11. The method of claim 8, wherein, The method further includes: The terminal contains other active frequency domain resources that trigger BFRs that have not been canceled, generating a BFR report. However, the BFR report does not include BFR reports for the frequency domain resources used by the random access procedure.

12. The method of any one of claims 1-11, wherein, The method further includes: The activated frequency domain resource is deactivated, and the BFR for the activated frequency domain resource is cancelled. Set the value of the BFR counter associated with the active frequency domain resource to the specified value.

13. The method of any one of claims 1-11, wherein, The method further includes: Send Media Access Control (MAC) Protocol Data Unit (PDU); The MAC PDU includes a BFR report for the active frequency domain resource, and cancels the BFR for the active frequency domain resource.

14. The method of any one of claims 1-11, wherein, The method further includes: Receive Physical Downlink Control Channel (PDCCH) information; The uplink new transmission scheduled by the PDCCH includes a BFR report for the active frequency domain resource, and sets the value of the BFR counter associated with the active frequency domain resource to a specified value.

15. A method of communication, comprising: Performed by a network device, the method includes: Sending indication information, wherein the indication information is configured to configure at least one of the following: Identification of multiple active frequency domain resources for beam failure detection (BFD) to be performed; The BFD parameters associated with the multiple activated frequency domain resources; The beam failure recovery BFR parameters associated with the multiple activated frequency domain resources.

16. The method of claim 15, wherein, The method further includes: Receive a BFR report, wherein the BFR report includes beam failure information for at least one of the plurality of active frequency domain resources.

17. A terminal, characterized by The terminal includes a processing module and a transceiver module, wherein... The processing module is used to perform beam failure detection (BFD) on multiple active frequency domain resources respectively. If a beam failure is detected on an active frequency domain resource and the number of beam failures reaches a threshold, the processing module is further configured to trigger a beam failure recovery (BFR) transmission signal for the active frequency domain resource.

18. A network device, comprising: The network device includes a processing module and a transceiver module, wherein... The transceiver module is used to send indication information, wherein the indication information is configured with at least one of the following: Identifiers of multiple active frequency domain resources for beam failure detection (BFD) to be performed; The BFD parameters associated with the multiple activated frequency domain resources; The beam failure recovery BFR parameters associated with the multiple activated frequency domain resources.

19. A communication device, characterized by The communication device includes: One or more processors; The processor is configured to execute the communication method according to any one of claims 1-14, or the processor is configured to execute the communication method according to any one of claims 15-16.

20. A storage medium, the storage medium storing instructions, wherein, When the instruction is executed on the communication device, the communication device performs the communication method as described in any one of claims 1-16.

21. A program product comprising at least one of a program, instructions, characterized in that When at least one of the programs or instructions is executed by the communication device, the communication method of any one of claims 1-16 is implemented.