Sidelink communication method and apparatus

Abstract

The embodiment of the disclosure discloses a kind of sidelink communication method and device, belong to communication technical field, wherein, sidelink communication method is applied to terminal equipment, this method includes: determine whether to trigger persistent LBT failure on the sidelink sending resource of shared frequency;When triggering persistent LBT failure, failure indication is reported to network equipment or determining standby sidelink sending resource is used to send sidelink message, so that terminal equipment can send data in time when LBT fails, avoid data loss, increase communication reliability.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a sidelink communication method and apparatus. Background Technology

[0002] Currently, in order to support direct communication between user equipment (UE) and user terminals, a sidelink communication method has been introduced, and the interface between user terminals is PC-5.

[0003] When a user equipment (UE) performs sidelink transmission on a shared frequency sidelink transmission resource, it needs to perform listen before talk (LBT). LBT failure may occur. When LBT fails, the UE continues to wait, which may lead to data transmission delay or even data loss. Summary of the Invention

[0004] The first aspect of this disclosure provides a sidelink communication method, which is executed by a terminal device. The method includes determining whether a persistent LBT failure is triggered on a sidelink transmission resource of a shared frequency; when the persistent LBT failure is triggered, reporting a failure indication to a network device or determining a backup sidelink transmission resource for transmitting a sidelink message.

[0005] In this technical solution, the terminal device determines whether a persistent LBT failure is triggered on the side link transmission resources of the shared frequency; when a persistent LBT failure is triggered, it reports a failure indication to the network device or determines a backup side link transmission resource for sending side link messages, so that the terminal device can send data in a timely manner when LBT fails, avoid data loss, and increase communication reliability.

[0006] The second aspect of this disclosure provides another sidelink communication method applied to a network device. The method includes sending a first message to a terminal device; wherein the first message carries a specified timer and a specified number of thresholds for determining whether a persistent LBT failure is triggered on the sidelink transmission resources of the shared frequency.

[0007] A third aspect of this disclosure provides a sidelink communication method applied to a destination terminal device. The method includes: receiving a failure indication sent by the terminal device, wherein the failure indication includes a first destination address identifier, and sidelink communication with the first destination address identifier triggers a continuous LBT failure.

[0008] A fourth aspect of this disclosure provides a sidelink communication device applied to a terminal device. The device includes: a first processing unit for determining whether a persistent LBT failure is triggered on a sidelink transmission resource of a shared frequency; and a second processing unit for reporting a failure indication to a network device or determining a backup sidelink transmission resource when the persistent LBT failure is triggered, for sending a sidelink message.

[0009] The fifth aspect of this disclosure provides another sidelink communication device applied to a network device. The device includes a transceiver unit for sending a first message to a terminal device; wherein the first message carries a specified timer and a specified number of thresholds for determining whether a persistent LBT failure is triggered on the sidelink transmission resources of the shared frequency.

[0010] The sixth aspect of this disclosure provides another sidelink communication device applied to a destination terminal device. The device includes a transceiver unit for receiving a failure indication sent by the terminal device, wherein the failure indication includes a first destination address identifier, and wherein sidelink communication with the first destination address identifier triggers a continuous LBT failure.

[0011] A seventh aspect of this disclosure provides a sidelink communication device, the device including a processor and a memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method described in the first aspect of this disclosure.

[0012] An eighth aspect of this disclosure provides another sidelink communication device, the device including a processor and a memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method described in the second aspect of this disclosure.

[0013] A ninth aspect of this disclosure provides another sidelink communication device, the device including a processor and a memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method described in the third aspect of this disclosure.

[0014] A tenth aspect embodiment of this disclosure provides a sidelink communication device, characterized in that it includes: a processor and an interface circuit; the interface circuit is configured to receive code instructions and transmit them to the processor; the processor is configured to execute the code instructions to perform the method described in the first aspect embodiment of this disclosure.

[0015] The eleventh aspect of this disclosure provides another sidelink communication device, characterized in that it includes: a processor and an interface circuit; the interface circuit is used to receive code instructions and transmit them to the processor; the processor is used to execute the code instructions to perform the method described in the second aspect of this disclosure.

[0016] The twelfth aspect of this disclosure provides another sidelink communication device, characterized in that it includes: a processor and an interface circuit; the interface circuit is configured to receive code instructions and transmit them to the processor; the processor is configured to execute the code instructions to perform the method described in the third aspect of this disclosure.

[0017] A thirteenth aspect of this disclosure provides a computer-readable storage medium for storing instructions that, when executed, cause the method described in the first aspect of this disclosure to be implemented.

[0018] The fourteenth aspect of this disclosure provides another computer-readable storage medium for storing instructions that, when executed, cause the method described in the second aspect of this disclosure to be implemented.

[0019] The fifteenth aspect of this disclosure provides another computer-readable storage medium for storing instructions that, when executed, cause the method described in the third aspect of this disclosure to be implemented.

[0020] The sixteenth aspect of this disclosure provides a computer program product that, when run on a computer, causes the computer to perform the method described in the first aspect of the present invention.

[0021] The seventeenth aspect of this disclosure provides another computer program product that, when run on a computer, causes the computer to perform the methods described in the second aspect of the present invention.

[0022] The eighteenth aspect of this disclosure provides another computer program product that, when run on a computer, causes the computer to perform the methods described in the third aspect of the present invention.

[0023] Additional aspects and advantages of this disclosure will be set forth in part in the description which follows, will become apparent from the description, or may be learned by practice of this disclosure. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments or background art of this disclosure, the accompanying drawings used in the embodiments or background art of this disclosure will be described below.

[0025] Figure 1A schematic diagram of a communication system structure provided in this disclosure embodiment;

[0026] Figure 2 A flowchart illustrating a sidelink communication method provided in an embodiment of this disclosure;

[0027] Figure 3 A flowchart illustrating another sidelink communication method provided in this embodiment of the disclosure;

[0028] Figure 4 A flowchart illustrating another sidelink communication method provided in this embodiment of the disclosure;

[0029] Figure 5 A flowchart illustrating another sidelink communication method provided in this embodiment of the disclosure;

[0030] Figure 6 A flowchart illustrating another sidelink communication method provided in this embodiment of the disclosure;

[0031] Figure 7 A flowchart illustrating another sidelink communication method provided in this embodiment of the disclosure;

[0032] Figure 8 A flowchart illustrating another sidelink communication method provided in this embodiment of the disclosure;

[0033] Figure 9 A flowchart illustrating another sidelink communication method provided in this embodiment of the disclosure;

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

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

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

[0037] Figure 13 This is a schematic diagram of the structure of a network device provided in an embodiment of the present disclosure;

[0038] Figure 14 This is a block diagram of a terminal device provided in an embodiment of the present disclosure. Detailed Implementation

[0039] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this disclosure as detailed in the appended claims.

[0040] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. The singular forms “a” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

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

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

[0043] It should be noted that the technical solutions of this disclosure can be applied to various communication systems. For example, Long Term Evolution (LTE) systems, 5th Generation (5G) mobile communication systems, 5G New Radio (NR) systems, or other future new mobile communication systems.

[0044] The network device 101 in this embodiment is a network-side entity used for transmitting or receiving signals. For example, the network device 101 can be an evolved NodeB (eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. This disclosure does not limit the specific technology or device form used in the network device. The network device provided in this disclosure can be composed of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure allows the protocol layer of a network device, such as a base station, to be separated. Some protocol layer functions are centrally controlled by the CU, while the remaining or all protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0045] The terminal device 102 in this disclosure is a user-side entity used to receive or transmit signals, such as a mobile phone. The terminal device can also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device can be a car with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, etc. This disclosure does not limit the specific technology or device form used in the terminal device.

[0046] To support direct communication between user equipment (UE) devices, a sidelink communication method is introduced, with the interface between UE devices being PC-5. Based on the correspondence between sending and receiving UE devices, three transmission modes are supported on the sidelink: unicast, multicast, and broadcast. In a unicast connection, each UE corresponds to a destination address identifier; in multicast, each UE can belong to one or more groups, with each group corresponding to a destination address identifier; in broadcast, all UEs correspond to at least one destination address identifier.

[0047] When a UE sends sidelink data, it needs to perform addressing based on the destination and source addresses. The application layer sends the source Layer 2 address and destination Layer 2 address to the access layer, with a length of 24 bits. The lower 8 bits of the source Layer 2 address are carried in the SCI (Site Code Interchange), becoming the source Layer 1 address, and the remaining 16 bits are carried in the MAC header. The lower 16 bits of the destination Layer 2 address are carried in the SCI, becoming the destination Layer 1 address, and the remaining 8 bits are carried in the MAC header.

