Information processing method and apparatus

Abstract

Disclosed in the embodiments of the present disclosure are an information processing method and apparatus. The method comprises: when a sidelink (SL) continuous listen-before-talk (LBT) failure has been detected by a terminal on a first resource block (RB) set, starting a timer associated with the first RB set, wherein the timer is used for enabling the terminal to determine whether to cancel the SL continuous LBT failure of the first RB set; and during the running of the timer associated with the first RB set, the terminal determining that the timer associated with the first RB set meets a stop condition, and stopping the timer associated with the first RB set. By means of the embodiments of the present disclosure, a timer can be accurately stopped to cancel an SL continuous LBT failure of an RB set as soon as possible, such that resources in the RB set are recovered as soon as possible for receiving and / or sending SL data.

Description

Information processing method and device thereof Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to an information processing method and device thereof. Background Art

[0002] To support direct communication between terminals, the direct communication (also called sidelink, SL) communication mode was introduced. The interface between terminals is PC-5. Sidelink communication can use unlicensed spectrum. Unlicensed spectrum is open and can be effectively utilized to improve performance and speed. This scenario is called Sindlink-U (Sidelink-Unlicensed). When terminals send sidelink data on unlicensed spectrum, LBT (listen before talk) is also required. The continuous LBT mechanism also applies to sidelink communication on unlicensed spectrum.

[0003] However, there is currently a lack of effective means to deal with continuous LBT failure in SL.

[0004] Summary of the Invention

[0005] The embodiments of the present disclosure provide an information processing method and an apparatus thereof.

[0006] According to a first aspect of an embodiment of the present disclosure, an information processing method is proposed, including:

[0007] The terminal detects a sidelink SL continuous listen-before-talk (LBT) failure on a first resource block set (RB set), and starts a timer associated with the first RB set; wherein the timer is used to enable the terminal to determine whether to cancel the SL continuous LBT failure of the first RB set;

[0008] During the running of the timer associated with the first RB set, the terminal determines that the timer associated with the first RB set meets a stop condition, and stops the timer associated with the first RB set.

[0009] According to a second aspect of the embodiments of the present disclosure, an information processing method is proposed, including:

[0010] The network device receives a side link SL continuous listen-before-talk LBT failure report sent by the terminal; wherein the SL continuous LBT failure report includes an indication of SL continuous LBT failure triggered by at least one resource block set RB set, and the at least one RB set includes a first RB set, and the SL continuous LBT failure report is used by the terminal to determine whether to stop the timer associated with the first RB set during the operation of the timer associated with the first RB set.

[0011] According to a third aspect of the embodiments of the present disclosure, an information processing method is proposed, including:

[0012] The network device sends first information to the terminal; the first information is used by the terminal to determine whether to stop the timer associated with the second resource block set RB set, wherein the second RB set triggers the side link SL continuous listen-before-talk LBT failure and the associated timer is running.

[0013] According to a fourth aspect of the embodiments of the present disclosure, an information processing method is proposed, including:

[0014] The network device sends timer reconfiguration information to the terminal; the timer reconfiguration information is used by the terminal to determine whether to cancel the side link SL continuous listen-before-talk LBT failure of the third resource block set RB set, wherein the third RB set triggers the side link SL continuous listen-before-talk LBT failure and the SL continuous LBT failure has not been canceled, and the timer is used to determine whether the third RB set that triggers the SL continuous LBT failure cancels the SL continuous LBT failure.

[0015] According to a fifth aspect of an embodiment of the present disclosure, a first communication device is provided, including:

[0016] a processing module, configured to detect a sidelink SL continuous listen-before-talk (LBT) failure on a first resource block set (RB set), and start a timer associated with the first RB set; wherein the timer is configured to determine whether the first RB set that triggered the SL continuous LBT failure cancels the SL continuous LBT failure;

[0017] The processing module is further configured to, during the running period of the timer associated with the first RB set, determine that the timer associated with the first RB set meets a stop condition, and stop the timer associated with the first RB set.

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

[0019] A transceiver module is used to receive a side link SL continuous listen-before-talk LBT failure report sent by a terminal; wherein the SL continuous LBT failure report includes an indication of SL continuous LBT failure triggered by at least one resource block set RB set, the at least one RB set includes a first RB set, and the SL continuous LBT failure report is used by the terminal to determine whether to stop the timer associated with the first RB set during the operation of the timer associated with the first RB set.

[0020] According to a seventh aspect of an embodiment of the present disclosure, a second communication device is provided, including:

[0021] A transceiver module is used to send first information to a terminal; the first information is used by the terminal to determine whether to stop a timer associated with a second resource block set RB set, wherein the second RB set triggers a side link SL continuous listen-before-talk LBT failure and the associated timer is running.

[0022] According to an eighth aspect of an embodiment of the present disclosure, a second communication device is provided, including:

[0023] A transceiver module is used to send timer reconfiguration information to a terminal; the timer reconfiguration information is used by the terminal to determine whether to cancel the side link SL continuous listen-before-talk LBT failure of a third resource block set RB set, wherein the third RB set triggers the side link SL continuous listen-before-talk LBT failure and the SL continuous LBT failure has not been canceled, and the timer is used to enable the terminal to determine whether to cancel the SL continuous LBT failure of the third RB set.

[0024] According to a ninth aspect of an embodiment of the present disclosure, a communication system is provided, including:

[0025] A terminal, configured to execute an optional implementation of the first aspect;

[0026] A network device is configured to perform the optional implementation of the aforementioned second aspect.

[0027] According to a tenth aspect of an embodiment of the present disclosure, a communication device is provided, including: one or more processors;

[0028] The processor is used to call instructions to enable the communication device to execute the optional implementation methods of the aforementioned first aspect, second aspect, third aspect and fourth aspect.

[0029] According to the eleventh aspect of the embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the optional implementation methods of the aforementioned first aspect, second aspect, third aspect and fourth aspect.

[0030] According to the technical solution disclosed in the present invention, the problem of how to deal with the detection of SL continuous LBT failure can be solved. A timer (such as a side link continuous LBT failure recovery timer) is used to determine whether the RB set that triggered the SL continuous LBT failure cancels the SL continuous LBT failure. During the operation of the timer associated with the RB set, the timer can be stopped accurately to cancel the SL continuous LBT failure of the RB set as soon as possible, so as to facilitate the resumption of using the resources on the RB set to receive and / or send SL data as soon as possible. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

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

[0033] FIG2A is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure;

[0034] FIG2B is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure;

[0035] FIG2C is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure;

[0036] FIG2D is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure;

[0037] FIG3A is a flow chart illustrating an information processing method according to an embodiment of the present disclosure;

[0038] FIG3B is a flow chart of an information processing method according to an embodiment of the present disclosure;

[0039] FIG3C is a flow chart illustrating an information processing method according to an embodiment of the present disclosure;

[0040] FIG3D is a flow chart illustrating an information processing method according to an embodiment of the present disclosure;

[0041] FIG3E is a flow chart illustrating an information processing method according to an embodiment of the present disclosure;

[0042] FIG4A is a flow chart illustrating an information processing method according to an embodiment of the present disclosure;

[0043] FIG4B is a flow chart illustrating an information processing method according to an embodiment of the present disclosure;

[0044] FIG4C is a flow chart illustrating an information processing method according to an embodiment of the present disclosure;

[0045] FIG5A is a schematic structural diagram of a terminal proposed in an embodiment of the present disclosure;

[0046] FIG5B is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure;

[0047] FIG6A is a schematic structural diagram of a communication device 6100 proposed in an embodiment of the present disclosure;

[0048] FIG6B is a schematic structural diagram of a chip 6200 according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0049] The embodiments of the present disclosure provide an information processing method and an apparatus thereof.

[0050] In a first aspect, an embodiment of the present disclosure provides an information processing method, including:

[0051] The terminal detects a sidelink SL continuous listen-before-talk (LBT) failure on a first resource block set (RB set), and starts a timer associated with the first RB set; wherein the timer is used to enable the terminal to determine whether to cancel the SL continuous LBT failure of the first RB set;

[0052] During the running of the timer associated with the first RB set, the terminal determines that the timer associated with the first RB set meets a stop condition, and stops the timer associated with the first RB set.

[0053] In the above embodiment, the problem of how to deal with the detection of SL continuous LBT failure can be solved. A timer (such as a side link continuous LBT failure recovery timer) is used to determine whether the RB set that triggers the SL continuous LBT failure cancels the SL continuous LBT failure. During the operation of the timer associated with the RB set, the timer can be stopped accurately to cancel the SL continuous LBT failure of the RB set as soon as possible, so as to facilitate the resumption of using the resources on the RB set to receive and / or send SL data as soon as possible.

[0054] It should be understood that when a side link SL continuous listen-before-talk LBT failure is detected on a specific resource in the resource pool (e.g., the first resource block set RB set), a timer associated with the resource (e.g., the first RB set) where the side link SL continuous listen-before-talk LBT failed can be started. When the timer times out, it is considered that the resource no longer has a SL continuous LBT failure and can be used for resource transmission. In some embodiments, the timer can be stopped according to specific conditions. When the timer is stopped, it is considered that the resource corresponding to the timer no longer has a SL continuous LBT failure. As a result, the terminal can use the resource for transmission or attempt to use the resource for transmission.

[0055] In combination with some embodiments of the first aspect, in some embodiments, the terminal determines that the timer associated with the first RB set meets a stop condition, and stops the timer associated with the first RB set, including:

[0056] The terminal generates or sends a SL continuous LBT failure report, the timer associated with the first RB set is running, and the timer associated with the first RB set is stopped; wherein, the SL continuous LBT failure report is used to indicate that at least one RB set triggers the SL continuous LBT failure, and the at least one RB set includes the first RB set.

[0057] In the above embodiment, when the terminal generates or sends an SL continuous LBT failure report, if the timer associated with the first RB set that triggers the SL continuous LBT failure is running, the timer associated with the first RB set can be stopped. Thus, the timer associated with the first RB set can be stopped accurately to cancel the SL continuous LBT failure of the first RB set as soon as possible, so as to facilitate the resumption of using the resources on the first RB set to receive and / or send SL data as soon as possible.

[0058] In combination with some embodiments of the first aspect, in some embodiments, the SL continuous LBT failure report is carried on the media access control MAC control element CE.

[0059] In conjunction with some embodiments of the first aspect, in some embodiments, the sidelink transmission resource allocation mode of the terminal is the first resource allocation mode or the second resource allocation mode, and the terminal is in a radio resource control RRC connected state;

[0060] Among them, the first resource allocation method is that the network device schedules the sidelink transmission resources; the second resource allocation method is that the terminal independently selects the sidelink transmission resources.

[0061] In the above embodiment, the timer proposed in the present disclosure (for example, it can also be called the side link continuous LBT failure recovery timer) can be applied to the terminal in which the side link transmission resource allocation mode is the first resource allocation mode or the second resource allocation mode and is in the RRC connection state, thereby solving the problem of unclear applicable scenarios of the timer.

[0062] In combination with some embodiments of the first aspect, in some embodiments, the terminal determines that the timer associated with the first RB set meets a stop condition, and stops the timer associated with the first RB set, including:

[0063] The terminal determines that the SL continuous LBT failure on the first RB set is canceled, and a timer associated with the first RB set is running, and stops the timer associated with the first RB set.

[0064] In the above embodiment, when the terminal cancels the SL continuous LBT failure on the first RB set through other means, if the timer associated with the first RB set is running, the timer associated with the first RB set is stopped. Thus, the timer associated with the first RB set can be stopped accurately and quickly to cancel the SL continuous LBT failure of the first RB set as soon as possible, so as to facilitate the resumption of using the resources on the first RB set to receive and / or send SL data as soon as possible.

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

