Method and apparatus for indicating LBT failure

Abstract

A method and apparatus for indicating LBT failure. The method is applied to a terminal device, and the method includes: when the lower layer or the upper layer determines that the first condition and / or the second condition are satisfied, the lower layer notifies or indicates LBT failure to the upper layer, or the lower layer starts to notify or indicate LBT failure to the upper layer; and / or, when the lower layer or the upper layer determines that the first condition is not satisfied and / or the third condition is satisfied, the lower layer does not notify or indicate LBT failure to the upper layer, or the lower layer stops notifying or indicating LBT failure to the upper layer.

Description

Technical Field

[0001] The present invention relates to the field of communications. Background Art

[0002] In order to provide 3GPP services on unlicensed bands, the following mechanisms are introduced: Listen Before Talk (LBT) and Discovery RS Measurement Timing Configuration (DMTC). Among them, the lower layer executes the LBT process. According to the LBT result, if the channel is determined to be occupied, no transmission is performed. When the lower layer executes the LBT process before transmission and this transmission is not performed, that is, when the uplink transmission is blocked due to LBT failure, the lower layer indicates the LBT failure to the upper layer.

[0003] It should be noted that the above introduction of the technical background is only for convenience, to clearly and completely explain the technical solution of the present invention, and to facilitate the understanding of those skilled in the art. It cannot be considered that the above technical solutions are well known to those skilled in the art just because these solutions are described in the background art part of the present invention. Summary of the Invention

[0004] In a New Radio - Unlicensed (NR - U) system on unlicensed bands, a continuous LBT failure detection and recovery mechanism for uplink transmission is introduced.

[0005] The Radio Resource Control (RRC) layer can configure the recovery process for continuous LBT failure for upper layers, such as MAC entities of the MAC layer. The detection of continuous LBT failure is performed on each uplink BWP (Bandwidth Part). For this purpose, a counter and a timer are introduced. When an uplink LBT failure occurs, the timer is started or restarted. Whenever the upper layer (such as the MAC layer) receives an uplink LBT failure indication from the lower layer (such as the physical layer), the counter is incremented by 1. When the count value of this counter exceeds a preset value, a continuous LBT failure is triggered. Additionally, when the timer times out, the counter is reset. This process can be regarded as a continuous (uplink) LBT failure detection process or a part or a step of the continuous (uplink) LBT failure detection process.

[0006] The inventors found that according to the existing mechanism, in order to implement the continuous LBT failure detection mechanism for the uplink transmission of the upper layer, the lower layer needs to provide an indication to the MAC layer, that is, when any uplink transmission is blocked due to LBT failure or there is a channel access failure, the lower layer notifies or indicates it to the upper layer.

[0007] However, in the lower layer, the uplink transmission including data, control information, and reference signals may occur at any time. If the lower layer notifies or indicates to the upper layer every time the uplink transmission is blocked due to LBT failure, it will greatly increase the inter-layer interaction between the lower layer and the upper layer and increase the power consumption of the terminal device.

[0008] To solve one or more of the above problems, embodiments of the present application provide a method and apparatus for indicating LBT failure.

[0009] According to the first aspect of the embodiments of the present application, there is provided an apparatus for indicating LBT failure. The apparatus is applied to a terminal device and includes: a first indication unit, when the uplink transmission is blocked due to LBT failure, the lower layer notifies or indicates LBT failure to the upper layer, or the lower layer starts to notify or indicate LBT failure when the lower layer or the upper layer determines that the first condition and / or the second condition is satisfied; and / or, a second indication unit, when the uplink transmission is blocked due to LBT failure, the lower layer does not notify or indicate LBT failure to the upper layer, or the lower layer stops notifying or indicating LBT failure when the lower layer or the upper layer determines that the first condition is not satisfied and / or the third condition is satisfied.

[0010] According to the second aspect of the embodiments of the present application, there is provided an apparatus for indicating LBT failure. The apparatus is applied to a network device and includes: a configuration unit, which configures high-layer parameters for the terminal device, and the high-layer parameters are used for the terminal device to determine whether the lower layer notifies or indicates LBT failure to the upper layer.

[0011] According to the third aspect of the embodiments of the present application, there is provided a terminal device, and the terminal device includes the apparatus according to the first aspect of the embodiments of the present application.

[0012] According to the fourth aspect of the embodiments of the present application, there is provided a network device, and the network device includes the apparatus according to the second aspect of the embodiments of the present application.

[0013] According to the fifth aspect of the embodiments of the present application, there is provided a communication system, and the communication system includes the terminal device according to the third aspect of the embodiments of the present application and / or the network device according to the fourth aspect of the embodiments of the present application.

[0014] According to a sixth aspect of the embodiments of the present application, a method for indicating LBT failure is provided. The method is applied to a terminal device and includes: when it is determined in a lower layer or a higher layer that a first condition and / or a second condition are satisfied, and when an uplink transmission is blocked due to LBT failure, the lower layer notifies or indicates the LBT failure to the higher layer, or the lower layer starts to notify or indicate the LBT failure to the higher layer; and / or when it is determined in the lower layer or the higher layer that the first condition is not satisfied and / or a third condition is satisfied, and when the uplink transmission is blocked due to LBT failure, the lower layer does not notify or indicate the LBT failure to the higher layer, or the lower layer stops notifying or indicating the LBT failure to the higher layer.

[0015] According to a seventh aspect of the embodiments of the present application, a method for indicating LBT failure is provided. The method is applied to a network device and includes: configuring a higher layer parameter for a terminal device, where the higher layer parameter is used for the terminal device to determine whether the lower layer notifies or indicates the LBT failure to the higher layer.

[0016] According to an eighth aspect of the embodiments of the present application, a computer-readable program is provided. When the program is executed in a device or a terminal device for indicating LBT failure, the program causes the device or the terminal device for indicating LBT failure to execute the method for indicating LBT failure according to the sixth aspect of the embodiments of the present invention.

[0017] According to a ninth aspect of the embodiments of the present invention, a storage medium storing a computer-readable program is provided, where the computer-readable program causes a device or a terminal device for indicating LBT failure to execute the method for indicating LBT failure according to the sixth aspect of the embodiments of the present invention.

[0018] According to a tenth aspect of the embodiments of the present application, a computer-readable program is provided. When the program is executed in a device or a network device for indicating LBT failure, the program causes the device or the network device for indicating LBT failure to execute the method for indicating LBT failure according to the seventh aspect of the embodiments of the present invention.

[0019] According to an eleventh aspect of the embodiments of the present invention, a storage medium storing a computer-readable program is provided, where the computer-readable program causes a device or a network device for indicating LBT failure to execute the method for indicating LBT failure according to the seventh aspect of the embodiments of the present invention.

[0020] The beneficial effects of the embodiments of the present application are as follows: The lower layer or the higher layer first determines whether relevant conditions are satisfied. Based on the determination result, when an uplink transmission is blocked due to LBT failure, it is determined whether the lower layer notifies or indicates the LBT failure to the higher layer, or it is determined whether the lower layer starts or stops notifying or indicating the LBT failure to the higher layer. In this way, the inter-layer interaction between the lower layer and the higher layer can be reduced, thereby reducing the power consumption of the terminal device.

[0021] With reference to the following description and the accompanying drawings, specific embodiments of the present invention are disclosed in detail, indicating the ways in which the principles of the present invention can be employed. It should be understood that the embodiments of the present invention are not limited thereby in scope. Within the spirit and terms of the appended claims, the embodiments of the present invention include many variations, modifications, and equivalents.

[0022] Features described and / or illustrated for one embodiment can be used in the same or similar way in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0023] It should be emphasized that the term "comprising / including / having" as used herein refers to the presence of features, whole things, steps, or components, but does not exclude the presence or addition of one or more other features, whole things, steps, or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Elements and features described in one drawing or one embodiment of the embodiments of the present application can be combined with elements and features shown in one or more other drawings or embodiments. In addition, in the drawings, like reference numerals denote corresponding components in several drawings and can be used to indicate corresponding components used in more than one embodiment.

[0025] The included drawings are used to provide a further understanding of the embodiments of the present application, which form a part of the specification, illustrate the embodiments of the present invention, and, together with the written description, explain the principles of the present invention. Obviously, the drawings in the following description are only some embodiments of the present invention, and for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts. In the drawings:

[0026] Figure 1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0027] Figure 2 is a schematic diagram of an existing indication LBT failure mechanism;

[0028] Figure 3 is a schematic diagram of an indication LBT failure mechanism according to an embodiment of the present application;

[0029] Figure 4 is a schematic diagram of a method for indicating LBT failure according to Embodiment 1 of the present application;

[0030] Figure 5 is another schematic diagram of a method for indicating LBT failure according to Embodiment 1 of the present application;

[0031] Figure 6It is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application;

[0032] Figure 7 It is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application;

[0033] Figure 8 It is a schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application;

[0034] Figure 9 It is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application;

[0035] Figure 10 It is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application;

[0036] Figure 11 It is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application;

[0037] Figure 12 It is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application;

[0038] Figure 13 It is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application;

[0039] Figure 14 It is a schematic diagram of the method for indicating LBT failure in Embodiment 2 of the present application;

[0040] Figure 15 It is a schematic diagram of the method for indicating LBT failure in Embodiment 3 of the present application;

[0041] Figure 16 It is another schematic diagram of the method for indicating LBT failure in Embodiment 3 of the present application;

[0042] Figure 17 It is another schematic diagram of the method for indicating LBT failure in Embodiment 3 of the present application;

[0043] Figure 18 It is a schematic diagram of the device for indicating LBT failure in Embodiment 4 of the present application;

[0044] Figure 19 It is a schematic diagram of the device for indicating LBT failure in Embodiment 5 of the present application;

[0045] Figure 20 It is a schematic block diagram of the system composition of the terminal device in Embodiment 6 of the present application;

[0046] Figure 21 It is a schematic block diagram of the system composition of the network device in Embodiment 7 of the present application. Detailed implementation manners

[0047] Referring to the accompanying drawings, the foregoing and other features of the present invention will become apparent through the following description. In the description and drawings, specific embodiments of the present invention are specifically disclosed, which show some embodiments in which the principles of the present invention can be adopted. It should be understood that the present invention is not limited to the described embodiments. On the contrary, the present invention includes all modifications, variations and equivalents falling within the scope of the appended claims.

[0048] In the embodiments of the present application, terms such as "first" and "second" are used to distinguish different elements in terms of name, but do not indicate the spatial arrangement or time sequence of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. Terms such as "comprising", "including", "having", etc. mean the presence of the stated features, elements, components or assemblies, but do not exclude the presence or addition of one or more other features, elements, components or assemblies.

[0049] In the embodiments of the present application, the singular forms "a", "the", etc. include the plural forms and should be broadly understood as "a kind" or "a class" rather than being limited to the meaning of "one"; in addition, the term "the" should be understood to include both the singular form and the plural form unless the context clearly indicates otherwise. In addition, the term "according to" should be understood as "at least partially according to...", and the term "based on" should be understood as "at least partially based on...", unless the context clearly indicates otherwise.

[0050] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that conforms to any of the following communication standards, such as Long Term Evolution (LTE), Long Term Evolution-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), and so on.

[0051] Moreover, the communication between devices in the communication system can be carried out according to the communication protocols at any stage, for example, it may include but is not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and future 5G, New Radio (NR), and so on, and / or other currently known or future-developed communication protocols.

[0052] In the embodiments of the present application, the term "network device" refers, for example, to a device in a communication system that connects a user equipment to a communication network and provides services for the user equipment. The network device may include, but is not limited to, the following devices: base station (BS, Base Station), access point (AP, Access Point), transmission reception point (TRP, Transmission Reception Point), broadcast transmitter, mobile management entity (MME, Mobile Management Entity), gateway, server, radio network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller), and so on.

[0053] Among them, the base station may include, but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), etc. In addition, it may also include remote radio head (RRH, Remote Radio Head), remote radio unit (RRU, Remote Radio Unit), relay, or low-power node (such as femto, pico, etc.). And the term "base station" may include some or all of their functions, and each base station can provide communication coverage for a specific geographical area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0054] In the embodiments of the present application, the term "user equipment" (UE, User Equipment) refers, for example, to a device that accesses a communication network through a network device and receives network services, and may also be referred to as "terminal equipment" (TE, Terminal Equipment). The terminal equipment may be fixed or mobile, and may also be referred to as mobile station (MS, Mobile Station), terminal, subscriber station (SS, Subscriber Station), access terminal (AT, Access Terminal), station, and so on.

[0055] Among them, the terminal equipment may include, but is not limited to, the following devices: cellular phone, personal digital assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication device, handheld device, machine-type communication device, laptop computer, cordless phone, smart phone, smart watch, digital camera, and so on.

[0056] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, for example, including but not limited to: Machine Type Communication (MTC) terminals, vehicle-mounted communication terminals, Device to Device (D2D) terminals, Machine to Machine (M2M) terminals, and so on.

