Medical tele-robotic system with a master remote station with an arbitrator

Abstract

A robotic system that includes a mobile robot linked to a plurality of remote stations. One of the remote stations includes an arbitrator that controls access to the robot. Each remote station may be assigned a priority that is used by the arbitrator to determine which station has access to the robot. The arbitrator may include notification and call back mechanisms for sending messages relating to an access request and a granting of access for a remote station.

Description

BACKGROUND OF THE INVENTION

1. Field of the Invention

The subject matter disclosed generally relates to the field of robotics.

2. Background Information

There is a growing need to provide remote health care to patients that have a variety of ailments ranging from Alzheimers to stress disorders. To minimize costs it is desirable to provide home care for such patients. Home care typically requires a periodic visit by a health care provider such as a nurse or some type of assistant. Due to financial and/or staffing issues the health care provider may not be there when the patient needs some type of assistance. Additionally, existing staff must be continuously trained, which can create a burden on training personnel. It would be desirable to provide a system that would allow a health care provider to remotely care for a patient without being physically present.

Robots have been used in a variety of applications ranging from remote control of hazardous material to assisting in the performance of surgery. For example, U.S. Pat. No. 5,762,458 issued to Wang et al. discloses a system that allows a surgeon to perform minimally invasive medical procedures through the use of robotically controlled instruments. One of the robotic arms in the Wang system moves an endoscope which has a camera that allows a surgeon to view a surgical area of a patient.

Tele-robots such as hazardous waste handlers and bomb detectors may contain a camera that allows the operator to view the remote site. Canadian Pat. No. 2289697 issued to Treviranus, et al. discloses a teleconferencing platform that has both a camera and a monitor. The platform includes mechanisms to both pivot and raise the camera and monitor. The teleconferencing platform disclosed in the Canadian patent is stationary and cannot move about a building.

Publication Application No. US-2003-0050233-A1 discloses a remote robotic system wherein a plurality of remote stations can control a plurality of robotic arms used to perform a minimally invasive medical procedure. Each remote station can receive a video image provided by the endo scope inserted into the patient. The remote stations are linked to the robotic system by a dedicated communication link.

BRIEF SUMMARY OF THE INVENTION

A robotic system that includes a mobile robot coupled to a first remote station and a second remote station. The second remote station includes an arbitrator that controls access to the robot. The robot includes a camera and a monitor.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an illustration of a robotic system;

FIG. 2 is a schematic of an electrical system of a robot;

FIG. 3 is a further schematic of the electrical system of the robot;

FIG. 4 is side view of the robot;

FIG. 5 is a top perspective view of a holonomic platform of the robot;

FIG. 6 is a side perspective view of a roller assembly of the holonomic platform;

FIG. 7 is a bottom perspective view showing a pedestal assembly of the robot;

FIG. 8 is a sectional view showing an actuator of the pedestal assembly;

FIG. 9 is a schematic of a robotic system wherein multiple remote stations are coupled to the robot;

FIG. 10 is a flowchart showing an arbitration scheme for allowing access to the robot;

FIG. 11 is a side view of a robot head.

DETAILED DESCRIPTION

Disclosed is a robotic system that includes a mobile robot linked to a plurality of remote stations. One of the remote stations includes an arbitrator that controls access to the robot. Each remote station may be assigned a priority that is used by the arbitrator to determine which station has access to the robot. The arbitrator may include notification and call back mechanisms for sending messages relating to an access request and a granting of access for a remote station.

Referring to the drawings more particularly by reference numbers, FIG. 1 shows a robotic system 10. The robotic system 10 includes a robot 12, a base station 14 and a plurality of remote control stations 16. Each remote control station 16 may be coupled to the base station 14 through a network 18. By way of example, the network 18 may be either a packet switched network such as the Internet, or a circuit switched network such has a Public Switched Telephone Network (PSTN) or other broadband system. The base station 14 may be coupled to the network 18 by a modem 20 or other broadband network interface device.