[0066] The terminal determines that a first parameter is configured or reconfigured, a timer associated with a second RB set is running, and stops the timer associated with the second RB set, wherein the first parameter is an SL continuous LBT failure recovery configuration parameter.

[0067] In the above embodiment, when the SL continuous LBT failure recovery configuration parameters are configured or reconfigured, if the timers associated with one or some RB sets (for example, also referred to as side link continuous LBT failure recovery timers) are running, these running timers can be stopped. Thus, these running timers can be stopped accurately and quickly to cancel the SL continuous LBT failure of these RB sets as soon as possible, so as to facilitate the recovery of the use of resources on these RB sets to receive and / or send SL data as soon as possible.

[0068] In conjunction with some embodiments of the first aspect, in some embodiments, the first parameter includes at least one of the following:

[0069] Sidelink continuous LBT failure detection timer;

[0070] Maximum number of consecutive LBT failures in the sidelink;

[0071] The timer (for example, may also be called a sidelink continuous LBT failure recovery timer).

[0072] In conjunction with some embodiments of the first aspect, in some embodiments, the first parameter is configured or reconfigured according to the SL bandwidth part BWP granularity;

[0073] The terminal determines that the first parameter is configured or reconfigured, and a timer associated with the second RB set is running, and stops the timer associated with the second RB set, including:

[0074] The terminal determines that the first parameter corresponding to the first SL BWP including the second RB set is configured or reconfigured, and a timer associated with the second RB set is running; the second RB set is any RB set belonging to the first SL BWP;

[0075] The terminal stops a timer associated with the second RB set.

[0076] In the above embodiment, the SL continuous LBT failure recovery configuration parameters are configured or reconfigured according to the SL BWP granularity. When the SL continuous LBT failure recovery configuration parameters are configured or reconfigured, if the timer associated with the RB set on a certain SL BWP (for example, it can also be called the side link continuous LBT failure recovery timer) is running, the timer associated with the RB set on the SL BWP can be stopped. Thus, these running timers can be stopped accurately and quickly to cancel the SL continuous LBT failure of these RB sets as soon as possible, so as to facilitate the recovery of the use of resources on these RB sets to receive and / or send SL data as soon as possible.

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

[0078] The terminal determines that the media access control MAC entity is reset and stops all the running timers.

[0079] In the above embodiment, when it is determined that the MAC entity is reset, the terminal can stop all running timers (for example, also called side link continuous LBT failure recovery timers). Thus, these running timers can be stopped accurately and quickly to cancel the SL continuous LBT failure of these RB sets as soon as possible, so as to facilitate the resumption of using the resources on these RB sets to receive and / or send SL data as soon as possible.

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

[0081] The terminal determines that a timer associated with the third RB set is reconfigured, and cancels the SL continuous LBT failure of the third RB set.

[0082] In the above embodiment, it is possible to resume using resources on the third RB set to receive and / or send SL data as quickly as possible.

[0083] In combination with some embodiments of the first aspect, in some embodiments, the timer is configured or reconfigured according to the SL BWP granularity; and the terminal determines the timer reconfiguration associated with the third RB set and cancels the SL continuous LBT failure of the third RB set, including:

[0084] The terminal determines a timer reconfiguration corresponding to the second SL BWP;

[0085] The terminal cancels the SL continuous LBT failure of the third RB set on the second SL BWP; the third RB set is any RB set belonging to the second SL BWP, the third RB set triggers the SL continuous LBT failure and the SL continuous LBT failure has not been canceled.

[0086] In the above embodiment, the timer (for example, it may also be called the side link continuous LBT failure recovery timer) is configured or reconfigured according to the SL BWP granularity; if the timer is reconfigured, the SL continuous LBT failure of any RB set on the SL BWP, which triggers the SL continuous LBT failure and has not yet canceled the SL continuous LBT failure, can facilitate the recovery of the use of the resources of the RB set on the SL BWP to receive and / or send SL data as soon as possible.

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

[0088] The terminal determines that the third SL BWP is deactivated and a timer associated with a fourth RB set is running, and stops the timer associated with the fourth RB set; the fourth RB set is any RB set belonging to the third SLBWP.

[0089] In the above embodiment, if the SL BWP is deactivated, the timer associated with any RB set on the SL BWP (such as a running timer) can be stopped. In this way, these running timers can be stopped accurately and quickly to cancel the SL continuous LBT failure of these RB sets as soon as possible, so as to facilitate the resumption of using the resources on these RB sets to receive and / or send SL data as soon as possible.

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

[0091] After stopping the timer associated with the first RB set, it is determined that the terminal resumes using resources on the first RB set to receive and / or send SL data.

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

[0093] The terminal determines that all RB sets in the resource pool including the first RB set trigger the SL continuous LBT failure;

[0094] The terminal clears the sidelink granted resources selected from the resource pool.

[0095] In conjunction with some embodiments of the first aspect, in some embodiments, the sidelink transmission resource allocation mode of the terminal is the second resource allocation mode, and the terminal is in any of the following states:

[0096] RRC connection state;

[0097] RRC idle state;

[0098] RRC inactive state;

[0099] Out of coverage, OOC state.

[0100] In combination with some embodiments of the first aspect, in some embodiments, the sidelink transmission resource allocation mode of the terminal is the first resource allocation mode, and the terminal is in an RRC connected state.

[0101] In a second aspect, an embodiment of the present disclosure provides an information processing method, including:

[0102] The network device receives a side link SL continuous listen-before-talk LBT failure report sent by the terminal; wherein the SL continuous LBT failure report includes an indication of SL continuous LBT failure triggered by at least one resource block set RB set, and the at least one RB set includes a first RB set, and the SL continuous LBT failure report is used by the terminal to determine whether to stop the timer associated with the first RB set during the operation of the timer associated with the first RB set.

[0103] In combination with some embodiments of the second aspect, in some embodiments, the SL continuous LBT failure report is carried on the media access control MAC control element CE.

[0104] In a third aspect, an embodiment of the present disclosure provides an information processing method, including:

[0105] The network device sends first information to the terminal; the first information is used by the terminal to determine whether to stop the timer associated with the second resource block set RB set, wherein the second RB set triggers the side link SL continuous listen-before-talk LBT failure and the associated timer is running.

[0106] In combination with some embodiments of the third aspect, in some embodiments, the first information includes configuration information or reconfiguration information of a first parameter, and the first parameter is an SL continuous LBT failure recovery configuration parameter.

[0107] In conjunction with some embodiments of the third aspect, in some embodiments, the first parameter includes at least one of the following:

[0108] Sidelink continuous LBT failure detection timer;

[0109] Maximum number of consecutive LBT failures in the sidelink;

[0110] The timer.

[0111] In combination with some embodiments of the third aspect, in some embodiments, the first parameter is configured or reconfigured according to the granularity of the SL bandwidth part BWP; wherein, the first information includes the configuration information or reconfiguration information of the first parameter corresponding to the first SL BWP, and the second RB set is any RB set belonging to the first SL BWP.

[0112] In a fourth aspect, an embodiment of the present disclosure provides an information processing method, including:

[0113] The network device sends timer reconfiguration information to the terminal; the timer reconfiguration information is used by the terminal to determine whether to cancel the side link SL continuous listen-before-talk LBT failure of the third resource block set RB set, wherein the third RB set triggers the side link SL continuous listen-before-talk LBT failure and the SL continuous LBT failure has not been canceled, and the timer is used to enable the terminal to determine whether to cancel the SL continuous LBT failure of the third RB set.

[0114] In combination with some embodiments of the fourth aspect, in some embodiments, the timer is configured or reconfigured according to the granularity of the SL bandwidth part BWP; the reconfiguration information of the timer includes the timer reconfiguration corresponding to the second SL BWP, and the third RB set is any RB set belonging to the second SL BWP.

[0115] In a fifth aspect, an embodiment of the present disclosure proposes a terminal, comprising at least one of a transceiver module and a processing module; wherein the terminal is used to execute the optional implementation method of the first aspect.

[0116] In a sixth aspect, an embodiment of the present disclosure proposes a network device, comprising at least one of a transceiver module and a processing module; wherein the above-mentioned network device is used to execute the optional implementation methods of the second aspect, the third aspect and the fourth aspect.

[0117] In a seventh aspect, an embodiment of the present disclosure provides a communication system, including:

[0118] A terminal configured as an optional implementation of the first aspect;

[0119] A network device is configured to execute the optional implementation of the aforementioned second aspect, third aspect and fourth aspect.

[0120] In an eighth aspect, an embodiment of the present disclosure proposes a communication device, comprising: one or more processors; wherein the processor is used to call instructions to enable the communication device to execute the optional implementation method of the aforementioned first aspect.

[0121] In the ninth aspect, an embodiment of the present disclosure proposes a communication device, comprising: one or more processors; wherein the processor is used to call instructions to enable the communication device to execute the optional implementation methods of the aforementioned second aspect, third aspect and fourth aspect.

[0122] In the tenth 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 optional implementation methods of the aforementioned first aspect, second aspect, third aspect and fourth aspect.

[0123] In an eleventh 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 optional implementation of the first, second, third and fourth aspects.

[0124] In a twelfth 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 optional implementation of the first, second, third and fourth aspects.

[0125] In a thirteenth aspect, an embodiment of the present disclosure provides a chip or a chip system, which includes a processing circuit configured to execute the method described in the optional implementation of the first, second, third, and fourth aspects above.

[0126] It is understandable that the above-mentioned terminals, network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods 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.

[0127] The present disclosure provides an information processing method and apparatus thereof. In some embodiments, the terms information processing method, communication method, etc. are interchangeable, the terms information processing apparatus, communication apparatus, etc. are interchangeable, and the terms information processing system, communication system, etc. are interchangeable.

[0128] 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.

[0129] 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.

[0130] 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.

[0131] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "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.

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

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

[0134] 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.

[0135] 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.

[0136] 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.

[0137] 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.

[0138] In some embodiments, terms such as "time / frequency" and "time / frequency domain" refer to the time domain and / or the frequency domain.

[0139] 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.

[0140] 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.

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

[0142] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0143] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0144] In some embodiments, "terminal" or "terminal device" may be referred to as "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.

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

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

[0147] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. The communication system may include, but is not limited to, one terminal and one network device. The number and configuration of devices shown in Figure 1 are for example purposes only and do not limit the present disclosure. In practical applications, two or more terminals and two or more network devices may be included. The communication system 100 shown in Figure 1 includes, for example, one terminal 101 and one network device 102.

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

[0149] In some embodiments, the network device may be an access network device. In some embodiments, the access network device is, for example, a node or device that connects a terminal device to a wireless network. The access network device may include, but is not limited to, at least one of an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a NodeB (NB), a home nodeB (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 RAN, a cloud RAN, a base station in other communication systems, and an access node in a Wi-Fi system.

[0150] 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.

[0151] 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.

[0152] 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.

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

[0154] 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).

[0155] In some embodiments, the link for direct communication between terminals is PC-5. The interface between the terminals is PC-5. Based on the correspondence between the sending and receiving terminals, three transmission modes are supported on the sidelink: unicast, multicast, and broadcast. The sending terminal sends sidelink control information (SCI) on the physical sidelink control channel (PSCCH) and sends the second-stage SCI on the physical sidelink shared channel (PSSCH), which carries the resource location of the transmitted data and the source and destination identifiers. For data packets with hybrid automatic repeat request (HARQ) feedback enabled, the receiving terminal performs hybrid automatic repeat request acknowledgment (HARQ-ACK) feedback on the physical sidelink feedback channel (PSFCH) for the PSSCH.

