Method and apparatus for generating and reporting beam failure information

Abstract

An embodiment of the present invention provides a method and device for generating and reporting beam failure information, which includes the steps of: a terminal device detecting that a beam failure occurs in a link between the terminal device and a transmission / reception point (TRP) or a beam failure recovery of the transmission / reception point is triggered; and generating a medium access control (MAC) control element (CE), which indicates information of the transmission / reception point where the beam failure is detected or the beam failure recovery is triggered.

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE The present invention relates to the field of communications technology. [Background technology]

[0002] In the New Radio (NR) system, beam transmission and reception are supported, and management of multiple beams is supported. The terminal device can perform a beam failure detection (BFD) procedure and a beam failure recovery (BFR) procedure. In the beam failure detection procedure, a MAC entity of a media access control (MAC) layer of the terminal device detects beam failure and / or triggers beam failure recovery by calculating the number indicated by the beam failure instance provided to the MAC entity by a lower layer (e.g., physical layer).

[0003] For example, the beam failure detection procedure uses a UE variable BFI_COUNTER, which is a counter indicated by the beam failure instance and is initially set to 0, with one BFI_COUNTER for each serving cell. For each serving cell for which beam failure detection is configured, the MAC entity performs the following operations:

[0004] When a beam failure instance indication is received from a lower layer, the beam failure detection timer beamFailureDetectionTimer is started or restarted. Also, the terminal device variable BFI_COUNTER is incremented by 1. If BFI_COUNTER is equal to or greater than the maximum beam failure instance count value beamFailureInstanceMaxCount, trigger one beam failure recovery (BFR) of the serving cell if the serving cell is a secondary cell (SCell), otherwise start a random access process in a special cell (SpCell). If the beamFailureDetectionTimer times out or if the upper layer has reconfigured the beamFailureDetectionTimer, beamFailureInstanceMaxCount or reference signal for beam failure detection of this serving cell, set BFI_COUNTER to 0.

[0005] For each serving cell, the Radio Resource Control (RRC) can be used to configure a beam failure recovery procedure for the MAC entity, which indicates a new SSB or CSI-RS to the serving network device (e.g., gNB) when a beam failure is detected in the serving synchronization signal block (SSB) / channel state information reference signal (CSI-RS).

[0006] When a MAC Protocol Data Unit (PDU) is transmitted by a terminal device to a network device, and this MAC PDU includes a BFR MAC Control Element (CE) or a truncated BFR MAC CE carrying beam failure information of a secondary cell, the terminal device needs to cancel all BFRs triggered by the secondary cell for beam failure recovery before the MAC PDU is assembled.

[0007] In the beam failure recovery procedure, the MAC entity performs the following operations:

[0008] If the beam failure recovery procedure determines that at least one BFR has been triggered, and the BFR has not been canceled, and, as requested, the evaluation of the candidate beams has been completed, when uplink resources (UL-SCH resources) are available for a new transmission and can accommodate a BFR MAC CE and its subheader as a result of a Logical Channel Prioritization procedure (LCP), a Multiplexing and Assembly procedure is instructed to generate a BFR MAC CE; If uplink resources are available for new transmission and can accommodate the Truncated BFR MAC CE and its subheader as a result of the LCP, instruct a multiplexing and assembly procedure to generate a Truncated BFR MAC CE; Otherwise, if a BFR has been triggered and the BFR has not been cancelled, and if requested, a Scheduling Request (SR) is triggered for a secondary cell for which evaluation of candidate beams for the BFR has been completed.

[0009] Therefore, the beam failure information of the secondary cell can be carried by the BFR MAC CE or the Truncated BFR MAC CE (hereinafter abbreviated as (Truncated) BFR MAC CE) and transmitted by the terminal device to the network device.

[0010] The above description of the background art is merely for the purpose of more clearly and completely explaining the configurations of the present invention and for the understanding of those skilled in the art, and should not be construed as meaning that these configurations are well known to those skilled in the art just because they are described in the background art of the present invention. Summary of the Invention [Problem to be solved by the invention]

[0011] However, the inventors of the present invention have discovered that in the operation of a multi-transmit / receive point (TRP: Transmit Receive Point), when the information provided by the terminal device to the network device includes whether a secondary cell transmits a beam failure, candidate beam information, etc., the network device cannot determine which TRP has experienced a beam failure based on this information, and takes measures similar to those for a cell beam failure, which may result in a waste of resources.

[0012] In view of at least one of the above problems, embodiments of the present invention provide a method and apparatus for generating and reporting beam obstruction information. [Means for solving the problem]

[0013] In one aspect of an embodiment of the present invention, a method for generating beam failure information is provided, the method including the steps of: a terminal device detecting that a beam failure has occurred in a link between a transmission / reception point (TRP) or that beam failure recovery of the transmission / reception point has been triggered; and a step of the terminal device generating a medium access control (MAC) control element (CE), the MAC CE indicating information of the transmission / reception point where beam failure has been detected or beam failure recovery has been triggered.

[0014] In another aspect of an embodiment of the present invention, a beam fault information generating device is provided, the device including: a detection unit that detects that a beam fault has occurred in a link between a transmission / reception point (TRP) or that a beam fault recovery of the transmission / reception point has been triggered; and a processing unit that generates a medium access control (MAC) control element (CE), the MAC CE indicating information of the transmission / reception point where a beam fault has been detected or where a beam fault recovery has been triggered.

[0015] Another aspect of an embodiment of the present invention provides a method for reporting beam failure information, the method including a step of a terminal device detecting that a beam failure has occurred in a link between a transmission / reception point or that beam failure recovery of the transmission / reception point has been triggered, and a step of instructing a network device, via another transmission / reception point of a cell to which the transmission / reception point belongs, that beam failure has been detected or beam failure recovery has been triggered.

[0016] Another aspect of an embodiment of the present invention provides a beam failure information reporting device, the device including a detection unit that detects that a beam failure has occurred in a link between a transmitting / receiving point or that beam failure recovery of the transmitting / receiving point has been triggered, and a transmission unit that instructs a network device that a beam failure has been detected or a beam failure recovery has been triggered via other transmitting / receiving points of a cell to which the transmitting / receiving point belongs.

[0017] Another aspect of an embodiment of the present invention provides a method for reporting beam failure information, the method including: a step of a terminal device detecting that a beam failure has occurred in a link between a transmission / reception point or that beam failure recovery of the transmission / reception point has been triggered; and a step of generating a MAC CE based on a carrier aggregation (CA) configuration and / or uplink resources, the MAC CE indicating information of the transmission / reception point where beam failure has been detected or beam failure recovery has been triggered, or instructing a network device of information that beam failure has been detected or beam failure recovery has been triggered via another transmission / reception point of a cell to which the transmission / reception point belongs.

[0018] In another aspect of an embodiment of the present invention, a beam failure information reporting device is provided, the device including: a detection unit that detects that a beam failure has occurred in a link between a transmission / reception point or that a beam failure recovery of the transmission / reception point has been triggered; and a transmission unit that generates a MAC CE based on a carrier aggregation (CA) configuration and / or uplink resources, the MAC CE indicating information of the transmission / reception point where a beam failure has been detected or where a beam failure recovery has been triggered, or instructing a network device of information that a beam failure has been detected or where a beam failure recovery has been triggered via another transmission / reception point of a cell to which the transmission / reception point belongs.

[0019] One of the advantageous effects of the embodiment of the present invention is as follows: The terminal device generates a MAC CE, and the MAC CE indicates the information of the TRP where the beam failure is detected or the beam failure recovery is triggered, or the terminal device indicates the information of the beam failure is detected or the beam failure recovery is triggered to the network device through another TRP of the cell to which the TRP where the beam failure is detected or the beam failure recovery is triggered belongs. In this way, the terminal device can explicitly or implicitly indicate the information of the TRP to the network device, and the network device can take measures for the beam failure at the TRP level, thereby avoiding the waste of resources.

[0020] As shown in the following description and drawings, certain embodiments of the present invention are disclosed in detail to show the manner in which the principles of the present invention can be employed. However, the scope of the embodiments of the present invention is not limited to these. The embodiments of the present invention include modifications, alterations and equivalents within the spirit and scope of the appended claims.

[0021] Features described and / or illustrated in one embodiment may be used in the same or similar manner in one or more other embodiments and may be combined with or substituted for features in the other embodiments.

[0022] It should be noted that in this text, the term "including / having" means the presence of a feature, element, step or component, and does not exclude the presence or addition of one or more other features, elements, steps or components. [Brief description of the drawings]

[0023] Elements and features depicted in one drawing and one embodiment of the present invention may be combined with elements and features shown in one or more drawings or embodiments, and in the drawings, like reference numerals may designate corresponding elements in multiple drawings and may designate corresponding elements used in more than one embodiment. [Figure 1] 1 is a schematic diagram of a communication system according to an embodiment of the present invention; [Diagram 2] 1 is a schematic diagram of an example of a first format BFR MAC CE or a Truncated BFR MAC CE. [Diagram 3] 1 is a schematic diagram of an example of a second format BFR MAC CE or a Truncated BFR MAC CE. [Figure 4] FIG. 2 is a schematic diagram of an example of a multi-TRP scenario according to an embodiment of the present invention. [Diagram 5] 1 is a schematic diagram of an example of a method for generating beam obstruction information according to an embodiment of the present invention. [Figure 6] FIG. 1 is a schematic diagram of an example of beam fault detection (BFD) or beam fault recovery (BFR) according to an embodiment of the present invention. [Figure 7] FIG. 2 is a schematic diagram of an example of a MAC CE according to an embodiment of the present invention. [Figure 8] FIG. 2 is a schematic diagram of another example of a MAC CE according to an embodiment of the present invention. [Figure 9] FIG. 2 is a schematic diagram of another example of a MAC CE according to an embodiment of the present invention. [Figure 10] FIG. 2 is a schematic diagram of another example of a MAC CE according to an embodiment of the present invention. [Figure 11] FIG. 1 is a schematic diagram of an example of a TRP-specific BFR MAC CE according to an embodiment of the present invention. [Figure 12]FIG. 13 is a schematic diagram of another example of a TRP-specific BFR MAC CE according to an embodiment of the present invention. [Figure 13] FIG. 13 is a schematic diagram of another example of a TRP-specific BFR MAC CE according to an embodiment of the present invention. [Figure 14] FIG. 13 is a schematic diagram of another example of a TRP-specific BFR MAC CE according to an embodiment of the present invention. [Figure 15] FIG. 13 is a schematic diagram of another example of a TRP-specific BFR MAC CE according to an embodiment of the present invention. [Figure 16] 1 is a schematic diagram of an example of a method for reporting beam failure information in an embodiment of the present invention. [Figure 17] FIG. 13 is a schematic diagram of another example of a TRP-specific BFR MAC CE according to an embodiment of the present invention. [Figure 18] FIG. 13 is a schematic diagram of another example of a TRP-specific BFR MAC CE according to an embodiment of the present invention. [Figure 19] FIG. 13 is a schematic diagram of another example of a TRP-specific BFR MAC CE according to an embodiment of the present invention. [Figure 20] FIG. 2 is a schematic diagram of an example of beam selection in accordance with an embodiment of the present invention. [Figure 21] 1 is a schematic diagram of an example of a beam obstruction information generating device according to an embodiment of the present invention; [Figure 22] 1 is a schematic diagram of an example of a beam failure information reporting device according to an embodiment of the present invention; [Figure 23] FIG. 2 is a schematic diagram of a network device according to an embodiment of the present invention. [Figure 24] FIG. 2 is a schematic diagram of a terminal device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0024] The above and other features of the present invention will become apparent from the following description. In the specification and drawings, specific embodiments of the present invention are disclosed in detail, and some of the embodiments in which the principles of the present invention can be adopted are shown. However, the present invention is not limited to the described embodiments. The present invention includes all modifications, variations, and equivalents within the scope of the appended claims. Each embodiment of the present invention will be described below with reference to the drawings. These embodiments are merely illustrative and do not limit the present invention.

[0025] In embodiments of the present invention, the terms "first", "second", etc. are used in the title to distinguish different elements, but do not represent the spatial arrangement or temporal order of these elements, and these elements are not limited to these terms. The term "and / or" includes any and all combinations of one or more of the terms listed in the associated list. The terms "including", "comprising", "having", etc. refer to the presence of listed features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.

[0026] In the embodiments of the present invention, the singular forms "a", "the", etc., include the plural forms and should be understood broadly as "one kind" or "a class", and are not limited to "one". In addition, the term "said" should be understood to include both the singular and the plural forms, unless the context clearly indicates otherwise. In addition, the term "described in" should be understood to mean "described at least in part", and the term "based on" should be understood to mean "based at least in part on", unless the context clearly indicates otherwise.

[0027] In an embodiment of the present invention, the term "communication network" or "wireless communication network" may refer to a network conforming to any communication standard, such as, for example, Long Term Evolution (LTE), Advanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0028] Additionally, communications between devices in a communication system may occur according to any stage of communication protocols, including, but not limited to, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and 5G, New Radio (NR), and / or other currently known or future developed communication protocols.

[0029] In the embodiment of the present invention, the term "network device" refers to a device in a communication system, for example, allowing a terminal device to access the communication system and providing a service to the terminal device. The network device may include, but is not limited to, a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobility management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), etc.

[0030] Among them, the base station may include, but is not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), and a 5G base station (gNB), etc., as well as a Remote Radio Head (RRH), a Remote Radio Unit (RRU), a relay or a low power node (e.g., femto, pico, etc.), an Integrated Access and Backhaul (IAB) node or an IAB-DU or an IAB-donor. In addition, the term "base station" may include some or all of the functions thereof, and each base station may provide communication coverage for a particular geographic area. The term "cell" may refer to a base station and / or its coverage area depending on the context in which the term is used. The terms "cell" and "base station" may be interchangeable unless confusion arises.

[0031] In the embodiment of the present invention, the term "User Equipment" (UE) or "Terminal Equipment" (TE) refers to an apparatus that accesses a communication network and receives a network service via, for example, a network device. The terminal apparatus may be fixed or mobile, and may be called a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), an IAB-MT, a station, etc.

[0032] Among them, the terminal device may include, but is not limited to, a mobile phone, a personal digital assistant (PDA), a wireless modulation / demodulation device, a wireless communication device, a handheld device, a machine-type communication device, a laptop computer, a cordless phone, a smartphone, a smart watch, a digital camera, and the like.

[0033] For example, in a scenario such as the Internet of Things (IoT), the user equipment may be a monitoring or measuring device or equipment, including, but not limited to, a Machine Type Communication (MTC) terminal, an in-vehicle communication terminal, a Device to Device (D2D) terminal, a Machine to Machine (M2M) terminal, etc.

[0034] Furthermore, the term "network side" or "network device side" refers to the side of a network, which may be a base station or may include one or more of the network devices mentioned above. The term "user side" or "terminal side" or "terminal device side" refers to the side of a user or terminal, which may be a UE or may include one or more of the terminal devices mentioned above. In this specification, unless otherwise specified, "device" may refer to a network device or may refer to a terminal device.

[0035] The following describes an embodiment scenario of the present invention with reference to an example, but the present invention is not limited thereto.

[0036] 1 is a schematic diagram of a communication system according to an embodiment of the present invention, and illustrates an example of a user device and a network device. As shown in FIG. 1, a communication system 100 may include a network device 101 and a terminal device 102. For convenience of explanation, FIG. 1 illustrates one terminal device and one network device as an example, but the embodiment of the present invention is not limited thereto.

[0037] In the embodiment of the present invention, existing services or services that can be implemented in the future can be performed between the network device 101 and the terminal device 102. For example, these services include, but are not limited to, enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC).

[0038] In the beam failure recovery procedure, beam failure information of a secondary cell is carried by a BFR MAC CE or a Truncated BFR MAC CE and transmitted by a terminal device to a network device.

[0039] Fig. 2 is a schematic diagram of an example of a BFR MAC CE or a truncated BFR MAC CE in a first format (referred to as format 1). Fig. 3 is a schematic diagram of an example of a BFR MAC CE or a truncated BFR MAC CE in a second format (referred to as format 2).

[0040] Specifically, for example, for a BFR MAC CE, the MAC entity uses Format 1 of Figure 2 if the highest serving cell index ServCellIndex of a secondary cell for which beam failure has been detected and evaluation of candidate beams has been completed as requested is less than 8, otherwise it uses Format 2 of Figure 3.

[0041] For a Truncated BFR MAC CE, the MAC entity shall use Format 1 of Figure 2 if the highest serving cell index ServCellIndex of a secondary cell for which beam failure has been detected and for which evaluation of candidate beams has been completed as requested is smaller than 8, or if a special cell has detected beam failure and this special cell is included in the Truncated BFR MAC CE and as a result of the LCP the UL-SCH resources cannot accommodate the Truncated BFR MAC CE of Format 2 of Figure 3 and its subheader, otherwise it shall use Format 2 of Figure 3.

[0042] For example, the fields for format 1 and format 2 are defined as follows:

[0043] For BFR MAC CE, the Ci field indicates beam failure detection for the secondary cell of ServCellIndex i, whether evaluation of candidate beams has been completed as requested, and the presence of one byte containing an AC field, which indicates whether a Candidate RS ID field is present in this byte, and the Candidate RS ID field is set to an index of an SSB or CSI-RS.

[0044] The Ci field set to 1 means that a beam obstruction has been detected in the secondary cell with ServCellIndex i, candidate beam evaluation has been completed as requested, and a byte containing an AC field is present. The Ci field set to 0 means that a beam obstruction has not been detected in the secondary cell with ServCellIndex i, a beam obstruction has been detected, candidate beam evaluation has not been completed as requested, and a byte containing an AC field is not present. If present, the bytes containing the AC field are present according to the ascending order of ServCellIndex.

[0045] For a Truncated BFR MAC CE, the Ci field indicates beam failure detection for the secondary cell with ServCellIndex i, whether evaluation of candidate beams has been completed as requested, and the presence of a byte containing an AC field, which indicates whether a Candidate RS ID field is present in this byte, and which is set to the index of an SSB or CSI-RS.

[0046] The Ci field set to 1 means that a beam failure has been detected in the secondary cell with ServCellIndex i, the evaluation of candidate beams has been completed as requested, and a byte containing an AC field may be present. The Ci field set to 0 means that a beam failure has not been detected in the secondary cell with ServCellIndex i, or a beam failure has been detected, the evaluation of candidate beams has not been completed as requested, and a byte containing an AC field does not exist. If present, the bytes containing the AC field appear according to the ascending order of ServCellIndex. The number of bytes containing the AC field may be 0 and does not exceed the size of the available grant.

[0047] The above is a brief description of the (Truncated) BFR MAC CE, and the following describes a scenario related to an embodiment of the present invention. In the embodiment of the present invention, a beam may be replaced by a reference signal (RS), for example, represented by SSB or CSI-RS.

[0048] 4 is a schematic diagram of an example of a multi-TRP scenario according to an embodiment of the present invention. A TRP may be part of a network device (e.g., gNB) that receives a signal from a terminal device, or may be part of a network device (gNB) that transmits a signal to a terminal device. A TRP may also represent a group of Downlink Control Information (DCI) or a group of reference signals, etc.

[0049] As shown in Fig. 4, in a multi-TRP operation scenario, a terminal device may have a panel-1 and a panel-2. The serving cell can schedule the terminal device from the two TRPs to provide better Physical Downlink Share Channel (PDSCH) coverage, reliability and / or data rate.

[0050] There are two different operation modes for multi-TRP operation: single DCI and multi-DCI. In these two modes, the control of uplink and downlink operation is done by the physical layer and the medium access control (MAC). In single DCI mode, the terminal device is scheduled by two TRPs over the same DCI. In multi-DCI mode, the terminal device is scheduled over a separate DCI for each TRP.

[0051] In multi-TRP operation, according to the Rel-15 / 16 beam failure detection and beam failure recovery mechanism, when the beam between a single TRP and the terminal device is blocked and the beam between other TRPs and the terminal device is working, the physical layer does not indicate a beam failure instance to the MAC layer and does not trigger the beam failure detection procedure of the MAC layer. To solve this problem, a TRP-specific BFRQ architecture based on the Rel-16 secondary cell beam failure recovery request BFRQ (Beam Failure Recovery reQuest) is introduced, which allows the terminal device to report beam failure information to the network device when the beam between any TRP and the terminal device is blocked.

[0052] However, based on the Rel-16 secondary cell beam failure recovery BFRQ, the information provided by the terminal device to the network device includes whether a beam failure occurs in the secondary cell and candidate beam information at the time of failure. Based on this information, the network device cannot determine which TRP has a beam failure, and takes the same measures as for cell beam failure, which may result in resource waste.

[0053] Regarding the above problems, the following further describes the embodiment of the present invention. The embodiment of the present invention is described from the MAC layer of the terminal device and implemented by the MAC entity. Here, the MAC entity includes a beam fault detection procedure, a beam fault recovery procedure, and a multiplexing and assembly entity (hereinafter also referred to as a multiplexing and assembly procedure), etc., and the lower layers of the embodiment of the present invention are, for example, a physical layer, an antenna unit, a measurement procedure, etc. For the specific concepts and definitions of each layer and each entity, reference may be made to the related art, and the description thereof will be omitted in the embodiment of the present invention.

[0054] In the embodiments of the present invention, cell-specific may be understood as cell level or all beams. TRP-specific may be understood as TRP level or some beams. Cell-specific MAC CE may be BFR MAC CE or truncated BFR MAC CE in Rel-16, etc. The term "beam failure detected" may be replaced with "beam failure recovery triggered" or "beam failure indication triggered".

[0055] <Example 1> An embodiment of the present invention provides a method for generating beam obstruction information, which is explained from the perspective of a terminal device.

[0056] 5 is a schematic diagram of an example of a method for generating beam obstruction information according to an embodiment of the present invention. As shown in FIG. 5, the method includes the following steps:

[0057] Step 501: A terminal device detects that a beam failure occurs in a link between the terminal device and a transmission / reception point (TRP) or that a beam failure recovery of the transmission / reception point is triggered.

[0058] Step 502: The terminal device generates a Medium Access Control (MAC) Control Element (CE), where the MAC CE indicates information of the transmission / reception point where a beam failure is detected or a beam failure recovery is triggered.

[0059] It should be noted that the above FIG. 5 only shows a schematic diagram of an embodiment of the present invention, but the present invention is not limited thereto. For example, the execution order between various steps may be appropriately adjusted, some other steps may be added, and some steps may be removed. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of the above FIG. 5.

[0060] 6 is a schematic diagram of an example of beam failure detection (BFD) or beam failure recovery (BFR) of an embodiment of the present invention. As shown in FIG. 6, a network device provides services to a terminal device via TRP-1 and TRP-2. Here, link-1 between TRP-1 and the terminal device works normally, but link-2 between TRP-2 and the terminal device is blocked.