Each remote control station 16 may include a computer 22 that has a monitor 24, a camera 26, a microphone 28 and a speaker 30. The computer 22 may also contain an input device 32 such as a joystick or a mouse. Each control station 16 is typically located in a place that is remote from the robot 12. Although only one robot 12 is shown, it is to be understood that the system 10 may have a plurality of robots 12. In general any number of robots 12 may be controlled by any number of remote stations. For example, one remote station 16 may be coupled to a plurality of robots 12, or one robot 12 may be coupled to a plurality of remote stations 16.

The robot 12 includes a movement platform 34 that is attached to a robot housing 36. Also attached to the robot housing 36 are a camera 38, a monitor 40, a microphone(s) 42 and a speaker 44. The microphone 42 and speaker 30 may create a stereophonic sound. The robot 12 may also have an antenna 45 that is wirelessly coupled to an antenna 46 of the base station 14. The system 10 allows a user at the remote control station 16 to move the robot 12 through the input device 32. The robot camera 38 is coupled to the remote monitor 24 so that a user at the remote station 16 can view a patient. Likewise, the robot monitor 40 is coupled to the remote camera 26 so that the patient can view the user. The microphones 28 and 42, and speakers 30 and 44, allow for audible communication between the patient and the user. The robot 12 may further have a handle 48 that can be rotated to a down position which allows someone to manually push or pull the robot 12.

Each remote station computer 22 may operate Microsoft OS software and WINDOWS XP or other operating systems such as LINUX. The remote computer 22 may also operate a video driver, a camera driver, an audio driver and a joystick driver. The video images may be transmitted and received with compression software such as MPEG CODEC.

FIGS. 2 and 3 show an embodiment of the robot 12. The robot 12 may include a high level control system 50 and a low level control system 52. The high level control system 50 may include a processor 54 that is connected to a bus 56. The bus is coupled to the camera 38 by an input/output (I/O) port 58, and to the monitor 40 by a serial output port 60 and a VGA driver 62. The monitor 40 may include a touchscreen function that allows the patient to enter input by touching the monitor screen.

The speaker 44 is coupled to the bus 56 by a digital to analog converter 64. The microphone 42 is coupled to the bus 56 by an analog to digital converter 66. The high level controller 50 may also contain random access memory (RAM) device 68, a non-volatile RAM device 70 and a mass storage device 72 that are all coupled to the bus 62. The mass storage device 72 may contain medical files of the patient that can be accessed by the user at the remote control station 16. For example, the mass storage device 72 may contain a picture of the patient. The user, particularly a health care provider, can recall the old picture and make a side by side comparison on the monitor 24 with a present video image of the patient provided by the camera 38. The robot antennae 45 may be coupled to a wireless transceiver 74. By way of example, the transceiver 74 may transmit and receive information in accordance with IEEE 802.11b.

The controller 54 may operate with a LINUX OS operating system. The controller 54 may also operate MS WINDOWS along with video, camera and audio drivers for communication with the remote control station 16. Video information may be transceived using MPEG CODEC compression techniques. The software may allow the user to send e-mail to the patient and vice versa, or allow the patient to access the Internet. In general the high level controller 50 operates to control the communication between the robot 12 and the remote control station 16.

The high level controller 50 may be linked to the low level controller 52 by serial ports 76 and 78. The low level controller 52 includes a processor 80 that is coupled to a RAM device 82 and non-volatile RAM device 84 by a bus 86. The robot 12 contains a plurality of motors 88 and motor encoders 90. The encoders 90 provide feedback information regarding the output of the motors 88. The motors 88 can be coupled to the bus 86 by a digital to analog converter 92 and a driver amplifier 94. The encoders 90 can be coupled to the bus 86 by a decoder 96. The robot 12 also has a number of proximity sensors 98 (see also FIG. 1). The position sensors 98 can be coupled to the bus 86 by a signal conditioning circuit 100 and an analog to digital converter 102.