[0156] In some embodiments, sidelink communication has two transmission resource allocation modes: one is the network dynamic scheduling mode (mode 1, also called the first resource allocation mode), and the other is the terminal autonomous selection mode from the network configured or pre-configured resource pool (mode 2, also called the second resource allocation mode). Dynamic scheduling means that the network dynamically allocates transmission resources on the sidelink to the terminal based on the terminal's cached data report, while autonomous selection means that the terminal randomly selects transmission resources from the network configured or pre-configured resource pool. The network can configure multiple resource pools for the terminal on a BWP (Bandwidth Part). The specific allocation mode to be used is configured by the network side through RRC (Radio Resource Control) signaling.

[0157] Version R18 supports Sidelink communication using unlicensed spectrum. Sidelink communication can use unlicensed frequency band spectrum for communication. The unlicensed frequency band spectrum is open and can improve performance and speed through effective utilization. This scenario can be called Sindlink-U (Sidelink-Unlicensed, unlicensed spectrum of the sidelink) scenario. The terminal also needs to perform LBT (listen before talk) when sending Sidelink data on the unlicensed spectrum. In some embodiments, the terminal must first sense the communication channel to determine whether the channel is busy. If the channel is detected to be busy, LBT fails and it is necessary to wait for a period of time before performing LBT again.

[0158] In some embodiments, the continuous LBT mechanism is also applicable to Sidelink communications on unlicensed spectrum. The terminal counts the number of LBT failures on each SLBWP (Bandwidth Part). The network device configures the maximum number of SL continuous LBT failures (e.g., sl-Lbt-FailureInstanceMaxCount) and the SL continuous LBT failure detection timer (e.g., sl-Lbt-FailureDetectionTimer) for the terminal according to the SL BWP granularity through RRC (Radio Resource Control) signaling (e.g., sl-Lbt-FailureRecoveryConfig) for counting SL continuous LBT failures. The terminal maintains a variable (e.g., LBT_counter) for each RB set, and the initial value of the variable is 0. For each RB set configured with Lbt-FailureRecoveryConfig, when the terminal receives the SL LBT failure indication submitted by the physical layer, it starts or restarts the sl-Lbt-FailureDetectionTimer, and the variable is increased by 1. When the variable is greater than or equal to the sl-Lbt-FailureInstanceMaxCount, the RB set triggers SL continuous LBT failure. When the SL continuous LBT failure detection timer times out or the upper layer reconfigures the maximum number of SL continuous LBT failures / SL continuous LBT failure detection timer, the terminal resets the variable to 0. The terminal indicates the identifier of the RB set where SL continuous LBT failure occurs on the network side through the SL continuous LBT failure MAC (Media Access Control) CE (Control Element). The MAC CE can carry the identifiers of multiple RB sets that have detected SL continuous LBT failures. If the MAC (Media Access Control) PDU (Protocol Data Unit) containing the SL continuous LBT failure MAC CE is sent successfully, the terminal cancels the SL continuous LBT failure status of the RB set where the SL continuous LBT failure occurs, which is indicated by the SL continuous LBT failure MAC CE.

[0159] In some embodiments, a terminal running in the above-mentioned first resource allocation mode and a terminal in the RRC connection state and running in the above-mentioned second resource allocation mode can report to the network device through the SL continuous LBT failure report, that is, the above-mentioned SL continuous LBT failure MAC CE.

[0160] However, there is currently a lack of effective means to deal with continuous LBT failure in SL.

[0161] To this end, the embodiments of the present disclosure provide an information processing method and device thereof, which can solve the problem of how to deal with the situation when SL continuous LBT failure is detected. A timer (such as a side link continuous LBT failure recovery timer) is used to determine whether the RB set that triggers the SL continuous LBT failure cancels the SL continuous LBT failure, and during the operation of the timer associated with the RB set, the timer can be accurately stopped to cancel the SL continuous LBT failure of the RB set as soon as possible, so as to facilitate the resumption of using the resources on the RB set to receive and / or send SL data as soon as possible.

[0162] FIG2A is an interactive diagram illustrating an information processing method according to an embodiment of the present disclosure. As shown in FIG2A , the information processing method according to an embodiment of the present disclosure can be applied to a communication system 100 , and the method includes but is not limited to the following steps.

[0163] Step S2101: Terminal 101 detects that SL continuous LBT fails on a first RB set, and starts a timer associated with the first RB set.

[0164] In some embodiments, the terminal 101 may detect whether a SL continuous LBT failure occurs based on the maximum number of SL continuous LBT failures (also referred to as the maximum number of side link continuous LBT failures) and the SL continuous LBT failure detection timer (also referred to as the side link continuous LBT failure detection timer) configured by the network device. Exemplarily, if the terminal 101 detects that the number of LBT failures occurring on the first RB set is greater than or equal to the maximum number of SL continuous LBT failures during the operation of the SL continuous LBT failure detection timer, it may be determined that a SL continuous LBT failure is detected on the first RB set, that is, the first RB set triggers the SL continuous LBT failure. When the terminal 101 detects a SL continuous LBT failure on the first RB set, it may start the timer associated with the first RB set.

[0165] In some embodiments, the timer can be used to enable the terminal to determine whether to cancel the SL continuous LBT failure of the first RB set. Exemplarily, the timer can be used to determine whether the RB set that has triggered the SL continuous LBT failure and has not yet canceled the SL continuous LBT failure can cancel the SL continuous LBT failure. Exemplarily, during the operation of the timer associated with the RB set, it means that the SL continuous LBT failure of the RB set cannot be canceled, and it can be considered that the RB set resources cannot be restored to use; if the timer associated with the RB set times out or stops, it means that the SL continuous LBT failure of the RB set can be canceled, and it can be considered that the RB set resources can be restored to use.

[0166] In some embodiments, the timer may also be called a side link continuous LBT failure recovery timer, or a side link continuous LBT failure cancellation timer, or may be named by other names, which is not limited in this disclosure.

[0167] In some embodiments, a timer associated with the first RB set can be used to determine whether the first RB set that triggered the SL continuous LBT failure cancels the SL continuous LBT failure. For example, if the timer associated with the first RB set is running, it indicates that the SL continuous LBT failure of the first RB set cannot be canceled, and it can be considered that the first RB set resources cannot be restored for use; if the timer associated with the first RB set times out or stops, it indicates that the SL continuous LBT failure of the first RB set can be canceled, and it can be considered that the first RB set resources can be restored for use.

[0168] In some embodiments, the timer (which may be referred to as a sidelink continuous LBT failure recovery timer or a SL continuous LBT failure cancellation timer) proposed in the present disclosure may be maintained at the RB set granularity. That is, one RB set may be associated with one timer. For example, taking the first RB set and the second RB set as an example, assuming that a SL continuous LBT failure is detected on the first RB set and no SL continuous LBT failure is detected on the second RB set, the timer associated with the first RB set may be started.

[0169] In some embodiments, the above-mentioned timer proposed in the present disclosure (which may be called a side link continuous LBT failure recovery timer, or may be called a SL continuous LBT failure cancellation timer) is applicable to a terminal operating in a second resource allocation mode, wherein the terminal is in an RRC IDLE / INACTIVE / OOC state.

[0170] In some embodiments, the above-mentioned timer proposed in the present disclosure (which may be called a side link continuous LBT failure recovery timer, or may be called a SL continuous LBT failure cancellation timer) is applicable to a terminal operating in a second resource allocation mode, wherein the terminal is in an RRC CONNECTED / IDLE / INACTIVE / OOC state.

[0171] In some embodiments, the timer (which may be referred to as a sidelink continuous LBT failure recovery timer or a SL continuous LBT failure cancellation timer) proposed in the present disclosure is applicable to a terminal operating in the second resource allocation mode, where the terminal is in the RRC CONNECTED / IDLE / INACTIVE / OOC state. The timer is also applicable to a terminal operating in the first resource allocation mode.

[0172] In some embodiments, the timer can be configured by a network device. For example, a terminal 101 in an RRC connected state can obtain the timer configuration through dedicated signaling. A terminal 101 in an RRC IDLE (idle) / INACTIVE (inactive) state can obtain the timer configuration through a SIB (System Information Block). A terminal 101 in an OOC (Out of Coverage) state can obtain the timer configuration through pre-configuration.

[0173] In some embodiments, the above-mentioned timers can be configured or reconfigured according to the granularity of the SL BWP. Different SL BWPs can be configured with the same or different timers, that is, the timer lengths can be the same or different. For example, taking the case where a network device is configured with Timer 1 of a first SL BWP and Timer 2 of a second SL BWP as an example, the first SL BWP and the second SL BWP are different BWPs, and the length of Timer 1 and the length of Timer 2 can be the same or different.

[0174] In step S2102, the terminal 101 generates or sends a SL continuous LBT failure report (SL continuous LBT failure MAC CE). If the timer associated with the first RB set is running, the timer associated with the first RB set is stopped.

[0175] In some embodiments, the SL continuous LBT failure report is used to indicate that at least one RB set triggers SL continuous LBT failure, and the at least one RB set includes the first RB set.

[0176] In some embodiments, the terminal 101 detects a SL continuous LBT failure on the first RB set, starts a timer associated with the first RB set, and during the operation of the timer associated with the first RB set, the terminal 101 generates or sends the above-mentioned SL continuous LBT failure report, and the SL continuous LBT failure report is used to indicate that at least one RB set triggers a SL continuous LBT failure, and the at least one RB set includes the first RB set, then the terminal 101 can stop the timer associated with the first RB set. Exemplarily, during the operation of the timer associated with the first RB set, the terminal 101 generates or sends the above-mentioned SL continuous LBT failure report, and the SL continuous LBT failure report is used to indicate that at least one RB set triggers a SL continuous LBT failure, and the at least one RB set includes the first RB set, and the timer associated with the first RB set has not timed out (such as being running), the terminal 101 will also stop the timer associated with the first RB set. That is to say, the terminal 101 generates or sends the above-mentioned SL continuous LBT failure report, which is used to indicate that at least one RB set triggers SL continuous LBT failure, and the at least one RB set includes the first RB set. Then the terminal 101 can stop the corresponding timer and consider resuming the use of resources on the corresponding RB set.

[0177] Exemplarily, during the operation of the timer associated with the above-mentioned first RB set, the terminal 101 generates or sends the above-mentioned SL continuous LBT failure report, and the SL continuous LBT failure report is used to indicate that at least one RB set triggers SL continuous LBT failure, and the at least one RB set includes the first RB set. The timer associated with the above-mentioned first RB set is running and has been running for a period of time (without timeout), then the terminal 101 will also stop the timer associated with the first RB set and cancel the SL continuous LBT failure of the first RB set, and then it can be considered that the resources of the first RB set can be restored to use.

[0178] In some embodiments, the terminal 101 detects a SL continuous LBT failure on the first RB set. The terminal 101 may report a SL continuous LBT failure report to the network device 101 so that the network device 101 can understand which RB set or sets triggered the SL continuous LBT failure. Of course, after detecting the SL continuous LBT failure, the terminal may generate a SL continuous LBT failure report and send the report to the network device. In some embodiments, the terminal generates the SL continuous LBT failure report and sends the SL continuous LBT failure report to the network device. In some embodiments, the terminal may cancel the SL continuous LBT failure after sending the SL continuous LBT failure report and stop the timer associated with the resource set of the SL continuous LBT failure. For example, the terminal may stop the timer when canceling the SL continuous LBT failure. Alternatively, the terminal may stop the timer after a preset time period after canceling the SL continuous LBT failure. Alternatively, the terminal may cancel the SL continuous LBT failure and stop the timer after a preset time period has passed after sending the SL continuous LBT failure report to the network device. It should be understood that when a SL continuous LBT failure occurs, a timer associated with the resource causing the SL continuous LBT failure is started, and a SL continuous LBT failure report is generated and sent to the network device. After the SL continuous LBT failure report is sent to the network device, the network device can make corresponding adjustments, such as reconfiguration. The terminal can cancel the SL continuous LBT failure for the corresponding resource / resource set and stop the timer associated with the SL continuous LBT failure.