[0048] If a unicast connection experiences a sidelink failure or a sidelink configuration failure, the UE reports the destination address identifier of the destination UE and the reason for the failure to the network device. The reasons for the failure include sidelink failure or sidelink configuration failure.

[0049] When a UE performs uplink transmission on a shared frequency (unlicensed spectrum), the UE needs to perform LBT (Listen Before Talk). If LBT fails, the physical layer notifies the media access control (MAC) layer. Upon receiving the LBT failure indication, the MAC layer starts or restarts a specified timer (lbt-FailureDetectionTimer) and increments the LBT failure count. If the specified timer expires, the LBT failure count is reset to 0. If the LBT failure count reaches a specified threshold (lbt-FailureInstanceMaxCount), continuous LBT failures are triggered. The specified timer and specified threshold are configured by the network device via Radio Resource Control (RRC) messages.

[0050] If all uplink bandwidth parts (BWPs) of the serving cell trigger a persistent LBT failure, then the serving cell experiences a radio link failure (RLF); otherwise, the UE will activate the uplink BWP and switch to the uplink BWP that has not experienced a persistent LBT failure.

[0051] When a user terminal performs sidelink transmission on a shared frequency sidelink transmission resource, it needs to perform listen before talk (LBT). LBT failure may occur. When LBT fails, the user terminal continues to wait, which may lead to data transmission delay or even data loss.

[0052] To address the aforementioned issues, this disclosure proposes a sidelink communication method and apparatus.

[0053] It is understood that the communication system described in the embodiments of this disclosure is for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and does not constitute a limitation on the technical solutions provided in the embodiments of this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this disclosure are also applicable to similar technical problems.

[0054] The sidelink communication method and apparatus provided in this disclosure will be described in detail below with reference to the accompanying drawings.

[0055] Please see Figure 2 , Figure 2 This is a flowchart illustrating a sidelink communication method provided in an embodiment of this disclosure. The sidelink communication method can be... Figure 1 The terminal device in the communication system shown performs the following.

[0056] like Figure 2 As shown, the sidelink communication method may include the following steps:

[0057] Step 201: Determine whether a persistent LBT failure is triggered on the side link transmission resources of the shared frequency.

[0058] In this embodiment of the disclosure, when the number of LBT failures on the shared frequency side-link transmission resource is greater than or equal to a specified threshold, it is determined that a continuous LBT failure is triggered on the shared frequency side-link transmission resource. When the number of LBT failures within a specified timer is less than the specified threshold, it is determined that a continuous LBT failure is not triggered on the shared frequency side-link transmission resource.

[0059] Step 202: When a persistent LBT failure is triggered, a failure indication is reported to the network device or backup side link transmission resources are determined for sending side link messages.

[0060] The backup side link transmission resources can be side link transmission resources on a shared frequency or side link transmission resources on a non-shared frequency.

[0061] In one example of this disclosure, when a persistent LBT failure is triggered, the terminal device reports a first failure indication to the network device and sends a side link message according to the backup side link sending resources scheduled by the network device.

[0062] In another example of this disclosure, when a persistent LBT failure is triggered, a backup side-crossing transmission resource is selected from at least one configured candidate side-crossing transmission resources to transmit the side-crossing message. Specifically, a candidate side-crossing transmission resource of a shared frequency that has not triggered a persistent LBT failure or a candidate side-crossing transmission resource of a non-shared frequency can be selected from at least one candidate side-crossing transmission resource as the backup side-crossing transmission resource.

[0063] In one embodiment of this disclosure, a terminal device receives a fourth RRC message from a network device, wherein the fourth RRC message carries candidate-side traversal transmission resources; wherein the candidate-side traversal transmission resources include candidate-side traversal transmission resources with shared frequencies or candidate-side traversal transmission resources with non-shared frequencies.

[0064] In another example, the terminal device receives a second sidelink RRC message from a destination terminal device corresponding to at least one destination address identifier. This second sidelink RRC message carries a candidate sidelink transmission resource message. The candidate sidelink transmission resources include candidate sidelink transmission resources at shared frequencies or candidate sidelink transmission resources at non-shared frequencies.

[0065] The implementation of the sidelink communication method on shared frequencies in the embodiments provided above is also applicable to the sidelink communication method on unlicensed frequencies.

[0066] In summary, by determining whether a persistent LBT failure is triggered on the side-link transmission resources of the shared frequency, and when a persistent LBT failure is triggered, a failure indication is reported to the network device or a backup side-link transmission resource is determined for sending side-link messages, the terminal device can promptly send data when LBT fails, avoiding data loss and increasing communication reliability.

[0067] This disclosure provides another sidelink communication method. Figure 3 This is a flowchart illustrating another sidelink communication method provided in an embodiment of the present disclosure. The sidelink communication method can be applied to a terminal device. The sidelink communication method can be executed alone, or it can be executed together with any embodiment of the present disclosure or possible implementations in the embodiments, or it can be executed together with any technical solution in the related technologies.

[0068] like Figure 3 As shown, the sidelink communication method may include the following steps:

[0069] Step 301: When the number of LBT failures on the side link transmission resources of the shared frequency is greater than or equal to a specified threshold, determine to trigger a continuous LBT failure on the side link transmission resources of the shared frequency.

[0070] In this embodiment of the disclosure, the process by which the terminal device determines the number of LBT failures on the side link transmission resources of the shared frequency can be, for example, by resetting the current number of LBT failures to zero and stopping the specified timer when the specified timer expires; and by starting or restarting the specified timer and incrementing the current number of LBT failures by 1 when an LBT failure occurs on the side link transmission resources of the shared frequency.

[0071] In this embodiment of the disclosure, when an LBT failure occurs on the side link transmission resource of the shared frequency, if the specified timer has not been started, the specified timer is started and the LBT failure count is incremented by 1; if the specified timer has not been stopped or has been started, the specified timer is restarted and the LBT failure count is incremented by 1.

[0072] The number of LBT failures on the sidelink transmission resources of the shared frequency includes the number of LBT failures on all sidelink transmission resources of all shared frequencies.

[0073] In this embodiment of the disclosure, when the number of LBT failures within a specified timer is less than a specified threshold, it is determined that no continuous LBT failure has been triggered on the side-link transmission resources of the shared frequency.

[0074] In this embodiment of the disclosure, before determining whether a persistent LBT failure is triggered on the side link transmission resources of the shared frequency, the terminal device receives a first RRC message from the network device, wherein the first RRC message carries a specified timer and a specified number threshold; the specified timer is used to reset the LBT failure count when the timeout occurs.

[0075] The first RRC message carries the same number of specified timers and specified count thresholds, and can carry one specified timer and one specified count threshold.

[0076] Step 302: When a persistent LBT failure is triggered, a failure indication is reported to the network device or backup side link transmission resources are determined for sending side link messages.

[0077] In one example of this disclosure, when a persistent LBT failure is triggered, the terminal device reports a first failure indication to the network device and sends a side link message according to the backup side link sending resources scheduled by the network device.

[0078] In another example of this disclosure, when a persistent LBT failure is triggered, the terminal device can select a backup side-link transmission resource from at least one configured candidate side-link transmission resource to transmit side-link messages. Specifically, a candidate side-link transmission resource with a shared frequency that has not triggered a persistent LBT failure or a candidate side-link transmission resource with a non-shared frequency can be selected from at least one candidate side-link transmission resource as the backup side-link transmission resource.

[0079] In one embodiment of this disclosure, a terminal device receives a fourth RRC message from a network device, wherein the fourth RRC message carries candidate-side traversal transmission resources; wherein the candidate-side traversal transmission resources include candidate-side traversal transmission resources with shared frequencies or candidate-side traversal transmission resources with non-shared frequencies.

[0080] In another example, the terminal device receives a second sidelink RRC message from a destination terminal device corresponding to at least one destination address identifier. This second sidelink RRC message carries a candidate sidelink transmission resource message. The candidate sidelink transmission resources include candidate sidelink transmission resources at shared frequencies or candidate sidelink transmission resources at non-shared frequencies.

[0081] The implementation of the sidelink communication method on shared frequencies in the embodiments provided above is also applicable to the sidelink communication method on unlicensed frequencies.

[0082] In summary, when the number of LBT failures on the shared frequency sidelink transmission resources is greater than or equal to a specified threshold, a continuous LBT failure is triggered on the shared frequency sidelink transmission resources. When a continuous LBT failure is triggered, a failure indication is reported to the network device or a backup sidelink transmission resource is determined for sending sidelink messages. This enables the terminal device to send data in a timely manner when LBT fails, avoiding data loss and increasing communication reliability.

