WO2021203395A1 - 指示lbt失败的方法及装置 - Google Patents

指示lbt失败的方法及装置 Download PDF

Info

Publication number
WO2021203395A1
WO2021203395A1 PCT/CN2020/084072 CN2020084072W WO2021203395A1 WO 2021203395 A1 WO2021203395 A1 WO 2021203395A1 CN 2020084072 W CN2020084072 W CN 2020084072W WO 2021203395 A1 WO2021203395 A1 WO 2021203395A1
Authority
WO
WIPO (PCT)
Prior art keywords
lbt failure
lbt
lower layer
condition
higher layer
Prior art date
Application number
PCT/CN2020/084072
Other languages
English (en)
French (fr)
Inventor
贾美艺
蒋琴艳
李国荣
路杨
Original Assignee
富士通株式会社
贾美艺
蒋琴艳
李国荣
路杨
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社, 贾美艺, 蒋琴艳, 李国荣, 路杨 filed Critical 富士通株式会社
Priority to JP2022554269A priority Critical patent/JP7380907B2/ja
Priority to PCT/CN2020/084072 priority patent/WO2021203395A1/zh
Priority to CN202080098279.5A priority patent/CN115245036A/zh
Publication of WO2021203395A1 publication Critical patent/WO2021203395A1/zh
Priority to US17/939,038 priority patent/US20230007693A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H04W74/0825—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA] with collision detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/115—Grant-free or autonomous transmission

