Counting method of SL continuous LBT failure times and communication device

CN119072999APending Publication Date: 2024-12-03BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380008789.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-03-30
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

In sidelink communication, the counting method of SL consecutive LBT failures fails to effectively solve the problem of inconsistent failure detection granularity between resource pools and resource block set granularities, resulting in limited communication efficiency and reliability.

Method used

When the terminal sends sidelink data on the SL unlicensed frequency band, the corresponding number of failures is counted according to the LBT failure indication of the resource pool or resource block set to implement SL continuous LBT failure detection at the resource pool or resource block set granularity. , supports detection that the resource pool or resource block collection granularity is greater or smaller than the resource block collection granularity.

Benefits of technology

It improves the consistency and reliability of the failure detection granularity of sidelink communication, enhances the communication efficiency of terminals on unlicensed frequency bands, and ensures the continuous LBT failure detection capability under the granularity of resource pools and resource block sets.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119072999A_ABST
    Figure CN119072999A_ABST
Patent Text Reader

Abstract

The invention provides a counting method of SL continuous LBT failure times and a communication device, which can be applied to a mobile communication technology, and the method comprises the step of counting the LBT failure times of a resource pool according to an LBT failure indication of a resource block set belonging to the resource pool when side link data is sent on an SL unlicensed frequency band. Therefore, when the granularity of the resource pool is greater than the granularity of the resource block set, the number of LBT failures of the resource pool is counted based on the LBT failure indication of the resource block set belonging to the resource pool, and SL continuous LBT failure detection of the granularity of the resource pool can be realized.
Need to check novelty before this filing date? Find Prior Art

Description

A method and communication device for counting the number of consecutive SL LBT failures Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a method for counting the number of consecutive listen before talk (LBT) failures of a sidelink (SL) and a communication device. Background Art

[0002] Related technologies allow uplink and downlink operations in unlicensed frequency bands. Channel access for both downlink and uplink relies on the LBT feature. Furthermore, to support direct communication between terminals, sidelink communication has been introduced. Sidelink communication can also use unlicensed frequency bands, and terminals also require LBT when sending sidelink data in unlicensed frequency bands.

[0003] Summary of the Invention

[0004] A first aspect of the present disclosure provides a method for counting consecutive SL LBT failures, which is executed by a terminal. The method includes:

[0005] When sending sidelink data on the SL unlicensed frequency band, the number of LBT failures of the resource pool is counted according to the LBT failure indication of the resource block set belonging to the resource pool.

[0006] A second aspect of the present disclosure provides another method for counting consecutive SL LBT failures, which is executed by a terminal. The method includes:

[0007] When sending sidelink data on the SL unlicensed frequency band, the number of LBT failures of the resource pool is counted according to the LBT failure indication of the resource block set to which the resource pool belongs.

[0008] A third aspect of the present disclosure provides another method for counting consecutive SL LBT failures, which is executed by a terminal. The method includes:

[0009] When sending sidelink data on the SL unlicensed frequency band, the number of LBT failures of the resource block set is counted according to the LBT failure indication of the resource block set.

[0010] The present disclosure provides a communication device according to four aspects, including:

[0011] The processing module is used to count the number of LBT failures of the resource pool according to the LBT failure indication of the resource block set belonging to the resource pool when sending side link data on the SL unlicensed frequency band.

[0012] A fifth aspect of the present disclosure provides another communication device, including:

[0013] The processing module is used to count the number of LBT failures of the resource pool according to the LBT failure indication of the resource block set to which the resource pool belongs when sending side link data on the SL unlicensed frequency band.

[0014] A sixth aspect of the present disclosure provides another communication device, including:

[0015] The processing module is used to count the number of LBT failures of the resource block set according to the LBT failure indication of the resource block set when sending side link data on the SL unlicensed frequency band.

[0016] A seventh aspect of the present disclosure provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in the first aspect is executed.

[0017] An eighth aspect of the present disclosure provides another communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in the second aspect is executed.

[0018] A ninth aspect of the present disclosure provides another communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in the third aspect is executed.

[0019] An embodiment of the tenth aspect of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory, so that the communication device executes the method described in the first aspect above.

[0020] An embodiment of the eleventh aspect of the present disclosure provides another communication device, which includes a processor and a memory, wherein the memory stores a computer program; the processor executes the computer program stored in the memory, so that the communication device executes the method described in the second aspect above.

[0021] The embodiment of the twelfth aspect of the present disclosure provides another communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the second aspect above.

[0022] A thirteenth aspect of the present disclosure provides another 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. The processor is used to run the code instructions to enable the device to execute the method described in the first aspect above.

[0023] An embodiment of the fourteenth aspect of the present disclosure provides another 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. The processor is used to run the code instructions to enable the device to execute the method described in the second aspect above.

[0024] A fifteenth aspect of the present disclosure provides another 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. The processor is used to run the code instructions to enable the device to execute the method described in the second aspect above.

[0025] A sixteenth aspect embodiment of the present disclosure provides a computer-readable storage medium for storing instructions used by the above-mentioned communication device. When the instructions are executed, the communication device executes the method described in the first aspect.

[0026] A seventeenth aspect embodiment of the present disclosure provides another computer-readable storage medium for storing instructions for the above-mentioned communication device, and when the instructions are executed, the communication device executes the method described in the above-mentioned second aspect.

[0027] The eighteenth aspect embodiment of the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the third aspect above.

[0028] The nineteenth aspect embodiment of the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect above.

[0029] The twentieth aspect of the present disclosure also provides another computer program product including a computer program, which, when executed on a computer, enables the computer to execute the method described in the second aspect above.

[0030] The twenty-first aspect embodiment of the present disclosure also provides another computer program product including a computer program, which, when executed on a computer, enables the computer to execute the method described in the second aspect above.

[0031] The embodiment of the twenty-second aspect of the present disclosure provides a chip system, which includes at least one processor and an interface for supporting a communication device to implement the functions involved in the first aspect, for example, determining or processing at least one of the data and information involved in the above method. In one possible design, the chip system also includes a memory, which is used to store computer programs and data necessary for the communication device. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0032] The embodiment of the twenty-third aspect of the present disclosure further provides another chip system, which includes at least one processor and an interface for supporting the communication device to implement the functions involved in the second aspect, for example, determining or processing at least one of the data and information involved in the above method. In one possible design, the chip system also includes a memory, which is used to store computer programs and data necessary for the communication device. The chip system can be composed of a chip or can include a chip and other discrete devices.

[0033] The embodiment of the twenty-fourth aspect of the present disclosure further provides another chip system, which includes at least one processor and an interface for supporting the communication device to implement the functions involved in the second aspect, for example, determining or processing at least one of the data and information involved in the above method. In one possible design, the chip system also includes a memory, which is used to store computer programs and data necessary for the communication device. The chip system can be composed of a chip or can include a chip and other discrete devices.

[0034] The twenty-fifth aspect of the present disclosure further provides a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect above.

[0035] The twenty-sixth aspect embodiment of the present disclosure also provides another computer program, which, when executed on a computer, enables the computer to execute the method described in the second aspect above.

[0036] The twenty-seventh embodiment of the present disclosure further provides another computer program, which, when executed on a computer, enables the computer to execute the method described in the third aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

[0038] FIG1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;

[0039] FIG2 is a flow chart of a method for counting the number of consecutive LBT failures of SL provided by an embodiment of the present disclosure;

[0040] FIG3 is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure;

[0041] FIG4 is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure;

[0042] FIG5 is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure;

[0043] FIG6 is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure;

[0044] FIG7 is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure;

[0045] FIG8 is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure;

[0046] FIG9 is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure;

[0047] FIG10 is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure;

[0048] FIG11 is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure;

[0049] FIG12 is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure;

[0050] FIG13 is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure;

[0051] FIG14 is a schematic structural diagram of a communication device provided in an embodiment of the present disclosure;

[0052] FIG15 is a schematic structural diagram of another communication device provided in an embodiment of the present disclosure;

[0053] FIG16 is a schematic diagram of the structure of a chip provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0054] In order to better understand the method for counting the number of consecutive SL LBT failures disclosed in an embodiment of the present disclosure, the communication system to which the embodiment of the present disclosure is applicable is first described below.

[0055] Please refer to Figure 1, which 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, a network device and two terminals, which are connected via a SL. The number and form of the devices shown in Figure 1 are for example only and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, two or more network devices and two or more terminals may be included. The communication system shown in Figure 1 includes, for example, a network device 11 and two terminals 12 and 13, wherein terminal 12 and terminal 13 are connected via a SL.

[0056] In the present disclosure, terminal 12 may be a transmitting terminal, and terminal 13 may be a peer terminal. Terminal 13 may be one or more, and this disclosure does not limit this. Alternatively, terminal 13 may be a transmitting terminal, and terminal 12 may be a peer terminal. Terminal 12 may be one or more, and this disclosure does not limit this.

[0057] It should be noted that the technical solutions of the embodiments of the present disclosure can be applied to various communication systems. For example, long term evolution (LTE) systems, fifth generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems. It should also be noted that the sidelink in the embodiments of the present disclosure can also be referred to as a sidelink or a through link.

[0058] The network device 11 in the embodiment of the present disclosure is an entity on the network side for transmitting or receiving signals. For example, the network device 11 can 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. The embodiment of the present disclosure does not limit the specific technology and specific device form adopted by the network device. The network device provided in the embodiment of the present disclosure can be composed of a centralized unit (CU) and a distributed unit (DU), wherein the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the network device, such as the base station, and the functions of some protocol layers are placed in the CU for centralized control, and the functions of the remaining part or all of the protocol layers are distributed in the DU, and the DC is centrally controlled by the CU.

[0059] The terminal in the embodiments of the present disclosure is an entity on the user side for receiving or transmitting signals, such as a mobile phone. The terminal can also be referred to as a terminal device (terminal), user equipment (UE), mobile station (MS), mobile terminal device (MT), etc. The terminal can be a car with communication functions, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self-driving (self-driving), a wireless terminal device in remote medical surgery (remote medical surgery), a wireless terminal device in a smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in a smart city (smart city), a wireless terminal device in a smart home (smart home), etc. The embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the terminal.

