Method and apparatus for reporting failure reports

Abstract

Embodiments of this disclosure disclose a method and apparatus for reporting failure reports, applicable to sidelink-unlicensed (SL-U) scenarios in unlicensed frequency bands, the method comprising the steps of: determining that a terminal device has triggered the reporting of a sidelink (SL) consistent listen before talk (LBT) failure report; determining an uplink resource to transmit the SL-consistent LBT failure report; and the terminal device transmitting the SL-consistent LBT failure report to a network device via the uplink resource. By implementing embodiments of this disclosure, when a terminal device determines that it has triggered the reporting of an SL-consistent LBT failure report, the terminal device can quickly report the SL-consistent LBT failure report to the network device via the uplink resource, enabling the network device to perform timely recovery processing for SL-consistent LBT failures, avoiding the terminal device continuously triggering connection rebuilding processes, and improving the efficiency of data transmission.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technologies, and particularly to a method for reporting a failure report and an apparatus therefor.

Background Art

[0002] In related technologies, Release R18 supports the use of unlicensed spectrum in sidelink (also called direct connection communication, Sidelink, SL) communication. In order for a terminal device to transmit Sidelink data in unlicensed spectrum, LBT (listen before talk) is required. A consistent LBT mechanism is also applicable to Sidelink communication in unlicensed spectrum.

[0003] However, currently, there is a lack of effective means for reporting SL consistent LBT failure reports.

Summary of the Invention

[0004] Embodiments of the present disclosure provide a method for reporting a failure report and an apparatus therefor applicable to a terminal sidelink (sidelink-unlicensed, SL-U) scenario in an unlicensed frequency band. When a terminal device determines to trigger the reporting of an SL consistent LBT failure report, the terminal device can quickly report the SL consistent LBT failure report to a network device via an uplink resource, so that the network device can perform timely recovery processing for the SL consistent LBT failure, avoid the terminal device continuously triggering a connection reconstruction process, and improve the efficiency of data transmission.

[0005] According to a first aspect, embodiments of the present disclosure provide a method for reporting a failure report, the method being executed by a terminal device, and the method comprising: The steps include determining to trigger the reporting of a sidelink (SL) consistent listening before talk (LBT) failure report, and determining the uplink resource to transmit the SL consistent LBT failure report, The step includes sending the SL consistent LBT failure report from the uplink resource to the network device.

[0006] In this proposed technology, when a terminal device determines that it has triggered the reporting of an SL-consistent LBT failure report, it is possible to quickly report the SL-consistent LBT failure report to a network device using the determined uplink resource. This allows the network device to perform timely recovery processing for the SL-consistent LBT failure, avoiding the terminal device continuously triggering the connection reconstruction process and improving the efficiency of data transmission.

[0007] In one possible implementation, the decision to trigger the reporting of the sidelink (SL) consistent listening before talk (LBT) failure report is: The detection granularity for the SL-consistent LBT failure is resource pool granularity, and the terminal device determines that at least one resource pool triggered the SL-consistent LBT failure and that the SL-consistent LBT failure in the at least one resource pool has not been canceled, and the terminal device determines that it will trigger the reporting of the SL-consistent LBT failure report.

[0008] In another possible implementation, the decision to trigger the reporting of the sidelink (SL) consistent listening before talk (LBT) failure report is: The detection granularity for the SL-consistent LBT failure is resource block set (RB set) granularity, and the terminal device determines that at least one RB set triggered the SL-consistent LBT failure and that the SL-consistent LBT failure in at least one RB set has not been canceled, and the terminal device determines that it will trigger the reporting of the SL-consistent LBT failure report.

[0009] In another possible implementation, the decision to trigger the reporting of the sidelink (SL) consistent listening before talk (LBT) failure report is: The detection granularity for the SL-consistent LBT failure is bandwidth portion (BWP) granularity, and the terminal device determines that at least one BWP or cell triggered the SL-consistent LBT failure and that the SL-consistent LBT failure in the at least one BWP or cell has not been canceled, and the terminal device determines that it will trigger the reporting of the SL-consistent LBT failure report.

[0010] In one possible implementation, determining the uplink resource to transmit the SL-consistent LBT failure report is: The terminal device has an uplink resource for new transmission, and it is determined that the uplink resource for new transmission can accommodate the SL-consistent LBT failure report and the subheader of the SL-consistent LBT failure report. This includes determining the uplink resource for the new transmission as the uplink resource for transmitting the SL consistent LBT failure report.

[0011] In another possible implementation, determining the uplink resource to transmit the SL-consistent LBT failure report is: The terminal device determines that it does not have an uplink resource for new transmission, and / or that the uplink resource for new transmission cannot accommodate the SL-consistent LBT failure report and the subheader of the SL-consistent LBT failure report. Triggering a scheduling request (SR), This includes determining the SR configuration associated with the triggered SR, and making an SR transmission based on the SR configuration associated with the triggered SR to request an uplink resource to transmit the SL consistent LBT failure report.

[0012] In one possible implementation, the SR setting associated with the triggered SR is: A dedicated SR setting, which is an SR setting specifically for SL Consistent LBT failure recovery, Choose one of the available SR settings, It includes at least one of the available SR settings, the earliest received SR setting, and one of the following.

[0013] In one possible implementation, determining the uplink resource to transmit the SL-consistent LBT failure report is: It is determined that the triggered SR does not have an associated SR setting, The process involves triggering a Random Access Channel (RACH), initiating the RACH based on a dedicated RACH resource, and requesting an uplink resource to transmit the SL-consistent LBT failure report, wherein the dedicated RACH resource is a RACH resource dedicated to SL-consistent LBT failure recovery.

[0014] According to a second aspect, an embodiment of the present disclosure provides a method for reporting another failure report, the method being performed by a network device, and the method is A step of transmitting configuration information to a terminal device, wherein the configuration information includes dedicated scheduling request (SR) settings and / or dedicated random access channel (RACH) settings, Here, the dedicated SR setting and / or the dedicated RACH setting are for assisting the terminal device in requesting uplink resources from the network device, and the uplink resources are for transmitting sidelink (SL) consistent listen before talk (LBT) failure reports.

[0015] According to a third aspect, embodiments of the present disclosure provide a communication device comprising some or all of the functions of a terminal device that implements the method described in the first aspect, for example, the functions of the communication device may comprise some or all of the functions in some or all embodiments of the present disclosure, or they may comprise functions that implement any one embodiment of the present disclosure independently. The functions can be implemented by hardware, which can also be implemented by the hardware running corresponding software. The hardware or software comprises one or more units or modules corresponding to the functions.

[0016] In one implementation, the structure of the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions of the above method. The transceiver module supports communication between the communication device and other devices. The communication device may further include a storage module, which is used to connect the transceiver module and the processing module, and which stores the computer programs and data required for the communication device.

[0017] 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 memory.

[0018] According to a fourth aspect, embodiments of the present disclosure provide a communication device that comprises some or all of the functions of a network device that implements the method described in the second aspect, for example, the functions of the communication device may comprise some or all of the functions in some or all embodiments of the present disclosure, or may comprise functions that implement any one embodiment of the present disclosure independently. The functions can be implemented by hardware, which can also be implemented by the hardware running corresponding software. The hardware or software comprises one or more units or modules that correspond to the functions.

[0019] In one implementation, the structure of the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions of the above method. The transceiver module supports communication between the communication device and other devices. The communication device may further include a storage module, which is used to connect the transceiver module and the processing module, and which stores the computer programs and data required for the communication device.

[0020] According to the fifth and sixth aspects, embodiments of the present disclosure provide a communication device which includes a processor which performs the method described in the first aspect when calling a computer program in memory.

[0021] According to the sixth aspect, an embodiment of the present disclosure provides a communication device which includes a processor which, when calling a computer program in memory, performs the method described in the second aspect.

[0022] According to the seventh aspect, an embodiment of the present disclosure provides a communication device comprising a processor and memory, the memory storing a computer program, and the processor causing the communication device to perform the method described in the first aspect by executing the computer program stored in the memory.

[0023] According to the eighth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory. A computer program is stored in the memory, and the processor executes the computer program stored in the memory to cause the communication device to execute the method described in the second aspect above.

[0024] According to the ninth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processor, and the processor executes the code instructions to cause the device to execute the method described in the first aspect above.

[0025] According to the tenth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processor, and the processor executes the code instructions to cause the device to execute the method described in the second aspect above.

