A method and apparatus for determining a trigger for continuous LBT failure

Abstract

The present disclosure provides a method and device for determining continuous LBT failure triggering, which can be applied in the field of communication technology. The method comprises: counting the number of LBT failures on sidelink when transmitting sidelink data on unlicensed frequency bands; and determining continuous LBT failure triggering in the case that the number of LBT failures is greater than or equal to the maximum number of LBT failures. Thus, the terminal device can count the number of LBT failures and determine whether to trigger continuous LBT failure when using unlicensed frequency bands for sidelink communication.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of communication, and particularly relates to a method and device for determining continuous LBT failure triggering. BACKGROUND

[0002] In the related art, uplink and downlink operations can be performed in an unlicensed frequency band, wherein channel access of the downlink and the uplink both depend on listen before talk (LBT) characteristics. In addition, in order to support direct communication between terminal devices, a sidelink communication mode is introduced. The sidelink communication can also use the unlicensed frequency band, and the terminal device also needs to perform LBT when transmitting sidelink data in the unlicensed frequency band. SUMMARY

[0003] The first aspect of the present disclosure provides a method for determining continuous LBT failure triggering, applied to a terminal device, and the method comprises the following steps:

[0004] When transmitting sidelink data in the unlicensed frequency band, counting the number of LBT failures on the sidelink;

[0005] In the case where the number of LBT failures is greater than or equal to the maximum number of LBT failures, determining that continuous LBT failure triggering is triggered.

[0006] In the technical solution, when transmitting sidelink data in the unlicensed frequency band, the number of LBT failures on the sidelink is counted, and in the case where the number of LBT failures is greater than or equal to the maximum number of LBT failures, it is determined that continuous LBT failure triggering is triggered. Therefore, the number of LBT failures can be counted and it can be determined whether continuous LBT failure triggering is triggered when using the unlicensed frequency band for sidelink communication.

[0007] The second aspect of the present disclosure provides another method for determining continuous LBT failure triggering, applied to a network device, and the method comprises the following steps:

[0008] Sending indication information to the terminal device, wherein the indication information is used to instruct the terminal device to count the number of LBT failures on the sidelink according to a specified counting manner when transmitting sidelink data in the unlicensed frequency band.

[0009] In the present disclosure, indication information is sent to the terminal device, wherein the indication information is used to instruct the terminal device to count the number of LBT failures on the sidelink according to a specified counting manner when sending sidelink data on the unlicensed frequency band. Therefore, the network device can instruct the terminal device to count the number of LBT failures on the sidelink according to the specified manner, so that the terminal device can count the number of LBT failures on the sidelink according to the specified manner in the indication information, and realize counting of the number of LBT failures on the sidelink and how to determine whether to trigger continuous LBT failure.

[0010] The third aspect embodiment of the present disclosure provides a communication device applied to a terminal device, and the device comprises:

[0011] The processing module is configured to count the number of LBT failures on the sidelink when sending sidelink data on the unlicensed frequency band, and determine to trigger continuous LBT failure when the number of LBT failures is greater than or equal to the maximum number of LBT failures.

[0012] The fourth aspect embodiment of the present disclosure provides another communication device applied to a network device, and the device comprises:

[0013] The transceiver module is configured to send indication information to the terminal device, wherein the indication information is used to instruct the terminal device to count the number of LBT failures on the sidelink according to a specified counting manner when sending sidelink data on the unlicensed frequency band.

[0014] The fifth aspect embodiment of the present disclosure provides a communication device, which comprises a processor. When the processor invokes a computer program in a memory, the method of the first aspect described above is executed.

[0015] The sixth aspect embodiment of the present disclosure provides another communication device, which comprises a processor. When the processor invokes a computer program in a memory, the method of the second aspect described above is executed.

[0016] The seventh aspect embodiment of the present disclosure provides a communication device, which comprises a processor and a memory. The memory stores a computer program. The processor executes the computer program stored in the memory, so that the communication device executes the method of the first aspect described above.

[0017] The eighth aspect embodiment of the present disclosure provides another communication device, which comprises a processor and a memory. The memory stores a computer program. The processor executes the computer program stored in the memory, so that the communication device executes the method of the second aspect described above.

[0018] The ninth aspect of the present disclosure provides another communication device, which comprises a processor and an interface circuit for receiving code instructions and transmitting to the processor, and the processor is configured to run the code instructions to make the device perform the method of the first aspect.

[0019] The tenth aspect of the present disclosure provides another communication device, which comprises a processor and an interface circuit for receiving code instructions and transmitting to the processor, and the processor is configured to run the code instructions to make the device perform the method of the second aspect.

[0020] The eleventh aspect of the present disclosure provides a system for determining a trigger continuous LBT failure, which comprises the communication device of the third aspect and the communication device of the fourth aspect, or the communication device of the fifth aspect and the communication device of the sixth aspect, or the communication device of the seventh aspect and the communication device of the eighth aspect, or the communication device of the ninth aspect and the communication device of the tenth aspect.

[0021] The twelfth aspect of the present disclosure provides a computer readable storage medium for storing instructions for the communication device, which when executed, causes the communication device to perform the method of the first aspect.

[0022] The thirteenth aspect of the present disclosure provides another computer readable storage medium for storing instructions for the communication device, which when executed, causes the communication device to perform the method of the second aspect.

[0023] The fourteenth aspect of the present disclosure provides a computer program product comprising a computer program which, when executed on a computer, causes the computer to perform the method of the first aspect.

[0024] The fifteenth aspect of the present disclosure provides another computer program product comprising a computer program which, when executed on a computer, causes the computer to perform the method of the second aspect.

[0025] The sixteenth aspect of the present disclosure provides a chip system, which comprises at least one processor and an interface for supporting the communication device to implement the functions related to the first aspect, such as determining or processing at least one of the data and information involved in the above method. In a possible design, the chip system further comprises a memory, and the memory is configured to store the necessary computer programs and data of the communication device. The chip system can be composed of a chip, or can comprise a chip and other discrete devices.

[0026] The seventeenth aspect of the embodiments of the present disclosure further provides another chip system, which comprises at least one processor and an interface for supporting the communication device to implement the functions related to the second aspect, for example, determining or processing at least one of the data and information involved in the above method. In a possible design, the chip system further comprises a memory, and the memory is configured to store the computer programs and data necessary for the communication device. The chip system can be composed of a chip, or can comprise a chip and other discrete devices.

[0027] The eighteenth aspect of the embodiments of the present disclosure further provides a computer program, which, when executed on a computer, causes the computer to perform the method of the first aspect.

[0028] The nineteenth aspect of the embodiments of the present disclosure further provides another computer program, which, when executed on a computer, causes the computer to perform the method of the second aspect. BRIEF DESCRIPTION OF DRAWINGS

[0029] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background art, the drawings needed to be used in the embodiments of the present disclosure or the background art will be described below.

[0030] Figure 1 An architecture schematic diagram of a communication system provided by the embodiments of the present disclosure;

[0031] Figure 2 A flowchart of a method for determining a trigger of continuous LBT failure provided by the embodiments of the present disclosure;

[0032] Figure 3 A flowchart of another method for determining a trigger of continuous LBT failure provided by the embodiments of the present disclosure;

[0033] Figure 4 A flowchart of another method for determining a trigger of continuous LBT failure provided by the embodiments of the present disclosure;

[0034] Figure 5 A flowchart of another method for determining a trigger of continuous LBT failure provided by the embodiments of the present disclosure;

[0035] Figure 6 A flowchart of another method for determining a trigger of continuous LBT failure provided by the embodiments of the present disclosure;

[0036] Figure 7 A flowchart of another method for determining a trigger of continuous LBT failure provided by the embodiments of the present disclosure;

[0037] Figure 8 A flowchart of another method for determining a trigger of continuous LBT failure provided by the embodiments of the present disclosure;

[0038] Figure 9 A flowchart illustrating another method for determining a continuous LBT failure as provided in an embodiment of this disclosure;

[0039] Figure 10 A flowchart illustrating another method for determining a continuous LBT failure as provided in an embodiment of this disclosure;

[0040] Figure 11 A flowchart illustrating another method for determining a continuous LBT failure as provided in an embodiment of this disclosure;

[0041] Figure 12 A flowchart illustrating another method for determining a continuous LBT failure as provided in an embodiment of this disclosure;

[0042] Figure 13 A flowchart illustrating another method for determining a continuous LBT failure as provided in an embodiment of this disclosure;

[0043] Figure 14 This is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure;

[0044] Figure 15 This is a schematic diagram of another communication device provided in an embodiment of the present disclosure;

[0045] Figure 16 This is a schematic diagram of the chip structure provided in an embodiment of this disclosure. Detailed Implementation

[0046] To better understand the method for determining continuous LBT failures disclosed in this disclosure, the communication system to which this disclosure applies is first described below.

[0047] Please see Figure 1 , Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of the present disclosure. The communication system may include, but is not limited to, a network device and a terminal device. Figure 1 The number and form of devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of this disclosure. In actual applications, two or more network devices and two or more terminal devices may be included. Figure 1 The communication system shown is an example including a network device 11 and a terminal device 12.

[0048] 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) system, 5th generation (5G) mobile communication system, 5G new radio (NR) system, or other future new mobile communication system, etc.

[0049] The network device 11 in the embodiments of the present disclosure is an entity for transmitting or receiving signals on the network side. For example, the network device 101 can be an evolved NodeB (eNB), a transmission reception point (TRP), a next generation NodeB (gNB) in the NR system, a base station in other future mobile communication system, or an access node in a wireless fidelity (WiFi) system, etc. The embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the network device. The network device provided by the embodiments of the present disclosure can be composed of a central unit (CU) and a distributed unit (DU), wherein the CU can also be referred to as a control unit. The structure of CU-DU can split the protocol layer of the network device, for example, the base station, and the functions of part of the protocol layer are placed in the CU for centralized control, and the functions of the remaining part or all of the protocol layer are distributed in the DU and controlled by the CU.

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

[0051] It can be understood that the communication system described in the embodiments of the present disclosure is for more clearly illustrating the technical solutions of the embodiments of the present disclosure, and does not constitute a limitation on the technical solutions provided by the embodiments of the present disclosure. Those skilled in the art can know that, with the evolution of system architecture and the appearance of new business scenarios, the technical solutions provided by the embodiments of the present disclosure are also applicable to similar technical problems.

[0052] In the related art, uplink and downlink operations can be performed in an unlicensed frequency band, wherein channel access of the downlink and the uplink both depend on LBT characteristics. In addition, in order to support direct communication between terminal devices, a sidelink communication mode is introduced. The sidelink communication can also use the unlicensed frequency band, and the terminal device also needs to perform LBT when transmitting sidelink data on the unlicensed frequency band.

