Continuous lbt failure handling method and apparatus, terminal and network-side device

Abstract

The application discloses a continuous LBT failure processing method and device, a terminal and a network side equipment, and belongs to the technical field of communication. The continuous LBT failure processing method comprises the following steps: in the case that continuous LBT failure occurs on an unlicensed frequency band, a first terminal performs a first failure processing operation. The first failure processing operation comprises at least one of the following: performing an SL RLF operation on an SL corresponding to the unlicensed frequency band; reporting the continuous LBT failure to a network side equipment; suspending the SL corresponding to the unlicensed frequency band; and performing SL transmission on a resource of a licensed frequency band.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a method and apparatus for handling continuous listen-before-talk (LBT) failures, as well as a terminal and network-side equipment. Background Technology

[0002] Sidelink (SL) communication is direct communication between terminals without going through network-side devices.

[0003] In existing technology, terminals can conduct SL communication via unlicensed bands (UB). Before sending a message using a particular unlicensed band, a terminal needs to perform a Level Bypass (LBT) check on that unlicensed band to detect whether it is occupied. If the LBT result indicates that the unlicensed band is occupied, it is recorded as an LBT failure. If consecutive LBT failures occur for that unlicensed band within a certain period of time, it indicates that the unlicensed band is unavailable.

[0004] Currently, there is no solution for consecutive LBT failures when conducting SL communication via unlicensed frequency bands. Therefore, how to handle consecutive LBT failures in SL communication has become an urgent problem to be solved. Summary of the Invention

[0005] This application provides a method, apparatus, terminal, and network-side device for handling continuous LBT failures, which can solve the problem of continuous LBT failures in SL communication.

[0006] In a first aspect, a method for handling consecutive LBT failures is provided, the method comprising: in the event of consecutive LBT failures occurring on an unlicensed frequency band, a first terminal performing a first failure handling operation.

[0007] The first failure handling operation includes at least one of the following:

[0008] Perform an SL RLF operation on the SL corresponding to the unlicensed frequency band;

[0009] Report the continuous LBT failures to the network-side device;

[0010] Suspend the SL corresponding to the unlicensed frequency band;

[0011] SL transmission is performed on resources within the licensed frequency band.

[0012] Secondly, a method for handling continuous LBT failures is provided, the method comprising: a network-side device configuring first information for a first terminal, the first information being used to indicate a first failure handling operation to be performed in the event of continuous LBT failures occurring on an unlicensed frequency band.

[0013] The first failure handling operation includes at least one of the following:

[0014] Perform an SL RLF operation on the SL corresponding to the unlicensed frequency band;

[0015] Report the continuous LBT failures to the network-side device;

[0016] Suspend the SL corresponding to the unlicensed frequency band;

[0017] SL transmission is performed on resources within the licensed frequency band.

[0018] Thirdly, a method for handling continuous LBT failures is provided, the method comprising: when it is determined that a first terminal has experienced continuous LBT failures on an unlicensed frequency band, a second terminal performs a second failure handling operation, wherein the first terminal is a terminal that has established a side link (SL) with the second terminal.

[0019] The second failure handling operation includes any one of the following:

[0020] Suspend the SL connection with the first terminal;

[0021] Data is transmitted with the first terminal using a method that disables HARQ feedback.

[0022] Release the SL between the first terminal.

[0023] Fourthly, a continuous LBT failure handling apparatus is provided, the apparatus including a processing module. The processing module is used to perform a first failure handling operation in the event of continuous LBT failures occurring on an unlicensed frequency band.

[0024] The first failure handling operation includes at least one of the following:

[0025] Perform an SL RLF operation on the SL corresponding to the unlicensed frequency band;

[0026] Report the continuous LBT failures to the network-side device;

[0027] Suspend the SL corresponding to the unlicensed frequency band;

[0028] SL transmission is performed on resources within the licensed frequency band.

[0029] Fifthly, a continuous LBT failure handling apparatus is provided, the apparatus including a configuration module. The configuration module is used to configure first information for a first terminal, the first information indicating a first failure handling operation to be performed in the event of continuous LBT failures occurring on an unlicensed frequency band.

[0030] The first failure handling operation includes at least one of the following:

[0031] Perform an SL RLF operation on the SL corresponding to the unlicensed frequency band;

[0032] Report the continuous LBT failures to the network-side device;

[0033] Suspend the SL corresponding to the unlicensed frequency band;

[0034] SL transmission is performed on resources within the licensed frequency band.

[0035] Sixthly, a continuous LBT failure handling apparatus includes a processing module. The processing module is configured to perform a second failure handling operation upon determining that a first terminal has experienced continuous LBT failures on an unlicensed frequency band, wherein the first terminal is a terminal with which a sidelink (SL) has been established with the second terminal.

[0036] The second failure handling operation includes any one of the following:

[0037] Suspend the SL connection with the first terminal;

[0038] Data is transmitted with the first terminal using a method that disables HARQ feedback.

[0039] Release the SL between the first terminal.

[0040] In a seventh aspect, a first terminal is provided, the first terminal including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the first aspect.

[0041] Eighthly, a network-side device is provided, the network-side device including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method as described in the second aspect.

[0042] In a ninth aspect, a second terminal is provided, the second terminal including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the third aspect.

[0043] In a tenth aspect, a first terminal is provided, the first terminal including a processor. The processor is configured to perform a first failure handling operation in the event that the first terminal experiences consecutive LBT failures on an unlicensed frequency band.

[0044] The first failure handling operation includes at least one of the following:

[0045] Perform an SL RLF operation on the SL corresponding to the unlicensed frequency band;

[0046] Report the continuous LBT failures to the network-side device;

[0047] Suspend the SL corresponding to the unlicensed frequency band;

[0048] SL transmission is performed on resources within the licensed frequency band.

[0049] Eleventhly, a network-side device is provided, comprising a processor. The processor is configured to configure first information for a first terminal, the first information indicating a first failure handling operation to be performed in the event of consecutive LBT failures occurring on an unlicensed frequency band.

[0050] The first failure handling operation includes at least one of the following:

[0051] Perform an SL RLF operation on the SL corresponding to the unlicensed frequency band;

[0052] Report the continuous LBT failures to the network-side device;

[0053] Suspend the SL corresponding to the unlicensed frequency band;

[0054] SL transmission is performed on resources within the licensed frequency band.

[0055] In a twelfth aspect, a second terminal is provided, the second terminal including a processor. The processor is configured to perform a second failure handling operation upon determining that a first terminal has experienced consecutive LBT failures on an unlicensed frequency band, the first terminal being a terminal with which an LBT has been established with the second terminal.

[0056] The second failure handling operation includes any one of the following:

[0057] Suspend the SL connection with the first terminal;