[0057] In the embodiments of the present application, "when...", "in... case", "for... situation", and "if..." all indicate based on a certain or certain conditions or states, etc. In addition, these expressions can be replaced with each other.

[0058] The scenarios of the embodiments of the present application are described below by examples, but the present invention is not limited thereto.

[0059] Figure 1 is a schematic diagram of the communication system according to the embodiments of the present application, which schematically illustrates the case taking the terminal device and the network device as examples, as Figure 1 shown, the communication system 100 may include: a network device 101 and a terminal device 102. For simplicity, Figure 1 only one terminal device is taken as an example for illustration. The network device 101 is, for example, a gNB of an NR network device.

[0060] In the embodiments of the present application, existing services or services that can be implemented in the future can be carried out between the network device 101 and the terminal device 102. For example, these services include but are not limited to: enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC), and so on.

[0061] When the terminal device 102 performs LBT, LBT failure may occur. Figure 2 is a schematic diagram of an existing mechanism for indicating LBT failure. As Figure 2As shown, the lower layer (e.g., the physical layer) of the terminal device 102 performs the LBT process. When the lower layer performs the LBT process before uplink transmission and the uplink transmission is not executed, that is, when the uplink transmission is blocked due to LBT failure, the lower layer indicates or notifies the LBT failure to the upper layer (e.g., the MAC layer). In this way, whenever the uplink transmission is blocked due to LBT failure, the lower layer notifies or indicates it to the upper layer, which will greatly increase the interaction between the lower layer and the upper layer and increase the power consumption of the terminal device 102.

[0062] Figure 3 is a schematic diagram of the mechanism for indicating LBT failure according to an embodiment of the present application. As Figure 3 shown, the lower layer of the terminal device 102 performs the LBT process. The lower layer or the upper layer first determines whether relevant conditions are met. When the determination result is that the relevant conditions are met, when the lower layer performs the LBT process before uplink transmission and the uplink transmission is not executed, that is, when the uplink transmission is blocked due to LBT failure, the lower layer notifies or indicates the LBT failure to the upper layer, or the lower layer starts to notify or indicate the LBT failure to the upper layer. When the determination result is that the relevant conditions are not met, when the uplink transmission is blocked due to LBT failure, the lower layer does not notify or indicate the LBT failure to the upper layer, or the lower layer stops notifying or indicating the LBT failure to the upper layer. In this way, the interaction between the lower layer and the upper layer can be reduced, and the power consumption of the terminal device 102 can be reduced.

[0063] The following describes various embodiments of the present application with reference to the accompanying drawings. These embodiments are merely exemplary and do not limit the present invention.

[0064] Embodiment 1

[0065] The embodiment of the present application provides a method for indicating LBT failure, and this method is applied to a terminal device.

[0066] Figure 4 is a schematic diagram of the method for indicating LBT failure according to Embodiment 1 of the present application. As Figure 4 shown, this method includes:

[0067] Step 401: When the uplink transmission is blocked due to LBT failure, the lower layer notifies or indicates the LBT failure to the upper layer, or the lower layer starts to notify or indicate the LBT failure to the upper layer when the lower layer or the upper layer determines that the first condition and / or the second condition is satisfied; and / or,

[0068] Step 402: When the uplink transmission is blocked due to LBT failure, the lower layer does not notify or indicate the LBT failure to the upper layer, or the lower layer stops notifying or indicating the LBT failure to the upper layer when the lower layer or the upper layer determines that the first condition is not satisfied and / or the third condition is satisfied.

[0069] In an embodiment of the present application, the method may include one of steps 401 and 402, or may include both steps 401 and 402. When the method includes both steps 401 and 402, the execution order of steps 401 and 402 is not limited.

[0070] Thus, the lower layer or the upper layer first determines whether relevant conditions are met. Based on the determination result, when the uplink transmission is blocked due to LBT failure, it is determined whether the lower layer notifies or indicates the LBT failure to the upper layer, or it is determined whether the lower layer starts or stops notifying or indicating the LBT failure to the upper layer. In this way, the inter-layer interaction between the lower layer and the upper layer can be reduced, thereby reducing the power consumption of the terminal device.

[0071] In an embodiment of the present application, the lower layer is, for example, the physical layer, and the upper layer is, for example, the MAC layer.

[0072] Hereinafter, various situations will be exemplarily described for the lower layer or the upper layer to determine whether each specific condition is met.

[0073] Situation 1: The lower layer determines whether the first condition is met: Figure 5 This is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application. As Figure 5 shown, the method includes:

[0074] Step 501: When the lower layer determines that the first condition is met and the uplink transmission is blocked due to LBT failure, the lower layer notifies or indicates the LBT failure to the upper layer, or the lower layer starts to notify or indicate the LBT failure to the upper layer; and / or,

[0075] Step 502: When the lower layer determines that the first condition is not met and the uplink transmission is blocked due to LBT failure, the lower layer does not notify or indicate the LBT failure to the upper layer, or the lower layer stops notifying or indicating the LBT failure to the upper layer.

[0076] In an embodiment of the present application, the method may include one of steps 501 and 502, or may include both steps 501 and 502. When the method includes both steps 501 and 502, the execution order of steps 501 and 502 is not limited.

[0077] In at least one embodiment of the present application, for example, the first condition includes at least one of the following conditions: the terminal device is an NR-U terminal; the terminal device is an NR terminal; the terminal device is an NR-U terminal or an NR terminal; the uplink transmission or the terminal device performs shared spectrum channel access operation; the uplink transmission is an uplink transmission scheduled or configured by a network device; the uplink transmission is not Licensed Assisted Access (LAA) or Enhanced Licensed Assisted Access (eLAA); the terminal device does not perform Licensed Assisted Access or Enhanced Licensed Assisted Access; and the uplink transmission is not an automatic uplink transmission.

[0078] That is to say, when at least one of the following holds: the terminal device is an NR-U terminal, the terminal device is an NR terminal, the terminal device is an NR-U terminal or an NR terminal, the uplink transmission or the terminal device performs shared spectrum channel access operation, the uplink transmission is an uplink transmission scheduled or configured by a network device, the uplink transmission is not Licensed Assisted Access (LAA) or Enhanced Licensed Assisted Access (eLAA), the terminal device does not perform Licensed Assisted Access or Enhanced Licensed Assisted Access, and the uplink transmission is not an automatic uplink transmission, the lower layer notifies or indicates LBT failure to the upper layer, or the lower layer starts to notify or indicate LBT failure to the upper layer. Additionally, when all the above-listed conditions do not hold, the lower layer does not notify or indicate LBT failure to the upper layer, or the lower layer stops notifying or indicating LBT failure to the upper layer.

[0079] Or, it can also be said that for at least one of an NR-U terminal, an NR terminal, an NR-U terminal or an NR terminal, a shared spectrum channel access operation, an uplink transmission scheduled or configured by a network device, non-LAA or eLAA, and non-AUL, the lower layer notifies or indicates LBT failure to the upper layer, or the lower layer starts to notify or indicate LBT failure to the upper layer.

[0080] According to the method described in Scenario 1, it can not only reduce the inter-layer interaction between the lower layer and the upper layer, thereby reducing the power consumption of the terminal device, but also the method is relatively simple, has little impact on the standard, can reduce the cost of the terminal device, and can also reduce the test cost.

[0081] In at least one embodiment of the present application, in step 501, notifying or indicating LBT failure includes: sending a notification or indication, or sending a notification or indication and the object performing LBT.

[0082] That is to say, the above-mentioned notification or indication can be carried out by a notification or indication sent from a lower layer to a higher layer, or can also be carried out by a notification or indication sent from a lower layer to a higher layer and an object that performs LBT.

[0083] For example, the sent notification or indication can be one of the following notifications or indications:

[0084] Generic indication or notification;

[0085] Notification or indication for specific purposes, for example, indication of continuous UL LBT failure detection, or indication of random access preamble, or indication of configured grant, or indication of Scheduling Request (SR);

[0086] Notification or indication sent from a lower layer to a higher layer through different Service Access Points (SAPs) or channels or paths; and

[0087] Notification or indication provided to different higher layer processes or functions or entities, for example, the higher layer process or function or entity refers to at least one of the following: continuous LBT failure detection, random access process, random access preamble transmission, Hybrid Automatic Repeat Request (HARQ), transmission of uplink configured grant, and Scheduling Request (SR).

[0088] In at least one embodiment of the present application, for the case where the above-mentioned notification or indication is carried out by a notification or indication sent from a lower layer to a higher layer and an object that performs LBT, the object that performs LBT can be characterized by uplink resources or an index corresponding to the uplink resources.

[0089] For example, the uplink resources include at least one of random access resources (RA / PRACH occasion), a valid PUCCH resource for Scheduling Request (SR), and configured grant.

[0090] For the case where the object that performs LBT is characterized by an index corresponding to the uplink resources, for example, a mapping relationship is defined, and the object can be characterized by the corresponding index. For example: it is defined that the random access resource (RA / PRACH occasion) corresponds to index 1, a valid PUCCH resource for SR corresponds to index 2, and configured grant corresponds to index 3.

[0091] In at least one embodiment of the present application, when the lower layer determines that the first condition is satisfied and the lower layer determines that the fourth condition is satisfied, the lower layer notifies or indicates to the upper layer that the LBT fails. In this way, by further restricting the conditions, the inter-layer interaction between the lower layer and the upper layer can be further reduced, thereby further reducing the power consumption of the terminal device.

[0092] Figure 6 It is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application. As Figure 6 shown, the method includes:

[0093] Step 601: When the lower layer determines that the first condition and the fourth condition are satisfied, and when the uplink transmission is blocked due to the LBT failure, the lower layer notifies or indicates to the upper layer that the LBT fails, or the lower layer starts to notify or indicate to the upper layer that the LBT fails.

[0094] In at least one embodiment of the present application, the fourth condition includes at least one of the following conditions: the LBT failure is any LBT failure; the LBT failure is the LBT failure performed for the transmission of the random access preamble; the LBT failure is the LBT failure performed for the configured grant; and the LBT failure is the LBT failure performed for a valid Physical Uplink Control Channel (PUCCH) resource of the scheduling request (SR).

[0095] In at least one embodiment of the present application, for the case where the LBT failure is any LBT failure, that is, for an uplink transmission, if the terminal device or the lower layer fails to access the channel, and if the lower layer determines that the first condition is simultaneously satisfied, the lower layer notifies or indicates to the upper layer that the LBT fails.

[0096] For example, the uplink transmission is indicated by the upper layer (such as the MAC layer), or triggered or generated by the lower layer (such as the physical layer), for example, acknowledgment or non-acknowledgment (ACK or NACK), sounding reference signal (SRS), channel quality indication (CQI), etc.;

[0097] For example, there is no restriction on the channel used for the uplink transmission. For example, the uplink transmission may be performed on the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH) or the Physical Random Access Channel (PRACH);

[0098] For example, the type of LBT performed is not limited. For example, the type of LBT performed can be LBT type 2 or LBT type 4, etc.

[0099] For example, the channel access priority class (CAPC) of the LBT performed is not limited. For example, the CAPC priority is 1 or 4, etc.

[0100] In at least one embodiment of the present application, for the case where the LBT failure is the LBT failure performed for the transmission of a random access preamble (RA preamble), that is, in order to send the RA preamble, the terminal device or the lower layer fails to access the channel. If the lower layer determines that the first condition is satisfied at the same time, the lower layer notifies or indicates the LBT failure to the upper layer.

[0101] For example, the channel corresponding to the LBT is a physical random access channel (PRACH), and the LBT is the LBT performed on the random access resource (RA / PRACH occasion) indicated by the upper layer.

[0102] For example, the uplink transmission is indicated by the upper layer (such as the MAC layer), or triggered or generated by the lower layer (such as the physical layer). For example, the repetition of the physical layer.

[0103] For example, the type of LBT performed is not limited. For example, the type of LBT performed can be LBT type 2 or LBT type 4, etc.

[0104] For example, the channel access priority class (CAPC) of the LBT performed is not limited. For example, the CAPC priority is 1 or 4, etc.

[0105] In at least one embodiment of the present application, for the case where the LBT failure is the LBT failure performed for the configured grant, that is, in order to send the uplink transmission on the configured grant, the terminal device or the lower layer fails to access the channel. If the lower layer determines that the first condition is satisfied at the same time, the lower layer notifies or indicates the LBT failure to the upper layer.

[0106] For example, the channel corresponding to the LBT is a physical uplink shared channel (PUSCH), and the LBT is the LBT performed on the configured grant indicated by the upper layer.

[0107] For example, the type of LBT performed is not limited. For example, the type of LBT performed can be LBT type 2 or LBT type 4, etc.

[0108] For example, the Channel Access Priority Class (CAPC) of the performed LBT is not limited. For example, the CAPC priority is 1 or 4, etc.

[0109] In at least one embodiment of the present application, for the case where the LBT failure is the LBT failure performed for a valid Physical Uplink Control Channel (PUCCH) resource for a Scheduling Request (SR), that is, in order to send an SR on a valid PUCCH resource, if the terminal device or the lower layer fails to access the channel, and if the lower layer determines that the first condition is satisfied at the same time, the lower layer notifies or indicates the LBT failure to the upper layer.