[0179] In some embodiments, the terminal 101 detects SL continuous LBT failure on the first RB set, and the terminal 101 may generate or send a MAC PDU, which includes a SL continuous LBT failure report. In some embodiments, the SL continuous LBT failure report may be carried on a MAC CE. Exemplarily, the terminal 101 may generate or send a MAC PDU, which includes a MAC CE, which is used to indicate that at least one RB set triggers SL continuous LBT failure, and the at least one RB set includes the first RB set. For the RB set that triggers SL continuous LBT failure indicated in the MAC CE, if the timer associated with the RB set is running, the terminal 101 stops the timer associated with the RB set. The RB set is the RB set that triggers SL continuous LBT failure indicated in the MAC CE, which may be one or more.

[0180] In some embodiments, the sidelink transmission resource allocation mode of the terminal 101 is the first resource allocation mode (such as the above-mentioned mode 1) or the second resource allocation mode (such as the above-mentioned mode 2), and the terminal 101 is in the RRC connected state; wherein, the first resource allocation mode is that the network device 102 schedules the sidelink transmission resource; and the second resource allocation mode is that the terminal 101 independently selects the sidelink transmission resource. Exemplarily, the timer proposed in the present disclosure (which may be referred to as the sidelink continuous LBT failure recovery timer) may only be applicable to the terminal 101 operating in the above-mentioned second resource allocation mode, for example, the terminal 101 is in the RRC connected state and operates in the above-mentioned mode 2, such as the sidelink transmission resource allocation mode of the terminal 101 is the second resource allocation mode.

[0181] Exemplarily, the timer proposed in the present disclosure (which may be referred to as a sidelink continuous LBT failure recovery timer) may be applicable to both the terminal 101 operating in the aforementioned mode 2 and the terminal 101 operating in the aforementioned mode 1. For example, when the terminal 101 is in an RRC connected state, the terminal 101 may operate in both mode 2 and mode 1.

[0182] In some embodiments, after stopping the timer associated with the first RB set, the terminal 101 cancels the SL continuous LBT failure of the first RB set. Optionally, after the terminal 101 cancels the SL continuous LBT failure of the first RB set, the terminal 101 can resume using the resources on the first RB set to receive and / or send SL data. Exemplarily, after stopping the timer associated with the first RB set, the terminal 101 can resume using the resources on the first RB set to receive and / or send SL data. However, it should be understood that the terminal can not only cancel the SL continuous LBT failure of the first RB set, but also cancel the SL continuous LBT failure of other resource sets or resource blocks in the resource pool so that these resources can be used.

[0183] Step S2103, the network device 102 receives the SL continuous LBT failure report.

[0184] In some embodiments, the above-mentioned SL continuous LBT failure report may be sent by the terminal 101. The network device 102 receives the SL continuous LBT failure report sent by the terminal 101. Exemplarily, the terminal 101 detects an SL continuous LBT failure on the first RB set, and the terminal 101 generates and sends the above-mentioned SL continuous LBT failure report. The above-mentioned SL continuous LBT failure report is used to indicate that at least one RB set triggers an SL continuous LBT failure, and the at least one RB set includes the first RB set. The network device 102 receives the SL continuous LBT failure report sent by the terminal 101, and can determine that the at least one RB set triggers the SL continuous LBT failure.

[0185] In some embodiments, the above-mentioned SL continuous LBT failure report can be used by the terminal 101 to determine whether to stop the timer associated with the first RB set during the operation of the timer associated with the first RB set. Exemplarily, the network device 102 receives the SL continuous LBT failure report sent by the terminal 101, and the network device can determine that the terminal 101 has stopped the timer associated with the first RB set. That is, the terminal informs the network device through the SL continuous LBT failure report: an SL continuous LBT failure has occurred in a specific resource set, but when the network device receives the SL continuous LBT failure report, it can be considered that the corresponding resource set of the terminal no longer has an SL continuous LBT failure, and the SL continuous LBT failure has been canceled. The network device can continue to use the resource to transmit with the terminal.

[0186] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0187] In some embodiments, terms such as "uplink", "uplink", "physical uplink" can be interchangeable with each other, and terms such as "downlink", "downlink", "physical downlink" can be interchangeable with each other, and terms such as "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" can be interchangeable with each other.

[0188] 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.

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

[0190] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "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, or first A, etc., but not limited to this.

[0191] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0192] The method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2103. For example, step S2102 may be implemented as an independent embodiment, step S2101 + step S2102 may be implemented as an independent embodiment, and step S2101 + step S2102 + step S2103 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0193] In some embodiments, step S2101 and step S2103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0194] In some embodiments, step S2103 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0195] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2A .

[0196] Figure 2B is an interactive diagram illustrating an information processing method according to an embodiment of the present disclosure. As shown in Figure 2B, the information processing method according to an embodiment of the present disclosure can be applied to a communication system 100, and the method includes but is not limited to the following steps.

[0197] Step S2201: Terminal 101 detects that SL continuous LBT fails on a first RB set, and starts a timer associated with the first RB set.

[0198] In some embodiments, the timer may be used to determine whether the RB set that triggered the SL continuous LBT failure and has not yet canceled the SL continuous LBT failure can cancel the SL continuous LBT failure.

[0199] In some embodiments, the timer may also be referred to as a sidelink continuous LBT failure recovery timer, or a sidelink continuous LBT failure cancellation timer, or other names, which are not limited in this disclosure. In short, the timer may be used by the terminal to determine the cancellation of the SL continuous LBT failure to continue resource transmission.

[0200] In some embodiments, the timer associated with the first RB set may be used to determine whether the first RB set that triggers the SL continuous LBT failure cancels the SL continuous LBT failure.

[0201] In some embodiments, the sidelink transmission resource allocation mode of the terminal 101 is the second resource allocation mode (for example, the terminal autonomously selects the sidelink transmission resource), and the terminal 101 is in any of the following states: RRC connected state; RRC idle state; RRC inactive state; OOC (out of coverage) state. Exemplarily, the timer proposed in the present disclosure (which may be referred to as the sidelink continuous LBT failure recovery timer) may only be applicable to the terminal 101 operating in the above-mentioned mode2, and the terminal 101 may be in any of the RRC connected state, RRC idle state, RRC inactive state, and OOC (out of coverage) state. Alternatively, the timer proposed in the present disclosure (which may be referred to as the sidelink continuous LBT failure recovery timer) may only be applicable to the terminal 101 operating in the above-mentioned mode2, and the terminal 101 may be in any of the RRC idle state, RRC inactive state, and OOC (out of coverage) state.

[0202] In some embodiments, the sidelink transmission resource allocation mode of the terminal 101 is the first resource allocation mode (for example, the network device schedules the sidelink transmission resource), and the terminal 101 is in the RRC connected state. Exemplarily, the timer proposed in the present disclosure (which may be referred to as the sidelink continuous LBT failure recovery timer) can be applied to the terminal 101 running in the above-mentioned mode2, and the terminal 101 can be in any of the RRC connected state, RRC idle state, RRC inactive state, and OOC (out of coverage) state; and can also be applied to the terminal 101 running in the above-mentioned mode1, and the terminal 101 is in the RRC connected state. Alternatively, the timer proposed in the present disclosure (which may be referred to as the sidelink continuous LBT failure recovery timer) can be applied to the terminal 101 running in mode2, and the terminal 101 can be in any of the RRC idle state, RRC inactive state, and OOC (out of coverage) state; and can also be applied to the terminal 101 running in the above-mentioned mode1, and the terminal 101 is in the RRC connected state.

[0203] The optional implementation of step S2201 can refer to the optional implementation of step S2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0204] Step S2202: The terminal 101 determines that the SL continuous LBT failure on the first RB set is cancelled, and the timer associated with the first RB set is running, and stops the timer associated with the first RB set.

[0205] Optionally, the terminal 101 determines that the SL continuous LBT failure on the first RB set is canceled during the operation of the timer associated with the first RB set, and if the timer associated with the first RB set is running, the timer associated with the first RB set is stopped. Specifically, the terminal can cancel the SL continuous LBT failure on the first RB set in a variety of ways. For example, when the SL continuous LBT failure on the first RB set reaches a preset duration, the terminal can cancel the SL continuous LBT failure on the first RB set. If at this time, the timer triggered by the SL continuous LBT failure on the first RB set is still running, the terminal stops the timer. Alternatively, the terminal can cancel the SL continuous LBT failure with the first RB set when determining the SL continuous LBT failure on the first RB set, and stop the timer triggered by the SL continuous LBT failure on the first RB set after a preset time period.

[0206] In some embodiments, after stopping the timer associated with the first RB set, terminal 101 may determine to resume using resources on the first RB set to receive and / or send SL data. Exemplarily, after stopping the timer associated with the first RB set, terminal 101 may resume using resources on the first RB set to receive and / or send SL data.

[0207] The method involved in the embodiment of the present disclosure may include at least one of step S2201 and step S2202. For example, step S2202 may be implemented as an independent embodiment, and step S2201 + step S2202 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0208] In some embodiments, step S2201 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0209] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2B .

[0210] Figure 2C is an interactive diagram illustrating an information processing method according to an embodiment of the present disclosure. As shown in Figure 2C, the information processing method according to an embodiment of the present disclosure can be applied to a communication system 100, and the method includes but is not limited to the following steps.

[0211] Step S2301: The network device 102 sends first information.

[0212] In some embodiments, the first information is sent by the network device 102 to the terminal 101. Exemplarily, the network device 102 sends the first information to the terminal 101.

[0213] In some embodiments, the first information may be used by the terminal 101 to determine whether to stop a timer associated with a second RB set, where the second RB set triggers SL continuous LBT failure and the associated timer is running.

[0214] In some embodiments, the first information may include configuration information or reconfiguration information of a first parameter. The first parameter may be a SL continuous LBT failure recovery configuration parameter.

[0215] In some embodiments, the first parameter may be configured or reconfigured at the SL BWP granularity. For example, the first parameter may be the first parameter corresponding to the first SL BWP that includes the second RB set. That is, the network device 102 configures or reconfigures the first parameter corresponding to the first SL BWP for the terminal 101. The first BWP includes the second RB set.

[0216] In some embodiments, the first parameter may be referred to as the SL continuous LBT failure recovery configuration parameter, and may be named sl-LBT-FailureRecoveryConfig, or other names, which are not limited in this disclosure.

[0217] In some embodiments, the first parameter may include but is not limited to at least one of the following: a sidelink continuous LBT failure detection timer; a maximum number of sidelink continuous LBT failures; a timer associated with the first RB set or the second RB set (such as also referred to as a sidelink continuous LBT failure recovery timer). For example, the timer can be understood as a timer associated with any RB set on the first SL BWP. The first RB set here can be a resource set in a resource pool different from the second RB set, or the first RB set can be a subset of the second RB set.

[0218] Step S2302: The terminal 101 determines whether a first parameter corresponding to a first SL BWP including a second RB set is configured or reconfigured.

[0219] In some embodiments, the second RB set is any RB set belonging to the first SL BWP.

[0220] Exemplarily, network device 102 sends first information to terminal 101, where the first information includes configuration information or reconfiguration information of a first parameter, where the first parameter is a first parameter corresponding to a first SL BWP including a second RB set. When terminal 101 receives the first information sent by network device 102, it determines that the first parameter corresponding to the first SL BWP including the second RB set is configured or reconfigured.

