Wireless communication methods and terminal equipment

Abstract

This application provides a wireless communication method and terminal equipment. The method includes the terminal equipment determining a first policy related to consecutive LBT (Listen Before Talk) failures, wherein the detection of said consecutive LBT failures is related to resource granularity.

Description

[Technical Field]

[0001] This application relates to the field of communications technology, and more specifically to wireless communication methods and terminal equipment. [Background technology]

[0002] In an unlicensed spectrum, terminal equipment can transmit signals based on the principle of listen before talk (LBT). If the channel is idle as a result of channel sensing, terminal equipment can transmit signals using the channel in the unlicensed spectrum. Conversely, if the channel is busy as a result of channel sensing, terminal equipment is generally not permitted to transmit signals using the channel in the unlicensed spectrum.

[0003] The side-link communication scenario introduces enhanced consideration for consecutive LBT failures. However, at present, there are no clear regulations regarding the specifics of consecutive LBT failures. [Overview of the project]

[0004] This application provides a wireless communication method and terminal equipment. Several embodiments relating to this application will be described in detail below.

[0005] In the first embodiment, a wireless communication method is provided, which includes a terminal device determining a first policy related to consecutive LBT failures, wherein the detection of consecutive LBT failures is related to resource granularity.

[0006] In the second embodiment, a terminal device is provided, which includes a decision unit configured to determine a first policy related to consecutive LBT failures, wherein the detection of consecutive LBT failures is related to resource granularity.

[0007] In the third embodiment, a terminal device is provided including memory and a processor, wherein the memory is configured to store a program, and the processor is configured to call the program in the memory and execute the method according to the first embodiment.

[0008] In the fourth embodiment, a device including a processor is provided, the processor being configured to call a program from memory and execute the wireless communication method described in the first embodiment.

[0009] In the fifth embodiment, a chip including a processor is provided, wherein the processor is configured to call a program from memory and cause a device on which the chip is mounted to execute the wireless communication method described in the first embodiment.

[0010] In the sixth embodiment, a computer-readable storage medium is provided, which stores a program that causes a computer to execute the wireless communication method described in the first embodiment.

[0011] In the seventh embodiment, a computer program product is provided, the computer program product including a program that causes a computer to execute the wireless communication method described in the first embodiment.

[0012] In the eighth embodiment, a computer program is provided, and the computer program causes the computer to execute the wireless communication method described in the first embodiment.

[0013] This application provides a clear solution for determining policies related to consecutive LBTs when detecting consecutive LBT failures, taking into account information related to resource granularity, and for terminal equipment to perform operations related to consecutive LBT failures. [Brief explanation of the drawing]

[0014] [Figure 1] This figure shows an example of a system architecture for a wireless communication system to which the embodiments of this application can be applied. [Figure 2]It is a diagram showing a scenario example of sidelink communication within network coverage. [Figure 3] It is a diagram showing a scenario example of sidelink communication with partial network coverage. [Figure 4] It is a diagram showing a scenario example of sidelink communication outside network coverage. [Figure 5] It is a schematic diagram of a sensing-based resource selection method in a sidelink communication system. [Figure 6] It is a diagram showing an example of a sidelink communication method based on broadcast. [Figure 7] It is a diagram showing an example of a sidelink communication method based on unicast. [Figure 8] It is a diagram showing an example of a sidelink communication method based on multicast. [Figure 9] It is a schematic diagram of the correspondence relationship between different resources according to the present application. [Figure 10] It is a flowchart of a wireless communication method according to an embodiment of the present application. [Figure 11] It is a flowchart of a communication method in which continuous LBT failure occurs in an RB set according to an embodiment of the present application, and the resource switching policy switches the resource pool. [Figure 12] It is a flowchart of a communication method in which continuous LBT failure occurs in an RB set according to an embodiment of the present application, and the resource switching policy switches the RB set. [Figure 13] It is a flowchart of a communication method in which continuous LBT failure occurs in a resource pool according to an embodiment of the present application, and the resource switching policy switches the resource pool. [Figure 14] It is a schematic block diagram of a terminal device according to an embodiment of the present application. [Figure 15] It is a schematic structural diagram of a device according to an embodiment of the present application.

Mode for Carrying Out the Invention

[0015] The technical solutions in this application will be described below, along with the drawings.

[0016] Communication system architecture Figure 1 shows an example of a system architecture of a wireless communication system 100 to which embodiments of this application can be applied. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 can provide communication coverage to a specific geographic area and communicate with the terminal device 120 located within that coverage area.

[0017] Figure 1 illustrates one network device and one terminal device, and selectively, the wireless communication system 100 may include one or more network devices 110 and / or one or more terminal devices 120. With respect to one network device 110, each of the one or more terminal devices 120 may be located within the network coverage of the network device 110, or outside the network coverage of the network device 110, with some located within the coverage of the network device 110 and others outside the network coverage of the network device 110. Embodiments of this application are not limited thereto.

[0018] The wireless communication system 100 may optionally include other network entities such as a network controller or a mobile management entity, and the embodiments of this application are not limited thereto.

[0019] It can be understood that the solutions of the embodiments of this application can be applied to various communication systems such as fifth-generation (5G) systems, new radio (NR), long-term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, and LTE time division duplex (TDD) systems. The solutions of this application can also be applied to future communication systems such as sixth-generation mobile communication systems and satellite communication systems.

[0020] In the embodiments of this application, terminal equipment is also called user equipment (UE), access terminal, user unit, user station, mobile station (MS), mobile terminal (MT), remote station, remote terminal equipment, mobile equipment, user terminal, wireless communication equipment, user agent, or user device. In the embodiments of this application, terminal equipment refers to equipment that provides voice and / or data connectivity to a user and can be used to connect people, things, and machines, such as handheld devices with wireless connectivity, in-vehicle equipment, etc. The terminal devices in the embodiments of this application may include mobile phones, tablets, laptops, handhelds, mobile internet devices (MIDs), wearable devices, vehicles, wireless terminals for industrial control, wireless terminals for self-driving, wireless terminals for remote medical surgery, wireless terminals for smart grids, wireless terminals for transportation safety, wireless terminals for smart cities, and wireless terminals for smart homes. For example, a terminal device can function as a scheduling entity that provides sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D) communication. For example, a mobile phone and a car communicate with each other using sidelink signals. Communication between a mobile phone and a smart home device does not require relaying communication signals via a base station. Optionally, a terminal device can also function as a base station.

[0021] The network equipment in the embodiments of this application may be equipment for communicating with terminal equipment, and such network equipment may also be called access network equipment or radio access network equipment, for example, the network equipment may be a base station. In the embodiments of this application, the network equipment refers to a radio access network (RAN) node (or equipment) for terminal equipment to access a radio network. The term "base station" broadly covers a variety of names, or can be replaced with the following names. Examples include NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master MeNB, secondary SeNB, multiplex radio (MSR) node, home base station, network controller, access node, radio node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), and positioning node. A base station can be a macro base station, micro base station, relay node, donor node or similar, or a combination thereof. A base station can refer to a communication module, modem, or chip for installation within the aforementioned equipment or devices. Base stations can be devices that perform base station functions in mobile switching centers and inter-device D2D, V2X, and machine-to-machine (M2M) communications, network-side devices in 6G networks, or devices that perform base station functions in future communication systems.Base stations can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technologies employed by network equipment or the specific forms of equipment.

[0022] Base stations may be stationary or mobile. For example, a helicopter or drone can be configured to function as a mobile base station, and one or more cells may move depending on the location of the mobile base station. In another example, a helicopter or drone can be configured as a device to communicate with another base station.

[0023] In some deployment scenarios, the network equipment in the embodiments of this application may refer to a CU or a DU, or the network equipment may include both a CU and a DU. The gNB may also include an AAU.

[0024] Network equipment and terminal equipment can be configured indoors or outdoors, on land including portable or vehicle-mounted configurations, on water, or in the air on airplanes, balloons, and satellites. The embodiments of this application do not limit the scenario in which the network equipment and terminal equipment are located.

[0025] Sidelink communication in the case of different network coverage Sidelink communication refers to communication technology based on sidelinks. Sidelink communication can be, for example, device-to-device (D2D) or vehicle-to-everything (V2X) communication. In conventional cellular systems, communication data is received or transmitted between terminal devices and network devices, but sidelink communication supports the direct transmission of communication data between terminal devices. Compared to conventional cellular communication, direct transmission of communication data between terminal devices can have higher spectral efficiency and lower transmission delay. For example, vehicle network systems employ sidelink communication technology.

[0026] In sidelink communication, depending on the network coverage situation in which the terminal equipment is located, sidelink communication can be divided into sidelink communication within network coverage, sidelink communication with partial network coverage, and sidelink communication outside of network coverage.

[0027] Figure 2 shows an example scenario of sidelink communication within network coverage. In the scenario shown in Figure 2, both terminal devices 120a are located within the coverage of network device 110. Therefore, both terminal devices 120a can receive configuration signaling from network device 110 (configuration signaling in this application can also be replaced with configuration information) and determine the sidelink configuration based on the configuration signaling from network device 110. After both terminal devices 120a have configured the sidelink, they can perform sidelink communication over the sidelink.

[0028] Figure 3 shows an example scenario of sidelink communication with partial network coverage. In the scenario shown in Figure 3, terminal devices 120a and 120b communicate via sidelink. Since terminal device 120a is located within the coverage of network device 110, terminal device 120a can receive the configuration signaling of network device 110 and determine the sidelink configuration based on the configuration signaling of network device 110. Terminal device 120b is located outside the network coverage and therefore cannot receive the configuration signaling of network device 110. In this case, terminal device 120b can determine the sidelink configuration based on pre-configuration information and / or information contained in the physical sidelink broadcast channel (PSBCH) transmitted by terminal device 120a, which is located within the network coverage. After both terminal devices 120a and 120b have configured the sidelink, they can communicate via sidelink over the sidelink.

[0029] Figure 4 shows an example scenario of sidelink communication outside of network coverage. In the scenario shown in Figure 4, both terminal devices 120b are located outside of network coverage. In this case, both terminal devices 120b can determine the sidelink configuration based on pre-configured information. After both terminal devices 120b have configured the sidelink, they can communicate via the sidelink.

[0030] Research on different stages of D2D In 3GPP communication protocols, D2D is studied in different stages, which are explained below with examples.

[0031] In Rel-12 / 13, inter-device communication is primarily studied as proximity services (ProSe), mainly targeting public security class traffic. ProSe allows terminal devices to send or receive data discontinuously over side links by configuring the location of the resource pool in the time domain (for example, the resource pool being discontinuous in the time domain), thereby achieving power savings.

[0032] Rel-14 / 15 primarily studies V2X systems in vehicle-to-vehicle communication scenarios, mainly targeting communication services between relatively high-speed moving vehicles and between vehicles and people. In V2X, since the in-vehicle system has a continuous power supply, power efficiency is not the main issue; rather, data transmission delay is the main issue. Therefore, the system design requires terminal equipment to perform continuous transmission and reception.

[0033] Rel-14 studies scenarios in which wearable devices access a network via mobile phones, primarily focusing on low-speed movement and low-power access. Further enhancements device to device (FeD2D) have been concluded in the preliminary research stage to allow a base station to configure discontinuous reception (DRX) parameters for a remote terminal via a single relay terminal; however, since the issue has not yet progressed to the standardization stage, the details of how to configure DRX have not yet been concluded.

[0034] Sidelink communication mode (LTE D2D / V2X) A certain standard or protocol (for example, the Third Generation Partnership Project (3GPP®)) defines two sidelink communication modes: Mode 1 and Mode 2.

[0035] In the first mode, the resources of the terminal device (resources in this application may also be called transmission resources, such as time-frequency resources) are allocated by the network device. The terminal device can transmit data via sidelink based on the resources allocated by the network device. The network device may allocate resources to the terminal device for single transmissions or for semi-static transmissions. The first mode can be applied to scenarios covered by the network device, such as the scenario shown in Figure 2. In the scenario shown in Figure 2, since the terminal device 120a is located within the network coverage of the network device 110, the network device 110 can allocate resources to the terminal device 120a that are used for the sidelink transmission process.

[0036] In the second mode, terminal devices can autonomously select one or more resources from the resource pool (RP). The terminal devices can then perform sidelink transmission based on the selected resources. For example, in the scenario shown in Figure 4, terminal device 120b is located outside the cell's coverage. Therefore, terminal device 120b can autonomously select resources from a pre-configured resource pool and perform sidelink transmission. Alternatively, in the scenario shown in Figure 2, terminal device 120a can also autonomously select one or more resources from the resource pool configured by network device 110 and perform sidelink transmission.

[0037] NR V2X While LTE V2X was primarily studied for broadcast scenarios, NR V2X builds upon LTE V2X and extends to unicast and multicast scenarios. In other words, NR V2X application scenarios include broadcast, unicast, and multicast. NR studies V2X applications in these scenarios.

[0038] Similar to LTE V2X, NR V2X also defines two resource-granting modes. Furthermore, a terminal device may be in a hybrid mode, meaning it can acquire resources using both the first and second modes simultaneously. Resource acquisition by a terminal device can be instructed by sidelink granting, which in turn instructs the time-frequency position of the corresponding physical sidelink control channel (PSCCH) and physical sidelink shared channel (PSSCH) resources.

[0039] Unlike LTE V2X, NR V2X introduces feedback-based HARQ retransmission, in addition to the hybrid automatic repeat request (HARQ) retransmission initiated autonomously by terminal devices without feedback. This feedback-based HARQ retransmission method is not limited to unicast communications but can also be applied to multicast communications.

