A listen before talk (LBT) failure indication method and apparatus

Abstract

This application provides a listen-before-speak LBT failure indication method and apparatus. The method includes: when a first device determines that a link between it and a second device has experienced consecutive LBT failures, the first device sends an LBT failure report to a third device, the LBT failure report indicating consecutive LBT failures; wherein the third device is a parent node, host node, or child node of the first device. Through this method, when the first device determines that a link between it and the second device has experienced consecutive LBT failures, it can indicate the consecutive LBT failures to its parent node, host node, or child node. Since no LBT failures have occurred on the link between the first device and its parent node, host node, or child node, the network can promptly identify whether the first device has experienced consecutive LBT failures, thereby enabling timely processing and reducing the impact on the first device's data transmission.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a method and apparatus for indicating failure of Listen Before Talk (LBT). Background Technology

[0002] Wireless communication is based on spectrum resources, which can be divided into two categories: licensed spectrum (non-shared spectrum) and unlicensed spectrum (shared spectrum). Unlicensed spectrum can be used by any device and is a shared spectrum resource. Since unlicensed spectrum is a shared resource, a mechanism is needed to prevent interference between different communication devices using different air interface technologies on the unlicensed spectrum. This mechanism is called Listen Before Talk (LBT). LBT can also be called the channel access procedure, and is referred to as LBT in this embodiment. Before transmitting data on the unlicensed spectrum, the communication device needs to perform LBT. When LBT is successful, the communication device can transmit data on the unlicensed spectrum.

[0003] Currently, communication equipment in New Radio (NR) systems also supports data transmission on unlicensed spectrum. NR systems introduce integrated access and backhaul (IAB) network technology. An IAB network includes IAB nodes and IAB donors. Terminal devices can access IAB nodes, and their service data can be transmitted from the IAB node to the IAB donor via a wireless backhaul link. However, in an IAB network, there can be multiple IAB nodes between the terminal device and the IAB donor. Therefore, how to reduce the impact on the terminal device's service transmission after consecutive LBT failures is determined by the IAB node remains a problem that urgently needs to be solved. Summary of the Invention

[0004] The purpose of this application is to provide an LBT failure indication method and apparatus to solve the problem of how to reduce the impact on service transmission of terminal equipment after an IAB node determines that consecutive LBT failures have occurred.

[0005] In a first aspect, this application provides an LBT failure indication method, comprising: a first device performing LBT on a link between the first device and a second device; when the first device determines that consecutive LBT failures have occurred, the first device sends an LBT failure report to a third device, the LBT failure report indicating the consecutive LBT failures; wherein the second device is a child node of the first device, and the third device is a parent node or a host node of the first device; or, the second device is a parent node of the first device, and the third device is a child node of the first device.

[0006] Using the method described above, when the first device determines that it has experienced consecutive LBT failures with the second device, it can indicate the consecutive LBT failures to its parent node, host node, or child node. Since no LBT failures have occurred in the link between the first device and its parent node, host node, or child node, the network can promptly identify whether the first device has experienced consecutive LBT failures, and thus take timely action to ensure the network quality of the first device.

[0007] In one possible implementation, where the second device is a child node of the first device and the third device is a parent node or host node of the first device, the first device determines that consecutive LBT failures have occurred, including:

[0008] When a first link experiences consecutive LBT failures, the first device determines that consecutive LBT failures have occurred; the first link is the link between the first device and the second device; or, when the first link experiences consecutive LBT failures and the second link experiences consecutive LBT failures, the first device determines that consecutive LBT failures have occurred; the second link is the link between the first device and the third device.

[0009] In one possible implementation, the LBT failure report includes: the identification information of the first device.

[0010] In one possible implementation, the LBT failure report further includes one or more of the following: cell identifier information of the cell in the first device where consecutive LBT failures occurred; center frequency information of the cell in the first device where consecutive LBT failures occurred; beam identifier information of the beam where consecutive LBT failures occurred; LBT failure ratio information, used to indicate the ratio of the number of LBT failures to the sum of the number of LBT failures and the number of LBT successes; LBT type information of the LBT; channel access priority level (CAPC) corresponding to the LBT; time information of the first device determining when consecutive LBT failures occurred; and location information of the first device.

[0011] In one possible implementation, where the second device is the parent node of the first device and the third device is a child node of the first device, the first device determines that a series of LBT failures has occurred, including: when a first link experiences a series of LBT failures and a second link experiences a series of LBT failures, the first device determines that a series of LBT failures has occurred; the first link is a link between the first device and the second device, and the second link is a link between the first device and the third device; or when the second link experiences a series of LBT failures, the first device determines that a series of LBT failures has occurred.

[0012] In one possible implementation, the LBT failure report includes one or more of the following: BWP identification information, used to indicate BWPs that have experienced consecutive LBT failures more than or equal to the first number; cell identification information of the cell in the first device that has experienced consecutive LBT failures; center frequency information of the cell in the first device that has experienced consecutive LBT failures; time information of the first device determining when consecutive LBT failures occurred; and location information of the first device.

[0013] In one possible implementation, the first device determines that the first link or the second link has experienced consecutive LBT failures by: the first device determining that the first link has experienced consecutive LBT failures when, within a first duration, the number of consecutive LBT failures occurring on each BWP in at least one bandwidth portion (BWP) of the first link is greater than or equal to the first number; or, the first device determining that the first link has experienced consecutive LBT failures when, within the first duration, the number of consecutive LBT failures occurring on each BWP in at least one bandwidth portion (BWP) of the second link is greater than or equal to the first number.

[0014] In one possible implementation, the method further includes: the first device receiving configuration information from the third device, the configuration information including the first duration and the first number of times.

[0015] Secondly, this application also provides a communication device that implements any of the methods provided in the first aspect. This communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functions described above.

[0016] In one possible implementation, the communication device includes a processor configured to support the communication device in performing corresponding functions of the first device in the method described above. The communication device may also include a memory coupled to the processor, which stores necessary program instructions and data for the communication device. Optionally, the communication device further includes a communication interface for supporting communication between the communication device and devices such as network devices.

[0017] In one possible implementation, the communication device includes corresponding functional modules, each used to implement the steps in the above method. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the functions described above.

[0018] In one possible implementation, the communication device includes a processing module and a communication module, which can perform the corresponding functions in the above method examples, as described in the method provided in the first aspect, and will not be repeated here.

[0019] Thirdly, this application provides an LBT failure indication method, comprising: a third device receiving an LBT failure report from a first device, the LBT failure report indicating continuous LBT failures; the third device modifying a third link between itself and a second device, including the first device, or limiting traffic on the third link between itself and the second device, including the first device, based on the LBT failure report; wherein the third device is a parent node or host node of the first device, and the second device is a child node of the first device.