[0060] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0061] In related technologies, uplink and downlink operations can be performed in unlicensed frequency bands. Channel access for both downlink and uplink relies on the LBT feature. Furthermore, to support direct communication between terminals, sidelink communication has been introduced. Sidelink communication can also use unlicensed frequency bands. When terminals send sidelink data in unlicensed frequency bands, LBT is also required. The continuous LBT mechanism also applies to sidelink communication in unlicensed spectrum.

[0062] For a SL transmission, the terminal may need to perform LBT on multiple resource block sets (RB sets). For LBT failure indication, the physical layer only submits the LBT failure indication when LBT fails. If LBT succeeds, the physical layer does not need to submit the indication. The granularity of the LBT failure indication can be the granularity of the resource block set, which means that to send a sidelink media access control protocol data unit (SL MAC PDU), the physical layer may need to perform LBT on multiple resource block sets, and the number of LBT failure indications submitted to the MAC layer may also be multiple.

[0063] In an embodiment of the present disclosure, when the terminal sends side link data on the SL unlicensed frequency band, the number of LBT failures of the resource pool can be counted based on the LBT failure indication of the resource block set belonging to the resource pool, thereby realizing that when the resource pool granularity is larger than the resource block set granularity and the continuous LBT failure detection granularity is the resource pool granularity, the number of LBT failures of the resource pool can be counted based on the LBT failure indication of the resource block set belonging to the resource pool.

[0064] The following is a detailed introduction to a method for counting the number of SL consecutive LBT failures and a communication device provided by the present disclosure in conjunction with the accompanying drawings.

[0065] The method for counting the number of SL consecutive LBT failures disclosed in the present invention can be applied to sidelink-unlicense (SL-U) scenarios.

[0066] First, there are two ways to allocate transmission resources for sidelink communication: one is a method in which the network schedules sidelink transmission resources (which may be referred to as Mode 1), and the other is a method in which the terminal autonomously selects sidelink transmission resources (which may be referred to as Mode 2). The specific allocation method used by the terminal can be configured by the network device through radio resource control (RRC) signaling.

[0067] Please refer to Figure 2, which is a flow chart of a method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure, which is executed by a terminal. As shown in Figure 2, the method may include but is not limited to the following steps:

[0068] Step 201: When sending sidelink data on the SL unlicensed frequency band, the number of LBT failures of the resource pool is counted according to the LBT failure indication of the resource block set belonging to the resource pool.

[0069] The sidelink data may include data sent by the terminal to other terminals, control signaling, hybrid automatic repeat request (HARQ) feedback, and synchronization signal block (SSB) units.

[0070] For example, the sidelink data may include control instructions sent on the physical sidelink control channel (PSCCH), data and control instructions sent on the physical sidelink shared channel (PSSCH), HARQ feedback sent on the physical sidelink feedback channel (PSFCH), etc.

[0071] In some embodiments of the present disclosure, one or more resource pools and one or more resource block sets may be configured for a terminal.

[0072] In some embodiments of the present disclosure, the resource pool and resource block set may be configured to the terminal by the network device, or may be pre-configured, which is not limited in the present disclosure.

[0073] In some embodiments of the present disclosure, a resource block set may belong to one resource pool or to multiple resource pools, that is, all resources of the resource block set may belong to one resource pool, or multiple different parts of the resource block set may belong to different resource pools respectively. The present disclosure does not limit this.

[0074] In some embodiments of the present disclosure, a resource pool may contain a resource block set, a resource pool may also contain multiple resource block sets, a resource pool may contain all or part of the resources of a resource block set, a resource pool may also contain resources of multiple resource block sets, and the multiple resource block sets contained in a resource pool may all or part of the resources belong to this resource pool, and the present disclosure does not limit this.

[0075] In some embodiments of the present disclosure, the resource pool granularity may be greater than the resource block set granularity. When the granularity of SL continuous LBT failure detection is the resource pool granularity, for each resource pool, the number of LBT failures of the resource pool may be counted based on the LBT failure indication of the resource block set belonging to the resource pool. For example, a resource pool contains a resource block set, and the number of LBT failures of the resource pool may be counted based on the LBT failure indication of the resource block set. For another example, a resource pool contains multiple resource block sets, and the number of LBT failures of the resource pool may be counted based on the LBT failure indication of the multiple resource block sets.

[0076] Exemplarily, the number of LBT failures of the resource pool may be determined based on the number of LBT failure indications of the resource block set belonging to the resource pool.

[0077] In some embodiments of the present disclosure, a resource pool of a terminal may be associated with at least one of the following: an LBT failure detection timer; an LBT failure counter; and a maximum number of LBT failure counts. That is, the terminal may maintain one or more of an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts for each resource pool. Exemplarily, for each resource pool, the terminal maintains an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts.

[0078] In some embodiments of the present disclosure, the maximum number of LBT failure counts associated with different resource pools may be the same or different, and the present disclosure does not limit this.

[0079] In an embodiment of the present disclosure, when the terminal sends side link data on the SL unlicensed frequency band, the number of LBT failures of the resource pool can be counted based on the LBT failure indication of the resource block set belonging to the resource pool. Therefore, when the resource pool granularity is larger than the resource block set granularity, the number of LBT failures of the resource pool can be counted based on the LBT failure indication of the resource block set belonging to the resource pool, thereby realizing SL continuous LBT failure detection at the resource pool granularity.

[0080] Please refer to Figure 3, which is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure, which is executed by a terminal. As shown in Figure 3, the method may include but is not limited to the following steps:

[0081] Step 301: upon receiving an LBT failure indication of a resource block set belonging to a resource pool submitted by the physical layer, start or restart the LBT failure detection timer associated with the resource pool, and add 1 to the LBT failure counter associated with the resource pool.

[0082] In some embodiments of the present disclosure, one or more resource pools and one or more resource block sets may be configured for a terminal.

[0083] In some embodiments of the present disclosure, the resource pool and resource block set may be configured to the terminal by the network device, or may be pre-configured, which is not limited in the present disclosure.

[0084] In some embodiments of the present disclosure, a resource block set may belong to one resource pool or to multiple resource pools, that is, all resources of the resource block set may belong to one resource pool, or multiple different parts of the resource block set may belong to different resource pools respectively. The present disclosure does not limit this.

[0085] In some embodiments of the present disclosure, a resource pool may contain a resource block set, a resource pool may also contain multiple resource block sets, a resource pool may contain all or part of the resources of a resource block set, a resource pool may also contain resources of multiple resource block sets, and the multiple resource block sets contained in a resource pool may all or part of the resources belong to this resource pool, and the present disclosure does not limit this.

[0086] In some embodiments of the present disclosure, a resource pool of a terminal may be associated with at least one of the following: an LBT failure detection timer; an LBT failure counter; and a maximum number of LBT failure counts. That is, the terminal may maintain one or more of an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts for each resource pool. Exemplarily, for each resource pool, the terminal maintains an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts.

[0087] In some embodiments of the present disclosure, the maximum number of LBT failure counts associated with different resource pools may be the same or different, and the present disclosure does not limit this.

[0088] In some embodiments of the present disclosure, the resource pool granularity may be greater than the resource block set granularity. When the granularity of SL continuous LBT failure detection is the resource pool granularity, for each resource pool, the terminal may count the number of LBT failures of the resource pool using the LBT failure detection timer and the LBT failure counter associated with the resource pool based on the LBT failure indication of the resource block set belonging to the resource pool. The LBT failure counter associated with the resource pool is used to count the number of LBT failures of the resource pool, and the initial value of the LBT failure counter associated with the resource pool may be zero.

[0089] In some embodiments of the present disclosure, before a terminal sends sidelink data each time, the physical layer of the terminal may first perform an LBT failure detection on a resource block set. If the LBT fails, the physical layer of the terminal will submit an LBT failure indication of the resource block set to the medium access control (MAC) layer. Each time the MAC layer of the terminal receives an LBT failure indication of a resource block set belonging to a resource pool submitted by the physical layer, it may start or restart an LBT failure detection timer associated with the resource pool and add 1 to the LBT failure counter associated with the resource pool. If the LBT failure detection timer associated with the resource pool times out, the LBT failure counter may be reset to 0.

[0090] For example, a resource pool includes R1, R2, and R3. The initial value of the LBT failure counter associated with the resource pool is 0. Upon receiving an LBT failure indication from the physical layer for R1, the LBT failure detection timer associated with the resource pool is started, and the LBT failure counter associated with the resource pool is incremented by 1. At this point, the number of LBT failures for the resource pool is 1. Subsequently, while the LBT failure detection timer associated with the resource pool is running, an LBT failure indication from the physical layer for R2 is received. The LBT failure detection timer associated with the resource pool is restarted, and the LBT failure counter associated with the resource pool is incremented by 1. At this point, the number of LBT failures for the resource pool is 2. Subsequently, while the LBT failure detection timer associated with the resource pool is running, an LBT failure indication from the physical layer for R1 is received. The LBT failure detection timer associated with the resource pool is restarted, and the LBT failure counter associated with the resource pool is incremented by 1. At this point, the number of LBT failures for the resource pool is 3.

[0091] Optionally, when all resources in any resource block set belonging to the resource pool belong to the resource pool, when an LBT failure indication of any resource block set is received, the LBT failure detection timer associated with the resource pool is started or restarted, and the LBT failure counter associated with the resource pool is increased by 1.

[0092] Optionally, when some resources of any resource block set among the resource block sets belonging to the resource pool belong to the resource pool (but not all resources belong to the resource pool), upon receiving an LBT failure indication for any resource block set, the LBT failure detection timer associated with the resource pool is started or restarted, and the LBT failure counter associated with the resource pool is incremented by 1. In other words, for a resource block set in which some resources belong to the resource pool, when counting the number of LBT failures of the resource pool, the LBT failure indications of the resource block sets in which some resources belong to the resource pool need to be taken into account.

[0093] For example, the resource block sets belonging to a certain resource pool are R4, R5, and R6, among which all resources of R4 and R5 belong to the resource pool, and some resources of R6 belong to the resource pool. When an LBT failure indication is received from R6, the LBT failure detection timer associated with the resource pool can be started or restarted, and the LBT failure counter associated with the resource pool can be increased by 1. In other words, when an LBT failure indication is received from any resource block set among R4, R5, and R6, the LBT failure detection timer associated with the resource pool can be started or restarted, and the LBT failure counter associated with the resource pool can be increased by 1.