[0058] Data is transmitted with the first terminal using a method that disables HARQ feedback.

[0059] Release the SL between the first terminal.

[0060] In a thirteenth aspect, a first terminal is provided, the terminal including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the first aspect.

[0061] In a fourteenth aspect, a network-side device is provided, the network-side device including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method as described in the second aspect.

[0062] In a fifteenth aspect, a second terminal is provided, the terminal including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the third aspect.

[0063] In a sixteenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect.

[0064] In a seventeenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the method as described in the first aspect, or the method as described in the second aspect, or the method as described in the third aspect.

[0065] Eighteenthly, a computer program / program product is provided, the computer program / program product being stored in a non-volatile storage medium, the program / program product being executed by at least one processor to implement the steps of the continuous LBT failure handling method as described in the first aspect, or the steps of the continuous LBT failure handling method as described in the second aspect, or the steps of the continuous LBT failure handling method as described in the third aspect.

[0066] In this embodiment, in the event of consecutive LBT failures on an unlicensed frequency band, the first terminal performs a first failure handling operation. This scheme allows the first terminal to handle consecutive LBT failures during SL communication by performing the first failure handling operation. Thus, it avoids situations where the terminal (e.g., the local terminal) is unable to handle consecutive LBT failures during SL communication via unlicensed frequency bands.

[0067] Furthermore, in the event of consecutive LBT failures occurring on an unlicensed frequency band by the first terminal, the second terminal performs a second failure handling operation. This scheme allows the second terminal to handle consecutive LBT failures during SL communication, as the second terminal can perform the second failure handling operation when the first terminal experiences consecutive LBT failures on an unlicensed frequency band. This avoids situations where a terminal (e.g., the peer terminal) is unable to handle consecutive LBT failures during SL communication via unlicensed frequency bands. Attached Figure Description

[0068] Figure 1 This is a schematic diagram of the structure of the wireless communication system provided in the embodiments of this application;

[0069] Figure 2 This is one of the flowcharts illustrating the continuous LBT failure handling method provided in the embodiments of this application;

[0070] Figure 3 This is a second flowchart illustrating the continuous LBT failure handling method provided in the embodiments of this application;

[0071] Figure 4 This is the third flowchart of the continuous LBT failure handling method provided in the embodiments of this application;

[0072] Figure 5 This is the fourth flowchart of the continuous LBT failure handling method provided in the embodiments of this application;

[0073] Figure 6 This is one of the structural schematic diagrams of the continuous LBT failure processing device provided in the embodiments of this application;

[0074] Figure 7 This is a second schematic diagram of the continuous LBT failure processing device provided in the embodiments of this application;

[0075] Figure 8 This is the third schematic diagram of the continuous LBT failure processing device provided in the embodiments of this application;

[0076] Figure 9 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application;

[0077] Figure 10 This is a schematic diagram of the terminal structure provided in the embodiments of this application;

[0078] Figure 11 This is a schematic diagram of the network-side device provided in the embodiments of this application. Detailed Implementation

[0079] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0080] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0081] In the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0082] To facilitate understanding, a brief introduction will first be given to the wireless communication systems to which the embodiments of this application can be applied and the related concepts involved in the embodiments of this application:

[0083] Figure 1 An example of a wireless communication system 10 applicable to embodiments of this application is shown. For example... Figure 1 As shown, the wireless communication system 10 includes a network-side device 12 and multiple terminals 11. A communication link can be established between the terminals 11 and the network-side device 12 for data transmission. The link through which the terminals 11 send data to the network-side device 12 is called the uplink (UL) link, and the link through which the network-side device 12 sends data to the terminals 11 is called the downlink (DL) link.

[0084] In addition, Figure 1In the wireless communication system shown, communication links can also be established between terminals 11, which are called sidelinks (SL). The sidelinks between terminals 11 mainly include three transmission methods: unicast transmission, broadcast transmission, and multicast transmission. Unicast transmission can be communication between a sending terminal and a receiving terminal, such as... Figure 1 As shown. Multicast transmission can be communication between a sending terminal and a group of receiving terminals. Broadcast transmission can be communication between a sending terminal and multiple receiving terminals. For ease of description, in this embodiment, the sending terminal is referred to as the first terminal, and the receiving terminal is referred to as the second terminal. For example, as... Figure 1 As shown in the figure, terminal 11A is the first terminal, and terminal 11B is the second terminal.

[0085] It should be noted that the continuous LBT failure handling method provided in this application embodiment is applicable to all three transmission methods mentioned above. It can be understood that in broadcast and multicast transmission scenarios, there are multiple second terminals.

[0086] It is worth pointing out that, Figure 1 The wireless communication system 10 shown can be applied to various communication systems, such as Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-carrier Frequency-Division Multiple Access (SC-FDMA) systems, 5th generation (5G) systems, New Radio (NR) systems, or other future networks, such as 6th generation (6G) communication systems. This application embodiment does not specifically limit these applications. Furthermore, the terms "system" and "network" in this application embodiment are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies.

[0087] The terminal 11 in the aforementioned wireless communication system 10 can be a mobile phone, tablet computer, laptop computer (also known as a notebook computer), personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines, or furniture), etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, game consoles, etc. It should be noted that the specific type of terminal 11 is not limited in this embodiment.

[0088] In the aforementioned wireless communication system 10, the network-side device 12 can be a base station or a core network. The base station can be referred to as a Node B, Evolved Node B, Access Point, Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), B Node, Evolved B Node (eNB), Next Generation Node B (gNB), Home B Node, Home Evolved B Node, WLAN Access Point, WiFi Node, Transmitting Receiving Point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that this application embodiment only uses a base station in an NR system as an example, but does not limit the specific type of base station.

[0089] For example, with Figure 1 Taking the wireless communication system 10 shown as an example applied to the current NR system, the network element or entity corresponding to the terminal 11 can be a terminal in the NR system, and the network element or entity corresponding to the network-side device 12 can be a gNB in ​​the NR system.

[0090] The continuous LBT failure handling method provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0091] It should be noted that the message names between network elements or the names of parameters in the messages in the following embodiments of this application are just examples. In specific implementations, they may be other names, and this application does not specifically limit them.

[0092] Figure 2 The illustration shows a continuous LBT failure handling method provided in an embodiment of this application. This method can be applied to... Figure 1 The wireless communication system 10 shown may include the following step 201.

[0093] Step 201: In the event of consecutive LBT failures on an unlicensed frequency band, the first terminal 11A performs the first failure handling operation.

[0094] It is understandable that when the first terminal 11A and the second terminal 11B are communicating via an unlicensed frequency band, before the first terminal 11A sends data to the second terminal 11B via the unlicensed frequency band, it can perform a Level Bypass (LBT) on that unlicensed frequency band to check whether the unlicensed frequency band is occupied. If consecutive LBT failures occur on the unlicensed frequency band, it indicates that the unlicensed frequency band is unavailable.