[0110] For example, the channel corresponding to the LBT is the Physical Uplink Control Channel (PUCCH), and the LBT is performed on a valid PUCCH resource for an SR indicated by the upper layer;

[0111] For example, the LBT type of the performed LBT is not limited. For example, the LBT type of the performed LBT may be LBT type 2 or LBT type 4, etc.;

[0112] For example, the Channel Access Priority Class (CAPC) of the performed LBT is not limited. For example, the CAPC priority is 1 or 4, etc.

[0113] In at least one embodiment of the present application, as Figure 5 shown, the method may further include:

[0114] Step 503: When the upper layer is notified or indicated or when the upper layer is not notified or indicated, a counter is incremented by 1 or remains unchanged or is suspended, or, a timer is started or restarted, or, the terminal device or the upper layer is triggered to execute a process.

[0115] In at least one embodiment of the present application, the counter is one of the following counters:

[0116] A counter for calculating the number of scheduling requests, for example, the counter SR_COUNTER;

[0117] A counter for applying or suspending power ramping, for example, the counter PREAMBLE_POWER_RAMPING_COUNTER; and

[0118] A counter for continuous LBT failure detection, for example, the counter LBT_COUNTER.

[0119] In at least one embodiment of the present application, the timer is a timer for configuring grants (CG), for example, configuredGrantTimer or cg-RetransmissionTimer, or the timer is a timer for continuous LBT failure detection, such as lbt-FailureDetectionTimer.

[0120] In at least one embodiment of the present application, the process triggered by the terminal device or the higher layer is a random access process or a random access resource selection process.

[0121] In this way, for the lower layer to notify or indicate LBT failure to the higher layer in the embodiments of the present application, the notification or indication can not only notify or indicate the LBT failure, but also trigger other behaviors or operations or processes according to whether the higher layer is notified or indicated. For example, as described above, for the operation of the counter for scheduling requests or the counter for applying or suspending power ramping, and / or trigger a random access process or a random access resource selection process.

[0122] Case 2: The lower layer determines whether the second condition and / or the third condition are met:

[0123] Figure 7 It is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application. As Figure 7 shown, the method includes:

[0124] Step 701: When the uplink transmission is blocked due to LBT failure and the lower layer determines that the second condition is met, the lower layer notifies or indicates the LBT failure to the higher layer, or the lower layer starts to notify or indicate the LBT failure to the higher layer; and / or

[0125] Step 702: When the uplink transmission is blocked due to LBT failure and the lower layer determines that the third condition is met, the lower layer does not notify or indicate the LBT failure to the higher layer, or the lower layer stops notifying or indicating the LBT failure to the higher layer.

[0126] In the embodiments of the present application, the method may include one of Step 701 and Step 702, or may include both Step 701 and Step 702. When the method includes both Step 701 and Step 702, the execution order of Step 701 and Step 702 is not limited.

[0127] In at least one embodiment of the present application, the second condition is that the higher layer parameters are configured and / or the capabilities are available, and / or the third condition is that the higher layer parameters are released or removed and / or the capabilities are not available.

[0128] For example, the higher layer parameter is an RRC parameter.

[0129] Figure 8 This is a schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application. As Figure 8 shown, the method includes:

[0130] Step 801: When the uplink transmission is blocked due to LBT failure under the condition that the high-layer parameters are configured and / or the capabilities are available in the lower layer, the lower layer notifies or indicates the LBT failure to the high layer, or the lower layer starts to notify or indicate the LBT failure to the high layer; and / or,

[0131] Step 802: When the uplink transmission is blocked due to LBT failure under the condition that the high-layer parameters are released or removed and / or the capabilities are not available in the lower layer, the lower layer does not notify or indicate the LBT failure to the high layer, or the lower layer stops notifying or indicating the LBT failure to the high layer.

[0132] In an embodiment of the present application, the method may include one of Step 801 and Step 802, or may include both Step 801 and Step 802. When the method includes both Step 801 and Step 802, the execution order of Step 801 and Step 802 is not restricted.

[0133] The method described in Case 2 restricts more precise conditions, which can further reduce the inter-layer interaction between the lower layer and the high layer, thereby further reducing the power consumption of the terminal device.

[0134] In at least one embodiment of the present application, the high-layer parameters include at least one of the following parameters: parameters for continuous LBT failure detection for shared spectrum channel access; configuration parameters for scheduling requests; configuration parameters for configured grants.

[0135] For the parameters for continuous LBT failure detection for shared spectrum channel access, for example, the high-layer parameter is lbt-FailureRecoveryConfig, or for another example, the high-layer parameter is cell-specific or terminal device-specific; and / or, when dual connectivity (DC) is configured, the high-layer parameter is configured separately in the master cell group (MCG) and the secondary cell group (SCG); and / or, when supplementary uplink (SUL) is configured, the high-layer parameter is configured separately for the supplementary uplink (SUL) and the normal uplink (NUL).

[0136] For the configuration parameters for scheduling requests, for example, the high-layer parameter is a parameter for configuring dedicated scheduling request resources, such as SchedulingRequestConfig; or for another example, the high-layer parameter is a parameter for the maximum number of SR transmissions, such as sr-TransMax.

[0137] For the configuration parameters authorized for configuration, for example, the high-layer parameter is a parameter for configuring uplink transmission without dynamic authorization, such as ConfiguredGrantConfig; or, for example, the high-layer parameter is a parameter for the timer of CG, such as configuredGrantTimer or cg-RetransmissionTimer.

[0138] In at least one embodiment of the present application, the capability is the capability of NR operation in a shared spectrum channel and / or the capability of continuous LBT detection and recovery.

[0139] In at least one embodiment of the present application, the capability is specific to the terminal device; or, the capability is cell-specific, for example, the individual capabilities of the primary cell (PCell), the primary secondary cell (PSCell), and the secondary cell (SCell); or, the capability is band-specific or band-combination-specific.

[0140] In at least one embodiment of the present application, in step 701 or step 801, notifying or indicating an LBT failure includes: sending a notification or indication, or, sending a notification or indication and the object performing the LBT.

[0141] That is to say, the above notification or indication can be carried out by a notification or indication sent from the lower layer to the upper layer, or can also be carried out by a notification or indication sent from the lower layer to the upper layer and the object performing the LBT.

[0142] In case 2, the specific methods of carrying out the above notification or indication by a notification or indication sent from the lower layer to the upper layer and of carrying out the above notification or indication by a notification or indication sent from the lower layer to the upper layer and the object performing the LBT can be the same as those described in case 1, and will not be repeated here.

[0143] In at least one embodiment of the present application, when the lower layer determines that the second condition is satisfied and the lower layer determines that the fourth condition is satisfied, the lower layer notifies or indicates an LBT failure to the upper layer. In this way, by further restricting the conditions, the inter-layer interaction between the lower layer and the upper layer can be further reduced, thereby further reducing the power consumption of the terminal device.

[0144] Figure 9 It is another schematic diagram of the method for indicating an LBT failure in Embodiment 1 of the present application. As Figure 9 shown, the method includes:

[0145] Step 901: When the lower layer determines that the second condition and the fourth condition are satisfied, when the uplink transmission is blocked due to an LBT failure, the lower layer notifies or indicates an LBT failure to the upper layer, or, the lower layer starts to notify or indicate an LBT failure to the upper layer.

[0146] In at least one embodiment of the present application, the fourth condition includes at least one of the following conditions: the LBT failure is any LBT failure; the LBT failure is an LBT failure performed for the transmission of a random access preamble; the LBT failure is an LBT failure performed for a configured grant; and the LBT failure is an LBT failure performed for a valid Physical Uplink Control Channel (PUCCH) resource of a scheduling request (SR).

[0147] In case 2, the specific content of the above fourth condition may be the same as that described in case 1, and will not be repeated here.

[0148] In at least one embodiment of the present application, similar to step 503 in case 1, as Figure 7 shown, the method may further include:

[0149] Step 703: When the higher layer is notified or instructed or when the higher layer is not notified or instructed, a counter is incremented or remains unchanged or suspended, or, a timer is started or restarted, or, the terminal device or the higher layer is triggered to execute a process.

[0150] In case 2, the specific content of the counter, the timer, and the process triggered for the terminal device or the higher layer to execute may be the same as that described in case 1, and will not be repeated here.

[0151] Case 3, the higher layer determines whether the first condition is satisfied:

[0152] Figure 10 is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application. As Figure 10 shown, the method includes:

[0153] Step 1001: When the higher layer determines that the first condition is satisfied, the higher layer sends a notification or instruction or request to the lower layer;

[0154] Step 1002: When the uplink transmission is blocked due to an LBT failure, the lower layer notifies or indicates the LBT failure to the higher layer, or, the lower layer starts to notify or indicate the LBT failure to the higher layer.

[0155] That is to say, when the higher layer determines that the first condition is satisfied, the higher layer sends a notification or instruction or request to the lower layer, and the lower layer, according to the notification or instruction or request, when the uplink transmission is blocked due to an LBT failure, notifies or indicates the LBT failure to the higher layer, or, starts to notify or indicate the LBT failure to the higher layer.

[0156] Figure 11Another schematic diagram of the method for indicating LBT failure in Embodiment 1 of this application. As Figure 11 shown, the method includes:

[0157] Step 1101: When it is determined at a higher layer that the first condition is not satisfied, the higher layer sends a notice, an indication, or a request to the lower layer;

[0158] Step 1102: When the uplink transmission is blocked due to LBT failure, the lower layer does not notify or indicate the LBT failure to the higher layer, or the lower layer stops notifying or indicating the LBT failure to the higher layer.

[0159] That is to say, when it is determined at a higher layer that the first condition is not satisfied, the higher layer sends a notice, an indication, or a request to the lower layer. According to this notice, indication, or request, when the uplink transmission is blocked due to LBT failure, the lower layer does not notify or indicate the LBT failure to the higher layer, or stops notifying or indicating the LBT failure.

[0160] The method described in Case 3 limits more precise conditions, which can further reduce the inter-layer interaction between the lower layer and the higher layer, thereby further reducing the power consumption of the terminal device.

[0161] In at least one embodiment of this application, for example, the specific content of the first condition is the same as that described in Case 1.

[0162] That is to say, when at least one of the following conditions is met: the terminal device is an NR-U terminal, the terminal device is an NR terminal, the terminal device is an NR-U terminal or an NR terminal, the uplink transmission or the terminal device performs shared spectrum channel access operation, the uplink transmission is an uplink transmission scheduled or configured by a network device, the uplink transmission is not Licensed Assisted Access (LAA) or Enhanced Licensed Assisted Access (eLAA), the terminal device does not perform licensed assisted access or enhanced licensed assisted access, and the uplink transmission is not an automatic uplink transmission, the higher layer sends a notice, an indication, or a request to the lower layer so that the lower layer notifies or indicates the LBT failure to the higher layer, or the lower layer starts to notify or indicate the LBT failure to the higher layer. Additionally, when all the above-listed conditions are not met, the higher layer sends a notice, an indication, or a request to the lower layer so that the lower layer does not notify or indicate the LBT failure to the higher layer, or the lower layer stops notifying or indicating the LBT failure to the higher layer.

[0163] Alternatively, it can also be said that, for at least one of the NR-U terminal, NR terminal, NR-U terminal or NR terminal, performing shared spectrum channel access operation, network device scheduling or configuration of uplink transmission, non-LAA or eLAA, and non-AUL, the higher layer sends a notification or indication or request to the lower layer, so that the lower layer notifies or indicates to the higher layer the LBT failure, or the lower layer starts to notify or indicate to the higher layer the LBT failure.

[0164] In at least one embodiment of the present application, in step 1002, notifying or indicating the LBT failure includes: sending a notification or indication, or sending a notification or indication and the object performing the LBT. The specific content is the same as that recorded in case 1 and will not be repeated here.

[0165] In at least one embodiment of the present application, in step 1001 and / or step 1101, the notification or indication or request includes: sending a notification or indication or request, or sending a notification or indication or request and the object performing the LBT. That is to say, the above notification or indication or request can be made by sending a notification or indication or request from the higher layer to the lower layer, or can also be made by sending a notification or indication or request from the higher layer to the lower layer and the object performing the LBT.

[0166] For example, the notification or indication or request sent by the higher layer to the lower layer is one of the following notifications or indications or requests:

[0167] Generic indication or notification;

[0168] Notification or indication for specific purposes, such as indication of continuous UL LBT failure detection, or indication of random access preamble, or indication of configured grant, or indication of Scheduling Request (SR);

[0169] Notification or indication sent by the lower layer to the higher layer through different Service Access Points (SAPs) or channels or paths; and

[0170] Notification or indication provided to different higher layer processes or functions or entities, for example, the higher layer process or function or entity refers to at least one of the following: continuous LBT failure detection, random access process, random access preamble transmission, Hybrid Automatic Repeat Request (HARQ), transmission of uplink configured grant, and Scheduling Request (SR).

