RU2857724C2 - Method and device for providing failure report - Google Patents

Abstract

FIELD: communication technology.

SUBSTANCE: invention relates to a method and device for providing a failure report. A terminal determines the need to initiate a persistent listen-before-talk (LBT) failure report for a direct connection (SL), and determines an uplink resource for transmitting the persistent SL LBT failure report. The terminal transmits the persistent SL LBT failure report on the uplink resource to a network device. When determining that it is necessary to initiate a persistent SL LBT failure report, the terminal can quickly report the persistent SL LBT failure to the network device using the uplink resource.

EFFECT: timely execution of processing to eliminate a persistent SL LBT failure, thereby preventing the terminal from constantly initiating a connection recovery procedure and, thus, increasing data transmission efficiency.

8 cl, 8 dwg

Description

Field of technology to which the invention relates

[0001] The present invention relates to the field of communications technology, namely to methods for providing a failure report and corresponding devices.

Prerequisites for the creation of the invention

[0002] In the prior art, Release 18 (R18) of the standard supports sidelink (SL) communications (also called direct communications) using unlicensed spectrum, and the terminal is required to perform listen before talk (LBT) to transmit data over the sidelink in the unlicensed spectrum. The continuous LBT mechanism is also applicable to sidelink communications in the unlicensed spectrum.

[0003] However, there is currently no effective means to report persistent LBT SL failure.

The essence of the invention

[0004] Embodiments of the present invention provide methods for providing a failure report and corresponding devices that can be applied to a scenario of a terminal communicating over a sidelink (SL) in an unlicensed frequency band (Sidelink-Unlicensed, SL-U). When the terminal determines the need to initiate reporting of a persistent listen-before-transmit (LBT) SL failure, the terminal can quickly report the persistent LBT SL failure to the network device by using uplink resources, so that the network device can perform processing to eliminate the persistent LBT SL failure in a timely manner, thereby avoiding the terminal from constantly initiating the connection restoration process and improving the data transmission efficiency.

[0005] According to a first aspect of embodiments of the present invention, a method for providing a failure report is provided. The method is performed by a terminal and includes:

[0006] determining whether to initiate provision of a report of a persistent LBT SL failure and determining an uplink resource for transmitting a report of a persistent LBT SL failure; and

[0007] transmitting to the network device a report of a persistent LBT SL failure on the uplink resource.

[0008] In this technical solution, when the terminal determines that it is necessary to start providing a report on the persistent LBT SL failure, the report on the persistent LBT SL failure can be quickly transmitted to the network device using a specified uplink resource, so that the network device can timely eliminate the persistent LBT SL failure, avoiding the terminal from constantly starting the connection restoration process, thereby improving the data transmission efficiency.

[0009] In one possible implementation, determining whether to initiate reporting of a persistent LBT SL failure includes:

[0010] determining by the terminal the necessity of starting the provision of a report on the persistent failure of the LBT SL in the event that the granularity of detecting the persistent failure of the LBT SL is the granularity of the resource pool, and the terminal determines that at least one resource pool causes the persistent failure of the LBT SL, and the persistent failure of the LBT SL in at least one resource pool is not eliminated.

[0011] In another possible implementation, determining whether to initiate reporting of a persistent LBT SL failure includes:

[0012] determining by the terminal the necessity of starting the provision of a report on the persistent failure of the LBT SL in the event that the granularity of detecting the persistent failure of the LBT SL is the granularity of a set of resource blocks (RBs), and the terminal determines that at least one set of RBs causes the persistent failure of the LBT SL, and the persistent failure of the LBT SL in at least one set of RBs is not eliminated.

[0013] In another possible implementation, determining whether to initiate reporting of a persistent LBT SL failure includes:

[0014] determining by the terminal the necessity to start reporting a persistent LBT SL failure in the event that the granularity of detecting the persistent LBT SL failure is the granularity of a Bandwidth Part (BWP), and the terminal determines that at least one BWP or cell is causing the persistent LBT SL failure, and the persistent LBT SL failure in at least one BWP or cell is not resolved.

[0015] In one possible implementation, determining an uplink resource for transmitting a persistent LBT SL failure report includes:

[0016] determining that the terminal has an uplink resource used for the new transmission that is capable of accommodating the LBT SL persistent failure report and its subheader; and

[0017] determining the uplink resource used for the new transmission as the uplink resource for transmitting the LBT SL persistent failure report.

[0018] In another possible implementation, determining the uplink resource for transmitting the LBT SL persistent failure report includes:

[0019] determining that there is no uplink resource for the terminal to be used for the new transmission and/or that the uplink resource to be used for the new transmission is not capable of accommodating the LBT SL persistent failure report and its subheader;

[0020] launching a Scheduling Request (SR); and

[0021] determining an SR configuration associated with the SR being triggered and transmitting an SR based on this configuration to request an uplink resource for transmitting a report of a persistent LBT SL failure.

[0022] In one possible implementation, the SR configuration associated with the SR being launched includes any of the following:

[0023] a dedicated SR configuration, wherein the dedicated SR configuration is an SR configuration designed to eliminate a persistent failure of the LBT SL;

[0024] any available SR configuration; or

[0025] the earliest arriving SR configuration among at least one available SR configuration.

[0026] In one possible implementation, determining the uplink resource for transmitting the LBT SL persistent failure report further includes:

[0027] determining that no SR configuration is associated with the SR being launched; and

[0028] starting a random access channel (RACH), initiating the RACH based on a dedicated RACH resource to request an uplink resource for transmitting a report of a persistent LBT SL failure; wherein the dedicated RACH resource is a RACH resource intended for recovering from a persistent LBT SL failure.

[0029] According to a second aspect of embodiments of the present invention, another method for providing a failure report is provided. The method is performed by a network device and includes:

[0030] transmitting configuration information to the terminal, wherein the configuration information includes a dedicated scheduling request (SR) configuration and/or a dedicated random access channel (RACH) configuration;

[0031] wherein the dedicated SR configuration and/or the dedicated RACH configuration are used to assist the terminal in requesting an uplink resource from the network device, and the uplink resource is used to transmit the LBT SL persistent failure report.

[0032] According to a third aspect of embodiments of the present invention, a communication device is provided. The communication device has some or all of the terminal functions described above in the methods of the first aspect. For example, the functions of the communication device may be some or all of the functions described in the embodiments of the invention or may be functions of an implementation of any of the individual embodiments of the invention. The functions may be implemented by hardware or hardware executing corresponding software. The hardware or software includes one or more blocks or modules corresponding to the above functions.

[0033] In one implementation, the structure of the communication device may comprise a transmitting and receiving module and a processing module that is configured to ensure that the communication device performs the corresponding functions of the method described above. The transmitting and receiving module is configured to ensure communication between the communication device and other devices. The communication device may also comprise a storage module that is connected to the transmitting and receiving module and the processing module and is configured to store computer programs and data necessary for the communication device.

[0034] For example, the processing module may be a processor, the transmitting/receiving module may be a transceiver or a communication interface, and the storage module may be a memory.

[0035] According to a fourth aspect of the embodiments of the invention, another communication device is provided. The communication device has some or all of the functions of the network device described above in the examples of the methods of the second aspect. For example, the functions of the communication device may be some or all of the functions described in the embodiments of the invention, or may be functions for independently implementing any of the embodiments of the invention. The functions may be implemented by hardware or may be implemented by hardware executing corresponding software. The hardware or software includes one or more blocks or modules corresponding to the functions described above.

[0036] In one implementation, the structure of the communication device may comprise a transmitting and receiving module and a processing module. The processing module is configured to ensure that the communication device performs the corresponding functions of the methods described above. The transmitting and receiving module is configured to ensure communication between the communication device and other devices. The communication device may also comprise a storage module that is connected to the transmitting and receiving module and the processing module and is configured to store computer programs and data necessary for the communication device.

[0037] According to a fifth aspect of the embodiments of the invention, a communication device is provided. The communication device comprises a processor. When the processor calls a computer program stored in the memory, the methods described in the first aspect are performed.

[0038] According to a sixth aspect of the embodiments of the invention, a communication device is provided. The communication device comprises a processor. When the processor calls a computer program stored in the memory, the methods described in the second aspect are performed.

[0039] According to a seventh aspect of the embodiments of the invention, a communication device is provided. The communication device comprises a processor and a memory. A computer program is stored in the memory. The processor is configured to execute the computer program stored in the memory to ensure that the communication device performs the method described above in the first aspect.

[0040] According to an eighth aspect of the embodiments of the invention, a communication device is provided. The communication device includes a processor and a memory. A computer program is stored in the memory. The processor is configured to execute the computer program stored in the memory to ensure that the communication device performs the method described above in the second aspect.

