Wireless communication method and device

By receiving and sending multiple LBT failed recovery configurations in wireless communication, detecting continuous LBT failures and adjusting counters and timers, the problem of insufficient flexibility in LBT failed recovery configurations is solved, and service transmission performance and terminal equipment requirements are improved.

CN116097893BActive Publication Date: 2024-11-15GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202080104063.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-10-09
Publication Date
2024-11-15
Estimated Expiration
2040-10-09

AI Technical Summary

Technical Problem

In existing wireless communications, the failure recovery configuration flexibility of Listen Before Talk (LBT) mechanism in the unauthorized frequency band is insufficient, resulting in poor service transmission performance and inability to meet different scenarios and business needs.

Method used

Provide a wireless communication method, by receiving and sending multiple LBT failed recovery configurations, detecting continuous LBT failures and triggering failed recovery processes, and adjusting the recovery configuration using counters and timers, improving the flexibility of LBT failure recovery.

Benefits of technology

It improves service transmission performance, meets the needs of terminal equipment, is suitable for different scenarios and services, and improves the flexibility and efficiency of LBT failure recovery.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116097893B_ABST
    Figure CN116097893B_ABST
Patent Text Reader

Abstract

The embodiment of the present application provides a wireless communication method and device, the method comprising: receiving multiple LBT failure recovery configurations; based on the first LBT failure recovery configuration corresponding to the first information among the multiple LBT failure recovery configurations, detecting continuous LBT failures and / or triggering a failure recovery process. Based on the first LBT failure recovery configuration corresponding to the first information among the multiple LBT failure recovery configurations, detecting continuous LBT failures and / or triggering a failure recovery process is conducive to using a more appropriate LBT failure recovery process for different first information, and accordingly, can improve the flexibility of configuring the LBT failure recovery configuration, thereby improving service transmission performance and ensuring the needs of terminal devices.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communications, and more specifically, to wireless communication methods and devices. Background Art

[0002] In order to expand the frequency bands that can be used for communication between user equipment and base stations, research on unlicensed frequency bands in NR (New Radio) is currently underway, with the aim of enabling user equipment and base stations to communicate in unlicensed frequency bands based on NR technology.

[0003] Before the user equipment performs uplink transmission on the unlicensed frequency band, it needs to perform Listen Before Talk (LBT) on the unlicensed frequency band to detect whether the unlicensed frequency band is idle. Only when the channel sensing result is that the channel is idle, the communication device can send signals; if the channel sensing result of the communication device on the channel of the unlicensed spectrum is that the channel is busy, it needs to wait until the next transmission opportunity to perform LBT again. In R16, only one resource that needs to be transmitted is indicated from the Media Access Control (MAC) layer to the physical layer, and LBT detection is performed on this resource.

[0004] However, as communication standards improve, the functions of LBT also need to be further improved. Summary of the invention

[0005] The embodiments of the present application provide a wireless communication method and device, which can improve the flexibility of configuring LBT failure recovery configuration, thereby improving service transmission performance and ensuring the needs of terminal devices.

[0006] In a first aspect, a wireless communication method is provided, comprising:

[0007] Receive multiple LBT failure recovery configurations;

[0008] Based on a first LBT failure recovery configuration corresponding to the first information among the multiple LBT failure recovery configurations, continuous LBT failures are detected and / or a failure recovery process is triggered.

[0009] In a second aspect, a wireless communication method is provided, including:

[0010] Send multiple LBT failure recovery configurations, where a first LBT failure recovery configuration corresponding to the first information is used by the terminal device to detect continuous LBT failures and / or trigger a failure recovery process.

[0011] In a third aspect, a wireless communication method is provided, including:

[0012] receiving a second LBT failure recovery configuration and at least one set of parameters;

[0013] Based on the second LBT failure recovery configuration and the first parameter, continuous LBT failures are detected and / or a failure recovery process is triggered; the first parameter is a parameter in the at least one group of parameters corresponding to the second information, and each group of parameters in the at least one group of parameters is used to adjust the second counter and / or second timer in the second LBT failure recovery configuration.

[0014] In a fourth aspect, a wireless communication method is provided, including:

[0015] A second LBT failure recovery configuration and at least one set of parameters are sent, wherein the second LBT failure recovery configuration and the first parameter are used by the terminal device to detect continuous LBT failures and / or trigger a failure recovery process; the first parameter is a parameter in the at least one set of parameters corresponding to the second information, and each set of parameters in the at least one set of parameters is used to adjust the second counter and / or second timer in the second LBT failure recovery configuration.

[0016] In a fifth aspect, a terminal device is provided, which is used to execute the method in the first aspect or its implementations. Specifically, the terminal device includes a functional module for executing the method in the first aspect or its implementations.

[0017] In a sixth aspect, a network device is provided, which is used to execute the method in the second aspect or its respective implementations. Specifically, the network device includes a functional module used to execute the method in the second aspect or its respective implementations.

[0018] In a seventh aspect, a terminal device is provided, which is used to execute the method in the third aspect or its respective implementations. Specifically, the terminal device includes a functional module for executing the method in the third aspect or its respective implementations.

[0019] In an eighth aspect, a network device is provided, which is used to execute the method in the fourth aspect or its respective implementations. Specifically, the network device includes a functional module used to execute the method in the fourth aspect or its respective implementations.

[0020] In a ninth aspect, a terminal device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect, the third aspect or each implementation thereof.

[0021] In a tenth aspect, a network device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect, the fourth aspect or each implementation thereof.

[0022] In the eleventh aspect, a chip is provided for implementing the method in any one of the first to fourth aspects or their respective implementations. Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the method in any one of the first to fourth aspects or their respective implementations.

[0023] In the twelfth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method in any one of the first to fourth aspects or its various implementations.

[0024] In a thirteenth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the first to fourth aspects or any of its implementations.

[0025] In a fourteenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to fourth aspects or in each of its implementations.

[0026] Based on the above technical solution, based on the first LBT failure recovery configuration corresponding to the first information among the multiple LBT failure recovery configurations, continuous LBT failures are detected and / or failure recovery processes are triggered, which is conducive to using more appropriate LBT failure recovery processes for different first information. Accordingly, the flexibility of configuring LBT failure recovery configurations can be improved, thereby improving service transmission performance and ensuring the needs of terminal equipment. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 This is an example of a communication system provided in an embodiment of the present application.

[0028] Figure 2 It is a schematic flowchart of the wireless communication method provided in an embodiment of the present application.

[0029] Figure 3 It is another schematic flowchart of the wireless communication method provided in an embodiment of the present application.

[0030] Figure 4 It is a schematic block diagram of a terminal device provided in an embodiment of the present application.

[0031] Figure 5It is a schematic block diagram of a network device provided in an embodiment of the present application.

[0032] Figure 6 It is another schematic block diagram of a terminal device provided in an embodiment of the present application.

[0033] Figure 7 It is another schematic block diagram of the network device provided in an embodiment of the present application.

[0034] Figure 8 It is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0035] Fig. 9 It is a schematic block diagram of the chip provided in the embodiment of the present application. DETAILED DESCRIPTION

[0036] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0037] Figure 1 It is a schematic diagram of an application scenario of an embodiment of the present application.

[0038] like Figure 1 As shown, the communication system 100 may include a terminal device 110 and a network device 120. The network device 120 may communicate with the terminal device 110 via an air interface. The terminal device 110 and the network device 120 support multi-service transmission.

[0039] It should be understood that the embodiments of the present application are only exemplified by the communication system 100, but the embodiments of the present application are not limited thereto. That is to say, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), 5G communication system (also known as New Radio (NR) communication system), or future communication systems.

[0040] exist Figure 1In the communication system 100 shown, the network device 120 may be an access network device that communicates with the terminal device 110. The access network device may provide communication coverage for a specific geographical area, and may communicate with the terminal device 110 (eg, UE) located in the coverage area.

[0041] The network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB) in an NR system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device 120 may be a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved Public Land Mobile Network (PLMN), etc.

[0042] The terminal device 110 may be any terminal device, including but not limited to a terminal device connected to the network device 120 or other terminal devices by wire or wireless connection.

[0043] For example, the terminal device 110 may refer to an access terminal, a user equipment (UE), a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolution network, etc.

[0044] The terminal device 110 may be used for device-to-device (D2D) communication.

[0045] The wireless communication system 100 may also include a core network device 130 for communicating with the base station, and the core network device 130 may be a 5G core network (5G Core, 5GC) device, for example, an access and mobility management function (Access and Mobility Management Function, AMF), and for example, an authentication server function (Authentication Server Function, AUSF), and for example, a user plane function (User Plane Function, UPF), and for example, a session management function (Session Management Function, SMF). Optionally, the core network device 130 may also be an evolved packet core (Evolved Packet Core, EPC) device of the LTE network, for example, a session management function + a data gateway (Session Management Function + Core Packet Gateway, SMF + PGW-C) device of the core network. It should be understood that SMF + PGW-C can simultaneously implement the functions that SMF and PGW-C can implement. In the process of network evolution, the above-mentioned core network device may also be called other names, or a new network entity may be formed by dividing the functions of the core network, which is not limited to the embodiments of the present application.

[0046] The functional units in the communication system 100 may also establish connections through next generation (NG) network interfaces to achieve communication.

[0047] For example, the terminal device establishes an air interface connection with the access network device through the NR interface for transmitting user plane data and control plane signaling; the terminal device can establish a control plane signaling connection with the AMF through the NG interface 1 (N1 for short); the access network device, such as the next generation wireless access base station (gNB), can establish a user plane data connection with the UPF through the NG interface 3 (N3 for short); the access network device can establish a control plane signaling connection with the AMF through the NG interface 2 (N2 for short); the UPF can establish a control plane signaling connection with the SMF through the NG interface 4 (N4 for short); the UPF can exchange user plane data with the data network through the NG interface 6 (N6 for short); the AMF can establish a control plane signaling connection with the SMF through the NG interface 11 (N11 for short); the SMF can establish a control plane signaling connection with the PCF through the NG interface 7 (N7 for short).

[0048] Figure 1A base station, a core network device and two terminal devices are shown exemplarily. Optionally, the wireless communication system 100 may include multiple base station devices and each base station may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0049] It should be understood that all devices with communication functions in the network / system in the embodiments of the present application can be referred to as communication devices. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include a network device 120 and a terminal device 110 with communication functions. The network device 120 and the terminal device 110 may be the devices described above and will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.

[0050] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0051] It should be noted that the communication system 100 can operate in an unlicensed frequency band, for example, including the following operating scenarios:

[0052] Scenario A: Carrier aggregation scenario, the primary cell (PCell) is the licensed spectrum, and the secondary cells (SCells) working on the unlicensed spectrum are aggregated through carrier aggregation.

[0053] Scenario B: Dual-connectivity working scenario, PCell is LTE licensed spectrum, and PScell ​​is NR unlicensed spectrum.

[0054] Scenario C: Independent working scenario, NR works as an independent cell in the unlicensed spectrum.

[0055] Scenario D: NR single-cell scenario, the uplink (UL) operates in the licensed spectrum and the downlink (DL) operates in the unlicensed spectrum.

[0056] Scenario E: Dual-connectivity working scenario, PCell is NR licensed spectrum, and primary secondary cell (PSCell) is NR unlicensed spectrum.