Definitions

  • the invention relates to the field of communications.
  • LBT Listen Before Talk
  • DMTC Discovery RS Measurement Timing Configuration
  • NR-U new wireless
  • a radio resource control (Radio Resource Control, RRC) layer may configure a higher layer, for example, a MAC entity of the MAC layer, to configure a recovery process from a continuous LBT failure.
  • the detection of continuous LBT failure is performed on each upstream BWP (Bandwidth Part).
  • a counter and a timer are introduced. When an upstream LBT failure occurs, the timer is started or restarted.
  • the counter is incremented by 1
  • the count value of the counter exceeds the preset value, the continuous LBT fails to be triggered.
  • the timer expires, the counter is reset. This process can be regarded as a part or a step of the continuous (uplink) LBT failure detection process or the continuous (uplink) LBT failure detection process.
  • the uplink transmission including data, control information and reference signals may occur at any time. If the lower layer informs or instructs the upper layer whenever the uplink transmission is blocked due to LBT failure, it will greatly increase the interaction between the lower layer and the upper layer. , And increase the power consumption of terminal equipment.
  • embodiments of the present application provide a method and device for indicating LBT failure.
  • a device for indicating LBT failure the device is applied to a terminal device, and the device includes: a first indicating unit that determines whether the first condition and/ Or under the second condition, when the 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, the second indicating unit, which In the case that the lower layer or the upper layer judges that the first condition and/or the third condition are not satisfied, 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 reporting to the higher layer Notify or indicate that LBT has failed.
  • a device for indicating LBT failure is applied to a network device, and the device includes: a configuration unit that configures a terminal device with high-level parameters, where the high-level parameters are used for The terminal device determines whether the lower layer informs or indicates the LBT failure to the higher layer.
  • a terminal device is provided, and the terminal device includes the apparatus according to the first aspect of the embodiments of the present application.
  • a network device is provided, and the network device includes the apparatus according to the second aspect of the embodiments of the present application.
  • a communication system including the terminal device according to the third aspect of the embodiments of the present application and/or according to the fourth aspect of the embodiments of the present application Network equipment.
  • a method for indicating LBT failure the method is applied to a terminal device, and the method includes: judging at a lower layer or a higher layer 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 higher layer, or the lower layer starts to notify or indicate the LBT failure to the higher layer; and/or, the lower layer or the higher layer determines that the first condition is not met And/or when 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 higher layer, or the lower layer stops notifying or indicating the LBT failure to the higher layer.
  • a method for indicating LBT failure is applied to a network device, and the method includes: configuring a terminal device with high-level parameters, and the high-level parameter is used by the terminal device to determine the low-level Whether to notify or indicate LBT failure to higher layers.
  • a computer-readable program wherein when the program is executed in an apparatus or terminal device indicating LBT failure, the program causes the apparatus or terminal indicating LBT failure
  • the device executes the method for indicating LBT failure described in the sixth aspect of the embodiment of the present invention.
  • a storage medium storing a computer readable program, wherein the computer readable program enables an apparatus or terminal device indicating LBT failure to execute the sixth aspect of the embodiment of the present invention.
  • the method to indicate LBT failure is described.
  • a computer-readable program wherein when the program is executed in an apparatus or network device indicating LBT failure, the program causes the apparatus or network indicating LBT failure
  • the device executes the method for indicating LBT failure described in the seventh aspect of the embodiment of the present invention.
  • a storage medium storing a computer readable program, wherein the computer readable program enables an apparatus or network device indicating LBT failure to execute the seventh aspect of the embodiment of the present invention The described method of indicating LBT failure.
  • the beneficial effect of the embodiments of the present application is that the lower layer or the higher layer first determines whether the relevant conditions are met, and based on the result of the judgment, when the uplink transmission is blocked due to the LBT failure, it is determined whether the lower layer informs or indicates the LBT failure to the higher layer, or determines the lower layer Whether to start or stop notifying or indicating LBT failure to the upper layer, in this way, the interaction between the lower layer and the upper layer can be reduced, thereby reducing the power consumption of the terminal equipment.
  • Fig. 1 is a schematic diagram of a communication system according to an embodiment of the present application.
  • Fig. 2 is a schematic diagram of an existing mechanism for indicating LBT failure
  • FIG. 3 is a schematic diagram of a mechanism for indicating LBT failure according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application.
  • FIG. 5 is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application.
  • FIG. 6 is another schematic diagram of the method for indicating LBT failure according to Embodiment 1 of the present application.
  • FIG. 7 is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application.
  • FIG. 8 is a schematic diagram of the method for indicating LBT failure in Embodiment 2 of the present application.
  • FIG. 9 is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application.
  • FIG. 10 is another schematic diagram of the method for indicating LBT failure according to Embodiment 1 of the present application.
  • FIG. 11 is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application.
  • FIG. 12 is another schematic diagram of the method for indicating LBT failure according to Embodiment 1 of the present application.
  • FIG. 13 is another schematic diagram of the method for indicating LBT failure according to Embodiment 1 of the present application.
  • FIG. 14 is a schematic diagram of the method for indicating LBT failure in Embodiment 2 of the present application.
  • FIG. 16 is another schematic diagram of the method for indicating LBT failure according to Embodiment 3 of the present application.
  • FIG. 17 is another schematic diagram of the method for indicating LBT failure according to Embodiment 3 of the present application.
  • FIG. 18 is a schematic diagram of the device for indicating LBT failure in Embodiment 4 of the present application.
  • FIG. 19 is a schematic diagram of the device for indicating LBT failure according to Embodiment 5 of the present application.
  • FIG. 20 is a schematic block diagram of the system configuration of a terminal device according to Embodiment 6 of the present application.
  • FIG. 21 is a schematic block diagram of the system configuration of a network device according to Embodiment 7 of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements from the terms, but they do not indicate the spatial arrangement or chronological order of these elements. These elements should not be used by these terms. Limited.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the terms “comprising”, “including”, “having” and the like refer to the existence of the stated features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.
  • the term "communication network” or “wireless communication network” can refer to a network that meets any of the following communication standards, such as Long Term Evolution (LTE), and Enhanced Long Term Evolution (LTE-A, LTE-A). Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed Packet Access (HSPA, High-Speed Packet Access), etc.
  • LTE Long Term Evolution
  • LTE-A Enhanced Long Term Evolution
  • LTE-A LTE-A
  • Advanced Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • High-Speed Packet Access High-Speed Packet Access
  • HSPA High-Speed Packet Access
  • the communication between devices in the communication system can be carried out according to any stage of communication protocol, for example, it can include but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR, New Radio), etc., and/or other communication protocols currently known or to be developed in the future.
  • 1G generation
  • 2G 2.5G
  • 2.75G 3G
  • 4G 4G
  • 4.5G future 5G
  • New Radio NR, New Radio
  • Network device refers to, for example, a device in a communication system that connects a user equipment to a communication network and provides services for the user equipment.
  • Network equipment may include but not limited to the following equipment: base station (BS, Base Station), access point (AP, Access Point), transmission and 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), etc.
  • the base station may include, but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), 5G base station (gNB), etc., and may also include remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay), or low-power node (such as femto, pico, etc.).
  • NodeB Node B
  • eNodeB or eNB evolved Node B
  • gNB 5G base station
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low-power node such as femto, pico, etc.
  • base station can include some or all of their functions, and each base station can provide communication coverage for a specific geographic 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.
  • the term "User Equipment” refers to, for example, 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 device may be fixed or mobile, and may also be called a mobile station (MS, Mobile Station), terminal, subscriber station (SS, Subscriber Station), access terminal (AT, Access Terminal), station, etc.
  • terminal devices may include but are not limited to the following devices: cellular phones (Cellular Phone), personal digital assistants (PDAs, Personal Digital Assistant), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, Cordless phones, smart phones, smart watches, digital cameras, etc.
  • cellular phones Cellular Phone
  • PDAs personal digital assistants
  • wireless modems wireless communication devices
  • handheld devices machine-type communication devices
  • laptop computers Cordless phones
  • smart phones smart watches, digital cameras, etc.
  • a terminal device may also be a machine or device that performs monitoring or measurement.
  • it may include, but is not limited to: Machine Type Communication (MTC) terminals, In-vehicle communication terminals, device to device (D2D, Device to Device) terminals, machine to machine (M2M, Machine to Machine) terminals, etc.
  • MTC Machine Type Communication
  • D2D Device to Device
  • M2M Machine to Machine
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application, which schematically illustrates a case where a terminal device and a network device are taken as an example.
  • the communication system 100 may include: a network device 101 and a terminal device 102.
  • Figure 1 only uses one terminal device as an example for illustration.
  • the network device 101 is, for example, a network device gNB of NR.
  • eMBB enhanced mobile broadband
  • mMTC large-scale machine type communication
  • URLLC Ultra-Reliable and Low- Latency Communication
  • FIG. 2 is a schematic diagram of an existing mechanism for indicating LBT failure.
  • the lower layer for example, the physical layer
  • the lower layer transfers to the higher layer.
  • the MAC layer indicates or informs the failure of the LBT. In this way, whenever the uplink transmission is blocked due to LBT failure, the lower layer will notify or instruct the higher layer, which will greatly increase the interaction between the lower layer and the higher layer, and increase the power consumption of the terminal device 102.
  • FIG. 3 is a schematic diagram of a mechanism for indicating LBT failure according to an embodiment of the present application.
  • the lower layer of the terminal device 102 executes the LBT process.
  • the lower layer or the higher layer first determines whether the relevant conditions are met.
  • the lower layer performs the LBT process before the uplink transmission and
  • the uplink transmission is not executed, that is, when the uplink transmission is blocked due to LBT failure, the lower layer informs 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 the result of the judgment is that the relevant conditions are not met.
  • the lower layer 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. 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.
  • the embodiment of the present application provides a method for indicating LBT failure, and the method is applied to a terminal device.
  • FIG. 4 is a schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application. As shown in Figure 4, the method includes:
  • Step 401 In the case that the lower layer or the higher 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 higher layer, or the lower layer starts to notify or Indicates that LBT has failed; and/or,
  • Step 402 In the case that the lower layer or the higher layer determines that the first condition and/or the third condition are not satisfied, 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 sending The higher layer informs or instructs the failure of LBT.
  • the method may include one of steps 402 in step 401, or may include two steps of step 401 and step 402.
  • the steps are not correct.
  • the execution order of 401 and step 402 is restricted.
  • the lower layer or the upper layer first judges whether the relevant conditions are met. Based on the result of the judgment, when the uplink transmission is blocked due to LBT failure, it is determined whether the lower layer informs or indicates the LBT failure to the upper layer, or whether the lower layer starts or stops to the upper layer. Notifying or indicating LBT failure, in this way, can reduce the interaction between the lower layer and the upper layer, thereby reducing the power consumption of the terminal device.
  • the lower layer is, for example, the physical layer
  • the higher layer is, for example, the MAC layer.
  • FIG. 5 is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application. As shown in Figure 5, the method includes:
  • Step 501 In the case that the lower layer determines that the first condition is met, when the 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,
  • Step 502 In the case that the lower layer judges that the first condition is not satisfied, 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.
  • the method may include one of steps 502 in step 501, or may include two steps of step 501 and step 502.
  • the steps are incorrect.
  • the execution order of 501 and step 502 is restricted.
  • 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 NR Terminal; the uplink transmission or the terminal device performs shared spectrum channel access operations; 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 authorization assistance Access (Enhanced Licensed Assisted Access, eLAA); the terminal device is not performing authorized assisted access or enhanced authorized assisted access; and the uplink transmission is not an automatic uplink transmission.
  • LAA Licensed Assisted Access
  • eLAA enhanced authorization assistance Access
  • the terminal device is not performing authorized assisted access or enhanced authorized assisted access
  • the uplink transmission is not an automatic uplink transmission.
  • the uplink transmission or the terminal device performs a shared spectrum channel access operation, the uplink The transmission is the uplink transmission scheduled or configured by the network device.
  • the uplink transmission is not authorized assisted access (LAA) or Enhanced Licensed Assisted Access (eLAA), and the terminal device is not authorized assisted access.
  • LAA assisted access
  • eLAA Enhanced Licensed Assisted Access
  • 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.
  • the lower layer does not notify or indicate LBT failure to the higher layer, or the lower layer stops to notify or indicate the LBT failure to the higher layer.
  • 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.
  • notifying or indicating the failure of LBT includes: sending a notification or instruction, or sending a notification or instruction and an object that executes LBT.
  • the above notification or instruction can be made through a notification or instruction sent by the low layer to the high layer, or it can be made through a notification or instruction sent by the low layer to the high layer and the object that executes the LBT.
  • the notification or instruction sent may be one of the following notifications or instructions:
  • a notification or indication for a specific purpose for example, an indication of continuous UL LBT failure detection, or an indication of a random access preamble, or an indication of a configured authorization, or an indication of a scheduling request (Scheduling Request, SR);
  • SAP Service Access Points
  • the high-level 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 Retransmission request (Hybrid Automatic Repeat Request, HARQ), authorized transmission of uplink configuration, and scheduling request (SR).
  • continuous LBT failure detection random access process
  • random access preamble transmission random access preamble transmission
  • hybrid automatic Retransmission request Hybrid Automatic Repeat Request, HARQ
  • authorized transmission of uplink configuration SR.
  • the object that executes LBT may use the uplink resource or the index corresponding to the uplink resource. Characterization.
  • the uplink resource includes at least one of a random access resource (RA/PRACH occasion), a valid PUCCH resource of a scheduling request (SR), and a configured grant.
  • RA/PRACH occasion a random access resource
  • SR scheduling request
  • configured grant a configured grant
  • the object performing LBT is characterized by the index corresponding to the uplink resource, for example, define a mapping relationship, and the object can be characterized by the corresponding index, for example: define the corresponding index of the random access resource (RA/PRACH occasion) 1 , A valid PUCCH resource of SR corresponds to index 2, and the configured authorization corresponds to index 3.
  • the lower layer 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 the LBT failure to the higher layer. In this way, by further restricting the conditions, the interaction between the lower layer and the upper layer can be further reduced, thereby further reducing the power consumption of the terminal device.
  • FIG. 6 is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application. As shown in Figure 6, the method includes:
  • Step 601 When the lower layer determines that the first condition and the fourth condition are met, when the 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.
  • 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 a failure of the LBT performed for the configured authorization; and the LBT failure is the failure of the LBT performed for a valid Physical Uplink Control Channel (PUCCH) resource of the scheduling request (SR).
  • 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 a failure of the LBT performed for the configured authorization; and the LBT failure is the failure of the LBT performed for a valid Physical Uplink Control Channel (PUCCH) resource of the scheduling request (SR).
  • PUCCH Physical Uplink Control Channel
  • the terminal device or the lower layer fails to access the channel. If the lower layer determines that the first condition is also met, Then the lower layer notifies or indicates the LBT failure to the higher layer.
  • the uplink transmission is instructed by a higher layer (for example, the MAC layer), or triggered or generated by a lower layer (for example, the physical layer) itself, for example, acknowledgement or non-acknowledgement (ACK or NACK), sounding reference signal (Sounding Reference Signal, SRS) , Channel quality indication (channel quality indication, CQI), etc.;
  • a higher layer for example, the MAC layer
  • a lower layer for example, the physical layer
  • acknowledgement or non-acknowledgement ACK or NACK
  • Sounding reference signal Sounding Reference Signal
  • SRS Sounding Reference Signal
  • Channel quality indication channel quality indication, CQI
  • the uplink transmission may be on the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH) or the physical random access channel (Physical Random Access Channel). , PRACH);
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • PRACH Physical Random Access Channel
  • the LBT type of the executed LBT is not limited, for example, the LBT type of the executed LBT may be LBT type 2 or LBT type 4, etc.;
  • the channel access priority class (Channel Access Priority Class, CAPC) of the executed LBT is not limited, for example, the CAPC priority is 1 or 4, etc.
  • the LBT failure is a case where the LBT performed for the transmission of the random access preamble (RA preamble) fails, that is, in order to send the RA preamble, the terminal device or the lower layer fails to access
  • RA preamble 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;
  • PRACH physical random access channel
  • RA/PRACH occasion a random access resource indicated by a higher layer
  • the uplink transmission is instructed by the higher layer (for example, the MAC layer), or triggered or generated by the lower layer (for example, the physical layer) itself, for example, repetition of the physical layer;
  • the higher layer for example, the MAC layer
  • the lower layer for example, the physical layer
  • the LBT type of the executed LBT is not limited, for example, the LBT type of the executed LBT may be LBT type 2 or LBT type 4, etc.;
  • the channel access priority class (Channel Access Priority Class, CAPC) of the executed LBT is not limited, for example, the CAPC priority is 1 or 4, etc.
  • the terminal device or the lower layer fails to access the channel, if the lower layer If it is determined that the first condition is met at the same time, the lower layer will notify or indicate the LBT failure to the higher layer.
  • the channel corresponding to the LBT is the physical uplink shared channel (PUSCH), and the LBT is the LBT performed on the authorization of the configuration indicated by the higher layer;
  • PUSCH physical uplink shared channel
  • the LBT type of the executed LBT is not limited, for example, the LBT type of the executed LBT may be LBT type 2 or LBT type 4, etc.;
  • the channel access priority class (Channel Access Priority Class, CAPC) of the executed LBT is not limited, for example, the CAPC priority is 1 or 4, etc.
  • the LBT failure is a case where the LBT performed on a valid physical uplink control channel (PUCCH) resource of the scheduling request (SR) fails, that is, in order to perform a valid PUCCH resource If the terminal device or the lower layer fails to access the channel and fails to access the channel, if the lower layer determines that the first condition is met at the same time, the lower layer will notify or indicate the LBT failure to the higher layer.
  • PUCCH physical uplink control channel
  • SR scheduling request
  • the channel corresponding to the LBT is a physical uplink control channel (PUCCH), and the LBT is an LBT performed on an effective PUCCH resource of an SR indicated by a higher layer;
  • PUCCH physical uplink control channel
  • the LBT type of the executed LBT is not limited, for example, the LBT type of the executed LBT may be LBT type 2 or LBT type 4, etc.;
  • the channel access priority class (Channel Access Priority Class, CAPC) of the executed LBT is not limited, for example, the CAPC priority is 1 or 4, etc.
  • the method may further include:
  • Step 503 When the higher layer is notified or instructed or when the higher layer is not notified or instructed, a counter is incremented or unchanged or suspended, or a timer is started or restarted, or the terminal device or the upper layer is triggered to execute a process.
  • the counter is one of the following counters:
  • a counter used to count the number of scheduling requests for example, the counter SR_COUNTER;
  • Counters used to apply or suspend power ramp for example, counter PREAMBLE_POWER_RAMPING_COUNTER;
  • a counter used for continuous LBT failure detection for example, the counter LBT_COUNTER.
  • the timer is a timer for configuration authorization (CG), for example, configuredGrantTimer or cg-RetransmissionTimer, or the timer is a timer for continuous LBT failure detection, For example, lbt-FailureDetectionTimer.
  • CG configuration authorization
  • configuredGrantTimer for example, configuredGrantTimer or cg-RetransmissionTimer
  • the timer is a timer for continuous LBT failure detection, For example, lbt-FailureDetectionTimer.
  • the process that triggers the terminal device or higher layer to execute is a random access process or a random access resource selection process.
  • the notification or instruction can not only notify or indicate the LBT failure, but can also trigger other actions or operations or processes based on whether the high layer is notified or instructed, such as As described above, the operation of the counter used for scheduling requests or the counter used for application or suspension of power ramping, and/or triggers the random access process or the random access resource selection process.
  • FIG. 7 is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application. As shown in Figure 7, the method includes:
  • Step 701 In the case that the lower layer determines that the second condition is met, when the 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,
  • Step 702 In the case where the lower layer determines that 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 higher layer, or the lower layer stops notifying or indicates the LBT failure to the higher layer.
  • the method may include one of steps 702 in step 701, or may include two steps of step 701 and step 702.
  • the steps are not correct.
  • the execution order of 701 and step 702 is restricted.
  • the second condition is that high-level parameters are configured and/or capabilities are configured
  • the third condition is that high-level parameters are released or removed and/or capabilities are not available.
  • the high-level parameter is an RRC parameter.
  • FIG. 8 is a schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application. As shown in Figure 8, the method includes:
  • Step 801 When the lower layer judges that the upper layer parameters are configured and/or has the capability, when the 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,
  • Step 802 When the lower layer judges that the upper layer parameters are released or removed and/or is not capable, 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 the notification to the higher layer Or indicate that LBT has failed.
  • the method may include one of steps 802 in step 801, or may include two steps of step 801 and step 802.
  • the steps are not correct.
  • the execution order of 801 and step 802 is restricted.
  • the high-level parameters include at least one of the following parameters: parameters used for persistent LBT failure detection for shared spectrum channel access; configuration parameters used for scheduling requests; authorized parameters used for configuration Configuration parameters.
  • the high-level parameter is lbt-FailureRecoveryConfig.
  • the high-level parameter is cell-specific or terminal device-specific; and/or, when dual When linking (DC), the high-level parameter is configured in the primary cell group (MCG) and the secondary cell group (SCG) respectively; and/or, when the supplementary uplink (SUL) is configured, the high-level parameter is the supplementary uplink The link (SUL) and normal uplink (NUL) are configured separately.
  • the high-level parameters are parameters for configuring dedicated scheduling request resources, such as SchedulingRequestConfig; for another example, the high-level parameters are parameters for the maximum number of SR transmissions, such as sr-TransMax.
  • the high-level parameter is a parameter used to configure uplink transmission without dynamic authorization, such as ConfiguredGrantConfig; for another example, the high-level parameter is a parameter for a CG timer, such as configuredGrantTimer or cg-RetransmissionTimer.
  • the capability is the capability of NR operation in the shared spectrum channel and/or the capability of continuous LBT detection and recovery.
  • the capability is terminal device specific; or, the capability is cell specific, for example, the primary cell (PCell), the primary secondary cell (PSCell), and the secondary cell (SCell) are independent of each other Capability; or, the capability is frequency band specific or frequency band combination specific.
  • notifying or indicating the failure of LBT includes: sending a notification or instruction, or sending a notification or instruction and an object that executes LBT.
  • the above notification or instruction can be made through a notification or instruction sent by the low layer to the high layer, or it can be made through a notification or instruction sent by the low layer to the high layer and the object that executes the LBT.
  • the lower layer 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 the LBT failure to the higher layer. In this way, by further restricting the conditions, the interaction between the lower layer and the upper layer can be further reduced, thereby further reducing the power consumption of the terminal device.
  • FIG. 9 is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application. As shown in Figure 9, the method includes:
  • Step 901 When the lower layer determines that the second condition and the fourth condition are met, when the 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.
  • 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 a failure of the LBT performed for the configured authorization; and the LBT failure is the failure of the LBT performed for a valid Physical Uplink Control Channel (PUCCH) resource of the scheduling request (SR).
  • 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 a failure of the LBT performed for the configured authorization; and the LBT failure is the failure of the LBT performed for a valid Physical Uplink Control Channel (PUCCH) resource of the scheduling request (SR).
  • PUCCH Physical Uplink Control Channel
  • the method may further include:
  • 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 unchanged or suspended, or a timer is started or restarted, or the terminal device or the upper layer is triggered to execute a process.
  • FIG. 10 is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application. As shown in Figure 10, the method includes:
  • Step 1001 In the case where the upper layer determines that the first condition is met, the upper layer sends a notification or instruction or request to the lower layer;
  • Step 1002 When the 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.
  • the higher layer when the upper layer determines that the first condition is met, the higher layer sends a notification or instruction or request to the lower layer. According to the notification or instruction or request, the lower layer will notify or notify the higher layer when the uplink transmission is blocked due to LBT failure. Indicate LBT failure, or start to notify or indicate LBT failure.
  • FIG. 11 is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application. As shown in Figure 11, the method includes:
  • Step 1101 In the case where the upper layer judges that the first condition is not met, the upper layer sends a notification or instruction or request to the lower layer;
  • 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 indicates the LBT failure to the higher layer.
  • the higher layer when the upper layer determines that the first condition is not met, the higher layer sends a notification or instruction or request to the lower layer, and the lower layer does not send a notification or instruction or request to the lower layer when the uplink transmission is blocked due to LBT failure.
  • the higher layers notify or indicate LBT failure, or stop notification or indicate LBT failure.
  • the specific content of the first condition is the same as the description in Case 1.
  • the terminal device when 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 The transmission is the uplink transmission scheduled or configured by the network device, and the uplink transmission is not authorized assisted access (LAA) or Enhanced Licensed Assisted Access (eLAA), and the terminal device is not authorized assisted access.
  • LAA assisted access
  • eLAA Enhanced Licensed Assisted Access
  • the upper layer sends a notification or instruction or 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 send The higher layer informs or instructs the failure of LBT.
  • the upper layer sends a notification or instruction or 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 upper layer.
  • the higher layer sends a notification or instruction or 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.
  • the notification or indication of the failure of the LBT includes: sending a notification or indication, or sending a notification or indication and the object that executes the LBT.
  • the specific content is the same as the description in Case 1, and the description will not be repeated here.
  • the notification or instruction or request includes: sending a notification or instruction or request, or sending a notification or instruction or request and executing LBT Object. That is to say, the above notification or instruction or request can be made through a notification or instruction or request sent by the higher layer to the lower layer, or it can be made through a notification or instruction or request sent by the higher layer to the lower layer and the object that executes the LBT. Instructions or requests.
  • the notification or instruction or request sent by the higher layer to the lower layer is one of the following notifications or instructions or requests:
  • a notification or indication for a specific purpose for example, an indication of continuous UL LBT failure detection, or an indication of a random access preamble, or an indication of a configured authorization, or an indication of a scheduling request (Scheduling Request, SR);
  • SAP Service Access Points
  • the high-level 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 Retransmission request (Hybrid Automatic Repeat Request, HARQ), authorized transmission of uplink configuration, and scheduling request (SR).
  • continuous LBT failure detection random access process
  • random access preamble transmission random access preamble transmission
  • hybrid automatic Retransmission request Hybrid Automatic Repeat Request, HARQ
  • authorized transmission of uplink configuration SR.
  • the object that executes LBT can use uplink resources or communicate with uplink resources.
  • the index representation corresponding to the resource is not limited to the resource.
  • the uplink resource includes at least one of a random access resource (RA/PRACH occasion), a valid PUCCH resource of a scheduling request (SR), and a configured grant.
  • RA/PRACH occasion a random access resource
  • SR scheduling request
  • configured grant a configured grant
  • the object performing LBT is characterized by the index corresponding to the uplink resource, for example, define a mapping relationship, and the object can be characterized by the corresponding index, for example: define the corresponding index of the random access resource (RA/PRACH occasion) 1 , A valid PUCCH resource of SR corresponds to index 2, and the configured authorization corresponds to index 3.
  • step 1001 when the upper layer determines that the first condition is satisfied and the higher layer determines that the fourth condition is satisfied, the upper layer sends a notification or instruction or request to the lower layer. In this way, by further restricting the conditions, the interaction between the lower layer and the upper layer can be further reduced, thereby further reducing the power consumption of the terminal device.
  • step 1001 when a counter is maintained, it is determined that a counter is incremented by 1 or remains unchanged or suspended, or when a timer is maintained, it is determined to start or restart a timer.
  • the higher layer sends the notification or instruction or request to the lower layer.
  • the counter is one of the following counters:
  • a counter used to count the number of scheduling requests for example, the counter SR_COUNTER;
  • Counters used to apply or suspend power ramp for example, counter PREAMBLE_POWER_RAMPING_COUNTER;
  • a counter used for continuous LBT failure detection for example, the counter LBT_COUNTER.
  • the timer is a timer for configuration authorization (CG), for example, configuredGrantTimer or cg-RetransmissionTimer, or the timer is a timer for continuous LBT failure detection, For example, lbt-FailureDetectionTimer.
  • CG configuration authorization
  • configuredGrantTimer for example, configuredGrantTimer or cg-RetransmissionTimer
  • the timer is a timer for continuous LBT failure detection, For example, lbt-FailureDetectionTimer.
  • the process that triggers the terminal device or higher layer to execute is a random access process or a random access resource selection process.
  • the method may further include:
  • Step 1003 When the higher layer is notified or instructed or when the higher layer is not notified or instructed, a counter is incremented or unchanged or suspended, or a timer is started or restarted, or the terminal device or the upper layer is triggered to execute a process.
  • the method may further include:
  • Step 1103 When the higher layer is not notified or instructed or when the higher layer is not notified or instructed, a counter is incremented or unchanged or suspended, or a timer is started or restarted, or the terminal device or the upper layer is triggered Perform a process.
  • FIG. 12 is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application. As shown in Figure 12, the method includes:
  • Step 1201 In the case where the upper layer determines that the second condition is met, the upper layer sends a notification or instruction or request to the lower layer;
  • Step 1202 When the 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.
  • the higher layer determines that the second condition is met, the higher layer sends a notification or instruction or request to the lower layer.
  • the notification or instruction or request the lower layer will notify or notify the higher layer when the uplink transmission is blocked due to LBT failure. Indicate LBT failure, or start to notify or indicate LBT failure.
  • FIG. 13 is another schematic diagram of the method for indicating LBT failure in Embodiment 1 of the present application. As shown in Figure 13, the method includes:
  • Step 1301 In the case where the upper layer determines that the third condition is met, the upper layer sends a notification or instruction or request to the lower layer;
  • Step 1302 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 indicates the LBT failure to the higher layer.
  • the upper layer when the third condition is satisfied by the upper layer, the upper layer sends a notification or instruction or request to the lower layer.
  • the notification or instruction or request the lower layer does not notify the upper layer when the uplink transmission is blocked due to LBT failure. Or indicate LBT failure, or stop notification or indicate LBT failure.
  • the second condition is that high-level parameters are configured and/or capabilities are configured
  • the third condition is that high-level parameters are released or removed and/or capabilities are not available.
  • the notification or instruction or request includes: sending a notification or instruction or request, or sending a notification or instruction or request and executing LBT Object. That is to say, the above notification or instruction or request can be made through a notification or instruction or request sent by the higher layer to the lower layer, or it can be made through a notification or instruction or request sent by the higher layer to the lower layer and the object that executes the LBT. Instructions or requests.
  • the notification or instruction or request sent by the higher layer to the lower layer is one of the following notifications or instructions or requests:
  • 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 authorization, or indication of scheduling request (Scheduling Request, SR);
  • SAP Service Access Points
  • the high-level 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 Retransmission request (Hybrid Automatic Repeat Request, HARQ), authorized transmission of uplink configuration, and scheduling request (SR).
  • continuous LBT failure detection random access process
  • random access preamble transmission random access preamble transmission
  • hybrid automatic Retransmission request Hybrid Automatic Repeat Request, HARQ
  • authorized transmission of uplink configuration SR.
  • the object that executes LBT can use uplink resources or communicate with uplink resources.
  • the index representation corresponding to the resource is not limited to the resource.
  • the uplink resource includes at least one of a random access resource (RA/PRACH occasion), a valid PUCCH resource of a scheduling request (SR), and a configured grant.
  • RA/PRACH occasion a random access resource
  • SR scheduling request
  • configured grant a configured grant
  • the object performing LBT is characterized by the index corresponding to the uplink resource, for example, define a mapping relationship, and the object can be characterized by the corresponding index, for example: define the corresponding index of the random access resource (RA/PRACH occasion) 1 , A valid PUCCH resource of SR corresponds to index 2, and the configured authorization corresponds to index 3.
  • step 1201 when the higher layer determines that the second condition is satisfied and the higher layer determines that the fourth condition is satisfied, the higher layer sends a notification or instruction or request to the lower layer. In this way, by further restricting the conditions, the interaction between the lower layer and the upper layer can be further reduced, thereby further reducing the power consumption of the terminal device.
  • step 1201 when a counter is maintained, it is determined that a counter is incremented by 1 or remains unchanged or suspended, or when a timer is maintained, it is determined to start or restart a timer.
  • the higher layer sends the notification or instruction or request to the lower layer.
  • the counter is one of the following counters:
  • a counter used to count the number of scheduling requests for example, the counter SR_COUNTER;
  • Counters used to apply or suspend power ramp for example, counter PREAMBLE_POWER_RAMPING_COUNTER;
  • a counter used for continuous LBT failure detection for example, the counter LBT_COUNTER.
  • the timer is a timer for configuration authorization (CG), for example, configuredGrantTimer or cg-RetransmissionTimer, or the timer is a timer for continuous LBT failure detection, For example, lbt-FailureDetectionTimer.
  • CG configuration authorization
  • configuredGrantTimer for example, configuredGrantTimer or cg-RetransmissionTimer
  • the timer is a timer for continuous LBT failure detection, For example, lbt-FailureDetectionTimer.
  • the process that triggers the terminal device or higher layer to execute is a random access process or a random access resource selection process.
  • the method may further include:
  • Step 1203 When the higher layer is notified or instructed or when the higher layer is not notified or instructed, a counter is incremented or unchanged or suspended, or a timer is started or restarted, or the terminal device or higher layer is triggered to execute a process.
  • the method may further include:
  • Step 1303 When the higher layer is not notified or instructed or when the higher layer is not notified or instructed, a counter is incremented or unchanged or suspended, or a timer is started or restarted, or a terminal device or a higher layer is triggered Perform a process.
  • the case 1-4 is used as an example to give an exemplary explanation.
  • the embodiments of the present application may also include various combinations based on the following three factors: whether the subject of execution is a high-level or a low-level, whether the first condition or the second condition is satisfied, or the first condition and the second condition are satisfied at the same time, 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.
  • the lower layer or the upper layer first determines whether the relevant conditions are met. Based on the result of the judgment, when the uplink transmission is blocked due to LBT failure, it is determined whether the lower layer informs or indicates the LBT failure to the higher layer, or whether the lower layer starts or Stop notifying or indicating the failure of LBT to the upper layer. In this way, the interaction between the lower layer and the upper layer can be reduced, thereby reducing the power consumption of the terminal equipment.
  • the embodiment of the present application provides a method for indicating LBT failure.
  • the method is applied to a network device and corresponds to the method for indicating LBT failure applied to a terminal device described in Embodiment 1. The same content will not be repeated.
  • FIG. 14 is a schematic diagram of the method for indicating LBT failure in Embodiment 2 of the present application. As shown in Figure 14, the method includes:
  • Step 1401 Configure high-level parameters to the terminal device, where the high-level parameters are used by the terminal device to determine whether the low-level notifies or indicates the LBT failure to the high-level.
  • the high-level parameter is also used for the terminal device to determine whether the high-level sends a notification or instruction or request to the low-level.
  • the terminal device determines whether the lower layer informs or indicates LBT failure to the higher layer according to the second condition and/or the third condition, or whether the lower layer starts or stops starting to notify or indicate the LBT failure to the higher layer
  • the second condition is that the high-level parameter is configured and/or the capability is available
  • the third condition is that the high-level parameter is released or removed and/or the capability is not available.
  • the terminal device uses high-level parameters for the specific content, please refer to the record in Embodiment 1, and the description will not be repeated here.
  • the high-level parameters include at least one of the following parameters: parameters used for persistent LBT failure detection for shared spectrum channel access; configuration parameters used for scheduling requests; authorized parameters used for configuration Configuration parameters.
  • the high-level parameters are cell-specific or terminal equipment-specific; and/or, when dual link (DC) is configured, the high-level parameters are in the primary cell group (MCG) and The secondary cell group (SCG) is configured separately; and/or, when the supplementary uplink (SUL) is configured, the upper layer parameters are configured separately for the supplementary uplink (SUL) and the normal uplink (NUL).
  • the specific content of the high-level parameter can refer to the record in Embodiment 1, and the description will not be repeated here.
  • the network device configures the terminal device to determine whether the lower layer will notify or indicate the LBT failure to the higher layer.
  • determine whether the lower layer will notify or indicate LBT failure to the higher layer or determine whether the lower layer will start or stop notifying or indicate LBT failure to the higher layer.
  • the interaction between the lower layer and the upper layer can be reduced, thereby reducing the number of terminals The power consumption of the device.
  • the embodiment of the present application provides a method for indicating LBT failure, which is applied to network equipment and terminal equipment, and corresponds to the method for indicating LBT failure applied to terminal equipment described in Embodiment 1 and the method described in Embodiment 2
  • the same content will not be repeated.
  • FIG. 15 is a schematic diagram of the method for indicating LBT failure in Embodiment 3 of the present application. As shown in Figure 15, the method includes:
  • Step 1501 The network device configures the terminal device with high-level parameters, and the high-level parameters are used by the terminal device to determine whether the low-level notifies or indicates the LBT failure to the high-level;
  • Step 1502 In the case that the lower 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 higher layer, or the lower layer starts to notify or instruct the LBT to the higher layer fail;
  • Step 1503 In the case that the lower layer judges that the first condition and/or the third condition are not satisfied, 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 notifying the higher layer. Indicates that LBT has failed.
  • FIG. 16 is another schematic diagram of the method for indicating LBT failure according to Embodiment 3 of the present application. As shown in Figure 16, the method includes:
  • Step 1601 The network equipment configures the terminal equipment with high-level parameters, and the high-level parameters are used by the terminal equipment to determine whether the low-level notifies or indicates the LBT failure to the high-level;
  • Step 1602 When the upper layer determines that the first condition and/or the second condition are met, the higher layer sends a notification or instruction or request to the lower layer;
  • Step 1603 When the uplink transmission is blocked due to LBT failure, the lower layer informs 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.
  • FIG. 17 is another schematic diagram of the method for indicating LBT failure in Embodiment 3 of the present application. As shown in Figure 17, the method includes:
  • Step 1701 The network device configures the terminal device with high-level parameters, and the high-level parameters are used by the terminal device to determine whether the low-level notifies or indicates the LBT failure to the high-level;
  • Step 1702 When the upper layer determines that the first condition and/or the third condition is not satisfied, the higher layer sends a notification or instruction 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 LBT failure, or, the lower layer will stop notifying or indicate LBT failure to the higher layer.
  • each step in FIG. 15 to FIG. 17 can refer to the description of Embodiment 1 and Embodiment 2, and the description will not be repeated here.
  • the lower layer or the upper layer first determines whether the relevant conditions are met. Based on the result of the judgment, when the uplink transmission is blocked due to LBT failure, it is determined whether the lower layer informs or indicates the LBT failure to the higher layer, or whether the lower layer starts or Stop notifying or indicating the failure of LBT to the upper layer. In this way, the interaction between the lower layer and the upper layer can be reduced, thereby reducing the power consumption of the terminal equipment.
  • the embodiment of the present application provides a device for indicating LBT failure, and the device is applied to a terminal device. Since the principle of the device to solve the problem is similar to the method of embodiment 1, its specific implementation can refer to the implementation of the method of embodiment 1, and the same content or related parts will not be repeated.
  • FIG. 18 is a schematic diagram of the device for indicating LBT failure according to Embodiment 4 of the present application. As shown in FIG. 18, the device 1800 includes:
  • the first indicating unit 1801 when the lower layer or the higher layer determines that the first condition and/or the second condition are met, when the uplink transmission is blocked due to the LBT failure, the lower layer notifies or indicates the LBT failure to the higher layer, or the lower layer Begin to notify or indicate LBT failure to senior management; and/or,
  • the second instructing unit 1802 when the lower layer or the higher layer determines that the first condition and/or the third condition are not satisfied, when the uplink transmission is blocked due to LBT failure, the lower layer does not notify or instruct the LBT to the higher layer Failure, or, the lower layer stops notifying or indicating LBT failure to the upper layer.
  • the apparatus 1800 may further include:
  • the first processing unit 1803 when the higher layer is notified or instructed, or when the higher layer is not notified or instructed, a counter is incremented by 1 or remains unchanged or suspended; or, starts or restarts a timer; or, triggers the terminal
  • the device or higher layer executes a process.
  • the apparatus 1800 when it is judged by a higher layer that the first condition and/or the second condition are satisfied, the apparatus 1800 may further include:
  • the third instructing unit 1804 which is used by the higher layer to send a notification or instruction or request to the lower layer; based on the notification or instruction or request, when the uplink transmission is blocked due to LBT failure, the lower layer notifies or instructs the higher layer that the LBT fails, or causes The lower layer starts to notify or indicate the LBT failure to the higher layer.
  • the apparatus 1800 may further include:
  • the fourth instruction unit 1805 which is used by the higher layer to send a notification or instruction or request to the lower layer; based on the notification or instruction 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 The lower layer stops notifying or indicating to the upper layer that the LBT has failed.
  • the lower layer or the upper layer first determines whether the relevant conditions are met. Based on the result of the judgment, when the uplink transmission is blocked due to LBT failure, it is determined whether the lower layer informs or indicates the LBT failure to the higher layer, or whether the lower layer starts or Stop notifying or indicating the failure of LBT to the upper layer. In this way, the interaction between the lower layer and the upper layer can be reduced, thereby reducing the power consumption of the terminal equipment.
  • the embodiment of the present application provides a device for indicating LBT failure, and the device is applied to a network device. Since the principle of the device to solve the problem is similar to the method of embodiment 2, its specific implementation can refer to the implementation of the method described in embodiment 2, and the same content or related parts will not be repeated.
  • FIG. 19 is a schematic diagram of the device for indicating LBT failure according to Embodiment 5 of the present application. As shown in FIG. 19, the device 1900 includes:
  • the configuration unit 1901 which configures high-level parameters to the terminal device,
  • This high-level parameter is used by the terminal device to determine whether the low-level informs or indicates the LBT failure to the high-level.
  • the high-level parameter is also used for the terminal device to determine whether the high-level sends a notification or instruction or request to the low-level.
  • the terminal device determines whether the lower layer informs or indicates LBT failure to the higher layer according to the second condition and/or the third condition, or whether the lower layer starts or stops starting to notify or indicate the LBT failure to the higher layer
  • the second condition is that the high-level parameter is configured and/or the capability is available
  • the third condition is that the high-level parameter is released or removed and/or the capability is not available.
  • the high-level parameters include at least one of the following parameters: parameters used for persistent LBT failure detection for shared spectrum channel access; configuration parameters used for scheduling requests; authorized parameters used for configuration Configuration parameters.
  • the high-level parameters are cell-specific or terminal equipment-specific; and/or, when dual link (DC) is configured, the high-level parameters are in the primary cell group (MCG) and The secondary cell group (SCG) is configured separately; and/or, when the supplementary uplink (SUL) is configured, the upper layer parameters are configured separately for the supplementary uplink (SUL) and the normal uplink (NUL).
  • the specific content of the high-level parameter can refer to the record in Embodiment 1, and the description will not be repeated here.
  • the network device configures the terminal device to determine whether the lower layer will notify or indicate the LBT failure to the upper layer.
  • determine whether the lower layer will notify or indicate LBT failure to the higher layer or determine whether the lower layer will start or stop notifying or indicate LBT failure to the higher layer.
  • the interaction between the lower layer and the upper layer can be reduced, thereby reducing the number of terminals The power consumption of the device.
  • the embodiment of the present application provides a terminal device, and the terminal device includes the apparatus for indicating LBT failure as described in Embodiment 4.
  • FIG. 20 is a schematic block diagram of the system configuration of a terminal device according to Embodiment 6 of the present application.
  • the terminal device 2000 may include a processor 2010 and a memory 2020; the memory 2020 is coupled to the processor 2010. It is worth noting that this figure is exemplary; other types of structures can also be used to supplement or replace this structure to achieve telecommunication functions or other functions.
  • the function of the device indicating LBT failure may be integrated into the processor 2010.
  • the processor 2010 may be configured to: when the lower layer or the higher layer determines that the first condition and/or the second condition are satisfied, when the uplink transmission is blocked due to the 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 the lower layer or the higher layer judges that the first condition and/or the third condition are not satisfied, when the uplink transmission is blocked due to the LBT failure, the lower layer Do not notify or indicate LBT failure to higher layers, or lower layer to stop notifying or indicate LBT failure to higher layers.
  • 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 an uplink transmission scheduled or configured by a network device; the uplink transmission is not an authorized assisted access (LAA) or an enhanced authorized assisted access (eLAA); The terminal device is not performing authorized assisted access or enhanced authorized assisted access; and the uplink transmission is not automatic uplink transmission.
  • LAA authorized assisted access
  • eLAA enhanced authorized assisted access
  • the terminal device is not performing authorized assisted access or enhanced authorized assisted access
  • the uplink transmission is not automatic uplink transmission.
  • the second condition is that high-level parameters are configured and/or the capability is available
  • the third condition is that the high-level parameters are released or removed and/or the capability is not available.
  • the high-level parameters include at least one of the following parameters: parameters used for persistent LBT failure detection for shared spectrum channel access; configuration parameters used for scheduling requests; and authorized configuration parameters used for configuration.
  • the high-level parameters are cell-specific or terminal equipment-specific; and/or, when dual link (DC) is configured, the high-level parameters are in the primary cell group (MCG) and the secondary cell group (SCG) respectively And/or when the supplementary uplink (SUL) is configured, the upper layer parameters are configured separately for the supplementary uplink (SUL) and the normal uplink (NUL).
  • the capability is the capability of NR operation in the shared spectrum channel and/or the capability of continuous LBT detection and recovery.
  • the capabilities are terminal device specific, or cell specific, or frequency band specific or frequency band combination specific.
  • the lower layer when the lower layer or the upper layer judges that the first condition and/or the second condition are satisfied, and the lower layer judges 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,
  • 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 configuration The LBT performed by the authorization fails; and the LBT failure is a failure of the LBT performed for a valid physical uplink control channel (PUCCH) resource of the scheduling request (SR).
  • 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 configuration The LBT performed by the authorization fails; and the LBT failure is a failure of the LBT performed for a valid physical uplink control channel (PUCCH) resource of the scheduling request (SR).
  • PUCCH physical uplink control channel
  • the channel corresponding to the LBT is the physical random access channel (PRACH), and the LBT is the random access indicated to the higher layer.
  • PRACH physical random access channel
  • LBT performed by the resource (RA/PRACH occasion) when the LBT failure is the failure of the LBT performed for the configured authorization, the channel corresponding to the LBT is the physical uplink shared channel (PUSCH), and the LBT is LBT authorized by the configuration indicated by the upper layer.
  • PUSCH physical uplink shared channel
  • the notification or indication of LBT failure includes: sending a notification or indication, or sending a notification or indication and the object that executes the LBT.
  • the notification or instruction sent is one of the following notifications or instructions: a general notification or instruction; a specific purpose notification or instruction; a notification or instruction sent from a lower layer to a higher layer through a different service access point (SAP) or channel or path Notifications or instructions; and notifications or instructions provided to different high-level processes or functions or entities.
  • SAP service access point
  • the high-level 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), authorized transmission of uplink configuration And scheduling requests.
  • continuous LBT failure detection random access process
  • random access preamble transmission random access preamble transmission
  • hybrid automatic repeat request HARQ
  • authorized transmission of uplink configuration And scheduling requests HARQ
  • the object performing LBT is characterized by uplink resources or an index corresponding to the uplink resources.
  • the uplink resource includes at least one of a random access resource (RA/PRACH occasion), a valid PUCCH resource of a scheduling request, and a configured grant.
  • the processor 2010 may also be configured to: when the higher layer is notified or instructed, or when the higher layer is not notified or instructed, a counter is incremented by 1 or remains unchanged or suspended; or, to start or restart A timer; or, to trigger the terminal device or higher layer to execute a process.
  • the counter is one of the following counters: a counter for counting the number of scheduling requests; a counter for applying or suspending a power ramp; and a counter for continuous LBT failure detection.
  • the timer is a timer for configuration authorization (CG) or a timer for continuous LBT failure detection.
  • the process that is triggered to be executed by the terminal device or the higher layer is a random access process or a random access resource selection process.
  • the processor 2010 may also be configured to: the higher layer sends a notification or instruction or request to the lower layer, and based on the notification or instruction or request, when the upstream
  • the lower layer notifies or indicates the LBT failure to the higher layer, or causes the lower layer to start to notify or indicate the LBT failure to the higher layer.
  • the processor 2010 may be further configured to: the higher layer sends a notification or instruction or request to the lower layer, based on the notification or instruction 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 causes the lower layer to stop the notification or indicate the LBT failure to the higher layer.
  • the notification or instruction or request includes: sending a notification or instruction or request, or sending a notification or instruction or request and an object that executes LBT.
  • the notification or instruction or request sent is one of the following notifications or instructions or requests: general notification or instruction or request; specific purpose notification or instruction or request; through different service access points (SAP) or channels Or route notifications or instructions or requests sent by higher layers to lower layers; and notifications or instructions or requests from different higher-layer processes or functions or entities.
  • SAP service access points
  • the high-level 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), authorized transmission of uplink configuration And scheduling requests.
  • continuous LBT failure detection random access process
  • random access preamble transmission random access preamble transmission
  • hybrid automatic repeat request HARQ
  • authorized transmission of uplink configuration And scheduling requests HARQ
  • the object performing LBT is characterized by uplink resources or an index corresponding to the uplink resources.
  • the uplink resource includes at least one of a random access resource (RA/PRACH occasion), a valid PUCCH resource of a scheduling request, and a configured grant.
  • the upper layer when maintaining a counter, that is, when it is determined that a counter is incremented by 1 or unchanged or suspended, or when maintaining a timer, that is, when it is determined to start or restart a timer, or when it is determined whether the terminal device or higher layer is triggered
  • the upper layer sends the notification or instruction or request to the lower layer.
  • the counter is one of the following counters: a counter for counting the number of scheduling requests; a counter for applying or suspending power ramp; and a counter for continuous LBT failure detection;
  • the timer is for Configure a grant (CG) timer or a timer for continuous LBT failure detection;
  • the process that triggers the terminal device or higher layer to execute is a random access process or a random access resource selection process.
  • the lower layer is a physical layer
  • the upper layer is a medium access control (MAC) layer.
  • MAC medium access control
  • the device for indicating LBT failure can be configured separately from the processor 2010.
  • the device for indicating LBT failure can be configured as a chip connected to the processor 2010, and the device for indicating LBT failure can be realized through the control of the processor 2010. The function of the device.
  • the terminal device 2000 may further include: a communication module 2030, an input unit 2040, a display 2050, and a power supply 2060. It is worth noting that the terminal device 2000 does not necessarily include all the components shown in FIG. 20; in addition, the terminal device 2000 may also include components not shown in FIG. 20, and related technologies can be referred to.
  • the processor 2010 is sometimes called a controller or an operating control, and may include a microprocessor or other processor device and/or logic device.
  • the processor 2010 receives input and controls the operation of the various components of the terminal device 2000. operate.
  • the memory 2020 may be, for example, one or more of a cache, a flash memory, a hard drive, a removable medium, a volatile memory, a non-volatile memory, or other suitable devices.
  • Various data can be stored, in addition to the program that executes related information.
  • the processor 2010 can execute the program stored in the memory 2020 to implement information storage or processing.
  • the functions of other components are similar to the existing ones, so I won't repeat them 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.
  • the lower layer or the upper layer first determines whether the relevant conditions are met. Based on the result of the judgment, when the uplink transmission is blocked due to LBT failure, it is determined whether the lower layer informs or indicates the LBT failure to the higher layer, or whether the lower layer starts or Stop notifying or indicating the failure of LBT to the upper layer. In this way, the interaction between the lower layer and the upper layer can be reduced, thereby reducing the power consumption of the terminal equipment.
  • the embodiment of the present application provides a network device, and the network device includes the apparatus for indicating LBT failure as described in the fifth embodiment.
  • FIG. 21 is a schematic block diagram of the system configuration of a network device according to Embodiment 7 of the present application.
  • 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 also stores an information processing program 2130, 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 .
  • the function of the device indicating LBT failure may be integrated into the processor 2110.
  • the processor 2110 may be configured to configure high-level parameters for the terminal device, where the high-level parameters are used by the terminal device to determine whether the low-level notifies or indicates the LBT failure to the high-level.
  • the upper layer parameters are also used for the terminal device to determine whether the upper layer sends a notification or instruction or request to the lower layer.
  • the high-level parameters include at least one of the following parameters: parameters used for persistent LBT failure detection for shared spectrum channel access; configuration parameters used for scheduling requests; and authorized configuration parameters used for configuration.
  • the high-level parameters are cell-specific or terminal equipment-specific; and/or, when dual link (DC) is configured, the high-level parameters are in the primary cell group (MCG) and the secondary cell group (SCG) respectively Configured; and/or, when the supplementary uplink (SUL) is configured, the upper layer parameters are configured separately for the supplementary uplink (SUL) and the normal uplink (NUL).
  • DC dual link
  • MCG primary cell group
  • SCG secondary cell group
  • NUL normal uplink
  • the device indicating LBT failure can be configured separately from the processor 2110.
  • the device indicating LBT failure can be configured as a chip connected to the processor 2110, and the device indicating LBT failure can be realized through the control of the processor 2110. The function of the device.
  • the network device 2100 may further include: a transceiver 2140, an antenna 2150, etc.; wherein the functions of the above-mentioned components are similar to those of the prior art, and will not be repeated here. It is worth noting that the network device 2100 does not necessarily include all the components shown in FIG. 21; in addition, the network device 2100 may also include components not shown in FIG. 21, and reference may be made to the prior art.
  • the network device configures the terminal device to determine whether the lower layer informs or indicates the LBT failure to the higher layer.
  • the upper layer parameters are used by the network device.
  • the lower layer or the upper layer first determines whether the relevant conditions are met.
  • 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.
  • the structure of the communication system can refer to FIG. 1.
  • 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 the sixth embodiment.
  • the network equipment recorded in 7 is the same, and the repeated content will not be repeated.
  • the above devices and methods of the present invention can be implemented by hardware, or can be implemented by hardware combined with software.
  • the present invention relates to such a computer-readable program, when the program is executed by a logic component, the logic component can realize the above-mentioned device or constituent component, or the logic component can realize the above-mentioned various methods Or steps.
  • Logic components such as field programmable logic components, microprocessors, processors used in computers, etc.
  • the present invention also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memory, and the like.
  • the method/device described in conjunction with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
  • one or more of the functional block diagrams and/or one or more combinations of the functional block diagrams shown in FIG. 18 may correspond to each software module of the computer program flow, or may correspond to each hardware module.
  • These software modules can respectively correspond to the steps shown in FIG. 4.
  • These hardware modules can be implemented by solidifying these software modules by using a field programmable gate array (FPGA), for example.
  • FPGA field programmable gate array
  • the software module can be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other form of storage medium known in the art.
  • a storage medium may 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 may be a component of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or a large-capacity flash memory device.
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described in FIG. 18 can be implemented as general-purpose processors or digital signal processors ( DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any appropriate combination thereof.
  • DSP digital signal processors
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described with respect to FIG. 18 can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, or multiple microcomputers.
  • a device for indicating LBT failure the device is applied to a terminal device, and the device includes:
  • the first indication unit is used to notify or indicate the LBT failure to the higher layer when the uplink transmission is blocked due to LBT failure when the lower layer or the higher layer determines that the first condition and/or the second condition are satisfied, or the lower layer Begin to notify or indicate LBT failure to senior management; and/or,
  • the second indication unit is used for when the lower layer or the higher layer judges 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 instruct the higher layer LBT fails, or the lower layer stops notifying or indicating LBT failure to the higher layer.
  • 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 equipment performs a shared spectrum channel access operation
  • the uplink transmission is uplink transmission scheduled or configured by a network device
  • the uplink transmission is not Authorized Assisted Access (LAA) or Enhanced Authorized Assisted Access (eLAA);
  • LAA Authorized Assisted Access
  • eLAA Enhanced Authorized Assisted Access
  • the terminal device is not performing authorized assisted access or enhanced authorized assisted access.
  • the uplink transmission is not automatic uplink transmission.
  • the second condition is that high-level parameters are configured and/or capable, and/or,
  • the third condition is release or removal of high-level parameters and/or lack of capability.
  • the high-level parameters are cell-specific or terminal equipment-specific; and/or,
  • the high-level parameters are configured in the primary cell group (MCG) and the secondary cell group (SCG) respectively; and/or,
  • the upper layer parameters are configured separately for the supplementary uplink (SUL) and the normal uplink (NUL).
  • the capability is the capability of NR operation in the shared spectrum channel and/or the capability of continuous LBT detection and recovery.
  • the capabilities are terminal device specific, or cell specific, or frequency band specific or frequency band combination specific.
  • 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 the random access preamble
  • the LBT failure is the failure of the LBT performed for the configured authorization
  • the LBT failure is a failure of the LBT performed for a valid physical uplink control channel (PUCCH) resource of the scheduling request (SR).
  • PUCCH physical uplink control channel
  • the channel corresponding to the LBT is a physical random access channel (PRACH), and the LBT is a resource for random access indicated by a higher layer (RA/PRACH occasion) LBT implemented;
  • PRACH physical random access channel
  • the channel corresponding to the LBT is the physical uplink shared channel (PUSCH), and the LBT is the LBT performed for the configured authorization indicated by the higher layer.
  • PUSCH physical uplink shared channel
  • SAP service access points
  • the high-level 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), authorized transmission of uplink configuration, and scheduling ask.
  • continuous LBT failure detection random access process
  • random access preamble transmission random access preamble transmission
  • hybrid automatic repeat request (HARQ) authorized transmission of uplink configuration
  • the object performing LBT is characterized by uplink resources or an index corresponding to the uplink resources.
  • the uplink resource includes at least one of a random access resource (RA/PRACH occasion), a valid PUCCH resource of a scheduling request, and a configured grant.
  • RA/PRACH occasion a random access resource (RA/PRACH occasion)
  • PUCCH resource of a scheduling request a scheduling request
  • configured grant a configured grant
  • the first processing unit which is used to increase a counter by 1 or remain unchanged or hang up when the higher layer is notified or instructed, or when the higher layer is not notified or instructed; or, to start or restart a timer ; Or, trigger the terminal device or higher layer to execute a process.
  • the timer is a timer for configuration authorization (CG) or a timer for continuous LBT failure detection.
  • the process that triggers the terminal device or the higher layer to execute is a random access process or a random access resource selection process.
  • the device further includes:
  • the third indication unit which is used by the higher layer to send a notification or instruction or request to the lower layer; based on the notification or instruction or request, when the uplink transmission is blocked due to LBT failure, the lower layer informs or instructs the higher layer that the LBT fails, or the lower layer starts Notify or indicate LBT failure to higher layers.
  • the apparatus further includes:
  • the fourth indication unit is used by the higher layer to send a notification or instruction or request to the lower layer; based on the notification or instruction 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, The lower layer stops notifying or indicating LBT failure to the upper layer.
  • notification or instruction or request sent is one of the following notifications or instructions or requests:
  • SAP service access points
  • the high-level 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), authorized transmission of uplink configuration, and scheduling ask.
  • continuous LBT failure detection random access process
  • random access preamble transmission random access preamble transmission
  • hybrid automatic repeat request (HARQ) authorized transmission of uplink configuration
  • the object performing LBT is characterized by uplink resources or an index corresponding to the uplink resources.
  • the uplink resource includes at least one of a random access resource (RA/PRACH occasion), a valid PUCCH resource of a scheduling request, and a configured grant.
  • RA/PRACH occasion a random access resource (RA/PRACH occasion)
  • PUCCH resource of a scheduling request a scheduling request
  • configured grant a configured grant
  • the third instruction unit or the fourth instruction unit is used by the higher layer to send the notification or instruction or request to the lower layer.
  • the counter is one of the following counters: a counter for counting the number of scheduling requests; a counter for applying or suspending power ramp; and a counter for detecting continuous LBT failure;
  • the timer is a timer used for configuration authorization (CG) or a timer used for continuous LBT failure detection;
  • the process that triggers the terminal device or the higher layer to execute is a random access process or a random access resource selection process.
  • the lower layer is a physical layer
  • the upper layer is a medium access control (MAC) layer.
  • MAC medium access control
  • a device for indicating LBT failure is applied to a network device, and the device includes:
  • the configuration unit which configures high-level parameters to the terminal device
  • the high-level parameters are used by the terminal device to determine whether the low-level notifies or indicates the LBT failure to the high-level.
  • the high-level parameters are also used for the terminal device to determine whether the high-level sends a notification or instruction or request to the low-level.
  • 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 ,
  • the second condition is that the high-level parameter is configured and/or the capability is available
  • the third condition is that the high-level parameter is released or removed and/or the capability is not available.
  • the high-level parameters include at least one of the following parameters:
  • the high-level parameters are cell-specific or terminal equipment-specific; and/or,
  • the high-level parameters are configured in the primary cell group (MCG) and the secondary cell group (SCG) respectively; and/or,
  • the upper layer parameters are configured separately for the supplementary uplink (SUL) and the normal uplink (NUL).
  • a terminal device comprising the device according to any one of appendix 1-28.
  • a network device comprising the device according to any one of Supplementary Notes 29-33.
  • a communication system comprising the terminal equipment according to Supplement 34 and/or the network equipment according to Supplement 35.
  • a method for indicating LBT failure is applied to a terminal device, and the method includes:
  • 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 higher layer, or the lower layer starts to notify or indicate the LBT failure to the higher layer ;and / or,
  • the lower layer or the upper layer judges that the first condition and/or the third condition are not satisfied, 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 the higher layer Or indicate that LBT has failed.
  • 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 equipment performs a shared spectrum channel access operation
  • the uplink transmission is uplink transmission scheduled or configured by a network device
  • the uplink transmission is not Authorized Assisted Access (LAA) or Enhanced Authorized Assisted Access (eLAA);
  • LAA Authorized Assisted Access
  • eLAA Enhanced Authorized Assisted Access
  • the terminal device is not performing authorized assisted access or enhanced authorized assisted access.
  • the uplink transmission is not automatic uplink transmission.
  • the second condition is that high-level parameters are configured and/or capable, and/or,
  • the third condition is release or removal of high-level parameters and/or lack of capability.
  • the high-level parameters are cell-specific or terminal equipment-specific; and/or,
  • the high-level parameters are configured in the primary cell group (MCG) and the secondary cell group (SCG) respectively; and/or,
  • the upper layer parameters are configured separately for the supplementary uplink (SUL) and the normal uplink (NUL).
  • the capability is the capability of NR operation in the shared spectrum channel and/or the capability of continuous LBT detection and recovery.
  • the capabilities are terminal device specific, or cell specific, or frequency band specific or frequency band combination specific.
  • 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 the random access preamble
  • the LBT failure is the failure of the LBT performed for the configured authorization
  • the LBT failure is a failure of the LBT performed for a valid physical uplink control channel (PUCCH) resource of the scheduling request (SR).
  • PUCCH physical uplink control channel
  • the channel corresponding to the LBT is a physical random access channel (PRACH), and the LBT is a resource for random access indicated by a higher layer (RA/PRACH occasion) LBT implemented;
  • PRACH physical random access channel
  • the channel corresponding to the LBT is the physical uplink shared channel (PUSCH), and the LBT is the LBT performed for the configured authorization indicated by the higher layer.
  • PUSCH physical uplink shared channel
  • SAP service access points
  • the high-level 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), authorized transmission of uplink configuration, and scheduling ask.
  • continuous LBT failure detection random access process
  • random access preamble transmission random access preamble transmission
  • hybrid automatic repeat request (HARQ) authorized transmission of uplink configuration
  • the object performing LBT is characterized by uplink resources or an index corresponding to the uplink resources.
  • the uplink resource includes at least one of a random access resource (RA/PRACH occasion), a valid PUCCH resource of a scheduling request, and a configured grant.
  • RA/PRACH occasion a random access resource (RA/PRACH occasion)
  • PUCCH resource of a scheduling request a scheduling request
  • configured grant a configured grant
  • a counter is incremented by 1 or remains unchanged or suspended; or, a timer is started or restarted; or, a terminal device or higher layer is triggered to execute a process.
  • the timer is a timer for configuration authorization (CG) or a timer for continuous LBT failure detection.
  • the process that triggers the terminal device or the higher layer to execute is a random access process or a random access resource selection process.
  • the method further includes:
  • the upper layer sends a notification or instruction or request to the lower layer; based on the notification or instruction 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 the lower layer starts to notify or indicate the LBT failure to the upper layer.
  • the method further includes:
  • the upper layer sends a notification or instruction or request to the lower layer; based on the notification or instruction 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 upper layer, or the lower layer stops notifying or indicating the LBT failure to the upper layer .
  • SAP service access points
  • the high-level 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), authorized transmission of uplink configuration, and scheduling ask.
  • continuous LBT failure detection random access process
  • random access preamble transmission random access preamble transmission
  • hybrid automatic repeat request (HARQ) authorized transmission of uplink configuration
  • the object performing LBT is characterized by uplink resources or an index corresponding to the uplink resources.
  • the uplink resource includes at least one of a random access resource (RA/PRACH occasion), a valid PUCCH resource of a scheduling request, and a configured grant.
  • RA/PRACH occasion a random access resource (RA/PRACH occasion)
  • PUCCH resource of a scheduling request a scheduling request
  • configured grant a configured grant
  • the higher layer When maintaining a counter, that is, when it is determined that a counter is incremented by 1 or unchanged or suspended, or when maintaining a timer, that is, when it is determined to start or restart a timer, or when it is determined whether to trigger the terminal device or the higher layer to execute a timer During the process, the higher layer sends the notification or instruction or request to the lower layer.
  • the counter is one of the following counters: a counter for counting the number of scheduling requests; a counter for applying or suspending power ramp; and a counter for detecting continuous LBT failure;
  • the timer is a timer used for configuration authorization (CG) or a timer used for continuous LBT failure detection;
  • the process that triggers the terminal device or the higher layer to execute is a random access process or a random access resource selection process.
  • the lower layer is a physical layer
  • the upper layer is a medium access control (MAC) layer.
  • MAC medium access control
  • a method for indicating LBT failure is applied to a network device, and the method includes:
  • the high-level parameters are used by the terminal device to determine whether the low-level notifies or indicates the LBT failure to the high-level.
  • the high-level parameters are also used for the terminal device to determine whether the high-level sends a notification or instruction or request to the low-level.
  • 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 ,
  • the second condition is that the high-level parameter is configured and/or the capability is available
  • the third condition is that the high-level parameter is released or removed and/or the capability is not available.
  • the high-level parameters include at least one of the following parameters:
  • the high-level parameters are cell-specific or terminal equipment-specific; and/or,
  • the high-level parameters are configured in the primary cell group (MCG) and the secondary cell group (SCG) respectively; and/or,
  • the upper layer parameters are configured separately for the supplementary uplink (SUL) and the normal uplink (NUL).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种指示LBT失败的方法及装置。所述方法应用于终端设备，所述方法包括：当低层或高层判断满足第一条件和/或第二条件时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败；和/或，当低层或高层判断不满足所述第一条件和/或满足第三条件时，低层不向高层通知或指示LBT失败，或者低层停止向高层通知或指示LBT失败。

