Method and apparatus for canceling SL consecutive LBT failures, communication device, communication system, and storage medium

WO2024229635A1PCT designated stage expired Publication Date: 2024-11-14BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2023/092616
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-06
Publication Date
2024-11-14

Smart Images

  • Figure CN2023092616_14112024_PF_FP_ABST
    Figure CN2023092616_14112024_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the present disclosure are a method and apparatus for canceling SL consecutive LBT failures, a communication device, a communication system, and a storage medium. The method comprises: when an SL consecutive LBT failure canceling condition is met, canceling the SL consecutive LBT failures triggered by a resource block set. The method of the present disclosure improves the accuracy of canceling the SL consecutive LBT failures triggered by the resource block set.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for canceling SL continuous LBT failure, communication equipment, communication system, and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a method and apparatus for canceling SL continuous LBT failures, a communication device, a communication system, and a storage medium. Background Art

[0002] Sidelink (SL) communications can use unlicensed spectrum. When a terminal sends SL data on the unlicensed spectrum, it must also perform listen to talk (LBT). The continuous LBT failure mechanism also applies to SL communications on the unlicensed spectrum.

[0003] Summary of the Invention

[0004] The method disclosed in the present invention can be used to solve the technical problem of "how the terminal cancels the SL continuous LBT failure triggered by the resource block set".

[0005] The present disclosure provides a method and apparatus for canceling SL continuous LBT failures, a communication device, a communication system, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, a method for canceling SL continuous LBT failure is proposed, comprising:

[0007] If the SL continuous LBT failure cancellation conditions are met, the SL continuous LBT failure triggered by the resource block set will be canceled.

[0008] According to a second aspect of an embodiment of the present disclosure, a method for canceling SL continuous LBT failure is proposed, comprising:

[0009] A control instruction is sent to the terminal, where the control instruction is used by the terminal to determine that a SL continuous LBT failure cancellation condition is met and to cancel the SL continuous LBT failure triggered by the resource block set.

[0010] According to a third aspect of an embodiment of the present disclosure, a method for canceling SL continuous LBT failure is proposed, which is used in a communication system, wherein the communication system includes a network device and a terminal. The method includes:

[0011] The terminal meets the SL continuous LBT failure cancellation condition and cancels the SL continuous LBT failure triggered by the resource block set.

[0012] According to a fourth aspect of an embodiment of the present disclosure, a first device for canceling SL continuous LBT failure is provided, comprising:

[0013] The processing module is used to meet the SL continuous LBT failure cancellation condition and cancel the SL continuous LBT failure triggered by the resource block set.

[0014] According to a fifth aspect of an embodiment of the present disclosure, a second device for canceling SL continuous LBT failure is provided, comprising:

[0015] The sending module is used to send a control instruction to the terminal, where the control instruction is used by the terminal to determine that the SL continuous LBT failure cancellation condition is met and cancel the SL continuous LBT failure triggered by the resource block set.

[0016] According to a sixth aspect of an embodiment of the present disclosure, a communication device is provided, including:

[0017] one or more processors;

[0018] The processor is used to call instructions to enable the communication device to execute the method for canceling SL continuous LBT failure described in any one of the first aspect and the second aspect.

[0019] According to the seventh aspect of an embodiment of the present disclosure, a communication system is proposed, characterized in that it includes a terminal and a network device, wherein the terminal is configured to implement the method for canceling SL continuous LBT failure described in the first aspect, and the network device is configured to implement the method for canceling SL continuous LBT failure described in the second aspect.

[0020] According to the eighth aspect of the embodiment of the present disclosure, a storage medium is proposed, which stores instructions, and is characterized in that when the instructions are executed on a communication device, the communication device executes the method for canceling SL continuous LBT failure as described in any one of the first and second aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The above and / or additional aspects and advantages of the present disclosure will become apparent and readily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0022] FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure;

[0023] FIG2 is an interactive schematic diagram illustrating a method for canceling SL continuous LBT failure according to an embodiment of the present disclosure;

[0024] 3a-3j are flowcharts illustrating a method for canceling SL continuous LBT failure according to an embodiment of the present disclosure;

[0025] FIG4 is a flow chart of a method for canceling SL continuous LBT failure according to an embodiment of the present disclosure;

[0026] 5a-5b are flowcharts illustrating a method for canceling SL continuous LBT failure according to an embodiment of the present disclosure;

[0027] FIG6 a is a schematic structural diagram of a first device for canceling SL continuous LBT failures proposed in an embodiment of the present disclosure;

[0028] FIG6 b is a schematic structural diagram of a second device for canceling SL continuous LBT failures proposed in an embodiment of the present disclosure;

[0029] FIG7a is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure;

[0030] FIG7 b is a schematic structural diagram of a chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0031] The embodiments of the present disclosure provide a method and apparatus for canceling SL continuous LBT failures, a communication device, a communication system, and a storage medium.

[0032] In a first aspect, an embodiment of the present disclosure provides a method for canceling SL continuous LBT failures, the method comprising:

[0033] If the SL continuous LBT failure cancellation conditions are met, the SL continuous LBT failure triggered by the resource block set will be canceled.

[0034] In the above embodiment, the terminal can cancel the SL continuous LBT failure triggered by the resource block set when the SL continuous LBT failure cancellation condition is met, thereby improving the accuracy of canceling the SL continuous LBT failure triggered by the resource block set, and avoiding the incorrect indication of the information of the resource block set that triggered the SL continuous LBT failure to the network device.

[0035] In conjunction with some embodiments of the first aspect, in some embodiments, satisfying the SL continuous LBT failure cancellation condition includes at least one of the following:

[0036] The resource allocation mode of the terminal is switched;

[0037] reconfiguring the resource pool to which the resource block set belongs;

[0038] The resource pool scheduled by the network device for the terminal is switched from the resource pool to which the resource block set belongs to another resource pool

[0039] The resource pool selected by the terminal is switched from the resource pool to which the resource block set belongs to another resource pool;

[0040] Medium access control (MAC) entity reset;

[0041] The MAC entity resets the SL function for any unicast connection.

[0042] In the above embodiment, the conditions under which the terminal cancels the SL continuous LBT of the resource block set are proposed, ensuring that the terminal can successfully cancel the SL continuous LBT of the resource block set, thereby effectively avoiding the error indication of the resource block set that triggers the SL continuous LBT failure to the network device.

[0043] In combination with some embodiments of the first aspect, in some embodiments, satisfying the SL continuous LBT failure cancellation condition and canceling the SL continuous LBT failure triggered by the resource block set includes:

[0044] Receive control instructions sent by network devices;

[0045] According to the control instruction, it is determined that the SL continuous LBT failure cancellation condition is met, and the SL continuous LBT failure triggered by the resource block set is canceled.

[0046] In the above embodiment, the terminal can determine whether the SL continuous LBT failure cancellation condition is met based on the control instruction sent by the network device, and cancel the SL continuous LBT failure triggered by the resource block set, thereby ensuring that the terminal can successfully cancel the SL continuous LBT of the resource block set, thereby effectively avoiding the erroneous indication of the information of the resource block set that triggered the SL continuous LBT failure to the network device.

[0047] In combination with some embodiments of the first aspect, in some embodiments, determining, according to the control instruction, that the SL continuous LBT failure cancellation condition is satisfied, and canceling the SL continuous LBT failure triggered by the resource block set includes:

[0048] According to the control instruction, it is determined that the resource allocation mode of the terminal is switched, and the SL continuous LBT failure triggered by the resource block set is canceled. The control instruction is used to configure or reconfigure the resource allocation mode of the terminal.

[0049] In the above embodiment, the control instruction is limited to configuring or reconfiguring the resource allocation mode of the terminal. When the terminal determines that the resource allocation mode of the terminal has switched based on the control instruction for configuring or reconfiguring the resource allocation mode of the terminal, the SL continuous LBT failure triggered by the resource block set is canceled, ensuring that the terminal can successfully cancel the SL continuous LBT of the resource block set, thereby effectively avoiding erroneous indication of the information of the resource block set that triggered the SL continuous LBT failure to the network device.

[0050] In combination with some embodiments of the first aspect, in some embodiments, determining, according to the control instruction, that the resource allocation mode of the terminal is switched, and canceling the SL continuous LBT failure triggered by the resource block set includes:

[0051] According to the control instruction, determining that the resource allocation mode of the terminal is switched from a network scheduling mode to an autonomous selection mode;

[0052] A resource block set in a resource pool scheduled by the network device triggers a SL continuous LBT failure and is not cancelled, and the SL continuous LBT failure triggered by the resource block set is cancelled.

[0053] In the above embodiment, when the terminal determines that the resource allocation mode of the terminal is switched from the network scheduling mode to the autonomous selection mode based on the control instruction used to configure the resource allocation mode of the terminal, if there is a resource block set in the resource pool scheduled by the network device that triggers the SL continuous LBT failure and is not canceled, the SL continuous LBT triggered by the resource block set is canceled. Therefore, when the resource allocation mode of the terminal is switched from the network scheduling mode to the autonomous selection mode, the SL continuous LBT failure triggered by the resource block set in the resource pool scheduled by the network is canceled, ensuring that the terminal can successfully cancel the SL continuous LBT triggered by the resource block set, thereby effectively avoiding the erroneous indication to the network device of the information of the resource block set that triggered the SL continuous LBT failure.

[0054] In combination with some embodiments of the first aspect, in some embodiments, determining, according to the control instruction, that the resource allocation mode of the terminal is switched, and canceling the SL continuous LBT failure triggered by the resource block set includes:

[0055] According to the control instruction, determining that the resource allocation mode of the terminal is switched from an autonomous selection mode to a network scheduling mode;

[0056] A resource block set in the resource pool selected by the terminal triggers a SL continuous LBT failure and is not cancelled, and the SL continuous LBT failure triggered by the resource block set is cancelled.

[0057] In the above embodiment, when the terminal determines that the resource allocation mode of the terminal is switched from the autonomous selection mode to the network scheduling mode based on the control instruction used to configure the resource allocation mode of the terminal, if there is a resource block set in the resource pool selected by the terminal that triggers the SL continuous LBT failure and is not canceled, the SL continuous LBT triggered by the resource block set is canceled. Therefore, when the resource allocation mode of the terminal is switched from the autonomous selection mode to the network scheduling mode, the SL continuous LBT failure triggered by the resource block set in the resource pool selected by the terminal is canceled, ensuring that the terminal can successfully cancel the SL continuous LBT triggered by the resource block set, thereby effectively avoiding the erroneous indication of the information of the resource block set that triggered the SL continuous LBT failure to the network device.

[0058] In combination with some embodiments of the first aspect, in some embodiments, determining, according to the control instruction, that the SL continuous LBT failure cancellation condition is satisfied and canceling the SL continuous LBT failure triggered by the resource block set includes:

