CN115836573A

CN115836573A - Method for reporting interception before transmission failure, terminal equipment and network equipment

Info

Publication number: CN115836573A
Application number: CN202080102887.9A
Authority: CN
Inventors: 付喆; 吴作敏
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-09-30
Filing date: 2020-09-30
Publication date: 2023-03-21
Also published as: WO2022067611A1

Abstract

The embodiment of the application relates to an antenna switching method for reporting interception before transmission failure, terminal equipment and communication equipment, wherein the method comprises the steps that the terminal equipment carries out interception before transmission LBT detection on at least one resource; the terminal equipment indicates LBT failure to a higher layer according to a first principle. The embodiment of the application can realize that how the UE definitely reports the LBT failure under the condition of resource conflict or overlapping.

Description

Method for reporting interception before transmission failure, terminal equipment and network equipment

Technical Field

The present application relates to the field of communications, and in particular, to a method, a terminal device, and a network device for reporting a transmission failure after interception.

Background

Generally, the operating Band (Band) of the New Radio Unlicensed (NR-U) is 5GHz Unlicensed spectrum and 6GHz Unlicensed spectrum. In order to ensure fair coexistence between systems over unlicensed spectrum, energy detection has been agreed as a basic coexistence mechanism. A general energy detection mechanism is an (LBT, listen Before Talk) mechanism, and the basic principle of the mechanism is as follows: a base station or a terminal (transmission end) needs to listen for a certain period of time according to a specification before transmitting data on an unlicensed spectrum. If the sensed result indicates that the channel is in an idle state, the transmitting end may transmit data to the receiving end. If the interception result indicates that the channel is in an occupied state, the transmission end needs to back off for a period of time according to the specification and then continues to intercept the channel until the channel interception result is in an idle state, and data can not be transmitted to the receiving end.

In the unlicensed band, the UE needs to listen to whether the channel is available or not by using LBT detection before transmitting, and if not, that is, LBT fails, the UE needs to wait until the next transmission opportunity to perform LBT detection again. If detecting the LBT failure, it needs to notify the MAC layer of the LBT failure (LBT failure) information.

In R16NR-U, the physical layer receives only one resource needing transmission from the higher layer, performs LBT detection on the resource and indicates the LBT failure of the higher layer when the LBT detection fails. However, in R17, in order to support the priority transmission of the high priority resource, the higher layer may indicate to the physical layer a plurality of resources that can be transmitted, and at this time, the physical layer may perform LBT detection on the plurality of resources. For the situation that the physical layer performs LBT detection on multiple resources, a reporting mode of LBT failure is not determined at present.

Disclosure of Invention

The embodiment of the application provides a LBT failure reporting method, terminal equipment and network equipment.

The embodiment of the application provides a method for reporting LBT failure, which comprises the following steps:

the terminal equipment performs LBT detection on at least one resource;

the terminal equipment indicates LBT failure to a higher layer according to a first principle.

The embodiment of the present application further provides a resource allocation or scheduling method, including:

the network equipment configures or schedules resources for the terminal equipment and configures or indicates priority information of the resources for the terminal equipment.

The embodiment of the present application further provides a terminal device, including:

a detection module to perform LBT detection on at least one resource;

and the indicating module is used for indicating the LBT failure to a high layer according to a first principle.

An embodiment of the present application further provides a network device, including:

the configuration module is used for configuring or scheduling resources for the terminal equipment and configuring or indicating the priority information of the resources for the terminal equipment.

The embodiment of the present application further provides a terminal device, including: the LBT failure reporting method comprises a processor and a memory, wherein the memory is used for storing computer programs, and the processor is used for calling and running the computer programs stored in the memory and executing the LBT failure reporting method.

An embodiment of the present application further provides a network device, including: the system comprises a processor and a memory, wherein 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 resource configuration or scheduling method.

The embodiment of the present application further provides a chip, including: and the processor is used for calling and running the computer program from the memory so that the equipment provided with the chip executes the LBT failure reporting method.

The embodiment of the present application further provides a chip, including: and the processor is used for calling and running the computer program from the memory so that the equipment provided with the chip executes the resource configuration or scheduling method.

The embodiment of the present application further provides a computer-readable storage medium, configured to store a computer program, where the computer program enables a computer to execute the method for reporting an LBT failure.

An embodiment of the present application further provides a computer-readable storage medium, configured to store a computer program, where the computer program enables a computer to execute the foregoing resource allocation or scheduling method.

The embodiment of the present application further provides a computer program product, which includes a computer program instruction, where the computer program instruction causes a computer to execute the method for reporting an LBT failure.

An embodiment of the present application further provides a computer program product, which includes computer program instructions, where the computer program instructions enable a computer to execute the resource allocation or scheduling method.

The embodiment of the present application further provides a computer program, where the computer program enables a computer to execute the method for reporting the LBT failure.

