IP Library › Granted Patent US 12,408,193
Granted Patent B2
US 12,408,193 · App. 18/370,986 · Granted Sep 2, 2025

Method and apparatus for LBT failure detection

Inventors: Hung-Chen Chen (Hsinchu, TW); Chie-Ming Chou (Hsinchu, TW); Chia-Hung Wei (Hsinchu, TW); Mei-Ju Shih (Hsinchu, TW)
H04W74/002H04W36/0058H04W36/00837H04W36/305H04W72/044H04W74/0808H04W36/00698H04W36/362
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,408,193
App. No.
18/370,986
Granted
Sep 2, 2025
Kind
B2
Abstract

A method for LBT failure detection performed by a UE is provided. The method includes: receiving, by a MAC entity of the UE, an LBT failure indication from a lower layer for all UL transmissions; increasing an LBT failure counter when the MAC entity receives the LBT failure indication; determining an LBT failure event occurs when the LBT failure counter is greater than or equal to a threshold; and resetting the LBT failure counter after the MAC entity has not received the LBT failure indication for a time period.

Claims (40)

1. A user equipment (UE) comprising:

one or more non-transitory computer-readable media having computer-executable instructions embodied thereon; and

at least one processor coupled to the one or more non-transitory computer-readable media, the computer-executable instructions causing the UE to:

receive, by a Medium Access Control (MAC) entity of the UE, a Listen-Before-Talk (LBT) failure indication from a lower layer in response to an unsuccessful uplink (UL) transmission attempt;

identify the unsuccessful UL transmission attempt associated with the received LBT failure indication based on a timing of resources used by the unsuccessful UL transmission attempt

increase an LBT failure counter by one when the MAC entity receives the LBT failure indication;

determine an LBT failure event has occurred when the LBT failure counter is greater than or equal to a threshold;

indicate an LBT failure problem to an upper layer in response to determining an LBT failure event has occurred; and

reset the LBT failure counter in response to indicating the LBT failure problem to the upper layer.

2. The UE of claim 1 , wherein the computer-executable instructions further cause the UE to:

reset the LBT failure counter after-the MAC entity has not received the LBT failure indication for a time period.

3. The UE of claim 1 , wherein the computer-executable instructions further cause the UE to:

perform a Radio Link Failure (RLF) recovery procedure.

4. The UE of claim 1 , wherein the computer-executable instructions further cause the UE to:

perform a re-establishment procedure by transmitting a Radio Resource Control (RRC) re-establishment request message indicating a re-establishment cause as LBT failure, when the LBT failure event occurs in a Primary Cell (PCell).

5. The UE of claim 1 , further comprising a transceiver communicatively coupled to the at least one processor, wherein the computer-executable instructions further cause the UE to:

transmit, to a master node via the transceiver, a Secondary Cell Group (SCG) failure report indicating the LBT failure problem when the LBT failure event occurs in a Primary Secondary Cell (PSCell).

6. The UE of claim 1 , further comprising a transceiver communicatively coupled to the at least one processor, wherein the computer-executable instructions further cause the UE to:

receive, via the transceiver, a configuration that indicates at least one of a time period and the threshold.

7. The UE of claim 6 , wherein the computer-executable instructions further cause the UE to:

reset the LBT failure counter when at least one of the time period and the threshold is reconfigured.

8. The UE of claim 1 , wherein the computer-executable instructions further cause the UE to:

reset the LBT failure counter when the MAC entity considers LBT for a UL transmission attempt as successful.

9. The UE of claim 1 , wherein the computer-executable instructions further cause the UE to:

reset the LBT failure counter when a reset of the MAC entity is requested.

10. A method for Listen-Before-Talk (LBT) failure detection performed by a User Equipment (UE), the method comprising:

receiving, by a Medium Access Control (MAC) entity of the UE, a Listen-Before-Talk (LBT) failure indication from a lower layer in response to an unsuccessful uplink (UL) transmission attempt;

identifying the unsuccessful UL transmission attempt associated with the received LBT failure indication based on a timing of resources used by the unsuccessful UL transmission attempt;

increasing an LBT failure counter by one when the MAC entity receives the LBT failure indication;

determining an LBT failure event has occurred when the LBT failure counter is greater than or equal to a threshold;

indicating an LBT failure problem to an upper layer in response to determining an LBT failure event has occurred; and

resetting the LBT failure counter in response to indicating the LBT failure problem to an upper layer.

11. The method of claim 10 , further comprising resetting the LBT failure counter after-the MAC entity has not received the LBT failure indication for a time period.

12. The method of claim 10 , further comprising performing a Radio Link Failure (RLF) recovery procedure.

13. The method of claim 10 , further comprising performing a re-establishment procedure by transmitting a Radio Resource Control (RRC) re-establishment request message indicating a re-establishment cause as LBT failure, when the LBT failure event occurs in a Primary Cell (PCell).