[0083] This disclosure provides another sidelink communication method. Figure 4This is a flowchart illustrating another sidelink communication method provided in an embodiment of the present disclosure. The sidelink communication method can be applied to a terminal device. The path switching method can be executed alone, or it can be executed together with any embodiment of the present disclosure or possible implementations in the embodiments, or it can be executed together with any technical solution in the related technologies.

[0084] like Figure 4 As shown, the sidelink communication method may include the following steps:

[0085] Step 401: When a first shared frequency exists in at least one shared frequency, determine that a persistent LBT failure is triggered on the side link transmission resource of the first shared frequency.

[0086] Specifically, on the side link transmission resources of the first shared frequency, the number of LBT failures corresponding to the first shared frequency is greater than or equal to the specified number threshold corresponding to the first shared frequency.

[0087] Specifically, if the number of LBT failures corresponding to the first shared frequency is less than the specified threshold number corresponding to the first shared frequency, it is determined that no continuous LBT failure has been triggered on the side link transmission resources of the first shared frequency.

[0088] In this embodiment of the present disclosure, before the terminal device determines whether a first shared frequency exists in at least one shared frequency, it receives a second RRC message from the network device, wherein the second RRC message carries: a specified timer corresponding to at least one shared frequency, and a specified number threshold corresponding to at least one shared frequency; wherein the specified timer is used to reset the LBT failure count corresponding to the shared frequency when a timeout occurs.

[0089] In this embodiment of the disclosure, at least one shared frequency corresponds to a specified timer that is the same or different; at least one shared frequency corresponds to a specified number of thresholds that is the same or different.

[0090] This involves multiple shared frequencies, multiple specified timers, and multiple specified count thresholds. In one example, each shared frequency can correspond to one specified timer, and each shared frequency can correspond to one specified count threshold. In another example, multiple shared frequencies can correspond to one specified timer, and multiple shared frequencies can correspond to one specified count threshold.

[0091] Step 402: When a persistent LBT failure is triggered on the side link transmission resource of the first shared frequency, a failure indication is reported to the network device or a backup side link transmission resource is determined for sending side link messages.

[0092] In one embodiment of this disclosure, when a persistent LBT failure is triggered on the side link transmission resource of the first shared frequency, a second failure indication carrying the first shared frequency is reported to the network device, and a side link message is sent according to the backup side link transmission resource scheduled by the network device.

[0093] In another example, when a persistent LBT failure is triggered on the side traversal transmission resource of the first shared frequency, the terminal device may select a backup side traversal transmission resource from at least one configured candidate side traversal transmission resource for transmitting side traversal messages.

[0094] Specifically, candidate side traversal transmission resources of shared frequencies or non-shared frequencies that have not triggered a continuous LBT failure can be selected from at least one candidate side traversal transmission resource as backup side traversal transmission resources.

[0095] In one embodiment of this disclosure, a terminal device receives a fourth RRC message from a network device, wherein the fourth RRC message carries candidate-side traversal transmission resources; wherein the candidate-side traversal transmission resources include candidate-side traversal transmission resources with shared frequencies or candidate-side traversal transmission resources with non-shared frequencies.

[0096] In another example, the terminal device receives a second sidelink RRC message from a destination terminal device corresponding to at least one destination address identifier. This second sidelink RRC message carries a candidate sidelink transmission resource message. The candidate sidelink transmission resources include candidate sidelink transmission resources at shared frequencies or candidate sidelink transmission resources at non-shared frequencies.

[0097] The implementation of the sidelink communication method on shared frequencies in the embodiments provided above is also applicable to the sidelink communication method on unlicensed frequencies.

[0098] In summary, when a first shared frequency exists in at least one shared frequency, a persistent LBT failure is determined to be triggered on the side-link transmission resource of the first shared frequency; wherein, on the side-link transmission resource of the first shared frequency, the number of LBT failures corresponding to the first shared frequency is greater than or equal to a specified threshold number corresponding to the first shared frequency; when a persistent LBT failure is triggered on the side-link transmission resource of the first shared frequency, a failure indication is reported to the network device or a backup side-link transmission resource is determined for sending side-link messages, so that the terminal device can send data in a timely manner when LBT fails, avoid data loss, and increase communication reliability.

[0099] This disclosure provides another sidelink communication method. Figure 5 This is a flowchart illustrating another sidelink communication method provided in an embodiment of the present disclosure. The sidelink communication method can be applied to a terminal device. The sidelink communication method can be executed alone, or it can be executed together with any embodiment of the present disclosure or possible implementations in the embodiments, or it can be executed together with any technical solution in the related technologies.

[0100] Step 501: When a first destination address identifier exists among at least one destination address identifier for sidelink communication on at least one shared frequency sidelink transmission resource, it is determined that sidelink communication with the first destination address identifier triggers a continuous LBT failure.

[0101] Specifically, on the sidelink transmission resources of the shared frequency used for sidelink communication with the first destination address identifier, the number of LBT failures corresponding to the first destination address identifier is greater than or equal to the specified number threshold corresponding to the first destination address identifier.

[0102] Specifically, on the sidelink transmission resources of the shared frequency used for sidelink communication with the first destination address identifier, if the number of LBT failures corresponding to the first destination address identifier is less than the specified number threshold corresponding to the first destination address identifier, it is determined that sidelink communication with the first destination address identifier has not triggered continuous LBT failure.

[0103] In one embodiment of this disclosure, before determining whether a persistent LBT failure is triggered on the side link transmission resource of the shared frequency, the terminal device receives a third RRC message from the network device, wherein the third RRC message carries: at least one specified timer corresponding to a destination address identifier, and at least one specified number threshold corresponding to a destination address identifier; the specified timer is used to reset the LBT failure count corresponding to the destination address identifier when the timeout occurs.

[0104] In another example, a first sidelink RRC message is received from a destination terminal device corresponding to at least one destination address identifier, wherein the first sidelink RRC message carries: a specified timer corresponding to the destination address identifier, and a specified number of thresholds corresponding to the destination address identifier.

[0105] Among them, at least one destination address identifier corresponds to the same or different specified timers; at least one destination address identifier corresponds to the same or different specified number of thresholds.

[0106] Step 502: When it is determined that the side-link communication with the first destination address identifier has triggered a continuous LBT failure, a failure indication is reported to the network device or a backup side-link sending resource is determined for sending side-link messages.

[0107] In one embodiment of this disclosure, when a persistent LBT failure is triggered during sidelink communication with the first destination address identifier, a third failure indication carrying the first destination address identifier is reported to the network device; and a sidelink message is sent according to the backup sidelink transmission resources scheduled by the network device.

[0108] In another example of this disclosure, when a persistent LBT failure is triggered during sidelink communication with the first destination address identifier, the terminal device may select a candidate sidelink transmission resource with a shared frequency or a candidate sidelink transmission resource with a non-shared frequency from at least one configured candidate sidelink transmission resource as a backup sidelink transmission resource.

[0109] Specifically, the terminal selects a candidate side-link transmission resource from at least one configured candidate side-link transmission resource that does not trigger a continuous LBT failure of the shared frequency, and uses it as a backup side-link transmission resource to send side-link messages.

[0110] The implementation of the sidelink communication method on shared frequencies in the embodiments provided above is also applicable to the sidelink communication method on unlicensed frequencies.

[0111] In summary, when a first destination address identifier exists among at least one destination address identifier used for sidelink communication on at least one shared frequency sidelink transmission resource, it is determined that sidelink communication with the first destination address identifier triggers a persistent LBT failure; wherein, on the shared frequency sidelink transmission resource used for sidelink communication with the first destination address identifier, the number of LBT failures corresponding to the first destination address identifier is greater than or equal to a specified threshold number corresponding to the first destination address identifier; when a persistent LBT failure is triggered, a failure indication is reported to the network device or a backup sidelink transmission resource is determined for sending sidelink messages, so that the terminal device can send data in a timely manner when LBT fails, avoiding data loss and increasing communication reliability.

[0112] This disclosure provides another sidelink communication method. Figure 6 This is a flowchart illustrating another sidelink communication method provided in this disclosure embodiment. This sidelink communication method can be applied to a terminal device, and can be provided by... Figure 1 The terminal device executes the command.

[0113] like Figure 6 As shown, the sidelink communication method may include the following steps:

[0114] Step 601: When a first destination address identifier exists among at least one destination address identifier for sidelink communication on at least one shared frequency sidelink transmission resource, it is determined that sidelink communication with the first destination address identifier triggers a continuous LBT failure.

[0115] Specifically, on the sidelink transmission resources of the shared frequency used for sidelink communication with the first destination address identifier, the number of LBT failures corresponding to the first destination address identifier is greater than or equal to the specified number threshold corresponding to the first destination address identifier.