[0057] As an example, the operating frequency bands of NR-U are 5 GHz unlicensed spectrum and 6 GHz unlicensed spectrum. On the unlicensed spectrum, the design of NR-U should ensure fairness with other systems that have already worked on these unlicensed spectrums, such as WiFi. The principle of fairness is that the impact of NR-U on systems that have already been deployed on unlicensed spectrum (such as WiFi) cannot exceed the impact between these systems.

[0058] In order to ensure fair coexistence between systems on the unlicensed spectrum, energy detection has been agreed upon as a basic coexistence mechanism. The general energy detection mechanism is the LBT mechanism, the basic principle of which is that before a base station or terminal (transmitter) transmits data on the unlicensed spectrum, it needs to listen for a period of time as specified. If the listening result indicates that the channel is idle, the transmitter can transmit data to the receiver. If the listening result indicates that the channel is occupied, the transmitter needs to back off for a period of time as specified and continue to listen to the channel until the channel listening result shows that the channel is idle, then it can transmit data to the receiver.

[0059] Currently, four channel access mechanisms (category) are defined in NR-U, refer to TR 38.889:

[0060] Category 1: Direct transmission mechanism.

[0061] The direct transmission mechanism is used on the TX side to quickly transmit after the switching gap within the COT; the switching gap refers to the conversion time from receiving to transmitting, and the typical value is no more than 16us.

[0062] Category 2: LBT mechanism that does not require random back-off.

[0063] The LBT mechanism that does not require random back-off means that the time for the UE to monitor the channel is fixed, usually short, such as 25us.

[0064] Category 3: LBT mechanism with random back-off (fixed contention window).

[0065] In the LBT process, the transmission side randomly selects a random value in the contention window to determine the time to listen to the channel.

[0066] Category 4: LBT mechanism with random back-off (contention window is not fixed).

[0067] In the LBT process, the transmission side randomly takes a random value in the contention window to determine the time to listen to the channel. The contention window is variable.

[0068] In summary, for the terminal, the base station needs to transmit data to the terminal within the MCOT time. If the base station does not seize the channel, that is, outside the MCOT time, the terminal will not receive the scheduling data from the base station to the terminal.

[0069] Uplink transmission initiated by UE can be mainly divided into the following categories:

[0070] Scheduling Request (SR): used to request uplink resources.

[0071] Physical Random Access Channel (PRACH) transmission: Due to RACH triggering, UE needs to send msg1.

[0072] Physical Uplink Shared Channel (PUSCH) transmission: includes uplink data transmission based on configured grant and uplink data transmission based on dynamic grant.

[0073] Physical layer signaling transmission: including ACK / NACK feedback, channel state information (CSI) reporting, etc.

[0074] On unlicensed bands, before transmitting SR, PRACH or PUSCH, UE needs to use LBT to detect whether the channel is available. If it is not available, that is, LBT fails, the UE needs to wait until the next transmission opportunity to perform LBT again. If LBT failure is detected, the MAC layer needs to be notified of the LBT failure.

[0075] It should be noted that the communication system 100 can support the transmission of services such as industrial automation (Factory automation), transport automation (Transport Industry), and smart power (Electrical Power Distribution) in the 5G system.

[0076] For example, in order to support the transmission of URLLC services, the configuration grant (CG) can be enhanced, for example, multiple CG configurations are introduced, and the specific configuration and use of CG (such as supporting slot-level cycles, supporting automatic transmission of CG, etc.) are enhanced.

[0077] For example, in order to support the high latency requirements of URLLC services, the CG cycle can be enhanced for URLLC to support service cycles at any slot level.

[0078] For example, in order to support multiple URLLC services and high latency requirements of URLLC services, multiple configuration authorization (multiple CG) can be introduced for URLLC. For example, the Hybrid Automatic Repeat Request (HARQ) processes of different CG configurations are different, and harq-ProcID-Offset2 is used to ensure that the processes of different CGs are different.

[0079] Due to the conflict between CG resources and other resources, in order to ensure that the Media Access Control (MAC) Protocol Data Unit (PDU) (i.e., Deprioritized MAC PDU) that has been packaged in the CG resources is not discarded / transmitted as soon as possible, automatic transmission for CG can be introduced. For the CG that cannot be transmitted due to resource conflict, the subsequent CG resources in the same HARQ process and the same CG configuration can be used for new transmission. The use of automatic transmission can be determined by autonomousTx.

[0080] If the physical layer priorities are different and there is a conflict between CG and CG, MAC can indicate one or more MAC PDUs to the physical layer. Similarly, if there is a conflict between data and scheduling request (SR), MAC can also indicate SR and MAC PDU to the physical layer.

[0081] From the above, it can be seen that URLLC services need to be supported in NRU scenarios. In general, the terminal device can assume that there is only one resource that needs to be transmitted, which is indicated from the MAC layer to the physical layer, and performs LBT detection on this resource. That is, LBT failure recovery is performed based on the common recovery parameters configured in the network. However, when the common recovery parameters configured in the network actually take effect, they can no longer meet the needs of URLLC services.

[0082] In view of this, the LBT failure recovery process can be performed by differentiating services to avoid the situation where the common recovery parameters of the network configuration cannot meet the needs of the URLLC service when they actually take effect. Therefore, the present application proposes a method for performing different processing on different services by differentiating the LBT failure recovery process of the services.

[0083] Figure 2 A schematic flow chart of a wireless communication method 200 according to an embodiment of the present application is shown. The method 200 can be interactively executed by a network device and a terminal device. Figure 2 The terminal device shown in FIG. 1 may be a terminal device such as Figure 1 The terminal equipment shown, Figure 2 The network devices shown in can be Figure 1 The access network equipment shown.

[0084] like Figure 2 As shown, the method 200 may include some or all of the following contents:

[0085] S210, the terminal device receives multiple LBT failure recovery configurations sent by the network device;

[0086] S220, the terminal device detects continuous LBT failures and / or triggers a failure recovery process based on a first LBT failure recovery configuration corresponding to the first information among the multiple LBT failure recovery configurations.

[0087] Based on the first LBT failure recovery configuration corresponding to the first information among the multiple LBT failure recovery configurations, continuous LBT failures are detected and / or failure recovery processes are triggered, which is conducive to using more appropriate LBT failure recovery processes for different first information. Accordingly, the flexibility of configuring LBT failure recovery configurations can be improved, thereby improving service transmission performance and ensuring the needs of terminal equipment.

[0088] In some embodiments of the present application, the multiple LBT failure recovery configurations correspond to multiple scenarios, or the multiple LBT failure recovery configurations correspond to multiple network environments; the first information is the scenario or network environment when LBT fails.

[0089] It should be understood that, for the multiple LBT failure recovery configurations, one or at least one of the multiple LBT failure recovery configurations may correspond to multiple scenarios; or, the multiple LBT failure recovery configurations may also correspond to multiple scenarios respectively. Similarly, one or at least one of the multiple LBT failure recovery configurations may correspond to multiple network environments; or, the multiple LBT failure recovery configurations may also correspond to multiple network environments respectively.

[0090] Different interference situations are different in different scenarios, and the services that can be prioritized / supported in different scenarios are also different. Different LBT failure detection and recovery parameters are assigned to different scenarios, which is conducive to better adapting to different environments and / or different services, using more appropriate LBT failure recovery processes for different situations, and timely ensuring service transmission performance and terminal equipment requirements.

[0091] For example, the multiple scenarios or the multiple network environments are preset, or the multiple scenarios or the multiple network environments are determined based on a certain condition.

[0092] For example, the determination condition includes a condition determined based on at least one of the following information:

[0093] The load of network equipment;

[0094] Interference with network equipment;

[0095] Interference to terminal equipment; or

[0096] Number of LBT failures.

[0097] For example, the determination condition is a condition determined based on the interference situation of the terminal device, and the multiple preset scenarios include at least one of the following scenarios:

[0098] Interference with uncontrolled scenes;

[0099] Interfere with a partially controlled scene; or

[0100] Interference controlled scene.

[0101] For example, the interference uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being greater than or equal to the first threshold; and / or, the interference partially uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to the second threshold; and / or, the interference partially uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to the third threshold and greater than the fourth threshold; and / or, the interference controlled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to the fifth threshold.

[0102] In some embodiments of the present application, the method 200 may further include:

[0103] Maintain an LBT failure recovery configuration, wherein the LBT failure recovery configuration is the first LBT failure recovery configuration.

[0104] For example, the terminal device maintains the first LBT failure recovery configuration.

[0105] In some embodiments of the present application, the method 200 may further include:

[0106] In case the scenario or network environment changes when LBT fails, the first LBT failure recovery configuration is reset.

[0107] For example, when the scenario or network environment changes when LBT fails, the terminal device resets the first LBT failure recovery configuration.

[0108] In some embodiments of the present application, the multiple LBT failure recovery configurations correspond to multiple services, and the first information is the service targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple bearers, and the first information is the bearer targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple slices, and the first information is the slice targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple resources or resource types, and the first information is the resource or resource type targeted by the LBT failure.

[0109] For example, the multiple services include low-latency and high-reliability communication (URLLC) services and / or enhanced mobile ultra-wideband (eMBB) services.

[0110] Due to different requirements for latency and other aspects of different services, different LBT failure detection and recovery parameters are configured for different services, which is conducive to better adapting to different services, using more appropriate LBT failure recovery processes, and timely ensuring service transmission performance and terminal equipment requirements. Similarly, different LBT failure detection and recovery parameters are configured for different bearers / slices / resources / resource types, which is conducive to better adapting to different bearers / slices / resources / resource types, using more appropriate LBT failure recovery processes, and timely ensuring service transmission performance and terminal equipment requirements.

[0111] It should be understood that, for the multiple LBT failure recovery configurations, one or at least one of the multiple LBT failure recovery configurations may correspond to multiple services; or, the multiple LBT failure recovery configurations may also correspond to multiple services respectively. Similarly, one or at least one of the multiple LBT failure recovery configurations may correspond to multiple bearers; or, the multiple LBT failure recovery configurations may also correspond to multiple bearers respectively. Similarly, one or at least one of the multiple LBT failure recovery configurations may correspond to multiple slices; or, the multiple LBT failure recovery configurations may also correspond to multiple slices respectively. Similarly, one or at least one of the multiple LBT failure recovery configurations may correspond to multiple resources; or, the multiple LBT failure recovery configurations may also correspond to multiple resources respectively. Similarly, one or at least one of the multiple LBT failure recovery configurations may correspond to multiple resource types; or, the multiple LBT failure recovery configurations may also correspond to multiple resource types respectively.

[0112] In some embodiments of the present application, the multiple LBT failure recovery configurations include at least one dedicated LBT failure recovery configuration and a public LBT failure recovery configuration, the at least one dedicated LBT failure recovery configuration includes a dedicated LBT failure recovery configuration configured for at least one of the services, bearers, slices, resources, or resource types, and the first information is at least one of the services, bearers, slices, resources, or resource types targeted by the LBT failure; the public LBT failure recovery configuration refers to an LBT failure recovery configuration that does not distinguish between at least one of the services, bearers, slices, resources, or resource types, and the first information is an LBT failure indication that does not distinguish between at least one of the services, bearers, slices, resources, or resource types.

