IP Library › Granted Patent US 12,262,440
Granted Patent B2
US 12,262,440 · App. 18/432,633 · Granted Mar 25, 2025

Simplified UE + eNB messaging

Inventors: Venkata Ratnakar Rao Rayavarapu (Bangalore, IN); Nicholas William Anderson (Exeter, GB); Richard Charles Burbidge (Swindon, GB); Gordon Peter Young (Kineton, GB)
Assignee: BlackBerry Limited
H04W76/27H04W68/005H04W72/23H04W76/19H04W76/28
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,262,440
App. No.
18/432,633
Granted
Mar 25, 2025
Kind
B2
Abstract

A method, mobile device ( 101 ) and radio access network RAN ( 102 ) are disclosed for suspending and re-establishing a radio resource control (RRC) connection. In some examples, the mobile device ( 101 ) indicates a preference to have the RRC connection either suspended or released. In other examples, RAN ( 102 ) sends to the mobile device ( 101 ) a connection suspend command message instructing the mobile device to suspend a RRC connection with the RAN ( 102 ). The mobile device ( 101 ), in response to the connection suspend command message, suspends the RRC connection. When the RRC connection is suspended the mobile device ( 101 ) cannot transmit or receive user plane data to the RAN ( 102 ) and performs functions the same as or similar to idle mode functions. On suspension, RRC connection information is stored and can be used to re-establish the suspended RRC connection.

Claims (48)

1. A method, comprising:

sending, by a first Radio Access Network (RAN) node of a RAN, a connection suspend command message to a user equipment (UE), wherein the connection suspend command message instructs the UE to suspend a radio resource control (RRC) connection between the UE and the first RAN node by:

causing storage of RRC connection data for the suspended RRC connection, and

causing release of radio resources associated with the suspended RRC connection, wherein user plane communications between the UE and the RAN are disabled until receipt of an RRC connection resume message by a second RAN node of the RAN from the UE, and wherein the RRC connection resume message comprises: an identifier of the first RAN node where the RRC connection was suspended, and a Short Message Authentication Code-Integrity (MAC-I) derived using parameters relating to the first RAN node where the RRC connection was suspended; and

in response to receiving the RRC connection resume message, resuming the user plane communications between the UE and the RAN by resuming the suspended RRC connection.

2. The method according to claim 1 , wherein the connection suspend command message sent by the first RAN node causes the UE to perform idle-mode mobility procedures.

3. The method according to claim 2 , wherein the connection suspend command message is sent in response to at least one suspension criterion being met at the first RAN node.

4. The method according to claim 3 , wherein the at least one suspension criterion is at least one of:

an expiry of a timer at the first RAN node;

a reception of a suspension request message from the UE at the first RAN node;

no user plane data having been received from or sent to the UE for a time period;

no user plane data being expected to be received from or sent to the UE for a period of time; or

a higher layer indication to a RRC layer.

5. The method according to claim 1 , wherein the first and second RAN nodes are eNodeBs operating according to Long Term Evolution (LTE) or LTE-Advanced protocols.

6. A method, comprising:

receiving, by a user equipment (UE), a connection suspend command message from a first Radio Access Network (RAN) node of a RAN, wherein the connection suspend command message instructs the UE to suspend a radio resource control (RRC) connection between the UE and the first RAN node by:

storing RRC connection data for the suspended RRC connection; and

releasing radio resources associated with the suspended RRC connection, wherein user plane communications between the UE and the RAN are disabled until the UE transmits an RRC connection resume request to the RAN;

in response to the connection suspend command message, suspending the RRC connection;

transmitting, to a second RAN node of the RAN, an RRC connection resume message comprising a request to resume the suspended RRC connection, wherein the RRC connection resume message comprises: an identifier of the first RAN node where the RRC connection was suspended, and a Short Message Authentication Code-Integrity (MAC-I) derived using parameters relating to the first RAN node where the RRC connection was suspended, and wherein the RRC connection resume message causes the suspended RRC connection to be resumed.

7. The method according to claim 6 , further comprising: responsive to receiving the connection suspend command message, performing idle-mode mobility procedures.

8. The method according to claim 6 , wherein the UE communicates with the RAN in accordance with Long Term Evolution (LTE) or LTE Advanced protocols.

9. A first Radio Access Network (RAN) node of a RAN, comprising:

at least one hardware processor; and