[0221] Step S2303: If the terminal 101 determines that the timer associated with the second RB set is running, the terminal 101 stops the timer associated with the second RB set.

[0222] Exemplarily, the terminal 10 determines that the first parameter corresponding to the first SL BWP including the second RB set is configured or reconfigured, and the terminal 101 needs to determine whether the timer associated with the second RB set is running. If the terminal 101 determines that the timer associated with the second RB set is running, the terminal 101 can stop the timer associated with the second RB set. The above-mentioned second RB set is any RB set belonging to the first SL BWP. That is, the terminal 101 determines that the first parameter corresponding to the first SL BWP including the second RB set is configured or reconfigured, and if the timer associated with the RB set on the first SL BWP is running, the terminal 101 can stop the timer associated with the RB set on the first SL BWP.

[0223] Exemplarily, the second RB set may include the first RB set. That is, during the operation of the timer associated with the first RB set, if the terminal 101 determines that the first parameter corresponding to the first SL BWP is configured or reconfigured, the first SL BWP includes the second RB set, and the second RB set may include the first RB set, if the timer associated with the first RB set is running, the terminal 101 may stop the timer associated with the first RB set. If the timers associated with other RB sets (RB sets other than the first RB set) on the first SL BWP are running, the terminal 101 will also stop the timers associated with the other RB sets.

[0224] In some embodiments, after stopping the timer associated with the second RB set, the terminal 101 may determine to resume using resources on the second RB set to receive and / or send SL data.

[0225] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2C .

[0226] Figure 2D is an interactive diagram illustrating an information processing method according to an embodiment of the present disclosure. As shown in Figure 2D, the information processing method according to the embodiment of the present disclosure can be applied to the communication system 100, and the method includes but is not limited to the following steps.

[0227] Step S2401 : The network device 102 sends timer reconfiguration information to the terminal 101 .

[0228] In some embodiments, the reconfiguration information of the above-mentioned timer is used by the terminal 101 to determine whether to cancel the SL continuous LBT failure of the third RB set, wherein the third RB set triggers the SL continuous LBT failure and the SL continuous LBT failure has not been canceled, and the timer is used to determine whether the third RB set that triggers the SL continuous LBT failure cancels the SL continuous LBT failure.

[0229] In some embodiments, the timer reconfiguration information includes a timer reconfiguration corresponding to a second SL BWP, and the third RB set is any RB set belonging to the second SL BWP.

[0230] In some embodiments, the timer (which may be referred to as the sidelink continuous LBT failure recovery timer) proposed in the present disclosure may be maintained at the RB set granularity. That is, one RB set may be associated with one timer. For example, taking the first and third RB sets as an example, if a SL continuous LBT failure is detected on the third RB set, but not on the first RB set, the timer associated with the third RB set may be started.

[0231] In some embodiments, the above-mentioned timers can be configured or reconfigured according to the granularity of the SL BWP. Different SL BWPs can be configured with the same or different timers, that is, the timer lengths can be the same or different. For example, taking the case where a network device is configured with Timer 1 of a first SL BWP and Timer 2 of a second SL BWP as an example, the first SL BWP and the second SL BWP are different BWPs, and the length of Timer 1 and the length of Timer 2 can be the same or different.

[0232] In some embodiments, the timer can be configured by a network device. For example, a terminal 101 in an RRC connected state can obtain the timer configuration through dedicated signaling. A terminal 101 in an RRC IDLE (idle) / INACTIVE (inactive) state can obtain the timer configuration through a SIB (System Information Block). A terminal 101 in an OOC (Out of Coverage) state can obtain the timer configuration through pre-configuration.

[0233] Step S2402: Terminal 101 determines the timer reconfiguration corresponding to the second SL BWP.

[0234] Exemplarily, network device 102 sends reconfiguration information including the timer reconfiguration corresponding to the second SL BWP to terminal 101. When terminal 101 receives the timer reconfiguration information sent by network device 102, terminal 101 can determine the timer reconfiguration corresponding to the second SL BWP.

[0235] In some embodiments, the sidelink transmission resource allocation mode of the terminal 101 is the second resource allocation mode, and the terminal 101 is in any of the following states: RRC connected state; RRC idle state; RRC inactive state; OOC (out of coverage) state. Exemplarily, the timer proposed in the present disclosure (which may be referred to as the sidelink continuous LBT failure recovery timer) may only be applicable to the terminal 101 operating in the above-mentioned mode2, and the terminal 101 may be in any of the RRC connected state, RRC idle state, RRC inactive state, and OOC (out of coverage) state. Alternatively, the timer proposed in the present disclosure (which may be referred to as the sidelink continuous LBT failure recovery timer) may only be applicable to the terminal 101 operating in the above-mentioned mode2, and the terminal 101 may be in any of the RRC idle state, RRC inactive state, and OOC (out of coverage) state.

[0236] In some embodiments, the sidelink transmission resource allocation mode of the terminal 101 is the first resource allocation mode, and the terminal 101 is in the RRC connected state. Exemplarily, the timer proposed in the present disclosure (which may be referred to as the sidelink continuous LBT failure recovery timer) may be applicable to the terminal 101 running in the above-mentioned mode2, where the terminal 101 may be in any of the RRC connected state, the RRC idle state, the RRC inactive state, and the OOC (out of coverage) state; and may also be applicable to the terminal 101 running in the above-mentioned mode1, where the terminal 101 is in the RRC connected state. Alternatively, the timer proposed in the present disclosure (which may be referred to as the sidelink continuous LBT failure recovery timer) may be applicable to the terminal 101 running in mode2, where the terminal 101 may be in any of the RRC idle state, the RRC inactive state, and the OOC (out of coverage) state; and may also be applicable to the terminal 101 running in the above-mentioned mode1, where the terminal 101 is in the RRC connected state.

[0237] Step S2403 : The terminal 101 cancels the SL continuous LBT failure of the third RB set on the second SL BWP; the third RB set is any RB set belonging to the second SL BWP, the third RB set triggers the SL continuous LBT failure and has not yet been canceled.

[0238] Exemplarily, after the terminal 101 determines that the timer corresponding to the second SL BWP is reconfigured, the terminal 101 can cancel the SL continuous LBT failure of the third RB set on the second SL BWP, where the third RB set is any RB set belonging to the second SL BWP, and the third RB set triggers the SL continuous LBT failure and the SL continuous LBT failure has not been canceled. In other words, the timer is configured according to the SL BWP granularity. If the timer corresponding to the second SL BWP is reconfigured, the terminal 101 cancels the SL continuous LBT failure of the RB set on the second SL BWP that triggered the SL continuous LBT failure and the SL continuous LBT failure has not been canceled.

[0239] Exemplarily, the third RB set may include the first RB set. That is, during the operation of the timer associated with the first RB set, if the terminal 101 determines that the timer corresponding to the second SL BWP is reconfigured, the second SL BWP includes the third RB set, and the third RB set includes the first RB set, if the SL continuous LBT failure of the first RB set has not been canceled, then the terminal 101 cancels the SL continuous LBT failure of the first RB set and also cancels the SL continuous LBT failure of other RB sets on the second SL BWP (which have triggered the SL continuous LBT failure and have not yet canceled the SL continuous LBT failure).

[0240] In some embodiments, after failing to cancel the SL continuous LBT of the third RB set on the second SL BWP, the terminal 101 may determine to resume using resources on the third RB set to receive and / or send SL data. Exemplarily, the SL data may include, but is not limited to, one or more of the following: PSSCH; PSCCH; PSFCH; SSB (Synchronization Signal / PBCH Block).

[0241] Thus, these running timers can be stopped accurately and quickly to cancel the SL continuous LBT failures of these RB sets as soon as possible, so as to resume using the resources on these RB sets to receive and / or send SL data as soon as possible.

[0242] In some embodiments of the present disclosure, terminal 101 determines a MAC entity reset (MAC reset) and stops all running timers. Exemplarily, when terminal 101 determines a MAC entity reconfiguration, for any RB set, if a timer associated with the RB set is running, terminal 101 may stop the timer associated with the RB set.

[0243] In some embodiments of the present disclosure, the terminal 101 determines that the third SL BWP is deactivated, and the timer associated with the fourth RB set is running, and stops the timer associated with the fourth RBset; the fourth RB set is any RB set belonging to the third SLBWP. Exemplarily, the terminal 101 determines that the third SL BWP including the fourth RB set is deactivated. If the timer associated with the fourth RB set is running, the terminal 101 may stop the timer associated with the fourth RBset. Exemplarily, the fourth RB set includes the above-mentioned first RBset. That is, when the terminal 101 determines that a certain SL BWP is deactivated, if the timer associated with the RB set on the SL BWP is running, the terminal 101 may stop these running timers to facilitate the subsequent resumption of use of the corresponding RB set resources.

[0244] In some embodiments of the present disclosure, terminal 101 determines that all RB sets in a resource pool including a first RB set trigger SL continuous LBT failures; terminal 101 clears the selected sidelink granted resources in the resource pool. Exemplarily, if all RB sets in a resource pool trigger SL continuous LBT failures, terminal 101 may clear the selected sidelink granted resources in the resource pool.

[0245] FIG3A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to an information processing method, which can be executed by terminal 101 and may include but is not limited to the following steps.

[0246] Step S3101: Continuous LBT failures of SL are detected on the first RB set, and a timer associated with the first RB set is started.

[0247] In some embodiments, the timer may be used to determine whether the RB set that triggered the SL continuous LBT failure and has not yet canceled the SL continuous LBT failure can cancel the SL continuous LBT failure.

[0248] In some embodiments, the timer may also be called a side link continuous LBT failure recovery timer, or a side link continuous LBT failure cancellation timer, or may be named by other names, which is not limited in this disclosure.

[0249] In some embodiments, the timer associated with the first RB set may be used to enable the terminal to determine whether to cancel the SL continuous LBT failure of the first RB set.

[0250] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0251] Step S3102: A SL continuous LBT failure report is generated or sent. If a timer associated with the first RB set is running, the timer associated with the first RB set is stopped.

[0252] In some embodiments, the SL continuous LBT failure report is used to indicate that at least one RB set triggers SL continuous LBT failure, and the at least one RB set includes the first RB set.

[0253] In some embodiments, the SL continuous LBT failure report can be carried on the MAC CE.

[0254] In some embodiments, the sidelink transmission resource allocation mode of the terminal 101 is the first resource allocation mode (such as the above-mentioned mode1) or the second resource allocation mode (such as the above-mentioned mode2), and the terminal 101 is in the RRC connection state; wherein, the first resource allocation mode is that the network device 102 schedules the sidelink transmission resources; the second resource allocation mode is that the terminal 101 autonomously selects the sidelink transmission resources.

[0255] In some embodiments, after stopping the timer associated with the first RB set, terminal 101 cancels the SL continuous LBT failure of the first RB set. Optionally, after terminal 101 cancels the SL continuous LBT failure of the first RB set, terminal 101 can resume using resources on the first RB set to receive and / or send SL data.

[0256] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0257] The method involved in the embodiment of the present disclosure may include at least one of step S3101 and step S3102. For example, step S3102 may be implemented as an independent embodiment, and step S3101 + step S3102 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0258] In some embodiments, step S3101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0259] Figure 3B is an interactive diagram illustrating an information processing method according to an embodiment of the present disclosure. As shown in Figure 3B, the information processing method according to the embodiment of the present disclosure can be applied to terminal 101, and the method includes but is not limited to the following steps.

[0260] Step S3201: Continuous LBT failures of SL are detected on the first RB set, and a timer associated with the first RB set is started.

[0261] In some embodiments, the timer may be used to determine whether the RB set that triggered the SL continuous LBT failure and has not yet canceled the SL continuous LBT failure can cancel the SL continuous LBT failure.