[0020] In one possible implementation, the third device modifies a third link between itself and the second device, including the first device, by either deleting the third link or switching it to a fourth link.

[0021] Fourthly, this application also provides a communication device that implements any of the methods provided in the third aspect above. This communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functions described above.

[0022] In one possible implementation, the communication device includes a processor configured to support the communication device in performing corresponding functions of the third device in the methods described above. The communication device may also include a memory coupled to the processor, which stores necessary program instructions and data for the communication device. Optionally, the communication device further includes a communication interface for supporting communication between the communication device and devices such as network devices.

[0023] In one possible implementation, the communication device includes corresponding functional modules, each used to implement the steps in the above method. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the functions described above.

[0024] In one possible implementation, the communication device includes a processing module and a communication module, which can perform the corresponding functions in the above method examples, as described in the method provided in the third aspect, and will not be repeated here.

[0025] Fifthly, this application provides an LBT failure indication method, comprising: a third device receiving an LBT failure report from a first device, the LBT failure report indicating consecutive LBT failures; the third device determining whether to perform cell selection or cell reselection based on the LBT failure report; wherein the third device is a child node of the first device, and the second device is a parent node or host node of the first device.

[0026] In one possible implementation, the LBT failure report includes one or more of the following:

[0027] Cell identifier information of cells that have experienced consecutive LBT failures in the first device;

[0028] The center frequency information of the cell in the first device that has experienced consecutive LBT failures.

[0029] In one possible implementation, when the third device determines to perform cell selection or cell reselection based on the LBT failure report, the method further includes: within a second time period, the third device does not consider cells in the first device that have experienced consecutive LBT failures as candidate cells for cell reselection or cell selection; or, within the second time period, the third device does not consider cells with the same center frequency as the center frequency information of the cells in the first device that have experienced consecutive LBT failures as candidate cells for cell reselection or cell selection; or, when performing cell selection or cell reselection, the third device lowers the frequency priority of the center frequency corresponding to the center frequency information, or sets the frequency priority of the center frequency corresponding to the center frequency information to the lowest priority.

[0030] Sixthly, this application also provides a communication device having any of the methods provided in the fifth aspect above. This communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functions described above.

[0031] In one possible implementation, the communication device includes a processor configured to support the communication device in performing corresponding functions of the third device in the methods described above. The communication device may also include a memory coupled to the processor, which stores necessary program instructions and data for the communication device. Optionally, the communication device further includes a communication interface for supporting communication between the communication device and devices such as network devices.

[0032] In one possible implementation, the communication device includes corresponding functional modules, each used to implement the steps in the above method. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the functions described above.

[0033] In one possible implementation, the communication device includes a processing module and a communication module, which can perform the corresponding functions in the above method examples, as described in the method provided in the fifth aspect, and will not be repeated here.

[0034] In a seventh aspect, this application provides a communication device including a processor, which, when executing a computer program or instructions in a memory, performs the method described in any one of the first, third, or fifth aspects.

[0035] Eighthly, this application provides a communication device comprising a processor and a memory for storing computer programs or instructions; the processor is configured to execute the computer programs or instructions stored in the memory to cause the communication device to perform a corresponding method as shown in any one of the first, third, or fifth aspects.

[0036] Ninthly, this application provides a communication device, the communication device including a processor, a memory, and a transceiver, the transceiver being used to receive or transmit signals; the memory being used to store computer programs or instructions; the processor being used to invoke the computer programs or instructions from the memory to execute the method described in any one of the first, third, or fifth aspects.

[0037] In a tenth aspect, this application provides a communication device comprising a processor and an interface circuit, the interface circuit being configured to receive code instructions and transmit them to the processor; the processor executing the code instructions to perform a corresponding method as shown in any one of the first, third, or fifth aspects.

[0038] Eleventhly, this application provides a computer-readable storage medium for storing a computer program or instructions that, when read and executed by a computer, cause the method described in any one of the first, third, or fifth aspects to be implemented.

[0039] In a twelfth aspect, this application provides a computer program product including instructions that, when a computer reads and executes the computer program product, cause the method described in any one of the first, third, or fifth aspects to be implemented.

[0040] In a thirteenth aspect, this application provides a chip including a processor coupled to a memory for executing a computer program or instructions stored in the memory, wherein when the processor executes the computer program or instructions, the method described in any one of the first, third, or fifth aspects is implemented.

[0041] In a fourteenth aspect, this application provides a system including the communication device provided in the second aspect, the communication device provided in the fourth aspect, and the communication device provided in the sixth aspect. Attached Figure Description

[0042] Figure 1 This is a schematic diagram of a network device architecture applicable to this application;

[0043] Figure 2 A schematic diagram of an IAB network architecture provided for an embodiment of this application;

[0044] Figure 3 This is a schematic flowchart of an information processing method provided in an embodiment of this application;

[0045] Figure 4 A schematic diagram of an IAB link provided in an embodiment of this application;

[0046] Figure 5 This is a schematic flowchart of an information processing method provided in an embodiment of this application;

[0047] Figure 6 This is a schematic diagram of a communication device structure provided in an embodiment of this application;

[0048] Figure 7 This is a schematic diagram of a communication device structure provided in an embodiment of this application. Detailed Implementation

[0049] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0050] The embodiments of this application can be applied to various mobile communication systems, such as new radio (NR), long-term evolution (LTE), advanced long-term evolution (LTE-A), evolved long-term evolution (eLTE), future communication systems, and other communication systems as defined by the 3rd generation partnership project (3GPP). No specific limitations are imposed here.

[0051] In this application embodiment, the terminal device can be a device with wireless transceiver function or a chip that can be set in any device. It can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user device. The terminal device in this application embodiment can be a mobile phone, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal, augmented reality (AR) terminal, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc.

[0052] The host node can be a next-generation node B (gNB) in an NR network or an evolved node B (eNB) in an LTE system. When the network device is a gNB, it can be an access network element with full base station functionality, or it can be an access network element with separate centralized unit (CU) and distributed unit (DU) structures. That is, a gNB consists of one CU and one or more DUs. The gNB's CU and DU are connected via an F1 interface, and the gNB's CU is connected to the 5G core network via an NG interface. For details, please refer to [reference needed]. Figure 1 As shown.

[0053] The host node can also be an IAB donor in an integrated access and backhaul (IAB) network.