[0095] Optionally, in the embodiments of this application, the occurrence of consecutive LBT failures on unlicensed frequency bands may include any one of the following:

[0096] In the case where there are multiple available resources in an unlicensed frequency band, consecutive LBT failures occur in one of the available resources.

[0097] In the case where there are multiple available resources in an unlicensed frequency band, consecutive LBT failures occur in each of the multiple available resources;

[0098] When there is only one available resource in an unlicensed frequency band, consecutive LBT failures occur on that available resource.

[0099] In the case of multiple available resources in an unlicensed frequency band, consecutive LBT failures occur in at least two of the available resources.

[0100] The aforementioned resources may be resource blocks, resource pools, or bandwidth parts (BWP), or other possible resources. This application embodiment does not specifically limit them.

[0101] Optionally, in this embodiment, the first terminal 11A can detect whether consecutive LBT failures have occurred on a certain resource using a timer (e.g., an LBT failure detection timer) and a counter (e.g., an LBT counter). For example, when the first terminal 11A first receives an LBT failure indication message from a lower layer (e.g., the MAC layer), it can start the LBT failure detection timer and increment the value of the LBT counter by 1. If the LBT failure detection timer does not time out, the first terminal 11A increments the value of the LBT counter by 1 each time it receives an LBT failure indication message. After the LBT counter value is incremented, if the value of the LBT counter is greater than a set threshold, it indicates that consecutive LBT failures have occurred on that resource. When the LBT failure detection timer times out, the first terminal 11A can reset the value of the LBT counter to 0 to re-accumulate the number of LBT failures.

[0102] Optionally, in embodiments of this application, the first failure handling operation may include at least one of the following:

[0103] Perform a sidelink radio link failure (SL RLF) operation on the SL corresponding to the unlicensed frequency band;

[0104] Report continuous LBT failures to network-side device 12;

[0105] Suspend the SL corresponding to the unlicensed frequency band;

[0106] SL transmission is performed on resources within the licensed frequency band.

[0107] The SL corresponding to the aforementioned unlicensed frequency band can be an SL built on that unlicensed frequency band, that is, an SL between two terminals that directly transmit data through that unlicensed frequency band. For example, assuming that the first terminal 11A and the second terminal 11B can directly transmit data through the unlicensed frequency band band 1, then the SL corresponding to the unlicensed frequency band band 1 is the SL between the first terminal 11A and the second terminal 11B.

[0108] Alternatively, the SL mentioned above can be identified by a layer 2 identifier pair (L2 ID pair). For example, the SL can be identified by a source L2 ID and a destination L2 ID.

[0109] In addition, the resources of the aforementioned authorized frequency bands can be configured or dynamically indicated by the network-side device 12 for the first terminal 11A, or they can be predefined (e.g., agreed upon by the protocol), and can be determined according to actual usage requirements.

[0110] In some embodiments, the SL transmission method between the first terminal 11A and the second terminal 11B can be broadcast transmission or multicast transmission. In this case, the above-described SL RLF operation may include at least one of the following:

[0111] Reset the media access control (MAC) entity corresponding to SL;

[0112] Reset or release the L2 entity corresponding to SL.

[0113] Resetting the MAC entity corresponding to SL may include at least one of the following:

[0114] Release all HARQ resources corresponding to the L2 ID pair of this SL;

[0115] Cancel the air interface reporting corresponding to the L2 ID pair of this SL, such as status report (SR) or buffer status report (BSR);

[0116] Stop the timers corresponding to the L2 ID pair of this SL, such as timers related to discontinuous reception (DRX);

[0117] Reset the variable corresponding to the L2 ID pair of this SL to its initial value.

[0118] In this embodiment of the application, the L2 entity corresponding to SL can be the radio link control (RLC) entity, packet data convergence protocol (PDCP) entity, and service data adaptation protocol (SDAP) entity of the relevant bearer.

[0119] In other embodiments, the SL transmission method between the first terminal 11A and the second terminal 11B can be unicast transmission. Since unicast transmission is established through the PC5-S connection and PC5-RRC connection between the first terminal 11A and the second terminal 11B, when performing the SL RLF operation, in addition to resetting or releasing the MAC entity and L2 entity, information related to the PC5-signaling (PC5-S) connection and the PC5-radio resource control (PC5-RRC) connection can also be released. In this case, the above-described SL RLF operation may include at least one of the following:

[0120] Reset the MAC entity corresponding to SL;

[0121] Reset or release the L2 entity corresponding to SL;

[0122] Release the data radio bearer (DRB) corresponding to SL;

[0123] Release the signal radio bearer (SRB) corresponding to SL;

[0124] Delete the SL configuration information;

[0125] Release the PC5-RRC connection corresponding to SL;

[0126] Release the PC5-S connection corresponding to SL;

[0127] Report SL RLF to network-side device 12;

[0128] The reason for reporting SL RLF to network-side device 12 is continuous LBT failure.

[0129] Optionally, in this embodiment of the application, the timing of reporting continuous LBT failures to the network-side device 12 may include any of the following:

[0130] (1) When the first terminal 11A is in the RRC connected state, the first terminal 11A immediately reports continuous LBT failure to the network side device 12;

[0131] (2) If the first terminal 11A is in the RRC idle state or the RRC inactive state, the first terminal 11A immediately enters the RRC connected state and reports continuous LBT failure to the network side device 12.

[0132] (3) When the first terminal 11A is in the RRC idle state or RRC inactive state, after the first terminal 11A subsequently enters the RRC connected state, the first terminal reports continuous LBT failure to the network side device 12.

[0133] Optionally, in this embodiment of the application, the first terminal 11A may use SL UE Information signaling or other uplink signaling to report continuous LBT failures to the network-side device 12.

[0134] That is, the first terminal 11A can report to the network side in the form of SL UE Information signaling or other uplink signaling.

[0135] Optionally, in this embodiment of the application, the above-mentioned reporting of continuous LBT failures to the network-side device 12 may include at least one of the following:

[0136] Report the time of occurrence of consecutive LBT failures to network-side device 12;

[0137] Report information about resources that have experienced consecutive LBT failures to network-side device 12.

[0138] That is, the content reported by the first terminal 11A to the network-side device 12 may include at least one of the following: the time information of the continuous LBT failure and the location information of the continuous LBT failure.

[0139] Optionally, in this embodiment of the application, the above-mentioned reporting of continuous LBT failures to the network-side device 12 may include: reporting continuous LBT failures to the network-side device 12 and requesting transmission resources from the network-side device 12.