[0262] In some embodiments, the timer may also be called a side link continuous LBT failure recovery timer, or a side link continuous LBT failure cancellation timer, or may be named by other names, which is not limited in this disclosure.

[0263] In some embodiments, the timer associated with the first RB set may be used to determine whether the first RB set that triggers the SL continuous LBT failure cancels the SL continuous LBT failure.

[0264] In some embodiments, the sidelink transmission resource allocation mode of terminal 101 is the second resource allocation mode, and terminal 101 is in any one of the following states: RRC connected state; RRC idle state; RRC inactive state; OOC (out of coverage) state.

[0265] In some embodiments, the sidelink transmission resource allocation mode of terminal 101 is the first resource allocation mode, and terminal 101 is in an RRC connected state.

[0266] The optional implementation of step S3201 can refer to the optional implementation of step S2201 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0267] Step S3202: It is determined that the SL continuous LBT failure on the first RB set is cancelled, and the timer associated with the first RB set is running, and the timer associated with the first RB set is stopped.

[0268] In some embodiments, after stopping the timer associated with the first RB set, the terminal 101 may determine to resume using resources on the first RB set to receive and / or send SL data.

[0269] The optional implementation of step S3202 can refer to the optional implementation of step S2202 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

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

[0271] In some embodiments, step S3201 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0272] Figure 3C is an interactive diagram illustrating an information processing method according to an embodiment of the present disclosure. As shown in Figure 3C, the information processing method according to the embodiment of the present disclosure can be applied to terminal 101, and the method includes but is not limited to the following steps.

[0273] Step S3301: Determine whether a first parameter corresponding to a first SL BWP including a second RB set is configured or reconfigured.

[0274] In some embodiments, the second RB set is any RB set belonging to the first SL BWP.

[0275] The optional implementation of step S3301 can refer to the optional implementation of step S2302 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

[0276] Step S3302: If it is determined that the timer associated with the second RB set is running, the timer associated with the second RB set is stopped.

[0277] In some embodiments, after stopping the timer associated with the second RB set, the terminal 101 may determine to resume using resources on the second RB set to receive and / or send SL data.

[0278] The optional implementation of step S3302 can refer to the optional implementation of step S2303 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

[0279] Figure 3D is an interactive diagram illustrating an information processing method according to an embodiment of the present disclosure. As shown in Figure 3D, the information processing method according to the embodiment of the present disclosure can be applied to terminal 101, and the method includes but is not limited to the following steps.

[0280] Step S3401: Determine the timer reconfiguration corresponding to the second SL BWP.

[0281] Exemplarily, network device 102 sends timer reconfiguration information to terminal 101, where the timer reconfiguration information includes the timer reconfiguration corresponding to the second SL BWP. When terminal 101 receives the timer reconfiguration information sent by network device 102, terminal 101 can determine the timer reconfiguration corresponding to the second SL BWP.

[0282] In some embodiments, the sidelink transmission resource allocation mode of terminal 101 is the second resource allocation mode, and terminal 101 is in any one of the following states: RRC connected state; RRC idle state; RRC inactive state; OOC (out of coverage) state.

[0283] In some embodiments, the sidelink transmission resource allocation mode of terminal 101 is the first resource allocation mode, and terminal 101 is in an RRC connected state.

[0284] The optional implementation of step S3401 can refer to the optional implementation of step S2402 in Figure 2D and other related parts in the embodiment involved in Figure 2D, which will not be repeated here.

[0285] Step S3402 : canceling the SL continuous LBT failure of the third RB set on the second SL BWP; the third RB set is any RB set belonging to the second SL BWP, which triggers the SL continuous LBT failure and has not been canceled.

[0286] In some embodiments, after canceling the SL continuous LBT failure of the third RB set on the second SL BWP, the terminal 101 may determine to resume using the resources on the third RB set to receive and / or send SL data.

[0287] The optional implementation of step S3402 can refer to the optional implementation of step S2403 in Figure 2D and other related parts in the embodiment involved in Figure 2D, which will not be repeated here.

[0288] Thus, these running timers can be stopped accurately and quickly to cancel the SL continuous LBT failures of these RB sets as soon as possible, so as to resume using the resources on these RB sets to receive and / or send SL data as soon as possible.

[0289] FIG3E is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3E , the embodiment of the present disclosure relates to an information processing method, which can be executed by terminal 101 and may include but is not limited to the following steps.

[0290] Step S3501: Continuous LBT failures of SL are detected on the first RB set, and a timer associated with the first RB set is started.

[0291] In some embodiments, the timer is used to enable the terminal to determine whether to cancel the SL continuous LBT failure of the first RB set.

[0292] The optional implementation of step S3501 can refer to the optional implementation of step S2101 in Figure 2A, step S2201 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0293] Step S3502: During the running of the timer associated with the first RB set, it is determined that the timer associated with the first RB set meets a stop condition, and the timer associated with the first RB set is stopped.

[0294] In some embodiments, the terminal 101 determines that the timer associated with the first RB set meets the stop condition, and stops the timer associated with the first RB set, including: generating or sending an SL continuous LBT failure report, the timer associated with the first RB set is running, and stopping the timer associated with the first RB set; wherein, the SL continuous LBT failure report is used to indicate that at least one RB set triggers SL continuous LBT failure, and the at least one RB set includes the first RB set. wherein, the SL continuous LBT failure report is carried on the media access control MAC control element CE. Its optional implementation method can refer to the optional implementation method of step S2102 of Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0295] In some embodiments, the terminal 101 determines that the timer associated with the first RB set meets a stop condition, and stops the timer associated with the first RB set, including: determining that the SL continuous LBT failure on the first RB set is canceled, and the timer associated with the first RB set is running, and stopping the timer associated with the first RB set. Optional implementations thereof can be found in the optional implementations of step S2202 in FIG. 2B and other related portions of the embodiment involved in FIG. 2B , and are not further described here.

[0296] In some embodiments, the terminal 101 determines that the first parameter is configured or reconfigured, the timer associated with the second RB set is running, and the timer associated with the second RB set is stopped, wherein the first parameter is a SL continuous LBT failure recovery configuration parameter. In some embodiments, the first parameter is configured or reconfigured according to the granularity of the SL bandwidth part BWP; wherein the terminal 101 determines that the first parameter is configured or reconfigured, the timer associated with the second RB set is running, and the timer associated with the second RB set is stopped, including: the terminal 101 determines that the first parameter corresponding to the first SL BWP containing the second RB set is configured or reconfigured, and the timer associated with the second RB set is running; the second RB set is any RB set belonging to the first SL BWP; the terminal 101 stops the timer associated with the second RB set. Its optional implementation method can refer to the optional implementation method of step S2302 of Figure 2C and other associated parts in the embodiment involved in Figure 2C, which will not be repeated here.

[0297] In some embodiments, the terminal 101 determines that the MAC entity is reset and stops all running timers.

[0298] In some embodiments, the terminal 101 determines the timer reconfiguration associated with the third RB set, and cancels the SL continuous LBT failure of the third RB set. In some embodiments, the timer is configured or reconfigured according to the SL BWP granularity; the terminal 101 determines the timer reconfiguration of the third RB set, and cancels the SL continuous LBT failure of the third RB set, including: the terminal 101 determines the timer reconfiguration corresponding to the second SL BWP; the terminal 101 cancels the SL continuous LBT failure of the third RB set on the second SL BWP; the third RB set is any RB set belonging to the second SL BWP, the third RB set triggers the SL continuous LBT failure and the SL continuous LBT failure has not been canceled. Its optional implementation method can refer to the optional implementation method of step S2402 in Figure 2D, and other related parts in the embodiment involved in Figure 2D, which will not be repeated here.

[0299] In some embodiments, the terminal 101 determines that the third SL BWP is deactivated and a timer associated with a fourth RB set is running, and stops the timer associated with the fourth RB set; the fourth RB set is any RB set belonging to the third SL BWP.

[0300] In some embodiments, after stopping the timer associated with the first RB set, it is determined that the terminal 101 resumes using resources on the first RB set to receive and / or send SL data.

[0301] In some embodiments, the terminal 101 determines that all RB sets in the resource pool including the first RB set trigger SL continuous LBT failure; the terminal 101 clears the sidelink granted resources selected in the resource pool.

[0302] Figure 4A is an interactive diagram illustrating an information processing method according to an embodiment of the present disclosure. As shown in Figure 4A, the information processing method according to the embodiment of the present disclosure can be applied to a network device 102, and the method includes but is not limited to the following steps.

[0303] Step S4101, receiving SL continuous LBT failure report.

[0304] In some embodiments, the SL continuous LBT failure report may be sent by the terminal 101. The network device 102 receives the SL continuous LBT failure report sent by the terminal 101.

[0305] In some embodiments, the SL continuous LBT failure report includes an indication of SL continuous LBT failure triggered by at least one RB set, the at least one RB set including the first RB set.

[0306] In some embodiments, the SL continuous LBT failure report may be used by the terminal 101 to determine whether to stop the timer associated with the first RB set during the running of the timer associated with the first RB set.

[0307] In some embodiments, the above-mentioned SL continuous LBT failure report can be carried on MAC CE.

[0308] The optional implementation of step S4101 can refer to the optional implementation of step S2103 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0309] Figure 4B is an interactive diagram illustrating an information processing method according to an embodiment of the present disclosure. As shown in Figure 4B, the information processing method according to an embodiment of the present disclosure can be applied to a network device 102, and the method includes but is not limited to the following steps.

[0310] Step S4201: Send first information to terminal 101.

[0311] In some embodiments, the first information is used by the terminal 101 to determine whether to stop a timer associated with a second RB set, where the second RB set triggers SL continuous LBT failure and the associated timer is running.

[0312] In some embodiments, the first information includes configuration information or reconfiguration information of the first parameter, and the first parameter is a SL continuous LBT failure recovery configuration parameter. The terminal 101 receives the configuration information or reconfiguration information of the first parameter sent by the network device 102, determines that the first parameter is configured or reconfigured, and the timer associated with the second RB set is running, and stops the timer associated with the second RB set. In some embodiments, the first parameter is configured or reconfigured according to the granularity of the SL bandwidth part BWP; wherein, the first information includes the configuration information or reconfiguration information of the first parameter corresponding to the first SL BWP, and the second RB set is any RB set belonging to the first SL BWP. Its optional implementation method can refer to the optional implementation method of the method described on the terminal 101 side above, which will not be repeated here.

[0313] In some embodiments, the first parameter includes at least one of the following: a sidelink continuous LBT failure detection timer; a maximum number of sidelink continuous LBT failures; and the timer.

[0314] The optional implementation of step S4201 can refer to the optional implementation of step S2301 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

[0315] Figure 4C is an interactive diagram illustrating an information processing method according to an embodiment of the present disclosure. As shown in Figure 4C, the information processing method according to an embodiment of the present disclosure can be applied to a network device 102, and the method includes but is not limited to the following steps.

[0316] Step S4301: Send timer reconfiguration information to terminal 101.

[0317] In some embodiments, the reconfiguration information of the timer is used by the terminal 101 to determine whether to cancel the SL continuous LBT failure of the third RB set, wherein the third RB set triggers the SL continuous LBT failure and the SL continuous LBT failure has not been canceled, and the timer is used to determine whether the third RB set that triggers the SL continuous LBT failure cancels the SL continuous LBT failure.

[0318] In some embodiments, the timer is configured or reconfigured according to the SLBWP granularity; the reconfiguration information of the timer includes the timer reconfiguration corresponding to the second SL BWP, and the third RB set is any RB set belonging to the second SL BWP.

