WO2025007652A1 - Resource determination method and apparatus, and readable storage medium - Google Patents

Abstract

The embodiments of the present application relate to the technical field of communications. Provided are a resource determination method and apparatus, and a readable storage medium. The resource determination method comprises: determining that consecutive LBT failures of a first resource of a terminal device are triggered, and a first state of the first resource of the terminal device is triggered, wherein the first state indicates that a sidelink (SL) resource corresponding to the first resource is unavailable; sending indication information to a network device, wherein the indication information is used for indicating that the terminal device detects the consecutive LBT failures; canceling the consecutive LBT failures of the first resource; and if a first condition is met, canceling the first state of the first resource. In the method, by means of the first condition, the first resource is prevented from becoming available immediately after the first resource triggers the consecutive LBT failures, and the terminal device is prevented from immediately re-selecting the first resource for SL transmission, thereby improving the success rate of LBT performed by the terminal device, and ensuring the timely transmission of SL data.

Description

Resource determination method, device and readable storage medium

This application claims the priority of the Chinese patent application filed with the State Intellectual Property Office on July 4, 2023, with application number 202310815963.6 and application name “A method and device for recovering continuous failure of listening before speaking”, and claims the priority of the Chinese patent application filed with the State Intellectual Property Office on August 7, 2023, with application number 202310993354.X and application name “Resource determination method, device and readable storage medium”, and claims the priority of the Chinese patent application filed with the State Intellectual Property Office on December 22, 2023, with application number 202311792556.4 and application name “Resource determination method, device and readable storage medium”, the entire contents of which are incorporated by reference into this application.

Technical Field

The embodiments of the present application relate to the field of communication technology, and in particular, to a resource determination method, device, and readable storage medium.

Background Art

With the development of communication technology, a sidelink (SL) communication standard has been developed for direct communication between terminal devices.

Sidelink communications can use both licensed and unlicensed spectrum. In order to use unlicensed spectrum fairly, the terminal device needs to perform a listen before talk (LBT) process, i.e., a channel access process, before sending sidelink data. If LBT succeeds, the sidelink resources can be used for sidelink transmission. If LBT fails, the sidelink resources cannot be used for sidelink transmission. When a channel is busy, LBT may fail continuously, which is called continuous LBT failure.

There are two sidelink resource selection modes for sidelink communication. In resource selection mode 1, the network device selects sidelink resources in the resource pool for the transmitting terminal device. In resource selection mode 2, the transmitting terminal device selects sidelink resources in the resource pool by itself. For a terminal device in a connected state and using resource selection mode 2, if continuous LBT failures are detected on a sidelink resource, the network device needs to be notified, and another sidelink resource can be selected to continue trying the LBT process for data transmission on the sidelink.

With the current processing mechanism, when a terminal device selects another side link resource to continue the LBT process, it may select a side link resource that has just failed in a continuous LBT process, which increases the probability of LBT failure and causes the side link data to be unable to be transmitted in a timely manner.

Summary of the invention

The present application provides a resource determination method, device and readable storage medium, which improve the success rate of LBT of terminal equipment and ensure the timely transmission of SL data.

In a first aspect, the present application provides a resource determination method, comprising: determining that a continuous LBT failure of a first resource of a terminal device is triggered, and a first state of the first resource of the terminal device is triggered; wherein the first state is that a side link resource corresponding to the first resource is unavailable; sending an indication message to a network device, the indication message being used to indicate that the terminal device has detected a continuous LBT failure; canceling the continuous LBT failure of the first resource; and if the first condition is met, canceling the first state of the first resource.

In this manner, the resource determination method is applicable to a scenario in which a connected terminal device (referred to as UE) uses unlicensed spectrum and resource selection mode 2 for SL communication. The UE determines that the continuous LBT failure of the first resource is triggered, and the first state of the first resource is triggered, and the first state is that the side link resource corresponding to the first resource is unavailable. If the continuous LBT failure of the UE's first resource is triggered, the UE sends an indication message to the network device. The UE sends an indication message to the network device, and the UE cancels the continuous LBT failure of the first resource. Thus, the UE will no longer report the indication message, saving signaling overhead. If the first state of the UE's first resource is triggered and the first condition is met, the UE cancels the first state of the first resource. Through the first condition, it is avoided that the first resource becomes available immediately after the first resource triggers the continuous LBT failure, and it is avoided that the UE immediately reselects the first resource for SL transmission, thereby improving the success rate of the UE's LBT and ensuring SL communication.

In one possible design, a first state of a first resource of a terminal device is triggered, including: the first resource of the terminal device is in a first state.

In this manner, the first state may be understood as an event or a state, when the event or the state is triggered, the SL resources corresponding to the first resources of the UE are unselectable or unavailable.

In one possible design, a first state of a first resource of a terminal device is triggered, including: setting the first resource to a first state.

In this manner, the first state is related information of the first resource, and the first state is used to indicate that the SL resource corresponding to the first resource is unavailable.

In one possible design, canceling the first state of the first resource includes: the first resource of the terminal device is not in the first state, the first resource of the terminal device is in the second state, and the second state is that the side link resource corresponding to the first resource is available.

In this manner, the first state and the second state may be understood as an event or a state, and the SL resources corresponding to the first resources of the UE are selectable or available.

In one possible design, canceling the first state of the first resource includes: setting the first resource to a second state, where the second state is that a side link resource corresponding to the first resource is available.

In this manner, the second state is related information of the first resource, and the second state is used to indicate that the SL resource corresponding to the first resource is available.

In one possible design, the first condition includes at least one of the following: a transmission is successfully completed using the sidelink resource on the second resource; a first time period elapses after the first state of the first resource is triggered; a first timer times out, and the first timer is started when the first state of the first resource is triggered; the sidelink channel quality satisfies a channel quality condition; and a sidelink channel busy state satisfies a channel busy condition.

In this method, since it takes a certain amount of time to meet the first condition, it ensures that the first resource will not become available again immediately after the failure of triggering continuous LBT, avoiding the UE from immediately reselecting the first resource for SL transmission, thereby improving the success rate of UE performing LBT. Moreover, there are multiple first conditions, which are more flexible.

In one possible design, it is determined that continuous LBT failures of a first resource of a terminal device are triggered, and a first state of the first resource of the terminal device is triggered, including: if the second condition is met, it is determined that continuous LBT failures of the first resource of the terminal device are triggered, and the first state of the first resource of the terminal device is triggered; or, if the second condition is met, it is determined that continuous LBT failures of the first resource of the terminal device are triggered, and if the third condition is met, it is determined that the first state of the first resource of the terminal device is triggered; wherein the second condition is: the cumulative number of LBT failures corresponding to the first resource is equal to or greater than the maximum number of LBT failures; the third condition is: continuous LBT failures are detected in the first resource, or the first resource triggers continuous LBT failures.

In this manner, through the second condition and the third condition, the condition for determining that the first state of the first resource of the UE is triggered is more flexible.

In one possible design, the indication information indicates that at least one first resource detects consecutive LBT failures.

In one possible design, canceling the continuous LBT failure of the first resource includes: canceling the continuous LBT failure of the first resource indicated by the indication information.

In a second aspect, the present application provides a resource determination method, including: if a continuous LBT failure of a first resource of a terminal device is triggered, the terminal device sends an indication message to a network device, the indication message is used to indicate that the terminal device has detected a continuous LBT failure, and the terminal device cancels the continuous LBT failure of the first resource; if a first state of a first resource of the terminal device is triggered and a first condition is met, the terminal device cancels the first state of the first resource; wherein the first state is that a side link resource corresponding to the first resource is unavailable.

In this manner, the resource determination method is applicable to the scenario where a connected UE uses unlicensed spectrum and resource selection mode 2 for SL communication. If the continuous LBT failure of the UE's first resource is triggered, the UE sends an indication message to the network device. The UE sends an indication message to the network device, and the UE cancels the continuous LBT failure of the first resource. As a result, the UE will no longer report the indication message, saving signaling overhead. If the first state of the UE's first resource is triggered and the first condition is met, the UE cancels the first state of the first resource. The first condition prevents the first resource from becoming available immediately after the first resource triggers a continuous LBT failure, prevents the UE from immediately reselecting the first resource for SL transmission, improves the success rate of the UE's LBT, and ensures SL communication.

In one possible design, a first state of a first resource of a terminal device is triggered, including: the first resource of the terminal device is in a first state.

In one possible design, a first state of a first resource of a terminal device is triggered, including: setting the first resource to a first state.

In one possible design, canceling the first state of the first resource includes: the first resource of the terminal device is not in the first state, the first resource of the terminal device is in the second state, and the second state is that the side link resource corresponding to the first resource is available.

In one possible design, canceling the first state of the first resource includes: setting the first resource to a second state, where the second state is that a side link resource corresponding to the first resource is available.

In one possible design, the first condition includes at least one of the following: a transmission is successfully completed using the sidelink resource on the second resource; a first time period elapses after the first state of the first resource is triggered; a first timer times out, and the first timer is started when the first state of the first resource is triggered; the sidelink channel quality satisfies a channel quality condition; and a sidelink channel busy state satisfies a channel busy condition.

In one possible design, determining that a continuous LBT failure of a first resource of a terminal device is triggered and a first state of the first resource of the terminal device is triggered includes: if a second condition is met, determining that a continuous LBT failure of the first resource of the terminal device is triggered and a first state of the first resource of the terminal device is triggered; or, if the second condition is met, determining that a continuous LBT failure of the first resource of the terminal device is triggered Trigger, if the third condition is met, it is determined that the first state of the first resource of the terminal device is triggered; wherein the second condition is: the cumulative number of LBT failures corresponding to the first resource is equal to or greater than the maximum number of LBT failures; the third condition is: continuous LBT failures are detected in the first resource, or the first resource triggers continuous LBT failures.

In one possible design, the indication information indicates that at least one first resource detects consecutive LBT failures.

In one possible design, canceling the continuous LBT failure of the first resource includes: canceling the continuous LBT failure of the first resource indicated by the indication information.

In a third aspect, the present application provides a resource determination method, including: determining that a continuous LBT failure of a first resource of a terminal device is triggered and a third state of the terminal device is triggered; if a first condition is met, canceling the continuous LBT failure of the first resource; sending an indication message to a network device, the indication message being used to indicate that the terminal device has detected a continuous LBT failure; and canceling the third state of the terminal device.

In this manner, the resource determination method is applicable to the scenario where a connected UE uses unlicensed spectrum and resource selection mode 2 for SL communication. The UE determines that the continuous LBT failure of the first resource is triggered and the third state of the terminal device is triggered. If the continuous LBT failure of the first resource of the UE is triggered and meets the first condition, the continuous LBT failure of the first resource is canceled. Through the first condition, the first resource becomes an available resource only after a period of time has passed after the continuous LBT failure is triggered, which improves the success rate of the UE's LBT and ensures SL communication. If the third state of the UE is triggered, the UE sends an indication message to the network device, and the UE sends the indication message to the network device, the third state of the UE is canceled, so that the UE will no longer report the indication information, saving signaling overhead.

In one possible design, the third state is continuous LBT failure reporting.

In this method, the third state may be expressed in other ways, for example, the third state is continuous LBT failure reporting.

In one possible design, the third state of the terminal device is the third state of a first resource of the terminal device, or the third state of the terminal device is the third state of a first resource of at least one first resource of the terminal device.

In this method, the third state is associated with a resource. If a resource meets the second condition or the third condition, the third state of the resource is triggered.

In one possible design, the third state of the terminal device is the third state of at least one first resource of the terminal device, or the third state of the terminal device is the third state of all first resources of the at least one first resource of the terminal device.

In this manner, the third state is shared by at least one first resource that triggers continuous LBT failure, or in other words, the third state is shared by all resources that trigger continuous LBT failure. If at least one resource meets the second condition or the third condition, the third state of the UE is triggered.

In one possible design, the resource determination method also includes: if the third state of the terminal device is canceled, setting the cumulative number of LBT failures of the first resource to 0.

In this manner, the cumulative number of LBT failures of the first resource is set to 0, which is used to subsequently detect whether continuous LBT failures are triggered on the first resource.

In one possible design, the first condition includes at least one of the following: a transmission is successfully completed using the sidelink resource on the second resource; a first time period elapses after the first state of the first resource is triggered; a first timer times out, and the first timer is started when the first state of the first resource is triggered; the sidelink channel quality satisfies a channel quality condition; and a sidelink channel busy state satisfies a channel busy condition.

In this method, since it takes a certain amount of time to meet the first condition, it ensures that the first resource will not become available again immediately after the failure of triggering continuous LBT, avoiding the UE from immediately reselecting the first resource for SL transmission, thereby improving the success rate of UE performing LBT. Moreover, there are multiple first conditions, which are more flexible.

In one possible design, it is determined that continuous LBT failures of a first resource of a terminal device are triggered, and a third state of the terminal device is triggered, including: if the second condition is met, it is determined that continuous LBT failures of the first resource of the terminal device are triggered, and the third state of the terminal device is triggered; or, if the second condition is met, it is determined that continuous LBT failures of the first resource of the terminal device are triggered, and if the third condition is met, it is determined that the third state of the terminal device is triggered; wherein the second condition is: the cumulative number of LBT failures corresponding to the first resource is equal to or greater than the maximum number of LBT failures; the third condition is: continuous LBT failures are detected in the first resource, or the first resource triggers continuous LBT failures.

In this manner, through the second condition and the third condition, the condition for determining that the third state of the UE is triggered is more flexible.

In one possible design, the indication information indicates that at least one first resource detects consecutive LBT failures.

In one possible design, when the third state of the terminal device is the third state of the first resource of the terminal device, canceling the third state sent by the terminal device includes: canceling the third state of the first resource indicated by the indication information.

In this manner, the third state is associated with a resource. When the UE sends indication information to the network device, the UE cancels the third state of the first resource indicated by the indication information.

In one possible design, consecutive LBT failures are used to indicate that the side link resources corresponding to the first resources are unavailable.

In this manner, if continuous LBT failures of the first resource are triggered and not cancelled, the SL resource corresponding to the first resource is unavailable.

In a fourth aspect, the present application provides a resource determination method, including: if a continuous LBT failure of a first resource of a terminal device is triggered and a first condition is met, the terminal device cancels the continuous LBT failure of the first resource; wherein the continuous LBT failure is used to indicate that a side link resource corresponding to the first resource is unavailable; if the third state of the terminal device is triggered, the terminal device sends an indication message to the network device, the indication message is used to indicate that the terminal device has detected a continuous LBT failure, and the terminal device cancels the third state of the terminal device.

In this manner, the resource determination method is applicable to the scenario where a connected UE uses unlicensed spectrum and resource selection mode 2 for SL communication. If the continuous LBT failure of the UE's first resource is triggered and meets the first condition, the continuous LBT failure of the first resource is canceled. Through the first condition, the first resource becomes an available resource only after a period of time has passed after the continuous LBT failure is triggered, which improves the success rate of the UE's LBT and ensures SL communication. If the UE's third state is triggered, the UE sends an indication message to the network device, and the UE sends an indication message to the network device, the UE's third state is canceled, so that the UE will no longer report the indication message, saving signaling overhead.

In one possible design, the third state is continuous LBT failure reporting.

In one possible design, the third state of the terminal device is the third state of a first resource of the terminal device, or the third state of the terminal device is the third state of a first resource of at least one first resource of the terminal device.

In one possible design, the third state of the terminal device is the third state of at least one first resource of the terminal device, or the third state of the terminal device is the third state of all first resources of the at least one first resource of the terminal device.

In one possible design, the resource determination method also includes: if the third state of the terminal device is canceled, setting the cumulative number of LBT failures of the first resource to 0.

In one possible design, the first condition includes at least one of the following: a transmission is successfully completed using the sidelink resource on the second resource; a first time period elapses after the first state of the first resource is triggered; a first timer times out, and the first timer is started when the first state of the first resource is triggered; the sidelink channel quality satisfies a channel quality condition; and a sidelink channel busy state satisfies a channel busy condition.

In one possible design, it is determined that continuous LBT failures of a first resource of a terminal device are triggered, and a third state of the terminal device is triggered, including: if the second condition is met, it is determined that continuous LBT failures of the first resource of the terminal device are triggered, and the third state of the terminal device is triggered; or, if the second condition is met, it is determined that continuous LBT failures of the first resource of the terminal device are triggered, and if the third condition is met, it is determined that the third state of the terminal device is triggered; wherein the second condition is: the cumulative number of LBT failures corresponding to the first resource is equal to or greater than the maximum number of LBT failures; the third condition is: continuous LBT failures are detected in the first resource, or the first resource triggers continuous LBT failures.

In one possible design, the indication information indicates that at least one first resource detects consecutive LBT failures.

In one possible design, when the third state of the terminal device is the third state of the first resource of the terminal device, canceling the third state sent by the terminal device includes: canceling the third state of the first resource indicated by the indication information.

In one possible design, consecutive LBT failures are used to indicate that the side link resources corresponding to the first resources are unavailable.

In a fifth aspect, the present application provides a resource determination method, comprising: if a first condition is met, sending an indication message to a network device, the indication message being used to indicate that a terminal device has detected continuous LBT failures; wherein the first condition comprises: the continuous LBT failure of a first resource is triggered and not canceled, and the number of first resources is greater than or equal to a preset threshold; canceling the continuous LBT failure of the first resource.

In this manner, the resource determination method is applicable to the scenario where the connected UE uses unlicensed spectrum and resource selection mode 2 for SL communication. The UE does not send indication information to the network device every time it detects continuous LBT failure on a resource, but only sends indication information to the base station when the first condition is met, thereby avoiding the first resource from becoming available immediately after triggering continuous LBT failure, avoiding the possibility that the UE may immediately reselect the first resource for SL transmission, improving the success rate of the UE performing LBT, and ensuring SL communication. Moreover, signaling overhead is also saved.

In one possible design, the resource pool where the first resource is located is a resource pool with PSFCH resources.

In this manner, the UE may be configured with a feedback-enabled logical channel or a feedback-disabled logical channel, and the UE may select the first resource in the resource pool with the PSFCH resource.

In one possible design, the terminal device is configured with a feedback-enabled logical channel.

In this method, which is applicable to the terminal device configured with a feedback-enabled logical channel, the UE can only select the first resource in the resource pool with PSFCH resources.

In one possible design, the resource pool where the first resource is located includes a resource pool with PSFCH resources and a resource pool without PSFCH resources.

In this manner, the UE may be configured with a feedback-disabled logical channel, and the UE may select a first resource in a resource pool with PSFCH resources and a resource pool without PSFCH resources.

In one possible design, the terminal device is not configured with a feedback-enabled logical channel.

In one possible design, the indication information indicates that at least one first resource detects consecutive LBT failures.

In one possible design, canceling the continuous LBT failure of the first resource includes: canceling the continuous LBT failure of the first resource indicated by the indication information.

In a sixth aspect, the present application provides a resource determination method, including: determining that a continuous LBT failure of a first resource of a terminal device is triggered and has not been canceled, and that the indication information corresponding to the first resource has not been generated or sent; wherein the indication information is used to indicate that the terminal device has detected a continuous LBT failure; if the first condition is met, the continuous LBT failure of the first resource is canceled, and the indication information corresponding to the first resource has not been generated or sent.