The embodiment of the present application further provides a computer program, where the computer program enables a computer to execute the resource allocation or scheduling method.

According to the method and the device, the LBT failure is indicated to the high layer through the UE according to the first resource, and how to report the LBT failure can be clearly determined under the condition of resource conflict or overlapping.

Drawings

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

Fig. 2 is a schematic flow chart of a method 200 for reporting LBT failure according to an embodiment of the present application.

Fig. 3 is a schematic flow chart of an LBT failure reporting method 300 according to an embodiment of the present application.

Fig. 4 is a schematic flow chart diagram of a resource configuration or scheduling method 400 according to an embodiment of the present application.

Fig. 5 is a schematic structural diagram of a terminal device 500 according to an embodiment of the present application.

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

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

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

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

Fig. 10 is a schematic structural diagram of a chip 1000 according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

It should be noted that the terms "first," "second," and the like in the description and claims of the embodiments of the present application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. The objects described in the "first" and "second" may be the same or different.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an Advanced Long Term Evolution (LTE-a) System, a New Radio (NR) System, an Evolution System of an NR System, an LTE (LTE-based Access to unlicensed spectrum, LTE-U) System on unlicensed spectrum, an NR (NR-based Access to unlicensed spectrum, a Universal Mobile telecommunications System (GSM) System, a UMTS (Universal Mobile telecommunications System), a Wireless Local Area network (UMTS) System, a Wireless Local Area Network (WLAN) 5 (Wireless Local Area network, or the like), and a Wireless Local Area network (WLAN-5) System.

Generally, the conventional Communication system supports a limited number of connections and is easy to implement, however, with the development of Communication technology, the mobile Communication system will support not only conventional Communication but also, for example, device-to-Device (D2D) Communication, machine-to-Machine (M2M) Communication, machine Type Communication (MTC), and Vehicle-to-Vehicle (V2V) Communication, and the embodiments of the present application can also be applied to these Communication systems.

Optionally, the communication system in the embodiment of the present application may be applied to a Carrier Aggregation (CA) scenario, may also be applied to a Dual Connectivity (DC) scenario, and may also be applied to an independent (SA) networking scenario.

The frequency spectrum of the application is not limited in the embodiment of the present application. For example, the embodiments of the present application may be applied to a licensed spectrum and may also be applied to an unlicensed spectrum.

The embodiments of the present application are described in conjunction with a network device and a terminal device, where: a terminal device may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, or a User Equipment, etc. The terminal device may be a Station (ST) in a WLAN, and may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, and a next generation communication system, for example, a terminal device in an NR Network or a terminal device in a future evolved Public Land Mobile Network (PLMN) Network, and the like.

By way of example and not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable equipment can also be called wearable intelligent equipment, is the general term of applying wearable technique to carry out intelligent design, develop the equipment that can dress to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. A wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.

The network device may be a device for communicating with a mobile device, and the network device may be an Access Point (AP) in a WLAN, a Base Station (BTS) in GSM or CDMA, a Base Station (NodeB, NB) in WCDMA, an evolved Node B (eNB, eNodeB) in LTE, a relay Station or an Access Point, or a vehicle-mounted device, a wearable device, a network device (gNB) in an NR network, or a network device in a PLMN network that is evolved in the future.

In this embodiment of the present application, a network device provides a service for a cell, and a terminal device communicates with the network device through a transmission resource (for example, a frequency domain resource or a spectrum resource) used by the cell, where the cell may be a cell corresponding to the network device (for example, a base station), and the cell may belong to a macro base station or a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells), and the like, and the small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-rate data transmission services.

Fig. 1 exemplarily shows one network device 110 and two terminal devices 120, and optionally, the wireless communication system 100 may include a plurality of network devices 110, and each network device 110 may include other numbers of terminal devices 120 within the coverage area, which is not limited in this embodiment of the present invention. The embodiment of the present application may be applied to one terminal device 120 and one network device 110, and may also be applied to one terminal device 120 and another terminal device 120.

Optionally, the wireless communication system 100 may further include other network entities such as a Mobility Management Entity (MME), an Access and Mobility Management Function (AMF), which is not limited in this embodiment.

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

It should be understood that "indication" mentioned in the embodiments of the present application may be a direct indication, an indirect indication, or an indication of an association relationship. For example, a indicates B, which may mean that a directly indicates B, e.g., B may be obtained by a; it may also mean that a indicates B indirectly, for example, a indicates C, and B may be obtained by C; it can also mean that there is an association between a and B.

In the description of the embodiments of the present application, the term "correspond" may indicate that there is a direct correspondence or an indirect correspondence between the two, may also indicate that there is an association between the two, and may also indicate and is indicated, configure and is configured, and the like.

For the convenience of understanding of the technical solutions of the embodiments of the present application, the following related technologies of the embodiments of the present application are described below, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as alternatives, and all of them belong to the protection scope of the embodiments of the present application.

