IP Library Granted Patent US 12,204,607
Granted Patent B2
US 12,204,607 · App. 18/529,194 · Granted Jan 21, 2025

Remote respiratory therapy device management

Inventors: Wendall Eric Trull (San Diego, CA); Boris Kovtun (San Diego, CA); Tara Kalro (San Diego, CA); Joseph White (San Diego, CA); Chinmayee Somaiya (Sydney, AU); Amila Fernando (Pennant Hills, AU); Andrew Weale (San Diego, CA); Maurizio Borsotto (San Diego, CA)
Assignee: ResMed Pty Ltd
G06F17/40G06F16/23A61M2205/502A61M2205/52
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,204,607
App. No.
18/529,194
Granted
Jan 21, 2025
Kind
B2
Abstract

A server is provided and is programmed to automatically determine, based on the identification data that uniquely identifies a patient device, whether there is an upgrade to the code or data (e.g., software or firmware) stored in the electronic memory of the patient device that can be applied thereto. In response to determination that there is an upgrade that can be applied, a data package is delivered to the patient device via the first wireless transceiver, the data package to be automatically applied to the electronic memory of the patient device.

Claims (45)

1. A computer system for managing updates of firmware and/or software for remotely located patient respiratory systems, each of the patient respiratory systems comprising a plurality of components, and each of the patient respiratory systems configured to communicate at least one message that includes corresponding device identification data that is associated with a corresponding patient respiratory system, the computer system comprising:

non-transitory computer readable storage coupled to at least one hardware processor configured to perform operations comprising:

accessing an update data structure that includes data for a plurality of update packages; and

based on reception of at least one message from each of the corresponding patient respiratory systems:

a) obtaining, based on corresponding device identification data included with the at least one message, profile data that is associated with the corresponding patient respiratory system, the profile data including at least versioning data that identifies firmware and/or software installed for the corresponding patient respiratory system and/or components thereof,

b) processing the profile data against the update data structure to determine which one of the plurality of update packages to apply to the corresponding patient respiratory system and/or components thereof,

c) adding, based on determination of which one of the plurality of update packages should be applied to the corresponding patient respiratory system, a pending request to a pending request data structure, and

d) transmitting an update request message to the corresponding patient respiratory system that is based on which one of the plurality of update packages is to be applied.

2. The computer system of claim 1 , wherein each of a plurality of records of the update data structure includes: 1) at least one update pre-condition, 2) at least one update post-condition, and 3) update data for firmware and/or software.

3. The computer system of claim 2 , wherein processing the profile data against the update data structure includes comparing the profile data against the at least one update pre-condition.

4. The computer system of claim 1 , wherein the update request message includes data used to download an update based on the data included in the update request message.

5. The computer system of claim 1 , wherein the operations further comprise:

receiving, after transmitting the update request message, a status update message from the corresponding patient respiratory system, wherein the status update message includes versioning information of software and/or firmware.

6. The computer system of claim 1 , wherein the operations further comprise:

based on reception of a message from a corresponding patient respiratory system, determining whether a pending request for the corresponding patient respiratory system is in the pending request data structure.

7. The computer system of claim 6 , wherein the operations further comprise:

based on determination that the pending request is in the pending request data structure, transmitting an update request message to the corresponding patient respiratory system based on the pending request that is in the pending request data structure without performing processing profile data against the update data structure.

8. The computer system of claim 6 , wherein determination of whether there is the pending request occurs prior to obtaining the profile data.

9. The computer system of claim 1 , wherein the corresponding device identification data for the patient respiratory system includes a unique identifier that uniquely identifies the patient respiratory system from other patient respiratory systems.

10. The computer system of claim 9 , wherein the unique identifier is associated with a transceiver component that is included with the patient respiratory system.

11. The computer system of claim 1 , wherein versioning information for the software and/or firmware of the patient respiratory system is not included in the at least one message that is received.

12. The system of claim 1 , wherein the at least one hardware process is distributed among different computing devices of a cloud-based computer system.

13. A method executed on a computer system for managing updates of firmware and/or software for remotely located patient respiratory systems, each of the patient respiratory systems comprising a plurality of components, and each of the patient respiratory systems configured to communicate at least one message that includes corresponding device identification data that is associated with a corresponding patient respiratory system, the method comprising:

accessing an update data structure that includes data for a plurality of update packages; and

based on reception of at least one message from each of the corresponding patient respiratory systems:

a) obtaining, based on corresponding device identification data included with the at least one message, profile data that is associated with the corresponding patient respiratory system, the profile data including at least versioning data that identifies firmware and/or software installed for the corresponding patient respiratory system and/or components thereof,