Description

指示LBT失败的方法及装置 技术领域
本发明涉及通信领域。
背景技术
为了在未授权频段上提供3GPP服务，引入了以下机制：通话前监听(Listen Before Talk，LBT)以及发现信号测量定时配置(Discovery RS Measurement Timing Configuration，DMTC)。其中，低层执行LBT过程，根据LBT结果，如果信道确定被占用，不进行传输。当低层在传输前执行了LBT过程且该传输未执行，即上行传输由于LBT失败被阻止时，低层向高层指示LBT失败。
应该注意，上面对技术背景的介绍只是为了方便，对本发明的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本发明的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
在未授权频段上的新无线(NR-U)系统中，引入了上行传输的持续LBT失败检测和恢复机制。
无线资源控制(Radio Resource Control，RRC)层可以为高层，例如MAC层的MAC实体配置持续LBT失败的恢复过程。持续LBT失败的检测是在每个上行BWP(Bandwidth part)上进行的。为此引入一个计数器和一个定时器，当上行LBT失败发生时，启动或重启定时器，每当高层(例如MAC层)收到来自低层(例如物理层)的上行LBT失败指示时，计数器加1，当该计数器的计数值超过预设的数值时，触发持续LBT失败。另外当定时器超时时，该计数器重置。该过程可以看作持续(上行)LBT失败检测过程或持续(上行)LBT失败检测过程的一部分或一个步骤。
发明人发现，按照现有的机制，为了实现高层的上行传输的持续LBT失败检测机制，低层需要为MAC层提供指示，即任意上行传输由于LBT失败被阻止或信道接入失败(channel access failure)时，低层通知或指示给高层。
但是，在低层，包括数据、控制信息和参考信号的上行传输可能随时发生，如果 每当上行传输由于LBT失败被阻止时，低层就通知或指示给高层，会大大增加低层和高层的层间交互，并增加终端设备的耗电。
为了解决上述问题中的一个或多个，本申请实施例提供了一种指示LBT失败的方法及装置。
根据本申请实施例的第一方面，提供了一种指示LBT失败的装置，所述装置应用于终端设备，所述装置包括：第一指示单元，其在低层或高层判断满足第一条件和/或第二条件的情况下，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败；和/或，第二指示单元，其在低层或高层判断不满足所述第一条件和/或满足第三条件的情况下，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者，低层停止向高层通知或指示LBT失败。
根据本申请实施例的第二方面，提供了一种指示LBT失败的装置，所述装置应用于网络设备，所述装置包括：配置单元，其向终端设备配置高层参数，所述高层参数用于终端设备确定低层是否向高层通知或指示LBT失败。
根据本申请实施例的第三方面，提供了一种终端设备，所述终端设备包括根据本申请实施例的第一方面所述的装置。
根据本申请实施例的第四方面，提供了一种网络设备，所述网络设备包括根据本申请实施例的第二方面所述的装置。
根据本申请实施例的第五方面，提供了一种通信系统，所述通信系统包括根据本申请实施例的第三方面所述的终端设备和/或根据本申请实施例的第四方面所述的网络设备。
根据本申请实施例的第六方面，提供了一种指示LBT失败的方法，所述方法应用于终端设备，所述方法包括：在低层或高层判断满足第一条件和/或第二条件的情况下，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败；和/或，在低层或高层判断不满足所述第一条件和/或满足第三条件的情况下，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者低层停止向高层通知或指示LBT失败。
根据本申请实施例的第七方面，提供了一种指示LBT失败的方法，所述方法应用于网络设备，所述方法包括：向终端设备配置高层参数，所述高层参数用于终端设 备确定低层是否向高层通知或指示LBT失败。
根据本申请实施例的第八方面，提供了一种计算机可读程序，其中当在指示LBT失败的装置或终端设备中执行所述程序时，所述程序使得所述指示LBT失败的装置或终端设备执行本发明实施例的第六方面所述的指示LBT失败的方法。
根据本发明实施例的第九方面，提供了一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得指示LBT失败的装置或终端设备执行本发明实施例的第六方面所述的指示LBT失败的方法。
根据本申请实施例的第十方面，提供了一种计算机可读程序，其中当在指示LBT失败的装置或网络设备中执行所述程序时，所述程序使得所述指示LBT失败的装置或网络设备执行本发明实施例的第七方面所述的指示LBT失败的方法。
根据本发明实施例的第十一方面，提供了一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得指示LBT失败的装置或网络设备执行本发明实施例的第七方面所述的指示LBT失败的方法。
本申请实施例的有益效果在于：低层或高层先判断是否满足相关的条件，基于判断的结果，当上行传输由于LBT失败而被阻止时，确定低层是否向高层通知或指示LBT失败，或者确定低层是否开始或停止向高层通知或指示LBT失败，这样，能够减少低层和高层的层间交互，从而减少终端设备的耗电。
参照后文的说明和附图，详细公开了本发明的特定实施方式，指明了本发明的原理可以被采用的方式。应该理解，本发明的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本发明的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含/具有”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标 号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
所包括的附图用来提供对本申请实施例的进一步的理解，其构成了说明书的一部分，用于例示本发明的实施方式，并与文字描述一起来阐释本发明的原理。显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其它的附图。在附图中：
图1是本申请实施例的通信系统的一示意图；
图2是现有的指示LBT失败机制的一示意图；
图3是本申请实施例的指示LBT失败机制的一示意图；
图4是本申请实施例1的指示LBT失败的方法的一示意图；
图5是本申请实施例1的指示LBT失败的方法的另一示意图；
图6是本申请实施例1的指示LBT失败的方法的另一示意图；
图7是本申请实施例1的指示LBT失败的方法的另一示意图；
图8本申请实施例2的指示LBT失败的方法的一示意图；
图9是本申请实施例1的指示LBT失败的方法的另一示意图；
图10是本申请实施例1的指示LBT失败的方法的另一示意图；
图11是本申请实施例1的指示LBT失败的方法的另一示意图；
图12是本申请实施例1的指示LBT失败的方法的另一示意图；
图13是本申请实施例1的指示LBT失败的方法的另一示意图；
图14本申请实施例2的指示LBT失败的方法的一示意图；
图15是本申请实施例3的指示LBT失败的方法的一示意图；
图16是本申请实施例3的指示LBT失败的方法的另一示意图；
图17是本申请实施例3的指示LBT失败的方法的另一示意图；
图18是本申请实施例4的指示LBT失败的装置的一示意图；
图19是本申请实施例5的指示LBT失败的装置的一示意图；
图20是本申请实施例6的终端设备的系统构成的一示意框图；
图21是本申请实施例7的网络设备的系统构成的一示意框图。
具体实施方式
参照附图，通过下面的说明书，本发明的前述以及其它特征将变得明显。在说明 书和附图中，具体公开了本发明的特定实施方式，其表明了其中可以采用本发明的原则的部分实施方式，应了解的是，本发明不限于所描述的实施方式，相反，本发明包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及未来的5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将用户设备接入通信网络并为该用户设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio  Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)例如是指通过网络设备接入通信网络并接收网络服务的设备，也可以称为“终端设备”(TE，Terminal Equipment)。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
在本申请实施例中，“当……时”、“在……情况下”、“对于……的情况”以及“如果……”都表示基于某个或某些条件或状态等，另外，这些表述方式可以互相替换。
以下通过示例对本申请实施例的场景进行说明，但本发明不限于此。
图1是本申请实施例的通信系统的一示意图，其示意性说明了以终端设备和网络设备为例的情况，如图1所示，通信系统100可以包括：网络设备101和终端设备102。为简单起见，图1仅以一个终端设备为例进行说明。网络设备101例如为NR的网络设备gNB。
在本申请实施例中，网络设备101和终端设备102之间可以进行现有的业务或者未来可实施的业务。例如，这些业务包括但不限于：增强的移动宽带(eMBB，enhanced Mobile Broadband)、大规模机器类型通信(mMTC，massive Machine Type Communication)和高可靠低时延通信(URLLC，Ultra-Reliable and Low-Latency Communication)，等等。
当终端设备102进行LBT时，可能发生LBT失败。图2是现有的指示LBT失败机制的一示意图。如图2所示，终端设备102的低层(例如物理层)执行LBT过程，当低层在上行传输前执行了LBT过程且该上行传输未执行，即上行传输由于LBT失败被阻止时，低层向高层(例如MAC层)指示或通知该LBT失败。这样，每当上行传输由于LBT失败被阻止时，低层就通知或指示给高层，会大大增加低层和高层之间的交互，并增加终端设备102的耗电。
图3是本申请实施例的指示LBT失败机制的一示意图。如图3所示，终端设备102的低层执行LBT过程，低层或高层先判断是否满足相关的条件，在判断的结果是满足相关的条件的情况下，当低层在上行传输前执行了LBT过程且该上行传输未执行，即上行传输由于LBT失败被阻止时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败，在判断的结果是不满足相关的条件的情况下，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者，低层停止向高层通知或指示LBT失败。这样，能够减少低层和高层之间的交互，并减少终端设备102的耗电。
下面结合附图对本申请实施例的各种实施方式进行说明。这些实施方式只是示例性的，不是对本发明的限制。
实施例1
本申请实施例提供了一种指示LBT失败的方法，该方法应用于终端设备。
图4是本申请实施例1的指示LBT失败的方法的一示意图。如图4所示，该方法包括：
步骤401：在低层或高层判断满足第一条件和/或第二条件的情况下，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败；和/或，
步骤402：在低层或高层判断不满足该第一条件和/或满足第三条件的情况下，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者低层停止向高层通知或指示LBT失败。
在本申请实施例中，该方法可以包括步骤401中步骤402中的一个，也可以包括步骤401和步骤402这两个步骤，当该方法包括步骤401和步骤402这两个步骤时，不对步骤401和步骤402的执行顺序进行限制。
由此，低层或高层先判断是否满足相关的条件，基于判断的结果，当上行传输由于LBT失败而被阻止时，确定低层是否向高层通知或指示LBT失败，或者确定低层是否开始或停止向高层通知或指示LBT失败，这样，能够减少低层和高层的层间交互，从而减少终端设备的耗电。
在本申请实施例中，低层例如是物理层，高层例如是MAC层。
以下，针对低层或高层判断是否满足各个具体条件，对各种情况进行示例性的说明。
情况1、低层判断是否满足第一条件：图5是本申请实施例1的指示LBT失败的方法的另一示意图。如图5所示，该方法包括：
步骤501：在低层判断满足第一条件的情况下，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败；和/或，
步骤502：在低层判断不满足该第一条件的情况下，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者低层停止向高层通知或指示LBT失败。
在本申请实施例中，该方法可以包括步骤501中步骤502中的一个，也可以包括步骤501和步骤502这两个步骤，当该方法包括步骤501和步骤502这两个步骤时，不对步骤501和步骤502的执行顺序进行限制。
在本申请的至少一个实施例中，例如，该第一条件包括以下条件中的至少一个：该终端设备是NR-U终端；该终端设备是NR终端；该终端设备是NR-U终端或NR终端；该上行传输或该终端设备进行共享频谱信道接入操作；该上行传输是网络设备调度或配置的上行传输；该上行传输不是授权辅助接入(Licensed Assisted Access，LAA)或增强型授权辅助接入(Enhanced Licensed Assisted Access，eLAA)；该终端设备不是进行授权辅助接入或增强型授权辅助接入；以及该上行传输不是自动上行传输。
也就是说，当该终端设备是NR-U终端、该终端设备是NR终端、该终端设备是NR-U终端或NR终端、该上行传输或该终端设备进行共享频谱信道接入操作、该上行传输是网络设备调度或配置的上行传输、该上行传输不是授权辅助接入(Licensed Assisted Access，LAA)或增强型授权辅助接入(Enhanced Licensed Assisted Access， eLAA)、该终端设备不是进行授权辅助接入或增强型授权辅助接入、以及该上行传输不是自动上行传输中的至少一个成立时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败。另外，当以上列出的所有条件都不成立时，低层不向高层通知或指示LBT失败，或者低层停止向高层通知或指示LBT失败。
或者，也可以说，对于NR-U终端、NR终端、NR-U终端或NR终端、进行共享频谱信道接入操作、网络设备调度或配置的上行传输、非LAA或eLAA、以及非AUL中的至少一个，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败。
根据情况1所述的方法，不仅能够减少低层和高层的层间交互，从而减少终端设备的耗电，且该方法较为简单，对标准影响小，并且能够降低终端设备的成本，也能降低测试成本。
在本申请的至少一个实施例中，在步骤501中，通知或指示LBT失败，包括：发送一个通知或指示，或者，发送一个通知或指示和执行LBT的对象。
也就是说，可以通过低层向高层发送的一个通知或指示进行上述通知或指示，也可以是通过低层向高层发送的一个通知或指示以及执行LBT的对象来进行上述通知或指示。
例如，发送的该通知或指示可以是以下通知或指示中的一个：
通用的通知或指示(generic indication or notification)；
特定用途的通知或指示，例如，持续UL LBT失败检测的指示，或者，随机接入前导码的指示，或者，配置的授权的指示，或者，调度请求(Scheduling Request，SR)的指示；
通过不同的服务访问点(Service Access Point，SAP)或通道或路径由低层发送给高层的通知或指示；以及
提供给不同高层过程或功能或实体的通知或指示，例如，该高层过程或功能或实体是指以下中的至少一个：持续LBT失败检测、随机接入过程、随机接入前导码传输、混合自动重传请求(Hybrid Automatic Repeat Request，HARQ)、上行配置的授权的传输以及调度请求(SR)。
在本申请的至少一个实施例中，对于通过低层向高层发送的一个通知或指示以及执行LBT的对象来进行上述通知或指示的情况，执行LBT的对象可以通过上行资源 或者与上行资源对应的索引表征。
例如，该上行资源包括随机接入的资源(RA/PRACH occasion)、调度请求(SR)的一个有效的PUCCH资源以及配置的授权中的至少一个。
对于执行LBT的对象通过与上行资源对应的索引表征的情况，例如，定义一种映射关系，该对象可以用相应的索引表征，例如：定义随机接入的资源(RA/PRACH occasion)对应索引1，SR的一个有效的PUCCH资源对应索引2，配置的授权对应索引3。
在本申请的至少一个实施例中，当低层判断满足第一条件时且低层判断满足第四条件时，低层向高层通知或指示LBT失败。这样，通过进一步限制条件，能够进一步减少低层和高层的层间交互，从而进一步减少终端设备的耗电。
图6是本申请实施例1的指示LBT失败的方法的另一示意图。如图6所示，该方法包括：
步骤601：在低层判断满足第一条件和第四条件的情况下，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败。
在本申请的至少一个实施例中，该第四条件包括以下条件中的至少一个：该LBT失败是任意一次的LBT失败；该LBT失败是为随机接入前导码的传输所执行的LBT失败；该LBT失败是为配置的授权所执行的LBT失败；以及该LBT失败是为调度请求(SR)的一个有效的物理上行控制信道(Physical Uplink Control Channel，PUCCH)资源所执行的LBT失败。
在本申请的至少一个实施例中，对于该LBT失败是任意一次的LBT失败的情况，即，即对于一个上行传输，终端设备或低层未能接入信道，如果低层判断同时满足第一条件，则低层向高层通知或指示LBT失败。
例如，该上行传输是高层(例如MAC层)指示的，或者低层(例如物理层)自己触发或生成的，例如，确认或不确认(ACK或NACK)，探测参考信号(Sounding Reference Signal，SRS)，信道质量指示(channel quality indication，CQI)等；
例如，对于上行传输使用的信道不进行限制，例如，该上行传输可能在物理上行控制信道(PUCCH)或物理上行共享信道(Physical Uplink Shared Channel，PUSCH)或物理随机接入信道(Physical Random Access Channel，PRACH)上进行；
例如，对于所执行的LBT的LBT类型不限，例如，所执行的LBT的LBT类型可以是LBT type 2或LBT type 4等；
例如，所执行的LBT的信道接入优先级等级(Channel Access Priority Class，CAPC)不限，例如CAPC优先级为1或4等。
在本申请的至少一个实施例中，对于该LBT失败是为随机接入前导码(RA preamble)的传输所执行的LBT失败的情况，即，为了发送RA preamble，终端设备或低层未能接入信道，如果低层判断同时满足第一条件，则低层向高层通知或指示LBT失败。
例如，该LBT对应的信道是物理随机接入信道(PRACH)，该LBT是对高层指示的随机接入的资源(RA/PRACH occasion)所执行的LBT；
例如，该上行传输是高层(例如MAC层)指示的，或者低层(例如物理层)自己触发或生成的，例如，物理层的重复传输(repetition)；
例如，对于所执行的LBT的LBT类型不限，例如，所执行的LBT的LBT类型可以是LBT type 2或LBT type 4等；
例如，所执行的LBT的信道接入优先级等级(Channel Access Priority Class，CAPC)不限，例如CAPC优先级为1或4等。
在本申请的至少一个实施例中，对于该LBT失败是为配置的授权所执行的LBT失败的情况，即，为了发送配置授权上的上行传输，终端设备或低层未能接入信道，如果低层判断同时满足第一条件，则低层向高层通知或指示LBT失败。
例如，该LBT对应的信道是物理上行共享信道(PUSCH)，该LBT是对高层指示的配置的授权进行的LBT；
例如，对于所执行的LBT的LBT类型不限，例如，所执行的LBT的LBT类型可以是LBT type 2或LBT type 4等；
例如，所执行的LBT的信道接入优先级等级(Channel Access Priority Class，CAPC)不限，例如CAPC优先级为1或4等。
在本申请的至少一个实施例中，对于该LBT失败是为调度请求(SR)的一个有效的物理上行控制信道(PUCCH)资源所执行的LBT失败的情况，即，为了在一个有效的PUCCH资源上发送SR，终端设备或低层未能接入信道未能接入信道，如果低层判断同时满足第一条件，则低层向高层通知或指示LBT失败。
例如，该LBT对应的信道是物理上行控制信道(PUCCH)，该LBT是对高层指示的一个SR的有效的PUCCH资源进行的LBT；
例如，对于所执行的LBT的LBT类型不限，例如，所执行的LBT的LBT类型可以是LBT type 2或LBT type 4等；
例如，所执行的LBT的信道接入优先级等级(Channel Access Priority Class，CAPC)不限，例如CAPC优先级为1或4等。
在本申请的至少一个实施例中，如图5所示，该方法还可以包括：
步骤503：当该高层被通知或指示时或者当该高层未被通知或指示时，一个计数器加1或不变或挂起，或者，启动或重启一个定时器，或者，触发终端设备或高层执行一个过程。
在本申请的至少一个实施例中，该计数器是以下计数器中的一个：
用于计算调度请求数量的计数器，例如，计数器SR_COUNTER；
用于应用或挂起功率爬坡的计数器，例如，计数器PREAMBLE_POWER_RAMPING_COUNTER；以及
用于持续LBT失败检测的计数器，例如，计数器LBT_COUNTER。
在本申请的至少一个实施例中，该定时器是用于配置授权(CG)的定时器，例如，例如configuredGrantTimer或cg-RetransmissionTimer，或者，该定时器是用于持续LBT失败检测的定时器，例如lbt-FailureDetectionTimer。
在本申请的至少一个实施例中，触发终端设备或高层执行的该过程是随机接入过程或随机接入资源选择过程。
这样，对于本申请实施例中的低层向高层通知或指示LBT失败，该通知或指示不仅能够通知或指示LBT失败，还可以根据高层是否被通知或指示，触发其他的行为或操作或过程，例如上面所述的，对于用于调度请求的计数器或用于应用或挂起功率爬坡的计数器的操作，和/或，触发随机接入过程或随机接入资源选择过程。
情况2、低层判断是否满足第二条件和/或第三条件：
图7是本申请实施例1的指示LBT失败的方法的另一示意图。如图7所示，该方法包括：
步骤701：在低层判断满足第二条件的情况下，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT 失败；和/或，
步骤702：在低层判断满足第三条件的情况下，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者，低层向高层停止通知或指示LBT失败。
在本申请实施例中，该方法可以包括步骤701中步骤702中的一个，也可以包括步骤701和步骤702这两个步骤，当该方法包括步骤701和步骤702这两个步骤时，不对步骤701和步骤702的执行顺序进行限制。
在本申请的至少一个实施例中，该第二条件是配置了高层参数和/或具备能力，和/或，该第三条件是释放或移除了高层参数和/或不具备能力。
例如，该高层参数是RRC参数。
图8是本申请实施例1的指示LBT失败的方法的一示意图。如图8所示，该方法包括：
步骤801：在低层判断配置了高层参数和/或具备能力的情况下，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败；和/或，
步骤802：在低层判断释放或移除了高层参数和/或不具备能力的情况下，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者低层向高层停止通知或指示LBT失败。
在本申请实施例中，该方法可以包括步骤801中步骤802中的一个，也可以包括步骤801和步骤802这两个步骤，当该方法包括步骤801和步骤802这两个步骤时，不对步骤801和步骤802的执行顺序进行限制。
情况2所述的方法限制了更为精确的条件，能够进一步减少低层和高层的层间交互，从而进一步减少终端设备的耗电。
在本申请的至少一个实施例中，该高层参数包括以下参数中的至少一个：用于共享频谱信道接入的持续LBT失败检测的参数；用于调度请求的配置参数；用于配置的授权的配置参数。
对于用于共享频谱信道接入的持续LBT失败检测的参数，例如，该高层参数是lbt-FailureRecoveryConfig，又例如，该高层参数是小区特定的或者终端设备特定的；和/或，当配置了双链接(DC)时，该高层参数是在主小区组(MCG)和辅小区组(SCG) 分别配置的；和/或，当配置了补充上行链路(SUL)时，该高层参数是补充上行链路(SUL)和正常上行链路(NUL)分别配置的。
对于用于调度请求的配置参数，例如，该高层参数是用于配置专用调度请求资源的参数，例如SchedulingRequestConfig；又例如，该高层参数是SR传输最大次数的参数，例如sr-TransMax。
对于用于配置的授权的配置参数，例如，该高层参数是用于配置没有动态授权的上行传输的参数，例如ConfiguredGrantConfig；又例如，该高层参数是用于CG的定时器的参数，例如configuredGrantTimer或cg-RetransmissionTimer。
在本申请的至少一个实施例中，该能力是共享频谱信道里的NR操作的能力和/或持续LBT检测和恢复的能力。
在本申请的至少一个实施例中，该能力是终端设备特定的；或者，该能力是小区特定的，例如，主小区(PCell)，主辅小区(PSCell)和辅小区(SCell)各自单独的能力；或者，该能力是频带特定或频带组合特定的。
在本申请的至少一个实施例中，在步骤701或步骤801中，通知或指示LBT失败，包括：发送一个通知或指示，或者，发送一个通知或指示和执行LBT的对象。
也就是说，可以通过低层向高层发送的一个通知或指示进行上述通知或指示，也可以是通过低层向高层发送的一个通知或指示以及执行LBT的对象来进行上述通知或指示。
在情况2中，通过低层向高层发送的一个通知或指示进行上述通知或指示以及通过低层向高层发送的一个通知或指示以及执行LBT的对象来进行上述通知或指示的具体方法可以与情况1中的记载相同，此处不再重复说明。
在本申请的至少一个实施例中，当低层判断满足第二条件时且低层判断满足第四条件时，低层向高层通知或指示LBT失败。这样，通过进一步限制条件，能够进一步减少低层和高层的层间交互，从而进一步减少终端设备的耗电。
图9是本申请实施例1的指示LBT失败的方法的另一示意图。如图9所示，该方法包括：
步骤901：在低层判断满足第二条件和第四条件的情况下，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败。
在本申请的至少一个实施例中，该第四条件包括以下条件中的至少一个：该LBT失败是任意一次的LBT失败；该LBT失败是为随机接入前导码的传输所执行的LBT失败；该LBT失败是为配置的授权所执行的LBT失败；以及该LBT失败是为调度请求(SR)的一个有效的物理上行控制信道(Physical Uplink Control Channel，PUCCH)资源所执行的LBT失败。
在情况2中，上述第四条件的具体内容可以与情况1中的记载相同，此处不再重复说明。
在本申请的至少一个实施例中，与情况1中的步骤503类似，如图7所示，该方法还可以包括：
步骤703：当该高层被通知或指示时或者当该高层未被通知或指示时，一个计数器加1或不变或挂起，或者，启动或重启一个定时器，或者，触发终端设备或高层执行一个过程。
在情况2中，该计数器、定时器以及触发终端设备或高层执行的该过程的具体内容可以与情况1中的记载相同，此处不再重复说明。
情况3、高层判断是否满足第一条件：
图10是本申请实施例1的指示LBT失败的方法的另一示意图。如图10所示，该方法包括：
步骤1001：在高层判断满足第一条件的情况下，高层向低层发送通知或指示或请求；
步骤1002：当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者，低层向高层开始通知或指示LBT失败。
也就是说，在由高层判断满足第一条件的情况下，高层向低层发送通知或指示或请求，低层根据该通知或指示或请求，当上行传输由于LBT失败而被阻止时，向高层通知或指示LBT失败，或者，开始通知或指示LBT失败。
图11是本申请实施例1的指示LBT失败的方法的另一示意图。如图11所示，该方法包括：
步骤1101：在高层判断不满足第一条件的情况下，高层向低层发送通知或指示或请求；
步骤1102：当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT 失败，或者，低层向高层停止通知或指示LBT失败。
也就是说，当在由高层判断不满足第一条件的情况下，高层向低层发送通知或指示或请求，低层根据该通知或指示或请求，当上行传输由于LBT失败而被阻止时，不向高层通知或指示LBT失败，或者，停止通知或指示LBT失败。
情况3所述的方法限制了更为精确的条件，能够进一步减少低层和高层的层间交互，从而进一步减少终端设备的耗电。
在本申请的至少一个实施例中，例如，该第一条件的具体内容和情况1中的记载相同。
也就是说，当该终端设备是NR-U终端、该终端设备是NR终端、该终端设备是NR-U终端或NR终端、该上行传输或该终端设备进行共享频谱信道接入操作、该上行传输是网络设备调度或配置的上行传输、该上行传输不是授权辅助接入(Licensed Assisted Access，LAA)或增强型授权辅助接入(Enhanced Licensed Assisted Access，eLAA)、该终端设备不是进行授权辅助接入或增强型授权辅助接入、以及该上行传输不是自动上行传输中的至少一个成立时，高层向低层发送通知或指示或请求，以使得低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败。另外，当以上列出的所有条件都不成立时，高层向低层发送通知或指示或请求，以使得低层不向高层通知或指示LBT失败，或者低层停止向高层通知或指示LBT失败。
或者，也可以说，对于NR-U终端、NR终端、NR-U终端或NR终端、进行共享频谱信道接入操作、网络设备调度或配置的上行传输、非LAA或eLAA、以及非AUL中的至少一个，高层向低层发送通知或指示或请求，以使得低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败。
在本申请的至少一个实施例中，在步骤1002中，通知或指示LBT失败，包括：发送一个通知或指示，或者，发送一个通知或指示和执行LBT的对象。其具体的内容与情况1中的记载相同，此处不再重复说明。
在本申请的至少一个实施例中，在步骤1001和/或步骤1101中，该通知或指示或请求，包括：发送一个通知或指示或请求，或者，发送一个通知或指示或请求和执行LBT的对象。也就是说，可以通过高层向低层发送的一个通知或指示或请求进行上述通知或指示或请求，也可以是通过高层向低层发送的一个通知或指示或请求以及执行LBT的对象来进行上述通知或指示或请求。
例如，高层向低层发送的该通知或指示或请求是以下通知或指示或请求中的一个：
通用的通知或指示(generic indication or notification)；
特定用途的通知或指示，例如，持续UL LBT失败检测的指示，或者，随机接入前导码的指示，或者，配置的授权的指示，或者，调度请求(Scheduling Request，SR)的指示；
通过不同的服务访问点(Service Access Point，SAP)或通道或路径由低层发送给高层的通知或指示；以及
提供给不同高层过程或功能或实体的通知或指示，例如，该高层过程或功能或实体是指以下中的至少一个：持续LBT失败检测、随机接入过程、随机接入前导码传输、混合自动重传请求(Hybrid Automatic Repeat Request，HARQ)、上行配置的授权的传输以及调度请求(SR)。
在本申请的至少一个实施例中，对于通过高层向低层发送的一个通知或指示或请求以及执行LBT的对象来进行上述通知或指示或请求的情况，执行LBT的对象可以通过上行资源或者与上行资源对应的索引表征。
例如，该上行资源包括随机接入的资源(RA/PRACH occasion)、调度请求(SR)的一个有效的PUCCH资源以及配置的授权中的至少一个。
对于执行LBT的对象通过与上行资源对应的索引表征的情况，例如，定义一种映射关系，该对象可以用相应的索引表征，例如：定义随机接入的资源(RA/PRACH occasion)对应索引1，SR的一个有效的PUCCH资源对应索引2，配置的授权对应索引3。
在本申请的至少一个实施例中，在步骤1001中，当高层判断满足第一条件时且高层判断满足第四条件时，高层向低层发送通知或指示或请求。这样，通过进一步限制条件，能够进一步减少低层和高层的层间交互，从而进一步减少终端设备的耗电。
在情况3中，上述第四条件的具体内容可以与情况1中的记载相同，此处不再重复说明。
在本申请的至少一个实施例中，在步骤1001中，当维护一个计数器时，即确定一个计数器加1或不变或挂起时，或者，当维护一个定时器，即确定启动或重启一个定时器时，或者，当确定触发终端设备或高层是否执行一个过程时，高层向低层发送 该通知或指示或请求。
在本申请的至少一个实施例中，该计数器是以下计数器中的一个：
用于计算调度请求数量的计数器，例如，计数器SR_COUNTER；
用于应用或挂起功率爬坡的计数器，例如，计数器PREAMBLE_POWER_RAMPING_COUNTER；以及
用于持续LBT失败检测的计数器，例如，计数器LBT_COUNTER。
在本申请的至少一个实施例中，该定时器是用于配置授权(CG)的定时器，例如，例如configuredGrantTimer或cg-RetransmissionTimer，或者，该定时器是用于持续LBT失败检测的定时器，例如lbt-FailureDetectionTimer。
在本申请的至少一个实施例中，触发终端设备或高层执行的该过程是随机接入过程或随机接入资源选择过程。
在本申请的至少一个实施例中，与情况1的步骤503类似，如图10所示，该方法还可以包括：
步骤1003：当该高层被通知或指示时或者当该高层未被通知或指示时，一个计数器加1或不变或挂起，或者，启动或重启一个定时器，或者，触发终端设备或高层执行一个过程。
在本申请的至少一个实施例中，与情况1的步骤503类似，如图11所示，该方法还可以包括：
步骤1103：当该高层未被通知或指示时或者当该高层未被通知或指示时，一个计数器加1或不变或挂起，或者，启动或重启一个定时器，或者，触发终端设备或高层执行一个过程。
在情况3中，该计数器、定时器以及触发终端设备或高层执行的该过程的具体内容可以与情况1中的记载相同，此处不再重复说明。
情况4、高层判断是否满足第二条件和/或第三条件：
图12是本申请实施例1的指示LBT失败的方法的另一示意图。如图12所示，该方法包括：
步骤1201：在高层判断满足第二条件的情况下，高层向低层发送通知或指示或请求；
步骤1202：当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT 失败，或者，低层开始向高层通知或指示LBT失败。
也就是说，在由高层判断满足第二条件的情况下，高层向低层发送通知或指示或请求，低层根据该通知或指示或请求，当上行传输由于LBT失败而被阻止时，向高层通知或指示LBT失败，或者，开始通知或指示LBT失败。
图13是本申请实施例1的指示LBT失败的方法的另一示意图。如图13所示，该方法包括：
步骤1301：在高层判断满足第三条件的情况下，高层向低层发送通知或指示或请求；
步骤1302：当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者，低层向高层停止通知或指示LBT失败。
也就是说，在由高层判断满足第三条件的情况下，高层向低层发送通知或指示或请求，低层根据该通知或指示或请求，当上行传输由于LBT失败而被阻止时，不向高层通知或指示LBT失败，或者，停止通知或指示LBT失败。
情况4所述的方法限制了更为精确的条件，能够进一步减少低层和高层的层间交互，从而进一步减少终端设备的耗电。
在本申请的至少一个实施例中，该第二条件是配置了高层参数和/或具备能力，和/或，该第三条件是释放或移除了高层参数和/或不具备能力。
在情况4中，该高层参数以及能力的具体内容可以与情况2中的记载相同，此处不再重复说明。
在本申请的至少一个实施例中，在步骤1201和/或步骤1301中，该通知或指示或请求，包括：发送一个通知或指示或请求，或者，发送一个通知或指示或请求和执行LBT的对象。也就是说，可以通过高层向低层发送的一个通知或指示或请求进行上述通知或指示或请求，也可以是通过高层向低层发送的一个通知或指示或请求以及执行LBT的对象来进行上述通知或指示或请求。
例如，高层向低层发送的该通知或指示或请求是以下通知或指示或请求中的一个：
通用的通知或指示(generic indication or notification)；
特定用途的通知或指示，例如，持续UL LBT失败检测的指示，或者，随机接入前导码的指示，或者，配置的授权的指示，或者，调度请求(Scheduling Request，SR) 的指示；
通过不同的服务访问点(Service Access Point，SAP)或通道或路径由低层发送给高层的通知或指示；以及
提供给不同高层过程或功能或实体的通知或指示，例如，该高层过程或功能或实体是指以下中的至少一个：持续LBT失败检测、随机接入过程、随机接入前导码传输、混合自动重传请求(Hybrid Automatic Repeat Request，HARQ)、上行配置的授权的传输以及调度请求(SR)。
在本申请的至少一个实施例中，对于通过高层向低层发送的一个通知或指示或请求以及执行LBT的对象来进行上述通知或指示或请求的情况，执行LBT的对象可以通过上行资源或者与上行资源对应的索引表征。
例如，该上行资源包括随机接入的资源(RA/PRACH occasion)、调度请求(SR)的一个有效的PUCCH资源以及配置的授权中的至少一个。
对于执行LBT的对象通过与上行资源对应的索引表征的情况，例如，定义一种映射关系，该对象可以用相应的索引表征，例如：定义随机接入的资源(RA/PRACH occasion)对应索引1，SR的一个有效的PUCCH资源对应索引2，配置的授权对应索引3。
在本申请的至少一个实施例中，在步骤1201中，当高层判断满足第二条件时且高层判断满足第四条件时，高层向低层发送通知或指示或请求。这样，通过进一步限制条件，能够进一步减少低层和高层的层间交互，从而进一步减少终端设备的耗电。
在情况4中，上述第四条件的具体内容可以与情况1中的记载相同，此处不再重复说明。
在本申请的至少一个实施例中，在步骤1201中，当维护一个计数器时，即确定一个计数器加1或不变或挂起时，或者，当维护一个定时器，即确定启动或重启一个定时器时，或者，当确定触发终端设备或高层是否执行一个过程时，高层向低层发送该通知或指示或请求。
在本申请的至少一个实施例中，该计数器是以下计数器中的一个：
用于计算调度请求数量的计数器，例如，计数器SR_COUNTER；
用于应用或挂起功率爬坡的计数器，例如，计数器PREAMBLE_POWER_RAMPING_COUNTER；以及
用于持续LBT失败检测的计数器，例如，计数器LBT_COUNTER。
在本申请的至少一个实施例中，该定时器是用于配置授权(CG)的定时器，例如，例如configuredGrantTimer或cg-RetransmissionTimer，或者，该定时器是用于持续LBT失败检测的定时器，例如lbt-FailureDetectionTimer。
在本申请的至少一个实施例中，触发终端设备或高层执行的该过程是随机接入过程或随机接入资源选择过程。
在本申请的至少一个实施例中，与情况1的步骤503类似，如图12所示，该方法还可以包括：
步骤1203：当该高层被通知或指示时或者当该高层未被通知或指示时，一个计数器加1或不变或挂起，或者，启动或重启一个定时器，或者，触发终端设备或高层执行一个过程。
在本申请的至少一个实施例中，与情况1的步骤503类似，如图13所示，该方法还可以包括：
步骤1303：当该高层未被通知或指示时或者当该高层未被通知或指示时，一个计数器加1或不变或挂起，或者，启动或重启一个定时器，或者，触发终端设备或高层执行一个过程。
在情况4中，该计数器、定时器以及触发终端设备或高层执行的该过程的具体内容可以与情况1中的记载相同，此处不再重复说明。
以上，针对低层或高层判断是否满足各个具体条件，以情况1-4为例进行了进行示例性的说明。但是，本申请实施例还可以包括根据以下三个因素进行各种组合：执行的主体为高层还是低层、满足的条件是第一条件还是第二条件还是同时满足第一条件和第二条件，以及不满足第一条件还是满足第三条件还是不满足第一条件且满足第三条件。
由上述实施例可知，低层或高层先判断是否满足相关的条件，基于判断的结果，当上行传输由于LBT失败而被阻止时，确定低层是否向高层通知或指示LBT失败，或者确定低层是否开始或停止向高层通知或指示LBT失败，这样，能够减少低层和高层的层间交互，从而减少终端设备的耗电。
实施例2
本申请实施例提供了一种指示LBT失败的方法，该方法应用于网络设备，其对 应于实施例1所述的应用于终端设备的指示LBT失败的方法，相同的内容不再重复说明。
图14本申请实施例2的指示LBT失败的方法的一示意图。如图14所示，该方法包括：
步骤1401：向终端设备配置高层参数，该高层参数用于终端设备确定低层是否向高层通知或指示LBT失败。
在本申请的至少一个实施例中，该高层参数还用于终端设备确定高层是否向低层发送通知或指示或请求。
在本申请的至少一个实施例中，所述终端设备根据第二条件和/或第三条件，确定低层是否向高层通知或指示LBT失败，或者，低层开始还是停止向高层开始通知或指示LBT失败，所述第二条件是配置了所述高层参数和/或具备能力，和/或，所述第三条件是释放或移除了所述高层参数和/或不具备能力。
终端设备如果使用高层参数的具体内容可以参见实施例1中的记载，此处不再重复说明。
在本申请的至少一个实施例中，该高层参数包括以下参数中的至少一个：用于共享频谱信道接入的持续LBT失败检测的参数；用于调度请求的配置参数；用于配置的授权的配置参数。
在本申请的至少一个实施例中，该高层参数是小区特定的或者终端设备特定的；和/或，当配置了双链接(DC)时，所述高层参数是在主小区组(MCG)和辅小区组(SCG)分别配置的；和/或，当配置了补充上行链路(SUL)时，所述高层参数是补充上行链路(SUL)和正常上行链路(NUL)分别配置的。
在本实施例中，该高层参数的具体内容可以参见实施例1中的记载，此处不再重复说明。
由上述实施例可知，网络设备向终端设备配置用于终端设备确定低层是否向高层通知或指示LBT失败高层参数，这样，低层或高层先判断是否满足相关的条件，再基于判断的结果，当上行传输由于LBT失败而被阻止时，确定低层是否向高层通知或指示LBT失败，或者确定低层是否开始或停止向高层通知或指示LBT失败，这样，能够减少低层和高层的层间交互，从而减少终端设备的耗电。
实施例3
本申请实施例提供了一种指示LBT失败的方法，该方法应用于网络设备和终端设备，其对应于实施例1所述的应用于终端设备的指示LBT失败的方法和实施例2所述的应用于网络设备的指示LBT失败的方法，相同的内容不再重复说明。
图15是本申请实施例3的指示LBT失败的方法的一示意图。如图15所示，该方法包括：
步骤1501：网络设备向终端设备配置高层参数，该高层参数用于终端设备确定低层是否向高层通知或指示LBT失败；
步骤1502：在低层判断满足第一条件和/或第二条件的情况下，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败；
步骤1503：在低层判断不满足第一条件和/或满足第三条件的情况下，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者低层停止向高层通知或指示LBT失败。
图16是本申请实施例3的指示LBT失败的方法的另一示意图。如图16所示，该方法包括：
步骤1601：网络设备向终端设备配置高层参数，该高层参数用于终端设备确定低层是否向高层通知或指示LBT失败；
步骤1602：当高层判断满足第一条件和/或第二条件时，高层向低层发送通知或指示或请求；步骤1603：当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败。
图17是本申请实施例3的指示LBT失败的方法的另一示意图。如图17所示，该方法包括：
步骤1701：网络设备向终端设备配置高层参数，该高层参数用于终端设备确定低层是否向高层通知或指示LBT失败；
步骤1702：当高层判断不满足第一条件和/或满足第三条件时，高层向低层发送通知或指示或请求；步骤1703：当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者，低层向高层停止通知或指示LBT失败。
在本申请的至少一个实施例中，图15至图17中各个步骤的具体实施可以参照实施例1和实施例2的记载，此处不再重复说明。
由上述实施例可知，低层或高层先判断是否满足相关的条件，基于判断的结果，当上行传输由于LBT失败而被阻止时，确定低层是否向高层通知或指示LBT失败，或者确定低层是否开始或停止向高层通知或指示LBT失败，这样，能够减少低层和高层的层间交互，从而减少终端设备的耗电。
实施例4
本申请实施例提供了一种指示LBT失败的装置，该装置应用于终端设备。由于该装置解决问题的原理与实施例1的方法类似，因此其具体的实施可以参照实施例1所述的方法的实施，内容相同或相关之处不再重复说明。
图18是本申请实施例4的指示LBT失败的装置的一示意图，如图18所示，装置1800包括：
第一指示单元1801，其在低层或高层判断满足第一条件和/或第二条件的情况下时，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败；和/或，
第二指示单元1802，其在低层或高层判断不满足所述第一条件和/或满足第三条件的情况下时，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者，低层向高层停止通知或指示LBT失败。
在本申请的至少一个实施例中，如图18所示，装置1800还可以包括：
第一处理单元1803，其当高层被通知或指示时，或者，当高层未被通知或指示时，一个计数器加1或不变或挂起；或者，启动或重启一个定时器；或者，触发终端设备或高层执行一个过程。
在本申请的至少一个实施例中，当由高层判断满足第一条件和/或第二条件时，装置1800还可以包括：
第三指示单元1804，其用于高层向低层发送通知或指示或请求；基于所述通知或指示或请求，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者使得低层开始向高层通知或指示LBT失败。
在本申请的至少一个实施例中，当由所述高层判断不满足所述第一条件和/或满足第三条件时，装置1800还可以包括：
第四指示单元1805，其用于高层向低层发送通知或指示或请求；基于所述通知或指示或请求，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT 失败，或者低层向高层停止通知或指示LBT失败。
在本实施例中，上述各个单元的功能的实现可以参照实施例1中相关步骤的内容，此处不再重复说明。
由上述实施例可知，低层或高层先判断是否满足相关的条件，基于判断的结果，当上行传输由于LBT失败而被阻止时，确定低层是否向高层通知或指示LBT失败，或者确定低层是否开始或停止向高层通知或指示LBT失败，这样，能够减少低层和高层的层间交互，从而减少终端设备的耗电。
实施例5
本申请实施例提供了一种指示LBT失败的装置，该装置应用于网络设备。由于该装置解决问题的原理与实施例2的方法类似，因此其具体的实施可以参照实施例2所述的方法的实施，内容相同或相关之处不再重复说明。
图19是本申请实施例5的指示LBT失败的装置的一示意图，如图19所示，装置1900包括：
配置单元1901，其向终端设备配置高层参数，
该高层参数用于终端设备确定低层是否向高层通知或指示LBT失败。
在本申请的至少一个实施例中，该高层参数还用于终端设备确定高层是否向低层发送通知或指示或请求。
在本申请的至少一个实施例中，所述终端设备根据第二条件和/或第三条件，确定低层是否向高层通知或指示LBT失败，或者，低层开始还是停止向高层开始通知或指示LBT失败，所述第二条件是配置了所述高层参数和/或具备能力，和/或，所述第三条件是释放或移除了所述高层参数和/或不具备能力。
在本申请的至少一个实施例中，该高层参数包括以下参数中的至少一个：用于共享频谱信道接入的持续LBT失败检测的参数；用于调度请求的配置参数；用于配置的授权的配置参数。
在本申请的至少一个实施例中，该高层参数是小区特定的或者终端设备特定的；和/或，当配置了双链接(DC)时，所述高层参数是在主小区组(MCG)和辅小区组(SCG)分别配置的；和/或，当配置了补充上行链路(SUL)时，所述高层参数是补充上行链路(SUL)和正常上行链路(NUL)分别配置的。
在本实施例中，该高层参数的具体内容可以参见实施例1中的记载，此处不再重 复说明。
由上述实施例可知，网络设备向终端设备配置用于终端设备确定低层是否向高层通知或指示LBT失败高层参数，这样，，低层或高层先判断是否满足相关的条件，基于判断的结果，当上行传输由于LBT失败而被阻止时，确定低层是否向高层通知或指示LBT失败，或者确定低层是否开始或停止向高层通知或指示LBT失败，这样，能够减少低层和高层的层间交互，从而减少终端设备的耗电。
实施例6
本申请实施例提供了一种终端设备，该终端设备包括如实施例4所述的指示LBT失败的装置。
图20是本申请实施例6的终端设备的系统构成的一示意框图。如图20所示，终端设备2000可以包括处理器2010和存储器2020；存储器2020耦合到处理器2010。值得注意的是，该图是示例性的；还可以使用其他类型的结构，来补充或代替该结构，以实现电信功能或其他功能。
在一个实施方式中，指示LBT失败的装置的功能可以被集成到处理器2010中。
处理器2010可以被配置为：在低层或高层判断满足第一条件和/或第二条件的情况下时，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败；和/或，在低层或高层判断不满足所述第一条件和/或满足第三条件的情况下时，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者低层向高层停止通知或指示LBT失败。
例如，所述第一条件包括以下条件中的至少一个：所述终端设备是NR-U终端；所述终端设备是NR终端；所述终端设备是NR-U终端或NR终端；所述上行传输或所述终端设备进行共享频谱信道接入操作；所述上行传输是网络设备调度或配置的上行传输；所述上行传输不是授权辅助接入(LAA)或增强型授权辅助接入(eLAA)；所述终端设备不是进行授权辅助接入或增强型授权辅助接入；以及所述上行传输不是自动上行传输。
例如，所述第二条件是配置了高层参数和/或具备能力，和/或，所述第三条件是释放或移除了高层参数和/或不具备能力。
例如，所述高层参数包括以下参数中的至少一个：用于共享频谱信道接入的持续LBT失败检测的参数；用于调度请求的配置参数；用于配置的授权的配置参数。
例如，所述高层参数是小区特定的或者终端设备特定的；和/或，当配置了双链接(DC)时，所述高层参数是在主小区组(MCG)和辅小区组(SCG)分别配置的；和/或，当配置了补充上行链路(SUL)时，所述高层参数是补充上行链路(SUL)和正常上行链路(NUL)分别配置的。
例如，所述能力是共享频谱信道里的NR操作的能力和/或持续LBT检测和恢复的能力。
例如，所述能力是终端设备特定的，或者，小区特定的，或者，频带特定或频带组合特定的。
例如，当低层或高层判断满足第一条件和/或第二条件，且低层判断满足第四条件时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败，
所述第四条件包括以下条件中的至少一个：所述LBT失败是任意一次的LBT失败；所述LBT失败是为随机接入前导码的传输所执行的LBT失败；所述LBT失败是为配置的授权所执行的LBT失败；以及所述LBT失败是为调度请求(SR)的一个有效的物理上行链路控制信道(PUCCH)资源所执行的LBT失败。
例如，当所述LBT失败是为随机接入前导码的传输所执行的LBT失败时，所述LBT对应的信道是物理随机接入信道(PRACH)，所述LBT是对高层指示的随机接入的资源(RA/PRACH occasion)所执行的LBT；当所述LBT失败是为配置的授权所执行的LBT失败时，所述LBT对应的信道是物理上行共享信道(PUSCH)，所述LBT是对高层指示的配置的授权进行的LBT。
例如，所述通知或指示LBT失败，包括：发送一个通知或指示，或者，发送一个通知或指示和执行LBT的对象。
例如，发送的所述通知或指示是以下通知或指示中的一个：通用的通知或指示；特定用途的通知或指示；通过不同的服务访问点(SAP)或通道或路径由低层发送给高层的通知或指示；以及提供给不同高层过程或功能或实体的通知或指示。
例如，所述高层过程或功能或实体是指以下中的至少一个：持续LBT失败检测、随机接入过程、随机接入前导码传输、混合自动重传请求(HARQ)、上行配置的授权的传输以及调度请求。
例如，执行LBT的所述对象通过上行资源或者与上行资源对应的索引表征。
例如，所述上行资源包括随机接入的资源(RA/PRACH occasion)、调度请求的一个有效的PUCCH资源以及配置的授权中的至少一个。
例如，处理器2010还可以被配置为：当所述高层被通知或指示时，或者，当所述高层未被通知或指示时，一个计数器加1或不变或挂起；或者，启动或重启一个定时器；或者，触发终端设备或高层执行一个过程。
例如，所述计数器是以下计数器中的一个：用于计算调度请求数量的计数器；用于应用或挂起功率爬坡的计数器；以及用于持续LBT失败检测的计数器。
例如，所述定时器是用于配置授权(CG)的定时器或用于持续LBT失败检测的定时器。
例如，触发终端设备或高层执行的所述过程是随机接入过程或随机接入资源选择过程。
例如，当由所述高层判断满足第一条件和/或第二条件时，处理器2010还可以被配置为：高层向低层发送通知或指示或请求，基于所述通知或指示或请求，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者使得低层开始向高层通知或指示LBT失败。
例如，当由所述高层判断不满足所述第一条件和/或满足第三条件时，处理器2010还可以被配置为：高层向低层发送通知或指示或请求，基于所述通知或指示或请求，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者使得低层向高层停止通知或指示LBT失败。
例如，所述通知或指示或请求，包括：发送一个通知或指示或请求，或者，发送一个通知或指示或请求和执行LBT的对象。
例如，发送的所述通知或指示或请求是以下通知或指示或请求中的一个：通用的通知或指示或请求；特定用途的通知或指示或请求；通过不同的服务访问点(SAP)或通道或路径由高层发送给低层的通知或指示或请求；以及来自不同高层过程或功能或实体的通知或指示或请求。
例如，所述高层过程或功能或实体是指以下中的至少一个：持续LBT失败检测、随机接入过程、随机接入前导码传输、混合自动重传请求(HARQ)、上行配置的授权的传输以及调度请求。
例如，执行LBT的所述对象通过上行资源或者与上行资源对应的索引表征。
例如，所述上行资源包括随机接入的资源(RA/PRACH occasion)、调度请求的一个有效的PUCCH资源以及配置的授权中的至少一个。
例如，当维护一个计数器时，即确定一个计数器加1或不变或挂起时，或者，当维护一个定时器，即确定启动或重启一个定时器时，或者，当确定触发终端设备或高层是否执行一个过程时，高层向低层发送所述通知或指示或请求。
例如，所述计数器是以下计数器中的一个：用于计算调度请求数量的计数器；用于应用或挂起功率爬坡的计数器；以及用于持续LBT失败检测的计数器；所述定时器是用于配置授权(CG)的定时器或用于持续LBT失败检测的定时器；触发终端设备或高层执行的所述过程是随机接入过程或随机接入资源选择过程。
例如，所述低层为物理层，所述高层为介质访问控制(MAC)层。
在另一个实施方式中，指示LBT失败的装置可以与处理器2010分开配置，例如可以将指示LBT失败的装置配置为与处理器2010连接的芯片，通过处理器2010的控制来实现指示LBT失败的装置的功能。
如图20所示，终端设备2000还可以包括：通信模块2030、输入单元2040、显示器2050、电源2060。值得注意的是，终端设备2000也并不是必须要包括图20中所示的所有部件；此外，终端设备2000还可以包括图20中没有示出的部件，可以参考相关技术。
如图20所示，处理器2010有时也称为控制器或操作控件，可以包括微处理器或其他处理器装置和/或逻辑装置，该处理器2010接收输入并控制终端设备2000的各个部件的操作。
其中，存储器2020，例如可以是缓存器、闪存、硬驱、可移动介质、易失性存储器、非易失性存储器或其它合适装置中的一种或更多种。可储存各种数据，此外还可存储执行有关信息的程序。并且处理器2010可执行该存储器2020存储的该程序，以实现信息存储或处理等。其他部件的功能与现有类似，此处不再赘述。终端设备2000的各部件可以通过专用硬件、固件、软件或其结合来实现，而不偏离本发明的范围。
由上述实施例可知，低层或高层先判断是否满足相关的条件，基于判断的结果，当上行传输由于LBT失败而被阻止时，确定低层是否向高层通知或指示LBT失败，或者确定低层是否开始或停止向高层通知或指示LBT失败，这样，能够减少低层和 高层的层间交互，从而减少终端设备的耗电。
实施例7
本申请实施例提供了一种网络设备，该网络设备包括如实施例5所述的指示LBT失败的装置。
图21是本申请实施例7的网络设备的系统构成的一示意框图。如图21所示，网络设备2100可以包括：处理器(processor)2110和存储器2120；存储器2120耦合到处理器2110。其中该存储器2120可存储各种数据；此外还存储信息处理的程序2130，并且在处理器2110的控制下执行该程序2130，以接收终端设备发送的各种信息、并且向终端设备发送各种信息。
在一个实施方式中，指示LBT失败的装置的功能可以被集成到处理器2110中。其中，处理器2110可以被配置为：向终端设备配置高层参数，所述高层参数用于终端设备确定低层是否向高层通知或指示LBT失败。
例如，所述高层参数还用于终端设备确定高层是否向低层发送通知或指示或请求。
例如，所述高层参数包括以下参数中的至少一个：用于共享频谱信道接入的持续LBT失败检测的参数；用于调度请求的配置参数；用于配置的授权的配置参数。
例如，所述高层参数是小区特定的或者终端设备特定的；和/或，当配置了双链接(DC)时，所述高层参数是在主小区组(MCG)和辅小区组(SCG)分别配置的；和/或，当配置了补充上行链路(SUL)时，所述高层参数是补充上行链路(SUL)和正常上行链路(NUL)分别配置的。
在另一个实施方式中，指示LBT失败的装置可以与处理器2110分开配置，例如可以将指示LBT失败的装置配置为与处理器2110连接的芯片，通过处理器2110的控制来实现指示LBT失败的装置的功能。
此外，如图21所示，网络设备2100还可以包括：收发机2140和天线2150等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备2100也并不是必须要包括图21中所示的所有部件；此外，网络设备2100还可以包括图21中没有示出的部件，可以参考现有技术。
由上述实施例可知，网络设备向终端设备配置用于终端设备确定低层是否向高层通知或指示LBT失败高层参数，这样，低层或高层先判断是否满足相关的条件，基 于判断的结果，当上行传输由于LBT失败而被阻止时，确定低层是否向高层通知或指示LBT失败，或者确定低层是否开始或停止向高层通知或指示LBT失败，这样，能够减少低层和高层的层间交互，从而减少终端设备的耗电。
实施例8
本申请实施例提供了一种通信系统，包括根据实施例6所述的终端设备和/或根据实施例7所述的网络设备。
例如，该通信系统的结构可以参照图1，如图1所示，通信系统100包括网络设备101和终端设备102，终端设备102与实施例6中记载的终端设备相同，网络设备101与实施例7中记载的网络设备相同，重复的内容不再赘述。
本发明以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本发明涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。逻辑部件例如现场可编程逻辑部件、微处理器、计算机中使用的处理器等。本发明还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图18中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图4中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图18中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本发明所描述功能的通用处理器、数字信号处理器(DSP)、 专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图18描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本发明进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本发明保护范围的限制。本领域技术人员可以根据本发明的精神和原理对本发明做出各种变型和修改，这些变型和修改也在本发明的范围内。
根据本申请实施例公开的各种实施方式，还公开了如下附记：
附记一、
1、一种指示LBT失败的装置，所述装置应用于终端设备，所述装置包括：
第一指示单元，其用于在低层或高层判断满足第一条件和/或第二条件的情况下，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败；和/或，
第二指示单元，其用于在低层或高层判断不满足所述第一条件和/或满足第三条件的情况下时，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者，低层停止向高层通知或指示LBT失败。
2、根据附记1所述的装置，其中，所述第一条件包括以下条件中的至少一个：
所述终端设备是NR-U终端；
所述终端设备是NR终端；
所述终端设备是NR-U终端或NR终端；
所述上行传输或所述终端设备进行共享频谱信道接入操作；
所述上行传输是网络设备调度或配置的上行传输；
所述上行传输不是授权辅助接入(LAA)或增强型授权辅助接入(eLAA)；
所述终端设备不是进行授权辅助接入或增强型授权辅助接入；以及
所述上行传输不是自动上行传输。
3、根据附记1所述的装置，其中，
所述第二条件是配置了高层参数和/或具备能力，和/或，
所述第三条件是释放或移除了高层参数和/或不具备能力。
4、根据附记3所述的装置，其中，所述高层参数包括以下参数中的至少一个：
用于共享频谱信道接入的持续LBT失败检测的参数；
用于调度请求的配置参数；
用于配置的授权的配置参数。
5、根据附记3或4所述的装置，其中，
所述高层参数是小区特定的或者终端设备特定的；和/或，
当配置了双链接(DC)时，所述高层参数是在主小区组(MCG)和辅小区组(SCG)分别配置的；和/或，
当配置了补充上行链路(SUL)时，所述高层参数是补充上行链路(SUL)和正常上行链路(NUL)分别配置的。
6、根据附记3所述的装置，其中，
所述能力是共享频谱信道里的NR操作的能力和/或持续LBT检测和恢复的能力。
7、根据附记3或6所述的装置，其中，
所述能力是终端设备特定的，或者，小区特定的，或者，频带特定或频带组合特定的。
8、根据附记1所述的装置，其中，所述第一指示单元当低层或高层判断满足第一条件和/或第二条件，且低层判断满足第四条件时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败，
所述第四条件包括以下条件中的至少一个：
所述LBT失败是任意一次的LBT失败；
所述LBT失败是为随机接入前导码的传输所执行的LBT失败；
所述LBT失败是为配置的授权所执行的LBT失败；以及
所述LBT失败是为调度请求(SR)的一个有效的物理上行链路控制信道(PUCCH)资源所执行的LBT失败。
9、根据附记8所述的装置，其中，
当所述LBT失败是为随机接入前导码的传输所执行的LBT失败时，所述LBT对应的信道是物理随机接入信道(PRACH)，所述LBT是对高层指示的随机接入的资源(RA/PRACH occasion)所执行的LBT；
当所述LBT失败是为配置的授权所执行的LBT失败时，所述LBT对应的信道是物理上行共享信道(PUSCH)，所述LBT是对高层指示的配置的授权进行的LBT。
10、根据附记1所述的装置，其中，所述第一指示单元用于发送一个通知或指示示，或者，发送一个通知或指示和执行LBT的对象。
11、根据附记10所述的装置，其中，发送的所述通知或指示是以下通知或指示中的一个：
通用的通知或指示；
特定用途的通知或指示；
通过不同的服务访问点(SAP)或通道或路径由低层发送给高层的通知或指示；以及
提供给不同高层过程或功能或实体的通知或指示。
12、根据附记11所述的装置，其中，
所述高层过程或功能或实体是指以下中的至少一个：持续LBT失败检测、随机接入过程、随机接入前导码传输、混合自动重传请求(HARQ)、上行配置的授权的传输以及调度请求。
13、根据附记10所述的装置，其中，
执行LBT的所述对象通过上行资源或者与上行资源对应的索引表征。
14、根据附记13所述的装置，其中，
所述上行资源包括随机接入的资源(RA/PRACH occasion)、调度请求的一个有效的PUCCH资源以及配置的授权中的至少一个。
15、根据附记1所述的装置，其中，所述装置还包括：
第一处理单元，其用于当所述高层被通知或指示时，或者，当所述高层未被通知或指示时，一个计数器加1或不变或挂起；或者，启动或重启一个定时器；或者，触发终端设备或高层执行一个过程。
16、根据附记15所述的装置，其中，所述计数器是以下计数器中的一个：
用于计算调度请求数量的计数器；
用于应用或挂起功率爬坡的计数器；以及
用于持续LBT失败检测的计数器。
17、根据附记15所述的装置，其中，
所述定时器是用于配置授权(CG)的定时器或用于持续LBT失败检测的定时器。
18、根据附记15所述的装置，其中，
触发终端设备或高层执行的所述过程是随机接入过程或随机接入资源选择过程。
19、根据附记1-18中的任一项所述的装置，其中，
当由所述高层判断满足第一条件和/或第二条件时，所述装置还包括：
第三指示单元，其用于高层向低层发送通知或指示或请求；基于所述通知或指示或请求，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者低层开始向高层通知或指示LBT失败。
20、根据附记1-19中的任一项所述的装置，其中，
当由所述高层判断不满足所述第一条件和/或满足第三条件时，所述装置还包括：
第四指示单元，其用于高层向低层发送通知或指示或请求；基于所述通知或指示或请求，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者，低层停止向高层通知或指示LBT失败。
21、根据附记19或20所述的装置，其中，所述第四指示单元用于发送一个通知或指示或请求，或者，发送一个通知或指示或请求和执行LBT的对象。
22、根据附记21所述的装置，其中，发送的所述通知或指示或请求是以下通知或指示或请求中的一个：
通用的通知或指示或请求；
特定用途的通知或指示或请求；
通过不同的服务访问点(SAP)或通道或路径由高层发送给低层的通知或指示或请求；以及
来自不同高层过程或功能或实体的通知或指示或请求。
23、根据附记22所述的装置，其中，
所述高层过程或功能或实体是指以下中的至少一个：持续LBT失败检测、随机接入过程、随机接入前导码传输、混合自动重传请求(HARQ)、上行配置的授权的传输以及调度请求。
24、根据附记21所述的装置，其中，
执行LBT的所述对象通过上行资源或者与上行资源对应的索引表征。
25、根据附记24所述的装置，其中，
所述上行资源包括随机接入的资源(RA/PRACH occasion)、调度请求的一个有效的PUCCH资源以及配置的授权中的至少一个。
26、根据附记19或20所述的装置，其中，
当维护一个计数器时，即确定一个计数器加1或不变或挂起时，或者，当维护一个定时器，即确定启动或重启一个定时器时，或者，当确定触发终端设备或高层是否执行一个过程时，所述第三指示单元或所述第四指示单元用于高层向低层发送所述通知或指示或请求。
27、根据附记26所述的装置，其中，
所述计数器是以下计数器中的一个：用于计算调度请求数量的计数器；用于应用或挂起功率爬坡的计数器；以及用于持续LBT失败检测的计数器；
所述定时器是用于配置授权(CG)的定时器或用于持续LBT失败检测的定时器；
触发终端设备或高层执行的所述过程是随机接入过程或随机接入资源选择过程。
28、根据附记1-27中的任一项所述的装置，其中，
所述低层为物理层，所述高层为介质访问控制(MAC)层。
29、一种指示LBT失败的装置，所述装置应用于网络设备，所述装置包括：
配置单元，其向终端设备配置高层参数，
所述高层参数用于终端设备确定低层是否向高层通知或指示LBT失败。
30、根据附记29所述的装置，其中，
所述高层参数还用于终端设备确定高层是否向低层发送通知或指示或请求。
31、根据附记29所述的装置，其中，所述高层参数用于终端设备确定低层是否向高层通知或指示LBT失败，包括：
所述终端设备根据第二条件和/或第三条件，当上行传输由于LBT失败而被阻止时，确定低层是否向高层通知或指示LBT失败，或者，低层开始还是停止向高层通知或指示LBT失败，
所述第二条件是配置了所述高层参数和/或具备能力，和/或，所述第三条件是释放或移除了所述高层参数和/或不具备能力。
32、根据附记29-31中的任一项所述的装置，其中，
所述高层参数包括以下参数中的至少一个：
用于共享频谱信道接入的持续LBT失败检测的参数；
用于调度请求的配置参数；
用于配置的授权的配置参数。
33、根据附记29-32中的任一项所述的装置，其中，
所述高层参数是小区特定的或者终端设备特定的；和/或，
当配置了双链接(DC)时，所述高层参数是在主小区组(MCG)和辅小区组(SCG)分别配置的；和/或，
当配置了补充上行链路(SUL)时，所述高层参数是补充上行链路(SUL)和正常上行链路(NUL)分别配置的。
34、一种终端设备，所述终端设备包括根据附记1-28中的任一项所述的装置。
35、一种网络设备，所述网络设备包括根据附记29-33中的任一项所述的装置。
36、一种通信系统，所述通信系统包括根据附记34所述的终端设备和/或根据附记35所述的网络设备。
附记二、
1、一种指示LBT失败的方法，所述方法应用于终端设备，所述方法包括：
在低层或高层判断满足第一条件和/或第二条件的情况下，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败；和/或，
在低层或高层判断不满足所述第一条件和/或满足第三条件的情况下，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者低层停止向高层通知或指示LBT失败。
2、根据附记1所述的方法，其中，所述第一条件包括以下条件中的至少一个：
所述终端设备是NR-U终端；
所述终端设备是NR终端；
所述终端设备是NR-U终端或NR终端；
所述上行传输或所述终端设备进行共享频谱信道接入操作；
所述上行传输是网络设备调度或配置的上行传输；
所述上行传输不是授权辅助接入(LAA)或增强型授权辅助接入(eLAA)；
所述终端设备不是进行授权辅助接入或增强型授权辅助接入；以及
所述上行传输不是自动上行传输。
3、根据附记1所述的方法，其中，
所述第二条件是配置了高层参数和/或具备能力，和/或，
所述第三条件是释放或移除了高层参数和/或不具备能力。
4、根据附记3所述的方法，其中，所述高层参数包括以下参数中的至少一个：
用于共享频谱信道接入的持续LBT失败检测的参数；
用于调度请求的配置参数；
用于配置的授权的配置参数。
5、根据附记3或4所述的方法，其中，
所述高层参数是小区特定的或者终端设备特定的；和/或，
当配置了双链接(DC)时，所述高层参数是在主小区组(MCG)和辅小区组(SCG)分别配置的；和/或，
当配置了补充上行链路(SUL)时，所述高层参数是补充上行链路(SUL)和正常上行链路(NUL)分别配置的。
6、根据附记3所述的方法，其中，
所述能力是共享频谱信道里的NR操作的能力和/或持续LBT检测和恢复的能力。
7、根据附记3或6所述的方法，其中，
所述能力是终端设备特定的，或者，小区特定的，或者，频带特定或频带组合特定的。
8、根据附记1所述的方法，其中，当低层或高层判断满足第一条件和/或第二条件，且低层判断满足第四条件时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败，
所述第四条件包括以下条件中的至少一个：
所述LBT失败是任意一次的LBT失败；
所述LBT失败是为随机接入前导码的传输所执行的LBT失败；
所述LBT失败是为配置的授权所执行的LBT失败；以及
所述LBT失败是为调度请求(SR)的一个有效的物理上行链路控制信道(PUCCH)资源所执行的LBT失败。
9、根据附记8所述的方法，其中，
当所述LBT失败是为随机接入前导码的传输所执行的LBT失败时，所述LBT 对应的信道是物理随机接入信道(PRACH)，所述LBT是对高层指示的随机接入的资源(RA/PRACH occasion)所执行的LBT；
当所述LBT失败是为配置的授权所执行的LBT失败时，所述LBT对应的信道是物理上行共享信道(PUSCH)，所述LBT是对高层指示的配置的授权进行的LBT。
10、根据附记1所述的方法，其中，所述通知或指示LBT失败，包括：
发送一个通知或指示，或者，发送一个通知或指示和执行LBT的对象。
11、根据附记10所述的方法，其中，发送的所述通知或指示是以下通知或指示中的一个：
通用的通知或指示；
特定用途的通知或指示；
通过不同的服务访问点(SAP)或通道或路径由低层发送给高层的通知或指示；以及
提供给不同高层过程或功能或实体的通知或指示。
12、根据附记11所述的方法，其中，
所述高层过程或功能或实体是指以下中的至少一个：持续LBT失败检测、随机接入过程、随机接入前导码传输、混合自动重传请求(HARQ)、上行配置的授权的传输以及调度请求。
13、根据附记10所述的方法，其中，
执行LBT的所述对象通过上行资源或者与上行资源对应的索引表征。
14、根据附记13所述的方法，其中，
所述上行资源包括随机接入的资源(RA/PRACH occasion)、调度请求的一个有效的PUCCH资源以及配置的授权中的至少一个。
15、根据附记1所述的方法，其中，所述方法还包括：
当所述高层被通知或指示时，或者，当所述高层未被通知或指示时，
一个计数器加1或不变或挂起；或者，启动或重启一个定时器；或者，触发终端设备或高层执行一个过程。
16、根据附记15所述的方法，其中，所述计数器是以下计数器中的一个：
用于计算调度请求数量的计数器；
用于应用或挂起功率爬坡的计数器；以及
用于持续LBT失败检测的计数器。
17、根据附记15所述的方法，其中，
所述定时器是用于配置授权(CG)的定时器或用于持续LBT失败检测的定时器。
18、根据附记15所述的方法，其中，
触发终端设备或高层执行的所述过程是随机接入过程或随机接入资源选择过程。
19、根据附记1-18中的任一项所述的方法，其中，
当由所述高层判断满足第一条件和/或第二条件时，所述方法还包括：
高层向低层发送通知或指示或请求；基于所述通知或指示或请求，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者低层开始向高层通知或指示LBT失败。
20、根据附记1-19中的任一项所述的方法，其中，
当由所述高层判断不满足所述第一条件和/或满足第三条件时，所述方法还包括：
高层向低层发送通知或指示或请求；基于所述通知或指示或请求，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者低层停止向高层通知或指示LBT失败。
21、根据附记19或20所述的方法，其中，所述通知或指示或请求，包括：
发送一个通知或指示或请求，或者，发送一个通知或指示或请求和执行LBT的对象。
22、根据附记21所述的方法，其中，发送的所述通知或指示或请求是以下通知或指示或请求中的一个：
通用的通知或指示或请求；
特定用途的通知或指示或请求；
通过不同的服务访问点(SAP)或通道或路径由高层发送给低层的通知或指示或请求；以及
来自不同高层过程或功能或实体的通知或指示或请求。
23、根据附记22所述的方法，其中，
所述高层过程或功能或实体是指以下中的至少一个：持续LBT失败检测、随机接入过程、随机接入前导码传输、混合自动重传请求(HARQ)、上行配置的授权的传输以及调度请求。
24、根据附记21所述的方法，其中，
执行LBT的所述对象通过上行资源或者与上行资源对应的索引表征。
25、根据附记24所述的方法，其中，
所述上行资源包括随机接入的资源(RA/PRACH occasion)、调度请求的一个有效的PUCCH资源以及配置的授权中的至少一个。
26、根据附记19或20所述的方法，其中，
当维护一个计数器时，即确定一个计数器加1或不变或挂起时，或者，当维护一个定时器，即确定启动或重启一个定时器时，或者，当确定触发终端设备或高层是否执行一个过程时，高层向低层发送所述通知或指示或请求。
27、根据附记26所述的方法，其中，
所述计数器是以下计数器中的一个：用于计算调度请求数量的计数器；用于应用或挂起功率爬坡的计数器；以及用于持续LBT失败检测的计数器；
所述定时器是用于配置授权(CG)的定时器或用于持续LBT失败检测的定时器；
触发终端设备或高层执行的所述过程是随机接入过程或随机接入资源选择过程。
28、根据附记1-27中的任一项所述的方法，其中，
所述低层为物理层，所述高层为介质访问控制(MAC)层。
29、一种指示LBT失败的方法，所述方法应用于网络设备，所述方法包括：
向终端设备配置高层参数，
所述高层参数用于终端设备确定低层是否向高层通知或指示LBT失败。
30、根据附记29所述的方法，其中，
所述高层参数还用于终端设备确定高层是否向低层发送通知或指示或请求。
31、根据附记29所述的方法，其中，所述高层参数用于终端设备确定低层是否向高层通知或指示LBT失败，包括：
所述终端设备根据第二条件和/或第三条件，当上行传输由于LBT失败而被阻止时，确定低层是否向高层通知或指示LBT失败，或者，低层开始还是停止向高层通知或指示LBT失败，
所述第二条件是配置了所述高层参数和/或具备能力，和/或，所述第三条件是释放或移除了所述高层参数和/或不具备能力。
32、根据附记29-31中任一项所述的方法，其中，
所述高层参数包括以下参数中的至少一个：
用于共享频谱信道接入的持续LBT失败检测的参数；
用于调度请求的配置参数；
用于配置的授权的配置参数。
33、根据附记29-32中的任一项所述的方法，其中，
所述高层参数是小区特定的或者终端设备特定的；和/或，
当配置了双链接(DC)时，所述高层参数是在主小区组(MCG)和辅小区组(SCG)分别配置的；和/或，
当配置了补充上行链路(SUL)时，所述高层参数是补充上行链路(SUL)和正常上行链路(NUL)分别配置的。