[0026] According to the eleventh aspect, an embodiment of the present disclosure provides a failure report reporting system, which includes the communication device described in the third aspect and the communication device described in the fourth aspect, or the system includes the communication device described in the fifth aspect and the communication device described in the sixth aspect, or the system includes the communication device described in the seventh aspect and the communication device described in the eighth aspect, or the system includes the communication device described in the ninth aspect and the communication device described in the tenth aspect.

[0027] According to the twelfth aspect, an embodiment of the present disclosure provides a computer-readable storage medium for storing instructions used in the terminal device. When the instructions are executed, the terminal device is caused to execute the method described in the first aspect above.

[0028] According to the 13th aspect, an embodiment of the present disclosure provides a readable storage medium for storing instructions used for the network device, and when the instructions are executed, causes the network device to perform the method described in the second aspect.

[0029] According to the fourteenth aspect, the disclosure further provides a computer program product, which, when executed on a computer, causes the computer to perform the method described in the first aspect.

[0030] According to the 15th aspect, the Disclosure further provides a computer program product, which, when executed on a computer, causes the computer to perform the method described in the second aspect.

[0031] According to the 16th aspect, the Disclosure provides a chip system which includes at least one processor and interface to support a terminal device in realizing a function according to the first aspect, such as determining or processing at least one of the data and information relating to the method described above. In one possible design, the chip system further includes memory which stores computer programs and data required by the terminal device. The chip system may consist of a chip, or it may include a chip and other discrete devices.

[0032] According to the 17th aspect, the Disclosure provides a chip system which includes at least one processor and interface to support a network device in realizing a function according to a second aspect, such as determining or processing at least one of the data and information relating to the above method. In one possible design, the chip system further includes memory which stores computer programs and data required by a terminal device. The chip system may consist of a chip, or it may include a chip and other discrete devices.

[0033] According to the 18th aspect, the Disclosure provides a computer program which, when executed on a computer, causes the computer to perform the method described in the first aspect.

[0034] According to the 19th aspect, the Disclosure provides a computer program which, when executed on a computer, causes the computer to perform the method described in the second aspect above. [Brief explanation of the drawing]

[0035] To more clearly illustrate the technical concepts in the embodiments or background art of this disclosure, the drawings necessary for use in the embodiments or background art of this disclosure are described below. [Figure 1] This is a schematic diagram of the architecture of the communication system provided by the embodiments of this disclosure. [Figure 2] This is a schematic flowchart of the failure reporting method provided by the embodiments of this disclosure. [Figure 3] This is a flowchart of the failure reporting method provided by the embodiments of this disclosure. [Figure 4] This is a flowchart of the failure reporting method provided by the embodiments of this disclosure. [Figure 5] This is a flowchart of another failure reporting method provided by the embodiments of this disclosure. [Figure 6] This is a schematic diagram of a communication device provided by the embodiments of this disclosure. [Figure 7] This is a schematic diagram of another communication device provided by the embodiments of this disclosure. [Figure 8] This is a schematic diagram of the chip provided by the embodiments of this disclosure. [Modes for carrying out the invention]

[0036] The embodiments of this disclosure will be described in detail below, examples of which are shown in the accompanying drawings, where the same or similar reference numerals from beginning to end indicate the same or similar elements or elements having the same or similar function. The embodiments described below with reference to the accompanying drawings are for illustrative purposes only and should not be understood as limitations to this disclosure. In the description of this disclosure, unless otherwise stated, “or” means “or,” for example, “A or B” can mean A or B, for example, “TD basis vector or DD basis vector” in this specification can mean TD basis vector or DD basis vector, and “and / or” in this specification is solely for the purpose of describing the relationship between related objects and indicates that three relationships are possible. For example, “A and / or B” can mean three situations: A exists alone, A and B exist together, or B exists alone.

[0037] The terms used in this disclosure are for the sole purpose of describing specific embodiments and are not intended to limit the embodiments of this disclosure. The singular forms “one,” “the said,” and “the said” as used in this disclosure and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise.

[0038] In the embodiments of this disclosure, terms such as first, second, third, etc., may be used to describe various types of information, but it should be understood that this information should not be limited to these terms. These terms are used solely to distinguish information of the same type from one another. For example, without departing the scope of this disclosure, first information may be called second information, and similarly, second information may be called first information. Depending on the context, for example, the word "then" as used herein may be interpreted as "when," "in the case of," or "in response to a decision."

[0039] The embodiments of this disclosure will be described in detail below, and examples of such embodiments are shown in the accompanying drawings, where the same or similar reference numerals from beginning to end indicate the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are for illustrative purposes of this disclosure and should not be understood as limitations to this disclosure.

[0040] Furthermore, to support direct communication between terminal devices, a direct connection communication method (also called Sidelink or SL) has been introduced, and the interface between terminal devices is PC-5. Depending on the correspondence between the transmitting and receiving terminal devices, Sidelink supports three types of transmission methods, such as unicast, multicast, and broadcast. The transmitting terminal device sends Sidelink Control Information (SCI) via PSCCH (Physical Sidelink Control Channel) and then sends second-stage SCI via PSSCH (Physical Sidelink Shared Channel), which includes the resource location and source and target identifiers for data transmission. For data packets with HARQ (Hybrid Automatic Repeat request) feedback enabled, the terminal device receives HARQ-ACK (Hybrid Automatic Retransmission Request Acknowledgement) feedback to the PSSCH (Physical Sidelink Feedback Channel) via the PSFCH (Physical Sidelink Feedback Channel).

[0041] Sidelink communication has two types of transmission resource allocation methods: one is a network dynamic scheduling method (resource allocation mode 1), and the other is a method in which the terminal device autonomously selects from a resource pool broadcast by the network (resource allocation mode 2). Here, dynamic scheduling means that the network dynamically allocates Sidelink transmission resources to the terminal device based on the terminal device's buffer data report, while autonomous selection means that the terminal device randomly selects transmission resources from a resource pool broadcast by the network or a pre-configured resource pool. A network device can configure multiple resource pools for terminal devices in a single BWP (Band Width Part). The specific allocation method used is configured by the network device using RRC (Radio Resource Control) signaling.

[0042] NR-U (New Radio Unlicensed for 5G) is a 3GPP (3rd Generation Partnership Project) release R16 proposal that provides the technology necessary for carriers to fully integrate unlicensed spectrum into their 5G networks. NR-U supports uplink and downlink operation in unlicensed frequency bands. In NR-U, both downlink and uplink channel access rely on listen-before-talk (LBT) characteristics. The radio device or base station must first "sens" the communication channel and discover that there is no communication before transmission. If one communication channel is an unlicensed broadband carrier (e.g., several hundred megahertz), the LBT process relies on detecting energy levels in multiple subbands of the communication channel. LBT parameters (type / duration, clear channel evaluation parameters, etc.) are set on the radio device by the base station.

[0043] Consistent LBT failure is a new characteristic defined in NR-U, where terminal devices count the number of uplink LBT failures per BWP. To statistically track consistent LBT failures, network devices configure terminal devices with a consistent LBT failure maximum count (lbt-FailureInstanceMaxCount) and a consistent LBT failure detection timer (lbt-FailureDetectionTimer) per serving cell via RRC signaling (lbt-FailureRecoveryConfig). Terminal devices maintain a variable (LBT_counter) per cell, which is initially set to 0. For each activated cell with lbt-FailureRecoveryConfig configured, when a terminal device receives an LBT failure instruction delivered by the physical layer, it starts or restarts the consistent LBT failure detection timer, increments LBT_counter by 1, and when LBT_counter exceeds the consistent LBT failure maximum count, the active BWP in that cell triggers a consistent LBT failure. If the consistent LBT failure detection timer expires, or if the upper layer resets the maximum number of consistent LBT failures / consistent LBT failure detection timer, or if all consistent LBT failures in this serving cell are canceled, the terminal device resets the LBT_counter to 0. If the terminal device detects that a consistent LBT failure has occurred in the active BWP of a PCell (Primary Cell) or PSCell (Primary Secondary Cell), and there are other BWPs in that cell configured with a PRACH (Physical Random Access Channel) resource, the terminal device triggers a BWP switch, switches to the BWP configured with the PRACH resource, and initiates a RACH (Random Access Channel) flow.If a terminal device detects consistent LBT failures in all N BWPs configured with PRACH resources in the primary cell, the terminal device initiates a radio link failure (RLF) recovery flow. If a consistent LBT failure is detected in the active BWP of a SCell (secondary cell), the terminal device notifies the network side via a Media Access Control element MAC CE of the cell identifier where the consistent LBT failure occurred. The MAC CE may contain multiple cell identifiers where the consistent LBT failure was detected, and the MAC CE is transmitted in other serving cells where the consistent LBT failure has not occurred.