[0140] That is, while the first terminal 11A reports continuous LBT failures to the network-side device 12, it requests the network-side device 12 to allocate other available resources, such as available licensed frequency band resources.

[0141] For example, the first terminal 11A can report indication information and / or service requirement information. The indication information may explicitly or implicitly indicate that the unlicensed frequency band is unavailable or that there have been consecutive LBT failures.

[0142] Optionally, in this embodiment of the application, the SL corresponding to the suspended unlicensed frequency band may include at least one of the following:

[0143] If no other available resources are available for SL transmission, suspend the SL corresponding to the unlicensed frequency band;

[0144] When the service transmitted by the SL is the primary service, the SL corresponding to the unlicensed frequency band is suspended.

[0145] That is, the timing for the first terminal 11A to suspend the SL corresponding to the unlicensed frequency band may include at least one of the above.

[0146] It is understandable that, if there are no other available resources on the network side for SL transmission, the first terminal 11A can suspend SL transmission and wait for the congestion of the current unlicensed frequency band to ease before resuming SL transmission. Alternatively, if the service being transmitted by the first terminal 11A in this SL transmission is not urgent, or the Quality of Service (QoS) requirement is relatively low, or if it is not suitable to use other resources for transmission due to cost reasons, the first terminal 11A can also suspend SL transmission and wait for the congestion of the current unlicensed frequency band to ease before resuming SL transmission.

[0147] Among them, the network-side device 12 can configure or indicate services that support suspension operations to the first terminal 11A, or the first terminal 11A can determine the services that can be suspended according to its own service needs.

[0148] That is, the first business described above can satisfy at least one of the following:

[0149] Configured by network-side device 12;

[0150] Indicated by network-side device 12;

[0151] Determined by the first terminal 11A.

[0152] Optionally, in this embodiment, the first terminal 11A may also decide whether to suspend the SL based on the transmission mode of the SL. For example, if the SL corresponding to the unlicensed frequency band is unicast transmission, the SL corresponding to the unlicensed frequency band will not be suspended; if the SL corresponding to the unlicensed frequency band is multicast transmission, the SL corresponding to the unlicensed frequency band will be suspended.

[0153] Optionally, in this embodiment of the application, the SL corresponding to the suspension of unlicensed frequency bands mentioned above may include:

[0154] Suspend at least some services on the SL corresponding to the unlicensed frequency band; or

[0155] Suspend at least a portion of the DRBs carrying at least a portion of the services on the SL corresponding to the unlicensed frequency band.

[0156] That is, the suspension operation can target at least some of the services on the SL, or at least some of the DRBs on the SL that carry at least some of the services.

[0157] Optionally, if the suspend operation targets at least some of the aforementioned DRBs, after suspending at least some of the DRBs, the first terminal 11A may perform at least one of the following operations:

[0158] Maintain or reset at least some of the PDCP layer transmit and receive state variables of the DRB;

[0159] Maintain or reset at least some of the transmit and receive state variables of the RLC layer of the DRB;

[0160] Stop or reset the MAC layer transmission-related state of at least part of the DRB.

[0161] That is, a suspend operation can include at least one of the above operations.

[0162] Specifically, keeping the transmit and receive state variables of the RLC and PDCP layers unchanged can be achieved by keeping them constant. Resetting the transmit and receive state variables of the RLC and PDCP layers to their initial values ​​can be achieved by restoring them to their original values.

[0163] In addition, stopping or resetting at least part of the MAC layer transmission-related states of the DRB can include: stopping the hybrid automatic repeat request (HARQ) process and buffer, canceling SR or BSR triggering, canceling the channel state information reporting (CSI) process, stopping the transmitter's timers (e.g., DRX timers), and resetting the transmitter's state variables such as logical channel-related token bucket variables.

[0164] Optionally, if the first failure handling operation described above includes suspending the SL corresponding to the unlicensed frequency band, the suspension parameter for suspending the SL corresponding to the unlicensed frequency band may include at least one of the following:

[0165] The length of the first pending timer;

[0166] The threshold value for suspending the attempt counter;

[0167] Conditions for resuming a suspended operation.

[0168] The recovery condition for the suspended operation indicates the conditions that must be met to resume the suspended operation. For example, the recovery condition for the suspended operation could be N consecutive successful LBTs. Based on this, after the SL corresponding to the unlicensed frequency band is suspended, if the first terminal 11A detects N consecutive successful LBTs, it means that the first terminal 11A can resume the suspended operation.

[0169] Optionally, the continuous LBT failure handling method provided in this application embodiment may further include the following steps 203 and 204.

[0170] Step 203: After the SL corresponding to the unlicensed frequency band is suspended, the first terminal 11A starts the first suspension timer.

[0171] Step 204: After the first suspend timer expires, the first terminal 11A performs LBT.

[0172] In the event of an LBT failure, the value of the suspend attempt counter is incremented by 1.

[0173] Optionally, if LBT is successful, the first terminal 11A can accumulate the number of consecutive LBT successes through a counter (such as a consecutive LBT success counter), and then resume the suspension operation after the number of consecutive LBT successes meets the resumption condition of the suspension operation.

[0174] Optionally, if the value of the suspend attempt counter is less than the threshold value of the suspend attempt counter, the method may further include step 205 below.

[0175] Step 205: The first terminal 11A restarts the first suspend timer and continues LBT after the first suspend timer expires.

[0176] Specifically, in each LBT failure, the value of the suspend attempt counter is incremented by 1.

[0177] Understandably, if multiple LBT tests result in consecutive LBT failures (i.e., consecutive LBT failures), the value of the suspend attempt counter will accumulate to the suspend attempt counter threshold. Simultaneously, consecutive LBT failures indicate that the unlicensed frequency band is currently unavailable.

[0178] Optionally, if the value of the suspension attempt counter is greater than or equal to the threshold value of the suspension attempt counter, the method may further include step 206 or step 207 as described below.

[0179] Step 206: The first terminal 11A releases the SL corresponding to the unlicensed frequency band.

[0180] Step 207: The first terminal 11A performs an SL RLF operation on the SL corresponding to the unlicensed frequency band.

[0181] That is, after the SL corresponding to the unlicensed frequency band is suspended, if the value of the suspension attempt counter is greater than or equal to the threshold value of the suspension attempt counter, the first terminal 11A can determine that the unlicensed frequency band is still unavailable, and thus the first terminal 11A can release the SL corresponding to the unlicensed frequency band, or perform an SL RLF operation on the SL corresponding to the unlicensed frequency band.

[0182] Optionally, if the first failure handling operation mentioned above includes suspending the SL corresponding to the unlicensed frequency band, after the first terminal 11A performs the first failure handling operation, the continuous LBT failure handling method provided in this application embodiment may further include the following steps 208 and 209, or the following steps 208 and 210.