[0116] Step 602: When the side-link communication with the first destination address identifier triggers a continuous LBT failure, a fourth failure indication is sent to the destination terminal device corresponding to the first destination address identifier.

[0117] In one embodiment of this disclosure, a fourth failure indication is used to instruct the destination terminal device to stop receiving sidelink messages from the terminal device on the sidelink transmission resources of the shared frequency where a persistent LBT failure has occurred.

[0118] In another example, a fourth failure indication is used to indicate that sidelink messages are received on the backup sidelink transmission resource when the backup sidelink transmission resource exists.

[0119] In this embodiment of the disclosure, the fourth failure indication further carries a second shared frequency. Specifically, in the sidelink transmission resources of at least one shared frequency used for sidelink communication with the first destination address identifier, the sidelink transmission resources of the second shared frequency trigger a persistent LBT failure.

[0120] In this embodiment of the disclosure, the terminal device sends a fourth failure indication carrying the second shared frequency to the destination terminal device, and the side link transmission resource of the second shared frequency triggers a continuous LBT failure, that is, the side link transmission resource of the second shared frequency cannot transmit side link messages.

[0121] In one embodiment of this disclosure, a third sidelink RRC message is sent to the destination terminal device corresponding to the first destination address identifier, wherein the third sidelink RRC message carries a fourth failure indication. In another embodiment, a sidelink MAC CE message is sent to the destination terminal device corresponding to the first destination address identifier, wherein the sidelink MAC CE message carries a fourth failure indication.

[0122] Step 603: When it is determined that the side-link communication with the first destination address identifier has triggered a continuous LBT failure, a failure indication is reported to the network device or a backup side-link sending resource is determined for sending side-link messages.

[0123] In one example of this disclosure, when a persistent LBT failure is triggered during sidelink communication with the first destination address identifier, the terminal device may select a candidate sidelink transmission resource with a shared frequency or a candidate sidelink transmission resource with a non-shared frequency from at least one configured candidate sidelink transmission resource as a backup sidelink transmission resource.

[0124] Specifically, the terminal selects a candidate side-link transmission resource from at least one configured candidate side-link transmission resource that does not trigger a continuous LBT failure of the shared frequency, and uses it as a backup side-link transmission resource to send side-link messages.

[0125] In another example, when a persistent LBT failure is triggered during side link communication with the first destination address identifier, a candidate side link transmission resource with a non-shared frequency is selected from at least one configured candidate side link transmission resource as a backup side link transmission resource.

[0126] In one embodiment of this disclosure, a fourth RRC message is received from a network device, wherein the fourth RRC message carries candidate-side traverse transmission resources; wherein the candidate-side traverse transmission resources include candidate-side traverse transmission resources of shared frequency or candidate-side traverse transmission resources of non-shared frequency.

[0127] In another example, a second sidelink RRC message is received from a destination terminal device corresponding to at least one destination address identifier. This second sidelink RRC message carries a candidate sidelink transmission resource message. The candidate sidelink transmission resources include candidate sidelink transmission resources at shared frequencies or candidate sidelink transmission resources at non-shared frequencies.

[0128] The implementation of the sidelink communication method on shared frequencies in the embodiments provided above is also applicable to the sidelink communication method on unlicensed frequencies.

[0129] In summary, when a first destination address identifier exists among at least one destination address identifier used for sidelink communication on at least one shared frequency sidelink transmission resource, it is determined that sidelink communication with the first destination address identifier triggers a continuous LBT failure. Specifically, on the shared frequency sidelink transmission resource used for sidelink communication with the first destination address identifier, the number of LBT failures corresponding to the first destination address identifier is greater than or equal to a specified threshold number corresponding to the first destination address identifier. When a continuous LBT failure is triggered by sidelink communication with the first destination address identifier, a fourth failure indication is sent to the destination terminal device corresponding to the first destination address identifier. When it is determined that a continuous LBT failure is triggered by sidelink communication with the first destination address identifier, a failure indication is reported to the network device or a backup sidelink transmission resource is determined for sending sidelink messages. This ensures that the terminal device can promptly send data when LBT fails, avoiding data loss and increasing communication reliability.

[0130] This disclosure provides another sidelink communication method. Figure 7 This is a flowchart illustrating another sidelink communication method provided in an embodiment of the present disclosure. The sidelink communication method can be applied to network devices. The sidelink communication method can be executed alone, or it can be executed together with any embodiment of the present disclosure or possible implementations in the embodiments, or it can be executed together with any technical solution in the related technologies.

[0131] like Figure 7 As shown, the sidelink communication method may include the following steps:

[0132] Step 701: Send the first message to the terminal device.

[0133] In this embodiment of the disclosure, the first message may be, for example, an RRC message. In one example, the first message carries a specified timer and a specified number of thresholds to determine whether a persistent LBT failure has been triggered on the shared frequency side-link transmission resource. The first RRC message carries the same number of specified timers and specified number of thresholds, and may carry one specified timer and one specified number of thresholds. The specified timer is used to reset the LBT failure count upon timeout.

[0134] In another example, the first message carries at least one specified timer corresponding to the shared frequency, and at least one specified count threshold corresponding to the shared frequency, used to determine whether a persistent LBT failure is triggered on the side-link transmission resource of the shared frequency. The specified timer is used to reset the LBT failure count corresponding to the shared frequency upon timeout; the specified timers for at least one shared frequency may be the same or different; the specified count thresholds for at least one shared frequency may be the same or different.

[0135] The specified number of timers is at least one, corresponding to at least one shared frequency; the specified number of count thresholds is at least one, corresponding to at least one shared frequency.

[0136] In another example, the first message carries at least one specified timer corresponding to a destination address identifier, and at least one specified count threshold corresponding to a destination address identifier, used to determine whether a persistent LBT failure is triggered on the shared frequency side-link transmission resource. The specified timer is used to reset the LBT failure count corresponding to the destination address identifier upon timeout.

[0137] The specified number of timers is at least one, corresponding to at least one destination address identifier; the specified number of count thresholds is at least one, corresponding to at least one destination address identifier.

[0138] In this embodiment of the present disclosure, the network device sends a fourth RRC message to the terminal device, wherein the fourth RRC message carries candidate-side traversal transmission resources; wherein the candidate-side traversal transmission resources include candidate-side traversal transmission resources of shared frequency or candidate-side traversal transmission resources of non-shared frequency.

[0139] The implementation of the sidelink communication method on shared frequencies in the embodiments provided above is also applicable to the sidelink communication method on unlicensed frequencies.

[0140] In summary, network devices send a first message to terminal devices, which carries a specified timer and a specified number of thresholds, to determine whether a continuous LBT failure has been triggered on the shared frequency sidelink transmission resources. This enables terminal devices to promptly transmit data when an LBT failure occurs, avoiding data loss and increasing communication reliability.

[0141] This disclosure provides another sidelink communication method. Figure 8This is a flowchart illustrating another sidelink communication method provided in an embodiment of this disclosure. This sidelink communication method can be applied to network devices. This sidelink communication method can be executed alone, or it can be executed in conjunction with any embodiment of this disclosure or possible implementations within those embodiments, or it can be executed in conjunction with any technical solution in the related art.

[0142] like Figure 8 As shown, the sidelink communication method may include the following steps:

[0143] Step 801: Send the first message to the terminal device.

[0144] In this embodiment of the disclosure, the first message may be, for example, an RRC message. In one example, the first message carries a specified timer and a specified number of thresholds to determine whether a persistent LBT failure has been triggered on the shared frequency side-link transmission resource. The first RRC message carries the same number of specified timers and specified number of thresholds, and may carry one specified timer and one specified number of thresholds. The specified timer is used to reset the LBT failure count upon timeout.

[0145] In another example, the first message carries at least one specified timer corresponding to the shared frequency, and at least one specified count threshold corresponding to the shared frequency, used to determine whether a persistent LBT failure is triggered on the side-link transmission resource of the shared frequency. The specified timer is used to reset the LBT failure count corresponding to the shared frequency upon timeout; the specified timers for at least one shared frequency may be the same or different; the specified count thresholds for at least one shared frequency may be the same or different.

[0146] The specified number of timers is at least one, corresponding to at least one shared frequency; the specified number of count thresholds is at least one, corresponding to at least one shared frequency.

[0147] In another example, the first message carries at least one specified timer corresponding to a destination address identifier, and at least one specified count threshold corresponding to a destination address identifier, used to determine whether a persistent LBT failure is triggered on the shared frequency side-link transmission resource. The specified timer is used to reset the LBT failure count corresponding to the destination address identifier upon timeout.

[0148] The specified number of timers is at least one, corresponding to at least one destination address identifier; the specified number of count thresholds is at least one, corresponding to at least one destination address identifier.

