CN114503775A

CN114503775A - Method and device for determining listening-before-speaking failure

Info

Publication number: CN114503775A
Application number: CN202280000052.1A
Authority: CN
Inventors: 江小威
Original assignee: Beijing Xiaomi Mobile Software Co Ltd
Current assignee: Beijing Xiaomi Mobile Software Co Ltd
Priority date: 2022-01-12
Filing date: 2022-01-12
Publication date: 2022-05-13
Also published as: WO2023133736A1

Abstract

The embodiment of the disclosure discloses a method for determining hearing before speaking failure, which can be applied to the technical field of communication, wherein the method executed by a terminal device comprises the following steps: in case that it is determined that the listen-before-talk LBT detection result corresponding to the bandwidth part BWP satisfies the preset condition, it is determined that the BWP has the continuous LBT failure. Therefore, the terminal device can accurately judge that the BWP has the continuous LBT failure, so that the accuracy and the reliability of determining that the BWP has the continuous LBT failure can be improved, the rationality of switching the BWP can be further improved, and the waste of resources is avoided.

Description

Method and device for determining listening-before-speaking failure

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for determining a listen before talk failure.

Background

With the continuous development of communication technology, the frequency supported by New Radio (NR) needs to be increased from maximum 52.6 gigahertz (GHz) to maximum 71GHz to meet more communication requirements.

In the related art, before the terminal device uses the frequency band to transmit data, it needs to Listen Before Talk (LBT), and can transmit data only after detecting that the channel is in an idle state.

Disclosure of Invention

The embodiments of the present disclosure provide a method and an apparatus for determining listen before talk failure, which can accurately determine that a BWP has a continuous LBT failure according to a preset condition.

In a first aspect, an embodiment of the present disclosure provides a method for determining a listen-before-talk failure, where the method is performed by a terminal device, and the method includes: and under the condition that the detection result of the listen-before-talk LBT corresponding to the bandwidth part BWP meets the preset condition, determining that the continuous LBT of the BWP fails.

In the disclosure, the terminal device determines that the sustained LBT failure occurs for the bandwidth part BWP in case that the listen-before-talk LBT detection result corresponding to the BWP is determined to satisfy the preset condition. Therefore, the terminal device can accurately judge that the BWP has the continuous LBT failure, so that the accuracy and the reliability of determining that the BWP has the continuous LBT failure can be improved, the rationality of switching the BWP can be further improved, and the waste of resources is avoided.

Optionally, the preset condition is any one of the following conditions:

persistent LBT fails and there is currently ongoing random access;

persistent LBT failure and no ongoing random access currently;

the LBT counting value is larger than or equal to a first threshold and the current random access is carried out;

the LBT counting value is larger than or equal to a first threshold and no ongoing random access exists currently;

the LBT count value corresponding to the preset beam is larger than a first threshold value;

sustained LBT failure was detected for all beams in the preset beam set.

Optionally, the preset beam set is any one of:

the preset beam set configured by the network equipment;

the preset beam set corresponding to a sending beam set configured by the network equipment;

the preset beam set corresponding to a currently activated transmit beam set.

Optionally, the method further includes:

determining a beam identifier corresponding to an LBT failure instance corresponding to the BWP;

and under the condition that the beam identifier is the identifier of a preset beam or the identifier of each beam in a preset beam set, adding 1 to the LBT count value.

Optionally, the currently ongoing random access is any one of:

there is random access associated with the current serving cell;

there is random access triggered by persistent LBT failure;

there is a random access triggered by the LBT count value being greater than or equal to the first threshold value.

Optionally, the random access currently not in progress is any of:

no random access associated with the current serving cell;

no random access triggered by a sustained LBT failure;

there is no random access triggered by the LBT count value being greater than or equal to the first threshold value.

Optionally, the method further includes:

triggering random access in response to no ongoing random access currently;

the LBT count value is cleared.

Optionally, the method further includes:

and sending first indication information to a network device under the condition that a preset function is in an enabled state, wherein the first indication information is used for indicating that continuous LBT failure occurs in the BWP.

Optionally, the method further includes:

and receiving second indication information, wherein the second indication information is used for indicating whether the preset function is started or not.

Optionally, the first indication information includes at least one of the following: BWP identification, serving cell identification, and beam set identification.

In a second aspect, an embodiment of the present disclosure provides a communication apparatus, including:

and the processing module is used for determining that continuous LBT failure occurs on the BWP under the condition that the detection result of listen-before-talk LBT corresponding to the bandwidth part BWP meets the preset condition.

Optionally, the preset condition is any one of the following conditions: :

persistent LBT fails and there is currently ongoing random access;

persistent LBT failure and no ongoing random access currently;

sustained LBT failure was detected for all beams in the preset beam set.

Optionally, the preset beam set is any one of:

the preset beam set configured by the network equipment;

the preset beam set corresponding to a currently activated transmit beam set.

Optionally, the processing module is specifically configured to:

Optionally, the currently ongoing random access is any one of:

there is random access associated with the current serving cell;

there is random access triggered by persistent LBT failure;

Optionally, the random access currently not in progress is any of:

no random access associated with the current serving cell;

no random access triggered by a sustained LBT failure;

Optionally, the processing module is specifically configured to:

triggering random access in response to no ongoing random access currently;

the LBT count value is cleared.

Optionally, the method further includes:

the transceiver module sends first indication information to a network device when a preset function is in an enabled state, where the first indication information is used to indicate that the BWP has a persistent LBT failure.

Optionally, the transceiver module is specifically configured to:

In a third aspect, the disclosed embodiments provide a communication device comprising a processor, which, when calling a computer program in a memory, executes the method of the first aspect.

In a fourth aspect, an embodiment of the present disclosure provides a communication apparatus including a processor and a memory, the memory having a computer program stored therein; the processor executes the computer program stored in the memory to cause the communication device to perform the method of the first aspect.

In a fifth aspect, the disclosed embodiments provide a communication device, which includes a processor and an interface circuit, the interface circuit is configured to receive code instructions and transmit the code instructions to the processor, and the processor is configured to execute the code instructions to cause the device to perform the method according to the first aspect.

In a sixth aspect, the present disclosure provides a system for determining a listen before talk failure, where the system includes the communication apparatus according to the second aspect, or the system includes the communication apparatus according to the third aspect, or the system includes the communication apparatus according to the fourth aspect, or the system includes the communication apparatus according to the fifth aspect.

In a seventh aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions for the terminal device, where the instructions, when executed, cause the terminal device to perform the method of the first aspect.

In an eighth aspect, the present disclosure also provides a computer program product comprising a computer program which, when run on a computer, causes the computer to perform the method of the first aspect described above.

In a ninth aspect, the present disclosure provides a chip system comprising at least one processor and an interface for enabling a terminal device to implement the functionality according to the first aspect, e.g. to determine or process at least one of data and information according to the method described above. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the terminal device. The chip system may be formed by a chip, or may include a chip and other discrete devices.

In a tenth aspect, the present disclosure provides a computer program which, when run on a computer, causes the computer to perform the method of the first aspect described above.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments or the background art of the present disclosure, the drawings required to be used in the embodiments or the background art of the present disclosure will be described below.

Fig. 1 is a schematic architecture diagram of a communication system provided by an embodiment of the present disclosure;

fig. 2 is a schematic flow chart diagram illustrating a method for determining a listen-before-talk failure according to an embodiment of the present disclosure;

fig. 3 is a flow chart illustrating a method for determining a listen before talk failure according to an embodiment of the present disclosure;

fig. 4 is a flow chart illustrating a method for determining a listen before talk failure according to an embodiment of the present disclosure;

fig. 5 is a flow chart illustrating a method for determining a listen before talk failure according to an embodiment of the present disclosure;

fig. 6 is a flow chart illustrating a method for determining a listen before talk failure according to an embodiment of the present disclosure;

fig. 7 is a flow chart illustrating a method for determining a listen before talk failure according to an embodiment of the present disclosure;

fig. 8 is a schematic structural diagram of a communication device according to an embodiment of the present disclosure;

fig. 9 is a schematic structural diagram of another communication device provided in the embodiments of the present disclosure;

fig. 10 is a schematic structural diagram of a chip according to an embodiment of the present disclosure.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

For ease of understanding, terms to which the present disclosure relates will be first introduced.

1. Listen before talk (listen-before-talk, LBT)

Listen-before-talk (LBT), called "listen-before-talk" or "listen-before-send" as the name suggests, is a widely used technology in radio communications, in which a radio transmitter first listens to its radio environment before starting transmission, detects whether a channel is idle, and waits for transmission when the channel is idle if the channel is in a busy state, thereby avoiding channel access collision and realizing channel spectrum sharing.

2. Partial bandwidth (Bandwidth part, BWP)

The partial Bandwidth (BWP), which is a subset bandwidth of the total bandwidth, flexibly adjusts the size of the terminal device reception and transmission bandwidth through bandwidth adaptation in the NR so that the terminal device reception and transmission bandwidth does not need to be as large as the bandwidth of the cell.

Referring to fig. 1, fig. 1 is a schematic diagram of an architecture of a communication system according to an embodiment of the present disclosure. The communication system may include, but is not limited to, one network device and one terminal device, the number and form of the devices shown in fig. 1 are only for example and do not constitute a limitation to the embodiments of the present disclosure, and two or more network devices and two or more terminal devices may be included in practical applications. The communication system shown in fig. 1 is exemplified to include one network device 11 and one terminal device 12.

It should be noted that the technical solutions of the embodiments of the present disclosure can be applied to various communication systems. For example: a Long Term Evolution (LTE) system, a 5th generation (5G) mobile communication system, a 5G New Radio (NR) system, or other future new mobile communication systems.

