Communication method, apparatus, and storage medium

Abstract

The present disclosure provides a communication method, device and storage medium. The communication method executed by a network device comprises: receiving a channel related to beam failure recovery (BFR) through a first carrier in a first time period, wherein the first time period is a time period in which the network device does not receive an uplink channel when the network device is in a cell discontinuous reception (cell DRX) state. The present disclosure can guarantee the data transmission performance of a terminal when the network device is in a cell DRX state.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and more specifically, to communication methods, apparatus, and storage media. Background Technology

[0002] To save energy, network equipment can employ a cell discontinuous reception (CDR) mechanism. This CDR mechanism involves two time periods: a first time period and a second time period. During the first time period, the network equipment does not receive certain uplink channels, such as the Physical Uplink Shared Channel (PUSCH) and the Physical Uplink Control Channel (PUCCH). During the second time period, the network equipment receives all uplink channels normally. Summary of the Invention

[0003] This disclosure provides a communication method, apparatus, and storage medium.

[0004] According to a first aspect of the present disclosure, a communication method is provided, executed by a network device, the method comprising:

[0005] During the first time period, channels related to beam failure recovery (BFR) are received via the first carrier, wherein the first time period is the period during which the network device does not receive uplink channels when it is in cell DRX state.

[0006] According to a second aspect of the embodiments of this disclosure, a communication method is provided, executed by a terminal, the method comprising:

[0007] Beam failure detected;

[0008] During the first time period, channels related to BFR are transmitted via the first carrier.

[0009] According to a third aspect of the present disclosure, a communication method is provided for a communication system, the method comprising:

[0010] The terminal detected a beam failure;

[0011] During the first time period, the terminal transmits the channel related to beam failure recovery (BFR) via the first carrier.

[0012] During the first time period, the network device receives channels related to beam failure recovery (BFR) via the first carrier.

[0013] The first time period is the period during which the network device does not receive uplink channels when it is in the cell discontinuous reception (CDR) state.

[0014] According to a fourth aspect of the present disclosure, a first communication device is provided, which may include a transceiver module, wherein the transceiver module can be used to support the communication device in communication.

[0015] When performing the steps described in the first aspect above, the transceiver module is configured to: receive a channel related to BFR via a first carrier during a first time period, wherein the first time period is the period during which the network device does not receive uplink channels when it is in cell DRX state.

[0016] According to a fifth aspect of the present disclosure, a second communication device is provided, which may include a transceiver module and a processing module, wherein the transceiver module is used to support the communication device in performing communication. The processing module is used to support the communication device in performing other processing besides communication.

[0017] When performing the steps described in the second aspect above, the processing module is configured to detect beam failure;

[0018] The transceiver module is configured to transmit a channel related to beam failure recovery (BFR) via a first carrier during a first time period, wherein the first time period is the period during which the network device does not receive uplink channels when it is in cell DRX state.

[0019] According to a sixth aspect of the present disclosure, a communication device is provided, comprising one or more processors; wherein the processors are configured to invoke instructions to cause the communication device to perform the method as described in the first or second aspect.

[0020] According to a seventh aspect of the present disclosure, a communication system is provided, including a terminal and a network device, wherein the terminal is configured to implement the method as described in the first aspect, and the access network device is configured to implement the method as described in the second aspect.

[0021] According to an eighth aspect of the present disclosure, a storage medium is provided that stores instructions, wherein when the instructions are executed on a communication device, the communication device causes the communication device to perform the method as described in the first or second aspect.

[0022] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0024] Figure 1 This is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0025] Figure 2 This is a schematic diagram illustrating DTX configuration information according to an exemplary embodiment;

[0026] Figure 3 This is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure;

[0027] Figures 4a-4f This is a flowchart illustrating a communication method according to an embodiment of the present disclosure;

[0028] Figures 5a-5f This is a flowchart illustrating a communication method according to an embodiment of the present disclosure;

[0029] Figure 6 This is a flowchart illustrating a communication method according to an embodiment of the present disclosure;

[0030] Figure 7a This is a schematic diagram of a communication device according to an embodiment of the present disclosure.

[0031] Figure 7b This is a schematic diagram of a communication device according to an embodiment of the present disclosure.

[0032] Figure 8a This is a schematic diagram of a communication device according to an embodiment of the present disclosure.

[0033] Figure 8b This is a schematic diagram of a communication device according to an embodiment of the present disclosure. Detailed Implementation

[0034] When network devices use the cell DRX mechanism, it can affect the normal operation of the BRF process.

[0035] This disclosure provides communication methods, apparatus, and readable storage media.

[0036] In a first aspect, embodiments of this disclosure provide a communication method executed by a network device, the method comprising:

[0037] During the first time period, the channel related to beam failure recovery (BFR) is received via the first carrier, wherein the first time period is the period during which the network device does not receive uplink channels when it is in the cell discontinuous reception (CDR) state.

[0038] Given that when network devices use the cell DRX mechanism, if they cannot receive channels related to BFR within the first time period according to the cell DRX configuration information, it will affect the normal progress of the BFR process.

[0039] In the above embodiments, when the network device uses the cell DRX mechanism, it no longer follows the cell DRX configuration information for channels related to BFR during the first time period. Instead, it still receives channels related to BFR during the first time period, so that the use of the cell DRX mechanism does not affect the normal operation of the BFR process, ensuring timely recovery of the terminal's beam failure and guaranteeing the terminal's data transmission performance.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the first carrier corresponds to a primary cell; or the first carrier corresponds to a primary-secondary cell; or the first carrier corresponds to a secondary cell.

[0041] In the above embodiments, the use of the cell DRX mechanism can be guaranteed to not affect the normal operation of the BFR process on different types of cells.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the BFR-related channel includes at least one of the following:

[0043] Physical random access channel (PRACH) used for BFR;

[0044] Scheduled request (SR) used for BFR;

[0045] PUSCH is used to carry the BFR medium access control control element (MAC CE).

[0046] In the above embodiments, it can be ensured that the use of the cell DRX mechanism does not affect the transmission of the uplink channel at different stages of the BFR process.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the PUSCH for carrying the BFR MAC CE includes at least one of the following:

[0048] The first PUSCH is scheduled by downlink control information (DCI) in the recovery search space;

[0049] The second PUSCH is scheduled by DCI after the terminal sends a scheduling request for BFR;

[0050] The first configured grant physical uplink shared channel (CG-PUSCH) is configured after the terminal sends a scheduling request for BFR;

[0051] The second configured authorized physical uplink shared channel CG-PUSCH is activated after the terminal sends a scheduling request for BFR.

[0052] In the above embodiments, it can be ensured that the use of the cell DRX mechanism does not affect the transmission of PUSCH used to carry BFR MAC CE by the terminal under different circumstances during the BFR process.

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

[0054] The scheduling request for BFR is received via a second carrier, which may be the same as or different from the first carrier.

[0055] In the above embodiments, it is possible to support receiving different uplink channels during the BFR process through the same or different carriers, while ensuring that the use of the cell DRX mechanism does not affect the normal operation of the BFR process.

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

[0057] The DCI is transmitted via a third carrier, which may be the same as or different from the first carrier.

[0058] In the above embodiments, it is possible to support the transmission of DCI and the reception of BFR-related channels via the same or different carriers, while ensuring that the use of the cell DRX mechanism does not affect the normal operation of the BFR process.

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

[0060] After receiving the channel related to beam failure recovery BFR via the first carrier, the first time period is terminated.

[0061] In the above embodiments, by shortening the duration of the first time period, the network device can enter the second time period earlier, allowing the network device to receive as many uplink channels as possible in advance. This sacrifices the energy-saving effect of the network device in exchange for improved data transmission performance of the terminal.