[0041] According to a ninth aspect of the embodiments of the invention, a communication device is provided. The communication device comprises a processor and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processor, and the processor is configured to execute the code instructions to ensure that the communication device performs the method described above in the first aspect.

[0042] According to a tenth aspect of the embodiments of the invention, a communication device is provided. The communication device comprises a processor and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processor, and the processor is configured to execute the code instructions to ensure that the communication device performs the method described above in the second aspect.

[0043] According to an eleventh aspect of the embodiments of the invention, a system for providing a failure report is provided. The system comprises the communication device described in the third aspect and the communication device described in the fourth aspect. Or the system comprises the communication device described in the fifth aspect and the communication device described in the sixth aspect. Or the system comprises the communication device described in the seventh aspect and the communication device described in the eighth aspect. Or the system comprises the communication device described in the ninth aspect and the communication device described in the tenth aspect.

[0044] According to a twelfth aspect of the embodiments of the invention, a computer-readable storage medium is provided. The computer-readable storage medium is configured to store commands used by the above-mentioned terminal. When these commands are executed, the terminal is enabled to perform the methods described above in the first aspect.

[0045] According to a thirteenth aspect of the embodiments of the invention, a computer-readable storage medium is provided. The computer-readable storage medium is configured to store instructions used by the above-mentioned network device. When these instructions are executed, the network device is enabled to perform the methods described above in the second aspect.

[0046] According to a fourteenth aspect of the embodiments of the invention, a computer program product is provided, including a computer program that, when executed on a computer, causes the computer to perform the methods described above in the first aspect.

[0047] According to a fifteenth aspect of the embodiments of the invention, a computer program product is provided, including a computer program that, when executed on a computer, causes the computer to perform the methods described above in the second aspect.

[0048] According to a sixteenth aspect of the embodiments of the invention, an integrated circuit system is proposed. The integrated circuit system comprises at least one processor and an interface and is used to provide a terminal with the implementation of the functions involved in the first aspect, for example, determining or processing at least one data and information involved in the above-mentioned methods. In one of the possible implementations, the integrated circuit system also includes a memory that is configured to store a computer program and data necessary for the terminal. The integrated circuit system may consist of an integrated circuit or may include an integrated circuit(s) and other discrete devices.

[0049] According to the seventeenth aspect of the invention, an integrated circuit system is proposed. The integrated circuit system comprises at least one processor and an interface and is used to ensure that the network device implements the functions involved in the second aspect, for example, determining or processing at least one data and information involved in the above-mentioned methods. In one possible implementation, the integrated circuit system also includes a memory that is configured to store a computer program and data necessary for the network device. The integrated circuit system may consist of an integrated circuit or may include an integrated circuit(s) and other discrete devices.

[0050] According to an eighteenth aspect of the invention, there is provided a computer program which, when executed on a computer, enables the computer to perform the methods described in the first aspect.

[0051] According to a nineteenth aspect of the invention, there is provided a computer program which, when executed on a computer, enables the computer to perform the methods described in the second aspect.

Brief description of the drawings

[0052] To illustrate in detail the technical solutions proposed in the embodiments of the present invention, as well as to describe existing technologies, drawings necessary for use in the embodiments of the invention or existing technologies will be described below.

[0053] Fig. 1 is a diagram illustrating the architecture of a communication system according to one embodiment of the invention.

[0054] Fig. 2 is a flow chart illustrating a method for providing a failure report according to one embodiment of the invention.

[0055] Fig. 3 is a flow chart illustrating a method for providing a failure report according to one embodiment of the invention.

[0056] Fig. 4 is a flow chart illustrating a method for providing a failure report according to one embodiment of the invention.

[0057] Fig. 5 is a block diagram illustrating another method for providing a failure report according to one embodiment of the invention.

[0058] Fig. 6 is a block diagram illustrating a communication device according to one embodiment of the invention.

[0059] Fig. 7 is a block diagram illustrating a communication device according to one embodiment of the invention.

[0060] Fig. 8 is a block diagram illustrating an integrated circuit according to one embodiment of the invention.

Detailed description of the invention

[0061] Embodiments of the present invention will be described in detail below, and example embodiments of the invention will be shown in the accompanying drawings, in which the same or similar reference numerals represent the same or similar elements or elements having the same or similar functions. The embodiments of the invention described below with reference to the accompanying drawings are illustrative and are intended to be used for the purpose of explaining the present invention and should not be construed as limiting the invention. In the description of the invention, unless otherwise indicated, the symbol "/" means "or". For example, the term "A/B" may mean "A or B". The term "and/or" in this document is a description of an association relationship of related objects, indicating that three relationships may exist. For example, "A and/or B" may mean "only A exists", "only B exists", and "both A and B exist".

[0062] The terms used in the embodiments of the invention are intended only to describe particular embodiments of the invention and are not intended to limit the embodiments of the invention. The singular forms used in the embodiments of the invention and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0063] It is understood that while the terms "first," "second," "third," etc. may be used to describe various information in embodiments of the invention, this information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, "first information" may also be referred to as "second information," and similarly, "second information" may also be referred to as "first information," without departing from the scope of embodiments of the present invention. Depending on the context, the words "if" used herein may be interpreted as "while," "when," or "in response to a determination that."

[0064] Embodiments of the present invention will be described in detail below, and examples of embodiments of the invention are shown in the accompanying drawings, in which the same or similar reference numerals represent the same or similar elements. The embodiments of the invention described below with reference to the accompanying drawings are illustrative, are intended to be used for the purpose of explaining the present invention, and should not be construed as limitations of the invention.

[0065] It should be noted that, in order to support direct communication between terminals, a sidelink (SL) communication is introduced, and the interface between terminals is a PC5 interface. Based on the correspondence between the transmitting terminal and the receiving terminal, three transmission modes are supported in the sidelink, namely, unicast, multicast, and broadcast. The transmitting terminal transmits sidelink control information (SCI) via a Physical Sidelink Control Channel (PSCCH) and transmits second-stage SCI information, which contains the location of the data transmission resource, the identifiers of the source and the destination, via a Physical Sidelink Shared Channel (PSSCH). For a data packet with Hybrid Automatic Repeat reQuest (HARQ) feedback support, the receiving terminal transmits feedback via the Physical Sidelink Feedback Channel (PSFCH) with an ACKnowledgment of the Hybrid Automatic Repeat reQuest (HARQ-ACK) on the PSSCH.

[0066] There are two methods for allocating transmission resources for communication over a direct link: one is a method dynamically scheduled by the network (called "resource allocation mode 1"), and the other is an autonomous selection method in which the terminal autonomously selects transmission resources from a resource pool broadcast by the network (called "resource allocation mode 2"). "Dynamic scheduled" means that the network dynamically allocates transmission resources over a direct link to the terminal based on cached data provided by the terminal, while "autonomous selection" means that the terminal autonomously and randomly selects transmission resources from a resource pool broadcast by the network or from a preconfigured resource pool. A network device can configure multiple resource pools for a terminal in one band width portion (BWP). The specific allocation method to be used is configured by the network device using Radio Resource Control (RRC) signaling.

[0067] The 5th generation (5G) New Radio Unlicensed (NR-U) system is a project in Release 16 (R16) of the Third Generation Partnership Project (3GPP) that provides operators with the necessary technologies to fully integrate unlicensed spectrum into 5G networks. NR-U supports uplink and downlink operations in unlicensed frequency bands. In NR-U, channel access for both the downlink and uplink is based on the listen-before-transmit (LBT) function. A wireless device or base station must first probe the channel and detect that there is no link before any transmission. When the channel is an unlicensed wideband channel (e.g., hundreds of megahertz wide), the LBT process is based on detecting energy levels in multiple sub-bands of the channel. LBT parameters (such as type/duration, channel idle estimation parameter, etc.) are configured in the wireless device by the base station.