[0054] In an IAB network, there are IAB nodes and IAB donors. Terminal devices can access IAB nodes, and their service data can be transmitted from the IAB node to the IAB donor via a wireless backhaul link.

[0055] It should be noted that the host node can also be called the host gNB, etc. Unless otherwise specified in the embodiments of this application, the above names all refer to the same device.

[0056] To facilitate understanding of the embodiments of this application, let's first take... Figure 2 The network architecture diagram shown in the figure serves as an example to illustrate the communication system applicable to the embodiments of this application. Figure 2 A schematic diagram of the IAB network architecture is shown. Figure 2 The IAB network shown includes the IAB host, IAB node 1, IAB node 2, and terminal devices.

[0057] Figure 2 The IAB network shown supports multi-hop networking, for example in Figure 2 There can be one or more intermediate IAB nodes between the IAB node and the IAB host shown.

[0058] Figure 2The IAB network shown supports not only multi-hop networking but also multi-connection networking. Between the terminal device served by the IAB node and the IAB host, there can be at least one link consisting of multiple links. Between the IAB node and the IAB host, there can also be one or more links, each with one or more IAB nodes. On a link, each IAB node considers its neighboring node providing backhaul services as its parent node; correspondingly, each IAB node can be considered a child node of its parent node. For example, in... Figure 2 In the scenario shown, the parent node of IAB node 1 is the IAB host, and the IAB host regards IAB node 1 as a child node.

[0059] An IAB node may include at least one mobile terminal (MT) unit and at least one distributed unit (DU). Figure 2 This description uses an IAB node comprising one MT unit and one DU as an example. The MT unit in the IAB node enables the IAB to act as a terminal, communicating with its parent node and the IAB host node. The DU in the IAB node provides access services to its attached terminal devices or other IAB nodes, and can also communicate with the IAB host node via the F1 interface. The MT in the IAB node can also be referred to as the MT functional entity, and the DU in the IAB node can also be referred to as the DU functional entity. For ease of description, the MT and MT functional entity in the IAB node are both abbreviated as "IAB MT," and the DU and DU functional entity in the IAB node are both abbreviated as "IAB DU."

[0060] An IAB node can provide wireless access services to terminal devices. The service data or control information of these terminal devices is transmitted by the IAB node to the IAB donor or network devices via a wireless backhaul link. The IAB donor can be an access network element with full base station functionality, or it can be an access network element with separate centralized units (CUs) and distributed units (DUs). The CU in the IAB donor can also be referred to as the CU functional entity in the IAB donor, and the DU in the IAB donor can also be referred to as the DU functional entity in the IAB donor.

[0061] For ease of description, in the embodiments of this application, the CU in the IAB host and the CU functional entity in the IAB host are simply referred to as IAB host CU, and the DU in the IAB host and the DU functional entity in the IAB host are simply referred to as IAB host DU. The IAB host CU may also be in the form of separate control plane (CP) and user plane (UP). For example, an IAB host CU consists of one CU-CP and multiple CU-UPs. The embodiments of this application do not limit this.

[0062] The F1 interface involved in the embodiments of this application is the interface between the IAB DU and the IAB host or the IAB host CU. The F1 interface can also be called the F1* interface, etc. For the sake of convenience, it can be uniformly referred to as the F1 interface in the embodiments of this application, but the name is not limited.

[0063] It should be noted that the F1 interface may also be an interface between functional entities within a device. For example, for a base station that includes a DU and a CU, the F1 interface can be the interface between the DU and the CU within the base station.

[0064] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0065] In the following description, the IAB network scenario is used as an example. It should be noted that the solution in the embodiments of this application can also be applied to other wireless communication networks, and the corresponding name can be replaced by the name of the corresponding function in other wireless communication networks.

[0066] In this embodiment, the interaction between the first device, the second device, and the third device is used as an example for explanation. The following description, in conjunction with... Figure 2 Describe them separately.

[0067] Example 1:

[0068] In Example 1, the second device is a child node of the first device, and the third device is the parent node or host node of the first device. For example, combining the previous... Figure 2 The first device is Figure 2 In the IAB node 1, the second device is Figure 2 The terminal device in the middle, the third device is Figure 2 The IAB node 2 or IAB host in the application. The method provided in the embodiments of this application can be as follows: Figure 3 As shown.

[0069] Optional, in Figure 3 Before step 301, the third device may send configuration information to the first device, the configuration information including a first duration and a first count.

[0070] The first count is used to trigger the first device to send an LBT failure report, as described later. The first duration can be used to configure the timing duration of a timer, which can be the LBT Failure Detection Timer defined in the 3GPP standard. When the first device determines an LBT failure, if the timer is not running, it starts the timer; otherwise, if the timer is running, it restarts the timer.

[0071] The configuration information may also include other information, which is not limited in this embodiment.

[0072] Step 301: The first device performs LBT on the link between the first device and the second device.

[0073] In one possible implementation, the first device determines that data will be sent to the second device before performing LBT; that is, the first device performs LBT in order to send data to the second device.

[0074] The first device can perform multiple LBTs in the link between the first device and the second device. When the first device determines that a series of LBT failures have occurred based on the results of the multiple LBTs, it executes step 302.

[0075] It should be noted that consecutive LBT failures can refer to multiple consecutive LBT failures. For example, when the first device performs an LBT, it increments a counter by 1 for each LBT failure (initial value of the counter is 0). Simultaneously, upon each LBT failure, the first device starts or restarts a timer. The timer's duration is a specified period, which can be pre-configured. If the timer is not running when an LBT failure occurs, it starts; if it is already running, it restarts. Before the timer expires, if the counter reaches a specified number of times (e.g., two times or other counts), the first device can determine that consecutive LBT failures have occurred.

[0076] In this embodiment of the application, the first device can determine that a series of LBT failures have occurred in a variety of ways. In the first possible implementation, when a series of LBT failures occur in the first link between the first device and the second device, the first device can determine that a series of LBT failures have occurred.

[0077] Specifically, the first device determines that the first link has experienced consecutive LBT failures when the number of consecutive LBT failures on each BWP in at least one bandwidth part (BWP) of the first link is greater than or equal to the first number within a first time period.

[0078] For example, when the first device performs LBT in any BWP of the first link, when the first device determines that an LBT failure occurs in that BWP, it can perform the following operations: 1. Increment the count value of the LBT failure counter (which can be LBT_FAIL_COUNTER defined in the 3GPP standard) by 1, where the initial value of the counter is 0; 2. Start or restart the timer (which can be lbtFailureDetectionTimer defined in the 3GPP standard), where the timer's duration can be a first duration.