[0183] Step 208: The first terminal 11A continuously or periodically monitors unlicensed frequency bands.

[0184] Step 209: If at least one available resource exists on an unlicensed frequency band, the first terminal 11A resumes the at least one available resource.

[0185] That is, when an idle resource (unoccupied resource) is detected on an unlicensed frequency band, the first terminal 11A restores the idle resource.

[0186] Step 210: If no available resources are detected on the unlicensed frequency band within the target duration, the first terminal 11A releases the SL corresponding to the unlicensed frequency band or performs an SL RLF operation on the SL corresponding to the unlicensed frequency band.

[0187] That is, after the first terminal 11A has been listening to the unlicensed frequency band for a period of time, if the occupation of the unlicensed frequency band is still not relieved, that is, the unlicensed frequency band is still unavailable, the first terminal 11A can release the SL corresponding to the unlicensed frequency band or perform an SL RLF operation on the SL.

[0188] Optionally, such as Figure 3 As shown, prior to step 201 above, the continuous LBT failure handling method provided in this application embodiment may further include the following step 201A.

[0189] Step 201A: The first terminal 11A determines the first failure handling operation based on the first information.

[0190] The first information is used to indicate the first failure handling operation to be performed in the event of consecutive LBT failures on an unlicensed frequency band.

[0191] The first piece of information can be configured by the network-side device 12 or it can be predefined (e.g., according to the protocol).

[0192] If the first information is configured by network-side device 12, such as Figure 3 As shown, prior to step 201A above, the method may further include step 202 below.

[0193] Step 202: Network-side device 12 configures first information for the first terminal 11A.

[0194] For example, network-side device 12 can configure the first information for the first terminal 11A through pre-configuration signaling, system information block (SIB) signaling, or dedicated RRC signaling. Of course, network-side device 12 can also configure the first information for the first terminal 11A in other ways, and this application embodiment does not specifically limit this.

[0195] In the continuous LBT failure handling method provided in this application embodiment, since the first terminal can perform a first failure handling operation when continuous LBT failures occur on an unlicensed frequency band, it can handle continuous LBT failures in SL communication. This avoids the situation where the terminal (e.g., the local terminal) cannot handle continuous LBT failures during SL communication via an unlicensed frequency band, thus making the SL communication strategy more complete.