[0053] In the present disclosure, when the terminal device transmits sidelink data on the unlicensed frequency band, the number of LBT failures on the sidelink is counted, and in the case that the number of LBT failures is greater than or equal to the maximum number of LBT failures, it is determined that continuous LBT failure is triggered, thereby solving the problems of how to count the number of LBT failures and how to determine whether to trigger continuous LBT failure when the terminal device transmits sidelink data on the unlicensed frequency band.

[0054] A method and device for determining a continuous LBT failure trigger are provided in the disclosure.

[0055] Please refer to Figure 2 , Figure 2 A flowchart of a method for determining a continuous LBT failure trigger is provided for the embodiments of the disclosure, which is executed by a terminal device. As shown in Figure 2 , the method can include but is not limited to the following steps:

[0056] Step 201: When transmitting sidelink data on an unlicensed frequency band, count the number of LBT failures on the sidelink.

[0057] The sidelink data can include data, control signaling, hybrid automatic repeat request (HARQ) feedback, etc. transmitted by the terminal device to other terminal devices.

[0058] For example, the sidelink data can include control instructions transmitted on a physical sidelink control channel (PSCCH), data and control instructions transmitted on a physical sidelink shared channel (PSSCH), HARQ feedback transmitted on a physical sidelink feedback channel (PSFCH), etc.

[0059] In the disclosure, when the terminal device transmits sidelink data on an unlicensed frequency band, it will first perform LBT failure detection, and then transmit data when the LBT failure detection is successful. Therefore, the number of LBT failures when the terminal device transmits sidelink data on an unlicensed frequency band can be counted.

[0060] In the present disclosure, the number of LBT failures can be counted by using an LBT failure detection timer and an LBT failure number counter. The initial value of the LBT failure number counter can be zero. Before the terminal device transmits sidelink data each time, the physical layer of the terminal device will first perform LBT failure detection. If LBT fails, the physical layer of the terminal device will submit an LBT failure indication to the medium access control (MAC) layer. When the MAC layer of the terminal device receives the LBT failure indication submitted by the physical layer, the LBT failure number counter is incremented by one, and the LBT failure detection timer is started or restarted. If no LBT failure indication is received during the running of the LBT failure detection timer, the LBT failure number counter can be reset to 0.

[0061] In the present disclosure, the terminal device can count the number of LBT failures according to the resource pool granularity on the unlicensed frequency band, or according to the source address and target address granularity, or according to the activated bandwidth part (BWP) granularity on the unlicensed frequency band, or according to any two of the three granularities, or according to the three granularities respectively.

[0062] The counting of the number of LBT failures according to the resource pool granularity on the unlicensed frequency band can refer to counting the number of LBT failures when transmitting sidelink data using the resources in the resource pool. The counting of the number of LBT failures according to the source address and target address granularity can refer to counting the number of LBT failures when transmitting data from the terminal device corresponding to the source address to the terminal device corresponding to the target address. The counting of the number of LBT failures according to the activated BWP on the unlicensed frequency band can refer to counting the number of LBT failures when transmitting sidelink data using all resource pool resources in the BWP.

[0063] In actual applications, the sidelink and the air interface uplink can have priorities when transmitting data. Optionally, if the priority of the sidelink is lower than that of the air interface uplink, and the sidelink data is not successfully transmitted, in the case of counting the number of LBT failures on the sidelink, the sidelink LBT result can be counted or not counted, or randomly selected from the two options, and the present disclosure does not limit this.

[0064] Step 202, in the case where the number of LBT failures is greater than or equal to the maximum number of LBT failures, it is determined that the continuous LBT failure is triggered.

[0065] In the present disclosure, when the terminal device transmits sidelink data on the unlicensed frequency band, the number of LBT failures is counted, and when the number of LBT failures is greater than or equal to the maximum number of LBT failures, it can be determined that continuous LBT failure is triggered. Wherein, the maximum number of LBT failures can be preconfigured or configured by the network device, and the present disclosure does not limit it.

[0066] In the embodiments of the present disclosure, when the terminal device transmits sidelink data on the unlicensed frequency band, the number of LBT failures on the sidelink is counted, and in the case that the number of LBT failures is greater than or equal to the maximum number of LBT failures, it is determined that continuous LBT failure is triggered. Therefore, the number of LBT failures can be counted and it can be determined whether continuous LBT failure is triggered when using the unlicensed frequency band for sidelink communication.

[0067] Please refer to Figure 3 , Figure 3 The flowchart of another method for determining whether continuous LBT failure is triggered provided by the embodiments of the present disclosure is provided, which is executed by a terminal device. As shown in Figure 3 , the method can include but is not limited to the following steps:

[0068] Step 301, when transmitting sidelink data using resources in a resource pool, using an LBT failure detection timer to count the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH associated with the resource pool.

[0069] Wherein, the sidelink data can refer to the detailed description in the above embodiments, and the embodiments of the present disclosure will not be repeated.

[0070] Wherein, the PSSCH, PSCCH and PSFCH associated with the resource pool can be understood as the PSSCH, PSCCH and PSFCH resources of the resource pool.

[0071] In the present disclosure, there is an active BWP on the unlicensed frequency band, and one or more resource pools can be configured on the active BWP. When the terminal device transmits sidelink data on the unlicensed frequency band, the number of LBT failures can be counted in the granularity of the resource pool.

[0072] In the present disclosure, when the terminal device transmits data on PSSCH, PSCCH, PSFCH and other channels using resources in a resource pool, the LBT failure detection timer can be used to count the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH.

[0073] In the present disclosure, if multiple resource pools are configured on a BWP, the length of the LBT failure detection timer used for each resource pool can be preconfigured or configured by the network device, and the present disclosure does not make any limitation in this regard.

[0074] Optionally, in the present disclosure, the terminal device can receive the first configuration information sent by the network device, and determine the LBT failure detection timer and the maximum number of LBT failures according to the first configuration information. The maximum number of LBT failures is used to determine whether the resource pool triggers continuous LBT failure.

[0075] In the present disclosure, the first configuration information can be dedicated RRC signaling or system information block (SIB) system message, that is, the network device can send the first configuration information to the terminal device through dedicated RRC signaling or SIB system message.

[0076] In the present disclosure, the first configuration information can include any of the following: the maximum number of LBT failures and the LBT failure detection timer corresponding to the resource pool; the maximum number of LBT failures and the LBT failure detection timer corresponding to the bandwidth BWP to which the resource pool belongs; the maximum number of LBT failures and the LBT failure detection timer corresponding to the unlicensed frequency band; the maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device.

[0077] That is, in the present disclosure, the LBT failure detection timer used by the terminal device when counting the number of LBT failures of a certain resource pool, and the maximum number of LBT failures used to determine whether to trigger continuous LBT failure, can be the maximum number of LBT failures and the LBT failure detection timer corresponding to the resource pool, the maximum number of LBT failures and the LBT failure detection timer corresponding to the BWP to which the resource pool belongs, the maximum number of LBT failures and the LBT failure detection timer corresponding to the unlicensed frequency band, or the maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device.

[0078] For example, the network device configures the terminal device with the maximum number of LBT failures and the LBT failure detection timer corresponding to each resource pool under a BWP, and then the terminal device can use the LBT failure detection timer corresponding to each resource pool when counting the number of LBT failures of each resource pool under the BWP, and use the maximum number of LBT failures corresponding to each resource pool when determining whether each resource pool triggers continuous LBT failure.

[0079] For another example, the network device configures the terminal device with the maximum number of LBT failures and the LBT failure detection timer corresponding to the BWP. The terminal device can use the LBT failure detection timer corresponding to the BWP when counting the number of LBT failures on each resource pool of the BWP, and can use the maximum number of LBT failures corresponding to the BWP when determining whether each resource pool triggers continuous LBT failures.

[0080] For another example, the network device configures the terminal device with the maximum number of LBT failures and the LBT failure detection timer corresponding to the unlicensed frequency band. The terminal device can use the LBT failure detection timer corresponding to the unlicensed frequency band to which the resource pool belongs when counting the number of LBT failures on each resource pool, and can use the maximum number of LBT failures corresponding to the unlicensed frequency band to which the resource pool belongs when determining whether each resource pool triggers continuous LBT failures.

[0081] For another example, the network device configures the terminal device with the maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device. The terminal device can use the LBT failure detection timer corresponding to the terminal device when counting the number of LBT failures on each resource pool, and can use the maximum number of LBT failures corresponding to the terminal device when determining whether each resource pool triggers continuous LBT failures.

[0082] In the present disclosure, the resource pool can maintain an LBT failure number counter, and the initial value of the LBT failure number counter can be zero. When counting the number of LBT failures on one or more channels in the PSSCH, PSCCH and PSFCH associated with the resource pool, the MAC layer of the terminal device can start or restart the LBT failure detection timer when receiving the LBT failure indication submitted by the physical layer, and increase the LBT failure number counter corresponding to the resource pool by 1. If no LBT failure indication is received during the running of the LBT failure detection timer, the LBT failure number counter corresponding to the resource pool can be reset to 0. Thus, the count value of the LBT failure number counter corresponding to the resource pool is the sum of the number of LBT failures on one or more channels in the PSSCH, PSCCH and PSFCH.

[0083] In actual application, the sidelink and the air interface uplink can have priority when transmitting data. Optionally, when counting the number of LBT failures on one or more channels in the PSSCH, PSCCH and PSFCH associated with the resource pool, if the priority of the sidelink is lower than that of the air interface uplink, the sidelink LBT result can be counted or can not be counted, or a random selection can be made from counting the sidelink LBT result and not counting the sidelink LBT result, and the present disclosure does not limit this.

[0084] In step 302, the number of LBT failures of the resource pool is determined according to the number of LBT failures on one or more of the PSSCH, PSCCH and PSFCH.

[0085] In the present disclosure, the sum of the number of LBT failures on one or more of the PSSCH, PSCCH and PSFCH can be used as the number of LBT failures of the resource pool.

[0086] In the present disclosure, if multiple resource pools are configured on the BWP, the number of LBT failures corresponding to each resource pool can be determined using the above method.

[0087] In step 303, if the number of LBT failures of the resource pool is greater than or equal to the maximum number of LBT failures, it is determined that the resource pool triggers continuous LBT failure.

