CN116097893A

CN116097893A - Wireless communication method and device

Info

Publication number: CN116097893A
Application number: CN202080104063.5A
Authority: CN
Inventors: 付喆
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-10-09
Filing date: 2020-10-09
Publication date: 2023-05-09
Also published as: WO2022073206A1; CN116097893A8

Abstract

The embodiment of the application provides a wireless communication method and device, wherein the method comprises the following steps: receiving a plurality of LBT failure recovery configurations; based on a first LBT failure recovery configuration of the plurality of LBT failure recovery configurations corresponding to the first information, detecting consecutive LBT failures and/or triggering a failure recovery procedure. Based on the first LBT failure recovery configuration corresponding to the first information in the plurality of LBT failure recovery configurations, detecting continuous LBT failure and/or triggering failure recovery processes is beneficial to using more proper LBT failure recovery processes for different first information, and accordingly, the flexibility of configuration of LBT failure recovery configuration can be improved, and further, the service transmission performance is improved and the requirements of terminal equipment are guaranteed.

Description

Wireless communication method and device

Technical Field

Embodiments of the present application relate to the field of communications, and more particularly, to wireless communication methods and devices.

Background

In order to expand the frequency band that can be used by the communication between the user equipment and the base station, the research on the unlicensed frequency band in the NR (New Radio) is currently underway, so as to enable the user equipment and the base station to communicate in the unlicensed frequency band based on the NR technology.

Before uplink transmission is performed on an unlicensed frequency band, the user equipment needs to listen before talk (Listen Before Talk, LBT) on the unlicensed frequency band to detect whether the unlicensed frequency band is idle, and the communication equipment can perform signal transmission only when a channel interception result is that a channel is idle; if the channel listening of the communication device on the channel of the unlicensed spectrum results in a busy channel, it is necessary to wait until the next transmission opportunity to perform LBT again. In R16, only one resource to be transmitted is indicated from the medium access control (Media Access Control, MAC) layer to the physical layer, and LBT detection is performed on this resource.

However, with the perfection of the communication standard, the function of LBT needs to be further perfected.

Disclosure of Invention

The embodiment of the application provides a wireless communication method and equipment, which can improve the flexibility of configuration LBT failure recovery configuration, further improve service transmission performance and ensure the requirements of terminal equipment.

In a first aspect, a wireless communication method is provided, including:

receiving a plurality of LBT failure recovery configurations;

based on a first LBT failure recovery configuration of the plurality of LBT failure recovery configurations corresponding to the first information, detecting consecutive LBT failures and/or triggering a failure recovery procedure.

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

and transmitting a plurality of LBT failure recovery configurations, wherein a first LBT failure recovery configuration corresponding to the first information in the plurality of LBT failure recovery configurations is used for detecting continuous LBT failures and/or triggering a failure recovery process by the terminal equipment.

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

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

detecting consecutive LBT failures and/or triggering a failure recovery procedure based on the second LBT failure recovery configuration and the first parameter; the first parameter is a parameter corresponding to second information in the at least one set of parameters, and each set of parameters in the at least one set of parameters is used for adjusting a second counter and/or a second timer in the second LBT failure recovery configuration.

In a fourth aspect, there is provided a wireless communication method comprising:

transmitting a second LBT failure recovery configuration and at least one set of parameters, the second LBT failure recovery configuration and the first parameters being used for the terminal device to detect consecutive LBT failures and/or to trigger a failure recovery procedure; the first parameter is a parameter corresponding to second information in the at least one set of parameters, and each set of parameters in the at least one set of parameters is used for adjusting a second counter and/or a second timer in the second LBT failure recovery configuration.

In a fifth aspect, a terminal device is provided for performing the method of the first aspect or each implementation manner thereof. Specifically, the terminal device includes a functional module for executing the method in the first aspect or each implementation manner thereof.

In a sixth aspect, a network device is provided for performing the method of the second aspect or implementations thereof. In particular, the network device comprises functional modules for performing the method of the second aspect or implementations thereof described above.

A seventh aspect provides a terminal device for performing the method of the third aspect or implementations thereof. Specifically, the terminal device comprises functional modules for performing the method in the third aspect or implementations thereof.

In an eighth aspect, a network device is provided for performing the method of the fourth aspect or implementations thereof. In particular, the network device comprises functional modules for performing the method of the fourth aspect described above or in various implementations thereof.

In a ninth aspect, a terminal device is provided, comprising a processor and a memory. The memory is configured to store a computer program, and the processor is configured to invoke and execute the computer program stored in the memory, so as to perform the method in the first aspect, the third aspect, or each implementation manner thereof.

In a tenth aspect, a network device is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the method in the second aspect, the fourth aspect or each implementation manner thereof.

An eleventh aspect provides a chip for implementing the method in any one of the first to fourth aspects or each implementation thereof. Specifically, the chip includes: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method as in any one of the first to fourth aspects or implementations thereof described above.

In a twelfth aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform the method of any one of the above first to fourth aspects or implementations thereof.

In a thirteenth aspect, there is provided a computer program product comprising computer program instructions for causing a computer to perform the method of any one of the above first to fourth aspects or implementations thereof.

In a fourteenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any one of the above-described first to fourth aspects or implementations thereof.

Based on the technical scheme, based on the first LBT failure recovery configuration corresponding to the first information in the plurality of LBT failure recovery configurations, the continuous LBT failure and/or the triggering failure recovery process are detected, so that more proper LBT failure recovery processes can be used for different first information, correspondingly, the flexibility of configuration of LBT failure recovery configuration can be improved, the service transmission performance is further improved, and the requirements of terminal equipment are guaranteed.

Drawings

Fig. 1 is an example of a communication system provided in an embodiment of the present application.

Fig. 2 is a schematic flow chart of a wireless communication method provided in an embodiment of the present application.

Fig. 3 is another schematic flow chart of a wireless communication method provided in an embodiment of the present application.

Fig. 4 is a schematic block diagram of a terminal device provided in an embodiment of the present application.

Fig. 5 is a schematic block diagram of a network device provided in an embodiment of the present application.

Fig. 6 is another schematic block diagram of a terminal device provided in an embodiment of the present application.

Fig. 7 is another schematic block diagram of a network device provided by an embodiment of the present application.

Fig. 8 is a schematic block diagram of a communication device provided in an embodiment of the present application.

Fig. 9 is a schematic block diagram of a chip provided in an embodiment of the present application.

Detailed Description

The following description of the technical solutions in the embodiments of the present application will be made with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.

As shown in fig. 1, communication system 100 may include a terminal device 110 and a network device 120. Network device 120 may communicate with terminal device 110 over the air interface. Multi-service transmission is supported between terminal device 110 and network device 120.

It should be understood that the present embodiments are illustrated by way of example only with respect to communication system 100, but the present embodiments are not limited thereto. That is, the technical solution of the embodiment of the present application may be applied to various communication systems, for example: long term evolution (Long Term Evolution, LTE) system, LTE time division duplex (Time Division Duplex, TDD), universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), 5G communication system (also referred to as New Radio (NR) communication system), or future communication system, etc.

In the communication system 100 shown in fig. 1, the network device 120 may be an access network device in communication with the terminal device 110. The access network device may provide communication coverage for a particular geographic area and may communicate with terminal devices 110 (e.g., UEs) located within the coverage area.

The network device 120 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in a long term evolution (Long Term Evolution, LTE) system, or a next generation radio access network (Next Generation Radio Access Network, NG RAN) device, or a base station (gNB) in a NR system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device 120 may be a relay station, an access point, a vehicle device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

Terminal device 110 may be any terminal device including, but not limited to, a terminal device that employs a wired or wireless connection with network device 120 or other terminal devices.

For example, the terminal device 110 may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolution network, etc.

The terminal Device 110 may be used for Device-to-Device (D2D) communication.