[0059] The control instruction is used to reconfigure a resource pool, where a resource block set in the reconfigured resource pool triggers a SL continuous LBT failure and is not cancelled, and cancels the SL continuous LBT failure triggered by the resource block set.

[0060] In the above embodiment, the control instruction is limited to reconfiguring the resource pool. When the terminal receives the control instruction for reconfiguring the resource pool, if there is a resource block set in the resource pool that triggers SL continuous LBT failure and has not been canceled, the SL continuous LBT failure triggered by the resource block set is canceled, ensuring that the terminal can successfully cancel the SL continuous LBT of the resource block set, thereby effectively avoiding erroneous indication of information about the resource block set that triggered the SL continuous LBT failure to the network device.

[0061] In combination with some embodiments of the first aspect, in some embodiments, determining, according to the control instruction, that the SL continuous LBT failure cancellation condition is satisfied and canceling the SL continuous LBT failure triggered by the resource block set includes:

[0062] The control instruction is used to instruct the network device to switch the resource pool scheduled for the terminal from the current resource pool to other resource pools. A resource block set in the current resource pool has triggered an SL continuous LBT failure and has not been canceled, and the SL continuous LBT failure triggered by the resource block set is canceled.

[0063] In the above embodiment, the control instruction is limited to instructing the network device to switch the resource pool scheduled for the terminal from the current resource pool to other resource pools. When the resource pool scheduled by the terminal in the network changes, if there is a resource block set in the current resource pool that triggers SL continuous LBT failure and is not canceled, the SL continuous LBT failure triggered by the resource block set is canceled, ensuring that the terminal can successfully cancel the SL continuous LBT of the resource block set, thereby effectively avoiding the erroneous indication of the information of the resource block set that triggered the SL continuous LBT failure to the network device.

[0064] In combination with some embodiments of the first aspect, in some embodiments, satisfying the SL continuous LBT failure cancellation condition and canceling the SL continuous LBT failure triggered by the resource block set includes:

[0065] The resource pool selected by the terminal is changed from the current resource pool to another resource pool;

[0066] A resource block set in the current resource pool triggers a SL continuous LBT failure and is not canceled, and the SL continuous LBT failure triggered by the resource block set is canceled.

[0067] In the above embodiment, when the resource pool autonomously selected by the terminal changes, if there is a resource block set in the current resource pool that triggers SL continuous LBT failure and has not been canceled, the SL continuous LBT failure triggered by the resource block set is canceled, ensuring that the terminal can successfully cancel the SL continuous LBT of the resource block set, thereby effectively avoiding the erroneous indication of the information of the resource block set that triggered the SL continuous LBT failure to the network device.

[0068] In combination with some embodiments of the first aspect, in some embodiments, satisfying the SL continuous LBT failure cancellation condition and canceling the SL continuous LBT failure triggered by the resource block set includes:

[0069] The MAC entity is reset to cancel the SL continuous LBT failure triggered by the resource block set.

[0070] In the above embodiment, the terminal can cancel the SL continuous LBT failure triggered by the resource block set when the MAC entity is reset, ensuring that the terminal can successfully cancel the SL continuous LBT of the resource block set, thereby effectively avoiding the erroneous indication of the information of the resource block set that triggered the SL continuous LBT failure to the network device.

[0071] In combination with some embodiments of the first aspect, in some embodiments, the resource block set is a resource block set in the configured resource pool that has triggered SL continuous LBT failure and has not been canceled.

[0072] In the above embodiment, the resource block set is limited to the resource block set in the configured resource pool that has triggered the SL continuous LBT failure and has not been canceled, so as to ensure that the terminal can accurately and effectively cancel the SL continuous LBT of the resource block set, thereby effectively avoiding the erroneous indication of the information of the resource block set that triggered the SL continuous LBT failure to the network device.

[0073] In combination with some embodiments of the first aspect, in some embodiments, satisfying the SL continuous LBT failure cancellation condition and canceling the SL continuous LBT failure triggered by the resource block set includes:

[0074] The MAC entity resets the SL function for any unicast connection and cancels the SL continuous LBT failure triggered by the resource block set associated with any unicast connection.

[0075] In the above embodiment, when the MAC entity resets the SL function for any unicast connection, the terminal can cancel the SL continuous LBT failure triggered by the resource block set associated with any unicast connection, thereby ensuring that the terminal successfully cancels the SL continuous LBT of the resource block set associated with the unicast connection, thereby effectively avoiding the erroneous indication of the information of the resource block set that triggered the SL continuous LBT failure to the network device.

[0076] In combination with some embodiments of the first aspect, in some embodiments, the set of resource blocks associated with any unicast connection is a set of resource blocks used by at least one of the physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH), and physical sidelink feedback channel (PSFCH) associated with any unicast connection.

[0077] In the above embodiment, it is defined that the resource block set associated with any unicast connection is the resource block set used by at least one of the PSSCH, PSCCH, and PSFCH associated with any unicast connection, thereby ensuring that the terminal successfully cancels the SL continuous LBT of the resource block set associated with the unicast connection, thereby effectively avoiding erroneous indication to the network of the information of the resource block set that triggered the failure of SL continuous LBT.

[0078] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0079] The MAC entity is reset and the SL continuous LBT failure reporting process is canceled.

[0080] In the above embodiment, the terminal can cancel the SL continuous LBT failure reporting process when the MAC entity is reset, thereby effectively avoiding the erroneous sending of SL continuous LBT failure to the network device.

[0081] In conjunction with some embodiments of the first aspect, in some embodiments, the canceling of the SL continuous LBT failure reporting process includes at least one of the following:

[0082] A first report is being generated, and generating the first report is canceled, where the first report is used to indicate to the network device information about the set of resource blocks that trigger SL continuous LBT failure;

[0083] The first report has been generated, and sending or resending the first report to the network device is canceled.

[0084] In the above embodiment, if the first report for indicating to the network device the information of the resource block set that triggered the SL continuous LBT failure is being generated, the terminal cancels the generation of the first report; if the first report has already been generated, the sending of the first report to the network device is canceled, thereby effectively avoiding the erroneous indication to the network device of the information of the resource block set that triggered the SL continuous LBT failure.

[0085] In a second aspect, an embodiment of the present disclosure provides a method for canceling SL continuous LBT failures, including:

[0086] A control instruction is sent to the terminal, where the control instruction is used by the terminal to determine that a SL continuous LBT failure cancellation condition is met and to cancel the SL continuous LBT failure triggered by the resource block set.

[0087] In the above embodiment, the network device can send a control instruction to the terminal, so that the terminal can determine, based on the control instruction, that the SL continuous LBT failure cancellation condition is met and cancel the control instruction of the SL continuous LBT failure triggered by the resource block set, thereby improving the accuracy of the terminal in canceling the SL continuous LBT failure triggered by the resource block set, and avoiding the terminal from erroneously indicating to the network device the information of the resource block set that triggered the SL continuous LBT failure.

[0088] In conjunction with some embodiments of the second aspect, in some embodiments, satisfying the SL continuous LBT failure cancellation condition includes at least one of the following:

[0089] The resource allocation mode of the terminal is switched;

[0090] reconfiguring the resource pool to which the resource block set belongs;

[0091] The resource pool scheduled by the network device for the terminal is switched from the resource pool to which the resource block set belongs to another resource pool.

[0092] In combination with some embodiments of the second aspect, in some embodiments, the control instruction is used to configure the resource allocation method of the terminal, and the control instruction is used by the terminal to determine that the resource allocation method of the terminal has switched and cancel the SL continuous LBT failure triggered by the resource block set, and the resource block set triggered the SL continuous LBT failure and was not canceled.

[0093] In combination with some embodiments of the second aspect, in some embodiments, the control instruction is used to reconfigure the resource pool, and the control instruction is used by the terminal to cancel the SL continuous LBT failure triggered by the resource block set when a resource block set in the reconfigured resource pool has triggered the SL continuous LBT failure and has not been canceled.

[0094] In combination with some embodiments of the second aspect, in some embodiments, the control instruction is used to instruct the network device to switch the resource pool scheduled for the terminal from the current resource pool to other resource pools, and the control instruction is used by the terminal to cancel the SL continuous LBT failure triggered by the resource block set in the current resource pool when the SL continuous LBT failure is triggered by the resource block set and has not been canceled.

[0095] In a third aspect, an embodiment of the present disclosure provides a method for canceling SL continuous LBT failures, for use in a communication system, the communication system including a network device and a terminal, the method comprising:

[0096] The terminal meets the SL continuous LBT failure cancellation condition and cancels the SL continuous LBT failure triggered by the resource block set.

[0097] In the above embodiment, the network device can send a control instruction to the terminal, so that the terminal can determine, based on the control instruction, that the SL continuous LBT failure cancellation condition is met and cancel the control instruction of the SL continuous LBT failure triggered by the resource block set, thereby improving the accuracy of the terminal in canceling the SL continuous LBT failure triggered by the resource block set, and avoiding the terminal from erroneously indicating to the network device the information of the resource block set that triggered the SL continuous LBT failure.

[0098] In conjunction with some embodiments of the third aspect, in some embodiments, satisfying the SL continuous LBT failure cancellation condition includes at least one of the following:

[0099] The resource allocation mode of the terminal is switched;

[0100] reconfiguring the resource pool to which the resource block set belongs;

[0101] The resource pool scheduled by the network device for the terminal is switched from the resource pool to which the resource block set belongs to another resource pool

[0102] The resource pool selected by the terminal is switched from the resource pool to which the resource block set belongs to another resource pool;

[0103] Media Access Control MAC entity reset;

[0104] The MAC entity resets the SL function for any unicast connection.

[0105] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes:

[0106] The network device sends a control instruction;

[0107] The terminal determines, according to the control instruction, that the SL continuous LBT failure cancellation condition is satisfied, and cancels the SL continuous LBT failure triggered by the resource block set.

[0108] In conjunction with some embodiments of the third aspect, in some embodiments, satisfying the SL continuous LBT failure cancellation condition and canceling the SL continuous LBT failure triggered by the resource block set includes:

[0109] The MAC entity is reset to cancel the SL continuous LBT failure triggered by the resource block set.

[0110] In conjunction with some embodiments of the third aspect, in some embodiments, satisfying the SL continuous LBT failure cancellation condition and canceling the SL continuous LBT failure triggered by the resource block set includes:

[0111] The MAC entity resets the SL function for any unicast connection and cancels the SL continuous LBT failure triggered by the resource block set associated with any unicast connection.

[0112] In a fourth aspect, an embodiment of the present disclosure provides a first device for canceling SL continuous LBT failure, comprising:

[0113] The processing module is used to meet the SL continuous LBT failure cancellation condition and cancel the SL continuous LBT failure triggered by the resource block set.