[0113] Due to different requirements for latency and other aspects of different services, different LBT failure detection and recovery parameters are configured for different services, which is conducive to better adapting to different services, using more appropriate LBT failure recovery processes, and timely ensuring service transmission performance and UE requirements. Similarly, different LBT failure detection and recovery parameters are configured for different bearers / slices / resources / resource types, which is conducive to better adapting to different bearers / slices / resources / resource types, using more appropriate LBT failure recovery processes, and timely ensuring service transmission performance and UE requirements.

[0114] In addition, through the public LBT failure recovery configuration and the dedicated LBT failure recovery configuration, both the transmission performance of the overall UE and the transmission performance of specific services are guaranteed.

[0115] It should be understood that, for the multiple LBT failure recovery configurations, one or at least one of the multiple LBT failure recovery configurations may correspond to multiple services; or, the multiple LBT failure recovery configurations may also correspond to multiple services respectively. Similarly, one or at least one of the multiple LBT failure recovery configurations may correspond to multiple bearers; or, the multiple LBT failure recovery configurations may also correspond to multiple bearers respectively. Similarly, one or at least one of the multiple LBT failure recovery configurations may correspond to multiple slices; or, the multiple LBT failure recovery configurations may also correspond to multiple slices respectively. Similarly, one or at least one of the multiple LBT failure recovery configurations may correspond to multiple resources; or, the multiple LBT failure recovery configurations may also correspond to multiple resources respectively. Similarly, one or at least one of the multiple LBT failure recovery configurations may correspond to multiple resource types; or, the multiple LBT failure recovery configurations may also correspond to multiple resource types respectively.

[0116] In some embodiments of the present application, the method 200 may further include:

[0117] Maintain at least one LBT failure recovery configuration, the at least one LBT failure recovery configuration including an LBT failure recovery configuration for at least one of a service, bearer, slice, resource or resource type, and / or an LBT failure recovery configuration that does not distinguish at least one of a service, bearer, slice, resource or resource type, the at least one LBT failure recovery configuration including the first LBT failure recovery configuration.

[0118] For example, the terminal device maintains the at least one dedicated LBT failure recovery configuration and the public LBT failure recovery configuration.

[0119] In some embodiments of the present application, the failure recovery process refers to a failure recovery process for the BWP triggered by at least one of the services, bearers, slices, resources or resource types on the bandwidth part BWP; or the failure recovery process refers to a failure recovery process for the service cell triggered by at least one of the services, bearers, slices, resources or resource types on the service cell.

[0120] In some embodiments of the present application, the method 200 may further include:

[0121] Send reporting information to the media access control MAC layer, where the reporting information is used to indicate the failure of triggering LBT.

[0122] For example, the MAC layer of the terminal device receives reporting information from the physical layer.

[0123] For example, the reporting information is used to indicate at least one of the services, bearers, slices, resources or resource types targeted by the triggered LBT failure.

[0124] In some embodiments of the present application, the multiple LBT failure recovery configurations are indicated or configured by the network device, or are predefined.

[0125] For example, the multiple LBT failure recovery configurations can be configured through RRC configuration information.

[0126] In some embodiments of the present application, each of the multiple LBT failure recovery configurations includes a corresponding counter and / or a corresponding timer.

[0127] For example, the corresponding counter is configured with an initial value and / or a maximum value.

[0128] Exemplarily, the initial value and / or maximum value of the corresponding counter configuration may be configured by the network through RRC, or may be specified by the protocol.

[0129] In some embodiments of the present application, the first LBT failure recovery configuration is indicated by a network device, or the first LBT failure recovery configuration is determined by a terminal device, or the first LBT failure recovery configuration is determined by a semi-static configuration.

[0130] For example, the first LBT failure recovery configuration can be configured through RRC configuration information.

[0131] In some embodiments of the present application, the first LBT failure recovery configuration includes a first counter and / or a first timer.

[0132] For example, the first counter is configured with an initial value and / or a maximum value.

[0133] Exemplarily, the initial value and / or maximum value of the first counter may be configured by the network through RRC, or may be specified by the protocol.

[0134] In some embodiments of the present application, the S220 may include:

[0135] When an LBT failure indication is received from the physical layer, the count of the first counter is increased by 1; and / or the first timer is restarted.

[0136] In some embodiments of the present application, the S220 may include:

[0137] When the count of the first counter is greater than or equal to the maximum value of the first counter, continuous LBT failure is determined or triggered.

[0138] In some embodiments of the present application, the S220 may include:

[0139] When the timing of the first timer exceeds the duration of the first timer or the triggered continuous LBT failure is cancelled, the first counter is reset, and / or the first timer is stopped.

[0140] The method 200 is described below in conjunction with a specific embodiment.

[0141] Embodiment 1:

[0142] The UE receives multiple sets of LBT failure recovery configurations, and uses different LBT failure recovery configurations for different scenarios to detect continuous LBT failures and / or trigger corresponding failure recovery processes.

[0143] For example, the specific process may include the following steps:

[0144] Step 1:

[0145] The network device configures multiple sets of LBT failure recovery configurations for the UE, and the multiple sets of LBT failure recovery configurations are used for different scenarios, for detecting continuous LBT failures corresponding to different scenarios, and / or triggering corresponding failure recovery processes.

[0146] For example, scenarios corresponding to different LBT failure recovery configurations. For example, LBT failure recovery configuration 1 corresponds to scenario 1 (such as uncontrolled interference scenario, partially controlled interference scenario), and LBT failure recovery configuration 2 corresponds to scenario 2 (such as controlled interference scenario). Optionally, the LBT failure recovery parameter A (such as counter maximum value, timer) corresponding to scenario 1 takes a smaller value.

[0147] Another example is the selection conditions of the scenarios corresponding to different LBT failure recovery configurations. For example, if the channel interference / LBT failure times is greater than or equal to the threshold, then select LBT failure recovery configuration 1, otherwise, select LBT failure recovery configuration 2. Optionally, the LBT failure recovery parameter A (such as the maximum value of the counter, the timer) corresponding to scenario 1 is smaller.

[0148] Optionally, the network device dynamically indicates which LBT failure recovery configuration to use. Alternatively, the network device semi-statically configures a pattern used by the LBT failure recovery configuration.

[0149] Step 2:

[0150] The UE receives multiple sets of LBT failure recovery configurations configured by the network, and selects LBT failure recovery parameters to be used according to the information in step 1.

[0151] For example, the LBT failure recovery parameters include at least one of the following: a counter (eglbt-FailureInstanceMaxCount, ie, the maximum value of the counter), a timer (lbt-FailureDetectionTimer).

[0152] Optionally, the initial value of the counter is 0. Optionally, it can be specified by the protocol.

[0153] Optionally, the UE maintains only one set of configurations at a time. It should be understood that the LBT failure recovery process may adopt a recovery process defined by a protocol.

[0154] In addition, for the LBT failure scenario or network environment, based on its corresponding LBT failure recovery configuration, continuous LBT failures are detected, and / or the corresponding failure recovery process is triggered.

[0155] For example, in scenario 1, the LBT failure recovery parameters corresponding to scenario 1 are used to detect continuous LBT failures and / or trigger the corresponding failure recovery process; in scenario 2, the LBT failure recovery parameters corresponding to scenario 2 are used to detect continuous LBT failures and / or trigger the corresponding failure recovery process.

[0156] Different interference situations are different for different scenarios, and the services that can be prioritized / supported in different scenarios are also different. Different LBT failure detection and recovery parameters are assigned to different scenarios, which is conducive to better adapting to different environments and / or different services, using more appropriate LBT failure recovery processes for different situations, and timely ensuring service transmission performance and UE requirements.

[0157] Embodiment 2:

[0158] The UE receives multiple sets of LBT failure recovery configurations, and uses different LBT failure recovery configurations for different services / bearers / slices / resources / resource types to detect continuous LBT failures and / or trigger corresponding failure recovery processes.

[0159] For example, the specific process may include the following steps:

[0160] Step 1:

[0161] The network device configures multiple sets of LBT failure recovery configurations for the UE, and the multiple sets of LBT failure recovery configurations are used for different services / bearers / slices / resources / resource types, and are used to detect continuous LBT failures corresponding to different services / bearers / slices / resources / resource types, and / or trigger corresponding failure recovery processes.

[0162] For example, services corresponding to different LBT failure recovery configurations. For example, LBT failure recovery configuration 1 corresponds to service 1, and LBT failure recovery configuration 2 corresponds to service 2. Optionally, the LBT failure recovery parameter A (such as a counter maximum value, a timer) corresponding to service 1 (such as a URLLC service) takes a smaller value.

[0163] Another example is the resource types corresponding to different LBT failure recovery configurations. For example, type 1 resources (such as high priority resources) correspond to LBT failure recovery configuration 1, and type 2 resources or other resources (such as low priority resources) correspond to LBT failure recovery configuration 2. Optionally, the LBT failure recovery parameter A (such as counter maximum value, timer) corresponding to service 1 (such as high priority resource service) takes a smaller value.

[0164] Step 2:

[0165] The UE receives multiple sets of LBT failure recovery configurations configured by the network, and selects corresponding LBT failure recovery parameters for different services according to the information in step 1.

[0166] For example, the LBT failure recovery parameters include at least one of the following: a counter (eglbt-FailureInstanceMaxCount, ie, the maximum value of the counter), a timer (lbt-FailureDetectionTimer).

[0167] Optionally, the initial value of the counter is 0. Optionally, it can be specified by the protocol.

[0168] Optionally, the UE maintains two sets of configurations simultaneously.

[0169] It should be understood that the LBT failure recovery process may adopt the recovery process defined by the protocol.

[0170] In addition, for the service / bearer / slice / resource / resource type with LBT failure, based on its corresponding LBT failure recovery configuration, continuous LBT failures are detected, and / or the corresponding failure recovery process is triggered.

[0171] In some embodiments of the present application, for high-priority resources or URLLC services, LBT failure recovery configuration 1 is used to detect continuous LBT failures and / or trigger a corresponding failure recovery process; and, for low-priority resources or eMBB services, LBT failure recovery configuration 2 is used to detect continuous LBT failures and / or trigger a corresponding failure recovery process.

[0172] For example, LBT failure recovery configuration 1 is used for URLLC services, that is, as long as an LBT failure corresponding to the URLLC is received from the bottom layer, the corresponding counter is incremented by 1 and the corresponding timer is restarted. If the corresponding counter is greater than or equal to the corresponding maximum value, the UE triggers a continuous LBT failure (which can be for the BWP of the cell). If the corresponding timer times out or the triggered continuous LBT failure is canceled, the corresponding counter is reset.

[0173] For another example, LBT failure recovery configuration 2 is used for eMBB services, that is, as long as an LBT failure corresponding to eMBB is received from the bottom layer, the corresponding counter is incremented by 1 and the corresponding timer is restarted. If the corresponding counter is greater than or equal to the corresponding maximum value, the UE triggers a continuous LBT failure (which can be for the BWP of the cell). If the corresponding timer times out or the triggered continuous LBT failure is canceled, the corresponding counter is reset.

[0174] Optionally, if LBT failure recovery is triggered for any service / bearer / slice / resource / resource type, the UE considers that there are continuous LBT failures in this BWP or service cell.

[0175] Optionally, when the UE reports an LBT failure, it indicates the service / bearer / slice / resource / resource type corresponding to the triggering LBT failure.