[0171] In at least one embodiment of the present application, for a case where a notification, or an indication, or a request sent from a higher layer to a lower layer and an object for performing LBT are used for the above-mentioned notification, or indication, or request, the object for performing LBT may be characterized by an uplink resource or an index corresponding to the uplink resource.

[0172] For example, the uplink resource includes at least one of a random access resource (RA / PRACH occasion), a valid PUCCH resource for a scheduling request (SR), and a configured grant.

[0173] For a case where the object for performing LBT is characterized by an index corresponding to the uplink resource, for example, a mapping relationship is defined, and the object may be characterized by the corresponding index. For example: it is defined that a random access resource (RA / PRACH occasion) corresponds to index 1, a valid PUCCH resource for SR corresponds to index 2, and a configured grant corresponds to index 3.

[0174] In at least one embodiment of the present application, in step 1001, when the higher layer determines that the first condition is satisfied and the higher layer determines that the fourth condition is satisfied, the higher layer sends a notification, or an indication, or a request to the lower layer. In this way, by further restricting the conditions, the inter-layer interaction between the lower layer and the higher layer can be further reduced, thereby further reducing the power consumption of the terminal device.

[0175] In case 3, the specific content of the above-mentioned fourth condition may be the same as that described in case 1, and will not be repeated here.

[0176] In at least one embodiment of the present application, in step 1001, when maintaining a counter, that is, determining whether to increment a counter, or keep it unchanged, or suspend it, or when maintaining a timer, that is, determining whether to start or restart a timer, or when determining whether to trigger a terminal device or a higher layer to execute a process, the higher layer sends the notification, or the indication, or the request to the lower layer.

[0177] In at least one embodiment of the present application, the counter is one of the following counters:

[0178] A counter for calculating the number of scheduling requests, for example, the counter SR_COUNTER;

[0179] A counter for applying or suspending power ramping, for example, the counter PREAMBLE_POWER_RAMPING_COUNTER; and

[0180] A counter for continuous LBT failure detection, for example, the counter LBT_COUNTER.

[0181] In at least one embodiment of the present application, the timer is a timer for configuring grants (CG), for example, configuredGrantTimer or cg-RetransmissionTimer, or the timer is a timer for continuous LBT failure detection, such as lbt-FailureDetectionTimer.

[0182] In at least one embodiment of the present application, the process triggered for the terminal device or the upper layer to execute is a random access process or a random access resource selection process.

[0183] In at least one embodiment of the present application, similar to step 503 in case 1, as Figure 10 shown, the method may further include:

[0184] Step 1003: When the upper layer is notified or instructed or when the upper layer is not notified or instructed, a counter is incremented or remains unchanged or suspended, or a timer is started or restarted, or a process is triggered for the terminal device or the upper layer to execute.

[0185] In at least one embodiment of the present application, similar to step 503 in case 1, as Figure 11 shown, the method may further include:

[0186] Step 1103: When the upper layer is not notified or instructed or when the upper layer is not notified or instructed, a counter is incremented or remains unchanged or suspended, or a timer is started or restarted, or a process is triggered for the terminal device or the upper layer to execute.

[0187] In case 3, the specific contents of the counter, the timer, and the process triggered for the terminal device or the upper layer to execute may be the same as those described in case 1, and will not be repeated here.

[0188] Case 4: The upper layer determines whether the second condition and / or the third condition are satisfied:

[0189] Figure 12 is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application. As Figure 12 shown, the method includes:

[0190] Step 1201: When the upper layer determines that the second condition is satisfied, the upper layer sends a notification or instruction or request to the lower layer;

[0191] Step 1202: When the uplink transmission is blocked due to LBT failure, the lower layer notifies or indicates the LBT failure to the upper layer, or the lower layer starts to notify or indicate the LBT failure to the upper layer.

[0192] That is to say, when the higher layer determines that the second condition is met, the higher layer sends a notice, an instruction, or a request to the lower layer. Based on this notice, instruction, or request, when the uplink transmission is blocked due to LBT failure, the lower layer notifies or instructs the higher layer of the LBT failure, or starts to notify or instruct the higher layer of the LBT failure.

[0193] Figure 13 is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application. As Figure 13 shown, the method includes:

[0194] Step 1301: When the higher layer determines that the third condition is met, the higher layer sends a notice, an instruction, or a request to the lower layer;

[0195] Step 1302: When the uplink transmission is blocked due to LBT failure, the lower layer does not notify or instruct the higher layer of the LBT failure, or the lower layer stops notifying or instructing the higher layer of the LBT failure.

[0196] That is to say, when the higher layer determines that the third condition is met, the higher layer sends a notice, an instruction, or a request to the lower layer. Based on this notice, instruction, or request, when the uplink transmission is blocked due to LBT failure, the lower layer does not notify or instruct the higher layer of the LBT failure, or stops notifying or instructing the higher layer of the LBT failure.

[0197] The method described in Case 4 limits more precise conditions, which can further reduce the interaction between the lower layer and the higher layer, thereby further reducing the power consumption of the terminal device.

[0198] In at least one embodiment of the present application, the second condition is that the higher layer parameters are configured and / or the capabilities are available, and / or the third condition is that the higher layer parameters are released or removed and / or the capabilities are not available.

[0199] In Case 4, the specific content of the higher layer parameters and capabilities may be the same as that described in Case 2, and will not be repeated here.

[0200] In at least one embodiment of the present application, in Step 1201 and / or Step 1301, the notice, instruction, or request includes: sending a notice, an instruction, or a request, or sending a notice, an instruction, or a request and the object for performing LBT. That is to say, the above notice, instruction, or request can be carried out by sending a notice, an instruction, or a request from the higher layer to the lower layer, or by sending a notice, an instruction, or a request from the higher layer to the lower layer and the object for performing LBT.

[0201] For example, the notice, instruction, or request sent by the higher layer to the lower layer is one of the following notices, instructions, or requests:

[0202] Generic indication or notification;

[0203] Notification or indication for specific purposes, for example, indication of continuous UL LBT failure detection, or indication of random access preamble, or indication of configured grant, or indication of Scheduling Request (SR);

[0204] Notification or indication sent from the lower layer to the upper layer through different Service Access Points (SAPs) or channels or paths; and

[0205] Notification or indication provided to different upper layer processes or functions or entities, for example, the upper layer process or function or entity refers to at least one of the following: continuous LBT failure detection, random access process, random access preamble transmission, Hybrid Automatic Repeat Request (HARQ), transmission of uplink configured grant, and Scheduling Request (SR).

[0206] In at least one embodiment of the present application, for a notification or indication or request sent from the upper layer to the lower layer and for the object that performs LBT in the case of the above notification or indication or request, the object that performs LBT can be characterized by an uplink resource or an index corresponding to the uplink resource.

[0207] For example, the uplink resource includes at least one of a random access resource (RA / PRACH occasion), a valid PUCCH resource for a Scheduling Request (SR), and a configured grant.

[0208] For the case where the object that performs LBT is characterized by an index corresponding to the uplink resource, for example, a mapping relationship is defined, and the object can be characterized by the corresponding index. For example: define that the random access resource (RA / PRACH occasion) corresponds to index 1, a valid PUCCH resource for SR corresponds to index 2, and the configured grant corresponds to index 3.

[0209] In at least one embodiment of the present application, in step 1201, when the upper layer determines that the second condition is satisfied and the upper layer determines that the fourth condition is satisfied, the upper layer sends a notification or indication or request to the lower layer. In this way, by further restricting the conditions, the inter-layer interaction between the lower layer and the upper layer can be further reduced, thereby further reducing the power consumption of the terminal device.

[0210] In case 4, the specific content of the above fourth condition may be the same as that described in case 1, and will not be repeated here.

[0211] In at least one embodiment of the present application, in step 1201, when maintaining a counter, that is, determining whether to increment a counter by 1, keep it unchanged, or suspend it, or when maintaining a timer, that is, determining whether to start or restart a timer, or when determining whether to trigger a terminal device or a higher layer to execute a process, the higher layer sends the notification, indication, or request to the lower layer.

[0212] In at least one embodiment of the present application, the counter is one of the following counters:

[0213] A counter for calculating the number of scheduling requests, for example, the counter SR_COUNTER;

[0214] A counter for applying or suspending power ramping, for example, the counter PREAMBLE_POWER_RAMPING_COUNTER; and

[0215] A counter for continuous LBT failure detection, for example, the counter LBT_COUNTER.

[0216] In at least one embodiment of the present application, the timer is a timer for configured grant (CG), for example, configuredGrantTimer or cg-RetransmissionTimer, or the timer is a timer for continuous LBT failure detection, for example, lbt-FailureDetectionTimer.

[0217] In at least one embodiment of the present application, the process triggered for the terminal device or the higher layer to execute is a random access process or a random access resource selection process.

[0218] In at least one embodiment of the present application, similar to step 503 of case 1, as Figure 12 shown, the method may further include:

[0219] Step 1203: When the higher layer is notified or indicated or when the higher layer is not notified or indicated, a counter is incremented by 1, kept unchanged, or suspended, or a timer is started or restarted, or the terminal device or the higher layer is triggered to execute a process.

[0220] In at least one embodiment of the present application, similar to step 503 of case 1, as Figure 13 shown, the method may further include:

[0221] Step 1303: When the higher layer is not notified or indicated or when the higher layer is not notified or indicated, a counter is incremented by 1, kept unchanged, or suspended, or a timer is started or restarted, or the terminal device or the higher layer is triggered to execute a process.

[0222] In Case 4, the counter, timer, and the specific content of the process that triggers the terminal device or the higher layer to execute can be the same as those described in Case 1, and will not be repeated here.

[0223] As described above, taking Cases 1-4 as examples, an exemplary description has been given for whether the lower layer or the higher layer meets each specific condition. However, the embodiments of the present application may also include various combinations based on the following three factors: whether the executing entity is the higher layer or the lower layer, whether the satisfied condition is the first condition, the second condition, or both the first condition and the second condition are satisfied, and whether the first condition is not satisfied, the third condition is satisfied, or the first condition is not satisfied and the third condition is satisfied.

[0224] As can be seen from the above embodiments, the lower layer or the higher layer first determines whether the relevant conditions are met. Based on the judgment result, when the uplink transmission is blocked due to LBT failure, it is determined whether the lower layer notifies or indicates the LBT failure to the higher layer, or determines whether the lower layer starts or stops notifying or indicating the LBT failure to the higher layer. In this way, the inter-layer interaction between the lower layer and the higher layer can be reduced, thereby reducing the power consumption of the terminal device.

[0225] Embodiment 2

[0226] The embodiment of the present application provides a method for indicating LBT failure. This method is applied to a network device, which corresponds to the method for indicating LBT failure applied to a terminal device described in Embodiment 1, and the same content will not be repeated.

[0227] Figure 14 A schematic diagram of the method for indicating LBT failure according to Embodiment 2 of the present application. As Figure 14 shown, this method includes:

[0228] Step 1401: Configure high-layer parameters for the terminal device, and the high-layer parameters are used for the terminal device to determine whether the lower layer notifies or indicates the LBT failure to the higher layer.

[0229] In at least one embodiment of the present application, the high-layer parameters are also used for the terminal device to determine whether the higher layer sends a notice, indication, or request to the lower layer.

[0230] In at least one embodiment of the present application, the terminal device determines whether the lower layer notifies or indicates the LBT failure to the higher layer, or whether the lower layer starts or stops notifying or indicating the LBT failure to the higher layer according to the second condition and / or the third condition. The second condition is that the high-layer parameters are configured and / or the capabilities are available, and / or the third condition is that the high-layer parameters are released or removed and / or the capabilities are not available.

[0231] For the specific content of the high-layer parameters used by the terminal device, reference can be made to the description in Embodiment 1, and no further description will be given here.

[0232] In at least one embodiment of the present application, the high-layer parameter includes at least one of the following parameters: a parameter for continuous LBT failure detection for shared spectrum channel access; a configuration parameter for scheduling requests; a configuration parameter for configured grants.

[0233] In at least one embodiment of the present application, the high-layer parameter is cell-specific or terminal device-specific; and / or, when dual connectivity (DC) is configured, the high-layer parameter is configured separately in the master cell group (MCG) and the secondary cell group (SCG); and / or, when supplementary uplink (SUL) is configured, the high-layer parameter is configured separately for the supplementary uplink (SUL) and the normal uplink (NUL).

[0234] In this embodiment, for the specific content of the high-layer parameter, reference can be made to the description in Embodiment 1, and no further description will be given here.

[0235] As can be seen from the above embodiments, the network device configures high-layer parameters for the terminal device to determine whether the lower layer notifies or indicates LBT failure to the high layer. In this way, the lower layer or the high layer first determines whether the relevant conditions are met, and then based on the judgment result, when the uplink transmission is blocked due to LBT failure, it is determined whether the lower layer notifies or indicates LBT failure to the high layer, or it is determined whether the lower layer starts or stops notifying or indicating LBT failure to the high layer. In this way, the inter-layer interaction between the lower layer and the high layer can be reduced, thereby reducing the power consumption of the terminal device.