[0196] The above embodiments of this application provide a transmitting terminal suitable for SL communication (e.g., Figure 1 The continuous LBT failure handling method for the first terminal 11A in the application can solve the problem of continuous LBT failures occurring in the transmitting terminal in the unlicensed frequency band. In addition, for LBT failures occurring in the transmitting terminal in the unlicensed frequency band, the following embodiments of this application also provide a receiving terminal (e.g., in the SL) suitable for LBT failures in the SL. Figure 2 The continuous LBT processing method of the second terminal 11B in the middle.

[0197] Figure 4 The image shows a continuous LBT failure handling method provided in an embodiment of this application. This method can be implemented by... Figure 1 The second terminal 11B in the wireless communication system 10 shown executes the method, which includes the following step 401.

[0198] Step 401: If it is determined that the first terminal 11A has experienced consecutive LBT failures on an unlicensed frequency band, the second terminal 11B performs a second failure handling operation.

[0199] Among them, the first terminal 11A can be a terminal that has established an SL with the second terminal 11B.

[0200] The second failure handling operation can include any of the following:

[0201] Suspend the SL connection with the first terminal 11A;

[0202] Data is transmitted with the first terminal 11A using a method that disables HARQ feedback.

[0203] Release the SL between the first terminal 11A and the first terminal 11A.

[0204] The aforementioned suspending of the SL between the first terminal 11A and the SL can be a suspension of the transmission of some or all services on that SL.

[0205] For example, the second terminal 11B can determine whether the first terminal 11A has experienced continuous LBT failures on an unlicensed frequency band by failing the keepalive process or the continuous feedback detection failure (i.e., continuously not receiving feedback information) connected to the PC5-S of the first terminal 11A.

[0206] Optionally, if the second failure handling operation involves transmitting data with the first terminal 11A using a HARQ feedback disabled method, the second terminal 11B can also use an active repetition method to transmit services with reliability requirements. For example, for services in unacknowledged mode (UM), active repetition can be used for transmission.

[0207] Optionally, such as Figure 5 As shown, before step 401, the continuous LBT failure handling method provided in this application embodiment may further include the following step 402.

[0208] Step 402: The second terminal 11B determines the second failure handling operation based on the second information.

[0209] The second information may be configured by the network-side device 12 or determined based on the negotiation information with the first terminal 11A.

[0210] For example, the second terminal 11B can interact with the first terminal 11A via a PC5-RRC connection according to the configuration of the network-side device 12 to synchronize whether suspend operation is supported or which services support suspend operation. If both support suspend operation, the second terminal 11B will not perform SL RLF operation triggered by the discontinuous reception feedback mechanism (feedback DTX) for the SL between the two or the services on the SL.

[0211] For example, during the establishment of the SL, the first terminal 11A and the second terminal 11B can negotiate whether to support suspend operations or which services support suspend operations. If both support suspend operations, the two terminals will not perform SL RLF operations triggered by the discontinuous reception feedback mechanism (feedback DTX) for the SL between them or for the services on that SL.

[0212] In some embodiments, where the second failure handling operation includes suspending the SL between the first terminal 11A and the second failure handling operation, the method may further include steps 403 and 404 as described below, or steps 403 and 405 as described below.

[0213] Step 403: After the SL between the second terminal 11A and the first terminal 11A is suspended, the second terminal 11B starts the second suspension timer.

[0214] Step 404: After the second suspend timer expires, the second terminal 11B releases the SL between itself and the first terminal 11A.

[0215] That is, after the second terminal 11B suspends the SL with the first terminal 11A, it can wait for a period of time before releasing the SL with the first terminal 11A.

[0216] Step 405: After the second suspend timer expires, the second terminal 11B resumes the SL with the first terminal 11A to receive data packets sent by the first terminal 11A.

[0217] That is, after the SL between the second terminal 11B and the first terminal 11A is suspended, if the first terminal 11A resumes suspension after a period of time, the second terminal 11B can resume the SL between the second terminal 11A and the first terminal 11A.

[0218] Optionally, in this embodiment of the application, the SL between the suspend and the first terminal 11A described above may include any one of the following:

[0219] Suspend at least some of the services on SL; or

[0220] Suspend at least a portion of the DRB carrying at least a portion of the services on the SL.

[0221] In the continuous LBT failure handling method provided in this application embodiment, since the second terminal can perform a second failure handling operation when the first terminal experiences continuous LBT failures on an unlicensed frequency band, continuous LBT failures occurring in SL communication can be handled. This avoids situations where the terminal (e.g., the peer terminal) is unable to handle continuous LBT failures during SL communication via an unlicensed frequency band, thus making the SL communication strategy more complete.

[0222] It should be noted that the execution entity of the continuous LBT failure handling method provided in the embodiments of this application can be a continuous LBT failure handling device, or a control module in the continuous LBT failure handling device for executing the continuous LBT failure handling method. This embodiment of the application uses the execution of the continuous LBT failure handling method by the continuous LBT failure handling device as an example to illustrate the continuous LBT failure handling device provided in the embodiments of this application.

[0223] like Figure 6 The diagram shows a continuous LBT failure processing device 600 provided in an embodiment of this application. The continuous LBT failure processing device 600 includes a processing module 601. The processing module 601 is used to perform a first failure processing operation in the event of continuous LBT failures occurring on an unlicensed frequency band.

[0224] The first failure handling operation mentioned above includes at least one of the following:

[0225] Perform SL RLF operation on the SL corresponding to the unlicensed frequency band;

[0226] Report consecutive LBT failures to the network-side device;

[0227] Suspend the SL corresponding to the unlicensed frequency band;

[0228] SL transmission is performed on resources within the licensed frequency band.

[0229] Optionally, in the embodiments of this application, the above-described SL RLF operation may include at least one of the following:

[0230] Reset the MAC entity corresponding to SL;

[0231] Reset or release the Layer 2 entity corresponding to SL.

[0232] Optionally, when the SL transmission method is unicast transmission, the above SL RLF operation further includes at least one of the following:

[0233] Release the DRB corresponding to SL;

[0234] Release the SRB corresponding to SL;

[0235] Delete the SL configuration information;

[0236] Release the PC5-RRC connection corresponding to SL;

[0237] Release the PC5-S connection corresponding to SL;

[0238] Report SL RLF to network-side devices;

[0239] The reason for reporting SL RLF to the network-side device is continuous LBT failure.

[0240] Optionally, in this embodiment of the application, consecutive LBT failures on unlicensed frequency bands may include any of the following:

[0241] In the case where there are multiple available resources in an unlicensed frequency band, consecutive LBT failures occur in one of the available resources.

[0242] In the case where there are multiple available resources in an unlicensed frequency band, consecutive LBT failures occur in each of the multiple available resources;

[0243] In the case where there is only one available resource in an unlicensed frequency band, consecutive LBT failures occur on that available resource.

[0244] Optionally, in this embodiment of the application, reporting continuous LBT failures to the network-side device may include at least one of the following:

[0245] Report the time of occurrence of consecutive LBT failures to the network-side device;

[0246] Report information about resources that have experienced consecutive LBT failures to the network-side devices.

[0247] Optionally, in this embodiment of the application, reporting continuous LBT failures to the network-side device may include:

[0248] Report consecutive LBT failures to the network-side device and request transmission resources from the network-side device.

[0249] Optionally, in the embodiments of this application, the SL corresponding to the suspended unlicensed frequency band mentioned above may include at least one of the following:

[0250] Suspend SL if no other resources are available for SL transfer;

[0251] If the service being transmitted via SL is the primary service, then SL is suspended.

[0252] Optionally, in the embodiments of this application, the first service may satisfy at least one of the following:

[0253] Configured by network-side devices;

[0254] Indicated by network-side devices;

[0255] Determined by the first terminal.

[0256] Optionally, in this embodiment of the application, the SL corresponding to the suspension of unlicensed frequency bands mentioned above may include:

[0257] Suspend at least some of the services on SL; or

[0258] Suspend at least a portion of the DRB carrying at least a portion of the services on the SL.

[0259] Optionally, in this embodiment of the application, after suspending at least a portion of the DRB, the processing module 601 may also perform at least one of the following operations:

[0260] Maintain or reset at least some of the PDCP layer transmit and receive state variables of the DRB;

[0261] Maintain or reset at least some of the transmit and receive state variables of the RLC layer of the DRB;

[0262] Stop or reset the MAC layer transmission-related state of at least part of the DRB.

[0263] Optionally, in this embodiment of the application, when the first failure handling operation includes suspending the SL corresponding to the unlicensed frequency band, the suspension parameters for suspending the SL include at least one of the following:

[0264] The length of the first pending timer;

[0265] The threshold value for suspending the attempt counter;

[0266] Conditions for resuming a suspended operation.

[0267] Optionally, in this embodiment of the application, the processing module 601 is further configured to:

[0268] After the SL corresponding to the unlicensed frequency band is suspended, the first suspension timer is started;

[0269] LBT is performed after the first suspend timer expires.

[0270] In the event of an LBT failure, the value of the suspend attempt counter is incremented by 1.

[0271] Optionally, in this embodiment of the application, the processing module 601 is further configured to:

[0272] If the value of the suspend attempt counter is less than the threshold value, the first suspend timer is restarted;

[0273] LBT continues after the first suspend timer times out.

[0274] Specifically, in each LBT failure, the value of the suspend attempt counter is incremented by 1.

[0275] Optionally, in this embodiment of the application, the processing module 601 is further configured to:

[0276] If the value of the suspend attempt counter is greater than or equal to the threshold value, release SL or perform an SLRLF operation on SL.

[0277] Optionally, in this embodiment of the application, the processing module 601 is further configured to:

[0278] If the first failure handling operation includes suspending the SL corresponding to the unlicensed frequency band, after the first failure handling operation is performed, continuously or periodically monitor the unlicensed frequency band.

[0279] If at least one available resource exists in the unlicensed frequency band, restore at least one available resource; or

[0280] If no available resources are detected on the unlicensed frequency band within the target duration, release the SL; or perform an SL RLF operation on the SL.

[0281] Optionally, in this embodiment of the application, the processing module 601 is further configured to:

[0282] Before executing the first failure handling operation, the first failure handling operation is determined based on the first information;

[0283] The first piece of information is either configured or predefined by the network-side devices.

[0284] Based on the continuous LBT failure handling apparatus provided in this application embodiment, in the event of continuous LBT failures on an unlicensed frequency band, the apparatus can perform a first failure handling operation. Through this scheme, since the apparatus can perform a first failure handling operation when continuous LBT failures occur on an unlicensed frequency band, continuous LBT failures occurring in SL communication can be handled. This avoids the situation where the terminal (e.g., the local terminal) is unable to handle continuous LBT failures during SL communication via unlicensed frequency bands.

[0285] like Figure 7 The image shows a continuous LBT failure processing device 700 provided in an embodiment of this application. The continuous LBT failure processing device 700 includes a configuration module 701. The configuration module 701 is used to configure first information for a first terminal, the first information indicating a first failure processing operation to be performed in the event of continuous LBT failures occurring on an unlicensed frequency band.

[0286] The first failure handling operation includes at least one of the following:

[0287] Perform SL RLF operation on the SL corresponding to the unlicensed frequency band;

[0288] Report consecutive LBT failures to the network-side device;

[0289] Suspend the SL corresponding to the unlicensed frequency band;

[0290] SL transmission is performed on resources within the licensed frequency band.

[0291] Optionally, in embodiments of this application, the SL RLF operation may include at least one of the following:

[0292] Reset the MAC entity corresponding to SL;

[0293] Reset or release the Layer 2 entity corresponding to SL.

[0294] Optionally, in the embodiments of this application, when the transmission mode of SL is unicast transmission, the SL RLF operation further includes at least one of the following:

[0295] Release the DRB corresponding to SL;

[0296] Release the SRB corresponding to SL;

[0297] Delete the SL configuration information;

[0298] Release the PC5-RRC connection corresponding to SL;

[0299] Report SL RLF to network-side devices;

[0300] The reason for reporting SL RLF to the network-side device is continuous LBT failure.

[0301] Optionally, in this embodiment of the application, consecutive LBT failures on unlicensed frequency bands may include any of the following:

[0302] In the case where there are multiple available resources in an unlicensed frequency band, consecutive LBT failures occur in one of the available resources.

[0303] In the case where there are multiple available resources in an unlicensed frequency band, consecutive LBT failures occur in each of the multiple available resources;

[0304] In the case where there is only one available resource in an unlicensed frequency band, consecutive LBT failures occur on that available resource.

[0305] Optionally, in this embodiment of the application, reporting continuous LBT failures to the network-side device may include at least one of the following:

[0306] Report the time of occurrence of consecutive LBT failures to the network-side device;

[0307] Report information about resources that have experienced consecutive LBT failures to the network-side devices.

[0308] Optionally, in this embodiment of the application, reporting continuous LBT failures to the network-side device may include:

[0309] Report consecutive LBT failures to the network-side device and request transmission resources from the network-side device.

[0310] Optionally, in this embodiment of the application, suspending the SL corresponding to the unlicensed frequency band may include at least one of the following:

[0311] Suspend SL if no other resources are available for SL transfer;

[0312] If the service being transmitted via SL is the primary service, then SL is suspended.

[0313] Optionally, the first service may satisfy at least one of the following:

[0314] Configured by network-side devices;

[0315] Indicated by network-side devices;

[0316] Determined by the first terminal.

[0317] Optionally, in this embodiment of the application, suspending the SL corresponding to the unlicensed frequency band may include:

[0318] Suspend at least some of the services on SL; or

[0319] Suspend at least a portion of the data radio bearer (DRB) carrying at least a portion of the services on the SL.

[0320] Optionally, in this embodiment of the application, when the first failure handling operation includes suspending the SL corresponding to the unlicensed frequency band, the suspension parameter for suspending the SL may include at least one of the following:

[0321] The length of the first pending timer;

[0322] The threshold value for suspending the attempt counter;

[0323] Conditions for resuming a suspended operation.

[0324] Based on the continuous LBT failure handling apparatus provided in the embodiments of this application, a first information can be configured for the first terminal. This first information indicates a first failure handling operation to be performed when continuous LBT failures occur on an unlicensed frequency band. Thus, when continuous LBT failures occur on an unlicensed frequency band, the first terminal can determine the first failure handling operation based on the first information and execute it, thereby handling continuous LBT failures in SL communication. This avoids situations where the terminal (e.g., the local terminal) is unable to handle continuous LBT failures during SL communication via an unlicensed frequency band.

[0325] like Figure 8The image shows a continuous LBT failure processing device 800 provided in an embodiment of this application. The continuous LBT failure processing device 800 includes a processing module 801. The processing module 801 is used to perform a second failure processing operation when it is determined that a first terminal has experienced continuous LBT failures on an unlicensed frequency band. The first terminal is a terminal that has established a sidelink (SL) with the second terminal.

[0326] The second failure handling operation includes any one of the following:

[0327] Suspend the SL between the first terminal;

[0328] Data is transmitted with the first terminal using a hybrid automatic repeat request (HARQ) feedback disabled method.

[0329] Release the SL between the first terminal and the first terminal.

[0330] Optionally, in this embodiment of the application, the processing module 801 may also be used for:

[0331] In the case where the second failure handling operation includes suspending the SL between the first terminal, the second suspend timer is started after the SL is suspended.

[0332] Release SL after the second suspend timer expires; or

[0333] After the second suspend timer expires, SL is resumed to receive data packets sent by the first terminal.

[0334] Optionally, in this embodiment of the application, suspending SL may include:

[0335] Suspend at least some of the services on SL; or

[0336] Suspend at least a portion of the data radio bearer (DRB) carrying at least a portion of the services on the SL.

[0337] Optionally, in this embodiment of the application, the processing module 801 may also be used for:

[0338] Before the second terminal executes the second failure handling operation, the second failure handling operation is determined based on the second information.

[0339] The second piece of information is configured by the network-side equipment or determined based on negotiation information with the first terminal.

[0340] Based on the continuous LBT failure handling apparatus provided in the embodiments of this application, since the first terminal experiences continuous LBT failures on an unlicensed frequency band, the apparatus can perform a second failure handling operation, thereby handling continuous LBT failures occurring in SL communication. This avoids situations where the terminal (e.g., the peer terminal) is unable to handle continuous LBT failures during SL communication via an unlicensed frequency band.

[0341] The continuous LBT failure handling device in this application embodiment can be a device, a device or electronic device with an operating system, or a component, integrated circuit, or chip in a terminal. The device or electronic device can be a mobile terminal or a non-mobile terminal. For example, a mobile terminal can include, but is not limited to, the types of terminals 11 listed above, while a non-mobile terminal can be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the specific type of terminal.

[0342] The continuous LBT failure processing device provided in this application embodiment can achieve... Figures 1 to 5 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0343] Optional, such as Figure 9 As shown, this application embodiment also provides a communication device 900, including a processor 901, a memory 902, and a program or instructions stored in the memory 902 and executable on the processor 901. For example, when the communication device 900 is a terminal, the program or instructions executed by the processor 901 implement the various processes of the above-described continuous LBT failure handling method embodiment, and achieve the same technical effect. When the communication device 900 is a network-side device, the program or instructions executed by the processor 901 implement the various processes of the above-described continuous LBT failure handling method embodiment, and achieve the same technical effect. To avoid repetition, further details are omitted here. The aforementioned communication device 900 can be a terminal or a network-side device.