[0044] In related technologies, Release R18 supports the use of the unlicensed spectrum in sidelink communication, and LBT is required for terminal devices to transmit Sidelink data in the unlicensed spectrum. The consistent LBT mechanism is also applicable to Sidelink communication in the unlicensed spectrum.

[0045] However, there is currently a lack of effective means to report SL-consistent LBT failures.

[0046] Therefore, the embodiments of this disclosure provide a failure reporting method that enables a terminal device to quickly report an SL-consistent LBT failure report to a network device via an uplink resource when the terminal device decides to trigger the reporting of an SL-consistent LBT failure report. This allows the network device to perform timely recovery processing for SL-consistent LBT failures, avoiding the terminal device continuously triggering the connection rebuilding process and improving the efficiency of data transmission.

[0047] To better understand the failure reporting method disclosed in the embodiments of this disclosure, the communication system applicable to the embodiments of this disclosure will be described below.

[0048] Referring to Figure 1, Figure 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure. The communication system may include, but is not limited to, one network device and one terminal device. The number and form of devices shown in Figure 1 are for illustrative purposes only and do not limit the embodiments of the present disclosure, and actual applications may include two or more network devices and two or more terminal devices. The communication system shown in Figure 1 is an example in which one network device 101 and one terminal device 102 are included.

[0049] The technical concepts of the embodiments of this disclosure are applicable to various communication systems, such as long-term evolution (LTE) systems, 5th generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems. The side links in the embodiments of this disclosure may also be called side links or direct communication links.