[0319] The optional implementation of step S4301 can refer to the optional implementation of step S2401 in Figure 2D and other related parts in the embodiment involved in Figure 2D, which will not be repeated here.

[0320] The present disclosure also provides an information processing method applicable to a communication system 100, which may include a terminal 101 and a network device 102. Terminal 101 may execute the information processing method described in any of the aforementioned terminal-side embodiments; network device 102 may execute the information processing method described in any of the aforementioned network-side embodiments. In other words, the aforementioned method may include the methods described in the aforementioned terminal-side and network-side embodiments, and will not be further elaborated here.

[0321] The embodiments of the present disclosure provide a method for processing a timer (also referred to as a sidelink continuous LBT failure recovery timer), which can solve the problem of whether the sidelink continuous LBT failure recovery timer is applicable to a terminal operating in mode 1, the configuration granularity, the stop condition, etc. In some embodiments, the sidelink continuous LBT failure recovery timer is configured according to the SLBWP granularity, and the terminal cancels the SL continuous LBT failure that was triggered by the RB set and not canceled when the timer is reconfigured.

[0322] For example, a terminal in an RRC connected state can obtain the timer configuration through dedicated signaling, a terminal in an RRC IDLE / INACTIVE state can obtain the timer configuration through SIB, and a terminal in an OOC (out of coverage) state can obtain the timer configuration through pre-configuration. The timer configuration is configured according to the BWP granularity. Different BWPs can be configured with the same or different timers (the timer lengths can be the same or different). The timer is maintained according to the RB set granularity.

[0323] Exemplarily, the timer is reconfigured, and the terminal cancels the SL continuous LBT failure of the RB set that triggered the SL continuous LBT failure and was not canceled on the BWP.

[0324] Exemplarily, the sidelink continuous LBT failure recovery timer may only apply to terminals running in mode 2, and the terminals may be in the RRC CONNECTED / IDLE / INACTIVE / OOC state. The sidelink continuous LBT failure recovery timer may only apply to terminals running in mode 2, and the terminals may be in the RRC IDLE / INACTIVE / OOC state.

[0325] Exemplarily, the sidelink continuous LBT failure recovery timer can be applicable to terminals running in mode 2, and the terminal can be in the RRC CONNECTED / IDLE / INACTIVE / OOC state, or the sidelink continuous LBT failure recovery timer can be applicable to terminals running in mode 2, and the terminal can be in the RRC IDLE / INACTIVE / OOC state; and also applicable to terminals running in mode 1, and the terminal is in the RRC CONNECTED state.

[0326] In some embodiments, the terminal reports a SL continuous LBT failure report, and if the sidelink continuous LBT failure recovery timer is running, the sidelink continuous LBT failure recovery timer is stopped.

[0327] Exemplarily, the terminal sends a MAC PDU that includes a SL continuous LBT failure report, specifically, a SL continuous LBT failure MAC CE. For the RB set that triggers the SL continuous LBT failure indicated in the MAC CE, if the sidelink continuous LBT failure recovery timer associated with the RB set is running, the sidelink continuous LBT failure recovery timer associated with the RB set is stopped. The RB set is the RB set that triggers the SL continuous LBT failure indicated in the MAC CE, which can be one or more.

[0328] Exemplarily, if the sidelink continuous LBT failure recovery timer can only be applied to the terminal running in mode 2, the terminal is in the RRC CONNECTED state and runs in mode 2.

[0329] Exemplarily, if the sidelink continuous LBT failure recovery timer is applicable to both terminals running in mode 2 and terminals running in mode 1, and the terminal is in the RRC CONNECTED state, the terminal can run in mode 2 or mode 1.

[0330] For example, as an extension of the solution, if the terminal cancels the SL continuous LBT failure of the RB set through other means, if the sidelink continuous LBT failure recovery timer associated with the RB set is running, the sidelink continuous LBT failure recovery timer associated with the RB set is stopped. This disclosure does not make specific limitations.

[0331] In some embodiments, SL continuous LBT failure recovery (such as SL continuous LBT failure recovery parameters) is configured or reconfigured, and if the side link continuous LBT failure recovery timer is running, the side link continuous LBT failure recovery timer is stopped.

[0332] Exemplarily, SL continuous LBT failure recovery can be sl-LBT-FailureRecoveryConfig, or other names, which are not specifically limited in this disclosure. When this parameter is configured or reconfigured, if the side link continuous LBT failure recovery timer associated with the RB set on the BWP is running, stop the side link continuous LBT failure recovery timer associated with the RB set on the BWP. Exemplarily, sl-LBT-FailureRecoveryConfig is configured or reconfigured according to the BWP granularity. When sl-LBT-FailureRecoveryConfig is configured or reconfigured, stop the side link continuous LBT failure recovery timer associated with the RB set on the BWP (if the timer is running).

[0333] In some embodiments, the terminal determines a MAC reset (MAC reset), and if the sidelink continuous LBT failure recovery timer is running, the terminal stops the sidelink continuous LBT failure recovery timer.

[0334] Exemplarily, MAC reset: for any RB set, if the sidelink continuous LBT failure recovery timer associated with the RB set is running, the terminal stops the sidelink continuous LBT failure recovery timer associated with the RB set.

[0335] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided that includes units or modules for implementing each step performed by a network device in any of the above methods.

[0336] 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.

[0337] In the embodiments of the present disclosure, the processor is a circuit with information 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.

[0338] Figure 5A is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. As shown in Figure 5A, terminal 5100 may include at least one of a transceiver module 5101 and a processing module 5102. In some embodiments, the processing module is configured to detect a continuous listen-before-talk (LBT) failure in a sidelink (SL) on a first resource block set (RB set) and start a timer associated with the first RB set; the timer is configured to enable the terminal to determine whether to cancel the continuous LBT failure for the first RB set; and the processing module is further configured to determine, during the operation of the timer associated with the first RB set, that the timer associated with the first RB set meets a stop condition and stop the timer associated with the first RB set.

[0339] In some embodiments, the transceiver module generates or sends a SL continuous LBT failure report; the processing module determines that a timer associated with the first RB set is running, and stops the timer associated with the first RB set; wherein the SL continuous LBT failure report is used to indicate that at least one RB set triggers a SL continuous LBT failure, and the at least one RB set includes the first RB set. The SL continuous LBT failure report is carried on a media access control MAC control element CE.

[0340] In some embodiments, the sidelink transmission resource allocation mode of the terminal is a first resource allocation mode or a second resource allocation mode, and the terminal is in a radio resource control RRC connection state; wherein, the first resource allocation mode is that the network device schedules the sidelink transmission resources; the second resource allocation mode is that the terminal autonomously selects the sidelink transmission resources.

[0341] In some embodiments, the processing module determines that the SL continuous LBT failure on the first RB set is canceled, and a timer associated with the first RB set is running, and stops the timer associated with the first RB set.

[0342] In some embodiments, the processing module determines that a first parameter is configured or reconfigured and a timer associated with a second RB set is running, and stops the timer associated with the second RB set, wherein the first parameter is a SL continuous LBT failure recovery configuration parameter. The optional first parameter includes at least one of the following: a sidelink continuous LBT failure detection timer; a maximum number of sidelink continuous LBT failures; and a timer associated with the first RB set or the second RB set (also referred to as a sidelink continuous LBT failure recovery timer).

[0343] In some embodiments, the first parameter is configured or reconfigured according to the granularity of the SL bandwidth part BWP; wherein the processing module determines that the first parameter corresponding to the first SL BWP including the second RB set is configured or reconfigured, and the timer associated with the second RB set is running; the second RB set is any RB set belonging to the first SL BWP; the processing module stops the timer associated with the second RB set.

[0344] In some embodiments, the processing module determines that a media access control (MAC) entity is reset and stops all running timers.

[0345] In some embodiments, the processing module determines that a timer associated with the third RB set is to be reconfigured, and cancels the SL continuous LBT failure of the third RB set.

[0346] In some embodiments, the timer is configured or reconfigured according to the SL BWP granularity; the processing module is specifically used to: determine the timer reconfiguration corresponding to the second SL BWP; cancel the SL continuous LBT failure of the third RB set on the second SL BWP; the third RB set is any RB set belonging to the second SL BWP, the third RB set triggers the SL continuous LBT failure and the SL continuous LBT failure has not been canceled.

[0347] In some embodiments, the processing module determines that the third SL BWP is deactivated and a timer associated with a fourth RB set is running, and stops the timer associated with the fourth RB set; the fourth RB set is any RB set belonging to the third SLBWP.

[0348] In some embodiments, after stopping the timer associated with the first RB set, the processing module determines that the terminal resumes using resources on the first RB set to receive and / or send SL data.

[0349] In some embodiments, the processing module determines that all RB sets in the resource pool including the first RB set trigger SL continuous LBT failure, and the terminal clears the sidelink authorized resources selected in the resource pool.

[0350] In some embodiments, the sidelink transmission resource allocation mode of the terminal is the second resource allocation mode, and the terminal is in any one of the following states: RRC connected state; RRC idle state; RRC inactive state; out-of-coverage OOC state.

[0351] In some embodiments, the sidelink transmission resource allocation mode of the terminal is the first resource allocation mode, and the terminal is in an RRC connected state.

[0352] Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal 101 in any of the above methods, which will not be repeated here. Optionally, the processing module is used to perform at least one of the other steps (such as step S2101, step S2102, step S2201, step S2202, step S2302, step S2303, step S2402, step S2403, but not limited to these) performed by the terminal device 101 in any of the above methods, which will not be repeated here.

[0353] FIG5B is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure. As shown in FIG5B , network device 5200 may include at least one of a transceiver module 5201 and a processing module 5202. In some embodiments, the transceiver module is configured to receive a sidelink (SL) continuous listen-before-talk (LBT) failure report sent by a terminal; the SL continuous LBT failure report includes an indication of SL continuous LBT failure triggered by at least one resource block set (RB) set, wherein the at least one RB set includes a first RB set, and the SL continuous LBT failure report is used by the terminal to determine whether to stop the timer associated with the first RB set during the operation of the timer associated with the first RB set.

[0354] In some embodiments, the SL continuous LBT failure report is carried on the media access control MAC control element CE.

[0355] In some embodiments, the transceiver module is configured to send first information to a terminal; the first information is used by the terminal to determine whether to stop a timer associated with a second resource block set (RB set), where the second RB set triggers a sidelink (SL) continuous listen-before-talk (LBT) failure and the associated timer is running. The first information includes configuration information or reconfiguration information of a first parameter, where the first parameter is a SL continuous LBT failure recovery configuration parameter.

[0356] In some embodiments, the first parameter includes at least one of the following: a sidelink continuous LBT failure detection timer; a maximum number of sidelink continuous LBT failures; a timer.

[0357] In some embodiments, the first parameter is configured or reconfigured according to the granularity of the SL bandwidth part BWP; wherein the first information includes configuration information or reconfiguration information of the first parameter corresponding to the first SL BWP, and the second RB set is any RB set belonging to the first SL BWP.

[0358] In some embodiments, the above-mentioned transceiver module is used to send timer reconfiguration information to the terminal; the timer reconfiguration information is used by the terminal to determine whether to cancel the side link SL continuous listen-before-talk LBT failure of the third resource block set RB set, wherein the third RB set triggers the side link SL continuous listen-before-talk LBT failure and the SL continuous LBT failure has not been canceled, and the timer is used to enable the terminal to determine whether to cancel the SL continuous LBT failure of the third RB set.

[0359] In some embodiments, the timer is configured or reconfigured according to the granularity of the SL bandwidth part BWP; the reconfiguration information of the timer includes the timer reconfiguration corresponding to the second SL BWP, and the third RB set is any RB set belonging to the second SL BWP.