The network device 11 in the embodiment of the present disclosure is an entity for transmitting or receiving signals on the network side. For example, the network device 101 may be an evolved NodeB (eNB), a transmission point (TRP), a next generation base station (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiments of the present disclosure do not limit the specific technologies and the specific device forms adopted by the network devices. The network device provided by the embodiment of the present disclosure may be composed of a Central Unit (CU) and a Distributed Unit (DU), where the CU may also be referred to as a control unit (control unit), and a protocol layer of a network device, such as a base station, may be split by using a structure of CU-DU, functions of a part of the protocol layer are placed in the CU for centralized control, and functions of the remaining part or all of the protocol layer are distributed in the DU, and the DU is centrally controlled by the CU.

The terminal device 12 in the embodiment of the present disclosure is an entity, such as a mobile phone, on the user side for receiving or transmitting signals. A terminal device may also be referred to as a terminal device (terminal), a User Equipment (UE), a Mobile Station (MS), a mobile terminal device (MT), etc. The terminal device may be a vehicle having a communication function, a smart vehicle, a mobile phone (mobile phone), a wearable device, a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self-driving (self-driving), a wireless terminal device in remote surgery (remote medical supply), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in smart city (smart city), a wireless terminal device in smart home (smart home), and the like. The embodiments of the present disclosure do not limit the specific technology and the specific device form adopted by the terminal device.

It is to be understood that the communication system described in the embodiment of the present disclosure is for more clearly illustrating the technical solutions of the embodiment of the present disclosure, and does not constitute a limitation to the technical solutions provided in the embodiment of the present disclosure, and as a person having ordinary skill in the art knows that as the system architecture evolves and new service scenarios appear, the technical solutions provided in the embodiment of the present disclosure are also applicable to similar technical problems.

In a communication system, for a high frequency band, for example, 60GHz, a very narrow beam can be used for transceiving. Then it makes no sense to do omni-directional LBT listening, since the LBT case not in the transmission direction has no impact on the transmission, as long as the channel in the transmission direction is idle. For this purpose, directional (directional) LBT may be introduced, i.e. LBT is not omni-directional monitoring, but only monitoring in a specific direction. The terminal device may transmit a beam and listen for a monitoring (transmitting) beam of LBT before it has some relationship as follows: one transmission beam may correspond to one sending beam or one sending beam set, or one sending beam corresponds to one transmission beam or one sending beam set, and the beam width of the sending beam or the sending beam set mapped by one transmission beam must at least cover the transmission beam.

At this time, after an LBT failure occurs once, because the terminal device may only have an LBT problem with the current uplink transmission beam, the terminal device may first attempt to switch the transmission beam, and trigger a continuous LBT failure of BWP when all beams have a continuous LBT failure. This poses a problem in that the terminal device does not know how many beams there are, so it is difficult to judge whether or not a sustained LBT failure has occurred for all beams. Therefore, the present disclosure may set a condition for triggering a persistent LBT failure for BWP, and the terminal device triggers the persistent LBT failure for BWP only when it is determined that the condition is satisfied. For example, a beam set or a preset beam that triggers the persistent LBT failure of BWP may be configured, so that the terminal device may determine whether to trigger the BWP to have the persistent LBT failure based on an LBT detection result corresponding to a beam in the preset beam set or the preset beam, and thus, accuracy and reliability of determining that the BWP has the persistent LBT failure may be improved. A method for determining location information and an apparatus thereof provided by the present disclosure are described in detail below with reference to the accompanying drawings.

Referring to fig. 2, fig. 2 is a flowchart illustrating a method for determining a listen before talk failure according to an embodiment of the present disclosure, where the method is executed by a terminal device. As shown in fig. 2, the method may include, but is not limited to, the following steps:

in step 201, in a case that it is determined that the listen-before-talk LBT detection result corresponding to the bandwidth portion BWP meets a preset condition, it is determined that the BWP has a sustained LBT failure.

The preset condition may be agreed by a protocol or preset in the system, which is not limited by the present disclosure.

In the present disclosure, a Medium Access Control (MAC) layer of a terminal device may receive an LBT failure instance indicated by a physical layer (PHY) in the process of performing LBT detection on BWP. Therefore, the terminal device can determine the LBT detection result corresponding to the current BWP according to the received LBT failure instance. For example, when the LBT failure instance is not received within a preset time period, it may be determined that the LBT detection corresponding to the current BWP is successful, so that the channel corresponding to the BWP may be utilized for data transmission. When receiving an LBT failure instance within a preset time period, the LBT detection result may be counted, and when the statistical result satisfies a preset condition, it may be determined that BWP has a continuous LBT failure, so that it may be determined that a channel corresponding to the current BWP belongs to an idle state.

In the present disclosure, the terminal device determines that the continuous LBT failure occurs for the bandwidth part BWP in a case where it is determined that the listen-before-talk LBT detection result corresponding to the BWP satisfies a preset condition. Therefore, the terminal device can accurately judge the BWP occurrence of the continuous LBT failure, thereby improving the accuracy and reliability of determining the BWP occurrence of the continuous LBT failure, further improving the rationality of switching the BWP and avoiding the waste of resources.

Referring to fig. 3, fig. 3 is a flowchart illustrating a method for determining a listen before talk failure according to an embodiment of the present disclosure, where the method is executed by a terminal device. As shown in fig. 3, the method may include, but is not limited to, the following steps:

step 301, determining a beam identifier corresponding to an LBT failure instance corresponding to BWP.

The beam identifier may be any information that can uniquely determine a beam, such as an Identity Document (ID) of the beam.

In this disclosure, when performing LBT detection on active BWP of a serving cell, when a PHY layer monitors that any LBT fails, the terminal device sends an LBT failure instance to an MAC layer, so that the MAC layer can determine a beam identifier corresponding to the LBT failure based on the LBT failure instance.

Step 302, in case that the beam identifier is the identifier of the preset beam, add 1 to the LBT count value.

The preset beam may be configured by the network device or agreed by a protocol. For example, the preset beam may be configured for the terminal device by the network device through a Physical Uplink Control CHannel (PUCCH) or a Physical Uplink Shared CHannel (PUSCH); or, the detection beam corresponding to the transmission beam set may also be used as a preset beam; alternatively, the detection beam corresponding to the currently activated transmission beam set may be determined as the preset beam. This is not limited by the present solution.

In addition, the beam set may be activated by a MAC Control Element (CE) or Downlink Control Information (DCI), or configured by a Radio Resource Control (RRC) layer. The first threshold value may be configured by each serving cell according to requirements.

In the present disclosure, after the MAC layer receives the LBT failure instance, if the detection beam corresponding to the LBT failure instance is the preset beam, the LBT counter (counter) is incremented by 1, and the failure detection timer is restarted (LBT-FailureDetectionTimer).

Optionally, the LBT counter may correspond to a preset beam, or may also correspond to a preset beam set, which is not limited in this disclosure.

In step 303, in case the LBT count value is greater than or equal to the first threshold, it is determined that BWP has occurred with persistent LBT failure.

In this disclosure, the terminal device may first determine a beam identifier corresponding to an LBT failure instance corresponding to the BWP, and then, add one to the LBT count value when the beam identifier is a preset beam or is each beam in a preset beam set, and determine that the BWP has a persistent LBT failure when the LBT count value is greater than or equal to a first threshold value. Therefore, the BWP is triggered to have the continuous LBT failure only under the condition that the LBT counting value corresponding to each beam in the preset beam or the preset beam set is larger than the first threshold value, so that the accuracy and the reliability of determining the BWP to have the continuous LBT failure are improved, the rationality of switching the BWP can be further improved, and the waste of resources is avoided.

Referring to fig. 4, fig. 4 is a flowchart illustrating a method for determining a listen before talk failure according to an embodiment of the present disclosure, where the method is executed by a terminal device. As shown in fig. 4, the method may include, but is not limited to, the following steps:

in step 401, in the case that the LBT count value is greater than or equal to the first threshold value and there is currently ongoing random access, it is determined that a continuous LBT failure occurs for BWP.

Optionally, the LBT detection result corresponding to BWP may also satisfy: and determining that the continuous LBT failure occurs in the BWP under the condition that the continuous LBT fails and the random access is currently carried out.

In this disclosure, before the LBT-FailureDetectionTimer times out, if the LBT counter count value is greater than or equal to the first threshold value, it may be considered that a persistent LBT failure has occurred, at this time, if there is an ongoing random access, it is determined that a persistent LBT failure has occurred in the BWP, and at this time, the LBT-FailureDetectionTimer timing may be stopped.

Optionally, when the LBT-FailureDetectionTimer times out, it indicates that the number of LBT failure instances received in the current timing period is smaller than the first threshold, that is, it may be determined that the channel state corresponding to the BWP becomes good, and the LBT counter count value may be cleared.

In the present disclosure, after the MAC layer receives the LBT failure instance, if the detection beam corresponding to the LBT failure instance is a preset beam or any beam in a preset beam set, the LBT counter is incremented by 1, and the failure monitoring timer is restarted (LBT-FailureDetectionTimer). Thereafter, the LBT count value may be compared with a first threshold value, and in the case that the LBT count value is greater than or equal to the first threshold value, it may be determined that BWP has sustained LBT failure.

Optionally, the network device may also configure different beam sets for PUSCH and PUCCH for triggering persistent LBT failure for BWP. Under the condition that the continuous LBT failure occurs on the preset beam set corresponding to the PUCCH and/or the PUSCH, the continuous LBT failure of the current BWP can be determined.

It should be noted that, when it is determined that the LBT detection result corresponding to the BWP is the continuous LBT failure, the terminal device may initiate random access on the current BWP to switch the transmission beam and attempt to recover the uplink beam. After the BWP is changed, the terminal device may set the LBT counter count value to 0 and stop LBT-FailureDetectionTimer counting.

In the present disclosure, there is a random access associated with the current serving cell, or a random access triggered by a persistent LBT failure, or a random access triggered by an LBT count value greater than or equal to a first threshold value, that is, it indicates that there is an ongoing random access currently.

Optionally, after determining that the BWP has the persistent LBT failure, that is, triggering the report of the association information of the persistent LBT failure, for example, the first indication information may be sent to the network device to indicate the association information of the BWP having the persistent LBT to the network device, where the association information of the BWP having the persistent LBT includes at least one of the following: identification of BWP where persistent LBT failure occurs, identification of serving cell, and identification of detection beam. That is, at least one of the following may be included in the first indication information: BWP identification, serving cell identification, and beam set identification, etc., which are not limited by this disclosure.

Optionally, the terminal device may further send the first indication information to the network device only when the preset function is in an enabled state, where the first indication information is used to indicate that the BWP has a persistent LBT failure, the preset function may be a function that controls the terminal device to send the first indication information, the terminal device may send the first indication information to the network device when the preset function is in the enabled state, and the terminal device does not send the first indication information to the network device when the preset function is in a disabled state.

Optionally, the association information may be reported to the network device through an MAC CE or an RRC signaling. After receiving the first indication information, the network device may determine that the current communication state of the terminal device is not good, and may allocate other communication resources to the terminal device according to the first indication information, so as to improve the communication quality.

Optionally, in the case that there is no available uplink resource, a Scheduling Request (SR) or a Random Access Channel (RACH) flow may also be triggered first to request the uplink resource, and then the first indication information may be sent based on the requested uplink resource.

Optionally, the terminal device may further receive second indication information sent by the network device, where the second indication information is used to indicate whether the preset function is started. Therefore, when the terminal equipment receives the second indication information, whether the preset function is started or not can be determined.

In the disclosure, the terminal device determines that the continuous LBT failure occurs for BWP when the LBT count value is greater than or equal to the first threshold value and there is currently ongoing random access. Therefore, only under the condition that the LBT count value corresponding to each beam in the preset beam or the preset beam set is larger than the first threshold value and the random access is currently carried out, the BWP is triggered to have the continuous LBT failure, so that the accuracy and the reliability of determining the continuous LBT failure of the BWP are improved, the rationality of switching the BWP can be further improved, and the waste of resources is avoided.

Referring to fig. 5, fig. 5 is a flowchart illustrating a method for determining a listen before talk failure according to an embodiment of the present disclosure, where the method is executed by a terminal device. As shown in fig. 5, the method may include, but is not limited to, the following steps:

in step 501, in the case that the LBT count value is greater than or equal to the first threshold value and there is no ongoing random access, it is determined that a continuous LBT failure occurs for BWP.

Optionally, the LBT detection result corresponding to BWP may also satisfy: and determining that the continuous LBT failure occurs in the BWP under the condition that the continuous LBT fails and no ongoing random access exists currently.

In this disclosure, before the LBT-FailureDetectionTimer times out, if the LBT counter count value is greater than or equal to the first threshold value, it may be considered that a persistent LBT failure has occurred, at this time, if there is no ongoing random access, it is determined that a persistent LBT failure has occurred in the BWP, and at this time, the LBT-FailureDetectionTimer timing may be stopped.

It should be noted that, when it is determined that the LBT detection result corresponding to the BWP is the continuous LBT failure, the terminal device may initiate random access on the current BWP to switch the transmission beam and attempt to recover the uplink beam. After the BWP is changed, the end device sets the LBT counter count value to 0 and stops LBT-FailureDetectionTimer.

In the present disclosure, there is no random access associated with the current serving cell, or no random access triggered by a persistent LBT failure, or no random access triggered by an LBT count value greater than or equal to a first threshold value, i.e. no random access currently ongoing.

Optionally, in this disclosure, the terminal device may further send, to the network device, the first indication information only when the preset function is in an enabled state, where the first indication information is used to indicate that the BWP has a persistent LBT failure, the preset function may be a function that controls the terminal device to send the first indication information, the terminal device may send the first indication information to the network device when the preset function is in the enabled state, and the terminal device does not send the first indication information to the network device when the preset function is in a disabled state.

Optionally, in the case that there is no available uplink resource, a Scheduling Request (SR) or Random Access Channel (RACH) flow may be triggered to request the uplink resource, and then the first indication information may be sent based on the requested uplink resource.

Optionally, the terminal device may further trigger random access in response to that there is no ongoing random access currently, and then clear the LBT count value.

In the present disclosure, the terminal device monitoring for persistent LBT failure is monitored with BWP as granularity. If a continuous LBT failure is monitored on a BWP of the current serving cell, it can be determined that the channel corresponding to the BWP is not in an idle state, so that the terminal device can switch to another BWP of the serving cell configured with a Physical Random Access Channel (PRACH) resource to initiate random access. Further, when the terminal device changes the BWP, it indicates that the BWP before the change is not available, and therefore, the LBT count value may be set to 0, facilitating the terminal device to start performing LBT detection of the BWP after the change.

Optionally, when all BWPs configured with PRACH resources in the current serving cell have a persistent LBT detection failure and the serving cell is a primary cell or a primary and secondary cell, the terminal device may notify, through the MAC, that a radio link of the RRC primary cell group or the secondary cell group has a failure.

In the disclosure, the terminal device determines that the continuous LBT failure occurs for BWP in case that the LBT count value is greater than or equal to the first threshold value and there is no ongoing random access currently. Therefore, the BWP is triggered to have the continuous LBT failure only under the condition that the LBT counting value corresponding to each beam in the preset beam or the preset beam set is larger than the first threshold value, so that the accuracy and the reliability of determining the BWP to have the continuous LBT failure are improved, the rationality of switching the BWP can be further improved, and the waste of resources is avoided.

Referring to fig. 6, fig. 6 is a flowchart illustrating a method for determining a listen before talk failure according to an embodiment of the present disclosure, where the method is executed by a terminal device. As shown in fig. 6, the method may include, but is not limited to, the following steps:

step 601, determining that continuous LBT failure occurs to BWP when an LBT count value corresponding to a preset beam is greater than a first threshold, where the preset beam may be any beam in a beam set configured by a network device.

In this disclosure, the terminal device may receive a beam set configured by the network device through a Physical Downlink Control Channel (PDCCH) or MAC CE or RRC signaling, and configured to trigger a persistent LBT failure of BWP.

Optionally, the network device may also configure different beam sets for PUSCH and PUCCH for triggering persistent LBT failure for BWP.

In this disclosure, after receiving the LBT failure instance, the MAC layer of the terminal device may add 1 to the LBT counter corresponding to the LBT failure instance if the detected beam corresponding to the LBT failure instance is any beam in the preset beam set, and then compare the LBT count value corresponding to each beam in the preset beam set with a first threshold, and when the LBT count value corresponding to any beam in the preset beam set is greater than the first threshold, it may be determined that the BWP has the continuous LBT failure.

Optionally, when the network device configures different beam sets for the PUSCH and the PUCCH respectively for triggering the persistent LBT failure of the BWP, the persistent LBT failure of the current BWP may be determined when the persistent LBT failure occurs on both the PUCCH and/or the PUSCH corresponding preset beam sets.

In this disclosure, the terminal device determines that the BWP has the continuous LBT failure when the LBT count value corresponding to the preset beam is greater than the first threshold. Therefore, the BWP is triggered to have the continuous LBT failure only when the LBT counting value corresponding to each beam in the preset beam or the preset beam set is larger than the first threshold value, so that the accuracy and the reliability of determining the BWP to have the continuous LBT failure are improved, the rationality of switching the BWP can be further improved, and the waste of resources is avoided.

Referring to fig. 7, fig. 7 is a flowchart illustrating a method for determining a listen before talk failure according to an embodiment of the present disclosure, where the method is executed by a terminal device. As shown in fig. 7, the method may include, but is not limited to, the following steps:

in step 701, it is determined that continuous LBT failure occurs for BWP when an LBT count value corresponding to a preset beam is greater than a first threshold, where the preset beam may correspond to a currently activated transmit beam set.

In this disclosure, the terminal device may receive the network device, activate a preset transmission beam set through PDCCH, MAC CE, or RRC signaling, and then may use a detection beam corresponding to the activated transmission beam set as the preset beam set.

Optionally, the preset beam may correspond to a transmission beam set configured by the network device, for example, a detection beam corresponding to the transmission beam set configured by the network device may be used as the preset beam set.

Optionally, the network device may also activate different transmit beam sets for the PUSCH and the PUCCH, so that the preset beam sets corresponding to the PUSCH and the PUCCH may be different.

In this disclosure, after receiving the LBT failure instance, the MAC layer of the terminal device may add 1 to the LBT counter corresponding to the LBT failure instance if the detected beam corresponding to the LBT failure instance is any beam in the preset beam set, compare the LBT count value corresponding to each beam in the preset beam set with a first threshold, and determine that the BWP has the continuous LBT failure when the LBT count value corresponding to any beam in the preset beam set is greater than the first threshold.

Optionally, when the network device activates different beam sets for PUSCH and PUCCH for triggering the persistent LBT failure of BWP, it may be determined that the persistent LBT failure occurs in the current BWP when the persistent LBT failure occurs on both the beam sets corresponding to PUCCH and/or PUSCH.

In the disclosure, the terminal device determines that the BWP has the continuous LBT failure when an LBT count value corresponding to a preset beam is greater than a first threshold value. Therefore, the BWP is triggered to have the continuous LBT failure only when the LBT counting value corresponding to each beam in the preset beam or the preset beam set is larger than the first threshold value, so that the accuracy and the reliability of determining the continuous LBT failure of the BWP are improved, the rationality of switching the BWP can be improved, and the waste of resources is avoided.

Please refer to fig. 8, which is a schematic structural diagram of a communication device 800 according to an embodiment of the present disclosure. The communication device 800 shown in fig. 8 may include a transceiver module 801 and a processing module 802. The transceiver module 801 may include a transmitting module and/or a receiving module, where the transmitting module is used to implement a transmitting function, the receiving module is used to implement a receiving function, and the transceiver module 801 may implement a transmitting function and/or a receiving function.

It is understood that the communication apparatus 800 may be a terminal device, an apparatus in the terminal device, or an apparatus capable of being used with the terminal device.

The communication apparatus 800 is on the terminal device side, wherein:

a processing module 802, configured to determine that sustained LBT failure occurs for a bandwidth part BWP when it is determined that a listen-before-talk LBT detection result corresponding to the BWP meets a preset condition.

Optionally, the preset condition is any one of the following conditions: :

persistent LBT fails and there is currently ongoing random access;

persistent LBT failure and no ongoing random access currently;

sustained LBT failure was detected for all beams in the preset beam set.

Optionally, the preset beam set is any one of:

the preset beam set configured by the network equipment;

the preset beam set corresponding to a currently activated transmit beam set.

Optionally, the processing module 802 is specifically configured to:

Optionally, the currently ongoing random access is any one of:

there is random access associated with the current serving cell;

there is random access triggered by persistent LBT failure;

Optionally, the random access currently not in progress is any of:

no random access associated with the current serving cell;

no random access triggered by a sustained LBT failure;

Optionally, the processing module 802 is specifically configured to:

triggering random access in response to no ongoing random access currently;

the LBT count value is cleared.

Optionally, the method further includes:

the transceiving module 801 is configured to send first indication information to a network device when a preset function is in an enabled state, where the first indication information is used to indicate that a persistent LBT failure occurs in the BWP.

Optionally, the transceiver module 802 is specifically configured to:

Referring to fig. 9, fig. 9 is a schematic structural diagram of another communication device 900 according to an embodiment of the present disclosure. The communication apparatus 900 may be a terminal device, or may be a chip, a chip system, a processor, or the like that supports the terminal device to implement the method described above. The apparatus may be configured to implement the method described in the method embodiment, and refer to the description in the method embodiment.

The communication device 900 may include one or more processors 901. The processor 901 may be a general purpose processor or a special purpose processor, etc. For example, a baseband processor or a central processor. The baseband processor may be configured to process communication protocols and communication data, and the central processor may be configured to control a communication device (e.g., a base station, a baseband chip, a terminal device chip, a DU or CU, etc.), execute a computer program, and process data of the computer program.

Optionally, the communication apparatus 900 may further include one or more memories 902, on which a computer program 904 may be stored, and the processor 901 executes the computer program 904, so that the communication apparatus 900 executes the method described in the above method embodiments. Optionally, the memory 902 may further store data therein. The communication device 900 and the memory 902 may be provided separately or may be integrated together.

Optionally, the communication device 900 may further include a transceiver 905 and an antenna 906. The transceiver 905 may be referred to as a transceiving unit, a transceiver, or a transceiving circuit, etc. for implementing a transceiving function. The transceiver 905 may include a receiver and a transmitter, and the receiver may be referred to as a receiver or a receiving circuit, etc. for implementing a receiving function; the transmitter may be referred to as a transmitter or a transmission circuit, etc. for implementing the transmission function.

Optionally, one or more interface circuits 907 may also be included in communications device 900. Interface circuit 907 is used to receive code instructions and transmit them to processor 901. The processor 901 executes the code instructions to cause the communication device 900 to perform the methods described in the above method embodiments.

The communication apparatus 900 is a terminal device: processor 901 may be configured to perform step 201 in fig. 2;

steps

301, 302, 303 in fig. 3; step 401 in FIG. 4; step 501 in FIG. 5; step 601 in fig. 6; step 701 in fig. 7, and so on.

In one implementation, the processor 901 may include a transceiver for implementing receiving and transmitting functions. The transceiver may be, for example, a transceiver circuit, or an interface circuit. The transmit and receive circuitry, interfaces or interface circuitry used to implement the receive and transmit functions may be separate or integrated. The transceiver circuit, the interface circuit or the interface circuit may be used for reading and writing code/data, or the transceiver circuit, the interface circuit or the interface circuit may be used for transmitting or transferring signals.

In one implementation, the processor 901 may store a computer program 903, and the computer program 903 runs on the processor 901, and may cause the communication apparatus 900 to execute the method described in the above method embodiment. The computer program 903 may be solidified in the processor 901, in which case the processor 901 may be implemented by hardware.

In one implementation, the communication device 900 may include circuitry that may implement the functionality of transmitting or receiving or communicating in the foregoing method embodiments. The processors and transceivers described in this disclosure may be implemented on Integrated Circuits (ICs), analog ICs, Radio Frequency Integrated Circuits (RFICs), mixed signal ICs, Application Specific Integrated Circuits (ASICs), Printed Circuit Boards (PCBs), electronic devices, and the like. The processor and transceiver may also be fabricated using various IC process technologies, such as Complementary Metal Oxide Semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (PMOS), Bipolar Junction Transistor (BJT), bipolar CMOS (bicmos), silicon germanium (SiGe), gallium arsenide (GaAs), and the like.

The communication apparatus in the above description of the embodiment may be a network device or a terminal device, but the scope of the communication apparatus described in the present disclosure is not limited thereto, and the structure of the communication apparatus may not be limited by fig. 9. The communication means may be a stand-alone device or may be part of a larger device. For example, the communication means may be:

(1) a stand-alone integrated circuit IC, or chip, or system-on-chip or subsystem;

(2) a set of one or more ICs, which optionally may also include storage means for storing data, computer programs;

(3) an ASIC, such as a Modem (Modem);

(4) a module that may be embedded within other devices;

(5) receivers, terminal devices, smart terminal devices, cellular phones, wireless devices, handsets, mobile units, in-vehicle devices, network devices, cloud devices, artificial intelligence devices, and the like;

(6) others, and so forth.

For the case that the communication device may be a chip or a system of chips, see the schematic structural diagram of the chip shown in fig. 10. The chip shown in fig. 10 includes a processor 1001 and an interface 1003. The number of the processors 1001 may be one or more, and the number of the interfaces 1003 may be more.

For the case that the chip is used for realizing the functions of the terminal device in the embodiments of the present disclosure:

processor 1001 may be configured to perform step 201 in fig. 2;

steps

Optionally, the chip further comprises a memory 1003, the memory 1003 being used to store necessary computer programs and data.

Those of skill in the art will further appreciate that the various illustrative logical blocks and steps (step) set forth in the embodiments of the disclosure may be implemented in electronic hardware, computer software, or combinations of both. Whether such functionality is implemented as hardware or software depends upon the particular application and design requirements of the overall system. 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 disclosed embodiments.

The present disclosure also provides a readable storage medium having stored thereon instructions which, when executed by a computer, implement the functionality of any of the above-described method embodiments.

The present disclosure also provides a computer program product which, when executed by a computer, implements the functionality of any of the above-described method embodiments.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs. The procedures or functions according to the embodiments of the present disclosure are wholly or partially generated when the computer program is loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer program can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer program can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disk (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.

It is understood that "a plurality" in this disclosure means two or more, and other words are analogous. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. The singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It is further to be understood that while operations are depicted in the drawings in a particular order, this is not to be understood as requiring that such operations be performed in the particular order shown or in serial order, or that all illustrated operations be performed, to achieve desirable results. In certain environments, multitasking and parallel processing may be advantageous.

Those of ordinary skill in the art will understand that: the various numbers of the first, second, etc. involved in this disclosure are merely for convenience of description and distinction, and are not intended to limit the scope of the embodiments of the disclosure, but also to indicate the order of precedence.

At least one of the present disclosure may also be described as one or more, and a plurality may be two, three, four or more, without limitation of the present disclosure. In the embodiment of the present disclosure, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "a", "B", "C", and "D", and the like, and the technical features described in "first", "second", "third", "a", "B", "C", and "D" are not in the order of priority or magnitude.

The correspondence shown in the tables in the present disclosure may be configured or predefined. The values of the information in each table are only examples, and may be configured as other values, and the disclosure is not limited thereto. When the correspondence between the information and each parameter is configured, it is not always necessary to configure all the correspondences indicated in each table. For example, in the table in the present disclosure, the correspondence relationship shown by some rows may not be configured. For another example, appropriate modification adjustments, such as splitting, merging, etc., can be made based on the above tables. The names of the parameters in the tables may be other names understandable by the communication device, and the values or the expression of the parameters may be other values or expressions understandable by the communication device. When the above tables are implemented, other data structures may be used, for example, arrays, queues, containers, stacks, linear tables, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or the like may be used.

Predefinition in this disclosure may be understood as defining, predefining, storing, pre-negotiating, pre-configuring, curing, or pre-firing.

Those of ordinary skill in the art will appreciate that the various illustrative 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 implementation. 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 present disclosure.

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

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

The above description is only for the specific embodiments of the present disclosure, but the scope of the present disclosure is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present disclosure, and all the changes or substitutions should be covered within the scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.

Claims

1. A method of determining a listen before talk failure, performed by a terminal device, the method comprising:

and under the condition that the detection result of the listen-before-talk LBT corresponding to the bandwidth part BWP meets the preset condition, determining that the continuous LBT of the BWP fails.

2. The method of claim 1, wherein the preset condition is any one of:

persistent LBT fails and there is currently ongoing random access;

persistent LBT failure and no ongoing random access currently;

sustained LBT failure was detected for all beams in the preset beam set.

3. The method of claim 2, wherein the preset set of beams is any one of:

the preset beam set configured by the network equipment;

the preset beam set corresponding to a currently activated transmit beam set.

4. The method of claim 2, further comprising:

5. The method of claim 2, wherein the current ongoing random access is any one of:

there is random access associated with the current serving cell;

there is random access triggered by persistent LBT failure;

6. The method of claim 2, wherein the current no ongoing random access is any one of:

no random access associated with the current serving cell;

no random access triggered by a sustained LBT failure;

7. The method of claim 2, further comprising:

responding to no random access currently in progress, and triggering the random access;

the LBT count value is cleared.

8. The method of any of claims 1-7, further comprising:

and sending first indication information to a network device under the condition that a preset function is in an enabled state, wherein the first indication information is used for indicating that the BWP has continuous LBT failure.

9. The method of claim 8, further comprising:

10. The method of claim 8, wherein the first indication information comprises at least one of: BWP identification, serving cell identification, and beam set identification.

11. A communications apparatus, the apparatus comprising:

12. The apparatus of claim 11, wherein the preset condition is any one of: :

the persistent LBT fails and there is currently an ongoing random access;

persistent LBT failure and no ongoing random access currently;

sustained LBT failure was detected for all beams in the preset beam set.

13. The apparatus of claim 12, wherein the preset set of beams is any one of:

the preset beam set configured by the network equipment;

the preset beam set corresponding to a currently activated transmit beam set.

14. The apparatus of claim 12, wherein the processing module is specifically configured to:

15. The apparatus of claim 12, wherein the current ongoing random access is any one of:

there is random access associated with the current serving cell;

there is random access triggered by persistent LBT failure;

16. The apparatus of claim 12, wherein the no current ongoing random access is any one of:

no random access associated with the current serving cell;

no random access triggered by a sustained LBT failure;

17. The apparatus of claim 12, wherein the processing module is specifically configured to:

triggering random access in response to no ongoing random access currently;

the LBT count value is cleared.

18. The apparatus of any of claims 11-17, further comprising:

19. The apparatus as claimed in claim 18, wherein said transceiver module is specifically configured to:

20. The apparatus of claim 18, wherein the first indication information comprises at least one of: BWP identification, serving cell identification, and beam set identification.

21. A communication apparatus, characterized in that the apparatus comprises a processor and a memory, in which a computer program is stored, the processor executing the computer program stored in the memory to cause the apparatus to perform the method according to any one of claims 1 to 10.

22. A computer-readable storage medium storing instructions that, when executed, cause the method of any of claims 1-10 to be implemented.