[0061] In an embodiment of the present invention, the terminal device may generate information of a TRP (e.g., TRP-2) where a beam failure is detected or a beam failure recovery is triggered, and may report the information of the TRP-2 to a network device. In this way, the terminal device can explicitly indicate the information of the TRP to the network device, and the network device can take measures against beam failure at the TRP level, thereby avoiding resource waste.

[0062] In some aspects, the transmission / reception point information includes an index or identifier of the transmission / reception point at which a beam obstruction was detected or a beam obstruction recovery was triggered.

[0063] For example, the index or identifier of a transmission / reception point may include an index of a control resource pool corresponding to the transmission / reception point, an index or identifier of the transmission / reception point, an index of a beam failure detection reference signal set (BFD-RS set) corresponding to the transmission / reception point, etc., but the present invention is not limited to these.

[0064] In some aspects, the MAC CE may be a TRP-specific MAC CE, e.g., different from the Rel-16 BFR MAC CE or the Rel-16 Truncated BFR MAC CE, or may be a cell-specific MAC CE, e.g., reusing the Rel-16 BFR MAC CE or the Rel-16 Truncated BFR MAC CE. One or more bits (e.g., two bits) may be used in the MAC CE to indicate the information of the TRP.

[0065] In some aspects, one value of the bit in the MAC CE indicates that beam failure has been detected or beam failure recovery has been triggered for a transmission / reception point corresponding to a control resource pool with index 0, and another value of the bit indicates that beam failure has been detected or beam failure recovery has been triggered for a transmission / reception point corresponding to a control resource pool with index 1.

[0066] For example, 0 indicates that a beam failure has been detected or a beam failure recovery has been detected for a transmission / reception point corresponding to a control resource pool with index 0, and 1 indicates that a beam failure has been detected or a beam failure recovery has been triggered for a transmission / reception point corresponding to a control resource pool with index 1.

[0067] In some aspects, one value of the bit in the MAC CE indicates that a beam failure has been detected or a beam failure recovery has been triggered for a transmission / reception point whose index is 0, and another value of the bit indicates that a beam failure has been detected or a beam failure recovery has been triggered for a transmission / reception point whose index is 1.

[0068] For example, 0 indicates that a beam failure has been detected or a beam failure recovery has been triggered for the transmission / reception point with index 0, and 1 indicates that a beam failure has been detected or a beam failure recovery has been triggered for the transmission / reception point with index 1.

[0069] In some aspects, a value of one bit in the MAC CE indicates that beam failure has been detected or beam failure recovery has been triggered for a transmission / reception point corresponding to a beam failure detection reference signal set (BFD-RS set) with index 0, or indicates that beam failure has been detected or beam failure recovery has been triggered for all beams corresponding to a beam failure detection reference signal set (BFD-RS set) with index 0.

[0070] The other value of the one bit indicates that a beam failure has been detected or a beam failure recovery has been triggered for a transmitting / receiving point corresponding to a beam failure detection reference signal set (BFD-RS set) whose index is 1, or indicates that a beam failure has been detected or a beam failure recovery has been triggered for all beams corresponding to a beam failure detection reference signal set (BFD-RS set) whose index is 1.

[0071] For example, 0 indicates that a beam failure has been detected or a beam failure recovery has been triggered for a transmission / reception point corresponding to a beam failure detection reference signal set (BFD-RS set) with index 0, or indicates that a beam failure has been detected or a beam failure recovery has been triggered for all beams corresponding to a beam failure detection reference signal set (BFD-RS set) with index 0.

[0072] 1 indicates that a beam failure has been detected or a beam failure recovery has been triggered for the transmission / reception point corresponding to the beam failure detection reference signal set (BFD-RS set) whose index is 1, or indicates that a beam failure has been detected or a beam failure recovery has been triggered for all beams corresponding to the beam failure detection reference signal set (BFD-RS set) whose index is 1.

[0073] In some aspects, the MAC CE uses the same format as the Beam Failure Recovery (BFR) MAC CE or the truncated Beam Failure Recovery (truncated BFR) MAC CE. The R bit of the Beam Failure Recovery (BFR) MAC CE or the truncated Beam Failure Recovery (truncated BFR) MAC CE is used to carry / indicate / represent the index of the transmission / reception point where a beam failure was detected or where beam failure recovery was triggered.

[0074] For example, the format of the Rel-16 BFR MAC CE shown in FIG. 2 or FIG. 3 may be reused, and the R bit of the Rel-16 BFR MAC CE may be used to indicate the information of the TRP.

[0075] FIG. 7 is a schematic diagram of an example of a MAC CE according to an embodiment of the present invention. FIG. 8 is a schematic diagram of another example of a MAC CE according to an embodiment of the present invention. For example, unlike the Rel-16 BFR MAC CE, a P bit (i.e., an R bit in the Rel-16 BFR MAC CEs) may be used. The length of the bitmap (1 byte or 4 bytes) may be determined to be the same as that of the Rel-16 BFR MAC CE. The P bit is used to indicate the information of the TRP in which a 1-bit beam failure is detected or a beam failure recovery is triggered, and the R bit in the original Rel-16 BFR MAC CEs is not reserved.

[0076] For example, the fields of FIG. 7 or FIG. 8 may be defined as follows:

[0077] For BFR MAC CE, the Ci field indicates the presence of one byte containing TRP-specific beam failure detection for the secondary cell of ServCellIndex i, whether candidate beam evaluation has been completed as requested, and an AC field, which indicates whether a Candidate RS ID field is present in this byte, and the Candidate RS ID field is set to the index of an SSB or CSI-RS.

[0078] The Ci field set to 1 means that a TRP-specific beam obstruction has been detected in the secondary cell with ServCellIndex i, candidate beam evaluation has been completed upon request, and a byte containing an AC field is present. The Ci field set to 0 means that a TRP-specific beam obstruction has not been detected in the secondary cell with ServCellIndex i, beam obstruction has been detected, candidate beam evaluation has not been completed upon request, and a byte containing an AC field is not present. If present, the bytes containing the AC field are present according to the ascending order of ServCellIndex.

[0079] The P bit is used to indicate the information of the TRP in which a 1-bit beam failure is detected or a beam failure recovery is triggered.

[0080] For a Truncated BFR MAC CE, the Ci field indicates the TRP-specific beam failure detection of the secondary cell with ServCellIndex i, whether the candidate beam evaluation has been completed as requested, and the presence of a byte containing an AC field, which indicates whether a Candidate RS ID field is present in this byte, and which is set to the index of an SSB or CSI-RS.

[0081] The Ci field set to 1 means that a TRP-specific beam obstruction has been detected in the secondary cell of ServCellIndex i, candidate beam evaluation has been completed as requested, and bytes containing AC fields may be present. The Ci field set to 0 means that a TRP-specific beam obstruction has not been detected in the secondary cell of ServCellIndex i, or a TRP-specific beam obstruction has been detected and candidate beam evaluation has not been completed as requested, and bytes containing AC fields do not exist. If present, the bytes containing AC fields appear according to the ascending order of ServCellIndex. The number of bytes containing AC fields may be 0 and does not exceed the size of the available grant.

[0082] The P bit is used to indicate the information of the TRP in which a 1-bit beam failure is detected or a beam failure recovery is triggered.

[0083] In some aspects, a value of one of the two bits in the MAC CE indicates one or any combination of the following: no transmission / reception point has been detected as a beam failure or a beam failure recovery has been triggered; a transmission / reception point corresponding to a control resource pool with index 0 has been detected as a beam failure or a beam failure recovery has been triggered; a transmission / reception point corresponding to a control resource pool with index 1 has been detected as a beam failure or a beam failure recovery has been triggered; and a transmission / reception point corresponding to a control resource pool with index 0 and a control resource pool with index 1 have been detected as a beam failure or a beam failure recovery has been triggered.

[0084] For example, 00 indicates that beam failure has been detected or beam failure recovery has been triggered at no transmission / reception point, 01 indicates that beam failure has been detected or beam failure recovery has been triggered for a transmission / reception point corresponding to a control resource pool with index 0, 10 indicates that beam failure has been detected or beam failure recovery has been triggered for a transmission / reception point corresponding to a control resource pool with index 1, and 11 indicates that beam failure has been detected or beam failure recovery has been triggered for both the transmission / reception point corresponding to the control resource pool with index 0 and the transmission / reception point corresponding to the control resource pool with index 1.

[0085] In some aspects, the value of one of the two bits in the MAC CE indicates one or any combination of the following: no transmission / reception point has detected beam failure or triggered beam failure recovery; a transmission / reception point with index 0 has detected beam failure or triggered beam failure recovery; a transmission / reception point with index 1 has detected beam failure or triggered beam failure recovery; and both a transmission / reception point with index 0 and a transmission / reception point with index 1 have detected beam failure or triggered beam failure recovery.

[0086] For example, 00 indicates that no beam failure has been detected or no beam failure recovery has been triggered at any transmission / reception point, 01 indicates that a beam failure has been detected or a beam failure recovery has been triggered for a transmission / reception point with index 0, 10 indicates that a beam failure has been detected or a beam failure recovery has been triggered for a transmission / reception point with index 1, and 11 indicates that a beam failure has been detected or a beam failure recovery has been triggered for both a transmission / reception point with index 0 and a transmission / reception point with index 1.

[0087] In some aspects, the value of one of the two bits in the MAC CE may indicate: no transmission / reception point has detected a beam failure or triggered a beam failure recovery; a beam failure has been detected or triggered for a transmission / reception point corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 0; a beam failure has been detected or triggered for all beams corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 0; a beam failure has been detected or triggered for a transmission / reception point corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 1; a beam failure has been detected or triggered for all beams corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 1; a beam failure has been detected or triggered for both a transmission / reception point corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 0 and a transmission / reception point corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 1; set) and all beams corresponding to a beam failure detection reference signal set (BFD-RS set) with index 1, indicates one or any combination of that a beam failure has been detected or a beam failure recovery has been triggered.

[0088] For example, 00 indicates that no transmission / reception points have detected beam obstruction or triggered beam obstruction recovery.

[0089] 01 indicates that a beam failure has been detected or a beam failure recovery has been triggered for the transmission / reception point corresponding to the beam failure detection reference signal set (BFD-RS set) with index 0, or that a beam failure has been detected or a beam failure recovery has been triggered for all beams corresponding to the beam failure detection reference signal set (BFD-RS set) with index 0.

[0090] 10 indicates that a beam failure has been detected or a beam failure recovery has been triggered for a transmission / reception point corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 1, or that a beam failure has been detected or a beam failure recovery has been triggered for all beams corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 1.

[0091] 11 indicates that beam failure has been detected, or beam failure recovery has been triggered, for both the transmitting and receiving points corresponding to the beam failure detection reference signal set (BFD-RS set) with index 0 and the transmitting and receiving points corresponding to the beam failure detection reference signal set (BFD-RS set) with index 1, or that beam failure has been detected, or beam failure recovery has been triggered, for all beams corresponding to the beam failure detection reference signal set (BFD-RS set) with index 0 and all beams corresponding to the beam failure detection reference signal set (BFD-RS set) with index 1.

[0092] In some aspects, the MAC CE uses the same format as the Beam Failure Recovery (BFR) MAC CE or the truncated Beam Failure Recovery (truncated BFR) MAC CE. The R bit and AC field of the Beam Failure Recovery (BFR) MAC CE or the truncated Beam Failure Recovery (truncated BFR) MAC CE are used to convey / indicate / represent the index of the transmission / reception point where a beam failure was detected or where beam failure recovery was triggered.

[0093] For example, the format of the Rel-16 BFR MAC CE shown in FIG. 2 or FIG. 3 may be reused, and the R bit and AC field of the Rel-16 BFR MAC CE may be used to indicate the information of the TRP.

[0094] FIG. 9 is a schematic diagram of another example of a MAC CE according to an embodiment of the present invention. FIG. 10 is a schematic diagram of another example of a MAC CE according to an embodiment of the present invention. For example, unlike the Rel-16 BFR MAC CE, the P bit (i.e., the AC field+R bit in the Rel-16 BFR MAC CEs) may be used. The length of the bitmap (1 byte or 4 bytes) may be determined to be the same as that of the Rel-16 BFR MAC CE. The P bit is used to indicate the information of the TRP in which 2 bits of beam failure are detected or beam failure recovery is triggered, and the R bit in the original Rel-16 BFR MAC CEs is not reserved. In this case, in order to distinguish the R bit from the candidate RS ID, the candidate RS ID needs to start from 1 and does not include a value that is all 0.

[0095] For example, the fields of FIG. 9 or FIG. 10 may be defined as follows:

[0096] For BFR MAC CE, the Ci field indicates the presence of one byte containing TRP-specific beam failure detection for the secondary cell of ServCellIndex i, whether candidate beam evaluation has been completed as requested, and a P field, which indicates whether a Candidate RS ID field is present in this byte, and the Candidate RS ID field is set to the index of an SSB or CSI-RS.

[0097] The Ci field set to 1 means that a TRP-specific beam obstruction has been detected in the secondary cell with ServCellIndex i, candidate beam evaluation has been completed upon request, and a byte containing a P field is present. The Ci field set to 0 means that a TRP-specific beam obstruction has not been detected in the secondary cell with ServCellIndex i, beam obstruction has been detected, candidate beam evaluation has not been completed upon request, and a byte containing a P field is not present. If present, the bytes containing the P field are present according to the ascending order of ServCellIndex.

[0098] The P bit is used to indicate the information of the TRP where a beam failure is detected or where a beam failure recovery is triggered, which is 2 bits.

[0099] For a Truncated BFR MAC CE, the Ci field indicates the TRP-specific beam failure detection of the secondary cell with ServCellIndex i, whether the candidate beam evaluation has been completed as requested, and the presence of a byte containing a P field, which indicates whether a Candidate RS ID field is present in this byte, and the Candidate RS ID field is set to the index of an SSB or CSI-RS.

[0100] The Ci field set to 1 means that a TRP-specific beam obstruction has been detected in the secondary cell of ServCellIndex i, candidate beam evaluation has been completed as requested, and a byte containing a P field may be present. The Ci field set to 0 means that a TRP-specific beam obstruction has not been detected in the secondary cell of ServCellIndex i, or a TRP-specific beam obstruction has been detected and candidate beam evaluation has not been completed as requested, and a byte containing a P field does not exist. If present, the bytes containing the P field appear according to the ascending order of ServCellIndex. The number of bytes containing the P field may be 0 and does not exceed the size of the available grant.

[0101] The P bit is used to indicate the information of the TRP where a beam failure is detected or where a beam failure recovery is triggered, which is 2 bits.

[0102] In some aspects, the MAC CE may further include a type of detected beam failure or a type of triggered beam failure recovery. For example, the MAC CE may be a TRP-specific MAC CE or may reuse a cell-specific MAC CE, and may use one or more bits (e.g., two bits) in the MAC CE to indicate the type of BFD or BFR.

[0103] In some aspects, one value of the bit in the MAC CE indicates that beam failure of a cell-specific or all beams has been detected or beam failure recovery of a cell-specific or all beams has been triggered, and another value of the bit indicates that beam failure of a transmission / reception point (TRP)-specific or some beams has been detected or beam failure recovery of a TRP-specific or some beams has been triggered.

[0104] For example, 0 indicates that beam failure of a cell-specific or all beams has been detected, or beam failure recovery of a cell-specific or all beams has been triggered, and 1 indicates that beam failure of a transmission / reception point (TRP)-specific or some beams has been detected, or beam failure recovery of a TRP-specific or some beams has been triggered.

[0105] In some aspects, one value of the bit in the MAC CE indicates that beam failure of a cell-specific or all beams has been detected or beam failure recovery of a cell-specific or all beams has been triggered, and another value of the bit indicates that beam failure of a non-cell specific or non-all beams has been detected or beam failure recovery of a non-cell specific or non-all beams has been triggered.

[0106] For example, 0 indicates that beam failure of a cell-specific or all beams has been detected or beam failure recovery of a cell-specific or all beams has been triggered, and 1 indicates that beam failure of a non-cell-specific or non-all beams has been detected or beam failure recovery of a non-cell-specific or non-all beams has been triggered.

[0107] In some aspects, one value of the bit in the MAC CE indicates that a beam failure of a TRP-specific or some beam has been detected or a beam failure recovery of a TRP-specific or some beam has been triggered, and another value of the bit indicates that a beam failure of a non-TRP-specific or some beam has been detected or a beam failure recovery of a non-TRP-specific or some beam has been triggered.

[0108] For example, 0 indicates that a beam failure of a TRP-specific or some beams has been detected, or a beam failure recovery of a TRP-specific or some beams has been triggered, and 1 indicates that a beam failure of a non-TRP-specific or some beams has been detected, or a beam failure recovery of a non-TRP-specific or some beams has been triggered.

[0109] In some aspects, the R bit in the beam failure recovery MAC CE or truncated beam failure recovery (truncated BFR) MAC CE is used to convey / indicate / represent the type of beam failure detected or the type of beam failure recovery triggered.

[0110] For example, the format of the Rel-16 BFR MAC CE shown in FIG. 2 or FIG. 3 may be reused, and the R bit of the Rel-16 BFR MAC CE may be used to indicate the type of BFD or BFR.

[0111] In some aspects, one value of the two bits in the MAC CE indicates that beam failure of a cell-specific or all beams has not been detected, or beam failure recovery of a cell-specific or all beams has not been triggered, and beam failure of a TRP-specific or some beams has not been detected, or beam failure recovery of a TRP-specific or some beams has not been triggered; another value of the two bits indicates that beam failure of a cell-specific or all beams has been detected, or beam failure recovery of a cell-specific or all beams has been triggered; another value of the two bits indicates that beam failure of a TRP point-specific or some beams has been detected, or beam failure recovery of a TRP-specific or some beams has been triggered; and another value of the two bits indicates that beam failure of a cell-specific or all beams has been detected, or beam failure recovery of a cell-specific or all beams has been triggered, and beam failure of a TRP-specific or some beams has been detected, or beam failure recovery of a TRP-specific or some beams has been triggered.

[0112] For example, 00 indicates that no beam failure of a cell-specific or all beams is detected, or beam failure recovery of a cell-specific or all beams is not triggered, and no beam failure of a TRP-specific or some beams is detected, or beam failure recovery of a TRP-specific or some beams is not triggered. 01 indicates that beam failure of a cell-specific or all beams is detected, or beam failure recovery of a cell-specific or all beams is triggered. 10 indicates that beam failure of a TRP point-specific or some beams is detected, or beam failure recovery of a TRP-specific or some beams is triggered. 11 indicates that beam failure of a cell-specific or all beams is detected, or beam failure recovery of a cell-specific or all beams is triggered, and beam failure of a TRP-specific or some beams is detected, or beam failure recovery of a TRP-specific or some beams is triggered.

[0113] In some aspects, one value of the two bits in the MAC CE indicates that beam failure of a cell-specific or all beams has not been detected, or beam failure recovery of a cell-specific or all beams has not been triggered, and beam failure of a non-cell-specific or non-all beams has not been detected, or beam failure recovery of a non-cell-specific or non-all beams has not been triggered; another value of the two bits indicates that beam failure of a cell-specific or all beams has been detected, or beam failure recovery of a cell-specific or non-all beams has been triggered; and another value of the two bits indicates that beam failure of a cell-specific or all beams has been detected, or beam failure recovery of a cell-specific or non-all beams has been triggered, and beam failure of a non-cell-specific or non-all beams has been detected, or beam failure recovery of a non-cell-specific or non-all beams has been triggered.

[0114] For example, 00 indicates that no beam failure of cell-specific or all beams is detected, or beam failure recovery of cell-specific or all beams is not triggered, and no beam failure of non-cell-specific or all beams is detected, or beam failure recovery of non-cell-specific or all beams is not triggered. 01 indicates that beam failure of cell-specific or all beams is detected, or beam failure recovery of cell-specific or all beams is triggered. 10 indicates that beam failure of non-cell-specific or all beams is detected, or beam failure recovery of non-cell-specific or all beams is triggered. 11 indicates that beam failure of cell-specific or all beams is detected, or beam failure recovery of cell-specific or all beams is triggered, and beam failure of non-cell-specific or all beams is detected, or beam failure recovery of non-cell-specific or all beams is triggered.

[0115] In some aspects, one value of the two bits in the MAC CE indicates that beam failure of a non-TRP-specific or non-some beam has not been detected, or beam failure recovery of a non-TRP-specific or non-some beam has not been triggered, and beam failure of a TRP-specific or non-some beam has not been detected, or beam failure recovery of a TRP-specific or non-some beam has not been triggered; another value of the two bits indicates that beam failure of a non-TRP-specific or non-some beam has been detected, or beam failure recovery of a non-TRP-specific or non-some beam has been triggered; another value of the two bits indicates that beam failure of a non-TRP-specific or non-some beam has been detected, or beam failure recovery of a TRP-specific or non-some beam has been triggered; and another value of the two bits indicates that beam failure of a non-TRP-specific or non-some beam has been detected, or beam failure recovery of a non-TRP-specific or non-some beam has been triggered, and beam failure of a TRP-specific or non-some beam has been detected, or beam failure recovery of a TRP-specific or non-some beam has been triggered.

[0116] For example, 00 indicates that no beam failure of non-TRP-specific or non-partial beams is detected, or beam failure recovery of non-TRP-specific or non-partial beams is not triggered, and no beam failure of TRP-specific or non-partial beams is detected, or beam failure recovery of TRP-specific or non-partial beams is not triggered. 01 indicates that a beam failure of non-TRP-specific or non-partial beams is detected, or beam failure recovery of non-TRP-specific or non-partial beams is triggered. 10 indicates that a beam failure of TRP-specific or non-partial beams is detected, or beam failure recovery of TRP-specific or non-partial beams is triggered. 11 indicates that a beam failure of non-TRP-specific or non-partial beams is detected, or beam failure recovery of non-TRP-specific or non-partial beams is triggered, and beam failure of TRP-specific or non-partial beams is detected, or beam failure recovery of TRP-specific or non-partial beams is triggered.

[0117] In some aspects, the R bit and AC field in the beam failure recovery MAC CE or truncated beam failure recovery (truncated BFR) MAC CE are used to convey / indicate / represent the type of beam failure detected or the type of beam failure recovery triggered.

[0118] For example, the format of the Rel-16 BFR MAC CE shown in FIG. 2 or FIG. 3 may be reused, and the R bit and AC field of the Rel-16 BFR MAC CE may be used to indicate the type of BFD or BFR.

[0119] In some aspects, the MAC CE may further include at least one or any combination of information of a cell to which a transmission / reception point belongs where a beam failure has been detected or where beam failure recovery has been triggered (e.g., CA is configured), information on whether a candidate beam has been found (e.g., a candidate reference signal list is configured), and information on a candidate beam (e.g., a candidate beam list is configured and a candidate beam has been found).