The wireless communication system 100 may further comprise a core network device 130 in communication with the base station, which core network device 130 may be a 5G core,5gc device, e.g. an access and mobility management function (Access and Mobility Management Function, AMF), further e.g. an authentication server function (Authentication Server Function, AUSF), further e.g. a user plane function (User Plane Function, UPF), further e.g. a session management function (Session Management Function, SMF). Optionally, the core network device 130 may also be a packet core evolution (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 appreciated that SMF+PGW-C may perform the functions performed by both SMF and PGW-C. In the network evolution process, the core network device may also call other names, or form a new network entity by dividing the functions of the core network, which is not limited in this embodiment of the present application.

Communication may also be achieved by establishing connections between various functional units in the communication system 100 through a next generation Network (NG) interface.

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

Fig. 1 exemplarily illustrates one base station, one core network device, and two terminal devices, alternatively, the wireless communication system 100 may include a plurality of base station devices and each base station may include other number of terminal devices within a coverage area, which is not limited in the embodiment of the present application.

It should be understood that devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 120 and a terminal device 110 with communication functions, where the network device 120 and the terminal device 110 may be the devices described above, and are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

It should be noted that the communication system 100 may operate in an unlicensed frequency band, for example, including the following several operating scenarios:

scene a: in the carrier aggregation scenario, a Primary Cell (PCell) is a licensed spectrum, and Secondary cells (scells) operating on an unlicensed spectrum are aggregated by a carrier aggregation method.

Scene B: in a dual connection working scenario, PCell is LTE licensed spectrum, and PScell is NR unlicensed spectrum.

Scene C: in an independent operation scenario, the NR operates as an independent cell on unlicensed spectrum.

Scene D: in the NR single cell scenario, the Uplink (UL) operates on licensed spectrum and the Downlink (DL) operates on unlicensed spectrum.

Scene E: in a dual connectivity operating scenario, PCell is an NR licensed spectrum and primary and secondary cells (Primary Secondary Cell, PSCell) are NR unlicensed spectrum.

By way of example, the operating Band (Band) of NR-U is a 5GHz unlicensed spectrum and a 6GHz unlicensed spectrum. On unlicensed spectrum, the design of NR-U should ensure fairness with other systems already operating on these unlicensed spectrum, such as WiFi, etc. The principle of fairness is that the NR-U cannot have more impact on systems already deployed on unlicensed spectrum (such as WiFi) than between these systems.

In order to ensure fair coexistence between systems on unlicensed spectrum, energy detection has been agreed as a basic coexistence mechanism. The general energy detection mechanism is an LBT mechanism, and the basic principle of the mechanism is as follows: a base station or terminal (transmitting end) needs to listen for a period of time as specified before transmitting data on the unlicensed spectrum. If the result of interception indicates that the channel is in an idle state, the transmitting end can transmit data to the receiving end. If the interception result indicates that the channel is in an occupied state, the transmission end needs to intercept the channel again according to a set back-off period, and knows that the channel interception result is in an idle state, and then the transmission end can transmit data to the receiving end.

Four channel access mechanisms (category) are currently defined in the NR-U, reference TR 38.889:

Category 1: a direct transmission mechanism.

The direct transmission mechanism is used for the TX side to quickly transmit after a switching gap (switching gap) within the COT; switching gap refers to the transition time of the received transmission, typically no more than 16us.

Category 2: no random back-off LBT mechanism is required.

The LBT mechanism that does not require random back-off means that the time for the UE to listen to the channel is deterministic, typically relatively short, such as 25us.

Category 3: random back-off LBT mechanism (contention window fixed).

In the LBT procedure, the transmitting side randomly goes a random value in the contention window to determine the time to listen to the channel.

Category 4: the LBT mechanism of random back-off (contention window is not fixed).

In the LBT procedure, the transmission side randomly takes a random value in the contention window to determine the time to listen to the channel, and the contention window is variable.

To sum up, for a terminal, the base station needs to transmit data to the terminal within the MCOT time, if the base station does not preempt the channel, that is, outside the MCOT time, the terminal will not receive the scheduling data from the base station to the terminal.

For uplink transmission initiated by the UE, the following classes may be mainly included:

scheduling request (Scheduling Request, SR): for requesting uplink resources.

Physical random access channel (Physical Random Access Channel, PRACH) transmission: due to RACH triggers, the UE needs to transmit msg1.

Physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) transmission: the method comprises the steps of uplink data transmission based on configured grant and uplink data transmission based on dynamic grant.

Physical layer signaling: including ACK/NACK feedback, channel state information (Channel State Information, CSI) reporting, etc.

On the unlicensed band, the UE needs to listen to whether the channel is available with LBT before transmitting SR, PRACH or PUSCH, and if not, i.e. LBT fails, the UE needs to wait until the next transmission opportunity to perform LBT again. If LBT failure is detected, information of LBT failure needs to be notified to the MAC layer.

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

For example, to support transfer of URLLC traffic, configuration grants (Configuration Grant, CG) may be enhanced, e.g., multiple CG configurations are introduced, as well as specific configuration and usage of the CG (e.g., slot-level enabled cycles, CG enabled automatic transfer, etc.).

For example, to support the high latency requirements of URLLC traffic, CG periods may be enhanced for URLLC, supporting traffic periods at arbitrary slot-level (slot-level).

As another example, to support multiple URLLC services and high latency requirements of URLLC services, multiple configuration grants (multiple CG) may be introduced for URLLC. For example, hybrid automatic repeat request (Hybrid Automatic Repeat Request, HARQ) processes for different CG configurations are different, and the different CG processes are guaranteed to be different by HARQ-ProcID-Offset 2.

Due to the existence of CG resources and other resource conflicts, in order to ensure that already packetized media access control (Media Access Control, MAC) protocol data units (Protocol Data Unit, PDU) (i.e. Deprioritized MAC PDU) in CG resources are not dropped/transmitted as soon as possible, automatic transmission for CG may be introduced. For CG of the packet MAC PDU, which cannot be transmitted due to resource collision, a new transmission may be performed using CG resources in the same CG configuration of the subsequent same HARQ process. The use of automatic transmission may be determined by autonomosutx.

If the physical layer priorities are different and CG collide, the MAC may instruct the physical layer of one or more MAC PDUs. Similarly, if there is a collision of data (data) and scheduling requests (Scheduling Request, SR), the MAC may also indicate SR and MAC PDUs to the physical layer.

In summary, it is seen that URLLC traffic needs to be supported in NRU scenarios. In general, the terminal device may consider that only one resource to be transmitted is indicated from the MAC layer to the physical layer, and perform LBT detection on the resource. I.e. LBT failure recovery based on the common (common) recovery parameters of the network configuration, but the requirements of the URLLC service are not met when the common (common) recovery parameters of the network configuration actually work.

Therefore, the LBT failure recovery procedure can be performed by differentiating the traffic, so that the requirement of the URLLC traffic is not satisfied when the recovery parameters of the common network are actually valid. Therefore, the application proposes a method for performing different treatments on different services through the LBT failure recovery process of differentiated services.

Fig. 2 shows a schematic flow chart of a wireless communication method 200 according to an embodiment of the present application, which method 200 may be interactively performed by a network device and a terminal device. The terminal device shown in fig. 2 may be a terminal device as shown in fig. 1, and the network device shown in fig. 2 may be an access network device as shown in fig. 1.

As shown in fig. 2, the method 200 may include some or all of the following:

S210, the terminal equipment receives a plurality of LBT failure recovery configurations sent by the network equipment;

s220, the terminal equipment detects continuous LBT failure and/or triggers a failure recovery process based on a first LBT failure recovery configuration corresponding to the first information in the plurality of LBT failure recovery configurations.

Based on the first LBT failure recovery configuration corresponding to the first information in the plurality of LBT failure recovery configurations, detecting continuous LBT failure and/or triggering failure recovery processes is beneficial to using more proper LBT failure recovery processes for different first information, and accordingly, the flexibility of configuration of LBT failure recovery configuration can be improved, and further, the service transmission performance is improved and the requirements of terminal equipment are guaranteed.

In some embodiments of the present application, the plurality of LBT failure recovery configurations corresponds to a plurality of scenarios, or the plurality of LBT failure recovery configurations corresponds to a plurality of network environments; the first information is a scene or a network environment when the LBT fails.

It should be appreciated that for the plurality of LBT failure recovery configurations, one or at least one of the plurality of LBT failure recovery configurations may correspond to a plurality of scenarios; alternatively, the LBT failure recovery configurations may also respectively correspond to multiple scenarios. Similarly, one or at least one of the plurality of LBT failure recovery configurations may correspond to a plurality of network environments; alternatively, the plurality of LBT failure recovery configurations may also respectively correspond to a plurality of network environments.

For different scenes, the interference conditions are different, and the services which can be preferentially ensured/supported by different scenes are also different. Different LBT failure detection recovery parameters are given to different scenes, so that the method is beneficial to being better suitable for different environments and/or different services, and a more suitable LBT failure recovery process is used according to different conditions, so that the service transmission performance and the requirements of terminal equipment are timely ensured.

For example, the plurality of scenes or the plurality of network environments are preset, or the plurality of scenes or the plurality of network environments are determined based on a determination condition.

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

load conditions of the network device;

interference conditions of the network device;

interference conditions of the terminal equipment; or (b)

Number of LBT failures.

For example, the determination condition is a condition determined based on an interference situation of the terminal device, and the plurality of preset scenes include at least one of the following scenes:

disturbing uncontrolled scenes;

disturbing the partially controlled scene; or (b)

Disturbing the controlled scene.

For example, the interference uncontrolled scenario refers to any one of load of the network device, interference of the network device, or interference of the terminal device, LBT failure times being greater than or equal to a first threshold; and/or the interference part uncontrolled scenario means that each of the load of the network device, the interference of the network device, or the interference of the terminal device is less than or equal to a second threshold; and/or the interference part uncontrolled scene refers to that any one of the load of the network equipment, the interference of the network equipment, or the interference of the terminal equipment, and the LBT failure times is smaller than or equal to a third threshold value and larger than a fourth threshold value; and/or, the interference controlled scenario refers to that each of the load of the network device, the interference of the network device, or the interference of the terminal device, and the LBT failure number is smaller than or equal to a fifth threshold value.

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

one LBT failure recovery configuration is maintained, the one LBT failure recovery configuration being the first LBT failure recovery configuration.

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

and resetting the first LBT failure recovery configuration under the condition that the scene or the network environment at the time of LBT failure is changed.

For example, in case of a scene or a network environment change at the time of LBT failure, the terminal device resets the first LBT failure recovery configuration.

