# US 12,594,135 B2 · Network virtualization for remotely controlling robotic-assisted medical procedures

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 12,594,135 B2
- Document ID: US12594135B2
- Status: Granted
- Kind: B2
- Application number: 19/320,605
- Filed: 2025-09-05
- Published: 2026-01-22
- Granted: 2026-04-07
- Earliest claimed: 2024-07-22
- Assignees: Sovato Health, Inc.
- Applicants: Sovato Health, Inc.
- Inventors: Brian Gaither; Daniel Wayne Haskell; Cynthia Perazzo; Tyler Grotenhuis; Blair Whitney
- Web page: https://patentgrep.com/patent/US12594135B2

## CPC

- A61B 34/30: Surgical robots
- A61B 34/35: for telesurgery
- A61B 34/37: Leader-follower robots (A61B34/35 takes precedence)
- A61B: DIAGNOSIS; SURGERY; IDENTIFICATION (usefulness limited to only animals A61D)

## Abstract

Disclosed systems, apparatuses, and methods enable remotely controlling robotic-assisted medical systems, such as robotic-assisted surgery systems, for performing remote robotic-assisted medical procedures. Disclosed approaches provide a secure, efficient, and dynamically-created virtual network for connecting physician consoles and robotic-assisted medical systems. Disclosed approaches improve efficiency, security, scalability, and reliability of remote robotic-assisted medical procedures.

## Claims

### Claim 1

A robotic-assisted medical procedure system comprising:
a plurality of patient-side robotic procedure systems including a first patient-side robotic procedure system and a second patient-side robotic procedure system each comprising at least one of an instrument or an imaging system;
a plurality of robotic procedure consoles including a first robotic procedure console and a second robotic procedure console each configured to control a remotely located patient-side robotic procedure system of the plurality of patient-side robotic procedure systems; and
a non-transitory computer readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to:
provide a virtual network for connecting 1) the first robotic procedure console to the first patient-side robotic procedure system and 2) the second robotic procedure console to the second patient-side robotic procedure system, the virtual network utilizing a plurality of different and disparate physical networks that comprise a first physical network on which the first robotic procedure console is configured to reside, a second physical network on which the second robotic procedure console is configured to reside, a third physical network on which the first patient-side robotic procedure system is configured to reside, and a fourth physical network on which the second patient-side robotic procedure system is configured to reside;
authenticate the first and second robotic procedure consoles for the virtual network;
authenticate the first and second patient-side robotic procedure systems for the virtual network;
subsequent to authenticating the first robotic procedure console and the first patient-side robotic procedure system:
establish, over the virtual network, a first virtual network connection between the first robotic procedure console and the first patient-side robotic procedure system, the first virtual network connection utilizing the first physical network, the third physical network, and a backbone network; and
transmit, over the first virtual network connection, data between the first robotic procedure console and the first patient-side robotic procedure system to permit the first robotic procedure console to remotely control the first patient-side robotic procedure system to perform a first medical procedure; and
subsequent to authenticating the second robotic procedure console and the second patient-side robotic procedure system:
establish, over the virtual network, a second virtual network connection between the second robotic procedure console and the second patient-side robotic procedure system, the second virtual network connection utilizing the second physical network, the fourth physical network, and the backbone network; and
transmit, over the second virtual network connection, data between the second robotic procedure console and the second patient-side robotic procedure system to permit the second robotic procedure console to remotely control the second patient-side robotic procedure system to perform a second medical procedure, the second medical procedure overlapping in time with the first medical procedure,
wherein the first and second virtual network connections remain independent and separate despite sharing at least the backbone network.

### Claim 2 (depends on 1)

The robotic-assisted medical procedure system of claim 1, wherein the first and second virtual network connections provide routing functionality.

### Claim 3 (depends on 2)

The robotic-assisted medical procedure system of claim 2, wherein the plurality of patient-side robotic procedure systems further comprises a third patient-side robotic procedure system that is configured to reside on the first physical network on which the first robotic procedure console is configured to reside, and wherein the one or more processors are further caused to:
authenticate the third patient-side robotic procedure system for the virtual network; and
subsequent to authenticating the first robotic procedure console and the third patient-side robotic procedure system:
establish, over the virtual network, a virtual interconnect between the first robotic procedure console and the third patient-side robotic procedure system, wherein the virtual interconnect provides switching functionality and does not provide routing functionality; and
transmit, over the virtual interconnect, data between the first robotic procedure console and the third patient-side robotic procedure system to permit the first robotic procedure console to control the third patient-side robotic procedure system to perform a third medical procedure, wherein the third medical procedure does not overlap in time with the first medical procedure.