[0114] In a fifth aspect, the embodiments of the present disclosure provide a second device for canceling SL continuous LBT failure, including:

[0115] The sending module is used to send a control instruction to the terminal, where the control instruction is used by the terminal to determine that the SL continuous LBT failure cancellation condition is met and cancel the SL continuous LBT failure triggered by the resource block set.

[0116] In the sixth aspect, an embodiment of the present disclosure proposes a communication device, which includes: one or more processors; one or more memories for storing instructions; wherein the processor is used to call the instructions so that the communication device executes the method for canceling SL continuous LBT failure as described in the first and second aspects, and the optional implementation methods of the first and second aspects.

[0117] In the seventh aspect, an embodiment of the present disclosure proposes a communication system, which includes: a terminal and a network device; wherein the terminal is configured to execute the method described in the first aspect and the optional implementation of the first aspect, and the network device is configured to execute the method described in the second aspect and the optional implementation of the second aspect.

[0118] In an eighth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first aspect, the optional implementation of the first aspect, the second aspect, and the optional implementation of the second aspect.

[0119] In a ninth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the first aspect, the optional implementation of the first aspect, the second aspect, and the optional implementation of the second aspect.

[0120] In a tenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect, the optional implementation of the first aspect, the second aspect, and the optional implementation of the second aspect.

[0121] It is understandable that the first device for canceling consecutive SL LBT failures, the second device for canceling consecutive SL LBT failures, the communication device, the communication system, the storage medium, the program product, and the computer program are all used to implement the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0122] The present disclosure provides a method and apparatus for canceling consecutive SL LBT failures, a communication device, a communication system, and a storage medium. In some embodiments, the term "method for canceling consecutive SL LBT failures" is interchangeable with terms such as "information processing method" and "communication method," and the term "information transmission device" is interchangeable with terms such as "information processing device" and "communication device," and the term "information processing system" and "communication system" are interchangeable.

[0123] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0124] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0125] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0126] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0127] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0128] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0129] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0130] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0131] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0132] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0133] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0134] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0135] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0136] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0137] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0138] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, it can also be called device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it can also be set as a structure in which the terminal has all or part of the functions of the access network device. In addition, language such as "uplink" and "downlink" can also be replaced by language corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0139] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0140] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0141] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0142] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0143] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1, the communication system 100 may include a terminal 101 and a network device 102. The network device 102 may include at least one of an access network device and a core network device.

[0144] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0145] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB) in a 5G communication system, a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a WiFi system, but is not limited thereto.

[0146] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0147] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0148] In some embodiments, a core network device may be a single device comprising one or more network elements, or may be a plurality of devices or a group of devices, each comprising all or part of one or more network elements. A network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

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

[0150] The following embodiments of the present disclosure may be applied to the communication system 100 shown in Figure 1, or a portion thereof, but are not limited thereto. The entities shown in Figure 1 are illustrative only. The communication system may include all or part of the entities shown in Figure 1, or may include other entities outside of Figure 1. The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0151] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0152] In order to support direct communication between terminals, the SL communication mode is introduced. Optionally, the interface between the terminals can be PC5.

[0153] Optionally, based on the correspondence between the transmitting terminal and the receiving terminal, three transmission modes are supported on the SL: unicast, multicast, and broadcast. Exemplarily, the transmitting terminal sends SL control information (Sidelink Control Information, SCI) on the PSCCH channel and sends the second-stage SCI on the PSSCH channel, such as the resource location of the transmitted data and the source and destination identifiers. Exemplarily, for HARQ feedback-enabled data packets, the receiving terminal performs hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback on the PSSCH channel.

[0154] Optionally, SL communication has two transmission resource allocation methods, one is a network dynamic scheduling method (for example, it can be a network scheduling method), and the other is a method in which the terminal independently selects from a resource pool configured or pre-configured by the network device (for example, it can be an autonomous selection method). Among them, the network scheduling method is that the network device dynamically allocates transmission resources on the SL to the terminal based on the cached data reported by the terminal, while the autonomous selection method is that the terminal randomly selects transmission resources from a resource pool configured or pre-configured by the network device. Optionally, the network device can configure multiple resource pools for the terminal on one BWP. Optionally, the specific resource allocation method used by the terminal can be configured by the network device through radio resource control (RRC) signaling.

[0155] In some embodiments, pre-configuration may be understood as definition, pre-definition, storage, pre-storage, pre-negotiation, curing, or pre-burning, etc.

[0156] Optionally, uplink and downlink operations can be performed in unlicensed bands, where both downlink and uplink channel access rely on the LBT feature. The wireless device or base station first "senses" the communication channel to detect the absence of communication before any transmission. When the communication channel is an unlicensed wideband carrier (e.g., several hundred megahertz), the LBT process relies on detecting energy levels across multiple sub-bands of the communication channel. Optionally, LBT parameters (such as type / duration, clear channel assessment parameters, etc.) can be configured on the wireless device by the base station.

[0157] In some embodiments, terms such as "uplink", "uplink", "physical uplink", etc. can be used interchangeably, and terms such as "downlink", "downlink", "physical downlink", etc. can be used interchangeably.

[0158] Optionally, the terminal can count the number of uplink LBT failures on each BWP. Optionally, the network device configures the maximum number of consecutive LBT failures (lbt-FailureInstanceMaxCount) and the consecutive LBT failure detection timer (lbt-FailureDetectionTimer) for the terminal in each serving cell (perservingcell) through RRC signaling (for example, lbt-FailureRecoveryConfig) for counting consecutive LBT failures. Among them, the UE maintains an LBT_counter variable for each cell, and the initial value of the variable is 0. For each cell that is activated and configured with lbt-FailureRecoveryConfig, when the terminal receives the LBT failure indication submitted by the physical layer, it starts or restarts the lbt-FailureDetectionTimer, and the LBT_counter is increased by 1. When the LBT_counter is greater than or equal to the lbt-FailureInstanceMaxCount, the activated BWP on the cell triggers a continuous LBT failure. When the lbt-FailureDetectionTimer times out or the higher layer reconfigures the lbt-FailureInstanceMaxCount / lbt-FailureDetectionTimer or all consecutive LBT failures on this serving cell are canceled, the UE resets the LBT_counter to 0. When the terminal detects consecutive LBT failures on the activated BWP of the PCell (primary cell) or PSCell (secondary cell), if there are other BWPs configured with physical random access channel (PRACH) resources on the cell, the terminal triggers BWP switch, switches to the BWP configured with PRACH resources and initiates the random access channel (RACH) process.

[0159] Optionally, if the terminal detects continuous LBT failures in N BWPs configured with PRACH resources in the primary cell, the terminal initiates a radio link failure (RLF) recovery process. Optionally, if continuous LBT failures are detected on the activated BWP of the SCell, the terminal indicates the cell identifier of the continuous LBT failure to the network device through the media access control control element (MAC CE). The MAC CE can carry multiple cell identifiers of the cells where continuous LBT failures are detected. The MAC CE is sent through other service cells where no continuous LBT failures have occurred. Optionally, if the MAC PDU containing the continuous LBT failure MAC CE is sent successfully, the terminal will cancel the continuous LBT failure status of the cell where the continuous LBT failure has occurred, as indicated by the continuous LBT failure MAC CE. Optionally, if continuous LBT failure is triggered on the PCell or PSCell, and the RACH process is successfully completed, the terminal cancels the continuous LBT failure status of the PCell or PSCell. Optionally, if the terminal receives a physical downlink control channel (PDCCH) indicating BWP switching of a certain serving cell, the continuous LBT failure state of the cell is cancelled.

[0160] SL communication can use unlicensed spectrum, and terminals sending SL data on unlicensed spectrum also need to perform LBT. The continuous LBT failure mechanism also applies to SL communication in unlicensed spectrum. In some embodiments, the terms "side," "sidelink," "side communication," "sidelink communication," "direct connection," "direct link," "direct communication," and "direct link communication" are interchangeable.

[0161] Optionally, the granularity of SL consecutive LBT failures can be resource block set granularity. This means that the terminal counts whether the number of LBT failure indications for a resource block set reaches a preset number within a period of time to determine whether SL consecutive LBT failures have been triggered for this resource block set. However, the detailed method for canceling SL consecutive LBT failures triggered by a resource block set is not yet clear.

[0162] Based on this, the present disclosure proposes a method for canceling SL continuous LBT failure.

[0163] Optionally, in some embodiments, the method of the present disclosure may be applied to an unlicensed sidelink (SL-U) scenario. For example, in some embodiments, the method of the present disclosure may be applied to an Internet of Vehicles (IoV) scenario.

[0164] FIG2 is an interactive diagram illustrating a method for canceling SL continuous LBT failure according to an embodiment of the present disclosure. As shown in FIG2 , an embodiment of the present disclosure relates to a method for canceling SL continuous LBT failure, which is used in a communication system 100. The method includes:

[0165] Step S2101: The network device sends a control instruction to the terminal.

[0166] In some embodiments, terminal 101 may receive control instructions.

[0167] In some embodiments, the control instruction may be an instruction for configuring or reconfiguring the resource allocation method of the terminal. The control instruction may include the resource allocation method configured or reconfigured by the network device for the terminal. Alternatively, the control instruction may be a resource allocation method configuration instruction, a resource allocation method reconfiguration instruction, etc., and the name of the control instruction is not limited. Exemplarily, terminal 101 is a terminal in an RRC connected state.

[0168] In some embodiments, the control instruction may be an instruction for reconfiguring a resource pool, that is, the control instruction is used to instruct the reconfiguration of a resource pool. Optionally, the control instruction may be used to reconfigure a single resource pool or multiple resource pools. Exemplarily, the control instruction may be a resource pool reconfiguration signaling, a resource reconfiguration signaling, or the like, and the name of the control instruction is not limited. Exemplarily, terminal 101 is a terminal in an RRC connected state.

[0169] In some embodiments, the control instruction may be an instruction for instructing the network device to switch the resource pool scheduled for the terminal from the current resource pool to another resource pool. Optionally, the name of the control instruction is not limited, and may be, for example, a resource pool switching instruction. Exemplarily, the resource allocation mode of terminal 101 is a network scheduling mode.

[0170] In some embodiments, the control instruction may be at least one of an instruction for configuring or reconfiguring the resource allocation method of the terminal, an instruction for reconfiguring the resource pool, and an instruction for instructing the network device to switch the resource pool scheduled to the terminal from the current resource pool to another resource pool.

[0171] In some embodiments, the control instruction may be RRC signaling, or other signaling such as downlink control information (DCI) signaling, physical downlink control channel (PDCCH) signaling, etc.

[0172] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0173] In some embodiments, if the optional embodiments of subsequent steps do not involve the above-mentioned control instructions, step S2101 can be omitted.