The 3GPP RAN working group has agreed to the establishment of an NR unlicensed mode of operation, which aims to enable NR to operate in unlicensed bands, and in general, the operating Band (Band) of NR-U is 5GHz unlicensed spectrum and 6GHz unlicensed spectrum. On unlicensed spectrum, the design of NR-U should guarantee fairness with other systems already operating on these unlicensed spectrum, such as WiFi and the like. The principle of fairness is that the impact of NR-U on systems already deployed on unlicensed spectrum cannot exceed the impact between these systems.

In order to ensure fair coexistence between systems over unlicensed spectrum, energy detection has been agreed as a basic coexistence mechanism. The general energy detection mechanism is the LBT mechanism, and the basic principle of the mechanism is: a base station or a terminal (transmission end) needs to listen for a certain period of time according to a specification before transmitting data on an unlicensed spectrum. If the sensed result indicates that the channel is in an idle state, the transmitting end may transmit data to the receiving end. If the channel is in the occupied state, the transmission end needs to back off for a period of time according to the regulation and then continues to listen to the channel until the channel listening result is in the idle state, and then the data can not be transmitted to the receiving end.

In the unlicensed band, before a UE transmits an uplink Scheduling Request (SR), a Physical Random Access Channel (PRACH), or an uplink Physical shared Channel (PUSCH), LBT is required to monitor whether a Channel is available. If it is not available, i.e. the LBT detection fails, the UE needs to wait until the next transmission opportunity to perform the LBT detection again. If detecting that the LBT detection fails, it needs to inform the MAC layer of the LBT failure information.