### Claim 4 (depends on 1)

The robotic-assisted medical procedure system of claim 1, wherein the first robotic procedure console utilizes a first IP address assigned to the first patient-side robotic procedure system to communicate with the first patient-side robotic procedure system, and wherein the first IP address is automatically encapsulated to facilitate communication with the first patient-side robotic procedure system over the first virtual network connection that traverses multiple local area networks.

### Claim 5 (depends on 4)

The robotic-assisted medical procedure system of claim 4, wherein the first IP address assigned to the first patient-side robotic procedure system is a first hard-coded IP address, and wherein the first hard-coded IP address of the first patient-side robotic procedure system overlaps with a hard-coded IP address of another patient-side robotic procedure system of the plurality of patient-side robotic procedure systems.

### Claim 6 (depends on 4)

The robotic-assisted medical procedure system of claim 4, wherein the first IP address is an address on a local area network designed to directly connect the first patient-side robotic procedure system to the first robotic procedure console.

### Claim 7 (depends on 4)

The robotic-assisted medical procedure system of claim 4, wherein:
the second robotic procedure console utilizes a second IP address assigned to the second patient-side robotic procedure system to communicate with the second patient-side robotic procedure system; and
the second IP address is automatically encapsulated to facilitate communication with the second patient-side robotic procedure system over the second virtual network connection that traverses multiple local area networks, wherein the second IP address is an address on a local area network designed to directly connect the second patient-side robotic procedure system to the second robotic procedure console.

### Claim 8

A non-transitory computer readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to:
provide a virtual network for connecting:
a first robotic procedure console of a plurality of robotic procedure consoles to a first patient-side robotic procedure system of a plurality of patient-side robotic procedure systems, the first patient-side robotic procedure system configured to be remotely located from the first robotic procedure console; and
a second robotic procedure console of the plurality of robotic procedure consoles to a second patient-side robotic procedure system of the plurality of patient-side robotic procedure systems, the second patient-side robotic procedure system configured to be remotely located from the second robotic procedure console,
the virtual network utilizing a plurality of different and disparate physical networks that comprise a first physical network on which the first robotic procedure console is configured to reside, a second physical network on which the second robotic procedure console is configured to reside, a third physical network on which the first patient-side robotic procedure system is configured to reside, and a fourth physical network on which the second patient-side robotic procedure system is configured to reside;
authenticate the first and second robotic procedure consoles for the virtual network;
authenticate the first and second patient-side robotic procedure systems for the virtual network;
subsequent to authenticating the first robotic procedure console and the first patient-side robotic procedure system:
establish, over the virtual network, a first virtual network connection between the first robotic procedure console and the first patient-side robotic procedure system, the first virtual network connection utilizing the first physical network, the third physical network, and a backbone network; and
transmit, over the first virtual network connection, data between the first robotic procedure console and the first patient-side robotic procedure system to permit the first robotic procedure console to remotely control the first patient-side robotic procedure system to perform a first medical procedure; and
subsequent to authenticating the second robotic procedure console and the second patient-side robotic procedure system:
establish, over the virtual network, a second virtual network connection between the second robotic procedure console and the second patient-side robotic procedure system, the second virtual network connection utilizing the second physical network, the fourth physical network, and the backbone network; and
transmit, over the second virtual network connection, data between the second robotic procedure console and the second patient-side robotic procedure system to permit the second robotic procedure console to remotely control the second patient-side robotic procedure system to perform a second medical procedure, the second medical procedure overlapping in time with the first medical procedure,
wherein the first and second virtual network connections remain independent and separate despite sharing at least the backbone network.

### Claim 9 (depends on 8)

The non-transitory computer readable medium of claim 8, wherein the first and second virtual network connections provide routing functionality.

### Claim 10 (depends on 9)

The non-transitory computer readable medium of claim 9, wherein the one or more processors are further caused to:
authenticate a third patient-side robotic procedure system for the virtual network, the third patient-side robotic procedure system configured to reside on the first physical network on which the first robotic procedure console is configured to reside; and
subsequent to authenticating the first robotic procedure console and the third patient-side robotic procedure system:
establish, over the virtual network, a virtual interconnect between the first robotic procedure console and the third patient-side robotic procedure system, wherein the virtual interconnect provides switching functionality and does not provide routing functionality; and
transmit, over the virtual interconnect, data between the first robotic procedure console and the third patient-side robotic procedure system to permit the first robotic procedure console to control the third patient-side robotic procedure system to perform a third medical procedure, wherein the third medical procedure does not overlap in time with the first medical procedure.