Claims (20)

  1. 一种指示LBT失败的装置，所述装置应用于终端设备，所述装置包括：
    第一指示单元，其用于在低层或高层判断满足第一条件和/或第二条件的情况下，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败；和/或，
    第二指示单元，其用于在低层或高层判断不满足所述第一条件和/或满足第三条件的情况下，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者，低层停止向高层通知或指示LBT失败。
  2. 根据权利要求1所述的装置，其中，所述第一条件包括以下条件中的至少一个：
    所述终端设备是NR-U终端；
    所述终端设备是NR终端；
    所述终端设备是NR-U终端或NR终端；
    所述上行传输或所述终端设备进行共享频谱信道接入操作；
    所述上行传输是网络设备调度或配置的上行传输；
    所述上行传输不是授权辅助接入(LAA)或增强型授权辅助接入(eLAA)；
    所述终端设备不是进行授权辅助接入或增强型授权辅助接入；以及
    所述上行传输不是自动上行传输。
  3. 根据权利要求1所述的装置，其中，
    所述第二条件是配置了高层参数和/或具备能力，和/或，
    所述第三条件是释放或移除了高层参数和/或不具备能力。
  4. 根据权利要求3所述的装置，其中，所述高层参数包括以下参数中的至少一个：
    用于共享频谱信道接入的持续LBT失败检测的参数；
    用于调度请求的配置参数；
    用于配置的授权的配置参数。
  5. 根据权利要求3所述的装置，其中，
    所述能力是共享频谱信道里的NR操作的能力和/或持续LBT检测和恢复的能力。
  6. 根据权利要求3所述的装置，其中，
    所述能力是终端设备特定的，或者，小区特定的，或者，频带特定或频带组合特定的。
  7. 根据权利要求1所述的装置，其中，所述第一指示单元当低层或高层判断满足第一条件和/或第二条件，且低层判断满足第四条件时，低层向高层通知或指示LBT失败，或者，低层开始向高层通知或指示LBT失败，
    所述第四条件包括以下条件中的至少一个：
    所述LBT失败是任意一次的LBT失败；
    所述LBT失败是为随机接入前导码的传输所执行的LBT失败；
    所述LBT失败是为配置的授权所执行的LBT失败；以及
    所述LBT失败是为调度请求(SR)的一个有效的物理上行链路控制信道(PUCCH)资源所执行的LBT失败。
  8. 根据权利要求1所述的装置，其中，所述第一指示单元用于发送一个通知或指示，或者，发送一个通知或指示和执行LBT的对象。
  9. 根据权利要求8所述的装置，其中，发送的所述通知或指示是以下通知或指示中的一个：
    通用的通知或指示；
    特定用途的通知或指示；
    通过不同的服务访问点(SAP)或通道或路径由低层发送给高层的通知或指示；以及
    提供给不同高层过程或功能或实体的通知或指示。
  10. 根据权利要求1所述的装置，其中，所述装置还包括：
    第一处理单元，其用于当所述高层被通知或指示时，或者，当所述高层未被通知或指示时，一个计数器加1或不变或挂起；或者，启动或重启一个定时器；或者，触发终端设备或高层执行一个过程。
  11. 根据权利要求10所述的装置，其中，所述计数器是以下计数器中的一个：
    用于计算调度请求数量的计数器；
    用于应用或挂起功率爬坡的计数器；以及
    用于持续LBT失败检测的计数器。
  12. 根据权利要求10所述的装置，其中，
    所述定时器是用于配置授权(CG)的定时器或用于持续LBT失败检测的定时器。
  13. 根据权利要求1所述的装置，其中，
    当由所述高层判断满足第一条件和/或第二条件时，所述装置还包括：
    第三指示单元，其用于高层向低层发送通知或指示或请求；基于所述通知或指示或请求，当上行传输由于LBT失败而被阻止时，低层向高层通知或指示LBT失败，或者低层开始向高层通知或指示LBT失败。
  14. 根据权利要求1所述的装置，其中，
    当由所述高层判断不满足所述第一条件和/或满足第三条件时，所述装置还包括：
    第四指示单元，其用于高层向低层发送通知或指示或请求；基于所述通知或指示或请求，当上行传输由于LBT失败而被阻止时，低层不向高层通知或指示LBT失败，或者低层停止向高层通知或指示LBT失败。
  15. 一种指示LBT失败的装置，所述装置应用于网络设备，所述装置包括：
    配置单元，其向终端设备配置高层参数，
    所述高层参数用于终端设备确定低层是否向高层通知或指示LBT失败。
  16. 根据权利要求15所述的装置，其中，
    所述高层参数还用于终端设备确定高层是否向低层发送通知或指示或请求。
  17. 根据权利要求15所述的装置，其中，所述高层参数用于终端设备确定低层是否向高层通知或指示LBT失败，包括：
    所述终端设备根据第二条件和/或第三条件，当上行传输由于LBT失败而被阻止时，确定低层是否向高层通知或指示LBT失败，或者，低层开始还是停止向高层开始通知或指示LBT失败，
    所述第二条件是配置了所述高层参数和/或具备能力，和/或，所述第三条件是释放或移除了所述高层参数和/或不具备能力。
  18. 根据权利要求15所述的装置，其中，
    所述高层参数包括以下参数中的至少一个：
    用于共享频谱信道接入的持续LBT失败检测的参数；
    用于调度请求的配置参数；
    用于配置的授权的配置参数。
  19. 根据权利要求15所述的装置，其中，
    所述高层参数是小区特定的或者终端设备特定的；和/或，
    当配置了双链接(DC)时，所述高层参数是在主小区组(MCG)和辅小区组(SCG)分别配置的；和/或，
    当配置了补充上行链路(SUL)时，所述高层参数是补充上行链路(SUL)和正常上行链路(NUL)分别配置的。
  20. 一种通信系统，所述通信系统包括终端设备和/或网络设备，
    所述终端设备包括根据权利要求1所述的装置，和/或，
    所述网络设备包括根据权利要求15所述的装置。