[0040] Similar to LTE V2X, in NR V2X, power efficiency is not the primary issue because the in-vehicle system has a continuous power supply. Instead, data transmission delay is the main problem, and therefore, the system design requires terminal equipment to perform continuous transmission and reception.

[0041] Resource selection method in second mode in NR V2X NR V2X introduced several new features, including support for large volumes of aperiodic traffic, increased retransmissions, and more flexible resource reservation cycles. These features significantly impact the autonomous resource selection mode of terminal devices. In the second mode, terminal devices can select resources from the resource pool that are not reserved by other terminal devices, or that are reserved but have low received power, by decoding sidelink control information (SCI) transmitted by other terminal devices and measuring the received power of the sidelink.

[0042] In some embodiments, the terminal device can implement the resource allocation method in the second mode by the following steps 1 and 2.

[0043] Step 1: The terminal device designates all available resources in the resource selection window as resource set A. Specifically, these are divided into situations 1-1 and 1-2.

[0044] In scenario 1-1, if the terminal device does not perform sensing in some time slots within the sensing window, those time slots that are not being sensed are excluded from all resources on the corresponding time slots in the selection window. In some embodiments, the terminal device can determine the corresponding time slots in the selection window for time slots that are not being sensed within the sensing window based on a set of values ​​in the resource reservation period field in the resource pool configuration being used.

[0045] In scenarios 1-2, if a terminal device senses a PSCCH within the sensing window, it measures the reference signal received power (RSRP) of the PSCCH or the RSRP of the PSSCH scheduled by the PSCCH. If the measured RSRP is greater than the sidelink reference signal received power (SL-RSRP) threshold, and it is determined that the reserved resource is within the resource selection window based on the resource reservation information in the sidelink control information transmitted by the PSCCH, the corresponding resource is excluded from set A. If the remaining resources in resource set A are less than X% of the total resources before resource set A performed resource exclusion, the SL-RSRP threshold is increased by 3dB, and step 1 is performed again. In some embodiments, the possible values ​​of X are {20, 35, 50}, and the terminal device can determine the parameter X from this set of possible values ​​based on the priority of data awaiting transmission. In LTE V2X, the value of X% is fixed at 20%, while in NR V2X, the value of X% is more flexible. The possible values ​​of X% in NR V2X may be configured by the network equipment or pre-configured. In some embodiments, the value of X% is calculated on a resource pool basis.

[0046] Furthermore, the SL-RSRP thresholds mentioned above are related to the priority of the PSCCH sensed by the terminal and the priority of the data awaiting transmission by the terminal device. The terminal device uses the remaining resources after excluding the resources in set A as the candidate resource set.

[0047] Step 2: The terminal device randomly selects several resources from the candidate resource set as the transmission resources for the initial transmission and retransmission. In some embodiments, the terminal device can randomly select one or more transmission resources from resource set A with equal probability. When the terminal device selects multiple transmission resources, one or more of the following two conditions must be met.

[0048] Under Condition 1, with the exception of several exceptional circumstances, terminal equipment may allow a selected retransmission resource to be indicated by a previously transmitted first-order SCI. The exceptional circumstances include one or more of Circumstances 1 and Circumstance 2. Circumstance 1 is when, after a terminal device has excluded a resource, it is unable to select a resource from resource set A that satisfies the time domain limit. Circumstance 2 is when, due to factors such as resource preemption, congestion control, and collisions with uplink services, the terminal device abandons the transmission and the transmission resource for a retransmission does not have an indication from a previously transmitted first-order SCI.

[0049] In condition 2, for any two selected time-frequency resources, the terminal equipment must ensure that if the first transmission resource requires HARQ feedback, the two resources are separated by at least a length (period) Z in the time domain. If, when selecting resources, it is not possible to select resources that satisfy the time domain constraints (for example, if the packet delay budget (PDB) is short but the number of retransmissions is high), the terminal equipment may abandon the selection of some retransmission resources or disable HARQ feedback for some transmissions. The specific method adopted by the terminal equipment depends on the implementation of the terminal equipment.

[0050] Sensing-based resource selection method Referring to Figure 5, a terminal device can trigger resource selection or re-selection in a time slot (also called a slot) n. In some embodiments, time slot n may be the time slot in which the upper layer reports a candidate resource set to the physical layer. The resource selection window begins at n+T1 and ends at n+T2, and is represented as [n+T1, n+T2], where 0<=T1<=T proc,1 And when the subcarrier interval is 15, 30, 60, and 120 kHz, T proc,1 These are 3, 5, 9, and 17 time slots. 2min <=T2<=The remaining delay budget for the service, T 2min The set of possible values ​​is {1, 5, 10, 20}*2 μ These are time slots, where μ=0, 1, 2, and 3 correspond to subcarrier intervals of 15, 30, 60, and 120 kHz, respectively. The terminal device selects T from this set of values ​​based on the priority of the data it is waiting to transmit. 2min This determines the number of subcarriers. For example, if the subcarrier interval is 15 kHz, the terminal device will choose from a set of {1, 5, 10, 20} based on the priority of the data it is waiting to transmit. 2min To decide. 2minIf it is greater than or equal to the remaining delay budget of the service, T2 becomes equal to the remaining delay budget of the service. The remaining delay budget refers to the difference between the time corresponding to the delay requirement of the data and the current time. For example, assuming that a data packet arriving at time slot n has a delay requirement of 50 milliseconds and one time slot is 1 millisecond, if the current time is time slot n, the remaining delay budget is 50 milliseconds, and if the current time is time slot n + 20, the remaining delay budget is 30 milliseconds.

[0051] Before resource selection, the terminal device needs to perform resource sensing within the sensing window from n - T0 to n - T proc,0 and the possible values of T0 are 100 or 1100 milliseconds. When the sub - carrier spacing is 15 kHz, 30 kHz, 60 kHz, 120 kHz, T proc,0 is 1, 1, 2, 4 time slots. Usually, the terminal device senses the SCI transmitted by other terminal devices in each time slot (except its own transmission time slot). After triggering resource selection or reselection at time slot n, the terminal device can use the resource sensing results from n - T0 to n - T proc,0 The resource selection process will be described below in combination with steps a to b.

[0052] In step a, the terminal device (for example, the physical layer of the terminal device) excludes resources that are not suitable for sidelink transmission from the resource selection window based on the channel sensing results.

[0053] The terminal device sets all candidate available resources belonging to the resource pool used by the terminal device within the resource selection window as resource set A. Any one resource in set A can be denoted as R(x, y), where x and y indicate the frequency - domain position and time - domain position of the resource respectively. Also, denote the initial quantity of resources in set A as M total as described.

[0054] The specific sensing method of the terminal device can be divided into two situations: situation a-1 and situation a-2.

[0055] In situation a-1, when the terminal device does not sense and transmits data in time slot a within the sensing window, the terminal device determines whether time slot a + q * Prxlg overlaps with resource R(x, y + jPtxlg). If they overlap, resource R(x, y) is excluded from resource set A. Here, j = 0, 1, 2, 3…C - 1, and C is determined by the random counter (counter) value generated by the terminal device. Ptxlg is the number obtained by converting the terminal's resource reservation period Ptx into logical time slots. Prxlg is the number obtained by converting Prx into logical time slots, where Prx is any one of the permitted resource reservation periods within the resource pool. If Prx < Tscal and n - m <= Prxlg, then Q = ┌Tscal / Prx┐, otherwise Q = 1. Tscal is equal to the value obtained by converting T2 into milliseconds.

[0056] In situation a-2, when the terminal device senses the first SCI transmitted on the PSCCH at E(v, m) within the time slot m in the sensing window, the terminal device measures the SL-reference signal receiving power (SL-RSRP: sidelink reference signal receiving power) of the PSCCH or the SL-RSRP of the PSSCH scheduled by the PSCCH (i.e., the SL-RSRP of the associated PSSCH transmitted in the same time slot as the PSCCH).

[0057] If the measured SL-RSRP is greater than the SL-RSRP threshold and the resource reservation between transport blocks (TBs) within the resource pool used by the terminal device is activated, the terminal device assumes that it has received the first sidelink control information of the same content in time slot m+q*Prxlg. Here, q = 1, 2, 3…Q, and when Prx < Tscal and n - m <= Prxlg, Q = ┌Tscal / Prx┐, otherwise Q = 1. Tscal is equal to the value obtained by converting T2 to milliseconds. Prxlg is the number obtained by converting Prx to logical time slots, where Prx is the resource reservation period indicated by the "resource reservation period" in the first sidelink control information transmitted on the PSCCH sensed by the terminal device. The terminal device determines whether the resource indicated by the "time resource assignment" field and the "frequency resource assignment" field of the first sidelink control information received in time slot m and the Q assumed received first sidelink control information overlaps with the resource R(x, y+jPtxlg). If there is an overlap, the terminal device excludes the corresponding resource R(x, y) from set A. Here, j = 0, 1, 2, 3…C-1, and C is determined by the random counter value generated by the terminal. Ptxlg is the number obtained by converting Ptx to logical time slots, and Ptx is the resource reservation period determined by the terminal device performing resource selection.

[0058] The above RSRP threshold is determined by the priority P1 in the PSCCH sensed by the terminal device and the priority P2 of the data waiting to be transmitted by the terminal device. The configuration of the resource pool used by the terminal device includes an SL-RSRP threshold table, and the SL-RSRP threshold table includes SL-RSRP thresholds corresponding to all combinations of priorities. The configuration of the resource pool can be a network configuration or a pre-configuration. After the above resource exclusion, the remaining resources in resource set A are M totalIf the value is less than X%, the terminal device can raise the SL-RSRP threshold by 3dB and re-execute step a. The possible values ​​for X are {20, 35, 50}. The configuration of the resource pool used by the terminal device includes a correspondence between priority and the possible values ​​X above, and the terminal device can determine the value of X based on the priority of the data waiting to be transmitted and this correspondence.

[0059] The physical layer of the terminal device can report resource set A, after resource exclusion, as a candidate resource set to the higher layer, namely the terminal's media access control (MAC) layer.

[0060] In step b, the upper layer (e.g., the MAC layer) randomly selects a resource from the reported candidate resource set and sends the data. That is, the terminal device randomly selects a resource from the candidate resource set and sends the data.

[0061] The RSRP threshold mentioned above is determined by the priority P1 of the PSCCH sensed by the terminal device and the priority P2 of the data awaiting transmission by the terminal device.

[0062] Furthermore, whether a terminal device uses the measured PSCCH-RSRP or the PSCCH-RSRP scheduled by that PSCCH for comparison with the SL-RSRP threshold depends on the resource pool configuration of the resource pool used by the terminal device. Here, the resource pool configuration can be a network configuration or a pre-configured configuration.

[0063] The possible values ​​for X% are {20%, 35%, 50%}. The configuration of the resource pool used by the terminal device includes a correspondence between priority and the possible values ​​mentioned above. The terminal device determines the value of X% based on the priority of the data awaiting transmission and this correspondence. The resource pool configuration can be a network configuration or a pre-configured configuration.

[0064] Sidelink communication data transmission method Some side-link communication systems (for example, Long Term Evolution Vehicle to Everything (LTE-V2X)) support broadcast-based data transmission (hereinafter abbreviated as broadcast transmission). In broadcast transmission, the receiving terminal can be any one terminal device in the vicinity of the transmitting terminal. Using Figure 6 as an example, terminal device 1 is the transmitting terminal, and the receiving terminal corresponding to the transmitting terminal is any one terminal device in the vicinity of terminal device 1, which could be, for example, terminal devices 2 to 6 in Figure 6.

[0065] In addition to broadcast transmission, some communication systems also support unicast-based data transmission methods (hereinafter abbreviated as unicast transmission) and / or multicast-based data transmission methods (hereinafter abbreviated as multicast transmission). For example, the New Radio Vehicle to Everything (NR-V2X) network aims to support autonomous driving. Autonomous driving requires higher demands, lower latency, higher reliability, wider coverage, and more flexible resource allocation methods for data exchange between vehicles. Therefore, to improve the performance of data exchange between vehicles, NR-V2X introduces unicast and multicast transmission.

[0066] In unicast transmission, the receiving terminal typically has only one terminal device. As an example, Figure 7 shows unicast transmission between terminal device 1 and terminal device 2. Terminal device 1 may be the transmitting terminal and terminal device 2 may be the receiving terminal. Alternatively, terminal device 1 may be the receiving terminal and terminal device 2 may be the transmitting terminal.

[0067] In multicast transmission, a receiving terminal can be a terminal device within a single communication group, or it can be a terminal device within a certain transmission distance. Using Figure 8 as an example, terminal devices 1, 2, 3, and 4 constitute a single communication group. When terminal device 1 transmits data, all other terminal devices in the group (terminal devices 2 through 4) can be receiving terminals.

[0068] Unauthorized spectrum Unlicensed spectra are spectra allocated by countries and regions for use in radio equipment communications, and these spectra are generally considered shared spectra. This means that communication equipment in different communication systems can use these spectra as long as they meet the regulatory requirements set on the spectrum by the country or region, and do not need to apply to the government for a dedicated spectrum license.

[0069] To ensure that each communication device (or communication system) using unlicensed spectrum wireless communication can coexist amicably in that frequency band, some countries and regions have established legal and regulatory requirements that must be met for the use of unlicensed spectrum. For example, communication devices must follow the "Listen Before Talk (LBT)" principle. LBT means that a communication device must first perform channel sensing before transmitting a signal on a channel in the unlicensed spectrum. If the channel sensing result shows that the channel is idle, the communication device can transmit a signal using the channel in the unlicensed spectrum. If the channel sensing result shows that the channel is busy, the communication device is generally not permitted to transmit a signal using the channel in the unlicensed spectrum.