[0062] In conjunction with some embodiments of the first aspect, in some embodiments, terminating the first time period includes:

[0063] After a first duration following the reception of the BFR-related channel via the first carrier, the first time period is terminated. The first duration is equal to or greater than 0. The BFR-related channel is at least one of the following: PRACH for BFR or SR for BFR.

[0064] In the above embodiments, considering that the network device takes different amounts of time to receive different types of uplink channels, a zero or greater than zero termination delay is set for PRACH or SR for BFR with a time close to zero.

[0065] In conjunction with some embodiments of the first aspect, in some embodiments, terminating the first time period includes:

[0066] After a second duration following the reception of the BFR-related channel via the first carrier, the first time period is terminated, wherein the second duration is greater than 0, and the BFR-related channel is at least one of the following: PUSCH or CG-PUSCH.

[0067] In the above embodiments, considering that the network device takes different amounts of time to receive different types of uplink channels, a termination delay greater than zero is set for PUSCH, which takes longer to carry BFR MAC CE.

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

[0069] When the first time period is terminated, a second time period is started. The second time period is the period during which the network device receives the uplink channel while in cellDRX state.

[0070] In the above embodiments, by shortening the duration of the first time period and correspondingly increasing the duration of the second time period, the duration distribution of the first and second time periods of the cell DRX within one cycle is changed, enabling the network device to receive as many uplink channels as possible in advance. This sacrifices the energy-saving effect of the network device in exchange for improved data transmission performance of the terminal.

[0071] Secondly, embodiments of this disclosure provide a communication method executed by a terminal, the method comprising:

[0072] Beam failure detected;

[0073] During the first time period, a channel related to beam failure recovery (BFR) is transmitted via the first carrier, wherein the first time period is the period during which the network device does not receive uplink channels when it is in the cell discontinuous reception (CDR) state.

[0074] In the above embodiments, when the network device uses the cell DRX mechanism, in order to enable the network device to no longer follow the cell DRX configuration information for the BFR-related channel during the first time period, that is, to still receive the BFR-related channel during the first time period, the terminal correspondingly transmits the BFR-related channel through the first carrier during the first time period, so that the use of the cell DRX mechanism does not affect the normal BFR process, ensuring the timely recovery of the terminal's beam failure and ensuring the terminal's data transmission performance.

[0075] In conjunction with some embodiments of the second aspect, in some embodiments, the first carrier corresponds to a primary cell; or the first carrier corresponds to a primary-secondary cell; or the first carrier corresponds to a secondary cell.

[0076] In conjunction with some embodiments of the second aspect, in some embodiments, the BFR-related channel includes at least one of the following:

[0077] PRACH for BFR;

[0078] Scheduler request (SR) for BFR;

[0079] PUSCH used to carry BFRMAC CE.

[0080] In conjunction with some embodiments of the second aspect, in some embodiments, the PUSCH for carrying the BFR MAC CE includes at least one of the following:

[0081] The first PUSCH is scheduled by DCI on the recovery search space;

[0082] The second PUSCH is scheduled by DCI after the terminal sends a scheduling request for BFR;

[0083] The first CG-PUSCH is configured after the terminal sends a scheduling request for BFR;

[0084] The second CG-PUSCH is activated after the terminal sends a scheduling request for BFR.

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

[0086] The scheduling request for BFR is transmitted via a second carrier, which may be the same as or different from the first carrier.

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

[0088] The DCI is received via a third carrier, which may be the same as or different from the first carrier.

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

[0090] After transmitting the channel related to beam failure recovery BFR via the first carrier, it is expected that the first time period will be terminated.

[0091] In conjunction with some embodiments of the second aspect, in some embodiments, the expectation of terminating the first time period includes:

[0092] The network device is expected to terminate the first time period after receiving the BFR-related channel via the first carrier for a first duration, wherein the first duration is equal to or greater than 0, and the BFR-related channel is at least one of the following: PRACH for BFR, or SR for BFR.

[0093] In conjunction with some embodiments of the second aspect, in some embodiments, the expectation of terminating the first time period includes:

[0094] After a second duration following the reception of the BFR-related channel via the first carrier, the first time period is terminated, wherein the second duration is greater than 0, and the BFR-related channel is at least one of the following: PUSCH or CG-PUSCH.

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

[0096] When the first time period is terminated, a second time period is started. The second time period is the period during which the network device receives the uplink channel while in cell DRX state.

[0097] Thirdly, embodiments of this disclosure provide a communication method for a communication system, the method comprising:

[0098] The terminal detected a beam failure;

[0099] During the first time period, the terminal transmits the channel related to beam failure recovery (BFR) via the first carrier.

[0100] During the first time period, the network device receives channels related to beam failure recovery (BFR) via the first carrier.

[0101] The first time period is the period during which the network device does not receive uplink channels when it is in the cell discontinuous reception (CDR) state.

[0102] Fourthly, embodiments of this disclosure provide a first communication device, which may include a transceiver module, wherein the transceiver module can be used to support the communication device in communication. When performing the steps described in the first aspect, the transceiver module is configured to: receive a channel related to Beam Failure Recovery (BFR) via a first carrier during a first time period, wherein the first time period is the period during which the network device does not receive uplink channels when it is in cell DRX state.

[0103] Fifthly, embodiments of this disclosure provide a second communication device, which may include a transceiver module and a processing module. The transceiver module is used to support communication by the communication device, and the processing module is used to support other processing besides communication by the communication device. When performing the steps described in the second aspect above, the processing module is configured to: detect beam failure; the transceiver module is configured to: transmit a channel related to beam failure recovery (BFR) via a first carrier during a first time period.

[0104] Sixthly, embodiments of this disclosure provide a communication device, including a processor and a memory, wherein,

[0105] One or more processors;

[0106] The processor is configured to invoke instructions to cause the communication device to execute the communication method as described in the optional implementation of the first aspect, or the communication method as described in the optional implementation of the second aspect.

[0107] In a seventh aspect, embodiments of this disclosure provide a communication system including a terminal and a network device, wherein the terminal is configured to implement the communication method described in the optional implementation of the first aspect, and the network device is configured to implement the communication method described in the optional implementation of the second aspect.

[0108] Eighthly, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method as described in the optional implementations of the first or second aspect.

[0109] Ninthly, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method as described in the optional implementations of the first or second aspect.

[0110] In a tenth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in an optional implementation of the first or second aspect.

[0111] It is understood that the first communication device, the second communication device, the communication equipment, the communication system, the storage medium, the program product, and the computer program described above are all used to execute the methods provided in the embodiments of this disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0112] This disclosure provides a communication method, apparatus, and readable storage medium. In some embodiments, the terms "communication method" and "processing method," "information processing method," etc., can be used interchangeably; the terms "communication apparatus" and "processing apparatus," "information processing apparatus," etc., can be used interchangeably; and the terms "communication system" and "processing system," "information processing system," etc., can be used interchangeably.

[0113] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. 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.

[0114] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0115] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0116] In this embodiment of the disclosure, 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 following the article can be understood as either a singular expression or a plural expression.

[0117] In the embodiments disclosed herein, "multiple" refers to two or more.

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

[0119] The descriptions in this disclosure, such as "at least one of A, B, C..." or "A and / or B and / or C...", include the case where any one of A, B, C... exists alone, as well as the case where any combination of any of A, B, C... exists alone. Each case can exist alone. For example, "at least one of A, B, C" includes the cases of A alone, B alone, C alone, A and B combination, A and C combination, B and C combination, and A and B and C combination. For example, A and / or B includes the cases of A alone, B alone, and A and B combination.