14. The method of claim 10 , further comprising transmitting, to a master node, a Secondary Cell Group (SCG) failure report indicating the LBT failure problem when the LBT failure event occurs in a Primary Secondary Cell (PSCell).

15. The method of claim 10 , further comprising receiving a configuration that indicates at least one of a time period and the threshold.

16. The method of claim 15 , further comprising resetting the LBT failure counter when at least one of the time period and the threshold is reconfigured.

17. The method of claim 10 , further comprising resetting the LBT failure counter when the MAC entity considers LBT for a UL transmission attempt as successful.

18. The method of claim 10 , further comprising resetting the LBT failure counter when a reset of the MAC entity is requested.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 21, 2023
From: CHEN, HUNG-CHEN; CHOU, CHIE-MING; WEI, CHIA-HUNG; SHIH, MEI-JU
To: FG INNOVATION COMPANY LIMITED
Reel/Frame 064982/0105 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 21, 2023
From: FG INNOVATION COMPANY LIMITED
To: HANNIBAL IP LLC
Reel/Frame 064982/0191 →
Continuity (4)
Continuation 17592664 · Feb 4, 2022
Continuation 16737787 · Jan 8, 2020
Provisional Application 62790099 · Jan 9, 2019
Related Publication 20240090019A1 · Mar 14, 2024
References Cited (75)
US 8625486B2 · Wang et al. · 2014 [cited by applicant]
US 11272535B2 · Chen · 2022 [cited by examiner]
US 11805544B2 · Chen · 2023 [cited by examiner]
US 20170006641A1 · Dinan · 2017 [cited by examiner]
US 20170231002A1 · Babaei et al. · 2017 [cited by applicant]
US 20170231005A1 · Babaei · 2017 [cited by examiner]
US 20180124825A1 · Lee · 2018 [cited by examiner]
US 20180124831A1 · Dinan · 2018 [cited by examiner]
US 20180176961A1 · Babaei · 2018 [cited by examiner]
US 20180184362A1 · Babaei · 2018 [cited by examiner]
US 20190363843A1 · Gordaychik · 2019 [cited by examiner]
US 20200077446A1 · Agiwal · 2020 [cited by examiner]
US 20200154480A1 · Jose · 2020 [cited by examiner]
US 20200221309A1 · Ozturk · 2020 [cited by examiner]
US 20200267763A1 · Deogun · 2020 [cited by examiner]
US 20210007101A1 · Tooher · 2021 [cited by examiner]
US 20210100031A1 · Cirik · 2021 [cited by examiner]
US 20210235500A1 · Hong · 2021 [cited by examiner]
US 20210243808A1 · Deenoo · 2021 [cited by examiner]
US 20210352717A1 · Lee et al. · 2021 [cited by applicant]
US 20220039016A1 · Terry et al. · 2022 [cited by applicant]
US 20220236222A1 · Chen · 2022 [cited by applicant]
CN 107371168 · 2017 [cited by applicant]
CN 107770868 · 2018 [cited by applicant]
CN 108633097 · 2018 [cited by applicant]
CN 113273269 · 2021 [cited by applicant]
CN 118055466A · 2024 [cited by applicant]
EP 3909331 · 2021 [cited by applicant]
EP 3909331B1 · 2023 [cited by applicant]
EP 4311327 · 2024 [cited by applicant]
IN 505116 · 2024 [cited by applicant]
WO 20170171999 · 2017 [cited by applicant]
WO 20170193843 · 2017 [cited by applicant]
WO 2020087369 · 2020 [cited by applicant]
WO 2020143672 · 2020 [cited by applicant]
Notice of Allowance issued on Sep. 11, 2023 for corresponding U.S. Appl. No. 17/592,664. [cited by applicant]
Notice of Allowance issued on Jun. 2, 2023 for corresponding U.S. Appl. No. 17/592,664. [cited by applicant]
Non-Final Office Action issued on Jan. 27, 2023 for corresponding U.S. Appl. No. 17/592,664. [cited by applicant]
Second Office Action issued on Sep. 27, 2023, for corresponding Chinese Patent Application No. 2020800082931. [cited by applicant]
3GPP TSG-RAN2 Meeting #62bis, 2008, R2-083143, Change Request 36.321 CR rev 8.20. [cited by applicant]
5G, 3GPP TS 38.321 V15.3.0, 2018, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 15). [cited by applicant]
Extended European Search Report for European Patent Application No. 20739185.5, issued on Jul. 26, 2022. [cited by applicant]
Final Examination Report issued for Indian Patent Application No. 202147035288, on Mar. 11, 2022. [cited by applicant]
Final Office Action for U.S. Appl. No. 16/737,787, issued on Jul. 27, 2021. [cited by applicant]
Indian Patent Application No. 202147035288.0, filed Aug. 5, 2021, as a national phase of International Patent Application No. PCT/CN2020/070940. [cited by applicant]
International Preliminary Report on Patentability for PCT/CN2020/070940, issued on Jun. 16, 2021. [cited by applicant]
International Search Report for International Patent Application No. PCT/CN2020/070940, issued on Mar. 27, 2020. [cited by applicant]
Issue Notification for U.S. Appl. No. 16/737,787, issued on Feb. 16, 2022. [cited by applicant]
Mexican Patent Application No. MX/a/2021/008190, filed on Jul. 9, 2021, as a national phase of International Patent Application No. PCT/CN2020/070940. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 16/737,787, issued on Apr. 16, 2021. [cited by applicant]
Non-Final Office Action issued on Mar. 29, 2023 for corresponding Chinese Patent Application No. 2020800082931. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 16/737,787, issued on Nov. 1, 2021. [cited by applicant]
Search Report issued on Mar. 29, 2023 for corresponding Chinese Patent Application No. 20200082931. [cited by applicant]
Vietnamese Patent Application No. 1-2021-4862. filed on Jan. 8, 2020. [cited by applicant]
Written Opinion of International Searching Authority for International Patent Application No. PCT/CN2020/070940, issued on Mar. 27, 2020. [cited by applicant]
XP051557634—CMCC: “Considerations on BWP switching and multi-activation for NR-U,” 3GPP Draft; R2-1818129 (resubmission of R2-1815251), 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, Sophia-Antipol… [cited by applicant]
XP051557645—CMCC: “Consideration of RACH procedure in NR-U system,” 3GPP Draft; R2-1818141, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, Sophia-Antipolis Cedex; France—retrieved from the Internet… [cited by applicant]
XP051557768—VIVO: “LBT impacts on BFD in NR-U,” 3GPP Draft; R2-1818267, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, Sophia-Antipolis Cedex; France—retrieved from the Internet on Nov. 12, 2018: U… [cited by applicant]
First Office Action issued on Sep. 22, 2023 for corresponding Indonesian Patent Application No. P-00 2021 06112. [cited by applicant]
Notice of Allowance issued by the State Intellectual Property Office of China on Dec. 29, 2023 for corresponding Chinese Patent Application No. 2020800082931. [cited by applicant]
Extended European Search Report issued on Jan. 22, 2024 for corresponding European Patent Application No. 23215599.4. [cited by applicant]
3GPP TSG-RAN WG2 Meeting #104, R2-1818129, Spokane, USA, Nov. 12-16, 2018, Resubmission of R2-1815251, 11.2.1.2, CMCC, Consideration of BWP switching and multi-activation for NR-U, Discussion. [cited by applicant]
Intimation of Grant of Indian Patent No. 505116, issued by the Indian Patent Office on Jan. 30, 2024, for corresponding Indian Patent Application No. 202147035288. [cited by applicant]
United Kingdom patent registration designated for validation in European Patent 3909331 on Jan. 18, 2024. [cited by applicant]
English translation of German Bibliographic Notification issued on Dec. 21, 2023 for German Patent Registration No. 602020022716. [cited by applicant]
Bibliographic Notification issued on Dec. 23, 2024 for German Patent Registration No. 602020022716. [cited by applicant]
German Patent Registration No. 602020022716 designated for validation in European Patent 3909331 on Nov. 16, 2023. [cited by applicant]
English translation of Chinese Patent Certificate issued on Apr. 2, 2024 for corresponding Chinese Patent Application No. 20208008293. [cited by applicant]
Chinese Patent Certificate issued on Apr. 2, 2024 for corresponding Chinese Patent Application No. 20208008293. [cited by applicant]
Communication under Rule 71(3) EPC dated Nov. 20, 2024 issued in corresponding EP 23215599.4. [cited by applicant]
Extended European Search report dated Jan. 22, 2024 issued in EP Application No. 23215599.4. [cited by applicant]
Vivo: “LBT impacts on BFD in NR-U”, vol. RAN WG2, No. Spokane, USA; Nov. 12, 2018-Nov 16, 2018 Nov. 12, 2018 (Nov. 12, 2018),XP051557768, [Retrieved from the Internet] URLzhttp://www.3gpp.org/ftp/Meetings%5FBGPP%5FSYNC/… [cited by applicant]
ACMCC: “Considerations on BWP switchingand multi-activation for NR-U”,3GPP Draft; R2-1818129 Considerations ONBWP Switching and Activation for NR-U(Resubmission of R2-1815251), 3rdgeneration Partnership project (3GPP),M… [cited by applicant]
CMCC: “Consideration of RACH procedure inNR-U system”,3GPP Draft; R2-1818141, 3rd Generationpartnership Project (3GPP), Mobilecompetence Centre ; 650, Route Deslucioles; F-06921 Sophia-Antipolis Cedex; Francelvol. RAN W… [cited by applicant]
Corresponding co-owned European Application No. 25171709.6, as filed on Apr. 22, 2025. [cited by applicant]