[0360] Optionally, the transceiver module is configured to execute at least one of the communication steps (e.g., step S2103, step S2301, and step S2401, but not limited thereto) such as sending and / or receiving performed by the network device 102 in any of the above methods, which are not described in detail here. Optionally, the processing module is configured to execute at least one of the other steps performed by the network device 102 in any of the above methods, which are not described in detail here.

[0361] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0362] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0363] Figure 6A is a schematic diagram of the structure of a communication device 6100 proposed in an embodiment of the present disclosure. Communication device 6100 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 6100 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.

[0364] As shown in Figure 6A, the communication device 6100 includes one or more processors 6101. The processor 6101 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 the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to perform any of the above methods. Optionally, one or more processors 6101 are used to call instructions to enable the communication device 6100 to perform any of the above methods.

[0365] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps (e.g., step S2103, step S2301, step S2401, but not limited thereto) of sending and / or receiving in the above method, and the processor 6101 performs at least one of the other steps (e.g., step S2101, step S2102, step S2201, step S2202, step S2302, step S2303, step S2402, step S2403, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be replaced with each other, terms such as transmitter, transmitting unit, transmitter, and transmitting circuit can be replaced with each other, and terms such as receiver, receiving unit, receiver, and receiving circuit can be replaced with each other.

[0366] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Alternatively, all or part of the memories 6103 may be located outside the communication device 6100. In alternative embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuits 6104 are connected to the memory 6102 and may be configured to receive data from the memory 6102 or other devices, or to send data to the memory 6102 or other devices. For example, the interface circuits 6104 may read data stored in the memory 6102 and send the data to the processor 6101.

[0367] The communication device 6100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited to FIG6A. 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 and 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.

[0368] 6B is a schematic diagram of the structure of a chip 6200 according to an embodiment of the present disclosure. If the communication device 6100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 6200 shown in FIG6B , but the present disclosure is not limited thereto.

[0369] The chip 6200 includes one or more processors 6201. The chip 6200 is configured to execute any of the above methods.

[0370] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data. Alternatively, all or part of memory 6203 may be located external to chip 6200. Optionally, interface circuit 6202 is connected to memory 6203 and may be used to receive data from memory 6203 or other devices, or may be used to send data to memory 6203 or other devices. For example, interface circuit 6202 may read data stored in memory 6203 and send the data to processor 6201.

[0371] In some embodiments, the interface circuit 6202 performs at least one of the communication steps (e.g., step S2103, step S2301, and step S2401) of the above-described method. The interface circuit 6202 performing the communication steps (e.g., step S2103, step S2301, and step S2401) of the above-described method, for example, means that the interface circuit 6202 performs data exchange between the processor 6201, chip 6200, memory 6203, or transceiver device. In some embodiments, the processor 6201 performs at least one of the other steps (e.g., step S2101, step S2102, step S2201, step S2202, step S2302, step S2303, step S2402, and step S2403, but not limited thereto).

[0372] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 6100, the communication device 6100 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 transient storage medium.

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

[0374] 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.

[0375] 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)).

[0376] 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.

[0377] 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.

[0378] 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. An information processing method, characterized in that: include: The terminal detects a side link SL continuous listen-before-talk LBT failure on a first resource block set RB set, and starts a timer associated with the first RB set; wherein the timer is used to enable the terminal to determine whether to cancel the SL continuous LBT failure of the first RB set; During the running of the timer associated with the first RB set, the terminal determines that the timer associated with the first RB set meets a stop condition, and stops the timer associated with the first RB set.

2. The method according to claim 1, characterized in that The terminal determines that the timer associated with the first RB set meets a stop condition, and stops the timer associated with the first RB set, including: The terminal generates or sends a SL continuous LBT failure report, the timer associated with the first RB set is running, and the timer associated with the first RB set is stopped; wherein the SL continuous LBT failure report is used to indicate that at least one RB set triggers the SL continuous LBT failure, and the at least one RB set includes the first RB set.

3. The method according to claim 2, characterized in that The SL continuous LBT failure report is carried on the media access control MAC control element CE.

4. The method according to claim 2 or 3, characterized in that The sidelink transmission resource allocation mode of the terminal is the first resource allocation mode or the second resource allocation mode, and the terminal is in a radio resource control RRC connected state; Among them, the first resource allocation method is that the network device schedules the sidelink transmission resources; the second resource allocation method is that the terminal autonomously selects the sidelink transmission resources.

5. The method according to claim 1, characterized in that The terminal determines that the timer associated with the first RB set meets a stop condition, and stops the timer associated with the first RB set, including: The terminal determines that the SL continuous LBT failure on the first RB set is cancelled, a timer associated with the first RB set is running, and stops the timer associated with the first RB set.

6. The method according to claim 1, characterized in that The method further comprises: The terminal determines that a first parameter is configured or reconfigured, a timer associated with a second RB set is running, and stops the timer associated with the second RBset, wherein the first parameter is an SL continuous LBT failure recovery configuration parameter.

7. The method according to claim 6, characterized in that The first parameter includes at least one of the following: Sidelink continuous LBT failure detection timer; Maximum number of consecutive LBT failures in the sidelink; A timer associated with the first RB set or the second RB set.

8. The method according to claim 6 or 7, characterized in that The first parameter is configured or reconfigured according to the SL bandwidth part BWP granularity; The terminal determines that the first parameter is configured or reconfigured, and a timer associated with the second RB set is running, and stops the timer associated with the second RB set, including: The terminal determines that the first parameter corresponding to the first SL BWP including the second RB set is configured or reconfigured, and a timer associated with the second RB set is running; the second RB set is any RB set belonging to the first SL BWP; The terminal stops a timer associated with the second RB set.

9. The method according to claim 1, characterized in that The method further comprises: The terminal determines that the media access control MAC entity is reset and stops all the timers that are running.

10. The method according to claim 1, characterized in that The method further comprises: The terminal determines that the timer associated with the third RB set is reconfigured, and cancels the SL continuous LBT failure of the third RB set.

11. The method according to claim 10, characterized in that The timer is configured or reconfigured according to the SL BWP granularity; the terminal determines the timer reconfiguration associated with the third RB set, and cancels the SL continuous LBT failure of the third RB set, including: The terminal determines a timer reconfiguration corresponding to the second SL BWP; The terminal cancels the SL continuous LBT failure of the third RB set on the second SL BWP; the third RB set is any RB set belonging to the second SL BWP, the third RB set triggers the SL continuous LBT failure and the SL continuous LBT failure has not been canceled.

12. The method according to claim 1, characterized in that The method further comprises: The terminal determines that the third SL BWP is deactivated, and a timer associated with a fourth RB set is running, and stops the timer associated with the fourth RB set; the fourth RB set is any RB set belonging to the third SL BWP.

13. The method according to any one of claims 1 to 12, characterized in that The method further comprises: After stopping the timer associated with the first RB set, it is determined that the terminal resumes using resources on the first RB set to receive and / or send SL data.

14. The method according to claim 1, wherein: The method further comprises: The terminal determines that all RB sets in the resource pool including the first RB set trigger the SL continuous LBT failure; The terminal clears the sidelink granted resources selected in the resource pool.

15. The method according to any one of claims 5 to 14, characterized in that The sidelink transmission resource allocation mode of the terminal is the second resource allocation mode, and the terminal is in any of the following states: RRC connection state; RRC idle state; RRC inactive state; Out of coverage, OOC state.

16. The method according to any one of claims 5 to 13, characterized in that: The sidelink transmission resource allocation mode of the terminal is a first resource allocation mode, and the terminal is in an RRC connected state.

17. An information processing method, characterized in that: include: A network device receives a side link SL continuous listen-before-talk LBT failure report sent by a terminal; wherein the SL continuous LBT failure report includes an indication of SL continuous LBT failure triggered by at least one resource block set RB set, the at least one RB set includes a first RB set, and the SL continuous LBT failure report is used by the terminal to determine whether to stop the timer associated with the first RB set during the operation of the timer associated with the first RB set.

18. The method according to claim 17, characterized in that The SL continuous LBT failure report is carried on the media access control MAC control element CE.

19. An information processing method, characterized in that: include: The network device sends first information to the terminal; The first information is used by the terminal to determine whether to stop a timer associated with a second resource block set RB set, wherein the second RB set triggers a sidelink SL continuous listen-before-talk LBT failure and the associated timer is running.

20. The method of claim 19, wherein: The first information includes configuration information or reconfiguration information of a first parameter, and the first parameter is a SL continuous LBT failure recovery configuration parameter.

21. The method according to claim 20, characterized in that The first parameter includes at least one of the following: Sidelink continuous LBT failure detection timer; Maximum number of consecutive LBT failures in the sidelink; A timer associated with the second RB set.

22. The method according to claim 20 or 21, characterized in that The first parameter is configured or reconfigured according to the granularity of the SL bandwidth part BWP; wherein, the first information includes configuration information or reconfiguration information of the first parameter corresponding to the first SL BWP, and the second RB set is any RB set belonging to the first SL BWP.

23. An information processing method, characterized in that: include: The network device sends timer reconfiguration information to the terminal; The reconfiguration information of the timer is used by the terminal to determine whether to cancel the side link SL continuous listen-before-talk LBT failure of the third resource block set RB set, wherein the third RB set triggers the side link SL continuous listen-before-talk LBT failure and the SL continuous LBT failure has not been canceled, and the timer is used to enable the terminal to determine whether to cancel the SL continuous LBT failure of the third RB set.

24. The method of claim 23, wherein: The timer is configured or reconfigured according to the SL bandwidth part BWP granularity; the reconfiguration information of the timer includes the timer reconfiguration corresponding to the second SL BWP, and the third RB set is any RB set belonging to the second SL BWP.

25. A first communication device, characterized in that: include: A processing module, configured to detect a side link SL continuous listen-before-talk LBT failure on a first resource block set RB set, and start a timer associated with the first RB set; wherein the timer is used to enable the terminal to determine whether to cancel the SL continuous LBT failure of the first RB set; The processing module is further configured to determine, during the running period of the timer associated with the first RB set, that the timer associated with the first RB set meets a stop condition, and stop the timer associated with the first RB set.

26. A second communication device, characterized in that: include: A transceiver module is used to receive a side link SL continuous listen-before-talk LBT failure report sent by a terminal; wherein the SL continuous LBT failure report includes an indication of SL continuous LBT failure triggered by at least one resource block set RB set, the at least one RB set includes a first RB set, and the SL continuous LBT failure report is used by the terminal to determine whether to stop the timer associated with the first RB set during the operation of the timer associated with the first RB set.

27. A second communication device, characterized in that: include: A transceiver module, used for sending first information to a terminal; The first information is used by the terminal to determine whether to stop a timer associated with a second resource block set RB set, wherein the second RB set triggers a sidelink SL continuous listen-before-talk LBT failure and the associated timer is running.

28. A second communication device, characterized in that: include: A transceiver module, used for sending timer reconfiguration information to the terminal; The reconfiguration information of the timer is used by the terminal to determine whether to cancel the side link SL continuous listen-before-talk LBT failure of the third resource block set RB set, wherein the third RB set triggers the side link SL continuous listen-before-talk LBT failure and the SL continuous LBT failure has not been canceled, and the timer is used to enable the terminal to determine whether to cancel the SL continuous LBT failure of the third RB set.

29. A communication system, characterized in that: include: A terminal, configured to execute the information processing method according to any one of claims 1 to 16; A network device, configured to execute the information processing method according to any one of claims 17 to 24.

30. A communication device, characterized in that: include: one or more processors; The processor is used to call instructions so that the communication device executes the information processing method described in any one of claims 1-16 and 17-24.

31. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device executes the information processing method according to any one of claims 1 to 16 and 17 to 24.

Images