[0070] Relationships between resources The resources according to the embodiments of this application may include channels, resource block (RB) sets, and resource pools. The relationships between the three types of resources will be described below in conjunction with Figure 9.

[0071] In some embodiments, one RB set may be associated with one or more resource pools, or one resource pool may be associated with one or more RB sets. RB sets associated with different resource pools may overlap, or RB sets associated with different resource pools may be different.

[0072] As shown in Figure 9, RB set A can be associated with resource pool 1 and resource pool 2, with some resources in RB set A belonging to resources in resource pool 1 and other resources belonging to resources in resource pool 2. Resource pool 2 is associated with RB set A and RB set B, with some resources in resource pool A belonging to resources in RB set A and other parts belonging to resources in RB set B. In the solution shown in Figure 9, both resource pool 1 and resource pool 2 contain resources in resource set A.

[0073] In the solution shown in Figure 9, the resources contained in resource pool 1 and resource pool 2 do not overlap. Of course, in some embodiments, the resources contained in resource pool 1 and resource pool 2 may overlap.

[0074] A single RB set can be associated with one or more LBT channels. Using Figure 9 as an example, RB set A can be associated with channels 1 and 2, and RB set B can be associated with channels 3 and 4. Since channels can be the smallest frequency domain granularity for performing LBT, the above channels are also called LBT channels.

[0075] NR operating in the unlicensed spectrum (NR in Unlicensed Spectrum, NR-U) If a terminal device detects a consistent uplink LBT failure, it can take action as defined by the protocol. LBT detection by the terminal device can be transmitted based on each bandwidth part (BWP) and on all uplinks within that BWP. If a consistent uplink LBT failure is detected in a secondary cell (SCell), the terminal device can report the LBT failure to network equipment in a different serving cell than the SCell that detected the failure. The terminal device can report the LBT failure via a medium access control control element (MAC CE). This network equipment is either a master node (MN) for a master cell group (MCG) or a secondary node (SN) for a secondary cell group (SCG). If there are no available resources to transmit the MAC CE, the terminal device can transmit a scheduling request (SR).

[0076] If SpCell detects a consistent uplink LBT failure, the terminal device can switch to another uplink BWP (UL) configured with random access channel (RACH) resources in that cell, initiate random access, and report the failure via MAC CE. If multiple UL BWPs are available for switching, the terminal device can select one based on its implementation.

[0077] In the case of a Primary Secondary Cell (PSCell), if a consistent uplink LBT failure is detected across all UL BWPs where the RACH resource is configured, terminal equipment can declare a radio link failure (RLF) and report the failure to the MN via SCGFailureInformation.

[0078] Regarding the primary cell (PCell), if a terminal device detects an uplink BWP failure in all UL BWPs where the RACH resource is configured, the terminal device can declare an RLF (Return Link Failure).

[0079] Unlicensed sidelink (SL-U) In the NR-V2X system, the resources used by terminal devices for sidelink data transmission can be allocated by network equipment (e.g., resource allocation method in mode 1) or determined by the terminal device itself based on resource sensing results (e.g., resource selection method in mode 2). Both of these resource allocation methods are also applicable to SL-U scenarios.

[0080] In the SL-U system, after the terminal device determines the sidelink transmission resource, it must perform a Level-Based Test (LBT) before data transmission can begin. If the LBT is successful, data transmission can proceed; otherwise, data cannot be transmitted using the determined sidelink transmission resource. If the LBT fails, the terminal device may consider actions such as abandoning transmission or triggering resource reselection.

[0081] To support terminal devices in operating normally in the unauthorized spectrum, enhanced consideration for consecutive LBT failures is introduced. Terminal devices can make decisions regarding consecutive LBT failures at the MAC layer and perform recovery from consecutive LBT failures. For example, terminal devices can set a maximum number of LBT failure instructions and a timer, which can be used to determine whether to trigger consecutive LBT failures. Each time the physical layer (or physical layer entity) reports an LBT failure instruction to the MAC layer (or MAC layer entity), the MAC layer must reset and start the timer. If the number of consecutive LBT failure instructions reported by the physical layer exceeds the set maximum number, the MAC layer can trigger the consecutive LBT failure process. On the other hand, if the MAC layer does not receive any LBT failure instructions from the physical layer until the timer times out, the MAC layer can reset the counters and timers.

[0082] The above-mentioned consecutive LBT failures are also referred to as consistent LBT failures, persistent LBT failures, or continuous LBT failures, and the embodiments of this application do not specifically limit this designation.

[0083] Currently, the protocol only mentions that consecutive LBT failures can be triggered, but there are no clear specifications yet regarding the details of consecutive LBT failures.

[0084] Based on this, embodiments of the present application provide a wireless communication method and apparatus that, when detecting a continuous LBT failure, considers information related to resource granularity to determine a policy related to continuous LBT, thereby providing a clear solution for terminal equipment to perform operations related to continuous LBT failures.

[0085] The wireless communication method provided by the embodiment of this application will be described in detail below, in conjunction with Figure 10.

[0086] Referring to Figure 10, in step S1010, the terminal device determines a first policy regarding consecutive LBT failures.

[0087] The terminal device in the embodiment of this application may be a terminal device that performs sidelink communication.

[0088] In some embodiments, the detection of consecutive LBT failures can be related to resource granularity. This resource granularity may include RB sets and / or resource pools. For example, a terminal device can determine whether consecutive LBT failures have occurred in an RB set, or whether consecutive LBT failures have occurred in a resource pool.

[0089] In some embodiments, the first policy may include one or more of the following: a resource switching policy, a second policy, and a third policy. Here, the second policy may be related to the cancellation of triggered consecutive LBT failures (consecutive LBT failure state or consecutive LBT failure identifier), and the third policy may be related to the determination of consecutive LBT failures.

[0090] Below, we will first explain the third policy.

[0091] In some embodiments, the terminal device can detect the RB set and determine whether consecutive LBT failures have occurred in the RB set. Alternatively, the terminal device can detect the resource pool and determine whether consecutive LBT failures have occurred in the resource pool. Consecutive LBT failures in the RB set can be understood as consecutive LBT failures occurring in the RB set, and consecutive LBT failures in the resource pool can be understood as consecutive LBT failures occurring in the resource pool. Examples are given below to illustrate this.

[0092] In some embodiments, the third policy may include determining that consecutive LBT failures have occurred in the first RB set if the number of LBT failures in the first RB set within a first pre-configured period reaches a first pre-configured threshold. The third policy may be a policy that determines whether consecutive LBT failures have occurred in the RB set. The first pre-configured period and / or the first pre-configured threshold may be instructed by a network device to a terminal device, instructed by another terminal device to a terminal device, determined by the terminal device itself, or predefined in a protocol.

[0093] In some embodiments, whether an LBT failure has occurred in the first RB set can be determined by the physical layer of the terminal device, the number of LBT failures that have occurred in the first RB set can be recorded by the MAC layer of the terminal device, the physical layer of the terminal device can report to the MAC layer of the terminal device when an LBT failure has occurred in the first RB set, and the MAC layer of the terminal device then records the number of LBT failures that have occurred in the first RB set. The process by which the terminal device determines whether consecutive LBT failures have occurred in the first RB set will be described in detail below.

[0094] When the MAC layer receives information from the physical layer indicating that an LBT failure has occurred in the first RB set, if the first timer corresponding to the first RB set has not been started, the MAC layer can start the first timer. The first timer is also called the LBT failure timer. If the first timer has already been started, the first counter corresponding to the first RB set is incremented by 1. The first counter is also called the LBT failure counter. The MAC layer triggers resource reselection, which is triggered by an LBT failure, and the reselected resource may be a resource within the current RB set (without switching the RB set). If the value recorded by the first counter exceeds a first preset threshold before the first timer times out, it can be determined that a series of LBT failures have occurred in the first RB set. If the value recorded by the first counter is less than the first preset threshold when the first timer times out, the first counter is set to zero.

[0095] In some embodiments, if a series of LBT failures occur in a first RB set, the MAC layer can instruct the physical layer of the series of LBT failures and / or the RB set in which the series of LBT failures occurred. If the MAC layer instructs the physical layer of a series of LBT failures, the physical layer can determine the RB set in which the series of LBT failures occurred based on previously detected RB sets.

[0096] Of course, in some embodiments, the physical layer can also determine whether consecutive LBT failures have occurred in the RB set. The physical layer can maintain its own timers and counters, record the number of LBT failures that have occurred in the RB set, and determine whether consecutive LBT failures have occurred in the RB set.

[0097] In some embodiments, the third policy may include determining that consecutive LBT failures have occurred in the first resource pool if the number of LBT failures in the RB set associated with the first resource pool within a second pre-configured period reaches a second pre-configured threshold. The third policy may be a policy that determines whether consecutive LBT failures have occurred in the resource pool. The second pre-configured time and / or second pre-configured threshold may be instructed by a network device to a terminal device, instructed by another terminal device to a terminal device, determined by the terminal device itself, or predefined in a protocol.

[0098] An RB set associated with a first resource pool may include one or more RB sets. In some embodiments, an RB set associated with a first resource pool means that some or all of the resources in the RB set belong to the resources in the first resource pool.

[0099] In some embodiments, the physical layer of the terminal device may determine whether an LBT failure has occurred in the RB set associated with the first resource pool, and the number of LBT failures in the first resource pool may be recorded by the MAC layer of the terminal device. The physical layer of the terminal device can report to the MAC layer of the terminal device when an LBT failure occurs in the RB set associated with the first resource pool, and the MAC layer of the terminal device then records the number of LBT failures in the RB set associated with the first resource pool. The process by which the terminal device determines whether consecutive LBT failures have occurred in the first resource pool will be described in detail below.

[0100] When the MAC layer receives information that an LBT failure has occurred in the RB set associated with the first resource pool indicated by the physical layer, the MAC layer can start the second timer corresponding to the first resource pool if it has not already started. The second timer is also called the LBT failure timer. If the second timer has already started, the MAC layer increments the second counter corresponding to the first resource pool by 1. The second counter is also called the LBT failure counter. The MAC layer triggers resource reselection, which is triggered by the LBT failure. If the value recorded by the second counter exceeds the second preset threshold before the second timer times out, it can be determined that consecutive LBT failures have occurred in the first resource pool. If the value recorded by the second counter is less than the second preset threshold when the second timer times out, the MAC layer sets the second counter to zero.

[0101] Of course, in some embodiments, the physical layer can also determine whether consecutive LBT failures have occurred in the resource pool. The physical layer can maintain its own timers and counters, record the number of LBT failures that have occurred in the RB set associated with the resource pool, and thereby determine whether consecutive LBT failures have occurred in the resource pool.

[0102] In some embodiments, an LBT failure occurring in an RB set associated with the first resource pool can refer to an LBT failure occurring in any one RB set associated with the first resource pool, or to an LBT failure occurring in one or more RB sets associated with the first resource pool. For example, when the physical layer first detects an LBT failure in RB set a, it instructs the MAC layer, which increments a second counter by 1. When the physical layer performs a second LBT failure detection, it may detect either RB set a or RB set b. Assuming the physical layer detects RB set b and detects an LBT failure in RB set b, the physical layer instructs the MAC, which can increment a second counter by 1. In other words, the second counter can count all RB sets corresponding to the first resource pool without distinguishing which RB set experienced the LBT failure.

[0103] In some embodiments, if consecutive LBT failures occur in the first resource pool, the MAC layer can instruct the physical layer on the consecutive LBT failures and / or the resource pool on which the consecutive LBT failures occurred. If the MAC layer instructs the physical layer on consecutive LBT failures, the physical layer can determine the resource pool on which the consecutive LBT failures occurred based on the resource pools associated with previously detected RB sets.

[0104] The embodiments of this application do not specifically limit the method for determining whether an LBT failure has occurred in an RB set. In some embodiments, when an RB set is associated with one channel, it is determined that an LBT failure has occurred in the RB set if an LBT failure occurs in that channel. In other embodiments, when an RB set is associated with multiple channels, an LBT failure in the RB set is related to second information, which may include one or more of the following: an LBT failure has occurred in all channels associated with the RB set; an LBT failure has occurred in at least one channel associated with the RB set; or an LBT failure has occurred in a channel where resources for data transmission are located. Resources for data transmission may refer to resources necessary for a terminal device to transmit data, or resources selected by the terminal device, or resources scheduled by a network device. The channel where resources for data transmission are located may be one or more of the channels associated with the RB set. The above channels are also called LBT channels.

[0105] For example, when an RB set is associated with multiple channels, the terminal device (or the physical layer of the terminal device) determines that an LBT failure has occurred in the RB set if an LBT failure occurs across all of those multiple channels. Alternatively, when an RB set is associated with multiple channels, the terminal device (or the physical layer of the terminal device) determines that an LBT failure has occurred in the RB set if an LBT failure occurs in at least one of those multiple channels. In other words, the terminal device can determine that an LBT failure has occurred in its RB set if an LBT failure occurs in any one of those multiple channels. Of course, in some embodiments, the terminal device may also determine that a series of LBT failures have occurred in the RB set if LBT failures occur in a predetermined number of those multiple channels. Furthermore, when an RB set is associated with multiple channels, the terminal device (or the physical layer of the terminal device) determines that an LBT failure has occurred in the RB set if an LBT failure occurs in the channel where the resources for data transmission are located.

[0106] The embodiments of this application do not specifically limit the channels associated with an RB set. For example, channels associated with an RB set may belong to some or all of the resources of that RB set.

[0107] In some embodiments, the second piece of information described above relates to whether a guardband is configured on the terminal device. This guardband may refer to a guardband between two channels. For example, if a guardband is configured on the terminal device, the second piece of information may include that LBT failures have occurred on all channels associated with the RB set. Alternatively, for example, if a guardband is not configured on the terminal device, the second piece of information may include that LBT failures have occurred on at least one channel associated with the RB set.