[0174] Step S2102: The terminal fails to cancel SL continuous LBT.

[0175] In some embodiments, the terminal may cancel the SL consecutive LBT failure triggered by the resource block set.

[0176] In some embodiments, the resource block set may be a resource block set that triggers SL consecutive LBT failure.

[0177] In some embodiments, the resource block set may be a resource block set that triggers the SL continuous LBT failure and does not cancel the SL continuous LBT failure.

[0178] In some embodiments, the terminal may cancel the SL continuous LBT failure triggered by the resource block set when the SL continuous LBT failure cancellation condition is met.

[0179] In some embodiments, the conditions for canceling SL continuous LBT failure are met, including at least one of the following: the resource allocation method of the terminal is switched; the resource pool to which the resource block set belongs is reconfigured; the resource pool scheduled by the network device to the terminal is switched from the resource pool to which the resource block set belongs to other resource pools; the resource pool selected by the terminal is switched from the resource pool to which the resource block set belongs to other resource pools; the MAC entity is reset; the SL function of the MAC entity is reset for any unicast connection.

[0180] In some embodiments, the resource allocation mode of the terminal switches, for example, the resource allocation mode of the terminal switches from a network scheduling mode to an autonomous selection mode, or vice versa. The name of the network scheduling mode is not limited, and may be, for example, a network dynamic scheduling mode, mode 1, or mode 1. The name of the autonomous selection mode is not limited, and may be, for example, mode 2 or mode 2.

[0181] In some embodiments, the resource allocation method of the terminal is an autonomous selection method. In some embodiments, the resource pool selected by the terminal changes, and the resource pool selected by the terminal is changed from the current resource pool to other resources. If there is a resource block set in the current resource pool that triggers SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by the resource block set is canceled. In some embodiments, the resource block set that triggers SL continuous LBT failure in the current resource pool can be one or more. Exemplarily, if there are multiple resource block sets in the current resource pool that trigger SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by each resource block set in the multiple resource block sets can be canceled.

[0182] In some embodiments, MAC entity reset can be understood as resetting all functions of the MAC entity. Exemplarily, the terminal high-level request MAC entity reset, the terminal cancels all SL continuous LBT failures triggered by resource block sets. Exemplarily, the terminal high-level request MAC entity reset, the MAC entity cancels all SL continuous LBT failures triggered by resource block sets, for example, the MAC entity can be an entity inside the terminal. In some embodiments, terminal 101 can be a terminal whose resource allocation method is a network scheduling method or an autonomous selection method. In some embodiments, terminal 101 can be a terminal in an RRC connected state, an idle state, or a dormant state. In some embodiments, terminal 101 is a terminal out of range (OOC).

[0183] In some embodiments, the SL function reset of the MAC entity for any unicast connection can be understood as resetting part of the functions of the MAC entity, which are functions for any unicast connection and related to the SL.

[0184] In some embodiments, the SL function reset of the MAC entity for any unicast connection can be understood as the SL MAC reset for any unicast connection.

[0185] In some embodiments, the MAC entity resets the SL function for any unicast connection and cancels any SL continuous LBT failure triggered by the resource block set associated with the unicast connection. Optionally, terminal 101 can be a terminal that uses a network scheduling method or an autonomous selection method for resource allocation. Optionally, terminal 101 can be a terminal in an RRC connected state, an idle state, or a dormant state. Optionally, terminal 101 is a terminal in an OOC state.

[0186] In some embodiments, the unicast connection may be a PC5-RRC connection. Exemplarily, the MAC layer receives an SL MAC reset request from a higher layer for a PC5-RRC connection, and the terminal cancels the SL continuous LBT failure triggered by the resource block set associated with the PC5-RRC connection. Exemplarily, the MAC layer receives an SL MAC reset request from a higher layer for a PC5-RRC connection, and the MAC entity cancels the SL continuous LBT failure triggered by the resource block set associated with the PC5-RRC connection. For example, the MAC entity may be an entity within the terminal.

[0187] In some embodiments, the resource block set associated with any unicast connection may refer to the resource block set used by the unicast connection.

[0188] In some embodiments, the resource block set associated with any unicast connection may be the resource block set used by at least one of the PSSCH, PSCCH, and PSFCH associated with the unicast connection. Optionally, if any resource block set associated with the unicast connection triggers a SL continuous LBT failure, the SL continuous LBT failure triggered by the resource block set is canceled. Optionally, if any resource block set associated with the unicast connection triggers a SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by the resource block set is canceled.

[0189] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "arbitrary", "any", "first", etc. can be interchangeable, and "specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", "any A", "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, any A, any A or first A, etc., but not limited to this.

[0190] In some embodiments, the MAC entity is reset and the SL continuous LBT failure reporting process is canceled. In some embodiments, the terminal 101 may be a terminal whose resource allocation mode is a network scheduling mode, or may be a terminal in an RRC connected state whose resource allocation mode is an autonomous selection mode.

[0191] In some embodiments, the MAC entity is reset and the SL continuous LBT failure reporting process is canceled.

[0192] In some embodiments, canceling the SL continuous LBT failure reporting process can be understood as canceling the SL continuous LBT failure reporting process.

[0193] In some embodiments, the MAC entity reset and the process of canceling the SL continuous LBT failure report may include at least one of the following: if a first report is being generated, canceling the generation of the first report; if the first report has already been generated, canceling the sending or resending of the first report to the network device. The first report may be used to indicate to the network device information about the resource block set that triggered the SL continuous LBT failure.

[0194] In some embodiments, the name of the first report is not limited, such as SL continuous LBT failure report, SL continuous LBT failure MAC CE, etc.

[0195] Exemplarily, the terminal upper layer requests the MAC entity to reset, and the MAC entity cancels the SL continuous LBT failure reporting process. For example, canceling the SL continuous LBT failure reporting process may include at least one of the following: if the SL continuous LBT failure MAC CE is being generated, canceling the generation of the SL continuous LBT failure MAC CE; if the SL continuous LBT failure MAC CE has already been generated, canceling the sending or retransmission of the SL continuous LBT failure MAC CE.

[0196] In some embodiments, the terminal may determine that the SL continuous LBT failure cancellation condition is met based on a control instruction sent by a network device, and cancel the SL continuous LBT failure triggered by the resource block set.

[0197] In some embodiments, the control instruction is used to configure or reconfigure the resource allocation method of the terminal. If the resource allocation method configured or reconfigured by the control instruction to the terminal is inconsistent with the current resource allocation method of the terminal, it can be determined that the resource allocation method of the terminal has switched, and the SL continuous LBT failure triggered by the resource block set can be canceled.

[0198] Exemplarily, the resource allocation mode of the terminal is the network scheduling mode, and the network device can configure or reconfigure the resource allocation mode of the terminal to the autonomous selection mode through control instructions. The terminal determines that the resource allocation mode is switched from the network scheduling mode to the autonomous selection mode according to the control instructions. If a resource block set in the resource pool scheduled by the network device triggers an SL continuous LBT failure, the SL continuous LBT failure triggered by the resource block set is canceled.

[0199] Exemplarily, the terminal determines, based on the control instruction, that the resource allocation mode of the terminal is switched from the network scheduling mode to the autonomous selection mode. If a resource block set in the resource pool scheduled by the network device triggers a SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by the resource block set is canceled.

[0200] Optionally, the resource pool scheduled by the network device may be one or more, and the resource block set that triggers SL continuous LBT failure in one resource pool may be one or more. Exemplarily, if there are multiple resource block sets in the resource pool scheduled by the network device that trigger SL continuous LBT failure, the SL continuous LBT failure triggered by each resource block set in the multiple resource block sets may be canceled. Exemplarily, if there are multiple resource block sets in the resource pool scheduled by the network device that trigger SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by each resource block set in the multiple resource block sets may be canceled.

[0201] In some embodiments, the resource allocation mode of the terminal is switched from the network scheduling mode to the autonomous selection mode, which can be understood as the resource allocation mode of the terminal being configured or reconfigured from the network scheduling mode to the autonomous selection mode.

[0202] Exemplarily, the resource allocation mode of the terminal is an autonomous selection mode, and the network device can configure or reconfigure the resource allocation mode of the terminal to a network scheduling mode through a control instruction. The terminal determines that the resource allocation mode of the terminal is switched from the autonomous selection mode to the network scheduling mode according to the control instruction. If there is a resource block set in the resource pool selected by the terminal that triggers SL continuous LBT failure, the SL continuous LBT failure triggered by the resource block set is canceled.

[0203] For example, the terminal determines that the resource allocation mode of the terminal is switched from the autonomous selection mode to the network scheduling mode according to the control instruction.

[0204] A resource block set in the resource pool selected by the terminal triggers SL continuous LBT failure and the SL continuous LBT failure is not canceled, and the SL continuous LBT failure triggered by the resource block set is canceled.

[0205] Optionally, the resource pool selected by the terminal may be one or more, and the resource block set that triggers the SL continuous LBT failure in the resource pool selected by the terminal may be one or more. Exemplarily, if there are multiple resource block sets in the resource pool selected by the terminal that trigger the SL continuous LBT failure, the SL continuous LBT failure triggered by each resource block set in the multiple resource block sets may be canceled. Exemplarily, if there are multiple resource block sets in the resource pool selected by the terminal that trigger the SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by each resource block set in the multiple resource block sets may be canceled.

[0206] In some embodiments, the resource allocation mode of the terminal is switched from the autonomous selection mode to the network scheduling mode, which can be understood as the resource allocation mode of the terminal being configured or reconfigured from the autonomous selection mode to the network scheduling mode.

[0207] In some embodiments, the terminal receives a control instruction for reconfiguring a resource pool. If a resource block set in the reconfigured resource pool triggers a SL continuous LBT failure, the SL continuous LBT failure triggered by the resource block set is canceled.

[0208] In some embodiments, the terminal receives a control instruction for reconfiguring a resource pool. If a resource block set in the reconfigured resource pool triggers a SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by the resource block set is canceled.

[0209] In some embodiments, the resource block set that triggers SL continuous LBT failure in the reconfigured resource pool may be one or more. Exemplarily, if there are multiple resource block sets in the reconfigured resource pool that trigger SL continuous LBT failure, the SL continuous LBT failure triggered by each resource block set in the multiple resource block sets may be canceled. Exemplarily, if there are multiple resource block sets in the reconfigured resource pool that trigger SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by each resource block set in the multiple resource block sets may be canceled.

[0210] In some embodiments, the control instruction is used to instruct the network device to switch the resource pool scheduled for the terminal from the current resource pool to other resource pools. The terminal determines, based on the control instruction, that the resource pool scheduled for the terminal by the network device is switched from the current resource pool to other resource pools. If a resource block set in the current resource pool triggers an SL continuous LBT failure, the SL continuous LBT failure triggered by the resource block set is canceled.