[0120] In some embodiments, the notation "in one case A, in another case B" or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: A is executed regardless of B, i.e., A is executed in some embodiments; B is executed regardless of A, i.e., B is executed in some embodiments; A and B are selectively executed, i.e., A and B are selected for execution in some embodiments; A and B are both executed, i.e., A and B are executed in some embodiments. The same applies when there are more branches such as A, B, and C.

[0121] The prefixes "first," "second," etc., used in the embodiments of this disclosure 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.

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

[0123] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0124] 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”.

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

[0126] 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," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0127] 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", "useragent", "mobile client", and "client" can be used interchangeably.

[0128] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure 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., also referred to as 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.

[0129] 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.

[0130] 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", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0131] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0132] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0133] In some embodiments, the terms "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can the terms "physical uplink shared channel (PUSCH)" and "UL data". In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", and "RAN-based" can be used interchangeably.

[0134] In some embodiments, the terms "search space", "search spaceset", "search space configuration", "search spaceset configuration", "control resource set (CORESET)", and "CORESET configuration" can be used interchangeably.

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

[0136] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0137] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.

[0138] In some embodiments, the terms “resource block (RB)”, “physical resource block (PRB)”, “sub-carrier group (SCG)”, “resource element group (REG)”, “PRB pair”, “RB pair”, and “resource element (RE)” can be used interchangeably.

[0139] In some embodiments, terms such as wireless access scheme and waveform can be used interchangeably.

[0140] In some embodiments, the terms "precoding", "precoder", "weight", "precoding weight", "quasi-co-location (QCL)", "transmission configuration indication (TCI) status", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "the number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angular degree", "antenna", "antennaelement", and "panel" can be used interchangeably.

[0141] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.

[0142] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining through self-processing, or autonomously implementing, among other meanings.

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

[0144] In some embodiments, "pre-defined" or "pre-set" can be interpreted as pre-specified in an agreement or the like, or as a device or the like performing a pre-set action.

[0145] In some embodiments, determining can be interpreted as judging, deciding, judging, calculating, computing, processing, deriving, investigating, searching, looking up, searching, querying, ascertaining, receiving, transmitting, inputting, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, considering, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but is not limited to these.

[0146] 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.

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

[0148] 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 after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

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

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

[0151] Furthermore, each element, each row, or each column in the table of this disclosure 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.

[0152] Figure 1 This is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

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

[0154] In some embodiments, terminal 101 includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things 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, and wireless terminal device in smart home.

[0155] In some embodiments, network device 102 may include at least one of access network device and core network device.

[0156] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), 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 a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a wireless fidelity (WiFi) system.

[0157] In some embodiments, the technical solutions of this disclosure 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 disclosure 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.

[0158] 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.

[0159] In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), or a Next Generation Core (NGC).

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

[0161] The following embodiments of this disclosure can be applied to Figure 1 The communication system 100 shown, or a part thereof, but not limited to it. Figure 1 The entities shown are illustrative; a communication system may include... Figure 1 All or part of the main body, or may include Figure 1 Other entities besides the main body, the number and form of each entity are arbitrary, the connection relationship between the entities is illustrative, the entities may not be connected or may be connected, and 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.

[0162] The embodiments disclosed herein can be applied to 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), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Futuregeneration radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0163] In this embodiment of the disclosure, for a cell configured with cell DRX function, the first time period can also be called the inactive time period, the off time period, etc., and the cell DRX status of the network device can be marked as cell DRX-off during the first time period; the second time period can also be called the active time period, the on time period, etc., and the cell DRX status of the network device can be marked as cell DRX-on during the second time period.

[0164] Network devices perform cell DRX configuration, which can also be called the cell DRX on-off mode of the configuration period, or cell DRX configuration information configuration. The cell DRX configuration information includes at least one of the following parameters: time domain period, time domain offset, active period duration, and inactive period duration.

[0165] Network devices can configure cell DRX for carriers. For example, cell DRX can be configured for some carriers while not being configured for others. For multiple carriers with cell DRX configured, their cell DRX configuration parameters can be the same or different.

[0166] Optionally, different cell DRX configurations can be performed for different carriers, that is, different cell DRX configuration information can be configured for different carriers.

[0167] In one example, such as Figure 2 As shown, different cell DRX configuration information is configured for carrier 1 and carrier 2 respectively.

[0168] In this embodiment of the disclosure, the network device will configure one or more reference signals (RS) for beam failure detection (BFD) for each carrier, and will also configure one or more reference signals for BFR for the terminal. The reference signal for BFR can also be called a candidate beam reference signal (RS).

[0169] Terminals may occupy different cells, such as the primary cell (Pcell) and at least one secondary cell (Scell) in a primary cell group, or the primary cell (PScell) and at least one secondary cell in a secondary cell group. The primary cell (Pcell) and primary secondary cell (PScell) can be collectively referred to as special cells (spcell).

[0170] In this embodiment of the disclosure, the network device may configure a first resource and a recovery search space on the spcell, wherein the first resource may be at least one of the following: a PRACH resource for BFR and an SR resource for BFR.

[0171] Beam recovery methods for spcells can include:

[0172] After detecting a beam failure on the spcell, the terminal sends the channel on the first resource to the network device via the first resource, thereby notifying the network device that a beam failure has occurred. The terminal listens for the DCI in the recovery search space within a preset time window, which corresponds to the BFR (beam failure recovery) timer. The DCI indicates the time-frequency resource location of the scheduled first PUSCH. The terminal sends a BFR MAC CE on the first PUSCH, which contains a reference pilot signal corresponding to the new beam for BFR.

[0173] In this embodiment of the disclosure, the network device may configure a second resource on the spcell, the second resource corresponding to the SR used for BFR.

[0174] Beam recovery for Scell ​​can be achieved using one of the following three methods:

[0175] In the first approach, after detecting beam failure on the Scell, the terminal sends a SR for BFR to the network device via the second resource and receives a DCI from the network device, the DCI indicating the time-frequency resource location of the scheduled first PUSCH. The terminal then sends the second PUSCH, which carries a BFR MAC CE, containing a reference pilot signal corresponding to the new beam for BFR. The DCI or the second PUSCH can correspond to any carrier.

[0176] In the second approach, after detecting beam failure on the Scell, the terminal sends an SR for BFR to the network device via the second resource, obtains the first CG-PUSCH resource configured by the network device, and sends the first CG-PUSCH. The first CG-PUSCH carries a BFR MAC CE, and the BFR MAC CE contains a reference signal pilot corresponding to the new beam for BFR. The first CG-PUSCH can correspond to any carrier.

[0177] In the third approach, after detecting beam failure on the Scell, the terminal sends an SR for BFR to the network device via the second resource, receives activation information from the network device, which instructs the activation of the configured second CG-PUSCH, and sends the second CG-PUSCH. The second CG-PUSCH carries a BFR MAC CE, and the BFR MAC CE contains a reference signal pilot corresponding to the new beam for BFR. The second CG-PUSCH can correspond to any carrier.

[0178] In the above-mentioned methods, when the resource consumption of the PUSCH (including the first PUSCH, the second PUSCH, the first CG-PUSCH, and the second CG-PUSCH) carrying the BFR MAC CE is large, the BFR MAC CE is a regular BFR MAC CE; when the corresponding resource consumption is small, the BFR MAC CE is a truncated BFR MAC CE.

[0179] Figure 3 This is an interactive schematic diagram illustrating a communication method according to an embodiment of this disclosure. For example... Figure 3 As shown, this disclosure relates to a communication method for a communication system 100, the method comprising:

[0180] In step S3101, terminal 101 detected a beam failure.