[0176] Due to different requirements for latency and other aspects of different services, different LBT failure detection and recovery parameters are configured for different services, which is conducive to better adapting to different services, using more appropriate LBT failure recovery processes, and timely ensuring service transmission performance and UE requirements. Similarly, different LBT failure detection and recovery parameters are configured for different bearers / slices / resources / resource types, which is conducive to better adapting to different bearers / slices / resources / resource types, using more appropriate LBT failure recovery processes, and timely ensuring service transmission performance and UE requirements.

[0177] Embodiment three:

[0178] The UE receives multiple sets of LBT failure recovery configurations, namely common LBT failure recovery configurations and at least one special LBT failure recovery configuration, wherein the special LBT failure recovery configuration may be for a specific service / bearer / slice / resource / resource type.

[0179] For example, the specific process may include the following steps:

[0180] Step 1:

[0181] The network device configures multiple sets of LBT failure recovery configurations for the UE, and the multiple sets of LBT failure recovery configurations are used for different services / bearers / slices / resources / resource types and LBT failure indications that do not distinguish between services / bearers / slices / resources / resource types, and are used to detect corresponding continuous LBT failures and / or trigger corresponding failure recovery processes.

[0182] For example, the multiple sets of LBT failure recovery configurations may include a common LBT failure recovery configuration and at least one special LBT failure recovery configuration. The special LBT failure recovery configuration is used for a service / bearer / slice / resource / resource type. The common LBT failure recovery configuration does not distinguish between different services / bearers / slices / resources / resource types.

[0183] Step 2:

[0184] The UE receives multiple sets of LBT failure recovery configurations configured by the network, and selects corresponding LBT failure recovery parameters for different situations according to the information in step 1.

[0185] For example, the LBT failure recovery parameters include at least one of the following: a counter (eglbt-FailureInstanceMaxCount, ie, the maximum value of the counter), a timer (lbt-FailureDetectionTimer).

[0186] Optionally, the initial value of the counter is 0. Optionally, it can be specified by the protocol.

[0187] For example, the UE maintains two sets of configurations simultaneously.

[0188] It should be understood that the LBT failure recovery process may adopt the recovery process defined by the protocol.

[0189] In addition, for the service / bearer / slice / resource / resource type with LBT failure, based on its corresponding LBT failure recovery configuration, continuous LBT failures are detected, and / or the corresponding failure recovery process is triggered; or, for LBT failures that do not distinguish between service / bearer / slice / resource / resource type, based on the common LBT failure recovery configuration, continuous LBT failures are detected, and / or the corresponding failure recovery process is triggered.

[0190] For example, the public LBT failure recovery configuration is used for all service / bearer / slice / resource types, that is, as long as an LBT failure is received from the bottom layer, the counter of the public LBT failure recovery configuration is increased by 1, and the timer of the public LBT failure recovery configuration is restarted. If the counter of the public LBT failure recovery configuration is greater than or equal to the maximum value of the counter of the public LBT failure recovery configuration, the UE triggers a continuous LBT failure (which can be for the BWP of the cell). If the timer of the public LBT failure recovery configuration times out or the triggered continuous LBT failure is canceled, the counter of the public LBT failure recovery configuration can be reset.

[0191] For another example, the dedicated LBT failure recovery configuration is used for specific service / bearer / slice / resource type, that is, only when an LBT failure corresponding to the service / bearer / slice / resource type is received from the bottom layer, the counter of the corresponding dedicated LBT failure recovery configuration is increased by 1, and the corresponding special timer is restarted. If the counter of the corresponding dedicated LBT failure recovery configuration is greater than or equal to the maximum value of the corresponding dedicated LBT failure recovery configuration counter, the UE triggers a continuous LBT failure (which can be for the BWP of the cell). If the timer of the corresponding dedicated LBT failure recovery configuration times out or the triggered continuous LBT failure is canceled, the counter of the corresponding dedicated LBT failure recovery configuration is reset.

[0192] Optionally, if LBT failure recovery is triggered for any service / bearer / slice / resource / resource type, the UE considers that there are continuous LBT failures in this BWP or service cell.

[0193] Optionally, when the UE reports an LBT failure, it indicates the service / bearer / slice / resource / resource type corresponding to the triggering LBT failure.

[0194] Due to different requirements for latency and other aspects of different services, different LBT failure detection and recovery parameters are configured for different services, which is conducive to better adapting to different services, using more appropriate LBT failure recovery processes, and timely ensuring service transmission performance and UE requirements. Similarly, different LBT failure detection and recovery parameters are configured for different bearers / slices / resources / resource types, which is conducive to better adapting to different bearers / slices / resources / resource types, using more appropriate LBT failure recovery processes, and timely ensuring service transmission performance and UE requirements.

[0195] In addition, compared with Example 2, the public LBT failure recovery configuration and the dedicated LBT failure recovery configuration ensure both the transmission performance of the overall UE and the transmission performance of specific services.

[0196] Figure 3 A schematic flow chart of a wireless communication method 300 according to an embodiment of the present application is shown. The method 300 can be interactively executed by a network device and a terminal device. Figure 3 The terminal device shown in FIG. 1 may be a terminal device such as Figure 1 The terminal equipment shown, Figure 3 The network devices shown in can be Figure 1 The access network equipment shown.

[0197] like Figure 3 As shown, the method 300 may include some or all of the following contents:

[0198] S310, receiving a second LBT failure recovery configuration and at least one set of parameters;

[0199] S320, based on the second LBT failure recovery configuration and the first parameter, detect continuous LBT failures and / or trigger a failure recovery process; the first parameter is a parameter in the at least one group of parameters corresponding to the second information, and each group of parameters in the at least one group of parameters is used to adjust the second counter and / or second timer in the second LBT failure recovery configuration.

[0200] In some embodiments of the present application, the at least one set of parameters corresponds to at least one scenario, or the at least one set of parameters corresponds to at least one network environment, and the second information is the scenario or network environment when LBT fails.

[0201] For example, the multiple scenarios or the multiple network environments are preset, or the multiple scenarios or the multiple network environments are determined based on a certain condition.

[0202] For example, the determination condition includes a condition determined based on at least one of the following information:

[0203] The load of network equipment;

[0204] Interference with network equipment;

[0205] Interference to terminal equipment; or

[0206] Number of LBT failures.

[0207] For example, the determination condition is a condition determined based on the interference situation of the terminal device, and the multiple preset scenarios include at least one of the following scenarios:

[0208] Interference with uncontrolled scenes;

[0209] Interfere with a partially controlled scene; or

[0210] Interference controlled scene.

[0211] For example, the interference uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being greater than or equal to the first threshold; and / or, the interference partially uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to the second threshold; and / or, the interference partially uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to the third threshold and greater than the fourth threshold; and / or, the interference controlled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to the fifth threshold.

[0212] In some embodiments of the present application, the at least one set of parameters corresponds to multiple services, and the second information is the service targeted by the LBT failure; or the at least one set of parameters corresponds to multiple bearers, and the second information is the bearer targeted by the LBT failure; or the at least one set of parameters corresponds to multiple slices, and the second information is the slice targeted by the LBT failure; or the at least one set of parameters corresponds to multiple resource types, and the second information is the type of resource targeted by the LBT failure.

[0213] For example, the multiple services include low-latency and highly reliable communications URLLC and / or enhanced mobile ultra-wideband eMBB.

[0214] In some embodiments of the present application, the failure recovery process refers to a failure recovery process for the BWP triggered by at least one of the services, bearers, slices, resources or resource types on the bandwidth part BWP; or the failure recovery process refers to a failure recovery process for the service cell triggered by at least one of the services, bearers, slices, resources or resource types on the service cell.

[0215] In some embodiments of the present application, the method 300 may further include:

[0216] Send reporting information to the media access control MAC layer, where the reporting information is used to indicate the failure of triggering LBT.

[0217] For example, the reporting information is used to indicate at least one of the services, bearers, slices, resources or resource types targeted by the triggered LBT failure.

[0218] In some embodiments of the present application, the at least one set of parameters is determined or selected by the terminal device, or the at least one set of parameters is pre-configured, or the at least one set of parameters is configured or indicated by the network.

[0219] In some embodiments of the present application, the at least one set of parameters includes parameters for adjusting the second counter and / or parameters for adjusting the second timer.

[0220] In some embodiments of the present application, the first parameter includes a second parameter for adjusting the second counter and / or a third parameter for adjusting the second timer.

[0221] For example, the second parameter is an impact factor or a weight value.

[0222] For example, the third parameter is an influence factor or a weight value.

[0223] For example, the second counter is configured with an initial value and / or a maximum value.

[0224] Optionally, the initial value of the second counter is 0. Optionally, it may be specified by a protocol.

[0225] In some embodiments of the present application, the S320 may include:

[0226] Based on the second counter and the second parameter, determine the count value; based on the first duration of the second timer and the third parameter, determine the second duration of the second timer; based on the maximum value of the second counter and / or the second duration, detect continuous LBT failures and / or trigger a failure recovery process.

[0227] In some embodiments of the present application, the S320 may include:

[0228] When an LBT failure indication is received from the physical layer, the count of the second counter is increased by the count value; and / or the second timer is restarted.

[0229] In some embodiments of the present application, the S320 may include:

[0230] In case the count of the second counter is greater than or equal to the maximum value of the second counter, continuous LBT failure is determined or triggered.

[0231] In some embodiments of the present application, the S320 may include:

[0232] When the timing of the second timer exceeds the second duration or the triggered continuous LBT failure is cancelled, the second counter is reset, and / or the second timer is stopped.

[0233] The method 300 is described below in conjunction with Example 4.

[0234] Embodiment 4:

[0235] The UE receives a set of LBT failure recovery configurations, but the impact factors or weighted values ​​on the counter and / or timer are different for different services / bearers / slices / resources / resource types / environments.

[0236] For example, the specific process may include the following steps:

[0237] Step 1:

[0238] The network device configures LBT failure recovery parameters for the UE, and the LBT failure recovery parameters are used to detect continuous LBT failures corresponding to different services / bearers / slices / resources / resource types / environments, and / or trigger corresponding failure recovery processes.

[0239] For example, the LBT failure recovery parameters include an LBT failure recovery configuration (only one set). Optionally, the LBT failure recovery configuration may include the following counter (eg lbt-FailureInstanceMaxCount, ie, the maximum value of the counter) and / or a timer (lbt-FailureDetectionTimer).

[0240] Optionally, the initial value of the counter is 0. Optionally, it can be specified by the protocol.

[0241] For example, the LBT failure recovery parameters include different impact factors or weighted values ​​corresponding to different services / bearers / slices / resources / resource types / environments, and the impact factors or weighted values ​​are used to affect the counter and / or timer. Optionally, the impact factors or weighted values ​​can also be pre-configured or selected by the UE itself.

[0242] For example, the final counter counting result is a function of the physical layer reporting value and the impact factor or weighted value, such as 1*impact factor or weighted value; for example, the final timer duration is a function of the physical layer reporting value and the impact factor or weighted value, such as the configured timer duration*impact factor or weighted value.

[0243] Step 2:

[0244] The UE receives the LBT failure recovery parameters configured by the network, determines the corresponding influencing factors or weighted values ​​for different services / bearers / slices / resources / resource types / environments, corrects the counter and / or timer, performs continuous LBT failure detection, and / or triggers the corresponding failure recovery process.

[0245] Optional: When PHY reports LBT failure to the upper layer, it indicates the service / bearer / slice / resource / resource type / environment that triggered the LBT failure.