[0068] "Consistent LBT failure" is a new feature defined in NR-U. The terminal counts the number of uplink LBT failures in each BWP. The network device configures the maximum number of consecutive LBT failures (e.g., lbt-FailureRecoveryMaxCount) and the persistent LBT failure detection timer (e.g., lbt-FailureDetectionTimer) for the terminal via RRC signaling (e.g., lbt-FailureRecoveryConfig) to the serving cell to count consecutive LBT failures. The terminal maintains a variable (e.g., LBTcounter) for each cell, and the initial value of the variable is 0. For each activated cell configured with lbt-FailureRecoveryConfig, when the terminal receives an LBT failure indication transmitted by the physical layer, the hard LBT failure detection timer is started or restarted, and the LBT counter is incremented by 1. When the LBT counter value is greater than or equal to the maximum number of consecutive LBT failures, the activated BWP in the cell causes a hard LBT failure. When the LBT hard failure detection timer expires, or when the upper layer reconfigures the maximum number of consecutive LBT failures/LBT hard failure detection timer, or when all hard LBT failures in this serving cell are eliminated, the terminal resets the LBT counter to 0. When the terminal detects a hard LBT failure in an activated BWP of the Primary Cell (PCell) or Primary Secondary Cell (PSCell), if there is another BWP configured with a Physical Random Access Channel (PRACH) resource in the cell, the terminal triggers a BWP switch to switch the activated BWP to the BWP configured with the PRACH resource and initiates a random access procedure to the Random Access Channel (RACH). If the terminal detects a permanent LBT failure in each of the N BWPs configured with PRACH resources in the primary cell, the terminal initiates the Radio Link Failure (RLF) recovery process. If a permanent LBT failure is detected in an activated BWP of a secondary cell (SCell), the terminal indicates to the network side, using a Media Access Control (MAC) Control Element (CE), the identity of the cell in which the permanent LBT failure occurs. The MAC CE may contain multiple identifiers of cells in which the permanent LBT failure is detected. The MAC CE is transmitted through other serving cells in which the permanent LBT failure does not occur.

[0069] In the prior art, Release 18 (R18) supports the use of unlicensed spectrum for direct link communications, and LBT is required for a terminal to transmit data over a direct link in the unlicensed spectrum. The continuous LBT mechanism is also applicable to direct link communications in the unlicensed spectrum.

[0070] However, there are currently no effective means for reporting persistent LBT SL failures.

[0071] To this end, embodiments of the invention propose a method for providing a failure report. When a terminal determines the need to initiate the provision of a report of a persistent LBT SL failure, the terminal can quickly provide a report of the persistent LBT SL failure to a network device using uplink resources, so that the network device can promptly recover from the persistent LBT SL failure, which allows the terminal to avoid constantly starting the connection restoration process, thereby improving the efficiency of data transmission.

[0072] In order to better understand the method for providing a failure report in accordance with embodiments of the invention, a communication system to which embodiments of the invention are applicable is first described below.

[0073] Fig. 1 is a diagram of the architecture of a communication system according to one embodiment of the invention. As shown in Fig. 1, the communication system may include, but is not limited to, one network device and one terminal. The number and types of devices shown in Fig. 1 are used only as examples and do not impose limitations on the embodiments of the invention. In practice, two or more network devices and two or more terminals may be used. The communication system shown in Fig. 1 includes, for example, a network device 101 and a terminal 102.

[0074] It should be noted that the technical solutions according to the embodiments of the present invention can be applied in various communication systems, for example, in the Long Term Evolution (LTE) system, the fifth generation (5G) mobile communication system, the 5G New Radio (NR) system, or in other future new mobile communication systems. It should be noted that the side link (Sidelink) in the embodiments of the invention can also be called a direct link.

[0075] The network device 101 in embodiments of the invention is an entity on the network side, designed to transmit or receive signals. For example, the network device 101 can be an evolved NodeB (eNB), a Transmission Reception Point (TRP), a next generation NodeB (gNB) in the NR system, a base station in other, future mobile communication systems, or an access node in the WiFi (Wireless Fidelity) wireless communication system. Embodiments of the invention are not limited with respect to specific technologies and specific types of the network device. The network device according to embodiments of the invention can consist of a centralized unit (CU) and a distributed unit (units) (Distributed Unit, DU). The central unit (CU) can also be called a control unit. The structure of central and distributed units, CU-DU, can be used to separate protocol layers in a network device, for example, in a base station. The functions of some protocol layers are placed in the CU for centralized management, and the functions of the remaining part or all protocol layers are placed in the DU, and the DUs are centrally managed by the CU.

[0076] Terminal 102 in embodiments of the invention is an object on the user side, designed to receive or transmit signals, such as a mobile telephone. The terminal may also be called an end device, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal may be a vehicle with communication functions, an intelligent vehicle, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality terminal (VR), an augmented reality terminal (AR), a wireless terminal in an industrial control system, a wireless terminal in an unmanned vehicle, a wireless terminal in a remote surgery system, a wireless terminal in an intelligent power grid, a wireless terminal in a transport security system, a wireless terminal in a smart city system, a wireless terminal in a smart home system, etc. Embodiments of the invention are not limited in relation to specific technologies and specific types of terminal used.

[0077] It should be understood that the communication system described in the embodiments of the present invention is intended to illustrate in more detail the technical solutions proposed in the embodiments of the invention and does not impose any limitations on the proposed technical solutions. It should be obvious to those skilled in the art that with the development of system architectures and the emergence of new commercial application scenarios, the technical solutions proposed in the embodiments of the present invention can also be applied to solve similar technical problems.

[0078] A detailed description of the failure reporting methods and associated devices according to the present invention is given below with reference to the attached drawings.

[0079] Fig. 2 is a flow chart illustrating a method for providing a failure report according to one embodiment of the invention. It should be noted that this method for providing a failure report according to embodiments of the invention may be performed by a terminal. As shown in Fig. 2, the method may include, but is not limited to, the following.

[0080] In step 201, a need to start providing a report of a persistent LBT SL failure is determined, and an uplink resource for transmitting a report of a persistent LBT SL failure is determined.

[0081] In embodiments of the invention, the terminal is in an RRC connected state. In one possible implementation, the terminal may operate in resource allocation mode 1 or in resource allocation mode 2.

[0082] In one possible implementation, a network device may configure a maximum number of consecutive LBT SL failures and a hard LBT SL failure detection timer for a terminal in a serving cell via RRC signaling, which is used to count LBT SL failures. The terminal maintains a variable for each cell, and the initial value of the variable is 0. For each activated cell configured via RRC signaling, when the terminal receives an LBT failure indication transmitted by the physical layer, the terminal starts or restarts the hard LBT SL failure detection timer, and the variable is incremented by 1. When the value of the variable is greater than or equal to the maximum number of consecutive LBT SL failures, the serving cell causes a hard LBT SL failure.

[0083] In embodiments of the invention, different granularities of detection of a persistent LBT SL failure will result in different implementations for determining the need to report a persistent LBT SL failure. In one possible implementation, the detection granularity may include, but is not limited to, any of the following: resource pool granularity, resource block (RB) set granularity, or BWP granularity.

[0084] In embodiments of the invention, when it is determined that it is necessary to trigger the provision of a permanent LBT SL failure report, the terminal may determine an uplink resource for transmitting the permanent LBT SL failure report. In one possible implementation, the permanent LBT SL failure report may be transmitted using an uplink resource in the terminal used for a new transmission, wherein the uplink resource used for the new transmission is an uplink resource allowed for the first transmission of data packets (as opposed to a retransmission). In another possible implementation, when there is no uplink resource in the terminal used for a new transmission, an SR is triggered, the uplink resource is requested through the SR configuration associated with the triggered SR, and the permanent LBT SL failure report is transmitted using the uplink resource. In another possible implementation, when the terminal does not have an uplink resource usable for a new transmission, the terminal may request an uplink resource via a dedicated RACH resource to transmit a persistent LBT SL failure report.

[0085] In step 202, a report of the persistent LBT SL failure is transmitted to the network device on the uplink resource.

[0086] In some examples, a terminal may transmit a report of a persistent LBT SL failure to a network device using an uplink resource. In one possible implementation, the terminal may transmit a report of a persistent LBT SL failure to a network device via a CE MAC on an uplink resource. In some embodiments of the invention, the report of a persistent LBT SL failure may include information for indicating the cell in which the persistent LBT SL failure was detected. In some examples, the report of a persistent LBT SL failure may be used to indicate to the network device the identifier of the cell in which the persistent LBT SL failure occurred, so that after the network device receives the report of a persistent LBT SL failure, the network device can perform processing in a timely manner to eliminate the persistent LBT SL failure.

[0087] When implementing embodiments of the invention, when the terminal determines the need to start providing a report of a persistent LBT SL failure, the terminal can quickly provide a report of the persistent LBT SL failure to the network device by using uplink resources, so that the network device can timely eliminate the persistent LBT SL failure, which can prevent the terminal from constantly starting the connection restoration process, thereby improving the efficiency of data transmission.

[0088] It should be noted that different granularities of the LBT SL persistent failure in embodiments of the invention will lead to different implementations for determining the need to report the LBT SL persistent failure. In some embodiments of the invention, if the granularity of detecting the LBT SL persistent failure is the granularity of the resource pool, the terminal determines that at least one resource pool causes the LBT SL persistent failure, and the LBT SL persistent failure in at least one resource pool has not been resolved, and the terminal can determine the need to trigger the reporting of the LBT SL persistent failure.