[0149] Step 802: Receive a failure indication reported by the terminal device. The failure indication is used to indicate that the continuous LBT was triggered and failed.

[0150] In this embodiment of the disclosure, the network device schedules backup side-link transmission resources to the terminal device based on a failure indication. The backup side-link transmission resources can be transmitted via a side-link using a shared frequency, or via a side-link using a non-shared frequency.

[0151] In one embodiment of this disclosure, the failure indication includes: a first shared frequency of the sidelink transmission resources of the shared frequency that triggered the persistent LBT failure. Based on the failure indication, the network device schedules sidelink transmission resources of other shared frequencies besides the first shared frequency to the terminal device, or schedules sidelink transmission resources of non-shared frequencies to the terminal device.

[0152] In another example, the failure indication includes a first destination address identifier, wherein sidelink communication with the first destination address identifier triggers a persistent LBT failure. Based on the failure indication, the network device schedules sidelink transmission resources of a different shared frequency than those used for sidelink communication with the first destination address identifier to the terminal device, or schedules sidelink transmission resources of a non-shared frequency to the terminal device.

[0153] It should be noted that the explanation of the sidelink communication method executed by the terminal device in any of the foregoing embodiments also applies to the sidelink communication method executed by the network device, and the implementation principle is similar, so it will not be repeated here.

[0154] In summary, the network device sends a first message to the terminal device and receives a failure indication reported by the terminal device. The failure indication is used to indicate the triggering of continuous LBT failure, so that the terminal device can send data in a timely manner when LBT fails, avoid data loss, and increase communication reliability.

[0155] This disclosure provides another sidelink communication method. Figure 9 This is a flowchart illustrating another sidelink communication method provided in an embodiment of this disclosure. This sidelink communication method can be applied to a destination terminal device. This sidelink communication method can be executed alone, or it can be executed in conjunction with any embodiment of this disclosure or any possible implementation thereof, or it can be executed in conjunction with any technical solution in the related art.

[0156] like Figure 9As shown, the sidelink communication method may include the following steps:

[0157] Step 901: Receive a failure indication sent by the terminal device, wherein the failure indication includes: a first destination address identifier, wherein sidelink communication with the first destination address identifier triggers a continuous LBT failure.

[0158] In one embodiment of this disclosure, based on a failure indication, receiving sidelink messages from the terminal device on the sidelink transmission resource of the shared frequency where a persistent LBT failure occurs is stopped. In another embodiment, based on a failure indication, if a backup sidelink transmission resource exists, receiving sidelink messages from the terminal device on the backup sidelink transmission resource.

[0159] In one embodiment of this disclosure, a sidelink RRC message from a terminal device is received, wherein the sidelink RRC message carries a failure indication. In another embodiment, a sidelink MAC CE message sent by the terminal device is received, wherein the sidelink MAC CE message carries a failure indication.

[0160] It should be noted that the explanation of the sidelink communication method executed by the terminal device in any of the foregoing embodiments also applies to the sidelink communication method executed by the target terminal device, and the implementation principle is similar, so it will not be repeated here.

[0161] It should be noted that the above-mentioned possible implementations can be executed individually or in combination, and this disclosure does not limit them.

[0162] The methods provided in the embodiments of this disclosure above are described from the perspectives of a terminal device, a network device, and a destination terminal device. To implement the functions of the methods provided in the embodiments of this disclosure above, the terminal device, network device, and destination terminal device may include hardware structures and software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. One of the above functions may be executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules.

[0163] With the above Figures 2 to 6 Corresponding to the sidelink communication method provided in the embodiments, this disclosure also provides a sidelink communication device. Since the sidelink communication device provided in this disclosure is similar to the one described above... Figures 2 to 6The sidelink communication method provided in the embodiments corresponds to the sidelink communication method provided in the embodiments of this disclosure. Therefore, the implementation of the sidelink communication method is also applicable to the sidelink communication device provided in the embodiments of this disclosure, and will not be described in detail in the embodiments of this disclosure.

[0164] Figure 10 This is a schematic diagram of a sidelink communication device provided in an embodiment of the present disclosure. This sidelink communication device is applied to a terminal device.

[0165] like Figure 10 As shown, the sidelink communication device 1000 includes: a first processing unit 1010 and a second processing unit 1020.

[0166] The first processing unit 1010 is used to determine whether a persistent LBT failure is triggered on the side-link transmission resources of the shared frequency; the second processing unit 1020 is used to report a failure indication to the network device or determine a backup side-link transmission resource when the persistent LBT failure is triggered, for sending a side-link message.

[0167] As one possible implementation of this disclosure, the first processing unit 1010 is specifically configured to determine to trigger a continuous LBT failure on the side link transmission resource of the shared frequency when the number of LBT failures on the side link transmission resource of the shared frequency is greater than or equal to a specified number threshold.

[0168] As one possible implementation of this disclosure, the first processing unit 1010 is specifically configured to: reset the current LBT failure count to zero and stop the specified timer when the specified timer expires; and start or restart the specified timer when an LBT failure occurs on the side link transmission resource of the shared frequency, and increment the current LBT failure count by 1.

[0169] As one possible implementation of this disclosure, the sidelink communication device 1000 further includes: a transceiver unit, configured to receive a first RRC message from a network device, wherein the first RRC message carries the specified timer and the specified number of failures threshold; the specified timer is configured to reset the LBT failure count when a timeout occurs.

[0170] As one possible implementation of this disclosure, the first processing unit 1010 is specifically configured to, when a first shared frequency exists in at least one shared frequency, determine to trigger a continuous LBT failure on the side link transmission resource of the first shared frequency; wherein, on the side link transmission resource of the first shared frequency, the number of LBT failures corresponding to the first shared frequency is greater than or equal to a specified number threshold corresponding to the first shared frequency.

[0171] As one possible implementation of this disclosure, the transceiver unit is further configured to receive a second RRC message from the network device, wherein the second RRC message carries: at least one specified timer corresponding to a shared frequency, and at least one specified number threshold corresponding to a shared frequency; the specified timer is configured to reset the LBT failure count corresponding to the shared frequency when a timeout occurs; the specified timers corresponding to the at least one shared frequency are the same or different; the specified number thresholds corresponding to the at least one shared frequency are the same or different.

[0172] As one possible implementation of this disclosure, the first processing unit 1010 is specifically configured to, when a first destination address identifier exists among at least one destination address identifier used for sidelink communication on at least one shared frequency sidelink transmission resource, determine that sidelink communication with the first destination address identifier triggers a continuous LBT failure; wherein, on the shared frequency sidelink transmission resource used for sidelink communication with the first destination address identifier, the number of LBT failures corresponding to the first destination address identifier is greater than or equal to a specified number threshold corresponding to the first destination address identifier.

[0173] As a possible implementation of this disclosure, the transceiver unit is further configured to: receive a third RRC message from a network device, wherein the third RRC message carries: at least one specified timer corresponding to a destination address identifier, and at least one specified number of failure thresholds corresponding to a destination address identifier; the specified timer is configured to reset the LBT failure count corresponding to the destination address identifier upon timeout; or, receive a first sidelink RRC message from a destination terminal device corresponding to at least one destination address identifier, wherein the first sidelink RRC message carries: a specified timer corresponding to the destination address identifier, and a specified number of failure thresholds corresponding to the destination address identifier; wherein the specified timers corresponding to the at least one destination address identifier are the same or different; and the specified number of failure thresholds corresponding to the at least one destination address identifier are the same or different.

[0174] As one possible implementation of this disclosure, the second processing unit 1020 is specifically used to report a first failure indication to the network device when the continuous LBT failure is triggered.

[0175] As one possible implementation of this disclosure, the second processing unit 1020 is specifically configured to select the backup side link transmission resource from at least one configured candidate side link transmission resource when the continuous LBT failure is triggered.

[0176] As one possible implementation of this disclosure, the second processing unit 1020 is specifically configured to report a second failure indication carrying the first shared frequency to the network device when a persistent LBT failure is triggered on the side walkway transmission resource of the first shared frequency; wherein, on the side walkway transmission resource of the first shared frequency, the number of LBT failures corresponding to the first shared frequency is greater than or equal to a specified number threshold corresponding to the first shared frequency.

[0177] As one possible implementation of this disclosure, the second processing unit 1020 is specifically configured to, when a persistent LBT failure is triggered on the side link transmission resource of the first shared frequency, select a candidate side link transmission resource of the shared frequency or a candidate side link transmission resource of the non-shared frequency from at least one configured candidate side link transmission resources as the backup side link transmission resource; wherein, on the side link transmission resource of the first shared frequency, the number of LBT failures corresponding to the first shared frequency is greater than or equal to a specified number threshold corresponding to the first shared frequency.