[0094] Optionally, when some resources of any resource block set among the resource block sets belonging to the resource pool belong to the resource pool (but not all resources belong to the resource pool), upon receiving an LBT failure indication for any resource block set, the LBT failure detection timer associated with the resource pool is not started or restarted, and the LBT failure counter associated with the resource pool is not incremented by 1. In other words, for resource block sets in which some resources belong to the resource pool, when counting the number of LBT failures for the resource pool, the LBT failure indications of resource block sets in which some resources belong to the resource pool do not need to be considered.

[0095] For example, the resource blocks belonging to a certain resource pool are R4, R5, and R6, where all resources of R4 and R5 belong to the resource pool, and some resources of R6 belong to the resource pool. When an LBT failure indication is received from R6, the LBT failure detection timer associated with the resource pool may not be started or restarted, and the LBT failure counter associated with the resource pool may not be incremented by 1. In other words, when only an LBT failure indication is received from R4 or R5, the LBT failure detection timer associated with the resource pool is started or restarted, and the LBT failure counter associated with the resource pool is incremented by 1.

[0096] Optionally, for a resource block set in which some resources belong to a resource pool (not a resource block set in which all resources belong to a resource pool), when counting the number of LBT failures of the resource pool, whether it is necessary to consider the LBT failure indication of the resource block set in which some resources belong to the resource pool can be implemented by the terminal as needed or configured by the network device, and this disclosure does not limit this. For example, the network device can configure an indication parameter to indicate whether the terminal needs to consider the LBT failure indication of the resource block set in which some resources belong to the resource pool.

[0097] In an embodiment of the present disclosure, the terminal can count the number of LBT failures of the resource pool based on the LBT failure indication of the resource block set belonging to the resource pool, using the LBT failure detection timer and LBT failure counter associated with the resource pool, thereby realizing SL continuous LBT failure detection at the resource pool granularity when the resource pool granularity is larger than the resource block set granularity.

[0098] Please refer to Figure 4, which is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure, which is executed by a terminal. As shown in Figure 4, the method may include but is not limited to the following steps:

[0099] Step 401: upon receiving an LBT failure indication of a resource block set belonging to a resource pool submitted by the physical layer, start or restart an LBT failure detection timer associated with the resource pool, and increase the LBT failure counter associated with the resource pool by 1.

[0100] In the embodiment of the present disclosure, step 401 may be implemented in any of the embodiments of the present disclosure, which is not limited in the present disclosure and will not be described in detail.

[0101] Step 402: When the LBT failure counter associated with the resource pool is greater than or equal to a first threshold, determine that the resource pool triggers SL continuous LBT failure.

[0102] In some embodiments of the present disclosure, a resource pool of a terminal may be associated with at least one of the following: an LBT failure detection timer; an LBT failure counter; and a maximum number of LBT failure counts. That is, the terminal may maintain one or more of an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts for each resource pool. Exemplarily, for each resource pool, the terminal maintains an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts.

[0103] In some embodiments of the present disclosure, during the operation of the LBT failure detection timer associated with the resource pool, an LBT failure indication of a set of resource blocks belonging to the resource pool is received, the LBT failure detection timer associated with the resource pool is started or restarted, and the LBT failure counter associated with the resource pool is increased by 1. During the operation of the LBT failure detection timer associated with the resource pool, if the LBT failure counter associated with the resource pool is greater than or equal to a first threshold, it can be determined that the resource pool triggers SL continuous LBT failure. That is, when the number of LBT failures of the resource pool is greater than or equal to the first threshold, it can be determined that the resource pool triggers SL continuous LBT failure.

[0104] Optionally, other implementation methods in the above embodiments may be used to count the number of LBT failures of the resource pool, and when the LBT failure counter associated with the resource pool is greater than or equal to a first threshold, it is determined that the resource pool triggers SL continuous LBT failure.

[0105] In some embodiments of the present disclosure, the first threshold may be configured by the network device or may be pre-configured. The first thresholds corresponding to different resource pools may be the same or different, and the present disclosure does not impose any limitation on this.

[0106] It should be noted that the first threshold in the present disclosure may refer to the maximum number of LBT failure counts associated with a resource pool. The maximum number of LBT failure counts associated with different resource pools may be the same or different, and the present disclosure does not limit this.

[0107] In an embodiment of the present disclosure, upon receiving an LBT failure indication for a resource block set belonging to a resource pool submitted by the physical layer, the terminal may start or restart an LBT failure detection timer associated with the resource pool, and add 1 to the LBT failure counter associated with the resource pool. During the operation of the LBT failure detection timer associated with the resource pool, if the LBT failure counter associated with the resource pool is greater than or equal to a first threshold, it is determined that the resource pool has triggered SL continuous LBT failure. Thus, when the resource pool granularity is greater than the resource block set granularity, SL continuous LBT failure detection is implemented at the resource pool granularity, and it is also possible to determine whether the resource pool has triggered SL continuous LBT failure based on the size relationship between the LBT failure counter associated with the resource pool and the first threshold.

[0108] Please refer to Figure 5, which is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure, which is executed by a terminal. As shown in Figure 5, the method may include but is not limited to the following steps:

[0109] Step 501: upon receiving an LBT failure indication of a resource block set belonging to a resource pool submitted by the physical layer, start or restart the LBT failure detection timer associated with the resource pool, and add 1 to the LBT failure counter associated with the resource pool.

[0110] Step 502: When the LBT failure counter associated with the resource pool is greater than or equal to a first threshold, it is determined that the resource pool triggers SL continuous LBT failure.

[0111] In the embodiment of the present disclosure, steps 501 and 502 may be implemented in any of the embodiments of the present disclosure, and the present disclosure does not limit this and will not elaborate on this.

[0112] Step 503: When it is determined that the resource pool triggers SL continuous LBT failure, reselect resources from a resource pool where SL continuous LBT failure has not occurred.

[0113] In some embodiments of the present disclosure, when determining that a resource pool triggers SL continuous LBT failure, the terminal may reselect resources from a resource pool where SL continuous LBT failure has not occurred, that is, reselect resources from a resource pool where SL continuous LBT failure has never occurred.

[0114] In some embodiments of the present disclosure, the terminal operates in mode 2, that is, the terminal operating in mode 2 can reselect resources of a resource pool where no SL continuous LBT failure occurs when it is determined that the resource pool triggers SL continuous LBT failure.

[0115] In an embodiment of the present disclosure, the terminal can count the number of LBT failures of the resource pool based on the LBT failure indication of the resource block set belonging to the resource pool, and realize SL continuous LBT failure detection at the resource pool granularity. It can also determine whether the resource pool triggers SL continuous LBT failure based on the size relationship between the LBT failure counter associated with the resource pool and the first threshold, and reselect the resources of the resource pool when it is determined that the resource pool triggers SL continuous LBT failure to ensure normal side link communication.

[0116] Please refer to Figure 6, which is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure, which is executed by a terminal. As shown in Figure 6, the method may include but is not limited to the following steps:

[0117] Step 601: When sending sidelink data on the SL unlicensed frequency band, the number of LBT failures of the resource pool is counted according to the LBT failure indication of the resource block set to which the resource pool belongs.

[0118] For the explanation of the sidelink data in the embodiments of the present disclosure, please refer to the above embodiments, so it will not be repeated here.

[0119] In some embodiments of the present disclosure, one or more resource pools and one or more resource block sets may be configured for a terminal.

[0120] In some embodiments of the present disclosure, the resource pool and resource block set may be configured to the terminal by a network device, or may be pre-configured, which is not limited in the present disclosure.

[0121] In some embodiments of the present disclosure, a resource pool may belong to one resource block set or to multiple resource block sets, that is, all resources of the resource pool may belong to one resource block set, or multiple different parts of the resource pool may belong to different resource block sets. The present disclosure does not limit this.

[0122] In some embodiments of the present disclosure, a resource block set may include a resource pool, a resource block set may also include multiple resource pools, a resource block set may include all or part of the resources of a resource pool, a resource block set may also include resources of multiple resource pools, and the multiple resource pools included in a resource block set may all or part of the resources belong to this resource block set, and the present disclosure does not limit this.

[0123] In some embodiments of the present disclosure, the resource pool granularity may be smaller than the resource block set granularity. When the granularity of SL continuous LBT failure detection is the resource pool granularity, for each resource pool, the number of LBT failures of the resource pool may be counted based on the LBT failure indication of the resource block set to which the resource pool belongs. For example, the resource pool belongs to one resource block set, for example, all resources of the resource pool belong to one resource block set, and the number of LBT failures of the resource pool may be counted based on the LBT failure indication of the resource block set. For another example, the resource pool belongs to multiple resource block sets, for example, multiple different parts of resources of the resource pool belong to different resource block sets, and the number of LBT failures of the resource pool may be counted based on the LBT failure indications of multiple resource block sets.

[0124] Exemplarily, the number of LBT failures of the resource pool can be determined based on the number of LBT failure indications of the resource block set to which the resource pool belongs.

[0125] In some embodiments of the present disclosure, a resource pool of a terminal may be associated with at least one of the following: an LBT failure detection timer; an LBT failure counter; and a maximum number of LBT failure counts. That is, the terminal may maintain one or more of an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts for each resource pool. Exemplarily, for each resource pool, the terminal maintains an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts.

[0126] In some embodiments of the present disclosure, the maximum number of LBT failure counts associated with different resource pools may be the same or different, and the present disclosure does not limit this.

[0127] In an embodiment of the present disclosure, when the terminal sends side link data on the SL unlicensed frequency band, the number of LBT failures of the resource pool can be counted based on the LBT failure indication of the resource block set to which the resource pool belongs. Therefore, when the resource pool granularity is smaller than the resource block set granularity, the number of LBT failures of the resource pool can be counted based on the LBT failure indication of the resource block set to which the resource pool belongs, thereby realizing SL continuous LBT failure detection at the resource pool granularity.

[0128] Please refer to Figure 7, which is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure, which is executed by a terminal. As shown in Figure 7, the method may include but is not limited to the following steps:

[0129] Step 701: upon receiving an LBT failure indication of a resource block set belonging to a resource pool submitted by the physical layer, start or restart an LBT failure detection timer associated with the resource pool, and increase the LBT failure counter associated with the resource pool by 1.

[0130] In some embodiments of the present disclosure, one or more resource pools and one or more resource block sets may be configured for a terminal.

[0131] In some embodiments of the present disclosure, the resource pool and resource block set may be configured to the terminal by the network device, or may be pre-configured, which is not limited in the present disclosure.

[0132] In some embodiments of the present disclosure, a resource pool may belong to one resource block set or to multiple resource block sets, that is, all resources of the resource pool may belong to one resource block set, or multiple different parts of the resource pool may belong to different resource block sets. The present disclosure does not limit this.

[0133] In some embodiments of the present disclosure, a resource block set may include a resource pool, a resource block set may also include multiple resource pools, a resource block set may include all or part of the resources of a resource pool, a resource block set may also include resources of multiple resource pools, and the multiple resource pools included in a resource block set may all or part of the resources belong to this resource block set, and the present disclosure does not limit this.

[0134] In some embodiments of the present disclosure, a resource pool of a terminal may be associated with at least one of the following: an LBT failure detection timer; an LBT failure counter; and a maximum number of LBT failure counts. That is, the terminal may maintain one or more of an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts for a set of resource blocks. Exemplarily, for each resource pool, the terminal maintains an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts.

[0135] In some embodiments of the present disclosure, the maximum number of LBT failure counts associated with different resource pools may be the same or different, and the present disclosure does not limit this.

[0136] In some embodiments of the present disclosure, the resource pool granularity may be smaller than the resource block set granularity. When the granularity of SL continuous LBT failure detection is the resource pool granularity, for each resource pool, the terminal may count the number of LBT failures of the resource pool using the LBT failure detection timer and the LBT failure counter associated with the resource pool based on the LBT failure indication of the resource block set to which the resource pool belongs. The LBT failure counter associated with the resource pool is used to count the number of LBT failures of the resource pool, and the initial value of the LBT failure counter associated with the resource pool may be zero.

[0137] In some embodiments of the present disclosure, before a terminal sends sidelink data each time, the terminal's physical layer may first perform an LBT failure detection on a resource block set. If the LBT fails, the terminal's physical layer will submit an LBT failure indication for the resource block set to the MAC layer. Each time the terminal's MAC layer receives an LBT failure indication for a resource block set belonging to a resource pool submitted by the physical layer, it may start or restart the LBT failure detection timer associated with the resource pool and add 1 to the LBT failure counter associated with the resource pool. If the LBT failure detection timer associated with the resource pool times out, the LBT failure counter may be reset to 0.

[0138] Optionally, when all resources of the resource pool belong to any resource block set, upon receiving an LBT failure indication of any resource block set, the LBT failure detection timer associated with the resource pool is started or restarted, and the LBT failure counter associated with the resource pool is increased by 1.

[0139] Optionally, when some resources of a resource pool belong to any resource block set, upon receiving an LBT failure indication for any resource block set delivered by the physical layer, an LBT failure detection timer associated with the resource pool is started or restarted, and an LBT failure counter associated with the resource pool is incremented by 1. In other words, if some resources of a resource block belong to a certain resource block set, the LBT failure indication of the resource block set needs to be taken into account when counting the number of LBT failures of the resource pool.

[0140] For example, a resource pool has some resources belonging to resource block set a1, some resources belonging to resource block set a2, and the remaining resources belonging to resource block set a3. The initial value of the LBT failure counter associated with this resource pool is 0. Upon receiving an LBT failure indication for a1 from the physical layer, the LBT failure detection timer associated with this resource pool is started, and the LBT failure counter associated with this resource pool is incremented by 1. At this point, the number of LBT failures for this resource pool is 1. Later, while the LBT failure detection timer is running, an LBT failure indication for a2 from the physical layer is received. The LBT failure detection timer associated with this resource pool is restarted, and the LBT failure counter associated with this resource pool is incremented by 1. At this point, the number of LBT failures for this resource pool is 2. Later, while the LBT failure detection timer is running, an LBT failure indication for a1 from the physical layer is received. The LBT failure detection timer associated with this resource pool is restarted, and the LBT failure counter associated with this resource pool is incremented by 1. At this point, the number of LBT failures for this resource pool is 3.

[0141] Optionally, if the resource pool belongs to multiple resource block sets, when an LBT failure indication of a target resource block set among multiple resource block sets is received, the LBT failure detection timer associated with the resource pool can be started or restarted, and the LBT failure counter associated with the resource pool can be increased by 1.

[0142] Among them, the target resource block set can be the resource block set that covers the most resources of the resource pool among the multiple resource block sets to which the resource pool belongs, or it can be other resource block sets among the multiple resource block sets to which the resource pool belongs except the resource block set that covers the least resources of the resource pool, or it can be a resource block set that meets other conditions, and this disclosure does not limit this.

[0143] For example, the resource block sets belonging to a resource pool are a4, a5 and a6, among which a4 covers 80% of the resources of the resource pool, a5 covers 10% of the resources of the resource pool, and a6 covers 10% of the resources of the resource pool. Only when the LBT failure indication of a4 is received, the LBT failure detection timer associated with the resource pool can be started or restarted, and the LBT failure counter associated with the resource pool can be increased by 1.

[0144] Optionally, if a resource pool belongs to multiple resource block sets, when counting the number of LBT failures of the resource pool, it is necessary to consider which resource block sets among the multiple resource block sets have LBT failure indications. This can be implemented by the terminal as needed or configured by the network device, and the present disclosure does not limit this. Exemplarily, the network device can configure an indication parameter to indicate to the terminal which resource block sets among the multiple resource block sets to which the resource pool belongs have LBT failure indications. Exemplarily, the indication parameter can be an identifier of the resource block set.

[0145] In an embodiment of the present disclosure, the terminal can count the number of LBT failures of the resource pool based on the LBT failure indication of the resource block set to which the resource pool belongs, using the LBT failure detection timer and LBT failure counter associated with the resource pool, thereby realizing SL continuous LBT failure detection at the resource pool granularity when the resource pool granularity is smaller than the resource block set granularity.

[0146] Please refer to Figure 8, which is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure, which is executed by a terminal. As shown in Figure 8, the method may include but is not limited to the following steps:

[0147] Step 801: upon receiving an LBT failure indication of a resource block set belonging to a resource pool submitted by the physical layer, start or restart the LBT failure detection timer associated with the resource pool, and add 1 to the LBT failure counter associated with the resource pool.

[0148] In the embodiment of the present disclosure, step 801 can be implemented in any of the embodiments of the present disclosure, and the present disclosure does not limit this and will not elaborate on it.

[0149] Step 802: When the LBT failure counter associated with the resource pool is greater than or equal to the second threshold, determine that the resource pool triggers SL continuous LBT failure.

[0150] In some embodiments of the present disclosure, a resource pool of a terminal may be associated with at least one of the following: an LBT failure detection timer; an LBT failure counter; and a maximum number of LBT failure counts. That is, the terminal may maintain one or more of an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts for each resource pool. Exemplarily, for each resource pool, the terminal maintains an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts.

[0151] In some embodiments of the present disclosure, during the operation of the LBT failure detection timer associated with the resource pool, an LBT failure indication of the resource block set belonging to the resource pool is received, the LBT failure detection timer associated with the resource pool is started or restarted, and the LBT failure counter associated with the resource pool is increased by 1. During the operation of the LBT failure detection timer associated with the resource pool, if the LBT failure counter associated with the resource pool is greater than or equal to the second threshold, it can be determined that the resource pool triggers SL continuous LBT failure, that is, when the number of LBT failures of the resource pool is greater than or equal to the second threshold, it can be determined that the resource pool triggers SL continuous LBT failure.

[0152] Optionally, other implementation methods in the above embodiments may be used to count the number of LBT failures of the resource pool, and when the LBT failure counter associated with the resource pool is greater than or equal to a second threshold, it is determined that the resource pool triggers SL continuous LBT failure.

[0153] In some embodiments of the present disclosure, the second threshold may be configured by the network device or may be pre-configured. The second thresholds corresponding to different resource pools may be the same or different, and the present disclosure does not limit this.

[0154] It should be noted that the second threshold in the present disclosure may refer to the maximum number of LBT failure counts associated with a resource pool. The maximum number of LBT failure counts associated with different resource pools may be the same or different, and the present disclosure does not limit this.

[0155] In the disclosed embodiment, the terminal may further determine that the resource pool has triggered SL continuous LBT failure when the LBT failure counter associated with the resource pool is greater than or equal to a second threshold. Thus, when the resource pool granularity is smaller than the resource block set granularity, whether the resource pool has triggered SL continuous LBT failure can be determined based on the relationship between the LBT failure counter associated with the resource pool and the second threshold.

[0156] Please refer to Figure 9, which is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure, which is executed by a terminal. As shown in Figure 9, the method may include but is not limited to the following steps:

[0157] Step 901: upon receiving an LBT failure indication of a resource block set belonging to a resource pool submitted by the physical layer, start or restart the LBT failure detection timer associated with the resource pool, and add 1 to the LBT failure counter associated with the resource pool.

[0158] Step 902: When the LBT failure counter associated with the resource pool is greater than or equal to the second threshold, determine that the resource pool triggers SL continuous LBT failure.

[0159] In the embodiment of the present disclosure, steps 901 and 902 may be implemented in any of the embodiments of the present disclosure, and the present disclosure does not limit this and will not elaborate on this.

[0160] Step 903: When it is determined that the resource pool triggers SL continuous LBT failure, reselect resources from a resource pool where SL continuous LBT failure has not occurred.

[0161] In some embodiments of the present disclosure, when determining that a resource pool triggers SL continuous LBT failure, the terminal may reselect resources from a resource pool where SL continuous LBT failure has not occurred, that is, reselect resources from a resource pool where SL continuous LBT failure has never occurred.

[0162] In some embodiments of the present disclosure, the terminal operates in mode 2, that is, the terminal operating in mode 2 can reselect resources of a resource pool where no SL continuous LBT failure occurs when it is determined that the resource pool triggers SL continuous LBT failure.