[0088] In the present disclosure, if the number of LBT failures of the resource pool is greater than or equal to the maximum number of LBT failures, it can be determined that the resource pool triggers continuous LBT failure. The maximum number of LBT failures can be preconfigured or configured by the network device, which is not limited in the present disclosure.

[0089] In the present disclosure, if multiple resource pools are configured on the BWP, the number of LBT failures of each resource pool can be determined using the above method, and according to the maximum number of LBT failures of each resource pool, it can be determined whether each resource pool triggers continuous LBT failure. The maximum number of LBT failures used when determining whether each resource pool triggers continuous LBT failure can be configured by the network device, as described above, or can be preconfigured, which is not limited in the present disclosure.

[0090] In the present disclosure, the terminal device can count the number of LBT failures on one or more of the PSSCH, PSCCH and PSFCH associated with the resource pool when transmitting sidelink data using the resources in the resource pool, and determine the number of LBT failures of the resource pool according to the number of LBT failures on one or more of the PSSCH, PSCCH and PSFCH. If the number of LBT failures of the resource pool is greater than or equal to the maximum number of LBT failures, it is determined that the resource pool triggers continuous LBT failure. Thus, when the terminal device transmits sidelink data on the unlicensed frequency band, the number of LBT failures can be counted in the granularity of the resource pool, and whether the resource pool triggers continuous LBT failure can be determined according to the number of LBT failures of the resource pool and the maximum number of LBT failures.

[0091] Please refer to Figure 4 , Figure 4Another flowchart for determining a method of triggering continuous LBT failure is provided for the embodiments of the present disclosure, which is executed by a terminal device. As shown in Figure 4 the method can include but is not limited to the following steps:

[0092] Step 401, when transmitting sidelink data using resources in a resource pool, using an LBT failure detection timer to count the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH associated with the resource pool.

[0093] Step 402, determining the number of LBT failures of the resource pool according to the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH.

[0094] Step 403, in the case that the number of LBT failures of the resource pool is greater than or equal to the maximum number of LBT failures, determining that the resource pool triggers continuous LBT failure.

[0095] In the present disclosure, steps 401-403 can be implemented in the manner of the embodiments shown in Figure 3 The embodiments of the present disclosure will not be described hereinafter.

[0096] Step 404, in the case that it is determined that the resource pool triggers continuous LBT failure, performing any one of the following operations: releasing all PC5-RRC connections associated with the terminal device; releasing all PC5-RRC connections associated with the terminal device and using resources of the resource pool; releasing PC5-RRC connections associated with the terminal device and using only resources of the resource pool.

[0097] In the present disclosure, in the case that it is determined that a certain resource pool triggers continuous LBT failure, the terminal device can release all PC5-radio resource control (PC5-RRC) connections associated with the terminal device, or release all PC5-RRC connections associated with the terminal device and using resources of the resource pool, or release PC5-RRC connections associated with the terminal device and using only resources of the resource pool.

[0098] Wherein, all PC5-RRC connections associated with the terminal device can refer to all PC5-RRC connections between the terminal device and other terminal devices; all PC5-RRC connections associated with the terminal device and using resources of the resource pool can refer to all PC5-RRC connections using resources of the resource pool among PC5-RRC connections between the terminal device and other terminal devices; PC5-RRC connections associated with the terminal device and using only resources of the resource pool can refer to PC5-RRC connections using only resources of the resource pool without using resources of other resource pools among PC5-RRC connections between the terminal device and other terminal devices.

[0099] In the embodiments of the present disclosure, when the terminal device transmits sidelink data on an unlicensed frequency band, the LBT failure number can be counted in the granularity of a resource pool. If the LBT failure number of the resource pool is greater than or equal to the maximum LBT failure number, it is determined that the resource pool triggers continuous LBT failure. In addition, if it is determined that a certain resource pool triggers continuous LBT failure, the terminal device associated PC5-RRC connection can be released, or all PC5-RRC connections associated with the terminal device using the resource pool resources can be released, or only the PC5-RRC connection associated with the terminal device using the resource pool resources can be released.

[0100] Please refer to Figure 5 , Figure 5 Another flowchart of a method for determining the trigger of continuous LBT failure is provided in the embodiments of the present disclosure, which is executed by a terminal device. As shown in Figure 5 , the method can include but is not limited to the following steps:

[0101] Step 501, for a source address and target address pair, using an LBT failure detection timer, counting the LBT failure number on one or more channels of PSSCH, PSCCH and PSFCH associated with the source address and target address pair.

[0102] Among them, the PSSCH, PSCCH and PSFCH associated with the source address and target address pair can be understood as all the sidelink PSSCH, PSCCH and PSFCH used by the source address and target address pair on one or more resource pools.

[0103] In the present disclosure, there can be one or more source address and target address pairs, for example, terminal device U0 performs sidelink communication with terminal devices U1, U2 and U3 respectively. For terminal device U0, there are three source address and target address pairs, which are U0 and U1, U0 and U2, and U0 and U3.

[0104] In the present disclosure, when the terminal device corresponding to the source address and the terminal device corresponding to the target address perform sidelink communication, the LBT failure detection timer can be used to count the LBT failure number on one or more channels of PSSCH, PSCCH and PSFCH used in the sidelink communication, without distinguishing the resource pool.

[0105] In the present disclosure, if there are multiple source address and target address pairs, the time length of the LBT failure detection timer used by each source address and target address pair can be preconfigured or configured by a network device, which is not limited in the present disclosure.

[0106] Optionally, in the disclosure, the terminal device can receive second configuration information sent by the network device, and can determine the LBT failure detection timer and the maximum number of LBT failures according to the second configuration information. The maximum number of LBT failures is used to determine whether the source address and the target address pair trigger continuous LBT failures.

[0107] In the disclosure, the second configuration information can be dedicated RRC signaling or SIB system message, that is, the network device can send the second configuration information to the terminal device through dedicated RRC signaling or SIB system message.

[0108] In the disclosure, the second configuration information can include any of the following: the maximum number of LBT failures and the LBT failure detection timer corresponding to the target address; and the maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device. It can be understood that the terminal device is the terminal device corresponding to the source address.

[0109] That is, in the disclosure, the LBT failure detection timer used by the terminal device to count the number of LBT failures of each source address and target address pair, and the maximum number of LBT failures used to determine whether to trigger continuous LBT failures, can be the maximum number of LBT failures and the LBT failure detection timer corresponding to the target address in the source address and target address pair, or the maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device (that is, the terminal device corresponding to the source address).

[0110] For example, the network device configures the terminal device with the maximum number of LBT failures and the LBT failure detection timer corresponding to each target address. Then, the terminal device corresponding to the source address can use the LBT failure detection timer corresponding to the target address when counting the number of LBT failures of each source address and target address pair, and can use the maximum number of LBT failures corresponding to the target address when determining whether each source address and target address pair triggers continuous LBT failures.

[0111] For another example, the network device configures the terminal device with the maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device. Then, the terminal device corresponding to the source address can use the LBT failure detection timer corresponding to the terminal device when counting the number of LBT failures of each source address and target address pair, and can use the maximum number of LBT failures corresponding to the terminal device when determining whether each source address and target address pair triggers continuous LBT failures.

[0112] In the present disclosure, a source address and a target address pair can maintain an LBT failure number counter, and the initial value of the LBT failure number counter can be zero. When counting the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH associated with the source address and the target address pair, the MAC layer of the terminal device can start or restart the LBT failure detection timer when receiving the LBT failure indication delivered by the physical layer, and add 1 to the LBT failure number counter corresponding to the source address and the target address pair. If no LBT failure indication is received during the running of the LBT failure detection timer, the LBT failure number counter corresponding to the source address and the target address pair can be reset to 0. Thus, the count value of the LBT failure number counter corresponding to the source address and the target address pair is the sum of the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH.

[0113] In actual application, the sidelink and the air interface uplink can have priority in sending data. Optionally, when counting the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH associated with the source address and the target address pair, if the sidelink data is not successfully sent due to the priority of the sidelink being lower than that of the air interface uplink, the sidelink LBT result can be counted or can not be counted, or a random selection can be made from counting the sidelink LBT result and not counting the sidelink LBT result, and the present disclosure does not limit this.

[0114] Step 502, determining the LBT failure number of the source address and the target address pair according to the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH.

[0115] In the present disclosure, the sum of the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH can be used as the LBT failure number of the source address and the target address pair.

[0116] In the present disclosure, if there are multiple source address and target address pairs, the LBT failure number corresponding to each source address and target address pair can be determined by using the above method.

[0117] Step 503, determining that the source address and the target address pair trigger continuous LBT failure in the case that the LBT failure number of the source address and the target address pair is greater than or equal to the maximum number of LBT failures.

[0118] In the present disclosure, if the number of LBT failures of a source address and a target address pair is greater than or equal to the maximum number of LBT failures, it can be determined that the source address and the target address pair trigger continuous LBT failures. The maximum number of LBT failures can be preconfigured or configured by a network device, and the present disclosure does not limit this.

[0119] In the present disclosure, if there are multiple source address and target address pairs, the number of LBT failures of each source address and target address pair can be determined by using the above method, and whether each source address and target address pair triggers continuous LBT failures can be determined according to the maximum number of LBT failures of each source address and target address pair. The maximum number of LBT failures used when determining whether each source address and target address pair triggers continuous LBT failures can be configured by a network device, as described above, or can be preconfigured, and the present disclosure does not limit this.

[0120] In the embodiments of the present disclosure, the terminal device can count the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH associated with the source address and the target address pair for the source address and the target address pair, and determine the number of LBT failures of the source address and the target address pair according to the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH. In the case where the number of LBT failures of the source address and the target address pair is greater than or equal to the maximum number of LBT failures, it is determined that the source address and the target address pair trigger continuous LBT failures. Therefore, when the terminal device transmits sidelink data on an unlicensed frequency band, it can count the number of LBT failures at the granularity of the source address and the target address pair, and determine whether the source address and the target address pair trigger continuous LBT failures according to the number of LBT failures of the source address and the target address pair and the maximum number of LBT failures.

[0121] Please refer to Figure 6 , Figure 6 The flowchart of another method for determining the trigger of continuous LBT failures provided by the embodiments of the present disclosure is provided, which is executed by a terminal device. As shown in Figure 6 , the method can include but is not limited to the following steps:

[0122] Step 601, for a source address and a target address pair, using an LBT failure detection timer, counting the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH associated with the source address and the target address pair.

[0123] Step 602, according to the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH, determining the number of LBT failures of the source address and the target address pair.

[0124] In step 603, it is determined that the source address and the target address pair trigger continuous LBT failure in a case where the number of LBT failures of the source address and the target address pair is greater than or equal to the maximum number of LBT failures.