The low level controller 52 runs software routines that mechanically actuate the robot 12. For example, the low level controller 52 provides instructions to actuate the movement platform to move the robot 12. The low level controller 52 may receive movement instructions from the high level controller 50. The movement instructions may be received as movement commands from the remote control station. Although two controllers are shown, it is to be understood that the robot 12 may have one controller controlling the high and low level functions.

The various electrical devices of the robot 12 may be powered by a battery(ies) 104. The battery 104 may be recharged by a battery recharger station 106 (see also FIG. 1). The low level controller 52 may include a battery control circuit 108 that senses the power level of the battery 104. The low level controller 52 can sense when the power falls below a threshold and then send a message to the high level controller 50. The high level controller 50 may include a power management software routine that causes the robot 12 to move so that the battery 104 is coupled to the recharger 106 when the battery power falls below a threshold value. Alternatively, the user can direct the robot 12 to the battery recharger 106. Additionally, the battery 104 may be replaced or the robot 12 may be coupled to a wall power outlet by an electrical cord (not shown).

FIG. 4 shows an embodiment of the robot 12. The robot 12 may include a holonomic platform 110 that is attached to a robot housing 112. The holonomic platform 110 provides three degrees of freedom to allow the robot 12 to move in any direction.

The robot 12 may have an pedestal assembly 114 that supports the camera 38 and the monitor 40. The pedestal assembly 114 may have two degrees of freedom so that the camera 26 and monitor 24 can be swiveled and pivoted as indicated by the arrows.

As shown in FIG. 5 the holonomic platform 110 may include three roller assemblies 120 that are mounted to a base plate 121. The roller assemblies 120 are typically equally spaced about the platform 110 and allow for movement in any direction, although it is to be understood that the assemblies may not be equally spaced.

The robot housing 112 may include a bumper 122. The bumper 122 may be coupled to optical position sensors 123 that detect when the bumper 122 has engaged an object. After engagement with the object the robot can determine the direction of contact and prevent further movement into the object.

FIG. 6 shows an embodiment of a roller assembly 120. Each assembly 120 may include a drive ball 124 that is driven by a pair of transmission rollers 126. The assembly 120 may include a retainer ring 128 and a plurality of bushings 130 that captures and allows the ball 124 to rotate in an x and y direction but prevents movement in a z direction. The assembly also holds the ball under the transmission rollers 126.

The transmission rollers 126 are coupled to a motor assembly 132. The assembly 132 corresponds to the motor 88 shown in FIG. 3. The motor assembly 132 includes an output pulley 134 attached to a motor 136. The output pulley 134 is coupled to a pair of ball pulleys 138 by a drive belt 140. The ball pulleys 138 are each attached to a transmission bracket 142. The transmission rollers 126 are attached to the transmission brackets 142.

Rotation of the output pulley 134 rotates the ball pulleys 138. Rotation of the ball pulleys 138 causes the transmission rollers 126 to rotate and spin the ball 124 through frictional forces. Spinning the ball 124 will move the robot 12. The transmission rollers 126 are constructed to always be in contact with the drive ball 124. The brackets 142 allow the transmission rollers 126 to freely spin and allow orthogonal directional passive movement of 124 when one of the other roller assemblies 120 is driving and moving the robot 12.

As shown in FIG. 7, the pedestal assembly 114 may include a motor 150 that is coupled to a gear 152 by a belt 154. The gear 152 is attached to a shaft 156. The shaft 156 is attached to an arm 158 that is coupled to the camera 38 and monitor 40 by a bracket 160. Activation of the motor 150 rotates the gear 152 and sleeve 156, and causes the camera 38 and monitor 40 to swivel (see also FIG. 4) as indicated by the arrows 4.