In this method, the terminal device determines that the continuous LBT failure of the first resource is triggered and has not been cancelled, and the side link resource corresponding to the first resource is unavailable. If the first condition is met, the first resource becomes an available resource after a period of time when the continuous LBT failure of the first resource is triggered, thereby improving the success rate of the UE performing LBT and ensuring SL communication. Moreover, the condition for the terminal device to send indication information to the network device is that the continuous LBT failure of the first resource of the terminal device is triggered and has not been cancelled and the indication information corresponding to the first resource has not been generated or sent, so that the terminal device can only report the indication information once at most, saving signaling overhead. By introducing "the indication information corresponding to the first resource has not been generated or sent", it will not affect the subsequent generation and sending of the indication information of the first resource.

In one possible design, before the first condition is met, the resource determination method also includes: sending indication information to the network device.

In this manner, the continuous LBT failure of the first resource of the terminal device is triggered and has not been canceled, and the indication information corresponding to the first resource has not been generated or sent. When there are available uplink resources for new transmission and the uplink resources can carry the sidelink continuous LBT failure MAC CE and its subheader, the terminal device can generate and send the indication information to enable the network device to obtain the continuous LBT failure information of the sidelink resources of the terminal device.

In one possible design, the first condition includes: a first timer of the first resource expires, wherein the first timer is started when the first resource detects consecutive LBT failures.

In one possible design, the indication information indicates that at least one first resource detects consecutive LBT failures.

In one possible design, the continuous LBT failure of the first resource is used to indicate that the side link resource corresponding to the first resource is not selectable or unavailable.

In the seventh aspect, the present application provides a resource determination method, including: determining that the continuous LBT failure of a first resource of a terminal device is triggered and not canceled, and since the most recent continuous LBT failure corresponding to the first resource was triggered, the indication information has not been generated or sent; wherein the indication information is used to indicate that the terminal device has detected a continuous LBT failure; if the first condition is met, cancel the continuous LBT failure of the first resource.

In this manner, the terminal device determines that the continuous LBT failure of the first resource is triggered and not cancelled, and the side link resource corresponding to the first resource is unavailable. If the first condition is met, the first resource becomes an available resource after a period of time when the continuous LBT failure is triggered by the first resource, thereby improving the success rate of the UE performing LBT and ensuring SL communication. Moreover, the condition for the terminal device to send indication information to the network device is that the continuous LBT failure of the first resource of the terminal device is triggered and not cancelled, and the indication information has not been generated or sent since the last continuous LBT failure corresponding to the first resource was triggered, so that the terminal device can only report the indication information once at most, saving signaling overhead. By introducing "the indication information has not been generated or sent since the last continuous LBT failure corresponding to the first resource was triggered", it will not affect the subsequent generation and sending of the indication information of the first resource.

In one possible design, before the first condition is met, the resource determination method also includes: sending indication information to the network device.

In one possible design, the first condition includes: a first timer of the first resource expires, wherein the first timer is started when the first resource detects consecutive LBT failures.

In one possible design, the indication information indicates that at least one first resource detects consecutive LBT failures.

In one possible design, the continuous LBT failure of the first resource is used to indicate that the side link resource corresponding to the first resource is not selectable or unavailable.

In an eighth aspect, a communication device is provided, comprising: a unit or means for executing each step in any of the above aspects.

In a ninth aspect, a communication device is provided, comprising a processor, a memory and a transceiver; the transceiver is used to communicate with other devices, and the processor is used to read instructions in the memory and enable the communication device to execute any of the methods provided in the above aspects according to the instructions.

In the tenth aspect, a program product is provided, which includes a computer program, wherein the computer program is stored in a readable storage medium, and at least one processor of a communication device can read the computer program from the readable storage medium, and the at least one processor executes the computer program so that the communication device implements the method provided in any of the above aspects.

In an eleventh aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores instructions. When the instructions are in a computer When the system is executed on a processor or a processor, the method provided in any of the above aspects is implemented.

In a twelfth aspect, a chip system is provided, which includes a processor for executing the method provided in any of the above aspects.

In a possible design, the chip system also includes a memory for storing program instructions and/or data. The chip system can be composed of a chip, or can include a chip and other discrete devices.

In a thirteenth aspect, a communication system is provided, the system comprising a terminal device, and the terminal device is used to implement the method provided in any of the above aspects.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a wireless communication system provided in an embodiment of the present application;

FIG2A is a schematic diagram of a connected UE detecting continuous LBT failures in mode 1 provided by the related art;

FIG2B is a flow chart of a method for processing continuous LBT failures provided by the related art;

FIG3A is a schematic diagram of an idle or inactive UE detecting continuous LBT failures in mode 2 provided by the related art;

FIG3B is another flow chart of a method for processing continuous LBT failures provided in the related art;

FIG4 is a schematic diagram of a connected UE detecting continuous LBT failures in mode 2 provided by the related art;

FIG5 is a flow chart of a resource determination method provided in an embodiment of the present application;

FIG6 is another schematic diagram of a connected UE detecting continuous LBT failures in mode 2 according to an embodiment of the present application;

FIG7 is another flow chart of a resource determination method provided in an embodiment of the present application;

FIG8 is another schematic diagram of a connected UE detecting continuous LBT failures in mode 2 according to an embodiment of the present application;

FIG9 is another flow chart of a resource determination method provided in an embodiment of the present application;

FIG10 is another schematic diagram of a connected UE detecting continuous LBT failures in mode 2 according to an embodiment of the present application;

FIG11 is a schematic diagram of the structure of a possible communication device provided in an embodiment of the present application;

FIG12 is a schematic diagram of a structure of a terminal device provided in an embodiment of the present application;

FIG13 is another flow chart of a resource determination method provided in an embodiment of the present application;

FIG14 is another schematic diagram of a connected UE detecting continuous LBT failures in mode 2 according to an embodiment of the present application;

FIG15 is another flow chart of a resource determination method provided in an embodiment of the present application;

FIG16 is another schematic diagram of a connected UE detecting continuous LBT failures in mode 2 according to an embodiment of the present application;

FIG17 is another flow chart of a resource determination method provided in an embodiment of the present application;

FIG. 18 is another schematic diagram of a connected UE detecting continuous LBT failures in mode 2 according to an embodiment of the present application.

DETAILED DESCRIPTION

In order to make the purpose, technical solution and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings. The specific operation methods, functional descriptions, etc. in the method embodiments can also be applied to the device embodiments or system embodiments.

The resource determination method provided in the present application can be applied to a wireless communication system, which includes a terminal device and a network device, wherein there are at least two terminal devices, and sidelink (SL) communication can be performed between the terminal devices.

Exemplarily, FIG1 is a schematic diagram of a wireless communication system provided in an embodiment of the present application. In FIG1 , a terminal device 101 includes two, identified as user equipment (UE) 1 and UE2, UE1 and UE2 perform SL communication. A network device 102 includes a base station 1, UE1 communicates with base station 1, and base station 1 is a serving base station for UE1.

It should be noted that FIG. 1 is only an example and does not limit the number of terminal devices 101 .

The terminal device 101 shown above may be a terminal device, a communication device, a communication device, a UE, a terminal, an access terminal, a terminal unit, a terminal station, a mobile station (MS), a remote station, a remote terminal, a mobile terminal (mobile terminal), a wireless communication device, a terminal agent, etc. The terminal device 101 may also be a chip, a vehicle, or a vehicle-mounted device (such as a vehicle-mounted communication device, a vehicle-mounted communication chip, a vehicle-mounted module, a vehicle-mounted module, an on-board unit (OBU), a telematics BOX (T-BOX), etc.), or a roadside unit (RSU), etc. The terminal device 101 may have a wireless transceiver function, and it may communicate with one or more network devices of one or more communication systems (such as wireless communication), and receive network services provided by the network devices, where the network devices include but are not limited to the illustrated network device 102.

The terminal device 101 may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, or a wearable Equipment, terminal devices in 5G networks, or terminal devices in future evolved public land mobile networks (PLMN) networks, etc.

The terminal device 101 can specifically be a mobile phone, a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving, a wireless terminal in remote medical, a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in a smart city (smart city), a wireless terminal in a smart home (smart home), etc.

In addition, the terminal device 101 can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; the terminal device 101 can also be deployed on the water surface (such as a ship, etc.); the terminal device 101 can also be deployed in the air (such as an airplane, balloon, and satellite, etc.).

The network device 102 shown above may be an access network device (or access network site, network node, etc.). Among them, the access network device refers to a device that provides network access function, such as a radio access network (RAN) base station, etc. The network device 102 may specifically include a base station (BS), or a base station and a wireless resource management device for controlling the base station, etc. The network device 102 may also include a relay station (relay device), an access point, a base station in a fifth generation system (5G) network, or a new radio (NR) base station, a base station in a future evolved PLMN network, etc. The network device 102 may be a wearable device or a vehicle-mounted device. The network device 102 may also be a communication chip with a communication module.