[0108] Resource switching policy In some embodiments, if a series of LBT failures occur in a terminal device, the terminal device may perform resource switching to guarantee the transmission performance of the terminal device. The terminal device may perform resource switching based on a resource switching policy. The resource switching policy may also be called another policy. That is, the resource switching policy may be replaced with other terms, but the embodiments of this application are not specifically limited thereto. The resource switching policy will be described in detail below.

[0109] As one example, a resource switching policy may include one or more of the following: switching resource pools, switching RB sets, and switching time-frequency resources. For example, a terminal device may switch RB sets if LBT failures occur in an RB set (e.g., switching from a first RB set to a second RB set). Also, for example, a terminal device may switch resource pools if consecutive LBT failures occur in an RB set (e.g., switching from a first resource pool to a second resource pool). Here, the first resource pool may be the resource pool associated with the RB set where the consecutive LBT failures occurred. The second resource pool is different from the first resource pool. In some embodiments, the second resource pool may or may not be associated with the RB set where the consecutive LBT failures occurred. Also, for example, a terminal device may switch time-frequency resources if consecutive LBT failures occur in an RB set (e.g., switching from a first time-frequency resource to a second time-frequency resource). Here, the first time-frequency resource may be a time-frequency resource associated with the RB set where the consecutive LBT failure occurred (for example, the first time-frequency resource may be a resource in the RB set where the consecutive LBT failure occurred). The second time-frequency resource may be a resource other than the resource in the RB set where the LBT failure occurred. For example, the first time-frequency resource may be a resource in the first RB set, the second time-frequency resource may be a resource in the second RB set, and the first RB set may be the RB set where the consecutive LBT failure occurred. When selecting a time-frequency resource, the terminal device (or the MAC layer of the terminal device) may select a resource on an RB set that is not marked as having consecutive LBT failures. The above time-frequency resource switching policy may be a policy proposed when consecutive LBT failures occur in an RB set.

[0110] As another example, a resource switching policy may include one or more of the following: switching resource pools, switching time-frequency resources, etc. For example, a terminal device may switch resource pools if consecutive LBT failures occur in a resource pool (e.g., switching from the first resource pool to the second resource pool). Also, for example, a terminal device may switch time-frequency resources if consecutive LBT failures occur in a resource pool (e.g., switching from the first time-frequency resource to the second time-frequency resource). Here, the first time-frequency resource may be a time-frequency resource associated with the resource pool where the consecutive LBT failures occurred (e.g., the first time-frequency resource may be a resource in the resource pool where the consecutive LBT failures occurred). The second time-frequency resource may be a resource other than the resource pool where the LBT failures occurred. For example, the first time-frequency resource may be a resource in the first resource pool, the second time-frequency resource may be a resource in the second resource pool, and the first resource pool may be the resource pool where the consecutive LBT failures occurred. When selecting a time-frequency resource, a terminal device (or the MAC layer of the terminal device) may select a resource on an RB set that is not marked as having consecutive LBT failures. The above time-frequency resource switching policy may be proposed when consecutive LBT failures occur in the resource pool.

[0111] In some embodiments, after a terminal device switches to a new resource pool, the new resource pool may still be associated with the RB set that experienced consecutive LBT failures.

[0112] The following describes the conditions under which terminal devices perform resource switching.

[0113] If the resource switching policy includes switching resource pools, terminal equipment can switch resource pools if the first condition is met. Here, the first condition may be whether consecutive LBT failures have occurred in the RB set, or may relate to one or more pieces of information from the data transmission requirements. The data transmission requirements may refer to several relevant requirements of the protocol concerning the transmission resources. For example, the data transmission requirements may include DRX requirements and / or minimum time interval requirements.

[0114] In some embodiments, the above consecutive LBT failures may refer to consecutive LBT failures that were triggered but not canceled.

[0115] In some implementations, if consecutive LBT failures occur in the RB set, the terminal equipment switches resource pools.

[0116] For example, the first condition may include consecutive LBT failures occurring in one or more RB sets associated with the current resource pool. That is, if consecutive LBT failures occur in one or more RB sets associated with the current resource pool, the terminal device switches the resource pool. Alternatively, the first condition may include consecutive LBT failures occurring in all RB sets associated with the current resource pool. That is, if consecutive LBT failures occur in all RB sets associated with the current resource pool, the terminal device switches the resource pool. Furthermore, the first condition may include consecutive LBT failures occurring in a predetermined number of RB sets associated with the current resource pool. That is, if consecutive LBT failures occur in a predetermined number of RB sets associated with the current resource pool, the terminal device switches the resource pool. This predetermined number may be indicated by the network device or predefined.

[0117] In some embodiments, the first condition may include that the number of remaining resources in the resource pool is less than or equal to a preset threshold. If the number of remaining resources in the resource pool is less than or equal to a preset threshold, i.e., if no resource that satisfies the condition can be selected within the resource pool, the terminal device can switch resource pools. Here, the remaining resources belong to resources that have not experienced consecutive LBT failures and / or resources that satisfy the data transmission requirements. The remaining resources may include time-frequency resources and / or RB resources. In other words, the resource division granularity in embodiments of this application may be time-frequency resources and / or RB sets.

[0118] To illustrate with an example, if, within a resource pool, it is not possible to select a resource that meets the data transmission requirements, excluding the resources associated with the RB set experiencing consecutive LBT failures, the terminal device can switch resource pools.

[0119] The resource pool switching described above is determined by the MAC layer. If the first condition is met, the MAC layer can trigger a resource pool switch or a new resource selection. The MAC layer can instruct the physical layer to use the resource pool after the switch. The resource pool after the switch is different from the resource pool before the switch.

[0120] If the number of remaining resources in the resource pool is greater than a preset threshold, i.e., if a sufficient number of resources can be selected from the resource pool, the MAC layer can send the selected resources and their corresponding pending data packets (e.g., MAC protocol data units (PDUs)) to the physical layer.

[0121] In some embodiments, if the resource switching policy includes switching RB sets, terminal equipment can switch RB sets if consecutive LBT failures occur on the current RB set. The above switching policy applies to situations where consecutive LBT failures occur on an RB set.

[0122] In some embodiments, if the resource switching policy includes switching of time-frequency resources, terminal equipment can switch time-frequency resources when consecutive LBT failures occur on the current RB set. The above switching policy applies to situations where consecutive LBT failures occur on the RB set.

[0123] In some embodiments, if the resource switching policy includes switching resource pools, terminal devices can switch resource pools when consecutive LBT failures occur in the current resource pool. The above switching policy applies to situations where consecutive LBT failures occur in a resource pool.

[0124] In some embodiments, if the resource switching policy includes switching of time-frequency resources, terminal equipment can switch time-frequency resources when consecutive LBT failures occur in the current resource pool. The above switching policy applies to situations where consecutive LBT failures occur on the resource pool.

[0125] The above-mentioned time-frequency resources may be time-frequency resources in an RB set or time-frequency resources in a resource pool. There are various ways in which time-frequency resources are partitioned in the time domain and frequency domain, and the embodiments of this application are not specifically limited thereto. For example, the partitioning granularity of time-frequency resources in the time domain may include symbols, time slots, subframes, etc. The partitioning granularity of time-frequency resources in the frequency domain may include channels, subchannels, RBs, physical resource blocks (PRBs), etc.

[0126] The second policy is explained below.

[0127] In some embodiments, the second policy may include performing a cancellation operation for consecutive LBT failures (e.g., canceling consecutive LBT failures for the triggered first resource) if the second condition is met. Here, the second condition may include one or more of the following: the terminal device has performed the first operation, or the terminal device has sent a consecutive LBT failure report. The first operation is related to resource switching.

[0128] For example, if a terminal device performs the first operation, it can perform a cancellation operation for consecutive LBT failures. Also, for example, if a terminal device sends a consecutive LBT failure report, it can perform a cancellation operation for consecutive LBT failures. Furthermore, for example, if a terminal device performs the first operation AND sends a consecutive LBT failure report, it can perform a cancellation operation for consecutive LBT failures.

[0129] In some embodiments, the transmission of a continuous LBT failure report by a terminal device may include the transmission of a continuous LBT failure report by the terminal device to a network device and / or the transmission of a continuous LBT failure report by the terminal device to a peer device.

[0130] The embodiments of this application do not specifically limit the first operation. For example, the first operation may include a resource switchover. Alternatively, the first operation may include a successful LBT on the switched-out resource. Alternatively, the first operation may include a successful data transmission on the switched-out resource. Alternatively, the first operation may include a triggering of a unicast link RLF. The above first operations may be used individually or in combination with each other, and the embodiments of this application are not specifically limited thereto.

[0131] The following provides an example of the conditions under which a terminal device performs a cancellation operation for consecutive LBT failures.

[0132] For example, a terminal device can cancel a series of LBT failures if it performs a resource switch and successfully transmits data within the switched-out resource. Also, for example, a terminal device can cancel a series of LBT failures if it performs a resource switch and successfully performs LBT within the switched-out resource. Furthermore, for example, a terminal device can cancel a series of LBT failures if the RLF of a unicast link is triggered. Also, for example, a terminal device can cancel a series of LBT failures if it performs a resource switch, successfully transmits data within the switched-out resource, and sends a series of LBT failure reports. Furthermore, for example, a terminal device can cancel a series of LBT failures if it performs a resource switch, successfully performs LBT within the switched-out resource, and sends a series of LBT failure reports. Also, for example, a terminal device can cancel a series of LBT failures if the RLF of a unicast link is triggered and the terminal sends a series of LBT failure reports.

[0133] A unicast link RLF may be triggered by one or more of the following: a failed LBT on the target resource after the failover; the target resource after the failover has already triggered a series of LBT failures; or a failed data transmission on the target resource after the failover. The target resource may be all configured resources or a predetermined number of resources. Configured resources may refer to resources configured by network equipment. Target resources may include resource pools and / or RB sets.

[0134] For example, if a terminal device tries all configured resource pools or RB sets and LBT fails or data transmission fails, an RLF (Routine Limit Break) is triggered on the unicast link. Also, for example, if a terminal device performs N resource switches and LBT fails or data transmission fails, an RLF is triggered on the unicast link. The number N may be configured by the network equipment or predefined by the protocol. The resource switches may include one or more of resource pool switches, RB set switches, and time-frequency resource switches. Also, for example, an RLF is triggered on the unicast link if all configured resources have already triggered consecutive LBT failures, or if N of the configured resources have already triggered consecutive LBT failures.

[0135] The embodiments of this application do not specifically limit the first resource. For example, the first resource may include one or more RB sets associated with one or more resource pools before the switchover, or RB sets before the switchover, or resource pools before the switchover.

[0136] In some embodiments, the first resource may include RB sets associated with one or more resource pools before the switchover. For example, if consecutive LBT failures occur in an RB set and a terminal device performs a resource pool switchover, the first resource may include RB sets associated with one or more resource pools before the switchover. These one or more resource pools may be resource pools associated with the RB set where the consecutive LBT failures occurred.

[0137] In some embodiments, the first resource may include one or more RB sets prior to the switchover. For example, if consecutive LBT failures occur in an RB set and a terminal device performs an RB set switchover, the first resource may include one or more RB sets prior to the switchover. These one or more RB sets may be the RB sets in which the consecutive LBT failures occurred.

[0138] In some embodiments, the first resource may include one or more resource pools prior to the switchover. For example, if consecutive LBT failures occur in a resource pool and a terminal device performs a resource pool switchover, the first resource may include one or more resource pools prior to the switchover. These one or more resource pools may be the resource pools where the consecutive LBT failures occurred.

[0139] In some embodiments, if the second condition includes the triggering of the RLF on the unicast link, the first resource may include the target resource described above.

[0140] In some embodiments, if the first condition includes that a terminal device has sent a series of LBT failure reports, the first resource includes a resource corresponding to the sent series of LBT failures.

[0141] The following provides specific examples of situations in which terminal equipment cancels consecutive LBT failures triggered by the device.

[0142] In some embodiments, a terminal device may cancel consecutive LBT failures in the RB set associated with one or more resource pools before the switch if it has performed a resource pool switch or has already triggered a new resource selection, or if it has performed a resource pool switch and LBT has succeeded or data transmission has succeeded in the new resource pool.

[0143] In some embodiments, the terminal device can trigger an RLF on the unicast link and cancel consecutive LBT failures in all RB sets associated with all resource pools if LBT fails, data transmission fails, or all consecutive LBT failures occur in all configured resource pools, or the terminal device can trigger an RLF on the unicast link and cancel consecutive LBT failures in all RB sets associated with a predetermined number of resource pools if LBT fails or data transmission fails in a predetermined number of resource pools.

[0144] In some embodiments, if a terminal device experiences consecutive LBT failures in an RB set and has performed an RB set switch or already triggered a new resource selection, it may cancel the consecutive LBT failures in one or more RB sets prior to the switch. Alternatively, if a terminal device performs an RB set switch and LBT is successful or data transmission is successful in the RB set after the switch, it may cancel the consecutive LBT failures in one or more RB sets prior to the switch.

[0145] In some embodiments, the terminal device can trigger a unicast link RLF and cancel the consecutive LBT failures in all RB sets if consecutive LBT failures occur in an RB set and LBT is unsuccessful or data transmission is unsuccessful in all configured RB sets, or if all consecutive LBT failures occur. Alternatively, the terminal device can trigger a unicast link RLF and cancel the consecutive LBT failures in a predetermined number of RB sets if LBT is unsuccessful or data transmission is unsuccessful in a predetermined number of RB sets.