PCT/CN2020/084072 2020-04-09 2020-04-09 指示lbt失败的方法及装置 WO2021203395A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2022554269A JP7380907B2 (ja) 2020-04-09 2020-04-09 Ｌｂｔ失敗を指示する方法及び装置
PCT/CN2020/084072 WO2021203395A1 (zh) 2020-04-09 2020-04-09 指示lbt失败的方法及装置
CN202080098279.5A CN115245036A (zh) 2020-04-09 2020-04-09 指示lbt失败的方法及装置
US17/939,038 US20230007693A1 (en) 2020-04-09 2022-09-07 Method and apparatus for indicating an lbt failure

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/084072 WO2021203395A1 (zh) 2020-04-09 2020-04-09 指示lbt失败的方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/939,038 Continuation US20230007693A1 (en) 2020-04-09 2022-09-07 Method and apparatus for indicating an lbt failure

Publications (1)

Publication Number Publication Date
WO2021203395A1 true WO2021203395A1 (zh) 2021-10-14

Family

ID=78022457

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/084072 WO2021203395A1 (zh) 2020-04-09 2020-04-09 指示lbt失败的方法及装置

Country Status (4)

Country Link
US (1) US20230007693A1 (zh)
JP (1) JP7380907B2 (zh)
CN (1) CN115245036A (zh)
WO (1) WO2021203395A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105580292A (zh) * 2013-09-24 2016-05-11 Lg电子株式会社 用于双连接的并行随机接入过程的mac和phy之间的通信
CN107371168A (zh) * 2016-05-12 2017-11-21 电信科学技术研究院 一种非授权频谱中的测量方法和设备
CN109845383A (zh) * 2019-01-18 2019-06-04 北京小米移动软件有限公司 上行传输的发送方法、装置、设备及存储介质
WO2019195563A1 (en) * 2018-04-04 2019-10-10 Convida Wireless, Llc Random access with new radio unlicensed cells
WO2019240512A1 (en) * 2018-06-13 2019-12-19 Samsung Electronics Co., Ltd. Method and wireless communication system for handling timer operation
WO2020061866A1 (zh) * 2018-09-26 2020-04-02 富士通株式会社 Lbt监测失败的处理方法、装置和系统

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10637619B2 (en) * 2014-11-03 2020-04-28 Samsung Electronics Co., Ltd. Method and apparatus for channel access for LTE on unlicensed spectrum
US10034305B2 (en) * 2015-11-12 2018-07-24 Qualcomm Incorporated LBT interface for logical DTX
KR20220010069A (ko) * 2016-01-20 2022-01-25 주식회사 윌러스표준기술연구소 비면허 대역 채널 액세스 방법, 장치, 및 시스템
CN108476532A (zh) * 2016-02-02 2018-08-31 英特尔Ip公司 随机接入过程期间的先听后说(lbt)失败
US10349320B2 (en) * 2016-03-29 2019-07-09 Sharp Kabushiki Kaisha User equipments, base stations and methods
US11528746B2 (en) * 2017-08-11 2022-12-13 Lg Electronics Inc. Method for handling pre-configured UL resources based on LBT procedure in wireless communication system and a device therefor
US11272540B2 (en) * 2018-08-09 2022-03-08 Ofinno, Llc Channel access and uplink switching
KR20200035822A (ko) * 2018-09-27 2020-04-06 삼성전자주식회사 비면허 주파수 대역에서 동작하는 차세대 이동통신 시스템에서 기지국이 lbt 실패 정보를 보고하는 방법 및 장치
WO2020147042A1 (zh) * 2019-01-16 2020-07-23 北京小米移动软件有限公司 Lbt失败的处理方法和lbt失败的处理装置
CN113439456B (zh) * 2019-02-13 2023-01-24 上海诺基亚贝尔股份有限公司 因lbt失败导致的带宽部分切换
CN114145072A (zh) * 2019-07-02 2022-03-04 三星电子株式会社 用于支持大随机接入响应（rar）窗口大小的随机接入过程的方法
CN115002908A (zh) * 2019-07-09 2022-09-02 华硕电脑股份有限公司 无线通信系统用于载波选择和早期数据传送的方法和设备
US11638302B2 (en) * 2019-08-15 2023-04-25 Qualcomm Incorporated Channel occupancy time (COT)-structure indication
KR102550663B1 (ko) * 2019-10-04 2023-07-04 엘지전자 주식회사 무선 통신 시스템에서 신호를 송수신하는 방법 및 이를 지원하는 장치
CN114667795A (zh) * 2019-11-13 2022-06-24 鸿颖创新有限公司 用于先听后说故障检测和恢复的方法和设备
BR112022020228A2 (pt) * 2020-04-09 2022-11-22 Ericsson Telefon Ab L M Métodos para realizar transferência para uma célula alvo e para suportar transferência de um equipamento de usuário para uma célula alvo, equipamento de usuário, meio legível por computador não transitório, e, nó de rede sem fio

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105580292A (zh) * 2013-09-24 2016-05-11 Lg电子株式会社 用于双连接的并行随机接入过程的mac和phy之间的通信
CN107371168A (zh) * 2016-05-12 2017-11-21 电信科学技术研究院 一种非授权频谱中的测量方法和设备
WO2019195563A1 (en) * 2018-04-04 2019-10-10 Convida Wireless, Llc Random access with new radio unlicensed cells
WO2019240512A1 (en) * 2018-06-13 2019-12-19 Samsung Electronics Co., Ltd. Method and wireless communication system for handling timer operation
WO2020061866A1 (zh) * 2018-09-26 2020-04-02 富士通株式会社 Lbt监测失败的处理方法、装置和系统
CN109845383A (zh) * 2019-01-18 2019-06-04 北京小米移动软件有限公司 上行传输的发送方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN115245036A (zh) 2022-10-25
JP7380907B2 (ja) 2023-11-15
US20230007693A1 (en) 2023-01-05
JP2023519163A (ja) 2023-05-10