[0089] In some examples, if the granularity of the LBT SL persistent failure is the granularity of the resource pool, the terminal determines that at least one resource pool causes the LBT SL persistent failure and there is no remedy, the terminal may determine the need to initiate reporting of the LBT SL persistent failure. In one embodiment of the invention, if the terminal determines the need to initiate reporting of the LBT SL persistent failure, the terminal may determine an uplink resource for transmitting a report of the LBT SL persistent failure and transmit the report of the LBT SL persistent failure to the network device on the uplink resource. Determining the uplink resource for transmitting a report of the LBT SL persistent failure in this embodiment may be implemented in any of the methods described in various embodiments of the invention, which is not limited to this document and will not be repeated.

[0090] In some embodiments of the invention, if the granularity of detecting the persistent LBT SL failure is the granularity of the RB set, the terminal determines that at least one RB set causes the persistent LBT SL failure, and the persistent LBT SL failure in at least one RB set has not been resolved, and the terminal may determine whether it is necessary to trigger reporting of the persistent LBT SL failure.

[0091] In some examples, if the granularity of the LBT SL persistent failure is the granularity of the RB set, the terminal determines that at least one set of RBs causes the LBT SL persistent failure and there is no remedy, the terminal may determine that it is necessary to start reporting the LBT SL persistent failure. In one embodiment of the invention, when the terminal determines that it is necessary to start reporting the LBT SL persistent failure, the terminal may determine an uplink resource for transmitting the LBT SL persistent failure report and transmit the LBT SL persistent failure report to the network device on the uplink resource. Determining the uplink resource for transmitting the LBT SL persistent failure report in this embodiment of the invention may be implemented in any of the embodiments of the invention, which is not limited to the present document and will not be repeated.

[0092] In some embodiments of the invention, if the granularity of detecting the LBT SL persistent failure is the granularity of the BWP, the terminal determines that at least one BWP or cell is causing the LBT SL persistent failure, and the LBT SL persistent failure in at least one BWP or cell is not resolved, and the terminal determines the need to start reporting the LBT SL persistent failure.

[0093] In some examples, if the granularity of detecting the LBT SL persistent failure is the granularity of the BWP, the terminal determines that at least one BWP/cell (in which only one activated BWP is supported in one cell) causes the LBT SL persistent failure, and there is no remedy, the terminal may determine that it is necessary to start reporting the LBT SL persistent failure. In one embodiment of the invention, if the terminal determines that it is necessary to start reporting the LBT SL persistent failure, the terminal may determine an uplink resource for transmitting the LBT SL persistent failure report and transmit the LBT SL persistent failure report to the network device on the uplink resource. Determining the uplink resource for transmitting the LBT SL persistent failure report in this embodiment of the invention may be implemented in any of the embodiments of the invention, which is not limited to the present document and will not be repeated.

[0094] It should be noted that in embodiments of the invention, the LBT SL persistent failure report may be transmitted using the uplink resource that is used for a new transmission in the terminal. Fig. 3 is a flow chart illustrating a method for providing a failure report according to one embodiment of the invention. It should be noted that the method may be performed by a terminal. As shown in Fig. 3, the method may include, but is not limited to, the following.

[0095] At step 301, it is determined that it is necessary to initiate reporting of the persistent LBT SL failure.

[0096] In embodiments of the invention, the implementation of step 301 may be any of the implementations in the embodiments of the invention, which is not limited here and will not be described in detail.

[0097] At step 302, it is determined that the terminal has an uplink resource used for the new transmission that is capable of accommodating the LBT SL persistent failure report and its subheader.

[0098] In some examples, when determining whether to initiate provision of a persistent LBT SL failure report, the terminal may determine whether there is an uplink resource used by the terminal for a new transmission and whether this resource can accommodate the persistent LBT SL failure report and its subheader. If there is an uplink resource used for a new transmission that is capable of accommodating the persistent LBT SL failure report and its subheader, the terminal may instruct the multiplexing and linking entities to generate the persistent LBT SL failure report.

[0099] In step 303, the uplink resource used for the new transmission is determined as the uplink resource for transmitting the LBT SL persistent failure report.

[0100] In other words, if the terminal determines that there is an uplink resource used for a new transmission that is capable of accommodating the LBT SL persistent failure report and its subheader, the terminal may determine this uplink resource as an uplink resource for transmitting the LBT SL persistent failure report.

[0101] At step 304, a report of the persistent LBT SL failure is transmitted to the network device on the uplink resource.

[0102] The implementation of step 304 may be any of the implementations in the embodiments of the invention, which is not limited here and will not be described in detail.

[0103] When implementing embodiments of the invention, when the terminal determines that there is an uplink resource used for a new transmission that is capable of accommodating the LBT SL persistent failure report and its subheader, the LBT SL persistent failure report can be quickly transmitted to the network device using the uplink resources used for the new transmission, so that the network device can timely recover from the LBT SL persistent failure, which can prevent the terminal from constantly starting the connection restoration process, thereby improving the data transmission efficiency.

[0104] It should be noted that when the terminal does not have an uplink resource used for a new transmission, the terminal, according to embodiments of the invention, triggers an SR, requests an uplink resource through the SR configuration associated with the triggered SR, and transmits a persistent LBT SL failure report using the uplink resource. Fig. 4 is a flowchart illustrating a method for providing a failure report according to an embodiment of the invention. It should be noted that the method may be performed by the terminal. As shown in Fig. 4, the method may include, but is not limited to, the following.

[0105] At step 401, a determination is made as to whether a persistent LBT SL failure report needs to be initiated.

[0106] The implementation of step 401 may be any of the implementations in the embodiments of the invention, which is not limited here and will not be described in detail.

[0107] In step 402, it is determined that there is no uplink resource for the terminal to use for the new transmission and/or that the uplink resource to use for the new transmission is not capable of accommodating the LBT SL persistent failure report and its subheader.

[0108] In some examples, when the terminal determines the need to initiate the provision of a LBT SL hard failure report, the terminal may determine whether the terminal has an uplink resource used for the new transmission and whether this resource is capable of accommodating the LBT SL hard failure report and its subheader. If there is no uplink resource used for the new transmission and/or it is not capable of accommodating the LBT SL hard failure report and/or its subheader, the terminal performs step 403, that is, the terminal initiates a scheduling request (SR).

[0109] At step 403, SR is started.

[0110] In step 404, an SR configuration associated with the SR being triggered is determined and the SR is transmitted via this configuration to request an uplink resource for transmitting a persistent LBT SL failure report.

[0111] In a possible embodiment of the invention, the SR configuration associated with the SR being launched may include, but is not limited to, any of the following:

[0112] a dedicated SR configuration, which may be an SR configuration designed to eliminate a persistent failure of the LBT SL;

[0113] any available SR configuration; or

[0114] the earliest arriving SR configuration among at least one available SR configuration.

[0115] In one embodiment of the invention, when the terminal determines that there are no uplink resources for a new transmission and/or that the uplink resource used for the new transmission is not capable of accommodating the LBT SL persistent failure report and its subheader, the terminal triggers an SR and uses a dedicated SR configuration as the corresponding configuration of the triggered SR. That is, the SR is transmitted via the dedicated SR configuration to request an uplink resource for transmitting the LBT SL persistent failure report.

[0116] In one embodiment of the invention, when the terminal determines that there are no uplink resources for a new transmission and/or that the uplink resource used for the new transmission is not capable of accommodating the LBT SL persistent failure report and its subheader, the terminal initiates an SR and uses any available SR configuration as the corresponding configuration of the initiated SR. That is, the terminal transmits an SR using any available SR configuration to request uplink resources for transmitting the LBT SL persistent failure report.

[0117] In one embodiment of the invention, when the terminal determines that there are no uplink resources for a new transmission and/or that the uplink resource used for the new transmission is not capable of accommodating the LBT SL persistent failure report and its subheader, the terminal initiates an SR and uses the SR configuration with the SR resource that has arrived earliest among the available SR configurations as the corresponding configuration of the initiated SR. That is, the SR is transmitted using the SR configuration with the SR resources that has arrived earliest among the available SR configurations to request an uplink resource for transmitting the LBT SL persistent failure report.

[0118] In one embodiment of the present invention, one dedicated SR configuration may be defined that is used exclusively to recover from a persistent LBT SL failure. In one possible implementation, the dedicated SR configuration may be indicated by a parameter, and this parameter may be sl-LBT-schedulingRequestlD. A scheduling request identifier (e.g., SchedulingRequestlD) associated with sl-LBT-schedulingRequestID is used to indicate the SR configuration dedicated to recover from a persistent LBT SL failure. There may be other implementations that are not limited to this embodiment of the invention.