[0120] The above describes the contents of the MAC CE as an example. The following describes the transmission of the MAC CE as an example.

[0121] As shown in FIG. 5, the method may further include the following steps.

[0122] Step 503: The terminal device sends a MAC CE to the network device.

[0123] In some aspects, the MAC CE is forwarded to the network device via another transmission / reception point of the cell to which the transmission / reception point belongs.

[0124] In some aspects, the MAC CE is forwarded to the network device via a transceiver point that is co-located with the transceiver point and that belongs to a cell different from the cell that the transceiver point belongs to, for example, in this case where the terminal device is configured for carrier aggregation (CA).

[0125] In some aspects, the MAC CE is reported to the network device via a cell different from the cell to which the transmission / reception point belongs, for example, in this case where the terminal device is configured for carrier aggregation (CA).

[0126] In some aspects, the MAC CE is identified by a Logical Channel Identifier (LCID) or an Extended Logical Channel Identifier (eLCID) MAC subheader, e.g., the MAC CE may use the same LCID / eLCID as the Rel-16 BFR MAC CEs or a different LCID / eLCID than the Rel-16 BFR MAC CEs.

[0127] In some aspects, the terminal device transmits the MAC CE using one of the uplink grants (UL grants): an uplink grant of a TRP in which a TRP-specific beam failure is not detected and of a cell to which the TRP in which a TRP-specific beam failure is detected belongs, an uplink grant of a TRP in which a TRP-specific beam failure is detected and which belongs to a cell other than the cell to which the transmission / reception point in which the TRP-specific beam failure is detected belongs, and an uplink grant of a cell other than the cell to which the TRP in which the TRP-specific beam failure is detected belongs.

[0128] In some aspects, when there are multiple available resources, the terminal device may select an uplink grant based on a predefined or network configuration and transmit the MAC CE, or may select an uplink grant based on implementation and transmit the MAC CE, or may randomly select an uplink grant and transmit the MAC CE.

[0129] For example, the available resources may be UL-SCH resources available for a new transmission, or the available resources may be UL-SCH resources that are available for a new transmission and can accommodate this MAC CE and its subheader as a result of the LCP. The uplink grant is used to indicate the UL-SCH resources in the available resources.

[0130] The above briefly describes transmitting MAC CE by reusing Rel-16 BFR MAC CE and Rel-16 Truncated BFR MAC CE (hereinafter, for convenience of explanation, also referred to as cell-level BFR MAC CE), and the following further describes the generation of TRP-specific MAC CE.

[0131] In some aspects, a medium access control (MAC) entity of the terminal device instructs the multiplexing and reassembly procedure to generate a TRP-specific MAC CE, which is different from a cell-specific MAC CE, e.g., the TRP-specific CE is different from a Rel-16 BFR MAC CE or a Rel-16 Truncated BFR MAC CE.

[0132] The cell-specific MAC CE may include a cell-specific BFR MAC CE (Rel-16 BFR MAC CE) and a cell-specific Truncated BFR MAC CE (Rel-16 Truncated BFR MAC CE).

[0133] The TRP-specific MAC CE (TRP-specific BFR MAC CE) may include a TRP-specific / TRP-level BFR MAC CE (Rel-17 BFR MAC CE), a TRP-specific / TRP-level BF MAC CE (Rel-17 BF MAC CE), a TRP-specific / TRP-level Truncated BFR MAC CE (TRP-specific / -level Truncated BFR MAC CE, Rel-17 Truncated BFR MAC CE), and a TRP-specific / TRP-level Truncated BF MAC CE (TRP-specific / -level Truncated BF MAC CE, Rel-17 Truncated BF MAC CE).

[0134] The following describes the TRP-specific MAC CE by taking the TRP-specific BFR MAC CE as an example.

[0135] Fig. 11 is a schematic diagram of an example of a TRP-specific BFR MAC CE according to an embodiment of the present invention, Fig. 12 is a schematic diagram of another example of a TRP-specific BFR MAC CE according to an embodiment of the present invention, and Fig. 13 is a schematic diagram of another example of a TRP-specific BFR MAC CE according to an embodiment of the present invention. The determination of the length of the bitmap (1 byte or 4 bytes) is the same as that of the Rel-16 BFR MAC CE.

[0136] P i The bits are used to indicate whether a TRP-specific beam obstruction is detected in the cell with cell index (e.g., ServCellIndex) i and whether an extra byte is present. For example, 1 indicates that an extra byte is detected and present, and 0 indicates that an extra byte is not detected and not present. N indicates the number of bytes corresponding to the TRP-specific beam obstruction in the corresponding cell. For example, 0 represents 1 byte and 1 represents 2 bytes.

[0137] If the number of bytes corresponding to TRP-specific beam failure is 2, the AC field is used to indicate whether the lower 6 bits in the byte are candidate RS IDs or R bits. If the number of bytes corresponding to TRP-specific beam failure is 1, the AC field is used to indicate whether the lower 6 bits in the byte are candidate RS IDs or one P bit (TRP information indicating that a TRP-specific beam failure has been detected, one bit of TRP information) and five R bits.

[0138] FIG 14 is a schematic diagram of another example of a TRP-specific BFR MAC CE according to an embodiment of the present invention, and FIG 15 is a schematic diagram of another example of a TRP-specific BFR MAC CE according to an embodiment of the present invention. The determination of the length of the bitmap (2 bytes or 8 bytes) is the same as that of the Rel-16 BFR MAC CE.

[0139] Here, C i The bit is used to indicate TRP information (2 bits of TRP information) in a cell whose cell index (eg, ServCellIndex) is i.

[0140] The above is a schematic description of the TRP-specific BFR MAC CE of the embodiment of the present invention, but the present invention is not limited thereto, and may refer to embodiment 2. For example, the TRP-specific BFR MAC CE may be combined with the structure shown in Figs. 17 to 19 described later.

[0141] In some aspects, a TRP-specific MAC CE may be generated using a procedure independent of the cell-specific MAC CE procedure, where the TRP-specific MAC CE may include a TRP-specific / TRP-level BFR MAC CE (Rel-17 BFR MAC CE), a TRP-specific / TRP-level BF MAC CE (Rel-17 BF MAC CE), a TRP-specific / TRP-level Truncated BFR MAC CE (Rel-17 Truncated BFR MAC CE), and a TRP-specific / TRP-level Truncated BF MAC CE (Rel-17 Truncated BF MAC CE). One or any combination of the above types of MAC CE may be generated independently.

[0142] For example, for one TRP, if at least one beam failure is detected (or at least one beam failure recovery is triggered) and not canceled in the beam failure detection procedure / beam failure recovery procedure, a TRP-specific MAC CE is generated using a procedure independent of the cell-specific beam failure recovery MAC CE procedure.

[0143] Also, for example, in a beam failure detection procedure / beam failure recovery procedure, if at least one TRP-specific beam failure is detected (or at least one TRP-specific beam failure recovery is triggered) and not canceled, a TRP-specific MAC CE is generated using a procedure independent of the cell-specific beam failure recovery MAC CE process.

[0144] For example, a shortened TRP-specific beam failure recovery MAC CE is supported. The procedure of generating the TRP-specific beam failure recovery MAC CE includes: if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the shortened TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly entity to generate the shortened TRP-specific beam failure recovery MAC CE; otherwise, triggering a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which a BFR is triggered and not cancelled.

[0145] Also, for example, a shortened TRP-specific beam failure recovery MAC CE is not supported. The procedure for generating the TRP-specific beam failure recovery MAC CE includes the MAC entity instructing the multiplexing and reassembly entity to generate the TRP-specific beam failure recovery MAC CE if uplink resources are available for a new transmission and can accommodate the TRP-specific beam failure recovery MAC CE and its subheader as a result of the LCP, otherwise triggering a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which a BFR is triggered and not canceled.

[0146] In some aspects, one procedure may be used to generate a cell-specific MAC CE and a TRP-specific MAC CE, where the cell-specific MAC CE may include a cell-specific BFR MAC CE (Rel-16 BFR MAC CE) and a cell-specific Truncated BFR MAC CE (Rel-16 Truncated BFR MAC CE).

[0147] The TRP-specific MAC CE may include a TRP-specific / TRP-level BFR MAC CE (Rel-17 BFR MAC CE), a TRP-specific / TRP-level BF MAC CE (Rel-17 BF MAC CE), a TRP-specific / TRP-level Truncated BFR MAC CE (TRP-specific / -level Truncated BFR MAC CE, Rel-17 Truncated BFR MAC CE), and a TRP-specific / TRP-level Truncated BF MAC CE (TRP-specific / -level Truncated BF MAC CE, Rel-17 Truncated BF MAC CE).

[0148] The procedure may be used to generate any or any combination of the above types of MAC CE.

[0149] For example, for one TRP, if at least one beam failure is detected (or at least one beam failure recovery is triggered) and not canceled in the beam failure detection procedure / beam failure recovery procedure, and it is determined in the beam failure recovery process that the BFR of at least one secondary cell is triggered and not canceled, a cell-specific MAC CE and a TRP-specific MAC CE are generated using one procedure.

[0150] Also, for example, in a beam failure detection procedure / beam failure recovery procedure, if at least one TRP-specific beam failure is detected (or at least one TRP-specific beam failure recovery is triggered) and has not been canceled, and in the beam failure recovery process, it is determined that a BFR of at least one secondary cell has been triggered and has not been canceled, a cell-specific MAC CE and a TRP-specific MAC CE are generated using one procedure.

[0151] Furthermore, when the MAC entity instructs to generate one MAC CE, it may further instruct to generate another MAC CE. The MAC PDU may include multiple MAC CEs indicating beam failure information, such as a cell-specific BFR MAC CE (Rel-16 BFR MAC CE) and a TRP-specific BFR MAC CE (TRP-specific BFR MAC CE).

[0152] In some aspects, a shortened TRP-specific beam failure recovery MAC CE is supported. The shortened TRP-specific beam failure recovery MAC CE is preferentially generated.

[0153] For example, the TRP-specific BFR MAC CE and the cell-specific BFR MAC CE may be generated sequentially.

[0154] If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the shortened TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened TRP-specific beam failure recovery MAC CE; otherwise, for each TRP for which a BFR is triggered and which has not been cancelled, a scheduling request (SR) for TRP-specific beam failure recovery is triggered; if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, for each TRP for which a BFR is triggered and which has not been cancelled, a scheduling request (SR) for TRP-specific beam failure recovery is triggered; otherwise, when uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam failure recovery MAC CE, otherwise it triggers a scheduling request (SR) for cell-specific beam failure recovery for each cell for which a BFR has been triggered and has not been cancelled.

[0155] In this example, two MAC CEs may be generated, namely, a TRP-specific BFR MAC CE (or a TRP-specific Truncated BFR MAC CE) and a cell-specific BFR MAC CE (or a cell-specific Truncated BFR MAC CE), and the two MAC CEs may be included in one MAC PDU.

[0156] Also, for example, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate a shortened TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened TRP-specific beam failure recovery MAC CE; otherwise, a BFR is triggered and for each TRP that has not been canceled, a scheduling request (SR) for TRP-specific beam failure recovery is triggered; if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources cannot accommodate the TRP-specific beam failure recovery MAC CE and its subheader and cannot accommodate the shortened TRP-specific beam failure recovery MAC CE and its subheader, the uplink resources instructs the multiplexing and reassembly entity to generate a shortened TRP-specific beam failure recovery MAC CE; otherwise, a BFR is triggered and for each TRP that has not been canceled, a scheduling request (SR) for TRP-specific beam failure recovery is triggered; When the CE and its subheader can be accommodated, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, when uplink resources are available for a new transmission and the uplink resources can accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader as a result of the LCP, the MAC entity instructs the multiplexing and assembly entity to generate a shortened cell-specific beam failure recovery MAC CE; otherwise, it triggers a scheduling request (SR) for cell-specific beam failure recovery for each cell for which a BFR has been triggered and has not been cancelled.

[0157] In this example, one MAC CE may be generated, i.e., a TRP-specific BFR MAC CE (or a TRP-specific Truncated BFR MAC CE) or a cell-specific BFR MAC CE (or a cell-specific Truncated BFR MAC CE), of which the MAC PDU includes one MAC CE.

[0158] As another example, the TRP-specific BFR MAC CE and the cell-specific BFR MAC CE may be generated in an alternating manner.

[0159] If uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources are capable of accommodating the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources are capable of accommodating the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources are not capable of accommodating the TRP-specific beam failure recovery MAC CE and its subheader (or the MAC entity has not instructed the multiplexing and assembly procedure to generate the TRP-specific beam failure recovery MAC CE), and (a) a shortened TRP-specific beam failure recovery MAC If the MAC entity is able to accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened TRP-specific beam failure recovery MAC CE; otherwise, if there are no uplink resources available for the new transmission or if uplink resources are available for the new transmission and the TRP-specific beam failure recovery MAC CE and its subheader cannot be accommodated as a result of the LCP (or the MAC entity has not instructed the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE) and the shortened TRP-specific beam failure recovery MAC CE and its subheader cannot be accommodated (or the MAC entity has not instructed the multiplexing and reassembly procedure to generate the shortened TRP-specific beam failure recovery MAC CE), the BFR is triggered and for each TRP that has not been canceled, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for the new transmission and the uplink resources are shortened as a result of the LCP, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened TRP-specific beam failure recovery MAC CE;If the CE and its subheader can be accommodated, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam failure recovery MAC CE, otherwise it triggers a scheduling request (SR) for cell-specific beam failure recovery for each cell for which a BFR has been triggered and not cancelled.

[0160] In this example, two MAC CEs may be generated, namely, a TRP-specific BFR MAC CE (or a cell-specific BFR MAC CE) and a TRP-specific Truncated BFR MAC CE (or a cell-specific Truncated BFR MAC CE), and the two MAC CEs may be included in one MAC PDU.

[0161] Also, for example, if uplink resources are available for a new transmission and, as a result of LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; if uplink resources are available for a new transmission and, as a result of LCP, the uplink resources cannot accommodate the TRP-specific beam failure recovery MAC CE and its subheader, and cannot accommodate the cell-specific beam failure recovery MAC CE and its subheader, when the uplink resources can accommodate a shortened TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate the shortened TRP-specific beam failure recovery MAC CE and its subheader. otherwise, if uplink resources are available for new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly entity to generate a shortened cell-specific beam failure recovery MAC CE, otherwise, triggers a scheduling request (SR) for cell-specific beam failure recovery for each cell for which BFR is triggered and not canceled.

[0162] In this example, one MAC CE may be generated, i.e., a TRP-specific BFR MAC CE (or a cell-specific BFR MAC CE) or a TRP-specific Truncated BFR MAC CE (or a cell-specific Truncated BFR MAC CE). One MAC PDU includes one MAC CE.

[0163] In some aspects, a shortened TRP-specific beam failure recovery MAC CE is supported. The cell-specific beam failure recovery MAC CE is generated preferentially.

[0164] For example, the cell-specific BFR MAC CE and the TRP-specific BFR MAC CE may be generated sequentially.

[0165] If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly entity to generate a shortened cell-specific beam failure recovery MAC CE; otherwise, for each cell for which a BFR is triggered and not canceled, a scheduling request (SR) for cell-specific beam failure recovery is triggered, and if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the ... TRP-specific beam failure recovery MAC CE; otherwise, when uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate a shortened TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened TRP-specific beam failure recovery MAC CE; otherwise, for each TRP for which a BFR is triggered and which has not been cancelled, the MAC entity triggers a scheduling request (SR) for TRP-specific beam failure recovery.

[0166] In this example, two MAC CEs may be generated, i.e., a cell-specific BFR MAC CE (or a cell-specific Truncated BFR MAC CE) and a TRP-specific BFR MAC CE (or a TRP-specific Truncated BFR MAC CE). The two MAC CEs may be included in one MAC PDU.

[0167] Also, for example, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate a shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam failure recovery MAC CE; otherwise, for each cell for which a BFR is triggered and has not been cancelled, a scheduling request (SR) for cell-specific beam failure recovery is triggered; if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources cannot accommodate the cell-specific beam failure recovery MAC CE and its subheader and cannot accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader, the uplink resources instructs the multiplexing and reassembly procedure to generate the shortened cell-specific beam failure recovery MAC CE; otherwise, for each cell for which a BFR is triggered and has not been cancelled, a scheduling request (SR) for cell-specific beam failure recovery is triggered; When the MAC entity is capable of accommodating the CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, when uplink resources are available for a new transmission and the uplink resources are capable of accommodating the shortened TRP-specific beam failure recovery MAC CE and its subheader as a result of the LCP, the MAC entity instructs the multiplexing and assembly entity to generate a shortened TRP-specific beam failure recovery MAC CE; otherwise, for each TRP for which a BFR is triggered and which has not been cancelled, the MAC entity triggers a scheduling request (SR) for TRP-specific beam failure recovery.

[0168] In this example, one MAC CE, i.e., a cell-specific BFR MAC CE (or a cell-specific Truncated BFR MAC CE) or a TRP-specific BFR MAC CE (or a TRP-specific Truncated BFR MAC CE), may be generated. One MAC PDU includes one MAC CE.

[0169] For example, the cell-specific BFR MAC CE and the TRP-specific BFR MAC CE may be generated in an alternating manner.

[0170] If uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources are capable of accommodating the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources are capable of accommodating the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the TRP-specific beam failure recovery MAC CE; if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources cannot accommodate the cell-specific beam failure recovery MAC CE and its subheader (or the MAC entity has not instructed the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE), (and) are capable of accommodating a shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly entity to generate the shortened cell-specific beam failure recovery MAC CE. Trigger a scheduling request (SR) for cell-specific beam failure recovery for each cell for which a BFR is triggered and not cancelled, otherwise if there are no uplink resources available for the new transmission, or if uplink resources are available for the new transmission and, as a result of the LCP, the cell-specific beam failure recovery MAC CE and its subheader cannot be accommodated (or the MAC entity has not instructed the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE) and the shortened cell-specific beam failure recovery MAC CE and its subheader cannot be accommodated (or the MAC entity has not instructed the multiplexing and assembly procedure to generate the shortened cell-specific beam failure recovery MAC CE), trigger a scheduling request (SR) for cell-specific beam failure recovery for each cell for which a BFR is triggered and not cancelled, otherwise if uplink resources are available for the new transmission and, as a result of the LCP, the uplink resources are shortenedIf the CE and its subheader can be accommodated, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened TRP-specific beam failure recovery MAC CE, otherwise it triggers a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which a BFR has been triggered and which has not been cancelled.

[0171] In this example, two MAC CEs may be generated: a cell-specific BFR MAC CE (or a TRP-specific BFR MAC CE) and a cell-specific Truncated BFR MAC CE (or a TRP-specific Truncated BFR MAC CE).

[0172] Also, for example, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; if the uplink resources cannot accommodate the cell-specific beam failure recovery MAC CE and its subheader and cannot accommodate the TRP-specific beam failure recovery MAC CE and its subheader, when the uplink resources can accommodate a shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate the shortened cell-specific beam failure recovery MAC CE and its subheader. otherwise, when uplink resources are available for new transmission and as a result of the LCP the uplink resources can accommodate a shortened TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened TRP-specific beam failure recovery MAC CE, otherwise, triggers a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which BFR is triggered and not canceled.

[0173] In this example, one MAC CE may be generated, that is, a cell-specific BFR MAC CE (or a TRP-specific BFR MAC CE) or a cell-specific Truncated BFR MAC CE (or a TRP-specific Truncated BFR MAC CE).

[0174] In some aspects, a shortened TRP-specific beam failure recovery MAC CE is supported, the priority of which is the same as the priority of the cell-specific beam failure recovery MAC CE.

[0175] For example, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader and the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE and the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, or the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE or the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader and the shortened TRP-specific beam failure recovery MAC When uplink resources are available for new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam failure recovery MAC CE and its subheader, or a shortened TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly entity to generate a shortened cell-specific beam failure recovery MAC CE or a shortened TRP-specific beam failure recovery MAC CE; otherwise, when uplink resources are available for new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam failure recovery MAC CE and its subheader, or a shortened TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly entity to generate a shortened cell-specific beam failure recovery MAC CE or a shortened TRP-specific beam failure recovery MAC CE; otherwise, it triggers a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which BFR is triggered and not canceled, and triggers a scheduling request (SR) for cell-specific beam failure recovery for each cell for which BFR is triggered and not canceled.

[0176] In some aspects, the shortened TRP-specific beam failure recovery MAC CE is not supported, and the TRP-specific beam failure recovery MAC CE is preferentially generated.

[0177] For example, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, for each TRP for which a BFR is triggered and not canceled, a scheduling request (SR) for TRP-specific beam failure recovery is triggered, and if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, when uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate the shortened cell-specific beam failure recovery MAC CE and its subheader. Instructs the BFR to generate a CE, otherwise triggers a cell-specific Scheduling Request (SR) for beam failure recovery for each cell for which a BFR has been triggered and not cancelled.

[0178] In this example, two MAC CEs may be generated, namely, a TRP-specific BFR MAC CE and a cell-specific BFR MAC CE (or a cell-specific Truncated BFR MAC CE). The two MAC CEs may be included in one MAC PDU.

[0179] Also, for example, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, for each TRP for which a BFR is triggered and not canceled, a scheduling request (SR) for TRP-specific beam failure recovery is triggered; if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources cannot accommodate the TRP-specific beam failure recovery MAC CE and its subheader and cannot accommodate the cell-specific beam failure recovery MAC CE and its subheader, the uplink resources are abbreviated cell-specific beam failure recovery MAC CE and its subheader. If the CE and its subheader can be accommodated, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam failure recovery MAC CE, otherwise it triggers a scheduling request (SR) for cell-specific beam failure recovery for each cell for which a BFR has been triggered and not cancelled.

[0180] In this example, one MAC CE, i.e., a TRP-specific BFR MAC CE, or a cell-specific BFR MAC CE (or a cell-specific Truncated BFR MAC CE), may be generated. One MAC PDU includes one MAC CE.

[0181] In some aspects, the truncated TRP-specific beam failure recovery MAC CE is not supported, and the cell-specific beam failure recovery MAC CE is generated preferentially.

[0182] For example, the cell-specific BFR MAC CE and the TRP-specific BFR MAC CE may be generated sequentially.

[0183] If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly entity to generate a shortened cell-specific beam failure recovery MAC CE; otherwise, for each cell for which a BFR is triggered and not canceled, a scheduling request (SR) for cell-specific beam failure recovery is triggered, and if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the ... TRP-specific beam failure recovery MAC CE; Instruct the BFR to generate a CE, otherwise trigger a TRP-specific Scheduling Request (SR) for beam failure recovery for each TRP for which a BFR has been triggered and not cancelled.