For example, the network device 102 includes but is not limited to: a base station (g node B, gNB) in 5G, an evolved node B (evolved node B, eNB) in a long term evolution (long term evolution, LTE) system, a radio network controller (radio network controller, RNC), a wireless controller under a cloud radio access network (cloud radio access network, CRAN) system, a base station controller (base station controller, BSC), a home base station (for example, home evolved node B, or home node B, HNB), a baseband unit (baseBand unit, BBU), a transmitting point (transmitting and receiving point, TRP), a transmitting point (tr It can be a base transceiver station (BTS) in a global mobile communication (Taiwan), mobile switching center, global system for mobile communication (GSM) or code division multiple access (CDMA) network, or a node base station (NB) in a wideband code division multiple access (WCDMA), or an evolved NB (eNB or eNodeB) in LTE, or a base station device in a future 5G network or an access network device in a future evolved PLMN network, or a wearable device or a vehicle-mounted device.

In some deployments, the network equipment may include a centralized unit (CU) and a distributed unit (DU). The network equipment may also include an active antenna unit (AAU). The CU implements some functions of the network equipment, and the DU implements some functions of the network equipment. For example, the CU is responsible for processing non-real-time protocols and services, and implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. The AAU implements some physical layer processing functions, RF processing, and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be converted from the information of the PHY layer, in this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or by the DU+AAU. It is understandable that the network device may be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU may be classified as a network device in an access network (radio access network, RAN), or the CU may be classified as a network device in a core network (core network, CN), which is not limited in this application.

In addition, the network device 102 can be connected to the CN device, and the CN device can be used to provide core network services for the access network device 102 and the terminal device 101. The core network device can correspond to different devices in different systems. For example, in 3G, the core network device can correspond to the serving GPRS support node (SGSN) of the general packet radio service (GPRS) and/or the gateway GPRS support node (GGSN) of GPRS. In 4G, the core network device can correspond to the mobility management entity (MME) and/or the serving gateway (S-GW). In 5G, the core network device can correspond to the access and mobility management function (AMF), the session management function (SMF) or the user plane function (UPF).

The wireless communication systems shown above include but are not limited to existing communication systems such as 5G and NR communication systems or future evolved PLMN systems.

It should be noted that, for the convenience of description, in this application, the terminal device is taken as a terminal equipment, the terminal equipment is specifically a UE, and the network equipment is taken as a base station as an example for description.

First, the relevant concepts are explained.

1. Sidelink (SL) communication

The 3rd Generation Partnership Project (3GPP) international standardization organization has introduced device-to-device direct communication (D2D) technology in LTE. With the development of 5G communication, D2D communication is also introduced in 5G NR technology.

Sidelink is a protocol designed by 3GPP for D2D technology. Terminal devices can communicate directly through the PC5 interface. Terminal devices can also communicate with network devices. The communication interface between terminal devices and network devices can be called the Uu interface. For example, as shown in Figure 1, the communication interface between UE1 and UE2 is called the PC5 interface, the communication interface between UE1 and base station 1 is called the Uu interface, and the link between UE1 and UE2 is called sidelink. UE1 and UE2 can communicate directly without the help of base station 1, which is called SL communication.

In Figure 1, when UE1 uses SL communication to send data to UE2, UE1 is called a sending terminal device, a sending device or a sending UE, and UE2 is called a receiving terminal device, a receiving device or a receiving UE. Similarly, when UE2 uses SL communication to send data to UE1, UE2 is called a sending UE, and UE1 is called a receiving UE.

One application scenario of SL communication can be 5G ProSe direct communication, where ProSe stands for proximity based service, which is the communication between two or more 5G ProSe terminal devices in proximity. 5G ProSe terminal devices are terminal devices that support 5G ProSe requirements and related processes.

Another application scenario of SL communication can be vehicle-to-everything (V2X) communication, which refers to the communication supporting V2X services using Uu interface and/or PC5 interface. V2X services are implemented through various types of V2X applications, such as vehicle-to-vehicle (V2V), vehicle-to-pedestrian (V2P), vehicle-to-infrastructure (V2I) and vehicle-to-network (V2N).

2. UE connection status in SL communication

The connection states of UE in SL communication include: connected state, idle state or inactive state.

When the UE is in a connected state, the UE can communicate with the base station. For example, in FIG1 , when UE1 is in a connected state, UE1 can communicate with base station 1.

When the UE is in an idle state or an inactive state, the UE does not communicate with the base station. For example, in FIG1 , when UE1 is in an idle state or an inactive state, UE1 does not communicate with base station 1.

3. Resource pool (RP), SL resources, resource selection mode 1 (Mode 1), resource selection mode 2 (Mode 2)

Resources, also called time-frequency resources, have a time range in the time domain and a frequency range in the frequency domain.

In SL communication, the UE is configured with a resource pool (RP), also called SL RP. This application does not limit the size of the time range and frequency range of the resource pool. For example, the frequency range of the resource pool is 100 MHz.

The resource pool may be configured by the base station, or configured by the upper layer, or pre-configured. "Upper layer" refers to the upper protocol layer divided according to the hierarchical structure of the communication protocol stack.

In SL communication, it is necessary to select SL resources in the resource pool for the transmitting UE, so as to use the SL resources to transmit SL data and realize SL communication between UEs. This application does not limit the time range and frequency range of the selected SL resources. For example, the frequency range of the resource pool is 100MHz, and the frequency range of the selected SL resources is 1MHz, 2MHz, 20MHz or 40MHz, etc.

For the transmitting UE to select SL resources in the resource pool, there are two resource selection modes, including: resource selection mode 1 and resource selection mode 2.

In resource selection mode 1, the base station selects SL resources from the resource pool for the transmitting UE. The base station may select one or more SL resources at a time, for example, up to 3 SL resources.

In resource selection mode 2, the transmitting UE selects a SL resource from the resource pool. The transmitting UE may select one or more SL resources at a time, for example, up to 3 SL resources.

Combined with the connection state of the UE, it can be seen that when the UE is in a connected state, the UE can communicate with the base station, and the UE can use resource selection mode 1 to select SL resources through the base station, or use resource selection mode 2 for the UE to select SL resources. When the UE is in an idle or inactive state, the UE does not communicate with the base station, and uses resource selection mode 2 to select SL resources.

4. Licensed spectrum, unlicensed spectrum, and resource pool types

The spectrum resources that can be used for SL communication include licensed spectrum and unlicensed spectrum. Unlicensed spectrum is shared spectrum. This application is applicable to unlicensed spectrum.

When using unlicensed spectrum for SL communication, UEs can configure SL carriers based on SL communication. Configure an SL uplink bandwidth part (BWP), and an SL BWP includes multiple Mode1 or Mode2 RPs. This application does not limit the number of RPs. For example, an SL BWP can include a maximum of 8 Mode1 or Mode2 RPs. An RP can include an integer number of resource block (RB) sets. This application does not limit the number of RB sets. Usually, the frequency range of an RB set is 20MHz.

For example, the UE is configured with 8 Mode 1 RPs and 8 Mode 2 RPs. The frequency range of each RP is 100 MHz, including 5 RB sets. The selected SL resources may be part or all of the resources in an RB set, or may include multiple RB sets. For example, the frequency range of the selected SL resources is 1 MHz, 2 MHz, 20 MHz, 30 MHz, or 40 MHz, etc.

In SL communication, UE can be configured with one or more logical channels (LCH). LCH carries different service data. Some types of service data need feedback after sending, while other types of service data do not need feedback after sending.

The LCH includes two categories: LCH with sidelink feedback enabled and LCH without sidelink feedback enabled.

Sidelink feedback is enabled, also known as sidelink hybrid automatic repeat request feedback enable or feedback enable. The LCH for sidelink feedback is enabled, that is, the sidelink hybrid automatic repeat request feedback enable (sl-HARQ-FeedbackEnabled) corresponding to the LCH is set to enabled (sl-HARQ-FeedbackEnabled is set to enabled for the LCH). The feedback-enabled LCH is used to carry SL data that requires feedback.

Sidelink feedback is not enabled, also known as sidelink hybrid automatic repeat request feedback is not enabled or feedback is not enabled. The LCH for which sidelink feedback is not enabled, that is, the sidelink hybrid automatic repeat request feedback enable (sl-HARQ-FeedbackEnabled) corresponding to the LCH is set to disabled (sl-HARQ-FeedbackEnabled is set to disabled for the LCH). The LCH for which feedback is not enabled is used to carry SL data that does not require feedback.

Correspondingly, the resource pools of UE in SL communication can be divided into two categories: resource pools with PSFCH resources (also called resource pools configured with PSFCH resources, expressed as RP with PSFCH resources or RP configured with PSFCH resources), and resource pools without PSFCH resources (also called resource pools not configured with PSFCH resources, i.e. other resource pools that are not "resource pools with PSFCH resources"). Among them, PSFCH represents the physical sidelink feedback channel (physical sidelink feedback channel).

The data on the feedback-enabled LCH needs to select SL resources for transmission from the resource pool with PSFCH resources. In other words, the SL resources in the resource pool without PSFCH resources cannot be used to transmit the data on the feedback-enabled LCH.

The data on the LCH that is not enabled for feedback can be transmitted using SL resources from a resource pool with PSFCH resources or from a resource pool without PSFCH resources.

For example. The UE is configured with 4 resource pools with PSFCH resources, identified as RP1 to RP4, and 4 resource pools without PSFCH resources, identified as RP5 to RP8. Then, the SL resources in RP1 to RP4 can transmit data on the LCH with feedback enabled, and can also transmit data on the LCH with feedback not enabled. The SL resources in RP5 to RP8 can only transmit data on the LCH with feedback not enabled. In other words, the data on the LCH with feedback enabled can only select SL resources from RP1 to RP4 for transmission. The data on the LCH with feedback not enabled can select SL resources from RP1 to RP4 and RP5 to RP8 for transmission.

5. LBT

When SL communication uses unlicensed spectrum, in order to use the unlicensed spectrum fairly, the UE needs to perform an LBT process, also known as a channel access process, before sending SL data on SL resources.

One implementation method is: before the UE sends a signal on the SL resource, it can first detect whether the SL resource is idle, for example, whether it detects that other nearby UEs are occupying the SL resource to send signals. This detection process can be called clear channel assessment (CCA) or channel access process.

If LBT is successful, the UE can use the SL resource for SL transmission. Otherwise, if LBT fails for the SL resource, the UE cannot use the SL resource for SL transmission.

It can be understood that LBT is performed based on SL resources, and this application does not limit the granularity of SL resources. For example, LBT can be performed at the granularity of a channel, where a channel is usually 20MHz, or it can be performed at the granularity of a resource pool. For another example, LBT is performed at the granularity of an RB set.

For the convenience of explanation, this application takes LBT based on RB set granularity as an example.

6. Continuous LBT failure

When a certain SL resource is busy, it may cause LBT to fail continuously, which is called a consistent LBT failure or SL consistent LBT failure, which can be expressed as SL C-LBT failure. In this application, to simplify the description, SL consistent LBT failure is referred to as a consistent LBT failure, that is, a consistent LBT failure is understood as a SL consistent LBT failure.

In one implementation of detecting continuous LBT failures, two parameters are configured: LBT failure detection timer length (lbt-FailureDetectionTimer) and LBT maximum failure count (lbt-FailureInstanceMaxCount), where the LBT maximum failure count is also called the maximum LBT failure count.

The MAC entity maintains a counter (LBT_COUNTER) and an LBT failure detection timer inside the UE. The initial value of the counter is 0, and it is used to record the number of LBT failures detected (or the cumulative number of LBT failures). When the MAC entity of the UE receives an LTB failure indication from the bottom layer (i.e., the physical layer), the LBT failure detection timer is started/restarted, and the number of LBT failures recorded by the counter is increased by 1. If the number of LBT failures recorded by the counter before the LBT failure detection timer times out is greater than or equal to the configured maximum number of LBT failures, it is considered that continuous LBT failures have been detected.

For example, assume that the LBT failure detection timer is 5 seconds and the maximum number of LBT failures is 4.

In one example, the initial value of the counter is 0. When an LBT failure is detected at 0 seconds, the number of LBT failures recorded by the counter is increased by 1, and the current value is 1, and the LBT failure detection timer is started. When an LBT failure is detected at 1 second, 2 seconds, and 4 seconds, the number of LBT failures recorded by the counter is accumulated to 4, and the LBT failure detection timer is restarted each time. Since the number of LBT failures recorded by the counter is 4, which is equal to the maximum number of LBT failures of 4, it is determined that continuous LBT failures are detected.

In another example, the initial value of the counter is 0. An LBT failure is detected at 0 seconds, the number of LBT failures recorded by the counter is increased by 1, the current value is 1, and the LBT failure detection timer is started. An LBT failure is detected at 3 seconds, the number of LBT failures recorded by the counter is accumulated to 2, and the LBT failure detection timer is restarted. The LBT failure detection timer times out at 8 seconds, and the value of the counter is set to the initial value 0. Since the number of LBT failures recorded by the counter is 2, which is less than the maximum number of LBT failures of 4, it is considered that no continuous LBT failures are detected.

It should be noted that LBT is based on SL resources. Each SL resource has its own LBT failure detection timer length and LBT maximum failure count. The values of these two parameters corresponding to different SL resources can be the same or different. For example, the SL resource can be RB set.

For example. SL resource 1 corresponds to LBT failure detection timer length 1 and LBT maximum failure number 1. For SL resource 1, the corresponding LBT failure detection timer and the counter recording the maximum number of LBT failures are maintained. SL resource 2 corresponds to LBT failure detection timer length 2 and LBT maximum failure number 2. For SL resource 2, the corresponding LBT failure detection timer and the counter recording the maximum number of LBT failures are maintained. When the number of LBT failures recorded by the counter corresponding to SL resource 1 is greater than or equal to the LBT maximum failure number 1, it is considered that SL resource 1 has detected continuous LBT failures. Similarly, when the number of LBT failures recorded by the counter corresponding to SL resource 2 is greater than or equal to the LBT maximum failure number 2, it is considered that SL resource 2 has detected continuous LBT failures. Among them, the LBT failure detection timer length 1 and the LBT failure detection timer length 2 can be the same or different, and the LBT maximum failure number 1 and the LBT maximum failure number 2 can be the same or different.

The following describes the processing procedure after detecting continuous LBT failures when the UE is in different connection states and uses different resource selection modes in the related art.

1. UE is in connected state, using resource selection mode 1

Exemplarily, FIG2A is a schematic diagram of a connected UE in mode 1 provided by the related art, and FIG2B is a flow chart of a method for processing continuous LBT failures provided by the related art. The UE is specifically UE1. As shown in FIG2A and FIG2B, UE1 is in a connected state and uses resource selection mode 1. The method for processing continuous LBT failures includes:

S201. UE1 determines that continuous LBT failures are detected on resource block set 1.

Detection of continuous LBT failure on resource block set 1 can be understood as an event or a state. At this time, UE1 determines that continuous LBT failure of resource block set 1 is triggered.

S202: If continuous LBT failure of resource block set 1 is triggered, UE1 sends indication information to the base station, indicating that UE1 has detected continuous LBT failure.

Specifically, the SL resources used by the connected UE are configured by the base station. After UE1 detects continuous LBT failures, it needs to indicate to the base station that "UE1 has detected continuous LBT failures." Accordingly, after receiving the indication information, the base station can perform subsequent resource scheduling processing. For example, the base station learns that UE1 has detected continuous LBT failures on resource block set 1, and the base station can switch to a resource block set 2 that has not detected continuous LBT failures to schedule SL resources. At this point, it can be understood that SL transmission has been restored, and the restoration of SL transmission depends on the base station.

Optionally, UE1 sends indication information to the base station, which may include: UE1 sends a medium access control control element (MAC CE) to the base station. Optionally, the MAC CE may include or indicate a set of resource blocks in which continuous LBT failures are detected, for example, including or indicating an identifier or index of the resource block set. The MAC CE may be called "Sidelink Continuous LBT Failure MAC CE (SL consistent LBT failure MAC CE)".

S203: If UE1 sends an indication message to the base station, canceling the continuous LBT failure of resource block set 1.

When MAC CE is successfully sent (successful means that the MAC layer does not receive PHY indication that the SL transmission has an LBT failure), UE1 can cancel the continuous LBT failure of resource block set 1. Among them, MAC CE includes or indicates that resource block set 1 detects continuous LBT failure.

Optionally, when continuous LBT failure of at least one resource block set is triggered, UE1 needs to send indication information to the base station, and when the triggered continuous LBT failure is cancelled, that is, no continuous LBT failure of the resource block set is currently triggered, UE1 does not need to send indication information to the base station. At this time, after canceling the continuous LBT failure of resource block set 1, UE1 no longer sends indication information to the base station.

S204. UE1 performs SL transmission on resource block set 2.

Among them, resource block set 2 is scheduled by the base station. Specifically, UE1 performs SL transmission on the SL resources in resource block set 2, and the SL resources in the resource block set 2 are scheduled by the base station. Before performing SL transmission, UE1 needs to perform LBT on the SL resources in the resource block set 2.

It can be seen that in this scenario, after the UE determines that continuous LBT has failed, it needs to send indication information to the base station to notify the base station of the resource block set where continuous LBT has failed. When the base station selects a new resource block set for the UE, it can exclude the resource block set that has previously detected continuous LBT failures, thereby avoiding selecting the resource block set for LBT again after a continuous LBT failure has been detected in a certain resource block set, thereby ensuring the success rate of the UE's LBT and ensuring SL communication. At the same time, after the indication information is sent to the base station, the indication information will no longer be sent to the base station.

2. The UE is in idle or inactive state and uses resource selection mode 2

Exemplarily, FIG. 3A is a schematic diagram of an idle or inactive UE in mode 2 provided by the related art, and FIG. 3B is another flow chart of a method for processing continuous LBT failures provided by the related art. The UE is specifically UE1. As shown in FIG. 3A and FIG. 3B, UE1 is in an idle or inactive state and uses resource selection mode 2. The method for processing continuous LBT failures includes:

S301. UE1 determines that continuous LBT failures are detected on resource block set 1.

Similar to S201, no further details will be given here.

Specifically, when UE1 is in an idle or inactive state, the SL resources used by UE1 are selected by UE1 itself in the resource pool. If UE1 detects continuous LBT failures on resource block set 1, it is considered that the SL resources in resource block set 1 can no longer be selected for SL transmission, thereby improving the success rate of UE1 performing LBT. At this time, resource block set 1 is considered to be an unselectable resource block set (i.e., an unavailable resource block set).

S302. UE1 performs SL transmission on resource block set 2.

Specifically, when UE1 is in an idle or inactive state, the SL resources used by UE1 are selected by UE1 itself in the resource pool. If UE1 detects continuous LBT failures on resource block set 1, UE1 can automatically switch to a new resource block set 2 in the resource pool where no continuous LBT failures are detected for SL transmission. Specifically, UE1 selects SL resources in resource block set 2 and performs SL transmission on the selected SL resources. Before performing SL transmission, UE1 needs to perform LBT on the SL resources in the resource block set 2. If an SL transmission is successfully completed using SL resources in the new resource block set 2 (successful, that is, the MAC layer does not receive a PHY indication that the SL transmission has an LBT failure), at this time, it can be understood that the SL transmission has been restored, and the restoration of the SL transmission depends on UE1.

It should be understood that UE1 cannot select SL resources for SL transmission in the resource block set where continuous LBT failures are detected (i.e., the resource block set that triggers continuous LBT failures), and can only select SL resources for SL transmission in the resource block set where continuous LBT failures are not detected (i.e., the resource block set that does not trigger continuous LBT failures, or the resource block set where the triggered continuous LBT failures have been canceled).

S303. According to the resource block set recovery mechanism, UE1 cancels the continuous LBT failure of resource block set 1.

The resource block set recovery mechanism may include: when a SL transmission is successfully completed using SL resources in a new resource block set, or after a period of time (such as after a timer expires), or after the SL channel quality is better than a certain condition, or after the SL busy state is lower than a certain condition.

If the resource block set recovery mechanism is satisfied, UE1 cancels the continuous LBT failure of resource block set 1, and resource block set 1 is no longer the resource block set where continuous LBT failure is detected, but becomes a selectable resource block set (ie, an available resource block set).

It can be seen that in this scenario, after the UE determines that continuous LBT failures have occurred, the UE needs to exclude the resource block set that previously detected continuous LBT failures when autonomously selecting a new resource block set. Through the resource block set recovery mechanism, the resource block set that previously detected continuous LBT failures will not be immediately selectable, and it must satisfy the resource block set recovery mechanism before it can become a selectable resource block set. This avoids selecting a resource block set for LBT again after a continuous LBT failure has been detected in a certain resource block set, thereby ensuring the success rate of the UE's LBT and ensuring SL communication.

3. UE is in connected state, using resource selection mode 2

In this scenario, the SL resources used by the UE are selected by the UE itself in the resource pool, and the UE is in a connected state. After the UE detects continuous LBT failures, it needs to indicate to the base station that "UE detects continuous LBT failures". A schematic diagram of a UE detecting continuous LBT failure in mode 2. The UE is specifically UE1. UE1 determines that continuous LBT failure is detected on resource block set 1. This involves reporting "UE1 detects continuous LBT failure" to the base station and canceling the continuous LBT failure of resource block set 1.

Optionally, in one implementation, the recovery of SL transmission depends on the base station. For canceling the continuous LBT failure of resource block set 1, reference can be made to the implementation of the scenario where the connected UE uses resource selection mode 1. If UE1 sends an indication message to the base station, the continuous LBT failure of resource block set 1 is canceled.

Specifically, UE1 detects continuous LBT failures on a resource block set, and UE1 needs to send indication information to the base station, indicating that UE1 has detected continuous LBT failures. The base station resumes SL transmission according to the indication information. For example, when the base station learns that UE1 has detected continuous LBT failures on resource block set 1, the base station can perform RRC reconfiguration to release resource pool 1 including resource block set 1, and then reconfigure a resource pool 2, where resource pool 2 includes resource block set 2 where no continuous LBT failures are detected.

If UE1 sends an indication message to the base station, UE1 cancels the continuous LBT failure of the resource block set. Since UE1 uses resource selection mode 2, after UE1 sends the indication message, regardless of whether the base station responds, UE1 may immediately select the resource block set that has just detected the continuous LBT failure, resulting in UE1 selecting a resource block set with a high probability of LBT failure, which reduces the success rate of UE1's LBT and causes the SL data to be unable to be transmitted in time. For example, in Figure 4, UE1 detects continuous LBT failures on resource block set 1. After sending the indication message, the continuous LBT failure of resource block set 1 is canceled, and resource block set 1 becomes a selectable resource block set. UE1 may immediately select resource block set 1 for LBT. Moreover, assuming that the base station responds immediately every time after receiving the indication message, even if UE1 has other selectable resource block sets, the base station needs to perform RRC reconfiguration, which increases the burden of RRC signaling.

Optionally, in another implementation, the recovery of SL transmission depends on UE1. There are two ways to cancel the continuous LBT failure of resource block set 1. Method 1: You can refer to the implementation method of the scenario where the connected UE uses resource selection mode 1. If UE1 sends an indication message to the base station, the continuous LBT failure of resource block set 1 is canceled. Method 2: You can refer to the resource block set recovery mechanism in the scenario where the idle or inactive UE uses resource selection mode 2. When the resource block set recovery mechanism is met, the continuous LBT failure of resource block set 1 is canceled.

Specifically, when UE1 detects continuous LBT failures on a resource block set, UE1 may automatically switch to a new resource block set in the resource pool where no continuous LBT failures are detected to perform LBT, thereby realizing recovery of SL transmission.

UE1 also needs to send indication information to the base station.

There are two ways to cancel the continuous LBT failure of resource block set 1. If UE1 first cancels the continuous LBT failure of resource block set 1 through method 1, and resource block set 1 becomes an optional resource block set, UE1 may immediately select resource block set 1 for LBT, resulting in an increase in the failure rate of UE1 performing LBT and the failure of SL data to be transmitted in time. If UE1 first cancels the continuous LBT failure of resource block set 1 through method 2, the indication information may not be reported to the base station in time and cannot be reported to the base station subsequently. If UE1 sends indication information to the base station, but the continuous LBT failure of resource block set 1 is not canceled due to method 2, then before the resource block set recovery mechanism is satisfied or before the triggered continuous LBT failure of resource block set 1 is canceled, UE1 will repeatedly report unnecessary indication information, increasing the signaling burden of MAC CE reporting.

It can be seen that in this scenario, after the UE determines that the continuous LBT has failed, it needs to send an indication message to the base station to notify the base station of the resource block set for which the continuous LBT has failed. The UE uses resource selection mode 2 and can select a new resource block set in the resource pool for LBT. Since there are two mechanisms (or two conditions, two events) for the UE to cancel the continuous LBT failure of the triggered resource block set, that is, canceling the continuous LBT failure by reporting the indication message to the base station or canceling the continuous LBT failure according to the resource block set recovery mechanism, the occurrence time of these two mechanisms may be different, resulting in the UE selecting a new resource block set to continue LBT. When selecting a new resource block set, it may select the resource block set that has just failed the continuous LBT, which increases the probability of LBT failure and causes the SL data to be unable to be transmitted in time. It may also increase the signaling overhead. From another perspective, since the UE needs to perform two actions, one action is to send indication information to the base station and no longer send the indication information repeatedly, and the other action is to determine that the resource block set where continuous LBT failures are detected becomes a selectable resource block set, the occurrence time of these two actions may be different, resulting in the inability to associate them with an event or a condition such as "triggering and canceling continuous LBT failures of a resource block set". In other words, these two actions should be associated with corresponding events or conditions.

The present application provides a resource determination method, which is applicable to the scenario where a connected UE uses unlicensed spectrum and resource selection mode 2 for SL communication. In this scenario, after the UE determines that continuous LBT failures are detected on a resource block set, it needs to send an indication message to the base station. Considering that there can be two mechanisms for UE to cancel the triggered continuous LBT failure, or the two behaviors should be respectively associated with corresponding events or conditions, by setting new conditions, it is ensured that the resource block set that has just failed the continuous LBT can become a selectable resource block set after a certain period of time, and it is avoided that the resource block set that has just failed the continuous LBT can be immediately changed to a selectable resource block set and reselected by the UE for LBT. This improves the LBT success rate and ensures that SL data can be transmitted in a timely manner.

The technical solution of the present application is described in detail below through specific embodiments.

In the embodiments of the present application, unless otherwise specified, the same or similar parts between the various embodiments can refer to each other. In the various embodiments of the present application, and the various implementation methods/implementation methods/implementation methods in the various embodiments, if there is no special description and logical conflict, the terms and/or descriptions between different embodiments and the various implementation methods/implementation methods/implementation methods in the various embodiments are consistent and can be referenced to each other, and the technical features in different embodiments and the various implementation methods/implementation methods/implementation methods in the various embodiments can be combined to form new embodiments, implementation methods, implementation methods, or implementation methods according to their inherent logical relationships. The above-described implementation methods of the present application do not constitute a limitation on the scope of protection of the present application. In each embodiment step, it can be partially executed (for example, the terminal device may not execute the steps performed by the terminal device in the above embodiment). The execution order of different steps can be changed. The embodiments described herein can be combined with other embodiments, and the steps of different embodiments of this article can also be combined.

Reference to "embodiment" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiment may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments.

The terms "first", "second", "third", "fourth", etc. (if any) in the embodiments of the present application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

In the embodiments of the present application, "include" can be an inclusion relationship or an equality relationship. For example, A includes B, which means that A includes B and can also include other contents, or A and B are the same content.

In the description of this application, unless otherwise specified, "/" indicates that the objects associated before and after are in an "or" relationship, for example, A/B can represent A or B; "and/or" in this application is only a kind of association relationship describing the associated objects, indicating that there can be three relationships, for example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In addition, in the description of this application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same items or similar items with substantially the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit the difference.

In the embodiments of the present application, the terms “of”, “corresponding”, “relevant” and “corresponding” may sometimes be used interchangeably. It should be noted that when the distinction between them is not emphasized, the meanings they intend to express are consistent.

In the embodiments of the present application, words such as "exemplarily" and "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of the word "exemplary" is intended to present concepts in a concrete way.

It should be noted that the resource determination method provided in this application is applied to SL communication. In this application, resources and SL resources have the same meaning; continuous LBT failure and SL continuous LBT failure have the same meaning; canceling continuous LBT failure and canceling continuous LBT failure of resources have the same meaning.

Figure 5 is a flow chart of a resource determination method provided in an embodiment of the present application. The resource determination method provided in this embodiment involves a terminal device and a network device, and is applicable to a scenario where a connected UE uses unlicensed spectrum and resource selection mode 2 for SL communication.

In this embodiment, after the UE detects continuous LBT failures on a resource, the recovery of SL transmission depends on the terminal device. That is, when the UE detects continuous LBT failures on a resource, it can select another resource in the resource pool where no continuous LBT failures are detected for SL transmission, but no longer select the resource where the continuous LBT failures are detected for SL transmission, thereby improving the success rate of the UE performing LBT and recovering SL transmission. Optionally, the resources where no continuous LBT failures are detected may include: resources where no continuous LBT failures are detected, or resources where continuous LBT failures were previously detected but are currently recovered as selectable resources (available resources); resources where continuous LBT failures are detected are non-selectable resources (i.e., unavailable resources).

The UE detects continuous LBT failure on a resource, and the subsequent steps involve: the terminal device cancels reporting indication information to the network device (event one), cancels the continuous LBT failure of the resource (event two), and recovers the resource that detects the continuous LBT failure (event three). In this embodiment, the time of event one and event three may be different. Event two is related to event one, and event two is not related to event three. Event three may be associated with the first state and/or the second state of the resource.

As shown in FIG5 , the resource determination method provided in this embodiment may include:

S501: The terminal device determines that a continuous LBT failure of a first resource of the terminal device is triggered, and a first state of the first resource of the terminal device is triggered, wherein the first state is that a sidelink resource corresponding to the first resource is unavailable (ie, not selectable).

The UE performs LBT based on the granularity of the first resource. Optionally, the first resource may be a resource block set, and the frequency range may be 20 MHz. The first resource may also be a resource of other granularity, such as a resource pool, a frequency range of 10 MHz, etc.

The UE performs LBT on the first resource, that is, performs LBT on the SL resource in the first resource, and determines that continuous LBT failures are detected on the first resource. Continuous LBT failures can be understood as an event or a state. At this time, the UE determines that the continuous LBT failure of the first resource of the terminal device is triggered, and the first state of the first resource of the terminal device is triggered. At this time, the SL resource corresponding to the first resource is unavailable.

Since the first state of the first resource is triggered (and not canceled), the SL resource corresponding to the first resource is unavailable. Therefore, the UE selects another resource in the resource pool (the corresponding first state is not triggered, or is triggered but canceled) for LBT without detecting continuous LBT failures, instead of the first resource. This avoids selecting the first resource for LBT again after the first resource triggers continuous LBT failures, thereby improving the success rate of the UE's LBT and ensuring SL communication.

Optionally, the number of the first resource may be at least one.

Optionally, the UE determines that continuous LBT failures are detected on the first resource, which may include any one of the following: continuous LBT failures are detected on a certain first resource, continuous LBT failures are detected on any first resource, continuous LBT failures are detected on at least one first resource, or continuous LBT failures are detected on each first resource.

The present embodiment does not limit the name of the first state. For example, the first state is also called unselectable or unavailable.

Optionally, in one implementation, the first state can be understood as an event or a state, and at this time, the first state of the first resource of the terminal device is triggered, which can include: the first resource of the terminal device is in the first state. The first resource of the terminal device is in the first state, which can be described as: the SL resource corresponding to the first resource of the terminal device is not selectable or unavailable.

Optionally, in another implementation, the state information of the resource may be set, and different values or different contents of the state information are the first state. At this time, the first state of the first resource of the terminal device is triggered, which may include: setting the first resource to the first state.

For example. The status information can be 1-bit information. The status information value of 0 indicates the first state, and the value of 1 indicates the second state, that is, the first state is equal to 0, and the second state is equal to 1. The first state indicates that the SL resource corresponding to the first resource is unavailable, and the second state indicates that the SL resource corresponding to the first resource is available (that is, optional). Alternatively, the first state can also be equal to 1, and the second state can be equal to 0.

The present embodiment does not limit the name of the second state. For example, the second state is also called selectable or available.

Optionally, in an implementation manner, determining that a continuous listen-before-talk LBT failure of a first resource of a terminal device is triggered and a first state of the first resource of the terminal device is triggered includes:

If the second condition is met, it is determined that the continuous LBT failure of the first resource of the terminal device is triggered, and the first state of the first resource of the terminal device is triggered. The second condition is: the cumulative number of LBT failures corresponding to the first resource is equal to or greater than the maximum LBT failure number.

Among them, the cumulative number of LBT failures and the maximum number of LBT failures can refer to the previous description of the concept of "continuous LBT failures", which will not be repeated here.

In this implementation, if the cumulative number of LBT failures corresponding to the first resource is equal to or greater than the maximum number of LBT failures, it is determined that continuous LBT failures are detected on the first resource, it is determined that the continuous LBT failure of the first resource of the terminal device is triggered, and it is determined that the first state of the first resource of the terminal device is triggered.

Optionally, in another implementation, determining that a continuous listen-before-talk LBT failure of a first resource of a terminal device is triggered and a first state of the first resource of the terminal device is triggered includes:

If the second condition is met, it is determined that the continuous LBT failure of the first resource of the terminal device is triggered. If the third condition is met, it is determined that the first state of the first resource of the terminal device is triggered.

The third condition is: continuous LBT failure is detected in the first resource, or the first resource triggers continuous LBT failure.

In this implementation, if the cumulative number of LBT failures corresponding to the first resource is equal to or greater than the maximum number of LBT failures, it is determined that continuous LBT failures are detected on the first resource, and it is determined that the continuous LBT failures of the first resource of the terminal device are triggered. If continuous LBT failures are detected on the first resource, or the first resource triggers continuous LBT failures, it is determined that the first state of the first resource of the terminal device is triggered. Through the second condition and the third condition, the conditions for determining that the first state of the first resource of the terminal device is triggered are more flexible.

S502: The terminal device sends indication information to the network device, where the indication information is used to indicate that the terminal device has detected continuous LBT failures.

Correspondingly, the network device receives the indication information sent by the terminal device.

Specifically, if the continuous LBT failure of the first resource of the terminal device is triggered and is not cancelled, the terminal device sends a Indication information. Notify the network device of the resource that triggered the continuous LBT failure. It should be understood that if the continuous LBT failure of a resource of the terminal device is triggered and has not been cancelled, the terminal device needs to send indication information to the network device until the continuous LBT failure of no resource of the terminal device is triggered, that is, the triggered continuous LBT failure of all resources of the terminal device are cancelled. If the continuous LBT failure of a resource of the terminal device is triggered and continues to exist and has not been cancelled, the terminal device needs to continue to send indication information to the network device.

Optionally, the number of first resources may be at least one. If the continuous LBT failure of the first resource of the terminal device is triggered, it may include any one of the following: the continuous LBT failure of a certain first resource is triggered, the continuous LBT failure of any first resource is triggered, the continuous LBT failure of at least one first resource is triggered, or whenever the continuous LBT failure of a first resource is triggered.

Optionally, the indication information indicates that at least one first resource detects continuous LBT failures.

The indication information may refer to the relevant description of S202 in FIG. 2B , which will not be described again here.

Optionally, after receiving the indication information, the network device may not perform subsequent resource configuration processing, and the UE may resume SL transmission. For example, if the network device finds that the UE still has sufficient resources without detecting continuous LBT failures, the resource pool of the UE may not be reconfigured. Of course, if the network device finds that the UE does not have sufficient resources without detecting continuous LBT failures, the resource pool of the UE may be reconfigured, and this application does not limit this.

S503: The terminal device fails to cancel the continuous LBT of the first resource.

Specifically, if the terminal device sends an indication message to the network device, the terminal device cancels the triggered continuous LBT failure of the first resource.

Optionally, the terminal device sends the indication information to the network device, which can be specifically: the terminal device sends a MAC protocol data unit (PDU), and the MAC PDU includes a side link continuous LBT failure MAC CE. If the terminal device sends the indication information to the network device, it can be replaced by: if a MAC PDU is sent and the MAC PDU includes a side link continuous LBT failure MAC CE.

Since the terminal device cancels the continuous LBT failure of the triggered first resource, the terminal device will no longer report the indication information, saving signaling overhead. Moreover, even if the terminal device cancels the continuous LBT failure of the triggered first resource, since the first state of the first resource of the terminal device is triggered and the SL resource corresponding to the first resource is unavailable, the UE will not select the first resource for SL transmission, thereby improving the success rate of the UE's LBT.

Optionally, canceling the continuous LBT failure of the first resource may include:

The continuous LBT failure of the first resource indicated in the indication information is cancelled. If a certain resource detects a continuous LBT failure but the indication information does not indicate the continuous LBT failure of the certain resource, the continuous LBT failure of the certain resource is not cancelled.

S504: If the first condition is met, the terminal device cancels the first state of the first resource.

Specifically, the condition for the terminal device to cancel the triggered continuous LBT failure of the first resource is that the terminal device sends indication information to the network device, and the condition for the terminal device to cancel the first state of the first resource is that the first state of the first resource is triggered and the first condition is met. Due to the different conditions, the time for the terminal device to cancel reporting the indication information to the network device (event one) and the time for detecting the recovery of the resource with continuous LBT failure (event three) can be different.

Since it takes a certain amount of time to meet the first condition, it is ensured that the first resource will not become available again immediately after the failure of triggering continuous LBT. Instead, the first state of the first resource is canceled after a certain period of time, and the SL resource corresponding to the first resource becomes available. This avoids the possibility that the UE immediately selects the first resource for SL transmission after the failure of the first resource to trigger continuous LBT, thereby improving the success rate of the UE's LBT and ensuring SL communication.

Optionally, the first condition includes at least one of the following:

A transmission is successfully completed using the sidelink resource on the second resource.

A first time period elapses after the first state of the first resource is triggered.

The first timer times out, and the first timer is started when the first state of the first resource is triggered.

The sidelink channel quality meets the channel quality condition.

The sidelink channel busy state satisfies the channel busy condition.

This embodiment does not limit the first time period, the time length of the first timer, the channel quality condition, and the channel busy condition.

Optionally, in an implementation manner, canceling the first state of the first resource may include:

The first resource of the terminal device is not in the first state, the first resource of the terminal device is in the second state, and the second state is that the side link resource corresponding to the first resource is available (ie, optional).

The present embodiment does not limit the name of the second state. For example, the second state is also called selectable or available.

In this implementation, the second state can be understood as an event or a state. At this time, the first resource of the terminal device is in the second state, which can be described as: the first resource of the terminal device is that the SL resource corresponding to the first resource is selectable or available.

Optionally, in another implementation, canceling the first state of the first resource may include: setting the first resource to a second state.

In this implementation, the state information of the resource may be set, and different values or different contents of the state information are the second state. For example, the state information may be 1-bit information, and the state information value of 0 indicates the first state, and the value of 1 indicates the second state, that is, the first state is equal to 0, and the second state is equal to 1.

After the UE detects continuous LBT failures on the first resource, it needs to exclude the resources in the first state when selecting resources and select SL resources from the resources in the second state. It should be understood that the UE cannot select SL resources for SL transmission in the resource block set in the first state, and can only select SL resources for SL transmission in the resource block set in the second state.

It can be seen that the resource determination method provided in this embodiment is applicable to the scenario where the connected UE uses unlicensed spectrum and resource selection mode 2 for SL communication. The terminal device determines that the continuous LBT failure of the first resource is triggered, and the first state of the first resource is triggered, and the first state is that the side link resource corresponding to the first resource is unavailable. If the continuous LBT failure of the first resource of the terminal device is triggered, the terminal device sends an indication message to the network device, and the terminal device cancels the continuous LBT failure of the first resource. The terminal device will no longer report the indication information, saving signaling overhead. If the first condition is met, the terminal device cancels the first state of the first resource. Through the first condition, it is avoided that the first resource becomes available immediately after the continuous LBT failure is triggered by the first resource, and it is avoided that the terminal device immediately reselects the first resource for SL transmission, thereby improving the success rate of LBT for the UE and ensuring SL communication.

The effect of the resource determination method provided by this embodiment is described below in conjunction with Figure 6. Figure 6 is another schematic diagram of a connected UE detecting continuous LBT failures in mode 2 provided by an embodiment of the present application. The UE is specifically UE1.

As shown in FIG6 , UE1 determines that the continuous LBT failure of resource block set 1 of UE1 is triggered, and the first state of resource block set 1 of UE1 is triggered. At this time, the side link resources corresponding to resource block set 1 are unavailable. UE1 sends an indication message to base station 1, indicating that UE1 has detected continuous LBT failure. When UE1 sends an indication message to base station 1, UE1 cancels the triggered continuous LBT failure of resource block set 1. At this time, the side link resources corresponding to resource block set 1 are still unavailable. UE1 can select another resource block set 2 in the resource pool where no continuous LBT failure is detected for SL transmission, and at this time, the second state of resource block set 2 is that the SL resources corresponding to resource block set 2 are available. If the first condition is met, for example, after the first time period has passed after the first state of resource block set 1 is triggered, UE1 cancels the first state of resource block set 1, for example, sets resource block set 1 to the second state. At this time, the side link resources corresponding to resource block set 1 are available, and UE1 can select the SL resources corresponding to resource block set 1 for SL transmission.

Figure 7 is another flow chart of the resource determination method provided in an embodiment of the present application. The resource determination method provided in this embodiment involves a terminal device and a network device, and is applicable to a scenario where a connected UE uses unlicensed spectrum and resource selection mode 2 for SL communication.

This embodiment is similar to the embodiment shown in FIG5 in that after the UE detects continuous LBT failures on a resource, the recovery of SL transmission depends on the terminal device. In the subsequent events involving the terminal device canceling the reporting of indication information to the network device (event one), canceling the continuous LBT failure of the resource (event two), and recovering the resource that detected the continuous LBT failure (event three), the time of event one and event three may be different.

The difference between this embodiment and the embodiment shown in Figure 5 is that: in this embodiment, event 2 is related to event 3, and event 2 is not related to event 1. Event 1 can be associated with the third state of the resource.

As shown in FIG. 7 , the resource determination method provided in this embodiment may include:

S701. The terminal device determines that continuous LBT failure of a first resource of the terminal device is triggered, and the third state of the terminal device is triggered.

The UE performs LBT based on the granularity of the first resource. Optionally, the first resource may be a resource block set, and the frequency range may be 20 MHz. The first resource may also be a resource of other granularity, such as a resource pool, a frequency range of 10 MHz, etc.

The UE performs LBT on the first resource, that is, performs LBT on the SL resource in the first resource, and determines that continuous LBT failure is detected on the first resource. Continuous LBT failure can be understood as an event or a state. At this time, the UE determines that the continuous LBT failure of the first resource of the terminal device is triggered, and the third state of the terminal device is triggered.

Among them, continuous LBT failure is used to indicate that the side link resource corresponding to the first resource is unavailable (i.e., not selectable). That is to say, if the continuous LBT failure of the first resource is triggered (and not cancelled), the SL resource corresponding to the first resource is unavailable (i.e., not selectable). If the continuous LBT failure of the first resource is not triggered, or is triggered but cancelled, the SL resource corresponding to the first resource is available (i.e., selectable).

Since the continuous LBT failure of the first resource is triggered (and not canceled), the SL resource corresponding to the first resource is unavailable. Therefore, the UE selects another resource in the resource pool where no continuous LBT failure is detected (the continuous LBT failure is not triggered, or is triggered but canceled) for LBT, instead of selecting the first resource. This avoids selecting the first resource for LBT again after the continuous LBT failure is triggered by the first resource, thereby improving the success rate of the UE's LBT and ensuring SL communication.

Optionally, the number of the first resource may be at least one.

Optionally, the UE determines that continuous LBT failure of the first resource is triggered, which may include any one of the following: continuous LBT failure of a certain first resource is triggered, continuous LBT failure of any first resource is triggered, continuous LBT failure of at least one first resource is triggered, or, whenever a continuous LBT failure of a first resource is triggered.

Whether the third state of the terminal device is triggered is related to the terminal device sending indication information to the network device. If the third state of the terminal device is triggered and not cancelled, the terminal device sends indication information to the network device. In other words, the condition for the terminal device to send indication information to the network device is "the third state of the terminal device is triggered and not cancelled".

Among them, this embodiment does not limit the name of the third state. For example, the third state is side link continuous LBT failure reporting, which can be expressed as SL C-LBT failure reporting.

Optionally, in an implementation manner, the terminal device determines that continuous LBT failures of a first resource of the terminal device are triggered, and a third state of the terminal device is triggered, including:

If the second condition is met, it is determined that the continuous LBT failure of the first resource of the terminal device is triggered, and the third state of the terminal device is triggered. The second condition is: the cumulative number of LBT failures corresponding to the first resource is equal to or greater than the maximum LBT failure number.

Among them, the cumulative number of LBT failures and the maximum number of LBT failures can refer to the previous description of the concept of "continuous LBT failures", which will not be repeated here.

In this implementation, if the cumulative number of LBT failures corresponding to the first resource is equal to or greater than the maximum number of LBT failures, it is determined that continuous LBT failures are detected on the first resource, it is determined that the continuous LBT failure of the first resource of the terminal device is triggered, and it is determined that the third state of the terminal device is triggered.

Optionally, in another implementation, the terminal device determines that continuous LBT failures of the first resource of the terminal device are triggered, and the third state of the terminal device is triggered, including:

If the second condition is met, it is determined that the continuous LBT failure of the first resource of the terminal device is triggered. If the third condition is met, it is determined that the third state of the terminal device is triggered.

The third condition is: continuous LBT failure is detected in the first resource, or the first resource triggers continuous LBT failure.

In this implementation, if the cumulative number of LBT failures corresponding to the first resource is equal to or greater than the maximum number of LBT failures, it is determined that continuous LBT failures are detected on the first resource, and it is determined that the continuous LBT failures of the first resource of the terminal device are triggered. If continuous LBT failures are detected on the first resource, or the first resource triggers continuous LBT failures, it is determined that the third state of the terminal device is triggered. Through the second condition and the third condition, the condition for determining that the third state of the terminal device is triggered is more flexible.

S702: If the first condition is met, the terminal device fails to cancel the continuous LBT of the first resource.

Specifically, if the continuous LBT failure of the first resource of the terminal device is triggered and the first condition is met, the terminal device cancels the continuous LBT failure of the first resource.

Specifically, if the terminal device cancels the continuous LBT failure of the triggered first resource, it means that the first resource has triggered the continuous LBT failure but has been canceled, and the first resource has become an available resource, and the UE can select the first resource for SL transmission. The condition for the terminal device to cancel the continuous LBT failure of the first resource triggered is "the continuous LBT failure of the first resource of the terminal device is triggered and the first condition is met", wherein the continuous LBT failure is used to indicate that the side link resource corresponding to the first resource is unavailable. Since it takes a certain amount of time to meet the first condition, it is ensured that the first resource will not immediately become an available resource after triggering the continuous LBT failure, but will become an available resource after a certain period of time, thereby avoiding the possibility that the UE may immediately select the first resource for SL transmission after the continuous LBT failure is triggered by the first resource, thereby improving the success rate of the UE performing LBT and ensuring SL communication.

Optionally, the first condition includes at least one of the following:

A transmission is successfully completed using the sidelink resource on the second resource.

A first time period elapses after the first state of the first resource is triggered.

The first timer times out, and the first timer is started when the first state of the first resource is triggered.

The sidelink channel quality meets the channel quality condition.

The sidelink channel busy state satisfies the channel busy condition.

This embodiment does not limit the first time period, the time length of the first timer, the channel quality condition, and the channel busy condition.

After the UE detects continuous LBT failures on the first resource, it needs to exclude the resources where the continuous LBT failures are triggered when selecting resources, and select SL resources from other resources (where the continuous LBT failures are not triggered, or are triggered but cancelled). The UE cannot select SL resources for SL transmission in the resource block set where continuous LBT failures are detected (i.e., the resource block set where continuous LBT failures are triggered), and can only select SL resources for SL transmission in the resource block set where continuous LBT failures are not detected (i.e., the resource block set where continuous LBT failures are not triggered, or the resource block set where the triggered continuous LBT failures have been cancelled).

S703: The terminal device sends indication information to the network device, where the indication information is used to indicate that the terminal device has detected continuous LBT failures.

Correspondingly, the network device receives the indication information sent by the terminal device.

Specifically, if the third state of the terminal device is triggered and not cancelled, the terminal device sends an indication message to the network device. Notify the network device to trigger the resource of the continuous LBT failure. It should be understood that if the third state of a resource of the terminal device is triggered and not cancelled, the terminal device needs to send an indication message to the network device until the third state of the resource that does not exist in the terminal device is triggered, that is, the triggered third state of all resources of the terminal device is cancelled. If the third state of a resource of the terminal device is triggered and exists all the time and is not cancelled, the terminal device needs to keep sending indication messages to the network device.

Optionally, the indication information indicates that at least one first resource detects continuous LBT failures.

The indication information may refer to the relevant description of S202 in FIG. 2B , which will not be described again here.

Optionally, after receiving the indication information, the network device may not perform subsequent resource configuration processing, and the UE may resume SL transmission. For example, if the network device finds that the UE still has sufficient resources whose third state has not been triggered, the resource pool of the UE may not be reconfigured. Of course, if the network device finds that the UE does not have sufficient resources whose third state has not been triggered, the resource pool of the UE may be reconfigured, and this application does not limit this.

In this embodiment, the condition for the terminal device to send the indication information to the network device is that the third state of the terminal device is triggered, and the condition for the terminal device to cancel the triggered continuous LBT failure of the first resource is that the first condition is satisfied. The two conditions are different, so that the time for the terminal device to cancel reporting the indication information to the network device (event one) and the time for detecting the recovery of the resource of the continuous LBT failure (event three) can be different.

S704: The terminal device cancels the third state of the terminal device.

Specifically, if the terminal device sends indication information to the network device, the terminal device cancels the third state of the terminal device.

Optionally, the terminal device sends the indication information to the network device, which can be specifically: the terminal device sends a MAC protocol data unit (PDU), and the MAC PDU includes a side link continuous LBT failure MAC CE. If the terminal device sends the indication information to the network device, it can be replaced by: if a MAC PDU is sent and the MAC PDU includes a side link continuous LBT failure MAC CE.

Since the third state of the terminal device is cancelled, the terminal device will no longer report indication information, thus saving signaling overhead.

Optionally, the resource determination method provided in this embodiment may further include:

If the third state of the terminal device is cancelled, the cumulative number of LBT failures of the first resource is set to 0.

By setting the cumulative number of LBT failures of the first resource to 0, it is used to detect whether continuous LBT failures are triggered on the first resource later.

It can be seen that the resource determination method provided in this embodiment is applicable to the scenario where the connected UE uses unlicensed spectrum and resource selection mode 2 for SL communication. The terminal device determines that the continuous LBT failure of the first resource is triggered, and the third state of the terminal device is triggered. If the first condition is met, the continuous LBT failure of the first resource is canceled. The first resource becomes an available resource only after a period of time after the first resource triggers continuous LBT failure, which improves the success rate of the UE performing LBT and ensures SL communication. If the third state of the terminal device is triggered, the terminal device sends an indication message to the network device and cancels the third state of the terminal device, so that the terminal device will no longer report the indication message, saving signaling overhead.

The effect of the resource determination method provided by this embodiment is described below in conjunction with Figure 8. Figure 8 is another schematic diagram of a connected UE detecting continuous LBT failures in mode 2 provided by an embodiment of the present application. The UE is specifically UE1.

As shown in Figure 8, UE1 determines that the continuous LBT failure of UE1's resource block set 1 is triggered, and the third state of UE1 is triggered. At this time, the first condition is not met, the continuous LBT failure of resource block set 1 will not be canceled, the SL resources corresponding to resource block set 1 are unavailable, and UE1 will not select the SL resources in resource block set 1. UE1 can select another resource block set 2 in the resource pool where no continuous LBT failure is detected for LBT. The third state of UE1 is triggered, and UE1 sends an indication message to base station 1, indicating that UE1 has detected a continuous LBT failure. When UE1 sends the indication message to base station 1, UE1 cancels the third state of UE1. Afterwards, if the first condition is met, UE1 cancels the continuous LBT failure of resource block set 1, the SL resources corresponding to resource block set 1 become available, and UE1 can select the SL resources corresponding to resource block set 1 for SL transmission.

In this embodiment, the third state of the terminal device is the third state of at least one first resource of the terminal device, which will be described in detail below.

Implementation method 1: the third state of the terminal device is the third state of the first resource of the terminal device, or the third state of the terminal device is the third state of one first resource among at least one first resource of the terminal device.

Specifically, the third state is associated with a resource (eg, a resource block set). If a resource meets the second condition or the third condition, the third state of the resource is triggered.

For example, the resource pool includes five resource block sets, labeled as resource block set 1 to resource block set 5. If resource block set 1 is If the corresponding cumulative number of LBT failures is equal to or greater than the maximum number of LBT failures, it is determined that the continuous LBT failure of resource block set 1 is triggered, and the third state of resource block set 1 is triggered. If continuous LBT failures are detected in resource block set 2, it is determined that the third state of resource block set 2 is triggered. If continuous LBT failures are triggered in resource block set 4, it is determined that the third state of resource block set 4 is triggered. In this example, the third state of resource block set 3 is not triggered, and the third state of resource block set 5 is not triggered.

Optionally, in S703, the terminal device sends the instruction information to the network device, which may include:

If the third state of the first resource of the terminal device is triggered and not cancelled, the terminal device sends an indication message to the network device.

Exemplarily, take the first resource as a resource block set (RB set) as an example. If the third state of at least one RB set is triggered and not cancelled, the UE reports to the base station a MAC CE indicating a sidelink continuous LBT failure (SL C-LBT failure MAC CE). If the third state of at least one RB set is triggered and not cancelled, if there are uplink resources available for new transmission, and these uplink resources can accommodate the SL C-LBT failure MAC CE plus its subheader, the multiplexing and assembly process is instructed to generate the SL C-LBT failure MAC CE, and then the generated SL C-LBT failure MAC CE is submitted to the lower layer to generate the transmission of the SL C-LBT failure MAC CE. For the generated SL C-LBT failure MAC CE, optionally, if the continuous LBT failure of a certain RB set is triggered and not cancelled, it is necessary to indicate in the SL C-LBT failure MAC CE that the RB set has experienced continuous LBT failure, for example, setting the bit corresponding to the RB set to 1; or, optionally, if the third state of a certain RB set is triggered and not cancelled, it is necessary to indicate in the SL C-LBT failure MAC CE that the RB set has experienced continuous LBT failure, for example, setting the bit corresponding to the RB set to 1.

Optionally, in S704, the terminal device canceling the third state of the terminal device may include:

If the terminal device sends an indication message to the network device, the terminal device cancels the third state of the first resource indicated by the indication message.

Optionally, if the third state of the terminal device is cancelled, setting the cumulative number of LBT failures of the first resource to 0 may include:

If the third state of the first resource of the terminal device is canceled, the cumulative number of LBT failures of the first resource indicated by the indication information is set to 0.

Take an example. The resource pool includes 5 resource block sets, marked as resource block set 1 to resource block set 5, and the third state of the 5 resource block sets are triggered. The indication information indicates that the first resources with continuous LBT failures are: resource block set 1, resource block set 4 and resource block set 5. Then, the UE sends an indication message to the network device, and the UE cancels the third state of resource block set 1, cancels the third state of resource block set 4, and cancels the third state of resource block set 5. If the third state of resource block set 1 is canceled, the UE sets the cumulative number of LBT failures of resource block set 1 to 0. If the third state of resource block set 4 is canceled, the UE sets the cumulative number of LBT failures of resource block set 4 to 0. If the third state of resource block set 5 is canceled, the UE sets the cumulative number of LBT failures of resource block set 5 to 0.

For example, in implementation mode 1, some description modes are as follows:

1>if LBT failure indication for an RB set has been received from lower layers:

2>start or restart the sl-lbt-FailureDetectionTimer for this RB set; (start/restart the LBT failure detection timer for this RB set)

2>increment SL_LBT_COUNTER for this RB set by 1; (the number of LBT failures recorded by the counter for this RB set is increased by 1)

2>if SL_LBT_COUNTER>＝sl-lbt-FailureInstanceMaxCount for this RB set:(if the LBT failure count of this RB set is greater than or equal to the maximum number of LBT failures)

3>trigger consistent LBT failure for this RB set; (trigger continuous LBT failure for this RB set)

3>trigger SL C-LBT failure reporting for this RB set. (trigger SL C-LBT failure reporting for this RB set)

1>if SL C-LBT failure reporting has been triggered, and not cancelled, for at least one RB set; and (if SL C-LBT failure reporting has been triggered, and not cancelled, for at least one RB set);

if UL-SCH resources are available for a new transmission and these UL-SCH resources can accommodate the SL C-LBT failure MAC CE plus its subheader as a result of logical channel prioritization:

2>instruct the Multiplexing and Assembly procedure to generate the SL C-LBT failure MAC CE. (Instruct the Multiplexing and Assembly process to generate the SL C-LBT failure MAC CE)

1>if a MAC PDU is transmitted and this PDU includes the SL C-LBT failure MAC CE: (if a MAC PDU is transmitted and this PDU includes the SL C-LBT failure MAC CE)

2>cancel all the triggered SL C-LBT failure reporting for which SL C-LBT failure was indicated in the transmitted SL C-LBT failure MAC CE.

1>if triggered SL C-LBT failure reporting are cancelled for an RB set; (if triggered SL C-LBT failure reporting are cancelled for an RB set)

2>set SL_LBT_COUNTER for this RB set to 0. (Set the LBT failure count of this RB set to 0)

Implementation method two: the third state of the terminal device is the third state of at least one first resource of the terminal device, or the third state of the terminal device is the third state of all first resources in the at least one first resource of the terminal device.

Specifically, the third state is not associated with a resource, but is associated with at least one resource for the terminal device. The third state is shared by at least one resource that triggers continuous LBT failure, or the third state is shared by all resources that trigger continuous LBT failure. If at least one resource meets the second condition or the third condition, the third state of the terminal device is triggered.

Take an example. The resource pool includes 5 resource block sets, marked as resource block set 1 to resource block set 5. If the cumulative number of LBT failures corresponding to resource block set 1 is equal to or greater than the maximum number of LBT failures, it is determined that the continuous LBT failure of resource block set 1 is triggered, and the third state of the terminal device is triggered. If continuous LBT failures are detected in resource block set 2, it is determined that the third state of the terminal device is triggered. If resource block set 4 triggers continuous LBT failures, it is determined that the third state of the terminal device is triggered. In this example, resource block set 1, resource block set 2 and resource block set 4 share the third state of the terminal device, so that the third state of the terminal device is triggered. Therefore, as long as the continuous LBT failure of one resource block set is triggered, the third state of the terminal device is triggered.

Optionally, in S703, the terminal device sends the instruction information to the network device, which may include:

If the third state of the terminal device is triggered and not cancelled, the terminal device sends an indication message to the network device.

Exemplarily, take the first resource as a resource block set (RB set) as an example. If the third state of the terminal device is triggered and not cancelled, the UE reports to the base station a MAC CE indicating a sidelink continuous LBT failure (SL C-LBT failure MAC CE). If the third state of the terminal device is triggered and not cancelled, if there are uplink resources available for new transmission, and these uplink resources can accommodate the SL C-LBT failure MAC CE plus its subheader, the multiplexing and assembly process is instructed to generate the SL C-LBT failure MAC CE, and then the generated SL C-LBT failure MAC CE is submitted to the lower layer to generate the transmission of the SL C-LBT failure MAC CE. For the generated SL C-LBT failure MAC CE, optionally, if the continuous LBT failure of a certain RB set is triggered and not canceled, it is necessary to indicate in the SL C-LBT failure MAC CE that the continuous LBT failure has occurred in the RB set, for example, by setting the corresponding bit of the RB set to 1; or, optionally, it is necessary to indicate in the SL C-LBT failure MAC CE all current RB sets that have experienced continuous LBT failures, for example, by setting the corresponding bit of the corresponding RB set to 1.

Optionally, in S704, the terminal device canceling the third state of the terminal device may include:

If the terminal device sends an indication message to the network device, the terminal device cancels the third state, or in other words, the terminal device cancels all third states.

Optionally, if the third state of the terminal device is cancelled, setting the cumulative number of LBT failures of the first resource to 0 may include:

If the third state of the terminal device is canceled, the cumulative number of LBT failures of all first resources in at least one first resource is set to 0, or the cumulative number of LBT failures of all first resources is set to 0. It should be noted that the indication information should indicate all the first resources that currently detect continuous LBT failures, so the cumulative number of LBT failures of all first resources can be set to 0.

Take an example. The resource pool includes 5 resource block sets, marked as resource block set 1 to resource block set 5, and the third states of resource block set 1, resource block set 4 and resource block set 5 are all triggered. The indication information indicates that the first resources with continuous LBT failures are: resource block set 1, resource block set 4 and resource block set 5. Then, the UE sends an indication message to the network device, and the UE cancels the third state of resource block set 1, resource block set 4, and resource block set 5. If the third state of the terminal device is canceled, the UE sets the cumulative number of LBT failures of resource block set 1 to 0, sets the cumulative number of LBT failures of resource block set 4 to 0, and the UE sets the cumulative number of LBT failures of resource block set 5 to 0.

For example, in the second implementation, some descriptions are as follows:

1>if LBT failure indication for an RB set has been received from lower layers:

2>start or restart the sl-lbt-FailureDetectionTimer for this RB set; (start/restart the LBT failure detection timer for this RB set)

2>increment SL_LBT_COUNTER for this RB set by 1; (the number of LBT failures recorded by the counter for this resource block set is increased by 1)

2>if SL_LBT_COUNTER>＝sl-lbt-FailureInstanceMaxCount for this RB set:(if the LBT failure count of this RB set is greater than or equal to the maximum number of LBT failures)

3>trigger consistent LBT failure for this RB set; (trigger continuous LBT failure for this RB set)

3>trigger SL C-LBT failure reporting. (trigger SL continuous LBT failure reporting)

1>if SL C-LBT failure reporting has been triggered,and not cancelled; and (if SL C-LBT failure reporting has been triggered, and not cancelled; and)

if UL-SCH resources are available for a new transmission and these UL-SCH resources can accommodate the SL C-LBT failure MAC CE plus its subheader as a result of logical channel prioritization:

2>instruct the Multiplexing and Assembly procedure to generate the SL C-LBT failure MAC CE. (Instruct the Multiplexing and Assembly process to generate the SL C-LBT failure MAC CE)

1>if a MAC PDU is transmitted and this PDU includes the SL C-LBT failure MAC CE:

2>cancel all the triggered SL C-LBT failure reporting.

1>if triggered SL C-LBT failure reporting are cancelled; (if triggered SL C-LBT failure reporting are cancelled)

2>set SL_LBT_COUNTER for all RB set to 0. (Set the number of LBT failures for all resource block sets to 0)

Figure 9 is another flow chart of a resource determination method provided in an embodiment of the present application. The resource determination method provided in this embodiment involves a terminal device and a network device, and is applicable to a scenario where a connected UE uses unlicensed spectrum and resource selection mode 2 for SL communication.

In this embodiment, it is considered that if the UE sends an indication message to the base station, the base station will respond to resume SL transmission, for example, by reconfiguring the resources that detected continuous LBT failures through RRC messages. If only one RB set detects continuous LBT failures and the UE has many other selectable RB sets, it is unnecessary to send an indication message to the base station at this time. The UE should first try to resume SL transmission by itself, that is, if the UE detects continuous LBT failures on one RB set, it can select other RB sets in the resource pool where no continuous LBT failures are detected. When the possibility of UE resuming SL transmission is reduced, for example, the number of currently selectable RB sets is limited or 0, it is necessary to send an indication message to the base station and rely on the base station to resume SL transmission.

The UE detects continuous LBT failures, and the subsequent steps involve: the terminal device cancels reporting indication information to the network device (event one), cancels the continuous LBT failure of the resource (event two), and recovers the resource that detects the continuous LBT failure (event three). In this embodiment, the time of event one and event three is the same. Event two is related to both event one and event three.

As shown in FIG. 9 , the resource determination method provided in this embodiment may include:

S901: If a first condition is met, the terminal device sends an indication message to the network device, the indication message being used to indicate that the terminal device has detected continuous LBT failures. The first condition includes: continuous LBT failures of the first resource are triggered and not cancelled, and the number of the first resource is greater than or equal to a preset threshold.

Among them, this embodiment does not limit the value of the preset threshold. For example, the preset threshold can be greater than or equal to 1 and less than or equal to the maximum number of configured RB sets. For example, the terminal device is configured with 2 resource pools, each resource pool includes 5 RB sets, and the maximum number of configured RB sets is 10. The value range of the preset threshold can be [1,10]. For example, the preset threshold is 1, 2, 5 or 10, and so on. When the preset threshold is equal to the maximum number of configured RB sets, it is equivalent to that all RB sets have triggered continuous LBT failures, and the UE will send indication information to the base station.

Optionally, the preset threshold may be configured by the base station or predefined by a protocol.

Optionally, the indication information indicates that at least one first resource detects continuous LBT failures.

Optionally, the continuous LBT failure of the first resource is triggered and not cancelled, which may include any one of the following: the continuous LBT failure of any first resource is triggered and not cancelled, or the continuous LBT failure of at least one first resource is triggered and not cancelled.

S902: The terminal device fails to cancel the continuous LBT of the first resource.

Specifically, if the terminal device sends an indication message to the network device, the terminal device fails to cancel the continuous LBT of the first resource.

Optionally, canceling the continuous LBT failure of the first resource may include: canceling the continuous LBT failure of the first resource indicated by the indication information.

It can be seen that in the resource determination method provided in this embodiment, the terminal device does not send indication information to the network device every time it detects continuous LBT failure on a resource, but sends indication information to the base station only when the first condition is met, thereby avoiding the first resource triggering continuous LBT. It becomes available immediately after failure, which prevents the terminal device from immediately reselecting the first resource for SL transmission, improves the success rate of UE performing LBT, ensures SL communication, and saves signaling overhead.

The effect of the resource determination method provided by this embodiment is described below in conjunction with Fig. 10. Assume that the maximum value of the number of configured resources is 2 and the preset threshold is 2. The UE is specifically UE1.

As shown in Figure 10, UE1 determines that the continuous LBT failure of resource block set 1 is triggered and not cancelled, determines that the continuous LBT failure of resource block set 2 is triggered and not cancelled, and the total number is equal to the preset threshold, and the first condition is met. All configured resources trigger continuous LBT failures, then UE1 sends an indication message to base station 1, indicating that UE1 has detected continuous LBT failures. UE1 sends an indication message to base station 1, and UE1 cancels the continuous LBT failure of resource block set 1 and the continuous LBT failure of resource block set 2. The SL resources corresponding to resource block set 1 and resource block set 2 become available, and UE1 can perform SL transmission using the SL resources corresponding to resource block set 1 and resource block set 2.

Optionally, the resource pool where the first resource is located is a resource pool with PSFCH resources.

In this implementation, the terminal device may be configured with a feedback-enabled logical channel or a feedback-disabled logical channel, and the terminal device may select the first resource of the resource pool with PSFCH resources.

Optionally, the terminal device is configured with a feedback-enabled logical channel.

In this implementation, the terminal device is configured with a feedback-enabled logical channel and can only select resources in a resource pool with PSFCH resources. Specifically, the first condition is: consecutive LBT failures of the first resource in the resource pool with PSFCH resources are triggered and not canceled, and the number of first resources is greater than or equal to a preset threshold. At this time, even if there are still many selectable resources in the UE's resource pool without PSFCH resources, the UE cannot use these resources to transmit data in the feedback-enabled logical channel. Therefore, the possibility of the UE resuming SL transmission only considers the number of RB sets in the resource pool with PSFCH resources.

Optionally, the resource pool where the first resource is located includes a resource pool with PSFCH resources and a resource pool without PSFCH resources.

In this implementation, the terminal device may be configured with a feedback-disabled logical channel, and the terminal device may select a first resource in a resource pool with PSFCH resources and a resource pool without PSFCH resources. Optionally, the terminal device is not configured with a feedback-enabled logical channel.

Optionally, based on the above embodiments, another embodiment of the present application provides a resource determination method.

In this embodiment, the base station may configure a method for processing consecutive LBT failures for a terminal device that is in a connected state and uses resource selection mode 2.

The method when the UE shown in FIG2B is in a connected state and uses resource selection mode 1 is referred to as mechanism 1. The method when the UE shown in FIG3B is in an idle state or an inactive state and uses resource selection mode 2 is referred to as mechanism 2. The resource determination method shown in FIG5 or FIG7 is referred to as mechanism 3. The resource determination method shown in FIG9 is referred to as mechanism 4.

Optionally, if the protocol supports mechanism 1 and mechanism 2, but the UE can only use one of the mechanisms at a time, the base station can configure the UE to use which mechanism. For example, if the base station wants to fully control the recovery of SL transmission, it can configure mechanism 1 for the UE, and the base station needs to use RRC reconfiguration messages more frequently; if the base station wants the UE to autonomously recover SL transmission and reduce the base station RRC reconfiguration messages, it can configure mechanism 2 for the UE, and the base station does not need the UE to send indication information.

Optionally, if the protocol supports one or more of Mechanism 1, Mechanism 2, Mechanism 3, and Mechanism 4, but the UE can only use one of the mechanisms at a time, the base station can configure the UE to use which mechanism, that is, the base station instructs the UE to use the mechanism.

Figure 13 is another flow chart of a resource determination method provided in an embodiment of the present application. The resource determination method provided in this embodiment involves a terminal device and a network device, and is applicable to (but not limited to) a scenario where a connected UE uses unlicensed spectrum and resource selection mode 2 for SL communication.

This embodiment is similar to the embodiments shown in FIG5 and FIG7 in that after the UE detects continuous LBT failures on a resource, the recovery of SL transmission depends on the terminal device. In the subsequent events involving the terminal device canceling the reporting of indication information to the network device (event one), canceling the continuous LBT failure of the resource (event two), and recovering the resource that detected the continuous LBT failure (event three), the time of event one and event three may be different.

The difference between this embodiment and the embodiment shown in FIG5 and the similarity with the embodiment shown in FIG7 is that in this embodiment, event 2 is related to event 3, and event 2 is not related to event 1. Specifically, in this embodiment, by setting the judgment condition, the terminal device reports or cancels the reporting indication information to the network device.

As shown in FIG. 13 , the resource determination method provided in this embodiment may include:

S1301: The terminal device determines that a continuous LBT failure of a first resource of the terminal device is triggered and not cancelled, and that indication information has not been generated, wherein the indication information is used to indicate that the terminal device has detected a continuous LBT failure.

The UE performs LBT on the first resource, that is, performs LBT on the SL resource in the first resource, and determines that continuous LBT failures are detected on the first resource. Optionally, the first resource may be a resource block set. Continuous LBT failures can be understood as an event or a state, at which point the UE determines that continuous LBT failures of the first resource of the terminal device are triggered and not canceled.

The terminal device also needs to determine whether the indication information has been generated. Specifically, if the continuous LBT failure of the first resource of the terminal device is triggered and not canceled, and the indication information has not been generated (that is, the sidelink continuous LBT failure MAC CE has not been generated), the terminal device may generate the indication information (that is, generate the sidelink continuous LBT failure MAC CE). That is, if the continuous LBT failure of the first resource of the terminal device is triggered and not canceled, and the indication information has been generated (that is, the condition of "the indication information has not been generated") is not met, the terminal device will not generate the indication information. Therefore, if the continuous LBT failure of the first resource of the terminal device is triggered and not canceled, the terminal device may only report the indication information once at most, so that the terminal device no longer sends the indication information repeatedly.

S1302. The terminal device sends instruction information to the network device.

Correspondingly, the network device receives the indication information sent by the terminal device.

Specifically, if the continuous LBT failure of the first resource of the terminal device is triggered and not cancelled, and the indication information has not been generated, the terminal device sends the indication information to the network device to notify the network device of the resource that triggered the continuous LBT failure.

Optionally, the indication information indicates that at least one first resource detects continuous LBT failures.

The indication information may refer to the relevant description of S202 in FIG. 2B , which will not be repeated here.

S1303: If the first condition is met, canceling the continuous LBT failure of the first resource.

Optionally, the first condition may be: the first timer of the first resource times out. The first timer of the first resource is started when the first resource detects continuous LBT failures. During the operation of the first timer of the first resource, the side link resource corresponding to the first resource is not available (i.e., not selectable). It should be noted that if the first resource detects continuous LBT failures and the first timer of the first resource is not in operation, the first timer of the first resource is started.

Optionally, the first timer is the SL-LBT recovery timer sl-LBT-RecoveryTimer defined in chapter 5.31 of the 3GPP TS 38.321 protocol.

Optionally, the implementation method of the first condition may also refer to the relevant description in the embodiment shown in FIG. 5 or FIG. 7 , which will not be repeated here.

In the resource determination method provided in this embodiment, the condition for the terminal device to send the indication information to the network device is that the continuous LBT failure of the first resource of the terminal device is triggered and has not been cancelled and the indication information has not been generated, and the condition for the terminal device to cancel the triggered continuous LBT failure of the first resource is to meet the first condition. The two conditions are different, so that the time for the terminal device to cancel the reporting of the indication information to the network device (event one) and the time for the recovery of the resource that detects the continuous LBT failure (event three) can be different. Through the first condition, the first resource becomes an available resource only after a period of time after the first resource triggers the continuous LBT failure, which improves the success rate of the UE performing LBT and ensures SL communication. Moreover, if the continuous LBT failure of the first resource of the terminal device is triggered and has not been cancelled, the terminal device may only report the indication information once at most, so that the terminal device no longer repeatedly sends the indication information, saving signaling overhead.

Exemplarily, the resource determination method provided in this embodiment is described as follows (wherein the first timer is the SL-LBT recovery timer sl-LBT-RecoveryTimer):

1>if SL consistent LBT failure has been triggered, and not cancelled, in the RB set(s), and SL LBT failure MAC CE(s)has not been generated; (If SL consistent LBT failure has been triggered, and not cancelled, in the RB set(s), and SL LBT failure MAC CE(s)has not been generated;)

2>if the sl-LBT-RecoveryTimer for the triggered SL consistent LBT failure is not running:(if the sl-LBT-RecoveryTimer for the triggered SL consistent LBT failure is not running:)

3>start the sl-LBT-RecoveryTimer. (Start the SL-LBT recovery timer.)

2>if UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the SL LBT failure MAC CE plus its subheader as a result of logical channel prioritization: (If UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the SL LBT failure MAC CE plus its subheader as a result of logical channel prioritization:)

3>instruct the Multiplexing and Assembly procedure to generate the SL LBT failure MAC CE(s). (instruct the Multiplexing and Assembly process to generate the SL LBT failure MAC CE)

2>else: (otherwise:)

3>trigger a Scheduling Request for SL LBT failure MAC CE. (Trigger a Scheduling Request for SL LBT failure MAC CE.)

1>if the sl-LBT-RecoveryTimer for the triggered SL consistent LBT failure(s)expires: The SL-LBT recovery timer corresponding to the LBT failure has timed out;)