### Claim 11 (depends on 8)

The non-transitory computer readable medium of claim 8, wherein the first robotic procedure console utilizes a first IP address assigned to the first patient-side robotic procedure system to communicate with the first patient-side robotic procedure system, and wherein the first IP address is automatically encapsulated to facilitate communication with the first patient-side robotic procedure system over the first virtual network connection that traverses multiple local area networks.

### Claim 12 (depends on 11)

The non-transitory computer readable medium of claim 11, wherein the first IP address assigned to the first patient-side robotic procedure system is a first hard-coded IP address, and wherein the first hard-coded IP address of the first patient-side robotic procedure system overlaps with a hard-coded IP address of another patient-side robotic procedure system of the plurality of patient-side robotic procedure systems.

### Claim 13 (depends on 12)

The non-transitory computer readable medium of claim 12, wherein the first IP address is an address on a local area network designed to directly connect the first patient-side robotic procedure system to the first robotic procedure console.

### Claim 14 (depends on 11)

The non-transitory computer readable medium of claim 11, wherein:
the second robotic procedure console utilizes a second IP address assigned to the second patient-side robotic procedure system to communicate with the second patient-side robotic procedure system; and
the second IP address is automatically encapsulated to facilitate communication with the second patient-side robotic procedure system over the second virtual network connection that traverses multiple local area networks, wherein the second IP address is an address on a local area network designed to directly connect the second patient-side robotic procedure system to the second robotic procedure console.

### Claim 15

A robotic-assisted medical procedure system comprising:
a plurality of patient-side robotic procedure systems including a first patient-side robotic procedure system and a second patient-side robotic procedure system each comprising at least one of an instrument or an imaging system;
a robotic procedure console configured to control the plurality of patient-side robotic procedure systems located remotely from the robotic procedure console; and
a non-transitory computer readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to:
provide a virtual network for connecting the robotic procedure console to the first and second patient-side robotic procedure systems, the virtual network utilizing a plurality of different and disparate physical networks that comprise a first physical network on which the robotic procedure console is configured to reside and a second physical network on which the first and second patient-side robotic procedure systems are configured to reside;
authenticate the robotic procedure console for the virtual network;
authenticate the first and second patient-side robotic procedure systems for the virtual network;
subsequent to authenticating the robotic procedure console and at least the first patient-side robotic procedure system:
establish, over the virtual network, a first virtual network connection between the robotic procedure console and the first patient-side robotic procedure system;
transmit, over the first virtual network connection, data between the robotic procedure console and the first patient-side robotic procedure system to permit the robotic procedure console to remotely control the first patient-side robotic procedure system to perform a first medical procedure; and
terminate the first virtual network connection subsequent to completion of the first medical procedure; and
subsequent to completion of the first medical procedure:
establish, over the virtual network, a second virtual network connection between the robotic procedure console and the second patient-side robotic procedure system;
transmit, over the second virtual network connection, data between the robotic procedure console and the second patient-side robotic procedure system to permit the robotic procedure console to remotely control the second patient-side robotic procedure system to perform a second medical procedure; and
terminate the second virtual network connection subsequent to completion of the second medical procedure,
wherein each of the first and second virtual network connections remain independent and separate from any other temporally overlapping virtual network connection that shares at least one physical network with the first or second virtual network connection.

### Claim 16 (depends on 15)

The robotic-assisted medical procedure system of claim 15, wherein the first and second virtual network connections provide routing functionality.

### Claim 17 (depends on 16)

The robotic-assisted medical procedure system of claim 16, wherein the plurality of patient-side robotic procedure systems further comprises a third patient-side robotic procedure system that is configured to reside on the first physical network on which the robotic procedure console is configured to reside, and wherein the one or more processors are further caused to:
authenticate the third patient-side robotic procedure system for the virtual network; and
subsequent to authenticating the robotic procedure console and the third patient-side robotic procedure system:
establish, over the virtual network, a virtual interconnect between the robotic procedure console and the third patient-side robotic procedure system, wherein the virtual interconnect provides switching functionality and does not provide routing functionality;
transmit, over the virtual interconnect, data between the robotic procedure console and the third patient-side robotic procedure system to permit the robotic procedure console to control the third patient-side robotic procedure system to perform a third medical procedure, wherein the third medical procedure does not overlap in time with the first or second medical procedure; and
terminate the virtual interconnect subsequent to completion of the third medical procedure.