[0211] In some embodiments, the control instruction is used to instruct the network device to switch the resource pool scheduled for the terminal from the current resource pool to other resource pools. The terminal determines that the resource pool scheduled for the terminal by the network device is switched from the current resource pool to other resource pools according to the control instruction. If there is a resource block set in the current resource pool that triggers SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by the resource block set is canceled.

[0212] In some embodiments, the resource block set that triggers SL continuous LBT failure in the current resource pool can be one or more. Exemplarily, if there are multiple resource block sets in the current resource pool that trigger SL continuous LBT failure, the SL continuous LBT failure triggered by each resource block set in the multiple resource block sets can be canceled. Exemplarily, if there are multiple resource block sets in the current resource pool that trigger SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by each resource block set in the multiple resource block sets can be canceled.

[0213] In some embodiments, the method disclosed herein can be applied to SL-U scenarios, and can also be applied to scenarios in other areas such as authorized spectrum where the problem of "how the terminal cancels SL continuous LBT failures triggered by a resource block set" is addressed.

[0214] The embodiments of the present disclosure list a variety of SL continuous LBT failure cancellation conditions, which are respectively configured by the network side, or by the high-level configuration, or by the terminal selection, etc., but are not limited to these. These conditions can also be determined by at least one of the following: specified by the protocol, configured by the network device, determined by the terminal, configured by the high-level configuration, configured by other entities, etc.

[0215] The method for canceling SL continuous LBT failures involved in the embodiments of the present disclosure may include at least one of steps S2101 and S2102. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, and steps S2101+S2102 may be implemented as independent embodiments, but are not limited thereto.

[0216] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0217] FIG3a is a flow chart of a method for canceling SL continuous LBT failure according to an embodiment of the present disclosure. As shown in FIG3a, the embodiment of the present disclosure relates to a method for canceling SL continuous LBT failure, which is used for terminal 101. The method includes:

[0218] Step S3101, receiving a control instruction.

[0219] In some embodiments, terminal 101 may receive control instructions sent by a network device.

[0220] Step S3102, canceling SL continuous LBT failure.

[0221] For a detailed description of steps S3101 - S3102 , please refer to the embodiment shown in FIG2 .

[0222] The method for canceling SL continuous LBT failures according to the embodiments of the present disclosure may include at least one of steps S3101 and S3102. For example, step S3101 may be implemented as an independent embodiment, step S3102 may be implemented as an independent embodiment, and step S3101 + step S3102 may be implemented as independent embodiments, but the present disclosure is not limited thereto.

[0223] FIG3 b is a flow chart of a method for canceling SL continuous LBT failure according to an embodiment of the present disclosure. As shown in FIG3 b , the embodiment of the present disclosure relates to a method for canceling SL continuous LBT failure, which is used for terminal 101. The method includes:

[0224] Step S3201, receiving a control instruction.

[0225] In some embodiments, the terminal may receive a control instruction sent by a network device.

[0226] In some embodiments, the control instruction may be an instruction for configuring or reconfiguring a resource allocation manner of the terminal.

[0227] In some embodiments, the name of the control instruction is not limited, and may be, for example, a resource allocation mode configuration instruction, a resource allocation mode reconfiguration instruction, etc.

[0228] Step S3202: According to the control instruction, it is determined that the resource allocation mode of the terminal is switched, and the SL continuous LBT failure triggered by the resource block set is canceled.

[0229] In some embodiments, the terminal may determine that the resource allocation mode of the terminal is switched according to a control instruction, and if a resource block set triggers SL continuous LBT failure, cancel the SL continuous LBT failure triggered by the resource block set.

[0230] In some embodiments, the resource block set that triggers the SL continuous LBT failure may be one or more resource block sets. For example, if multiple resource block sets trigger the SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by each resource block set in the multiple resource block sets may be canceled.

[0231] For a detailed description of steps S3201 - S3202 , please refer to the embodiment shown in FIG2 .

[0232] The method for canceling SL continuous LBT failures involved in the embodiments of the present disclosure may include at least one of steps S3201 and S3202. For example, step S3201 may be implemented as an independent embodiment, step S3202 may be implemented as an independent embodiment, and step S3201 + step S3202 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0233] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0234] FIG3c is a flow chart of a method for canceling SL continuous LBT failure according to an embodiment of the present disclosure. As shown in FIG3c, the embodiment of the present disclosure relates to a method for canceling SL continuous LBT failure, which is used for terminal 101. The method includes:

[0235] Step S3301, receiving a control instruction.

[0236] In some embodiments, the terminal may receive a control instruction sent by a network device.

[0237] In some embodiments, control instructions may be used to reconfigure resource pools.

[0238] In some embodiments, the name of the control instruction is not limited, for example, it can be a resource pool reconfiguration signaling or a resource reconfiguration signaling.

[0239] Step S3302: If a resource block set in the resource pool reconfigured by the control instruction triggers a SL continuous LBT failure and is not cancelled, the SL continuous LBT failure triggered by the resource block set is cancelled.

[0240] In some embodiments, the terminal receives a control instruction for reconfiguring a resource pool. If a resource block set in the reconfigured resource pool triggers a SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by the resource block set is canceled.

[0241] In some embodiments, the resource block set that triggers SL continuous LBT failure in the reconfigured resource pool may be one or more resource block sets. For example, if multiple resource block sets in the reconfigured resource pool trigger SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by each resource block set in the multiple resource block sets may be canceled.

[0242] For a detailed description of steps S3301 - S3302 , please refer to the embodiment shown in FIG2 .

[0243] The method for canceling SL continuous LBT failures involved in the embodiments of the present disclosure may include at least one of steps S3301 and S3302. For example, step S3301 may be implemented as an independent embodiment, step S3302 may be implemented as an independent embodiment, and steps S3201 and S3302 may be implemented as independent embodiments, but are not limited thereto.

[0244] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0245] FIG3 d is a flow chart of a method for canceling SL continuous LBT failure according to an embodiment of the present disclosure. As shown in FIG3 d , the embodiment of the present disclosure relates to a method for canceling SL continuous LBT failure, which is used in terminal 101 and includes:

[0246] Step S3401, receiving a control instruction.

[0247] Optionally, the terminal 101 may receive a receiving control instruction sent by a network device.

[0248] Step S3402: According to the control instruction, it is determined that the resource pool scheduled by the network device for the terminal is switched from the current resource pool to another resource pool.

[0249] Step S3403: A resource block set in the current resource pool has triggered a SL continuous LBT failure and has not been cancelled, and the SL continuous LBT failure triggered by the resource block set is cancelled.

[0250] In some embodiments, the resource block set that triggers the SL continuous LBT failure in the current resource pool may be one or more. For example, if there are multiple resource block sets in the current resource pool that trigger the SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by each resource block set in the multiple resource block sets may be canceled.

[0251] For a detailed description of steps S3401-S3403, please refer to the embodiment of FIG2 above.

[0252] The method for canceling SL continuous LBT failures involved in the embodiments of the present disclosure may include at least one of steps S3401 to S3403. For example, step S3401 can be implemented as an independent embodiment, step S3402 can be implemented as an independent embodiment, step S3403 can be implemented as an independent embodiment, step S3401 + step S3402 can be implemented as an independent embodiment, and step S3401 + step S3402 + step S3403 can be implemented as independent embodiments, but are not limited thereto.

[0253] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0254] FIG3e is a flow chart of a method for canceling SL continuous LBT failure according to an embodiment of the present disclosure. As shown in FIG3e , the embodiment of the present disclosure relates to a method for canceling SL continuous LBT failure, which is used for terminal 101. The method includes:

[0255] Step S3501, receiving a control instruction.

[0256] Optionally, the terminal may receive a receiving control instruction sent by the network device.

[0257] Step S3502: According to the control instruction, it is determined that the SL continuous LBT failure cancellation condition is met, and the SL continuous LBT failure triggered by the resource block set is cancelled.

[0258] In some embodiments, the resource block set that triggers the SL continuous LBT failure may be one or more resource block sets. For example, if multiple resource block sets trigger the SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by each resource block set in the multiple resource block sets may be canceled.

[0259] For a detailed description of steps S3501 - S3502 , please refer to the embodiment shown in FIG2 .

[0260] The method for canceling SL continuous LBT failures according to the embodiments of the present disclosure may include at least one of steps S3501 and S3502. For example, step S3501 may be implemented as an independent embodiment, step S3502 may be implemented as an independent embodiment, and step S3501 + step S3502 may be implemented as independent embodiments, but the present disclosure is not limited thereto.

[0261] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0262] FIG3f is a flow chart of a method for canceling SL continuous LBT failure according to an embodiment of the present disclosure. As shown in FIG3f , the embodiment of the present disclosure relates to a method for canceling SL continuous LBT failure, which is used in terminal 101. The method includes:

[0263] Step S3601: The resource pool selected by the terminal is changed from the current resource pool to another resource pool.

[0264] In some embodiments, the resource allocation mode of the terminal is an autonomous selection mode.

[0265] In some embodiments, the resource pool selected by the terminal changes, and the resource pool selected by the terminal is changed from the current resource pool to another resource pool.

[0266] Step S3602: A resource block set in the current resource pool has triggered a SL continuous LBT failure and has not been cancelled, and the SL continuous LBT failure triggered by the resource block set is cancelled.

[0267] In some embodiments, if a resource block set in the current resource pool triggers a SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by the resource block set is canceled.

[0268] In some embodiments, the resource block set that triggers the SL continuous LBT failure in the current resource pool may be one or more. For example, if there are multiple resource block sets in the current resource pool that trigger the SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by each resource block set in the multiple resource block sets may be canceled.

[0269] For a detailed description of steps S3601-S3602, please refer to the embodiment of FIG2 above.

[0270] The method for canceling SL continuous LBT failures according to the embodiments of the present disclosure may include at least one of steps S3601 and S3602. For example, step S3601 may be implemented as an independent embodiment, step S3602 may be implemented as an independent embodiment, and step S3601 + step S3602 may be implemented as independent embodiments, but the present disclosure is not limited thereto.

[0271] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0272] FIG3g is a flow chart of a method for canceling SL continuous LBT failure according to an embodiment of the present disclosure. As shown in FIG3g, the embodiment of the present disclosure relates to a method for canceling SL continuous LBT failure, which is used for terminal 101. The method includes:

[0273] Step S3701: The MAC entity is reset to cancel the SL continuous LBT failure triggered by the resource block set.

[0274] In some embodiments, resetting the MAC entity may be understood as resetting all functions of the MAC entity.

[0275] In some embodiments, if the MAC entity is reset, the SL continuous LBT failure triggered by the resource block set can be canceled. Optionally, the resource block set is a resource block set in the configured resource pool that has triggered the SL continuous LBT failure and has not canceled the SL continuous LBT failure.