[0146] In some embodiments, if a terminal device experiences consecutive LBT failures in a resource pool and has performed a resource pool switch or already triggered a new resource selection, it may cancel the consecutive LBT failures on the RB sets associated with one or more resource pools prior to the switch. Alternatively, if a resource pool switch is performed and LBT is successful or data transmission is successful in the new resource pool, the terminal device may cancel the consecutive LBT failures on the RB sets associated with one or more resource pools prior to the switch.

[0147] In some embodiments, a terminal device can trigger a unicast link RLF and cancel the consecutive LBT failures in all resource pools if consecutive LBT failures occur in a resource pool and LBT fails to succeed or data transmission fails in all configured resource pools, or if all consecutive LBT failures occur. Alternatively, a terminal device can trigger a unicast link RLF and cancel the consecutive LBT failures on a predetermined number of resource pools if LBT fails to succeed or data transmission fails in a predetermined number of resource pools.

[0148] The cancellation operation of the consecutive LBT failures described above can be performed by the MAC layer. In some embodiments, the MAC layer may transmit a first instruction to the physical layer, which is used to cancel consecutive LBT failures and / or to instruct which resources to cancel consecutive LBT failures. For example, the first instruction can be used to instruct the cancellation of consecutive LBT failures, and after receiving the first instruction, the physical layer can determine which resources' consecutive LBT failure status to cancel based on the LBT failure instructions previously reported to the MAC layer. Alternatively, for example, the first instruction can be used to instruct the cancellation of a resource where consecutive LBT failures have occurred, i.e., the first instruction can directly instruct which resources' consecutive LBT failure status to cancel. Resources in this application may include RB sets and / or resource pools.

[0149] Resource Configuration In some embodiments, the selected resource for data transmission from a terminal device is determined based on second instruction information. The selected resource may, for example, be a resource for data awaiting transmission. The second instruction information can be used to indicate one or more of the following: information about a target resource pool, information about a target RB set, which is determined based on information related to consecutive LBT failures.

[0150] In some embodiments, the second instruction information can be transmitted to the physical layer by the MAC layer. For example, the MAC layer can instruct the physical layer to provide the second instruction information during the process of performing resource selection at the physical layer. In some embodiments, when the MAC layer instructs the physical layer to provide information about the target resource pool, it can consider information about resources where consecutive LBT failures have occurred. In other embodiments, the MAC layer can also directly instruct the physical layer to provide information about the RB set.

[0151] In some embodiments, the target resource pool is associated with an RB set or resource pool that has not triggered at least one consecutive LBT failure. That is, the target resource pool belongs to a resource in which at least one resource is available. For example, the target resource pool belongs to a resource in an RB set in which at least one resource has not experienced consecutive LBT failures.

[0152] In some embodiments, the target resource pool includes resource pools that have not triggered at least one consecutive LBT failure.

[0153] In addition, resource information from consecutive LBT failures can also be considered in resource selection on unauthorized spectra triggered under circumstances other than those described in the embodiments of this application.

[0154] In some embodiments, the target RB set may include one or more of the selected RB sets and the RB sets where consecutive LBT failures occurred. In some embodiments, the selected RB set may refer to the RB set where consecutive LBT failures occurred or an RB set selected based on the resource pool. For example, the selected RB set may not include the RB set where consecutive LBT failures occurred. Also, for example, the selected RB set may not include the RB set associated with the resource pool where consecutive LBT failures occurred. The above-described selected RB set applies to situations where consecutive LBT failures occur on an RB set.

[0155] In some embodiments, the second instruction information can be used to specify one or more parameters, such as information about the target resource pool, information about the selected RB set, and the RB set where consecutive LBT failures occurred. The above second instruction information applies to situations where consecutive LBT failures occur in an RB set. The second instruction information can be used to specify one or more parameters, such as information about the target resource pool and information about the selected RB set. The above second instruction information applies to situations where consecutive LBT failures occur in a resource pool.

[0156] In some embodiments, the second instruction information may include one or more of the following: transmission data-related information, currently available channel occupancy time (COT) information, coordination information between received UEs, and SL DRX information. Transmission data-related information may include one or more of the following: required resource size, number of retransmissions, priority, etc. Available COT information may include COT time-related information (e.g., remaining time, start time, end time, etc.).

[0157] The method for determining the selected resources described above is explained below. In some embodiments, the selected resources can be transmitted to the physical layer by the MAC layer. The selected resources can be determined by the MAC layer based on a second resource, and the second resource can be determined by the physical layer performing resource selection based on the second instruction information.

[0158] In some embodiments, the physical layer can perform resource selection based on second instruction information. When performing resource selection, the physical layer can perform resource selection according to the resource sensing method described above. In some embodiments, the physical layer can exclude unavailable resources and obtain an available resource set A.

[0159] In some embodiments, the second resource can be determined based on one or more of the following: resources in the target resource pool, resources in the selected RB set, and resources excluding those that have experienced consecutive LBT failures.

[0160] In some embodiments, if the parameters indicated by the second instruction information include target resource pool information, set A may be a resource set obtained based on the target resource pool. For example, the physical layer can perform resource sensing on the resources in the target resource pool to obtain set A. If the parameters indicated by the second instruction information include a selected RB set, set A may be a resource set obtained based on the selected RB set. For example, the physical layer can perform resource sensing on the resources in the selected RB set to obtain set A. If the parameters indicated by the second instruction information include an RB set where consecutive LBT failures occurred, set A may be a resource set obtained by excluding the RB set where consecutive LBT failures occurred.

[0161] The above embodiments can be used individually or in combination with each other. For example, the physical layer can obtain resource set A by performing resource sensing on resources in the target resource pool and excluding RB sets where consecutive LBT failures have occurred. Alternatively, for example, the physical layer can obtain resource set A by performing sensing on resources in a selected RB set and excluding RB sets where consecutive LBT failures have occurred. The RB sets where consecutive LBT failures have occurred may be determined by the physical layer based on previous LBT detection results, or they may be indicated by second instruction information.

[0162] In some embodiments, the physical layer can report resource set A to the MAC layer. The MAC layer can then select resources based on resource set A reported by the physical layer.

[0163] In some embodiments, the MAC layer can perform resource selection within resource set A, for example, by selecting resources on RB sets that have not been marked as having consecutive LBT failures. Of course, if the physical layer has already excluded resources on RB sets where consecutive LBT failures have occurred when determining resource set A, the MAC layer can perform resource selection directly within resource set A. Also, as mentioned above, if the MAC layer can select a sufficient number of resources from resource set A, the MAC layer can send the selected resources (also called resources awaiting transmission) and the corresponding data packets awaiting transmission to the physical layer. If the MAC layer cannot select a sufficient number of resources that meet the criteria from resource set A, the MAC layer can trigger a resource pool switch or a new resource selection. For example, the MAC layer can instruct the physical layer to use the resource pool after the switch. The physical layer can then re-execute resource selection based on the resource pool after the switch. The above operations are applicable to situations where consecutive LBT failures have occurred on an RB set and the terminal equipment has performed an RB set switch.

[0164] In some embodiments, the MAC layer can perform resource selection on resource set A, for example, by selecting resources on RB set that are not marked as consecutive LBT failures. If the MAC layer can select a sufficient number of resources from resource set A, the MAC layer can send the selected resources (also called pending resources) and the corresponding pending data packets to the physical layer. The above operation can be applied to situations where consecutive LBT failures occur on RB set and the terminal device has performed a resource pool switch.

[0165] In some embodiments, the MAC layer can perform resource selection in resource set A and transmit the selected resource (also called a resource awaiting transmission) and the corresponding data packet awaiting transmission to the physical layer. The above operation can be applied to situations where consecutive LBT failures occur in the resource pool and the terminal device has switched to a different resource pool.

[0166] The physical layer can perform LBT detection on resources waiting to transmit, as instructed by the MAC layer, before transmitting data packets waiting to transmit. If LBT is successful, it transmits the data packets waiting to transmit. If LBT fails, it instructs the MAC layer of the LBT failure and / or the RB set on which the LBT failure occurred. Furthermore, as described above, the MAC layer can, based on the instructions from the physical layer, perform counting and timers on the RB set that transmitted the LBT failure to determine whether that RB set triggered a series of LBT failures.

[0167] In some embodiments, if consecutive LBT failures occur in an RB set, the MAC layer can trigger a new resource selection. For example, the MAC layer can direct the physical layer to a resource pool. This resource pool may be the same as the previous resource pool (i.e., the reselected resource is in another available RB set in the current resource pool, and the resource pool is the non-switched resource pool), or it may be different from the previous resource pool (i.e., the reselected resource is in another available RB set in another resource pool, and the resource pool is the switched-out resource pool).

[0168] The new resource selection process may be triggered by consecutive LBTs in a single RB set. This resource selection may take place within the current resource pool (if there are RB sets in the current resource pool that have not yet triggered consecutive LBT failures). Alternatively, it may take place in another resource pool. The specific resource pool in which the resource selection is performed is determined by the implementation of the terminal device.

[0169] In some embodiments, if consecutive LBT failures occur in an RB set, the MAC layer can trigger a new resource selection. For example, the MAC layer can instruct the physical layer to select a new RB set, which is the RB set after the switchover.

[0170] In the embodiments of this application, the RB set in which consecutive LBT failures occurred may refer to the RB set of consecutive LBT failures that were triggered but not canceled. The resource pool in which consecutive LBT failures occurred may refer to the resource pool of consecutive LBT failures that were triggered but not canceled.

[0171] The methods of the embodiments described in this application will be explained in detail below, along with three examples. These three examples are provided to facilitate understanding of this application and are not intended to limit it. Furthermore, these three examples can be used in combination with each other, provided there are no conflicts.

[0172] Example 1 Figure 11 illustrates a scenario where consecutive LBT failures occur in an RB set, and the resource switching policy switches resource pools. For example, if all resources in a resource pool are marked as consecutive LBT failures, the resource pool is replaced.

[0173] Referring to Figure 11, in step S1102, the MAC layer triggers resource selection or resource re-selection. The MAC layer can trigger the physical layer to perform resource selection and simultaneously send second instruction information to the physical layer.

[0174] The second instruction information can be used to specify one or more parameters, such as transmission data-related information, currently available COT information, received IUC information, SL DRX information, target resource pool information, selected RB set information, and RB set information where consecutive LBT failures occurred. Here, transmission data-related information may include one or more of the required resource size, number of retries, priority, etc. Available COT information may include COT time-related information (e.g., remaining time, start time, end time, etc.). Target resource pool information can be determined based on the RB set where consecutive LBT failures occurred. The resource pool selected by the MAC layer must be associated with an RB set that has not triggered at least one consecutive LBT failure. The selected RB set may consider the RB set that triggered the consecutive LBT failure; that is, the selected RB set may exclude RB sets of consecutive LBT failures that were triggered but not canceled.

[0175] In step S1104, the physical layer performs resource selection. Based on the second instruction information, the physical layer selects resources, excludes unavailable resources, and obtains the available resource set A.

[0176] If the second instruction indicates a target resource pool, resource set A is obtained based on the resources in that target resource pool. If the second instruction indicates a selected RB set, resource set A is obtained based on the resources in the selected RB set. If the second instruction indicates a resource where consecutive LBT failures have occurred, resource set A is obtained by excluding the RB set where consecutive LBT failures have occurred.

[0177] In step S1106, the physical layer reports resource set A to the MAC layer.

[0178] In step S1108, the MAC layer selects resources based on resource set A reported by the physical layer.

[0179] The MAC layer can consider RB sets of consecutive LBT failures that have been triggered but not canceled when making resource selection. Specifically, the MAC layer can select resources (also called time-frequency resources) from RB sets that have not been marked as consecutive LBT failures. After a terminal device switches to a new resource pool, the new resource pool may still be associated with RB sets that have experienced consecutive LBT failures, and it is understood that this situation must also be considered when making resource selection.

[0180] In step S1110, the MAC layer determines whether there are any resources that can be selected. For example, the MAC layer can determine whether it can select resources that satisfy a sufficient number of conditions. If the MAC layer can select resources that satisfy a sufficient number of conditions, step S1112 is executed. If the MAC layer cannot select resources that satisfy a sufficient number of conditions (1114), step S1126 is executed.

[0181] In step S1112, the MAC layer can send transmission-related information to the physical layer, such as selected resources and data packets awaiting transmission (e.g., MAC PDUs).

[0182] In step S1114, the physical layer can perform LBT detection on the resource selected by the MAC layer before transmitting data. If LBT is successful, the data is transmitted. If LBT fails, step S1116 is executed.

[0183] In step S1116, the physical layer sends an LBT failure instruction to the MAC layer. Using RB set 1 as an example, the physical layer can send an LBT failure instruction for RB set 1 to the MAC layer.

[0184] If RB set 1 is associated with multiple channels, the LBT failure instruction for RB set 1 can be sent in at least one of the following situations: all channels have transmitted an LBT failure; an LBT failure has occurred in at least one channel; or an LBT failure has occurred in the channel on which the resources used for data transmission are located. Specifically, the situation in which the LBT failure instruction for RB set 1 is sent depends on whether a guard band is configured on the terminal equipment. If a guard band is configured on the terminal equipment, the LBT failure instruction for RB set 1 can be sent if all channels have transmitted an LBT failure. If a guard band is not configured on the terminal equipment, the LBT failure instruction for RB set 1 can be sent if an LBT failure occurs in at least one channel.

[0185] In step S1118, after the MAC layer receives an LBT failure instruction for RBset1, it starts the RBset1 timer if it has not already started, and if it has already started, it increments the value of the RBset1 counter by 1.