[0050] In embodiments of this disclosure, the network device 101 is an entity for sending and receiving network-side signals. For example, the network device 101 may be an evolved NodeB (eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. Embodiments of this disclosure are not limited to the specific technology used by the network device or the specific form of the device. The network device provided by embodiments of this disclosure may consist of a central unit (CU) and a distributed unit (DU), where the CU may also be called a control unit, and the CU-DU structure can be used to divide the protocol layer of a network device, such as a base station, with some of the functions of the protocol layer being centrally controlled by the CU, and the remaining or all of the functions of the protocol layer being distributed to the DU, with the CU centrally controlling the DU.

[0051] In the embodiments of this disclosure, terminal device 102 is an entity for sending and receiving user-side signals, such as a mobile phone. Terminal devices may also be called terminals, user equipment (UE), mobile stations (MS), mobile terminals (MT), etc. Terminal devices may also be automobiles with communication functions, smart cars, mobile phones, wearable devices, tablets (Pads), computers with wireless transmission and reception functions, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminal devices in industrial control, wireless terminal devices in self-driving, wireless terminal devices in remote medical surgery, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, wireless terminal devices in smart homes, etc. The embodiments of this disclosure do not limit the specific technologies or specific device forms used by terminal devices.

[0052] Furthermore, the communication systems described in the embodiments of this disclosure are intended to more clearly illustrate the technical solutions of the embodiments of this disclosure and do not limit the technical solutions provided by the embodiments of this disclosure. As those skilled in the art will see, the technical solutions provided by the embodiments of this disclosure are applicable to similar technical problems as system architectures evolve and new business scenarios emerge.

[0053] The failure reporting method and apparatus provided by this disclosure will be described in detail below, in conjunction with the drawings.

[0054] Referring to Figure 2, Figure 2 is a schematic flowchart of the failure reporting method provided by an embodiment of the present disclosure. The failure reporting method according to an embodiment of the present disclosure can be executed by a terminal device. As shown in Figure 2, the method may, but is not limited to, the following steps.

[0055] In step 201, it is decided to trigger the reporting of an SL-consistent LBT failure report and to determine the uplink resource to which the SL-consistent LBT failure report will be transmitted.

[0056] In the embodiments of this disclosure, the terminal device is in an RRC connection state. In one possible implementation, the terminal device may operate in resource allocation mode 1 or in resource allocation mode 2.

[0057] In one possible implementation, a network device can set a maximum number of SL-consistent LBT failures and an SL-consistent LBT failure detection timer on a terminal device in a single serving cell via RRC signaling to statistically track SL-consistent LBT failures. A variable is maintained for each terminal device cell, with an initial value of 0. For each activated and RRC-signaled cell, when the terminal device receives an LBT failure instruction delivered by the physical layer, it starts or restarts the consistent LBT failure detection timer, increments the variable by 1, and when the value of the variable becomes equal to or greater than the maximum number of consistent LBT failures, the serving cell triggers an SL-consistent LBT failure.

[0058] In embodiments of this disclosure, different detection granularities for SL-consistent LBT failures result in different implementations for determining whether to report an SL-consistent LBT failure. In one possible implementation, the detection granularity may include, but is not limited to, resource pool granularity, RB set (Resource Block set) granularity, BWP granularity, and the like.

[0059] In embodiments of this disclosure, if it is determined that it is necessary to trigger the reporting of an SL-consistent LBT failure report, the terminal device may determine an uplink resource for transmitting the SL-consistent LBT failure report. In one possible implementation, the terminal device may transmit the SL-consistent LBT failure report on an uplink resource for new transmission, which is an authorized uplink resource for the initial transmission (separate from retransmission) of a data packet. In another possible implementation, if the terminal device does not have an uplink resource for new transmission, it may trigger an SR, request an uplink resource with the SR setting associated with the triggered SR, and transmit the SL-consistent LBT failure report on that uplink resource. In yet another possible implementation, if the terminal device does not have an uplink resource for new transmission, the terminal device may request an uplink resource with a dedicated RACH resource and transmit the SL-consistent LBT failure report.

[0060] In step 202, the uplink resource sends an SL consistent LBT failure report to the network device.

[0061] Selectively, a terminal device may send the SL-consistent LBT failure report to a network device via an uplink resource. In one possible implementation, the terminal device may send the SL-consistent LBT failure report to a network device via a MAC CE on the uplink resource. Here, in some embodiments, the SL-consistent LBT failure report may include cell identification information where the SL-consistent LBT failure was detected. Selectively, the SL-consistent LBT failure report may instruct the network device on the cell identifier where the SL-consistent LBT failure occurred, thereby enabling the network device to perform timely recovery processing for the SL-consistent LBT failure after receiving the SL-consistent LBT failure report.

[0062] By implementing the embodiments of this disclosure, when a terminal device determines that it has triggered the reporting of an SL-consistent LBT failure report, the terminal device can quickly report the SL-consistent LBT failure report to a network device via an uplink resource. This allows the network device to perform timely recovery processing for the SL-consistent LBT failure, avoiding the terminal device continuously triggering the connection reconstruction process and improving the efficiency of data transmission.

[0063] Furthermore, if the detection granularity of SL-consistent LBT failures differs in the embodiments of this disclosure, the implementation that determines whether to report an SL-consistent LBT failure report will also differ. In some embodiments of this disclosure, if the detection granularity of SL-consistent LBT failures is resource pool granularity, and the terminal device determines that at least one resource pool has triggered an SL-consistent LBT failure and that the SL-consistent LBT failure in at least one resource pool has not been canceled, the terminal device may determine to trigger the reporting of an SL-consistent LBT failure report.

[0064] Selectively, if the detection granularity of an SL-consistent LBT failure is resource pool granularity, and the terminal device determines that at least one resource pool has triggered an SL-consistent LBT failure and will not cancel it, the terminal device may decide to trigger the reporting of an SL-consistent LBT failure report. In embodiments of this disclosure, if the terminal device decides to trigger the reporting of an SL-consistent LBT failure report, it may determine the uplink resource to transmit the SL-consistent LBT failure report, and the uplink resource may transmit the SL-consistent LBT failure report to a network device. Hereinafter, the implementation of determining the uplink resource to transmit the SL-consistent LBT failure report in this embodiment can be implemented in any of the manners of each embodiment of this disclosure, and is not limited thereto, nor is further explanation provided.

[0065] In some embodiments of the present disclosure, the detection granularity of SL-consistent LBT failures is RB set granularity, and the terminal device may determine to trigger reporting of an SL-consistent LBT failure if it determines that at least one RB set triggered an SL-consistent LBT failure and that the SL-consistent LBT failure in at least one RB set has not been canceled.

[0066] Selectively, if the detection granularity of an SL-consistent LBT failure is RB set granularity, and the terminal device determines that at least one RB set triggered an SL-consistent LBT failure and has not been canceled, the terminal device may decide to trigger the reporting of an SL-consistent LBT failure report. In embodiments of this disclosure, if the terminal device decides to trigger the reporting of an SL-consistent LBT failure report, it may determine an uplink resource to transmit the SL-consistent LBT failure report, and the uplink resource may transmit the SL-consistent LBT failure report to a network device. Hereinafter, the implementation of determining the uplink resource to transmit the SL-consistent LBT failure report in this embodiment can be implemented in any of the methods of each embodiment of this disclosure, and is not limited thereto, nor is it described further.

[0067] In some embodiments of the present disclosure, the detection granularity for SL-consistent LBT failures is bandwidth portion (BWP) granularity, and the terminal device determines that if it determines that at least one BWP or cell has triggered an SL-consistent LBT failure and that the SL-consistent LBT failure in at least one BWP or cell has not been canceled, the terminal device will trigger the reporting of an SL-consistent LBT failure report.

[0068] Selectively, if the detection granularity for SL-consistent LBT failures is BWP granularity, and the terminal device determines that at least one BWP / cell (where only one active BWP is supported in a single cell) has triggered an SL-consistent LBT failure and has not been canceled, the terminal device may decide to trigger the reporting of an SL-consistent LBT failure report. In embodiments of this disclosure, if the terminal device decides to trigger the reporting of an SL-consistent LBT failure report, it may determine an uplink resource to transmit the SL-consistent LBT failure report, and the uplink resource may transmit the SL-consistent LBT failure report to a network device. Hereinafter, the implementation of determining the uplink resource to transmit the SL-consistent LBT failure report in this embodiment can be implemented in any of the manners of each embodiment of this disclosure, and is not limited thereto, nor is further explanation provided.

[0069] In the embodiments of this disclosure, the SL-consistent LBT failure report can be transmitted using the uplink resource for new transmissions in the terminal device. Referring to Figure 3, Figure 3 is a flowchart of the failure report reporting method provided by the embodiments of this disclosure. This method can be performed by the terminal device. As shown in Figure 3, the method may, but is not limited to, the following steps.

[0070] In step 301, it is decided to trigger the reporting of an SL Consistent LBT failure report.

[0071] In the embodiments of this disclosure, the implementation of step 301 can be implemented in any of the manners of each embodiment of this disclosure, and is not limited thereto, nor is it described further.

[0072] In step 302, it is determined that the terminal device has an uplink resource for new transmission and that the uplink resource for new transmission can accommodate the SL-consistent LBT failure report and the subheader of the SL-consistent LBT failure report.

[0073] Selectively, if a terminal device decides to trigger the reporting of an SL-consistent LBT failure report, it can determine whether it has an uplink resource for a new transmission and whether that uplink resource can accommodate the SL-consistent LBT failure report and its subheader. If it has an uplink resource for a new transmission and that uplink resource can accommodate the SL-consistent LBT failure report and its subheader, the terminal device can instruct the entities to multiplex and assemble in order to generate the SL-consistent LBT failure report.

[0074] In step 303, the uplink resource for new transmissions is determined to be the uplink resource for transmitting SL-consistent LBT failure reports.

[0075] In other words, if a terminal device has an uplink resource for a new transmission and determines that the uplink resource for the new transmission can accommodate an SL-consistent LBT failure report and its subheader, it can determine that the uplink resource is for transmitting the SL-consistent LBT failure report.

[0076] In step 304, the uplink resource sends an SL consistent LBT failure report to the network device.

[0077] In the embodiments of this disclosure, the implementation of step 304 can be implemented in any of the manners of each embodiment of this disclosure, and is not limited to these, nor is further explanation provided herein.

[0078] By implementing the embodiments of this disclosure, if a terminal device determines that it has an uplink resource for a new transmission and that the uplink resource for the new transmission can accommodate an SL-consistent LBT failure report and a subheader of the SL-consistent LBT failure report, the uplink resource for the new transmission can quickly report the SL-consistent LBT failure report to the network device. This allows the network device to perform recovery processing for the SL-consistent LBT failure in a timely manner, avoiding the terminal device continuously triggering the connection reconstruction process and improving the efficiency of data transmission.

[0079] If the terminal device does not have an uplink resource for new transmission, the terminal device in the embodiment of this disclosure triggers an SR, requests an uplink resource with the SR setting associated with the triggered SR, and sends the SL-consistent LBT failure report on the uplink resource. Referring to Figure 4, Figure 4 is a flowchart of the failure report reporting method provided by the embodiment of this disclosure. This method can be performed by the terminal device. As shown in Figure 4, the method may, but is not limited to, the following steps.

[0080] In step 401, it is decided to trigger the reporting of an SL Consistent LBT failure report.

[0081] In the embodiments of this disclosure, the implementation of step 401 can be implemented in any of the manners of each embodiment of this disclosure, and is not limited to these, nor is further explanation provided herein.

[0082] In step 402, it is determined that the terminal device does not have an uplink resource for the new transmission, and / or that the uplink resource for the new transmission cannot accommodate the SL-consistent LBT failure report and the subheader of the SL-consistent LBT failure report.

[0083] Selectively, if the terminal device decides to trigger the reporting of an SL-consistent LBT failure report, it can determine whether it has an uplink resource for a new transmission and whether that uplink resource can accommodate the SL-consistent LBT failure report and its subheader. If there is no uplink resource for a new transmission and / or the uplink resource for a new transmission cannot accommodate the SL-consistent LBT failure report and / or its subheader, the terminal device performs step 403, i.e., the terminal device triggers an SR (Scheduled Request).

[0084] In step 403, trigger SR.

[0085] In step 404, the SR configuration associated with the triggered SR is determined, and an SR transmission is made using the SR configuration associated with the triggered SR to request an uplink resource to transmit the SL-consistent LBT failure report.

[0086] In one possible embodiment, the SR setting associated with the triggered SR is: A dedicated SR setting that may be specifically for SL Consistent LBT failure recovery, Choose one of the available SR settings, It may include, but is not limited to, the earliest received SR setting among at least one available SR setting, and one of the following.

[0087] In embodiments of the present disclosure, if a terminal device determines that there is no uplink resource available for a new transmission and / or that the uplink resource available for the new transmission cannot accommodate the SL-consistent LBT failure report and its subheader, it triggers an SR and sets a dedicated SR setting to the corresponding setting for this triggered SR, i.e., it sends an SR with the dedicated SR setting to request an uplink resource to transmit the SL-consistent LBT failure report.

[0088] In embodiments of the present disclosure, if a terminal device determines that there is no uplink resource available for a new transmission and / or that the uplink resource for the new transmission is unable to accommodate the SL-consistent LBT failure report and its subheader, it triggers an SR and sets one of the available SR settings as the corresponding setting for this triggered SR, i.e., it sends an SR with one of the available SR settings to request an uplink resource to transmit the SL-consistent LBT failure report.

[0089] In embodiments of the present disclosure, if a terminal device determines that there are no uplink resources available for a new transmission and / or that the uplink resources available for the new transmission cannot accommodate the SL-consistent LBT failure report and the subheader of the SL-consistent LBT failure report, it triggers an SR and sets the SR setting in which the SR resource arrives earliest among any available SR settings as the corresponding setting for this triggered SR, i.e., it sends an SR in the SR setting in which the SR resource arrives earliest among the available SR settings to request an uplink resource to transmit the SL-consistent LBT failure report.

[0090] In embodiments of this disclosure, a dedicated SR setting for SL-consistent LBT failure recovery may be defined. In one possible implementation, the dedicated SR setting may be indicated by a parameter, which may be an sl-LBT-schedulingRequestID, and the SchedulingRequestId (scheduling request identifier) ​​associated with the sl-LBT-schedulingRequestID is used to indicate the dedicated SR setting for SL-consistent LBT failure recovery. Other embodiments may exist and are not limited to those described herein.

[0091] In one possible implementation, the dedicated SR setting is a setting for a single terminal device (per UE), and optionally, the dedicated SR setting may be carried to the SL-PHY-MAC-RLC-Config setting. Other embodiments may exist and are not limited to this embodiment. In the embodiments of this disclosure, the dedicated SR setting may be set on the terminal device by the network device, or it may be pre-configured on the terminal device.

[0092] In one possible implementation, a dedicated SR configuration may consist of one set of PUCCH (Physical Uplink Control Channel) resources, and these PUCCH resources can be distributed across different BWPs and cells. A single BWP may have a maximum of one PUCCH resource configured for a dedicated SR configuration.

[0093] In step 405, the uplink resource sends an SL consistent LBT failure report to the network device.

[0094] In the embodiments of this disclosure, the implementation of step 405 can be implemented in any of the manners of each embodiment of this disclosure, and is not limited to these, nor is further explanation provided herein.

[0095] By implementing the embodiments of this disclosure, a terminal device can trigger an SR, request an uplink resource with the SR settings associated with the triggered SR, and then promptly report the SL-consistent LBT failure report to the network device using the uplink resource. This allows the network device to perform timely recovery processing for SL-consistent LBT failures, avoiding the terminal device continuously triggering the connection rebuilding process and improving the efficiency of data transmission.

[0096] Embodiments of this disclosure provide a method for reporting failure reports, which can be performed by a terminal device, and which may include, but are not limited to, the following steps.

[0097] In step 401a, it is decided to trigger the reporting of an SL-consistent LBT failure report.

[0098] In the embodiments of this disclosure, the implementation of step 401a can be implemented in any of the manners of each embodiment of this disclosure, and is not limited to these, nor is further explanation provided herein.

[0099] In step 402a, trigger SR.

[0100] In step 403a, a dedicated SR setting is determined, and an SR transmission is performed using the dedicated SR setting to request an uplink resource to transmit the SL consistent LBT failure report.

[0101] In one implementation, the terminal device sets a dedicated SR setting to the setting corresponding to the triggered SR, and sends an SR using that dedicated SR setting to request an uplink resource to transmit an SL-consistent LBT failure report.

[0102] In embodiments of this disclosure, a dedicated SR setting for SL-consistent LBT failure recovery may be defined. In one possible implementation, the dedicated SR setting may be indicated by a parameter, which may be an sl-LBT-schedulingRequestID, and the SchedulingRequestId (scheduling request identifier) ​​associated with the sl-LBT-schedulingRequestID is used to indicate the dedicated SR setting for SL-consistent LBT failure recovery. Other embodiments may exist and are not limited to those described herein.

[0103] In one possible implementation, the dedicated SR setting is a setting for a single terminal device (per UE), and optionally, the dedicated SR setting may be carried to the SL-PHY-MAC-RLC-Config setting. Other embodiments may exist and are not limited to this embodiment. In the embodiments of this disclosure, the dedicated SR setting may be set on the terminal device by the network device, or it may be pre-configured on the terminal device.

[0104] In one possible implementation, a dedicated SR configuration may consist of one set of PUCCH (Physical Uplink Control Channel) resources, and these PUCCH resources can be distributed across different BWPs and cells. A single BWP may have a maximum of one PUCCH resource configured for a dedicated SR configuration.

[0105] In step 404a, the uplink resource sends an SL consistent LBT failure report to the network device.

[0106] In the embodiments of this disclosure, the implementation of step 404a can be implemented in any of the manners of each embodiment of this disclosure, and is not limited to these, nor is further explanation provided herein.

[0107] By implementing the embodiments of this disclosure, the terminal device triggers an SR, requests an uplink resource with a dedicated SR setting, and then promptly reports the SL-consistent LBT failure report to the network device using the uplink resource. This allows the network device to perform timely recovery processing for SL-consistent LBT failures, avoiding the terminal device continuously triggering the connection reconstruction process and improving the efficiency of data transmission.

[0108] Selectively, in some embodiments of the present disclosure, if an SR triggered by a terminal device does not have an associated SR setting, a Random Access Channel (RACH) may be triggered, and the RACH may be initiated based on a dedicated RACH resource to request an uplink resource to transmit an SL-consistent LBT failure report, where the dedicated RACH resource is a RACH resource dedicated to SL-consistent LBT failure recovery.

[0109] In one possible implementation, if a terminal device decides to trigger the reporting of an SL-consistent LBT failure report, and there is an uplink resource for a new transmission and that uplink resource can accommodate the SL-consistent LBT failure report and its subheader, the terminal device instructs the entities to multiplex and assemble to generate the SL-consistent LBT failure report; otherwise, the terminal device triggers an SR. If the terminal device triggers an SR and there is no dedicated SR setting, or no available SR setting (e.g., the terminal device does not have an SR setting), the terminal device triggers a RACH, initiates a RACH with a dedicated RACH resource, requests an uplink resource, and sends the SL-consistent LBT failure report.

[0110] In one possible implementation, the disclosure may define a dedicated RACH resource, and a terminal device may use the dedicated RACH resource to request an uplink resource and send an SL-consistent LBT failure report.

[0111] In one possible implementation, a new parameter such as sl-LBT-rachconfig may be defined, which may include a dedicated RACH resource for SL-consistent LBT failure recovery. Other embodiments may exist and are not limited to this embodiment.

[0112] In one possible implementation, the dedicated RACH resource may be configured for a single terminal device (per UE), and selectively, the dedicated RACH resource may be carried to the SL-PHY-MAC-RLC-Config configuration. Other embodiments may exist and are not limited to this embodiment. In the embodiments of this disclosure, the dedicated RACH resource may be configured on the terminal device by a network device, or may be pre-configured on the terminal device.

[0113] Embodiments of this disclosure provide a method for reporting failure reports, which can be performed by a terminal device, and which may include, but are not limited to, the following steps.

[0114] In step 401a, it is decided to trigger the reporting of an SL-consistent LBT failure report.

[0115] In the embodiments of this disclosure, the implementation of step 401a can be implemented in any of the manners of each embodiment of this disclosure, and is not limited to these, nor is further explanation provided herein.

[0116] In step 402a, trigger SR.

[0117] In step 403a, a dedicated SR setting is determined, and an SR transmission is performed using the dedicated SR setting to request an uplink resource to transmit the SL consistent LBT failure report.

[0118] In one implementation, the terminal device sets a dedicated SR setting to the setting corresponding to the triggered SR, and sends an SR using that dedicated SR setting to request an uplink resource to transmit an SL-consistent LBT failure report.

[0119] In embodiments of this disclosure, a dedicated SR setting for SL-consistent LBT failure recovery may be defined. In one possible implementation, the dedicated SR setting may be indicated by a parameter, which may be an sl-LBT-schedulingRequestID, and the SchedulingRequestId (scheduling request identifier) ​​associated with the sl-LBT-schedulingRequestID is used to indicate the dedicated SR setting for SL-consistent LBT failure recovery. Other embodiments may exist and are not limited to those described herein.

[0120] In one possible implementation, the dedicated SR setting is a setting for a single terminal device (per UE), and optionally, the dedicated SR setting may be carried to the SL-PHY-MAC-RLC-Config setting. Other embodiments may exist and are not limited to this embodiment. In the embodiments of this disclosure, the dedicated SR setting may be set on the terminal device by the network device, or it may be pre-configured on the terminal device.

[0121] In one possible implementation, a dedicated SR configuration may consist of one set of PUCCH (Physical Uplink Control Channel) resources, and these PUCCH resources can be distributed across different BWPs and cells. A single BWP may have a maximum of one PUCCH resource configured for a dedicated SR configuration.

[0122] In step 404a, the uplink resource sends an SL consistent LBT failure report to the network device.

[0123] In the embodiments of this disclosure, the implementation of step 404a can be implemented in any of the manners of each embodiment of this disclosure, and is not limited to these, nor is further explanation provided herein.

[0124] By implementing the embodiments of this disclosure, the terminal device triggers an SR, requests an uplink resource with a dedicated SR setting, and then promptly reports the SL-consistent LBT failure report to the network device using the uplink resource. This allows the network device to perform timely recovery processing for SL-consistent LBT failures, avoiding the terminal device continuously triggering the connection reconstruction process and improving the efficiency of data transmission.

[0125] Embodiments of this disclosure provide a method for reporting failure reports, which can be performed by a terminal device, and which may include, but are not limited to, the following steps.

[0126] In step 401b, it is decided to trigger the reporting of an SL-consistent LBT failure report.

[0127] In the embodiments of this disclosure, the implementation of step 401b can be implemented in any of the manners of each embodiment of this disclosure, and is not limited to these, nor is further explanation provided herein.

[0128] In step 402b, trigger SR.

[0129] In step 403b, one of the available SR settings is determined, and an SR transmission is made using the determined available SR setting to request an uplink resource to transmit an SL consistent LBT failure report.

[0130] In one implementation, the terminal device sets one of the available SR settings as the corresponding setting for this triggered SR, and sends an SR using one of the available SR settings to request an uplink resource to transmit the SL-consistent LBT failure report.

[0131] In step 404b, the uplink resource sends an SL consistent LBT failure report to the network device.

[0132] In the embodiments of this disclosure, the implementation of step 404b can be implemented in any of the manners of each embodiment of this disclosure, and is not limited to these, nor is further explanation provided herein.

[0133] By implementing the embodiments of this disclosure, a terminal device can trigger an SR, request an uplink resource with any available SR configuration, and then promptly report the SL-consistent LBT failure report to the network device using that uplink resource. This allows the network device to perform timely recovery processing for SL-consistent LBT failures, avoiding the terminal device continuously triggering the connection rebuilding process and improving the efficiency of data transmission.

[0134] Embodiments of this disclosure provide a method for reporting failure reports, which can be performed by a terminal device, and which may include, but are not limited to, the following steps.

[0135] In step 401c, it is decided to trigger the reporting of an SL-consistent LBT failure report.

[0136] In the embodiments of this disclosure, the implementation of step 401c can be implemented in any of the manners of each embodiment of this disclosure, and is not limited to these, nor is further explanation provided herein.

[0137] In step 402c, trigger SR.

[0138] In step 403c, determine which of the at least one available SR settings arrived first, and send an SR using the determined first available SR setting to request an uplink resource to transmit an SL consistent LBT failure report.

[0139] In one implementation, the terminal device selects the SR setting from among the available SR settings for which the SR resource arrives earliest as the corresponding setting for this triggered SR, and then sends an SR using the SR setting for which the SR resource arrived earliest, requesting an uplink resource to transmit the SL consistent LBT failure report.

[0140] In step 404c, the uplink resource sends an SL consistent LBT failure report to the network device.

[0141] In the embodiments of this disclosure, the implementation of step 404c can be implemented in any of the manners of each embodiment of this disclosure, and is not limited to these, nor is further explanation provided herein.

[0142] By implementing the embodiments of this disclosure, a terminal device can trigger an SR, request an uplink resource in the SR configuration in which the SR resource arrives earliest among any possible SR configurations, and then promptly report the SL-consistent LBT failure report to the network device using the uplink resource. This allows the network device to perform timely recovery processing for SL-consistent LBT failures, avoiding the terminal device continuously triggering the connection reconstruction process and improving the efficiency of data transmission.

[0143] It can be understood that the above embodiment describes an implementation of the failure report reporting method according to the embodiment of this disclosure from the terminal device side. The embodiment of this disclosure further proposes a failure report reporting method, and the implementation of said failure report reporting method will be described below from the network device side. Referring to Figure 5, Figure 5 is a flowchart of another failure report reporting method provided by the embodiment of this disclosure. This method can be executed by a network device. As shown in Figure 5, the method includes, but is not limited to, the following steps.

[0144] In step 501, configuration information is sent to the terminal device, and this configuration information may include dedicated SR settings and / or dedicated RACH settings.

[0145] In embodiments of the present disclosure, the dedicated SR setting and / or dedicated RACH setting can be used to assist a terminal device in requesting uplink resources from a network device, which can then be used to transmit SL-consistent LBT failure reports.

[0146] In embodiments of this disclosure, a dedicated SR setting may be defined for SL-consistent LBT failure recovery. In one possible implementation, the dedicated SR setting may be represented by a parameter, which may be an sl-LBT-schedulingRequestID, and the SchedulingRequestId (scheduling request identifier) ​​associated with the sl-LBT-schedulingRequestID is used to indicate a dedicated SR setting for SL-consistent LBT failure recovery.

[0147] In one possible implementation, the dedicated SR configuration is a configuration for a single terminal device (per UE), and optionally, the dedicated SR configuration may be passed to the SL-PHY-MAC-RLC-Config configuration. Other embodiments may exist and are not limited to this embodiment.

[0148] In one possible implementation, a dedicated SR configuration may consist of one set of PUCCH (Physical Uplink Control Channel) resources, and these PUCCH resources can be distributed across different BWPs and cells. A single BWP may have a maximum of one PUCCH resource configured for a dedicated SR configuration.

[0149] In one possible implementation, the disclosure may define a dedicated RACH resource, and a terminal device may request an uplink resource using the dedicated RACH resource to send an SL-consistent LBT failure report.

[0150] In one possible implementation, a new parameter such as sl-LBT-rachconfig may be defined, which may include a dedicated RACH resource for SL-consistent LBT failure recovery. Other embodiments may exist and are not limited to this embodiment.

[0151] In one possible implementation, the dedicated RACH resource may be configured for a single terminal device (per UE), and selectively, the dedicated RACH resource may be carried to the SL-PHY-MAC-RLC-Config configuration. Other embodiments may exist and are not limited to this embodiment.

[0152] By implementing the embodiments of this disclosure, a network device can configure dedicated SR settings and / or dedicated RACH settings for a terminal device, enabling the terminal device to request uplink resources with the dedicated SR settings and / or dedicated RACH settings. Furthermore, the terminal device can quickly report the SL-consistent LBT failure report to the network device using the uplink resources. This allows the network device to perform timely recovery processing for SL-consistent LBT failures, avoiding the terminal device continuously triggering the connection reconstruction process and improving the efficiency of data transmission.

[0153] The embodiments provided in the above disclosure describe the methods provided by the embodiments of the disclosure from the perspective of a terminal device and a network device, respectively. To implement each function of the methods provided by the embodiments of the above disclosure, the terminal device and the network device may include hardware structures and software modules, and each of the above functions is implemented in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module. Some of the above functions can be implemented in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module.

[0154] Referring to Figure 6, it is a schematic diagram of a communication device 60 provided by an embodiment of the present disclosure. The communication device 60 shown in Figure 6 may include a transceiver module 601 and a processing module 602. The transceiver module 601 may include a transmit module and / or a receive module, the transmit module may implement a transmit function and the receive module may implement a receive function, and the transceiver module 601 may implement a transmit function and / or a receive function.

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

[0156] If the communication device 60 is a terminal device, the processing module 602 determines that it will trigger the reporting of a sidelink (SL) consistent listen before talk (LBT) failure report, determines the uplink resource to which the SL consistent LBT failure report will be transmitted, and the transmitting / receiving module 601 transmits the SL consistent LBT failure report to the network device via the uplink resource.

[0157] In one implementation, the processing module 602 specifically determines that if the detection granularity of SL-consistent LBT failures is resource pool granularity, and the terminal device determines that at least one resource pool has triggered an SL-consistent LBT failure and that the SL-consistent LBT failure in at least one resource pool has not been canceled, the terminal device will trigger the reporting of an SL-consistent LBT failure report.

[0158] In another implementation, the processing module 602 specifically determines that if the detection granularity for SL-consistent LBT failures is resource block set (RB set) granularity, and the terminal device determines that at least one RB set has triggered an SL-consistent LBT failure and that the SL-consistent LBT failure in at least one RB set has not been canceled, then the terminal device will trigger the reporting of an SL-consistent LBT failure report.

[0159] In another implementation, the processing module 602 specifically determines that if the detection granularity for SL-consistent LBT failures is bandwidth portion (BWP) granularity, and the terminal device determines that at least one BWP or cell has triggered an SL-consistent LBT failure and that the SL-consistent LBT failure in at least one BWP or cell has not been canceled, the terminal device will trigger the reporting of an SL-consistent LBT failure report.

[0160] In one implementation, the processing module 602 specifically determines that the terminal device has an uplink resource for new transmission and that the uplink resource for new transmission can accommodate the SL-consistent LBT failure report and the subheader of the SL-consistent LBT failure report, and then determines the uplink resource for new transmission to be the uplink resource for transmitting the SL-consistent LBT failure report.

[0161] In another implementation, the processing module 602 specifically determines that the terminal device does not have an uplink resource for a new transmission and / or that the uplink resource for the new transmission cannot accommodate the SL-consistent LBT failure report and its subheader, triggers a scheduling request (SR), determines the SR setting associated with the triggered SR, and sends an SR based on the SR setting associated with the triggered SR to request an uplink resource to transmit the SL-consistent LBT failure report.

[0162] In one possible implementation, the SR setting associated with a triggered SR includes a dedicated SR setting which is an SR setting dedicated to SL-consistent LBT failure recovery, one of the available SR settings, and the earliest arriving SR setting among at least one available SR setting.

[0163] In one possible implementation, the processing module 602 further determines that the triggered SR does not have an associated SR setting, triggers a Random Access Channel (RACH), initiates the RACH based on a dedicated RACH resource, and requests an uplink resource to transmit the SL-consistent LBT failure report, where the dedicated RACH resource is a RACH resource dedicated to SL-consistent LBT failure recovery.

[0164] If the communication device 60 is a network device, the transceiver module 601 transmits configuration information to the terminal device, which includes dedicated scheduling request (SR) settings and / or dedicated random access channel (RACH) settings, where the dedicated SR settings and / or dedicated RACH settings are to assist the terminal device in requesting uplink resources from the network device, and the uplink resources are for transmitting sidelink (SL) consistent listening before talk (LBT) failure reports.

[0165] The specific methods by which each module of the apparatus in the above-described embodiment performs its operation are described in detail in the embodiment describing the method, but will not be described in detail here.

[0166] Referring to Figure 7, which is a schematic diagram of another communication device 70 provided by an embodiment of the present disclosure, the communication device 70 may be a network device, a terminal device, a chip, chip system, or processor that supports the implementation of the above method by a network device, or a chip, chip system, or processor that supports the implementation of the above method by a terminal device. The device may be used to implement the method described in the above embodiment of the method, for which you should refer to the description of the above embodiment of the method.

[0167] The communication device 70 may include one or more processors 701. The processors 701 may be general-purpose processors or dedicated processors, for example. They may be baseband processors or central processors. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute computer programs, and process data from computer programs.

[0168] Selectively, the communication device 70 may further include one or more memories 702 capable of storing a computer program 704, and the processor 701 executes the computer program 704 so that the communication device 70 performs the method described in the embodiment of the above method. Selectively, further data may be stored in the memories 702. The communication device 70 and the memories 702 may be provided separately or integrated.

[0169] Selectively, the communication device 70 may further include a transceiver 705 and an antenna 706. The transceiver 705 may be called a transmit / receive unit, transceiver, or transmit / receive circuit, etc., for implementing transmit / receive functions. The transceiver 705 may include a receiver and a transmitter, the receiver may be called a receiver or receiving circuit, etc., for implementing a receive function, and the transmitter may be called a transmitter or transmitting circuit, etc., for implementing a transmit function.

[0170] Selectively, the communication device 70 may further include one or more interface circuits 707. The interface circuits 707 are used to receive code instructions and transmit them to the processor 701. The processor 701 executes the code instructions to cause the communication device 70 to perform the method described in the embodiments of the above method.

[0171] If the communication device 70 is a terminal device: The processor 701 performs step 201 in Figure 2, steps 301, 302, and 303 in Figure 3, or steps 401, 402, 403, and 404 in Figure 4. The transceiver 705 performs step 202 in Figure 2, step 304 in Figure 3, or step 405 in Figure 4.

[0172] If the communication device 70 is a network device: The transceiver 705 performs step 501 in Figure 5.

[0173] In one embodiment, the processor 701 may include a transceiver for implementing receiving and transmitting functions. For example, this transceiver may be a transmit / receive circuit, an interface, or an interface circuit. The transmit / receive circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The transmit / receive circuit, interface, or interface circuit may be used for reading or writing code or data, or it may be used for transmitting or transmitting signals.

[0174] In one implementation, the processor 701 can store a computer program that, when executed on the processor 701, causes the communication device 70 to execute the method described in the embodiment of the above method. The computer program may be hardened within the processor 701, in which case the processor 701 may be implemented by hardware.

[0175] In one embodiment, the communication device 70 may include a circuit capable of implementing the transmission, reception, or communication functions in the embodiment of the above method. The processor and transceiver described herein can be implemented in integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), hybrid signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies such as complementary metal oxide semiconductors (CMOS), n-metal oxide semiconductors (NMOS), positive channel metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon germanium (SiGe), and gallium arsenide (GaAs).