[0276] Exemplarily, the terminal higher layer requests the MAC entity to reset, and the terminal cancels the SL continuous LBT failure triggered by all resource block sets.

[0277] Exemplarily, the terminal upper layer requests a MAC entity reset, and the MAC entity cancels all SL continuous LBT failures triggered by all resource block sets, for example, the MAC entity may be an entity within the terminal. Optionally, the resource block set is a resource block set that triggered the SL continuous LBT failure and did not cancel the SL continuous LBT failure.

[0278] In some embodiments, the terminal 101 may be a terminal that allocates resources in a network scheduling manner or an autonomous selection manner.

[0279] In some embodiments, the terminal 101 may be a terminal in an RRC connected state, an idle state, or a dormant state.

[0280] In some embodiments, terminal 101 is an out of range (OOC) terminal.

[0281] For a detailed description of step S3701, please refer to the embodiment shown in FIG2 .

[0282] In this embodiment or example, the optional modes or optional examples may be arbitrarily combined unless there is any contradiction.

[0283] FIG3h is a flow chart of a method for canceling SL continuous LBT failure according to an embodiment of the present disclosure. As shown in FIG3h , the embodiment of the present disclosure relates to a method for canceling SL continuous LBT failure, which is used for terminal 101. The method includes:

[0284] Step S3801: The MAC entity resets the SL function for any unicast connection and cancels the SL continuous LBT failure triggered by the resource block set associated with any unicast connection.

[0285] In some embodiments, the SL function reset of the MAC entity for any unicast connection can be understood as resetting part of the functions of the MAC entity, which are functions for any unicast connection and related to the SL.

[0286] In some embodiments, the SL function reset of the MAC entity for any unicast connection can be understood as the SL MAC reset for any unicast connection.

[0287] In some embodiments, the unicast connection may be a PC5-RRC connection. Exemplarily, the MAC layer receives an SL MAC reset request from a higher layer for a PC5-RRC connection, and the terminal cancels the SL continuous LBT failure triggered by the resource block set associated with the PC5-RRC connection. Exemplarily, the MAC layer receives an SL MAC reset request from a higher layer for a PC5-RRC connection, and the MAC entity cancels the SL continuous LBT failure triggered by the resource block set associated with the PC5-RRC connection. For example, the MAC entity may be an entity within the terminal.

[0288] In some embodiments, the resource block set associated with any unicast connection may refer to the resource block set used by the unicast connection.

[0289] In some embodiments, the resource block set associated with any unicast connection may be a resource block set used by at least one of the PSSCH, PSCCH, and PSFCH associated with the unicast connection. Optionally, if a resource block set associated with any unicast connection triggers a SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure triggered by the resource block set is canceled.

[0290] In some embodiments, the terminal 101 may be a terminal that allocates resources in a network scheduling manner or an autonomous selection manner.

[0291] In some embodiments, the terminal 101 may be a terminal in an RRC connected state, an idle state, or a dormant state.

[0292] In some embodiments, terminal 101 is an OOC terminal.

[0293] For a detailed description of step S3801, please refer to the embodiment shown in FIG2 .

[0294] In this embodiment or example, the optional modes or optional examples may be arbitrarily combined unless there is any contradiction.

[0295] FIG3i is a flow chart of a method for canceling SL continuous LBT failure according to an embodiment of the present disclosure. As shown in FIG3i , the embodiment of the present disclosure relates to a method for canceling SL continuous LBT failure, which is used in terminal 101 and includes:

[0296] Step S3901, the MAC entity is reset and the SL continuous LBT failure reporting process is canceled.

[0297] In some embodiments, canceling the SL continuous LBT failure reporting process can be understood as canceling the SL continuous LBT failure reporting process.

[0298] Exemplarily, the process of canceling a SL continuous LBT failure report may include at least one of the following: if a first report is being generated, canceling the generation of the first report; if the first report has already been generated, canceling the sending or retransmission of the first report to the network device. The first report may be used to indicate to the network device information about the set of resource blocks that triggered the SL continuous LBT failure. Optionally, the first report may be a SL continuous LBT failure MAC CE.

[0299] In some embodiments, the name of the first report is not limited, such as SL continuous LBT failure report, SLth continuous LBT failure MAC CE, etc.

[0300] Exemplarily, the terminal upper layer requests the MAC entity to reset, and the MAC entity cancels the SL continuous LBT failure reporting process. For example, canceling the SL continuous LBT failure reporting process may include at least one of the following: if the SL continuous LBT failure MAC CE is being generated, canceling the generation of the SL continuous LBT failure MAC CE; if the SL continuous LBT failure MAC CE has already been generated, canceling the sending or retransmission of the SL continuous LBT failure MAC CE.

[0301] In some embodiments, the terminal 101 may be a terminal whose resource allocation mode is a network scheduling mode, or may be a terminal in an RRC connection state and whose resource allocation mode is an autonomous selection mode.

[0302] For a detailed description of step S3901, please refer to the embodiment shown in FIG2 .

[0303] In this embodiment or example, the optional modes or optional examples may be arbitrarily combined unless there is any contradiction.

[0304] FIG3j is a flow chart of a method for canceling SL continuous LBT failure according to an embodiment of the present disclosure. As shown in FIG3j , the embodiment of the present disclosure relates to a method for canceling SL continuous LBT failure, which is used for terminal 101. The method includes:

[0305] Step S31001: If the SL continuous LBT failure cancellation condition is met, the SL continuous LBT failure triggered by the resource block set is canceled.

[0306] In some embodiments, the SL continuous LBT failure cancellation condition includes at least one of the following:

[0307] The resource allocation mode of the terminal is switched;

[0308] The resource pool to which the resource block set belongs is reconfigured;

[0309] The resource pool that the network device schedules for the terminal is switched from the resource pool to which the resource block set belongs to another resource pool.

[0310] The resource pool selected by the terminal is switched from the resource pool to which the resource block set belongs to another resource pool;

[0311] MAC entity reset;

[0312] The SL functionality of the MAC entity is reset for any unicast connection.

[0313] In some embodiments, the satisfying of the SL continuous LBT failure cancellation condition and canceling the SL continuous LBT failure triggered by the resource block set includes:

[0314] Receive control instructions sent by network devices;

[0315] According to the control instruction, it is determined that the SL continuous LBT failure cancellation condition is met, and the SL continuous LBT failure triggered by the resource block set is canceled.

[0316] In some embodiments, determining, according to the control instruction, that the SL continuous LBT failure cancellation condition is satisfied, and canceling the SL continuous LBT failure triggered by the resource block set, includes:

[0317] According to the control instruction, it is determined that the resource allocation mode of the terminal is switched, and the SL continuous LBT failure triggered by the resource block set is canceled. The control instruction is used to configure or reconfigure the resource allocation mode of the terminal.

[0318] In some embodiments, determining, according to the control instruction, that a resource allocation mode of the terminal is switched, and canceling the SL continuous LBT failure triggered by the resource block set includes:

[0319] According to the control instruction, determining that the resource allocation mode of the terminal is switched from a network scheduling mode to an autonomous selection mode;

[0320] A resource block set in a resource pool scheduled by the network device triggers a SL continuous LBT failure and is not cancelled, and the SL continuous LBT failure triggered by the resource block set is cancelled.

[0321] In some embodiments, determining, according to the control instruction, that a resource allocation mode of the terminal is switched, and canceling the SL continuous LBT failure triggered by the resource block set includes:

[0322] According to the control instruction, determining that the resource allocation mode of the terminal is switched from an autonomous selection mode to a network scheduling mode;

[0323] A resource block set in the resource pool selected by the terminal triggers a SL continuous LBT failure and is not cancelled, and the SL continuous LBT failure triggered by the resource block set is cancelled.

[0324] In some embodiments, determining, according to the control instruction, that the SL continuous LBT failure cancellation condition is satisfied and canceling the SL continuous LBT failure triggered by the resource block set includes:

[0325] The control instruction is used to reconfigure a resource pool, where a resource block set in the reconfigured resource pool triggers a SL continuous LBT failure and is not cancelled, and cancels the SL continuous LBT failure triggered by the resource block set.

[0326] In some embodiments, determining, according to the control instruction, that the SL continuous LBT failure cancellation condition is satisfied and canceling the SL continuous LBT failure triggered by the resource block set includes:

[0327] The control instruction is used to instruct the network device to switch the resource pool scheduled for the terminal from the current resource pool to other resource pools. A resource block set in the current resource pool has triggered an SL continuous LBT failure and has not been canceled, and the SL continuous LBT failure triggered by the resource block set is canceled.

[0328] In some embodiments, the satisfying of the SL continuous LBT failure cancellation condition and canceling the SL continuous LBT failure triggered by the resource block set includes:

[0329] The resource pool selected by the terminal is changed from the current resource pool to another resource pool;

[0330] A resource block set in the current resource pool triggers a SL continuous LBT failure and is not canceled, and the SL continuous LBT failure triggered by the resource block set is canceled.

[0331] In some embodiments, satisfying the SL continuous LBT failure cancellation condition and canceling the SL continuous LBT failure triggered by the resource block set includes: resetting the MAC entity and canceling the SL continuous LBT failure triggered by the resource block set.

[0332] In some embodiments, the resource block set is a resource block set in a configured resource pool that has triggered SL continuous LBT failure and has not been canceled.

[0333] In some embodiments, the SL continuous LBT failure cancellation condition is met, and the SL continuous LBT failure triggered by the resource block set is canceled, including: the MAC entity resets the SL function for any unicast connection, and cancels the SL continuous LBT failure triggered by the resource block set associated with any unicast connection.

[0334] In some embodiments, the resource block set associated with any unicast connection is a resource block set used by at least one of the physical sidelink shared channel PSSCH, the physical sidelink control channel PSCCH, and the physical sidelink feedback PSFCH associated with any unicast connection.

[0335] In some embodiments, the method may further include: resetting the MAC entity and canceling the SL continuous LBT failure reporting process.

[0336] In some embodiments, the process of canceling the SL continuous LBT failure report includes at least one of the following:

[0337] A first report is being generated, and generating the first report is canceled, where the first report is used to indicate to the network device information about the set of resource blocks that trigger SL continuous LBT failure;

[0338] The first report has been generated, and sending or resending the first report to the network device is canceled.

[0339] In some embodiments, optional implementation methods of step S31001 may include any one or several of the methods in the above-mentioned embodiments of FIG. 3 a - FIG. 3 i .

[0340] For a detailed description of step S31001, please refer to the above-mentioned embodiments of Figures 2 and 3a to 3i.

[0341] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0342] FIG4 is a flow chart of a method for canceling SL continuous LBT failure according to an embodiment of the present disclosure. As shown in FIG4 , the embodiment of the present disclosure relates to a method for canceling SL continuous LBT failure, which is used for a network device 102, and the method includes:

[0343] Step S4101, sending a control instruction.

[0344] In some embodiments, the network device may send a control instruction to the terminal.

[0345] In some embodiments, the control instruction is used by the terminal to determine that the SL continuous LBT failure cancellation condition is met and cancel the SL continuous LBT failure triggered by the resource block set.

[0346] In some embodiments, the SL continuous LBT failure cancellation condition is satisfied, including at least one of the following:

[0347] The resource allocation mode of the terminal is switched;

[0348] reconfiguring the resource pool to which the resource block set belongs;

[0349] The resource pool scheduled by the network device for the terminal is switched from the resource pool to which the resource block set belongs to another resource pool.

[0350] For a detailed description of step S4101, please refer to the embodiment shown in FIG2 .

[0351] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0352] In this implementation manner or example, optional modes or optional examples can be combined arbitrarily.

[0353] FIG5a is a flow chart illustrating a method for canceling consecutive SL LBT failures according to an embodiment of the present disclosure. As shown in FIG5a , the present disclosure relates to a method for canceling consecutive SL LBT failures, which is used in a communication system 100, wherein the communication system 100 includes a terminal 101 and a network device 102. The method includes:

[0354] Step S5101: The terminal meets the SL continuous LBT failure cancellation condition and cancels the SL continuous LBT failure triggered by the resource block set.

[0355] Optional implementations of step S5101 may refer to the above step S2102, any one or more steps in the embodiment of FIG4, and other related parts of the embodiments involved in FIG2 and FIG4.

[0356] FIG5 b is a flow chart of a method for canceling consecutive SL LBT failures according to an embodiment of the present disclosure. As shown in FIG5 , the embodiment of the present disclosure relates to a method for canceling consecutive SL LBT failures, which is used in a communication system 100, wherein the communication system 100 includes a terminal 101 and a network device 102. The method includes:

[0357] Step S5201: The network device sends a control instruction to the terminal.

[0358] In step S5202, the terminal determines that the SL continuous LBT failure cancellation condition is met according to the control instruction, and cancels the SL continuous LBT failure triggered by the resource block set.

[0359] Optional implementations of step S5201 may refer to the above step S2101, any one or more steps in the embodiment of FIG4 , and other related parts of the embodiments involved in FIG2 and FIG4 , which will not be described in detail here.

[0360] Optional implementations of step S5202 may refer to the aforementioned step S2102, any one or more of the embodiments in FIG3a - FIG3d, and other related parts of the embodiments involved in FIG2 and FIG3a - FIG3d, which will not be described in detail here.

[0361] In some embodiments, the above method may include the method described in the above embodiments of the communication system side, terminal side, network device side, etc., which will not be repeated here.

[0362] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0363] The following is an exemplary introduction to the above method.

[0364] Optional embodiment: The terminal is configured or reconfigured from mode 1 to mode 2, and the SL continuous LBT failure of the resource block set (RB set) is canceled.

[0365] Exemplarily, when a terminal is configured or reconfigured from mode 1 to mode 2, the SL continuous LBT failure of a resource block set (RB set) is canceled. The resource block set (RB set) is a resource block set (RB set) in a resource pool scheduled by the network in mode 1 of the terminal. Specifically, if a resource block set (RB set) in a resource pool scheduled by the network in mode 1 of the terminal triggers a SL continuous LBT failure and is not canceled, the terminal is configured or reconfigured from mode 1 to mode 2, and the terminal cancels the SL continuous LBT failure of these resource block sets (RB sets).

[0366] Optional embodiment: The terminal is configured or reconfigured from mode 2 to mode 1, and the SL continuous LBT failure of the resource block set (RB set) is canceled.

[0367] Exemplarily, when a terminal is configured or reconfigured from mode 2 to mode 1, SL continuous LBT failures for a resource block set (RB set) are canceled. The resource block set (RB set) is a resource block set (RB set) in a resource pool selected by the terminal in mode 2. Specifically, if any resource block set (RB set) in the resource pool selected by the terminal in mode 2 triggers SL continuous LBT failures and is not canceled, the terminal is configured or reconfigured from mode 2 to mode 1, and the terminal cancels SL continuous LBT failures for these resource block sets (RB sets).

[0368] Optional embodiment: The resource pool is reconfigured to cancel the SL continuous LBT failure of the resource block set (RB set) in the resource pool.

[0369] Exemplarily, the terminal receives resource pool / resource reconfiguration signaling. If there are resource block sets (RB sets) on this resource pool that trigger SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure of these resource block sets (RB sets) is canceled.

[0370] Exemplarily, it is applicable to a terminal in an RRC connected state.

[0371] Optional embodiment: resource pool switching, canceling SL continuous LBT failure of resource block set (RB set) on the resource pool.

[0372] Exemplarily, the terminal receives a resource pool switching instruction, such as receiving a control signaling to schedule other resource pools. If there is a resource block set (RB set) on this resource pool that triggers SL continuous LBT failure and the SL continuous LBT failure is not canceled, the SL continuous LBT failure of these resource block sets (RB sets) is canceled.

[0373] Exemplarily, it is applicable to a terminal in mode 1.

[0374] Optional embodiment: MAC reset, cancel SL continuous LBT failure reporting process.

[0375] Exemplarily, if the upper layer requests a MAC entity reset, the MAC entity cancels the SL continuous LBT failure reporting process. Specifically, if a SL continuous LBT failure MAC CE is being generated, the generating SL continuous LBT failure MAC CE is canceled; if the SL continuous LBT failure MAC CE has already been generated, the sending of the SL continuous LBT failure MAC CE is canceled. The SL continuous LBT failure MAC CE is used to indicate the resource block set (RB set) where the network device has experienced SL continuous LBT failure.

[0376] Exemplarily, it is applicable to a terminal in mode 1 and a terminal in mode 2 in an RRC connected state.

[0377] Optional embodiment: MAC reset, canceling SL continuous LBT failure of all resource block sets (RB sets).

[0378] Exemplarily, the higher layer requests the MAC entity to reset, and the MAC entity cancels the SL continuous LBT failure of all resource block sets (RB sets) that have triggered the SL continuous LBT failure and have not canceled the SL continuous LBT failure.

[0379] Exemplarily, it is applicable to terminals in mode 1 or mode 2, terminals in RRC connected / idle / inactive states, or terminals in OOC.

[0380] Optional embodiment: SL MAC is reset to cancel the SL continuous LBT failure of the resource block set (RB set) associated with this unicast connection.

[0381] Exemplarily, the MAC layer receives a SL MAC reset request from a higher layer for a PC5-RRC connection, and the terminal cancels the SL continuous LBT failure of the resource block set (RB set) associated with the PC5-RRC connection. Exemplarily, the RB set associated with the PC5-RRC connection refers to the resource block set (RB set) used by the PC5-RRC connection, such as the resource block set (RB set) used for PSSCH / PSCCH / PSFCH transmission of the PC5-RRC connection. Optionally, if the resource block set (RB set) associated with the PC5-RRC connection triggers an SL continuous LBT failure and has not been canceled, the SL continuous LBT failure of the resource block set (RB set) is canceled.

[0382] Exemplarily, it is applicable to terminals in mode 1 or mode 2, terminals in RRC CONNECTED / IDLE / INACTIVE state, or terminals in OOC state.

[0383] It should be noted that the above-mentioned mode1 and mode2 may refer to the resource allocation mode of the terminal, mode1 may be understood as the network scheduling mode, and mode2 may be understood as the autonomous selection mode.

[0384] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0385] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0386] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0387] Figure 6a is a structural diagram of the first device for canceling SL continuous LBT failure proposed in an embodiment of the present disclosure. As shown in Figure 6a, the first device for canceling SL continuous LBT failure includes: a processing module, which is used to meet the SL continuous LBT failure cancellation condition and cancel the SL continuous LBT failure triggered by the resource block set. Optionally, the above-mentioned processing module is used to execute the steps related to "meeting the SL continuous LBT failure cancellation condition and canceling the SL continuous LBT failure triggered by the resource block set" executed by the terminal 101 in any of the above methods, which will not be repeated here. Optionally, the first device for canceling SL continuous LBT failure also includes at least one of a sending module and a receiving module, the above-mentioned sending module is used to execute the steps related to sending executed by the terminal 101 in any of the above methods, and the above-mentioned receiving module is used to execute the steps related to receiving executed by the terminal 101 in any of the above methods, which will not be repeated here.

[0388] Figure 6b is a structural diagram of the second device for canceling SL continuous LBT failure proposed in an embodiment of the present disclosure. As shown in Figure 6b, the second device for canceling SL continuous LBT failure includes: a sending module for sending a control instruction to the terminal, and the control instruction is used by the terminal to determine whether the SL continuous LBT failure cancellation condition is met, and cancel the SL continuous LBT failure triggered by the resource block set. Optionally, the above-mentioned sending module is used to execute the steps related to "sending control instructions to the terminal" performed by the network device 102 in any of the above methods, which will not be repeated here. Optionally, the second device for canceling SL continuous LBT failure also includes a receiving module, and the above-mentioned receiving module is used to execute the steps related to reception performed by the network device 102 in any of the above methods, which will not be repeated here.

[0389] Figure 7a is a schematic diagram of the structure of a communication device 7100 proposed in an embodiment of the present disclosure. Communication device 7100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 7100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0390] As shown in Figure 7a, the communication device 7100 includes one or more processors 7101. The processor 7101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, baseband chip, terminal device, terminal device chip, DU or CU, etc.), execute programs, and process program data. The processor 7101 is used to call instructions to enable the communication device 7100 to perform any of the above methods.

[0391] In some embodiments, the communication device 7100 further includes one or more memories 7102 for storing instructions. Optionally, all or part of the memories 7102 may be located outside the communication device 7100.

[0392] In some embodiments, the communication device 7100 further includes one or more transceivers 7103. When the communication device 7100 includes one or more transceivers 7103, the communication steps such as sending and receiving in the above method are performed by the transceiver 7103, and the other steps are performed by the processor 7101.

[0393] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0394] Optionally, the communication device 7100 further includes one or more interface circuits 7104, which are connected to the memory 7102. The interface circuits 7104 may be configured to receive signals from the memory 7102 or other devices, and may be configured to send signals to the memory 7102 or other devices. For example, the interface circuits 7104 may read instructions stored in the memory 7102 and send the instructions to the processor 7101.

[0395] The communication device 7100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 7100 described in the present disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7a. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0396] FIG7 b is a schematic diagram of the structure of a chip 7200 according to an embodiment of the present disclosure. If the communication device 7100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 7200 shown in FIG7 b , but the present disclosure is not limited thereto.