In R16, it is assumed that only one resource to be transmitted is indicated from the MAC layer to the physical layer. Therefore, for the R16NR-U, a resource collision scenario is not discussed in particular, in the R16NR-U, the physical layer receives only one resource to be transmitted from a higher layer, performs LBT detection on the resource, and indicates the higher layer LBT failure when the LBT detection fails. However, in R17, in order to support the priority transmission of the high-priority resource (e.g., the priority transmission of the resource corresponding to the Ultra Reliable and Low Latency Communication (URLLC), the higher layer may indicate to the physical layer a plurality of resources that can be transmitted, such as a plurality of Medium Access Control (MAC) Protocol Data Units (PDUs), MAC PDU + SR, where the physical layer may perform LBT detection on the plurality of resources. Then there may be cases where some of the LBT tests succeed and some of the LBT tests fail. For how to handle this complex situation, for example, how to report LBT failure, the embodiments of the present application propose a solution to this problem.

An embodiment of the present application provides a method for reporting an LBT failure, and fig. 2 is a schematic flowchart of a method 200 for reporting an LBT failure according to an embodiment of the present application, where the method may be optionally applied to the system shown in fig. 1, for example, to the terminal device shown in fig. 1, but is not limited thereto. The method includes at least part of the following.

S210: the terminal equipment detects the transmission after interception (LBT) on at least one resource;

s220: the terminal equipment indicates LBT failure to a higher layer according to a first principle.

Optionally, the resource includes at least one of a Dynamic Grant (DG), a Configuration Grant (CG), a Physical Uplink Control Channel (PUCCH), and a PRACH.

Optionally, the resource includes at least one of a Physical Uplink Shared Channel (PUSCH), a PUCCH, and a PRACH resource.

Optionally, the resource may include a resource configured or scheduled by the network device. For example, the CG configured by the network device for the terminal, or the DG scheduled by the network device for the terminal.

While configuring or scheduling resources, the network device may configure or indicate priority information for the resources. For example, the network device may configure priority information of a CG configured for the terminal, simultaneously with the CG. As another example, the network device may indicate the priority information of the DG scheduled for the terminal at the same time as the DG. For another example, the network device may configure the priority information of the PUCCH/PRACH while configuring the PUCCH/PRACH for the terminal.

Optionally, the terminal device receives a configuration or an indication of the resource, where the configuration or the indication includes priority information of the resource.

Optionally, the priority information includes a high priority or a low priority.

Alternatively, the priority information may be resource priority information based on a physical layer resource priority, and/or resource priority information based on a Logical Channel (LCH) priority.

Alternatively, the priority information may be resource priority information used when performing resource priority selection based on a physical layer, and/or resource priority information used when performing resource priority selection based on a MAC layer.

Optionally, the first principle comprises at least one of:

(1) If the LBT detection on all the resources in the at least one resource is successful, the LBT failure is not reported to a high layer;

(2) If LBT detection fails on all resources in the at least one resource, reporting LBT failure to a high layer;

(3) If the LBT detection is successful on at least part of the resources in the at least one resource, the LBT failure is not reported to a high layer;

(4) If LBT detection fails on at least part of the at least one resource, the LBT failure is reported to a high layer.

For the item (2) of the first principle, optionally, the count value (counter) of the LBT failure reported by the terminal includes one of the following: 1, the number of resources failing LBT detection, and the number of resources failing LBT detection with high priority. Optionally, the count value of the LBT failure reported by the terminal may further include the number of low-priority resources for which the LBT detection fails.

For the item (2) of the first principle, optionally, the reporting LBT failure is reporting for at least one of a Bandwidth Part (BWP), a serving cell (serving cell), and a resource. Optionally, reporting that the LBT fails carries at least one of the following: an identity of the BWP, an identity of the serving cell, and an identity of the resource.

With respect to item (3) of the first principle, optionally, the at least part of the resources comprise high-priority resources.

Or, as to item (3) of the first principle, optionally, the at least part of the resources does not include a high-priority resource, and data (e.g., a MAC PDU, e.g., an SR) corresponding to the high-priority resource may be transmitted through other resources in which LBT detection is successful.

With respect to item (4) of the first principle, optionally, the at least part of the resources comprise high-priority resources.

Or, as to item (4) of the first principle, optionally, the at least part of the resources includes a high-priority resource, and data (e.g., MAC PDU) corresponding to the high-priority resource cannot be transmitted through other resources successfully detected by LBT.

For the item (4) of the first principle, optionally, the count value of the LBT failure reported by the terminal includes one of: 1, the number of resources failing LBT detection, and the number of resources failing LBT detection with high priority. Optionally, the count value of the LBT failure reported by the terminal may further include the number of low-priority resources for which the LBT detection fails.

As for item (4) of the first principle, optionally, the reporting of the LBT failure is performed for at least one of BWP, serving cell, and resource. Optionally, reporting that the LBT fails carries at least one of the following: an identity of the BWP, an identity of the serving cell, and an identity of the resource.

Optionally, in a case of resource collision or overlap, the terminal device performs LBT detection on at least one resource, and indicates LBT failure to a higher layer according to the first principle.

Or, in case of resource conflict or overlap and the first condition is satisfied, performing LBT detection on at least one resource and indicating LBT failure to a higher layer according to the first principle.

Specifically, the physical layer of the terminal device may indicate the LBT failure to a higher layer (e.g., MAC layer).

After the high layer of the UE receives the LBT failure indication, it may determine whether the LBT failure is recovered according to the existing rule.

Optionally, the first condition includes at least one of:

the physical layer receives a plurality of available/to-be-transmitted information from a high layer;

the physical layer determines that a plurality of resource conflicts or overlaps exist;

the priority of multiple conflicted or overlapping resources is different;

the priority of a plurality of conflicted or overlapped resources is different, and the physical layer receives a plurality of available/to-be-transmitted information from the higher layer;

the priority of multiple conflicted or overlapping resources is the same;

the priority of multiple conflicted or overlapping resources is the same and the physical layer receives multiple information available/to be transmitted from higher layers.

Optionally, the information available/to be transmitted includes at least one of:

MAC PDU；

SR；

an Acknowledgement (ACK)/Negative Acknowledgement (NACK) generation indication;

an ACK/NACK indication.

Optionally, the terminal device may detect the resource according to an LBT detection manner indicated by the network. For example, the terminal device receives the LBT detection mode indication information.

Optionally, the LBT detection mode indication information includes at least one of the following:

performing LBT detection for any one resource;

performing LBT detection for at least one particular resource;

performing LBT detection for a certain number of resources;

performing LBT detection for a particular resource;

performing LBT detection for all resources;

and performing LBT detection according to the LBT detection mode indicated by the network.

Alternatively, the specific resource may refer to a specific type of resource; such as high priority resources and/or low priority resources.

For example, performing LBT detection according to the LBT detection method indicated by the network, the terminal may detect the corresponding resource according to the indication, and indicate an LBT failure to a higher layer according to the first principle after the detection.

In the following, specific embodiments are described, where resources are repeated or overlapped, if the UE performs LBT detection on at least one resource, the UE indicates LBT failure to a specific implementation manner of a higher layer according to a first principle.

Fig. 3 is a schematic flow chart of an LBT failure reporting method 300 according to an embodiment of the present application. As shown in fig. 3, the network equipment configures resources or schedules resource transmission for the UE. Wherein, the resource can be at least one of DG, CG, PUCCH and PRACH. The network device may configure or indicate the priority information of the resource at the same time as configuring or scheduling the resource. For example, the priority information may be a high priority, or a low priority. Further, the network device may indicate the LBT detection mode to the UE. The LBT detection mode indication information is introduced in the above embodiments, and is not described herein again.

The UE receives the resource scheduled or configured by the network, optionally, the UE performs LBT detection according to the LBT detection method indicated by the network device, and transmits the LBT detection. And, the UE indicates the LBT failure to the higher layer according to the first principle. The first principle has been described in the above embodiments, and will not be described herein.

After a higher layer (such as a MAC layer) of the UE receives the LBT failure indication, it determines whether the LBT failure is recovered according to the existing rule.

Therefore, the embodiment of the application defines how the UE reports the UE behavior of the LBT failure under the condition of resource conflict, and ensures the transmission quality of the channel while meeting the URLLC service transmission.

The present application embodiment further provides a resource allocation or scheduling method, and fig. 4 is a schematic flow chart of a resource allocation or scheduling method 400 according to an embodiment of the present application, which may be optionally applied to the system shown in fig. 1, such as the network device shown in fig. 1, but is not limited thereto. The method includes at least part of the following. The method comprises the following steps:

s410: the network device configures or schedules resources for the terminal device, and configures or indicates priority information of the resources to the terminal device.

Optionally, the method further includes: and sending LBT detection mode indication information.

performing LBT detection for any one resource;

performing LBT detection for at least one specific resource;

performing LBT detection for a certain number of resources;

performing LBT detection for a particular resource;

performing LBT detection for all resources;

Optionally, the resource includes at least one of DG, CG, PUCCH, and PRACH.

Optionally, the resource includes at least one of PUSCH, PUCCH, and PRACH resource.

An embodiment of the present application further provides a terminal device, and fig. 5 is a schematic structural diagram of a terminal device 500 according to the embodiment of the present application, including:

a detection module 510, configured to perform listen before transmit LBT detection on at least one resource;

an indicating module 520, configured to indicate the LBT failure to the higher layer according to the first principle.

Optionally, the first principle comprises at least one of:

if the LBT detection is successful on all resources in at least one resource, the LBT failure is not reported to a high layer;

if LBT detection fails on all resources in at least one resource, reporting LBT failure to a high layer;

if the LBT detection is successful on at least part of the resources in the at least one resource, the LBT failure is not reported to a high layer;

and if the LBT detection fails on at least part of the at least one resource, reporting the LBT failure to a high layer.

Optionally, if the LBT detection is successful on at least part of the at least one resource, the LBT failure is not reported to the higher layer, where the at least part of the resource includes a high-priority resource.

Optionally, if the LBT detection is successful on at least part of the at least one resource, the first principle content of LBT failure is not reported to the higher layer, and at least part of the resources does not include the resource with high priority, and the data corresponding to the resource with high priority may be sent through other resources for which the LBT detection is successful.

Optionally, if the LBT detection fails on at least a part of the at least one resource, reporting to the higher layer that the LBT failed in the first principle content, where the at least part of the resource includes a resource with a high priority.

Optionally, if the LBT detection fails on at least a part of the at least one resource, reporting to the higher layer that the LBT failed, where the at least part of the resource includes a high-priority resource, and the data corresponding to the high-priority resource cannot be sent through other resources where the LBT detection succeeds.

Optionally, the reported LBT failure count value includes one of the following: 1, the number of resources failing LBT detection, and the number of resources failing LBT detection with high priority.

Optionally, the first principle further includes: reporting LBT failure is reported aiming at least one of bandwidth part BWP, service cell and resource.

Optionally, the first principle further includes: when reporting LBT failure, the LBT carries at least one of the following: identification of BWP, identification of serving cell, identification of resource.

Optionally, the indicating module 520 is configured to indicate, according to a first principle, an LBT failure to a higher layer in case of resource collision or overlap.

Optionally, the indicating module 520 is configured to indicate the LBT failure to the higher layer according to the first principle if the resources conflict or overlap and the first condition is satisfied.

Optionally, the first condition includes at least one of:

the priority of multiple conflicted or overlapping resources is different;

the priority of multiple conflicted or overlapping resources is the same;

multiple conflicted or overlapping resources are of the same priority and the physical layer receives multiple information available/to be transmitted from higher layers.

media Access Control (MAC) Protocol Data Unit (PDU);

an uplink scheduling request SR;

an acknowledgement ACK/negative acknowledgement NACK generation indication;

an ACK/NACK indication.

Optionally, the indicating module 520 is configured to indicate, by using a physical layer of the terminal device, the LBT failure to a higher layer according to a first principle.

Optionally, the higher layer includes a MAC layer.

Optionally, the resource includes a resource configured or scheduled by the network device.

Optionally, as shown in fig. 6, the terminal device further includes:

a first receiving module 630, configured to receive a configuration or indication of a resource, where the configuration or indication includes priority information of the resource.

Optionally, as shown in fig. 6, the terminal device further includes:

a second receiving module 640, configured to receive LBT detection mode indication information.

performing LBT detection for any one resource;

performing LBT detection for at least one specific resource;

performing LBT detection for a certain number of resources;

performing LBT detection for a particular resource;

performing LBT detection for all resources;

Optionally, the resources include at least one of:

dynamically authorizing the DG;

configuring an authorization CG;

a Physical Uplink Control Channel (PUCCH);

PRACH。

it should be understood that the above and other operations and/or functions of the modules in the terminal device according to the embodiment of the present application are respectively for implementing the corresponding flows of the terminal device in the method 200 of fig. 2, and are not described herein again for brevity.

An embodiment of the present application further provides a network device, and fig. 7 is a schematic structural diagram of a network device 700 according to an embodiment of the present application, including:

the configuration module 710 is configured to configure or schedule resources for the terminal device, and configure or indicate priority information of the resources to the terminal device.

Optionally, as shown in fig. 8, the network device further includes:

a sending module 820, configured to send LBT detection mode indication information.

performing LBT detection for any one resource;

performing LBT detection for at least one specific resource;

performing LBT detection for a certain number of resources;

performing LBT detection for a particular resource;

performing LBT detection for all resources;

Optionally, the resource includes at least one of DG, CG, PUCCH, and PRACH.

It should be understood that the above and other operations and/or functions of the modules in the network device according to the embodiment of the present application are respectively for implementing the corresponding flows of the network device in the method 400 of fig. 4, and are not described herein again for brevity.

Fig. 9 is a schematic block diagram of a communication device 900 according to an embodiment of the present application. The communication device 900 shown in fig. 9 includes a processor 910, and the processor 910 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 9, the communication device 900 may also include a memory 920. From the memory 920, the processor 910 can call and run a computer program to implement the method in the embodiment of the present application.

The memory 920 may be a separate device from the processor 910, or may be integrated in the processor 910.

Optionally, as shown in fig. 9, the communication device 900 may further include a transceiver 930, and the processor 910 may control the transceiver 930 to communicate with other devices, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

The transceiver 930 may include a transmitter and a receiver, among others. The transceiver 930 may further include one or more antennas.

Optionally, the communication device 900 may be a terminal device in this embodiment, and the communication device 900 may implement a corresponding process implemented by the terminal device in each method in this embodiment, which is not described herein again for brevity.

Optionally, the communication device 900 may be a network device in this embodiment, and the communication device 900 may implement a corresponding process implemented by the network device in each method in this embodiment, which is not described herein again for brevity.

Fig. 10 is a schematic structural diagram of a chip 1000 according to an embodiment of the present application. The chip 1000 shown in fig. 10 includes a processor 1010, and the processor 1010 may call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 10, the chip 1000 may further include a memory 1020. From the memory 1020, the processor 1010 may call and run a computer program to implement the method in the embodiment of the present application.

The memory 1020 may be a separate device from the processor 1010 or may be integrated into the processor 1010.

Optionally, the chip 1000 may further include an input interface 1030. The processor 1010 may control the input interface 1030 to communicate with other devices or chips, and specifically may obtain information or data transmitted by the other devices or chips.

Optionally, the chip 1000 may further include an output interface 1040. The processor 1010 may control the output interface 1040 to communicate with other devices or chips, and may particularly output information or data to the other devices or chips.

Optionally, the chip may be applied to the terminal device in the embodiment of the present application, and the chip may implement a corresponding process implemented by the terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement a corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

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

The aforementioned processors may be general purpose processors, digital Signal Processors (DSPs), field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general purpose processor mentioned above may be a microprocessor or any conventional processor etc.

The above-mentioned memories may be either volatile or nonvolatile memories, or may include both volatile and nonvolatile memories. The non-volatile 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. Volatile memory can be Random Access Memory (RAM).

It should be understood that the above memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), synchronous Link DRAM (SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

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 instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, 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 includes one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), among others.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

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.