[0236] Embodiment 3

[0237] The embodiment of the present application provides a method for indicating LBT failure. This method is applied to the network device and the terminal device, corresponding to the method for indicating LBT failure applied to the terminal device described in Embodiment 1 and the method for indicating LBT failure applied to the network device described in Embodiment 2. The same content will not be repeated here.

[0238] Figure 15 It is a schematic diagram of the method for indicating LBT failure in Embodiment 3 of the present application. As Figure 15 shown, the method includes:

[0239] Step 1501: The network device configures high-layer parameters for the terminal device, and the high-layer parameter is used for the terminal device to determine whether the lower layer notifies or indicates LBT failure to the high layer;

[0240] Step 1502: When the uplink transmission is blocked due to LBT failure under the condition that the lower layer determines that the first condition and / or the second condition is satisfied, the lower layer notifies or indicates the LBT failure to the upper layer, or the lower layer starts to notify or indicate the LBT failure to the upper layer;

[0241] Step 1503: When the uplink transmission is blocked due to LBT failure under the condition that the lower layer determines that the first condition is not satisfied and / or the third condition is satisfied, the lower layer does not notify or indicate the LBT failure to the upper layer, or the lower layer stops notifying or indicating the LBT failure to the upper layer.

[0242] Figure 16 is another schematic diagram of the method for indicating LBT failure in Embodiment 3 of the present application. As Figure 16 shown, the method includes:

[0243] Step 1601: The network device configures high-layer parameters for the terminal device, and the high-layer parameters are used for the terminal device to determine whether the lower layer notifies or indicates the LBT failure to the upper layer;

[0244] Step 1602: When the upper layer determines that the first condition and / or the second condition is satisfied, the upper layer sends a notification or indication or request to the lower layer; Step 1603: When the uplink transmission is blocked due to LBT failure, the lower layer notifies or indicates the LBT failure to the upper layer, or the lower layer starts to notify or indicate the LBT failure to the upper layer.

[0245] Figure 17 is another schematic diagram of the method for indicating LBT failure in Embodiment 3 of the present application. As Figure 17 shown, the method includes:

[0246] Step 1701: The network device configures high-layer parameters for the terminal device, and the high-layer parameters are used for the terminal device to determine whether the lower layer notifies or indicates the LBT failure to the upper layer;

[0247] Step 1702: When the upper layer determines that the first condition is not satisfied and / or the third condition is satisfied, the upper layer sends a notification or indication or request to the lower layer; Step 1703: When the uplink transmission is blocked due to LBT failure, the lower layer does not notify or indicate the LBT failure to the upper layer, or the lower layer stops notifying or indicating the LBT failure to the upper layer.

[0248] In at least one embodiment of the present application, Figures 15 to 17 the specific implementation of each step can refer to the descriptions in Embodiment 1 and Embodiment 2, and will not be repeated here.

[0249] As can be seen from the above embodiments, the lower layer or the upper layer first determines whether relevant conditions are met. Based on the judgment result, when the uplink transmission is blocked due to LBT failure, it is determined whether the lower layer notifies or indicates the LBT failure to the upper layer, or determines whether the lower layer starts or stops notifying or indicating the LBT failure to the upper layer. In this way, the inter-layer interaction between the lower layer and the upper layer can be reduced, thereby reducing the power consumption of the terminal device.

[0250] Embodiment 4

[0251] An embodiment of the present application provides a device for indicating LBT failure, and this device is applied to a terminal device. Since the principle of this device for solving problems is similar to the method of Embodiment 1, the specific implementation thereof can refer to the implementation of the method described in Embodiment 1, and the same or relevant content will not be repeated.

[0252] Figure 18 is a schematic diagram of the device for indicating LBT failure according to Embodiment 4 of the present application. As Figure 18 shown, the device 1800 includes:

[0253] A first indication unit 1801, when the lower layer or the upper layer determines that the first condition and / or the second condition are met, when the uplink transmission is blocked due to LBT failure, the lower layer notifies or indicates the LBT failure to the upper layer, or the lower layer starts to notify or indicate the LBT failure to the upper layer; and / or,

[0254] A second indication unit 1802, when the lower layer or the upper layer determines that the first condition is not met and / or the third condition is met, when the uplink transmission is blocked due to LBT failure, the lower layer does not notify or indicate the LBT failure to the upper layer, or the lower layer stops notifying or indicating the LBT failure to the upper layer.

[0255] In at least one embodiment of the present application, as Figure 18 shown, the device 1800 may further include:

[0256] A first processing unit 1803, when the upper layer is notified or indicated, or when the upper layer is not notified or indicated, a counter is incremented or remains unchanged or suspended; or a timer is started or restarted; or a process of the terminal device or the upper layer is triggered.

[0257] In at least one embodiment of the present application, when the upper layer determines that the first condition and / or the second condition are met, the device 1800 may further include:

[0258] A third indication unit 1804, which is used for the upper layer to send a notice or indication or request to the lower layer; based on the notice or indication or request, when the uplink transmission is blocked due to LBT failure, the lower layer notifies or indicates the LBT failure to the upper layer, or causes the lower layer to start notifying or indicating the LBT failure to the upper layer.

[0259] In at least one embodiment of the present application, when it is determined by the upper layer that the first condition is not satisfied and / or the third condition is satisfied, the apparatus 1800 may further include:

[0260] A fourth indication unit 1805, which is used for the upper layer to send a notification or an indication or a request to the lower layer; based on the notification or the indication or the request, when the uplink transmission is blocked due to LBT failure, the lower layer does not notify or indicate the LBT failure to the upper layer, or the lower layer stops notifying or indicating the LBT failure to the upper layer.

[0261] In this embodiment, the implementation of the functions of the above-mentioned respective units may refer to the content of the relevant steps in Embodiment 1, and will not be repeated here.

[0262] As can be seen from the above embodiments, the lower layer or the upper layer first determines whether the relevant conditions are satisfied. Based on the determination result, when the uplink transmission is blocked due to LBT failure, it is determined whether the lower layer notifies or indicates the LBT failure to the upper layer, or it is determined whether the lower layer starts or stops notifying or indicating the LBT failure to the upper layer. In this way, the inter-layer interaction between the lower layer and the upper layer can be reduced, thereby reducing the power consumption of the terminal device.

[0263] Embodiment 5

[0264] An embodiment of the present application provides an apparatus for indicating LBT failure, and this apparatus is applied to a network device. Since the principle of solving the problem by this apparatus is similar to that of the method in Embodiment 2, the specific implementation thereof may refer to the implementation of the method described in Embodiment 2, and the same or related content will not be repeated.

[0265] Figure 19 is a schematic diagram of the apparatus for indicating LBT failure according to Embodiment 5 of the present application. As Figure 19 shown, the apparatus 1900 includes:

[0266] A configuration unit 1901, which configures upper layer parameters for a terminal device,

[0267] The upper layer parameters are used for the terminal device to determine whether the lower layer notifies or indicates the LBT failure to the upper layer.

[0268] In at least one embodiment of the present application, the upper layer parameters are further used for the terminal device to determine whether the upper layer sends a notification or an indication or a request to the lower layer.

[0269] In at least one embodiment of the present application, the terminal device determines whether the lower layer notifies or indicates an LBT failure to the upper layer according to a second condition and / or a third condition, or whether the lower layer starts or stops notifying or indicating an LBT failure to the upper layer. The second condition is that the upper layer parameters are configured and / or the capabilities are available, and / or the third condition is that the upper layer parameters are released or removed and / or the capabilities are not available.

[0270] In at least one embodiment of the present application, the upper layer parameters include at least one of the following parameters: parameters for continuous LBT failure detection for shared spectrum channel access; configuration parameters for scheduling requests; configuration parameters for configured grants.

[0271] In at least one embodiment of the present application, the upper layer parameters are cell-specific or terminal device-specific; and / or when dual connectivity (DC) is configured, the upper layer parameters are configured separately in the master cell group (MCG) and the secondary cell group (SCG); and / or when supplementary uplink (SUL) is configured, the upper layer parameters are configured separately for the supplementary uplink (SUL) and the normal uplink (NUL).

[0272] In this embodiment, the specific content of the upper layer parameters can be referred to the description in Embodiment 1, and will not be repeated here.

[0273] As can be seen from the above embodiments, the network device configures upper layer parameters for the terminal device to determine whether the lower layer notifies or indicates an LBT failure to the upper layer. In this way, the lower layer or the upper layer first determines whether the relevant conditions are met. Based on the judgment result, when the uplink transmission is blocked due to an LBT failure, it is determined whether the lower layer notifies or indicates an LBT failure to the upper layer, or it is determined whether the lower layer starts or stops notifying or indicating an LBT failure to the upper layer. In this way, the inter-layer interaction between the lower layer and the upper layer can be reduced, thereby reducing the power consumption of the terminal device.

[0274] Embodiment 6

[0275] An embodiment of the present application provides a terminal device, which includes a device for indicating an LBT failure as described in Embodiment 4.

[0276] Figure 20 It is a schematic block diagram of the system composition of the terminal device according to Embodiment 6 of the present application. As Figure 20 shown, the terminal device 2000 may include a processor 2010 and a memory 2020; the memory 2020 is coupled to the processor 2010. It should be noted that this figure is exemplary; other types of structures can also be used to supplement or replace this structure to implement telecommunication functions or other functions.

[0277] In one embodiment, the function of the device indicating LBT failure may be integrated into the processor 2010.

[0278] The processor 2010 may be configured to: when it is determined in the lower layer or the upper layer that the first condition and / or the second condition is satisfied, when the uplink transmission is blocked due to LBT failure, the lower layer notifies or indicates the LBT failure to the upper layer, or the lower layer starts to notify or indicate the LBT failure to the upper layer; and / or, when it is determined in the lower layer or the upper layer that the first condition is not satisfied and / or the third condition is satisfied, when the uplink transmission is blocked due to LBT failure, the lower layer does not notify or indicate the LBT failure to the upper layer, or the lower layer stops notifying or indicating the LBT failure to the upper layer.

[0279] For example, the first condition includes at least one of the following conditions: the terminal device is an NR-U terminal; the terminal device is an NR terminal; the terminal device is an NR-U terminal or an NR terminal; the uplink transmission or the terminal device performs shared spectrum channel access operation; the uplink transmission is an uplink transmission scheduled or configured by the network device; the uplink transmission is not licensed-assisted access (LAA) or enhanced licensed-assisted access (eLAA); the terminal device does not perform licensed-assisted access or enhanced licensed-assisted access; and the uplink transmission is not an automatic uplink transmission.

[0280] For example, the second condition is that the upper layer parameters are configured and / or the capabilities are available, and / or the third condition is that the upper layer parameters are released or removed and / or the capabilities are not available.

[0281] For example, the upper layer parameters include at least one of the following parameters: parameters for continuous LBT failure detection for shared spectrum channel access; configuration parameters for scheduling requests; configuration parameters for configured grants.

[0282] For example, the upper layer parameters are cell-specific or terminal device-specific; and / or, when dual connectivity (DC) is configured, the upper layer parameters are configured in the master cell group (MCG) and the secondary cell group (SCG) respectively; and / or, when supplementary uplink (SUL) is configured, the upper layer parameters are configured in the supplementary uplink (SUL) and the normal uplink (NUL) respectively.

[0283] For example, the capabilities are the capabilities of NR operation in the shared spectrum channel and / or the capabilities of continuous LBT detection and recovery.

[0284] For example, the capabilities are terminal device-specific, or cell-specific, or frequency band-specific or frequency band combination-specific.

[0285] For example, when the lower layer or upper layer determines that the first condition and / or the second condition is satisfied, and the lower layer determines that the fourth condition is satisfied, the lower layer notifies or indicates to the upper layer that the LBT has failed, or the lower layer starts to notify or indicate to the upper layer that the LBT has failed.

[0286] The fourth condition includes at least one of the following conditions: the LBT failure is any LBT failure; the LBT failure is an LBT failure performed for the transmission of a random access preamble; the LBT failure is an LBT failure performed for a configured grant; and the LBT failure is an LBT failure performed for a valid physical uplink control channel (PUCCH) resource for a scheduling request (SR).

[0287] For example, when the LBT failure is an LBT failure performed for the transmission of a random access preamble, the channel corresponding to the LBT is a physical random access channel (PRACH), and the LBT is an LBT performed on a random access resource (RA / PRACH occasion) indicated to the upper layer; when the LBT failure is an LBT failure performed for a configured grant, the channel corresponding to the LBT is a physical uplink shared channel (PUSCH), and the LBT is an LBT performed on the configured grant indicated to the upper layer.

[0288] For example, notifying or indicating the LBT failure includes: sending a notification or indication, or sending a notification or indication and the object on which the LBT is performed.