2>cancel the triggered SL consistent LBT failure(s) in RB set(s) for which SL consistent LBT failure was detected.

The effect of the resource determination method provided in this embodiment is exemplarily illustrated below in conjunction with FIG14. FIG14 is another schematic diagram of a connected UE detecting continuous LBT failures in mode 2 provided in an embodiment of the present application. Exemplarily, the first condition is: the first timer of the first resource times out. The first timer of the first resource is started when the first resource detects continuous LBT failures.

As shown in FIG14 , the terminal device detects continuous LBT failure on RB set 1, determines that the continuous LBT failure of RB set 1 is triggered and not cancelled, and judges that "the indication information has not been generated", and considers that the condition is met. The terminal device starts the first timer corresponding to RB set 1. Moreover, when there are available uplink resources for new transmission, and the uplink resources can carry the sidelink continuous LBT failure MAC CE and its subheader, the terminal device generates indication information and submits the indication information to the physical layer for transmission, so as to send the indication information to the network device. During the operation of the first timer corresponding to RB set 1, the continuous LBT failure of RB set 1 is still in the state of "triggered and not cancelled", RB set 1 is an unavailable resource, and the terminal device will not select RB set 1 for LBT, thereby improving the success rate of LBT of the terminal device, and will not report the indication information repeatedly, saving signaling overhead. When the first timer corresponding to RB set 1 times out, the terminal device cancels the continuous LBT failure of RB set 1, RB set 1 is restored to an available resource, and the terminal device can select RB set 1 for LBT.