[0184] In this example, two MAC CEs may be generated, namely a cell-specific BFR MAC CE (or a cell-specific Truncated BFR MAC CE) and a TRP-specific BFR MAC CE, and the two MAC CEs may be included in one MAC PDU.

[0185] Also, for example, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate a shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam failure recovery MAC CE; otherwise, for each cell for which a BFR is triggered and not canceled, a scheduling request (SR) for cell-specific beam failure recovery is triggered; if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources cannot accommodate the cell-specific beam failure recovery MAC CE and its subheader and cannot accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader, the uplink resources instructs the multiplexing and reassembly procedure to generate the shortened cell-specific beam failure recovery MAC CE; otherwise, for each cell for which a BFR is triggered and not canceled, a scheduling request (SR) for cell-specific beam failure recovery is triggered; When the CE and its subheader can be accommodated, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE, otherwise it triggers a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which a BFR has been triggered and which has not been cancelled.

[0186] In this example, one MAC CE may be generated, that is, a cell-specific BFR MAC CE (or a cell-specific Truncated BFR MAC CE) or a TRP-specific BFR MAC CE. One MAC PDU includes one MAC CE.

[0187] As another example, the cell-specific BFR MAC CE and the TRP-specific BFR MAC CE may be generated in an alternating manner.

[0188] If uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, for each TRP for which a BFR is triggered and which has not been cancelled, a scheduling request (SR) for TRP-specific beam failure recovery is triggered; if uplink resources are available for a new transmission and as a result of the LCP the uplink resources cannot accommodate the cell-specific beam failure recovery MAC CE and its subheader (or the MAC entity has not instructed the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE), and (and) a shortened cell-specific beam failure recovery MAC If the CE and its subheader can be accommodated, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam failure recovery MAC CE, otherwise it triggers a scheduling request (SR) for cell-specific beam failure recovery for each cell for which a BFR has been triggered and not cancelled.

[0189] In this example, two MAC CEs may be generated: a cell-specific BFR MAC CE (or a TRP-specific BFR MAC CE) and a cell-specific Truncated BFR MAC CE.

[0190] Also, for example, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, for each TRP for which a BFR is triggered and which has not been cancelled, a scheduling request (SR) for TRP-specific beam failure recovery is triggered; if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources cannot accommodate the cell-specific beam failure recovery MAC CE and its subheader and cannot accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, for each TRP for which a BFR is triggered and which has not been cancelled, a scheduling request (SR) for TRP-specific beam failure recovery is triggered; If the CE and its subheader can be accommodated, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam failure recovery MAC CE, otherwise it triggers a scheduling request (SR) for cell-specific beam failure recovery for each cell for which a BFR has been triggered and not cancelled.

[0191] In this example, one MAC CE may be generated, that is, a cell-specific BFR MAC CE (or a TRP-specific BFR MAC CE) or a cell-specific Truncated BFR MAC CE. One MAC PDU includes one MAC CE.

[0192] In some aspects, a shortened TRP-specific beam failure recovery MAC CE is not supported, and the priority of the TRP-specific beam failure recovery MAC CE is the same as the priority of the cell-specific beam failure recovery MAC CE.

[0193] For example, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader and the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE and the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, or the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE or the TRP-specific beam failure recovery MAC CE; otherwise, it triggers a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which BFR is triggered and not canceled, and triggers a scheduling request (SR) for cell-specific beam failure recovery for each cell for which BFR is triggered and not canceled.

[0194] The following describes the TRP-specific MAC CE priorities.

[0195] In some aspects, the priority of the logical channel corresponding to the transmission / reception point specific beam failure recovery MAC CE is lower than the priority of the logical channel corresponding to the C-RNTI MAC CE or data from an uplink channel (UL-CCCH) and is higher than the priority of the logical channel corresponding to the cell specific beam failure recovery MAC CE.

[0196] In some aspects, the priority of the logical channel corresponding to the transmission / reception point specific beam failure recovery MAC CE is the same as the priority of the logical channel corresponding to the cell specific beam failure recovery MAC CE.

[0197] In some aspects, the priority of a logical channel corresponding to the transmission / reception point specific beam failure recovery MAC CE is lower than the priority of a logical channel corresponding to the cell specific beam failure recovery MAC CE and higher than the priority of a logical channel corresponding to a Sidelink Configured Grant Confirmation MAC CE.

[0198] In some aspects, the priority of the logical channel corresponding to the transmission / reception point specific beam failure recovery MAC CE is the same as the priority of the logical channel corresponding to the Sidelink Configured Grant Confirmation MAC CE.

[0199] In some aspects, the priority of a logical channel corresponding to the transmission / reception point specific beam failure recovery MAC CE is lower than the priority of a logical channel corresponding to a Sidelink Configured Grant Confirmation MAC CE and higher than the priority of a logical channel corresponding to an LBT failure MAC CE.

[0200] In some aspects, the priority of the logical channel corresponding to the transmission / reception point specific beam failure recovery MAC CE is the same as the priority of the logical channel corresponding to the LBT failure MAC CE.

[0201] In some aspects, the priority of a logical channel corresponding to the transmission / reception point-specific beam failure recovery MAC CE is lower than the priority of a logical channel corresponding to an LBT failure MAC CE and higher than the priority of a logical channel corresponding to a MAC CE for SL-BSR.

[0202] The following describes candidate beams (which may also be referred to as available beams or new beams).

[0203] In some aspects, the MAC CE further includes information of candidate beams.

[0204] In some aspects, the candidate beam information includes a synchronization signal block (SSB) index or a channel state information reference signal (CSI-RS) index, or the candidate beam information indicates the order in which they appear in the configured candidate beams.

[0205] In some aspects, the candidate beam satisfies at least one of the following conditions:

[0206] The candidate beam is included in a candidate beam list configured for the TRP in which a TRP-specific beam failure was detected, or is included in a candidate beam / BFD-RS list configured for the cell to which the TRP in which a TRP-specific beam failure was detected belongs, or is included in a candidate beam / BFD-RS list configured for another TRP in the cell to which the TRP in which a TRP-specific beam failure was detected belongs.

[0207] The received power of the reference signal (RSRP) is higher than a configured threshold.

[0208] The signal-to-interference-and-noise ratio (SINR) is higher than a configured threshold.

[0209] The received signal strength indicator (RSSI) is higher than a configured threshold.

[0210] The beam / RS paired with the candidate beam is included in a candidate beam list configured for the TRP in which a TRP-specific beam failure was detected, or the beam / RS paired with the candidate beam is included in a candidate beam / BFD-RS list configured for the cell to which the TRP in which a TRP-specific beam failure was detected belongs, or the beam / RS paired with the candidate beam is included in a candidate beam / BFD-RS list configured for another TRP in the cell to which the TRP in which a TRP-specific beam failure was detected belongs.

[0211] The measurement value of the beam / RS paired with the candidate beam is higher than a configured threshold.

[0212] In some aspects, the terminal device selects one or N of multiple candidate beams based on implementation or arbitrarily, or selects the one or N with the highest measurement value, or selects the one or N with the highest measurement value and whose paired beam / RS has a measurement value higher than a configured threshold, or selects the one or N with the highest measurement value and whose paired beam / RS has a measurement value higher than a configured threshold, where N is an integer greater than 1.

[0213] The above embodiments are merely illustrative of the present invention, and the present invention is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, each of the above embodiments may be used alone, or one or more of the above embodiments may be used in combination.

[0214] According to this embodiment, the terminal device generates a MAC CE, and the MAC CE indicates the information of the TRP where the beam failure is detected or the beam failure recovery is triggered. Thus, the terminal device can explicitly indicate the information of the TRP to the network device, and the network device can take measures against the beam failure at the TRP level, thereby avoiding the waste of resources.

[0215] <Example 2> The embodiment of the present invention provides a method for reporting beam failure information, and will be described starting from the terminal device. Descriptions of contents similar to those of the first embodiment will be omitted.

[0216] 16 is a schematic diagram of an example of a method for reporting beam failure information according to an embodiment of the present invention. As shown in FIG. 16, the method includes the following steps:

[0217] Step 1601: A terminal device detects that a beam failure occurs in a link between a transmission / reception point, or that a beam failure recovery of the transmission / reception point is triggered.

[0218] Step 1602: The terminal device indicates to the network device, via another transmission / reception point of the cell to which the transmission / reception point belongs, information that a beam failure has been detected or a beam failure recovery has been triggered.

[0219] It should be noted that the above FIG. 16 only shows a schematic example of the embodiment of the present invention, but the present invention is not limited thereto. For example, the execution order between various steps may be appropriately adjusted, some other steps may be added, and some steps may be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description of the above FIG. 16.

[0220] In an embodiment of the present invention, the terminal device can indicate to the network device the information that the beam failure is detected or the beam failure recovery is triggered through another transmission / reception point (e.g., TRP-1) of the cell to which the transmission / reception point (e.g., TRP-2) belongs, so that the terminal device can implicitly indicate the information of the TRP to the network device, and the network device can take measures against the beam failure at the TRP level, thereby avoiding the waste of resources.

[0221] In some aspects, the information that the beam failure was detected or the beam failure recovery was triggered is included in a transmission / reception point (TRP) specific beam failure recovery MAC CE (TRP-specific BFR MAC CE).

[0222] In some aspects, the beam failure detected or beam failure recovery triggered information includes an indication of whether a candidate beam or a candidate reference signal is found. For example, a value of one bit of the beam failure detected or beam failure recovery triggered information indicates that a candidate beam is configured and found, or indicates that a candidate beam is configured and the MAC CE includes information of the candidate beam, or indicates that the MAC CE includes information of the candidate beam.

[0223] For example, 1 indicates that a candidate beam is configured and found, or indicates that a candidate beam is configured and the MAC CE includes information on the candidate beam, or indicates that the MAC CE includes information on the candidate beam, and for example, 0 indicates that a candidate beam is configured and found, or indicates that a candidate beam is configured and the MAC CE includes information on the candidate beam, or indicates that the MAC CE includes information on the candidate beam.

[0224] Figure 17 is a schematic diagram of another example of a TRP-specific BFR MAC CE according to an embodiment of the present invention, Figure 18 is a schematic diagram of another example of a TRP-specific BFR MAC CE according to an embodiment of the present invention, and Figure 19 is a schematic diagram of another example of a TRP-specific BFR MAC CE according to an embodiment of the present invention, which shows a format having 4 / 2 pairs of candidate beams.

[0225] As shown in Figures 17 to 19, the TRP-specific BFR MAC CE may include a serving cell index and a fractional bandwidth (BWP) ID, and may further include an AC field. In addition, the TRP-specific BFR MAC CE may include 0, 1, or multiple candidate RS IDs.

[0226] In some aspects, the beam failure detected or beam failure recovery triggered information further includes information of candidate beams, where the information of candidate beams indicates a reference signal (RS).

[0227] For example, the candidate beam information includes a synchronization signal block (SSB) index or a channel state information reference signal (CSI-RS) index, or the candidate beam information indicates the order of appearance in the configured candidate beams, for example, 0 represents the first candidate beam, 1 represents the second candidate beam, and so on.

[0228] In some aspects, a candidate beam satisfies at least one of the following conditions:

[0229] The candidate beam is included in a candidate beam list configured for the TRP in which a TRP-specific beam failure was detected, or is included in a candidate beam / BFD-RS list configured for the cell to which the TRP in which a TRP-specific beam failure was detected belongs, or is included in a candidate beam / BFD-RS list configured for another TRP in the cell to which the TRP in which a TRP-specific beam failure was detected belongs.

[0230] The Reference Signal Received Power (RSRP) is higher than a configured threshold, for example SS-RSRP or CSI-RSRP.

[0231] The Signal to Interference plus Noise Ratio (SINR) is higher than a configured threshold.

[0232] The Received Signal Strength Indicator (RSSI) is higher than a configured threshold.

[0233] The beam / RS paired with the candidate beam is included in a candidate beam list configured for the TRP in which a TRP-specific beam failure was detected, or the beam / RS paired with the candidate beam is included in a candidate beam / BFD-RS list configured for the cell to which the TRP in which a TRP-specific beam failure was detected belongs, or the beam / RS paired with the candidate beam is included in a candidate beam / BFD-RS list configured for another TRP in the cell to which the TRP in which a TRP-specific beam failure was detected belongs.

[0234] The measurement value of the beam / RS paired with the candidate beam is higher than a configured threshold.

[0235] In some aspects, the terminal device selects one or N of multiple candidate beams based on implementation or arbitrarily, or selects the one or N with the highest measurement value, or selects the one or N with the highest measurement value and whose paired beam / RS has a measurement value higher than a configured threshold, or selects the one or N with the highest measurement value and whose paired beam / RS has a measurement value higher than a configured threshold, where N is an integer greater than 1.

[0236] For example, the terminal device may select one or more candidate beams, and if multiple candidate beams are selected, they may be added to the MAC CE in the order in which they are selected.

[0237] Fig. 20 is a schematic diagram of an example of beam selection in an embodiment of the present invention. As shown in Fig. 20, for a beam with a candidate RS ID of i, it may be determined whether there is another beam (e.g., a beam with RS ID=j) whose RSRP is greater than that of the beam with RS ID=i. If NO, it indicates that the RSRP value of the beam with RS ID=i is the largest, and select the beam with the candidate RS ID of i.

[0238] If YES, further determine whether the RSRP of the beam paired with the other beam (e.g., beam with RS ID=j) is greater than the threshold (Thr1); if NO, even if the RSRP of the other beam is greater than the RSRP of the beam with RS ID=i, it indicates that the beam paired with the other beam does not satisfy the threshold condition, and select the candidate beam with RS ID=i; if YES, it indicates that there exists another beam whose RSRP is greater than the RS ID=i and whose paired beam satisfies the threshold condition, and do not select the candidate beam with RS ID=i, and continue to determine the subsequent beams after adding 1 to i.

[0239] In some aspects, the information on which the beam failure was detected or the beam failure recovery was triggered may further include beam / RS information paired with the selected candidate beam.

[0240] In some aspects, the MAC CE is identified by a Logical Channel Identifier (LCID) or an extended Logical Channel Identifier (eLCID) MAC subheader.

[0241] The above is an outline of the contents of the MAC CE. The following is an outline of the generation of the TRP-specific MAC CE.

[0242] In some aspects, a medium access control (MAC) entity of the terminal device instructs the multiplexing and assembly procedure to generate a transmission / reception point (TRP) specific beam failure recovery MAC CE, which is different from a cell specific beam failure recovery MAC CE.

[0243] In some aspects, a TRP-specific MAC CE may be generated using a procedure independent of the cell-specific MAC CE procedure, where the TRP-specific MAC CE may include a TRP-specific / TRP-level BFR MAC CE (Rel-17 BFR MAC CE), a TRP-specific / TRP-level BF MAC CE (Rel-17 BF MAC CE), a TRP-specific / TRP-level Truncated BFR MAC CE (Rel-17 Truncated BFR MAC CE), and a TRP-specific / TRP-level Truncated BF MAC CE (Rel-17 Truncated BF MAC CE). One or any combination of the above types of MAC CE may be generated independently.

[0244] For example, the procedure for generating the TRP-specific beam failure recovery MAC CE includes, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructing the multiplexing and assembly entity to generate the TRP-specific beam failure recovery MAC CE, and otherwise triggering a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which a BFR has been triggered and has not been canceled.

[0245] In some aspects, a procedure may be used to generate cell-specific MAC CE and TRP-specific MAC CE, where cell-specific MAC CE may include cell-specific BFR MAC CE (Rel-16 BFR MAC CE), cell-specific truncated BFR MAC CE (Rel-16 Truncated BFR MAC CE), and TRP-specific BFR MAC CE (TRP-specific BFR MAC CE) may include TRP-specific / TRP-level BFR MAC CE (Rel-17 BFR MAC CE), TRP-specific / TRP-level BF MAC CE (Rel-17 Truncated BF MAC CE). The procedure may be used to generate any or any combination of the above types of MAC CE.

[0246] For example, a beam failure recovery MAC CE specific to the TRP is preferentially generated.

[0247] For example, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, for each TRP for which a BFR is triggered and not canceled, a scheduling request (SR) for TRP-specific beam failure recovery is triggered, and if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, when uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate the shortened cell-specific beam failure recovery MAC CE and its subheader. Instructs the BFR to generate a CE, otherwise triggers a cell-specific Scheduling Request (SR) for beam failure recovery for each cell for which a BFR has been triggered and not cancelled.

[0248] In this example, two MAC CEs may be generated: a TRP-specific BFR MAC CE and a cell-specific BFR MAC CE (or a cell-specific Truncated BFR MAC CE).

[0249] Also, for example, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, for each TRP for which a BFR is triggered and not canceled, a scheduling request (SR) for TRP-specific beam failure recovery is triggered, and if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, when uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate the shortened cell-specific beam failure recovery MAC CE and its subheader. Instructs the BFR to generate a CE, otherwise triggers a cell-specific Scheduling Request (SR) for beam failure recovery for each cell for which a BFR has been triggered and not cancelled.

[0250] In this example, one MAC CE may be generated, ie, a TRP-specific BFR MAC CE or a cell-specific BFR MAC CE (or a cell-specific Truncated BFR MAC CE).

[0251] Also, for example, a cell-specific beam interference recovery MAC CE is preferentially generated.

[0252] For example, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate the shortened cell-specific beam failure recovery MAC CE; otherwise, for each cell for which a BFR is triggered and not canceled, a scheduling request (SR) for cell-specific beam failure recovery is triggered, and if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE. Instruct the BFR to generate a CE, otherwise trigger a TRP-specific Scheduling Request (SR) for beam failure recovery for each TRP for which a BFR has been triggered and not cancelled.

[0253] In this example, two MAC CEs may be generated: a cell-specific BFR MAC CE (or a cell-specific Truncated BFR MAC CE) and a TRP-specific BFR MAC CE.

[0254] Also, for example, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, for each TRP for which a BFR is triggered and which has not been canceled, a scheduling request (SR) for TRP-specific beam failure recovery is triggered; otherwise, if uplink resources are available for a new transmission and, as a result of the LCP, the uplink resources can accommodate the shortened cell ... entity to generate the shortened cell-specific beam failure recovery MAC CE and its subheader. Instructs the BFR to generate a CE, otherwise triggers a cell-specific Scheduling Request (SR) for beam failure recovery for each cell for which a BFR has been triggered and not cancelled.

[0255] In this example, one MAC CE may be generated, that is, a cell-specific BFR MAC CE (or a TRP-specific BFR MAC CE), or a cell-specific Truncated BFR MAC CE.

[0256] In some aspects, the priority of the transmission / reception point specific beam failure recovery MAC CE is the same as the priority of the cell specific beam failure recovery MAC CE.

[0257] For example, if uplink resources are available for a new transmission and, as a result of LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader and the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE and the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, or the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE or ... are shortened, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE or the TRP-specific beam failure recovery MAC CE. When the CE and its subheader can be accommodated, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam failure recovery MAC CE, otherwise it triggers a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which BFR is triggered and not canceled, and triggers a scheduling request (SR) for cell-specific beam failure recovery for each cell for which BFR is triggered and not canceled.

[0258] Also, for example, if uplink resources are available for a new transmission and, as a result of LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader and the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE and the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of LCP, the uplink resources can accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader and the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate the shortened cell-specific beam failure recovery MAC CE and the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, or the TRP-specific beam failure recovery MAC When the MAC entity is capable of accommodating the shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE or the TRP-specific beam failure recovery MAC CE; otherwise, when uplink resources are available for a new transmission and the uplink resources are capable of accommodating the shortened cell-specific beam failure recovery MAC CE and its subheader as a result of the LCP, the MAC entity instructs the multiplexing and assembly entity to generate a shortened cell-specific beam failure recovery MAC CE; otherwise, the MAC entity triggers a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which BFR is triggered and not canceled, and triggers a scheduling request (SR) for cell-specific beam failure recovery for each cell for which BFR is triggered and not canceled.

[0259] The following describes the TRP-specific MAC CE priorities.

[0260] In some aspects, the priority of the logical channel corresponding to the transmission / reception point specific beam failure recovery MAC CE is lower than the priority of the logical channel corresponding to the C-RNTI MAC CE or data from an uplink channel (UL-CCCH) and is higher than the priority of the logical channel corresponding to the cell specific beam failure recovery MAC CE.

[0261] In some aspects, the priority of the logical channel corresponding to the transmission / reception point specific beam failure recovery MAC CE is the same as the priority of the logical channel corresponding to the cell specific beam failure recovery MAC CE.

[0262] In some aspects, the priority of a logical channel corresponding to the transmission / reception point specific beam failure recovery MAC CE is lower than the priority of a logical channel corresponding to the cell specific beam failure recovery MAC CE and higher than the priority of a logical channel corresponding to a Sidelink Configured Grant Confirmation MAC CE.

[0263] In some aspects, the priority of the logical channel corresponding to the transmission / reception point specific beam failure recovery MAC CE is the same as the priority of the logical channel corresponding to the Sidelink Configured Grant Confirmation MAC CE.

[0264] In some aspects, the priority of a logical channel corresponding to the transmission / reception point specific beam failure recovery MAC CE is lower than the priority of a logical channel corresponding to a Sidelink Configured Grant Confirmation MAC CE and higher than the priority of a logical channel corresponding to an LBT failure MAC CE.

[0265] In some aspects, the priority of the logical channel corresponding to the transmission / reception point specific beam failure recovery MAC CE is the same as the priority of the logical channel corresponding to the LBT failure MAC CE.

[0266] In some aspects, the priority of a logical channel corresponding to the transmission / reception point-specific beam failure recovery MAC CE is lower than the priority of a logical channel corresponding to an LBT failure MAC CE and higher than the priority of a logical channel corresponding to a MAC CE for SL-BSR.

[0267] The above embodiments are merely illustrative of the present invention, and the present invention is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, each of the above embodiments may be used alone, or one or more of the above embodiments may be used in combination.

[0268] According to this embodiment, the terminal device indicates the information that the beam failure is detected or the beam failure recovery is triggered to the network device through another TRP of the cell to which the TRP in which the beam failure is detected or the beam failure recovery is triggered belongs. This allows the terminal device to implicitly indicate the information of the TRP to the network device, and the network device can take measures against the beam failure at the TRP level, thereby avoiding the waste of resources.

[0269] <Example 3> The following description will be based on the first and second embodiments, and description of the same contents as those of the first and second embodiments will be omitted. The third embodiment may be implemented in combination with the first and second embodiments, or may be implemented independently.

