Systems and methods for fleet management of robotic surgical systems

Patent metadata

Field	Value
Publication number	US-11642183-B2
Application number	US-201916429336-A
Country	US
Kind code	B2
Filing date	Jun 3, 2019
Priority date	Jun 6, 2018
Publication date	May 9, 2023
Grant date	May 9, 2023

Abstract

One method for fleet management of robotic surgical systems includes receiving, by a management server from a robotic surgery system, a provisioning request; in response to receiving the provisioning request: generating an encryption key pair for the robotic surgery system, the encryption key pair comprising a private key and a public key, communicating the private key to the robotic surgery system, and communicating a set of secure certificates to the robotic surgery system, at least one of the secure certificates enabling secure communications between the robotic surgery system and the management server; receiving from the robotic surgery system, and using the at least one secure certificate enabling secure communications, a message indicating one or more software packages, each software package indicating a version of an installed software package on the robotic surgery system; communicating one or more software updates to the robotic surgery system based on the message; and registering, at the management server, the robotic surgery system.

First claim

That which is claimed is:

1. A method comprising:
receiving, by a management server from a robotic surgical system, a provisioning request;
in response to receiving the provisioning request:
generating an encryption key pair for the robotic surgical system, the encryption key pair comprising a private key and a public key,
communicating the private key to the robotic surgical system, and
communicating a set of secure certificates to the robotic surgical system, at least one of the secure certificates enabling secure communications between the robotic surgical system and the management server;

receiving from the robotic surgical system, and using the at least one secure certificate enabling secure communications, a message indicating one or more software packages, each software package indicating a version of an installed software package on the robotic surgical system;
communicating one or more software updates to the robotic surgical system based on the message; and
registering, at the management server, the robotic surgical system.

2. The method of claim 1 , further comprising activating the robotic surgical system.

3. The method of claim 1 , wherein the management server and the robotic surgical system are in communication via a robotic surgical hub device.

4. The method of claim 3 , wherein the provisioning request comprises an identifier of the robotic surgical hub device, and further comprising:
associating, by the management server, the robotic surgical system and the robotic surgical hub device.

5. The method of claim 1 , further comprising:
receiving an indication of a new software version;
generating a signed reference to the new software version;
providing the signed reference to the robotic surgical system;
receiving from the robotic surgical system a confirmation of installation of the new software version.

6. The method of claim 5 , wherein the signed reference comprises a signed uniform resource locator (“URL”).

7. The method of claim 1 , wherein the robotic surgical system and the management server are located at a medical center.

8. The method of claim 1 , wherein the robotic surgical system is located at a medical center, and the management server is located remotely from the medical center.

9. A system comprising:
one or more cloud management servers; and
a plurality of robotic surgical systems remote from the cloud management server, each robotic surgical system in communication with the cloud management server and associated with a respective medical center, wherein the cloud management server is configured to:
receive, from a robotic surgical system located at a medical center, a provisioning request;
in response to receipt of the provisioning request:
generate an encryption key pair for the robotic surgical system, the encryption key pair comprising a private key and a public key,
communicate the private key to the robotic surgical system, and
communicate a set of secure certificates to the robotic surgical system, at least one of the secure certificates enabling secure communications between the robotic surgical system and the one or more cloud management servers;
receive from the robotic surgical system, and using the at least one secure certificate enabling secure communications, a message indicating one or more software packages, each software package indicating a version of an installed software package on the robotic surgical system;
communicate one or more software updates to the robotic surgical system based on the message; and
register, at the management server, the robotic surgical system.

10. The system of claim 9 , wherein the cloud management server comprises a web portal application, the web portal application providing functionality to provision, deprovision, and update software on each robotic surgical system of the plurality of robotic surgical systems.

11. The system of claim 10 , wherein the web portal application is further configured to receive remote monitoring information from each robotic surgical system and schedule service based on the received remote monitoring information.

12. The system of claim 10 , further comprising at least one robotic surgical hub device, the robotic surgical hub device located at a first medical center, the robotic surgical hub device associated with at least one of the robotic surgical systems associated with the first medical center,
wherein the robotic surgical hub device is in communication with at least one robotic surgical system and the one or more cloud management servers,
the robotic surgical hub device comprising at least one certificate associated with the one or more cloud management servers.

13. The system of claim 9 , wherein the one or more cloud management servers are further configured to:
receive tracking or diagnostic information from a robotic surgical system;
determine a service requirement based on the received tracking or diagnostic information;
generate a service request based on the service requirement; and
transmit a message to the robotic surgical system.

14. The system of claim 13 , wherein determining a service requirement comprises determining a trend based on the received tracking or diagnostic information.

15. The system of claim 14 , wherein determining the trend is based on a trained machine learning model.

16. The system of claim 13 , wherein the message comprises an emergency shutdown message or a network disconnect command.

17. The system of claim 9 , wherein the message revokes one or more certificates.

18. A non-transitory computer-readable medium comprising processor-executable instructions to cause a processor to:
receive, from a robotic surgical system, a provisioning request;
in response to receipt of the provisioning request:
generate an encryption key pair for the robotic surgical system, the encryption key pair comprising a private key and a public key,
communicate the private key to the robotic surgical system, and
communicate a set of secure certificates to the robotic surgical system, at least one of the secure certificates enabling secure communications between the robotic surgical system and a management server;
receive from the robotic surgical system, and using the at least one secure certificate enabling secure communications, a message indicating one or more software packages, each software package indicating a version of an installed software package on the robotic surgical system;
communicate one or more software updates to the robotic surgical system based on the message; and
register the robotic surgical system.

19. The non-transitory computer-readable medium of claim 18 , further comprising processor-executable instructions to cause a processor to activate the robotic surgical system.

Assignees

• Verily Life Sciences Llc

Inventors

• Barral Joëlle
• Shuma James
• Thellend Robin
• Sprague Brandon

Classifications

• A61B2017/00123

  and automatic shutdown · CPC title

• H04L63/0823

  using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263) · CPC title

• B25J13/085

  Force or torque sensors (B25J13/082, B25J13/084 take precedence) · CPC title

• H04L63/0442

  wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30) · CPC title

• A61B34/25

  User interfaces for surgical systems · CPC title