[0289] For example, the notification or indication sent is one of the following notifications or indications: a general notification or indication; a notification or indication for a specific purpose; a notification or indication sent from the lower layer to the upper layer through different service access points (SAPs) or channels or paths; and a notification or indication provided to different upper layer processes or functions or entities.

[0290] For example, the upper layer process or function or entity refers to at least one of the following: continuous LBT failure detection, random access procedure, random access preamble transmission, hybrid automatic repeat request (HARQ), transmission of an uplink configured grant, and scheduling request.

[0291] For example, the object on which the LBT is performed is characterized by an uplink resource or an index corresponding to the uplink resource.

[0292] For example, the uplink resource includes at least one of a random access resource (RA / PRACH occasion), a valid PUCCH resource for a scheduling request, and a configured grant.

[0293] For example, the processor 2010 can also be configured to: when the upper layer is notified or instructed, or when the upper layer is not notified or instructed, increment a counter by 1, keep it unchanged, or suspend it; or start or restart a timer; or trigger the terminal device or the upper layer to execute a process.

[0294] For example, the counter is one of the following counters: a counter for calculating the number of scheduling requests; a counter for applying or suspending power ramping; and a counter for continuous LBT failure detection.

[0295] For example, the timer is a timer for configuring grant (CG) or a timer for continuous LBT failure detection.

[0296] For example, the process triggered for the terminal device or the upper layer to execute is a random access process or a random access resource selection process.

[0297] For example, when the upper layer determines that the first condition and / or the second condition is satisfied, the processor 2010 can also be configured to: the upper layer sends a notification, an instruction, or a request to the lower layer, and based on the notification, the instruction, or the request, when the uplink transmission is blocked due to LBT failure, the lower layer notifies or instructs the upper layer of the LBT failure, or causes the lower layer to start notifying or instructing the upper layer of the LBT failure.

[0298] For example, when the upper layer determines that the first condition is not satisfied and / or the third condition is satisfied, the processor 2010 can also be configured to: the upper layer sends a notification, an instruction, or a request to the lower layer, and based on the notification, the instruction, or the request, when the uplink transmission is blocked due to LBT failure, the lower layer does not notify or instruct the upper layer of the LBT failure, or causes the lower layer to stop notifying or instructing the upper layer of the LBT failure.

[0299] For example, the notification, the instruction, or the request includes: sending a notification, an instruction, or a request, or sending a notification, an instruction, or a request and the object for performing LBT.

[0300] For example, the notification, the instruction, or the request sent is one of the following notifications, instructions, or requests: a general notification, instruction, or request; a notification, instruction, or request for a specific purpose; a notification, instruction, or request sent by the upper layer to the lower layer through different service access points (SAPs), channels, or paths; and a notification, instruction, or request from different upper layer processes, functions, or entities.

[0301] For example, the upper layer process, function, or entity refers to at least one of the following: continuous LBT failure detection, random access process, random access preamble transmission, hybrid automatic repeat request (HARQ), transmission of uplink configured grant, and scheduling request.

[0302] For example, the object performing LBT is characterized by uplink resources or an index corresponding to the uplink resources.

[0303] For example, the uplink resources include at least one of a random access resource (RA / PRACH occasion), a valid PUCCH resource for a scheduling request, and a configured grant.

[0304] For example, when maintaining a counter, that is, determining whether to increment a counter by 1, keep it unchanged, or suspend it, or when maintaining a timer, that is, determining whether to start or restart a timer, or when determining whether to trigger a terminal device or a higher layer to execute a process, the higher layer sends the notification, indication, or request to the lower layer.

[0305] For example, the counter is one of the following counters: a counter for calculating the number of scheduling requests; a counter for applying or suspending power ramping; and a counter for continuous LBT failure detection; the timer is a timer for a configured grant (CG) or a timer for continuous LBT failure detection; the process triggered for the terminal device or the higher layer to execute is a random access process or a random access resource selection process.

[0306] For example, the lower layer is the physical layer and the higher layer is the media access control (MAC) layer.

[0307] In another embodiment, the device indicating LBT failure can be separately configured from the processor 2010. For example, the device indicating LBT failure can be configured as a chip connected to the processor 2010, and the function of the device indicating LBT failure is implemented through the control of the processor 2010.

[0308] As Figure 20 shown, the terminal device 2000 may further include: a communication module 2030, an input unit 2040, a display 2050, and a power supply 2060. It should be noted that the terminal device 2000 does not necessarily have to include Figure 20 all the components shown in Figure 20 ; in addition, the terminal device 2000 may further include

[0309] As Figure 20 shown, the processor 2010 is sometimes also referred to as a controller or an operation control, and may include a microprocessor or other processor devices and / or logic devices. The processor 2010 receives inputs and controls the operations of the various components of the terminal device 2000.

[0310] Among them, the memory 2020 can be, for example, one or more of a buffer, a flash memory, a hard drive, a removable medium, a volatile memory, a non-volatile memory, or other suitable devices. It can store various data, and can also store programs for executing relevant information. And the processor 2010 can execute the program stored in the memory 2020 to implement information storage or processing, etc. The functions of other components are similar to those in the prior art and will not be elaborated here. Each component of the terminal device 2000 can be implemented by dedicated hardware, firmware, software, or a combination thereof without departing from the scope of the present invention.

[0311] As can be seen from the above embodiments, the lower layer or the upper layer first determines whether relevant conditions are met. Based on the judgment result, when the uplink transmission is blocked due to LBT failure, it is determined whether the lower layer notifies or indicates the LBT failure to the upper layer, or determines whether the lower layer starts or stops notifying or indicating the LBT failure to the upper layer. In this way, the inter-layer interaction between the lower layer and the upper layer can be reduced, thereby reducing the power consumption of the terminal device.

[0312] Embodiment 7

[0313] The embodiment of the present application provides a network device, which includes a device for indicating LBT failure as described in Embodiment 5.

[0314] Figure 21 It is a schematic block diagram of the system composition of the network device according to Embodiment 7 of the present application. As Figure 21 shown, the network device 2100 may include: a processor 2110 and a memory 2120; the memory 2120 is coupled to the processor 2110. The memory 2120 can store various data; in addition, it stores a program 2130 for information processing, and executes the program 2130 under the control of the processor 2110 to receive various information sent by the terminal device and send various information to the terminal device.

[0315] In one embodiment, the function of the device for indicating LBT failure can be integrated into the processor 2110. Among them, the processor 2110 can be configured to: configure high-layer parameters for the terminal device, and the high-layer parameters are used for the terminal device to determine whether the lower layer notifies or indicates the LBT failure to the upper layer.

[0316] For example, the high-layer parameters are also used for the terminal device to determine whether the upper layer sends a notification, an indication, or a request to the lower layer.

[0317] For example, the high-layer parameters include at least one of the following parameters: parameters for continuous LBT failure detection for shared spectrum channel access; configuration parameters for scheduling requests; configuration parameters for configured grants.

[0318] For example, the high-layer parameter is cell-specific or terminal device-specific; and / or, when dual connectivity (DC) is configured, the high-layer parameter is configured separately for the master cell group (MCG) and the secondary cell group (SCG); and / or, when supplementary uplink (SUL) is configured, the high-layer parameter is configured separately for the supplementary uplink (SUL) and the normal uplink (NUL).

[0319] In another embodiment, the device for indicating LBT failure may be configured separately from the processor 2110. For example, the device for indicating LBT failure may be configured as a chip connected to the processor 2110, and the function of the device for indicating LBT failure is implemented through the control of the processor 2110.

[0320] In addition, as Figure 21 shown, the network device 2100 may further include: a transceiver 2140, an antenna 2150, etc.; among them, the functions of the above components are similar to those in the prior art and will not be elaborated here. It should be noted that the network device 2100 does not necessarily have to include Figure 21 all the components shown in Figure 21 ; in addition, the network device 2100 may further include components not shown in

[0321] which can refer to the prior art.

[0321] As can be seen from the above embodiments, the network device configures high-layer parameters for the terminal device to determine whether the lower layer notifies or indicates LBT failure to the high layer. In this way, the lower layer or the high layer first determines whether the relevant conditions are met. Based on the judgment result, when the uplink transmission is blocked due to LBT failure, it is determined whether the lower layer notifies or indicates LBT failure to the high layer, or it is determined whether the lower layer starts or stops notifying or indicating LBT failure to the high layer. In this way, the inter-layer interaction between the lower layer and the high layer can be reduced, thereby reducing the power consumption of the terminal device.

[0322] Embodiment 8

[0323] An embodiment of the present application provides a communication system, including the terminal device according to Embodiment 6 and / or the network device according to Embodiment 7.

[0324] For example, the structure of the communication system may refer to Figure 1 , as Figure 1 shown, the communication system 100 includes a network device 101 and a terminal device 102. The terminal device 102 is the same as the terminal device described in Embodiment 6, and the network device 101 is the same as the network device described in Embodiment 7. The repeated content will not be elaborated.

[0325] The above-described apparatus and method of the present invention can be implemented by hardware, or by a combination of hardware and software. The present invention relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or constituent components described above, or enables the logic component to implement the various methods or steps described above. The logic component is, for example, a field-programmable logic component, a microprocessor, a processor used in a computer, etc. The present invention also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0326] The method / apparatus described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, Figure 18 One or more of the functional block diagrams shown in and / or one or more combinations of the functional block diagrams can correspond to each software module of the computer program flow, and can also correspond to each hardware module. These software modules can respectively correspond to Figure 4 each of the steps shown in. These hardware modules can be implemented, for example, by using a field-programmable gate array (FPGA) to solidify these software modules.

[0327] The software module can be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium can be coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium can be a component of the processor. The processor and the storage medium can be located in an ASIC. The software module can be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a larger-capacity MEGA-SIM card or a large-capacity flash device, the software module can be stored in the MEGA-SIM card or the large-capacity flash device.

[0328] Regarding one or more of the functional blocks described in the appendix Figure 18 and / or one or more combinations of the functional blocks, it can be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof for performing the functions described in the present invention. Regarding the appendix Figure 18One or more of the described functional blocks and / or one or more combinations of functional blocks can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication combination with a DSP, or any other such configuration.

[0329] The present invention has been described in connection with specific embodiments, but those skilled in the art should understand that these descriptions are exemplary and not a limitation on the protection scope of the present invention. Those skilled in the art can make various variations and modifications to the present invention according to the spirit and principle of the present invention, and these variations and modifications are also within the scope of the present invention.

[0330] According to various embodiments disclosed in the embodiments of the present application, the following appendices are also disclosed:

[0331] Appendix 1

[0332] 1. A device for indicating LBT failure, the device being applied to a terminal device, the device comprising:

[0333] A first indication unit, which is used for, when it is judged in a lower layer or a higher layer that a first condition and / or a second condition is satisfied, when an uplink transmission is blocked due to LBT failure, the lower layer notifies or indicates the LBT failure to the higher layer, or the lower layer starts to notify or indicate the LBT failure to the higher layer; and / or,

[0334] A second indication unit, which is used for, when it is judged in a lower layer or a higher layer that the first condition is not satisfied and / or a third condition is satisfied, when an uplink transmission is blocked due to LBT failure, the lower layer does not notify or indicate the LBT failure to the higher layer, or the lower layer stops notifying or indicating the LBT failure to the higher layer.

[0335] 2. The device according to Appendix 1, wherein the first condition includes at least one of the following conditions:

[0336] The terminal device is an NR-U terminal;

[0337] The terminal device is an NR terminal;

[0338] The terminal device is an NR-U terminal or an NR terminal;

[0339] The uplink transmission or the terminal device performs shared spectrum channel access operation;

[0340] The uplink transmission is an uplink transmission scheduled or configured by a network device;

[0341] The uplink transmission is not licensed-assisted access (LAA) or enhanced licensed-assisted access (eLAA);

[0342] The terminal device does not perform licensed-assisted access or enhanced licensed-assisted access; and

[0343] The uplink transmission is not an automatic uplink transmission.

[0344] 3. The apparatus according to Note 1, wherein

[0345] The second condition is that high-layer parameters are configured and / or capabilities are available, and / or

[0346] The third condition is that the high-layer parameters are released or removed and / or capabilities are not available.

[0347] 4. The apparatus according to Note 3, wherein the high-layer parameters include at least one of the following parameters:

[0348] Parameters for continuous LBT failure detection for shared spectrum channel access;

[0349] Configuration parameters for scheduling requests;

[0350] Configuration parameters for configured grants.

[0351] 5. The apparatus according to Note 3 or 4, wherein

[0352] The high-layer parameters are cell-specific or terminal-device-specific; and / or

[0353] When dual connectivity (DC) is configured, the high-layer parameters are configured in the master cell group (MCG) and the secondary cell group (SCG) respectively; and / or

[0354] When supplementary uplink (SUL) is configured, the high-layer parameters are configured for the supplementary uplink (SUL) and the normal uplink (NUL) respectively.

[0355] 6. The apparatus according to Note 3, wherein

[0356] The capabilities are the capabilities of NR operations in a shared spectrum channel and / or the capabilities of continuous LBT detection and recovery.