[0246] For example, as long as an LBT failure corresponding to the URLLC is received from the bottom layer, the corresponding counter is increased by 1*factor1, and the corresponding timer is restarted (the timer duration is the configured duration*factor3). If the corresponding counter is greater than or equal to the corresponding maximum value, the UE triggers a continuous LBT failure (which can be for the BWP of the cell). If the corresponding timer times out or the triggered continuous LBT failure is canceled, the corresponding counter is reset.

[0247] For another example, as long as an LBT failure corresponding to eMBB is received from the bottom layer, the corresponding counter is increased by 1*factor2, and the corresponding timer is restarted (the timer duration is the configured duration*factor4). If the corresponding counter is greater than or equal to the corresponding maximum value, the UE triggers a continuous LBT failure (which can be for the BWP of the cell). If the corresponding timer times out or the triggered continuous LBT failure is canceled, the corresponding counter is reset.

[0248] Due to different requirements for latency and other aspects of different services. Compared with Embodiment 2-3, the UE only maintains a set of LBT failure recovery parameters, reducing the complexity of the UE. In addition, through the influencing factors, the impact of different services or scenarios is considered, ensuring that the needs of different services / scenarios are reflected, serving different scenarios / services, and restoring service transmission.

[0249] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all belong to the protection scope of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will not further explain various possible combinations. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the ideas of the present application, they should also be regarded as the contents disclosed in the present application.

[0250] It should also be understood that in various method embodiments of the present application, the size of the sequence number of each process does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. In addition, in the embodiment of the present application, the terms "downlink" and "uplink" are used to indicate the transmission direction of the signal or data, wherein "downlink" is used to indicate that the transmission direction of the signal or data is a first direction sent from the site to the user equipment of the cell, and "uplink" is used to indicate that the transmission direction of the signal or data is a second direction sent from the user equipment of the cell to the site, for example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiment of the present application, the term "and / or" is only a description of the association relationship of the associated objects, indicating that there can be three relationships. Specifically, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0251] Combination of the above Figures 1 to 3The method embodiment of the present application is described in detail below. Figures 4 to 9 The device embodiments of the present application are described in detail.

[0252] Figure 4 It is a schematic block diagram of a terminal device 400 according to an embodiment of the present application.

[0253] like Figure 4 As shown, the terminal device 400 may include:

[0254] A receiving unit 410, configured to receive a plurality of LBT failure recovery configurations;

[0255] The processing unit 420 is used to detect continuous LBT failures and / or trigger a failure recovery process based on a first LBT failure recovery configuration corresponding to the first information among the multiple LBT failure recovery configurations.

[0256] In some embodiments of the present application, the multiple LBT failure recovery configurations correspond to multiple scenarios, or the multiple LBT failure recovery configurations correspond to multiple network environments; the first information is the scenario or network environment when LBT fails.

[0257] In some embodiments of the present application, the multiple scenarios or the multiple network environments are preset, or the multiple scenarios or the multiple network environments are determined based on a certain condition.

[0258] In some embodiments of the present application, the determining condition includes a condition determined based on at least one of the following information:

[0259] The load of network equipment;

[0260] Interference with network equipment;

[0261] Interference to terminal equipment; or

[0262] Number of LBT failures.

[0263] In some embodiments of the present application, the determination condition is a condition determined based on the interference situation of the terminal device, and the multiple preset scenarios include at least one of the following scenarios:

[0264] Interference with uncontrolled scenes;

[0265] Interfere with a partially controlled scene; or

[0266] Interference controlled scene.

[0267] In some embodiments of the present application, the interference uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being greater than or equal to a first threshold; and / or, the interference partially uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to a third threshold and greater than a fourth threshold; and / or, the interference controlled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to a fifth threshold.

[0268] In some embodiments of the present application, the processing unit 420 is further configured to:

[0269] Maintain an LBT failure recovery configuration, wherein the LBT failure recovery configuration is the first LBT failure recovery configuration.

[0270] In some embodiments of the present application, the processing unit 420 is further configured to:

[0271] In case the scenario or network environment changes when LBT fails, the first LBT failure recovery configuration is reset.

[0272] In some embodiments of the present application, the multiple LBT failure recovery configurations correspond to multiple services, and the first information is the service targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple bearers, and the first information is the bearer targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple slices, and the first information is the slice targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple resources or resource types, and the first information is the resource or resource type targeted by the LBT failure.

[0273] In some embodiments of the present application, the multiple services include low-latency and high-reliability communication (URLLC) services and / or enhanced mobile ultra-wideband (eMBB) services.

[0274] In some embodiments of the present application, the multiple LBT failure recovery configurations include at least one dedicated LBT failure recovery configuration and a public LBT failure recovery configuration, the at least one dedicated LBT failure recovery configuration includes a dedicated LBT failure recovery configuration configured for at least one of the services, bearers, slices, resources, or resource types, and the first information is at least one of the services, bearers, slices, resources, or resource types targeted by the LBT failure; the public LBT failure recovery configuration refers to an LBT failure recovery configuration that does not distinguish between at least one of the services, bearers, slices, resources, or resource types, and the first information is an LBT failure indication that does not distinguish between at least one of the services, bearers, slices, resources, or resource types.

[0275] In some embodiments of the present application, the method further includes:

[0276] Maintain at least one LBT failure recovery configuration, the at least one LBT failure recovery configuration including an LBT failure recovery configuration for at least one of a service, bearer, slice, resource or resource type, and / or an LBT failure recovery configuration that does not distinguish at least one of a service, bearer, slice, resource or resource type, the at least one LBT failure recovery configuration including the first LBT failure recovery configuration.

[0277] In some embodiments of the present application, the failure recovery process refers to a failure recovery process for the BWP triggered by at least one of the services, bearers, slices, resources or resource types on the bandwidth part BWP; or the failure recovery process refers to a failure recovery process for the service cell triggered by at least one of the services, bearers, slices, resources or resource types on the service cell.

[0278] In some embodiments of the present application, the processing unit 420 is further configured to:

[0279] Send reporting information to the media access control MAC layer, where the reporting information is used to indicate the failure of triggering LBT.

[0280] In some embodiments of the present application, the reporting information is used to indicate at least one of the services, bearers, slices, resources or resource types targeted by the triggered LBT failure.

[0281] In some embodiments of the present application, the first LBT failure recovery configuration is indicated by a network device, or the first LBT failure recovery configuration is determined by a terminal device, or the first LBT failure recovery configuration is determined by a semi-static configuration.

[0282] In some embodiments of the present application, the first LBT failure recovery configuration includes a first counter and / or a first timer.

[0283] In some embodiments of the present application, the first counter is configured with an initial value and / or a maximum value.

[0284] In some embodiments of the present application, the processing unit 420 is specifically used to:

[0285] In case of receiving an LBT failure indication from the physical layer, increasing the count of the first counter by 1; and / or,

[0286] Restart the first timer.

[0287] In some embodiments of the present application, the processing unit 420 is specifically used to:

[0288] When the count of the first counter is greater than or equal to the maximum value of the first counter, continuous LBT failure is determined or triggered.

[0289] In some embodiments of the present application, the processing unit 420 is specifically used to:

[0290] When the timing of the first timer exceeds the duration of the first timer or the triggered continuous LBT failure is cancelled, resetting the first counter, and / or;

[0291] Stop the first timer.

[0292] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. Specifically, Figure 4 The terminal device 400 shown may correspond to the corresponding subject in the method 200 of the embodiment of the present application, and the aforementioned and other operations and / or functions of each unit in the terminal device 400 are respectively to implement Figure 2 For the sake of brevity, the corresponding processes in each method are not repeated here.

[0293] Figure 5 It is a schematic block diagram of a network device 500 according to an embodiment of the present application.

[0294] The sending unit 510 is used to send multiple LBT failure recovery configurations, where the first LBT failure recovery configuration corresponding to the first information is used by the terminal device to detect continuous LBT failures and / or trigger a failure recovery process.

[0295] In some embodiments of the present application, the multiple LBT failure recovery configurations correspond to multiple scenarios, or the multiple LBT failure recovery configurations correspond to multiple network environments; the first information is the scenario or network environment when LBT fails.

[0296] In some embodiments of the present application, the multiple scenarios or the multiple network environments are preset, or the multiple scenarios or the multiple network environments are determined based on a certain condition.

[0297] In some embodiments of the present application, the determining condition includes a condition determined based on at least one of the following information:

[0298] The load of network equipment;

[0299] Interference with network equipment;

[0300] Interference to terminal equipment; or

[0301] Number of LBT failures.

[0302] In some embodiments of the present application, the determination condition is a condition determined based on the interference situation of the terminal device, and the multiple preset scenarios include at least one of the following scenarios:

[0303] Interference with uncontrolled scenes;

[0304] Interfere with a partially controlled scene; or

[0305] Interference controlled scene.

[0306] In some embodiments of the present application, the interference uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being greater than or equal to a first threshold; and / or, the interference partially uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to a third threshold and greater than a fourth threshold; and / or, the interference controlled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to a fifth threshold.

[0307] In some embodiments of the present application, the multiple LBT failure recovery configurations correspond to multiple services, and the first information is the service targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple bearers, and the first information is the bearer targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple slices, and the first information is the slice targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple resources or resource types, and the first information is the resource or resource type targeted by the LBT failure.

[0308] In some embodiments of the present application, the multiple services include low-latency and high-reliability communication (URLLC) services and / or enhanced mobile ultra-wideband (eMBB) services.

[0309] In some embodiments of the present application, the multiple LBT failure recovery configurations include at least one dedicated LBT failure recovery configuration and a public LBT failure recovery configuration, the at least one dedicated LBT failure recovery configuration includes a dedicated LBT failure recovery configuration configured for at least one of the services, bearers, slices, resources, or resource types, and the first information is at least one of the services, bearers, slices, resources, or resource types targeted by the LBT failure; the public LBT failure recovery configuration refers to an LBT failure recovery configuration that does not distinguish between at least one of the services, bearers, slices, resources, or resource types, and the first information is an LBT failure indication that does not distinguish between at least one of the services, bearers, slices, resources, or resource types.

[0310] In some embodiments of the present application, the failure recovery process refers to a failure recovery process for the BWP triggered by at least one of the services, bearers, slices, resources or resource types on the bandwidth part BWP; or the failure recovery process refers to a failure recovery process for the service cell triggered by at least one of the services, bearers, slices, resources or resource types on the service cell.

[0311] In some embodiments of the present application, the first LBT failure recovery configuration is indicated by a network device, or the first LBT failure recovery configuration is determined by a terminal device, or the first LBT failure recovery configuration is determined by a semi-static configuration.

[0312] In some embodiments of the present application, the first LBT failure recovery configuration includes a first counter and / or a first timer.

[0313] In some embodiments of the present application, the first counter is configured with an initial value and / or a maximum value.

[0314] like Figure 5 As shown, the network device 500 may include:

[0315] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. Specifically, Figure 5 The network device 500 shown may correspond to the corresponding subject in the method 200 of the embodiment of the present application, and the aforementioned and other operations and / or functions of each unit in the network device 500 are respectively to implement Figure 2 For the sake of brevity, the corresponding processes in each method are not repeated here.

[0316] Figure 6It is a schematic block diagram of a terminal device 600 according to an embodiment of the present application.