In some embodiments of the present application, the plurality of LBT failure recovery configurations correspond to a plurality of services, and the first information is a service for which LBT failure is intended; or the plurality of LBT failure recovery configurations correspond to a plurality of bearers, and the first information is a bearer for which the LBT failure is aimed; or the plurality of LBT failure recovery configurations correspond to a plurality of slices, and the first information is a slice for which LBT failure is aimed; or the plurality of LBT failure recovery configurations correspond to a plurality of resources or resource types, and the first information is the resource or the resource type for which the LBT failure is aimed.

For example, the plurality of services includes low latency high reliability communication URLLC services and/or enhanced mobile ultra wideband eMBB services.

Due to different requirements such as time delay of different services. Different LBT failure detection recovery parameters are configured for different services, so that the method is favorable for being better suitable for different services, a more suitable LBT failure recovery process is used, and the service transmission performance and the requirements of terminal equipment are timely ensured. Similarly, different LBT failure detection recovery parameters are configured for different bearer/slice/resource types, so that the method is favorable for being better applicable to different bearer/slice/resource types, and a more appropriate LBT failure recovery process is used, so that the service transmission performance and the requirements of terminal equipment are timely ensured.

It should be appreciated that for the plurality of LBT failure recovery configurations, one or at least one of the plurality of LBT failure recovery configurations may correspond to a plurality of services; alternatively, the plurality of LBT failure recovery configurations may also correspond to a plurality of services, respectively. Similarly, one or at least one of the plurality of LBT failure recovery configurations may correspond to a plurality of bearers; alternatively, the plurality of LBT failure recovery configurations may also correspond to a plurality of bearers, respectively. Similarly, one or at least one of the plurality of LBT failure recovery configurations may correspond to a plurality of slices; alternatively, the plurality of LBT failure recovery configurations may also correspond to a plurality of slices, respectively. Similarly, one or at least one of the plurality of LBT failure recovery configurations may correspond to a plurality of resources; alternatively, the plurality of LBT failure recovery configurations may also correspond to a plurality of resources, respectively. Similarly, one or at least one of the plurality of LBT failure recovery configurations may correspond to a plurality of resource types; alternatively, the plurality of LBT failure recovery configurations may also respectively correspond to a plurality of resource types.

In some embodiments of the present application, the plurality of LBT failure recovery configurations includes at least one dedicated LBT failure recovery configuration and a common LBT failure recovery configuration, the at least one dedicated LBT failure recovery configuration including a dedicated LBT failure recovery configuration configured for at least one of traffic, bearer, slice, resource, or resource type, the first information being at least one of traffic, bearer, slice, resource, or resource type for which LBT failure was intended; the common LBT failure recovery configuration refers to an LBT failure recovery configuration that does not differentiate between at least one of a service, a bearer, a slice, a resource, or a resource type, and the first information is an LBT failure indication that does not differentiate between at least one of a service, a bearer, a slice, a resource, or a resource type.

Due to different requirements such as time delay of different services. Different LBT failure detection recovery parameters are configured for different services, so that the method is favorable for being better suitable for different services, a more suitable LBT failure recovery process is used, and the service transmission performance and the UE requirements are timely ensured. Similarly, different LBT failure detection recovery parameters are configured for different bearer/slice/resource types, so that the method is beneficial to better adapting to different bearer/slice/resource types, and a more suitable LBT failure recovery process is used, so that the service transmission performance and the UE requirements are timely ensured.

In addition, through the public LBT failure recovery configuration and the special LBT failure recovery configuration, the transmission performance of the whole UE is ensured, and the transmission performance of the specific service is ensured.

at least one LBT failure recovery configuration is maintained, the at least one LBT failure recovery configuration comprising an LBT failure recovery configuration for at least one of a traffic, a bearer, a slice, a resource, or a resource type, and/or an LBT failure recovery configuration that does not differentiate between at least one of a traffic, a bearer, a slice, a resource, or a resource type, the at least one LBT failure recovery configuration comprising the first LBT failure recovery configuration.

For example, the terminal device maintains the at least one dedicated LBT failure recovery configuration and the common LBT failure recovery configuration.

In some embodiments of the present application, the failure recovery procedure refers to a failure recovery procedure for a bandwidth portion BWP triggered based on at least one of traffic, bearers, slices, resources, or resource types on the BWP; or the failure recovery procedure refers to a failure recovery procedure for a serving cell triggered by at least one of traffic, bearers, slices, resources, or resource types on the serving cell.

and sending reporting information to a Media Access Control (MAC) layer, wherein the reporting information is used for indicating failure of triggering the LBT.

For example, the MAC layer of the terminal device receives the report information from the physical layer.

For example, the reporting information is used to indicate at least one of a service, a bearer, a slice, a resource, or a resource type for which the triggered LBT failed.

In some embodiments of the present application, the plurality of LBT failure recovery configurations are indicated or configured by a network device, or predefined.

For example, the plurality of LBT failure recovery configurations may be configured by RRC configuration information.

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

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

The initial value and/or the maximum value of the corresponding counter configuration may be configured by the network through RRC, or may be specified by a protocol.

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.

For example, the first LBT failure recovery configuration may be configured by RRC configuration information.

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

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

The initial value and/or the maximum value of the first counter may be configured by the network through RRC, or may be specified by a protocol.

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

in case of receiving an LBT failure indication from the physical layer, incrementing the count of the first counter by 1; and/or restarting the first timer.

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

in case the count of the first counter is greater than or equal to the maximum value of the first counter, a consecutive LBT failure is determined or triggered.

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

resetting the first counter, and/or in case the timing of the first timer exceeds the duration of the first timer or a triggered consecutive LBT failure is cancelled; stopping the first timer.

The method 200 is described below in connection with specific embodiments.

Embodiment one:

The UE receives multiple sets of LBT failure recovery configurations, uses different LBT failure recovery configurations for different scenarios, detects consecutive LBT failures, and/or triggers a corresponding failure recovery procedure.

For example, a specific procedure may include the steps of:

step 1:

the network equipment configures a plurality of sets of LBT failure recovery configurations for the UE, wherein the sets of LBT failure recovery configurations are used for different scenes, are used for detecting continuous LBT failures corresponding to the different scenes, and/or trigger a corresponding failure recovery process.

For example, different LBT failure recovery configurations correspond to the scenario. For example, LBT failure recovery configuration 1 corresponds to scenario 1 (e.g., interference uncontrolled scenario, interference partially controlled scenario), and LBT failure recovery configuration 2 corresponds to scenario 2 (e.g., interference controlled scenario). Optionally, the LBT failure recovery parameter a (e.g., the maximum counter value, the timer) corresponding to scenario 1 is smaller.

For another example, the selection conditions of the corresponding scene are recovered by different LBT failures. For example, the number of channel interference/LBT failures is greater than or equal to the threshold, then LBT failure recovery configuration 1 is selected, otherwise LBT failure recovery configuration 2 is selected. Optionally, the LBT failure recovery parameter a (e.g., the maximum counter value, the timer) corresponding to scenario 1 is smaller.

Optionally, the network device dynamically indicates which LBT failure recovery configuration to use. Alternatively, the network device semi-statically configures the LBT failure recovery configuration to use a pattern (pattern), etc.

Step 2:

and the UE receives a plurality of sets of LBT failure recovery configurations of the network configuration, and selects the used LBT failure recovery parameters according to the information in the step 1.

For example, the LBT failure recovery parameters include at least one of: a counter (e.g. lbt-failureiinstancemaxcount), a timer (lbt-FailureDetectionTimer).

Optionally, the initial value of the counter is 0. Alternatively, it may be protocol-specified.

Alternatively, the UE maintains only one set of configurations at a time. It should be appreciated that the LBT failure recovery procedure may employ a protocol defined recovery procedure.

In addition, for LBT failure scenarios or network environments, consecutive LBT failures are detected based on their corresponding LBT failure recovery configurations, and/or corresponding failure recovery procedures are triggered.

For example, under scenario 1, performing detection of consecutive LBT failures using the LBT failure recovery parameter corresponding to scenario 1, and/or triggering a corresponding failure recovery procedure; in scenario 2, using the LBT failure recovery parameters corresponding to scenario 2, performing detection of consecutive LBT failures, and/or triggering a corresponding failure recovery procedure.

For different scenes, the interference conditions are different, and the services which can be preferentially ensured/supported by different scenes are also different. Different LBT failure detection recovery parameters are given to different scenes, so that the method is beneficial to being better suitable for different environments and/or different services, and a more suitable LBT failure recovery process is used for different situations, so that the service transmission performance and the UE requirements are timely ensured.

Embodiment two:

the UE receives multiple sets of LBT failure recovery configurations, uses different LBT failure recovery configurations for different traffic/bearers/slices/resources/resource types to detect consecutive LBT failures, and/or triggers corresponding failure recovery procedures.

For example, a specific procedure may include the steps of:

step 1:

the network equipment configures a plurality of sets of LBT failure recovery configurations for the UE, wherein the sets of LBT failure recovery configurations are used for different service/bearing/slicing/resource types, are used for detecting continuous LBT failures corresponding to the different service/bearing/slicing/resource types, and/or trigger corresponding failure recovery processes.

For example, different LBT failure recovery configurations correspond to the traffic. 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 (e.g., counter maximum value, timer) corresponding to the service 1 (e.g., URLLC service) has a smaller value.