[0344] This application also provides a first terminal, including a processor. The processor is configured to perform a first failure handling operation when the first terminal experiences consecutive LBT failures on an unlicensed frequency band. This embodiment is similar to the one described above. Figure 2 The various implementation processes and methods of the above-described method embodiments can be applied to this embodiment and achieve the same technical effect.

[0345] Furthermore, this application embodiment also provides a second terminal, including a processor. The processor is configured to perform a second failure handling operation when it is determined that a first terminal has experienced consecutive LBT failures on an unlicensed frequency band, wherein the first terminal is a terminal with which a Service Level Agreement (SL) has been established. This embodiment is similar to the one described above. Figure 4 The various implementation processes and methods of the above-described method embodiments can be applied to this embodiment and achieve the same technical effect.

[0346] For example, Figure 10 A schematic diagram of a terminal hardware structure for implementing the first terminal and / or the second terminal in the above embodiments of this application.

[0347] The terminal 1000 includes, but is not limited to, at least some of the following components: radio frequency unit 1001, network module 1002, audio output unit 1003, input unit 1004, sensor 1005, display unit 1006, user input unit 1007, interface unit 1008, memory 1009, and processor 1010.

[0348] Those skilled in the art will understand that the terminal 1000 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 1010 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 10 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0349] It should be understood that, in this embodiment, the input unit 1004 may include a graphics processing unit (GPU) 10041 and a microphone 10042. The GPU 10041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0350] In this embodiment, the radio frequency unit 1001 receives downlink data from the network-side device and processes it for the processor 1010; additionally, it sends uplink data to the network-side device. Typically, the radio frequency unit 1001 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0351] The memory 1009 can be used to store software programs or instructions and various data. The memory 1009 may primarily include a program or instruction storage area and a data storage area. The program or instruction storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1009 may include high-speed random access memory and non-volatile memory, wherein the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. For example, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0352] Processor 1010 may include one or more processing units; optionally, processor 1010 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications or instructions, and the modem processor mainly handles wireless communication, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1010.