[0119] In one possible implementation, the dedicated SR configuration is a per-terminal (or per-UE) configuration. In some examples, the dedicated SR configuration may be contained in the SL-PHY-MAC-RLC-Config configuration. There may be other implementations that are not limited to this embodiment of the invention. It should be noted that in embodiments of the invention, the dedicated SR configuration may be configured by a network device for a terminal or pre-configured for a terminal.

[0120] In one possible implementation, the dedicated SR configuration may include a set of Physical Uplink Control Channel (PUCCH) resources that may be distributed across different BWPs and cells. In one BWP, a maximum of one PUCCH resource may be configured for the dedicated SR configuration.

[0121] At step 405, the LBT SL persistent failure report is transmitted to the network device on the uplink resource.

[0122] The implementation of step 405 may be any of the implementations in the embodiments of the invention, which is not limited here and will not be described in detail.

[0123] When implementing embodiments of the invention, the SR may be triggered by the terminal, and the uplink resource may be requested through the SR configuration associated with the triggered SR. A report of the persistent LBT SL failure may be quickly transmitted to the network device using the uplink resources, so that the network device can promptly recover from the persistent LBT SL failure, which may prevent the terminal from constantly triggering the connection restoration process, thereby improving the data transmission efficiency.

[0124] The present invention provides a method for providing a failure report. The method may be performed by a terminal. The method may include, but is not limited to, the following.

[0125] At step 401a, a determination is made as to whether a report of a persistent LBT SL failure should be initiated.

[0126] The implementation of step 401a may be any of the implementations in the embodiments of the invention, which is not limited here and will not be described in detail.

[0127] At step 402a, SR is started.

[0128] In step 403a, a dedicated SR configuration is determined, and an SR is transmitted through the dedicated SR configuration to request an uplink resource for transmitting a persistent LBT SL failure report.

[0129] In one implementation, the terminal uses a dedicated SR configuration as a corresponding configuration of the SR to be triggered and transmits an SR via the dedicated SR configuration to request an uplink resource for transmitting a persistent LBT SL failure report.

[0130] In one embodiment of the invention, a dedicated SR configuration may be defined that is used exclusively to recover from a persistent LBT SL failure. In one possible implementation, the dedicated SR configuration may be indicated by a parameter, and the parameter may be sl-LBT-schedulingRequestID. A scheduling request identifier (SchedulingRequestlD) associated with sl-LBT-schedulingRequestlD is used to indicate the SR configuration dedicated to recovering from a persistent LBT SL failure. There may be other implementations that are not limited to this embodiment.

[0131] In one possible implementation, the dedicated SR configuration is a per-terminal (or per-UE) configuration. In some examples, the dedicated SR configuration may be carried in the SL-PHY-MAC-RLC-Config configuration. There may be other implementations that are not limited to this embodiment of the invention. It should be noted that in embodiments of the invention, the dedicated SR configuration may be configured by a network device for a terminal or pre-configured for a terminal.

[0132] In one possible implementation, the dedicated SR configuration may include a set of physical uplink control channel (PUCCH) resources that may be distributed across different BWPs and cells. In one BWP, a maximum of one PUCCH resource may be configured for the dedicated SR configuration.

[0133] At step 404a, the LBT SL persistent failure report is transmitted to the network device on the uplink resource.

[0134] The implementation of step 404a may be any of the implementations in the embodiments of the invention, which is not limited here and will not be described in detail.

[0135] When implementing embodiments of the invention, the SR can be triggered by the terminal, and the uplink resource can be requested through a dedicated SR configuration. A report of the persistent LBT SL failure can be quickly transmitted to the network device using the uplink resources, so that the network device can promptly recover from the persistent LBT SL failure, which avoids the terminal from constantly triggering the connection restoration process, thereby improving the data transmission efficiency.

[0136] In some embodiments of the invention, there is no SR configuration associated with the SR initiated by the terminal, and a random access channel (RACH) may be initiated, and the RACH may be initiated based on a dedicated RACH resource for requesting an uplink resource for transmitting a report of a persistent LBT SL failure, wherein the dedicated RACH resource is a RACH resource intended for eliminating the persistent LBT SL failure.

[0137] In one possible implementation, the terminal determines the need to initiate the provision of a LBT SL persistent failure report. If there is an uplink resource used for a new transmission that is capable of accommodating the LBT SL persistent failure report and its subheader, the terminal instructs the multiplexing and linking entities to generate the LBT SL persistent failure report; otherwise, the terminal initiates SR. The terminal initiates SR. If there is no dedicated SR configuration, or if there is no available SR configuration (e.g., the terminal does not have an SR configuration), the terminal initiates RACH, initiates RACH using the dedicated RACH resource, and requests an uplink resource for transmitting the LBT SL persistent failure report.

[0138] In one possible implementation, the present invention may determine a dedicated RACH resource, and a terminal may request an uplink resource using the dedicated RACH resource to transmit a persistent LBT SL failure report.

[0139] In one possible implementation, a new parameter, such as sl-LBT-rachconfig, may be defined. The sl-LBT-rachconfig parameter may carry a dedicated RACH resource used to recover from a persistent LBTSL failure. There may be other implementations that are not limited to this embodiment of the invention.

[0140] In one possible implementation, the dedicated RACH resource may be a configuration for each terminal (for each UE). In some examples, the dedicated RACH resource may be carried in the SL-PHY-MAC-RLC-Config configuration. There may be other implementations that are not limited in this embodiment of the invention. It should be noted that in embodiments of the present invention, the dedicated RACH resource may be configured by a network device for a terminal or may be pre-configured for a terminal.

[0141] The present invention provides a method for providing a failure report. The method may be performed by a terminal. The method may include, but is not limited to, the following.

[0142] At step 401a, a determination is made as to whether a persistent LBT SL failure report should be initiated.

[0143] In embodiments of the invention, the implementation of step 401a may be any of the implementations in the embodiments of the invention, which is not limited here and will not be described in detail.

[0144] At step 402a, SR is started.

[0145] In step 403a, a dedicated SR configuration is determined, and an SR is transmitted via the dedicated SR configuration to request uplink resources used to transmit the LBT SL persistent failure report.

[0146] In one implementation, the terminal uses a dedicated SR configuration as a corresponding configuration of the SR to be triggered and transmits an SR via the dedicated SR configuration to request uplink resources for transmitting a persistent LBT SL failure report.

[0147] In one embodiment of the invention, a dedicated SR configuration may be defined that is used exclusively to recover from a persistent LBT SL failure. In one possible implementation, the dedicated SR configuration may be indicated by a parameter, and the parameter may be sl-LBT-schedulingRequestID. A scheduling request identifier (such as SchedulingRequestld) associated with sl-LBT-schedulingRequestID is used to indicate the SR configuration dedicated to recovering from a persistent LBT SL failure. There may be other implementations that are not limited to this embodiment of the invention.

[0148] In one possible implementation, the dedicated SR configuration is a per-terminal (or per-UE) configuration. In some examples, the dedicated SR configuration may be carried in the SL-PHY-MAC-RLC-Config configuration. There may be other implementations that are not limited to this embodiment of the invention. It should be noted that in embodiments of the invention, the dedicated SR configuration may be configured by a network device for a terminal or pre-configured for a terminal.

[0149] In one possible implementation, the dedicated SR configuration may include a set of physical uplink control channel (PUCCH) resources that may be distributed across different BWPs and cells. In one BWP, a maximum of one PUCCH resource may be configured for the dedicated SR configuration.

[0150] At step 404a, the LBT SL persistent failure report is transmitted to the network device on the uplink resource.

[0151] The implementation of step 404a may be any of the implementations in the embodiments of the invention, which is not limited here and will not be described in detail.

[0152] When implementing embodiments of the invention, the SR can be initiated by the terminal, and the uplink resource can be requested through a dedicated SR configuration. A report of the persistent LBT SL failure can be quickly transmitted to the network device using the uplink resources, so that the network device can promptly recover from the persistent LBT SL failure, which avoids the terminal from constantly initiating the connection restoration process, thereby improving the data transmission efficiency.

[0153] The present invention provides a method for providing a failure report. The method may be performed by a terminal. The method may include, but is not limited to, the following.

[0154] At step 401b, a determination is made as to whether a persistent LBT SL failure report should be initiated.

[0155] The implementation of step 401b may be any of the implementations in the embodiments of the invention, which is not limited here and will not be described in detail.