b) processing the profile data against the update data structure to determine which one of the plurality of update packages to apply to the corresponding patient respiratory system and/or components thereof,

c) adding, based on determination of which one of the plurality of update packages should be applied to the corresponding patient respiratory system, a pending request to a pending request data structure, and

d) transmitting an update request message to the corresponding patient respiratory system that is based on which one of the plurality of update packages is to be applied.

14. The method of claim 13 , wherein each of a plurality of records of the update data structure includes: 1) at least one update pre-condition, 2) at least one update post-condition, and 3) update data for firmware and/or software.

15. The method of claim 14 , wherein processing the profile data against the update data structure includes comparing the profile data against the at least one update pre-condition.

16. The method of claim 13 , wherein the update request message includes data used to download an update based on the data included in the update request message.

17. The method of claim 13 , further comprising:

receiving, after transmitting the update request message, a status update message from the corresponding patient respiratory system, wherein the status update message includes versioning information of software and/or firmware.

18. The method of claim 13 , further comprising:

based on reception of a message from a corresponding patient respiratory system, determining whether a pending request for the corresponding patient respiratory system is in the pending request data structure.

19. The method of claim 18 , further comprising:

based on determination that the pending request is in the pending request data structure, transmitting an update request message to the corresponding patient respiratory system based on the pending request that is in the pending request data structure without performing processing profile data against the update data structure.

20. A non-transitory computer readable medium storing computer executable instructions for use with a computer system that manages updates of firmware and/or software for remotely located patient respiratory systems, each of the patient respiratory systems comprising a plurality of components, and each of the patient respiratory systems configured to communicate at least one message that includes corresponding device identification data that is associated with a corresponding patient respiratory system, the computer executable instructions including instructions configured to cause the computer system to perform operations comprising:

accessing an update data structure that includes data for a plurality of update packages; and

based on reception of at least one message from each of the corresponding patient respiratory systems:

a) obtaining, based on corresponding device identification data included with the at least one message, profile data that is associated with the corresponding patient respiratory system, the profile data including at least versioning data that identifies firmware and/or software installed for the corresponding patient respiratory system and/or components thereof,

b) processing the profile data against the update data structure to determine which one of the plurality of update packages to apply to the corresponding patient respiratory system and/or components thereof,

c) adding, based on determination of which one of the plurality of update packages should be applied to the corresponding patient respiratory system, a pending request to a pending request data structure, and