[0163] Optionally, when it is determined that a resource pool triggers SL continuous LBT failure, resources of a resource pool in which no SL continuous LBT failure occurs in the resource block set to which the resource pool belongs may be reselected.

[0164] For example, the resource block set to which a resource pool A belongs is b1, and the resource block set b1 also includes resources from resource pool B and resource pool C. When it is determined that resource pool A triggers SL continuous LBT failure, the resources from resource pools B and C that have not experienced SL continuous LBT failure can be reselected.

[0165] Optionally, if SL continuous LBT failures occur in other resource pools in the resource block set to which the resource pool belongs, resources of the resource block set that has not experienced SL continuous LBT failures can be reselected from other resource block sets.

[0166] Optionally, when it is determined that the resource pool triggers SL continuous LBT failure, resources of a resource pool in which SL continuous LBT failure does not occur in a resource block set outside the resource block set to which the resource pool belongs may be reselected.

[0167] Optionally, when it is determined that a resource pool has triggered a SL continuous LBT failure, resources from a resource pool that has not experienced a SL continuous LBT failure in the resource block set to which the resource pool belongs may be preferentially reselected. If it is not possible to reselect resources from a resource pool that has not experienced a SL continuous LBT failure in the resource block set to which the resource pool belongs, resources from a resource pool that has not experienced a SL continuous LBT failure in a resource block set other than the resource block set to which the resource pool belongs may be reselected.

[0168] Optionally, when it is determined that a resource pool has triggered a SL continuous LBT failure, resources of a resource pool that has not experienced a SL continuous LBT failure in a resource block set outside the resource block set to which the resource pool belongs may be preferentially reselected. If it is not possible to reselect resources of a resource pool that has not experienced a SL continuous LBT failure in a resource block set outside the resource block set to which the resource pool belongs, resources of a resource pool that has not experienced a SL continuous LBT failure in a resource block set to which the resource pool belongs may be reselected.

[0169] In an embodiment of the present disclosure, the terminal can count the number of LBT failures of the resource pool based on the LBT failure indication of the resource block set to which the resource pool belongs, thereby realizing SL continuous LBT failure detection at the resource pool granularity. It can also determine whether the resource pool triggers SL continuous LBT failure based on the size relationship between the LBT failure counter associated with the resource pool and the second threshold, and reselect the resources of the resource pool when it is determined that the resource pool triggers SL continuous LBT failure to ensure normal side link communication.

[0170] Please refer to Figure 10, which is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure, which is executed by a terminal. As shown in Figure 10, the method may include but is not limited to the following steps:

[0171] Step 1001: When sending sidelink data on the SL unlicensed frequency band, the number of LBT failures of the resource block set is counted according to the LBT failure indication of the resource block set.

[0172] For the explanation of the sidelink data in the embodiments of the present disclosure, please refer to the above embodiments, so it will not be repeated here.

[0173] In some embodiments of the present disclosure, one or more resource block sets may be configured for a terminal. Optionally, one or more resource pools may also be configured for the terminal.

[0174] In some embodiments of the present disclosure, the resource pool and resource block set may be configured to the terminal by the network device, or may be pre-configured, which is not limited in the present disclosure.

[0175] In some of the above-mentioned embodiments of the present disclosure, the resource pool granularity may be greater than the resource block set granularity. Exemplarily, a resource block set may belong to one resource pool or to multiple resource pools, that is, all resources of the resource block set may belong to one resource pool, or multiple different partial resources of the resource block set may belong to different resource pools, and the present disclosure does not limit this. Exemplarily, a resource pool may contain one resource block set, a resource pool may also contain multiple resource block sets, a resource pool may contain all or part of the resources of a resource block set, a resource pool may also contain resources of multiple resource block sets, and multiple resource block sets contained in a resource pool may all or part of the resources belong to this resource pool, and the present disclosure does not limit this.

[0176] In some of the above-mentioned embodiments of the present disclosure, the granularity of the resource pool may be smaller than the granularity of the resource block set. Exemplarily, a resource pool may belong to one resource block set or to multiple resource block sets, that is, all resources of the resource pool may belong to one resource block set, or multiple different parts of the resource pool may belong to different resource block sets, and the present disclosure does not limit this. Exemplarily, a resource block set may contain one resource pool, a resource block set may also contain multiple resource pools, a resource block set may contain all or part of the resources of a resource pool, a resource block set may also contain resources of multiple resource pools, and multiple resource pools contained in a resource block set may all or part of their resources belong to this resource block set, and the present disclosure does not limit this.

[0177] In some embodiments of the present disclosure, for each resource block set, the number of LBT failures of the resource block set can be counted based on the LBT failure indication of the resource block set. Exemplarily, the number of LBT failures of the resource block set can be determined based on the number of LBT failure indications of the resource block set.

[0178] In some embodiments of the present disclosure, a resource block set of a terminal may be associated with at least one of the following: an LBT failure detection timer; an LBT failure counter; and a maximum number of LBT failure counts. In other words, the terminal may maintain one or more of an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts for a resource block set. Exemplarily, for each resource block set, the terminal maintains an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts.

[0179] In some embodiments of the present disclosure, the maximum number of LBT failure counts associated with different resource block sets may be the same or different, and the present disclosure does not limit this.

[0180] In an embodiment of the present disclosure, when a terminal sends sidelink data on an SL unlicensed frequency band, the number of LBT failures of a resource block set can be counted according to the LBT failure indication of the resource block set, thereby realizing SL continuous LBT failure detection at the granularity of the resource block set.

[0181] Please refer to Figure 11, which is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure, which is executed by a terminal. As shown in Figure 11, the method may include but is not limited to the following steps:

[0182] Step 1101: upon receiving an LBT failure indication of a resource block set delivered by the physical layer, start or restart an LBT failure detection timer associated with the resource block set, and add 1 to an LBT failure counter associated with the resource block set.

[0183] In some embodiments of the present disclosure, one or more resource block sets may be configured for a terminal. Optionally, one or more resource pools may also be configured for the terminal.

[0184] In some embodiments of the present disclosure, the resource pool and resource block set may be configured to the terminal by the network device, or may be pre-configured, which is not limited in the present disclosure.

[0185] In some of the above-mentioned embodiments of the present disclosure, the resource pool granularity may be greater than the resource block set granularity. Exemplarily, a resource block set may belong to one resource pool or to multiple resource pools, that is, all resources of the resource block set may belong to one resource pool, or multiple different partial resources of the resource block set may belong to different resource pools, and the present disclosure does not limit this. Exemplarily, a resource pool may contain a resource block set, a resource pool may also contain multiple resource block sets, a resource pool may contain all or part of the resources of a resource block set, a resource pool may also contain resources of multiple resource block sets, and multiple resource block sets contained in a resource pool may all or part of the resources belong to this resource pool, and the present disclosure does not limit this.

[0186] In some of the above-mentioned embodiments of the present disclosure, the granularity of the resource pool may be smaller than the granularity of the resource block set. Exemplarily, a resource pool may belong to one resource block set or to multiple resource block sets, that is, all resources of the resource pool may belong to one resource block set, or multiple different parts of the resource pool may belong to different resource block sets, and the present disclosure does not limit this. Exemplarily, a resource block set may contain one resource pool, a resource block set may also contain multiple resource pools, a resource block set may contain all or part of the resources of a resource pool, a resource block set may also contain resources of multiple resource pools, and multiple resource pools contained in a resource block set may all or part of their resources belong to this resource block set, and the present disclosure does not limit this.

[0187] In some embodiments of the present disclosure, a resource block set of a terminal may be associated with at least one of the following: an LBT failure detection timer; an LBT failure counter; and a maximum number of LBT failure counts. In other words, the terminal may maintain one or more of an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts for a resource block set. Exemplarily, for each resource block set, the terminal maintains an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts.

[0188] In some embodiments of the present disclosure, the maximum number of LBT failure counts associated with different resource block sets may be the same or different, and the present disclosure does not limit this.

[0189] In some embodiments of the present disclosure, when the granularity of SL continuous LBT failure detection is the resource block set granularity, for each resource block set, the terminal may, based on the LBT failure indication of the resource block set, use the LBT failure detection timer associated with the resource block set and the LBT failure counter associated with the resource block set to count the number of LBT failures of the resource block set. The LBT failure counter associated with the resource block set is used to count the number of LBT failures of the resource block set, and the initial value of the LBT failure counter associated with the resource block set may be zero.

[0190] In some embodiments of the present disclosure, before a terminal sends sidelink data each time, the terminal's physical layer may first perform LBT failure detection on a resource block set. If LBT fails, the terminal's physical layer will submit an LBT failure indication for the resource block set to the MAC layer. Each time the terminal's MAC layer receives an LBT failure indication for a resource block set submitted by the physical layer, it may start or restart the LBT failure detection timer associated with the resource block set and increment the LBT failure counter associated with the resource block set by 1.

[0191] For example, when an LBT failure indication for a certain resource block set delivered by the physical layer is received, the LBT failure detection timer associated with the resource block set is started, and the LBT failure counter associated with the resource block set is incremented by 1. At this time, the number of LBT failures for the resource block set is 1. Thereafter, while the LBT failure detection timer associated with the resource block set is running, an LBT failure indication for the resource block set delivered by the physical layer is received, the LBT failure detection timer associated with the resource block set is restarted, and the LBT failure counter associated with the resource block set is incremented by 1. At this time, the number of LBT failures for the resource block set is 2.

[0192] In an embodiment of the present disclosure, the terminal can count the number of LBT failures of the resource block set based on the LBT failure indication of the resource block set, using the LBT failure detection timer and LBT failure counter associated with the resource block set, thereby realizing SL continuous LBT failure detection at the granularity of the resource block set.

[0193] Please refer to Figure 12, which is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure, which is executed by a terminal. As shown in Figure 12, the method may include but is not limited to the following steps:

[0194] Step 1201: upon receiving an LBT failure indication of a resource block set delivered by the physical layer, start or restart an LBT failure detection timer associated with the resource block set, and add 1 to an LBT failure counter associated with the resource block set.