[0178] As one possible implementation of this disclosure, the second processing unit 1020 is specifically configured to report a third failure indication carrying the first destination address identifier to the network device when a continuous LBT failure is triggered during sidelink communication with the first destination address identifier; wherein, on the sidelink transmission resource of the shared frequency used for sidelink communication with the first destination address identifier, the number of LBT failures corresponding to the first destination address identifier is greater than or equal to a specified number threshold corresponding to the first destination address identifier.

[0179] As one possible implementation of this disclosure, the second processing unit 1020 is specifically configured to, when a continuous LBT failure is triggered during side-link communication with the first destination address identifier, select a candidate side-link transmission resource with a shared frequency or a candidate side-link transmission resource with a non-shared frequency from at least one configured candidate side-link transmission resource as the backup side-link transmission resource; wherein, on the side-link transmission resource with a shared frequency used for side-link communication with the first destination address identifier, the number of LBT failures corresponding to the first destination address identifier is greater than or equal to a specified number threshold corresponding to the first destination address identifier.

[0180] As one possible implementation of this disclosure, the transceiver unit is further configured to: receive a fourth RRC message from a network device, wherein the fourth RRC message carries the candidate sidelink transmission resource; or receive a second sidelink RRC message from a destination terminal device corresponding to at least one destination address identifier, wherein the second sidelink RRC message carries the candidate sidelink transmission resource message.

[0181] As one possible implementation of this disclosure, the transceiver unit is further configured to send a fourth failure indication to the destination terminal device corresponding to the first destination address identifier when a continuous LBT failure is triggered during sidelink communication with the first destination address identifier; wherein, on the sidelink transmission resource of the shared frequency used for sidelink communication with the first destination address identifier, the number of LBT failures corresponding to the first destination address identifier is greater than or equal to a specified number threshold corresponding to the first destination address identifier.

[0182] As one possible implementation of this disclosure, the fourth failure indication is used to instruct the destination terminal device to stop receiving the terminal device's sidelink message on the sidelink transmission resource of the shared frequency where the continuous LBT failure occurs; or, the fourth failure indication is used to instruct the sidelink message to be received on the backup sidelink transmission resource when the backup sidelink transmission resource exists.

[0183] As one possible implementation of this disclosure, the fourth failure indication further carries: a second shared frequency; wherein, in the sidelink transmission resources of at least one shared frequency used for sidelink communication with the first destination address identifier, the sidelink transmission resources of the second shared frequency trigger the persistent LBT failure.

[0184] As a possible implementation of this disclosure, the transceiver unit is further configured to: send a third sidelink RRC message to the destination terminal device corresponding to the first destination address identifier, wherein the third sidelink RRC message carries the fourth failure indication; or send a sidelink MAC CE message to the destination terminal device corresponding to the first destination address identifier, wherein the sidelink MAC CE message carries the fourth failure indication.

[0185] The sidelink communication device of this disclosure is applied to a terminal device. It determines whether a persistent LBT failure is triggered on the sidelink transmission resources of the shared frequency. When a persistent LBT failure is triggered, it reports a failure indication to the network device or determines a backup sidelink transmission resource for sending sidelink messages. This enables the terminal device to send data in a timely manner when LBT fails, avoids data loss, and increases communication reliability.

[0186] With the above Figures 7 to 8 Corresponding to the sidelink communication method provided in the embodiments, this disclosure also provides a sidelink communication device. Since the sidelink communication device provided in this disclosure is similar to the one described above... Figures 7 to 8 The sidelink communication method provided in the embodiments corresponds to the sidelink communication method provided in the embodiments of this disclosure. Therefore, the implementation of the sidelink communication method is also applicable to the sidelink communication device provided in the embodiments of this disclosure, and will not be described in detail in the embodiments of this disclosure.

[0187] Figure 11 This is a schematic diagram of another sidelink communication device provided in an embodiment of this disclosure. This sidelink communication device is applied to a network device.

[0188] like Figure 11 As shown, the sidelink communication device 1100 includes a transceiver unit 1110.

[0189] The transceiver unit 1110 is used to send a first message to the terminal device; wherein the first message carries a specified timer and a specified number of thresholds, used to determine whether a continuous LBT failure is triggered on the side link transmission resource of the shared frequency.

[0190] As one possible implementation of this disclosure, the number of specified timers is at least one, corresponding to at least one shared frequency; the number of specified count thresholds is at least one, corresponding to at least one shared frequency; or, the number of specified timers is at least one, corresponding to at least one destination address identifier; the number of specified count thresholds is at least one, corresponding to at least one destination address identifier.

[0191] As one possible implementation of this disclosure, the transceiver unit 1110 is further configured to receive a failure indication reported by the terminal device, the failure indication being used to indicate a failure to trigger a continuous LBT.

[0192] As one possible implementation of this disclosure, the method further includes: scheduling backup side link transmission resources to the terminal device according to the failure indication; wherein the backup side link transmission resources are either transmission resources via a side link with a shared frequency or transmission resources via a side link with a non-shared frequency.

[0193] As one possible implementation of this disclosure, the failure indication includes: a first shared frequency of the sidelink transmission resource of the shared frequency that triggers the persistent LBT failure; or, the failure indication includes: a first destination address identifier, wherein sidelink communication with the first destination address identifier triggers the persistent LBT failure.

[0194] The sidelink communication device of this disclosure embodiment is applied to a network device. By sending a first message to a terminal device, the first message carries a specified timer and a specified number of thresholds to determine whether a continuous LBT failure is triggered on the sidelink transmission resource of the shared frequency. This enables the terminal device to send data in a timely manner when an LBT failure occurs, avoiding data loss and increasing communication reliability.

[0195] With the above Figure 9 Corresponding to the sidelink communication method provided in the embodiments, this disclosure also provides a sidelink communication device. Since the sidelink communication device provided in this disclosure is similar to the one described above... Figure 9 The sidelink communication method provided in the embodiments corresponds to the sidelink communication method provided in the embodiments of this disclosure. Therefore, the implementation of the sidelink communication method is also applicable to the sidelink communication device provided in the embodiments of this disclosure, and will not be described in detail in the embodiments of this disclosure.

[0196] Figure 12 This is a schematic diagram of another sidelink communication device provided in an embodiment of this disclosure. This sidelink communication device is applied to a destination terminal device.

[0197] like Figure 12 As shown, the sidelink communication device 1200 includes a transceiver unit 1210.

[0198] The transceiver unit 1210 is used to receive a failure indication sent by the terminal device, wherein the failure indication includes a first destination address identifier, and the continuous LBT failure is triggered by side link communication with the first destination address identifier.

[0199] As one possible implementation of this disclosure, according to the failure indication, receiving sidelink messages from the terminal device on the sidelink transmission resource of the shared frequency where the persistent LBT failure occurred is stopped; or, according to the failure indication, when a backup sidelink transmission resource exists, receiving sidelink messages from the terminal device on the backup sidelink transmission resource.

[0200] As one possible implementation of this disclosure, the transceiver unit 1210 is further configured to: receive a sidelink RRC message from the terminal device, wherein the sidelink RRC message carries the failure indication; or receive a sidelink MAC CE message sent by the terminal device, wherein the sidelink MAC CE message carries the failure indication.

[0201] To implement the above embodiments, this disclosure also proposes a sidelink communication device, which includes a processor and a memory. The memory stores a computer program, and the processor executes the computer program stored in the memory to cause the device to perform... Figures 2 to 6 The sidelink communication method described in the embodiment.

[0202] To implement the above embodiments, this disclosure also proposes another sidelink communication device, which includes a processor and a memory. The memory stores a computer program, and the processor executes the computer program stored in the memory to cause the device to perform... Figures 7 to 8 The sidelink communication method described in the embodiment.

[0203] To implement the above embodiments, this disclosure also proposes another sidelink communication device, which includes a processor and a memory. The memory stores a computer program, and the processor executes the computer program stored in the memory to cause the device to perform... Figure 9 The sidelink communication method described in the embodiment.

[0204] To implement the above embodiments, this disclosure also proposes a sidelink communication method, including: a processor and an interface circuit; the interface circuit is used to receive code instructions and transmit them to the processor; the processor is used to execute the code instructions to perform... Figures 2 to 6 The sidelink communication method described in the embodiment.

[0205] To implement the above embodiments, this disclosure also proposes another sidelink communication method, including: a processor and an interface circuit; the interface circuit is used to receive code instructions and transmit them to the processor; the processor is used to execute the code instructions to perform... Figures 7 to 8 The sidelink communication method described in the embodiment.