a non-transitory computer-readable storage medium coupled to the at least one hardware processor and storing programming instructions for execution by the at least one hardware processor, wherein the programming instructions, when executed, cause the at least one hardware processor to perform operations comprising:

sending, a connection suspend command message to a user equipment (UE), wherein the connection suspend command message instructs the UE to suspend a radio resource control (RRC) connection between the UE and the first RAN node by:

causing storage of RRC connection data for the suspended RRC connection, and

causing release of radio resources associated with the suspended RRC connection, wherein user plane communications between the UE and the RAN are disabled until receipt of an RRC connection resume message by a second RAN node of the RAN from the UE, and wherein the RRC connection resume message comprises: an identifier of the first RAN node where the RRC connection was suspended, and a Short Message Authentication Code-Integrity (MAC-I) derived using parameters relating to the first RAN node where the RRC connection was suspended; and

in response to receiving the RRC connection resume message, resuming the user plane communications between the UE and the RAN by resuming the suspended RRC connection.

10. The first RAN node according to claim 9 , wherein the connection suspend command message sent by the first RAN node causes the UE to perform idle-mode mobility procedures.

11. The first RAN node according to claim 9 , wherein the connection suspend command message is sent in response to at least one suspension criterion being met at the first RAN node.

12. The first RAN node according to claim 11 , wherein the at least one suspension criterion is at least one of:

an expiry of a timer at the first RAN node;

a reception of a suspension request message from the UE at the first RAN node;

no user plane data having been received from or sent to the UE for a time period;

no user plane data being expected to be received from or sent to the UE for a period of time; or

a higher layer indication to a RRC layer.

13. The first RAN node according to claim 9 , wherein the first and second RAN nodes are eNodeBs operating according to Long Term Evolution (LTE) or LTE-Advanced protocols.

14. A user equipment (UE), comprising:

at least one hardware processor; and

a non-transitory computer-readable storage medium coupled to the at least one hardware processor and storing programming instructions for execution by the at least one hardware processor, wherein the programming instructions, when executed, cause the at least one hardware processor to perform operations comprising:

receiving a connection suspend command message from a first Radio Access Network (RAN) node of a RAN, wherein the connection suspend command message instructs the UE to suspend a radio resource control (RRC) connection between the UE and the first RAN node by:

storing RRC connection data for the suspended RRC connection; and

releasing radio resources associated with the suspended RRC connection, wherein user plane communications between the UE and the RAN are disabled until the UE transmits an RRC connection resume request to the RAN; and

in response to the connection suspend command message, suspending the RRC connection; and

transmitting, to a second RAN node of the RAN, an RRC connection resume message comprising a request to resume the suspended RRC connection, wherein the RRC connection resume message comprises: an identifier of the first RAN node where the RRC connection was suspended, and a Short Message Authentication Code-Integrity (MAC-I) derived using parameters relating to the first RAN node where the RRC connection was suspended, and wherein the RRC connection resume message causes the suspended RRC connection to be resumed.

15. The UE according to claim 14 , the operations further comprising: responsive to receiving the connection suspend command message, performing idle-mode mobility procedures.