[0195] In the embodiment of the present disclosure, step 1201 can be implemented in any of the embodiments of the present disclosure, and the present disclosure does not limit this and will not elaborate on it.

[0196] Step 1202: When the LBT failure counter associated with the resource block set is greater than or equal to a third threshold, determine that the resource block set triggers SL continuous LBT failure.

[0197] In some embodiments of the present disclosure, a resource block set of a terminal may be associated with at least one of the following: an LBT failure detection timer; an LBT failure counter; and a maximum number of LBT failure counts. In other words, the terminal may maintain one or more of an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts for a resource block set. Exemplarily, for each resource block set, the terminal maintains an LBT failure detection timer, an LBT failure counter, and a maximum number of LBT failure counts.

[0198] In some embodiments of the present disclosure, an LBT failure indication of a resource block set is received during the operation of an LBT failure detection timer associated with the resource block set, the LBT failure detection timer associated with the resource block set is started or restarted, and the LBT failure counter associated with the resource block set is increased by 1. During the operation of the LBT failure detection timer associated with the resource block set, if the LBT failure counter associated with the resource block set is greater than or equal to a third threshold, it can be determined that the resource block set triggers SL continuous LBT failure. That is, when the number of LBT failures of the resource block set is greater than or equal to the third threshold, it can be determined that the resource block set triggers SL continuous LBT failure.

[0199] In some embodiments of the present disclosure, the third threshold may be configured by the network device or may be pre-configured, and the third thresholds corresponding to different resource block sets may be the same or different, which is not limited in the present disclosure.

[0200] It should be noted that the third threshold in the present disclosure may refer to the maximum number of LBT failure counts associated with a resource block set. The maximum number of LBT failure counts associated with different resource block sets may be the same or different, and the present disclosure does not limit this.

[0201] In the embodiment of the present disclosure, the terminal may further determine that the resource pool triggers SL continuous LBT failure when the LBT failure counter associated with the resource block set is greater than or equal to a third threshold. Thus, whether the resource block set triggers SL continuous LBT failure can be determined based on the magnitude relationship between the LBT failure counter associated with the resource block set and the third threshold.

[0202] Please refer to Figure 13, which is a flow chart of another method for counting the number of consecutive SL LBT failures provided by an embodiment of the present disclosure, which is executed by a terminal. As shown in Figure 13, the method may include but is not limited to the following steps:

[0203] Step 1301: upon receiving an LBT failure indication of a resource block set delivered by the physical layer, start or restart an LBT failure detection timer associated with the resource block set, and add 1 to an LBT failure counter associated with the resource block set.

[0204] Step 1302: When the LBT failure counter associated with the resource block set is greater than or equal to a third threshold, determine that the resource block set triggers SL continuous LBT failure.

[0205] In the embodiment of the present disclosure, steps 1301 to 1302 may be implemented in any of the embodiments of the present disclosure, and the present disclosure does not limit this and will not elaborate on it.

[0206] Step 1303: When it is determined that the resource pool triggers SL continuous LBT failure, reselect resources from a resource pool where SL continuous LBT failure has not occurred.

[0207] In some embodiments of the present disclosure, when determining that a resource block set triggers SL continuous LBT failure, the terminal may reselect resources from a resource block set where SL continuous LBT failure has not occurred, that is, reselect resources from a resource block set where SL continuous LBT failure has never occurred.

[0208] In some embodiments of the present disclosure, the terminal operates in mode 2, that is, the terminal operating in mode 2 can reselect resources of a resource block set that has not experienced SL continuous LBT failure when it is determined that the resource block set triggers SL continuous LBT failure.

[0209] Optionally, if the resource pool granularity is larger than the resource block set granularity, when it is determined that the resource block set triggers SL continuous LBT failure, the resources of the resource block set in the resource pool to which the resource block set belongs, which has not experienced SL continuous LBT failure, can be reselected.

[0210] Optionally, if other resource block sets in the resource pool to which the resource block set belongs all experience SL continuous LBT failures, resources of resource block sets that have not experienced SL continuous LBT failures may be reselected from other resource pools.

[0211] Optionally, if the resource pool granularity is larger than the resource block set granularity, when it is determined that the resource block set triggers SL continuous LBT failure, resources of the resource block set in the resource pool other than the resource pool to which the resource block set belongs, which has not experienced SL continuous LBT failure, can be reselected.

[0212] Optionally, if the resource pool granularity is larger than the resource block set granularity, when it is determined that a resource block set has triggered an SL continuous LBT failure, the resources of a resource block set that has not experienced an SL continuous LBT failure in the resource pool to which the resource block set belongs may be preferentially reselected. If it is not possible to reselect the resources of a resource block set that has not experienced an SL continuous LBT failure in the resource pool to which the resource block set belongs, the resources of a resource block set that has not experienced an SL continuous LBT failure in a resource pool other than the resource pool to which the resource block set belongs may be reselected.

[0213] Optionally, if the resource pool granularity is greater than the resource block set granularity, when it is determined that a resource block set has triggered an SL continuous LBT failure, resources of a resource block set that has not experienced an SL continuous LBT failure in a resource pool other than the resource pool to which the resource block set belongs may be preferentially reselected. If it is not possible to reselect resources of a resource block set that has not experienced an SL continuous LBT failure in a resource pool other than the resource pool to which the resource block set belongs, resources of a resource block set that has not experienced an SL continuous LBT failure in the resource pool to which the resource block set belongs will be reselected.

[0214] Optionally, if the resource pool granularity is smaller than the resource block set granularity, when it is determined that the resource block set triggers SL continuous LBT failure, the resources of the resource block set that has not experienced SL continuous LBT failure can be re-selected.

[0215] In an embodiment of the present disclosure, the terminal can count the number of LBT failures of the resource block set based on the LBT failure indication of the resource block set to realize SL continuous LBT failure detection at the granularity of the resource block set. It can also determine whether the resource block set triggers SL continuous LBT failure based on the size relationship between the LBT failure counter associated with the resource block set and the third threshold, and reselect the resources of the resource block set when it is determined that the resource block set triggers SL continuous LBT failure to ensure normal side link communication.

[0216] To facilitate understanding of the method for counting the number of SL consecutive LBT failures in the embodiment of the present disclosure, the following examples are provided for explanation:

[0217] In an optional embodiment, the granularity of SL continuous LBT failure detection is the resource pool granularity, and the number of LBT failures of all resource block sets belonging to this resource pool is counted.

[0218] Optionally, the terminal maintains an LBT_RP_counter variable for each resource pool, and the initial value of the variable is 0. The terminal maintains an LBT failure detection timer for each resource pool. When the terminal receives an LBT failure indication for a resource block set belonging to this resource pool submitted by the physical layer, it starts or restarts the LBT failure detection timer associated with the resource pool, and adds 1 to the LBT_RP_counter. When the LBT_RP_counter is greater than or equal to the maximum number of LBT failures, the terminal determines that the resource pool has triggered SL continuous LBT failure.

[0219] Optionally, if part but not all of a resource block set belongs to the resource pool, the terminal also needs to count this resource block set when counting the number of LBT failures in the resource pool. Another possible implementation is that if only part of a resource block set belongs to the resource pool, the terminal does not count this resource block set when counting the number of LBT failures in the resource pool. Optionally, counting or not counting can be implemented by the terminal. Optionally, whether to count in this case can be configured on the network side. For example, the network configures an indication parameter to indicate to the terminal whether to count in this case.

[0220] In an optional embodiment, the granularity of SL continuous LBT failure detection is the resource pool granularity, and the number of LBT failures of the resource block set to which the resource pool belongs is counted.

[0221] Optionally, the terminal maintains an LBT_RP_counter variable for each resource pool, and the initial value of the variable is 0. The terminal maintains an LBT failure detection timer for each resource pool. When the terminal receives an LBT failure indication for the resource block set to which the resource pool belongs, which is submitted by the physical layer, the terminal starts or restarts the LBT failure detection timer associated with the resource pool, and the LBT_RP_counter is incremented by 1. When the LBT_RP_counter is greater than or equal to the maximum number of LBT failures, the terminal determines that the resource pool has triggered continuous LBT failures.

[0222] Optionally, if only a part of a resource pool belongs to one resource block set and the other part belongs to another / multiple resource block sets, the terminal also needs to consider the more than one resource block sets when counting the number of LBT failures in the resource pool. That is to say, the LBT failure indication of any of the more than one resource block sets needs to be counted in the LBT failure count of the resource pool. Another possible implementation is that the terminal only considers the resource block set with the largest coverage when counting the number of LBT failures in the resource pool. For example, most of the resources in the resource pool belong to resource block set 1, then the terminal only considers resource block set 1 when counting the number of LBT failures in the resource pool. Optionally, in this case, which resource block set to count or which resource block set not to count can be implemented by the terminal. Optionally, the network side can configure whether it is necessary to count more than one resource block set in this case. For example, the network configures an indication parameter to indicate whether the terminal needs to count more than one resource block set in this case.

[0223] In an optional embodiment, the SL continuous LBT failure detection granularity is the resource pool granularity. When the resource pool triggers the SL continuous LBT failure, the terminal reselects the resources of the resource pool in which no SL continuous LBT failure occurs in the resource block set to which the resource pool belongs.

[0224] In an optional embodiment, the SL continuous LBT failure detection granularity is the resource pool granularity. When the resource pool triggers SL continuous LBT failure, the terminal reselects resources of a resource pool in which no SL continuous LBT failure occurs in a resource block set other than the resource block set to which the resource pool belongs.

[0225] Optionally, if the resource pool granularity is larger than the resource block set granularity, the resource pool triggers SL continuous LBT failure, and the terminal reselects resources from a resource pool where SL continuous LBT failure does not occur.

[0226] In an optional embodiment, the SL continuous LBT failure detection granularity is the resource block set granularity, and the LBT failure detection counter variable and the LBT failure detection timer are both maintained at the resource block set granularity.

[0227] Optionally, the terminal maintains an LBT_RB set_counter variable for each resource block set, and the initial value of the variable is 0. The terminal maintains an LBT failure detection timer for each resource block set. When the terminal receives an LBT failure indication for a resource block set submitted by the physical layer, it starts or restarts the LBT failure detection timer associated with the resource block set, and adds 1 to the LBT_RB set_counter. When the LBT_RB set_counter is greater than or equal to the maximum number of LBT failures, the terminal determines that the resource block set triggers SL continuous LBT failure.