For another example, the different LBT failure recovery configurations correspond to the corresponding resource types. For example, type one resources (e.g., high priority resources) correspond to LBT failure recovery configuration 1, type two resources or other resources (e.g., low priority resources) correspond to LBT failure recovery configuration 2. Optionally, the LBT failure recovery parameter a (e.g., counter maximum value, timer) corresponding to the service 1 (e.g., high priority resource service) has a smaller value.

Step 2:

and the UE receives a plurality of sets of LBT failure recovery configurations of the network configuration, and selects LBT failure recovery parameters which are correspondingly used according to the information in the step 1 aiming at different services.

For example, the LBT failure recovery parameters include at least one of: a counter (e.g. lbt-failureiinstancemaxcount, i.e. the maximum value of the counter), a timer (lbt-FailureDetectionTimer).

Optionally, the UE maintains both sets of configurations at the same time.

It should be appreciated that the LBT failure recovery procedure may employ a protocol defined recovery procedure.

In addition, for the service/bearer/slice/resource type of LBT failure, based on its corresponding LBT failure recovery configuration, consecutive LBT failures are detected and/or a corresponding failure recovery procedure is triggered.

In some embodiments of the present application, LBT failure recovery configuration 1 is used for high priority resources or URLLC traffic, consecutive LBT failures are detected, and/or a corresponding failure recovery procedure is triggered; and, for low priority resources or eMBB traffic, LBT failure recovery configuration 2 is used, consecutive LBT failures are detected, and/or a corresponding failure recovery procedure is triggered.

For example, LBT failure recovery (LBT failure recovery) configures 1 for URLLC traffic, i.e., as soon as there is a LBT failure received from the underlying, corresponding URLLC, 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 consecutive LBT failure (which may be the BWP for the cell). If the corresponding timer times out or the triggered consecutive LBT failures are canceled, the corresponding counter is reset.

For another example, LBT failure recovery configures 2 for the eMBB traffic, i.e., as soon as there is a LBT failure from the bottom layer that corresponds to an eMBB, 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 consecutive LBT failure (which may be the BWP for the cell). If the corresponding timer times out or the triggered consecutive LBT failures are canceled, the corresponding counter is reset.

Alternatively, if LBT failure recovery is triggered for any traffic/bearer/slice/resource type, the UE considers that there are consecutive LBT failures for this BWP or serving cell.

Optionally, when the UE reports the LBT failure, the UE indicates a service/bearer/slice/resource type corresponding to the triggering LBT failure.

Embodiment III:

the UE receives a plurality of sets of LBT failure recovery configurations, a common (common) LBT failure recovery configuration and at least one special (specific) LBT failure recovery configuration, respectively. Wherein the special LBT failure recovery configuration may be for a specific traffic/bearer/slice/resource type.

For example, a specific procedure may include the steps of:

step 1:

the network equipment configures a plurality of sets of LBT failure recovery configurations for the UE, wherein the sets of LBT failure recovery configurations are used for LBT failure indication of different service/bearing/slice/resource types and without distinguishing the service/bearing/slice/resource types, and are used for detecting corresponding continuous LBT failures and/or triggering corresponding failure recovery processes.

For example, the plurality of sets of LBT failure recovery configurations may include a common LBT failure recovery (common LBT failure recovery) configuration and at least one dedicated LBT failure recovery (special LBT failure recovery) configuration. The dedicated LBT failure recovery configuration is for one traffic/bearer/slice/resource type. The common LBT failure recovery configuration does not distinguish between different traffic/bearers/slices/resources/resource types.

Step 2:

and the UE receives a plurality of sets of LBT failure recovery configurations of the network configuration, and selects the corresponding LBT failure recovery parameters according to the information in the step 1 according to different conditions.

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

In addition, for the service/bearer/slice/resource type of LBT failure, based on its corresponding LBT failure recovery configuration, detecting consecutive LBT failures and/or triggering a corresponding failure recovery procedure; or, for LBT failures that do not differentiate traffic/bearer/slice/resource types, detecting consecutive LBT failures based on a common LBT failure recovery configuration, and/or triggering a corresponding failure recovery procedure.

For example, the common LBT failure recovery configuration is used for all traffic/bearers/slices/resource types, i.e. the counter of the common LBT failure recovery configuration is incremented by 1 as soon as there is a LBT failure received from the bottom layer, and the timer of the common LBT failure recovery configuration is restarted. If the counter of the common LBT failure recovery configuration is greater than or equal to the maximum value of the counter of the common LBT failure recovery configuration, the UE triggers a continuous LBT failure (which may be the BWP for the cell). If the timer of the common LBT failure recovery configuration times out or the triggered consecutive LBT failures are cancelled (cancel), the counter of the common LBT failure recovery configuration may be reset.

For another example, the dedicated LBT failure recovery configuration is for a specific service/bearer/slice/resource type, i.e., only if an LBT failure corresponding to that service/bearer/slice/resource type is received from the bottom layer, the counter of the corresponding dedicated LBT failure recovery configuration is incremented by 1 and the timer of the corresponding special 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 consecutive LBT failure (which may be the BWP for the cell). Resetting the counter of the corresponding special LBT failure recovery configuration if the timer of the corresponding special LBT failure recovery configuration is timed out or the triggered continuous LBT failure is canceled.

In addition, compared with embodiment 2, the transmission performance of the whole UE and the transmission performance of the specific service are ensured by the common LBT failure recovery configuration and the dedicated LBT failure recovery configuration.

Fig. 3 shows a schematic flow chart of a wireless communication method 300 according to an embodiment of the present application, which method 300 may be interactively performed by a network device and a terminal device. The terminal device shown in fig. 3 may be a terminal device as shown in fig. 1, and the network device shown in fig. 3 may be an access network device as shown in fig. 1.

As shown in fig. 3, the method 300 may include some or all of the following:

s310, receiving a second LBT failure recovery configuration and at least one set of parameters;

s320, detecting continuous LBT failure and/or triggering failure recovery process based on the second LBT failure recovery configuration and the first parameter; the first parameter is a parameter corresponding to second information in the at least one set of parameters, and each set of parameters in the at least one set of parameters is used for adjusting a second counter and/or a second timer in the second LBT failure recovery configuration.

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 a scenario or network environment when LBT fails.

load conditions of the network device;

interference conditions of the network device;

interference conditions of the terminal equipment; or (b)

Number of LBT failures.

disturbing uncontrolled scenes;

disturbing the partially controlled scene; or (b)

Disturbing the controlled scene.

In some embodiments of the present application, the at least one set of parameters corresponds to a plurality of services, and the second information is a service for which LBT fails; or the at least one group of parameters corresponds to a plurality of bearers, and the second information is the bearer for which the LBT fails; or the at least one group of parameters corresponds to a plurality of slices, and the second information is a slice for which LBT fails; or the at least one set of parameters corresponds to a plurality of resource types, and the second information is the type of the resource for which the LBT fails.

For example, the plurality of services includes low latency high reliability communications URLLC and/or enhanced mobile ultra wideband eMBB.

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

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 preconfigured, or the at least one set of parameters is network configured or indicated.

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.

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.

For example, the second parameter is an influence factor or a weight value.

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

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

Optionally, the initial value of the second counter is 0. Alternatively, it may be protocol-specified.

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

determining a count value based on the second counter and the second parameter; determining a second duration of a second timer based on the second timer first duration and the third parameter; based on the maximum value of the second counter and/or the second time period, detecting a consecutive LBT failure and/or triggering a failure recovery procedure.

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

in case of receiving an LBT failure indication from the physical layer, adding the count value to the count value of the second counter; and/or restarting the second timer.

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

in case the count of the second counter is greater than or equal to the maximum value of the second counter, a consecutive LBT failure is determined or triggered.

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

resetting the second counter, and/or, in case the timing of the second timer exceeds the second duration or the triggered consecutive LBT failures are cancelled; stopping the second timer.

The method 300 is described below in connection with example 4.

Example 4:

the UE receives a set of LBT failure recovery configurations, but the impact factors or weights on the counter and/or timer are different for different traffic/bearers/slices/resources/resource types/environments.

For example, a specific procedure may include the steps of:

step 1:

the network equipment configures LBT failure recovery parameters for the UE, wherein the LBT failure recovery parameters are used for detecting continuous LBT failures corresponding to different services/bearing/slicing/resources/resource types/environments and/or triggering corresponding failure recovery processes.

For example, the LBT failure recovery parameters include LBT failure recovery configuration (only one set). Optionally, the LBT failure recovery configuration may include the following counter (e.g. LBT-FailureInstaceMaxCount, i.e. the maximum value of the counter) and/or timer (LBT-FailureDetectionTimer).

For example, the LBT failure recovery parameters include different impact factors or weighting values corresponding to different services/bearers/slices/resources/resource types/environments, where the impact factors or weighting values are used to impact the counter and/or the timer. Alternatively, the impact factor or weighting value may be preconfigured or UE-selected.

For example, the final counter count is a function of the physical layer report value and an impact factor or weight, e.g., 1 x the impact factor or weight; for example, the final timer duration is a function of the physical layer report value and an impact factor or weight, such as a configured timer duration.

Step 2:

the UE receives the LBT failure recovery parameters configured by the network, determines corresponding influence factors or weighted values aiming at different services/bearers/slices/resources/resource types/environments, corrects a counter and/or a timer, carries out continuous LBT failure detection, and/or triggers a corresponding failure recovery process.