[0079] If the LBT failure counter reaches its first count before the timer expires, the first device can determine that the BWP has experienced consecutive LBT failures. If the timer expires, the first device can reset the counter to 0.

[0080] It should be noted that at least one BWP in the first link can also be indicated by a third device, and the specific indication method is not limited in the embodiments of this application.

[0081] Optionally, in this embodiment, when the first device includes a DU and an MT, the configuration information is received by the DU of the first device.

[0082] In the second possible implementation, when the first link experiences consecutive LBT failures and the second link between the first device and the third device experiences consecutive LBT failures, the first device determines that consecutive LBT failures have occurred.

[0083] Specifically, how the first device determines that the first link has experienced consecutive LBT failures can be found in the preceding description.

[0084] The method by which the first device determines that the second link has experienced consecutive LBT failures can be the same as the method used to determine that the first link has experienced consecutive LBT failures. For example, the first device determines that the second link has experienced consecutive LBT failures when, within a first time period, the number of consecutive LBT failures occurring on each of at least one BWP in the second link is greater than or equal to the number of the first failure. For details, please refer to the preceding description, which will not be repeated here.

[0085] Step 302: When the first device determines that consecutive LBT failures have occurred, the first device sends an LBT failure report to the third device.

[0086] The LBT failure report is used to indicate the consecutive LBT failures.

[0087] In this embodiment of the application, the LBT failure report may be transmitted via radio resource control (RRC) messages or F1 application protocol (F1AP) messages, or other types of message transmission, which is not limited here.

[0088] The embodiments of this application do not limit the content included in the LBT failure report. For example, the LBT failure report may include one or more of the following:

[0089] The identification information of the first device; the identification information of the first device may be the identification information of the first device under the second device or the third device, and the second device or the third device can determine the link where consecutive LBT failures occur based on the identification information of the first device. For example, the identification information of the first device may be the cell radio network temporary identity (C-RNTI) of the first device, or the Backhaul Adaptation Protocol (BAP) identifier, or the F1AP identifier, etc.

[0090] Optionally, the LBT failure report may also include one or more of the following:

[0091] The cell identifier information of the first device's cell; the cell identifier information of the first device's cell is used to indicate cells that have experienced consecutive LBT failures.

[0092] It should be noted that in step 301, the first device performs LBT in at least one BWP in a cell. When the first device determines that consecutive LBT failures have occurred, it can be considered that consecutive LBT failures have occurred in that cell.

[0093] The center frequency information of the cell of the first device; the center frequency information of the first device is used to indicate the center frequency of the cell where consecutive LBT failures have occurred.

[0094] The beam identification information of the first device is used to indicate the beam in the at least one BWP where the number of consecutive LBT failures is greater than or equal to the number of the first failure.

[0095] LBT failure ratio information is used to indicate the ratio of the number of LBT failures to the sum of the number of LBT failures and the number of LBT successes. For example, if the first device performs a total of 100 LBTs and 40 of them fail, then the indicated ratio is 0.4.

[0096] The LBT type information of LBT, specifically, can refer to the LBT type information of consecutive LBT failures;

[0097] The channel access priority class (CAPC) corresponding to LBT can specifically refer to the CAPC of consecutive LBT failures.

[0098] The first device determines the time information of consecutive LBT failures;

[0099] The location information of the first device.

[0100] It should be noted that there are two types of LBT: Type 1, fixed-duration LBT; and Type 2, LBT based on a backoff mechanism. The specific processes for these two types can be found in existing technologies and will not be repeated here. The LBT based on a backoff mechanism introduces four channel access priority classes (CAPCs). Different CAPCs correspond to different channel access parameters, including the contention window size, corresponding service conditions, and channel occupancy time (COT) information. COT refers to the duration for which the channel can be used after a successful LBT.

[0101] Step 303: The third device receives an LBT failure report from the first device.

[0102] Step 304: Based on the LBT failure report, the third device modifies the third link between the third device and the second device, including the first device, or imposes traffic restrictions on the third link between the third device and the second device, including the first device.

[0103] When the third device makes changes to the third link, the third device can delete the third link or switch the third link to the fourth link.

[0104] For example, combining Figure 2 ,like Figure 4 As shown, there are two links between the terminal device and the IAB host. The first link can be... Figure 2The first link includes IAB node 1 and IAB node 2; the second link may include IAB node 3 and IAB node 4, where IAB node 3 is a child node of IAB node 4, and IAB node 4 is a child node of the IAB host. The third device is... Figure 4 When the third device is hosted in the IAB, after receiving an LBT failure report, if it determines that a series of LBT failures have occurred on the third link between the third device and the second device, including the first device, one possible implementation is that the third device can delete the third link including the first device. Another possible implementation is that the third device can switch the third link to a fourth link.

[0105] It should be noted that if there are multiple links between the third device and the second device, such as the third link and the third link, when the third device deletes the third link or switches the third link to the fourth link, the third device can indicate to the second device through the third link whether to delete the third link or to indicate the fourth link after the switch.

[0106] When a third device limits traffic on a third link, it can reduce the amount of data transmitted on the third link. For example, the amount of data transmitted on the third link can be reduced to one-third of the amount before consecutive LBT failures occur. The specific amount of reduction can be determined based on the actual situation, and this application embodiment does not limit this.

[0107] Example 2:

[0108] In Example 2, the second device is the parent node or host node of the first device, and the third device is a child node of the first device. For example, combining the previous... Figure 2 The first device is Figure 2 In the IAB node 1, the second device is Figure 2 In the IAB node 2 or IAB host, the third device is Figure 2 The terminal device in this application, the method provided in the embodiments can be as follows: Figure 5 As shown.

[0109] Optional, in Figure 5 Before step 501, the second device may send configuration information to the first device, the configuration information including a first duration and a first count.

[0110] The first count is used to trigger the first device to send an LBT failure report, as described later. The first duration can be used to configure the timing duration of a timer, which can be the LBT Failure Detection Timer defined in the 3GPP standard. When the first device determines an LBT failure, if the timer is not running, it starts the timer; otherwise, if the timer is running, it restarts the timer.

[0111] The configuration information may also include other information, which is not limited in this embodiment.

[0112] Step 501: The first device performs LBT on the link between the first device and the second device.

[0113] In one possible implementation, the first device determines that data will be sent to the second device before performing LBT; that is, the first device performs LBT in order to send data to the second device.

[0114] When the first device determines that consecutive LBT failures have occurred based on the results of multiple LBTs, step 502 is executed.

[0115] The first device can determine the occurrence of consecutive LBT failures in a variety of ways, which are described below.