[0206] To implement the above embodiments, this disclosure also proposes another sidelink communication method, including: a processor and an interface circuit; the interface circuit is used to receive code instructions and transmit them to the processor; the processor is used to execute the code instructions to perform... Figure 9 The sidelink communication method described in the embodiment.

[0207] To implement the above embodiments, this disclosure proposes a computer-readable storage medium for storing instructions that, when executed, cause... Figures 2 to 6 The sidelink communication method described in the embodiment is implemented.

[0208] To implement the above embodiments, this disclosure proposes another computer-readable storage medium for storing instructions that, when executed, cause... Figures 7 to 8 The sidelink communication method described in the embodiment is implemented.

[0209] To implement the above embodiments, this disclosure proposes another computer-readable storage medium for storing instructions that, when executed, cause... Figure 9 The sidelink communication method described in the embodiment is implemented.

[0210] like Figure 13 As shown, Figure 13 This is a schematic diagram of the structure of a network device provided in an embodiment of this disclosure. (Refer to...) Figure 13 The network device 1300 includes a processing component 1322, which further includes at least one processor, and memory resources represented by memory 1332 for storing instructions, such as applications, that can be executed by the processing component 1322. The applications stored in memory 1332 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 1322 is configured to execute instructions to perform any of the methods described above applied to the network device, such as... Figures 7 to 8 The method of the embodiment.

[0211] Network device 1300 may also include a power supply component 1326 configured to perform power management of network device 1300, a wired or wireless network interface 1350 configured to connect network device 1300 to a network, and an input / output (I / O) interface 1358. Network device 1300 can operate on an operating system stored in memory 1332, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or similar.

[0212] Figure 14 This is a block diagram of a terminal device provided in an embodiment of this disclosure. For example, the terminal device 1400 may be a mobile phone, computer, digital broadcast user equipment, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0213] Reference Figure 14 The terminal device 1400 may include at least one of the following components: a processing component 1402, a memory 1404, a power supply component 1406, a multimedia component 1408, an audio component 1410, an input / output (I / O) interface 1412, a sensor component 1414, and a communication component 1416.

[0214] Processing component 1402 typically controls the overall operation of terminal device 1400, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 1402 may include at least one processor 1420 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 1402 may include at least one module to facilitate interaction between processing component 1402 and other components. For example, processing component 1402 may include a multimedia module to facilitate interaction between multimedia component 1408 and processing component 1402.

[0215] Memory 1404 is configured to store various types of data to support the operation of terminal device 1400. Examples of this data include instructions for any application or method operating on terminal device 1400, contact data, phonebook data, messages, pictures, videos, etc. Memory 1404 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0216] Power supply component 1406 provides power to various components of terminal device 1400. Power supply component 1406 may include a power management system, at least one power supply, and other components associated with generating, managing, and distributing power to terminal device 1400.

[0217] Multimedia component 1408 includes a screen that provides an output interface between the terminal device 1400 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes at least one touch sensor to sense touch, swipe, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or swipe action but also detect the wake-up time and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 1408 includes a front-facing camera and / or a rear-facing camera. When the terminal device 1400 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0218] Audio component 1410 is configured to output and / or input audio signals. For example, audio component 1410 includes a microphone (MIC) configured to receive external audio signals when terminal device 1400 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 1804 or transmitted via communication component 1416. In some embodiments, audio component 1410 also includes a speaker for outputting audio signals.

[0219] I / O interface 1412 provides an interface between processing component 1402 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0220] Sensor assembly 1414 includes at least one sensor for providing status assessments of various aspects of terminal device 1400. For example, sensor assembly 1414 may detect the on / off state of terminal device 1400, the relative positioning of components such as the display and keypad of terminal device 1400, changes in position of terminal device 1400 or a component of terminal device 1400, the presence or absence of user contact with terminal device 1400, orientation or acceleration / deceleration of terminal device 1400, and temperature changes of terminal device 1400. Sensor assembly 1414 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 1414 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 1414 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0221] Communication component 1416 is configured to facilitate wired or wireless communication between terminal device 1400 and other devices. Terminal device 1400 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 1416 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 1416 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0222] In an exemplary embodiment, the terminal device 1400 may be implemented by at least one application-specific integrated circuit (ASIC), digital signal processor (DSP), digital signal processing device (DSPD), programmable logic device (PLD), field-programmable gate array (FPGA), controller, microcontroller, microprocessor, or other electronic component for performing the above-described functions. Figures 2 to 5 The method shown.

[0223] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 1404 including instructions, which can be executed by the processor 1420 of the terminal device 1400 to complete the above-mentioned tasks. Figures 2 to 6 The methods shown, and / or, to complete the above Figure 9 The method is illustrated. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0224] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0225] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

[0226] To implement the above embodiments, this disclosure also provides a communication device. The communication device can be a network device, a user equipment, or a chip, chip system, or processor that supports the implementation of the above methods in a network device, or a chip, chip system, or processor that supports the implementation of the above methods in a user equipment. This device can be used to implement the methods described in any of the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

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

[0228] Optionally, the communication device may further include one or more memories, on which computer programs may be stored. The processor executes the computer programs to cause the communication device to perform the methods described in the above method embodiments. Optionally, the memories may also store data. The communication device and the memories may be provided separately or integrated together.

[0229] Optionally, the communication device may also include a transceiver and an antenna. A transceiver, also called a transceiver unit, transceiver, or transceiver circuit, is used to implement transmission and reception functions. A transceiver may include a receiver and a transmitter; the receiver, also called a receiver circuit, is used to implement the receiving function; the transmitter, also called a transmitter or transmitting circuit, is used to implement the transmitting function.

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

[0231] In one implementation, the processor may include a transceiver for implementing receive and transmit functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receive and transmit functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0232] In one implementation, the processor may store a computer program that runs on the processor, causing the communication device to perform the methods described in any of the above method embodiments. The computer program may be embedded in the processor; in this case, the processor may be implemented in hardware.

[0233] In one implementation, the communication device may include a circuit that can perform the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in this disclosure can be implemented on ICs (Integrated Circuits), analog ICs, RFICs, mixed-signal ICs, ASICs (Application Specific Integrated Circuits), PCBs (Printed Circuit Boards), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as CMOS (Complementary Metal Oxide Semiconductor), NMOS (nMetal-Oxide-Semiconductor), PMOS (Positive Channel Metal Oxide Semiconductor), BJT (Bipolar Junction Transistor), Bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0234] The communication device described in the above embodiments can be a network device or a user equipment, but the scope of the communication device described in this disclosure is not limited thereto. The communication device can be a standalone device or part of a larger device. For example, the communication device can be:

[0235] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0236] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

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

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

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

[0240] (6) Others, etc.

[0241] When the communication device can be a chip or a chip system, the chip may include a processor and an interface. There may be one or more processors, and multiple interfaces.

[0242] Optionally, the chip may also include memory for storing necessary computer programs and data.

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

[0244] This disclosure also provides a computer program product that, when executed by a computer, performs the above-described functions. Figures 2 to 6 Functionality of the embodiment.

[0245] This disclosure also provides a computer program product that, when executed by a computer, performs the above-described functions. Figures 7 to 8 Functionality of the embodiment.

[0246] This disclosure also provides a computer program product that, when executed by a computer, performs the above-described functions. Figure 9 Functionality of the embodiment.

[0247] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, DSL (Digital Subscriber Line)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density DVDs (Digital Video Discs)), or semiconductor media (e.g., SSDs (Solid State Disks)).

[0248] Those skilled in the art will understand that the various numerical designations such as "first," "second," etc., used in this disclosure are merely for the convenience of description and are not intended to limit the scope of the embodiments of this disclosure, nor do they indicate the order of events.

[0249] At least one of the features described in this disclosure can also be described as one or more, and multiple features can be two, three, four or more, and this disclosure does not impose any limitations. In the embodiments of this disclosure, for a technical feature, the technical features in that technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", etc., and there is no sequential order or size order among the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0250] The correspondences shown in the tables of this disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this disclosure is not limiting. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this disclosure may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headers of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

[0251] The predefined terms in this disclosure can be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0252] Those skilled in the art will recognize that the units and algorithm steps of the various examples 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 implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0253] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0254] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A method of sidelink communication, the method comprising: The method is applied to a terminal device, and comprises: determining whether a persistent LBT failure is triggered on a sidelink sending resource of a shared frequency; when the persistent LBT failure is triggered, determining a backup sidelink sending resource for sending a sidelink message; the step of determining the backup sidelink sending resource for sending the sidelink message when the persistent LBT failure is triggered comprises: selecting the backup sidelink sending resource from at least one candidate sidelink sending resource of the shared frequency when the persistent LBT failure is triggered, wherein the selected backup sidelink sending resource is a candidate sidelink sending resource of the shared frequency that does not trigger the persistent LBT failure.