The above description is only for the specific embodiments of the present application, but the scope of the present application 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 application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method for reporting transmission failure after interception comprises the following steps:

the terminal equipment carries out the detection of the LBT after the interception on at least one resource;

and the terminal equipment indicates the LBT failure to a high layer according to a first principle.
The method of claim 1, wherein the first principle comprises at least one of:

if the LBT detection on all the resources in the at least one resource is successful, not reporting the LBT failure to a high layer;

if LBT detection fails on all resources in the at least one resource, reporting LBT failure to a high layer;

if the LBT detection is successful on at least part of the resources in the at least one resource, not reporting the LBT failure to a high layer;

if LBT detection fails on at least part of the at least one resource, reporting LBT failure to a high layer.
The method of claim 2, wherein the first principle content of not reporting LBT failure to a higher layer if LBT detection is successful on at least some of the at least one resource comprises a high priority resource.
The method according to claim 2, wherein, in the first principle that if LBT detection is successful on at least some of the at least one resource, LBT failure is not reported to a higher layer, the at least some resources do not include high-priority resources, and data corresponding to the high-priority resources may be sent through other resources for which LBT detection is successful.
The method of claim 2, wherein the first principle content of LBT failure is reported to a higher layer if LBT detection fails on at least some of the at least one resource, where the at least some resource includes a high priority resource.
The method according to claim 2, wherein if LBT detection fails on at least some of the at least one resource, reporting to a higher layer the first principle content of LBT failure, where the at least some resources include a high-priority resource, and data corresponding to the high-priority resource cannot be transmitted through other resources for which LBT detection succeeds.
The method of claim 2, 5 or 6, wherein the reported count of LBT failures comprises one of: 1, the number of resources failing LBT detection, and the number of resources failing LBT detection with high priority.
The method of claim 2, 5 or 6, wherein the first principle further comprises: the reporting LBT failure is reported aiming at least one of bandwidth part BWP, service cell and resource.
The method of claim 8, wherein the first principle further comprises: when reporting LBT failure, the LBT carries at least one of the following: an identity of the BWP, an identity of the serving cell, an identity of the resource.
The method according to any one of claims 1 to 9, wherein the terminal device indicates LBT failure to a higher layer according to a first principle, comprising:

and under the condition of resource conflict or overlapping, the terminal equipment indicates LBT failure to a higher layer according to a first principle.
The method according to any of claims 1 to 9, wherein the terminal device indicates LBT failure to higher layers according to a first principle, comprising:

and under the condition that the resources conflict or overlap and a first condition is met, the terminal equipment indicates LBT failure to a higher layer according to a first principle.
The method of claim 11, wherein the first condition comprises at least one of:

the physical layer receives a plurality of available/to-be-transmitted information from a high layer;

the physical layer determines that a plurality of resource conflicts or overlaps exist;

the priority of multiple conflicted or overlapping resources is different;

the priority of multiple conflicted or overlapped resources is different, and the physical layer receives multiple available/to-be-transmitted information from the higher layer;

the priority of multiple conflicted or overlapping resources is the same;

multiple conflicted or overlapping resources are of the same priority and the physical layer receives multiple information available/to be transmitted from higher layers.
The method of claim 12, wherein the available/to-be-transmitted information comprises at least one of:

media Access Control (MAC) Protocol Data Unit (PDU);

an uplink scheduling request SR;

an acknowledgement ACK/negative acknowledgement NACK generation indication;

an ACK/NACK indication.
The method according to any of claims 1 to 13, wherein the terminal device indicates LBT failure to higher layers according to a first principle, comprising:

and the physical layer of the terminal equipment indicates the LBT failure to a high layer according to a first principle.
The method according to any of claims 1 to 14, wherein the higher layer comprises a MAC layer.
The method of any of claims 1 to 15, the resources comprising network device configured or scheduled resources.
The method of claim 16, further comprising:

and the terminal equipment receives the configuration or the indication of the resources, wherein the configuration or the indication comprises the priority information of the resources.
The method of claim 17, wherein the priority information comprises a high priority or a low priority.
The method of any of claims 1 to 18, further comprising: and the terminal equipment receives LBT detection mode indication information.
The method of claim 19, wherein the LBT detection mode indication information comprises at least one of:

performing LBT detection for any one resource;

performing LBT detection for at least one specific resource;

performing LBT detection for a certain number of resources;

performing LBT detection for a particular resource;

performing LBT detection for all resources;

and performing LBT detection according to the LBT detection mode indicated by the network.
The method of any of claims 1 to 20, wherein the resources comprise at least one of:

dynamically authorizing the DG;

configuring an authorization CG;

a Physical Uplink Control Channel (PUCCH);

physical random access channel PRACH.
A method of resource configuration or scheduling, comprising:

the network equipment configures or schedules resources for the terminal equipment and configures or indicates priority information of the resources for the terminal equipment.
The method of claim 22, wherein the priority information comprises a high priority or a low priority.
The method of claim 22 or 23, further comprising: and sending LBT detection mode indication information.
The method of claim 24, wherein the LBT detection mode indication information comprises at least one of:

performing LBT detection for any one resource;

performing LBT detection for at least one specific resource;

performing LBT detection for a certain number of resources;

performing LBT detection for a particular resource;

performing LBT detection for all resources;

and performing LBT detection according to the LBT detection mode indicated by the network.
The method of any of claims 22 to 25, wherein the resources comprise at least one of DG, CG, PUCCH and PRACH.
A terminal device, comprising:

a detection module configured to perform listen before transmit LBT detection on at least one resource;

and the indicating module is used for indicating the LBT failure to a high layer according to a first principle.
The terminal device of claim 27, wherein the first principle comprises at least one of:

if the LBT detection on all the resources in the at least one resource is successful, not reporting the LBT failure to a high layer;

if LBT detection fails on all resources in the at least one resource, reporting LBT failure to a high layer;

if the LBT detection is successful on at least part of the resources in the at least one resource, not reporting the LBT failure to a high layer;