As shown in FIG. 8, the assembly 114 may further include a tilt motor 162 within the arm 158 that can cause the monitor 40 and camera 38 to pivot as indicated by the arrows 5. The tilt motor 162 may rotate a worm 164 that rotates a worm gear 166. The pin 168 is rigidly attached to both the worm gear 166 and the bracket 160 so that rotation of the gear 166 pivots the camera 38 and the monitor 40. The camera 38 may also include a zoom feature to provide yet another degree of freedom for the operator.

In operation, the robot 12 may be placed in a home or a facility where one or more patients are to be monitored and/or assisted. The facility may be a hospital or a residential care facility. By way of example, the robot 12 may be placed in a home where a health care provider may monitor and/or assist the patient. Likewise, a friend or family member may communicate with the patient. The cameras and monitors at both the robot and remote control stations allow for teleconferencing between the patient and the person at the remote station(s).

The robot 12 can be maneuvered through the home or facility by manipulating the input device 32 at a remote station 16.

FIG. 9 shows a plurality of remote stations 16A-C that can access a robot 12 through a network 18. One of the remote stations 12B can be designated a master station which contains an arbitrator 250. The remote stations 16 may be configured so that all messages, commands, etc. provided to the robot 12 are initially routed to the master remote station 16B. Each message packet may include a priority field that contains the priority number of the station 16A, 16B or 16C sending the message. The arbitrator 250 determines which station has priority and then forwards the message from that station 16A, 16B or 16C to the robot 12. The arbitrator 250 may also send a call back message to the other remote station(s) stating that the station(s) with lower priority does not have access to the robot 12. The arbitrator 250 can cut-off access to the robot from one station and provide access to another station with a higher priority number.

Alternatively, a remote station may route a message, command, etc. to the robot 12 which then forwards a message, command, etc. to the arbitrator 250 to determine whether the station should have access. The arbitrator 250 can then provide a reply message either granting or denying access to the robot.

FIG. 10 shows a flowchart describing a process for access the robot 12. A remote station 16A, 16B or 16C may generate a request message to access the robot in block 300. The message may include the priority number of the remote station. The arbitrator 250 determines whether the request includes a priority number higher than any existing priority number in decision block 302. If a remote station has the same priority number the station first in time maintains access to the robot.

If the request included the highest priority number the arbitrator allows access to the robot in block 304. If the request does not contain the highest priority number, then arbitrator 250 sends a call-back message in block 306. To establish priority, the users may be divided into classes that include the robot itself, a local user, a caregiver, a doctor, a family member, or a service provider. The robot 12 may override input commands that conflict with robot operation. For example, if the robot runs into a wall, the system may ignore all additional commands to continue in the direction of the wall. A local user is a person who is physically present with the robot. The robot could have an input device that allows local operation. For example, the robot may incorporate a voice recognition system that receives and interprets audible commands.

A caregiver is someone who remotely monitors the patient. A doctor is a medical professional who can remotely control the robot and also access medical files contained in the robot memory. The family and service users remotely access the robot. The service user may service the system such as by upgrading software, or setting operational parameters.

Message packets may be transmitted between a robot 12 and a remote station 16. The packets provide commands and feedback. Each packet may have multiple fields. By way of example, a packet may include an ID field a forward speed field, an angular speed field, a stop field, a bumper field, a sensor range field, a configuration field, a text field and a debug field.

The identification of remote users can be set in an ID field of the information that is transmitted from the remote control station 16 to the robot 12. For example, a user may enter a user ID into a setup table in the application software run by the remote control station 16. The user ID is then sent with each message transmitted to the robot.

The robot 12 may operate in one of two different modes; an exclusive mode, or a sharing mode. In the exclusive mode only one user has access control of the robot. The exclusive mode may have a priority assigned to each type of user. By way of example, the priority may be in order of local, doctor, caregiver, family and then service user. In the sharing mode two or more users may share access with the robot. For example, a caregiver may have access to the robot, the caregiver may then enter the sharing mode to allow a doctor to also access the robot. Both the caregiver and the doctor can conduct a simultaneous tele-conference with the patient.