[0156] At step 402b, SR is started.

[0157] At step 403b, any available SR configuration is determined, and an SR is transmitted based on the determined available SR configuration to request an uplink resource for transmitting a persistent LBT SL failure report.

[0158] In one implementation, the terminal uses any available SR configuration as the corresponding configuration of the SR to be triggered and transmits an SR using the available SR configuration to request an uplink resource for transmitting a persistent LBT SL failure report.

[0159] At step 404b, the LBT SL persistent failure report is transmitted to the network device on the uplink resource.

[0160] The implementation of step 404b may be any of the implementations in the embodiments of the invention, which is not limited here and will not be described in detail.

[0161] When implementing embodiments of the invention, the SR can be initiated by the terminal, and the uplink resource can be requested through any available SR configuration. A report of the persistent LBT SL failure can be quickly transmitted to the network device using the uplink resources, so that the network device can promptly recover from the persistent LBT SL failure, which can prevent the terminal from constantly initiating the connection restoration process, thereby improving the data transmission efficiency.

[0162] The present invention provides a method for providing a failure report. The method may be performed by a terminal. The method may include, but is not limited to, the following.

[0163] At step 401, a determination is made as to whether a report of a persistent LBT SL failure should be initiated.

[0164] The implementation of step 401c may be any of the implementations in the embodiments of the invention, which is not limited here and will not be described in detail.

[0165] At step 402, SR is started.

[0166] In step 403, an early-arriving SR configuration is determined among at least one available SR configuration, and an SR is transmitted based on the early-arriving SR configuration determined among the at least one available SR configuration to request an uplink resource for transmitting a persistent LBT SL failure report.

[0167] In one implementation, the terminal uses the earliest-arrived SR configuration with SR resources among the available SR configurations as the corresponding configuration of the SR to be started and transmits an SR based on the earliest-arrived SR configuration with SR resources among the available SR configurations to request an uplink resource for transmitting a persistent LBT SL failure report.

[0168] At step 404, the LBT SL persistent failure report is transmitted to the network device on the uplink resource.

[0169] The implementation of step 404c may be any of the implementations in the embodiments of the invention, which is not limited here and will not be described in detail.

[0170] When implementing embodiments of the invention, the SR can be triggered by the terminal, and the uplink resource can be requested through the SR configuration of the SR resource that arrives earliest among the available SR configurations. The report of the persistent LBT SL failure can be quickly transmitted to the network device using the uplink resources, so that the network device can recover from the persistent LBT SL failure in a timely manner, which can relieve the terminal from constantly triggering the connection restoration process, thereby improving the efficiency of data transmission.

[0171] It is understood that the above embodiments of the invention describe the implementation of the method for providing a failure report according to the embodiments of the invention from the terminal side. The embodiments of the invention also provide a method for providing a failure report, and the implementation of the method for providing a failure report will be described from the network device side. Fig. 5 is a flowchart of another method for providing a failure report according to the embodiments of the present invention. It should be noted that this method can be performed by a network device. As shown in Fig. 5, the method may include, but is not limited to, the following.

[0172] In step 501, configuration information is transmitted to the terminal. The configuration information may include a dedicated SR configuration and/or a dedicated RACH configuration.

[0173] In embodiments of the invention, a dedicated SR configuration and/or a dedicated RACH configuration may be used to assist a terminal in requesting an uplink resource from a network device, wherein the uplink resource is used to transmit a persistent LBT SL failure report.

[0174] In embodiments of the invention, one dedicated SR configuration may be defined that is used exclusively to recover from a persistent LBT SL failure. In one possible implementation, the dedicated SR configuration may be represented by a parameter, and the parameter may be sl-LBT-schedulingRequestlD. A scheduling request identifier (SchedulingRequestlD) associated with sl-LBT-schedulingRequestID is used to indicate the SR configuration dedicated to recovering from a persistent LBT SL failure.

[0175] In one possible implementation, the dedicated SR configuration is a per-terminal (per-UE) configuration. In some examples, the dedicated SR configuration may be carried in the SL-PHY-MAC-RLC-Config configuration. There may be other implementations that are not limited to this embodiment of the invention.

[0176] In one possible implementation, the dedicated SR configuration may include a set of PUCCH resources. The PUCCH resources may be distributed across different BWPs and cells. In one BWP, a maximum of one PUCCH resource is configured for the dedicated SR configuration.

[0177] In one possible implementation, the present invention may determine a dedicated RACH resource, and the terminal may request an uplink resource for transmitting an LBT SL persistent failure report using the dedicated RACH resource.

[0178] In one possible implementation, a new parameter such as sl-LBT-rachconfig may be defined, and sl-LBT-rachconfig may carry a dedicated RACH resource used to recover from a persistent SL LBT failure. There may be other implementations that are not limited to this embodiment of the invention.

[0179] In one possible implementation, the dedicated RACH resource may be a per-terminal (per-UE) configuration. In some examples, the dedicated RACH resource may be carried in the SL-PHY-MAC-RLC-Config configuration. There may be other implementations that are not limited to this embodiment of the invention.

[0180] When implementing embodiments of the invention, a dedicated SR configuration and/or a dedicated RACH configuration may be configured for a terminal by a network device. In this way, the terminal may request an uplink resource through the dedicated SR configuration and/or the dedicated RACH configuration, and the terminal may quickly report a persistent LBT SL failure to the network device using the uplink resources, so that the network device can promptly recover from the persistent LBT SL failure, which avoids the terminal from constantly triggering a connection restoration process, thereby improving the efficiency of data transmission.

[0181] The methods according to the above embodiments of the invention are described from the perspective of a terminal and a network device, respectively. To implement the functions in the methods according to the above embodiments of the invention, the terminal and the network device may comprise hardware structures and software modules, and the above functions may be implemented in the form of hardware structures, software modules, or hardware structures plus software modules. One of the above functions may be performed in the form of hardware structures, software modules, or hardware structures plus software modules.

[0182] Fig. 6 is a block diagram illustrating a communication device 60 according to one embodiment of the invention. The communication device 60 shown in Fig. 6 may include a transmitting and receiving module 601 and a processing module 602. The transmitting and receiving module 601 may include a transmitting module and/or a receiving module. The transmitting module is configured to implement a transmitting function, the receiving module is configured to implement a receiving function, and the transmitting and receiving module 601 may implement the transmitting function and/or the receiving function.

[0183] The communication device 60 may be a terminal, a device in a terminal, or a device that can be used in conjunction with a terminal. Or the communication device 60 may be a network device, a device in a network device, or a device that can be used in conjunction with a network device.

[0184] The communication device 60 is a terminal. The processing module 602 is configured to determine whether to start providing a report of a permanent LBT SL failure and to determine an uplink resource for transmitting the report of a permanent LBT SL failure. The transmitting module 601 is configured to transmit the report of a permanent LBT SL failure to a network device on the uplink resource.

[0185] In one implementation, the processing module 602 is configured to determine by the terminal whether to initiate reporting of a persistent LBT SL failure; if the granularity of detecting the persistent LBT SL failure is the granularity of a resource pool, the terminal determines that at least one resource pool is causing the persistent LBT SL failure, and the persistent LBT SL failure in at least one resource pool is not resolved.

[0186] In another implementation, the processing module 602 is configured to determine by the terminal whether to start reporting a persistent LBT SL failure; if the granularity of detecting the persistent LBT SL failure is the granularity of a set of RBs, the terminal determines that at least one set of RBs causes the persistent LBT SL failure, and the persistent LBT SL failure in at least one set of RBs is not resolved.

[0187] In another implementation, the processing module 602 is configured to determine by the terminal whether to start reporting a persistent LBT SL failure; if the granularity of detecting the persistent LBT SL failure is the granularity of a BWP, the terminal determines that at least one BWP or cell is causing the persistent LBT SL failure, and the persistent LBT SL failure in at least one BWP or cell is not resolved.

[0188] In one implementation, the processing module 602 is configured to determine the availability of an uplink resource for the terminal used for the new transmission that is capable of accommodating the LBT SL persistent failure report and its subheader; and to determine the uplink resource for the new transmission as the uplink resource for transmitting the LBT SL persistent failure report.

[0189] In another implementation, the processing module 602 is configured to determine that there is no uplink resource for the terminal used for the new transmission and/or that the uplink resource used for the new transmission is not capable of accommodating the LBT SL persistent failure report and its subheader; trigger an SR; determine an SR configuration associated with the triggered SR; and transmit an SR based on this configuration to request an uplink resource for transmitting the LBT SL persistent failure report.