[0125] In the present disclosure, steps 601-603 can be implemented in the manner of the embodiments shown in the drawings, and the present disclosure will not repeat the same. Figure 5 The present disclosure embodiments are implemented in the manner of the embodiments shown in the drawings, and the present disclosure will not repeat the same.

[0126] In step 604, any one of the following operations is performed in a case where it is determined that the source address and the target address pair trigger continuous LBT failure: releasing the PC5-RRC connection associated with the source address and the target address pair; and determining that the broadcast service or the anchor service associated with the target address trigger continuous LBT failure.

[0127] The PC5-RRC connection associated with the source address and the target address pair can refer to the PC5-RRC connection between the terminal device corresponding to the source address and the terminal device corresponding to the target address.

[0128] In the present disclosure, in a case where it is determined that the source address and the target address pair trigger continuous LBT failure, the PC5-RRC connection associated with the source address and the target address pair can be released, or it is determined that the broadcast service or the anchor service associated with the target address in the source address and the target address pair trigger continuous LBT failure.

[0129] Optionally, after it is determined that the broadcast service or the anchor service associated with the target address trigger continuous LBT failure, the terminal device can also notify the high layer, such as the V2X layer, that the broadcast service or the anchor service associated with the target address trigger continuous LBT failure.

[0130] In the present disclosure embodiments, when the terminal device transmits sidelink data on an unlicensed frequency band, the terminal device can count the number of LBT failures in the granularity of the source address and the target address pair, and determine that the source address and the target address pair trigger continuous LBT failure in a case where the number of LBT failures of the source address and the target address pair is greater than or equal to the maximum number of LBT failures. In addition, in a case where it is determined that a certain source address and target address pair trigger continuous LBT failure, the PC5-RRC connection associated with the source address and the target address pair can be released, or it is determined that the broadcast service or the anchor service associated with the target address in the source address and the target address pair trigger continuous LBT failure.

[0131] Please refer to Figure 7 , Figure 7 Another flowchart of a method for determining continuous LBT failure trigger provided by the present disclosure embodiments is provided, which is executed by a terminal device. As shown in Figure 7 , the method can include but is not limited to the following steps:

[0132] In step 701, when transmitting sidelink data using resources of all resource pools under the activated BWP, the LBT failure detection timer is used to count the number of LBT failures on one or more of the PSSCH, PSCCH and PSFCH associated with all resource pools under the BWP.

[0133] The sidelink data can refer to the detailed description in the above embodiments, and the embodiments of the present disclosure will not be repeated.

[0134] The PSSCH, PSCCH and PSFCH associated with all resource pools under the BWP can be understood as the PSSCH, PSCCH and PSFCH resources of all resource pools under the activated BWP.

[0135] In the present disclosure, when the terminal device transmits data on the PSSCH, PSCCH, PSFCH and the like using resources of all resource pools under the activated BWP on the unlicensed frequency band, the LBT failure detection timer can be used to count the number of LBT failures on one or more of the PSSCH, PSCCH and PSFCH.

[0136] In the present disclosure, the length of the LBT failure detection timer used can be preconfigured or configured by the network device, and the present disclosure does not limit this.

[0137] Optionally, in the present disclosure, the terminal device can receive third configuration information sent by the network device, and determine the LBT failure detection timer and the maximum number of LBT failures according to the third configuration information. The maximum number of LBT failures is used to determine whether the BWP triggers continuous LBT failure.

[0138] In the present disclosure, the third configuration information can be dedicated RRC signaling or SIB system message, that is, the network device can send the third configuration information to the terminal device through dedicated RRC signaling or SIB system message.

[0139] In the present disclosure, the third configuration information can include any of the following: the maximum number of LBT failures and the LBT failure detection timer corresponding to the BWP; the maximum number of LBT failures and the LBT failure detection timer corresponding to the unlicensed frequency band; the maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device.

[0140] That is, in the disclosure, the LBT failure detection timer used by the terminal device when counting the number of LBT failures of the BWP, and the maximum number of LBT failures used to determine whether to trigger continuous LBT failures, can be the maximum number of LBT failures and the LBT failure detection timer corresponding to the BWP, can also be the maximum number of LBT failures and the LBT failure detection timer corresponding to the unlicensed frequency band to which the BWP belongs, or can also be the maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device.

[0141] For example, the network device configures the terminal device with the maximum number of LBT failures and the LBT failure detection timer corresponding to the BWP, then when the terminal device counts the number of LBT failures of the BWP, the LBT failure detection timer corresponding to the BWP can be used, and when determining whether the BWP triggers continuous LBT failures, the maximum number of LBT failures corresponding to the BWP can be used.

[0142] For another example, the network device configures the terminal device with the maximum number of LBT failures and the LBT failure detection timer corresponding to the unlicensed frequency band, then when the terminal device counts the number of LBT failures of the BWP, the LBT failure detection timer corresponding to the unlicensed frequency band to which the BWP belongs can be used, and when determining whether the BWP triggers continuous LBT failures, the maximum number of LBT failures corresponding to the unlicensed frequency band to which the BWP belongs can be used.

[0143] For another example, the network device configures the terminal device with the maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device, then when the terminal device counts the number of LBT failures of the BWP, the LBT failure detection timer corresponding to the terminal device can be used, and when determining whether the BWP triggers continuous LBT failures, the maximum number of LBT failures corresponding to the terminal device can be used.

[0144] In the disclosure, the BWP can maintain an LBT failure number counter, and the initial value of the LBT failure number counter can be zero. When counting the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH associated with all resource pools under the BWP, the MAC layer of the terminal device can start or restart the LBT failure detection timer when receiving the LBT failure indication submitted by the physical layer, and add 1 to the LBT failure number counter corresponding to the BWP. If no LBT failure indication is received during the running of the LBT failure detection timer, the LBT failure number counter corresponding to the BWP can be reset to 0. Therefore, the count value of the LBT failure number counter corresponding to the BWP is the sum of the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH associated with all resource pools under the BWP.

[0145] In actual application, the sidelink and the air interface uplink can have priority in sending data. Optionally, when counting the number of LBT failures on one or more of the PSSCH, PSCCH and PSFCH associated with all resource pools under the BWP, if the sidelink data is not successfully sent due to the priority of the sidelink being lower than that of the air interface uplink, the sidelink LBT result can be counted or can not be counted, or one of the two can be randomly selected, and the present disclosure does not limit this.

[0146] Step 702, determining the number of LBT failures of the BWP according to the number of LBT failures on one or more of the PSSCH, PSCCH and PSFCH associated with all resource pools under the BWP.

[0147] In the present disclosure, the sum of the number of LBT failures on one or more of the PSSCH, PSCCH and PSFCH associated with all resource pools under the BWP can be taken as the number of LBT failures of the BWP.

[0148] Step 703, determining that the BWP triggers continuous LBT failure in the case that the number of LBT failures of the BWP is greater than or equal to the maximum number of LBT failures.

[0149] In the present disclosure, if the number of LBT failures of the BWP is greater than or equal to the maximum number of LBT failures, it can be determined that the BWP triggers continuous LBT failure. The maximum number of LBT failures can be preconfigured or configured by a network device, and the present disclosure does not limit this. The method for the network device to configure the maximum number of LBT failures is as described above, and the present embodiment will not be described here.

[0150] In the present embodiment, the terminal device can count the number of LBT failures on one or more of the PSSCH, PSCCH and PSFCH associated with all resource pools under the BWP when sending sidelink data using the resources of all resource pools under the activated BWP, and determine the number of LBT failures of the BWP according to the number of LBT failures on one or more of the PSSCH, PSCCH and PSFCH associated with all resource pools under the BWP. In the case that the number of LBT failures of the BWP is greater than or equal to the maximum number of LBT failures, it is determined that the BWP triggers continuous LBT failure. Thus, when the terminal device sends sidelink data on an unlicensed frequency band, it can count the number of LBT failures in BWP granularity, and determine whether the BWP triggers continuous LBT failure according to the number of LBT failures of the BWP and the maximum number of LBT failures.

[0151] Please refer toFigure 8 , Figure 8 Another flowchart for determining a method of triggering continuous LBT failure is provided for the embodiments of the present disclosure, which is executed by a terminal device. As shown in Figure 8 , the method can include but is not limited to the following steps:

[0152] Step 801, when transmitting sidelink data using resources of all resource pools under the activated BWP, using an LBT failure detection timer to count the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH associated with all resource pools under the BWP.

[0153] Step 802, determine the number of LBT failures of the BWP according to the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH.

[0154] Step 803, in the case where the number of LBT failures of the BWP is greater than or equal to the maximum number of LBT failures, determine that the BWP triggers continuous LBT failure.

[0155] In the present disclosure, steps 801-803 can be implemented in the manner of the embodiments shown in Figure 3 , and the embodiments of the present disclosure will not be described again.

[0156] Step 804, in the case where it is determined that the BWP triggers continuous LBT failure, perform any one of the following operations: release all PC5-RRC connections associated with the terminal device; release all PC5-RRC connections associated with the terminal device and using BWP resource pool resources.

[0157] Among them, all PC5-RRC connections associated with the terminal device can refer to all PC5-RRC connections between the terminal device and other terminal devices, and all PC5-RRC connections associated with the terminal device and using BWP resource pool resources can refer to all PC5-RRC connections using BWP resource pool resources among the PC5-RRC connections between the terminal device and other terminal devices.

[0158] In the present disclosure, in the case where it is determined that the BWP triggers continuous LBT failure, all PC5-RRC connections associated with the terminal device can be released, or all PC5-RRC connections associated with the terminal device and using BWP resource pool resources can be released.

[0159] In the embodiments of the present disclosure, when the terminal device transmits sidelink data on an unlicensed frequency band, the terminal device can count the number of LBT failures in a BWP granularity, and determine that the BWP triggers continuous LBT failures when the number of LBT failures of the BWP is greater than or equal to the maximum number of LBT failures. In addition, the terminal device can release the PC5-RRC connection associated with the terminal device or release all PC5-RRC connections associated with the terminal device and using BWP resource pool resources when it is determined that the BWP triggers continuous LBT failures.

[0160] Please refer to Figure 9 , Figure 9 Another flowchart of a method for determining a trigger of continuous LBT failures is provided in the embodiments of the present disclosure, and the method is executed by a terminal device. As shown in Figure 9 , the method can include but is not limited to the following steps:

[0161] Step 901, receiving indication information transmitted by a network device, wherein the indication information is used to instruct the terminal device to count the number of LBT failures on a sidelink in a specified counting manner.