The arbitrator may have one of four mechanisms; notification, timeouts, queue and call back. The notification mechanism may inform either a present user or a requesting user that another user has, or wants, access to the robot. The timeout mechanism gives certain types of users a prescribed amount of time to finish access to the robot. The queue mechanism is an orderly waiting list for access to the robot. The call back mechanism informs a user that the robot can be accessed. By way of example, a family user may receive an e-mail message that the robot is free for usage. Tables 1 and 2, show how the mechanisms resolve access request from the various users.

TABLE I
	Access	Medical	Command	Software/Debug	Set
User	Control	Record	Override	Access	Priority
Robot	No	No	Yes (1)	No	No
Local	No	No	Yes (2)	No	No
Caregiver	Yes	Yes	Yes (3)	No	No
Doctor	No	Yes	No	No	No
Family	No	No	No	No	No
Service	Yes	No	Yes	Yes	Yes

	TABLE II
	Requesting User
	Local	Caregiver	Doctor	Family	Service
Current	Local	Not Allowed	Warn current user of	Warn current user of	Warn current user of	Warn current user of
User			pending user	pending user	pending user	pending user
			Notify requesting	Notify requesting user	Notify requesting user	Notify requesting
			user that system is in	that system is in use	that system is in use	user that system is in
			use	Set timeout = 5 m	Set timeout = 5 m	use
			Set timeout		Call back	No timeout
						Call back
	Caregiver	Warn current user	Not Allowed	Warn current user of	Warn current user of	Warn current user of
		of pending user.		pending user	pending user	pending user
		Notify requesting		Notify requesting user	Notify requesting user	Notify requesting
		user that system is		that system is in use	that system is in use	user that system is in
		in use.		Set timeout = 5 m	Set timeout = 5 m	use
		Release control		Queue or callback		No timeout
						Callback
	Doctor	Warn current user	Warn current user of	Warn current user of	Notify requesting user	Warn current user of
		of pending user	pending user	pending user	that system is in use	pending user
		Notify requesting	Notify requesting	Notify requesting user	No timeout	Notify requesting
		user that system is	user that system is in	that system is in use	Queue or callback	user that system is in
		in use	use	No timeout		use
		Release control	Set timeout = 5 m	Callback		No timeout
						Callback
	Family	Warn current user	Notify requesting	Warn current user of	Warn current user of	Warn current user of
		of pending user	user that system is in	pending user	pending user	pending user
		Notify requesting	use	Notify requesting user	Notify requesting user	Notify requesting
		user that system is	No timeout	that system is in use	that system is in use	user that system is in
		in use	Put in queue or	Set timeout = 1 m	Set timeout = 5 m	use
		Release Control	callback		Queue or callback	No timeout
						Callback
	Service	Warn current user	Notify requesting	Warn current user of	Warn current user of	Not Allowed
		of pending user	user that system is in	request	pending user
		Notify requesting	use	Notify requesting user	Notify requesting user
		user that system is	No timeout	that system is in use	that system is in use
		in use	Callback	No timeout	No timeout
		No timeout		Callback	Queue or callback

The information transmitted between the station 16 and the robot 12 may be encrypted. Additionally, the user may have to enter a password to enter the system 10. A selected robot is then given an electronic key by the station 16. The robot 12 validates the key and returns another key to the station 16. The keys are used to encrypt information transmitted in the session.

FIG. 11 shows a robot head 350 that can both pivot and spin the camera 38 and the monitor 40. The robot head 350 can be similar to the robot 12 but without the platform 110. The robot head 350 may have the same mechanisms and parts to both pivot the camera 38 and monitor 40 about the pivot axis 4, and spin the camera 38 and monitor 40 about the spin axis 5. The pivot axis may intersect the spin axis. Having a robot head 350 that both pivots and spins provides a wide viewing area. The robot head 350 may be in the system either with or instead of the mobile robot 12.