[0176] The communication device described in the above embodiments may be a network device or a terminal device, but the scope of the communication device described in this disclosure is not limited thereto, and the structure of the communication device may not be limited to Figure 7. The communication device may be an independent device or part of a larger device. For example, the communication device may be as follows: (1) an independent integrated circuit IC, or chip, or chip system or subsystem, (2) Having one or more sets of ICs, which optionally include storage components for storing data, computer programs, (3) ASICs such as modems, (4) Modules that can be incorporated into other devices (5) Receivers, terminal devices, smart terminal devices, mobile phones, wireless devices, handhelds, mobile units, in-vehicle devices, network-side devices, cloud devices, artificial intelligence devices, etc. (6) Others, etc.

[0177] If the communication device is a chip or a chip system, refer to the schematic configuration diagram of the chip shown in Figure 8. The chip shown in Figure 8 includes a processor 801 and an interface 802. Here, the number of processors 801 may be one or more, and the number of interfaces 802 may be multiple.

[0178] When the chip implements the functions of the terminal device in the embodiments of this disclosure: Processor 801 determines to trigger the reporting of a sidelink (SL) consistent listen before talk (LBT) failure report, determines the uplink resource to transmit the SL consistent LBT failure report, and interface 802 sends the SL consistent LBT failure report to the network device via the uplink resource.