[0116] In the first possible implementation, when a second link between the first device and the third device experiences consecutive LBT failures, the first device can determine that a consecutive LBT failure has occurred.

[0117] In the second possible implementation, when the first link experiences consecutive LBT failures and the second link between the first device and the third device experiences consecutive LBT failures, the first device can determine that consecutive LBT failures have occurred.

[0118] The specific method for determining whether a first link or a second link has experienced consecutive LBT failures is not limited in the embodiments of this application. For example, if a first device determines that the first link has experienced consecutive LBT failures when the number of consecutive LBT failures on each BWP in at least one bandwidth part (BWP) of the first link is greater than or equal to the first number within a first time period, then the first link can be determined to have experienced consecutive LBT failures.

[0119] Specifically, when the first device performs LBT in any BWP of the first link, when the first device determines that an LBT failure occurs in that BWP, it can perform the following operations: 1. Increment the count value of the LBT failure counter (which can be LBT_FAIL_COUNTER defined in the 3GPP standard) by 1, where the initial value of the counter is 0; 2. Start or restart the timer (which can be lbtFailureDetectionTimer defined in the 3GPP standard), where the timer's duration can be a first duration.

[0120] If the LBT failure counter reaches its first count before the timer expires, the first device can determine that the BWP has experienced consecutive LBT failures. If the timer expires, the first device can reset the counter to 0.

[0121] Other situations can be referred to the description in step 302, and will not be repeated here.

[0122] Step 502: When the first device determines that consecutive LBT failures have occurred, the first device sends an LBT failure report to the third device, the LBT failure report being used to indicate the consecutive LBT failures.

[0123] This application does not limit the content included in the LBT failure report. For example, the LBT failure report may include:

[0124] The identification information of the first device; the identification information of the first device may be the identification information of the first device under the second device or the third device, and the second device or the third device can determine the link where consecutive LBT failures have occurred based on the identification information of the first device. For example, the identification information of the first device may be the C-RNTI, or BAP identifier, or F1AP identifier of the first device, etc.

[0125] The LBT failure report may also include one or more of the following: cell identification information of the cell of the first device; the cell identification information of the cell of the first device is used to indicate the cell where consecutive LBT failures have occurred.

[0126] The center frequency information of the cell of the first device; the center frequency information of the first device is used to indicate the center frequency at which consecutive LBT failures occur.

[0127] BWP identification information is used to indicate a BWP that has experienced a number of consecutive LBT failures greater than or equal to the number of the first failure.

[0128] The first device determines the time information of consecutive LBT failures;

[0129] The location information of the first device.

[0130] Step 503: The third device receives an LBT failure report from the first device.

[0131] Step 504: The third device determines whether to perform cell selection or cell reselection based on the LBT failure report.

[0132] Optionally, the third device determines whether to perform cell selection or cell reselection when it determines, based on the LBT failure report, that the link between the first device and the second device has experienced consecutive LBT failures.

[0133] Optionally, the third device performs cell selection or cell reselection. The third device may also perform one or more of the following:

[0134] During the second duration, the third device will not consider cells in the first device that have experienced consecutive LBT failures as candidate cells for cell reselection or cell selection. The second duration can be configured by the third device or determined by other means, such as those specified in the communication protocol. The specific value of the second duration is not limited; for example, it can be 300 milliseconds (ms).

[0135] The above method can prevent the terminal device from camping in a cell that has experienced consecutive LBT failures again during cell reselection or cell selection, and increases the probability of camping in a cell with better channel quality.

[0136] During the second time period, the third device will not use cells with the same center frequency as the cells with consecutive LBT failures in the first device as candidate cells for cell reselection or cell selection; it should be noted that cells with the same frequency refer to cells with the same center frequency.

[0137] The above method can prevent terminal devices from camping in cells with the same frequency as cells that have experienced consecutive LBT failures during cell reselection or cell selection, thereby increasing the probability of camping in cells with better channel quality.

[0138] When performing cell selection or cell reselection, the third device reduces the frequency priority of the center frequency point corresponding to the center frequency point information of the cell that has experienced consecutive LBT failures in the first device, or sets the frequency priority of the center frequency point corresponding to the center frequency point information of the cell that has experienced consecutive LBT failures in the first device to the lowest priority.

[0139] In the above method, by reducing the frequency priority of the center frequency point corresponding to the center frequency point information of the cell where consecutive LBT failures occur in the first device, the probability of the third device camping in the cell corresponding to the center frequency point again during cell reselection or cell selection can be reduced, and the probability of camping in the cell with better channel quality can be increased.

[0140] Optionally, the third device may also send failure information to the host node based on the LBT failure report. The failure information is used to notify the IAB node between the third device and the host node of the LBT failure.

[0141] The various embodiments described herein can be independent solutions or combinations thereof based on their inherent logic, and all such solutions fall within the protection scope of this application.

[0142] It is understood that, in the above-described method embodiments, the methods and operations implemented by devices such as terminal devices can also be implemented by components (such as chips or circuits) that can be used in devices such as terminal devices.

[0143] In the embodiments provided above, the methods provided by the embodiments of this application have been described from the perspective of interaction between various devices. To implement the functions of the methods provided in the embodiments of this application, the terminal device and the network device may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0144] The module division in this embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0145] Similar to the above concept, such as Figure 6 As shown, this application embodiment also provides an apparatus 600 for implementing the functions of the terminal device or network device in the above method. For example, the apparatus can be a software module or a chip system. In this application embodiment, the chip system can be composed of chips or may include chips and other discrete devices. The apparatus 600 may include: a processing module 601 and a communication module 602.

[0146] In this embodiment of the application, the communication module may also be called a transceiver unit, which may include a sending unit and / or a receiving unit, respectively used to perform the sending and receiving steps of each device in the above method embodiment.

[0147] The following, combined with Figures 6 to 7 This application provides a detailed description of the communication device provided in its embodiments. It should be understood that the descriptions of the device embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail here will be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.

[0148] For example, when the device 600 performs the function of the first device in the process described above:

[0149] Communication module 602 is used to perform listen-before-speak (LBT) communication between the communication device and the second device;

[0150] Processing module 601 is used to send an LBT failure report to a third device through communication module 602 when it is determined that consecutive LBT failures have occurred. The LBT failure report is used to indicate the consecutive LBT failures.

[0151] Wherein, the second device is a child node of the communication device, and the third device is a parent node or host node of the communication device; or, the second device is a parent node of the communication device, and the third device is a child node of the communication device.

[0152] In one possible implementation, where the second device is a child node of the communication device and the third device is a parent node or host node of the communication device, the processing module 601 is specifically used for:

[0153] When a series of LBT failures occur on the first link, it is determined that a series of LBT failures have occurred; the first link is the link between the first device and the second device.

[0154] Alternatively, if the first link experiences consecutive LBT failures and the second link experiences consecutive LBT failures, then consecutive LBT failures are determined to have occurred; the second link is the link between the first device and the third device.

[0155] In one possible implementation, the LBT failure report includes:

[0156] The identification information of the communication device.

[0157] In one possible implementation, the LBT failure report further includes one or more of the following:

[0158] Cell identifier information of cells that have experienced consecutive LBT failures in the communication device;

[0159] The center frequency information of the cell in the communication device that has experienced consecutive LBT failures;

[0160] Beam identification information for beams that experience consecutive LBT failures;

[0161] LBT failure ratio information indicates the ratio of the number of LBT failures to the sum of the number of LBT failures and the number of LBT successes.

[0162] LBT type information;

[0163] LBT corresponds to the channel access priority level CAPC;

[0164] The communication device determines the time information of consecutive LBT failures.

[0165] The location information of the communication device.

[0166] In one possible implementation, where the second device is the parent node of the communication device and the third device is a child node of the communication device, the processing module 601 is specifically used for:

[0167] A series of consecutive LBT failures is determined when the first link experiences consecutive LBT failures and the second link experiences consecutive LBT failures; the first link is the link between the first device and the second device, and the second link is the link between the first device and the third device;

[0168] Alternatively, if the second link experiences consecutive LBT failures, it can be determined that consecutive LBT failures have occurred.

[0169] In one possible implementation, the LBT failure report includes one or more of the following:

[0170] BWP identification information is used to indicate a BWP that has experienced a number of consecutive LBT failures greater than or equal to the first failure.

[0171] Cell identifier information of cells that have experienced consecutive LBT failures in the communication device;

[0172] The center frequency information of the cell in the communication device that has experienced consecutive LBT failures;

[0173] The communication device determines the time information of consecutive LBT failures.

[0174] The location information of the communication device.

[0175] In one possible implementation, the processing module 601 is specifically used for:

[0176] If, within a first time period, the number of consecutive LBT failures on each BWP in at least one bandwidth portion (BWP) of the first link is greater than or equal to the first number, it is determined that the first link has experienced consecutive LBT failures.

[0177] Alternatively, if it is determined that the first link has experienced a continuous LBT failure when the number of consecutive LBT failures on each BWP in at least one bandwidth portion (BWP) of the second link is greater than or equal to the first number within the first duration, then the first link has experienced a continuous LBT failure.

[0178] In one possible implementation, the communication module 602 is further configured to:

[0179] The system receives configuration information from the third device, the configuration information including the first duration and the first number of times.

[0180] For example, when the device 600 performs the function of the third device in the process described above:

[0181] Communication module 602 is configured to receive an LBT failure report from a first device, the LBT failure report being used to indicate that consecutive LBT failures have occurred;

[0182] The processing module 601 is configured to, based on the LBT failure report, modify the third link between the third device and the second device, including the first device, or impose traffic restrictions on the third link between the third device and the second device, including the first device;

[0183] The communication device is the parent node or host node of the first device, and the second device is the child node of the first device.

[0184] In one possible implementation, the processing module 601 is specifically used for:

[0185] The third link is deleted, or the third device switches the third link to the fourth link.

[0186] For example, when the device 600 performs the function of the third device in the process described above:

[0187] Communication module 602 is configured to receive an LBT failure report from a first device, the LBT failure report being used to indicate the occurrence of consecutive LBT failures;

[0188] Processing module 601 is used to determine whether to perform cell selection or cell reselection based on the LBT failure report;

[0189] The communication device is a child node of the first device, and the second device is the parent node or host node of the first device.

[0190] In one possible implementation, the LBT failure report includes one or more of the following:

[0191] Cell identifier information for cells that have experienced consecutive LBT failures;

[0192] Center frequency information of cells that have experienced consecutive LBT failures.

[0193] In one possible implementation, when determining whether to perform cell selection or cell reselection based on the LBT failure report, the processing module 601 is further configured to:

[0194] During the second time period, cells that have experienced consecutive LBT failures in the first device will not be considered as candidate cells for cell reselection or cell selection.

[0195] Alternatively, during the second time period, cells with the same center frequency as the center frequency of the cells that have experienced consecutive LBT failures in the first device are not considered as candidate cells for cell reselection or cell selection.

[0196] Alternatively, when performing cell selection or cell reselection, the frequency priority of the center frequency point corresponding to the center frequency point information can be reduced, or the frequency priority of the center frequency point corresponding to the center frequency point information can be set to the lowest priority.

[0197] like Figure 7 The image shown is of the apparatus 700 provided in an embodiment of this application. Figure 7 The device shown can be Figure 6 The diagram illustrates one hardware circuit implementation of the device. This communication device can be applied to the preceding flowchart to perform the functions of the first or third device in the above method embodiments. For ease of explanation, Figure 7 Only the main components of the communication device are shown.

[0198] Figure 7 The apparatus 700 shown includes at least one processor 720 for implementing any of the methods provided in the embodiments of this application.

[0199] The device 700 may further include at least one memory 730 for storing program instructions and / or data. The memory 730 is coupled to the processor 720. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, and may be electrical, mechanical, or other forms, for information exchange between devices, units, or modules. The processor 720 may operate in conjunction with the memory 730. The processor 720 may execute program instructions stored in the memory 730. At least one of the at least one memories may be included in the processor.

[0200] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be implemented by a hardware processor, or by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0201] It should be noted that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by the integrated logic circuitry in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processing circuit (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be implemented by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0202] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0203] The device 700 may further include a communication interface 710 for communicating with other devices via a transmission medium, thereby enabling the device in the device 700 to communicate with other devices. In this embodiment, the communication interface may be a transceiver, a circuit, a bus, a module, or other types of communication interface. In this embodiment, when the communication interface is a transceiver, the transceiver may include an independent receiver, an independent transmitter, or a transceiver with integrated transceiver functions, or an interface circuit.

[0204] The device 700 may further include a communication line 740. The communication interface 710, processor 720, and memory 730 can be interconnected via the communication line 740. The communication line 740 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The communication line 740 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 7 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0205] For example, when the device 700 performs the function of the first device in the process described above:

[0206] Communication interface 710 is used to perform listen-before-speak (LBT) link between the communication device and the second device;

[0207] The processor 720 is configured to send an LBT failure report to a third device via the communication interface 710 when it is determined that consecutive LBT failures have occurred, the LBT failure report being used to indicate the consecutive LBT failures;