[0397] The chip 7200 includes one or more processors 7201 , and the processor 7201 is used to call instructions so that the chip 7200 executes any of the above methods.

[0398] In some embodiments, chip 7200 further includes one or more interface circuits 7202, which are connected to memory 7203. Interface circuits 7202 can be used to receive signals from memory 7203 or other devices, or to send signals to memory 7203 or other devices. For example, interface circuit 7202 can read instructions stored in memory 7203 and send these instructions to processor 7201. Alternatively, the terms interface circuit, interface, transceiver pin, and transceiver can be used interchangeably.

[0399] In some embodiments, the chip 7200 further includes one or more memories 7203 for storing instructions. Alternatively, all or part of the memories 7203 may be located outside the chip 7200.

[0400] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 7100, the communication device 7100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

[0401] The present disclosure also provides a program product, which, when executed by the communication device 7100, enables the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0402] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

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

[0404] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians 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.

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

[0406] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A method for canceling the failure of continuous listen-before-talk (LBT) of a side link SL, characterized in that: Executed by a terminal, the method includes: If the SL continuous LBT failure cancellation conditions are met, the SL continuous LBT failure triggered by the resource block set is canceled.

2. The method according to claim 1, characterized in that The SL continuous LBT failure cancellation condition is met, including at least one of the following: The resource allocation mode of the terminal is switched; reconfiguring the resource pool to which the resource block set belongs; The resource pool scheduled by the network device for the terminal is switched from the resource pool to which the resource block set belongs to another resource pool. The resource pool selected by the terminal is switched from the resource pool to which the resource block set belongs to another resource pool; Media Access Control MAC entity reset; The MAC entity resets the SL functionality for any unicast connection.

3. The method according to claim 1 or 2, characterized in that The satisfying the SL continuous LBT failure cancellation condition and canceling the SL continuous LBT failure triggered by the resource block set includes: Receive control instructions sent by network devices; According to the control instruction, it is determined that the SL continuous LBT failure cancellation condition is met, and the SL continuous LBT failure triggered by the resource block set is canceled.

4. The method according to claim 3, characterized in that The determining, according to the control instruction, that the SL continuous LBT failure cancellation condition is satisfied, and canceling the SL continuous LBT failure triggered by the resource block set, comprises: According to the control instruction, it is determined that the resource allocation mode of the terminal is switched, and the SL continuous LBT failure triggered by the resource block set is canceled. The control instruction is used to configure or reconfigure the resource allocation mode of the terminal.

5. The method according to claim 4, characterized in that The determining, according to the control instruction, that the resource allocation mode of the terminal is switched, and canceling the SL continuous LBT failure triggered by the resource block set, includes: According to the control instruction, determining that the resource allocation mode of the terminal is switched from a network scheduling mode to an autonomous selection mode; A resource block set in a resource pool scheduled by the network device triggers a SL continuous LBT failure and is not canceled, and the SL continuous LBT failure triggered by the resource block set is canceled.

6. The method according to claim 4, characterized in that The determining, according to the control instruction, that the resource allocation mode of the terminal is switched, and canceling the SL continuous LBT failure triggered by the resource block set, includes: According to the control instruction, determining that the resource allocation mode of the terminal is switched from an autonomous selection mode to a network scheduling mode; A resource block set in the resource pool selected by the terminal triggers a SL continuous LBT failure and is not cancelled, and the SL continuous LBT failure triggered by the resource block set is cancelled.

7. The method according to any one of claims 3 to 6, characterized in that The determining, according to the control instruction, that the SL continuous LBT failure cancellation condition is satisfied and cancelling the SL continuous LBT failure triggered by the resource block set comprises: The control instruction is used to reconfigure a resource pool, in which a resource block set in the reconfigured resource pool triggers a SL continuous LBT failure and is not cancelled, and the SL continuous LBT failure triggered by the resource block set is cancelled.

8. The method according to any one of claims 3 to 7, characterized in that The determining, according to the control instruction, that the SL continuous LBT failure cancellation condition is satisfied and cancelling the SL continuous LBT failure triggered by the resource block set comprises: The control instruction is used to instruct the network device to switch the resource pool scheduled for the terminal from the current resource pool to other resource pools, and a resource block set in the current resource pool has triggered an SL continuous LBT failure and has not been canceled, and the SL continuous LBT failure triggered by the resource block set is canceled.

9. The method according to any one of claims 1 to 7, characterized in that The satisfying the SL continuous LBT failure cancellation condition and canceling the SL continuous LBT failure triggered by the resource block set includes: The resource pool selected by the terminal is changed from the current resource pool to another resource pool; There is a resource block set in the current resource pool that triggers the SL continuous LBT failure and has not been cancelled, and the SL continuous LBT failure triggered by the resource block set is cancelled.

10. The method according to any one of claims 1 to 9, characterized in that The satisfying the SL continuous LBT failure cancellation condition and canceling the SL continuous LBT failure triggered by the resource block set includes: The MAC entity is reset to cancel the SL continuous LBT failure triggered by the resource block set.

11. The method according to any one of claims 1 to 10, characterized in that The resource block set is a resource block set in the configured resource pool that triggers SL continuous LBT failure and has not been cancelled.

12. The method according to any one of claims 1 to 11, characterized in that The satisfying the SL continuous LBT failure cancellation condition and canceling the SL continuous LBT failure triggered by the resource block set includes: The MAC entity resets the SL function for any unicast connection and cancels the SL continuous LBT failure triggered by the resource block set associated with any unicast connection.

13. The method according to claim 12, characterized in that The resource block set associated with any one of the unicast connections is a resource block set used by at least one of the physical sidelink shared channel PSSCH, the physical sidelink control channel PSCCH, and the physical sidelink feedback PSFCH associated with any one of the unicast connections.

14. The method according to any one of claims 1 to 13, characterized in that Also includes: The MAC entity is reset and the SL continuous LBT failure reporting process is canceled.

15. The method according to claim 14, characterized in that The process of canceling the SL continuous LBT failure report includes at least one of the following: A first report is being generated, and the generation of the first report is canceled, wherein the first report is used to indicate to the network device information about the set of resource blocks that trigger the SL continuous LBT failure; The first report has been generated, and sending or resending the first report to the network device is canceled.

16. A method for cancelling SL continuous LBT failure, characterized in that: Executed by a network device, the method includes: A control instruction is sent to the terminal, wherein the control instruction is used by the terminal to determine that a SL continuous LBT failure cancellation condition is met and cancel the SL continuous LBT failure triggered by the resource block set.

17. The method according to claim 16, characterized in that The SL continuous LBT failure cancellation condition is met, including at least one of the following: The resource allocation mode of the terminal is switched; reconfiguring the resource pool to which the resource block set belongs; The resource pool scheduled by the network device for the terminal is switched from the resource pool to which the resource block set belongs to another resource pool.

18. The method according to claim 16 or 17, characterized in that The control instruction is used to configure the resource allocation mode of the terminal, and the control instruction is used by the terminal to determine that the resource allocation mode of the terminal has been switched and cancel the SL continuous LBT failure triggered by the resource block set. The resource block set triggered the SL continuous LBT failure and was not canceled.

19. The method according to any one of claims 16 to 18, characterized in that The control instruction is used to reconfigure the resource pool, and the control instruction is used by the terminal to cancel the SL continuous LBT failure triggered by the resource block set in the reconfigured resource pool when there is a resource block set in the terminal that triggers the SL continuous LBT failure and has not been cancelled.

20. The method according to any one of claims 16 to 19, characterized in that The control instruction is used to instruct the network device to switch the resource pool scheduled for the terminal from the current resource pool to other resource pools, and the control instruction is used for the terminal to cancel the SL continuous LBT failure triggered by the resource block set in the current resource pool when the SL continuous LBT failure is triggered by the resource block set and has not been canceled.

21. A method for cancelling SL continuous LBT failure, characterized in that: Used in a communication system, the communication system comprising a network device and a terminal, the method comprising: The terminal meets the SL continuous LBT failure cancellation condition and cancels the SL continuous LBT failure triggered by the resource block set.

22. The method according to claim 21, characterized in that The SL continuous LBT failure cancellation condition is met, including at least one of the following: The resource allocation mode of the terminal is switched; reconfiguring the resource pool to which the resource block set belongs; The resource pool scheduled by the network device for the terminal is switched from the resource pool to which the resource block set belongs to another resource pool The resource pool selected by the terminal is switched from the resource pool to which the resource block set belongs to another resource pool; Media Access Control MAC entity reset; The MAC entity resets the SL functionality for any unicast connection.

23. The method according to claim 21 or 22, characterized in that Also includes: The network device sends a control instruction; The terminal determines, according to the control instruction, that the SL continuous LBT failure cancellation condition is satisfied, and cancels the SL continuous LBT failure triggered by the resource block set.

24. The method according to any one of claims 21 to 23, characterized in that The satisfying the SL continuous LBT failure cancellation condition and canceling the SL continuous LBT failure triggered by the resource block set includes: The MAC entity is reset to cancel the SL continuous LBT failure triggered by the resource block set.

25. The method according to any one of claims 21 to 24, characterized in that The satisfying the SL continuous LBT failure cancellation condition and canceling the SL continuous LBT failure triggered by the resource block set includes: The MAC entity resets the SL function for any unicast connection and cancels the SL continuous LBT failure triggered by the resource block set associated with any unicast connection.

26. A device for first cancelling SL continuous LBT failure, characterized in that: The device comprises: The processing module is used to meet the SL continuous LBT failure cancellation condition and cancel the SL continuous LBT failure triggered by the resource block set.

27. A second device for canceling SL continuous LBT failure, characterized in that: The device comprises: The sending module is used to send a control instruction to the terminal, where the control instruction is used by the terminal to determine that the SL continuous LBT failure cancellation condition is met and cancel the SL continuous LBT failure triggered by the resource block set.

28. A communication device, characterized in that: include: One or more processors; The processor is used to call instructions to enable the communication device to execute the SL continuous LBT failure method described in any one of claims 1-15 and 16-20.

29. A communication system, characterized in that: It includes a terminal and a network device, wherein the terminal is configured to implement the SL continuous LBT failure method described in any one of claims 1-15, and the network device is configured to implement the SL continuous LBT failure method described in any one of claims 16-20.

30. A storage medium storing instructions, characterized in that: When the instruction is executed on the communication device, the communication device executes the SL continuous LBT failure method as described in any one of claims 1-15 and 16-20.

Citation Information

Patent Citations

  • failure report reporting method and related equipment

    CN112770350A

  • Communication channel failure detection and recovery

    CN114868449A

  • Sidelink listen before talk detection method, terminal, base station and storage medium

    CN115884240A

  • Method and apparatus for consistent LBT failure detection and recovery

    US20230025873A1

  • Methods, apparatuses, and media for indicating listen before talk failure

    WO2022141218A1