[0228] In an optional embodiment, the SL continuous LBT failure detection granularity is the resource block set granularity. The resource block set triggers the SL continuous LBT failure, and the terminal reselects the resources of the resource block set in the resource pool to which the resource block set belongs, where no SL continuous LBT failure occurs.

[0229] Optionally, when a terminal operating in mode 2 detects that a resource block set triggers a SL continuous LBT failure, the terminal reselects resources in a resource block set that does not experience a SL continuous LBT failure in the resource pool where the resource block set that triggered the SL continuous LBT failure is located. If a resource block set cannot be selected from the resource pool, the terminal reselects resources in a resource block set that does not experience a SL continuous LBT failure in another resource pool.

[0230] In an optional embodiment, the SL continuous LBT failure detection granularity is the resource block set granularity. The resource block set triggers the SL continuous LBT failure. The terminal reselects resources of the resource block set in a resource pool other than the resource pool to which the resource block set belongs, where no SL continuous LBT failure occurs.

[0231] Optionally, the terminal operating in mode 2 detects that a resource block set triggers SL continuous LBT failure, and the terminal reselects resources on a resource block set where SL continuous LBT failure does not occur in a resource pool other than the resource pool where the resource block set that triggered the SL continuous LBT failure is located.

[0232] Optionally, if the granularity of the resource block set is larger than the granularity of the resource pool, the resource block set triggers SL continuous LBT failure, and the terminal reselects resources of the resource block set in which no SL continuous LBT failure occurs.

[0233] Please refer to Figure 14, which is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure. The communication device 1400 shown in Figure 10 may include a processing module 1401. In addition, the communication device 1400 may also include a transceiver module, which may include a sending module and / or a receiving module. The sending module is used to implement a sending function, and the receiving module is used to implement a receiving function. The transceiver module can implement the sending function and / or the receiving function.

[0234] It is understandable that the communication device 1400 may be a terminal, a device in a terminal, or a device that can be used in conjunction with a terminal.

[0235] The communication device 1400 is on the terminal side, wherein:

[0236] The processing module 1401 is configured to count the number of LBT failures of the resource pool according to the LBT failure indication of the resource block set belonging to the resource pool when sending sidelink data on the SL unlicensed frequency band.

[0237] Optionally, the processing module 1401 is used to start or restart the LBT failure detection timer associated with the resource pool and add 1 to the LBT failure counter associated with the resource pool when receiving an LBT failure indication of a resource block set belonging to the resource pool submitted by the physical layer.

[0238] Optionally, the processing module 1401 is configured to:

[0239] In the case where some resources of any resource block set belong to the resource pool, upon receiving an LBT failure indication of any resource block set, starting or restarting the LBT failure detection timer associated with the resource pool and adding 1 to the LBT failure counter associated with the resource pool; or

[0240] In the case that some resources of any resource block set belong to the resource pool, when an LBT failure indication of any resource block set is received, the LBT failure detection timer associated with the resource pool is not started or restarted, and the LBT failure counter associated with the resource pool is not increased by 1.

[0241] Optionally, the processing module 1401 is further configured to determine that the resource pool triggers SL continuous LBT failure when the LBT failure counter associated with the resource pool is greater than or equal to a first threshold.

[0242] Optionally, the processing module 1401 is further configured to, when it is determined that the resource pool triggers SL continuous LBT failure, reselect resources from a resource pool in which SL continuous LBT failure has not occurred.

[0243] Optionally, a resource pool is associated with at least one of the following:

[0244] An LBT failure detection timer;

[0245] An LBT failure counter;

[0246] The maximum number of LBT failures.

[0247] Optionally, a resource pool includes one or more resource block sets.

[0248] Optionally, the transceiver module can be used to receive an LBT failure detection timer configured by the network device for the resource pool.

[0249] Optionally, the transceiver module is further configured to receive a first threshold configured by the network device for the resource pool.

[0250] In an embodiment of the present disclosure, when the terminal sends side link data on the SL unlicensed frequency band, the number of LBT failures of the resource pool can be counted based on the LBT failure indication of the resource block set belonging to the resource pool. Therefore, when the resource pool granularity is larger than the resource block set granularity, the number of LBT failures of the resource pool can be counted based on the LBT failure indication of the resource block set belonging to the resource pool, thereby realizing SL continuous LBT failure detection at the resource pool granularity.

[0251] It is understandable that the communication device 1400 may be a terminal, a device in a terminal, or a device that can be used in conjunction with a terminal.

[0252] The communication device 1400 is on the terminal side, wherein:

[0253] The processing module 1401 is configured to count the number of LBT failures of the resource pool according to the LBT failure indication of the resource block set to which the resource pool belongs when sending sidelink data on the SL unlicensed frequency band.

[0254] Optionally, the processing module 1401 is used to start or restart the LBT failure detection timer associated with the resource pool and add 1 to the LBT failure counter associated with the resource pool when receiving the LBT failure indication of the resource block set to which the resource pool belongs submitted by the physical layer.

[0255] Optionally, the processing module 1401 is used to start or restart the LBT failure detection timer associated with the resource pool and add 1 to the LBT failure counter associated with the resource pool when an LBT failure indication of any resource block set submitted by the physical layer is received, when part of the resources of the resource pool belong to any resource block set.

[0256] Optionally, the processing module 1401 is further configured to determine that the resource pool triggers SL continuous LBT failure when the LBT failure counter associated with the resource pool is greater than or equal to a second threshold.

[0257] Optionally, the processing module 1401 is further configured to, when it is determined that the resource pool triggers SL continuous LBT failure, reselect resources from a resource pool in which SL continuous LBT failure has not occurred.

[0258] Optionally, the processing module 1401 is further configured to reselect resources of a resource pool in which no SL continuous LBT failure has occurred in the resource block set to which the resource pool belongs.

[0259] Optionally, the processing module 1401 is further configured to reselect resources of a resource pool in which no SL continuous LBT failure occurs in a resource block set outside the resource block set to which the resource pool belongs.

[0260] Optionally, a resource pool is associated with at least one of the following:

[0261] An LBT failure detection timer;

[0262] An LBT failure counter;

[0263] The maximum number of times an LBT failure is counted. Optionally, the number of resource block sets to which a resource pool belongs is one or more.

[0264] Optionally, the transceiver module can be used to receive an LBT failure detection timer configured by the network device for the resource pool.

[0265] Optionally, the transceiver module is further configured to receive a second threshold configured by the network device for the resource pool.

[0266] In the disclosed embodiments, when a terminal transmits sidelink data on an SL unlicensed frequency band, the number of LBT failures of the resource pool can be counted based on the LBT failure indication of the resource block set to which the resource pool belongs. Thus, when the resource pool granularity is smaller than the resource block set granularity, the number of LBT failures of the resource pool can be counted based on the LBT failure indication of the resource block set to which the resource pool belongs, thereby implementing SL continuous LBT failure detection at the resource pool granularity. It is understood that the communication device 1400 can be a terminal, a device in a terminal, or a device that can be used in conjunction with a terminal.

[0267] The communication device 1400 is on the terminal side, wherein:

[0268] The processing module 1501 is configured to count the number of LBT failures of the resource block set according to the LBT failure indication of the resource block set when sending sidelink data on the SL unlicensed frequency band.

[0269] Optionally, the processing module 1401 is used to start or restart the LBT failure detection timer associated with the resource block set and add 1 to the LBT failure counter associated with the resource block set when receiving the LBT failure indication of the resource block set submitted by the physical layer.

[0270] Optionally, the processing module 1401 is further configured to determine that the resource block set triggers SL continuous LBT failure when the LBT failure counter associated with the resource block set is greater than or equal to a third threshold.

[0271] Optionally, the processing module 1401 is further configured to, when it is determined that the resource block set triggers SL continuous LBT failure, reselect resources of the resource block set in which SL continuous LBT failure has not occurred.

[0272] Optionally, the processing module 1401 is further configured to reselect resources of a resource block set in a resource pool to which the resource block set belongs and in which no SL continuous LBT failure has occurred.

[0273] Optionally, the processing module 1401 is further configured to reselect resources of a resource block set in a resource pool other than the resource pool to which the resource block set belongs, in which no SL continuous LBT failure has occurred.

[0274] Optionally, a resource block set is associated with at least one of the following:

[0275] An LBT failure detection timer;

[0276] An LBT failure counter;

[0277] The maximum number of LBT failures.

[0278] Optionally, the transceiver module can be used to receive an LBT failure detection timer configured by the network device for the resource block set.

[0279] Optionally, the transceiver module is further configured to receive a third threshold value configured by the network device for the resource block set.

[0280] In an embodiment of the present disclosure, when a terminal sends sidelink data on an SL unlicensed frequency band, the number of LBT failures of a resource block set can be counted according to the LBT failure indication of the resource block set, thereby realizing SL continuous LBT failure detection at the granularity of the resource block set.

[0281] Please refer to Figure 15, which is a schematic diagram of the structure of another communication device provided in an embodiment of the present disclosure. In Figure 11, the communication device 1500 can be a network device, a terminal, a chip, a chip system, or a processor that supports the network device to implement the above method, or a chip, a chip system, or a processor that supports the terminal to implement the above method. This device can be used to implement the method described in the above method embodiment. For details, please refer to the description of the above method embodiment.

[0282] The communication device 1500 may include one or more processors 1501. The processor 1501 may be a general-purpose processor or a dedicated processor. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control the communication device (e.g., a base station, a baseband chip, a terminal, a terminal chip, a DU or a CU, etc.), execute computer programs, and process computer program data.

[0283] Optionally, the communication device 1500 may further include one or more memories 1502, on which a computer program 1504 may be stored. The processor 1501 executes the computer program 1504 to cause the communication device 1500 to perform the method described in the above method embodiment. Optionally, the memory 1502 may also store data. The communication device 1500 and the memory 1502 may be provided separately or integrated together.

[0284] Optionally, the communication device 1500 may further include a transceiver 1505 and an antenna 1506. The transceiver 1505 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, and is configured to implement transceiver functions. The transceiver 1505 may include a receiver and a transmitter. The receiver may be referred to as a receiver or a receiving circuit, and is configured to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, and is configured to implement a transmitting function.