[0179] In one implementation, the processor 801 specifically determines that if the detection granularity of SL-consistent LBT failures is resource pool granularity, and the terminal device determines that at least one resource pool has triggered an SL-consistent LBT failure and that the SL-consistent LBT failure in at least one resource pool has not been canceled, then the terminal device will trigger the reporting of an SL-consistent LBT failure report.

[0180] In another implementation, the processor 801 specifically determines that the detection granularity for SL-consistent LBT failures is resource block set (RB set) granularity, and that the terminal device determines that at least one RB set triggered an SL-consistent LBT failure and that the SL-consistent LBT failure in at least one RB set has not been canceled, in which case the terminal device will trigger the reporting of an SL-consistent LBT failure report.

[0181] In another implementation, the processor 801 specifically determines that the detection granularity for SL-consistent LBT failures is bandwidth portion (BWP) granularity, and that the terminal device determines that at least one BWP or cell has triggered an SL-consistent LBT failure and that the SL-consistent LBT failure in at least one BWP or cell has not been canceled, in which case the terminal device will trigger the reporting of an SL-consistent LBT failure report.

[0182] In one implementation, the processor 801 specifically determines that the terminal device has an uplink resource for new transmission and that the uplink resource for new transmission can accommodate the SL-consistent LBT failure report and the subheader of the SL-consistent LBT failure report, and then determines the uplink resource for new transmission to be the uplink resource for transmitting the SL-consistent LBT failure report.