[0357] 7. The apparatus according to Note 3 or 6, wherein

[0358] The capabilities are terminal-device-specific, or cell-specific, or band-specific or band-combination-specific.

[0359] 8. The apparatus according to Note 1, wherein when the lower layer or the higher layer determines that the first condition and / or the second condition are satisfied, and the lower layer determines that the fourth condition is satisfied, the lower layer notifies or indicates the LBT failure to the higher layer, or the lower layer starts to notify or indicate the LBT failure to the higher layer,

[0360] The fourth condition includes at least one of the following conditions:

[0361] The LBT failure is any LBT failure;

[0362] The LBT failure is an LBT failure performed for the transmission of a random access preamble;

[0363] The LBT failure is an LBT failure performed for a configured grant; and

[0364] The LBT failure is an LBT failure performed for a valid physical uplink control channel (PUCCH) resource of a scheduling request (SR).

[0365] 9. The apparatus according to Note 8, wherein

[0366] When the LBT failure is an LBT failure performed for the transmission of a random access preamble, the channel corresponding to the LBT is a physical random access channel (PRACH), and the LBT is an LBT performed on a random access resource (RA / PRACH occasion) indicated by a higher layer;

[0367] When the LBT failure is an LBT failure performed for a configured grant, the channel corresponding to the LBT is a physical uplink shared channel (PUSCH), and the LBT is an LBT performed on a configured grant indicated by a higher layer.

[0368] 10. The apparatus according to Note 1, wherein the first indication unit is configured to send a notification or an indication, or send a notification or an indication and an object for performing LBT.

[0369] 11. The apparatus according to Note 10, wherein the sent notification or indication is one of the following notifications or indications:

[0370] A general notification or indication;

[0371] A notification or indication for a specific purpose;

[0372] A notification or indication sent from a lower layer to a higher layer through different service access points (SAPs) or channels or paths; and

[0373] A notification or indication provided to different higher layer processes or functions or entities.

[0374] 12. The apparatus according to Note 11, wherein

[0375] The high-layer process or function or entity refers to at least one of the following: continuous LBT failure detection, random access process, random access preamble transmission, hybrid automatic repeat request (HARQ), transmission of uplink configured grant, and scheduling request.

[0376] 13. The apparatus according to item 10 of the annex, wherein

[0377] The object performing LBT is characterized by an uplink resource or an index corresponding to the uplink resource.

[0378] 14. The apparatus according to item 13 of the annex, wherein

[0379] The uplink resource includes at least one of a random access resource (RA / PRACH occasion), a valid PUCCH resource for a scheduling request, and a configured grant.

[0380] 15. The apparatus according to item 1 of the annex, wherein the apparatus further comprises:

[0381] A first processing unit, which is configured to increment by 1 or remain unchanged or suspend a counter when the high layer is notified or instructed, or when the high layer is not notified or instructed; or start or restart a timer; or trigger the terminal device or the high layer to execute a process.

[0382] 16. The apparatus according to item 15 of the annex, wherein the counter is one of the following counters:

[0383] A counter for calculating the number of scheduling requests;

[0384] A counter for applying or suspending power ramping; and

[0385] A counter for continuous LBT failure detection.

[0386] 17. The apparatus according to item 15 of the annex, wherein

[0387] The timer is a timer for configured grant (CG) or a timer for continuous LBT failure detection.

[0388] 18. The apparatus according to item 15 of the annex, wherein

[0389] The process triggered for the terminal device or the high layer to execute is a random access process or a random access resource selection process.

[0390] 19. The apparatus according to any one of items 1 - 18 of the annex, wherein

[0391] When the high layer determines that the first condition and / or the second condition is satisfied, the apparatus further comprises:

[0392] A third indication unit, which is used for a higher layer to send a notification or indication or request to a lower layer; based on the notification or indication or request, when an uplink transmission is blocked due to an LBT failure, the lower layer notifies or indicates the LBT failure to the higher layer, or the lower layer starts to notify or indicate the LBT failure to the higher layer.

[0393] 20. The apparatus according to any one of Appendices 1-19, wherein

[0394] When it is determined by the higher layer that the first condition is not satisfied and / or the third condition is satisfied, the apparatus further includes:

[0395] A fourth indication unit, which is used for a higher layer to send a notification or indication or request to a lower layer; based on the notification or indication or request, when an uplink transmission is blocked due to an LBT failure, the lower layer does not notify or indicate the LBT failure to the higher layer, or the lower layer stops notifying or indicating the LBT failure to the higher layer.

[0396] 21. The apparatus according to Appendix 19 or 20, wherein the fourth indication unit is used to send a notification or indication or request, or to send a notification or indication or request and an object for performing LBT.

[0397] 22. The apparatus according to Appendix 21, wherein the notification or indication or request sent is one of the following notifications or indications or requests:

[0398] A general notification or indication or request;

[0399] A specific-purpose notification or indication or request;

[0400] A notification or indication or request sent by the higher layer to the lower layer through different service access points (SAPs) or channels or paths; and

[0401] A notification or indication or request from different higher layer processes or functions or entities.

[0402] 23. The apparatus according to Appendix 22, wherein

[0403] The higher layer process or function or entity refers to at least one of the following: continuous LBT failure detection, random access process, random access preamble transmission, hybrid automatic repeat request (HARQ), uplink configured grant transmission, and scheduling request.

[0404] 24. The apparatus according to Appendix 21, wherein

[0405] The object for performing LBT is characterized by an uplink resource or an index corresponding to the uplink resource.

[0406] 25. The apparatus according to Appendix 24, wherein

[0407] The uplink resources include at least one of resources for random access (RA / PRACH occasion), a valid PUCCH resource for a scheduling request, and configured grants.

[0408] 26. The apparatus according to paragraph 19 or 20 of the annex, wherein

[0409] When maintaining a counter, that is, determining whether to increment a counter by 1, keep it unchanged, or suspend it, or when maintaining a timer, that is, determining whether to start or restart a timer, or when determining whether to trigger a terminal device or a higher layer to execute a process, the third indication unit or the fourth indication unit is used for the higher layer to send the notification, indication, or request to the lower layer.

[0410] 27. The apparatus according to paragraph 26 of the annex, wherein

[0411] The counter is one of the following counters: a counter for calculating the number of scheduling requests; a counter for applying or suspending power ramping; and a counter for continuous LBT failure detection;

[0412] The timer is a timer for configured grant (CG) or a timer for continuous LBT failure detection;

[0413] The process triggered for the terminal device or the higher layer to execute is a random access process or a random access resource selection process.

[0414] 28. The apparatus according to any one of paragraphs 1 - 27 of the annex, wherein

[0415] The lower layer is the physical layer, and the higher layer is the medium access control (MAC) layer.

[0416] 29. An apparatus for indicating LBT failure, the apparatus is applied to a network device, and the apparatus includes:

[0417] A configuration unit that configures high - layer parameters for a terminal device,

[0418] The high - layer parameters are used for the terminal device to determine whether the lower layer notifies or indicates LBT failure to the higher layer.

[0419] 30. The apparatus according to paragraph 29 of the annex, wherein

[0420] The high - layer parameters are further used for the terminal device to determine whether the higher layer sends a notification, indication, or request to the lower layer.

[0421] 31. The apparatus according to paragraph 29 of the annex, wherein the high - layer parameters for the terminal device to determine whether the lower layer notifies or indicates LBT failure include:

[0422] The terminal device determines whether the lower layer notifies or indicates the LBT failure to the upper layer, or whether the lower layer starts or stops notifying or indicating the LBT failure to the upper layer according to the second condition and / or the third condition when the uplink transmission is blocked due to LBT failure.

[0423] The second condition is that the upper layer parameters are configured and / or the capabilities are available, and / or the third condition is that the upper layer parameters are released or removed and / or the capabilities are not available.

[0424] 32. The apparatus according to any one of Appendices 29 - 31, wherein

[0425] The upper layer parameters include at least one of the following parameters:

[0426] Parameters for continuous LBT failure detection for shared spectrum channel access;

[0427] Configuration parameters for scheduling requests;

[0428] Configuration parameters for configured grants.

[0429] 33. The apparatus according to any one of Appendices 29 - 32, wherein

[0430] The upper layer parameters are cell - specific or terminal - device - specific; and / or

[0431] When dual - connectivity (DC) is configured, the upper layer parameters are configured separately in the master cell group (MCG) and the secondary cell group (SCG); and / or

[0432] When supplementary uplink (SUL) is configured, the upper layer parameters are configured separately for the supplementary uplink (SUL) and the normal uplink (NUL).

[0433] 34. A terminal device, the terminal device includes the apparatus according to any one of Appendices 1 - 28.

[0434] 35. A network device, the network device includes the apparatus according to any one of Appendices 29 - 33.

[0435] 36. A communication system, the communication system includes the terminal device according to Appendix 34 and / or the network device according to Appendix 35.

[0436] Appendix II

[0437] 1. A method for indicating LBT failure, the method is applied to a terminal device, and the method includes:

[0438] When it is determined in the lower layer or the upper layer that the first condition and / or the second condition is satisfied, when the uplink transmission is blocked due to LBT failure, the lower layer notifies or indicates the LBT failure to the upper layer, or the lower layer starts to notify or indicate the LBT failure to the upper layer; and / or,

[0439] When it is determined in the lower layer or the upper layer that the first condition is not satisfied and / or the third condition is satisfied, when the uplink transmission is blocked due to LBT failure, the lower layer does not notify or indicate the LBT failure to the upper layer, or the lower layer stops notifying or indicating the LBT failure to the upper layer.

[0440] 2. The method according to note 1, wherein the first condition includes at least one of the following conditions:

[0441] The terminal device is an NR-U terminal;

[0442] The terminal device is an NR terminal;

[0443] The terminal device is an NR-U terminal or an NR terminal;

[0444] The uplink transmission or the terminal device performs a shared spectrum channel access operation;

[0445] The uplink transmission is an uplink transmission scheduled or configured by a network device;

[0446] The uplink transmission is not licensed-assisted access (LAA) or enhanced licensed-assisted access (eLAA);

[0447] The terminal device does not perform licensed-assisted access or enhanced licensed-assisted access; and

[0448] The uplink transmission is not an automatic uplink transmission.

[0449] 3. The method according to note 3, wherein

[0450] The second condition is that upper layer parameters are configured and / or capabilities are available, and / or,

[0451] The third condition is that upper layer parameters are released or removed and / or capabilities are not available.

[0452] 4. The method according to note 3, wherein the upper layer parameters include at least one of the following parameters:

[0453] Parameters for continuous LBT failure detection for shared spectrum channel access;

[0454] Configuration parameters for scheduling requests;

[0455] Configuration parameters for configured grants.

[0456] 5. The method according to Note 3 or 4, wherein,

[0457] the high-layer parameter is cell-specific or terminal-device-specific; and / or,

[0458] when dual connectivity (DC) is configured, the high-layer parameter is configured separately in the master cell group (MCG) and the secondary cell group (SCG); and / or,

[0459] when supplementary uplink (SUL) is configured, the high-layer parameter is configured separately for the supplementary uplink (SUL) and the normal uplink (NUL).

[0460] 6. The method according to Note 3, wherein,

[0461] the capability is the capability of NR operation in a shared spectrum channel and / or the capability of continuous LBT detection and recovery.

[0462] 7. The method according to Note 3 or 6, wherein,

[0463] the capability is terminal-device-specific, or cell-specific, or band-specific or band-combination-specific.

[0464] 8. The method according to Note 1, wherein when the lower layer or the higher layer determines that the first condition and / or the second condition are satisfied, and the lower layer determines that the fourth condition is satisfied, the lower layer notifies or indicates LBT failure to the higher layer, or the lower layer starts to notify or indicate LBT failure to the higher layer,

[0465] the fourth condition includes at least one of the following conditions:

[0466] the LBT failure is any LBT failure;

[0467] the LBT failure is the LBT failure performed for the transmission of the random access preamble;

[0468] the LBT failure is the LBT failure performed for the configured grant; and

[0469] the LBT failure is the LBT failure performed for a valid physical uplink control channel (PUCCH) resource of a scheduling request (SR).

[0470] 9. The method according to Note 8, wherein,

[0471] when the LBT failure is the LBT failure performed for the transmission of the random access preamble, the channel corresponding to the LBT is the physical random access channel (PRACH), and the LBT is the LBT performed on the random access resource (RA / PRACH occasion) indicated to the higher layer;

[0472] When the LBT failure is an LBT failure performed for a configured grant, the channel corresponding to the LBT is a Physical Uplink Shared Channel (PUSCH), and the LBT is an LBT for a configured grant indicated by a higher layer.

[0473] 10. The method according to appendix 1, wherein the notification or indication of the LBT failure includes:

[0474] Sending a notification or indication, or, sending a notification or indication and the object performing the LBT.

[0475] 11. The method according to appendix 10, wherein the notification or indication sent is one of the following notifications or indications:

[0476] A general notification or indication;

[0477] A notification or indication for a specific purpose;