[0181] In some embodiments, terminal 101 detects a beam failure on the spcell.

[0182] In some embodiments, terminal 101 detects beam failure on the scell.

[0183] In step S3102, terminal 101 sends at least one of the following: a channel related to BFR, information related to BFR, and / or network device 102 sends at least one of the following: a channel related to BFR, information related to BFR.

[0184] In some embodiments, terminal 101 sends a channel related to BFR to network device 102, and network device 102 receives the channel related to BFR.

[0185] In some embodiments, network device 102 sends information related to BFR to terminal 101, and terminal 101 receives the information related to BFR.

[0186] In some embodiments, terminal 101 transmits the BFR-related channel to network device via a first carrier, and network device 102 receives the BFR-related channel via the first carrier.

[0187] In some embodiments, terminal 101 sends the BFR-related channel to network device during a first time period, and network device 102 receives the BFR-related channel during the first time period.

[0188] In some embodiments, terminal 101 transmits a BFR-related channel to network device via a first carrier during a first time period, and network device 102 receives the BFR-related channel via the first carrier during the first time period.

[0189] In some embodiments, the first time period is the period during which the network device 102 does not receive uplink channels when it is in cell DRX state.

[0190] Optionally, the first time period is the period during which the network device 102 abnormally receives the uplink channel when it is in the cell DRX state.

[0191] Optionally, the first time period is the period during which network device 102 does not receive some uplink channels when it is in cell DRX state. For example, the partial uplink channels are PRACH, SR, and PUSCH.

[0192] In some embodiments, the first carrier corresponds to the primary cell.

[0193] In some embodiments, the first carrier corresponds to a primary or secondary cell.

[0194] In some embodiments, the first carrier corresponds to a secondary cell.

[0195] In some embodiments, the BFR-related channel includes at least one of the following:

[0196] PRACH for BFR;

[0197] Scheduler request (SR) for BFR;

[0198] PUSCH used to carry BFRMAC CE.

[0199] Optionally, the BFR MAC CE can be a conventional BFR MAC CE or a reduced BFR MAC CE.

[0200] In some embodiments, the PUSCH for carrying the BFR MAC CE includes at least one of the following:

[0201] The first PUSCH is scheduled by DCI on the recovery search space;

[0202] The second PUSCH is scheduled by DCI after the terminal sends a scheduling request for BFR;

[0203] The first CG-PUSCH is configured after the terminal sends a scheduling request for BFR;

[0204] The second CG-PUSCH is activated after the terminal sends a scheduling request for BFR.

[0205] Optionally, the recovery search space corresponds to the secondary cell.

[0206] In some embodiments, the channel associated with the BFR is a first channel.

[0207] In some embodiments, the first channel is at least one of the following: PRACH for BFR and SR for BFR.

[0208] Optionally, the PRACH resources for BFR are pre-configured.

[0209] Optionally, the SR resources used for BFR are pre-configured.

[0210] In some embodiments, the first channel may carry a beam recovery request.

[0211] In some embodiments, terminal 101 transmits the first channel to the network device via a first carrier during a first time period. Alternatively, when terminal 101 transmits the first channel via the first carrier, the first carrier is within the first time period at the time of transmission of the first channel.

[0212] Optionally, the first channel is at least one of the following: PRACH for BFR, SR for BFR; the first carrier corresponds to the spcell.

[0213] Optionally, the first channel is an SR for BFR; the first carrier corresponds to the Scell.

[0214] In some embodiments, the information related to BFR is first information.

[0215] In some embodiments, the first information includes at least one of the following: DCI, configuration information, and activation information.

[0216] In some embodiments, network device 102 sends first information to terminal 101, and terminal 101 receives the first information.

[0217] In some embodiments, network device 102 sends the first information to terminal 101 via a second carrier, and terminal 101 receives the first information via the second carrier, which may be the same as or different from the first carrier.

[0218] In some embodiments, in step S3101, if terminal 101 detects a beam failure on the spcell, the channel related to BFR sent by terminal 101 to network device 102 is the first channel, and the first information sent by network device 102 to terminal 101 is the first DCI, which is used to schedule the first PUSCH.

[0219] Optionally, network device 102 sends the first DCI over the recovery search space.

[0220] Optionally, the recovery search space is pre-configured.

[0221] In some embodiments, network device 102 transmits the first DCI over the recovery search space via the second carrier.

[0222] In some embodiments, in step S3101, terminal 101 detects beam failure on Scell, and the channel related to BFR sent by terminal 101 to network device 102 is the SR for BFR. The first information sent by network device 102 to terminal 101 is the second DCI, and the second DCI is used to schedule the second PUSCH.

[0223] In some embodiments, in step S3101, terminal 101 detects beam failure on Scell, and the channel related to BFR sent by terminal 101 to network device 102 is the SR for BFR. The first information sent by network device 102 to terminal 101 is configuration information, which is used to configure the first CG-PUSCH.

[0224] In some embodiments, in step S3101, terminal 101 detects beam failure on Scell, and the channel related to BFR sent by terminal 101 to network device 102 is the SR for BFR. The first information sent by network device 102 to terminal 101 is activation information, which is used to activate the second CG-PUSCH.

[0225] In some embodiments, the channel associated with the BFR is a second channel.

[0226] In some embodiments, terminal 101 sends a second channel to network device, and network device 102 receives the second channel.

[0227] In some embodiments, the second channel includes at least one of the following: a second PUSCH, a first CG-PUSCH, and a second CG-PUSCH.

[0228] In some embodiments, terminal 101 transmits the second channel to network device 102 via a third carrier, the third carrier being the same as or different from the first carrier, and the third carrier being the same as or different from the second carrier.

[0229] In some embodiments, the third channel carries a BFR MAC CE, which is a conventional BFR MAC CE or a reduced BFR MAC CE.

[0230] Optionally, the BFR MAC CE includes a new beam-corresponding reference signal pilot for the BFR.

[0231] In some embodiments, terminal 101 sends the second channel to network device 102 during a first time period.

[0232] In some embodiments, in step S3101, terminal 101 detects beam failure on spcell, terminal 101 sends the first channel to network device, the first information sent by network device 102 to terminal 101 is the first DCI, and the second channel sent by terminal 101 to network device is the second PUSCH, the second PUSCH carrying the BFR MAC CE.

[0233] In some embodiments, in step S3101, terminal 101 detects beam failure on Scell, terminal 101 sends the SR for BFR to network device, the first information sent by network device 102 to terminal 101 is the second DCI, the second DCI is used to schedule the second PUSCH, the second channel sent by terminal 101 to network device is the second PUSCH, and the second PUSCH carries BFR MAC CE.

[0234] In some embodiments, in step S3101, terminal 101 detects beam failure on Scell, terminal 101 sends the SR for BFR to network device, the first information sent by network device 102 to terminal 101 is configuration information, the configuration information is used to configure the first CG-PUSCH, the second channel sent by terminal 101 to network device is the first CG-PUSCH, and the first CG-PUSCH carries BFR MAC CE.

[0235] In some embodiments, in step S3101, terminal 101 detects beam failure on Scell, terminal 101 sends the SR for BFR to network device, the first information sent by network device 102 to terminal 101 is activation information, the activation information is used to activate the second CG-PUSCH, the second channel sent by terminal 101 to network device is the second CG-PUSCH, and the second CG-PUSCH carries BFR MAC CE.

[0236] In step S3103, network device 102 terminates the first time period.

[0237] In some embodiments, when the channel associated with BFR is PRACH for BFR or SR for BFR, the network device 102 terminates the first time period after receiving the first channel via the first carrier for a first duration, wherein the first duration is equal to or greater than 0.