Optionally: when the PHY reports the LBT failure to the higher layer, the corresponding service/bearer/slice/resource type/environment for triggering the LBT failure is indicated.

For example, as soon as there is a LBT failure received from the bottom layer corresponding to the URLLC, the corresponding counter is incremented by 1 x factor1 and the corresponding timer is restarted (the timer duration is configured as duration x factor 3). If the corresponding counter is greater than or equal to the corresponding maximum value, the UE triggers a consecutive LBT failure (which may be the BWP for the cell). If the corresponding timer times out or the triggered consecutive LBT failures are canceled, the corresponding counter is reset.

For another example, as soon as there is a LBT failure to receive the corresponding eMBB from the bottom layer, the corresponding counter is incremented by 1 x factor2 and the corresponding timer is restarted (the timer duration is configured as duration x factor 4). If the corresponding counter is greater than or equal to the corresponding maximum value, the UE triggers a consecutive LBT failure (which may be the BWP for the cell). If the corresponding timer times out or the triggered consecutive LBT failures are canceled, the corresponding counter is reset.

Due to different requirements such as time delay of different services. Compared with the embodiment 2-3, the UE only maintains one set of LBT failure recovery parameters, thereby reducing the complexity of the UE. In addition, the influence of different services or scenes is considered through the influence factors, so that the requirements of reflecting different services/scenes are guaranteed, the different scenes/services are served, and the service transmission is recovered.

The preferred embodiments of the present application have been described in detail above with reference to the accompanying drawings, but the present application is not limited to the specific details of the above embodiments, and various simple modifications may be made to the technical solutions of the present application within the scope of the technical concept of the present application, and all the simple modifications belong to the protection scope of the present application. For example, the specific features described in the above embodiments may be combined in any suitable manner, and in order to avoid unnecessary repetition, various possible combinations are not described in detail. As another example, any combination of the various embodiments of the present application may be made without departing from the spirit of the present application, which should also be considered as disclosed herein.

It should be further understood that, in the various method embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic of the processes, and should not constitute any limitation on the implementation process of the embodiments of the present application. Further, in the embodiments of the present application, the terms "downlink" and "uplink" are used to indicate a transmission direction of a signal or data, where "downlink" is used to indicate that the transmission direction of the signal or data is a first direction of a user equipment transmitted from a station to a cell, and "uplink" is used to indicate that the transmission direction of the signal or data is a second direction of a user equipment transmitted from a cell to a station, 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 merely an association relationship describing the association object, which means that three relationships may exist. Specifically, a and/or B may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

Method embodiments of the present application are described in detail above in connection with fig. 1-3, and apparatus embodiments of the present application are described in detail below in connection with fig. 4-9.

Fig. 4 is a schematic block diagram of a terminal device 400 of an embodiment of the present application.

As shown in fig. 4, the terminal device 400 may include:

a receiving unit 410 for receiving a plurality of LBT failure recovery configurations;

a processing unit 420, configured to detect a continuous LBT failure and/or trigger a failure recovery procedure based on a first LBT failure recovery configuration corresponding to the first information in the plurality of LBT failure recovery configurations.

In some embodiments of the present application, the plurality of scenes or the plurality of network environments are preset, or the plurality of scenes or the plurality of network environments are determined based on a determination condition.

In some embodiments of the present application, the determining conditions include conditions determined based on at least one of the following information:

load conditions of the network device;

Interference conditions of the network device;

interference conditions of the terminal equipment; or (b)

Number of LBT failures.

In some embodiments of the present application, the determining condition is a condition determined based on an interference situation of the terminal device, and the plurality of preset scenes includes at least one of the following scenes:

disturbing uncontrolled scenes;

disturbing the partially controlled scene; or (b)

Disturbing the controlled scene.

In some embodiments of the present application, the interference uncontrolled scenario refers to any one of load of the network device, interference of the network device, or interference of the terminal device, LBT failure times being greater than or equal to a first threshold; and/or the interference part uncontrolled scenario means that each of the load of the network device, the interference of the network device, or the interference of the terminal device is less than or equal to a second threshold; and/or the interference part uncontrolled scene refers to that any one of the load of the network equipment, the interference of the network equipment, or the interference of the terminal equipment, and the LBT failure times is smaller than or equal to a third threshold value and larger than a fourth threshold value; and/or, the interference controlled scenario refers to that each of the load of the network device, the interference of the network device, or the interference of the terminal device, and the LBT failure number is smaller than or equal to a fifth threshold value.

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

In some embodiments of the present application, the plurality of services includes low latency high reliability communication URLLC services and/or enhanced mobile ultra wideband eMBB services.

In some embodiments of the present application, the method further comprises:

In some embodiments of the present application, the reporting information is used to indicate at least one of a service, a bearer, a slice, a resource, or a resource type for which the triggered LBT failure is intended.

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

In some embodiments of the present application, the processing unit 420 is specifically configured to:

in case of receiving an LBT failure indication from the physical layer, incrementing the count of the first counter by 1; and/or the number of the groups of groups,

restarting the first timer.

resetting the first counter, and/or in case the timing of the first timer exceeds the duration of the first timer or a triggered consecutive LBT failure is cancelled;

Stopping the first timer.

It should be understood that apparatus embodiments and method embodiments may correspond with each other and that similar descriptions may refer to the method embodiments. Specifically, the terminal device 400 shown in fig. 4 may correspond to a corresponding main body in performing the method 200 of the embodiment of the present application, and the foregoing and other operations and/or functions of each unit in the terminal device 400 are respectively for implementing the corresponding flow in each method in fig. 2, which is not described herein for brevity.

Fig. 5 is a schematic block diagram of a network device 500 of an embodiment of the present application.

A sending unit 510, configured to send a plurality of LBT failure recovery configurations, where a first LBT failure recovery configuration corresponding to the first information in the plurality of LBT failure recovery configurations is used for the terminal device to detect a continuous LBT failure and/or trigger a failure recovery procedure.

load conditions of the network device;

interference conditions of the network device;

interference conditions of the terminal equipment; or (b)

Number of LBT failures.

disturbing uncontrolled scenes;

disturbing the partially controlled scene; or (b)

Disturbing the controlled scene.

As shown in fig. 5, the network device 500 may include:

it should be understood that apparatus embodiments and method embodiments may correspond with each other and that similar descriptions may refer to the method embodiments. Specifically, the network device 500 shown in fig. 5 may correspond to a corresponding main body in performing the method 200 in the embodiment of the present application, and the foregoing and other operations and/or functions of each unit in the network device 500 are respectively for implementing the corresponding flow in each method in fig. 2, which are not described herein for brevity.

Fig. 6 is a schematic block diagram of a terminal device 600 of an embodiment of the present application.

As shown in fig. 6, the terminal device 600 may include:

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

a processing unit 620, configured to detect consecutive LBT failures and/or trigger a failure recovery procedure based on the second LBT failure recovery configuration and the first parameter; the first parameter is a parameter corresponding to second information in the at least one set of parameters, and each set of parameters in the at least one set of parameters is used for adjusting a second counter and/or a second timer in the second LBT failure recovery configuration.

Load conditions of the network device;

interference conditions of the network device;

interference conditions of the terminal equipment; or (b)

Number of LBT failures.

disturbing uncontrolled scenes;

disturbing the partially controlled scene; or (b)

Disturbing the controlled scene.

In some embodiments of the present application, the plurality of services includes low latency high reliability communications URLLC and/or enhanced mobile ultra wideband eMBB.

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

In some embodiments of the present application, the second parameter is an impact factor or a weight value.

In some embodiments of the present application, the third parameter is an impact factor or a weight value.

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

In some embodiments of the present application, the processing unit 620 is specifically configured to:

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

determining a second duration of a second timer based on the second timer first duration and the third parameter;

Based on the maximum value of the second counter and/or the second time period, detecting a consecutive LBT failure and/or triggering a failure recovery procedure.

in case of receiving an LBT failure indication from the physical layer, adding the count value to the count value of the second counter; and/or the number of the groups of groups,

restarting the second timer.

resetting the second counter, and/or, in case the timing of the second timer exceeds the second duration or the triggered consecutive LBT failures are cancelled;

stopping the second timer.

It should be understood that apparatus embodiments and method embodiments may correspond with each other and that similar descriptions may refer to the method embodiments. Specifically, the terminal device 600 shown in fig. 6 may correspond to a corresponding main body in performing the method 300 of the embodiment of the present application, and the foregoing and other operations and/or functions of each unit in the terminal device 600 are respectively for implementing the corresponding flow in each method in fig. 3, which are not described herein for brevity.

Fig. 7 is a schematic block diagram of a network device 700 of an embodiment of the present application.

As shown in fig. 7, the network device 700 may include:

a transmitting unit 710, configured to transmit a second LBT failure recovery configuration and at least one set of parameters, where the second LBT failure recovery configuration and the first parameters are used for the terminal device to detect a continuous LBT failure and/or trigger a failure recovery procedure; the first parameter is a parameter corresponding to second information in the at least one set of parameters, and each set of parameters in the at least one set of parameters is used for adjusting a second counter and/or a second timer in the second LBT failure recovery configuration.

Load conditions of the network device;

interference conditions of the network device;

interference conditions of the terminal equipment; or (b)

Number of LBT failures.

disturbing uncontrolled scenes;

disturbing the partially controlled scene; or (b)