[0353] The processor 1010 is used to perform a first failure handling operation when the first terminal experiences consecutive LBT failures on an unlicensed frequency band.

[0354] Alternatively, processor 1010 is configured to perform a second failure handling operation if it is determined that the first terminal has experienced consecutive LBT failures on an unlicensed frequency band.

[0355] This application also provides a network-side device, including a processor. The processor is configured to configure first information for a first terminal, the first information indicating a first failure handling operation to be performed in the event of consecutive LBT failures on an unlicensed frequency band. This network-side device embodiment corresponds to the network-side device method embodiment described above; all implementation processes and methods of the above method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[0356] Specifically, embodiments of this application also provide a network-side device. For example... Figure 11 As shown, the network-side device 1100 includes: an antenna 1101, a radio frequency (RF) device 1102, and a baseband device 1103. The antenna 1101 is connected to the RF device 1102. In the uplink direction, the RF device 1102 receives information through the antenna 1101 and transmits the received information to the baseband device 1103 for processing. In the downlink direction, the baseband device 1103 processes the information to be transmitted and sends it to the RF device 1102. The RF device 1102 processes the received information and transmits it through the antenna 1101.

[0357] The aforementioned frequency band processing device can be located in the baseband device 1103. The method executed by the network-side device in the above embodiments can be implemented in the baseband device 1103, which includes a processor 1104 and a memory 1105.

[0358] The baseband device 1103 may include, for example, at least one baseband board on which multiple chips are disposed, such as... Figure 11 As shown, one of the chips, for example, is a processor 1104, which is connected to a memory 1105 to call the program in the memory 1105 and execute the network device operation shown in the above method embodiment.

[0359] The baseband device 1103 may also include a network interface 1106 for exchanging information with the radio frequency device 1102, such as a common public radio interface (CPRI).

[0360] Specifically, the network-side device in this embodiment of the invention further includes: instructions or programs stored in memory 1105 and executable on processor 1104, wherein processor 1104 calls the instructions or programs in memory 1105 to execute. Figure 7 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0361] This application also provides a readable storage medium storing a program or instructions. When executed by a processor, the program or instructions implement the various processes of the above-described continuous LBT failure handling method embodiments and achieve the same technical effect. To avoid repetition, further details are omitted here. It should be noted that the readable storage medium can be non-volatile or volatile, and it can also be non-transient.

[0362] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0363] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described continuous LBT failure handling method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0364] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0365] This application also provides a computer program / program product stored in a volatile and / or non-volatile storage medium, which is executed by at least one processor to implement the steps of the continuous LBT failure handling method as described in the first aspect, or the steps of the continuous LBT failure handling method as described in the second aspect, or the steps of the continuous LBT failure handling method as described in the third aspect.

[0366] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0367] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0368] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for handling continuous listen-before-speak (LBT) failures, characterized in that, include: If it is determined that the first terminal has experienced consecutive LBT failures on an unlicensed frequency band, the second terminal performs a second failure handling operation, wherein the first terminal is a terminal that has established a side link SL with the second terminal; The second failure handling operation includes any one of the following: Suspend the SL connection with the first terminal; Data is transmitted with the first terminal using a hybrid automatic repeat request (HARQ) feedback disabled method. Release the SL between the terminal and the first terminal.

2. The method according to claim 1, characterized in that, In the case where the second failure handling operation includes suspending the SL with the first terminal, the method further includes: After the SL is suspended, the second terminal starts the second suspension timer; After the second suspend timer expires, the second terminal releases the SL; or After the second suspend timer expires, the second terminal resumes the SL to receive data packets sent by the first terminal.

3. The method according to claim 1, characterized in that, The suspension of the SL includes: Suspend at least some services on the SL; or Suspend at least a portion of the data radio bearer (DRB) carrying at least a portion of the services on the SL.

4. The method according to claim 1, characterized in that, Before the second terminal performs the second failure handling operation, the method further includes: The second terminal determines the second failure handling operation based on the second information; The second information is configured by the network-side device or determined based on negotiation information with the first terminal.

5. A continuous listen-before-speak LBT failure processing device, characterized in that, The continuous LBT failure handling device includes a processing module; The processing module is used to perform a second failure processing operation when it is determined that the first terminal has experienced consecutive LBT failures on an unlicensed frequency band, wherein the first terminal is a terminal that has established a side link SL with the second terminal. The second failure handling operation includes any one of the following: Suspend the SL connection with the first terminal; Data is transmitted with the first terminal using a hybrid automatic repeat request (HARQ) feedback disabled method. Release the SL between the terminal and the first terminal.

6. A second terminal, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the continuous listen-before-speak LBT failure handling method as described in any one of claims 1 to 4.

7. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the continuous listen-before-speak LBT failure handling method as described in any one of claims 1 to 4.

Images