[0238] In some embodiments, when the channel associated with BFR is a PUSCH carrying BFRMAC CE, the network device 102 terminates the first time period after receiving the first channel via the first carrier for a second duration, wherein the second duration is greater than 0.

[0239] In some embodiments, when the network device 102 terminates the first time period, it starts a second time period, which is the time period during which the network device 102 receives the uplink channel while in cell DRX state.

[0240] Optionally, the second time period is the period during which network device 102 normally receives the uplink channel when it is in cell DRX state.

[0241] Optionally, the second time period is the period during which network device 102 receives all uplink channels when it is in cell DRX state.

[0242] In step S3104, terminal 101 expects network device 102 to terminate the first time period.

[0243] In some embodiments, when the transmission of the channel related to BFR is a PRACH for BFR or an SR for BFR, the terminal 101 expects the network device 102 to terminate the first time period after receiving the first channel via the first carrier for a first duration, wherein the first duration is equal to or greater than 0.

[0244] In some embodiments, when the channel associated with BFR is a PUSCH carrying BFRMAC CE, terminal 101 expects network device 102 to terminate the first time period after receiving the first channel via the first carrier for a second duration, wherein the second duration is greater than 0.

[0245] In some embodiments, terminal 101 expects network device 102 to start a second time period when the first time period ends, the second time period being the time period during which network device 102 receives uplink channels in cell DRX state.

[0246] In some embodiments, at least one of steps S3101 to S3104 may be performed. For example, step S3102 may be implemented as a standalone embodiment; step S3101 + step S3102 may be implemented as a standalone embodiment; step S3102 + step S3103 may be implemented as a standalone embodiment; step S3102 + step S3104 may be implemented as a standalone embodiment; and step S3102 + step S3103 + step S3104 may be implemented as a standalone embodiment; but not limited thereto.

[0247] Figure 4a This is a flowchart illustrating a communication method according to an embodiment of this disclosure. Figure 4a As shown, this disclosure relates to a communication method executed by network device 102, the method including:

[0248] Step S4101: Receive channels related to BFR and / or transmit information related to BFR.

[0249] For optional implementations of step S4101, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0250] Figure 4b This is a flowchart illustrating a communication method according to an embodiment of this disclosure. Figure 4b As shown, this disclosure relates to a communication method executed by network device 102, the method including:

[0251] Step S4201: Receive the channel associated with BFR.

[0252] For optional implementations of step S4201, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described again here.

[0253] Step S4202: Terminate the first time period.

[0254] For optional implementations of step S4202, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3103, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0255] In some embodiments, at least one of steps S4201 to S4202 may be performed. For example, step S4201 may be implemented as a standalone embodiment; step S4202 may be implemented as a standalone embodiment; but it is not limited thereto.

[0256] Figure 4c A flowchart illustrating a communication method according to embodiments of this disclosure is shown. Figure 4c As shown, this disclosure relates to a communication method executed by network device 102, the method including:

[0257] Step S4301: Receive the first channel.

[0258] For optional implementations of step S4301, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0259] In some embodiments, the first channel may carry a beam recovery request.

[0260] In some embodiments, the first channel is at least one of the following: PRACH for BFR and SR for BFR.

[0261] In some embodiments, the first channel is received on PRACH resources used for BFR.

[0262] In some embodiments, the first channel is received on SR resources used for BFR.

[0263] In some embodiments, the first channel is received on PRACH resources for BFR and SR resources for BFR.

[0264] Optionally, the PRACH resources for BFR are pre-configured.

[0265] Optionally, the SR resources used for BFR are pre-configured.

[0266] Step S4302: Send the first message.

[0267] For optional implementations of step S4302, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0268] In some embodiments, the first information includes at least one of the following: DCI, configuration information, and activation information.

[0269] Step S4303: Receive the second channel.

[0270] For optional implementations of step S4303, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0271] In some embodiments, the second channel includes at least one of the following: a second PUSCH, a first CG-PUSCH, and a second CG-PUSCH.

[0272] In some embodiments, the third channel carries a BFR MAC CE, which is a conventional BFR MAC CE or a reduced BFR MAC CE.

[0273] In some embodiments, terminal 101 detects beam failure on spcell, the first information is the second DCI, the second channel is the first PUSCH, and the first PUSCH carries the BFR MAC CE.

[0274] In some embodiments, terminal 101 detects beam failure on Scell, the second channel is the second PUSCH, and the second PUSCH carries BFR MAC CE.

[0275] In some embodiments, terminal 101 detects beam failure on Scell, the first information is configuration information, the second channel is the first CG-PUSCH, and the first CG-PUSCH carries BFR MAC CE.

[0276] In some embodiments, terminal 101 detects beam failure on Scell, the first information is activation information, the second channel is the second CG-PUSCH, and the second CG-PUSCH carries BFR MAC CE.

[0277] In some embodiments, at least one of steps S4301 to S4303 may be performed. For example, step S4301 may be implemented as a standalone embodiment; step S4303 may be implemented as a standalone embodiment; step S4301 + step S4302 may be implemented as a standalone embodiment; step S4302 + step S4303 may be implemented as a standalone embodiment; but not limited thereto.

[0278] Figure 4d A flowchart illustrating a communication method according to embodiments of this disclosure is shown. Figure 4d As shown, this disclosure relates to a communication method executed by network device 102, the method including:

[0279] Step S4401: Receive the first channel.

[0280] For optional implementations of step S4401, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0281] In some embodiments, a second channel is received during a first time period.

[0282] Step S4402: Terminate the first time period.

[0283] For optional implementations of step S4402, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3103, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0284] In some embodiments, at least one of steps S4401 to S4402 may be performed. For example, step S4401 may be implemented as a standalone embodiment; step S4402 may be implemented as a standalone embodiment; but it is not limited thereto.

[0285] Figure 4e A flowchart illustrating a communication method according to embodiments of this disclosure is shown. Figure 4e As shown, this disclosure relates to a communication method executed by network device 102, the method including:

[0286] Step S4501: Receive the first channel.

[0287] For optional implementations of step S4501, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0288] Step S4502: Send the first message.

[0289] For optional implementations of step S4502, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0290] Step S4503: Receive the second channel.

[0291] For optional implementations of step S4503, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0292] In some embodiments, a second channel is received during a first time period.

[0293] Step S4504: Terminate the first time period.

[0294] For optional implementations of step S4502, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3103, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0295] In some embodiments, at least one of steps S4501 to S4504 may be performed. For example, step S4501 may be implemented as a standalone embodiment; step S4503 may be implemented as a standalone embodiment; step S4503 + step S4504 may be implemented as a standalone embodiment; or step S4501 + step S4503 + step S4504 may be implemented as a standalone embodiment; but not limited thereto.

[0296] Figure 4f A flowchart illustrating a communication method according to embodiments of this disclosure is shown. Figure 4f As shown, this disclosure relates to a communication method executed by network device 102, the method including:

[0297] Step S4601: During the first time period, receive the channel related to beam failure recovery BFR via the first carrier.

[0298] In some embodiments, the first time period is the period during which the network device does not receive uplink channels when it is in the cell discontinuous reception (CDR) state.

[0299] In some embodiments, the first carrier corresponds to a primary cell; or the first carrier corresponds to a primary-secondary cell; or the first carrier corresponds to a secondary cell.

[0300] In some embodiments, the BFR-related channel includes at least one of the following:

[0301] Physical Random Access Channel (PRACH) used for BFR;

[0302] Scheduler request (SR) for BFR;

[0303] The Physical Uplink Shared Channel (PUSCH) is used to carry the BFR Media Access Control (MAC) control element CE.