[0186] Furthermore, the MAC layer can also trigger resource reselection. This resource reselection is triggered by an LBT failure.

[0187] In step S1120, when the RB set 1 timer times out, it is determined whether the value of the RB set 1 counter is greater than a preset threshold.

[0188] In step S1122, if the value of the RB set 1 counter is greater than a preset threshold, it is determined that consecutive LBT failures have occurred in RB set 1.

[0189] The MAC layer can trigger a new resource selection. For example, it can return to step S1102 and re-execute it. The MAC layer can redirect the physical layer to a resource pool, which may be the previous resource pool (i.e., the current resource pool) or a new resource pool.

[0190] The new resource selection may be triggered by consecutive LBT failures in a single RB set. If the current resource pool has associated RB sets that have not yet triggered consecutive LBT failures, the resource selection can be performed within the current resource pool, or it can be performed within another resource pool.

[0191] In step S1124, if the RB set 1 timer times out and the value of the RB set 1 counter has not reached a preset threshold, the RB set 1 counter is set to zero.

[0192] In step S1126, the MAC layer triggers a resource pool switch or a new resource selection. For example, the process can be returned to and re-executed in step S1102. The MAC layer can then re-instruct the physical layer to use a resource pool, which is the switched-over resource pool and is different from the previous resource pool.

[0193] In step S1128, after the resource pool switchover, the MAC layer can cancel consecutive LBT failures for triggered but uncancelled RB sets.

[0194] If a new resource selection or resource pool switch has already been triggered, and an LBT has succeeded or data transmission has succeeded within the new resource pool, the terminal device may cancel any consecutive LBT failures that were triggered but not canceled on the RB set associated with one or more resource pools prior to the switch.

[0195] If the terminal device scans all configured resource pools and LBT fails or data transmission fails, trigger RLF on all unicast links and cancel consecutive LBT failures on triggered and uncancelled RB sets.

[0196] If the terminal device fails to switch over N times (reaching the set number of times) and LBT fails, or if data transmission fails, trigger the RLF on all unicast links and cancel any consecutive LBT failures on triggered and uncancelled RB sets.

[0197] When a terminal device is in a radio resource control (RRC) connection state, the connected terminal device can send a continuous LBT failure report (for example, by sending a continuous LBT failure report to a network device or peer device). Furthermore, a terminal device sending a continuous LBT failure report can also trigger a continuous LBT failure cancellation operation. In other words, a terminal device can trigger a continuous LBT failure cancellation operation (release operation) when a resource switch occurs, and it can also trigger a continuous LBT failure cancellation operation when it sends a continuous LBT failure report. Therefore, it is necessary to standardize how to perform these two continuous LBT failure cancellation operations.

[0198] Based on this, embodiments of the present application propose that a terminal device triggers a cancellation operation for consecutive LBT failures only after completing the two operations described above. For example, in the event of consecutive LBT failures on a triggered RB set, the terminal device will not trigger a cancellation operation for consecutive LBT failures until it has sent a consecutive LBT failure report for that RB set and performed a resource pool switchover. Alternatively, the terminal device may trigger a cancellation operation for consecutive LBT failures after completing any one of the two operations described above. For example, the terminal device may choose to send a consecutive LBT failure report or switch resource pools, and after completing the corresponding operation, it may trigger a cancellation operation for consecutive LBT failures.

[0199] After a cancellation operation for consecutive LBT failures is triggered, the MAC layer can instruct the physical layer to cancel the consecutive LBT failures or cancel (release) the RB set associated with the consecutive LBT failures.

[0200] Example 2 Figure 12 illustrates a situation where consecutive LBT failures occur in an RB set, and the resource switching policy switches the RB set. For example, if an RB set is marked as having consecutive LBT failures, the RB set is replaced.

[0201] Referring to Figure 12, in step S1202, the MAC layer triggers resource selection or resource re-selection. Simultaneously with triggering the physical layer to perform resource selection, the MAC layer can send second instruction information to the physical layer.

[0202] The second instruction information can be used to specify one or more parameters, such as transmission data-related information, currently available COT information, received IUC information, SL DRX information, target resource pool information, selected RB set information, and RB set information where consecutive LBT failures occurred. Here, transmission data-related information may include one or more pieces of information such as required resource size, number of retries, and priority. Available COT information may include COT time-related information (e.g., remaining time, start time, end time). Target resource pool information can be determined based on the RB set where consecutive LBT failures occurred. The resource pool selected by the MAC layer must be associated with an RB set that has not triggered at least one consecutive LBT failure. The selected RB set may consider the RB set that triggered the consecutive LBT failure; that is, the selected RB set may exclude RB sets of consecutive LBT failures that were triggered but not canceled.

[0203] In step S1204, the physical layer performs resource selection. Based on the second instruction information, the physical layer selects resources, excludes unavailable resources, and obtains the available resource set A.

[0204] If the second instruction specifies a target resource pool, resource set A is obtained based on the resources in that target resource pool. If the second instruction specifies a selected RB set, resource set A is obtained based on the resources in the selected RB set. If the second instruction specifies a resource where consecutive LBT failures have occurred, resource set A is obtained by excluding the RB set where the consecutive LBT failures occurred.

[0205] In step S1206, the physical layer reports resource set A to the MAC layer.

[0206] In step S1208, the MAC layer selects resources based on resource set A reported by the physical layer.

[0207] In step S1210, if the MAC layer can select a sufficient number of resources that meet the requirements, the MAC layer can send transmission-related information to the physical layer, such as the selected resources and data packets awaiting transmission (e.g., MAC PDUs).

[0208] In step S1212, the physical layer can perform LBT detection on the resource selected by the MAC layer before transmitting data. If LBT is successful, the data is transmitted. If LBT fails, step S1214 is executed.

[0209] In step S1214, the physical layer sends an LBT failure instruction to the MAC layer. Using RB set 1 as an example, the physical layer can send an LBT failure instruction for RB set 1 to the MAC layer.

[0210] If RB set 1 is associated with multiple channels, the LBT failure instruction for RB set 1 can be sent in at least one of the following situations: all channels have transmitted an LBT failure; an LBT failure has occurred in at least one channel; or an LBT failure has occurred in the channel on which the resources used for data transmission reside. Specifically, the situation in which the LBT failure instruction for RB set 1 is sent depends on whether a guard band is configured on the terminal equipment. If a guard band is configured on the terminal equipment, the LBT failure instruction for RB set 1 can be sent if all channels have transmitted an LBT failure. If a guard band is not configured on the terminal equipment, the LBT failure instruction for RB set 1 can be sent if an LBT failure occurs in at least one channel.

[0211] In step S1216, after the MAC layer receives an LBT failure instruction for RBset1, it starts the RBset1 timer if it has not already started, and if it has already started, it increments the value of the RBset1 counter by 1.

[0212] Furthermore, the MAC layer can also trigger resource reselection. This resource reselection is triggered by an LBT failure.

[0213] The MAC layer directs the physical layer to the RB set that has experienced consecutive LBT failures and / or consecutive LBT failures.

[0214] In step S1218, when the RB set 1 timer times out, it is determined whether the value of the RB set 1 counter is greater than a preset threshold.

[0215] In step S1220, if the value of the RB set 1 counter is greater than a preset threshold, it is determined that consecutive LBT failures have occurred in RB set 1.

[0216] The MAC layer can trigger a new resource selection. For example, it can return to step S1202 and re-execute it. The MAC layer can redirect the physical layer to a resource pool, which may be the previous resource pool (i.e., the current resource pool) or a new resource pool.

[0217] The new resource selection may be triggered by consecutive LBT failures in a single RB set. If the current resource pool has any associated RB sets that have not yet triggered consecutive LBT failures, the resource selection can be performed in the current resource pool. Alternatively, the resource selection can be performed in another resource pool.

[0218] In step S1222, if the RB set 1 timer times out and the value of the RB set 1 counter has not reached a preset threshold, the RB set 1 counter is set to zero.

[0219] If consecutive LBT failures occur in RB set 1, the MAC layer triggers an RB set switch or a new resource selection. For example, it can return to step S1202 and re-execute. The MAC layer can then re-instruct the physical layer to select a new RB set, which may be the RB set after the switch.

[0220] In step S1224, after the resource pool switchover, the MAC layer can cancel the consecutive LBT failures of the old RB set that were triggered.

[0221] If LBT is successful with a new resource or RB set, the MAC layer can cancel the consecutive LBT failures on the triggered old RB set. Alternatively, if data transmission is successful with a new resource or RB set, the MAC layer can cancel the consecutive LBT failures on the triggered old RB set.

[0222] If the terminal device scans all configured RB sets but LBT fails or data transmission fails, it triggers the unicast link RLF and cancels consecutive LBT failures in triggered and uncancelled RB sets.

[0223] If the terminal device switches N times (reaching the set number of times) and LBT is still unsuccessful, or if data transmission is unsuccessful, trigger the RLF on all unicast links and cancel consecutive LBT failures in triggered and uncancelled RB sets.

[0224] When a terminal device is in an RRC connection state, it can send a continuous LBT failure report (for example, to a network device or peer device). Furthermore, a terminal device sending a continuous LBT failure report can also trigger a cancellation operation (release operation) of the continuous LBT failure. In other words, a terminal device can trigger a cancellation operation of the continuous LBT failure when it performs a resource switch, and it can also trigger a cancellation operation of the continuous LBT failure when it sends a continuous LBT failure report. Therefore, it is necessary to standardize how to perform these two consecutive LBT failure cancellation operations.

[0225] Based on this, embodiments of the present application propose that a terminal device triggers a cancellation operation for consecutive LBT failures only after completing the two operations described above. For example, in the event of consecutive LBT failures on a triggered RB set, the terminal device will not trigger a cancellation operation for consecutive LBT failures until it has sent a consecutive LBT failure report for that RB set and performed a resource pool switchover. Alternatively, the terminal device may trigger a cancellation operation for consecutive LBT failures after completing any one of the two operations described above. For example, the terminal device may choose to send a consecutive LBT failure report or switch resource pools, and after completing the corresponding operation, it may trigger a cancellation operation for consecutive LBT failures.

[0226] After a cancellation operation for consecutive LBT failures is triggered, the MAC layer can instruct the physical layer to cancel the consecutive LBT failures or cancel (release) the RB set associated with the consecutive LBT failures.

[0227] Example 3 Figure 13 illustrates a situation where consecutive LBT failures occur in a resource pool, and the resource switching policy switches the resource pool set. For example, if a resource pool is marked as having consecutive LBT failures, the resource pool is replaced. If the RB set associated with a resource pool is indicated as having an LBT failure, the counter corresponding to that resource pool is incremented by 1, and if the number of consecutive LBT failures in that resource pool exceeds a preset threshold, the resource pool is replaced.

[0228] Referring to Figure 13, in step S1302, the MAC layer triggers resource selection or resource re-selection. Simultaneously with triggering the physical layer to perform resource selection, the MAC layer can send second instruction information to the physical layer.

[0229] The second instruction information can be used to specify one or more parameters, such as transmission data-related information, currently available COT information, received IUC information, SL DRX information, target resource pool information, and selected RB set information. Here, transmission data-related information may include one or more of the required resource size, number of retries, priority, etc. Available COT information may include COT time-related information (e.g., remaining time, start time, end time, etc.). Target resource pool information can be determined based on the RB set that has experienced consecutive LBT failures. The resource pool selected by the MAC layer must be associated with an RB set that has not triggered at least one consecutive LBT failure.

[0230] In step S1304, the physical layer performs resource selection. Based on the second instruction information, the physical layer selects resources, excludes unavailable resources, and obtains an available resource set A.

[0231] If the second instruction information indicates a target resource pool, resource set A is obtained based on the resources in that target resource pool. If the second instruction information indicates a selected RB set, resource set A is obtained based on the resources in the selected RB set.

[0232] In step S1306, the physical layer reports resource set A to the MAC layer.

[0233] In step S1308, the MAC layer selects resources based on resource set A reported by the physical layer.

[0234] In step S1310, the MAC layer can send transmission-related information to the physical layer, such as selected resources and data packets awaiting transmission (e.g., MAC PDUs).

[0235] In step S1312, the physical layer can perform LBT detection on the resource selected by the MAC layer before transmitting data. If LBT is successful, the data is transmitted. If LBT fails, step S1316 is executed.

[0236] In step S1314, the physical layer sends an LBT failure instruction to the MAC layer.

[0237] Taking RB set 1 as an example, if RB set 1 is associated with multiple channels, the LBT failure instruction for RB set 1 can be sent in at least one of the following situations: all channels have transmitted an LBT failure; an LBT failure has occurred in at least one channel; or an LBT failure has occurred in the channel where the resources used for data transmission are located. Specifically, when the LBT failure instruction for RB set 1 is sent depends on whether the terminal equipment is configured to have a guard band. If the terminal equipment is configured to have a guard band, the LBT failure instruction for RB set 1 can be sent when all channels have transmitted an LBT failure. If the terminal equipment is not configured to have a guard band, the LBT failure instruction for RB set 1 can be sent when an LBT failure occurs in at least one channel.

[0238] In step S1316, after receiving an LBT failure instruction, the MAC layer starts the corresponding resource pool 1 timer if it has not already started, and increments the value of the resource pool 1 counter by 1 if the resource pool 1 timer has already started.

[0239] Furthermore, the MAC layer can also trigger resource reselection. This resource reselection is triggered by an LBT failure.

[0240] The MAC layer directs the physical layer to the resource pool where consecutive LBT failures and / or consecutive LBT failures have occurred.

[0241] In step S1318, when the resource pool 1 timer times out, it is determined whether the value of the resource pool 1 counter is greater than a preset threshold.