[0208] Wherein, the second device is a child node of the communication device, and the third device is a parent node or host node of the communication device; or, the second device is a parent node of the communication device, and the third device is a child node of the communication device.

[0209] In one possible implementation, where the second device is a child node of the communication device and the third device is a parent node or host node of the communication device, the processor 720 is specifically used for:

[0210] When a series of LBT failures occur on the first link, it is determined that a series of LBT failures have occurred; the first link is the link between the first device and the second device.

[0211] Alternatively, if the first link experiences consecutive LBT failures and the second link experiences consecutive LBT failures, then consecutive LBT failures are determined to have occurred; the second link is the link between the first device and the third device.

[0212] In one possible implementation, the LBT failure report includes:

[0213] The identification information of the communication device.

[0214] In one possible implementation, the LBT failure report further includes one or more of the following:

[0215] Cell identifier information of cells that have experienced consecutive LBT failures in the communication device;

[0216] The center frequency information of the cell in the communication device that has experienced consecutive LBT failures;

[0217] Beam identification information for beams that experience consecutive LBT failures;

[0218] LBT failure ratio information indicates the ratio of the number of LBT failures to the sum of the number of LBT failures and the number of LBT successes.

[0219] LBT type information;

[0220] LBT corresponds to the channel access priority level CAPC;

[0221] The communication device determines the time information of consecutive LBT failures.

[0222] The location information of the communication device.

[0223] In one possible implementation, where the second device is the parent node of the communication device and the third device is the child node of the communication device, the processor 720 is specifically used for:

[0224] A series of consecutive LBT failures is determined when the first link experiences consecutive LBT failures and the second link experiences consecutive LBT failures; the first link is the link between the first device and the second device, and the second link is the link between the first device and the third device;

[0225] Alternatively, if the second link experiences consecutive LBT failures, it can be determined that consecutive LBT failures have occurred.

[0226] In one possible implementation, the LBT failure report includes one or more of the following:

[0227] BWP identification information is used to indicate a BWP that has experienced a number of consecutive LBT failures greater than or equal to the first failure.

[0228] Cell identifier information of cells that have experienced consecutive LBT failures in the communication device;

[0229] The center frequency information of the cell in the communication device that has experienced consecutive LBT failures;

[0230] The communication device determines the time information of consecutive LBT failures.

[0231] The location information of the communication device.

[0232] In one possible implementation, the processor 720 is specifically used for:

[0233] If, within a first time period, the number of consecutive LBT failures on each BWP in at least one bandwidth portion (BWP) of the first link is greater than or equal to the first number, it is determined that the first link has experienced consecutive LBT failures.

[0234] Alternatively, if it is determined that the first link has experienced a continuous LBT failure when the number of consecutive LBT failures on each BWP in at least one bandwidth portion (BWP) of the second link is greater than or equal to the first number within the first duration, then the first link has experienced a continuous LBT failure.

[0235] In one possible implementation, the communication interface 710 is further used for:

[0236] The system receives configuration information from the third device, the configuration information including the first duration and the first number of times.

[0237] For example, when the device 700 performs the function of the third device in the process described above:

[0238] The communication interface 710 is used to receive an LBT failure report from a first device, the LBT failure report being used to indicate that consecutive LBT failures have occurred;

[0239] The processor 720 is configured to, based on the LBT failure report, modify the third link between the third device and the second device, including the first device, or to impose traffic restrictions on the third link between the third device and the second device, including the first device;

[0240] The communication device is the parent node or host node of the first device, and the second device is the child node of the first device.

[0241] In one possible implementation, the processor 720 is specifically used for:

[0242] The third link is deleted, or the third device switches the third link to the fourth link.

[0243] For example, when the device 700 performs the function of the third device in the process described above:

[0244] The communication interface 710 is used to receive an LBT failure report from the first device, the LBT failure report being used to indicate that consecutive LBT failures have occurred;

[0245] The processor 720 is configured to determine, based on the LBT failure report, whether to perform cell selection or cell reselection;

[0246] The communication device is a child node of the first device, and the second device is the parent node or host node of the first device.

[0247] In one possible implementation, the LBT failure report includes one or more of the following:

[0248] Cell identifier information for cells that have experienced consecutive LBT failures;

[0249] Center frequency information of cells that have experienced consecutive LBT failures.

[0250] In one possible implementation, when determining whether to perform cell selection or cell reselection based on the LBT failure report, the processor 720 is further configured to:

[0251] During the second time period, cells that have experienced consecutive LBT failures in the first device will not be considered as candidate cells for cell reselection or cell selection.

[0252] Alternatively, during the second time period, cells with the same center frequency as the center frequency of the cells that have experienced consecutive LBT failures in the first device are not considered as candidate cells for cell reselection or cell selection.

[0253] Alternatively, when performing cell selection or cell reselection, the frequency priority of the center frequency point corresponding to the center frequency point information can be reduced, or the frequency priority of the center frequency point corresponding to the center frequency point information can be set to the lowest priority.

[0254] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, etc.) containing computer-usable program code.

[0255] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0256] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0257] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for indicating failure of Listen-The-After-Speak LBT, characterized in that, include: The first device performs listen-before-speak (LBT) communication between the first device and the second device; The first device is an integrated access and backhaul node; When the first device determines that consecutive LBT failures have occurred, the first device sends an LBT failure report to the third device. The LBT failure report is used to indicate the consecutive LBT failures. The LBT failure report also includes one or more of the following: the identification information of the first device; the cell identification information of the cell in the first device where consecutive LBT failures have occurred; and the center frequency information of the cell in the first device where consecutive LBT failures have occurred. The following information is provided: beam identification information of the beam where consecutive LBT failures occurred; LBT failure ratio information, indicating the ratio of the number of LBT failures to the sum of the number of LBT failures and the number of successful LBTs; LBT type information; Channel Access Priority Class (CAPC) corresponding to the LBT; time information of when the first device determined that consecutive LBT failures occurred; and location information of the first device. Wherein, the second device is a child node of the first device, and the third device is a parent node or host node of the first device; or, the second device is a parent node of the first device, and the third device is a child node of the first device; the third device is an integrated access and backhaul node or an integrated access and backhaul host or terminal device. The continuous LBT failure includes: a first link experiencing continuous LBT failure, and a second link experiencing continuous LBT failure; the first link is the link between the first device and the second device, and the second link is the link between the first device and the third device; the LBT failure report also includes: The identification information of the BWP is used to indicate a BWP that has experienced a number of consecutive LBT failures greater than or equal to the number of the first failure.