[0270] In some aspects, the terminal device detects that a beam failure occurs in a link between the transmission / reception point or that a beam failure recovery of the transmission / reception point is triggered, and generates a MAC CE based on a carrier aggregation (CA) configuration and / or uplink resources, where the MAC CE indicates information of the transmission / reception point where the beam failure is detected or the beam failure recovery is triggered, or indicates information that the beam failure is detected or the beam failure recovery is triggered via another transmission / reception point of the cell to which the transmission / reception point belongs to, to a network device.

[0271] For example, when the terminal device does not configure carrier aggregation, the terminal device generates a MAC CE, and the MAC CE indicates the information of the transmission / reception point where the beam failure is detected or the beam failure recovery is triggered. In addition, the terminal device may further report the MAC CE to the network device.

[0272] When carrier aggregation is configured, the terminal device indicates to the network device information that beam failure has been detected or beam failure recovery has been triggered via other transmission / reception points of the cell to which the transmission / reception point belongs.

[0273] Also, for example, when carrier aggregation is configured and uplink resources can accommodate MAC CE, the terminal device generates a MAC CE, where the MAC CE indicates the information of the transmission / reception point where beam failure is detected or beam failure recovery is triggered. Also, the terminal device may further report the MAC CE to the network device.

[0274] If carrier aggregation is not configured, or if carrier aggregation is configured and the uplink resources cannot accommodate the MAC CE, the terminal device indicates to the network device information that beam failure has been detected or beam failure recovery has been triggered via other transmission / reception points of the cell to which the transmission / reception point belongs.

[0275] An embodiment of the present invention further provides a method for receiving beam failure information, the method including the following steps:

[0276] The network device receives a MAC CE sent by a terminal device, or receives information indicating that a beam failure has been detected or a beam failure recovery has been triggered, which is indicated by the terminal device via another transmission / reception point of the cell to which the transmission / reception point belongs, where the MAC CE indicates information of the transmission / reception point where a beam failure has been detected or a beam failure recovery has been triggered.

[0277] For the configuration of the network device and the interaction related to the terminal device, reference may be made to the first and second embodiments.

[0278] The above embodiments are merely illustrative of the present invention, and the present invention is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, each of the above embodiments may be used alone, or one or more of the above embodiments may be used in combination.

[0279] According to this embodiment, the terminal device generates a MAC CE based on the configuration of carrier aggregation (CA) and / or uplink resources. Here, the MAC CE indicates the information of the TRP where the beam failure is detected or the beam failure recovery is triggered, or the terminal device indicates the information of the beam failure is detected or the beam failure recovery is triggered to the network device via another TRP of the cell to which the TRP where the beam failure is detected or the beam failure recovery is triggered belongs. In this way, the terminal device can explicitly or implicitly indicate the information of the TRP to the network device, and the network device can take measures against the beam failure at the TRP level, thereby avoiding resource waste.

[0280] <Example 4> The embodiment of the present invention provides a beam obstruction information generating device. The device may be, for example, a terminal device, or one or more components configured in the terminal device. The description of the same contents as those in the first to third embodiments will be omitted.

[0281] 21 is a schematic diagram of an example of a beam hazard information generating device according to an embodiment of the present invention. As shown in FIG. 21, a beam hazard information generating device 2100 includes the following units.

[0282] The detection unit 2101 detects that a beam failure has occurred in a link with a transmission / reception point (TRP) or that beam failure recovery of the transmission / reception point has been triggered.

[0283] The processing unit 2102 generates a Medium Access Control (MAC) Control Element (CE), where the MAC CE indicates the information of the transmission / reception point where a beam failure is detected or a beam failure recovery is triggered.

[0284] In some aspects, the transmission / reception point information includes an index or identifier of the transmission / reception point at which a beam obstruction was detected or a beam obstruction recovery was triggered.

[0285] In some aspects, one value of the bit in the MAC CE indicates that beam failure has been detected or beam failure recovery has been triggered for a transmission / reception point corresponding to a control resource pool with index 0, and another value of the bit indicates that beam failure has been detected or beam failure recovery has been triggered for a transmission / reception point corresponding to a control resource pool with index 1.

[0286] In some aspects, one value of the bit in the MAC CE indicates that a beam failure has been detected or a beam failure recovery has been triggered for a transmission / reception point whose index is 0, and another value of the bit indicates that a beam failure has been detected or a beam failure recovery has been triggered for a transmission / reception point whose index is 1.

[0287] In some aspects, one value of the one bit in the MAC CE indicates that a beam failure has been detected or a beam failure recovery has been triggered for a transmission / reception point corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 0, or indicates that a beam failure has been detected or a beam failure recovery has been triggered for all beams corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 0. Another value of the one bit indicates that a beam failure has been detected or a beam failure recovery has been triggered for a transmission / reception point corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 1, or indicates that a beam failure has been detected or a beam failure recovery has been triggered for all beams corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 1.

[0288] In some aspects, the R bit in a beam failure recovery (BFR) MAC CE or a truncated beam failure recovery (truncated BFR) MAC CE is used to convey / indicate / represent the index of the transmission / reception point where beam failure was detected or beam failure recovery was triggered.

[0289] In some aspects, a value of one of the two bits in the MAC CE indicates one or any combination of the following: no transmission / reception point has been detected as a beam failure or a beam failure recovery has been triggered; a transmission / reception point corresponding to a control resource pool with index 0 has been detected as a beam failure or a beam failure recovery has been triggered; a transmission / reception point corresponding to a control resource pool with index 1 has been detected as a beam failure or a beam failure recovery has been triggered; and a transmission / reception point corresponding to a control resource pool with index 0 and a control resource pool with index 1 have been detected as a beam failure or a beam failure recovery has been triggered.

[0290] In some aspects, the value of one of the two bits in the MAC CE indicates one or any combination of the following: no transmission / reception point has detected beam failure or triggered beam failure recovery; a transmission / reception point with index 0 has detected beam failure or triggered beam failure recovery; a transmission / reception point with index 1 has detected beam failure or triggered beam failure recovery; and both a transmission / reception point with index 0 and a transmission / reception point with index 1 have detected beam failure or triggered beam failure recovery.

[0291] In some aspects, the value of one of the two bits in the MAC CE may indicate: no transmission / reception point has detected a beam failure or triggered a beam failure recovery; a beam failure has been detected or triggered for a transmission / reception point corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 0; a beam failure has been detected or triggered for all beams corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 0; a beam failure has been detected or triggered for a transmission / reception point corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 1; a beam failure has been detected or triggered for all beams corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 1; a beam failure has been detected or triggered for both a transmission / reception point corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 0 and a transmission / reception point corresponding to a beam failure detection reference signal set (BFD-RS set) with an index of 1; set) and all beams corresponding to a beam failure detection reference signal set (BFD-RS set) with index 1, indicates one or any combination of that a beam failure has been detected or a beam failure recovery has been triggered.

[0292] In some aspects, the R bit and AC field in the beam failure recovery MAC CE or shortened beam failure recovery MAC CE are used to convey / indicate / represent the index of the transmission / reception point where beam failure was detected or beam failure recovery was triggered.

[0293] In some aspects, the MAC CE includes the type of beam failure detected or the type of beam failure recovery triggered.

[0294] In some aspects, one bit in the MAC CE indicates a type of beam failure detected or a type of beam failure recovery triggered, with one value of the one bit indicating that beam failure of a cell-specific or all beams is detected or beam failure recovery of a cell-specific or all beams is triggered, and another value of the one bit indicating that beam failure of a transmission / reception point (TRP) specific or some beams is detected or beam failure recovery of a transmission / reception point specific or some beams is triggered, or one value of the one bit indicating that beam failure of a cell-specific or all beams is detected or beam failure recovery of a cell-specific or all beams is triggered. One value of the one bit indicates that beam failure of a non-cell specific or non-all beams has been detected or beam failure recovery of a non-cell specific or non-all beams has been triggered, and the other value of the one bit indicates that beam failure of a non-TRP specific or non-some beams has been detected or beam failure recovery of a non-TRP specific or non-some beams has been triggered.

[0295] In some aspects, the R bit in the beam failure recovery MAC CE or truncated beam failure recovery (truncated BFR) MAC CE is used to convey / indicate / represent the type of beam failure detected or the type of beam failure recovery triggered.

[0296] In some aspects, the two bits in the MAC CE indicate the type of beam failure detected or the type of beam failure recovery triggered, where one value of the two bits indicates that beam failure of a cell-specific or all beams is not detected or beam failure recovery of a cell-specific or all beams is not triggered and beam failure of a TRP-specific or some beams is not detected or beam failure recovery of a TRP-specific or some beams is not triggered, another value of the two bits indicates that beam failure of a cell-specific or all beams is detected or beam failure recovery of a cell-specific or all beams is triggered, another value of the two bits indicates that beam failure of a cell-specific or all beams is detected or beam failure recovery of a TRP-specific or some beams is triggered, and another value of the two bits indicates that beam failure of a cell-specific or all beams is detected or beam failure recovery of a cell-specific or all beams is triggered and beam failure of a TRP-specific or some beams is detected or beam failure recovery of a TRP-specific or some beams is triggered. One value of the two bits indicates that beam failure of a cell-specific or all beams has not been detected, or beam failure recovery of a cell-specific or all beams has not been triggered, and beam failure of a non-cell-specific or non-all beams has not been detected, or beam failure recovery of a non-cell-specific or non-all beams has not been triggered; another value of the two bits indicates that beam failure of a cell-specific or all beams has been detected, or beam failure recovery of a cell-specific or non-all beams has been triggered; and another value of the two bits indicates that beam failure of a cell-specific or all beams has been detected, or beam failure recovery of a cell-specific or non-all beams has been triggered, and beam failure of a non-cell-specific or non-all beams has been detected, or beam failure recovery of a non-cell-specific or non-all beams has been triggered.One value of the two bits indicates that beam failure of a non-TRP-specific or non-some beam has not been detected, or beam failure recovery of a non-TRP-specific or non-some beam has not been triggered, and beam failure of a TRP-specific or non-some beam has not been detected, or beam failure recovery of a TRP-specific or non-some beam has not been triggered; another value of the two bits indicates that beam failure of a non-TRP-specific or non-some beam has been detected, or beam failure recovery of a non-TRP-specific or non-some beam has been triggered; another value of the two bits indicates that beam failure of a TRP-specific or non-some beam has been detected, or beam failure recovery of a TRP-specific or non-some beam has been triggered; and the other value of the two bits indicates that beam failure of a non-TRP-specific or non-some beam has been detected, or beam failure recovery of a non-TRP-specific or non-some beam has been triggered, and beam failure of a TRP-specific or non-some beam has been detected, or beam failure recovery of a TRP-specific or non-some beam has been triggered.

[0297] In some aspects, the R bit and AC field in the beam failure recovery MAC CE or truncated beam failure recovery (truncated BFR) MAC CE are used to convey / indicate / represent the type of beam failure detected or the type of beam failure recovery triggered.

[0298] In some aspects, the MAC CE includes at least one or any combination of information of a cell to which a transmission / reception point belongs where a beam failure has been detected or where beam failure recovery has been triggered, information on whether a candidate beam has been found, and information on the candidate beam.

[0299] In some aspects, as shown in FIG. 21, the beam obstruction information generating device 2100 may further include the following units:

[0300] The transmitting unit 2103 transmits the medium access control control element to the network device.

[0301] The MAC CE is forwarded to the network device via another transmission / reception point in the cell to which the transmission / reception point belongs, or the MAC CE is forwarded to the network device via a transmission / reception point that is co-located with the transmission / reception point and belongs to a cell other than the cell to which the transmission / reception point belongs, or the MAC CE is reported to the network device via a cell other than the cell to which the transmission / reception point belongs.

[0302] In some aspects, the MAC CE is identified by a Logical Channel Identifier (LCID) or an extended Logical Channel Identifier (eLCID) MAC subheader.

[0303] In some aspects, the MAC CE is transmitted using one of an uplink grant of a TRP in a cell to which a TRP in which a TRP-specific beam failure is detected belongs and in which a TRP-specific beam failure is not detected, an uplink grant of a TRP co-located with the TRP in which a TRP-specific beam failure is detected and belonging to a cell other than the cell to which the TRP in which a TRP-specific beam failure is detected belongs, and an uplink grant of a cell other than the cell to which the TRP in which a TRP-specific beam failure is detected belongs.

[0304] In some aspects, when there are multiple available resources, an uplink grant is selected to transmit the MAC CE based on a predefined or network configuration, an uplink grant is selected to transmit the MAC CE based on implementation, or an uplink grant is randomly selected to transmit the MAC CE.

[0305] In some aspects, a medium access control (MAC) entity instructs the multiplexing and reassembly procedure to generate a TRP-specific beam failure recovery MAC CE, which is different from the cell-specific beam failure recovery MAC CE.

[0306] In some aspects, the TRP-specific MAC CE is generated using a procedure that is independent of the procedure for generating the cell-specific MAC CE.

[0307] In some aspects, a shortened TRP-specific beam failure recovery MAC CE is supported. The procedure of generating a TRP-specific beam failure recovery MAC CE includes the MAC entity instructing the multiplexing and assembly procedure to generate the TRP-specific beam failure recovery MAC CE if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, otherwise, when uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the shortened TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructing the multiplexing and assembly entity to generate the shortened TRP-specific beam failure recovery MAC CE, otherwise, triggering a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which a BFR is triggered and not cancelled.

[0308] In some aspects, the shortened TRP-specific beam failure recovery MAC CE is not supported. The procedure for generating the TRP-specific beam failure recovery MAC CE includes the MAC entity instructing the multiplexing and reassembly entity to generate the TRP-specific beam failure recovery MAC CE if uplink resources are available for new transmission and can accommodate the TRP-specific beam failure recovery MAC CE and its subheader as a result of LCP, otherwise triggering a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which BFR is triggered and not canceled.

[0309] In some aspects, one procedure is used to generate the cell-specific MAC CE and the TRP-specific MAC CE.

[0310] In some aspects, a shortened TRP-specific beam failure recovery MAC CE is supported. The shortened TRP-specific beam failure recovery MAC CE is preferentially generated.

[0311] In some aspects, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate a shortened TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly entity to generate a shortened TRP-specific beam failure recovery MAC CE; otherwise, a BFR is triggered and a scheduling request (SR) for TRP-specific beam failure recovery is triggered for each TRP that has not been canceled, and if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE. otherwise, when uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam failure recovery MAC CE, otherwise it triggers a scheduling request (SR) for cell-specific beam failure recovery for each cell for which a BFR has been triggered and has not been cancelled.

[0312] In some aspects, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the shortened TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the shortened TRP-specific beam failure recovery MAC CE. When uplink resources are available for new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam failure recovery MAC CE, otherwise triggers a scheduling request (SR) for cell-specific beam failure recovery for each cell for which BFR is triggered and not canceled.

[0313] In some aspects, a shortened TRP-specific beam failure recovery MAC CE is supported. A cell-specific beam failure recovery MAC CE is preferentially generated.

[0314] In some aspects, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate a shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly entity to generate a shortened cell-specific beam failure recovery MAC CE; otherwise, for each cell for which a BFR is triggered and not canceled, a scheduling request (SR) for cell-specific beam failure recovery is triggered, and if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the ... otherwise, when uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate a shortened TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened TRP-specific beam failure recovery MAC CE; otherwise, for each TRP for which a BFR is triggered and which has not been cancelled, the MAC entity triggers a scheduling request (SR) for TRP-specific beam failure recovery.

[0315] In some aspects, if uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the shortened cell-specific beam failure recovery MAC CE. When uplink resources are available for new transmission and as a result of the LCP the uplink resources can accommodate the shortened TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened TRP-specific beam failure recovery MAC CE, otherwise triggers a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which BFR is triggered and not canceled.

[0316] In some aspects, a shortened TRP-specific beam failure recovery MAC CE is supported, the priority of which is the same as the priority of the cell-specific beam failure recovery MAC CE.

[0317] In some aspects, if uplink resources are available for a new transmission and, as a result of LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader and the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE and the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, or the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE or the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of LCP, the uplink resources can accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader and the shortened TRP-specific beam failure recovery MAC When uplink resources are available for new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam failure recovery MAC CE and its subheader, or a shortened TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly entity to generate a shortened cell-specific beam failure recovery MAC CE or a shortened TRP-specific beam failure recovery MAC CE; otherwise, when uplink resources are available for new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam failure recovery MAC CE and its subheader, or a shortened TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly entity to generate a shortened cell-specific beam failure recovery MAC CE or a shortened TRP-specific beam failure recovery MAC CE; otherwise, it triggers a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which BFR is triggered and not canceled, and triggers a scheduling request (SR) for cell-specific beam failure recovery for each cell for which BFR is triggered and not canceled.

[0318] In some aspects, the shortened TRP-specific beam failure recovery MAC CE is not supported, and the TRP-specific beam failure recovery MAC CE is preferentially generated.

[0319] In some aspects, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE, otherwise, for each TRP for which a BFR is triggered and not canceled, a scheduling request (SR) for TRP-specific beam failure recovery is triggered, and if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE, otherwise, when uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate the shortened cell-specific beam failure recovery MAC CE, otherwise, when uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity Instructs the BFR to generate a CE, otherwise triggers a cell-specific Scheduling Request (SR) for beam failure recovery for each cell for which a BFR has been triggered and not cancelled.

[0320] In some aspects, the truncated TRP-specific beam failure recovery MAC CE is not supported, and the cell-specific beam failure recovery MAC CE is generated preferentially.

[0321] In some aspects, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate a shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly entity to generate a shortened cell-specific beam failure recovery MAC CE; otherwise, for each cell for which a BFR is triggered and not canceled, a scheduling request (SR) for cell-specific beam failure recovery is triggered, and if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the ... Instruct the BFR to generate a CE, otherwise trigger a TRP-specific Scheduling Request (SR) for beam failure recovery for each TRP for which a BFR has been triggered and not cancelled.

[0322] In some aspects, if uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, for each TRP for which a BFR is triggered and which has not been cancelled, a scheduling request (SR) for TRP-specific beam failure recovery is triggered; otherwise, if uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate the shortened cell ... shortened cell-specific beam failure recovery MAC CE. Instructs the BFR to generate a CE, otherwise triggers a cell-specific Scheduling Request (SR) for beam failure recovery for each cell for which a BFR has been triggered and not cancelled.

[0323] In some aspects, a shortened TRP-specific beam failure recovery MAC CE is not supported, and the priority of the TRP-specific beam failure recovery MAC CE is the same as the priority of the cell-specific beam failure recovery MAC CE.

[0324] In some aspects, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader and the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE and the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, or the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE or the TRP-specific beam failure recovery MAC CE. Instruct the system to generate a CE, otherwise trigger a TRP-specific scheduling request (SR) for beam failure recovery for each TRP for which BFR is triggered and not canceled, and trigger a cell-specific scheduling request (SR) for beam failure recovery for each cell for which BFR is triggered and not canceled.

[0325] In some aspects, a priority of the logical channel corresponding to the Tx / Rx specific beam failure recovery MAC CE is lower than a priority of a logical channel corresponding to a C-RNTI MAC CE or data from an uplink channel (UL-CCCH) and higher than a priority of a logical channel corresponding to a cell specific beam failure recovery MAC CE, or a priority of the logical channel corresponding to the Tx / Rx specific beam failure recovery MAC CE is the same as a priority of a logical channel corresponding to the cell specific beam failure recovery MAC CE, or a priority of the logical channel corresponding to the Tx / Rx specific beam failure recovery MAC CE is lower than a priority of a logical channel corresponding to the cell specific beam failure recovery MAC CE and higher than a priority of a logical channel corresponding to a Sidelink Configured Grant Confirmation MAC CE, or a priority of the logical channel corresponding to the Tx / Rx specific beam failure recovery MAC CE is the same as a priority of a logical channel corresponding to a Sidelink Configured Grant Confirmation MAC CE, or a priority of the logical channel corresponding to the Tx / Rx specific beam failure recovery MAC CE is higher than a priority of a logical channel corresponding to a Sidelink Configured Grant Confirmation MAC CE. the priority of the logical channel corresponding to the beam failure recovery MAC CE specific to the transmission / reception point is lower than the priority of the logical channel corresponding to the LBT failure MAC CE and higher than the priority of the logical channel corresponding to the LBT failure MAC CE, or the priority of the logical channel corresponding to the beam failure recovery MAC CE specific to the transmission / reception point is the same as the priority of the logical channel corresponding to the LBT failure MAC CE, or the priority of the logical channel corresponding to the beam failure recovery MAC CE specific to the transmission / reception point is lower than the priority of the logical channel corresponding to the LBT failure MAC CE and higher than the priority of the logical channel corresponding to the MAC CE for SL-BSR.

[0326] In some aspects, the MAC CE further includes information of candidate beams.

[0327] In some aspects, the candidate beam information includes a synchronization signal block (SSB) index or a channel state information reference signal (CSI-RS) index, or the candidate beam information indicates the order in which the candidate beams appear in the configured candidate beams.

[0328] In some aspects, the candidate beam is detected based on the following: the candidate beam is included in a candidate beam list configured for the TRP in which the TRP-specific beam failure was detected, or is included in a candidate beam / BFD-RS list configured for the cell to which the TRP in which the TRP-specific beam failure was detected belongs, or is included in a candidate beam / BFD-RS list configured for another TRP to which the TRP in which the TRP-specific beam failure was detected belongs; the received power of a reference signal (RSRP) is higher than a configured threshold; the signal-to-interference-and-noise ratio (SINR) is higher than a configured threshold; and the received signal strength indicator (RSSI) is higher than a configured threshold. At least one of the following conditions is satisfied: a beam / RS paired with the candidate beam is included in a candidate beam list configured for the TRP in which a TRP-specific beam failure was detected, or a beam / RS paired with the candidate beam is included in a candidate beam / BFD-RS list configured for the cell to which the TRP in which a TRP-specific beam failure was detected belongs, or a beam / RS paired with the candidate beam is included in a candidate beam / BFD-RS list configured for another TRP in the cell to which the TRP in which a TRP-specific beam failure was detected belongs; and a measurement value of the beam / RS paired with the candidate beam is higher than a configured threshold.

[0329] In some aspects, based on the implementation or arbitrarily, one or N of multiple candidate beams are selected, or the one or N with the highest measurement value are selected, or the one or N with the highest measurement value and whose paired beam / RS has a measurement value higher than a configured threshold value are selected, or the one or N with the highest measurement value and whose paired beam / RS has a highest measurement value, where N is an integer greater than 1.

[0330] In some aspects, the detection unit 2101 detects that a beam failure occurs in a link between the transmission / reception point or that a beam failure recovery of the transmission / reception point is triggered. The processing unit 2102 generates a MAC CE based on a carrier aggregation (CA) configuration and / or an uplink resource. Here, the MAC CE indicates information of the transmission / reception point where the beam failure is detected or the beam failure recovery is triggered. Alternatively, the transmission unit 2103 indicates information that the beam failure is detected or the beam failure recovery is triggered to a network device via another transmission / reception point of the cell to which the transmission / reception point belongs.