[0304] In some embodiments, the PUSCH for carrying the BFR MAC CE includes at least one of the following:

[0305] The first PUSCH is scheduled by downlink control information (DCI) on the recovery search space;

[0306] The second PUSCH is scheduled by the downlink control information (DCI) after the terminal sends a scheduling request for BFR.

[0307] The first configured authorized physical uplink shared channel CG-PUSCH is configured after the terminal sends a scheduling request for BFR;

[0308] The second CG-PUSCH is activated after the terminal sends a scheduling request for BFR.

[0309] In some embodiments, the method further includes:

[0310] The scheduling request for BFR is received via a second carrier, which may be the same as or different from the first carrier.

[0311] In some embodiments, the method further includes:

[0312] The DCI is transmitted via a third carrier, which may be the same as or different from the first carrier.

[0313] In some embodiments, the method further includes:

[0314] After receiving the channel related to beam failure recovery BFR via the first carrier, the first time period is terminated.

[0315] In some embodiments, terminating the first time period includes:

[0316] After a first duration following the reception of the BFR-related channel via the first carrier, the first time period is terminated. The first duration is equal to or greater than 0. The BFR-related channel is at least one of the following: PRACH for BFR or SR for BFR.

[0317] In some embodiments, terminating the first time period includes:

[0318] After a second duration following the reception of the BFR-related channel via the first carrier, the first time period is terminated, wherein the second duration is greater than 0, and the BFR-related channel is at least one of the following: PUSCH or CG-PUSCH.

[0319] In some embodiments, the method further includes:

[0320] When the first time period is terminated, a second time period is started. The second time period is the period during which the network device receives the uplink channel while in cell DRX state.

[0321] Figure 5a This is a flowchart illustrating a communication method according to an embodiment of this disclosure. Figure 5a As shown, this disclosure relates to a communication method executed by terminal 101. The method includes:

[0322] Step S5101: Send channels related to BFR and / or receive information related to BFR.

[0323] For optional implementations of step S5101, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0324] Figure 5b This is a flowchart illustrating a communication method according to an embodiment of this disclosure. Figure 5b As shown, this disclosure relates to a communication method executed by terminal 101. The method includes:

[0325] Step S5201: Beam failure detected.

[0326] For optional implementations of step S5201, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3101, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0327] Step S5202: Send the channel related to BFR.

[0328] For optional implementations of step S5202, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0329] In some embodiments, channels related to BFR are transmitted during a first time period.

[0330] Step S5203, expecting to terminate the first period.

[0331] For optional implementations of step S5203, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3104, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0332] In some embodiments, at least one of steps S5201 to S5203 may be performed. For example, step S5202 may be implemented as a standalone embodiment; steps S5201+S5202 may be implemented as standalone embodiments; steps S5202+S5203 may be implemented as standalone embodiments; but not limited thereto.

[0333] Figure 5c This is a flowchart illustrating a communication method according to an embodiment of this disclosure. Figure 5c As shown, this disclosure relates to a communication method executed by terminal 101. The method includes:

[0334] Step S5301: Beam failure detected.

[0335] For optional implementations of step S5301, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3101, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0336] Step S5302: Send the first channel.

[0337] For optional implementations of step S5302, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0338] Step S5303: Receive the first information.

[0339] For optional implementations of step S5303, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0340] Step S5304: Send the second channel.

[0341] For optional implementations of step S5204, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0342] In some embodiments, at least one of steps S5301 to S5304 may be performed. For example, step S5302 may be implemented as a standalone embodiment; step S5304 may be implemented as a standalone embodiment; step S5301 + step S5302 may be implemented as a standalone embodiment; step S5302 + step S5303 + step S5304 may be implemented as a standalone embodiment; but not limited thereto.

[0343] Figure 5d This is a flowchart illustrating a communication method according to an embodiment of this disclosure. Figure 5d As shown, this disclosure relates to a communication method executed by terminal 101. The method includes:

[0344] Step S5401: Beam failure detected.

[0345] For optional implementations of step S5401, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3101, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0346] Step S5402: Send the first channel.

[0347] For optional implementations of step S5402, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0348] In some embodiments, a first channel is transmitted during a first time period.

[0349] Step S5403, expecting to terminate the first time period.

[0350] The content of expecting to terminate the first time period in step S5403 is the same as the content of expecting to terminate the first time period in step S3103, and will not be repeated here.

[0351] In some embodiments, at least one of steps S5401 to S5403 may be performed. For example, step S5401 + step S5402 may be implemented as a standalone embodiment; step S5402 + step S5403 may be implemented as a standalone embodiment; but it is not limited thereto.

[0352] Figure 5e This is a flowchart illustrating a communication method according to an embodiment of this disclosure. Figure 5e As shown, this disclosure relates to a communication method executed by terminal 101. The method includes:

[0353] Step S5501: Beam failure detected.

[0354] For optional implementations of step S5501, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3101, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0355] Step S5502: Send the first channel.

[0356] For optional implementations of step S5502, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0357] Step S5503: Receive the first information.

[0358] For optional implementations of step S5503, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0359] Step S5504: Send the second channel.

[0360] For optional implementations of step S5504, please refer to [link / reference]. Figure 3 Optional implementation methods of step S3102, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0361] In some embodiments, a second channel is transmitted during a first time period.

[0362] Step S5505, expecting to terminate the first time period.

[0363] The content of expecting to terminate the first time period in step S5505 is the same as the content of expecting to terminate the first time period in step S3103, and will not be repeated here.

[0364] In some embodiments, at least one of steps S5501 to S5505 may be performed. For example, step S5502 may be implemented as a standalone embodiment; step S5504 may be implemented as a standalone embodiment; step S5501 + step S5502 may be implemented as a standalone embodiment; step S5504 + step S5305 may be implemented as a standalone embodiment; step S5502 + step S5503 + step S5504 may be implemented as a standalone embodiment; and step S5502 + step S5503 + step S5504 + step S5505 may be implemented as a standalone embodiment; but not limited thereto.

[0365] Figure 5f This is a flowchart illustrating a communication method according to an embodiment of this disclosure. Figure 5f As shown, this disclosure relates to a communication method executed by terminal 101. The method includes:

[0366] Step S5601, beam failure detected;

[0367] Step S5602: During the first time period, transmit the channel related to beam failure recovery BFR via the first carrier.

[0368] In some embodiments, the first time period is the period during which the network device does not receive uplink channels when it is in the cell discontinuous reception (CDR) state.

[0369] Beam failure detected;

[0370] During the first time period, a channel related to beam failure recovery (BFR) is transmitted via the first carrier, wherein the first time period is the period during which the network device does not receive uplink channels when it is in the cell discontinuous reception (CDR) state.

[0371] In some embodiments, the first carrier corresponds to a primary cell; or the first carrier corresponds to a primary-secondary cell; or the first carrier corresponds to a secondary cell.

[0372] In some embodiments, the BFR-related channel includes at least one of the following:

[0373] Physical Random Access Channel (PRACH) used for BFR;

[0374] Scheduler request (SR) for BFR;

[0375] The Physical Uplink Shared Channel (PUSCH) is used to carry the BFR Media Access Control (MAC) control element CE.

[0376] In some embodiments, the PUSCH for carrying the BFR MAC CE includes at least one of the following:

[0377] The first PUSCH is scheduled by downlink control information (DCI) on the recovery search space;

[0378] The second PUSCH is scheduled by the downlink control information (DCI) after the terminal sends a scheduling request for BFR.

[0379] The first configured authorized physical uplink shared channel CG-PUSCH is configured after the terminal sends a scheduling request for BFR;