### Claim 18 (depends on 15)

The robotic-assisted medical procedure system of claim 15, wherein the robotic procedure console utilizes a first IP address assigned to the first patient-side robotic procedure system to communicate with the first patient-side robotic procedure system, and wherein the first IP address is automatically encapsulated to facilitate communication with the first patient-side robotic procedure system over the first virtual network connection that traverses multiple local area networks.

### Claim 19 (depends on 18)

The robotic-assisted medical procedure system of claim 18, wherein the first IP address assigned to the first patient-side robotic procedure system is a first hard-coded IP address, and wherein the first hard-coded IP address of the first patient-side robotic procedure system overlaps with a hard-coded IP address of another patient-side robotic procedure system of the plurality of patient-side robotic procedure systems.

### Claim 20 (depends on 18)

The robotic-assisted medical procedure system of claim 18, wherein the first IP address is an address on a local area network designed to directly connect the first patient-side robotic procedure system to the robotic procedure console.

### Claim 21 (depends on 18)

The robotic-assisted medical procedure system of claim 18, wherein:
the robotic procedure console utilizes a second IP address assigned to the second patient-side robotic procedure system to communicate with the second patient-side robotic procedure system; and
the second IP address is automatically encapsulated to facilitate communication with the second patient-side robotic procedure system over the second virtual network connection that traverses multiple local area networks, wherein the second IP address is an address on a local area network designed to directly connect the second patient-side robotic procedure system to the robotic procedure console.

### Claim 22 (depends on 15)

The robotic-assisted medical procedure system of claim 15, further comprising another robotic procedure console configured to be connected to the first patient-side robotic procedure system by one or more dedicated cables or a direct local area network (LAN) connection and a switching circuitry configured to be integrated with the first patient-side robotic procedure system, the switching circuitry further configured to:
cause the first patient-side robotic procedure system to operate in a first mode in which the first patient-side robotic procedure system and the another robotic procedure console connected to the first patient-side robotic procedure system by one or more dedicated cables or a direct local area network (LAN) connection exchange data to permit the another robotic procedure console to control the first patient-side robotic procedure system to perform the first medical procedure; and
cause the first patient-side robotic procedure system to operate in a second mode in which the first patient-side robotic procedure system and the robotic procedure console exchange data to permit the robotic procedure console to remotely control the first patient-side robotic procedure system to perform the first medical procedure;
responsive to a first signal, cause the first patient-side robotic procedure system to transition from operating in the first mode to operating in the second mode; and
responsive to a second signal, cause the first patient-side robotic procedure system to transition from operating in the second mode to operating in the first mode.

### Claim 23

A non-transitory computer readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to:
provide a virtual network for connecting a robotic procedure console to first and second patient-side robotic procedure systems of a plurality of patient-side robotic procedure systems, the virtual network utilizing a plurality of different and disparate physical networks that comprise a first physical network on which the robotic procedure console is configured to reside and a second physical network on which the first and second patient-side robotic procedure systems are configured to reside;
authenticate the robotic procedure console for the virtual network;
authenticate the first and second patient-side robotic procedure systems for the virtual network;
subsequent to authenticating the robotic procedure console and at least the first patient-side robotic procedure system:
establish, over the virtual network, a first virtual network connection between the robotic procedure console and the first patient-side robotic procedure system;
transmit, over the first virtual network connection, data between the robotic procedure console and the first patient-side robotic procedure system to permit the robotic procedure console to remotely control the first patient-side robotic procedure system to perform a first medical procedure; and
terminate the first virtual network connection subsequent to completion of the first medical procedure; and
subsequent to completion of the first medical procedure:
establish, over the virtual network, a second virtual network connection between the robotic procedure console and the second patient-side robotic procedure system;
transmit, over the second virtual network connection, data between the robotic procedure console and the second patient-side robotic procedure system to permit the robotic procedure console to remotely control the second patient-side robotic procedure system to perform a second medical procedure; and
terminate the second virtual network connection subsequent to completion of the second medical procedure,
wherein each of the first and second virtual network connections remain independent and separate from any other temporally overlapping virtual network connection that shares at least one physical network with the first or second virtual network connection.