Subsequently, as shown in FIG14 , the terminal device detects continuous LBT failures on RB set 2, determines that the continuous LBT failures of RB set 2 are triggered and not cancelled, and the terminal device should start the first timer corresponding to RB set 2. At this time, the terminal device determines that "the indication information has been generated" and believes that the conditions are not met, so the terminal device will not generate the indication information, resulting in the terminal device being unable to indicate the continuous LBT failures of RB set 2 to the network device. Even more, the terminal device determines that "the indication information has been generated" and believes that the conditions are not met, and the terminal device will not start the first timer corresponding to RB set 2, resulting in the resource in the failed RB set 2 being selected all the time, increasing the probability of transmission failure.

Similarly, later, as shown in FIG14 , the terminal device detects continuous LBT failures on RB set 1 again, and determines that the continuous LBT failures of RB set 1 are triggered and not cancelled, and the terminal device should start the first timer corresponding to RB set 1. At this time, the terminal device determines that "the indication information has been generated" and believes that the conditions are not met, so the terminal device will not generate the indication information, resulting in the terminal device being unable to indicate to the network device the continuous LBT failures detected again on RB set 1. Even more, the terminal device determines that "the indication information has been generated" and believes that the conditions are not met, and the terminal device will not start the first timer corresponding to RB set 1, resulting in the resource in the failed RB set 1 being selected all the time, increasing the probability of transmission failure.