[0162] In the present disclosure, the terminal device can receive indication information transmitted by a network device, wherein the indication information can be used to instruct the terminal device to count the number of LBT failures on a sidelink in a specified counting manner. Therefore, the terminal device can count the number of LBT failures on a sidelink in the counting manner indicated by the network device.

[0163] Optionally, the indication information can include any of the following: instructing the terminal device to count the number of LBT failures on a sidelink in a resource pool granularity; instructing the terminal device to count the number of LBT failures on a sidelink in a source address and target address granularity; and instructing the terminal device to count the number of LBT failures on a sidelink in a BWP granularity.

[0164] Then, if the indication information is used to instruct the terminal device to count the number of LBT failures on a sidelink in a resource pool granularity, the terminal device can count the number of LBT failures on a sidelink in the resource pool granularity; if the indication information is used to instruct the terminal device to count the number of LBT failures on a sidelink in a source address and target address granularity, the terminal device can count the number of LBT failures on a sidelink in the source address and target address granularity; and if the indication information is used to instruct the terminal device to count the number of LBT failures on a sidelink in a BWP granularity, the terminal device can count the number of LBT failures on a sidelink in the BWP granularity.

[0165] Optionally, the indication information can also be used to indicate the terminal device to count the number of LBT failures on the sidelink according to any two of the above three granularities, or to count the number of LBT failures according to the three granularities, and the embodiments of the present disclosure do not limit this.

[0166] At step 902, when transmitting sidelink data on the unlicensed frequency band, the number of LBT failures on the sidelink is counted according to the specified counting manner.

[0167] At step 903, in the case that the number of LBT failures is greater than or equal to the maximum number of LBT failures, it is determined that continuous LBT failure is triggered.

[0168] In the present disclosure, steps 902-903 can be implemented by any one of the embodiments of the present disclosure, and the embodiments of the present disclosure do not limit this and will not be repeated.

[0169] In the embodiments of the present disclosure, the terminal device can receive the indication information sent by the network device, and when transmitting sidelink data on the unlicensed frequency band, the number of LBT failures on the sidelink can be counted according to the counting manner specified by the indication information, and in the case that the number of LBT failures is greater than or equal to the maximum number of LBT failures, it is determined that continuous LBT failure is triggered. Therefore, the terminal device can count the number of LBT failures on the sidelink according to the counting manner indicated by the network device, and determine whether continuous LBT failure is triggered.

[0170] Please refer to Figure 10 , Figure 10 Another flowchart of a method for determining whether continuous LBT failure is triggered is provided for the embodiments of the present disclosure, and the method is executed by a network device. As shown in Figure 10 , the method can include but is not limited to the following steps:

[0171] At step 1001, indication information is sent to a terminal device, wherein the indication information is used to indicate the terminal device to count the number of LBT failures on the sidelink according to a specified counting manner when transmitting sidelink data on the unlicensed frequency band.

[0172] In the present disclosure, the network device can indicate the terminal device to count the number of LBT failures on the sidelink according to a specified manner by sending indication information to the network device.

[0173] Optionally, the indication information can include any one of the following: indicating the terminal device to count the number of LBT failures on the sidelink according to the resource pool granularity; indicating the terminal device to count the number of LBT failures on the sidelink according to the source address and target address granularity; and indicating the terminal device to count the number of LBT failures on the sidelink according to the BWP granularity.

[0174] So, if the indication information is used to indicate the terminal device to count the number of LBT failures on the sidelink in the resource pool granularity, the terminal device can count the number of LBT failures on the sidelink in the resource pool granularity; if the indication information is used to indicate the terminal device to count the number of LBT failures on the sidelink in the source address and target address granularity, the terminal device can count the number of LBT failures on the sidelink in the source address and target address granularity; if the indication information is used to indicate the terminal device to count the number of LBT failures on the sidelink in the BWP granularity, the terminal device can count the number of LBT failures on the sidelink in the BWP granularity.

[0175] Optionally, the indication information can also be used to indicate the terminal device to count the number of LBT failures on the sidelink in any two of the above three granularities, or to count the number of LBT failures in the three granularities, which is not limited in the embodiment of the present disclosure.

[0176] Wherein, counting the number of LBT failures in the resource pool granularity can refer to counting the number of LBT failures when transmitting sidelink data using the resources in the resource pool, and if multiple resource pools are configured on the activated BWP on the unlicensed frequency band, the number of LBT failures of each resource pool can be counted; counting the number of LBT failures in the source address and target address granularity can refer to counting the number of LBT failures when the terminal device corresponding to the source address transmits data to the terminal device corresponding to the target address; counting the number of LBT failures in the BWP can refer to counting the number of LBT failures when transmitting sidelink data using all resource pool resources under the activated BWP on the unlicensed frequency band.

[0177] In the embodiment of the present disclosure, the network device can send indication information to the terminal device, wherein the indication information is used to indicate the terminal device to count the number of LBT failures on the sidelink in a specified counting manner when transmitting sidelink data on the unlicensed frequency band. Therefore, the network device can indicate the terminal device to count the number of LBT failures on the sidelink in a specified manner, so that the terminal device can count the number of LBT failures on the sidelink according to the specified manner in the indication information, and realize counting the number of LBT failures on the sidelink and determining whether to trigger continuous LBT failure.

[0178] Please refer to Figure 11 , Figure 11 The flowchart of another method for determining whether to trigger continuous LBT failure provided by the embodiment of the present disclosure is provided, and the method is executed by the network device. As shown in Figure 11 , the method can include but is not limited to the following steps:

[0179] In step 1101, the first configuration information is sent to the terminal device, wherein the first configuration information is used for the terminal device to determine the maximum number of LBT failures and the LBT failure detection timer.

[0180] The LBT failure detection timer is used for counting the number of LBT failures of the resource pool, and the maximum number of LBT failures is used for determining whether the resource pool triggers continuous LBT failures.

[0181] In the present disclosure, the network device can send the first configuration information to the terminal device to configure the LBT failure detection timer used for counting the number of LBT failures of the resource pool for the terminal device, and configure the maximum number of LBT failures used for determining whether the resource pool triggers continuous LBT failures.

[0182] Optionally, the first configuration information can be dedicated RRC signaling or SIB system message.

[0183] Optionally, the first configuration information includes any one of the following: the maximum number of LBT failures and the LBT failure detection timer corresponding to the resource pool; the maximum number of LBT failures and the LBT failure detection timer corresponding to the bandwidth BWP to which the resource pool belongs; the maximum number of LBT failures and the LBT failure detection timer corresponding to the unlicensed frequency band; and the maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device.

[0184] For example, the network device configures the terminal device with the maximum number of LBT failures and the LBT failure detection timer corresponding to each resource pool under the BWP, and the terminal device can use the LBT failure detection timer corresponding to each resource pool when counting the number of LBT failures of each resource pool under the BWP, and can use the maximum number of LBT failures corresponding to each resource pool when determining whether each resource pool triggers continuous LBT failures.

[0185] For another example, the network device configures the terminal device with the maximum number of LBT failures and the LBT failure detection timer corresponding to the BWP, and the terminal device can use the LBT failure detection timer corresponding to the BWP when counting the number of LBT failures of each resource pool under the BWP, and can use the maximum number of LBT failures corresponding to the BWP when determining whether each resource pool triggers continuous LBT failures.

[0186] For another example, the network device configures the terminal device with the maximum number of LBT failures and the LBT failure detection timer corresponding to the unlicensed frequency band, and the terminal device can use the LBT failure detection timer corresponding to the unlicensed frequency band to which the resource pool belongs when counting the number of LBT failures of each resource pool, and can use the maximum number of LBT failures corresponding to the unlicensed frequency band to which the resource pool belongs when determining whether each resource pool triggers continuous LBT failures.

[0187] For another example, the network device configures the terminal device with the maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device, and the terminal device can use the LBT failure detection timer corresponding to the terminal device when counting the number of LBT failures of each resource pool, and can use the maximum number of LBT failures corresponding to the terminal device when determining whether each resource pool triggers continuous LBT failures.

[0188] In the embodiments of the present disclosure, the network device can send the first configuration information to the terminal device, and configure the terminal device with the LBT failure detection timer used when counting the number of LBT failures of the resource pool and the maximum number of LBT failures used when determining whether the resource pool triggers continuous LBT failures through the first configuration information. Therefore, the terminal device can count the number of LBT failures of the resource pool on the sidelink and determine whether the resource pool triggers continuous LBT failures according to the first configuration information.

[0189] Please refer to Figure 12 , Figure 12 The flowchart of another method for determining whether to trigger continuous LBT failures is provided in the embodiments of the present disclosure, and the method is executed by a network device. As shown in Figure 12 , the method can include but is not limited to the following steps:

[0190] Step 1201, sending second configuration information to the terminal device, wherein the second configuration information is used by the terminal device to determine the maximum number of LBT failures and the LBT failure detection timer.

[0191] In the present disclosure, the network device can send the second configuration information to the terminal device to configure the terminal device with the LBT failure detection timer used when counting the number of LBT failures of the source address and target address pair, and configure the terminal device with the maximum number of LBT failures used when determining whether the source address and target address pair triggers continuous LBT failures.

[0192] Optionally, the second configuration information can be dedicated RRC signaling or SIB system message.

[0193] Optionally, the second configuration information includes any of the following: the maximum number of LBT failures corresponding to the target address and the LBT failure detection timer; the maximum number of LBT failures corresponding to the terminal device and the LBT failure detection timer.

[0194] For example, the network device configures the terminal device with the maximum number of LBT failures corresponding to each target address and the LBT failure detection timer. The terminal device corresponding to the source address can use the LBT failure detection timer corresponding to the target address when counting the number of LBT failures of each source address and target address pair, and can use the maximum number of LBT failures corresponding to the target address when determining whether each source address and target address pair triggers continuous LBT failure.

[0195] For another example, the network device configures the terminal device with the maximum number of LBT failures corresponding to the terminal device and the LBT failure detection timer. The terminal device corresponding to the source address can use the LBT failure detection timer corresponding to the terminal device when counting the number of LBT failures of each source address and target address pair, and can use the maximum number of LBT failures corresponding to the terminal device when determining whether each source address and target address pair triggers continuous LBT failure.

[0196] In the embodiments of the present disclosure, the network device can send the second configuration information to the terminal device, and configure the terminal device with the LBT failure detection timer used when counting the number of LBT failures of the source address and target address pair, and the maximum number of LBT failures used when determining whether the source address and target address pair triggers continuous LBT failure, so that the terminal device can count the number of LBT failures of the source address and target address pair and determine whether the source address and target address pair triggers continuous LBT failure according to the second configuration information.