[0317] like Figure 6 As shown, the terminal device 600 may include:

[0318] A receiving unit 610, configured to receive a second LBT failure recovery configuration and at least one set of parameters;

[0319] Processing unit 620 is used to detect continuous LBT failures and / or trigger a failure recovery process based on the second LBT failure recovery configuration and a first parameter; the first parameter is a parameter in the at least one group of parameters corresponding to the second information, and each group of parameters in the at least one group of parameters is used to adjust the second counter and / or second timer in the second LBT failure recovery configuration.

[0320] In some embodiments of the present application, the at least one set of parameters corresponds to at least one scenario, or the at least one set of parameters corresponds to at least one network environment, and the second information is the scenario or network environment when LBT fails.

[0321] In some embodiments of the present application, the multiple scenarios or the multiple network environments are preset, or the multiple scenarios or the multiple network environments are determined based on a certain condition.

[0322] In some embodiments of the present application, the determining condition includes a condition determined based on at least one of the following information:

[0323] The load of network equipment;

[0324] Interference with network equipment;

[0325] Interference to terminal equipment; or

[0326] Number of LBT failures.

[0327] In some embodiments of the present application, the determination condition is a condition determined based on the interference situation of the terminal device, and the multiple preset scenarios include at least one of the following scenarios:

[0328] Interference with uncontrolled scenes;

[0329] Interfere with a partially controlled scene; or

[0330] Interference controlled scene.

[0331] In some embodiments of the present application, the interference uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being greater than or equal to a first threshold; and / or, the interference partially uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to a third threshold and greater than a fourth threshold; and / or, the interference controlled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to a fifth threshold.

[0332] In some embodiments of the present application, the at least one set of parameters corresponds to multiple services, and the second information is the service targeted by the LBT failure; or the at least one set of parameters corresponds to multiple bearers, and the second information is the bearer targeted by the LBT failure; or the at least one set of parameters corresponds to multiple slices, and the second information is the slice targeted by the LBT failure; or the at least one set of parameters corresponds to multiple resource types, and the second information is the type of resource targeted by the LBT failure.

[0333] In some embodiments of the present application, the multiple services include low-latency high-reliability communication URLLC and / or enhanced mobile ultra-wideband eMBB.

[0334] In some embodiments of the present application, the failure recovery process refers to a failure recovery process for the BWP triggered by at least one of the services, bearers, slices, resources or resource types on the bandwidth part BWP; or the failure recovery process refers to a failure recovery process for the service cell triggered by at least one of the services, bearers, slices, resources or resource types on the service cell.

[0335] In some embodiments of the present application, the receiving unit 610 is further configured to:

[0336] Send reporting information to the media access control MAC layer, where the reporting information is used to indicate the failure of triggering LBT.

[0337] In some embodiments of the present application, the reporting information is used to indicate at least one of the services, bearers, slices, resources or resource types targeted by the triggered LBT failure.

[0338] In some embodiments of the present application, the at least one set of parameters is determined or selected by the terminal device, or the at least one set of parameters is pre-configured, or the at least one set of parameters is configured or indicated by the network.

[0339] In some embodiments of the present application, the first parameter includes a second parameter for adjusting the second counter and / or a third parameter for adjusting the second timer.

[0340] In some embodiments of the present application, the second parameter is an influence factor or a weight value.

[0341] In some embodiments of the present application, the third parameter is an influence factor or a weight value.

[0342] In some embodiments of the present application, the second counter is configured with an initial value and / or a maximum value.

[0343] In some embodiments of the present application, the processing unit 620 is specifically used to:

[0344] determining a count value based on the second counter and the second parameter;

[0345] Determine a second duration of the second timer based on the first duration of the second timer and the third parameter;

[0346] Based on the maximum value of the second counter and / or the second time period, continuous LBT failures are detected and / or a failure recovery process is triggered.

[0347] In some embodiments of the present application, the processing unit 620 is specifically used to:

[0348] In case of receiving an LBT failure indication from the physical layer, adding the count value to the second counter; and / or,

[0349] Restart the second timer.

[0350] In some embodiments of the present application, the processing unit 620 is specifically used to:

[0351] In case the count of the second counter is greater than or equal to the maximum value of the second counter, continuous LBT failure is determined or triggered.

[0352] In some embodiments of the present application, the processing unit 620 is specifically used to:

[0353] When the timing of the second timer exceeds the second duration or the triggered continuous LBT failure is cancelled, resetting the second counter, and / or;

[0354] Stop the second timer.

[0355] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. Specifically, Figure 6The terminal device 600 shown may correspond to the corresponding subject in executing the method 300 of the embodiment of the present application, and the aforementioned and other operations and / or functions of each unit in the terminal device 600 are respectively to implement Figure 3 For the sake of brevity, the corresponding processes in each method are not repeated here.

[0356] Figure 7 It is a schematic block diagram of a network device 700 according to an embodiment of the present application.

[0357] like Figure 7 As shown, the network device 700 may include:

[0358] The sending unit 710 is used to send a second LBT failure recovery configuration and at least one set of parameters, wherein the second LBT failure recovery configuration and the first parameter are used by the terminal device to detect continuous LBT failures and / or trigger a failure recovery process; the first parameter is a parameter in the at least one set of parameters corresponding to the second information, and each set of parameters in the at least one set of parameters is used to adjust the second counter and / or second timer in the second LBT failure recovery configuration.

[0359] In some embodiments of the present application, the at least one set of parameters corresponds to at least one scenario, or the at least one set of parameters corresponds to at least one network environment, and the second information is the scenario or network environment when LBT fails.

[0360] In some embodiments of the present application, the multiple scenarios or the multiple network environments are preset, or the multiple scenarios or the multiple network environments are determined based on a certain condition.

[0361] In some embodiments of the present application, the determining condition includes a condition determined based on at least one of the following information:

[0362] The load of network equipment;

[0363] Interference with network equipment;

[0364] Interference to terminal equipment; or

[0365] Number of LBT failures.

[0366] In some embodiments of the present application, the determination condition is a condition determined based on the interference situation of the terminal device, and the multiple preset scenarios include at least one of the following scenarios:

[0367] Interference with uncontrolled scenes;

[0368] Interfere with a partially controlled scene; or

[0369] Interference controlled scene.

[0370] In some embodiments of the present application, the interference uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being greater than or equal to a first threshold; and / or, the interference partially uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to a third threshold and greater than a fourth threshold; and / or, the interference controlled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to a fifth threshold.

[0371] In some embodiments of the present application, the at least one set of parameters corresponds to multiple services, and the second information is the service targeted by the LBT failure; or the at least one set of parameters corresponds to multiple bearers, and the second information is the bearer targeted by the LBT failure; or the at least one set of parameters corresponds to multiple slices, and the second information is the slice targeted by the LBT failure; or the at least one set of parameters corresponds to multiple resource types, and the second information is the type of resource targeted by the LBT failure.

[0372] In some embodiments of the present application, the multiple services include low-latency high-reliability communication URLLC and / or enhanced mobile ultra-wideband eMBB.

[0373] In some embodiments of the present application, the failure recovery process refers to a failure recovery process for the BWP triggered by at least one of the services, bearers, slices, resources or resource types on the bandwidth part BWP; or the failure recovery process refers to a failure recovery process for the service cell triggered by at least one of the services, bearers, slices, resources or resource types on the service cell.

[0374] In some embodiments of the present application, the at least one set of parameters is determined or selected by the terminal device, or the at least one set of parameters is pre-configured, or the at least one set of parameters is configured or indicated by the network.

[0375] In some embodiments of the present application, the first parameter includes a second parameter for adjusting the second counter and / or a third parameter for adjusting the second timer.

[0376] In some embodiments of the present application, the second parameter is an influence factor or a weight value.

[0377] In some embodiments of the present application, the third parameter is an influence factor or a weight value.

[0378] In some embodiments of the present application, the second counter is configured with an initial value and / or a maximum value.

[0379] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. Specifically, Figure 7 The network device 700 shown may correspond to the corresponding subject in the method 300 of the embodiment of the present application, and the aforementioned and other operations and / or functions of each unit in the network device 700 are respectively to implement Figure 3 For the sake of brevity, the corresponding processes in each method are not repeated here.

[0380] The communication device of the embodiment of the present application is described above from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that the functional modules can be implemented in hardware form, can also be implemented by software instructions, and can also be implemented by a combination of hardware and software modules.

[0381] Specifically, each step of the method embodiment in the embodiment of the present application can be completed by the hardware integrated logic circuit and / or software instructions in the processor. The steps of the method disclosed in the embodiment of the present application can be directly reflected as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor.

[0382] Optionally, the software module may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps in the above method embodiment in combination with its hardware.

[0383] For example, the processing unit and the communication unit mentioned above may be implemented by a processor and a transceiver, respectively.

[0384] Figure 8 It is a schematic structural diagram of a communication device 800 according to an embodiment of the present application.

[0385] like Figure 8 As shown, the communication device 800 may include a processor 810 .

[0386] The processor 810 may call and run a computer program from the memory to implement the method in the embodiment of the present application.

[0387] Please continue to see Figure 8 , the communication device 800 may further include a memory 820 .

[0388] The memory 820 may be used to store indication information, and may also be used to store codes, instructions, etc. executed by the processor 810. The processor 810 may call and run a computer program from the memory 820 to implement the method in the embodiment of the present application. The memory 820 may be a separate device independent of the processor 810, or may be integrated in the processor 810.

[0389] Please continue to see Figure 8 , the communication device 800 may further include a transceiver 830 .

[0390] The processor 810 may control the transceiver 830 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices. The transceiver 830 may include a transmitter and a receiver. The transceiver 830 may further include an antenna, and the number of antennas may be one or more.

[0391] It should be understood that the various components in the communication device 800 are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.

[0392] It should also be understood that the communication device 800 may be a terminal device of an embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application, that is, the communication device 800 of the embodiment of the present application may correspond to the terminal device 400 or 600 in the embodiment of the present application, and may correspond to the corresponding subject in the method 200 or 300 according to the embodiment of the present application, for the sake of brevity, it will not be repeated here. Similarly, the communication device 800 may be a network device of the embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application. That is to say, the communication device 800 of the embodiment of the present application may correspond to the network device 500 or 700 in the embodiment of the present application, and may correspond to the corresponding subject in the method 200 or 300 according to the embodiment of the present application, for the sake of brevity, it will not be repeated here.

[0393] In addition, a chip is also provided in an embodiment of the present application.

[0394] For example, the chip may be an integrated circuit chip with signal processing capabilities, and can implement or execute the methods, steps, and logic diagrams disclosed in the embodiments of the present application. The chip may also be called a system-level chip, a system chip, a chip system, or a system-on-chip chip, etc. Optionally, the chip can be applied to various communication devices, so that the communication device equipped with the chip can execute the methods, steps, and logic diagrams disclosed in the embodiments of the present application.

[0395] Fig. 9 is a schematic structural diagram of a chip 900 according to an embodiment of the present application.

[0396] like Fig. 9 As shown, the chip 900 includes a processor 910 .

[0397] The processor 910 may call and run a computer program from the memory to implement the method in the embodiment of the present application.

[0398] Please continue to see Fig. 9 , the chip 900 may further include a memory 920 .