[0331] The above-mentioned embodiments are merely illustrative of the present invention, and the present invention is not limited thereto, and appropriate modifications can be made based on the above-mentioned embodiments. For example, each of the above-mentioned embodiments can be used alone, or one or more of the above-mentioned embodiments can be used in combination.

[0332] In addition, although only the components or modules related to the present invention are described above, the present invention is not limited thereto. The beam obstruction information generating device 2100 may further include other components or modules. For specific contents of these components or modules, reference may be made to related art.

[0333] Furthermore, for convenience of explanation, Fig. 21 only exemplarily illustrates the connection relationships or signal directions between various components or modules, but it is clear to those skilled in the art that various related technologies such as bus connections can be used. The above-mentioned various components or modules may be implemented by hardware devices such as a processor, a memory, a transmitter, and a receiver, and the present invention is not limited thereto.

[0334] According to this embodiment, the terminal device generates a MAC CE, and the MAC CE indicates the information of the TRP where the beam failure is detected or the beam failure recovery is triggered. Thus, the terminal device can explicitly indicate the information of the TRP to the network device, and the network device can take measures against the beam failure at the TRP level, thereby avoiding the waste of resources.

[0335] <Example 5> The embodiment of the present invention provides a reporting device for beam failure information. The device may be, for example, a terminal device, or may be one or more components configured in the terminal device. The description of the same contents as those in the first to third embodiments will be omitted.

[0336] 22 is a schematic diagram of an example of a beam failure information reporting device 2200 according to an embodiment of the present invention. As shown in FIG. 22, a beam failure information reporting device 2200 includes the following units.

[0337] The detection unit 2201 detects that a beam failure has occurred in a link between a transmitting / receiving point, or that a beam failure recovery of the transmitting / receiving point has been triggered.

[0338] The transmitter 2202 notifies the network device of information that a beam failure has been detected or that beam failure recovery has been triggered via other transmission / reception points of the cell to which the transmission / reception point belongs.

[0339] In some aspects, the information that the beam failure was detected or the beam failure recovery was triggered is included in a transmission / reception point specific beam failure recovery MAC CE.

[0340] In some aspects, the beam failure detected or beam failure recovery triggered information includes an indication of whether a candidate beam was found.

[0341] In some aspects, a value of one bit of the information that a beam failure has been detected or a beam failure recovery has been triggered indicates that a candidate beam has been configured and found, or indicates that a candidate beam has been configured and information about the candidate beam is included in the MAC CE, or indicates that information about the candidate beam is included in the MAC CE.

[0342] In some aspects, the information of the beam failure detected or the beam failure recovery triggered further includes information of a candidate beam, where the information of the candidate beam is indicative of a reference signal.

[0343] In some aspects, the candidate beam information includes a synchronization signal block (SSB) index or a channel state information reference signal (CSI-RS) index, or the candidate beam information indicates the order in which the candidate beams appear in the configured candidate beams.

[0344] In some aspects, the candidate beam is included in a candidate beam list configured for the TRP in which a TRP-specific beam failure was detected, or included in a candidate beam / BFD-RS list configured for the cell to which the TRP in which a TRP-specific beam failure was detected belongs, or included in a candidate beam / BFD-RS list configured for another TRP to which the TRP in which a TRP-specific beam failure was detected belongs, the received power of a reference signal (RSRP) is higher than a configured threshold, the signal-to-interference-and-noise ratio (SINR) is higher than a configured threshold, and the received signal strength indicator (RSSI) is higher than a configured threshold. At least one of the following conditions is satisfied: a beam / RS paired with the candidate beam is included in a candidate beam list configured for the TRP in which a TRP-specific beam failure was detected, or a beam / RS paired with the candidate beam is included in a candidate beam / BFD-RS list configured for the cell to which the TRP in which a TRP-specific beam failure was detected belongs, or a beam / RS paired with the candidate beam is included in a candidate beam / BFD-RS list configured for another TRP in the cell to which the TRP in which a TRP-specific beam failure was detected belongs; and a measurement value of the beam / RS paired with the candidate beam is higher than a configured threshold.

[0345] In some aspects, based on the implementation or arbitrarily, one or N of multiple candidate beams are selected, or the one or N with the highest measurement value are selected, or the one or N with the highest measurement value and whose paired beam / RS has a measurement value higher than a configured threshold value are selected, or the one or N with the highest measurement value and whose paired beam / RS has a highest measurement value, where N is an integer greater than 1.

[0346] In some aspects, the information on which the beam failure was detected or the beam failure recovery was triggered further includes beam / RS information paired with the selected candidate beam.

[0347] In some aspects, the MAC CE is identified by a Logical Channel Identifier (LCID) or an extended Logical Channel Identifier (eLCID) MAC subheader.

[0348] In some aspects, the medium access control (MAC) entity instructs the multiplexing and assembly procedure to generate a transmission / reception point (TRP)-specific beam failure recovery MAC CE, which is different from a cell-specific beam failure recovery MAC CE.

[0349] In some aspects, the TRP-specific MAC CE is generated using a procedure that is independent of the cell-specific MAC CE procedure.

[0350] In some aspects, the procedure for generating the TRP-specific beam failure recovery MAC CE includes, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructing the multiplexing and assembly entity to generate the TRP-specific beam failure recovery MAC CE, and otherwise triggering a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which a BFR has been triggered and has not been canceled.

[0351] In some aspects, a single procedure is used to generate the cell-specific MAC CE and the TRP-specific MAC CE.

[0352] In some aspects, the TRP-specific beam failure recovery MAC CE is preferentially generated.

[0353] In some aspects, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE, otherwise, for each TRP for which a BFR is triggered and not canceled, a scheduling request (SR) for TRP-specific beam failure recovery is triggered, and if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE, otherwise, when uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate the shortened cell-specific beam failure recovery MAC CE, otherwise, when uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity Instructs the BFR to generate a CE, otherwise triggers a cell-specific Scheduling Request (SR) for beam failure recovery for each cell for which a BFR has been triggered and not cancelled.

[0354] In some aspects, a cell-specific beam failure recovery MAC CE is preferentially generated.

[0355] In some aspects, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate a shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly entity to generate a shortened cell-specific beam failure recovery MAC CE; otherwise, for each cell for which a BFR is triggered and not canceled, a scheduling request (SR) for cell-specific beam failure recovery is triggered, and if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the ... Instruct the BFR to generate a CE, otherwise trigger a TRP-specific Scheduling Request (SR) for beam failure recovery for each TRP for which a BFR has been triggered and not cancelled.

[0356] In some aspects, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the TRP-specific beam failure recovery MAC CE; otherwise, a BFR is triggered and a scheduling request (SR) for TRP-specific beam failure recovery is triggered for each TRP that has not been canceled; otherwise, if uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the shortened cell ... shortened cell-specific beam failure recovery MAC CE. Instructs the BFR to generate a CE, otherwise triggers a cell-specific Scheduling Request (SR) for beam failure recovery for each cell for which a BFR has been triggered and not cancelled.

[0357] In some aspects, the priority of the transmission / reception point specific beam failure recovery MAC CE is the same as the priority of the cell specific beam failure recovery MAC CE.

[0358] In some aspects, if uplink resources are available for a new transmission and, as a result of LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader and the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE and the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and, as a result of LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, or the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE or ... are shortened to the cell-specific beam failure recovery MAC CE. When the CE and its subheader can be accommodated, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam failure recovery MAC CE, otherwise it triggers a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which BFR is triggered and not canceled, and triggers a scheduling request (SR) for cell-specific beam failure recovery for each cell for which BFR is triggered and not canceled.

[0359] In some aspects, if uplink resources are available for a new transmission and as a result of LCP the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader and the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE and the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of LCP the uplink resources can accommodate a shortened cell-specific beam failure recovery MAC CE and its subheader and the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate the shortened cell-specific beam failure recovery MAC CE and the TRP-specific beam failure recovery MAC CE; otherwise, if uplink resources are available for a new transmission and as a result of LCP the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader or the TRP-specific beam failure recovery MAC When the MAC entity is capable of accommodating the shortened cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and assembly procedure to generate the cell-specific beam failure recovery MAC CE or the TRP-specific beam failure recovery MAC CE; otherwise, when uplink resources are available for a new transmission and the uplink resources are capable of accommodating the shortened cell-specific beam failure recovery MAC CE and its subheader as a result of the LCP, the MAC entity instructs the multiplexing and assembly entity to generate a shortened cell-specific beam failure recovery MAC CE; otherwise, the MAC entity triggers a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which BFR is triggered and not canceled, and triggers a scheduling request (SR) for cell-specific beam failure recovery for each cell for which BFR is triggered and not canceled.

[0360] In some aspects, a priority of the logical channel corresponding to the Tx / Rx specific beam failure recovery MAC CE is lower than a priority of a logical channel corresponding to a C-RNTI MAC CE or data from an uplink channel (UL-CCCH) and higher than a priority of a logical channel corresponding to a cell specific beam failure recovery MAC CE, or a priority of the logical channel corresponding to the Tx / Rx specific beam failure recovery MAC CE is the same as a priority of a logical channel corresponding to the cell specific beam failure recovery MAC CE, or a priority of the logical channel corresponding to the Tx / Rx specific beam failure recovery MAC CE is lower than a priority of a logical channel corresponding to the cell specific beam failure recovery MAC CE and higher than a priority of a logical channel corresponding to a Sidelink Configured Grant Confirmation MAC CE, or a priority of the logical channel corresponding to the Tx / Rx specific beam failure recovery MAC CE is the same as a priority of a logical channel corresponding to a Sidelink Configured Grant Confirmation MAC CE, or a priority of the logical channel corresponding to the Tx / Rx specific beam failure recovery MAC CE is higher than a priority of a logical channel corresponding to a Sidelink Configured Grant Confirmation MAC CE. the priority of the logical channel corresponding to the beam failure recovery MAC CE specific to the transmission / reception point is lower than the priority of the logical channel corresponding to the LBT failure MAC CE and higher than the priority of the logical channel corresponding to the LBT failure MAC CE, or the priority of the logical channel corresponding to the beam failure recovery MAC CE specific to the transmission / reception point is the same as the priority of the logical channel corresponding to the LBT failure MAC CE, or the priority of the logical channel corresponding to the beam failure recovery MAC CE specific to the transmission / reception point is lower than the priority of the logical channel corresponding to the LBT failure MAC CE and higher than the priority of the logical channel corresponding to the MAC CE for SL-BSR.

[0361] The above-mentioned embodiments are merely illustrative of the present invention, and the present invention is not limited thereto, and appropriate modifications can be made based on the above-mentioned embodiments. For example, each of the above-mentioned embodiments can be used alone, or one or more of the above-mentioned embodiments can be used in combination.

[0362] It should be noted that the above describes only the components or modules related to the present invention, but the present invention is not limited thereto. The beam failure information reporting device 2200 may further include other components or modules. For specific contents of these components or modules, reference may be made to the related art.

[0363] Furthermore, for convenience of explanation, Fig. 22 only exemplarily illustrates the connection relationships or signal directions between various components or modules, but it is clear to those skilled in the art that various related technologies such as bus connections can be used. The above-mentioned various components or modules may be implemented by hardware devices such as a processor, a memory, a transmitter, and a receiver, and the present invention is not limited thereto.

[0364] According to this embodiment, the terminal device indicates the information that the beam failure is detected or the beam failure recovery is triggered to the network device through another TRP of the cell to which the TRP in which the beam failure is detected or the beam failure recovery is triggered belongs. This allows the terminal device to implicitly indicate the information of the TRP to the network device, and the network device can take measures against the beam failure at the TRP level, thereby avoiding the waste of resources.

[0365] <Example 6> The embodiment of the present invention further provides a communication system, and may refer to FIG. 1. Description of the same contents as those in the first to fifth embodiments will be omitted.

[0366] In some embodiments, a communication system may include a terminal device and a network device.

[0367] A terminal device detects that a beam failure occurs in a link between the terminal device and a transmission / reception point (TRP) or that a beam failure recovery of the transmission / reception point is triggered, and generates a medium access control (MAC) control element (CE), where the MAC CE indicates information of the transmission / reception point where a beam failure is detected or where a beam failure recovery is triggered.

[0368] The network device receives information about the transmission / reception point where the beam failure has been detected or where beam failure recovery has been triggered.

[0369] In some aspects a communication system may include a terminal device and a network device.

[0370] The terminal device detects that a beam failure has occurred in a link between the transmitting / receiving point or that beam failure recovery has been triggered at the transmitting / receiving point, and instructs the network device via other transmitting / receiving points of the cell to which the transmitting / receiving point belongs that beam failure has been detected or beam failure recovery has been triggered.

[0371] The network device receives information that the beam failure has been detected or that beam failure recovery has been triggered.

[0372] An embodiment of the present invention further provides a network device, which may be, for example, a base station, but the present invention is not limited thereto and may be other network devices.

[0373] Fig. 23 is a schematic diagram of a network device according to an embodiment of the present invention. As shown in Fig. 23, the network device 2300 may include a processor 2310 (e.g., a central processing unit (CPU)) and a memory 2320, and the memory 2320 is connected to the processor 2310. The memory 2320 may store various data, and further stores an information processing program 2330, and executes the program 2330 under the control of the processor 2310.

[0374] For example, the processor 2310 may execute a program to realize the beam failure information receiving method described in the first to third embodiments. For example, the processor 2310 may be configured to receive a MAC CE transmitted by a terminal device, or to receive information indicating that a beam failure has been detected or that a beam failure recovery has been triggered, which is indicated by the terminal device via another transmission / reception point of the cell to which the transmission / reception point belongs. Here, the MAC CE indicates information of the transmission / reception point where a beam failure has been detected or that a beam failure recovery has been triggered.

[0375] Also, as shown in Fig. 23, the network device 2300 may further include a transceiver 2340 and an antenna 2350. The functions of the above members are similar to those of the prior art, and the description thereof will be omitted here. It is not necessary for the network device 2300 to include all the units shown in Fig. 23. Also, the network device 2300 may further include units not shown in Fig. 23, and may refer to the prior art.

[0376] The embodiment of the present invention further provides a terminal device, but the present invention is not limited thereto and may be other devices.

[0377] Fig. 24 is a schematic diagram of a terminal device according to an embodiment of the present invention. As shown in Fig. 24, the terminal device 2400 may include a processor 2410 and a memory 2420, where the memory 2420 stores data and programs and is connected to the processor 2410. It should be noted that this diagram is exemplary, and other types of structures may be used to supplement or replace this structure to realize communication functions or other functions.

[0378] For example, the processor 2410 may execute a program to realize the method for generating beam fault information described in the embodiment 1. For example, the processor 2310 may be configured to detect that a beam fault occurs in a link between a transmission / reception point (TRP) or that a beam fault recovery of the transmission / reception point is triggered, and generate a medium access control (MAC) control element (CE), where the MAC CE indicates information of the transmission / reception point where a beam fault is detected or where a beam fault recovery is triggered.

[0379] Also, for example, the processor 2410 may execute a program to realize the method for reporting beam failure information described in the embodiment 2. For example, the processor 2410 may be configured to detect that a beam failure has occurred in a link between a transmission / reception point or that a beam failure recovery of the transmission / reception point has been triggered, and to instruct a network device, via another transmission / reception point of a cell to which the transmission / reception point belongs, that a beam failure has been detected or that a beam failure recovery has been triggered.

[0380] For example, the processor 2410 may execute a program to realize the method for reporting beam failure information described in the third embodiment. For example, the processor 2410 may be configured to detect that a beam failure occurs in a link between a transmission / reception point or that a beam failure recovery of the transmission / reception point is triggered, and generate a MAC CE based on a carrier aggregation (CA) configuration and / or an uplink resource. Here, the MAC CE indicates information of the transmission / reception point where a beam failure is detected or where a beam failure recovery is triggered, or indicates information that a beam failure is detected or where a beam failure recovery is triggered to a network device via another transmission / reception point of a cell to which the transmission / reception point belongs.

[0381] Also, as shown in Fig. 24, the terminal device 2400 may further include a communication module 2430, an input unit 2440, a display 2450, a power supply 2460, and the like. Here, the functions of the above units are similar to those of the prior art, and the description thereof will be omitted here. It is not necessary for the terminal device 2400 to include all the units shown in Fig. 24. Also, the terminal device 2400 may further include units not shown in Fig. 24, and may refer to the prior art.

[0382] In an embodiment of the present invention, there is further provided a computer-readable program which, when executed in a terminal device, causes the terminal device to execute the beam fault information generating method described in embodiment 1 or the beam fault information reporting method described in embodiments 2 to 3.

[0383] An embodiment of the present invention further provides a storage medium having a computer-readable program stored therein, which, when executing the program, causes a terminal device to execute the beam fault information generating method described in embodiment 1 or the beam fault information reporting method described in embodiments 2 to 3.

[0384] The above-mentioned apparatus and method of the present invention may be realized by hardware or by a combination of hardware and software.The present invention relates to a computer readable program which, when executed by a logic unit, causes the logic unit to realize the above-mentioned apparatus or components, or to realize the above-mentioned various methods or steps.The present invention relates to a storage medium for storing the above-mentioned program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0385] Each processing method in each device described with reference to the embodiments of the present invention may be implemented by hardware, a software module executed by a processor, or a combination of both. For example, one or more of the functional block diagrams shown in the drawings, or one or more combinations of the functional block diagrams, may correspond to each software module in a computer program flow, or each hardware module. These software modules may correspond to each step shown in the drawings. These hardware modules may be realized by implementing these software modules in hardware, for example, using a field programmable gate array (FPGA).

[0386] The software module may be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a mobile hard disk, a CD-ROM, or any other form of storage medium known to those skilled in the art. The storage medium may be connected to the processor so that the processor reads information from the storage medium and writes information to the storage medium, or the storage medium may be a component of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal, or in a memory card inserted in the mobile terminal. For example, if the device (e.g., a mobile terminal) uses a MEGA-SIM card or a large capacity flash memory device with a relatively large capacity, the software module may be stored in the MEGA-SIM card or the large capacity flash memory device.

[0387] One or more of the functional blocks and / or one or more combinations of functional blocks in the functional block diagrams illustrated in the drawings may be implemented with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any suitable combination thereof to perform the functions described herein. One or more of the functional blocks and / or one or more combinations of functional blocks in the functional block diagrams illustrated in the drawings may be implemented with, for example, a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors in combination with a DSP communication, or any other configuration.

[0388] Although the present invention has been described above with reference to specific embodiments, the above description is merely illustrative and does not limit the scope of protection of the present invention. Various modifications and changes may be made to the present invention without departing from the spirit and principles of the present invention, and these modifications and changes are also within the scope of the present invention.