To sum up, although the resource determination method provided in this embodiment can solve the problem of the terminal device repeatedly sending indication information, it will cause the indication information that needs to be sent to fail to be sent (for example, the continuous LBT failure of RB set 2 and the continuous LBT failure of RB set 1 in Figure 14), resulting in the network device being unable to obtain the continuous LBT failure information of the side link resources of the terminal device.

Figure 15 is another flow chart of a resource determination method provided in an embodiment of the present application. The resource determination method provided in this embodiment involves a terminal device and a network device, and is applicable to (but not limited to) a scenario where a connected UE uses unlicensed spectrum and uses resource selection mode 2 for SL communication.

The present embodiment is similar to the embodiments shown in FIG5 , FIG7 and FIG13 in that after the UE detects continuous LBT failures on a resource, the recovery of SL transmission depends on the terminal device. In the subsequent events involving the terminal device canceling the reporting of indication information to the network device (event one), canceling the continuous LBT failure of the resource (event two), and recovering the resource that detected the continuous LBT failure (event three), the time of event one and event three may be different.

The difference between this embodiment and the embodiment shown in FIG. 5 and the similarity with the embodiments shown in FIG. 7 and FIG. 13 is that in this embodiment, event two is related to event three, and event two is unrelated to event one.

In this embodiment, by setting reasonable judgment conditions, the terminal device can report or cancel the reporting of indication information to the network device, which solves the problem of repeatedly reporting indication information after detecting continuous LBT failures, and also solves the problem that the indication information that needs to be sent cannot be sent as shown in Figure 14.

As shown in FIG. 15 , the resource determination method provided in this embodiment may include:

S1501, the terminal device determines that the continuous LBT failure of the first resource of the terminal device is triggered and not cancelled, and the indication information corresponding to the first resource has not been generated or sent. The indication information is used to indicate that the terminal device has detected the continuous LBT failure.

The UE performs LBT based on the granularity of the first resource. Optionally, the first resource may be a resource block set, and the frequency range may be 20 MHz. The first resource may also be a resource of other granularity, such as a resource pool, a frequency range of 10 MHz, etc.

The UE performs LBT on the first resource, that is, performs LBT on the SL resource in the first resource, and determines that a connection is detected on the first resource. Continuous LBT failure. Continuous LBT failure can be understood as an event or a state, at which time, the UE determines that the continuous LBT failure of the first resource of the terminal device is triggered and has not been cancelled.

Among them, continuous LBT failure is used to indicate that the side link resource corresponding to the first resource is unavailable (i.e., not selectable). That is to say, if the continuous LBT failure of the first resource is triggered and not cancelled, the SL resource corresponding to the first resource is unavailable (i.e., not selectable). If the continuous LBT failure of the first resource is not triggered, or is triggered but cancelled, the SL resource corresponding to the first resource is available (i.e., selectable).

Since the continuous LBT failure of the first resource is triggered and not canceled, the SL resource corresponding to the first resource is unavailable. Therefore, the UE selects another resource in the resource pool that has not detected the continuous LBT failure (the continuous LBT failure has not been triggered, or has been triggered but canceled) for LBT, instead of selecting the first resource. This avoids selecting the first resource for LBT again after the continuous LBT failure is triggered by the first resource, thereby improving the success rate of the UE's LBT and ensuring SL communication.

Optionally, if the continuous LBT failure of the first resource is triggered and not cancelled, and the first timer is not in operation: the terminal device starts the first timer of the first resource. Alternatively, if the continuous LBT failure of the first resource is triggered and not cancelled, and the first timer is not in operation, and the indication information corresponding to the first resource has not been generated or sent: the terminal device starts the first timer of the first resource. During the operation of the first timer of the first resource, the side link resource corresponding to the first resource is not available (i.e., not selectable).

Optionally, the first timer is the SL-LBT recovery timer sl-LBT-RecoveryTimer defined in chapter 5.31 of the 3GPP TS 38.321 protocol.

Optionally, the number of the first resource may be at least one.

Optionally, the UE determines that continuous LBT failure of the first resource is triggered, which may include any one of the following: continuous LBT failure of a certain first resource is triggered, continuous LBT failure of any first resource is triggered, continuous LBT failure of at least one first resource is triggered, or, whenever a continuous LBT failure of a first resource is triggered.

The terminal device also needs to determine whether the indication information corresponding to the first resource has been generated or sent (i.e., whether the sidelink continuous LBT failure MAC CE corresponding to the first resource has been generated or sent). If the continuous LBT failure of the first resource is triggered and not canceled, and the indication information corresponding to the first resource has not been generated or sent, the terminal device may generate indication information (i.e., generate the sidelink continuous LBT failure MAC CE). That is, if the continuous LBT failure of the first resource is triggered and not canceled, and the indication information corresponding to the first resource has been generated or sent, the terminal device will not generate the indication information. Therefore, if the continuous LBT failure of the first resource is triggered and not canceled, the terminal device may only report the indication information once at most, so that the terminal device no longer sends the indication information repeatedly. Moreover, by limiting it to "the indication information corresponding to the first resource", it will not affect the generation and sending of the indication information of other resources except the first resource, thus avoiding the problem that the indication information that needs to be sent corresponding to other resources except the first resource cannot be sent.

Optionally, the indication information corresponding to the first resource has not been generated, that is, the indication information indicating the continuous LBT failure of the first resource has not been generated, that is, the indication information has not been generated, and the indication information indicates or includes the information of the continuous LBT failure of the first resource. Or, optionally, the indication information corresponding to the first resource has not been sent, that is, the indication information indicating the continuous LBT failure of the first resource has not been sent, that is, the indication information has not been sent, and the indication information indicates or includes the information of the continuous LBT failure of the first resource. Optionally, the indication information is the sidelink continuous LBT failure MAC CE.

S1502: If the first condition is met, the terminal device fails to cancel the continuous LBT of the first resource, and the indication information corresponding to the first resource has not been generated or sent.

Specifically, if the continuous LBT failure of the first resource of the terminal device is triggered and not canceled, and the first condition is met, the terminal device cancels the continuous LBT failure of the first resource. At the same time, the indication information corresponding to the first resource has not been generated or sent, that is, the terminal device believes that the indication information corresponding to the first resource has not been generated or sent.

Specifically, if the terminal device cancels the continuous LBT failure of the triggered first resource, it means that the first resource has triggered the continuous LBT failure but has been canceled, and the first resource has become an available resource, and the UE can select the first resource for SL transmission. The condition for the terminal device to cancel the continuous LBT failure of the first resource triggered is "the continuous LBT failure of the first resource of the terminal device is triggered and the first condition is met", wherein the continuous LBT failure is used to indicate that the side link resource corresponding to the first resource is unavailable. Since it takes a certain amount of time to meet the first condition, it is ensured that the first resource will not immediately become an available resource after triggering the continuous LBT failure, but will become an available resource after a certain period of time, thereby avoiding the possibility that the UE may immediately select the first resource for SL transmission after the continuous LBT failure is triggered by the first resource, thereby improving the success rate of the UE performing LBT and ensuring SL communication.

Optionally, the first condition may be: a first timer of the first resource times out, wherein the first timer of the first resource is started when the first resource detects continuous LBT failures.

After the UE detects continuous LBT failures on the first resource, it needs to exclude the resource triggered by the continuous LBT failure when selecting resources, and select SL resources from other resources (where the continuous LBT failure is not triggered, or is triggered but cancelled). SL resources can be selected for SL transmission from the resource block set with continuous LBT failure (i.e., the resource block set that triggered the continuous LBT failure). SL resources can only be selected for SL transmission from the resource block set in which no continuous LBT failure is detected (i.e., the resource block set that did not trigger the continuous LBT failure, or the resource block set in which the triggered continuous LBT failure has been canceled).

Optionally, the implementation method of the first condition may also refer to the relevant description in the embodiment shown in FIG. 5 or FIG. 7 , which will not be repeated here.

The indication information corresponding to the first resource has not been generated or sent, which can be understood as an event or a state or an action performed by the terminal device. Specifically, the terminal device believes that the indication information corresponding to the first resource has not been generated or sent, which can be understood as the terminal device sets the indication information corresponding to the first resource to have not been generated or sent, and then the terminal device determines the condition of "the indication information corresponding to the first resource has not been generated or sent", and then it is considered that the condition is met.

It should be noted that when the terminal device determines that the first condition is met, the terminal device may have generated or sent the indication information corresponding to the first resource, or may not have generated or sent the indication information corresponding to the first resource. Specifically, when there is an available uplink resource for new transmission, and the uplink resource can carry the sidelink continuous LBT failure MAC CE and its subheader, the terminal device can generate and send the indication information. Regardless of whether the terminal device generates or sends the indication information at this time, when the first condition is met, the terminal device cancels the continuous LBT failure of the first resource, and the indication information corresponding to the first resource has not been generated or sent. Subsequently, when the terminal device detects the continuous LBT failure of the first resource again, when judging whether the condition of "the indication information corresponding to the first resource has not been generated or sent" is met, it will be determined that the condition is met, and it will not affect the terminal device sending the indication information corresponding to the first resource again. Among them, the first resource that subsequently detects the continuous LBT failure can be a resource that has previously detected the continuous LBT failure but has canceled the continuous LBT failure, or it can be a resource that has not previously detected the continuous LBT failure.

By introducing "the indication information corresponding to the first resource has not been generated or sent", the subsequent generation and sending of indication information of the first resource will not be affected, thereby avoiding the problem that the indication information corresponding to the first resource that needs to be sent cannot be sent.

It can be seen that the resource determination method provided in this embodiment is applicable to (but not limited to) scenarios in which connected UEs use unlicensed spectrum and resource selection mode 2 for SL communication. The condition for the terminal device to send indication information to the network device is that the continuous LBT failure of the first resource of the terminal device is triggered and has not been canceled and the indication information of the first resource has not been generated or sent, and the condition for the terminal device to cancel the triggered continuous LBT failure of the first resource is to meet the first condition. The two conditions are different, so that the time for the terminal device to cancel reporting the indication information to the network device (event one) and the time for detecting the recovery of the resource of the continuous LBT failure (event three) may be different. Through the first condition, the first resource becomes an available resource only after the first resource triggers the continuous LBT failure and a period of time has passed, which improves the success rate of the UE performing LBT and ensures SL communication. Moreover, by judging whether the condition of "the indication information corresponding to the first resource has not been generated or sent" is met, when the continuous LBT failure of the first resource of the terminal device is triggered and not canceled, the terminal device may only report the indication information once at most, which saves signaling overhead and will not affect the subsequent generation and sending of the indication information of the first resource. Therefore, the network device can obtain the continuous LBT failure information of the side link resources of the terminal device and perform reasonable resource configuration processing on the terminal device.