[0380] The second CG-PUSCH is activated after the terminal sends a scheduling request for BFR.

[0381] In some embodiments, the method further includes:

[0382] The scheduling request for BFR is transmitted via a second carrier, which may be the same as or different from the first carrier.

[0383] In some embodiments, the method further includes:

[0384] The DCI is received via a third carrier, which may be the same as or different from the first carrier.

[0385] In some embodiments, the method further includes:

[0386] After transmitting the channel related to beam failure recovery BFR via the first carrier, it is expected that the first time period will be terminated.

[0387] In some embodiments, the expectation of terminating the first time period includes:

[0388] The network device is expected to terminate the first time period after receiving the BFR-related channel via the first carrier for a first duration, wherein the first duration is equal to or greater than 0, and the BFR-related channel is at least one of the following: PRACH for BFR, or SR for BFR.

[0389] In some embodiments, the expectation of terminating the first time period includes:

[0390] The first time period is expected to terminate after a second duration following the network device receiving the BFR-related channel via the first carrier, wherein the second duration is greater than 0, and the BFR-related channel is at least one of the following: PUSCH or CG-PUSCH.

[0391] In some embodiments, the method further includes:

[0392] It is expected that when the network device terminates the first time period, it will start the second time period, which is the time period during which the network device receives the uplink channel while in cell DRX state.

[0393] Figure 6 This is a schematic diagram illustrating a communication method according to an embodiment of this disclosure. For example... Figure 6 As shown, the embodiments of this disclosure relate to a communication method, which includes:

[0394] In step S6101, network device 102 receives a channel related to BFR via the first carrier while the first carrier is in cell DRX-off state.

[0395] In some embodiments, the first carrier may be a special cell (spcell) or a secondary cell (Scell).

[0396] In some embodiments, the BFR-related channels include at least one of the following: PRACH for BFR, SR for BFR, and PUSCH for carrying BFR MAC CE.

[0397] In some embodiments, terminal 101 transmits the BFR-related channel via the first carrier.

[0398] In some embodiments, the PUSCH for carrying the BFR MAC CE includes at least one of the following:

[0399] PUSCH scheduled by DCI in the BFR search space;

[0400] CG-PUSCH after the UE sends the SR for BFR;

[0401] The scheduled PUSCH following the SR sent by the UE for BFR.

[0402] Optionally, the DCI corresponding to the PUSCH used to carry the BFR MAC CE is transmitted via a second carrier, which may be the same as or different from the first carrier.

[0403] In step S6102, network device 102 terminates the cell DTX-off period on the first carrier.

[0404] After the cell DTX-off period on the first carrier is terminated, network device 102 can normally receive various uplink channels, and thus can receive various uplink channels that the terminal normally sends.

[0405] In some embodiments, at least one of steps S6101 to S6102 may be performed. For example, step S6101 may be implemented as a standalone embodiment; however, it is not limited thereto.

[0406] The following examples illustrate this.

[0407] Example 1:

[0408] The first carrier is configured with PRACH for BFR. While the first carrier is in cell DTX-OFF, network device 102 will still listen for PRACH for BFR on the first carrier.

[0409] Example 2:

[0410] The first carrier is configured with an SR for BFR. While the first carrier is in cell DTX-OFF, network device 102 still needs to listen for the SR for BFR on the first carrier.

[0411] Example 3:

[0412] Network device 102 transmits DCI in the BFR search space, the DCI being scheduled on the PUSCH of the first carrier.

[0413] Network device 102 still needs to receive the PUSCH on the first carrier while the first carrier is in cell DTX-OFF.

[0414] The BFR search space is located on the second carrier, which may be the same as or different from the first carrier.

[0415] Example 4:

[0416] Terminal 101 transmits an SR for BFR on the second carrier and receives a scheduling DCI on the third carrier that schedules a PUSCH on the first carrier during the cell DTX-OFF period of the first carrier.

[0417] Network device 102 still needs to receive the PUSCH on the first carrier.

[0418] Optionally, the first, second, and third carriers may be the same or different.

[0419] Example 5:

[0420] Terminal 101 transmits an SR for BFR on the second carrier. After transmitting the SR, it obtains CG-PUSCH resources on the first carrier. The CG-PUSCH is during the cell DTX-OFF period of the first carrier. Network device 102 receives the CG-PUSCH on the first carrier.

[0421] Optionally, the first and second carriers may be the same or different.

[0422] Example 6:

[0423] During the cell DTX-OFF period of the first carrier, network device 102 receives a BFR-related channel on the first carrier. After a set duration T following the receipt of the channel, the network device ends the cell DTX-OFF period on the first carrier, where T can be equal to 0 or greater than 0.

[0424] Optionally, when the BFR-related channel is PRACH or SR, T can be equal to 0, because the time required for the network device to detect PRACH or SR is very short, and it can be considered that it can be detected immediately.

[0425] Optionally, when the BFR-related channel is PUSCH or CG-PUSCH, T can be greater than 0, because the network device needs some time to demodulate PUSCH or CG-PUSCH.

[0426] This disclosure also provides apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that 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.

[0427] 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.

[0428] In this disclosure, 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 type of 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. In addition, 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), a Deep Learning Processing Unit (DPU), etc.

[0429] Figure 7a This is a schematic diagram of the structure of the first communication device provided in an embodiment of this disclosure. Figure 7a As shown, the first communication device includes a transceiver module 7101. Optionally, the transceiver module 7101 is used to perform the communication method-related steps performed by the network device 102 in any of the above methods, which will not be described in detail here. Optionally, the first communication device 7100 further includes a processing module 7102, which is used to perform processing-related steps unrelated to transmission and reception performed by the terminal 101 in any of the above methods, which will not be described in detail here.

[0430] Figure 7b This is a schematic diagram of the structure of the second communication device provided in an embodiment of this disclosure. Figure 7bAs shown, the second communication device includes a transceiver module 7201. Optionally, the transceiver module 7201 is used to perform the communication method-related steps performed by the terminal 101 in any of the above methods, which will not be described in detail here. Optionally, it also includes a processing module 7202, which is used to perform processing-related steps unrelated to transmission and reception performed by the terminal 101 in any of the above methods, which will not be described in detail here.

[0431] Figure 8a This is a schematic diagram of the structure of the communication device 8100 provided in this embodiment. The communication device 8100 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 8100 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.

[0432] like Figure 8a As shown, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can 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. The processor 8101 is used to invoke instructions to cause the communication device 8100 to execute any of the above methods.

[0433] In some embodiments, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may also be located outside the communication device 8100.

[0434] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the communication steps such as sending and receiving in the above method are performed by the transceivers 8103, and other steps are performed by the processor 8101.

[0435] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, etc., may be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., may be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., may be used interchangeably.

[0436] Optionally, the communication device 8100 further includes one or more interface circuits 8104, which are connected to the memory 8102. The interface circuits 8104 can be used to receive signals from the memory 8102 or other devices, and can be used to send signals to the memory 8102 or other devices. For example, the interface circuits 8104 can read instructions stored in the memory 8102 and send the instructions to the processor 8101.