[0389] Furthermore, the following supplementary notes are disclosed regarding the embodiments including the above-mentioned examples. (Appendix 1) A method for generating beam obstruction information, comprising the steps of: A step of detecting that a beam failure occurs in a link between a terminal device and a transmission / reception point (TRP) or that a beam failure recovery of the transmission / reception point is triggered; A method comprising: a step of the terminal device generating a medium access control (MAC) control element (CE), the MAC CE indicating information of the transmission / reception point where a beam failure has been detected or where beam failure recovery has been triggered. (Appendix 2) 2. The method of claim 1, wherein the information of the transmission / reception point includes an index or identifier of the transmission / reception point at which a beam failure has been detected or at which beam failure recovery has been triggered. (Appendix 3) A value of 1 bit in the MAC CE indicates that a beam failure is detected or a beam failure recovery is triggered for a transmission / reception point corresponding to a control resource pool whose index is 0; The method described in Supplementary Note 2, wherein another value of the one bit indicates that a beam failure has been detected or a beam failure recovery has been triggered for a transmission / reception point corresponding to a control resource pool whose index is 1. (Appendix 4) A value of one bit in the MAC CE indicates that a beam failure is detected or a beam failure recovery is triggered for a transmission / reception point whose index is 0; The method described in Supplementary Note 2, wherein another value of the one bit indicates that a beam failure has been detected or a beam failure recovery has been triggered for a transmitting / receiving point whose index is 1. (Appendix 5) A value of one bit in the MAC CE indicates that a beam failure is detected or a beam failure recovery is triggered for a transmission / reception point corresponding to a beam failure detection reference signal set (BFD-RS set) whose index is 0, or indicates that a beam failure is detected or a beam failure recovery is triggered for all beams corresponding to a beam failure detection reference signal set (BFD-RS set) whose index is 0; The method described in Supplementary Note 2, wherein the other value of the one bit indicates that a beam failure has been detected or a beam failure recovery has been triggered for a transmitting / receiving point corresponding to a beam failure detection reference signal set (BFD-RS set) whose index is 1, or indicates that a beam failure has been detected or a beam failure recovery has been triggered for all beams corresponding to a beam failure detection reference signal set (BFD-RS set) whose index is 1. (Appendix 6) 6. The method of any of Supplementary Notes 2 to 5, wherein the R bit in the beam failure recovery (BFR) MAC CE or truncated beam failure recovery (truncated BFR) MAC CE is used to convey / indicate / represent the index of the transmission / reception point at which beam failure is detected or beam failure recovery is triggered. (Appendix 7) The value of one of the two bits in the MAC CE is No transmission / reception points have detected beam obstruction or triggered beam obstruction recovery; A beam failure is detected or a beam failure recovery is triggered for a transmission / reception point corresponding to a control resource pool whose index is 0; A beam failure is detected or a beam failure recovery is triggered for a transmission / reception point corresponding to a control resource pool whose index is 1; The method described in Supplementary Note 2, which indicates one or any combination of that a beam failure has been detected or a beam failure recovery has been triggered for both a transmission / reception point corresponding to a control resource pool with an index of 0 and a transmission / reception point corresponding to a control resource pool with an index of 1. (Appendix 8) The value of one of the two bits in the MAC CE is No transmission / reception points have detected beam obstruction or triggered beam obstruction recovery; A beam failure has been detected or a beam failure recovery has been triggered for the transmission / reception point with index 0; A beam failure has been detected or a beam failure recovery has been triggered for a transmission / reception point whose index is 1; The method described in Appendix 2, wherein a transmitting / receiving point with an index of 0 and a transmitting / receiving point with an index of 1 indicate one or any combination of that a beam failure has been detected or that a beam failure recovery has been triggered. (Appendix 9) The value of one of the two bits in the MAC CE is No transmission / reception points have detected beam obstruction or triggered beam obstruction recovery; A beam failure is detected or a beam failure recovery is triggered for a transmitting / receiving point corresponding to a beam failure detection reference signal set (BFD-RS set) having an index of 0, or a beam failure is detected or a beam failure recovery is triggered for all beams corresponding to a beam failure detection reference signal set (BFD-RS set) having an index of 0; A beam failure is detected or a beam failure recovery is triggered for a transmitting / receiving point corresponding to a beam failure detection reference signal set (BFD-RS set) whose index is 1, or a beam failure is detected or a beam failure recovery is triggered for all beams corresponding to a beam failure detection reference signal set (BFD-RS set) whose index is 1; The method described in Supplementary Note 2, indicating one or any combination of the following: beam failure has been detected or beam failure recovery has been triggered for both transmission / reception points corresponding to a beam failure detection reference signal set (BFD-RS set) with index 0 and a beam failure detection reference signal set (BFD-RS set) with index 1; or beam failure has been detected or beam failure recovery has been triggered for all beams corresponding to a beam failure detection reference signal set (BFD-RS set) with index 0 and all beams corresponding to a beam failure detection reference signal set (BFD-RS set) with index 1. (Appendix 10) The method of any of Supplementary Notes 2, 7 to 9, wherein the R bit and AC field in the beam failure recovery MAC CE or the shortened beam failure recovery MAC CE are used to convey / indicate / represent the index of the transmission / reception point at which beam failure is detected or beam failure recovery is triggered. (Appendix 11) 11. The method of any of claims 1 to 10, wherein the MAC CE includes a type of beam failure detected or a type of beam failure recovery triggered. (Appendix 12) A bit in the MAC CE indicates a type of detected beam failure or a type of triggered beam failure recovery; One value of the one bit indicates that a beam failure of a cell-specific or all beams is detected, or a beam failure recovery of a cell-specific or all beams is triggered, and another value of the one bit indicates that a beam failure of a transmission / reception point (TRP)-specific or some beams is detected, or a beam failure recovery of a transmission / reception point-specific or some beams is triggered, or One value of the one bit indicates that a beam failure of a cell-specific or all beams is detected or a beam failure recovery of a cell-specific or all beams is triggered, and another value of the one bit indicates that a beam failure of a non-cell-specific or non-all beams is detected or a beam failure recovery of a non-cell-specific or non-all beams is triggered, or The method of claim 11, wherein one value of the one bit indicates that a beam failure of a TRP-specific or a portion of a beam has been detected or a beam failure recovery of a TRP-specific or a portion of a beam has been triggered, and another value of the one bit indicates that a beam failure of a non-TRP-specific or non-portion of a beam has been detected or a beam failure recovery of a non-TRP-specific or non-portion of a beam has been triggered. (Appendix 13) The method described in Supplementary Note 12, wherein the R bit in the beam failure recovery MAC CE or truncated beam failure recovery (truncated BFR) MAC CE is used to convey / indicate / represent the type of beam failure detected or the type of beam failure recovery triggered. (Appendix 14) Two bits in the MAC CE indicate the type of beam failure detected or the type of beam failure recovery triggered; One value of the two bits indicates that beam failure of a cell-specific or all beams is not detected, or beam failure recovery of a cell-specific or all beams is not triggered, and beam failure of a TRP-specific or some beams is not detected, or beam failure recovery of a TRP-specific or some beams is not triggered; another value of the two bits indicates that beam failure of a cell-specific or all beams is detected, or beam failure recovery of a cell-specific or all beams is triggered; another value of the two bits indicates that beam failure of a cell-specific or all beams is detected, or beam failure recovery of a TRP-specific or some beams is triggered; and another value of the two bits indicates that beam failure of a cell-specific or all beams is detected, or beam failure recovery of a cell-specific or all beams is triggered, and beam failure of a TRP-specific or some beams is detected, or beam failure recovery of a TRP-specific or some beams is triggered; One value of the two bits indicates that no beam failure of a cell-specific or all beams is detected, or beam failure recovery of a cell-specific or all beams is not triggered, and no beam failure of a non-cell-specific or non-all beams is detected, or beam failure recovery of a non-cell-specific or non-all beams is not triggered; another value of the two bits indicates that beam failure of a cell-specific or all beams is detected, or beam failure recovery of a cell-specific or non-all beams is triggered; another value of the two bits indicates that beam failure of a cell-specific or all beams is detected, or beam failure recovery of a cell-specific or non-all beams is triggered, and another value of the two bits indicates that beam failure of a cell-specific or all beams is detected, or beam failure recovery of a cell-specific or non-all beams is triggered, and beam failure of a non-cell-specific or non-all beams is detected, or beam failure recovery of a non-cell-specific or non-all beams is triggered; The method of claim 11, wherein one value of the two bits indicates that a beam failure of a non-TRP-specific or non-some beam has not been detected, or a beam failure recovery of a non-TRP-specific or non-some beam has not been triggered, and a beam failure of a TRP-specific or non-some beam has not been detected, or a beam failure recovery of a TRP-specific or non-some beam has not been triggered; another value of the two bits indicates that a beam failure of a non-TRP-specific or non-some beam has been detected, or a beam failure recovery of a non-TRP-specific or non-some beam has been triggered; another value of the two bits indicates that a beam failure of a TRP-specific or non-some beam has been detected, or a beam failure recovery of a TRP-specific or non-some beam has been triggered; and another value of the two bits indicates that a beam failure of a non-TRP-specific or non-some beam has been detected, or a beam failure recovery of a non-TRP-specific or non-some beam has been triggered, and a beam failure of a TRP-specific or non-some beam has been detected, or a beam failure recovery of a TRP-specific or non-some beam has been triggered. (Appendix 15) The method described in Supplementary Note 14, wherein the R bit and AC field in the beam failure recovery MAC CE or truncated beam failure recovery (truncated BFR) MAC CE are used to convey / indicate / represent the type of beam failure detected or the type of beam failure recovery triggered. (Appendix 16) A method as described in any of Supplementary Notes 1 to 15, wherein the MAC CE includes at least one or any combination of information of a cell to which a transmitting / receiving point belongs where beam failure has been detected or beam failure recovery has been triggered, information on whether a candidate beam has been found, and information on the candidate beam. (Appendix 17) 17. The method of any of claims 1 to 16, wherein the MAC CE is identified by a MAC subheader of a Logical Channel Identifier (LCID) or an extended Logical Channel Identifier (eLCID). (Appendix 18) The terminal device further includes a step of transmitting the MAC CE to a network device; A method according to any one of Supplementary Notes 1 to 17, wherein the MAC CE is forwarded to the network device via another transmission / reception point of the cell to which the transmission / reception point belongs, or the MAC CE is forwarded to the network device via a transmission / reception point that is co-located with the transmission / reception point and belongs to a cell other than the cell to which the transmission / reception point belongs, or the MAC CE is reported to the network device via a cell other than the cell to which the transmission / reception point belongs. (Appendix 19) The terminal device Uplink grants for TRPs where TRP-specific beam obstruction is not detected for the cell to which the TRP belongs, where TRP-specific beam obstruction is detected; An uplink grant of a TRP that is co-located with a TRP in which a beam obstruction specific to the TRP is detected and that belongs to a cell different from the cell to which the TRP in which the beam obstruction specific to the TRP is detected belongs; A method according to any one of appendices 1 to 18, wherein the MAC CE is transmitted using one of the uplink grants of a cell other than the cell to which the TRP in which the TRP-specific beam failure is detected belongs. (Appendix 20) A method according to any one of Supplementary Notes 1 to 19, wherein, when there are multiple available resources, the terminal device selects an uplink grant based on a predefined or network configuration and transmits the MAC CE, or selects an uplink grant based on implementation and transmits the MAC CE, or randomly selects an uplink grant and transmits the MAC CE. (Appendix 21) The step of generating a medium access control (MAC) control element (CE) by the terminal device includes: A medium access control (MAC) entity of the terminal device instructs a multiplexing and reassembly procedure to generate a TRP-specific MAC CE; 21. The method of any one of claims 1 to 20, wherein the MAC CE includes a MAC CE specific to the TRP, and the TRP specific MAC CE is different from a cell specific MAC CE. (Appendix 22) 22. The method of claim 21, wherein the TRP-specific MAC CE is generated using a procedure independent of the procedure for generating the cell-specific MAC CE. (Appendix 23) The shortened TRP-specific beam failure recovery MAC CE is supported, The procedure for generating a TRP-specific beam failure recovery MAC CE is as follows: If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the shortened TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate the shortened TRP-specific beam failure recovery MAC CE; Otherwise, for each TRP for which a BFR is triggered and not canceled, triggering a scheduling request (SR) for TRP-specific beam failure recovery. (Appendix 24) The shortened TRP-specific beam failure recovery MAC CE is not supported, The procedure for generating the TRP-specific beam failure recovery MAC CE comprises: If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate the TRP-specific beam failure recovery MAC CE; Otherwise, triggering a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which BFR is triggered and not canceled. (Appendix 25) 22. The method of claim 21, wherein the cell-specific MAC CE and the TRP-specific MAC CE are generated using a single procedure. (Appendix 26) The shortened TRP-specific beam failure recovery MAC CE is supported, 26. The method of claim 25, wherein the TRP-specific beam failure recovery MAC CE is preferentially generated. (Appendix 27) If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the shortened TRP-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate the shortened TRP-specific beam fault recovery MAC CE; Otherwise, for each TRP for which a BFR has been triggered and not cancelled, trigger a TRP-specific scheduling request (SR) for beam failure recovery; If uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs a multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam fault recovery MAC CE; Otherwise, the method described in Supplementary Note 26 triggers a cell-specific scheduling request (SR) for beam failure recovery for each cell for which BFR is triggered and not canceled. (Appendix 28) If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs a multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the shortened TRP-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate the shortened TRP-specific beam fault recovery MAC CE; Otherwise, for each TRP for which a BFR has been triggered and not cancelled, trigger a TRP-specific scheduling request (SR) for beam failure recovery; When uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam fault recovery MAC CE; Otherwise, the method described in Supplementary Note 26 triggers a cell-specific scheduling request (SR) for beam failure recovery for each cell for which BFR is triggered and not canceled. (Appendix 29) The shortened TRP-specific beam failure recovery MAC CE is supported, 26. The method of claim 25, wherein the cell-specific beam failure recovery MAC CE is preferentially generated. (Appendix 30) If uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs a multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam fault recovery MAC CE; otherwise, trigger a cell-specific scheduling request (SR) for beam failure recovery for each cell for which a BFR has been triggered and not cancelled; If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the shortened TRP-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate the shortened TRP-specific beam fault recovery MAC CE; Otherwise, the method described in Supplementary Note 29 triggers a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which the BFR is triggered and not canceled. (Appendix 31) If uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs a multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader as a result of the LCP, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam fault recovery MAC CE; otherwise, trigger a cell-specific scheduling request (SR) for beam failure recovery for each cell for which a BFR has been triggered and not cancelled; When uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate a shortened TRP-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened TRP-specific beam fault recovery MAC CE; Otherwise, the method described in Supplementary Note 29 triggers a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which the BFR is triggered and not canceled. (Appendix 32) The shortened TRP-specific beam failure recovery MAC CE is supported, The method of claim 25, wherein the priority of the TRP-specific beam failure recovery MAC CE is the same as the priority of the cell-specific beam failure recovery MAC CE. (Appendix 33) If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader and the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE and the TRP-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, or the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE or the TRP-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate a shortened cell-specific beam fault recovery MAC CE and its subheader and a shortened TRP-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam fault recovery MAC CE and a shortened TRP-specific beam fault recovery MAC CE, Otherwise, when uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate a shortened cell-specific beam fault recovery MAC CE and its subheader, or a shortened TRP-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam fault recovery MAC CE or a shortened TRP-specific beam fault recovery MAC CE, Otherwise, trigger a TRP-specific scheduling request (SR) for beam failure recovery for each TRP for which BFR is triggered and not canceled, and trigger a cell-specific scheduling request (SR) for beam failure recovery for each cell for which BFR is triggered and not canceled, as described in Supplementary Note 32. (Appendix 34) The shortened TRP-specific beam failure recovery MAC CE is not supported, 26. The method of claim 25, wherein the TRP-specific beam failure recovery MAC CE is preferentially generated. (Appendix 35) If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; Otherwise, trigger a TRP-specific scheduling request (SR) for beam failure recovery for each TRP for which a BFR has been triggered and not cancelled; If uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs a multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam fault recovery MAC CE; Otherwise, the method described in Supplementary Note 34 triggers a cell-specific scheduling request (SR) for beam failure recovery for each cell for which BFR is triggered and not canceled. (Appendix 36) The shortened TRP-specific beam failure recovery MAC CE is not supported, 26. The method of claim 25, wherein the cell-specific beam failure recovery MAC CE is preferentially generated. (Appendix 37) If uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs a multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam fault recovery MAC CE; otherwise, trigger a cell-specific scheduling request (SR) for beam failure recovery for each cell for which a BFR has been triggered and not cancelled; If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; Otherwise, the method described in Supplementary Note 36 triggers a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which a BFR is triggered and not canceled. (Appendix 38) If uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs a multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader as a result of the LCP, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; Otherwise, for each TRP for which a BFR has been triggered and not cancelled, trigger a TRP-specific scheduling request (SR) for beam failure recovery; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam fault recovery MAC CE; Otherwise, the method described in Supplementary Note 36 triggers a cell-specific scheduling request (SR) for beam failure recovery for each cell for which BFR is triggered and not canceled. (Appendix 39) The shortened TRP-specific beam failure recovery MAC CE is not supported, The method of claim 25, wherein the priority of the TRP-specific beam failure recovery MAC CE is the same as the priority of the cell-specific beam failure recovery MAC CE. (Appendix 40) If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader and the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE and the TRP-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, or the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE or the TRP-specific beam failure recovery MAC CE; Otherwise, for each TRP for which BFR is triggered and not cancelled, trigger a TRP-specific scheduling request (SR) for beam failure recovery, and for each cell for which BFR is triggered and not cancelled, trigger a cell-specific scheduling request (SR) for beam failure recovery, as described in Supplementary Note 39. (Appendix 41) The priority of the logical channel corresponding to the transmission / reception point specific beam failure recovery MAC CE is lower than the priority of the logical channel corresponding to the C-RNTI MAC CE or data from an uplink channel (data from UL-CCCH), and is higher than the priority of the logical channel corresponding to the cell specific beam failure recovery MAC CE, or The priority of the logical channel corresponding to the transmission / reception point specific beam fault recovery MAC CE is the same as the priority of the logical channel corresponding to the cell specific beam fault recovery MAC CE; or The priority of the logical channel corresponding to the transmission / reception point specific beam failure recovery MAC CE is lower than the priority of the logical channel corresponding to the cell specific beam failure recovery MAC CE and higher than the priority of the logical channel corresponding to a sidelink configured grant confirmation MAC CE, or The priority of the logical channel corresponding to the beam failure recovery MAC CE specific to the transmission / reception point is the same as the priority of the logical channel corresponding to a sidelink configured grant confirmation MAC CE; or The priority of the logical channel corresponding to the beam failure recovery MAC CE specific to the transmission / reception point is lower than the priority of the logical channel corresponding to the sidelink configured grant confirmation MAC CE and higher than the priority of the logical channel corresponding to the LBT failure MAC CE; or The priority of the logical channel corresponding to the beam failure recovery MAC CE specific to the transmitting / receiving point is equal to the priority of the logical channel corresponding to the LBT failure MAC CE; or A method as claimed in any one of appendices 21 to 40, wherein the priority of a logical channel corresponding to a beam failure recovery MAC CE specific to the transmitting / receiving point is lower than the priority of a logical channel corresponding to an LBT failure MAC CE and higher than the priority of a logical channel corresponding to a MAC CE for SL-BSR. (Appendix 42) A method as described in any of Supplementary Notes 1 to 41, wherein the candidate beam information includes a synchronization signal block (SSB) index or a channel state information reference signal (CSI-RS) index, or the candidate beam information indicates the order in which the candidate beams appear in the configured candidate beams. (Appendix 43) The candidate beams are The candidate beam is included in a candidate beam list configured for the TRP in which a TRP-specific beam failure is detected, or is included in a candidate beam / BFD-RS list configured for a cell to which the TRP in which a TRP-specific beam failure is detected belongs, or is included in a candidate beam / BFD-RS list configured for another TRP in which the TRP in which a TRP-specific beam failure is detected belongs; The received power of the reference signal (RSRP) is higher than a configured threshold; The signal-to-interference-and-noise ratio (SINR) is higher than a configured threshold; The received signal strength indicator (RSSI) is higher than a configured threshold; The beam / RS paired with the candidate beam is included in a candidate beam list configured for the TRP in which a TRP-specific beam failure is detected, or the beam / RS paired with the candidate beam is included in a candidate beam / BFD-RS list configured for the cell to which the TRP in which a TRP-specific beam failure is detected belongs, or the beam / RS paired with the candidate beam is included in a candidate beam / BFD-RS list configured for another TRP in the cell to which the TRP in which a TRP-specific beam failure is detected belongs; The method described in Supplementary Note 42, wherein at least one condition is satisfied: a measurement value of a beam / RS paired with the candidate beam is higher than a configured threshold. (Appendix 44) The method described in Supplementary Note 42, in which the terminal device selects one or N of multiple candidate beams based on implementation or arbitrarily, or selects one or N of the beams with the highest measurement values, or selects one or N of the beams with the highest measurement values ​​and whose paired beams / RSs have measurement values ​​higher than a configured threshold, or selects one or N of the beams with the highest measurement values ​​and whose paired beams / RSs have the highest measurement values, where N is an integer greater than 1. (Appendix 45) A method for reporting beam failure information, comprising: A step of detecting that a beam failure occurs in a link between a terminal device and a transmission / reception point (TRP) or that a beam failure recovery of the transmission / reception point is triggered; A method comprising the step of instructing a network device that a beam failure has been detected or a beam failure recovery has been triggered via another transmission / reception point of a cell to which the transmission / reception point belongs. (Appendix 46) The method described in Supplementary Note 45, wherein the information that the beam failure has been detected or the beam failure recovery has been triggered is included in a beam failure recovery MAC CE specific to a transmitting / receiving point. (Appendix 47) 47. The method of claim 46, wherein the information that a beam failure has been detected or a beam failure recovery has been triggered includes an indication of whether a candidate beam has been found. (Appendix 48) The method described in Supplementary Note 47, wherein one value of one bit of the information in which beam failure has been detected or beam failure recovery has been triggered indicates that a candidate beam has been configured and found, or indicates that a candidate beam has been configured and information on the candidate beam is included in the MAC CE, or indicates that information on the candidate beam is included in the MAC CE. (Appendix 49) 49. The method of any of claims 45 to 48, wherein the information that a beam failure has been detected or a beam failure recovery has been triggered further includes information of a candidate beam. (Appendix 50) The method of claim 49, wherein the information about the candidate beam indicates a reference signal. (Appendix 51) The method of claim 49 or 50, wherein the candidate beam information includes a synchronization signal block (SSB) index or a channel state information reference signal (CSI-RS) index, or the candidate beam information indicates an order in which the candidate beams appear in the configured candidate beams. (Appendix 52) The candidate beams are The candidate beam is included in a candidate beam list configured for the TRP in which a TRP-specific beam failure is detected, or is included in a candidate beam / BFD-RS list configured for a cell to which the TRP in which a TRP-specific beam failure is detected belongs, or is included in a candidate beam / BFD-RS list configured for another TRP in which the TRP in which a TRP-specific beam failure is detected belongs; The received power of the reference signal (RSRP) is higher than a configured threshold; The signal-to-interference-and-noise ratio (SINR) is higher than a configured threshold; The received signal strength indicator (RSSI) is higher than a configured threshold; The beam / RS paired with the candidate beam is included in a candidate beam list configured for the TRP in which a TRP-specific beam failure is detected, or the beam / RS paired with the candidate beam is included in a candidate beam / BFD-RS list configured for the cell to which the TRP in which a TRP-specific beam failure is detected belongs, or the beam / RS paired with the candidate beam is included in a candidate beam / BFD-RS list configured for another TRP in the cell to which the TRP in which a TRP-specific beam failure is detected belongs; The method of claim 49 or 50, wherein at least one condition is satisfied: a measurement value of a beam / RS paired with the candidate beam is higher than a configured threshold. (Appendix 53) The method according to claim 49 or 50, wherein the terminal device selects one or N of a plurality of candidate beams based on implementation or arbitrarily, or selects one or N of the beams with the highest measurement values, or selects one or N of the beams with the highest measurement values ​​and whose paired beams / RSs have measurement values ​​higher than a configured threshold, or selects one or N of the beams with the highest measurement values ​​and whose paired beams / RSs have the highest measurement values, where N is an integer greater than 1. (Appendix 54) A method as described in any of Supplementary Notes 45 to 53, wherein the information indicating that beam failure has been detected or beam failure recovery has been triggered further includes beam / RS information that pairs with the selected candidate beam. (Appendix 55) 55. The method of any of claims 46 to 54, wherein the MAC CE is identified by a MAC subheader of a Logical Channel Identifier (LCID) or an extended Logical Channel Identifier (eLCID). (Appendix 56) The medium access control (MAC) entity instructs a multiplexing and reassembly procedure to generate a transmission / reception point (TRP) specific beam failure recovery MAC CE; 56. The method of any of claims 46 to 55, wherein the TRP-specific beam failure recovery MAC CE is different from a cell-specific beam failure recovery MAC CE. (Appendix 57) 57. The method of claim 56, wherein a TRP-specific MAC CE is generated using a procedure independent of the cell-specific MAC CE procedure. (Appendix 58) The procedure for generating the TRP-specific beam failure recovery MAC CE comprises: If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate the TRP-specific beam failure recovery MAC CE; Otherwise, triggering a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which BFR is triggered and not canceled. (Appendix 59) 57. The method of claim 56, wherein a cell-specific MAC CE and the TRP-specific MAC CE are generated using a single procedure. (Appendix 60) 59. The method of claim 59, wherein the TRP-specific beam failure recovery MAC CE is preferentially generated. (Appendix 61) The preferential generation of the TRP-specific beam failure recovery MAC CE includes: If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; Otherwise, triggering a TRP-specific scheduling request (SR) for beam failure recovery for each TRP for which a BFR has been triggered and not cancelled; If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs a multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, when uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam fault recovery MAC CE; otherwise, triggering a cell-specific scheduling request (SR) for beam failure recovery for each cell for which BFR has been triggered and not canceled. (Appendix 62) 60. The method of claim 59, wherein the cell-specific beam failure recovery MAC CE is preferentially generated. (Appendix 63) The preferential generation of the cell-specific beam failure recovery MAC CE includes: If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs a multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; otherwise, when uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam fault recovery MAC CE; otherwise, triggering a cell-specific beam failure recovery scheduling request (SR) for each cell for which a BFR has been triggered and not cancelled; If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; Otherwise, triggering a scheduling request (SR) for TRP-specific beam failure recovery for each TRP for which BFR is triggered and not canceled. (Appendix 64) If uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs a multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and the uplink resources can accommodate the TRP-specific beam failure recovery MAC CE and its subheader as a result of the LCP, the MAC entity instructs the multiplexing and reassembly procedure to generate the TRP-specific beam failure recovery MAC CE; Otherwise, for each TRP for which a BFR has been triggered and not cancelled, trigger a TRP-specific scheduling request (SR) for beam failure recovery; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam fault recovery MAC CE; Otherwise, the method described in Supplementary Note 62 triggers a cell-specific scheduling request (SR) for beam failure recovery for each cell for which BFR is triggered and not canceled. (Appendix 65) The method described in Supplementary Note 59, wherein the priority of the transmission / reception point-specific beam failure recovery MAC CE is the same as the priority of the cell-specific beam failure recovery MAC CE. (Appendix 66) If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader and the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE and the TRP-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, or the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE or the TRP-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam fault recovery MAC CE; Otherwise, trigger a TRP-specific scheduling request (SR) for beam failure recovery for each TRP for which BFR is triggered and not canceled, and trigger a cell-specific scheduling request (SR) for beam failure recovery for each cell for which BFR is triggered and not canceled, as described in Supplementary Note 65. (Appendix 67) If uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader and the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE and the TRP-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and the uplink resources can accommodate the shortened cell-specific beam failure recovery MAC CE and its subheader and the TRP-specific beam failure recovery MAC CE and its subheader as a result of the LCP, the MAC entity instructs the multiplexing and reassembly entity to generate the shortened cell-specific beam failure recovery MAC CE and the TRP-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP, the uplink resources can accommodate the cell-specific beam failure recovery MAC CE and its subheader, or the TRP-specific beam failure recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly procedure to generate the cell-specific beam failure recovery MAC CE or the TRP-specific beam failure recovery MAC CE; Otherwise, when uplink resources are available for a new transmission and as a result of the LCP the uplink resources can accommodate a shortened cell-specific beam fault recovery MAC CE and its subheader, the MAC entity instructs the multiplexing and reassembly entity to generate a shortened cell-specific beam fault recovery MAC CE; Otherwise, trigger a TRP-specific scheduling request (SR) for beam failure recovery for each TRP for which BFR is triggered and not canceled, and trigger a cell-specific scheduling request (SR) for beam failure recovery for each cell for which BFR is triggered and not canceled, as described in Supplementary Note 65. (Appendix 68) The priority of the logical channel corresponding to the transmission / reception point specific beam failure recovery MAC CE is lower than the priority of the logical channel corresponding to the C-RNTI MAC CE or data from an uplink channel (data from UL-CCCH), and is higher than the priority of the logical channel corresponding to the cell specific beam failure recovery MAC CE, or The priority of the logical channel corresponding to the transmission / reception point specific beam fault recovery MAC CE is the same as the priority of the logical channel corresponding to the cell specific beam fault recovery MAC CE; or The priority of the logical channel corresponding to the transmission / reception point specific beam failure recovery MAC CE is lower than the priority of the logical channel corresponding to the cell specific beam failure recovery MAC CE and higher than the priority of the logical channel corresponding to a sidelink configured grant confirmation MAC CE, or The priority of the logical channel corresponding to the beam failure recovery MAC CE specific to the transmission / reception point is the same as the priority of the logical channel corresponding to a sidelink configured grant confirmation MAC CE; or The priority of the logical channel corresponding to the beam failure recovery MAC CE specific to the transmission / reception point is lower than the priority of the logical channel corresponding to the sidelink configured grant confirmation MAC CE and higher than the priority of the logical channel corresponding to the LBT failure MAC CE; or The priority of the logical channel corresponding to the beam failure recovery MAC CE specific to the transmitting / receiving point is equal to the priority of the logical channel corresponding to the LBT failure MAC CE; or A method as claimed in any one of appendices 47 to 67, wherein the priority of a logical channel corresponding to a beam failure recovery MAC CE specific to the transmitting / receiving point is lower than the priority of a logical channel corresponding to an LBT failure MAC CE and higher than the priority of a logical channel corresponding to a MAC CE for SL-BSR. (Appendix 69) A method for reporting beam failure information, comprising: A terminal device detects that a beam failure occurs in a link between the terminal device and a transmitting / receiving point, or that a beam failure recovery of the transmitting / receiving point is triggered; A method comprising: generating a MAC CE based on a carrier aggregation (CA) configuration and / or uplink resources, the MAC CE indicating information of the transmission / reception point where beam failure has been detected or beam failure recovery has been triggered, or instructing a network device via another transmission / reception point of a cell to which the transmission / reception point belongs, information that beam failure has been detected or beam failure recovery has been triggered. (Appendix 70) When the terminal device does not configure carrier aggregation, it generates a MAC CE, and the MAC CE indicates information of the transmission / reception point where a beam failure is detected or a beam failure recovery is triggered; The method described in Supplementary Note 69, in which the terminal device, when carrier aggregation is configured, indicates to the network device information that beam failure has been detected or beam failure recovery has been triggered via other transmission / reception points of the cell to which the transmission / reception point belongs. (Appendix 71) When the terminal device is configured with carrier aggregation and the uplink resource can accommodate a MAC CE, the terminal device generates a MAC CE, and the MAC CE indicates information of the transmission / reception point where a beam failure is detected or a beam failure recovery is triggered; The method described in Supplementary Note 69, in which the terminal device indicates to the network device information that beam failure has been detected or beam failure recovery has been triggered via another transmission / reception point of the cell to which the transmission / reception point belongs when carrier aggregation is not configured, or when carrier aggregation is configured and the uplink resources cannot accommodate the MAC CE. (Appendix 72) A method for receiving beam failure information, comprising the steps of: A method comprising the steps of: a network device receiving a MAC CE transmitted by a terminal device, or receiving information that a beam failure has been detected or a beam failure recovery has been triggered, indicated by the terminal device via another transmission / reception point of a cell to which the transmission / reception point belongs, wherein the MAC CE indicates information of the transmission / reception point where a beam failure has been detected or a beam failure recovery has been triggered. (Appendix 73) A terminal device including a memory in which a computer program is stored and a processor, wherein the processor is configured to execute the computer program to realize a method for generating beam fault information described in any of Appendices 1 to 45, or a method for reporting beam fault information described in any of Appendices 46 to 71. (Appendix 74) A network device comprising: a memory having a computer program stored therein; and a processor, the processor being configured to execute the computer program to realize the beam fault information receiving method described in Appendix 72. (Appendix 75) A communication system including a terminal device and a network device, The terminal device detects that a beam failure occurs in a link between the terminal device and a transmission / reception point (TRP) or that a beam failure recovery of the transmission / reception point is triggered, and generates a medium access control (MAC) control element (CE), and the MAC CE indicates information of the transmission / reception point where a beam failure is detected or where a beam failure recovery is triggered; A communication system in which the network device receives information of the transmission / reception point where the beam failure has been detected or beam failure recovery has been triggered. (Appendix 76) A communication system including a terminal device and a network device, The terminal device detects that a beam failure has occurred in a link between the transmission / reception point and the terminal device, or that a beam failure recovery of the transmission / reception point has been triggered, and notifies the network device of the beam failure detection or beam failure recovery triggered information via another transmission / reception point of the cell to which the transmission / reception point belongs; A communication system in which the network device receives information that the beam failure has been detected or beam failure recovery has been triggered.