[0197] Please refer to Figure 13 , Figure 13 Another flowchart of a method for determining whether to trigger continuous LBT failure is provided in the embodiments of the present disclosure, and the method is performed by a network device. As shown in Figure 13 , the method can include but is not limited to the following steps:

[0198] Step 1301: sending third configuration information to a terminal device, wherein the third configuration information is used by the terminal device to determine the maximum number of LBT failures and the LBT failure detection timer.

[0199] In the present disclosure, the network device can send the third configuration information to the terminal device to configure the terminal device with the LBT failure detection timer used when counting the number of LBT failures of the BWP, and configure the terminal device with the maximum number of LBT failures used when determining whether the BWP triggers continuous LBT failure.

[0200] Optionally, the third configuration information can be dedicated RRC signaling or SIB system message.

[0201] Optionally, the third configuration information includes any of the following: the maximum number of LBT failures and the LBT failure detection timer corresponding to the BWP; the maximum number of LBT failures and the LBT failure detection timer corresponding to the unlicensed frequency band; and the maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device.

[0202] For example, the network device configures the terminal device with the maximum number of LBT failures and the LBT failure detection timer corresponding to the BWP, and the terminal device can use the LBT failure detection timer corresponding to the BWP when counting the number of LBT failures of the BWP, and can use the maximum number of LBT failures corresponding to the BWP when determining whether the BWP triggers continuous LBT failures.

[0203] For another example, the network device configures the terminal device with the maximum number of LBT failures and the LBT failure detection timer corresponding to the unlicensed frequency band to which the BWP belongs, and the terminal device can use the LBT failure detection timer corresponding to the unlicensed frequency band to which the BWP belongs when counting the number of LBT failures of the BWP, and can use the maximum number of LBT failures corresponding to the unlicensed frequency band to which the BWP belongs when determining whether the BWP triggers continuous LBT failures.

[0204] For another example, the network device configures the terminal device with the maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device, and the terminal device can use the LBT failure detection timer corresponding to the terminal device when counting the number of LBT failures of the BWP, and can use the maximum number of LBT failures corresponding to the terminal device when determining whether the BWP triggers continuous LBT failures.

[0205] In the embodiments of the present disclosure, the network device can send the third configuration information to the terminal device, and configure the terminal device with the LBT failure detection timer used when counting the number of LBT failures of the BWP and the maximum number of LBT failures used when determining whether the BWP triggers continuous LBT failures through the third configuration information. Therefore, the terminal device can count the number of LBT failures of the BWP and determine whether the BWP triggers continuous LBT failures according to the third configuration information.

[0206] Please refer to Figure 14 , Figure 14 A structural schematic diagram of a communication apparatus 1400 provided by the embodiments of the present disclosure is shown. Figure 14The illustrated communication apparatus 1400 can include a processing module 1401 and a transceiver module 1402. The transceiver module 1402 can include a sending module for implementing a sending function and / or a receiving module for implementing a receiving function, and the transceiver module 1402 can implement the sending function and / or the receiving function.

[0207] It can be understood that the communication apparatus 1400 can be a terminal device, can be an apparatus in a terminal device, and can also be an apparatus that can be used in matching with a terminal device.

[0208] The communication apparatus 1400 is at the terminal device side, wherein:

[0209] The processing module 1401 is configured to count the number of LBT failures on the sidelink when transmitting sidelink data on an unlicensed frequency band; and determine that continuous LBT failure is triggered in a case where the number of LBT failures is greater than or equal to a maximum number of LBT failures.

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

[0211] When transmitting sidelink data by using resources in a resource pool, the processing module 1401 is configured to count the number of LBT failures on one or more of a physical sidelink control channel (PSSCH), a physical sidelink shared channel (PSCCH), and a physical sidelink feedback channel (PSFCH) associated with the resource pool by using an LBT failure detection timer.

[0212] The processing module 1401 is configured to determine the number of LBT failures of the resource pool according to the number of LBT failures on the one or more of the PSSCH, the PSCCH, and the PSFCH.

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

[0214] When receiving an LBT failure indication delivered by a physical layer, the processing module 1401 is configured to start or restart the LBT failure detection timer and add 1 to a LBT failure number counter corresponding to the resource pool.

[0215] During running of the LBT failure detection timer, if no LBT failure indication is received, the processing module 1401 is configured to reset the LBT failure number counter corresponding to the resource pool to 0.

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

[0217] In a case where the number of LBT failures of the resource pool is greater than or equal to the maximum number of LBT failures, the processing module 1401 is configured to determine that the resource pool triggers continuous LBT failure.

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

[0219] In a case where it is determined that the resource pool triggers continuous LBT failure, any one of the following operations is performed:

[0220] Release all PC5-RRC connections associated with the terminal device based on the PC5 interface;

[0221] Release all PC5-RRC connections associated with the terminal device using resource pool resources;

[0222] Release only PC5-RRC connections associated with the terminal device using resource pool resources.

[0223] Optionally, the apparatus described above can further include:

[0224] The transceiver module 1402 is configured to receive the first configuration information sent by the network device;

[0225] The processing module 1401 is configured to determine the maximum number of LBT failures and the LBT failure detection timer according to the first configuration information.

[0226] Optionally, the first configuration information is any one of the following:

[0227] Dedicated RRC signaling;

[0228] System information block (SIB) system message.

[0229] Optionally, the first configuration information includes any one of the following:

[0230] The maximum number of LBT failures and the LBT failure detection timer corresponding to the resource pool;

[0231] The maximum number of LBT failures and the LBT failure detection timer corresponding to the bandwidth (BWP) to which the resource pool belongs;

[0232] The maximum number of LBT failures and the LBT failure detection timer corresponding to the unlicensed frequency band;

[0233] The maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device.

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

[0235] For a source address and a target address pair, use the LBT failure detection timer to count the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH associated with the source address and the target address pair;

[0236] Determine the number of LBT failures of the source address and the target address pair according to the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH.

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

[0238] start or restart the LBT failure detection timer and increase the LBT failure number counter corresponding to the source address and target address pair by 1 upon receiving the LBT failure indication submitted by the physical layer;

[0239] reset the LBT failure number counter corresponding to the source address and target address pair to 0 if no LBT failure indication is received during the running of the LBT failure detection timer.

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

[0241] determine that the source address and target address pair triggers continuous LBT failure if the LBT failure number of the source address and target address pair is greater than or equal to the maximum LBT failure number.

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

[0243] perform any one of the following operations if it is determined that the source address and target address pair triggers continuous LBT failure:

[0244] release the PC5-RRC connection associated with the source address and target address pair;

[0245] determine that the broadcast service or the anchor service associated with the target address triggers continuous LBT failure.

[0246] Optionally, the apparatus can further include:

[0247] the transceiver module 1402 is configured to receive the second configuration information sent by the network device;

[0248] the processing module 1401 is configured to determine the maximum LBT failure number and the LBT failure detection timer according to the second configuration information.

[0249] Optionally, the second configuration information is any one of the following:

[0250] dedicated RRC signaling;

[0251] SIB system message.

[0252] Optionally, the second configuration information includes any one of the following:

[0253] the maximum LBT failure number and the LBT failure detection timer corresponding to the target address;

[0254] the maximum LBT failure number and the LBT failure detection timer corresponding to the terminal device.

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

[0256] In a case that the terminal device activates all the resource pools of the BWP to send the sidelink data, the LBT failure detection timer is utilized to count the number of LBT failures on one or more of the PSSCH, PSCCH and PSFCH associated with all the resource pools of the BWP.

[0257] The number of LBT failures of the BWP is determined according to the number of LBT failures on one or more of the PSSCH, PSCCH and PSFCH.

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

[0259] In a case that the LBT failure indication is received from the physical layer, the LBT failure detection timer is started or restarted, and the number of LBT failures corresponding to the BWP is counted by 1.

[0260] In a case that the LBT failure indication is not received during the running of the LBT failure detection timer, the number of LBT failures corresponding to the BWP is reset to 0.

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

[0262] In a case that the number of LBT failures of the BWP is greater than or equal to the maximum number of LBT failures, it is determined that the BWP triggers the continuous LBT failure.

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

[0264] In a case that it is determined that the BWP triggers the continuous LBT failure, any one of the following operations is performed:

[0265] Release all the PC5-RRC connections associated with the terminal device;

[0266] Release all the PC5-RRC connections associated with the terminal device and using the resource pool of the BWP.

[0267] Optionally, the apparatus can further include:

[0268] The transceiver module 1402 is configured to receive the third configuration information sent by the network device.

[0269] The processing module is configured to determine the maximum number of LBT failures and the LBT failure detection timer according to the third configuration information.

[0270] Optionally, the third configuration information is any one of the following:

[0271] Dedicated RRC signaling;

[0272] SIB system message.

[0273] Optionally, the third configuration information includes any of the following:

[0274] a maximum number of LBT failures corresponding to the BWP and an LBT failure detection timer;

[0275] a maximum number of LBT failures corresponding to the unlicensed frequency band and an LBT failure detection timer;

[0276] a maximum number of LBT failures corresponding to the terminal device and an LBT failure detection timer.

[0277] Optionally, the apparatus can further include:

[0278] The transceiver module 1402 is configured to receive indication information sent by the network device, wherein the indication information is used to instruct the terminal device to count the number of LBT failures on the sidelink according to a specified counting manner.

[0279] Optionally, the indication information includes any of the following:

[0280] instructing the terminal device to count the number of LBT failures on the sidelink according to a resource pool granularity;

[0281] instructing the terminal device to count the number of LBT failures on the sidelink according to a source address and target address granularity;

[0282] instructing the terminal device to count the number of LBT failures on the sidelink according to a BWP granularity.

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

[0284] in a case where the sidelink data is not successfully transmitted due to the priority of the sidelink being lower than the air interface uplink, performing any of the following operations:

[0285] counting the sidelink LBT result;

[0286] not counting the sidelink LBT result;

[0287] randomly selecting one of counting the sidelink LBT result and not counting the sidelink LBT result.

[0288] In the present disclosure, when the terminal device transmits sidelink data on the unlicensed frequency band, the terminal device counts the number of LBT failures on the sidelink, and in a case where the number of LBT failures is greater than or equal to a maximum number of LBT failures, determines to trigger continuous LBT failure. In this way, counting the number of LBT failures and determining whether to trigger continuous LBT failure can be realized when sidelink communication is performed using the unlicensed frequency band.