Disturbing the controlled scene.

It should be understood that apparatus embodiments and method embodiments may correspond with each other and that similar descriptions may refer to the method embodiments. Specifically, the network device 700 shown in fig. 7 may correspond to a corresponding main body in performing the method 300 of the embodiment of the present application, and the foregoing and other operations and/or functions of each unit in the network device 700 are respectively for implementing the corresponding flow in each method in fig. 3, which are not described herein for brevity.

The communication device of the embodiments of the present application is described above from the perspective of the functional module in conjunction with the accompanying drawings. It should be understood that the functional module may be implemented in hardware, or may be implemented by instructions in software, or may be implemented by a combination of hardware and software modules.

Specifically, each step of the method embodiments in the embodiments of the present application may be implemented by an integrated logic circuit of hardware in a processor and/or an instruction in software form, and the steps of the method disclosed in connection with the embodiments of the present application may be directly implemented as a hardware decoding processor or implemented by a combination of hardware and software modules in the decoding processor.

Alternatively, the software modules may be located in a well-established storage medium in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, and the like. The storage medium is located in a memory, and the processor reads information in the memory, and in combination with hardware, performs the steps in the above method embodiments.

For example, the processing unit and the communication unit referred to above may be implemented by a processor and a transceiver, respectively.

Fig. 8 is a schematic structural diagram of a communication device 800 of an embodiment of the present application.

As shown in fig. 8, the communication device 800 may include a processor 810.

The processor 810 may call and execute a computer program from a memory to implement the methods of the embodiments of the present application.

With continued reference to fig. 8, the communication device 800 may also include a memory 820.

The memory 820 may be used for storing instruction information, and may also be used for storing code, instructions, etc. for execution by the processor 810. Wherein the processor 810 may call and run a computer program from the memory 820 to implement the methods in embodiments of the present application. The memory 820 may be a separate device from the processor 810 or may be integrated into the processor 810.

With continued reference to fig. 8, the communication device 800 may also include a transceiver 830.

The processor 810 may control the transceiver 830 to communicate with other devices, and in particular, may send information or data to other devices or receive information or data sent by other devices. Transceiver 830 may include a transmitter and a receiver. Transceiver 830 may further include antennas, the number of which may be one or more.

It should be appreciated that the various components in the communication device 800 are connected by a bus system that includes a power bus, a control bus, and a status signal bus in addition to a data bus.

It should also be understood that the communication device 800 may be a terminal device of the embodiment of the present application, and the communication device 800 may implement a corresponding flow 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 of the embodiment of the present application, and may correspond to a corresponding main body in executing the

method

200 or 300 according to the embodiment of the present application, which is not repeated herein for brevity. Similarly, the communication device 800 may be a network device according to an embodiment of the present application, and the communication device 800 may implement a corresponding flow implemented by the network device in the respective methods according to the embodiments of the present application. That is, the communication device 800 of the embodiment of the present application may correspond to the

network device

500 or 700 of the embodiment of the present application, and may correspond to the respective subject performing the

method

200 or 300 according to the embodiment of the present application, and for brevity, will not be described herein.

In addition, the embodiment of the application also provides a chip.

For example, the chip may be an integrated circuit chip having signal processing capabilities, and may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. The chip may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc. Alternatively, the chip may be applied to various communication devices, so that the communication device mounted with the chip can perform the methods, steps and logic blocks disclosed in the embodiments of the present application.

Fig. 9 is a schematic block diagram of a chip 900 according to an embodiment of the present application.

As shown in fig. 9, the chip 900 includes a processor 910.

Wherein the processor 910 may call and run a computer program from a memory to implement the methods in embodiments of the present application.

With continued reference to fig. 9, the chip 900 may also include a memory 920.

Wherein the processor 910 may invoke and run a computer program from the memory 920 to implement the methods in the embodiments of the present application. The memory 920 may be used for storing instruction information and may also be used for storing code, instructions, etc. for execution by the processor 910. The memory 920 may be a separate device from the processor 910 or may be integrated in the processor 910.

With continued reference to fig. 9, the chip 900 may also include an input interface 930.

The processor 910 may control the input interface 930 to communicate with other devices or chips, and in particular, may acquire information or data sent by the other devices or chips.

With continued reference to fig. 9, the chip 900 may further include an output interface 940.

Wherein the processor 910 may control the output interface 940 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

It should be understood that the chip 900 may be applied to a network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, or may implement a corresponding flow implemented by a terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

It should also be appreciated that the various components in the chip 900 are connected by a bus system that includes a power bus, a control bus, and a status signal bus in addition to a data bus.

The processors referred to above may include, but are not limited to:

a general purpose processor, digital signal processor (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like.

The processor may be configured to implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present application. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory or erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

The above references to memory include, but are not limited to:

volatile memory and/or nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and Direct memory bus RAM (DR RAM).

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

There is also provided in an embodiment of the present application a computer-readable storage medium for storing a computer program. The computer readable storage medium stores one or more programs, the one or more programs comprising instructions, which when executed by a portable electronic device comprising a plurality of application programs, enable the portable electronic device to perform the method of the embodiments shown in

method

200 or 300.

Optionally, the computer readable storage medium may be applied to a network device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, which is not described herein for brevity.

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

Optionally, the computer program product may be applied to a network device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program causes a computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, which are not described herein for brevity.

A computer program is also provided in an embodiment of the present application. The computer program, when executed by a computer, enables the computer to perform the methods of the embodiments shown in

method

200 or 300.

Optionally, the computer program may be applied to a network device in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

In addition, the embodiment of the present application further provides a communication system, which may include the above-mentioned terminal device and network device, so as to form the communication system 100 shown in fig. 1, which is not described herein for brevity. It should be noted that the term "system" and the like herein may also be referred to as "network management architecture" or "network system" and the like.

It is also to be understood that the terminology used in the embodiments of the present application and the appended claims is for the purpose of describing particular embodiments only, and is not intended to be limiting of the embodiments of the present application.

For example, as used in the examples and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

Those of skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the embodiments of the present application.

If implemented as a software functional unit and sold or used as a stand-alone product, may be stored on a computer readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or, what contributes to the prior art, or part of the technical solution may be embodied in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method of the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

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

For example, the division of units or modules or components in the above-described apparatus embodiments is merely a logic function division, and there may be another division manner in actual implementation, for example, multiple units or modules or components may be combined or may be integrated into another system, or some units or modules or components may be omitted or not performed.

As another example, the units/modules/components described above as separate/display components may or may not be physically separate, i.e., may be located in one place, or may be distributed over multiple network elements. Some or all of the units/modules/components may be selected according to actual needs to achieve the purposes of the embodiments of the present application.

Finally, it is pointed out that the coupling or direct coupling or communication connection between the various elements shown or discussed above can be an indirect coupling or communication connection via interfaces, devices or elements, which can be in electrical, mechanical or other forms.

The foregoing is merely a specific implementation of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto, and any person skilled in the art may easily think about changes or substitutions within the technical scope of the embodiments of the present application, and all changes and substitutions are 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 subject to the protection scope of the claims.

Claims

A method of wireless communication, comprising:

receiving a plurality of LBT failure recovery configurations;

based on a first LBT failure recovery configuration of the plurality of LBT failure recovery configurations corresponding to the first information, detecting consecutive LBT failures and/or triggering a failure recovery procedure.
The method of claim 1, wherein the plurality of LBT failure recovery configurations correspond to a plurality of scenarios or the plurality of LBT failure recovery configurations correspond to a plurality of network environments; the first information is a scene or a network environment when the LBT fails.
The method of claim 2, wherein the plurality of scenes or the plurality of network environments are preset or the plurality of scenes or the plurality of network environments are determined based on a determination condition.
A method according to claim 3, wherein the determination condition comprises a condition determined based on at least one of the following information:

load conditions of the network device;

interference conditions of the network device;

interference conditions of the terminal equipment; or (b)

Number of LBT failures.
A method according to claim 3, characterized in that the determination condition is a condition determined based on an interference situation of the terminal device, and the plurality of preset scenarios comprises at least one of the following scenarios:

disturbing uncontrolled scenes;

disturbing the partially controlled scene; or (b)

Disturbing the controlled scene.
The method of capability 5, wherein the interference uncontrolled scenario refers to any one of a load of a network device, an interference of a network device, or an interference of a terminal device, a number of LBT failures being greater than or equal to a first threshold; and/or the interference part uncontrolled scenario means that each of the load of the network device, the interference of the network device, or the interference of the terminal device is less than or equal to a second threshold; and/or the interference part uncontrolled scene refers to that any one of the load of the network equipment, the interference of the network equipment, or the interference of the terminal equipment, and the LBT failure times is smaller than or equal to a third threshold value and larger than a fourth threshold value; and/or, the interference controlled scenario refers to that each of the load of the network device, the interference of the network device, or the interference of the terminal device, and the LBT failure number is smaller than or equal to a fifth threshold value.
The method according to any one of claims 2 to 6, further comprising:

one LBT failure recovery configuration is maintained, the one LBT failure recovery configuration being the first LBT failure recovery configuration.
The method according to any one of claims 2 to 7, further comprising:

and resetting the first LBT failure recovery configuration under the condition that the scene or the network environment at the time of LBT failure is changed.
The method of claim 1, wherein the plurality of LBT failure recovery configurations correspond to a plurality of services, and the first information is a service for which LBT failure is intended; or the plurality of LBT failure recovery configurations correspond to a plurality of bearers, and the first information is a bearer for which the LBT failure is aimed; or the plurality of LBT failure recovery configurations correspond to a plurality of slices, and the first information is a slice for which LBT failure is aimed; or the plurality of LBT failure recovery configurations correspond to a plurality of resources or resource types, and the first information is the resource or the resource type for which the LBT failure is aimed.
The method of claim 9, wherein the plurality of services comprises low latency high reliability communication URLLC services and/or enhanced mobile ultra wideband eMBB services.
The method of claim 1, wherein the plurality of LBT failure recovery configurations comprises at least one dedicated LBT failure recovery configuration and a common LBT failure recovery configuration, the at least one dedicated LBT failure recovery configuration comprising a dedicated LBT failure recovery configuration configured for at least one of traffic, bearer, slice, resource, or resource type, the first information being at least one of traffic, bearer, slice, resource, or resource type for which LBT failure was intended; the common LBT failure recovery configuration refers to an LBT failure recovery configuration that does not differentiate between at least one of a service, a bearer, a slice, a resource, or a resource type, and the first information is an LBT failure indication that does not differentiate between at least one of a service, a bearer, a slice, a resource, or a resource type.
The method according to any one of claims 9 to 11, further comprising:

at least one LBT failure recovery configuration is maintained, the at least one LBT failure recovery configuration comprising an LBT failure recovery configuration for at least one of a traffic, a bearer, a slice, a resource, or a resource type, and/or an LBT failure recovery configuration that does not differentiate between at least one of a traffic, a bearer, a slice, a resource, or a resource type, the at least one LBT failure recovery configuration comprising the first LBT failure recovery configuration.
The method according to any of claims 1 to 12, wherein the failure recovery procedure refers to a failure recovery procedure for a bandwidth portion BWP triggered based on at least one of traffic, bearers, slices, resources or resource types on the BWP; or the failure recovery procedure refers to a failure recovery procedure for a serving cell triggered by at least one of traffic, bearers, slices, resources, or resource types on the serving cell.
The method according to any one of claims 1 to 13, further comprising:

and sending reporting information to a Media Access Control (MAC) layer, wherein the reporting information is used for indicating failure of triggering the LBT.
The method of claim 14, wherein the reporting information is used to indicate at least one of traffic, bearers, slices, resources, or resource types for which triggered LBT failure is intended.
The method according to any of claims 1 to 15, wherein the first LBT failure recovery configuration is indicated by a network device, or wherein the first LBT failure recovery configuration is determined by a terminal device, or wherein the first LBT failure recovery configuration is determined by a semi-static configuration.
The method according to any of claims 1 to 16, wherein the first LBT failure recovery configuration comprises a first counter and/or a first timer.
Method according to claim 17, characterized in that the first counter is configured with an initial value and/or a maximum value.
The method of claim 17, wherein the detecting consecutive LBT failures and/or triggering a failure recovery procedure based on a first LBT failure recovery configuration of the plurality of LBT failure recovery configurations corresponding to first information comprises:

in case of receiving an LBT failure indication from the physical layer, incrementing the count of the first counter by 1; and/or the number of the groups of groups,

restarting the first timer.
The method of claim 17, wherein the detecting consecutive LBT failures and/or triggering a failure recovery procedure based on a first LBT failure recovery configuration of the plurality of LBT failure recovery configurations corresponding to first information comprises:

in case the count of the first counter is greater than or equal to the maximum value of the first counter, a consecutive LBT failure is determined or triggered.
The method of claim 17, wherein the detecting consecutive LBT failures and/or triggering a failure recovery procedure based on a first LBT failure recovery configuration of the plurality of LBT failure recovery configurations corresponding to first information comprises:

Resetting the first counter, and/or in case the timing of the first timer exceeds the duration of the first timer or a triggered consecutive LBT failure is cancelled;

stopping the first timer.
A method of wireless communication, comprising:

and transmitting a plurality of LBT failure recovery configurations, wherein a first LBT failure recovery configuration corresponding to the first information in the plurality of LBT failure recovery configurations is used for detecting continuous LBT failures and/or triggering a failure recovery process by the terminal equipment.
The method of claim 22, wherein the plurality of LBT failure recovery configurations correspond to a plurality of scenarios or the plurality of LBT failure recovery configurations correspond to a plurality of network environments; the first information is a scene or a network environment when the LBT fails.
The method of claim 23, wherein the plurality of scenes or the plurality of network environments are preset or the plurality of scenes or the plurality of network environments are determined based on a determination condition.
The method of claim 24, wherein the determining a condition comprises determining a condition based on at least one of:

load conditions of the network device;

Interference conditions of the network device;

interference conditions of the terminal equipment; or (b)

Number of LBT failures.
The method according to claim 24, wherein the determination condition is a condition determined based on an interference situation of the terminal device, and the plurality of preset scenes include at least one of the following scenes:

disturbing uncontrolled scenes;

disturbing the partially controlled scene; or (b)

Disturbing the controlled scene.
The method of capability 26, wherein the interference uncontrolled scenario refers to any one of a load of a network device, interference of a network device, or interference of a terminal device, LBT failure times being greater than or equal to a first threshold; and/or the interference part uncontrolled scenario means that each of the load of the network device, the interference of the network device, or the interference of the terminal device is less than or equal to a second threshold; and/or the interference part uncontrolled scene refers to that any one of the load of the network equipment, the interference of the network equipment, or the interference of the terminal equipment, and the LBT failure times is smaller than or equal to a third threshold value and larger than a fourth threshold value; and/or, the interference controlled scenario refers to that each of the load of the network device, the interference of the network device, or the interference of the terminal device, and the LBT failure number is smaller than or equal to a fifth threshold value.
The method of claim 22, wherein the plurality of LBT failure recovery configurations correspond to a plurality of services, and wherein the first information is a service for which LBT failure is intended; or the plurality of LBT failure recovery configurations correspond to a plurality of bearers, and the first information is a bearer for which the LBT failure is aimed; or the plurality of LBT failure recovery configurations correspond to a plurality of slices, and the first information is a slice for which LBT failure is aimed; or the plurality of LBT failure recovery configurations correspond to a plurality of resources or resource types, and the first information is the resource or the resource type for which the LBT failure is aimed.
The method of claim 28, wherein the plurality of services comprises low latency high reliability communication URLLC services and/or enhanced mobile ultra wideband eMBB services.
The method of claim 22, wherein the plurality of LBT failure recovery configurations comprises at least one dedicated LBT failure recovery configuration and a common LBT failure recovery configuration, the at least one dedicated LBT failure recovery configuration comprising a dedicated LBT failure recovery configuration configured for at least one of traffic, bearer, slice, resource, or resource type, the first information being at least one of traffic, bearer, slice, resource, or resource type for which LBT failure was intended; the common LBT failure recovery configuration refers to an LBT failure recovery configuration that does not differentiate between at least one of a service, a bearer, a slice, a resource, or a resource type, and the first information is an LBT failure indication that does not differentiate between at least one of a service, a bearer, a slice, a resource, or a resource type.
The method according to any of claims 22 to 30, wherein the failure recovery procedure refers to a failure recovery procedure for a bandwidth portion BWP triggered based on at least one of traffic, bearers, slices, resources or resource types on the BWP; or the failure recovery procedure refers to a failure recovery procedure for a serving cell triggered by at least one of traffic, bearers, slices, resources, or resource types on the serving cell.
The method according to any of claims 22 to 31, wherein the first LBT failure recovery configuration is indicated by a network device, or wherein the first LBT failure recovery configuration is determined by a terminal device, or wherein the first LBT failure recovery configuration is determined by a semi-static configuration.
The method according to any of claims 22 to 32, wherein the first LBT failure recovery configuration comprises a first counter and/or a first timer.
The method according to claim 33, wherein the first counter is configured with an initial value and/or a maximum value.
A method of wireless communication, comprising:

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

Detecting consecutive LBT failures and/or triggering a failure recovery procedure based on the second LBT failure recovery configuration and the first parameter; the first parameter is a parameter corresponding to second information in the at least one set of parameters, and each set of parameters in the at least one set of parameters is used for adjusting a second counter and/or a second timer in the second LBT failure recovery configuration.
The method of claim 35, wherein 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 a scenario or network environment when LBT fails.
The method of claim 36, wherein the plurality of scenes or the plurality of network environments are preset or the plurality of scenes or the plurality of network environments are determined based on a determination condition.
The method of claim 37, wherein the determining a condition comprises determining a condition based on at least one of:

load conditions of the network device;

interference conditions of the network device;

interference conditions of the terminal equipment; or (b)

Number of LBT failures.
The method of claim 37, wherein the determination condition is a condition determined based on an interference situation of the terminal device, and the plurality of preset scenes include at least one of the following scenes:

Disturbing uncontrolled scenes;

disturbing the partially controlled scene; or (b)

Disturbing the controlled scene.
The method of claim 39, wherein the uncontrolled interference scenario refers to any one of a load of a network device, interference of a network device, or interference of a terminal device, LBT failure times being greater than or equal to a first threshold; and/or the interference part uncontrolled scenario means that each of the load of the network device, the interference of the network device, or the interference of the terminal device is less than or equal to a second threshold; and/or the interference part uncontrolled scene refers to that any one of the load of the network equipment, the interference of the network equipment, or the interference of the terminal equipment, and the LBT failure times is smaller than or equal to a third threshold value and larger than a fourth threshold value; and/or, the interference controlled scenario refers to that each of the load of the network device, the interference of the network device, or the interference of the terminal device, and the LBT failure number is smaller than or equal to a fifth threshold value.
The method of claim 35, wherein the at least one set of parameters corresponds to a plurality of services, and the second information is a service for which LBT failed; or the at least one group of parameters corresponds to a plurality of bearers, and the second information is the bearer for which the LBT fails; or the at least one group of parameters corresponds to a plurality of slices, and the second information is a slice for which LBT fails; or the at least one set of parameters corresponds to a plurality of resource types, and the second information is the type of the resource for which the LBT fails.
The method of claim 41, wherein the plurality of services include low latency high reliability communications URLLC and/or enhanced mobile ultra-wideband eMBB.
The method according to any one of claims 35 to 42, wherein the failure recovery procedure refers to a failure recovery procedure for a bandwidth part BWP triggered based on at least one of traffic, bearers, slices, resources or resource types on the BWP; or the failure recovery procedure refers to a failure recovery procedure for a serving cell triggered by at least one of traffic, bearers, slices, resources, or resource types on the serving cell.
The method of any one of claims 35 to 43, further comprising:

and sending reporting information to a Media Access Control (MAC) layer, wherein the reporting information is used for indicating failure of triggering the LBT.
The method of claim 44, wherein the reporting information is used to indicate at least one of traffic, bearers, slices, resources, or resource types for which the triggered LBT failure was intended.
The method according to any one of claims 35 to 45, wherein the at least one set of parameters is determined or selected by the terminal device, or wherein the at least one set of parameters is preconfigured, or wherein the at least one set of parameters is network configured or indicated.
The method according to any one of claims 1 to 46, wherein the first parameter comprises a second parameter for adjusting the second counter and/or a third parameter for adjusting the second timer.
The method of claim 47, wherein the second parameter is an impact factor or a weight value.
The method of claim 47 or 48, wherein the third parameter is an impact factor or a weight value.
Method according to any one of claims 47 to 49, characterized in that the second counter is configured with an initial value and/or a maximum value.
The method of claim 50, wherein detecting consecutive LBT failures and/or triggering a failure recovery procedure based on the second LBT failure recovery configuration and a first parameter comprises:

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

determining a second duration of a second timer based on the second timer first duration and the third parameter;

based on the maximum value of the second counter and/or the second time period, detecting a consecutive LBT failure and/or triggering a failure recovery procedure.
The method of claim 51, wherein detecting consecutive LBT failures and/or triggering a failure recovery procedure based on a maximum value of the second counter and/or the second duration comprises:

in case of receiving an LBT failure indication from the physical layer, adding the count value to the count value of the second counter; and/or restarting the second timer.
The method of claim 51, wherein detecting consecutive LBT failures and/or triggering a failure recovery procedure based on a maximum value of the second counter and/or the second duration comprises:

in case the count of the second counter is greater than or equal to the maximum value of the second counter, a consecutive LBT failure is determined or triggered.
The method of claim 51, wherein detecting consecutive LBT failures and/or triggering a failure recovery procedure based on a maximum value of the second counter and/or the second duration comprises:

resetting the second counter, and/or, in case the timing of the second timer exceeds the second duration or the triggered consecutive LBT failures are cancelled;

stopping the second timer.
A method of wireless communication, comprising:

transmitting a second LBT failure recovery configuration and at least one set of parameters, the second LBT failure recovery configuration and the first parameters being used for the terminal device to detect consecutive LBT failures and/or to trigger a failure recovery procedure; the first parameter is a parameter corresponding to second information in the at least one set of parameters, and each set of parameters in the at least one set of parameters is used for adjusting a second counter and/or a second timer in the second LBT failure recovery configuration.
The method of claim 55, wherein 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 a scenario or network environment when LBT fails.
The method of claim 56, wherein said plurality of scenes or said plurality of network environments are preset or said plurality of scenes or said plurality of network environments are determined based on a determination condition.
The method of claim 57, wherein the determining a condition comprises a condition determined based on at least one of:

load conditions of the network device;

Interference conditions of the network device;

interference conditions of the terminal equipment; or (b)

Number of LBT failures.
The method of claim 57, wherein the determination condition is a condition determined based on an interference situation of the terminal device, and the plurality of preset scenes include at least one of the following scenes:

disturbing uncontrolled scenes;

disturbing the partially controlled scene; or (b)

Disturbing the controlled scene.
The method of claim 59, wherein the uncontrolled interference scenario refers to any one of a load of a network device, interference of a network device, or interference of a terminal device, LBT failure times being greater than or equal to a first threshold; and/or the interference part uncontrolled scenario means that each of the load of the network device, the interference of the network device, or the interference of the terminal device is less than or equal to a second threshold; and/or the interference part uncontrolled scene refers to that any one of the load of the network equipment, the interference of the network equipment, or the interference of the terminal equipment, and the LBT failure times is smaller than or equal to a third threshold value and larger than a fourth threshold value; and/or, the interference controlled scenario refers to that each of the load of the network device, the interference of the network device, or the interference of the terminal device, and the LBT failure number is smaller than or equal to a fifth threshold value.
The method of claim 55, wherein the at least one set of parameters corresponds to a plurality of services, and the second information is a service for which LBT failed; or the at least one group of parameters corresponds to a plurality of bearers, and the second information is the bearer for which the LBT fails; or the at least one group of parameters corresponds to a plurality of slices, and the second information is a slice for which LBT fails; or the at least one set of parameters corresponds to a plurality of resource types, and the second information is the type of the resource for which the LBT fails.
The method of claim 61, wherein the plurality of services comprise low latency high reliability communications URLLC and/or enhanced mobile ultra-wideband eMBB.
The method according to any one of claims 55 to 62, wherein the failure recovery procedure refers to a failure recovery procedure for a bandwidth portion BWP triggered based on at least one of traffic, bearers, slices, resources or resource types on the BWP; or the failure recovery procedure refers to a failure recovery procedure for a serving cell triggered by at least one of traffic, bearers, slices, resources, or resource types on the serving cell.
The method according to any one of claims 55 to 63, 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 preconfigured, or the at least one set of parameters is network configured or indicated.
The method according to any one of claims 55 to 64, wherein the first parameter comprises a second parameter for adjusting the second counter and/or a third parameter for adjusting the second timer.
The method of claim 65, wherein the second parameter is an impact factor or a weight value.
The method of claim 65 or 66, wherein the third parameter is an impact factor or a weight value.
The method according to any one of claims 65 to 67, wherein the second counter is configured with an initial value and/or a maximum value.
A terminal device, comprising:

a receiving unit configured to receive a plurality of LBT failure recovery configurations;

and the processing unit is used for detecting continuous LBT failure and/or triggering a failure recovery process based on a first LBT failure recovery configuration corresponding to the first information in the plurality of LBT failure recovery configurations.
A network device, comprising:

and the sending unit is used for sending a plurality of LBT failure recovery configurations, and a first LBT failure recovery configuration corresponding to the first information in the plurality of LBT failure recovery configurations is used for detecting continuous LBT failures and/or triggering a failure recovery process by the terminal equipment.
A terminal device, comprising:

a receiving unit for receiving a second LBT failure recovery configuration and at least one set of parameters;

a processing unit, configured to detect a continuous LBT failure and/or trigger a failure recovery procedure based on the second LBT failure recovery configuration and the first parameter; the first parameter is a parameter corresponding to second information in the at least one set of parameters, and each set of parameters in the at least one set of parameters is used for adjusting a second counter and/or a second timer in the second LBT failure recovery configuration.
A network device, comprising:

a transmitting unit, configured to transmit a second LBT failure recovery configuration and at least one set of parameters, where the second LBT failure recovery configuration and the first parameters are used for detecting continuous LBT failures and/or triggering a failure recovery procedure by a terminal device; the first parameter is a parameter corresponding to second information in the at least one set of parameters, and each set of parameters in the at least one set of parameters is used for adjusting a second counter and/or a second timer in the second LBT failure recovery configuration.
A terminal device, comprising:

a processor, a memory and a transceiver, the memory being for storing a computer program, the processor being for invoking and running the computer program stored in the memory to perform the method of any of claims 1 to 21 or the method of any of claims 35 to 54.
A network device, comprising:

a processor, a memory and a transceiver, the memory for storing a computer program, the processor for invoking and running the computer program stored in the memory to perform the method of any of claims 22 to 34 or the method of any of claims 55 to 68.
A chip, comprising:

a processor for calling and running a computer program from memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 21, the method of any one of claims 22 to 34, the method of any one of claims 35 to 54, or the method of any one of claims 55 to 68.
A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 21, the method of any one of claims 22 to 34, the method of any one of claims 35 to 54, or the method of any one of claims 55 to 68.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 21, the method of any one of claims 22 to 34, the method of any one of claims 35 to 54 or the method of any one of claims 55 to 68.
A computer program, characterized in that it causes a computer to perform the method of any one of claims 1 to 21, the method of any one of claims 22 to 34, the method of any one of claims 35 to 54 or the method of any one of claims 55 to 68.