16. The UE according to claim 14 , wherein the UE communicates with the RAN in accordance with Long Term Evolution (LTE) or LTE Advanced protocols.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 6, 2024
From: RAYAVARAPU, VENKATA RATNAKAR RAO; ANDERSON, NICHOLAS WILLIAM; BURBIDGE, RICHARD CHARLES; YOUNG, GORDON PETER
To: RESEARCH IN MOTION UK LIMITED
Reel/Frame 066392/0098 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 6, 2024
From: RESEARCH IN MOTION UK LIMITED
To: RESEARCH IN MOTION LIMITED
Reel/Frame 066507/0713 →
CHANGE OF NAME Recorded Feb 6, 2024
From: RESEARCH IN MOTION LTD.
To: BLACKBERRY LIMITED
Reel/Frame 066507/0745 →
Continuity (5)
Continuation 17196793 · Mar 9, 2021
Continuation 15587082 · May 4, 2017
Division 13431799 · Mar 27, 2012
Provisional Application 61523021 · Aug 12, 2011
Related Publication 20240179788A1 · May 30, 2024
References Cited (168)
US 5924042A · Sakamoto et al. · 1999 [cited by applicant]
US 7016321B1 · Park et al. · 2006 [cited by applicant]
US 8238281B2 · Pelletier et al. · 2012 [cited by applicant]
US 8335183B2 · Nguyen · 2012 [cited by applicant]
US 8514732B2 · Gholmieh et al. · 2013 [cited by applicant]
US 8514735B1 · Vargantwar · 2013 [cited by applicant]
US 10986689B2 · Rayavarapu et al. · 2021 [cited by applicant]
US 20030093535A1 · Choi et al. · 2003 [cited by applicant]
US 20040192309A1 · Watanabe et al. · 2004 [cited by applicant]
US 20060035642A1 · Farnsworth · 2006 [cited by examiner]
US 20060159061A1 · Takano · 2006 [cited by examiner]
US 20060251098A1 · Morioka · 2006 [cited by applicant]
US 20070211693A1 · Hirsimaki et al. · 2007 [cited by applicant]
US 20070213061A1 · Kim · 2007 [cited by applicant]
US 20080039092A1 · Kitazoe · 2008 [cited by applicant]
US 20080043623A1 · Franceschini et al. · 2008 [cited by applicant]
US 20080095119A1 · Bachmann et al. · 2008 [cited by applicant]
US 20080167089A1 · Suzuki et al. · 2008 [cited by applicant]
US 20080233963A1 · Alanara et al. · 2008 [cited by applicant]
US 20080242292A1 · Koskela et al. · 2008 [cited by applicant]
US 20090129339A1 · Young et al. · 2009 [cited by applicant]
US 20090137258A1 · Nguyen · 2009 [cited by applicant]
US 20090147670A1 · Hu · 2009 [cited by applicant]
US 20090163211A1 · Kitazoe et al. · 2009 [cited by applicant]
US 20090221306A1 · Jacobsohn et al. · 2009 [cited by applicant]
US 20090238098A1 · Cai et al. · 2009 [cited by applicant]
US 20090274095A1 · Iwasa · 2009 [cited by examiner]
US 20090274122A1 · Wu · 2009 [cited by applicant]
US 20090285157A1 · Yeoum et al. · 2009 [cited by applicant]
US 20100056147A1 · Sun et al. · 2010 [cited by applicant]
US 20100074246A1 · Harada et al. · 2010 [cited by applicant]
US 20100111039A1 · Kim et al. · 2010 [cited by applicant]
US 20100113030A1 · Kanazawa et al. · 2010 [cited by applicant]
US 20100130205A1 · Jung et al. · 2010 [cited by applicant]
US 20100173610A1 · Kitazoe et al. · 2010 [cited by applicant]
US 20100184438A1 · Wu · 2010 [cited by applicant]
US 20100195621A1 · Kekki et al. · 2010 [cited by applicant]
US 20100220689A1 · Hu et al. · 2010 [cited by applicant]
US 20100254348A1 · Prakash et al. · 2010 [cited by applicant]
US 20100255835A1 · Suzuki et al. · 2010 [cited by applicant]
US 20100278037A1 · Jen et al. · 2010 [cited by applicant]
US 20100278108A1 · Cho et al. · 2010 [cited by applicant]
US 20100284333A1 · Shirota et al. · 2010 [cited by applicant]
US 20110009075A1 · Jantunen et al. · 2011 [cited by applicant]
US 20110019532A1 · Jung et al. · 2011 [cited by applicant]
US 20110038347A1 · Patil et al. · 2011 [cited by applicant]
US 20110039552A1 · Narasimha et al. · 2011 [cited by applicant]
US 20110092198A1 · Miyata · 2011 [cited by applicant]
US 20110092236A1 · Iwamura et al. · 2011 [cited by applicant]
US 20110105120A1 · Abdel-Samad · 2011 [cited by examiner]
US 20110117908A1 · Huang et al. · 2011 [cited by applicant]
US 20110159873A1 · Iwamura et al. · 2011 [cited by applicant]
US 20110159880A1 · Kumar et al. · 2011 [cited by applicant]
US 20110176512A1 · Sun · 2011 [cited by applicant]
US 20110176680A1 · Wu · 2011 [cited by applicant]
US 20110194441A1 · Jung et al. · 2011 [cited by applicant]
US 20110195668A1 · Lee et al. · 2011 [cited by applicant]
US 20110199898A1 · Cho et al. · 2011 [cited by applicant]
US 20110222451A1 · Peisa · 2011 [cited by applicant]
US 20110235581A1 · Diachina et al. · 2011 [cited by applicant]
US 20110269426A1 · Hultin · 2011 [cited by examiner]
US 20110269463A1 · Wang et al. · 2011 [cited by applicant]
US 20110292790A1 · Iwamura et al. · 2011 [cited by applicant]
US 20110294508A1 · Min et al. · 2011 [cited by applicant]
US 20110299429A1 · Tiwari · 2011 [cited by applicant]
US 20110306345A1 · Wu · 2011 [cited by applicant]
US 20120002637A1 · Adjakple et al. · 2012 [cited by applicant]
US 20120069732A1 · Xu et al. · 2012 [cited by applicant]
US 20120120789A1 · Ramachandran et al. · 2012 [cited by applicant]
US 20120236709A1 · Ramachandran et al. · 2012 [cited by applicant]
US 20120264420A1 · Williams · 2012 [cited by applicant]
US 20120270545A1 · Zhao et al. · 2012 [cited by applicant]
US 20120281561A1 · Shukla et al. · 2012 [cited by applicant]
US 20130039287A1 · Rayavarapu et al. · 2013 [cited by applicant]
US 20130039339A1 · Rayavarapu et al. · 2013 [cited by applicant]
US 20130215772A1 · Kaur et al. · 2013 [cited by applicant]
US 20130223267A1 · Jung et al. · 2013 [cited by applicant]
US 20130223268A1 · Jung et al. · 2013 [cited by applicant]
US 20130260740A1 · Rayavarapu et al. · 2013 [cited by applicant]
US 20130260810A1 · Rayavarapu et al. · 2013 [cited by applicant]
US 20130260811A1 · Rayavarapu et al. · 2013 [cited by applicant]
US 20150023284A1 · Zhao et al. · 2015 [cited by applicant]
US 20170245318A1 · Rayavarapu et al. · 2017 [cited by applicant]
US 20210204351A1 · Rayavarapu et al. · 2021 [cited by applicant]
CN 101483898 · 2009 [cited by applicant]
CN 101617552 · 2009 [cited by applicant]
CN 101873718 · 2010 [cited by applicant]
EP 2061192 · 2009 [cited by applicant]
EP 2252127 · 2010 [cited by applicant]
EP 2557889 · 2013 [cited by applicant]
EP 2617261 · 2013 [cited by applicant]
TW 201318463 · 2013 [cited by applicant]
TW 201320679 · 2013 [cited by applicant]
WO WO2012034580 · 2012 [cited by applicant]
ETSI TS 136 331—LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification, Nov. 2008, V8.2.0, p. 33-39. (Year: 2008). [cited by examiner]
3GPP TS 36.331 (V10.2.0) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol Specification (… [cited by applicant]
3GPP 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol Specification (Release 8; R2-081378… [cited by applicant]
3GPP TS 36.300 (V8.12.0) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network… [cited by applicant]
ETSI TS 36.331 (V10.4.0) LTE: Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol Specification (Release 10); Jan. 2012, 300 pages. [cited by applicant]
HTC Corporation “Performance Enhancement in the RRC Connection Re-Establishment Procedure” R2-093997; Los Angeles; Jun. 29-Jul. 3, 2009, 6 pages. [cited by applicant]
LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (3GPP TS 36.331 version 10.4.0 Release 10), 300 pages. [cited by applicant]
3GPP TS 25.331; “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 11)”; vol. RAN WG2; No. V11.1.0; Mar. 16, 2012, 1,91… [cited by applicant]
3GPP TS 36.331; “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol Specification (Release… [cited by applicant]
3GPP TS 25.331; “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 4)”; vol. V4.1.0; Jun. 1, 2001, 811 pages. [cited by applicant]
3GPP TS 36.331 [V8.16.0] 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol Specification (… [cited by applicant]
3GPP TS 23.272 [V9.8.0], 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Circuit Switched (CS) Fallback in Evolved Packet System (EPS), Stage 2, Release 9, Jun. 2011, 72 pa… [cited by applicant]
Extended European Search Report in European Appln. No. 12161621.3, mailed on Nov. 14, 2012, 7 pages. [cited by applicant]
EP Communication Pursuant to Article 94(3) EPC in European Appln. No. 12161621.3, mailed on Mar. 17, 2014, 7 pages. [cited by applicant]
Extended European Search Report in European Appln. No. 12161622.1, mailed on Aug. 21, 2012, 8 pages. [cited by applicant]
Extended European Search Report in European Appln. No. 12161618.9, mailed on Sep. 11, 2012, 8 pages. [cited by applicant]
EP Communication Pursuant to Article 94(3) EPC in European Appln. No. 12161618.9, mailed on Jun. 2, 2014, 9 pages. [cited by applicant]
EP Communication Pursuant to Article 94(3) EPC in European Appln. No. 12161619.7, mailed on Mar. 17, 2014, 8 pages. [cited by applicant]
EP Communication Pursuant to Article 94(3) EPC in European Appln. No. 12161620.5, mailed on Mar. 17, 2014, 9 pages. [cited by applicant]
Extended European Search Report in European Appln. No. 12161619.7, mailed on Nov. 14, 2012, 7 pages. [cited by applicant]
Extended European Search Report in European Appln. No. 12161620.5, mailed on Sep. 14, 2012, 8 pages. [cited by applicant]
EP Communication Pursuant to Article 94(3) EPC in European Appln. No. 12161618.9, mailed on Jan. 12, 2016, 5 pages. [cited by applicant]
EP Communication Pursuant to Article 94(3) EPC in European Appln. No. 12161621.3, mailed on Jan. 12, 2016, 7 pages. [cited by applicant]
EP Communication Pursuant to Article 94(3) EPC in European Appln. No. 12161622.1, mailed on Oct. 25, 2016, 8 pages. [cited by applicant]
EP Communication Pursuant to Article 94(3) EPC in European Appln. No. 12161618.9, mailed on Dec. 22, 2016, 7 pages. [cited by applicant]
EP Communication Pursuant to Article 94(3) EPC in European Appln. No. 12161620.5, mailed on Dec. 22, 2016, 7 pages. [cited by applicant]
EP Communication Pursuant to Article 94(3) EPC in European Appln. No. 12161621.3, mailed on Dec. 23, 2016, 5 pages. [cited by applicant]
EP Communication Pursuant to Article 94(3) EPC in European Appln. No. 12161619.7, mailed on Dec. 23, 2016, 7 pages. [cited by applicant]
EP Communication Pursuant to Article 94(3) EPC in European Appln. No. 12161618.9, mailed on Mar. 15, 2018, 5 pages. [cited by applicant]
EP Communication Pursuant to Article 94(3) EPC in European Appln. No. 12161620.5, mailed on Mar. 15, 2018, 5 pages. [cited by applicant]
EP Communication Pursuant to Article 94(3) EPC in European Appln. No. 12161621.3, mailed on Mar. 15, 2018, 8 pages. [cited by applicant]
EP Communication Pursuant to Article 94(3) EPC in European Appln. No. 12161619.7, mailed on Mar. 15, 2018, 6 pages. [cited by applicant]
EP Communication under Rule 71(3) EPC in European Appln. No. 12161619.7, mailed on Feb. 5, 2019, 149 pages. [cited by applicant]
Extended European Search Report in European Appln. No. 19184674.0, mailed on Sep. 11, 2019, 6 pages. [cited by applicant]
Extended European Search Report in European Appln. No. 19184673.2, mailed on Sep. 11, 2019, 6 pages. [cited by applicant]
Extended European Search Report in European Appln. No. 19184676.5, mailed on Sep. 11, 2019, 6 pages. [cited by applicant]
EP Communication under Rule 71 (3) EPC in European Appln. No. 19184673.2, mailed on Jul. 27, 2020, 7 pages. [cited by applicant]
EP Communication under Rule 71 (3) EPC in European Appln. No. 19184674.0, mailed on Jul. 27, 2020, 7 pages. [cited by applicant]
EP Communication under Rule 71 (3) EPC in European Appln. No. 19184676.5, mailed on Aug. 13, 2020, 5 pages. [cited by applicant]
Extended European Search Report in European Appln. No. 23207280.1, mailed on Jan. 30, 2024, 9 pages. [cited by applicant]
International Search Report and Written Opinion in International Appln. No. PCT/EP2012/065632, mailed on Nov. 14, 2012, 10 pages. [cited by applicant]
International Preliminary Report on Patentability in International Appln. No. PCT/EP2012/065632, mailed on Feb. 27, 2014, 7 pages. [cited by applicant]
International Search Report and Written Opinion in International Appln. No. PCT/EP2012/065552, mailed on Nov. 23, 2012, 12 pages. [cited by applicant]
International Search Report and Written Opinion in International Appln. No. PCT/GB2013/050792, mailed on May 7, 2013, 12 pages. [cited by applicant]
International Search Report and Written Opinion in International Appln. No. PCT/EP2012/065634, mailed on Nov. 6, 2012, 7 pages. [cited by applicant]
International Preliminary Report on Patentability in International Appln. No. PCT/EP2012/065634, mailed on Feb. 27, 2014, 5 pages. [cited by applicant]
International Search Report and Written Opinion in International Appln. No. PCT/GB2013/050781, mailed on Jul. 4, 2013, 13 pages. [cited by applicant]
Non-Final Office Action in U.S. Appl. No. 15/587,082, mailed on Oct. 3, 2017, 27 pages. [cited by applicant]
Final Office Action in U.S. Appl. No. 15/587,082, mailed on May 18, 2018, 23 pages. [cited by applicant]
Interview Summary in U.S. Appl. No. 15/587,082, mailed on Jul. 30, 2018, 1 page. [cited by applicant]
Advisory Action in U.S. Appl. No. 15/587,082, mailed on Aug. 3, 2018, 7 pages. [cited by applicant]
Non-Final Office Action in U.S. Appl. No. 15/587,082, mailed on Feb. 8, 2019, 24 pages. [cited by applicant]
Final Office Action in U.S. Appl. No. 15/587,082, mailed on Aug. 16, 2019, 24 pages. [cited by applicant]
Advisory Action in U.S. Appl. No. 15/587,082, mailed on Oct. 29, 2019, 3 pages. [cited by applicant]
Non-Final Office Action in U.S. Appl. No. 15/587,082, mailed on Mar. 24, 2020, 20 pages. [cited by applicant]
Final Office Action in U.S. Appl. No. 15/587,082, mailed on Oct. 1, 2020, 25 pages. [cited by applicant]
Notice of Allowance in U.S. Appl. No. 15/587,082, mailed on Dec. 31, 2020, 6 pages. [cited by applicant]
Non-Final Office Action in U.S. Appl. No. 17/196,793, mailed on Mar. 15, 2023, 25 pages. [cited by applicant]
Final Office Action in U.S. Appl. No. 17/196,793, mailed on Jun. 26, 2023, 18 pages. [cited by applicant]
Notice of Allowance in U.S. Appl. No. 17/196,793, mailed on Nov. 8, 2023, 10 pages. [cited by applicant]
Supplemental Notice of Allowance in U.S. Appl. No. 17/196,793, mailed on Dec. 6, 2023, 14 pages. [cited by applicant]
Office Action in Canadian Appln. No. 2,844,629, mailed on Jul. 5, 2016, 3 pages. [cited by applicant]
Office Action in Canadian Appln. No. 2,844,630, mailed on Jul. 5, 2016, 4 pages. [cited by applicant]
Office Action in Canadian Appln. No. 2,844,630, mailed on Apr. 28, 2017, 4 pages. [cited by applicant]
Office Action in Canadian Appln. No. 2,844,629, mailed on May 3, 2017, 4 pages. [cited by applicant]
Examination Search Report in Canadian Appln. No. 2,844,629, mailed on May 4, 2018, 11 pages. [cited by applicant]
Notice of Allowance in Canadian Appln. No. 2,844,630, mailed on May 2, 2018, 1 page. [cited by applicant]
Notice of Allowance in Canadian Appln. No. 2,844,629, mailed on Apr. 5, 2019, 10 pages. [cited by applicant]
Office Action in Chinese Appln. No. 201280050197.9, mailed on Dec. 16, 2016, 8 pages. [cited by applicant]
Office Action in Chinese Appln. No. 201280050198.3, mailed on Jan. 5, 2017, 9 pages. [cited by applicant]
Office Action in Chinese Appln. No. 201280050197.9, mailed on Aug. 2, 2017, 7 pages. [cited by applicant]
Office Action in Chinese Appln. No. 201280050198.3, mailed on Sep. 5, 2017, 8 pages. [cited by applicant]
Office Action in Chinese Appln. No. 201280050197.9, mailed on Jan. 19, 2018, 10 pages. [cited by applicant]
Office Action in Chinese Appln. No. 201280050198.3, mailed on Mar. 5, 2018, 4 pages. [cited by applicant]
Cited By (1)
US 12,526,880