[0437] The communication device 8100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 8100 described in this disclosure is not limited thereto, and the structure of the communication device 8100 may vary. Figure 8a The limitations. The communication device can be a standalone device or part of a larger device. For example, the communication device can be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally including storage components for storing data and programs; (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.

[0438] Figure 8b This is a schematic diagram of the structure of chip 8200 provided in an embodiment of this disclosure. For cases where the communication device 8100 can be a chip or a chip system, please refer to... Figure 8b The diagram shown is a schematic representation of the structure of chip 8200, but is not limited thereto. Chip 8200 includes one or more processors 8201, which are used to invoke instructions to cause chip 8200 to execute any of the methods described above.

[0439] In some embodiments, chip 8200 further includes one or more interface circuits 8202 connected to memory 8203. Interface circuits 8202 can be used to receive signals from memory 8203 or other devices, and can also be used to send signals to memory 8203 or other devices. For example, interface circuit 8202 can read instructions stored in memory 8203 and send those instructions to processor 8201. Optionally, terms such as interface circuit, interface, transceiver pin, and transceiver can be used interchangeably.

[0440] In some embodiments, chip 8200 further includes one or more memories 8203 for storing instructions. Optionally, all or part of the memories 8203 may be located outside of chip 8200.

[0441] This disclosure also provides a storage medium storing instructions that, when executed on a communication device 8100, cause the communication device 8100 to perform any of the methods described above. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is 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 is not limited thereto; it may also be a temporary storage medium.

[0442] This disclosure also provides a program product, which, when executed by a communication device 8100, causes the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0443] This disclosure also provides a computer program that, when run on a computer, causes the computer to perform any of the above methods.

[0444] Industrial applicability

[0445] When using the cell DRX mechanism, network devices will no longer follow the cell DRX configuration information for channels related to BFR during the first time period. They will still receive channels related to BFR during the first time period, so that the use of the cell DRX mechanism does not affect the normal BFR process, ensuring timely recovery of the terminal's beam failure and guaranteeing the terminal's data transmission performance.

Claims

1. A communication method performed by a network device, the method comprising: During the first time period, the channel related to beam failure recovery (BFR) is received via the first carrier, wherein the first time period is the period during which the network device does not receive uplink channels when it is in the cell discontinuous reception (CDR) state.

2. The method as described in claim 1, wherein, The first carrier corresponds to the primary cell; or The first carrier corresponds to the primary and secondary cells; or The first carrier corresponds to the secondary cell.

3. The method as described in claim 1 or 2, wherein, The channels associated with BFR include at least one of the following: Physical Random Access Channel (PRACH) used for BFR; Scheduler request (SR) for BFR; The Physical Uplink Shared Channel (PUSCH) is used to carry the BFR Media Access Control (MAC) control element CE.

4. The method of claim 3, wherein, The PUSCH used to carry the BFR MAC CE includes at least one of the following: The first PUSCH is scheduled by downlink control information (DCI) on the recovery search space; The second PUSCH is scheduled by the downlink control information (DCI) after the terminal sends a scheduling request for BFR. The first configured authorized physical uplink shared channel CG-PUSCH is configured after the terminal sends a scheduling request for BFR; The second CG-PUSCH is activated after the terminal sends a scheduling request for BFR.

5. The method of claim 4, wherein, The method further includes: The scheduling request for BFR is received via a second carrier, which may be the same as or different from the first carrier.

6. The method as described in claim 4 or 5, wherein, The method further includes: The DCI is transmitted via a third carrier, which may be the same as or different from the first carrier.

7. The method of claim 1, wherein, The method further includes: After receiving the channel related to beam failure recovery BFR via the first carrier, the first time period is terminated.

8. The method of claim 7, wherein, The termination of the first time period includes: After a first duration following the reception of the BFR-related channel via the first carrier, the first time period is terminated. The first duration is equal to or greater than 0. The BFR-related channel is at least one of the following: PRACH for BFR or SR for BFR.

9. The method of claim 7, wherein, The termination of the first time period includes: After a second duration following the reception of the BFR-related channel via the first carrier, the first time period is terminated, wherein the second duration is greater than 0, and the BFR-related channel is at least one of the following: PUSCH or CG-PUSCH.

10. The method according to any one of claims 7 to 9, wherein, The method further includes: When the first time period is terminated, a second time period is started. The second time period is the period during which the network device receives the uplink channel while in cellDRX state.

11. A communication method, executed by a terminal, the method comprising: Beam failure detected; During the first time period, a channel related to beam failure recovery (BFR) is transmitted via the first carrier, wherein the first time period is the period during which the network device does not receive uplink channels when it is in the cell discontinuous reception (CDR) state.

12. The method of claim 11, wherein, The first carrier corresponds to the primary cell; or The first carrier corresponds to the primary and secondary cells; or The first carrier corresponds to the secondary cell.

13. The method of claim 11 or 12, wherein, The channels associated with BFR include at least one of the following: Physical Random Access Channel (PRACH) used for BFR; Scheduler request (SR) for BFR; The Physical Uplink Shared Channel (PUSCH) is used to carry the BFR Media Access Control (MAC) control element CE.

14. The method of claim 13, wherein, The PUSCH used to carry the BFR MAC CE includes at least one of the following: The first PUSCH is scheduled by downlink control information (DCI) on the recovery search space; The second PUSCH is scheduled by the downlink control information (DCI) after the terminal sends a scheduling request for BFR. The first configured authorized physical uplink shared channel CG-PUSCH is configured after the terminal sends a scheduling request for BFR; The second CG-PUSCH is activated after the terminal sends a scheduling request for BFR.

15. The method of claim 14, wherein, The method further includes: The scheduling request for BFR is transmitted via a second carrier, which may be the same as or different from the first carrier.

16. The method of claim 14 or 15, wherein, The method further includes: The DCI is received via a third carrier, which may be the same as or different from the first carrier.

17. The method of claim 11, wherein, The method further includes: After transmitting the channel related to beam failure recovery BFR via the first carrier, it is expected that the first time period will be terminated.

18. The method of claim 17, wherein, The expectation of terminating the first time period includes: The network device is expected to terminate the first time period after receiving the BFR-related channel via the first carrier for a first duration, wherein the first duration is equal to or greater than 0, and the BFR-related channel is at least one of the following: PRACH for BFR, or SR for BFR.

19. The method of claim 17, wherein, The expectation of terminating the first time period includes: The first time period is expected to terminate after a second duration following the network device receiving the BFR-related channel via the first carrier, wherein the second duration is greater than 0, and the BFR-related channel is at least one of the following: PUSCH or CG-PUSCH.

20. The method according to any one of claims 17 to 19, wherein, The method further includes: It is expected that when the network device terminates the first time period, it will start the second time period, which is the time period during which the network device receives the uplink channel while in cell DRX state.

21. A communication method for a communication system, the method comprising: The terminal detected a beam failure; During the first time period, the terminal transmits the channel related to beam failure recovery (BFR) via the first carrier. During the first time period, the network device receives channels related to beam failure recovery (BFR) via the first carrier. The first time period is the period during which the network device does not receive uplink channels when it is in the cell discontinuous reception (CDR) state.

22. A first communication device applied to a network equipment, the device comprising: The transceiver module is configured to receive channels related to beam failure recovery (BFR) via a first carrier during a first time period, wherein the first time period is the period during which the network device does not receive uplink channels when it is in cell DRX state.

23. A second communication device applied to a terminal, the device comprising: The processing module is configured to detect beam failure; The transceiver module is configured to transmit a channel related to beam failure recovery (BFR) via a first carrier during a first time period, wherein the first time period is the period during which the network device does not receive uplink channels when it is in the cell discontinuous reception (CDR) state.

24. A communication device, comprising a processor and a memory, wherein, One or more processors; The processor is used to invoke instructions to cause the communication device to execute the communication method according to any one of claims 1-10 and 11-20.

25. A communication system comprising a terminal and network equipment, wherein, The terminal is configured to implement the communication method of any one of claims 1-10, and the access network device is configured to implement the communication method of any one of claims 11-20.

26. A storage medium storing instructions, wherein, When the instructions are executed on the communication device, the communication device performs the method as described in any one of claims 1-10 and 11-20.

Images