if LBT detection fails on at least part of the at least one resource, reporting LBT failure to a high layer.
The terminal device of claim 28, wherein, if the LBT detection is successful on at least some of the at least one resource, the at least some of the resources include a high-priority resource, and the first principle content of LBT failure is not reported to a higher layer.
The terminal device of claim 28, wherein, in the first principle that if LBT detection is successful on at least some of the at least one resource, LBT failure is not reported to a higher layer, the at least some resources do not include a high-priority resource, and data corresponding to the high-priority resource may be sent through other resources for which LBT detection is successful.
The terminal device of claim 28, wherein, if LBT detection fails on at least some of the at least one resource, the at least some resource includes a high-priority resource, and the first principle content of LBT failure is reported to a higher layer.
The terminal device of claim 28, wherein, if LBT detection fails on at least some of the at least one resource, the first principle content of LBT failure is reported to a higher layer, where the at least some resources include a high-priority resource, and data corresponding to the high-priority resource cannot be sent through other resources for which LBT detection succeeds.
The terminal device of claim 28, 31 or 32, wherein the reported count value of LBT failures includes one of: 1, the number of resources failing LBT detection, and the number of resources failing LBT detection with high priority.
A terminal device according to claim 28, 31 or 32, wherein the first principle further comprises: the reporting LBT failure is reported for at least one of a bandwidth part BWP, a serving cell, and a resource.
The terminal device of claim 34, wherein the first principle further comprises: when reporting LBT failure, the LBT carries at least one of the following: an identity of the BWP, an identity of the serving cell, an identity of the resource.
The terminal device according to any of claims 27 to 35, wherein the indicating module is configured to indicate LBT failure to a higher layer according to a first principle in case of resource collision or overlap.
The terminal device according to any of claims 27 to 35, wherein the indicating module is configured to indicate LBT failure to a higher layer according to a first principle in case of resource collision or overlap and a first condition is met.
The terminal device of claim 37, wherein the first condition comprises at least one of:

the physical layer receives a plurality of available/to-be-transmitted information from a high layer;

the physical layer determines that a plurality of resource conflicts or overlaps exist;

the priority of multiple conflicted or overlapping resources is different;

the priority of a plurality of conflicted or overlapped resources is different, and the physical layer receives a plurality of available/to-be-transmitted information from the higher layer;

the priority of multiple conflicted or overlapping resources is the same;

the priority of multiple conflicted or overlapping resources is the same and the physical layer receives multiple information available/to be transmitted from higher layers.
The terminal device of claim 38, wherein the available/to-be-transmitted information comprises at least one of:

media Access Control (MAC) Protocol Data Unit (PDU);

an uplink scheduling request SR;

an acknowledgement ACK/negative acknowledgement NACK generation indication;

an ACK/NACK indication.
The terminal device according to any of claims 27 to 39, wherein the indicating module is configured to indicate, by using a physical layer of the terminal device, an LBT failure to a higher layer according to a first principle.
A terminal device according to any one of claims 27 to 40, wherein the higher layer comprises a MAC layer.
A terminal device according to any of claims 27 to 41, wherein the resources comprise network device configured or scheduled resources.
The terminal device of claim 42, further comprising:

a first receiving module, configured to receive a configuration or indication of the resource, where the configuration or indication includes priority information of the resource.
The terminal device of claim 43, wherein the priority information comprises a high priority or a low priority.
The terminal device of any of claims 27 to 44, further comprising:

and the second receiving module is used for receiving the LBT detection mode indication information.
The terminal device of claim 45, wherein the LBT detection mode indication information comprises at least one of:

performing LBT detection for any one resource;

performing LBT detection for at least one specific resource;

performing LBT detection for a certain number of resources;

performing LBT detection for a particular resource;

performing LBT detection for all resources;

and performing LBT detection according to the LBT detection mode indicated by the network.
The terminal device of any of claims 27 to 46, wherein the resources comprise at least one of DG, CG, PUCCH and PRACH.
A network device, comprising:

the configuration module is used for configuring or scheduling resources for the terminal equipment and configuring or indicating the priority information of the resources for the terminal equipment.
The network device of claim 48, wherein the priority information comprises a high priority or a low priority.
The network device of claim 48 or 49, further comprising:

and the sending module is used for sending the LBT detection mode indication information.
The network device of claim 50, wherein the LBT detection mode indication information comprises at least one of:

performing LBT detection for any one resource;

performing LBT detection for at least one specific resource;

performing LBT detection for a certain number of resources;

performing LBT detection for a particular resource;

performing LBT detection for all resources;

and performing LBT detection according to the LBT detection mode indicated by the network.
The network device of any of claims 48 to 51, wherein the resources comprise at least one of DG, CG, PUCCH and PRACH.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and execute the computer program stored in the memory, performing the method of any of claims 1 to 21.
A network device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 22 to 26.
A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1 to 21.
A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 22 to 26.
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.
A computer-readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 22 to 26.
A computer program product comprising computer program instructions to cause a computer to perform the method of any one of claims 1 to 21.
A computer program product comprising computer program instructions to cause a computer to perform the method of any of claims 22 to 26.
A computer program for causing a computer to perform the method of any one of claims 1 to 21.
A computer program for causing a computer to perform the method of any one of claims 22 to 26.