2. The method of claim 1, wherein, the step of determining whether the persistent LBT failure is triggered on the sidelink sending resource of the shared frequency comprises: when the number of LBT failures on the sidelink sending resource of the shared frequency is greater than or equal to a specified number threshold, determining that the persistent LBT failure is triggered on the sidelink sending resource of the shared frequency.

3. The method of claim 2, wherein, the step of determining the number of LBT failures on the sidelink sending resource of the shared frequency comprises: when a specified timer expires, resetting the current number of LBT failures to zero and stopping the specified timer; when an LBT failure occurs on the sidelink sending resource of the shared frequency, starting or restarting the specified timer and performing a plus 1 process on the current number of LBT failures.

4. The method of claim 2, wherein, before the step of determining whether the persistent LBT failure is triggered on the sidelink sending resource of the shared frequency, the method further comprises: receiving a first RRC message from a network device, wherein the first RRC message carries a specified timer and the specified number threshold; the specified timer is used to reset the number of LBT failures when it expires.

5. The method of claim 1, wherein, the step of determining whether the persistent LBT failure is triggered on the sidelink sending resource of the shared frequency comprises: when there is a first shared frequency in at least one shared frequency, determining that the persistent LBT failure is triggered on a sidelink sending resource of the first shared frequency; wherein on the sidelink sending resource of the first shared frequency, the number of LBT failures corresponding to the first shared frequency is greater than or equal to a specified number threshold corresponding to the first shared frequency.

6. The method of claim 5, wherein, before the step of determining whether the persistent LBT failure is triggered on the sidelink sending resource of the shared frequency, the method further comprises: receiving a second RRC message from a network device, wherein the second RRC message carries a specified timer corresponding to at least one shared frequency and a specified number threshold corresponding to at least one shared frequency; the specified timer is used to reset the number of LBT failures corresponding to the shared frequency when it expires; the specified timers corresponding to the at least one shared frequency are the same or different; the specified number thresholds corresponding to the at least one shared frequency are the same or different.

7. The method of claim 1, wherein, the step of determining whether the persistent LBT failure is triggered on the sidelink sending resource of the shared frequency comprises: determine that a persistent LBT failure is triggered when there is a first destination address identity in at least one destination address identity of sidelink communication on at least one sidelink transmission resource of a shared frequency; wherein, on the sidelink transmission resource of the shared frequency for sidelink communication with the first destination address identity, a number of LBT failures corresponding to the first destination address identity is greater than or equal to a specified number threshold corresponding to the first destination address identity.

8. The method of claim 7, wherein, Before determining whether the persistent LBT failure is triggered on the sidelink transmission resource of the shared frequency, further comprising: receiving a third RRC message from a network device, wherein the third RRC message carries a specified timer corresponding to at least one destination address identity and a specified number threshold corresponding to at least one destination address identity; the specified timer is used to reset the number of LBT failures corresponding to the destination address identity when it expires; or, receiving a first sidelink RRC message from a destination terminal device corresponding to at least one destination address identity, wherein the first sidelink RRC message carries a specified timer corresponding to the destination address identity and a specified number threshold corresponding to the destination address identity; wherein the specified timers corresponding to the at least one destination address identity are the same or different; the specified number thresholds corresponding to the at least one destination address identity are the same or different.

9. The method of claim 1 or 5, wherein, The determination of the backup sidelink transmission resource for transmitting the sidelink message when the persistent LBT failure is triggered comprises: selecting a candidate sidelink transmission resource of a shared frequency or a candidate sidelink transmission resource of a non-shared frequency from at least one candidate sidelink transmission resource configured as the backup sidelink transmission resource when a persistent LBT failure is triggered on a first sidelink transmission resource of a shared frequency; wherein, on the first sidelink transmission resource of the shared frequency, a number of LBT failures corresponding to the first shared frequency is greater than or equal to a specified number threshold corresponding to the first shared frequency.

10. The method of claim 1 or 7, wherein, The determination of the backup sidelink transmission resource for transmitting the sidelink message when the persistent LBT failure is triggered comprises: selecting a candidate sidelink transmission resource of a shared frequency or a candidate sidelink transmission resource of a non-shared frequency from at least one candidate sidelink transmission resource configured as the backup sidelink transmission resource when a persistent LBT failure is triggered for sidelink communication with a first destination address identity; wherein, on the sidelink transmission resource of the shared frequency for sidelink communication with the first destination address identity, a number of LBT failures corresponding to the first destination address identity is greater than or equal to a specified number threshold corresponding to the first destination address identity.

11. The method of claim 1, wherein, The method further comprises: receiving a fourth RRC message from a network device, wherein the fourth RRC message carries the candidate sidelink transmission resource; or, receiving a second sidelink RRC message from a corresponding destination terminal device identified by at least one destination address, wherein the second sidelink RRC message carries the candidate sidelink transmission resource message.

12. The method of claim 1 or 7, wherein, The method further comprises: sending a fourth failure indication to a corresponding destination terminal device of the first destination address identification when a sidelink communication with the first destination address identification triggers a continuous LBT failure; wherein the number of LBT failures corresponding to the first destination address identification on the sidelink transmission resource of the shared frequency used for sidelink communication with the first destination address identification is greater than or equal to a specified number threshold corresponding to the first destination address identification.

13. The method of claim 12, wherein, the fourth failure indication is used to instruct the destination terminal device to stop receiving the sidelink message of the terminal device on the sidelink transmission resource of the shared frequency where the continuous LBT failure occurs; or, the fourth failure indication is used to instruct to receive the sidelink message on a backup sidelink transmission resource when the backup sidelink transmission resource exists.

14. The method of claim 12, wherein, The fourth failure indication also carries a second shared frequency; wherein the sidelink transmission resource of the second shared frequency triggers the continuous LBT failure among the sidelink transmission resources of at least one shared frequency used for sidelink communication with the first destination address identification.

15. The method of claim 12, wherein, The sending of the fourth failure indication to the corresponding destination terminal device of the first destination address identification comprises: sending a third sidelink RRC message to the corresponding destination terminal device of the first destination address identification, wherein the third sidelink RRC message carries the fourth failure indication; or, sending a sidelink MAC CE message to the corresponding destination terminal device of the first destination address identification, wherein the sidelink MAC CE message carries the fourth failure indication.

16. A method of sidelink communication, comprising: Applied to a network device, the method comprises: sending a first message to a terminal device; wherein the first message carries a specified timer and a specified number threshold, which are used to determine whether a continuous LBT failure is triggered on a sidelink transmission resource of a shared frequency; when the continuous LBT failure is triggered, the terminal device selects a backup sidelink transmission resource from at least one candidate sidelink transmission resource configured, which is used to send a sidelink message; wherein the selected backup sidelink transmission resource is a candidate sidelink transmission resource of a shared frequency that does not trigger a continuous LBT failure.

17. The method of claim 16, wherein, The number of specified timers is at least one, corresponding to at least one shared frequency; the number of specified number thresholds is at least one, corresponding to at least one shared frequency; or, The number of specified timers is at least one, corresponding to at least one destination address identification; the number of specified number thresholds is at least one, corresponding to at least one destination address identification.

18. A method of sidelink communication, comprising: Applied to a destination terminal device, the method comprises: receive a failure indication sent by a terminal device, wherein the failure indication comprises: a first destination address identifier, wherein a sidelink communication with the first destination address identifier on a sidelink sending resource of a shared frequency triggers a continuous LBT failure; according to the failure indication, when a backup sidelink sending resource exists, receive a sidelink message of the terminal device on the backup sidelink sending resource; wherein the backup sidelink sending resource is a candidate sidelink sending resource of the shared frequency without triggering a continuous LBT failure.

19. The method of claim 18, wherein, The receiving the failure indication sent by the terminal device comprises: receiving a sidelink RRC message of the terminal device, wherein the sidelink RRC message carries the failure indication; or receiving a sidelink MAC CE message sent by the terminal device, wherein the sidelink MAC CE message carries the failure indication.

20. An apparatus for sidelink communication, the apparatus comprising: The apparatus comprises a processor and a memory, the memory stores a computer program, and the processor executes the computer program stored in the memory to enable the apparatus to perform the method of any one of claims 1 to 15.

21. An apparatus for sidelink communication, the apparatus comprising: The apparatus comprises a processor and a memory, the memory stores a computer program, and the processor executes the computer program stored in the memory to enable the apparatus to perform the method of any one of claims 16 to 17.

22. An apparatus for sidelink communication, the apparatus comprising: The apparatus comprises a processor and a memory, the memory stores a computer program, and the processor executes the computer program stored in the memory to enable the apparatus to perform the method of any one of claims 18 to 19.

Images