2. The method according to claim 1, characterized in that, The first device determines that either the first link or the second link has experienced consecutive LBT failures by means of the following methods: The first device determines that the first link has experienced a continuous LBT failure when the number of consecutive LBT failures on each BWP in at least one bandwidth portion (BWP) of the first link is greater than or equal to the first number within a first time period. Alternatively, the first device determines that the first link has experienced a continuous LBT failure when the number of consecutive LBT failures on each BWP in at least one bandwidth portion (BWP) of the second link is greater than or equal to the first number within the first duration.

3. The method according to claim 2, characterized in that, The method further includes: The first device receives configuration information from the third device, the configuration information including the first duration and the first number of times.

4. A method for indicating failure of Listen-The-After-Speak LBT, characterized in that, include: The third device receives an LBT failure report from the first device, the LBT failure report indicating that consecutive LBT failures have occurred; the LBT failure report also includes one or more of the following: the identification information of the first device; the cell identification information of the cell in the first device where consecutive LBT failures have occurred; the center frequency information of the cell in the first device where consecutive LBT failures have occurred. The following information is provided: beam identification information of the beam where consecutive LBT failures occurred; LBT failure ratio information, indicating the ratio of the number of LBT failures to the sum of the number of LBT failures and the number of successful LBTs; LBT type information; Channel Access Priority Class (CAPC) corresponding to the LBT; time information of when the first device determined that consecutive LBT failures occurred; and location information of the first device. The third device may, based on the LBT failure report, modify the third link between the third device and the second device, including the first device, or impose traffic restrictions on the third link between the third device and the second device, including the first device. Wherein, the third device is the parent node or host node of the first device, and the second device is the child node of the first device; the third device is an integrated access and backhaul node or an integrated access and backhaul host or terminal device; the first device is an integrated access and backhaul node; The continuous LBT failures include: A first link experiences consecutive LBT failures, and a second link experiences consecutive LBT failures; the first link is the link between the first device and the second device, and the second link is the link between the first device and the third device; the LBT failure report also includes: The identification information of the BWP is used to indicate a BWP that has experienced a number of consecutive LBT failures greater than or equal to the number of the first failure.

5. The method according to claim 4, characterized in that, The third device modifies the third link between itself and the second device, including the first device, including: The third device deletes the third link, or the third device switches the third link to the fourth link.

6. A communication device, characterized in that, include: The communication module is used to perform listen-before-speak (LBT) communication between the communication device and the second device. The communication device is an integrated access and backhaul node; The processing module is configured to send an LBT failure report to a third device via the communication module when it is determined that consecutive LBT failures have occurred. The LBT failure report is used to indicate the consecutive LBT failures. The LBT failure report also includes one or more of the following: identification information of the communication device; cell identification information of the cell in the communication device where consecutive LBT failures have occurred; and center frequency information of the cell in the communication device where consecutive LBT failures have occurred. The following information is provided: beam identification information of the beam that experienced consecutive LBT failures; LBT failure ratio information, indicating the ratio of the number of LBT failures to the sum of the number of LBT failures and the number of successful LBTs; LBT type information; Channel Access Priority Class (CAPC) corresponding to the LBT; time information of when the communication device determined the consecutive LBT failures; and location information of the communication device. Wherein, the second device is a child node of the communication device, and the third device is a parent node or host node of the communication device; or, the second device is a parent node of the communication device, and the third device is a child node of the communication device; the third device is an integrated access and backhaul node or an integrated access and backhaul host or terminal device; The continuous LBT failures include: A first link experiences consecutive LBT failures, and a second link experiences consecutive LBT failures; the first link is the link between the communication device and the second device, and the second link is the link between the communication device and the third device; the LBT failure report further includes: The identification information of the BWP is used to indicate a BWP that has experienced a number of consecutive LBT failures greater than or equal to the number of the first failure.

7. The communication device according to claim 6, characterized in that, The processing module is specifically used for: If, within a first time period, the number of consecutive LBT failures on each BWP in at least one bandwidth portion (BWP) of the first link is greater than or equal to the first number, it is determined that the first link has experienced consecutive LBT failures. Alternatively, if it is determined that the first link has experienced a continuous LBT failure when the number of consecutive LBT failures on each BWP in at least one bandwidth portion (BWP) of the second link is greater than or equal to the first number within the first duration, then the first link has experienced a continuous LBT failure.

8. The communication device according to claim 7, characterized in that, The communication module is also used for: The system receives configuration information from the third device, the configuration information including the first duration and the first number of times.

9. A communication device, characterized in that, include: A communication module is configured to receive an LBT failure report from a first device, the LBT failure report indicating consecutive LBT failures; the LBT failure report further includes one or more of the following: identification information of the first device; cell identification information of the cell in the first device where consecutive LBT failures occurred; center frequency information of the cell in the first device where consecutive LBT failures occurred; The following information is provided: beam identification information of the beam where consecutive LBT failures occurred; LBT failure ratio information, indicating the ratio of the number of LBT failures to the sum of the number of LBT failures and the number of successful LBTs; LBT type information; Channel Access Priority Class (CAPC) corresponding to the LBT; time information of when the first device determined that consecutive LBT failures occurred; and location information of the first device. The processing module is configured to, based on the LBT failure report, modify the third link between the communication device and the second device, including the first device, or impose traffic restrictions on the third link between the communication device and the second device, including the first device; Wherein, the communication device is the parent node or host node of the first device, and the second device is the child node of the first device; the communication device is an integrated access and backhaul node or an integrated access and backhaul host or terminal device; the first device is an integrated access and backhaul node; The continuous LBT failures include: A first link experiences consecutive LBT failures, and a second link experiences consecutive LBT failures; the first link is the link between the first device and the second device, and the second link is the link between the first device and the communication device; the LBT failure report further includes: The identification information of the BWP is used to indicate a BWP that has experienced a number of consecutive LBT failures greater than or equal to the number of the first failure.

10. The communication device according to claim 9, characterized in that, The processing module is specifically used for: The third link is deleted, or the communication device switches the third link to the fourth link.

11. A communication device, characterized in that, Including processor and memory: The processor is configured to execute a computer program or instructions stored in the memory, wherein when the computer program or instructions are executed, the method described in any one of claims 1 to 5 is performed.

12. A readable storage medium, characterized in that, It includes a computer program or instructions, which, when executed, cause the method described in any one of claims 1 to 5 to be performed.

13. A chip, characterized in that, The method includes a processor coupled to a memory for executing a computer program or instructions stored in the memory, wherein when the processor executes the computer program or instructions, the method described in any one of claims 1 to 5 is performed.

Images