Optionally, the resource determination method provided in this embodiment may further include:

S1503. The terminal device sends instruction information to the network device.

Correspondingly, the network device receives the indication information sent by the terminal device.

Specifically, if the terminal device has not generated or sent indication information corresponding to the first resource, when there is an available uplink resource for new transmission and the uplink resource can carry the sidelink continuous LBT failure MAC CE and its subheader, the terminal device sends indication information to the network device to notify the network device to trigger the resource of continuous LBT failure. It should be understood that if the terminal device has not generated or sent indication information corresponding to a certain resource, the terminal device needs to send indication information to the network device until the terminal device has generated or sent indication information corresponding to the resource once. If the terminal device has generated or sent indication information corresponding to a certain resource, even if the continuous LBT failure of the first resource of the terminal device is still "triggered and not canceled", the terminal device will not send indication information to the network device.

Optionally, the indication information indicates that at least one first resource detects continuous LBT failures.

Optionally, the indication information indicates the continuous LBT failure information corresponding to the resource that currently detects the continuous LBT failure.

Optionally, the terminal device sends an indication message to the network device, which can be specifically: the terminal device sends a MAC PDU, and the MAC PDU includes a MAC CE indicating a continuous LBT failure of the side link. If the terminal device sends an indication message to the network device, it can be replaced by: if a MAC PDU is sent and the MAC PDU includes a MAC CE indicating a continuous LBT failure of the side link.

The indication information may refer to the relevant description of S202 in FIG. 2B , which will not be repeated here.

Optionally, after receiving the indication information, the network device may not perform subsequent resource configuration processing, and the UE may resume SL transmission. For example, if the network device finds that the UE still has sufficient side link resources and does not detect continuous LBT failures, the resource pool of the UE may not be reconfigured. Of course, if the network device finds that the UE does not have sufficient available side link resources, the resource pool of the UE may be reconfigured, and this application does not limit this.

In this embodiment, the condition for the terminal device to send indication information to the network device takes into account "the terminal device has not generated or sent indication information corresponding to the first resource", and the condition for the terminal device to cancel the triggering of the continuous LBT failure of the first resource is to meet the first condition. The two conditions are different, so that the time for the terminal device to cancel the reporting of indication information to the network device (event one) and the time for detecting the recovery of the resource of the continuous LBT failure (event three) can be different.

Optionally, if the terminal device sends indication information corresponding to the first resource to the network device (ie, S1503 is executed), in S1502, the indication information corresponding to the first resource has not been generated or sent, and may include:

The terminal device believes that the indication information corresponding to the first resource has not been generated or sent.

Specifically, if the terminal device has sent the indication information corresponding to the first resource to the network device before determining that the first condition is met, then the terminal device executes the step of: considering that the indication information corresponding to the first resource has not been generated or sent; otherwise, the terminal device does not execute the step of: considering that the indication information corresponding to the first resource has not been generated or sent. Only when the terminal device has sent the indication information corresponding to the first resource to the network device, will it be considered that the condition "the indication information corresponding to the first resource has not been generated or sent" is not met when judging the condition, resulting in the terminal device not sending the indication information corresponding to the first resource again; and when the terminal device has not sent the indication information corresponding to the first resource to the network device, the terminal device will originally consider that the condition "the indication information corresponding to the first resource has not been generated or sent" is met when judging the condition, which will not affect the terminal device sending the indication information corresponding to the first resource again.

Exemplarily, some descriptions are as follows (wherein the first timer is the SL-LBT recovery timer sl-LBT-RecoveryTimer):

1>if SL consistent LBT failure has been triggered, and not cancelled, in the RB set(s), and SL LBT failure MAC CE(s) for the RB set(s)has not been generated; (If SL consistent LBT failure has been triggered, and not cancelled, in the RB set(s), and SL LBT failure MAC CE(s) for the RB set(s)has not been generated;)

2>if the sl-LBT-RecoveryTimer for the triggered SL consistent LBT failure is not running:(if the sl-LBT-RecoveryTimer for the triggered SL consistent LBT failure is not running:)

3>start the sl-LBT-RecoveryTimer. (Start the SL-LBT recovery timer.)

2>if UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the SL LBT failure MAC CE plus its subheader as a result of logical channel prioritization: (If UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the SL LBT failure MAC CE plus its subheader as a result of logical channel prioritization:)

3>instruct the Multiplexing and Assembly procedure to generate the SL LBT failure MAC CE(s). (instruct the Multiplexing and Assembly process to generate the SL LBT failure MAC CE)

2>else: (otherwise:)

3>trigger a Scheduling Request for SL LBT failure MAC CE. (Trigger a Scheduling Request for SL LBT failure MAC CE.)

1>if the sl-LBT-RecoveryTimer for the triggered SL consistent LBT failure(s)expires:(if the sl-LBT-RecoveryTimer for the triggered SL consistent LBT failure(s)expires:)

2>cancel the triggered SL consistent LBT failure(s) in RB set(s) for which SL consistent LBT failure was detected.

2>consider SL LBT failure MAC CE(s) for the RB set(s) has not been generated. (It is considered that the indication information corresponding to the first resource has not been generated or sent.)

The effect of the resource determination method provided in this embodiment is exemplarily described below in conjunction with Figure 16. Figure 16 is another schematic diagram of a connected UE detecting continuous LBT failures in mode 2 provided in an embodiment of the present application. Exemplarily, the first condition is: the first timer of the first resource times out, and the first timer is started when the first state of the first resource is triggered.

As shown in Figure 16, the terminal device detects continuous LBT failure on RB set 1, determines that the continuous LBT failure of RB set 1 is triggered and not cancelled, and judges that "the indication information corresponding to RB set 1 has not been generated or sent", and considers that the condition is met. The terminal device starts the first timer corresponding to RB set 1. Moreover, when there are available uplink resources for new transmission, and the uplink resources can carry the side link continuous LBT failure MAC CE and its subheader, the terminal device generates indication information, and submits the indication information to the physical layer for transmission, so as to send the indication information to the network device. During the operation of the first timer corresponding to RB set 1, the continuous LBT failure of RB set 1 is still in the state of "triggered and not cancelled", RB set 1 is an unavailable resource, and the terminal device will not select RB set 1 for LBT, thereby improving the success rate of LBT of the terminal device, and will not repeatedly report the indication information, saving signaling overhead. When the first timer corresponding to RB set 1 times out, the terminal device cancels the continuous LBT failure of RB set 1, RB set 1 is restored as an available resource, and the terminal device can select RB set 1 for LBT. In addition, the terminal device considers that the indication information corresponding to RB set 1 has not been generated or If a continuous LBT failure is detected again on RB set 1 later, it will be considered that the condition of "the indication information corresponding to RB set 1 has not been generated or sent" is met.

Subsequently, as shown in FIG16 , the terminal device detects continuous LBT failure on RB set 2, determines that the continuous LBT failure of RB set 2 is triggered and not cancelled, and judges that "the indication information corresponding to RB set 2 has not been generated or sent", and considers that the condition is met. The terminal device starts the first timer corresponding to RB set 2. When there are available uplink resources for new transmission, and the uplink resources can carry the sidelink continuous LBT failure MAC CE and its subheader, the terminal device generates indication information and submits the indication information to the physical layer for transmission, so as to send the indication information to the network device. During the operation of the first timer corresponding to RB set 2, the continuous LBT failure of RB set 2 is still in the state of "triggered and not cancelled", RB set 2 is an unavailable resource, and the terminal device will not select RB set 2 for LBT, thereby improving the success rate of LBT of the terminal device. When the first timer corresponding to RB set 2 times out, the terminal device cancels the continuous LBT failure of RB set 2 and considers that the indication information corresponding to RB set 2 has not been generated or sent. It can be seen that the continuous LBT failure previously detected on RB set 1 does not affect the sending of the indication information corresponding to the continuous LBT failure of RB set 2.

Subsequently, similarly, as shown in FIG16 , the terminal device detects continuous LBT failures on RB set 1 again, determines that the continuous LBT failures of RB set 1 are triggered and not cancelled, and judges that “the indication information corresponding to RB set 1 has not been generated or sent”, and considers that the conditions are met, and can send indication information to the network device. It can be seen that the continuous LBT failures previously detected on RB set 1 and the continuous LBT failures detected on RB set 2 do not affect the sending of the indication information corresponding to the continuous LBT failures detected again on RB set 1.

Figure 17 is another flow chart of a resource determination method provided in an embodiment of the present application. The resource determination method provided in this embodiment involves a terminal device and a network device, and is applicable to (but not limited to) a scenario where a connected UE uses unlicensed spectrum and uses resource selection mode 2 for SL communication.

The present embodiment is similar to the embodiments shown in FIG. 5 , FIG. 7 , FIG. 13 and FIG. 15 in that after the UE detects continuous LBT failures on a resource, the recovery of SL transmission depends on the terminal device. In the subsequent events involving the terminal device canceling the reporting of indication information to the network device (event one), canceling the continuous LBT failure of the resource (event two), and recovering the resource that detected the continuous LBT failure (event three), the time of event one and event three may be different.

The difference between this embodiment and the embodiment shown in FIG. 5 and the similarity with the embodiments shown in FIG. 7 , FIG. 13 , and FIG. 15 is that in this embodiment, event two is related to event three, and event two is unrelated to event one.

In this embodiment, by setting reasonable judgment conditions, the terminal device can report or cancel the reporting of indication information to the network device, which solves the problem of repeatedly reporting indication information after detecting continuous LBT failures, and also solves the problem that the indication information that needs to be sent cannot be sent as shown in Figure 14.

As shown in FIG. 17 , the resource determination method provided in this embodiment may include:

S1701. The terminal device determines that a continuous LBT failure of a first resource of the terminal device is triggered and has not been cancelled, and that no indication information has been generated or sent since the last continuous LBT failure corresponding to the first resource was triggered. The indication information is used to indicate that the terminal device has detected a continuous LBT failure.

The UE performs LBT based on the granularity of the first resource. Optionally, the first resource may be a resource block set, and the frequency range may be 20 MHz. The first resource may also be a resource of other granularity, such as a resource pool, a frequency range of 10 MHz, etc.

The UE performs LBT on the first resource, that is, performs LBT on the SL resource in the first resource, and determines that continuous LBT failure is detected on the first resource. Continuous LBT failure can be understood as an event or a state, at which time, the UE determines that the continuous LBT failure of the first resource of the terminal device is triggered and not cancelled.

Among them, continuous LBT failure is used to indicate that the side link resource corresponding to the first resource is unavailable (i.e., not selectable). That is to say, if the continuous LBT failure of the first resource is triggered and not cancelled, the SL resource corresponding to the first resource is unavailable (i.e., not selectable). If the continuous LBT failure of the first resource is not triggered, or is triggered but cancelled, the SL resource corresponding to the first resource is available (i.e., selectable).

Since the continuous LBT failure of the first resource is triggered and not canceled, the SL resource corresponding to the first resource is unavailable. Therefore, the UE selects another resource in the resource pool where no continuous LBT failure is detected (the continuous LBT failure is not triggered, or is triggered but canceled) for LBT, instead of selecting the first resource. This avoids selecting the first resource for LBT again after the continuous LBT failure is triggered by the first resource, thereby improving the success rate of the UE's LBT and ensuring SL communication.

Optionally, if the continuous LBT failure of the first resource is triggered and not cancelled, and the first timer is not in operation: the terminal device starts the first timer of the first resource. Alternatively, if the continuous LBT failure of the first resource is triggered and not cancelled, and the first timer is not in operation, and the indication information corresponding to the first resource has not been generated or sent: the terminal device starts the first timer of the first resource. Alternatively, if the continuous LBT failure of the first resource is triggered and not cancelled, and the first timer is not in operation: the terminal device starts the first timer of the first resource. During the process of the first resource, and since the last consecutive LBT failure corresponding to the first resource was triggered, the indication information has not been generated or sent: the terminal device starts a first timer for the first resource. During the operation of the first timer for the first resource, the side link resource corresponding to the first resource is not available (i.e., not selectable).

Optionally, the first timer is the SL-LBT recovery timer sl-LBT-RecoveryTimer defined in chapter 5.31 of the 3GPP TS 38.321 protocol.

Optionally, the number of the first resource may be at least one.

Optionally, the UE determines that continuous LBT failure of the first resource is triggered, which may include any one of the following: continuous LBT failure of a certain first resource is triggered, continuous LBT failure of any first resource is triggered, continuous LBT failure of at least one first resource is triggered, or, whenever a continuous LBT failure of a first resource is triggered.

The terminal device also needs to determine whether the indication information has been generated or sent (i.e., the sidelink continuous LBT failure MAC CE has not been generated or sent). Optionally, since the last continuous LBT failure corresponding to the first resource was triggered, the indication information has not been generated or sent. It can be understood that the judgment of "whether the indication information has been generated or sent" starts from the last continuous LBT failure corresponding to the first resource being triggered, that is, only the time period when and after the last continuous LBT failure corresponding to the first resource is triggered is judged, and there is no need to judge the time period before the last continuous LBT failure corresponding to the first resource is triggered. In this way, after a certain continuous LBT failure corresponding to a certain resource is triggered, the terminal device will only generate or send the corresponding indication information once at most, and the continuous LBT failure of other resources and the continuous LBT failure at other times will not affect the indication information of this (i.e., the most recent) continuous LBT failure, and the terminal device will definitely have the opportunity to generate or send the corresponding indication information once. Optionally, the most recent continuous LBT failure is the last continuous LBT failure. Optionally, the indication information is the sidelink continuous LBT failure MAC CE.

By limiting the time information of "since the most recent continuous LBT failure corresponding to the first resource was triggered", the terminal device will have the opportunity to generate or send corresponding indication information once for a certain continuous LBT failure corresponding to a certain resource, and will only generate or send the corresponding indication information once at most, avoiding the problem that the indication information that needs to be sent cannot be sent.

S1702: If the first condition is met, the terminal device fails to cancel the continuous LBT of the first resource.

Specifically, if the continuous LBT failure of the first resource of the terminal device is triggered and not cancelled, and the first condition is met, the terminal device cancels the continuous LBT failure of the first resource.

Specifically, if the terminal device cancels the continuous LBT failure of the triggered first resource, it means that the first resource has triggered the continuous LBT failure but has been canceled, and the first resource has become an available resource, and the UE can select the first resource for SL transmission. The condition for the terminal device to cancel the continuous LBT failure of the first resource triggered is "the continuous LBT failure of the first resource of the terminal device is triggered and the first condition is met", wherein the continuous LBT failure is used to indicate that the side link resource corresponding to the first resource is unavailable. Since it takes a certain amount of time to meet the first condition, it is ensured that the first resource will not immediately become an available resource after triggering the continuous LBT failure, but will become an available resource after a certain period of time, thereby avoiding the possibility that the UE may immediately select the first resource for SL transmission after the continuous LBT failure is triggered by the first resource, thereby improving the success rate of the UE performing LBT and ensuring SL communication.

Optionally, the first condition may be: a first timer of the first resource times out, wherein the first timer of the first resource is started when the first resource detects continuous LBT failures.

After the UE detects continuous LBT failures on the first resource, it needs to exclude the resources where the continuous LBT failures are triggered when selecting resources, and select SL resources from other resources (where the continuous LBT failures are not triggered, or are triggered but cancelled). The UE cannot select SL resources for SL transmission in the resource block set where continuous LBT failures are detected (i.e., the resource block set where continuous LBT failures are triggered), and can only select SL resources for SL transmission in the resource block set where continuous LBT failures are not detected (i.e., the resource block set where continuous LBT failures are not triggered, or the resource block set where the triggered continuous LBT failures have been cancelled).

Optionally, the implementation method of the first condition may also refer to the relevant description in the embodiment shown in FIG. 5 or FIG. 7 , which will not be repeated here.

It should be noted that when the terminal device determines that the first condition is met, the terminal device may have generated or sent the indication information, or may not have generated or sent the indication information. Specifically, when there is an available uplink resource for new transmission, and the uplink resource can carry the sidelink continuous LBT failure MAC CE and its subheader, the terminal device can generate and send the indication information. Regardless of whether the terminal device generates or sends the indication information at this time, when the first condition is met, the terminal device cancels the continuous LBT failure of the first resource, and the first resource becomes an available resource. Subsequently, when the terminal device detects the continuous LBT failure of the first resource again, it determines that the indication information has not been generated or sent since the most recent continuous LBT failure corresponding to the first resource was triggered. Among them, the first resource that subsequently detects the continuous LBT failure can be a resource that has previously detected the continuous LBT failure but has canceled the continuous LBT failure, or it can be a resource that has not previously detected the continuous LBT failure.

It can be seen that by introducing "since the last consecutive LBT failure corresponding to the first resource was triggered, the indication information has not been generated or "Sent", will not affect the subsequent generation and sending of indication information of the first resource, thereby avoiding the problem that the indication information that needs to be sent corresponding to the first resource cannot be sent.

The resource determination method provided in this embodiment is applicable to (but not limited to) scenarios in which connected UEs use unlicensed spectrum and resource selection mode 2 for SL communications. The condition for a terminal device to send indication information to a network device is that the continuous LBT failure of a first resource of the terminal device is triggered and has not been canceled and the indication information has not been generated or sent, and the condition for the terminal device to cancel the triggered continuous LBT failure of the first resource is that the first condition is satisfied. The two conditions are different, so that the time for the terminal device to cancel reporting the indication information to the network device (event one) and the time for detecting the recovery of resources that have failed to achieve continuous LBT (event three) may be different. Through the first condition, the first resource becomes an available resource only after a period of time after the first resource triggers a continuous LBT failure, thereby improving the success rate of the UE performing LBT and ensuring SL communication. By introducing "since the most recent continuous LBT failure corresponding to the first resource was triggered, the indication information has not been generated or sent", the terminal device determines that the condition of "the indication information has not been generated or sent" is met. When the continuous LBT failure of the first resource of the terminal device is triggered and not canceled, the terminal device may only report the indication information once at most, which saves signaling overhead and will not affect the subsequent generation and sending of the indication information of the first resource. Therefore, the network device can obtain the continuous LBT failure information of the side link resources of the terminal device and perform reasonable resource configuration processing on the terminal device.

Optionally, the resource determination method provided in this embodiment may further include:

S1703. The terminal device sends instruction information to the network device.

Correspondingly, the network device receives the indication information sent by the terminal device.

Specifically, if the terminal device has not generated or sent indication information corresponding to the first resource, when there is an available uplink resource for new transmission and the uplink resource can carry the sidelink continuous LBT failure MAC CE and its subheader, the terminal device sends indication information to the network device to notify the network device to trigger the resource of continuous LBT failure. It should be understood that if the terminal device has not generated or sent indication information corresponding to a certain resource, the terminal device needs to send indication information to the network device until the terminal device has generated or sent indication information corresponding to the resource once. If the terminal device has generated or sent indication information corresponding to a certain resource, even if the continuous LBT failure of the first resource of the terminal device is still "triggered and not canceled", the terminal device will not send indication information to the network device.

Optionally, the indication information indicates that at least one first resource detects continuous LBT failures.

Optionally, the indication information indicates the continuous LBT failure information corresponding to the resource that currently detects the continuous LBT failure.