[0190] In one possible implementation, the SR configuration associated with the SR being launched includes any of the following: a dedicated SR configuration, wherein the dedicated SR configuration is an SR configuration designed to eliminate the persistent failure of the LBT SL; any available SR configuration; or an SR configuration that arrived earlier among at least one available SR configuration.

[0191] In one possible implementation, the processing module 602 is configured to: determine that no SR configuration is associated with the SR being triggered; trigger an RACH; initiate an RACH based on a dedicated RACH resource to request an uplink resource for transmitting a report of a persistent LBT SL failure; wherein the dedicated RACH resource is a RACH resource designated for recovering from a persistent LBT SL failure.

[0192] The communication device 60 is a network device. The transmitting/receiving module 601 is configured to transmit configuration information to the terminal, wherein the configuration information includes a dedicated SR configuration and/or a dedicated RACH configuration. The dedicated SR configuration and/or the dedicated RACH configuration are used to assist the terminal in requesting an uplink resource from the network device, wherein the uplink resource is used to transmit a report of a persistent LBT SL failure.

[0193] With respect to the devices in the embodiments of the invention described above, the specific manner in which each module performs operations has been described in detail in the embodiments of the method and will not be discussed in detail here.

[0194] Fig. 7 is a block diagram illustrating another communication device 70 according to an embodiment of the invention. As shown in Fig. 7, the communication device 70 may be a network device or a terminal. Or, the communication device 70 may be an integrated circuit, an integrated circuit system, or a processor that supports the network device for implementing the above-mentioned method. Or, the communication device 70 may be an integrated circuit, an integrated circuit system, or a processor that provides a terminal for implementing the methods described above. The device may be configured to implement the methods described above in the embodiments of the method, and for detailed information, reference may be made to the description of the above embodiments of the method.

[0195] The communication device 70 may comprise one or more processors 701. The processor 701 may be a general-purpose processor or a specialized processor. For example, the processor 701 may be a baseband processor or a central processor. The baseband processor may be configured to process a communication protocol and communication data, and the central processor may be configured to control a communication device (such as a base station, a baseband integrated circuit, a terminal, a terminal integrated circuit, a DU, a CU, etc.), to execute computer programs and to process computer program data.

[0196] In some examples, the communication device 70 may further comprise one or more memory units 702, in which a computer program 704 may be stored. The processor 701 may execute the computer program 704 to cause the communication device 70 to perform the methods described in the above embodiments of the method. In some examples, data may also be stored in the memory 702. The communication device 70 and the memory 702 may be installed separately or integrated together.

[0197] In some examples, the communication device 70 may further comprise a transceiver 705 and an antenna 706. The transceiver 705 may be called a transceiver unit, a transceiver device, a transceiver circuit, and the like for implementing a transceiver function. The transceiver 705 may comprise a receiver and a transmitter. The receiver may be called a receiver or a receiver circuit for implementing a receiving function. The transmitter may be called a transmitter or a transmitter circuit for implementing a transmitting function.

[0198] In some examples, the communication device 70 may further comprise one or more interface circuits 707. The interface circuit 707 is configured to receive code instructions and transmit the code instructions to the processor 701. The processor 701 executes the code instructions so that the communication device 70 can perform the methods described in the above embodiments of the method.

[0199] The communication device 70 is a terminal. The processor 701 is configured to perform step 201 in Fig. 2, steps 301, 302 and 303 in Fig. 3 or steps 401, 402, 403 and 404 in Fig. 4. The transceiver 705 is configured to perform step 202 in Fig. 2, step 304 in Fig. 3 or step 405 in Fig. 4.

[0200] The communication device 70 is a network device. The transceiver 705 is configured to perform step 501 in Fig. 5.

[0201] In one implementation, the processor 701 may comprise a transceiver for implementing reception and transmission functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the reception and transmission functions may be separate or integrated together. The aforementioned transceiver circuit, interface, or interface circuit may be configured to read and write code/data, or the aforementioned transceiver circuit, interface, or interface circuit may be configured to transmit or deliver signals.

[0202] In one implementation, the processor 701 may store a computer program that is executed in the processor 701 and allows the communication device 70 to perform the methods described in the above embodiments of the method. The computer program may be embedded in the processor 701, and in this case, the processor 701 may be implemented in hardware.

[0203] In one implementation, the communication device 70 may comprise circuitry that may implement the transmitting or receiving or communicating functions in the above-mentioned embodiments of the method. The processor and transceiver described in the disclosure of the present invention can be implemented on integrated circuits (Integrated Circuit, IC), analog IC, radio frequency IC (Radio Frequency Integrated Circuit, RFIC), mixed digital-analog IC, specialized IC (Application Specific Integrated Circuit, ASIC), printed circuit boards (Printed Circuit Board, PCB) and electronic devices, etc. The processor and transceiver can also be manufactured using various IC manufacturing process technologies based on structures such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (N-Metal-Oxide-Semiconductor, NMOS), positive channel metal oxide semiconductor (PMOS), bipolar junction transistor (BJT), bipolar and complementary metal-oxide-semiconductor (Bipolar CMOS, BiCMOS), silicon-germanium (Silicon Germanium, SiGe), gallium arsenide (Gallium Arsenide, GaAs), etc.

[0204] The communication device described in the above embodiments of the invention may be a network device or a terminal, but the scope of application of the communication device described herein is not limited thereto, and the structure of the communication device may not be limited to Fig. 7. The communication device may be a stand-alone device or may be part of a larger device. For example, the communication device may be:

[0205] (1) a stand-alone integrated circuit (IC), or an IC chip, or a system or subsystem on an IC chip;

[0206] (2) a set of one or more ICs, which in some examples may also include a storage component for storing data and computer programs;

[0207] (3) ASIC, such as a modem;

[0208] (4) a module that can be built into other devices;

[0209] (5) a receiver, a terminal, an intelligent terminal, a cellular phone, a wireless device, a handheld device, a mobile device, a device installed on a vehicle, a network device, a cloud device, an artificial intelligence device, etc.;

[0210] (6) other devices.

[0211] For the case where the communication device may be an integrated circuit or a system of integrated circuits, the structure of the integrated circuit is shown in Fig. 8. The integrated circuit shown in Fig. 8 comprises a processor 801 and an interface 802. The number of processors 801 may be one or more, and the number of interfaces 802 may be multiple.

[0212] For the case where an integrated circuit is used to implement the functions of a terminal in embodiments of the invention:

[0213] The processor 801 is configured to determine whether to trigger a persistent LBT SL failure report and to determine an uplink resource for transmitting the persistent LBT SL failure report. The interface 802 is configured to transmit the persistent LBT SL failure report to the network device on the uplink resource.

[0214] In one implementation, the processor 801 is configured to determine by the terminal whether to initiate reporting of a persistent LBT SL failure; if the granularity of detecting the persistent LBT SL failure is the granularity of a resource pool, the terminal determines that at least one resource pool is causing the persistent LBT SL failure, and the persistent LBT SL failure in at least one resource pool is not resolved.

[0215] In another implementation, the processor 801 is configured to determine by the terminal whether to start reporting a persistent LBT SL failure; if the granularity of detecting the persistent LBT SL failure is the granularity of a set of RBs, the terminal determines that at least one set of RBs causes the persistent LBT SL failure, and the persistent LBT SL failure in at least one set of RBs is not resolved.

[0216] In another implementation, the processor 801 is configured to determine by the terminal whether to start reporting a persistent LBT SL failure; if the granularity of detecting the persistent LBT SL failure is the granularity of a BWP, the terminal determines that at least one BWP or cell is causing the persistent LBT SL failure, and the persistent LBT SL failure in at least one BWP or cell is not resolved.

[0217] In one implementation, the processor 801 is configured to determine the availability of an uplink resource for the terminal used for the new transmission that is capable of accommodating the LBT SL persistent failure report and its subheader; and to determine the uplink resource for the new transmission as the uplink resource for transmitting the LBT SL persistent failure report.

[0218] In another implementation, the processor 801 is configured to determine that there is no uplink resource for the terminal used for the new transmission and/or that the uplink resource used for the new transmission is not capable of accommodating the LBT SL persistent failure report and its subheader; to trigger an SR; to determine an SR configuration associated with the triggered SR, and to transmit an SR based on this configuration to request an uplink resource for transmitting the LBT SL persistent failure report.

[0219] In one possible implementation, the SR configuration associated with the SR being launched includes any of the following: a dedicated SR configuration, wherein the dedicated SR configuration is an SR configuration designed to eliminate the persistent failure of the LBT SL; any available SR configuration; or an SR configuration that arrived earlier among at least one available SR configuration.