[0289] It can be understood that the communication apparatus 1400 can be a network device, a device in a network device, or a device capable of being used with a network device.

[0290] The communication apparatus 1400 is at the network device side, wherein:

[0291] The transceiver module 1402 is configured to send indication information to the terminal device, wherein the indication information is used to instruct the terminal device to count the number of LBT failures on the sidelink according to a specified counting manner when the terminal device sends sidelink data on an unlicensed frequency band.

[0292] Optionally, the indication information includes any of the following:

[0293] The terminal device is instructed to count the number of LBT failures on the sidelink according to a resource pool granularity;

[0294] The terminal device is instructed to count the number of LBT failures on the sidelink according to a source address and a target address granularity;

[0295] The terminal device is instructed to count the number of LBT failures on the sidelink according to a BWP granularity.

[0296] Optionally, the transceiver module 1402 is further configured to:

[0297] Send first configuration information to the terminal device, wherein the first configuration information is used for the terminal device to determine the maximum number of LBT failures and an LBT failure detection timer, the LBT failure detection timer is used to count the number of LBT failures of a resource pool, and the maximum number of LBT failures is used to determine whether the resource pool triggers continuous LBT failures.

[0298] Optionally, the first configuration information includes any of the following:

[0299] The maximum number of LBT failures and the LBT failure detection timer corresponding to the resource pool;

[0300] The maximum number of LBT failures and the LBT failure detection timer corresponding to the bandwidth BWP to which the resource pool belongs;

[0301] The maximum number of LBT failures and the LBT failure detection timer corresponding to the unlicensed frequency band;

[0302] The maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device.

[0303] Optionally, the transceiver module 1402 is further configured to:

[0304] The second configuration information is used for the terminal device to determine the maximum number of LBT failures and an LBT failure detection timer, and the LBT failure detection timer is used for counting the number of LBT failures of the source address and the target address pair, and the maximum number of LBT failures is used for determining whether the source address and the target address pair trigger continuous LBT failures.

[0305] Optionally, the second configuration information includes any of the following:

[0306] the maximum number of LBT failures and the LBT failure detection timer corresponding to the target address;

[0307] the maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device.

[0308] Optionally, the transceiver module 1402 is further configured to:

[0309] The third configuration information is used for the terminal device to determine the maximum number of LBT failures and an LBT failure detection timer, and the LBT failure detection timer is used for counting the number of LBT failures of the activated BWP, and the maximum number of LBT failures is used for determining whether the BWP triggers continuous LBT failures.

[0310] Optionally, the third configuration information includes any of the following:

[0311] the maximum number of LBT failures and the LBT failure detection timer corresponding to the BWP;

[0312] the maximum number of LBT failures and the LBT failure detection timer corresponding to the unlicensed frequency band;

[0313] the maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device.

[0314] In the present disclosure, the network device can send indication information to the terminal device, wherein the indication information is used to instruct the terminal device to count the number of LBT failures on the sidelink according to a specified counting manner when the terminal device sends sidelink data on the unlicensed frequency band. Therefore, the network device can instruct the terminal device to count the number of LBT failures on the sidelink according to the specified manner, so that the terminal device can count the number of LBT failures on the sidelink according to the specified manner in the indication information, and realize the counting of the number of LBT failures on the sidelink and how to determine whether to trigger continuous LBT failures.

[0315] Please refer to Figure 15 , Figure 15This is a schematic diagram of another communication device 1500 provided in an embodiment of this disclosure. The communication device 1500 can be a network device, a terminal device, a chip, chip system, or processor that supports the implementation of the above methods in a network device, or a chip, chip system, or processor that supports the implementation of the above methods in a terminal device. This device can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0316] The communication device 1500 may include one or more processors 1501. The processor 1501 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal equipment, terminal equipment chip, DU or CU, etc.), execute computer programs, and process data from the computer programs.

[0317] 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 methods described in the above method embodiments. Optionally, the memory 1502 may also store data. The communication device 1500 and the memory 1502 may be provided separately or integrated together.

[0318] Optionally, the communication device 1500 may also include a transceiver 1505 and an antenna 1506. The transceiver 1505 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 1505 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0319] Optionally, the communication device 1500 may further include one or more interface circuits 1507. The interface circuits 1507 are used to receive code instructions and transmit them to the processor 1501. The processor 1501 executes the code instructions to cause the communication device 1500 to perform the methods described in the above method embodiments.

[0320] Communication device 1500 is a terminal device: processor 1501 is used to execute... Figure 2 Steps 201-202 in the process; Figure 3 Steps 301-303 in the process; Figure 4 Steps 401-404 in the text; Figure 5 Steps 501-503 in the text; Figure 6 Steps 601-604 in the text;Figure 7 steps 701-703 in method 700; Figure 8 steps 801-804 in method 800; Figure 9 steps 902-903 in method 900; etc.

[0321] The communication apparatus 1500 is a network device: the transceiver 1505 is configured to perform Figure 10 step 1001 in method 1000; Figure 11 step 1101 in method 1100; Figure 12 step 1201 in method 1200; Figure 13 step 1301 in method 1300.

[0322] In an implementation, the processor 1501 can include a transceiver for implementing the receiving and sending functions. For example, the transceiver can be a transceiver circuit, or an interface, or an interface circuit. The transceiver circuit, interface or interface circuit for implementing the receiving and sending functions can be separate, or integrated together. The transceiver circuit, interface or interface circuit described above can be used for reading and writing of code / data, or the transceiver circuit, interface or interface circuit described above can be used for transmission or transfer of signals.

[0323] In an implementation, the processor 1501 can store a computer program 1503, which, when running on the processor 1501, can cause the communication apparatus 1500 to perform the methods described in the above method embodiments. The computer program 1503 can be fixed in the processor 1501, in which case the processor 1501 can be implemented by hardware.

[0324] In an implementation, the communication apparatus 1500 can include circuitry that can implement the functions of transmitting or receiving or communicating in the foregoing method embodiments. The processor and the 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 the transceiver can also be manufactured with various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), positive channel metal oxide semiconductor (PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0325] The communication apparatus described in the above embodiments can be a network device, or a terminal device, but the scope of the communication apparatus described in the present disclosure is not limited thereto, and the structure of the communication apparatus can not be limited by Figure 11 The communication apparatus can be a standalone device or can be a part of a larger device. For example, the communication apparatus can be:

[0326] (1) a standalone integrated circuit (IC), or a chip, or a chip system or subsystem;

[0327] (2) a set of one or more ICs, optionally including storage for storing data, computer programs, etc.

[0328] (3) an ASIC, such as a Modem;

[0329] (4) a module that can be embedded within other devices;

[0330] (5) a receiver, a terminal device, a smart terminal device, a cellular phone, a wireless device, a handset, a mobile unit, a car device, a network device, a cloud device, an artificial intelligence device, etc.

[0331] (6) other, etc.

[0332] For the case that the communication device can be a chip or a chip system, refer to Figure 16 The chip shown in the structural diagram. Figure 16 The chip shown includes a processor 1601 and an interface 1603. Among them, the number of processors 1601 can be one or more, and the number of interfaces 163 can be multiple.

[0333] For the case that the chip is used to implement the function of the terminal device in the embodiments of the disclosure:

[0334] The interface 1603 is configured to perform steps 9019 and the like in Figure 9

[0335] For the case that the chip is used to implement the function of the network device in the embodiments of the disclosure:

[0336] The interface 1603 is configured to perform steps 1001 in Figure 10 Figure 11 Steps 1101 in Figure 12 Steps 1201 in Figure 13 Steps 1301 in

[0337] Optionally, the chip further includes a memory 1603, and the memory 1603 is configured to store necessary computer programs and data.

[0338] Those skilled in the art can also understand that the various illustrative logical blocks and steps listed in the embodiments of the disclosure can be implemented by electronic hardware, computer software, or a combination of the two. Whether the function is implemented by hardware or software depends on the specific application and design requirements of the whole system. Those skilled in the art can use various methods to implement the described functions for each specific application, but such implementation should not be understood as beyond the scope of the embodiments of the disclosure.

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

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

[0341] ​​In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by 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 programs are loaded on a computer and executed, 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 devices. The computer programs can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer programs can be transferred from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode. 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, data center, etc. integrated with one or more available media. The available media can be magnetic media (such as floppy disk, hard disk, magnetic tape), optical media (such as high-density digital video disc (digital video disc, DVD)), or semiconductor media (such as solid state disk (solid state disk, SSD)) and the like.

[0342] Those skilled in the art can understand that the first, second, etc. various numerical numbers involved in the present disclosure are only for the convenience of description, and do not limit the scope of the embodiments of the present disclosure, nor represent the order of precedence.

[0343] At least one of the present disclosure can also be described as one or more, and the plurality can be two, three, four or more, which is not limited by 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". There is no order or size order between the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0344] The correspondence relationship shown in each table in the present disclosure can be configured or predefined. The values of the information in each table are merely examples, and other values can be configured, and the present disclosure is not limited. When configuring the correspondence relationship between the information and each parameter, it is not necessarily required to configure all the correspondence relationships shown in each table. For example, the correspondence relationship shown in some rows in the table in the present disclosure can also not be configured. For another example, the above table can be appropriately deformed and adjusted, for example, split, merged, etc. The name of the parameter shown in the title of each table above can also use other names understandable by the communication device, and the value or representation of the parameter can also use other values or representations understandable by the communication device. Each table above can also use other data structures when implemented, for example, an array, a queue, a container, a stack, a linear table, a pointer, a linked list, a tree, a graph, a structure, a class, a heap, a hash table, etc.

Claims

1. A method for determining the failure of triggering continuous listen-before-speak (LBT), characterized in that, The method, executed by a terminal device, includes: The terminal device receives indication information sent by a network device, wherein the indication information is used to instruct the terminal device to count the number of LBT failures on the sidelink according to a specified counting method, and the indication information includes at least one of the following: instructing the terminal device to count the number of LBT failures on the sidelink at the resource pool granularity; instructing the terminal device to count the number of LBT failures on the sidelink at the source address and destination address granularity; instructing the terminal device to count the number of LBT failures on the sidelink at the BWP granularity; When transmitting sidelink data on unlicensed frequency bands, the number of LBT failures on the sidelink is counted according to a specified counting method; If the number of LBT failures is greater than or equal to the maximum number of LBT failures, a continuous LBT failure is determined to be triggered.