[0399] The processor 910 may call and run a computer program from the memory 920 to implement the method in the embodiment of the present application. The memory 920 may be used to store indication information, and may also be used to store codes, instructions, etc. executed by the processor 910. The memory 920 may be a separate device independent of the processor 910, or may be integrated in the processor 910.

[0400] Please continue to see Fig. 9 , the chip 900 may further include an input interface 930 .

[0401] The processor 910 may control the input interface 930 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0402] Please continue to see Fig. 9 , the chip 900 may further include an output interface 940 .

[0403] The processor 910 may control the output interface 940 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0404] It should be understood that the chip 900 can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiments of the present application, and can also implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, it will not be repeated here.

[0405] It should also be understood that the various components in the chip 900 are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.

[0406] The processors mentioned above may include but are not limited to:

[0407] General-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.

[0408] The processor can be used to implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware decoding processor, or a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0409] The memory mentioned above includes but is not limited to:

[0410] Volatile memory and / or non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM) or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus random access memory (DR RAM).

[0411] It should be noted that the memory described herein is intended to include these and any other suitable types of memory.

[0412] In an embodiment of the present application, a computer-readable storage medium is further provided for storing a computer program. The computer-readable storage medium stores one or more programs, and the one or more programs include instructions, which, when executed by a portable electronic device including a plurality of application programs, enable the portable electronic device to execute the method of the embodiment shown in method 200 or 300.

[0413] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0414] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0415] A computer program product is also provided in an embodiment of the present application, including a computer program.

[0416] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0417] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0418] The present application also provides a computer program in an embodiment. When the computer program is executed by a computer, the computer can execute the method in the embodiment shown in method 200 or 300 .

[0419] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.

[0420] In addition, the embodiment of the present application also provides a communication system, which may include the terminal device and the network device involved above to form a communication system as follows: Figure 1The communication system 100 shown is not described in detail for the sake of brevity. It should be noted that the term "system" and the like in this document may also be referred to as "network management architecture" or "network system" and the like.

[0421] It should also be understood that the terms used in the embodiments of the present application and the appended claims are for the purpose of describing specific embodiments only and are not intended to limit the embodiments of the present application.

[0422] For example, as used in the embodiments of the present application and the appended claims, the singular forms "a," "said," "above," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

[0423] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present application.

[0424] If implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk.

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

[0426] In several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways.

[0427] For example, the division of units or modules or components in the device embodiment described above is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or modules or components can be combined or integrated into another system, or some units or modules or components can be ignored or not executed.

[0428] For another example, the units / modules / components described above as separation / display components may or may not be physically separated, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units / modules / components may be selected according to actual needs to achieve the purpose of the embodiments of the present application.

[0429] Finally, it should be noted that the mutual coupling or direct coupling or communication connection shown or discussed above may be an indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.

[0430] The above contents are only specific implementation methods of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the embodiments of the present application, which should be included in the protection scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be based on the protection scope of the claims.

Claims

1. A wireless communication method, characterized in that: include: Receive multiple LBT failure recovery configurations; Based on a first LBT failure recovery configuration corresponding to the first information among the multiple LBT failure recovery configurations, detecting continuous LBT failures and / or triggering a failure recovery process; The multiple LBT failure recovery configurations correspond to multiple services, and the first information is the service targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple bearers, and the first information is the bearer targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple slices, and the first information is the slice targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple resources or resource types, and the first information is the resource or resource type targeted by the LBT failure.

2. The method according to claim 1, characterized in that The multiple LBT failure recovery configurations correspond to multiple scenarios, or the multiple LBT failure recovery configurations correspond to multiple network environments; the first information is the scenario or network environment when LBT fails.

3. The method according to claim 2, characterized in that The multiple scenarios or the multiple network environments are preset, or the multiple scenarios or the multiple network environments are determined based on a determined condition.

4. The method according to claim 3, characterized in that The determination condition includes a condition determined based on at least one of the following information: The load of network equipment; Interference with network equipment; Interference to terminal equipment; or Number of LBT failures.

5. The method according to claim 3, characterized in that: The determination condition is a condition determined based on the interference situation of the terminal device, and the multiple scenarios include at least one of the following scenarios: Interference with uncontrolled scenes; Interfere with a partially controlled scene; or Interference controlled scene.

6. The method according to claim 5, characterized in that The interference uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being greater than or equal to the first threshold; and / or, the interference partially uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to the third threshold and greater than the fourth threshold; and / or, the interference controlled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to the fifth threshold.

7. The method according to any one of claims 2 to 6, characterized in that The method further comprises: Maintain an LBT failure recovery configuration, wherein the LBT failure recovery configuration is the first LBT failure recovery configuration.

8. The method according to any one of claims 2 to 6, characterized in that The method further comprises: In case the scenario or network environment changes when LBT fails, the first LBT failure recovery configuration is reset.

9. The method according to claim 1, characterized in that: The multiple services include low-latency and highly reliable communication (URLLC) services and / or enhanced mobile ultra-wideband (eMBB) services.

10. The method according to claim 1, characterized in that The multiple LBT failure recovery configurations include at least one dedicated LBT failure recovery configuration and a public LBT failure recovery configuration, the at least one dedicated LBT failure recovery configuration includes a dedicated LBT failure recovery configuration configured for at least one of the services, bearers, slices, resources or resource types, and the first information is at least one of the services, bearers, slices, resources or resource types targeted by the LBT failure; the public LBT failure recovery configuration refers to an LBT failure recovery configuration that does not distinguish at least one of the services, bearers, slices, resources or resource types, and the first information is an LBT failure indication that does not distinguish at least one of the services, bearers, slices, resources or resource types.

11. The method according to claim 1, characterized in that: The method further comprises: Maintain at least one LBT failure recovery configuration, the at least one LBT failure recovery configuration including an LBT failure recovery configuration for at least one of a service, bearer, slice, resource or resource type, and / or an LBT failure recovery configuration that does not distinguish at least one of a service, bearer, slice, resource or resource type, the at least one LBT failure recovery configuration including the first LBT failure recovery configuration.

12. The method according to claim 1, characterized in that The failure recovery process refers to a failure recovery process for the BWP triggered based on at least one of the services, bearers, slices, resources or resource types on the bandwidth part BWP; Or the failure recovery process refers to a failure recovery process for the service cell triggered by at least one of the services, bearers, slices, resources or resource types on the service cell.

13. The method according to claim 1, characterized in that The method further comprises: Send reporting information to the media access control MAC layer, where the reporting information is used to indicate the failure of triggering LBT.

14. The method according to claim 13, characterized in that The reporting information is used to indicate at least one of the services, bearers, slices, resources or resource types targeted by the triggered LBT failure.

15. The method according to claim 1, characterized in that The first LBT failure recovery configuration is indicated by a network device, or the first LBT failure recovery configuration is determined by a terminal device, or the first LBT failure recovery configuration is determined by a semi-static configuration.

16. The method according to claim 1, characterized in that The first LBT failure recovery configuration includes a first counter and / or a first timer.

17. The method according to claim 16, characterized in that The first counter is configured with an initial value and / or a maximum value.

18. The method according to claim 16, characterized in that The detecting continuous LBT failures and / or triggering a failure recovery process based on a first LBT failure recovery configuration corresponding to the first information among the multiple LBT failure recovery configurations includes: In case of receiving an LBT failure indication from the physical layer, increasing the count of the first counter by 1; and / or, Restart the first timer.

19. The method according to claim 16, characterized in that The detecting continuous LBT failures and / or triggering a failure recovery process based on a first LBT failure recovery configuration corresponding to the first information among the multiple LBT failure recovery configurations includes: When the count of the first counter is greater than or equal to the maximum value of the first counter, continuous LBT failure is determined or triggered.

20. The method according to claim 16, characterized in that The detecting continuous LBT failures and / or triggering a failure recovery process based on a first LBT failure recovery configuration corresponding to the first information among the multiple LBT failure recovery configurations includes: When the timing of the first timer exceeds the duration of the first timer or the triggered continuous LBT failure is cancelled, resetting the first counter, and / or; Stop the first timer.

21. A wireless communication method, characterized in that: include: Sending multiple LBT failure recovery configurations, wherein a first LBT failure recovery configuration corresponding to the first information among the multiple LBT failure recovery configurations is used by the terminal device to detect continuous LBT failures and / or trigger a failure recovery process; The multiple LBT failure recovery configurations correspond to multiple services, and the first information is the service targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple bearers, and the first information is the bearer targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple slices, and the first information is the slice targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple resources or resource types, and the first information is the resource or resource type targeted by the LBT failure.

22. The method according to claim 21, characterized in that The multiple LBT failure recovery configurations correspond to multiple scenarios, or the multiple LBT failure recovery configurations correspond to multiple network environments; the first information is the scenario or network environment when LBT fails.

23. The method according to claim 22, characterized in that The multiple scenarios or the multiple network environments are preset, or the multiple scenarios or the multiple network environments are determined based on a determined condition.

24. The method according to claim 23, characterized in that The determination condition includes a condition determined based on at least one of the following information: The load of network equipment; Interference with network equipment; Interference to terminal equipment; or Number of LBT failures.

25. The method according to claim 23, characterized in that The determination condition is a condition determined based on the interference situation of the terminal device, and the multiple scenarios include at least one of the following scenarios: Interference with uncontrolled scenes; Interfere with a partially controlled scene; or Interference controlled scene.

26. The method according to claim 25, characterized in that The interference uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being greater than or equal to the first threshold; and / or, the interference partially uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to the third threshold and greater than the fourth threshold; and / or, the interference controlled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to the fifth threshold.

27. The method according to claim 21, characterized in that The multiple services include low-latency and highly reliable communication (URLLC) services and / or enhanced mobile ultra-wideband (eMBB) services.

28. The method according to claim 21, characterized in that The multiple LBT failure recovery configurations include at least one dedicated LBT failure recovery configuration and a public LBT failure recovery configuration, the at least one dedicated LBT failure recovery configuration includes a dedicated LBT failure recovery configuration configured for at least one of the services, bearers, slices, resources or resource types, and the first information is at least one of the services, bearers, slices, resources or resource types targeted by the LBT failure; the public LBT failure recovery configuration refers to an LBT failure recovery configuration that does not distinguish at least one of the services, bearers, slices, resources or resource types, and the first information is an LBT failure indication that does not distinguish at least one of the services, bearers, slices, resources or resource types.

29. The method according to claim 21, characterized in that The failure recovery process refers to a failure recovery process for the BWP triggered based on at least one of the services, bearers, slices, resources or resource types on the bandwidth part BWP; Or the failure recovery process refers to a failure recovery process for the service cell triggered by at least one of the services, bearers, slices, resources or resource types on the service cell.

30. The method according to claim 21, characterized in that The first LBT failure recovery configuration is indicated by a network device, or the first LBT failure recovery configuration is determined by a terminal device, or the first LBT failure recovery configuration is determined by a semi-static configuration.

31. The method according to claim 21, characterized in that The first LBT failure recovery configuration includes a first counter and / or a first timer.

32. The method according to claim 31, characterized in that The first counter is configured with an initial value and / or a maximum value.