[0183] In another implementation, the processor 801 specifically determines that the terminal device does not have an uplink resource for a new transmission and / or that the uplink resource for the new transmission cannot accommodate the SL-consistent LBT failure report and its subheader, triggers a scheduling request (SR), determines the SR setting associated with the triggered SR, and sends an SR based on the SR setting associated with the triggered SR to request an uplink resource to transmit the SL-consistent LBT failure report.

[0184] In one possible implementation, the SR setting associated with a triggered SR includes a dedicated SR setting which is an SR setting dedicated to SL-consistent LBT failure recovery, one of the available SR settings, and the earliest arriving SR setting among at least one available SR setting.

[0185] In one possible implementation, the processor 801 further determines that the triggered SR does not have an associated SR setting, triggers a Random Access Channel (RACH), initiates the RACH based on a dedicated RACH resource, and requests an uplink resource to transmit an SL-consistent LBT failure report, where the dedicated RACH resource is a RACH resource dedicated to SL-consistent LBT failure recovery.

[0186] When the chip implements the functionality of the network device in the embodiments of this disclosure: Interface 802 transmits configuration information to the terminal device, which includes dedicated scheduling request (SR) settings and / or dedicated random access channel (RACH) settings, where the dedicated SR settings and / or dedicated RACH settings are to assist the terminal device in requesting uplink resources from the network device, and the uplink resources are for transmitting sidelink (SL) consistent listening before talk (LBT) failure reports.

[0187] Selectively, the chip further includes memory 803 for storing necessary computer programs and data.

[0188] Those skilled in the art will also understand that the various illustrative logical blocks and steps described in the embodiments of this disclosure can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented in hardware or software will depend on the specific application and the design requirements of the overall system. Those skilled in the art may implement the described functionality using various methods for each specific application, but this implementation should not be understood as exceeding the scope of protection of the embodiments of this disclosure.

[0189] Embodiments of the present disclosure further provide a failure reporting system which includes a communication device as a terminal device and a communication device as a network device in the embodiment of Figure 6 described above, or which includes a communication device as a terminal device and a communication device as a network device in the embodiment of Figure 7 described above.