2. The method as described in claim 1, characterized in that, The counting of LBT failures on the side link according to the specified counting method includes: When transmitting side-link data using resources in the resource pool, an LBT failure detection timer is used to count the number of LBT failures on one or more of the physical side-link control channel PSSCH, physical side-link shared channel PSCCH, and physical side-link feedback channel PSFCH associated with the resource pool. The number of LBT failures of the resource pool is determined based on the number of LBT failures on one or more channels of the PSSCH, PSCCH, and PSFCH.

3. The method as described in claim 2, characterized in that, The method of using an LBT failure detection timer to count the number of LBT failures on one or more of the following channels associated with the resource pool: Physical-side Link Control Channel (PSSCH), Physical-side Link Shared Channel (PSCCH), and Physical-side Link Feedback Channel (PSFCH) includes: Upon receiving an LBT failure indication from the physical layer, start or restart the LBT failure detection timer and increment the LBT failure count counter corresponding to the resource pool by 1; If no LBT failure indication is received during the operation of the LBT failure detection timer, the LBT failure count counter corresponding to the resource pool is reset to 0.

4. The method as described in claim 2, characterized in that, The determination of triggering continuous LBT failures includes: If the number of LBT failures in the resource pool is greater than or equal to the maximum number of LBT failures, it is determined that the resource pool has triggered continuous LBT failures.

5. The method as described in claim 4, characterized in that, Also includes: In the event that the resource pool has triggered consecutive LBT failures, perform any of the following operations: Release all PC5-RRC (Radio Resource Control) connections associated with the terminal device based on the PC5 interface; Release all PC5-RRC connections associated with the terminal device that use the resources of the resource pool; Release the PC5-RRC connection associated with the terminal device that only uses the resources of the resource pool.

6. The method as described in claim 2, characterized in that, The method further includes: Receive the first configuration information sent by the network device; Based on the first configuration information, determine the maximum number of LBT failures and the LBT failure detection timer.

7. The method as described in claim 6, characterized in that, The first configuration information is any one of the following: Dedicated RRC signaling; System Information Block (SIB) System Messages.

8. The method as described in claim 6, characterized in that, The first configuration information includes any one of the following: The maximum number of LBT failures and the LBT failure detection timer corresponding to the resource pool; The maximum number of LBT failures and the LBT failure detection timer corresponding to the bandwidth BWP to which the resource pool belongs; The maximum number of LBT failures and the LBT failure detection timer corresponding to the unlicensed frequency band; The maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device.

9. The method as described in claim 1, characterized in that, The counting of LBT failures on the side link according to the specified counting method includes: For a source address and a destination address pair, an LBT failure detection timer is used to count the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH associated with the source address and destination address pair. The number of LBT failures for the source address and destination address pair is determined based on the number of LBT failures on one or more of the channels, namely PSSCH, PSCCH and PSFCH.

10. The method as described in claim 9, characterized in that, The method of using an LBT failure detection timer to count the number of LBT failures on one or more channels of PSSCH, PSCCH, and PSFCH associated with the source and destination addresses includes: Upon receiving an LBT failure indication from the physical layer, start or restart the LBT failure detection timer and increment the corresponding LBT failure count counters for the source address and destination address by 1; If no LBT failure indication is received during the operation of the LBT failure detection timer, the LBT failure count counters corresponding to the source address and destination address pairs are reset to 0.

11. The method as described in claim 9, characterized in that, The determination of triggering continuous LBT failures includes: If the number of LBT failures for the source address and destination address pair is greater than or equal to the maximum number of LBT failures, then the source address and destination address pair is determined to have triggered consecutive LBT failures.

12. The method as described in claim 11, characterized in that, Also includes: In the event that the source address and destination address pair are determined to trigger consecutive LBT failures, perform any of the following operations: Release the PC5-RRC connection associated with the source and destination address pairs; The broadcast or anchor service associated with the target address is determined to trigger continuous LBT failures.

13. The method as described in claim 9, characterized in that, The method further includes: Receive the second configuration information sent by the network device; Based on the second configuration information, determine the maximum number of LBT failures and the LBT failure detection timer.

14. The method as described in claim 13, characterized in that, The second configuration information is any one of the following: Dedicated RRC signaling; SIB system message.

15. The method as described in claim 13, characterized in that, The second configuration information includes any one of the following: The maximum number of LBT failures and the LBT failure detection timer corresponding to the target address; The maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device.

16. The method as described in claim 1, characterized in that, The counting of LBT failures on the side link according to the specified counting method includes: When activating the resource transmission side link data of all resource pools under BWP, the LBT failure detection timer is used to count the number of LBT failures on one or more channels of PSSCH, PSCCH and PSFCH associated with all resource pools under BWP. The number of LBT failures of the BWP is determined based on the number of LBT failures on one or more of the channels, namely PSSCH, PSCCH and PSFCH.

17. The method as described in claim 16, characterized in that, The method of using an LBT failure detection timer to count the number of LBT failures on one or more channels of PSSCH, PSCCH, and PSFCH associated with all resource pools under the BWP includes: Upon receiving an LBT failure indication from the physical layer, start or restart the LBT failure detection timer and increment the LBT failure count counter corresponding to the BWP by 1; If no LBT failure indication is received during the operation of the LBT failure detection timer, the LBT failure count counter corresponding to the BWP is reset to 0.

18. The method as described in claim 16, characterized in that, The determination of triggering continuous LBT failures includes: If the number of LBT failures of the BWP is greater than or equal to the maximum number of LBT failures, it is determined that the BWP has triggered continuous LBT failures.

19. The method as described in claim 18, characterized in that, Also includes: In the event that the BWP triggers a series of LBT failures, perform any of the following operations: Release all PC5-RRC connections associated with the terminal device; Release all PC5-RRC connections associated with the terminal device that use resources from the BWP resource pool.

20. The method as described in claim 16, characterized in that, The method further includes: Receive third configuration information sent by network devices; Based on the third configuration information, the maximum number of LBT failures and the LBT failure detection timer are determined.

21. The method as described in claim 20, characterized in that, The third configuration information is any one of the following: Dedicated RRC signaling; SIB system message.

22. The method as described in claim 20, characterized in that, The third configuration information includes any of the following: The maximum number of LBT failures and the LBT failure detection timer corresponding to the BWP; The maximum number of LBT failures and the LBT failure detection timer corresponding to the unlicensed frequency band; The maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device.

23. The method according to any one of claims 1-22, characterized in that, The counting of LBT failures on the side link includes: If data transmission fails because the side link has a lower priority than the air interface uplink, perform any of the following operations: Include the side-link LBT results; The side-link LBT results are not included; Choose one implementation randomly, either including the sidelink LBT results or not.

24. A method for determining the triggering of continuous LBT failures, characterized in that, Performed by a network device, the method includes: Sending instruction information to the terminal device, wherein the instruction information is used to instruct the terminal device to count the number of LBT failures on the sidelink according to a specified counting method when transmitting sidelink data on an unlicensed frequency band; The indication information includes at least one of the following: The terminal device is instructed to count the number of LBT failures on the sidelink at the resource pool granularity. The terminal device is instructed to count the number of LBT failures on the granular cross link according to the source address and the destination address; The terminal device is instructed to count the number of LBT failures on the side link at the BWP granularity.

25. The method as described in claim 24, characterized in that, The method further includes: Send first configuration information to the terminal device, wherein the first configuration information is used by the terminal device to determine the maximum number of LBT failures and the LBT failure detection timer, the LBT failure detection timer is used to count the number of LBT failures in the resource pool, and the maximum number of LBT failures is used to determine whether the resource pool has triggered continuous LBT failures.

26. The method as described in claim 25, characterized in that, The first configuration information includes any one of the following: The maximum number of LBT failures and the LBT failure detection timer corresponding to the resource pool; The maximum number of LBT failures and the LBT failure detection timer corresponding to the bandwidth BWP to which the resource pool belongs; The maximum number of LBT failures and the LBT failure detection timer corresponding to the unlicensed frequency band; The maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device.

27. The method as described in claim 24, characterized in that, The method further includes: Send second configuration information to the terminal device, wherein the second configuration information is used by the terminal device to determine the maximum number of LBT failures and the LBT failure detection timer, the LBT failure detection timer is used to count the number of LBT failures of the source address and target address pair, and the maximum number of LBT failures is used to determine whether the source address and target address pair triggers continuous LBT failures.

28. The method as described in claim 27, characterized in that, The second configuration information includes any one of the following: The maximum number of LBT failures and the LBT failure detection timer corresponding to the target address; The maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device.

29. The method as described in claim 24, characterized in that, The method further includes: The terminal device is sent third configuration information, wherein the third configuration information is used by the terminal device to determine the maximum number of LBT failures and the LBT failure detection timer, the LBT failure detection timer is used to count the number of LBT failures when BWP is activated, and the maximum number of LBT failures is used to determine whether BWP triggers continuous LBT failures.

30. The method as described in claim 29, characterized in that, The third configuration information includes any of the following: The maximum number of LBT failures and the LBT failure detection timer corresponding to the BWP; The maximum number of LBT failures and the LBT failure detection timer corresponding to the unlicensed frequency band; The maximum number of LBT failures and the LBT failure detection timer corresponding to the terminal device.

31. A communication device, characterized in that, include: A processing module is configured to receive indication information sent by a network device, wherein the indication information is used to instruct the communication device to count the number of LBT failures on the sidelink according to a specified counting method, and the indication information includes at least one of the following: instructing the communication device to count the number of LBT failures on the sidelink at the resource pool granularity; instructing the communication device to count the number of LBT failures on the sidelink at the source address and destination address granularity; instructing the communication device to count the number of LBT failures on the sidelink at the BWP granularity; when transmitting sidelink data on an unlicensed frequency band, counting the number of LBT failures on the sidelink according to the specified counting method; and determining to trigger continuous LBT failures when the number of LBT failures is greater than or equal to the maximum number of LBT failures.

32. A communication device, characterized in that, include: The transceiver module is used to send indication information to the terminal device, wherein the indication information is used to instruct the terminal device to count the number of LBT failures on the sidelink according to a specified counting method when transmitting sidelink data on an unlicensed frequency band. The indication information includes at least one of the following: The terminal device is instructed to count the number of LBT failures on the sidelink at the resource pool granularity. The terminal device is instructed to count the number of LBT failures on the granular cross link according to the source address and the destination address; The terminal device is instructed to count the number of LBT failures on the side link at the BWP granularity.

33. A communication device, characterized in that, The device includes a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method as claimed in any one of claims 1 to 23, or to perform the method as claimed in any one of claims 24 to 30.

34. A computer-readable storage medium for storing instructions that, when executed, cause the method of any one of claims 1 to 23 to be implemented, or cause the method of any one of claims 24 to 30 to be implemented.

Images