[0285] Optionally, the communication device 1500 may further include one or more interface circuits 1507. The interface circuit 1507 is configured to receive code instructions and transmit the instructions to the processor 1501. The processor 115 executes the code instructions to enable the communication device 1500 to perform the method described in the above method embodiment.

[0286] The communication device 1500 is a terminal: the processor 1501 is configured to execute step 301 in FIG. 3 and the like.

[0287] The communication device 1500 is a network device: the transceiver 1505 is used to execute step 601 in Figure 6; steps 701 and 702 in Figure 7; step 801 in Figure 8; and steps 901 and 902 in Figure 9.

[0288] In one implementation, processor 1501 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or may be used for transmitting or delivering signals.

[0289] In one implementation, processor 1501 may store a computer program 1503. Computer program 1503, when executed on processor 1501, enables communication device 1500 to perform the method described in the above method embodiment. Computer program 1503 may be embedded in processor 1501, in which case processor 1501 may be implemented by hardware.

[0290] In one implementation, the communication device 1500 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in the present disclosure can be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0291] The communication device described in the above embodiments may be a network device or a terminal, 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 FIG15. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

[0292] (1) An independent integrated circuit (IC), or chip, or chip system or subsystem;

[0293] (2) a collection of one or more ICs, optionally including a storage component for storing data and computer programs;

[0294] (3) ASIC, such as modem;

[0295] (4) Modules that can be embedded in other devices;

[0296] (5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;

[0297] (6)Others, etc.

[0298] If the communication device can be a chip or a chip system, please refer to the schematic diagram of the chip structure shown in Figure 16. The chip 1600 shown in Figure 16 includes a processor 1601 and an interface 1603. The number of processors 1601 can be one or more, and the number of interfaces 1603 can be multiple.

[0299] For the case where the chip is used to implement the functions of the terminal in the embodiments of the present disclosure:

[0300] Interface 1603 is used to execute step 201 in FIG. 2 , step 301 in FIG. 3 , etc.

[0301] Optionally, the chip 1600 further includes a memory 1602 , which is used to store necessary computer programs and data.

[0302] Those skilled in the art will also appreciate that the various illustrative logical blocks and steps listed in the embodiments of the present disclosure may be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the described functionality for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of the present disclosure.

[0303] The present disclosure also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

[0304] The present disclosure also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0305] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0306] Those skilled in the art will understand that the various numerical numbers such as first and second involved in the present disclosure are only for the convenience of description and are not used to limit the scope of the embodiments of the present disclosure, and also indicate the order of precedence.

[0307] The at least one in the present disclosure can also be described as one or more, and the multiple can be two, three, four or more, which is not limited in the present disclosure. In the embodiments of the present disclosure, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", and there is no order of precedence or size between the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0308] The correspondences shown in the tables of the present disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values, which are not limited by the present disclosure. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, in the tables of the present disclosure, the correspondences shown in certain rows may not be configured. For another example, appropriate deformation adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables may also adopt other names that can be understood by the communication device, and the values ​​or representations of the parameters may also adopt other values ​​or representations that can be understood by the communication device. When implementing the above tables, other data structures may also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables, etc.

Claims

1. A method for counting the number of consecutive LBT failures of a sidelink SL, characterized in that: Executed by a terminal, the method includes: When sending sidelink data on the SL unlicensed frequency band, the number of LBT failures of the resource pool is counted according to the LBT failure indication of the resource block set RB set belonging to the resource pool.

2. The method according to claim 1, characterized in that The counting of the number of LBT failures of the resource pool according to the LBT failure indication of the resource block set belonging to the resource pool comprises: When receiving an LBT failure indication of a resource block set belonging to the resource pool submitted by the physical layer, the LBT failure detection timer associated with the resource pool is started or restarted, and the LBT failure counter associated with the resource pool is increased by 1.

3. The method according to claim 1 or 2, characterized in that The counting of the number of LBT failures of the resource pool according to the LBT failure indication of the resource block set belonging to the resource pool comprises: In the case where some resources of any resource block set belong to the resource pool, upon receiving an LBT failure indication of any resource block set, starting or restarting an LBT failure detection timer associated with the resource pool, and adding 1 to an LBT failure counter associated with the resource pool; or, In the case that some resources of any resource block set belong to the resource pool, upon receiving an LBT failure indication of any resource block set, the LBT failure detection timer associated with the resource pool is not started or restarted, and the LBT failure counter associated with the resource pool is not increased by 1.

4. The method according to claim 2 or 3, characterized in that Also includes: When the LBT failure counter associated with the resource pool is greater than or equal to the first threshold, it is determined that the resource pool triggers SL continuous LBT failure.

5. The method according to any one of claims 1 to 4, characterized in that Also includes: When it is determined that the resource pool triggers the SL continuous LBT failure, resources of the resource pool where the SL continuous LBT failure has not occurred are reselected.

6. The method according to any one of claims 1 to 5, characterized in that The resource pool is associated with at least one of the following: An LBT failure detection timer; An LBT failure counter; The maximum number of times an LBT failure is counted.

7. The method according to any one of claims 1 to 6, characterized in that The resource pool includes one or more resource block sets.

8. A method for counting the number of consecutive LBT failures of a sidelink SL, characterized in that: Executed by a terminal, the method includes: When sending sidelink data on the SL unlicensed frequency band, the number of LBT failures of the resource pool is counted according to the LBT failure indication of the resource block set to which the resource pool belongs.

9. The method according to claim 8, characterized in that The counting of the number of LBT failures of the resource pool according to the LBT failure indication of the resource block set to which the resource pool belongs includes: When receiving the LBT failure indication of the resource block set to which the resource pool belongs submitted by the physical layer, the LBT failure detection timer associated with the resource pool is started or restarted, and the LBT failure counter associated with the resource pool is increased by 1.

10. The method according to claim 8 or 9, characterized in that The counting of the number of LBT failures of the resource pool according to the LBT failure indication of the resource block set to which the resource pool belongs includes: In the case that some resources of the resource pool belong to any resource block set, upon receiving the LBT failure indication of any resource block set submitted by the physical layer, the LBT failure detection timer associated with the resource pool is started or restarted, and the LBT failure counter associated with the resource pool is increased by 1.

11. The method according to claim 9 or 10, characterized in that Also includes: When the LBT failure counter associated with the resource pool is greater than or equal to the second threshold, it is determined that the resource pool triggers SL continuous LBT failure.

12. The method according to any one of claims 8 to 11, characterized in that Also includes: When it is determined that the resource pool triggers the SL continuous LBT failure, resources of the resource pool where the SL continuous LBT failure has not occurred are reselected.

13. The method according to claim 12, characterized in that The reselecting of resources in a resource pool where no SL continuous LBT failure occurs includes: Reselect resources of a resource pool in which no SL continuous LBT failure has occurred in the resource block set to which the resource pool belongs.

14. The method according to claim 12 or 13, characterized in that The reselecting of resources in a resource pool where no SL continuous LBT failure occurs includes: Reselect resources of a resource pool in which no SL continuous LBT failure has occurred in a resource block set outside the resource block set to which the resource pool belongs.

15. The method according to any one of claims 8 to 14, characterized in that The resource pool is associated with at least one of the following: An LBT failure detection timer; An LBT failure counter; The maximum number of times an LBT failure is counted.

16. The method according to any one of claims 8 to 15, characterized in that The number of resource block sets to which the resource pool belongs is one or more.

17. A method for counting the number of consecutive LBT failures of a sidelink SL, characterized in that: Executed by a terminal, the method includes: When sending sidelink data on the SL unlicensed frequency band, the number of LBT failures of the resource block set is counted according to the LBT failure indication of the resource block set.

18. The method according to claim 17, characterized in that The counting of the number of LBT failures of the resource block set according to the LBT failure indication of the resource block set includes: When the LBT failure indication of the resource block set submitted by the physical layer is received, the LBT failure detection timer associated with the resource block set is started or restarted, and the LBT failure counter associated with the resource block set is increased by 1.

19. The method according to claim 17 or 18, characterized in that Also includes: When the LBT failure counter associated with the resource block set is greater than or equal to a third threshold, it is determined that the resource block set triggers SL continuous LBT failure.

20. The method according to any one of claims 17 to 19, characterized in that Also includes: In the case where it is determined that the resource block set triggers SL continuous LBT failure, resources of the resource block set in which SL continuous LBT failure has not occurred are reselected.

21. The method according to claim 20, characterized in that The reselecting of resources of a resource block set in which no SL continuous LBT failure occurs comprises: Reselect resources of a resource block set in a resource pool to which the resource block set belongs, in which no SL continuous LBT failure has occurred.

22. The method according to claim 20 or 21, characterized in that The reselecting of resources of a resource block set in which no SL continuous LBT failure occurs comprises: Reselect resources of a resource block set in a resource pool other than the resource pool to which the resource block set belongs, in which no SL continuous LBT failure has occurred.

23. The method according to any one of claims 17 to 22, characterized in that The resource block set is associated with at least one of the following: An LBT failure detection timer; An LBT failure counter; The maximum number of times an LBT failure is counted.

24. A communication device, characterized in that: include: The processing module is used to count the number of LBT failures of the resource pool according to the LBT failure indication of the resource block set belonging to the resource pool when sending side link data on the SL unlicensed frequency band.

25. A communication device, characterized in that: include: The processing module is used to count the number of LBT failures of the resource pool according to the LBT failure indication of the resource block set to which the resource pool belongs when sending side link data on the SL unlicensed frequency band.

26. A communication device, characterized in that: include: The processing module is used to count the number of LBT failures of the resource block set according to the LBT failure indication of the resource block set when sending side link data on the SL unlicensed frequency band.

27. A communication device, characterized in that: The device includes a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory so that the device performs the method as described in any one of claims 1 to 7, or performs the method as described in any one of claims 8 to 16, or performs the method as described in any one of claims 17 to 23.

28. A computer-readable storage medium storing instructions, which, when executed, implement the method according to any one of claims 1 to 7, or implement the method according to any one of claims 8 to 16, or implement the method according to any one of claims 17 to 23.