[0190] This disclosure further provides a readable storage medium in which instructions are stored that, when executed by a computer, enable the functionality of any of the embodiments of the above methods.

[0191] This disclosure further provides computer program products that, when executed by a computer, realize the functionality of embodiments of any of the methods described above.

[0192] The embodiments described above can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs. The processes or functions according to the embodiments of this disclosure are generated in whole or in part when the computer program is loaded and executed on a computer. The computer may be a general-purpose computer, a dedicated 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, the computer program may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired connection (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless connection (e.g., infrared, radio, microwave, etc.). The computer-readable storage medium may be any available medium accessible by a computer, or it may include a data storage device such as a server or data center integrated by one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0193] Those skilled in the art will understand that the various numerical designations such as "First," "Second," etc., in this disclosure are merely classifications for explanatory convenience and do not limit the scope of the embodiments of this disclosure, nor do they represent priority.

[0194] At least one of the disclosures may be described as one or more, and the number may be two, three, four or more, and is not limited to the disclosures. In the embodiments of the disclosures, a technical feature of a given type is distinguished by "First," "Second," "Third," "A," "B," "C," and "D," and there is no hierarchical or hierarchical order between the technical features described in "First," "Second," "Third," "A," "B," "C," and "D."

[0195] The correspondences shown in each table in this disclosure may be set or predefined. The values ​​of the information in each table are merely examples and can be set to other values, and are not limited to this disclosure. When setting the correspondence between information and each parameter, it is not necessary to set all of the correspondences shown in each table. For example, in the tables of this disclosure, the correspondence shown by a certain row may not be set. As another example, appropriate transformation adjustments such as splitting and merging can be performed based on the above tables. The names of the parameters shown in the titles of each table above may be other names that the communication device can understand, and the values ​​or representations of those parameters may be other values ​​or representations that the communication device can understand. In implementation, each of the above tables may adopt other data structures, such as arrays, queues, containers, stacks, linear tables, pointers, linked tables, trees, diagrams, structures, classes, heaps, hash lists, or hash tables.

[0196] In this disclosure, "pre-defined" can be understood as definition, pre-defined, memory, pre-storage, pre-negotiated, pre-set, hardened, or pre-fired.

[0197] Those skilled in the art will recognize that each example unit and algorithmic step described in the embodiments disclosed herein can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. How a certain function is performed in hardware or software will depend on the specific application and design constraints of the invention. Those skilled in the art may implement the described functions using different methods for each specific application, but such implementations should not be considered beyond the scope of this disclosure.

[0198] For the convenience and brevity of explanation, as will be obvious to those skilled in the art, the specific operating processes of the systems, apparatus, and units described above can be described by referring to the corresponding processes in the embodiments of the above methods, and are therefore omitted here.

[0199] As described above, although only specific embodiments of this disclosure are shown, the scope of protection of this disclosure is not limited thereto, and a person skilled in the art will readily realize that modifications or substitutions within the scope of the art disclosed should be included in the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be based on the scope of protection of the claims.

Claims

1. A method for reporting a failure report, wherein the method is performed by a terminal device, and the method is The steps include determining to trigger the reporting of a sidelink (SL) consistent listen before talk (LBT) failure report, and determining the uplink resource to transmit the SL consistent LBT failure report, The uplink resource includes the step of sending the SL-consistent LBT failure report to the network device, A method for reporting failures, characterized by the following features.

2. The decision to trigger the reporting of the aforementioned side-link (SL) consistent listening before talk (LBT) failure report means that The detection granularity of the SL-consistent LBT failure is resource pool granularity, and the terminal device determines that at least one resource pool triggered the SL-consistent LBT failure and that the SL-consistent LBT failure in the at least one resource pool has not been canceled, and the terminal device determines that it will trigger the reporting of the SL-consistent LBT failure report. The method for reporting a failure report as described in feature 1.

3. The decision to trigger the reporting of the aforementioned side-link (SL) consistent listening before talk (LBT) failure report means that The detection granularity of the SL-consistent LBT failure is resource block set (RB set) granularity, and the terminal device determines that if it determines that at least one RB set triggered the SL-consistent LBT failure and that the SL-consistent LBT failure in the at least one RB set has not been canceled, the terminal device will trigger the reporting of the SL-consistent LBT failure report. The method for reporting a failure report as described in feature 1.

4. The decision to trigger the reporting of the aforementioned side-link (SL) consistent listening before talk (LBT) failure report means that The detection granularity of the SL-consistent LBT failure is bandwidth portion (BWP) granularity, and the terminal device determines that if it determines that at least one BWP or cell triggered the SL-consistent LBT failure and that the SL-consistent LBT failure in the at least one BWP or cell has not been canceled, the terminal device will trigger the reporting of the SL-consistent LBT failure report. The method for reporting a failure report as described in feature 1.

5. Determining the uplink resource to transmit the SL consistent LBT failure report is: The terminal device has an uplink resource for new transmission, and it is determined that the uplink resource for new transmission can accommodate the SL-consistent LBT failure report and the subheader of the SL-consistent LBT failure report. This includes determining the uplink resource for the new transmission as the uplink resource for transmitting the SL-consistent LBT failure report, The method for reporting a failure report as described in feature 1.

6. Determining the uplink resource to transmit the SL consistent LBT failure report is: The terminal device determines that it does not have an uplink resource for new transmission, and / or that the uplink resource for new transmission cannot accommodate the SL-consistent LBT failure report and the subheader of the SL-consistent LBT failure report. Triggering a scheduling request (SR), This includes determining the SR settings associated with the triggered SR, and making an SR transmission based on the SR settings associated with the triggered SR to request an uplink resource to transmit the SL-consistent LBT failure report, The method for reporting a failure report as described in feature 1.

7. The SR setting associated with the triggered SR is A dedicated SR setting, which is an SR setting specifically for SL Consistent LBT failure recovery, Choose one of the available SR settings, The first available SR setting to arrive, and one of the following: The method for reporting a failure report as described in feature 6.

8. Determining the uplink resource to transmit the SL consistent LBT failure report is: It is determined that the triggered SR does not have an associated SR setting, Triggering a Random Access Channel (RACH), initiating the RACH based on a dedicated RACH resource, and requesting an uplink resource to transmit the SL-consistent LBT failure report, further comprising the dedicated RACH resource being a RACH resource dedicated to SL-consistent LBT failure recovery. The method for reporting a failure report as described in feature 6.

9. A method for reporting a failure report, wherein the method is performed by a network device, and the method is A step of transmitting configuration information to a terminal device, wherein the configuration information includes dedicated scheduling request (SR) settings and / or dedicated random access channel (RACH) settings. The dedicated SR setting and / or the dedicated RACH setting are for assisting the terminal device in requesting uplink resources from the network device, and the uplink resources are for transmitting sidelink (SL) consistent listening before talk (LBT) failure reports. A method for reporting failures, characterized by the following features.

10. A communication device, A processing module for determining which uplink resource will transmit the sidelink (SL) consistent listen before talk (LBT) failure report, and which will trigger the reporting of the sidelink (SL) consistent LBT failure report. The uplink resource includes a transmit / receive module for sending the SL consistent LBT failure report to a network device, A communication device characterized by the following features.

11. A communication device, A transmit / receive module for transmitting configuration information to a terminal device, the transmit / receive module including a dedicated scheduling request (SR) setting and / or dedicated random access channel (RACH) setting, The dedicated SR setting and / or the dedicated RACH setting are for assisting the terminal device in requesting uplink resources from the network device, and the uplink resources are for transmitting sidelink (SL) consistent listening before talk (LBT) failure reports. A communication device characterized by the following features.

12. A communication device, A processor and memory are included, the memory storing a computer program, and the processor causes the communication device to perform the method according to any one of claims 1 to 8 by executing the computer program stored in the memory. A communication device characterized by the following features.

13. A communication device, The invention includes a processor and memory, the memory storing a computer program, and the processor causes the communication device to perform the method according to claim 9 by executing the computer program stored in the memory. A communication device characterized by the following features.

14. A computer-readable storage medium in which instructions are stored, When the aforementioned instruction is executed, the method described in any of claims 1 to 8 is realized. A computer-readable storage medium characterized by the following features.

15. A computer-readable storage medium in which instructions are stored, When the aforementioned instruction is executed, the method according to claim 9 is realized. A computer-readable storage medium characterized by the following features.

Images