Claims

1. A beam obstruction information generating device including a memory in which a program is stored and a processor, The processor, Detecting that a beam failure recovery has been triggered for a transmitting / receiving point; Executing the program to realize: if at least one beam failure recovery has been triggered and not canceled for the transmitting / receiving point, and evaluation of the candidate beams has been completed, generating a beam failure recovery medium access control control element, the beam failure recovery medium access control control element indicating information of the transmitting / receiving point for which beam failure recovery has been triggered; One value of the one bit in the beam failure recovery medium access control control element indicates that beam failure recovery is triggered for a transmission / reception point corresponding to a control resource pool whose index is 0, and another value of the one bit indicates that beam failure recovery is triggered for a transmission / reception point corresponding to a control resource pool whose index is 1, or An apparatus, wherein one value of a bit in the beam failure recovery medium access control control element indicates that a beam failure has been detected for one corresponding to a beam failure detection reference signal set having a first index, and another value of the bit indicates that a beam failure has been detected for one corresponding to a beam failure detection reference signal set having a second index.

2. The apparatus of claim 1 , wherein the information of the transmission / reception point includes an index or identifier of the transmission / reception point at which a beam failure is detected or a beam failure recovery is triggered.

3. The value of one of the two bits in the beam failure recovery medium access control element is: No transmission / reception points have detected beam obstruction or triggered beam obstruction recovery; A beam failure is detected or a beam failure recovery is triggered for a transmission / reception point corresponding to a control resource pool whose index is 0; A beam failure is detected or a beam failure recovery is triggered for a transmission / reception point corresponding to a control resource pool whose index is 1; For a transmission / reception point corresponding to a control resource pool with an index of 0 and a transmission / reception point corresponding to a control resource pool with an index of 1, a beam failure is detected or a beam failure recovery is triggered, or any combination thereof; or The value of one of the two bits in the beam failure recovery medium access control element is: No transmission / reception points have detected beam obstruction or triggered beam obstruction recovery; A beam failure is detected or a beam failure recovery is triggered for a transmission / reception point corresponding to a beam failure detection reference signal set whose index is 0, or a beam failure recovery is triggered for all beams corresponding to a beam failure detection reference signal set whose index is 0; A beam failure is detected or a beam failure recovery is triggered for a transmission / reception point corresponding to a beam failure detection reference signal set whose index is 1, or a beam failure is detected or a beam failure recovery is triggered for all beams corresponding to a beam failure detection reference signal set whose index is 1; The device of claim 2, indicating one or any combination of: beam failure has been detected or beam failure recovery has been triggered for both transmission and reception points corresponding to a beam failure detection reference signal set with index 0 and a beam failure detection reference signal set with index 1; or beam failure has been detected or beam failure recovery has been triggered for all beams corresponding to a beam failure detection reference signal set with index 0 and all beams corresponding to a beam failure detection reference signal set with index 1.

4. The R bit in the beam failure recovery medium access control control element or the shortened beam failure recovery medium access control control element is used to convey / indicate / represent the index of the transmission / reception point where a beam failure is detected or where beam failure recovery is triggered, or The apparatus of claim 2, wherein the R bit and AC field in the beam failure recovery medium access control control element or the shortened beam failure recovery medium access control control element are used to convey / indicate / represent the index of the transmission / reception point at which a beam failure is detected or beam failure recovery is triggered.

5. The apparatus of claim 1 , wherein the beam failure recovery medium access control control element comprises a type of beam failure detected or a type of beam failure recovery triggered.

6. a bit in the beam fault recovery medium access control element indicating a type of beam fault detected or a type of beam fault recovery triggered; One value of the one bit indicates that a beam failure of a cell-specific or all beams is detected, or a beam failure recovery of a cell-specific or all beams is triggered, and another value of the one bit indicates that a beam failure of a transmission / reception point-specific or some beams is detected, or a beam failure recovery of a transmission / reception point-specific or some beams is triggered, or One value of the one bit indicates that a beam failure of a cell-specific or all beams is detected or a beam failure recovery of a cell-specific or all beams is triggered, and another value of the one bit indicates that a beam failure of a non-cell-specific or non-all beams is detected or a beam failure recovery of a non-cell-specific or non-all beams is triggered, or The device of claim 5, wherein one value of the one bit indicates that a beam failure of a transmitting / receiving point-specific or some beams has been detected, or a beam failure recovery of a transmitting / receiving point-specific or some beams has been triggered, and another value of the one bit indicates that a beam failure of a non-transmitting / receiving point-specific or beam that is not a part of a beam has been detected, or a beam failure recovery of a non-transmitting / receiving point-specific or beam that is not a part of a beam has been triggered.

7. Two bits in the beam fault recovery medium access control control element indicate a type of beam fault detected or a type of beam fault recovery triggered; One value of the two bits indicates that beam failure of a cell-specific or all beams has not been detected, or beam failure recovery of a cell-specific or all beams has not been triggered, and beam failure of a transmission / reception point-specific or some beams has not been detected, or beam failure recovery of a transmission / reception point-specific or some beams has not been triggered; another value of the two bits indicates that beam failure of a cell-specific or all beams has been detected, or beam failure recovery of a cell-specific or all beams has been triggered; another value of the two bits indicates that beam failure of a cell-specific or all beams has been detected, or beam failure recovery of a transmission / reception point-specific or some beams has been triggered; and another value of the two bits indicates that beam failure of a cell-specific or all beams has been detected, or beam failure recovery of a cell-specific or all beams has been triggered, and beam failure of a transmission / reception point-specific or some beams has been detected, or beam failure recovery of a transmission / reception point-specific or some beams has been triggered; One value of the two bits indicates that no beam failure of a cell-specific or all beams is detected, or beam failure recovery of a cell-specific or all beams is not triggered, and no beam failure of a non-cell-specific or non-all beams is detected, or beam failure recovery of a non-cell-specific or non-all beams is not triggered; another value of the two bits indicates that beam failure of a cell-specific or all beams is detected, or beam failure recovery of a cell-specific or non-all beams is triggered; another value of the two bits indicates that beam failure of a cell-specific or all beams is detected, or beam failure recovery of a cell-specific or non-all beams is triggered, and another value of the two bits indicates that beam failure of a cell-specific or all beams is detected, or beam failure recovery of a cell-specific or non-all beams is triggered, and beam failure of a non-cell-specific or non-all beams is detected, or beam failure recovery of a non-cell-specific or non-all beams is triggered; 6. The device according to claim 5, wherein one value of the two bits indicates that a beam failure of a beam other than a non-transmitting / receiving point-specific or a portion of a beam has not been detected, or a beam failure recovery of a beam other than a non-transmitting / receiving point-specific or a portion of a beam has not been triggered, and a beam failure of a beam other than a non-transmitting / receiving point-specific or a portion of a beam has not been detected, or a beam failure recovery of a beam other than a non-transmitting / receiving point-specific or a portion of a beam has not been triggered; another value of the two bits indicates that a beam failure of a beam other than a non-transmitting / receiving point-specific or a portion of a beam has been detected, or a beam failure recovery of a beam other than a non-transmitting / receiving point-specific or a portion of a beam has been triggered; and another value of the two bits indicates that a beam failure of a beam other than a non-transmitting / receiving point-specific or a portion of a beam has been detected, or a beam failure recovery of a beam other than a non-transmitting / receiving point-specific or a portion of a beam has been triggered, and a beam failure of a beam other than a beam other than a non-transmitting / receiving point-specific or a portion of a beam has been detected, or a beam failure recovery of a beam other than a non-transmitting / receiving point-specific or a portion of a beam has been triggered.

8. The R bit in the beam failure recovery medium access control control element or the shortened beam failure recovery medium access control control element is used to convey / indicate / represent the type of beam failure detected or the type of beam failure recovery triggered, or The apparatus of claim 5, wherein the R bit and AC field in the beam failure recovery medium access control control element or the shortened beam failure recovery medium access control control element are used to convey / indicate / represent the type of beam failure detected or the type of beam failure recovery triggered.

9. The device of claim 1, wherein the beam failure recovery medium access control control element includes at least one or any combination of information of a cell to which a transmitting / receiving point belongs where a beam failure has been detected or where a beam failure recovery has been triggered, information on whether a candidate beam has been found, and information on the candidate beam.

10. The processor executes the program to cause the beam failure recovery medium access control element to be transmitted to a network device; The device of claim 1, wherein the beam failure recovery medium access control control element is transferred to the network device via another transmission / reception point of the cell to which the transmission / reception point belongs, or the beam failure recovery medium access control control element is transferred to the network device via a transmission / reception point that is co-located with the transmission / reception point and belongs to a cell different from the cell to which the transmission / reception point belongs, or the beam failure recovery medium access control control element is reported to the network device via a cell different from the cell to which the transmission / reception point belongs.

11. The processor, An uplink grant of a transmitting / receiving point in which a beam failure specific to a transmitting / receiving point of a cell to which a transmitting / receiving point in which a beam failure specific to a transmitting / receiving point belongs is not detected; An uplink grant of a transmission / reception point that is co-located with a transmission / reception point in which a beam obstruction specific to the transmission / reception point is detected and that belongs to a cell different from the cell to which the transmission / reception point in which the beam obstruction specific to the transmission / reception point is detected belongs; The device of claim 10, further comprising: an apparatus for executing the program to realize transmitting the beam failure recovery medium access control control element using one of the uplink grants of a cell other than a cell to which a transmitting / receiving point in which a beam failure specific to the transmitting / receiving point is detected belongs.

12. The medium access control entity instructs the multiplexing and assembly procedure to generate a beam failure recovery medium access control control element specific to the transmitting and receiving point; The apparatus of claim 1 , wherein the transmission / reception point specific beam failure recovery medium access control control element is different from a cell specific beam failure recovery medium access control control element.

13. generating said transmission / reception point specific beam fault recovery medium access control control elements using a procedure independent of the procedure of the cell specific beam fault recovery medium access control control elements, or The apparatus of claim 12 , further comprising: generating the cell-specific beam failure recovery medium access control control element and the transmission / reception point-specific beam failure recovery medium access control control element using a single procedure.

14. The priority of the logical channel corresponding to the transmission / reception point specific beam failure recovery medium access control control element is lower than the priority of the logical channel corresponding to the data from the C-RNTI medium access control control element or the uplink channel, and is higher than the priority of the logical channel corresponding to the cell specific beam failure recovery medium access control control element, or The priority of the logical channel corresponding to the transmission / reception point specific beam fault recovery medium access control control element is the same as the priority of the logical channel corresponding to the cell specific beam fault recovery medium access control control element; or the priority of the logical channel corresponding to the transmission / reception point specific beam failure recovery medium access control control element is lower than the priority of the logical channel corresponding to the cell specific beam failure recovery medium access control control element and higher than the priority of the logical channel corresponding to the sidelink configuration grant confirmation medium access control control element, or the priority of the logical channel corresponding to the transmission / reception point specific beam failure recovery MAC control element is equal to the priority of the logical channel corresponding to the sidelink configuration grant confirmation MAC control element; or The priority of the logical channel corresponding to the beam failure recovery MAC control element specific to the transmitting / receiving point is lower than the priority of the logical channel corresponding to the sidelink configuration grant confirmation MAC control element and is higher than the priority of the logical channel corresponding to the LBT failure MAC control element, or The priority of the logical channel corresponding to the beam failure recovery medium access control element specific to the transmitting and receiving point is the same as the priority of the logical channel corresponding to the beam failure medium access control element; or The device of claim 12, wherein the priority of a logical channel corresponding to the transmitting / receiving point-specific beam failure recovery medium access control control element is lower than the priority of a logical channel corresponding to an LBT failure medium access control control element and higher than the priority of a logical channel corresponding to a medium access control control element for SL-BSR.

15. The beam failure recovery medium access control element includes information of a candidate beam, The information of the candidate beams includes an index of a synchronization signal block or an index of a channel state information reference signal, or the information of the candidate beams indicates an order of appearance in the configured candidate beams; The candidate beams are The candidate beam is included in a candidate beam list configured for the transmitting / receiving point in which a beam failure specific to the transmitting / receiving point has been detected, or is included in a candidate beam / BFD-RS list configured for a cell to which the transmitting / receiving point in which a beam failure specific to the transmitting / receiving point has been detected belongs, or is included in a candidate beam / BFD-RS list configured for another transmitting / receiving point in the cell to which the transmitting / receiving point in which a beam failure specific to the transmitting / receiving point has been detected belongs; the received power of the reference signal is higher than a configured threshold; the signal to interference plus noise ratio is higher than a configured threshold; that the received signal strength indicator is higher than a configured threshold; A beam / reference signal paired with the candidate beam is included in a candidate beam list configured for the transmitting / receiving point in which a transmitting / receiving point-specific beam failure is detected, or a beam / reference signal paired with the candidate beam is included in a candidate beam / BFD-RS list configured for the cell to which the transmitting / receiving point in which a transmitting / receiving point-specific beam failure is detected belongs, or a beam / reference signal paired with the candidate beam is included in a candidate beam / BFD-RS list configured for another transmitting / receiving point in the cell to which the transmitting / receiving point in which a transmitting / receiving point-specific beam failure is detected belongs; The apparatus of claim 1 , wherein the measurement value of a beam / reference signal paired with the candidate beam satisfies at least one condition of being higher than a configured threshold.

16. The apparatus of claim 1 , wherein the beam failure recovery medium access control element is a medium access control element for a plurality of transmission / reception points including the transmission / reception point.

17. A terminal device that communicates with a network device via a communication network, A memory having a plurality of instructions stored therein; a processor coupled to the memory, The processor, Detecting that a beam failure recovery has been triggered for a transmitting / receiving point; Executing the instructions to realize: if at least one beam failure recovery has been triggered and not canceled for the transmitting / receiving point, and evaluation of the candidate beams has been completed, generating a beam failure recovery medium access control control element, the beam failure recovery medium access control control element indicating information of the transmitting / receiving point for which beam failure recovery has been triggered; One value of the one bit in the beam failure recovery medium access control control element indicates that beam failure recovery is triggered for a transmission / reception point corresponding to a control resource pool whose index is 0, and another value of the one bit indicates that beam failure recovery is triggered for a transmission / reception point corresponding to a control resource pool whose index is 1, or A terminal device, wherein one value of a bit in the beam failure recovery medium access control control element indicates that a beam failure has been detected for one corresponding to a beam failure detection reference signal set having a first index, and another value of the bit indicates that a beam failure has been detected for one corresponding to a beam failure detection reference signal set having a second index.

18. A network device that communicates with a terminal device via a communication network, A memory having a plurality of instructions stored therein; a processor coupled to the memory, The processor, Execute the instructions to realize receiving a beam failure recovery medium access control control element from the terminal device, the beam failure recovery medium access control control element being generated by the terminal device when at least one beam failure recovery has been triggered for a transmission / reception point and has not been canceled, and evaluation of candidate beams has been completed, the beam failure recovery medium access control control element indicating information of the transmission / reception point for which beam failure recovery has been triggered; One value of the one bit in the beam failure recovery medium access control control element indicates that beam failure recovery is triggered for a transmission / reception point corresponding to a control resource pool whose index is 0, and another value of the one bit indicates that beam failure recovery is triggered for a transmission / reception point corresponding to a control resource pool whose index is 1, or A network device, wherein one value of a bit in the beam failure recovery medium access control control element indicates that a beam failure has been detected for one corresponding to a beam failure detection reference signal set having a first index, and another value of the bit indicates that a beam failure has been detected for one corresponding to a beam failure detection reference signal set having a second index.

Images