[0242] In step S1320, if the value of the resource pool 1 counter is greater than a preset threshold, it is determined that consecutive LBT failures have occurred in resource pool 1.

[0243] In step S1322, if the resource pool 1 timer times out and the value of the resource pool 1 counter has not reached a predetermined threshold, the resource pool 1 counter is set to zero.

[0244] If consecutive LBT failures occur in resource pool 1, the MAC layer triggers a resource pool switchover or a new resource selection. For example, it can return to step S1302 and re-execute. The MAC layer can then re-instruct the physical layer to use a resource pool, which may be the resource pool after the switchover.

[0245] In step S1324, after the resource pool switchover, the MAC layer can cancel the consecutive LBT failures of the old resource pool that were triggered.

[0246] If LBT is successful on a new resource or resource pool, the MAC layer can cancel the consecutive LBT failures on the old resource pool that triggered it. Alternatively, if data transmission is successful on a new resource or resource pool, the MAC layer can cancel the consecutive LBT failures on the old resource pool that triggered it.

[0247] If the terminal device scans all configured resource pools but LBT fails or data transmission fails, it triggers an RLF on the unicast link and cancels consecutive LBT failures on resource pools that have already been triggered and not canceled.

[0248] If LBT fails or data transmission fails after N (the set number of) terminal devices have switched over, trigger an RLF on all unicast links and cancel any consecutive LBT failures on the resource pool that have already been triggered and not canceled.

[0249] When a terminal device is in an RRC connection state, it can send a continuous LBT failure report (for example, to a network device or peer device). Furthermore, a terminal device sending a continuous LBT failure report can also trigger a cancellation operation (release operation) of the continuous LBT failure. In other words, a terminal device can trigger a cancellation operation of the continuous LBT failure when it performs a resource switch, and it can also trigger a cancellation operation of the continuous LBT failure when it sends a continuous LBT failure report. Therefore, it is necessary to standardize how to perform these two consecutive LBT failure cancellation operations.

[0250] Based on this, embodiments of the present application propose that a terminal device triggers a cancellation operation for consecutive LBT failures only after completing the two operations described above. For example, in response to consecutive LBT failures on a triggered resource pool, the terminal device will not trigger a cancellation operation for consecutive LBT failures until it has sent a consecutive LBT failure report for that resource pool and performed a resource pool switch. Alternatively, the terminal device may trigger a cancellation operation for consecutive LBT failures after completing any one of the two operations described above. For example, the terminal device may choose to send a consecutive LBT failure report or switch resource pools, and after completing the corresponding operation, it may trigger a cancellation operation for consecutive LBT failures.

[0251] After a cancellation operation for consecutive LBT failures is triggered, the MAC layer can instruct the physical layer to cancel the consecutive LBT failures or the resource pool where the consecutive LBT failures occurred.

[0252] Embodiments of the method of this application have been described in detail with reference to Figures 1 to 13. Embodiments of the apparatus of this application have been described in detail below with reference to Figures 14 and 15. It should be understood that the description of the method embodiment and the description of the apparatus embodiment correspond to each other. Therefore, for parts not described in detail, refer to the method embodiment described above.

[0253] Figure 14 is a schematic block diagram of a terminal device according to an embodiment of the present application. The terminal device 1400 shown in Figure 14 may be any of the terminal devices described above. The terminal device 1400 may include a decision unit 1410.

[0254] The decision unit 1410 is configured to determine a first policy regarding consecutive LBT failures, the detection of which is related to resource granularity.

[0255] In some embodiments, the resource granularity includes RB sets and / or resource pools.

[0256] In some embodiments, the first policy includes one or more of the following: a resource switching policy, a second policy related to the cancellation of triggered consecutive LBT failures, and a third policy related to the determination of consecutive LBT failures.

[0257] In some embodiments, the resource switching policy includes one or more of the following: switching resource pools, switching RB sets, and switching time-frequency resources.

[0258] In some embodiments, the resource switching policy includes switching resource pools, and the terminal equipment further includes a switching unit configured to switch resource pools when a first condition is met. The first condition relates to whether consecutive LBT failures have occurred in the RB set and one or more of the data transmission requirements.

[0259] In some embodiments, the first condition includes one or more of the following: all RB sets associated with the current resource pool experience consecutive LBT failures, and the number of remaining resources in the resource pool is below a predetermined threshold. The remaining resources belong to resources that have not experienced consecutive LBT failures and / or resources that meet the data transmission requirements.

[0260] In some embodiments, the remaining resources include time-frequency resources and / or RB sets.

[0261] In some embodiments, the resource switching policy includes switching RB sets or time-frequency resources, and the terminal equipment further includes a switching unit configured to switch RB sets or time-frequency resources when consecutive LBT failures occur in the current RB set.

[0262] In some embodiments, consecutive LBT failures occur on the RB set.

[0263] In some embodiments, the resource switching policy includes switching resource pools or switching time-frequency resources.

[0264] In some embodiments, the terminal equipment further includes a switching unit configured to switch resource pools or time-frequency resources in the event of a series of LBT failures in the current resource pool.

[0265] In some embodiments, consecutive LBT failures occur on the resource pool.

[0266] In some embodiments, the second policy includes canceling triggered consecutive LBT failures of the first resource if the second condition is met. The second condition includes one or more of the following: the terminal device has performed a first operation related to resource switching, and the terminal device has sent a consecutive LBT failure report.

[0267] In some embodiments, the transmission of the continuous LBT failure report by the terminal device includes one or more of the terminal device transmitting a continuous LBT failure to a peer device and the terminal device transmitting a continuous LBT failure to a network device.

[0268] In some embodiments, the first operation includes one or more of performing a resource switch, the LBT being successful within the switched resource, the data transmission being successful within the switched resource, and the RLF of the unicast link being triggered.

[0269] In some embodiments, the triggering of the RLF of the unicast link includes one or more of the LBT not being successful in the target resource after switching, the target resource after switching already triggering a continuous LBT failure, and the data transmission not being successful on the target resource after switching. The target resource is all configured resources or a preset number of resources.

[0270] In some embodiments, the target resource includes a time-frequency resource and / or a set of RBs.

[0271] In some embodiments, when the second condition includes the triggering of the RLF of the unicast link, the first resource includes the target resource.

[0272] In some embodiments, the first resource includes one or more of a set of RBs associated with one or more resource pools before switching, one or more sets of RBs before switching, and one or more resource pools before switching.

[0273] In some embodiments, when the first condition includes the transmission of a continuous LBT failure report by the terminal device, the first resource includes the resource corresponding to the transmitted continuous LBT failure.

[0274] In some embodiments, the terminal device further includes a transmission unit configured to transmit first indication information from the MAC layer to the physical layer of the terminal device, and the first indication information is used to indicate cancellation of the continuous LBT failure and / or cancellation of the resource of the continuous LBT failure.

[0275] In some embodiments, the third policy includes determining that a continuous LBT failure has occurred in the first set of RBs when the number of LBT failures occurring on the first set of RBs reaches a first preset threshold within a first preset period. Or, the third policy includes determining that a continuous LBT failure has occurred in the first resource pool when the number of LBT failures occurring on the set of RBs associated with the first resource pool reaches a second preset threshold within a second preset period.

[0276] In some embodiments, the occurrence of an LBT failure in the first set of RBs is related to second information, and the second information includes one or more of the information that an LBT failure has occurred in all channels associated with the first set of RBs, that an LBT failure has occurred in at least one channel associated with the first set of RBs, and that an LBT failure has occurred in the channel where the resource for data transmission is located.

[0277] In some embodiments, the second information is associated with whether the terminal device is configured to include a guard band.

[0278] In some embodiments, the selected resource for data transmission by the terminal device is determined based on second instruction information, which is used to indicate one or more of the following: information about the target resource pool, which is determined based on information related to consecutive LBT failures, and information related to the target RB set.

[0279] In some embodiments, the target RB set includes one or more of the selected RB sets and the RB sets that have experienced consecutive LBT failures.

[0280] In some embodiments, the selected RB set does not include any RB sets that experience consecutive LBT failures.

[0281] In some embodiments, the target resource pool is associated with at least one RB set or resource pool that does not trigger consecutive LBT failures, and / or the target resource pool includes at least one resource pool that does not trigger consecutive LBT failures.

[0282] In some embodiments, the selected resource is transmitted from the MAC layer of the terminal device to the physical layer of the terminal device, the selected resource is determined by the MAC layer based on a second resource, and the second resource is determined by the physical layer through resource selection based on second instruction information.

[0283] In some embodiments, the second resource is determined based on one or more of the following: resources in the target resource pool, resources in the selected RB set, and resources from which consecutive LBT failures have been excluded.

[0284] Figure 15 is a schematic diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 15 indicate that a unit or module is optional. The device 1500 may be configured to perform the method described in the embodiment of the method described above. The device 1500 may be a chip or a terminal device.

[0285] The apparatus 1500 may include one or more processors 1510. The processors 1510 can assist the apparatus 1500 in performing the methods described in the embodiments of the above-described methods. The processors 1510 may be general-purpose processors or dedicated processors. For example, the processor may be a central processing unit (CPU). Optionally, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc.

[0286] The device 1500 may further include one or more memories 1520. Each memory 1520 stores a program executed by the processor 1510, which causes the processor 1510 to perform the method described in the embodiment of the above method. The memory 1520 may be independent of the processor 1510 or integrated with the processor 1510.

[0287] The device 1500 may further include a transceiver 1530. The processor 1510 can communicate with other devices or chips via the transceiver 1530. For example, the processor 1510 can send data to or receive data from other devices or chips via the transceiver 1530.

[0288] Furthermore, embodiments of this application provide a computer-readable storage medium configured to store a program. This computer-readable storage medium may be applied to a terminal device in embodiments of this application. When the program is executed on a computer, it causes the computer to perform the same actions as those performed by the terminal devices in various embodiments of this application.

[0289] Furthermore, a computer program product is provided in the embodiments of this application. The computer program product includes a program. The computer program product can be applied to the terminal equipment in the embodiments of this application, and the program, when executed on a computer, causes the computer to carry out the methods executed by the terminal equipment in the various embodiments of this application.

[0290] Furthermore, a computer program for the embodiments of this application is provided. This computer program can be applied to the terminal device for the embodiments of this application, and when executed on a computer, it causes the computer to execute the methods performed by the terminal device for the various embodiments of this application.

[0291] It should be understood that the terms “system” and “network” used herein may be used interchangeably. Furthermore, the terms used herein are used solely to describe the specific embodiments herein and are not intended to limit the invention. Terms such as “first,” “second,” “third,” and “fourth” presented herein, in the claims and drawings are used to distinguish different subjects and do not indicate a particular order. Furthermore, “includes,” “has,” and variations thereof are intended to indicate non-exclusive inclusion.

[0292] As used in the embodiments of this specification, the term "indicating" can be a direct or indirect indication, and may also indicate a relationship. For example, when A indicates B, it may mean that A directly indicates B (e.g., when B is obtained through A), A indirectly indicates B (e.g., when A indicates C and B is obtained through C), or it may mean that there is a correlation between A and B.

[0293] In the embodiments of this application, the term "including" mentioned may refer to directly including or indirectly including. Alternatively, in the embodiments of this application, the term "including" may be replaced with "indicating" or "for determining". For example, the expression that A includes B may be replaced with that A indicates B, or A is for determining B.

[0294] In the embodiments of this application, the expression "B corresponding to A" means that B is associated with A and B is determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined only based on A, and B may be determined based on A and / or other information.

[0295] The term "corresponding" in the embodiments of this application may indicate that the listed items have a direct or indirect correspondence relationship, association relationship, indication-indicated relationship, composition-composed relationship, etc.

[0296] As used in the embodiments of this specification, the expressions "predefined" or "preset" can be implemented by pre-saving the corresponding code or table, or by other means that can be used to indicate relevant information in a device (such as a terminal device or a network device). Its specific implementation is not limited in this specification. For example, being predefined may mean being defined within a protocol.

[0297] In the embodiments herein, “protocol” refers to, but is not limited to, standard protocols in the field of communications, such as the LTE protocol, the NR protocol, and related protocols applicable to future communication systems.

[0298] In the examples herein, the term "and / or" is used solely to describe the relationship between related objects and indicates that three relationships may exist. For example, A and / or B may represent three conditions: the independent existence of A, the existence of both A and B, and the independent existence of B. Furthermore, the letter " / " in this specification generally indicates that the preceding and following related objects form an "or" relationship.

[0299] In the various embodiments of this application, the size of the sequence number of the above process does not indicate the execution order, and the execution order of various processes is determined by their function and inherent logic, and should not be limited in any way to the implementation processes of the embodiments of this application.

[0300] It should be understood that in the various embodiments provided herein, the provided systems, apparatus, and methods may be implemented in other ways. For example, the embodiments of the described apparatus are merely examples. For example, the division of units is merely a logical functional division, and other divisions may exist in actual embodiments. For example, multiple units or components may be coupled or integrated into another system, or some functions may be omitted or not performed. Furthermore, the mutual coupling, direct coupling, and communication connection illustrated or described may be indirect coupling or communication connection implemented through some interface. The apparatus or unit may be implemented in electrical, mechanical, or other forms.

[0301] Units described as separate components may or may not be physically separated. Components illustrated as units may or may not be physical units. They may be located in one place or distributed across multiple network units. To achieve the objectives of the embodiment's solution, some or all of the units may be selected according to the actual needs.