33. A wireless communication method, characterized in that: include: receiving a second LBT failure recovery configuration and at least one set of parameters; detecting consecutive LBT failures and / or triggering a failure recovery process based on the second LBT failure recovery configuration and the first parameter; The first parameter is a parameter in the at least one group of parameters corresponding to the second information, and each group of parameters in the at least one group of parameters is used to adjust the second counter and / or the second timer in the second LBT failure recovery configuration; The at least one group of parameters corresponds to multiple services, and the second information is the service for which the LBT failed; or the at least one group of parameters corresponds to multiple bearers, and the second information is the bearer for which the LBT failed; or the at least one group of parameters corresponds to multiple slices, and the second information is the slice for which the LBT failed; or the at least one group of parameters corresponds to multiple resource types, and the second information is the type of resource for which the LBT failed.

34. The method according to claim 33, characterized in that The at least one set of parameters corresponds to at least one scenario, or the at least one set of parameters corresponds to at least one network environment, and the second information is the scenario or network environment when LBT fails.

35. The method according to claim 34, characterized in that The multiple scenarios or the multiple network environments are preset, or the multiple scenarios or the multiple network environments are determined based on a determined condition.

36. The method according to claim 35, characterized in that The determination condition includes a condition determined based on at least one of the following information: The load of network equipment; Interference with network equipment; Interference to terminal equipment; or Number of LBT failures.

37. The method according to claim 35, characterized in that The determination condition is a condition determined based on the interference situation of the terminal device, and the multiple scenarios include at least one of the following scenarios: Interference with uncontrolled scenes; Interfere with a partially controlled scene; or Interference controlled scene.

38. The method according to claim 37, characterized in that The interference uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being greater than or equal to the first threshold; and / or, the interference partially uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to the third threshold and greater than the fourth threshold; and / or, the interference controlled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to the fifth threshold.

39. The method according to claim 33, characterized in that The multiple services include low-latency and highly reliable communications (URLLC) and / or enhanced mobile ultra-wideband (eMBB).

40. The method according to claim 33, characterized in that The failure recovery process refers to a failure recovery process for the BWP triggered based on at least one of the services, bearers, slices, resources or resource types on the bandwidth part BWP; Or the failure recovery process refers to a failure recovery process for the service cell triggered by at least one of the services, bearers, slices, resources or resource types on the service cell.

41. The method according to claim 33, characterized in that The method further comprises: Send reporting information to the media access control MAC layer, where the reporting information is used to indicate the failure of triggering LBT.

42. The method according to claim 41, characterized in that The reporting information is used to indicate at least one of the services, bearers, slices, resources or resource types targeted by the triggered LBT failure.

43. The method according to claim 33, characterized in that The at least one set of parameters is determined or selected by the terminal device, or the at least one set of parameters is pre-configured, or the at least one set of parameters is configured or indicated by the network.

44. The method according to claim 33, characterized in that The first parameters include a second parameter for adjusting the second counter and / or a third parameter for adjusting the second timer.

45. The method according to claim 44, characterized in that The second parameter is an impact factor or a weight value.

46. ​​The method according to claim 44, characterized in that The third parameter is an impact factor or a weight value.

47. The method according to claim 44, characterized in that The second counter is configured with an initial value and / or a maximum value.

48. The method according to claim 44, characterized in that The detecting continuous LBT failures and / or triggering a failure recovery process based on the second LBT failure recovery configuration and the first parameter includes: determining a count value based on the second counter and the second parameter; Determine a second duration of the second timer based on the first duration of the second timer and the third parameter; Based on the maximum value of the second counter and / or the second time period, continuous LBT failures are detected and / or a failure recovery process is triggered.

49. The method according to claim 48, characterized in that The detecting continuous LBT failures and / or triggering a failure recovery process based on the maximum value of the second counter and / or the second duration includes: In case of receiving an LBT failure indication from the physical layer, adding the count value to the second counter; and / or, Restart the second timer.

50. The method according to claim 48, characterized in that The detecting continuous LBT failures and / or triggering a failure recovery process based on the maximum value of the second counter and / or the second duration includes: In case the count of the second counter is greater than or equal to the maximum value of the second counter, continuous LBT failure is determined or triggered.

51. The method according to claim 48, characterized in that The detecting continuous LBT failures and / or triggering a failure recovery process based on the maximum value of the second counter and / or the second duration includes: When the timing of the second timer exceeds the second duration or the triggered continuous LBT failure is cancelled, resetting the second counter, and / or; Stop the second timer.

52. A wireless communication method, characterized in that: include: Sending a second LBT failure recovery configuration and at least one set of parameters, wherein the second LBT failure recovery configuration and the first parameter are used by the terminal device to detect continuous LBT failures and / or trigger a failure recovery process; the first parameter is a parameter in the at least one set of parameters corresponding to the second information, and each set of parameters in the at least one set of parameters is used to adjust the second counter and / or the second timer in the second LBT failure recovery configuration; The at least one group of parameters corresponds to multiple services, and the second information is the service for which the LBT failed; or the at least one group of parameters corresponds to multiple bearers, and the second information is the bearer for which the LBT failed; or the at least one group of parameters corresponds to multiple slices, and the second information is the slice for which the LBT failed; or the at least one group of parameters corresponds to multiple resource types, and the second information is the type of resource for which the LBT failed.

53. The method according to claim 52, characterized in that The at least one set of parameters corresponds to at least one scenario, or the at least one set of parameters corresponds to at least one network environment, and the second information is the scenario or network environment when LBT fails.

54. The method according to claim 53, characterized in that The multiple scenarios or the multiple network environments are preset, or the multiple scenarios or the multiple network environments are determined based on a determined condition.

55. The method according to claim 54, characterized in that The determination condition includes a condition determined based on at least one of the following information: The load of network equipment; Interference with network equipment; Interference to terminal equipment; or Number of LBT failures.

56. The method according to claim 54, characterized in that The determination condition is a condition determined based on the interference situation of the terminal device, and the multiple scenarios include at least one of the following scenarios: Interference with uncontrolled scenes; Interfere with a partially controlled scene; or Interference controlled scene.

57. The method according to claim 56, characterized in that The interference uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being greater than or equal to the first threshold; and / or, the interference partially uncontrolled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to the third threshold and greater than the fourth threshold; and / or, the interference controlled scenario refers to any one of the load of the network device, the interference of the network device, or the interference of the terminal device, and the number of LBT failures being less than or equal to the fifth threshold.

58. The method according to claim 52, characterized in that The multiple services include low-latency and highly reliable communications (URLLC) and / or enhanced mobile ultra-wideband (eMBB).

59. The method according to claim 52, characterized in that The failure recovery process refers to a failure recovery process for the BWP triggered based on at least one of the services, bearers, slices, resources or resource types on the bandwidth part BWP; Or the failure recovery process refers to a failure recovery process for the service cell triggered by at least one of the services, bearers, slices, resources or resource types on the service cell.

60. The method of claim 52, wherein: The at least one set of parameters is determined or selected by the terminal device, or the at least one set of parameters is pre-configured, or the at least one set of parameters is configured or indicated by the network.

61. The method according to claim 52, characterized in that The first parameters include a second parameter for adjusting the second counter and / or a third parameter for adjusting the second timer.

62. The method according to claim 61, characterized in that The second parameter is an impact factor or a weight value.

63. The method according to claim 61, characterized in that The third parameter is an impact factor or a weight value.

64. The method according to claim 61, characterized in that The second counter is configured with an initial value and / or a maximum value.

65. A terminal device, characterized in that: include: A receiving unit, used for receiving a plurality of LBT failure recovery configurations; a processing unit, configured to detect continuous LBT failures and / or trigger a failure recovery process based on a first LBT failure recovery configuration corresponding to the first information among the plurality of LBT failure recovery configurations; The multiple LBT failure recovery configurations correspond to multiple services, and the first information is the service targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple bearers, and the first information is the bearer targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple slices, and the first information is the slice targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple resources or resource types, and the first information is the resource or resource type targeted by the LBT failure.

66. A network device, characterized in that: include: A sending unit, configured to send a plurality of LBT failure recovery configurations, wherein a first LBT failure recovery configuration corresponding to the first information among the plurality of LBT failure recovery configurations is used by a terminal device to detect continuous LBT failures and / or trigger a failure recovery process; The multiple LBT failure recovery configurations correspond to multiple services, and the first information is the service targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple bearers, and the first information is the bearer targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple slices, and the first information is the slice targeted by the LBT failure; or the multiple LBT failure recovery configurations correspond to multiple resources or resource types, and the first information is the resource or resource type targeted by the LBT failure.

67. A terminal device, characterized in that: include: A receiving unit, configured to receive a second LBT failure recovery configuration and at least one set of parameters; a processing unit, configured to detect continuous LBT failures and / or trigger a failure recovery process based on the second LBT failure recovery configuration and the first parameter; The first parameter is a parameter in the at least one group of parameters corresponding to the second information, and each group of parameters in the at least one group of parameters is used to adjust the second counter and / or the second timer in the second LBT failure recovery configuration; The at least one group of parameters corresponds to multiple services, and the second information is the service for which the LBT failed; or the at least one group of parameters corresponds to multiple bearers, and the second information is the bearer for which the LBT failed; or the at least one group of parameters corresponds to multiple slices, and the second information is the slice for which the LBT failed; or the at least one group of parameters corresponds to multiple resource types, and the second information is the type of resource for which the LBT failed.

68. A network device, characterized in that: include: A sending unit, configured to send a second LBT failure recovery configuration and at least one set of parameters, wherein the second LBT failure recovery configuration and the first parameter are used by the terminal device to detect continuous LBT failures and / or trigger a failure recovery process; the first parameter is a parameter in the at least one set of parameters corresponding to the second information, and each set of parameters in the at least one set of parameters is used to adjust a second counter and / or a second timer in the second LBT failure recovery configuration; The at least one group of parameters corresponds to multiple services, and the second information is the service for which the LBT failed; or the at least one group of parameters corresponds to multiple bearers, and the second information is the bearer for which the LBT failed; or the at least one group of parameters corresponds to multiple slices, and the second information is the slice for which the LBT failed; or the at least one group of parameters corresponds to multiple resource types, and the second information is the type of resource for which the LBT failed.

69. A terminal device, characterized in that: include: A processor, a memory and a transceiver, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 20 or the method according to any one of claims 33 to 51.

70. A network device, characterized in that: include: A processor, a memory and a transceiver, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the method as claimed in any one of claims 21 to 32 or the method as claimed in any one of claims 52 to 64.

71. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory so that a device equipped with the chip executes a method as described in any one of claims 1 to 20, a method as described in any one of claims 21 to 32, a method as described in any one of claims 33 to 51, or a method as described in any one of claims 52 to 64.

72. A computer-readable storage medium, characterized in that Used to store a computer program, the computer program causing a computer to execute the method of any one of claims 1 to 20, the method of any one of claims 21 to 32, the method of any one of claims 33 to 51, or the method of any one of claims 52 to 64.

73. A computer program product, characterized in that Comprising computer program instructions that cause a computer to perform the method of any one of claims 1 to 20, the method of any one of claims 21 to 32, the method of any one of claims 33 to 51, or the method of any one of claims 52 to 64.

Citation Information

Patent Citations

  • SR adaptive configuration method in unlicensed frequency band

    CN110167188A

  • Dual connectivity scheduling request for wireless network and wireless device

    US20180124831A1

  • Handling of channel access problems

    US20200221309A1

  • Method and apparatus for LBT failure detection

    US20200221495A1