While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of and not restrictive on the broad invention, and that this invention not be limited to the specific constructions and arrangements shown and described, since various other modifications may occur to those ordinarily skilled in the art.

For example, although the arbitrator is described and shown as being in one of the remote stations, the arbitrator could be within a server, robot or any device, that is connected to the network and in communication with both the remote stations and the robot.

Claims

1. A robotic teleconferencing system, comprising: a first teleconferencing device and a second teleconferencing device that each have a camera that can generate an image and be remotely controlled in at least three degrees of freedom, a monitor, a speaker, and a microphone that can generate audio;a first remote station that can access said first and second teleconferencing devices, said first remote station including a camera, a monitor that can receive said image from said first or second teleconferencing devices, a microphone and a speaker that can produce audio provided by said first or second teleconferencing devices;a second remote station that can access said first and second teleconferencing devices, said second remote station including a camera, a monitor that can receive said image from said first and second teleconferencing devices, a microphone and a speaker that can produce audio provided by said first and second teleconferencing devices; and,a server coupled to said first and second teleconferencing devices and said first and second remote stations, said server allows exclusive access to said first teleconferencing device by said first remote station wherein said image and audio from said first teleconferencing device is provided to said first remote station and said image and audio are not provided to said second remote station and even though said second remote station is prevented from accessing said first teleconferencing device said server allows said second remote station to access said second teleconferencing device.

2. The system of claim 1, wherein said server includes a notification mechanism.

3. The system of claim 1, wherein said server includes a timeout mechanism.

4. The system of claim 1, wherein said server includes a queue mechanism.

5. The system of claim 1, wherein said server includes a call back mechanism.

6. The system of claim 1, wherein said first and second remote stations each have a priority and said server provides teleconferencinq device access to said remote station with a highest priority.

7. The system of claim 6, wherein said remote stations are given priority as a local user, a doctor, a caregiver, a family member, a service user or another teleconferencing device.

8. A method for controlling access to a plurality of teleconferencing devices, comprising: providing a first teleconferencing device and a second teleconferencing device that each have a monitor, a camera that can generate an image, a speaker and a microphone that can generate audio;providing a plurality of remote stations, including a first remote station and a second remote station, each remote station including a camera, a monitor that can receive the image from the first or second teleconferencing devices, a microphone and a speaker that can produce audio provided by the first or second teleconferencinq devices;transmitting a request to access the first teleconferencing device from the first remote station; transmitting a request to access the first teleconferencing device from the second remote station;allowing exclusive access to the first teleconferencinq device by the first remote station wherein the image and audio from the first teleconferencing device is provided to the first remote station and the image and audio are not provided to the second remote station;transmitting a request to access the second teleconferencing device from the second remote station; and,accessing the second teleconferencinq device by the second remote station.

9. The method of claim 8, further comprising receiving a request to access the first teleconferencing device from the second remote station and notifying the first remote station of the request.

10. The method of claim 8, further comprising creating a time interval in which the first remote station must relinquish access to the first teleconferencing device.

11. The method of claim 8, wherein the request from the second remote station is placed in a waiting list queue.

12. The method of claim 8, further comprising transmitting a call back message to the second remote station to indicate the granting of access to the first teleconferencinq device.

13. The method of claim 8, wherein the access request includes a priority that is evaluated to determine access to the first teleconferencing device.

14. The method of claim 13, wherein the remote stations are given priority as a local user, a doctor, a caregiver, a family member, a service user or another teleconferencing device.

15. The method of claim 8, wherein the second teleconferencinq device operates in either an exclusive mode or a sharing mode.

16. The method of claim 8, wherein the second remote station's request to access the first teleconferencinq device is initially transmitted to a server.

17. The method of claim 8, wherein the second remote station's request to access the first teleconferencinq device is initially transmitted to the first teleconferencinq device.