Similar Documents

Publication Publication Date Title
US20230269673A1 (en) Method for modifying parameter values for long range extension and corresponding node
JP7559850B2 (ja) Ｌｂｔ監視失敗の処理方法、装置及びシステム
TW202415131A (zh) 具多連線性移動性
TW202118323A (zh) 頻寬部分操作系統及方法
JP2022501946A (ja) Ｎｒ−ｕ ｌｂｔ ｍａｃ手順
CN114747288A (zh) 报告无线网络中的先听后说失败
BR112021011715A2 (pt) Métodos realizados por um equipamento de usuário e por um nó da rede de rádio, equipamento de usuário, nó da rede de rádio, produto de programa de computador, e, mídia de armazenamento legível por computador
JP2013225868A (ja) Ｍａｃのリセットおよび再構成
US20220279591A1 (en) Random access method and apparatus
WO2021203396A1 (zh) 持续lbt失败检测与恢复的方法及装置
US20230353223A1 (en) Method and apparatus for detecting beam failure
CN116250342A (zh) 针对小数据传输的空闲/非活动移动性
JP2022533337A (ja) アップリンク送信のための方法、端末デバイス、およびネットワークノード
WO2021203528A1 (zh) 发送数据的方法、装置和通信系统
EP4140243A1 (en) Handling scell deactivation for unlicensed operation
WO2021232383A1 (zh) 小区切换中的持续lbt失败检测和恢复的方法及装置
WO2021203395A1 (zh) 指示lbt失败的方法及装置
WO2021159402A1 (zh) Lbt失败的处理方法及装置
WO2020029295A1 (zh) 上行数据传输方法、用于上行数据传输的配置方法及装置
WO2021232384A1 (zh) 计数器维护方法，调度请求接收方法以及装置
WO2024031402A1 (zh) 测量放松的方法、装置以及通信系统
WO2023193266A1 (zh) 下行无线链路质量的评估方法及装置
WO2023205975A1 (zh) 辅小区波束失败恢复的方法和装置
WO2024065543A1 (zh) 失败检测及恢复方法和装置
WO2024207388A1 (zh) 小区非连续发送/接收场景中的通信方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20930095

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022554269

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20930095

Country of ref document: EP

Kind code of ref document: A1