d) transmitting an update request message to the corresponding patient respiratory system that is based on which one of the plurality of update packages is to be applied.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 5, 2023
From: SOMAIYA, CHINMAYEE; FERNANDO, AMILA
To: RESMED PTY LTD
Reel/Frame 065765/0699 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 5, 2023
From: RESMED CORPORATION
To: RESMED PTY LTD
Reel/Frame 065765/0853 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 5, 2023
From: TRULL, WENDALL ERIC; KOVTUN, BORIS; KALRO, TARA; WHITE, JOSEPH; WEALE, ANDREW; BORSOTTO, MAURIZIO
To: RESMED CORPORATION
Reel/Frame 065775/0438 →
Continuity (6)
Continuation 18189060 · Mar 23, 2023
Continuation 17854956 · Jun 30, 2022
Continuation 17302992 · May 18, 2021
Continuation 17097962 · Nov 13, 2020
Provisional Application 62935356 · Nov 14, 2019
Related Publication 20240111834A1 · Apr 4, 2024
References Cited (76)
US 6208974B1 · Campbell · 2001 [cited by examiner]
US 7574368B2 · Pawlikowski et al. · 2009 [cited by applicant]
US 7913689B2 · Henry et al. · 2011 [cited by applicant]
US 7924150B2 · Baldus et al. · 2011 [cited by applicant]
US 7978062B2 · Lalonde et al. · 2011 [cited by applicant]
US 8058986B2 · Klabunde et al. · 2011 [cited by applicant]
US 8302600B2 · Andrieux et al. · 2012 [cited by applicant]
US 8302602B2 · Andrieux et al. · 2012 [cited by applicant]
US 8373556B2 · Lalonde et al. · 2013 [cited by applicant]
US 8395498B2 · Gaskill et al. · 2013 [cited by applicant]
US 8515547B2 · Mass et al. · 2013 [cited by applicant]
US 8587427B2 · Lalonde et al. · 2013 [cited by applicant]
US 8694600B2 · Gaines et al. · 2014 [cited by applicant]
US 8818522B2 · Mass et al. · 2014 [cited by applicant]
US 8863106B2 · Schöller et al. · 2014 [cited by applicant]
US 8943168B2 · Wiesner et al. · 2015 [cited by applicant]
US 8950398B2 · Andrieux et al. · 2015 [cited by applicant]
US 8970392B2 · Lalonde et al. · 2015 [cited by applicant]
US 9269251B2 · Lalonde et al. · 2016 [cited by applicant]
US 9289571B2 · Peiris et al. · 2016 [cited by applicant]
US 9495511B2 · Harrington et al. · 2016 [cited by applicant]
US 9848058B2 · Johnson et al. · 2017 [cited by applicant]
US 10108785B2 · Kamen et al. · 2018 [cited by applicant]
US 10255647B2 · Rodman et al. · 2019 [cited by applicant]
US 10290071B2 · Heil et al. · 2019 [cited by applicant]
US 10293124B2 · Bychkov et al. · 2019 [cited by applicant]
US 11042606B2 · Trull et al. · 2021 [cited by applicant]
US 11423119B2 · Trull et al. · 2022 [cited by applicant]
US 20020123673A1 · Webb · 2002 [cited by applicant]
US 20060064323A1 · Alleckson et al. · 2006 [cited by applicant]
US 20060089855A1 · Holland · 2006 [cited by applicant]
US 20060189854A1 · Webb · 2006 [cited by applicant]
US 20080271010A1 · Scholler · 2008 [cited by applicant]
US 20090063193A1 · Barton et al. · 2009 [cited by applicant]
US 20090081951A1 · Erdmann et al. · 2009 [cited by applicant]
US 20090099867A1 · Newman · 2009 [cited by applicant]
US 20110073107A1 · Rodman · 2011 [cited by examiner]
US 20130036412A1 · Birtwhistle et al. · 2013 [cited by applicant]
US 20130154851A1 · Gaskill et al. · 2013 [cited by applicant]
US 20130239961A1 · Ross, Jr. et al. · 2013 [cited by applicant]
US 20130317753A1 · Kamen et al. · 2013 [cited by applicant]
US 20130317837A1 · Ballantyne et al. · 2013 [cited by applicant]
US 20140102455A1 · D'Angelo et al. · 2014 [cited by applicant]
US 20140188516A1 · Kamen et al. · 2014 [cited by applicant]
US 20140366876A1 · Huby et al. · 2014 [cited by applicant]
US 20150006196A1 · Schoeller · 2015 [cited by examiner]
US 20150070187A1 · Wiesner et al. · 2015 [cited by applicant]
US 20150154364A1 · Biasi et al. · 2015 [cited by applicant]
US 20150370551A1 · Mahajan · 2015 [cited by applicant]
US 20160034655A1 · Gray et al. · 2016 [cited by applicant]
US 20160188318A1 · Li et al. · 2016 [cited by applicant]
US 20160193437A1 · Bao et al. · 2016 [cited by applicant]
US 20160199601A1 · Peiris et al. · 2016 [cited by applicant]
US 20170136198A1 · Delangre · 2017 [cited by examiner]
US 20170239432A1 · Delangre et al. · 2017 [cited by applicant]
US 20170242683A1 · Nekoomaram et al. · 2017 [cited by applicant]
US 20180233225A1 · Experton et al. · 2018 [cited by applicant]
US 20180268106A1 · Velaga · 2018 [cited by examiner]
US 20180286510A1 · Kwan et al. · 2018 [cited by applicant]
US 20190347086A1 · Kiaie · 2019 [cited by applicant]
US 20210146080A1 · Trull et al. · 2021 [cited by applicant]
US 20210271737A1 · Trull et al. · 2021 [cited by applicant]
US 20220342957A1 · Trull et al. · 2022 [cited by applicant]
US 20230281274A1 · Trull et al. · 2023 [cited by applicant]
CN 102136934 · 2011 [cited by applicant]
CN 104834537 · 2015 [cited by applicant]
CN 107203395 · 2017 [cited by applicant]
CN 107358032 · 2017 [cited by applicant]
JP 2014016837 · 2014 [cited by applicant]
JP 2017519292 · 2017 [cited by applicant]
JP 2017534107 · 2017 [cited by applicant]
JP 2022551008 · 2022 [cited by applicant]
International Search Report for Application No. PCT/IB2020/060711, six pages, mailed Jan. 15, 2021. [cited by applicant]
Written Opinion of the ISA for Application No. PCT/IB2020/060711, six pages, mailed Jan. 15, 2021. [cited by applicant]
Notification of the First Office Action with English Translation for Chinese Application No. 202080086564.5, 20 pages, dated Dec. 28, 2022. [cited by applicant]
Notice of Refusal with English Translation for Application No. JP 2023-008086, 14 pages, dated Dec. 2, 2024. [cited by applicant]