[0302] The embodiments described above may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software form, the embodiments may be implemented in whole or in part by a computer program product. A computer program product includes one or more computer instructions. When computer program instructions are loaded into a computer and executed, all or part of the processes or functions described according to the embodiments of this application are generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable device. Computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted in wired (e.g., coaxial cable, fiber optic cable, digital subscriber line (DSL)) or wireless (e.g., infrared, radio, microwave, etc.) form from one website, computer, server, or data center to another. A computer-readable storage medium may be any available medium accessible to a data storage device such as a computer or server or data center, or a medium integrated with one or more available media. Available media include magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVDs)), and semiconductor media (e.g., solid-state disks (SSDs)).

[0303] The above description is merely a specific example of the present application and is not intended to limit the scope of protection of this application. Any modification or substitution that a person skilled in the art can easily conceive within the scope of the art disclosed in this application is included in the scope of protection of this application. Accordingly, the scope of protection of this application shall be subject to the scope of protection of the claims.

Claims

1. The terminal device includes determining a first policy related to consecutive LBT (Listen Before Talk) failures, The detection of the aforementioned consecutive LBT failures is related to resource granularity. Wireless communication method.

2. The aforementioned resource granularity includes resource block (RB) sets and / or resource pools. The wireless communication method according to claim 1.

3. The first policy includes one or more of the following: a resource switching policy, a second policy related to the cancellation of triggered consecutive LBT failures, and a third policy related to the determination of consecutive LBT failures. The wireless communication method according to claim 1 or 2.

4. The resource switching policy includes one or more of the following: switching resource pools, switching RB sets, and switching time-frequency resources. The wireless communication method according to claim 3.

5. The aforementioned resource switching policy includes switching resource pools, The aforementioned wireless communication method is If the terminal device satisfies the first condition, the method further includes switching the resource pool. The first condition is, This refers to whether consecutive LBT failures occurred in the RB set. Data transmission requirements, Related to one or more pieces of information from the above, The wireless communication method according to claim 4.

6. The first condition is Consecutive LBT failures have occurred in all RB sets associated with the current resource pool. The number of remaining resources in the resource pool must be below a predetermined threshold. Includes one or more of the following: The remaining resources belong to resources where no consecutive LBT failures have occurred and / or resources that meet the data transmission requirements. The wireless communication method according to claim 5.

7. The remaining resources include time-frequency resources and / or RB sets. The wireless communication method according to claim 6.

8. The resource switching policy includes switching RB sets or time-frequency resources, and the wireless communication method is The terminal device further includes switching the RB set or time-frequency resource if a series of LBT failures occur in the current RB set. The wireless communication method according to claim 4.

9. The aforementioned consecutive LBT failures occur in the RB set. The wireless communication method according to any one of claims 4 to 8.

10. The resource switching policy includes switching resource pools or time-frequency resources. The wireless communication method according to claim 3.

11. The wireless communication method further includes the terminal device switching resource pools or time-frequency resources when a series of LBT failures occur in the current resource pool. The wireless communication method according to claim 10.

12. The aforementioned consecutive LBT failures occur in the resource pool. The wireless communication method according to claim 10 or 11.

13. The second policy includes canceling a series of triggered LBT failures of the first resource if the second condition is met. The second condition is, The terminal device has performed a first operation related to resource switching. The terminal device has transmitted a series of LBT failure reports, including one or more of the above. The wireless communication method according to any one of claims 3 to 12.

14. The fact that the aforementioned terminal device sent a continuous LBT failure report indicates that The terminal device sent a series of LBT failures to the peer device. This includes one or more of the following: a terminal device sending a series of LBT failures to a network device. The wireless communication method according to claim 13.

15. The first operation is, We performed a resource switch. The LBT was successful within the resources after the switchover. Data transmission was successful within the resources after the switch. One or more of the following: a unicast link radio link failure (RLF) was triggered. The wireless communication method according to claim 13 or 14.

16. The RLF of the aforementioned unicast link is triggered by, LBT failed on the target resource after the switchover. The target resource after the switchover has already triggered a series of LBT failures. This includes one or more instances where data transmission failed at the target resource after the switchover. The aforementioned target resources are all configured resources or a predetermined number of resources. The wireless communication method according to claim 15.

17. The aforementioned target resource includes a resource pool and / or RB set. The wireless communication method according to claim 16.

18. If the second condition includes the RLF of the unicast link being triggered, the first resource includes the target resource. The wireless communication method according to claim 16 or 17.

19. The first resource is, RB sets associated with one or more resource pools before the switchover, One or more RB sets before switching, Includes one or more of the resource pools prior to the switchover, The wireless communication method according to any one of claims 13 to 17.

20. If the first condition includes the transmission of a series of LBT failure reports by the terminal device, the first resource includes the resource corresponding to the transmitted series of LBT failures. The wireless communication method according to any one of claims 13 to 17.

21. The wireless communication method includes the media access control (MAC) layer of the terminal device transmitting first instruction information to the physical layer of the terminal device. The first instruction information is used to instruct the cancellation of consecutive LBT failures and / or the cancellation of the resource where consecutive LBT failures occurred. The wireless communication method according to any one of claims 13 to 20.

22. The third policy includes determining that consecutive LBT failures have occurred in the first RB set if the number of LBT failures in the first RB set within a first pre-configured period reaches a first pre-configured threshold, or The third policy includes determining that a series of LBT failures have occurred in the first resource pool if, within a second pre-configured period, the number of LBTs in the RB set associated with the first resource pool reaches a second pre-configured threshold. The wireless communication method according to any one of claims 3 to 21.

23. The occurrence of an LBT failure in the first RB set is related to the second piece of information, The second information mentioned above is, LBT failures occurred in all channels associated with the first RB set. An LBT failure occurred in at least one channel associated with the first RB set. This includes one or more pieces of information, such as that an LBT failure occurred on the Channel where resources for data transmission are located. The wireless communication method according to claim 22.

24. The second information relates to whether a guard band is configured on the terminal device. The wireless communication method according to claim 23.

25. The selected resource for data transmission from the terminal device is determined based on the second instruction information. The second instruction information is, Information on the target resource pool determined based on information related to consecutive LBT failures. Used to indicate one or more pieces of information related to the target RB set, The wireless communication method according to any one of claims 1 to 24.

26. The aforementioned target RB set is Selected RB set, Including one or more RB sets in which consecutive LBT failures occurred, The wireless communication method according to claim 25.

27. The selected RB set does not include any RB set in which consecutive LBT failures occurred. The wireless communication method according to claim 26.

28. The target resource pool is associated with at least one RB set or resource pool that has not triggered consecutive LBT failures, and / or The target resource pool includes at least one resource pool that has not triggered consecutive LBT failures. The wireless communication method according to any one of claims 25 to 27.

29. The selected resource is transmitted from the MAC layer of the terminal device to the physical layer of the terminal device. The selected resource is determined by the MAC layer based on the second resource. The second resource is determined by the physical layer performing resource selection based on the second instruction information. The wireless communication method according to any one of claims 25 to 28.

30. The aforementioned second resource is, Resources in the aforementioned target resource pool, Resources in the selected RB set, Resources excluding those that experienced consecutive LBT failures. Determined based on one or more of the following: The wireless communication method according to claim 29.

31. It includes a decision unit configured to determine a first policy related to consecutive Listen Before Talk (LBT) failures, The detection of the aforementioned consecutive LBT failures is related to resource granularity. Terminal equipment.

32. The aforementioned resource granularity includes resource block (RB) sets and / or resource pools. The terminal device according to claim 31.

33. The first policy includes one or more of the following: a resource switching policy, a second policy related to the cancellation of triggered consecutive LBT failures, and a third policy related to the determination of consecutive LBT failures. The terminal device according to claim 31 or 32.

34. The resource switching policy includes one or more of the following: switching resource pools, switching RB sets, and switching time-frequency resources. The terminal device according to claim 33.

35. The aforementioned resource switching policy includes switching resource pools, The terminal device further includes a switching unit configured to switch resource pools when the first condition is met, The first condition is, Whether consecutive LBT failures occurred in the RB set. Related to one or more of the data transmission requirements, The terminal device according to claim 34.

36. The first condition is, Consecutive LBT failures have occurred in all RB sets associated with the current resource pool. The number of remaining resources in the resource pool must be below a predetermined threshold. Includes one or more of the following: The remaining resources belong to resources where no consecutive LBT failures have occurred and / or resources that meet the data transmission requirements. The terminal device according to claim 35.

37. The remaining resources include time-frequency resources and / or RB sets. The terminal device according to claim 36.

38. The resource switching policy includes switching RB sets or time-frequency resources, and the terminal equipment, The system further includes a switching unit configured to switch between RB sets or time-frequency resources in the event of a series of LBT failures in the current RB set. The terminal device according to claim 34.

39. The aforementioned consecutive LBT failures occur on the RB set. The terminal device according to any one of claims 34 to 38.

40. The resource switching policy includes switching resource pools or time-frequency resources. The terminal device according to claim 33.

41. The terminal device further includes a switching unit configured to switch resource pools or time-frequency resources in the event of a series of LBT failures in the current resource pool. The terminal device according to claim 40.

42. The aforementioned consecutive LBT failures occur on the resource pool. The terminal device according to claim 40 or 41.

43. The second policy includes canceling a series of triggered LBT failures of the first resource if the second condition is met. The second condition is, The terminal device has performed a first operation related to resource switching. The terminal device has transmitted a series of LBT failure reports, including one or more of the above. The terminal device according to any one of claims 33 to 42.

44. The fact that the aforementioned terminal device sent a continuous LBT failure report indicates that The terminal device sent a series of LBT failures to the peer device. This includes one or more of the following: a terminal device sending a series of LBT failures to a network device. The terminal device according to claim 43.

45. The first operation is, We performed a resource switch. The LBT was successful within the resources after the switchover. Data transmission was successful within the resources after the switch. One or more of the following are triggered: The terminal device according to claim 43 or 44.

46. The triggering of the aforementioned unicast link wireless link failure (RLF) is: LBT failed on the target resource after the switchover. The target resource after the switchover has already triggered a series of LBT failures. This includes one or more instances where data transmission failed on the target resource after the switchover. The aforementioned target resources are all configured resources or a predetermined number of resources. The terminal device according to claim 45.

47. The aforementioned target resource includes a resource pool and / or RB set. The terminal device according to claim 46.

48. If the second condition includes the RLF of the unicast link being triggered, the first resource includes the target resource. The terminal device according to claim 46 or 47.

49. The first resource is, RB sets associated with one or more resource pools before the switchover, One or more RB sets before switching, Including one or more of the one or more resource pools before the switchover, The terminal device according to any one of claims 43 to 47.

50. If the first condition includes the transmission of a series of LBT failure reports by the terminal device, the first resource includes the resource corresponding to the transmitted series of LBT failures. The terminal device according to any one of claims 43 to 47.

51. The terminal device further includes a transmission unit configured to transmit first instruction information to the physical layer of the terminal device via the MAC layer. The first instruction information is used to instruct the cancellation of consecutive LBT failures and / or the cancellation of the resource where consecutive LBT failures occurred. A terminal device according to any one of claims 43 to 50.

52. The third policy includes determining that consecutive LBT failures have occurred in the first RB set if the number of LBT failures in the first RB set within a first pre-configured period reaches a first pre-configured threshold, or The third policy includes determining that a series of LBT failures have occurred in the first resource pool if, within a second pre-configured period, the number of LBTs in the RB set associated with the first resource pool reaches a second pre-configured threshold. The terminal device according to any one of claims 33 to 51.

53. The occurrence of an LBT failure in the first RB set is related to the second piece of information, The second information mentioned above is, LBT failures occurred in all channels associated with the first RB set. An LBT failure occurred in at least one channel associated with the first RB set. This includes one or more pieces of information, such as: an LBT failure occurred on the Channel where the resources for data transmission are located; The terminal device according to claim 52.

54. The second information relates to whether the terminal device is configured to include a guard band. The terminal device according to claim 53.

55. The selected resource for data transmission from the terminal device is determined based on the second instruction information. The second instruction information is, Information on the target resource pool determined based on information related to consecutive LBT failures. Used to indicate one or more pieces of information related to the target RB set, The terminal device according to any one of claims 31 to 54.

56. The aforementioned target RB set is Selected RB set, Including one or more RB sets in which consecutive LBT failures occurred, The terminal device according to claim 55.

57. The selected RB set does not include any RB set in which consecutive LBT failures occurred. The terminal device according to claim 56.

58. The target resource pool is associated with at least one RB set or resource pool that has not triggered consecutive LBT failures, and / or The target resource pool includes at least one resource pool that has not triggered consecutive LBT failures. The terminal device according to any one of claims 55 to 57.

59. The selected resource is transmitted from the MAC layer of the terminal device to the physical layer of the terminal device. The selected resource is determined by the MAC layer based on the second resource. The second resource is determined by the physical layer performing resource selection based on the second instruction information. The terminal device according to any one of claims 55 to 58.

60. The aforementioned second resource is, Resources in the aforementioned target resource pool, Resources in the selected RB set, Resources excluding those that experienced consecutive LBT failures. Determined based on one or more of the following: The terminal device according to claim 59.

61. A terminal device including memory and a processor, The memory is configured to store a program, The processor is configured to call a program in the memory and execute the wireless communication method described in any one of claims 1 to 30. Terminal equipment.

62. A device including a processor, The processor is configured to call a program from memory and execute the method according to any one of claims 1 to 30. Device.

63. A chip including a processor, The processor is configured to call a program from memory and cause the device on which the chip is installed to execute the wireless communication method described in any one of claims 1 to 30. Tip.

64. A computer-readable storage medium for storing a program that causes a computer to execute the wireless communication method described in any one of claims 1 to 30.

65. A computer program product comprising a program that causes a computer to execute the wireless communication method described in any one of claims 1 to 30.

66. A computer program that causes a computer to perform the wireless communication method described in any one of claims 1 to 30.

Images