[0220] In one possible implementation, the processor 801 is configured to determine that no SR configuration is associated with the SR being triggered; to trigger a RACH; and to initiate a RACH based on the allocated RACH resource to request an uplink resource for transmitting a report of a persistent LBT SL failure; wherein the allocated RACH resource is a RACH resource designated for recovering from a persistent LBT SL failure.

[0221] For the case where the integrated circuit is configured to implement the functions of the network device in embodiments of the invention:

[0222] the 802 interface is configured to transmit configuration information to the terminal, wherein the configuration information includes a dedicated SR configuration and/or a dedicated RACH configuration; the dedicated SR configuration and/or the dedicated RACH configuration are used to assist the terminal in requesting an uplink resource from a network device, and the uplink resource is used to transmit a report of a persistent LBT SL failure.

[0223] In some examples, the integrated circuit further comprises a memory 803. The memory 803 is configured to store necessary computer programs and data.

[0224] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of the invention may be implemented by electronic hardware, software, or a combination of both. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the overall system. Those skilled in the art may use various methods to implement the functions described for each specific application, but such implementation should not be construed as leaving the scope of the embodiments of the present invention.

[0225] Embodiments of the invention also provide a system for providing a failure report. The system comprises a communication device as a terminal and a communication device as a network device in the embodiments of the invention described above in Fig. 6 or in Fig. 7.

[0226] The present invention also provides a machine-readable storage medium that stores instructions that, when executed by a computer, result in the implementation of the functions of any of the above embodiments of the method.

[0227] The present invention also provides a computer program product that, when executed by a computer, enables the implementation of the functions of any of the above embodiments of the method.

[0228] The embodiments of the invention described above may be implemented in whole or in part using software, hardware, firmware, or any combination thereof. When implemented using software, embodiments of the invention may be implemented in whole or in part as a computer program product. The computer program product comprises one or more computer programs. When the computer program is loaded and executed on the computer, the process or function described in the embodiments of the invention is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program may be stored on a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, a computer program may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center by wired means (e.g., coaxial cables, fiber optic cables, or Digital Subscriber Line (DSL), etc.) or wireless means (e.g., infrared, wireless, microwave, etc.). A computer-readable storage medium may be any usable storage medium that can be accessed by a computer or a data storage device, such as a server or data center, that incorporates one or more accessible storage media. An accessible storage medium may be a magnetic storage medium (e.g., a floppy disk, hard disk, or magnetic tape), an optical storage medium (e.g., a high-density digital video disc (DVD)) or a solid state disk (SSD), etc.

[0229] Those skilled in the art will understand that various numerical values, such as "first" and "second," used in this description are for convenience of description only and are not intended to limit the scope of embodiments of the invention, nor are they intended to represent a sequential order.

[0230] The term "at least one" used in the present invention may also be described as one or more, and the term "plurality" may cover two, three, four or more, which is not limited in the present invention. In the embodiments of the present invention, with regard to the types of technical features, the expressions "first", "second" and "third", as well as "A", "B", "C" or "D", etc. are used to distinguish technical features of the same type, while when the expressions "first", "second" and "third", as well as "A", "B", "C" or "D" are used to describe a technical feature, this does not indicate either the order of precedence or the magnitude.

[0231] The correspondences shown in the tables in the present document may be configurable or may be predetermined. The values of the various information in each table are given solely by way of example and may be configured to be equal to other values, without limiting the present invention in this regard. Configuring the correspondence between the information and each parameter does not necessarily require that all correspondences shown in each table be configured. For example, the correspondences shown in some rows of the table in the present document may not be configured. As another example, appropriate transformations or adjustments (such as splitting, merging, etc.) can be made based on the above table. The names of the parameters shown in the headings of the above tables may also take other names recognized by the communication device, and the values or representations of the parameters may also be other values or representations recognized by the communication device. When implementing the above tables, other data structures can also be used, for example, arrays, queues, containers, stacks, linear tables, pointers, linked lists, trees, graphs, structure bodies, classes, unordered data arrays, or hash tables can be used.

[0232] The expression "predetermined" in the present invention can be understood as given, established in advance, stored, pre-stored, pre-agreed, pre-configured, hard-coded, or initially set.

[0233] Those skilled in the art will understand that the blocks and steps of the algorithms in the various examples described in connection with the embodiments of the invention disclosed herein may be implemented in the form of electronic hardware or by a combination of computer software and electronic hardware. Whether these functions are performed in the form of hardware or software depends on the specific applications and design constraints imposed on the technical solutions. Engineering personnel may use various methods to implement the described functions for each specific application, but such implementation should not be considered as leaving the scope of the present invention.

[0234] It should be understood by those skilled in the art that, for convenience and brevity of description, the specific operational processes of the systems, devices and units described above may refer to the corresponding processes in the above-mentioned embodiments of the method and are not repeated.

[0235] The foregoing describes only some specific embodiments of the present invention, but the scope of the present invention is not limited thereto. Any changes or substitutions that are obvious to those skilled in the art within the technical scope of the present invention should fall within the protection scope of the present invention. Accordingly, the scope of the invention should be determined by the protection scope of the claims.

Claims (27)

1. A method for providing a failure report performed by the terminal and including: determining whether to trigger a direct link (SL) persistent listen-before-transmit (LBT) failure report and determining an uplink resource for transmitting the SL persistent LBT failure report; wherein the determination of the uplink resource for transmitting the LBT SL persistent failure report includes: determining that the terminal has an uplink resource usable for the new transmission that is capable of accommodating the LBT SL persistent failure report and its subheader; and determining the uplink resource used for the new transmission as the uplink resource for transmitting the LBT SL persistent failure report; or determining that there is no uplink resource available for the terminal to use for the new transmission and/or that the uplink resource available for the new transmission is not capable of accommodating the LBT SL persistent failure report and its subheader; launching a scheduling request (SR); and determining an SR configuration associated with the SR being triggered and transmitting an SR based on the SR configuration to request an uplink resource for transmitting a report of a persistent LBT SL failure; and transmitting a report to the network device about a persistent LBT SL failure on the uplink resource. 2. The method according to claim 1, wherein determining the need to initiate the provision of a report on a persistent failure of the LBT SL includes at least one of the following: determining by the terminal the necessity to start providing a report on the persistent failure of the LBT SL in the event that the granularity of detecting the persistent failure of the LBT SL is the granularity of the resource pool, and the terminal determines that at least one resource pool causes the persistent failure of the LBT SL, and the persistent failure of the LBT SL in at least one resource pool is not eliminated; determining by the terminal of the necessity to start providing a report on the LBT SL persistent failure in the event that the granularity of detecting the LBT SL persistent failure is the granularity of a frequency band portion (BWP), the terminal determines that at least one BWP or cell causes the LBT SL persistent failure, and the LBT SL persistent failure in at least one BWP or cell is not eliminated. 3. The method according to claim 1, wherein determining the need to initiate the provision of a report on a persistent failure of the LBT SL includes: determining by the terminal the necessity to start providing a report on the persistent failure of the LBT SL in the event that the granularity of detecting the persistent failure of the LBT SL is the granularity of a set of resource blocks (RBs), the terminal determines that at least one set of RBs causes the persistent failure of the LBT SL, and the persistent failure of the LBT SL in at least one set of RBs is not eliminated. 4. The method of claim 1, wherein the SR configuration associated with the SR being launched includes any of the following: a dedicated SR configuration, wherein the dedicated SR configuration is an SR configuration designed to eliminate the persistent failure of the LBT SL; any available SR configuration; or the earliest arriving SR configuration among at least one available SR configuration. 5. The method according to claim 1, wherein determining the uplink resource for transmitting the LBT SL persistent failure report further includes: determining that no SR configuration is associated with the SR being launched; and starting a random access channel (RACH), initiating the RACH based on the allocated RACH resource to request an uplink resource for transmitting a report of the LBT SL persistent failure; wherein the allocated RACH resource is a RACH resource dedicated to recovering from the LBT SL persistent failure. 6. A method for providing a failure report performed by a network device and comprising: transmitting configuration information to the terminal, wherein the configuration information includes a dedicated scheduling request (SR) configuration and/or a dedicated random access channel (RACH) configuration; wherein the dedicated SR configuration and/or the dedicated RACH configuration are used to assist the terminal in requesting an uplink resource from the network device, and the uplink resource is used to transmit the LBT SL persistent failure report. 7. A communication device comprising a processor and a memory in which a computer program is stored, and the processor is configured to execute the computer program stored in the memory so that the device performs the method according to any one of claims 1-5. 8. A machine-readable storage medium on which commands are stored, the execution of which carries out the method according to any of paragraphs 1-5.