[0478] A notification or indication sent from a lower layer to a higher layer through different Service Access Points (SAPs) or channels or paths; and

[0479] A notification or indication provided to different higher layer processes or functions or entities.

[0480] 12. The method according to appendix 11, wherein,

[0481] The higher layer process or function or entity refers to at least one of the following: continuous LBT failure detection, random access process, random access preamble transmission, Hybrid Automatic Repeat Request (HARQ), transmission of an uplink configured grant, and scheduling request.

[0482] 13. The method according to appendix 10, wherein,

[0483] The object performing the LBT is characterized by an uplink resource or an index corresponding to the uplink resource.

[0484] 14. The method according to appendix 13, wherein,

[0485] The uplink resource includes at least one of a random access resource (RA / PRACH occasion), a valid PUCCH resource for a scheduling request, and a configured grant.

[0486] 15. The method according to appendix 1, wherein the method further includes:

[0487] When the higher layer is notified or indicated, or, when the higher layer is not notified or indicated,

[0488] A counter is incremented by 1, remains unchanged, or is suspended; alternatively, a timer is started or restarted; or a terminal device or a higher layer is triggered to execute a process.

[0489] 16. The method according to item 15 of the appendix, wherein the counter is one of the following counters:

[0490] A counter for calculating the number of scheduling requests;

[0491] A counter for applying or suspending power ramping; and

[0492] A counter for continuous LBT failure detection.

[0493] 17. The method according to item 15 of the appendix, wherein

[0494] The timer is a timer for configuring grants (CG) or a timer for continuous LBT failure detection.

[0495] 18. The method according to item 15 of the appendix, wherein

[0496] The process triggered for the terminal device or the higher layer to execute is a random access process or a random access resource selection process.

[0497] 19. The method according to any one of items 1-18 of the appendix, wherein

[0498] When the higher layer determines that the first condition and / or the second condition is satisfied, the method further includes:

[0499] The higher layer sends a notification, an indication, or a request to the lower layer; based on the notification, the indication, or the request, when the uplink transmission is blocked due to an LBT failure, the lower layer notifies or indicates the LBT failure to the higher layer, or the lower layer starts to notify or indicate the LBT failure to the higher layer.

[0500] 20. The method according to any one of items 1-19 of the appendix, wherein

[0501] When the higher layer determines that the first condition is not satisfied and / or the third condition is satisfied, the method further includes:

[0502] The higher layer sends a notification, an indication, or a request to the lower layer; based on the notification, the indication, or the request, when the uplink transmission is blocked due to an LBT failure, the lower layer does not notify or indicate the LBT failure to the higher layer, or the lower layer stops notifying or indicating the LBT failure to the higher layer.

[0503] 21. The method according to item 19 or 20 of the appendix, wherein the notification, the indication, or the request includes:

[0504] Send a notification or an indication or a request, or, an object that sends a notification or an indication or a request and performs LBT.

[0505] 22. The method according to item 21, wherein the notification or indication or request sent is one of the following notifications or indications or requests:

[0506] A general notification or indication or request;

[0507] A notification or indication or request for a specific purpose;

[0508] A notification or indication or request sent from a higher layer to a lower layer through different service access points (SAPs) or channels or paths; and

[0509] A notification or indication or request from different higher layer processes or functions or entities.

[0510] 23. The method according to item 22, wherein

[0511] The higher layer process or function or entity refers to at least one of the following: continuous LBT failure detection, random access process, random access preamble transmission, hybrid automatic repeat request (HARQ), transmission of uplink configured grant, and scheduling request.

[0512] 24. The method according to item 21, wherein

[0513] The object that performs LBT is characterized by an uplink resource or an index corresponding to the uplink resource.

[0514] 25. The method according to item 24, wherein

[0515] The uplink resource includes at least one of a random access resource (RA / PRACH occasion), a valid PUCCH resource for a scheduling request, and a configured grant.

[0516] 26. The method according to item 19 or 20, wherein

[0517] When maintaining a counter, that is, determining whether to increment a counter or keep it unchanged or suspend it, or, when maintaining a timer, that is, determining whether to start or restart a timer, or, when determining whether to trigger a terminal device or a higher layer to perform a process, the higher layer sends the notification or indication or request to the lower layer.

[0518] 27. The method according to item 26, wherein

[0519] The counter is one of the following counters: a counter for calculating the number of scheduling requests; a counter for applying or suspending power ramping; and a counter for continuous LBT failure detection;

[0520] The timer is a timer for configuring grant (CG) or a timer for continuous LBT failure detection;

[0521] The process triggered by the terminal device or the higher layer is a random access process or a random access resource selection process.

[0522] 28. The method according to any one of Appendices 1-27, wherein

[0523] The lower layer is a physical layer and the higher layer is a media access control (MAC) layer.

[0524] 29. A method for indicating LBT failure, which is applied to a network device, and the method includes:

[0525] Configuring higher layer parameters for the terminal device,

[0526] The higher layer parameters are used for the terminal device to determine whether the lower layer notifies or indicates LBT failure to the higher layer.

[0527] 30. The method according to Appendix 29, wherein

[0528] The higher layer parameters are further used for the terminal device to determine whether the higher layer sends a notification or indication or request to the lower layer.

[0529] 31. The method according to Appendix 29, wherein the higher layer parameters are used for the terminal device to determine whether the lower layer notifies or indicates LBT failure to the higher layer, including:

[0530] The terminal device determines whether the lower layer notifies or indicates LBT failure to the higher layer, or whether the lower layer starts or stops notifying or indicating LBT failure to the higher layer according to the second condition and / or the third condition when the uplink transmission is blocked due to LBT failure,

[0531] The second condition is that the higher layer parameters are configured and / or the capabilities are available, and / or the third condition is that the higher layer parameters are released or removed and / or the capabilities are not available.

[0532] 32. The method according to any one of Appendices 29-31, wherein

[0533] The higher layer parameters include at least one of the following parameters:

[0534] Parameters for continuous LBT failure detection for shared spectrum channel access;

[0535] Configuration parameters for scheduling requests;

[0536] Configuration parameters for configured grant.

[0537] 33. The method according to any one of Appendices 29 - 32, wherein,

[0538] the high - layer parameter is cell - specific or terminal - device - specific; and / or,

[0539] when dual - connectivity (DC) is configured, the high - layer parameter is configured separately for the master cell group (MCG) and the secondary cell group (SCG); and / or,

[0540] when supplementary uplink (SUL) is configured, the high - layer parameter is configured separately for the supplementary uplink (SUL) and the normal uplink (NUL).

Claims

1. An apparatus for indicating LBT failure, the apparatus being applied to a terminal device, the apparatus comprising: A first indication unit, which is used to determine at the physical layer that when the terminal device satisfies the condition of performing shared spectrum channel access operation, and the uplink transmission is the uplink transmission scheduled or configured by the network device, and the uplink transmission is not licensed-assisted access (LAA) or enhanced licensed-assisted access (eLAA), when the uplink transmission is blocked due to LBT failure, the lower layer notifies the upper layer of the LBT failure; And A first processing unit, which is used to trigger the upper layer to execute a random access resource selection process when the upper layer is notified.

2. The apparatus according to claim 1, wherein, The first indication unit is used to, when the terminal device performs a shared spectrum channel access operation and the uplink transmission is scheduled or configured by the gNB, when the uplink transmission is blocked due to LBT failure, the lower layer notifies the upper layer of the LBT failure.

3. The apparatus according to claim 1, wherein, The situation further includes: High-layer parameters are configured and / or capabilities are available.

4. The apparatus according to claim 3, wherein, The high-layer parameters include at least one of the following parameters: Parameters for continuous LBT failure detection for shared spectrum channel access; Configuration parameters for scheduling requests; Configuration parameters for configured grants.

5. The apparatus according to claim 3, wherein, The capability is the capability of NR operation in the shared spectrum channel and / or the capability of continuous LBT detection and recovery.

6. The apparatus according to claim 3, wherein, The capability is terminal-device specific, or cell specific, or frequency-band specific or frequency-band combination specific.

7. The apparatus according to claim 1, wherein, The first indication unit is further used to send a notification or indication, or send a notification or indication and the object for performing LBT.

8. The apparatus according to claim 7, wherein, The sent notification or indication is one of the following notifications or indications: General notification or indication; Notification or indication for specific purposes; Notification or indication sent by the lower layer to the upper layer through different service access points (SAPs) or channels or paths; and Notification or indication provided to different high-layer processes or functions or entities.

9. The apparatus according to claim 1, wherein, When the upper layer is not notified, increment the timer SR_COUNTER by 1, or start or restart the configured grant (CG) timer.

10. The apparatus according to claim 1, wherein, The apparatus further includes: A second indication unit, which is used to, when the lower layer or the upper layer determines that the first condition is not satisfied and / or the third condition is satisfied, when the uplink transmission is blocked due to LBT failure, the lower layer does not notify or indicate the LBT failure to the upper layer, or the lower layer stops notifying or indicating the LBT failure to the upper layer.

11. The apparatus according to claim 10, wherein, The first condition includes at least one of the following conditions: The terminal device is an NR-U terminal; The terminal device is an NR terminal; The terminal device is an NR-U terminal or an NR terminal; The uplink transmission or the terminal device performs a shared spectrum channel access operation; The uplink transmission is the uplink transmission scheduled or configured by the network device; The uplink transmission is not licensed-assisted access (LAA) or enhanced licensed-assisted access (eLAA); The terminal device is not performing licensed-assisted access or enhanced licensed-assisted access; And The uplink transmission is not an automatic uplink transmission.

12. The device according to claim 1, wherein, For the first indication unit, the situation further includes that when the lower layer determines that the fourth condition is satisfied, the lower layer notifies or indicates the LBT failure to the upper layer, or the lower layer starts to notify or indicate the LBT failure to the upper layer. The fourth condition includes at least one of the following conditions: The LBT failure is any LBT failure; The LBT failure is an LBT failure performed for the transmission of a random access preamble; The LBT failure is an LBT failure performed for a configured grant; and The LBT failure is an LBT failure performed for a valid physical uplink control channel (PUCCH) resource of a scheduling request (SR).

13. The device according to claim 1, wherein, The apparatus further includes: A third indication unit, configured to send a notification, an indication, or a request from a higher layer to a lower layer; based on the notification, the indication, or the request, when uplink transmission is blocked due to an LBT failure, the lower layer notifies or indicates the LBT failure to the higher layer, or the lower layer starts to notify or indicate the LBT failure to the higher layer.

14. The device according to claim 1, wherein, The apparatus further includes: A fourth indication unit, configured to send a notification, an indication, or a request from a higher layer to a lower layer; based on the notification, the indication, or the request, when uplink transmission is blocked due to an LBT failure, the lower layer does not notify or indicate the LBT failure to the higher layer, or the lower layer stops notifying or indicating the LBT failure to the higher layer.

15. A device for indicating LBT failure, the device being applied to a network device, the device comprising: A configuration unit, configured to configure high-layer parameters for the terminal device, The high-layer parameters are used for the terminal device to determine whether the lower layer notifies or indicates the LBT failure to the higher layer. Wherein, when it is determined at the physical layer that the terminal device satisfies the shared spectrum channel access operation, and the uplink transmission is an uplink transmission scheduled or configured by the network device, and the uplink transmission is not licensed-assisted access (LAA) or enhanced licensed-assisted access (eLAA), when the uplink transmission is blocked due to an LBT failure, the terminal device notifies the LBT failure to the higher layer through the lower layer; and when the higher layer is notified, the terminal device triggers the higher layer to execute a random access resource selection process.

16. The device according to claim 15, wherein, The high-layer parameters are further used for the terminal device to determine whether the higher layer sends a notification, an indication, or a request to the lower layer.

17. The device according to claim 15, wherein, The high-layer parameters for the terminal device to determine whether the lower layer notifies or indicates the LBT failure to the higher layer include: The terminal device determines whether the lower layer notifies or indicates the LBT failure to the higher layer, or whether the lower layer starts or stops notifying or indicating the LBT failure to the higher layer when the uplink transmission is blocked due to an LBT failure according to the second condition and / or the third condition, The second condition is that the high-layer parameters are configured and / or the capabilities are available, and / or the third condition is that the high-layer parameters are released or removed and / or the capabilities are not available.

18. The device according to claim 15, wherein, The high-layer parameters include at least one of the following parameters: Parameters for continuous LBT failure detection for shared spectrum channel access; Configuration parameters for scheduling requests; Configuration parameters for configured grants.

19. The device according to claim 15, wherein, The high-layer parameters are cell-specific or terminal device-specific; and / or, When dual connectivity (DC) is configured, the high-layer parameters are configured in the master cell group (MCG) and the secondary cell group (SCG) respectively; and / or, When supplementary uplink (SUL) is configured, the high-layer parameters are configured in the supplementary uplink (SUL) and the normal uplink (NUL) respectively.

20. A communication system, the communication system comprising a terminal device and / or a network device, the terminal device comprises the device according to claim 1, and / or, the network device comprises the device according to claim 15.

Images