Optionally, the terminal device sends an indication message to the network device, which can be specifically: the terminal device sends a MAC PDU, and the MAC PDU includes a MAC CE indicating a continuous LBT failure of the side link. If the terminal device sends an indication message to the network device, it can be replaced by: if a MAC PDU is sent and the MAC PDU includes a MAC CE indicating a continuous LBT failure of the side link.

The indication information may refer to the relevant description of S202 in FIG. 2B , which will not be described again here.

Optionally, after receiving the indication information, the network device may not perform subsequent resource configuration processing, and the UE may resume SL transmission. For example, if the network device finds that the UE still has sufficient side link resources and does not detect continuous LBT failures, the resource pool of the UE may not be reconfigured. Of course, if the network device finds that the UE does not have sufficient available side link resources, the resource pool of the UE may be reconfigured, and this application does not limit this.

In this embodiment, the condition for the terminal device to send indication information to the network device takes into account "the terminal device has not generated or sent indication information". Due to the introduction of "the indication information has not been generated or sent since the most recent continuous LBT failure corresponding to the first resource was triggered", it can be understood that the condition for the terminal device to send indication information to the network device takes into account "the terminal device has not generated or sent indication information corresponding to the first resource". The condition for the terminal device to cancel the triggered continuous LBT failure of the first resource is to meet the first condition. The two conditions are different, so the time for the terminal device to cancel reporting the indication information to the network device (event one) and the time for the recovery of the resource that detects the continuous LBT failure (event three) can be different.

Exemplarily, some descriptions are as follows (wherein the first timer is the SL-LBT recovery timer sl-LBT-RecoveryTimer):

1>if SL consistent LBT failure has been triggered, and not cancelled, in the RB set(s), and SL LBT failure MAC CE(s)has not been generated since the last SL consistent LBT failure for the RB set(s)was triggered;

2>if the sl-LBT-RecoveryTimer for the triggered SL consistent LBT failure is not running:(if the sl-LBT-RecoveryTimer for the triggered SL consistent LBT failure is not running:)

3>start the sl-LBT-RecoveryTimer. (Start the SL-LBT recovery timer.)

2>if UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the SL LBT failure MAC CE plus its subheader as a result of logical channel prioritization:(if any UL-SCH resources available for new transmissions, and these UL-SCH resources can accommodate the SL LBT failure MAC CE plus its subheader after logical channel priority processing)

3>instruct the Multiplexing and Assembly procedure to generate the SL LBT failure MAC CE(s). (instruct the Multiplexing and Assembly process to generate the SL LBT failure MAC CE)

2>else: (otherwise:)

3>trigger a Scheduling Request for SL LBT failure MAC CE. (Trigger a Scheduling Request for SL LBT failure MAC CE.)

1>if the sl-LBT-RecoveryTimer for the triggered SL consistent LBT failure(s)expires:(if the sl-LBT-RecoveryTimer for the triggered SL consistent LBT failure(s)expires:)

2>cancel the triggered SL consistent LBT failure(s) in RB set(s) for which SL consistent LBT failure was detected.

The effect of the resource determination method provided in this embodiment is exemplarily described below in conjunction with Figure 18. Figure 18 is another schematic diagram of a connected UE detecting continuous LBT failures in mode 2 provided in an embodiment of the present application. Exemplarily, the first condition is: the first timer of the first resource times out, and the first timer is started when the first state of the first resource is triggered.

As shown in FIG18 , the terminal device detects continuous LBT failure on RB set 1, determines that the continuous LBT failure of RB set 1 is triggered and not cancelled, and "since the most recent continuous LBT failure corresponding to RB set 1 is triggered (i.e., the moment shown by the dotted line A), the indication information has not been generated or sent", and considers that the condition is met. The terminal device starts the first timer corresponding to RB set 1. Moreover, when there are available uplink resources for new transmission, and the uplink resources can carry the sidelink continuous LBT failure MAC CE and its subheader, the terminal device generates indication information and submits the indication information to the physical layer for transmission, so as to send the indication information to the network device. During the operation of the first timer corresponding to RB set 1, the continuous LBT failure of RB set 1 is still in the state of "triggered and not cancelled", RB set 1 is an unavailable resource, and the terminal device will not select RB set 1 for LBT, thereby improving the success rate of LBT of the terminal device, and will not report the indication information repeatedly, saving signaling overhead. When the first timer corresponding to RB set 1 times out, the terminal device cancels the continuous LBT failure of RB set 1, RB set 1 is restored to an available resource, and the terminal device can select RB set 1 for LBT.

Subsequently, as shown in FIG18 , the terminal device detects continuous LBT failures on RB set 2, determines that the continuous LBT failure of RB set 2 is triggered and has not been canceled, and "since the most recent continuous LBT failure corresponding to RB set 2 was triggered (i.e., the moment shown by the dotted line B), the indication information has not been generated or sent", and considers that the condition is met. The terminal device starts the first timer corresponding to RB set 2. Moreover, when there are available uplink resources for new transmission and the uplink resources can carry the sidelink continuous LBT failure MAC CE and its subheader, the terminal device generates indication information and submits the indication information to the physical layer for transmission, thereby sending the indication information to the network device.

Similarly, as shown in FIG18 , the terminal device then detects continuous LBT failure on RB set 1 again, determines that the continuous LBT failure of RB set 1 is triggered and has not been canceled, and "since the most recent continuous LBT failure corresponding to RB set 1 was triggered (i.e., the moment shown by the dotted line C), the indication information has not been generated or sent", and considers that the condition is met. The terminal device starts the first timer corresponding to RB set 1. Moreover, when there are available uplink resources for new transmission and the uplink resources can carry the sidelink continuous LBT failure MAC CE and its subheader, the terminal device generates indication information and submits the indication information to the physical layer for transmission, thereby sending the indication information to the network device.

In the embodiments provided by the present application, the method provided by the embodiments of the present application is introduced from the perspective of the interaction between the terminal device, the network device, and the terminal device and the network device. In order to realize the functions in the methods provided by the embodiments of the present application, the terminal device and the network device may include a hardware structure and/or a software module, and the functions are realized in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether a function in the functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.

FIG11 is a schematic diagram of the structure of a possible communication device provided in an embodiment of the present application. The communication device can implement the functions of the terminal device or the network device in the above method embodiment, and thus can also achieve the beneficial effects possessed by the above method embodiment. In an embodiment of the present application, the communication device can be a terminal device 101 as shown in FIG1 , or a module (such as a chip) applied to a terminal device, or a network device 102 as shown in FIG1 , or a module (such as a chip) applied to a network device.

As shown in Figure 11, the communication device includes a transceiver module 1101 and a processing module 1102. The transceiver module 1101 is used to communicate with other devices, and the processing module 1102 is used to implement other processing steps. The communication device can be used to implement the functions of the terminal device in the above method embodiment, or can be used to implement the functions of the network device in the above method embodiment.

When the terminal device is a terminal equipment, FIG12 is a schematic diagram of the structure of the terminal equipment provided in an embodiment of the present application. For ease of understanding and illustration, in FIG12, a mobile phone is used as an example of the terminal equipment. As shown in FIG12, the terminal equipment includes a processor, a memory, a radio frequency circuit, an antenna, and an input-output device. The processor is mainly used to process communication protocols and communication data, as well as to control the terminal equipment, execute software programs, process software program data, etc. The memory is mainly used to store software programs and data. The radio frequency circuit is mainly used for conversion between baseband signals and radio frequency signals and processing of radio frequency signals. The antenna is mainly used to send and receive radio frequency signals in the form of electromagnetic waves. Input-output devices, such as touch screens, display screens, keyboards, etc., are mainly used to receive data input by users and output data to users. It should be noted that some types of terminal equipment may not have input-output devices.

When data needs to be sent, the processor performs baseband processing on the data to be sent, and then outputs the baseband signal to the RF circuit. The RF circuit performs RF processing on the baseband signal and then sends the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the terminal device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data. For ease of explanation, only one memory and processor are shown in Figure 12. In an actual terminal device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device, etc. The memory may be set independently of the processor or integrated with the processor, and the embodiments of the present application do not limit this.

In the embodiment of the present application, the antenna and the radio frequency circuit with transceiver function can be regarded as the transceiver unit of the terminal device (the transceiver unit can be a functional unit that can realize the sending function and the receiving function; or, the transceiver unit can also include two functional units, namely, a receiving unit that can realize the receiving function and a sending unit that can realize the sending function), and the processor with processing function can be regarded as the processing unit of the terminal device. As shown in FIG12, the terminal device includes a transceiver unit 2310 and a processing unit 2320. The transceiver unit can also be referred to as a transceiver, a transceiver, a transceiver device, etc. The processing unit can also be referred to as a processor, a processing board, a processing module, a processing device, etc. Optionally, the device used to realize the receiving function in the transceiver unit 2310 can be regarded as a receiving unit, and the device used to realize the sending function in the transceiver unit 2310 can be regarded as a sending unit, that is, the transceiver unit 2310 includes a receiving unit and a sending unit. The transceiver unit can sometimes also be referred to as a transceiver, a transceiver, or a transceiver circuit, etc. The receiving unit can sometimes also be referred to as a receiver, a receiver, or a receiving circuit, etc. The sending unit may sometimes also be called a transmitter, a transmitter or a transmitting circuit, etc.

It should be understood that the transceiver unit 2310 is used to perform the sending operation and the receiving operation of the terminal device in the above method embodiment, and the processing unit 2320 is used to perform other operations except the sending and receiving operation on the terminal device in the above method embodiment.

When the terminal device is a chip-type device or circuit, the device may include a transceiver unit and a processing unit, wherein the transceiver unit may be an input/output circuit and/or a communication interface; and the processing unit may be an integrated processor or microprocessor or integrated circuit.

The embodiment of the present application also provides a communication system. The communication system may include the terminal device and network equipment involved in the above embodiment. Optionally, the terminal device in the communication system may execute the steps executed by the terminal device in the embodiment of the method of the present application.

An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a computer, the computer can implement the process related to the terminal device in any of the embodiments shown in the above method embodiments.

An embodiment of the present application also provides a computer program product, which is used to store a computer program. When the computer program is executed by a computer, the computer can implement the process related to the terminal device in any of the embodiments shown in the above method embodiments.

The present application also provides a chip or chip system, which may include a processor, which may be used to call a program or instruction in a memory to execute a process related to a terminal device in any of the above method embodiments. The chip system may include the chip, and may also include other components such as a memory or a transceiver.

The present application also provides a circuit that can be coupled to a memory and can be used to execute a process related to a terminal device in any of the above method embodiments. The chip system may include the chip and may also include other components such as a memory or a transceiver.

It should be understood that the processor mentioned in the embodiments of the present application may be a CPU, or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory. A random access memory (RAM) is used as an external cache memory. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) is integrated in the processor.

It should be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and modules described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

In the several embodiments provided in the present application, it should be understood that the disclosed methods and devices can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the module is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

If the function is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or the part that makes the contribution or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, etc.) to perform all or part of the steps of the method of each embodiment of the present application. The aforementioned computer-readable storage medium can be any available medium that can be accessed by a computer. By way of example but not limitation, computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), universal serial bus flash disk, mobile hard disk, or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer.

The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person of ordinary skill in the art can appreciate that with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

The above is only a specific implementation of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the embodiments of the present application, which should be included in the protection scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application should be based on the protection scope of the claims.

Claims (36)

A resource determination method, characterized by comprising: Determine that a continuous listen-before-talk (LBT) failure of a first resource of a terminal device is triggered, and a first state of the first resource of the terminal device is triggered; wherein the first state is that a sidelink resource corresponding to the first resource is unavailable; Sending indication information to the network device, the indication information being used to indicate that the terminal device has detected continuous LBT failures; canceling the continuous LBT failure of the first resource; If the first condition is met, the first state of the first resource is canceled. The method according to claim 1, characterized in that the first state of the first resource of the terminal device is triggered, comprising: The first resource of the terminal device is in the first state. The method according to claim 1 or 2, characterized in that canceling the first state of the first resource comprises: The first resource is set to a second state, where the second state is that a side link resource corresponding to the first resource is available. The method according to any one of claims 1 to 3, characterized in that the first condition includes at least one of the following: successfully completing a transmission using the sidelink resource on the second resource; a first time period elapses after a first state of the first resource is triggered; A first timer times out, the first timer being started when a first state of the first resource is triggered; The side link channel quality meets the channel quality condition; The sidelink channel busy state satisfies the channel busy condition. The method according to any one of claims 1 to 4, characterized in that the determining that a continuous listen-before-talk (LBT) failure of a first resource of a terminal device is triggered and a first state of the first resource of the terminal device is triggered comprises: If the second condition is met, it is determined that the continuous LBT failure of the first resource of the terminal device is triggered, and the first state of the first resource of the terminal device is triggered; or, If the second condition is met, it is determined that the continuous LBT failure of the first resource of the terminal device is triggered, and if the third condition is met, it is determined that the first state of the first resource of the terminal device is triggered; Among them, the second condition is: the cumulative number of LBT failures corresponding to the first resource is equal to or greater than the maximum number of LBT failures; the third condition is: continuous LBT failures are detected in the first resource, or the first resource triggers continuous LBT failures. The method according to any one of claims 1-5 is characterized in that the indication information indicates that at least one of the first resources detects continuous LBT failures. The method according to claim 6, wherein the canceling of the continuous LBT failures of the first resource comprises: Cancel the continuous LBT failure of the first resource indicated by the indication information. A resource determination method, characterized by comprising: Determining that a continuous listen-before-talk (LBT) failure of a first resource of a terminal device is triggered, and a third state of the terminal device is triggered; If the first condition is met, canceling the continuous LBT failure of the first resource; Sending indication information to the network device, the indication information being used to indicate that the terminal device has detected continuous LBT failures; The third state of the terminal device is canceled. The method according to claim 8 is characterized in that the third state is continuous LBT failure reporting. The method according to claim 8 or 9 is characterized in that the third state of the terminal device is the third state of the first resource of the terminal device. The method according to any one of claims 8 to 10, characterized in that the method further comprises: If the third state of the terminal device is cancelled, the cumulative number of LBT failures of the first resource is set to 0. The method according to any one of claims 8 to 11, characterized in that the first condition includes at least one of the following: successfully completing a transmission using the sidelink resource on the second resource; a first time period elapses after a first state of the first resource is triggered; A first timer times out, the first timer being started when a first state of the first resource is triggered; The side link channel quality meets the channel quality condition; The sidelink channel busy state satisfies the channel busy condition. The method according to any one of claims 8 to 12, characterized in that the determining that the continuous listen-before-talk (LBT) failure of the first resource of the terminal device is triggered and the third state of the terminal device is triggered comprises: If the second condition is met, it is determined that the continuous LBT failure of the first resource of the terminal device is triggered, and the third state of the terminal device is triggered; or, If the second condition is met, it is determined that the continuous LBT failure of the first resource of the terminal device is triggered, and if the third condition is met, it is determined that the third state of the terminal device is triggered; Among them, the second condition is: the cumulative number of LBT failures corresponding to the first resource is equal to or greater than the maximum number of LBT failures; the third condition is: continuous LBT failures are detected in the first resource, or the first resource triggers continuous LBT failures. The method according to any one of claims 8-13 is characterized in that the indication information indicates that at least one of the first resources detects continuous LBT failures. The method according to claim 10 or 14, characterized in that when the third state of the terminal device is the third state of the first resource of the terminal device, canceling the third state of the terminal device comprises: Cancel the third state of the first resource indicated by the indication information. The method according to any one of claims 8-15 is characterized in that the continuous LBT failure is used to indicate that the side link resource corresponding to the first resource is unavailable. A resource determination method, characterized by comprising: If the first condition is met, an indication message is sent to the network device, where the indication message is used to indicate that the terminal device has detected a continuous listen-before-talk LBT failure; wherein the first condition includes: the continuous LBT failure of the first resource is triggered and not cancelled, and the number of the first resource is greater than or equal to a preset threshold; The continuous LBT failure of the first resource is cancelled. The method according to claim 17 is characterized in that the resource pool where the first resource is located is a resource pool with physical sidelink feedback channel PSFCH resources. The method according to claim 18 is characterized in that the terminal device is configured with a feedback-enabled logical channel. The method according to claim 17 is characterized in that the resource pool where the first resource is located includes a resource pool with physical sidelink feedback channel PSFCH resources and a resource pool without PSFCH resources. The method according to claim 20 is characterized in that the terminal device is not configured with a feedback-enabled logical channel. The method according to any one of claims 17-21 is characterized in that the indication information indicates that at least one of the first resources detects continuous LBT failures. The method according to any one of claims 17 to 22, wherein the canceling of the continuous LBT failures of the first resource comprises: Cancel the continuous LBT failure of the first resource indicated by the indication information. A resource determination method, characterized by comprising: Determine that a continuous listen-before-talk LBT failure of a first resource of a terminal device is triggered and not cancelled, and that indication information corresponding to the first resource has not been generated or sent; wherein the indication information is used to indicate that the terminal device has detected a continuous LBT failure; If the first condition is met, canceling the continuous LBT of the first resource fails, and the indication information corresponding to the first resource has not been generated or sent. The method according to claim 24, characterized in that before the first condition is satisfied, the method further comprises: The indication information is sent to the network device. The method according to claim 24 or 25 is characterized in that the first condition includes: a first timer of the first resource times out, wherein the first timer is started when the first resource detects continuous LBT failures. The method according to any one of claims 24-26 is characterized in that the indication information indicates that at least one of the first resources detects continuous LBT failures. The method according to any one of claims 24-26 is characterized in that the continuous LBT failure of the first resource is used to indicate that the side link resource corresponding to the first resource is not selectable or unavailable. A resource determination method, characterized by comprising: Determining that a continuous listen-before-talk LBT failure of a first resource of a terminal device is triggered and not cancelled, and that an indication message has not been generated or sent since the last continuous LBT failure corresponding to the first resource was triggered; wherein the indication message is used to indicate that the terminal device has detected a continuous LBT failure; If the first condition is met, canceling the continuous LBT failure of the first resource. The method according to claim 29, characterized in that before the first condition is satisfied, the method further comprises: The indication information is sent to the network device. The method according to claim 29 or 30 is characterized in that the first condition includes: a first timer of the first resource times out, wherein the first timer is started when the first resource detects continuous LBT failures. The method according to any one of claims 29-31 is characterized in that the indication information indicates that at least one of the first resources detects continuous LBT failures. The method according to any one of claims 29-31 is characterized in that the continuous LBT failure of the first resource is used to indicate that the side link resource corresponding to the first resource is not selectable or unavailable. A terminal device, characterized in that it includes a processor, wherein the processor is used to couple with a memory, read instructions in the memory and, according to the instructions, enable the terminal device to execute a method as described in any one of claims 1 to 7, or execute a method as described in any one of claims 8 to 16, or execute a method as described in any one of claims 17 to 23, or execute a method as described in any one of claims 24 to 28, or execute a method as described in any one of claims 29 to 33. A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a terminal device, the terminal device executes the method as described in any one of claims 1 to 7, or executes the method as described in any one of claims 8 to 16, or executes the method as described in any one of claims 17 to 23, or executes the method as described in any one of claims 24 to 28, or executes the method as described in any one of claims 29 to 33. A computer program product comprising instructions, characterized in that when the computer program product is run on a terminal device, the terminal device executes the method as described in any one of claims 1 to 7, or executes the method as described in any one of claims 8 to 16, or executes the method as described in any one of claims 17 to 23, or executes the method as described in any one of claims 24 to 28, or executes the method as described in any one of claims 29 to 33.