Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20040162637 A1
Publication typeApplication
Application numberUS 10/783,760
Publication dateAug 19, 2004
Filing dateFeb 20, 2004
Priority dateJul 25, 2002
Also published asUS8515577, US8682486, US20080065268, US20130304257, US20140156069
Publication number10783760, 783760, US 2004/0162637 A1, US 2004/162637 A1, US 20040162637 A1, US 20040162637A1, US 2004162637 A1, US 2004162637A1, US-A1-20040162637, US-A1-2004162637, US2004/0162637A1, US2004/162637A1, US20040162637 A1, US20040162637A1, US2004162637 A1, US2004162637A1
InventorsYulun Wang, Charles Jordan, Keith Laby, Jonathan Southard
Original AssigneeYulun Wang, Jordan Charles S., Laby Keith Phillip, Jonathan Southard
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Medical tele-robotic system with a master remote station with an arbitrator
US 20040162637 A1
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.
Images(11)
Previous page
Next page
Claims(60)
What is claimed is:
1. A robot system, comprising:
a mobile robot that has a camera and a monitor;
a first remote station that can access said mobile robot; and,
a second remote station that includes an arbitrator that can control access to said mobile robot by said first and second remote stations.
2. The system of claim 1, wherein said arbitrator includes a notification mechanism.
3. The system of claim 1, wherein said arbitrator includes a timeout mechanism.
4. The system of claim 1, wherein said arbitrator includes a queue mechanism.
5. The system of claim 1, wherein said arbitrator includes a call back mechanism.
6. The system of claim 1, wherein said second remote station can access said mobile robot, and said first and second remote stations each have a priority and said arbitrator provides robot access to said remote station with a highest priority.
7. The system of claim 6, wherein said remote stations may be given priority as a local user, a doctor, a caregiver, a family member, a service user or another mobile robot.
8. The system of claim 1, wherein said mobile robot operates in either an exclusive mode or a sharing mode.
9. The system of claim 1, wherein said first remote station transmits a communication for said mobile robot that is initially transmitted to said second remote station.
10. The system of claim 1, wherein said first remote station sends a communication for said mobile robot that is initially transmitted to said mobile robot.
11. A robot system, comprising:
a mobile robot that has a camera and a monitor;
a first remote station that can access said mobile robot; and,
a second remote station that includes arbitration means for controlling access to said mobile robot by said first and second remote stations.
12. The system of claim 11, wherein said arbitrator means includes notification means for notifying said first remote station that said second remote station is requesting access to said mobile robot.
13. The system of claim 11, wherein said arbitrator means includes timeout means that creates a time interval in which one of said remote stations must relinquish access to said mobile robot.
14. The system of claim 11, wherein said arbitrator means includes queue means for establishing a waiting list of remote stations seeking access to said mobile robot.
15. The system of claim 11, wherein said arbitrator means includes call back means for providing a message to one of said remote stations that said mobile robot can be accessed.
16. The system of claim 11, wherein said second remote station can access said mobile robot, and said first and second remote stations each have a priority and said arbitrator means provides robot access to said remote station with a highest priority.
17. The system of claim 16, wherein said remote stations may be given priority as a local user, a doctor, a caregiver, a family member, a service user or another mobile robot.
18. The system of claim 11, wherein said mobile robot operates in either an exclusive mode or a sharing mode.
19. The system of claim 11, wherein said first remote station transmits a communication for said mobile robot that is initially transmitted to said second remote station.
20. The system of claim 11, wherein said first remote station sends a communication for said mobile robot that is initially transmitted to said mobile robot.
21. A method for controlling access to a remote controlled robot, comprising:
transmitting a request to access a mobile robot from a first remote station;
determining whether the first remote station should have access to the mobile robot at a second remote station;
allowing access to the mobile robot; and,
transmitting video images between the robot and the first remote station.
22. The method of claim 21, further comprising requesting access to the mobile robot from the second remote station and notifying the first remote station of the request.
23. The method of claim 22, wherein the second remote station creates a time interval in which the first remote station must relinquish access to the mobile robot.
24. The method of claim 22, wherein the request from the second remote station is placed in a waiting list queue.
25. The method of claim 21, further comprising transmitting a call back message from the second remote station to the first remote station to indicate the granting of access to the mobile robot.
26. The method of claim 21, wherein the access request includes a priority that is evaluated by the second remote station to determine access to the mobile robot.
27. The method of claim 26, wherein the remote stations may be given priority as a local user, a doctor, a caregiver, a family member, a service user or another mobile robot.
28. The method of claim 25, wherein the mobile robot operates in either an exclusive mode or a sharing mode.
29. The method of claim 25, wherein the access request is initially transmitted to the second remote station.
30. The method of claim 25, wherein the access request is initially transmitted to the mobile robot.
31. A robot system, comprising:
a broadband network;
a mobile robot that is coupled to said broadband network, and has a camera and a monitor;
a first remote station that can access said mobile robot through said broadband network; and,
a second remote station that includes an arbitrator that can control access to said mobile robot by said first and second remote stations.
32. The system of claim 31, wherein said arbitrator includes a notification mechanism.
33. The system of claim 31, wherein said arbitrator includes a timeout mechanism.
34. The system of claim 31, wherein said arbitrator includes a queue mechanism.
35. The system of claim 31, wherein said arbitrator includes a call back mechanism.
36. The system of claim 31, wherein said second remote station can access said mobile robot, and said first and second remote stations each have a priority and said arbitrator provides robot access to said remote station with a highest priority.
37. The system of claim 36, wherein said remote stations may be given priority as a local user, a doctor, a caregiver, a family member, a service user or another mobile robot.
38. The system of claim 31, wherein said mobile robot operates in either an exclusive mode or a sharing mode.
39. The system of claim 31, wherein said first remote station transmits a communication for the mobile robot that is initially transmitted to said second remote station.
40. The system of claim 31, wherein said first remote station sends a communication for said mobile robot that is initially transmitted to said mobile robot.
41. A robot system, comprising:
a broadband network;
a mobile robot that is coupled to said broadband network, and has a camera and a monitor;
a first remote station that can access said mobile robot through said broadband network; and,
a second remote station that includes arbitration means for controlling access to said robot by said first and second remote stations.
42. The system of claim 41, wherein said arbitrator means includes notification means for notifying said first remote station that said second remote station is requesting access to said mobile robot.
43. The system of claim 41, wherein said arbitrator means includes timeout means that creates a time interval in which one of said remote stations must relinquish access to said mobile robot.
44. The system of claim 41, wherein said arbitrator means includes queue means for establishing waiting list of remote stations seeking access to said mobile robot.
45. The system of claim 41, wherein said arbitrator means includes call back means for providing a message to one of said remote stations that said mobile robot can be accessed.
46. The system of claim 41, wherein said second remote station can access said mobile robot, and said first and second remote stations each have a priority and said arbitrator means provides robot access to said remote station with a highest priority.
47. The system of claim 46, wherein said remote stations may be given priority as a local user, a doctor, a caregiver, a family member, a service user or another mobile robot.
48. The system of claim 41, wherein said mobile robot operates in either an exclusive mode or a sharing mode.
49. The system of claim 41, wherein said first remote station transmits a communication for said mobile robot that is initially transmitted to said second remote station.
50. The system of claim 41, wherein said first remote station sends a communication for said mobile robot that is initially transmitted to said mobile robot.
51. A method for controlling access to a remote controlled robot, comprising:
transmitting a request to access a mobile robot from a first remote station through a broadband network;
determining whether the first remote station should have access to the mobile robot at a second remote station;
allowing access to the mobile robot through the broadband network; and,
transmitting video images between the robot and the first remote station between the broadband network.
52. The method of claim 51, further comprising requesting access to the mobile robot from the second remote station and notifying the first remote station of the request.
53. The method of claim 52, wherein the second remote station creates a time interval in which the first remote station must relinquish access to the mobile robot.
54. The method of claim 52, wherein the request from the second remote station is placed in a waiting list queue.
55. The method of claim 51, further comprising transmitting a call back message from the second remote station to the first remote station to indicate the granting of access to the mobile robot.
56. The method of claim 51, wherein the access request includes a priority that is evaluated by the second remote station to determine access to the mobile robot.
57. The method of claim 56, wherein the remote stations may be given priority as a local user, a doctor, a caregiver, a family member, a service user or another mobile robot.
58. The method of claim 51, wherein the mobile robot operates in either an exclusive mode or a sharing mode.
59. The method of claim 51, wherein the access request is initially transmitted to the second remote station.
60. The method of claim 51, wherein the access request is initially transmitted to the mobile robot.
Description
    REFERENCE TO CROSS-RELATED APPLICATIONS
  • [0001]
    This application is a continuation-in-part of U.S. patent application Ser. No. 10/206,457 filed on Jul. 25, 2002, pending, and claims priority to Provisional Application No.60/449,762 filed on Feb. 24, 2003.
  • BACKGROUND OF THE INVENTION
  • [0002]
    1. Field of the Invention
  • [0003]
    The subject matter disclosed generally relates to the field of robotics.
  • [0004]
    2. Background Information
  • [0005]
    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.
  • [0006]
    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.
  • [0007]
    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.
  • [0008]
    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 endoscope inserted into the patient. The remote stations are linked to the robotic system by a dedicated communication link.
  • BRIEF SUMMARY OF THE INVENTION
  • [0009]
    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
  • [0010]
    [0010]FIG. 1 is an illustration of a robotic system;
  • [0011]
    [0011]FIG. 2 is a schematic of an electrical system of a robot;
  • [0012]
    [0012]FIG. 3 is a further schematic of the electrical system of the robot;
  • [0013]
    [0013]FIG. 4 is side view of the robot;
  • [0014]
    [0014]FIG. 5 is a top perspective view of a holonomic platform of the robot;
  • [0015]
    [0015]FIG. 6 is a side perspective view of a roller assembly of the holonomic platform;
  • [0016]
    [0016]FIG. 7 is a bottom perspective view showing a pedestal assembly of the robot;
  • [0017]
    [0017]FIG. 8 is a sectional view showing an actuator of the pedestal assembly;
  • [0018]
    [0018]FIG. 9 is a schematic of a robotic system wherein multiple remote stations are coupled to the robot;
  • [0019]
    [0019]FIG. 10 is a flowchart showing an arbitration scheme for allowing access to the robot;
  • [0020]
    [0020]FIG. 11 is a side view of a robot head.
  • DETAILED DESCRIPTION
  • [0021]
    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.
  • [0022]
    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.
  • [0023]
    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.
  • [0024]
    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.
  • [0025]
    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.
  • [0026]
    [0026]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.
  • [0027]
    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.
  • [0028]
    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.
  • [0029]
    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.
  • [0030]
    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.
  • [0031]
    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).
  • [0032]
    [0032]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.
  • [0033]
    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.
  • [0034]
    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.
  • [0035]
    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.
  • [0036]
    [0036]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.
  • [0037]
    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.
  • [0038]
    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.
  • [0039]
    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.
  • [0040]
    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.
  • [0041]
    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).
  • [0042]
    The robot 12 can be maneuvered through the home or facility by manipulating the input device 32 at a remote station 16.
  • [0043]
    [0043]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.
  • [0044]
    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.
  • [0045]
    [0045]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.
  • [0046]
    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.
  • [0047]
    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.
  • [0048]
    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.
  • [0049]
    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.
  • [0050]
    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 teleconference with the patient.
  • [0051]
    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
  • [0052]
    [0052]
    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
    use Set timeout = 5 m Set timeout = 5 m is in 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
    in use. Set timeout = 5 m Set timeout = 5 m is in 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
    in use use No timeout is in 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
    in use Put in queue or Set timeout = 1 m Set timeout = 5 m is in 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
  • [0053]
    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.
  • [0054]
    [0054]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.
  • [0055]
    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.
  • [0056]
    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.
Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
US4709265 *Oct 15, 1985Nov 24, 1987Advanced Resource Development CorporationRemote control mobile surveillance system
US4803625 *Jun 30, 1986Feb 7, 1989Buddy Systems, Inc.Personal health monitor
US4977971 *May 17, 1989Dec 18, 1990University Of FloridaHybrid robotic vehicle
US5084828 *Sep 29, 1989Jan 28, 1992Healthtech Services Corp.Interactive medication delivery system
US5130794 *Mar 29, 1990Jul 14, 1992Ritchey Kurtis JPanoramic display system
US5341242 *May 4, 1992Aug 23, 1994Elbit Ltd.Helmet mounted display
US5441047 *May 25, 1993Aug 15, 1995David; DanielAmbulatory patient health monitoring techniques utilizing interactive visual communication
US5442728 *Sep 22, 1993Aug 15, 1995Healthtech Services Corp.Interactive patient assistance device for storing and dispensing a testing device
US5462051 *Aug 31, 1994Oct 31, 1995Colin CorporationMedical communication system
US5553609 *Feb 9, 1995Sep 10, 1996Visiting Nurse Service, Inc.Intelligent remote visual monitoring system for home health care service
US5572229 *Oct 26, 1993Nov 5, 1996Evans & Sutherland Computer Corp.Head-mounted projection display system featuring beam splitter and method of making same
US5701904 *Jan 11, 1996Dec 30, 1997Krug InternationalTelemedicine instrumentation pack
US5786846 *Mar 11, 1996Jul 28, 1998Nec CorporationUser interface of a video communication terminal unit and a method for notifying a terminal user's deviation from an appropriate shoot range
US5836872 *Apr 13, 1990Nov 17, 1998Vanguard Imaging, Ltd.Digital optical visualization, enhancement, quantification, and classification of surface and subsurface features of body surfaces
US5867653 *Apr 18, 1996Feb 2, 1999International Business Machines CorporationMethod and apparatus for multi-cast based video conferencing
US5917958 *Oct 31, 1996Jun 29, 1999Sensormatic Electronics CorporationDistributed video data base with remote searching for image data features
US5927423 *Mar 5, 1998Jul 27, 1999Massachusetts Institute Of TechnologyReconfigurable footprint mechanism for omnidirectional vehicles
US6133944 *Dec 17, 1996Oct 17, 2000Telcordia Technologies, Inc.Head mounted displays linked to networked electronic panning cameras
US6170929 *Dec 2, 1998Jan 9, 2001Ronald H. WilsonAutomated medication-dispensing cart
US6211903 *Mar 22, 1999Apr 3, 2001Cambridge Technology Development, Inc.Video telephone headset
US6219587 *May 27, 1998Apr 17, 2001Nextrx CorporationAutomated pharmaceutical management and dispensing system
US6232735 *Nov 24, 1999May 15, 2001Thames Co., Ltd.Robot remote control system and robot image remote control processing system
US6233504 *Apr 14, 1999May 15, 2001California Institute Of TechnologyTool actuation and force feedback on robot-assisted microsurgery system
US6256556 *May 25, 2000Jul 3, 2001Mitsubishi Denki Kabushiki KaishaRemote operation system for a robot
US6289263 *Dec 15, 1998Sep 11, 2001Board Of Trustees Operating Michigan State UniversitySpherical mobile robot
US6292713 *May 20, 1999Sep 18, 2001Compaq Computer CorporationRobotic telepresence system
US6321137 *Sep 4, 1998Nov 20, 2001Dynalog, Inc.Method for calibration of a robot inspection system
US6325756 *Mar 27, 1998Dec 4, 2001Medtronic, Inc.Concepts to implement medconnect
US6330493 *Sep 18, 2000Dec 11, 2001Fanuc Ltd.Control system for synchronously cooperative operation of plurality of robots
US6369847 *Mar 17, 2000Apr 9, 2002Emtel, Inc.Emergency facility video-conferencing system
US6430475 *Apr 10, 2001Aug 6, 2002National Aerospace Laboratory Of JapanPressure-distribution sensor for controlling multi-jointed nursing robot
US6466844 *Mar 1, 2001Oct 15, 2002Matsushita Electric Industrial Co., Ltd.Robot, robot system, and robot control method
US6532404 *Mar 1, 2002Mar 11, 2003Colens AndreMobile robots and their control system
US6535182 *Dec 7, 1998Mar 18, 2003Koninklijke Philips Electronics N.V.Head-mounted projection display system
US6535793 *May 1, 2001Mar 18, 2003Irobot CorporationMethod and system for remote control of mobile robot
US6540039 *Aug 3, 2000Apr 1, 2003Massachusetts Institute Of TechnologyOmnidirectional vehicle with offset wheel pairs
US6543899 *Dec 5, 2000Apr 8, 2003Eastman Kodak CompanyAuto-stereoscopic viewing system using mounted projection
US6691000 *Jul 25, 2002Feb 10, 2004Communications Research Laboratory, Independent Administrative InstitutionRobot-arm telemanipulating system presenting auditory information
US20010010053 *Mar 23, 2001Jul 26, 2001Ofer Ben-ShacharService framework for a distributed object network system
US20020177925 *May 21, 2002Nov 28, 2002Ken OnishiMethod and system for providing service by robot
US20050065659 *Feb 10, 2003Mar 24, 2005Michiharu TanakaRobot control device
Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US7142945 *Aug 6, 2004Nov 28, 2006Intouch Technologies, Inc.Medical tele-robotic system
US7142947 *Aug 6, 2004Nov 28, 2006Intouch Technologies, Inc.Medical tele-robotic method
US7164969 *Jan 2, 2004Jan 16, 2007Intouch Technologies, Inc.Apparatus and method for patient rounding with a remote controlled robot
US7164970 *Aug 6, 2004Jan 16, 2007Intouch Technologies, Inc.Medical tele-robotic system
US7222000Jan 18, 2005May 22, 2007Intouch Technologies, Inc.Mobile videoconferencing platform with automatic shut-off features
US7289883 *Jan 5, 2007Oct 30, 2007Intouch Technologies, Inc.Apparatus and method for patient rounding with a remote controlled robot
US7761185Oct 3, 2006Jul 20, 2010Intouch Technologies, Inc.Remote presence display through remotely controlled robot
US7769492Aug 3, 2010Intouch Technologies, Inc.Graphical interface for a remote presence system
US7957837Jun 7, 2011Irobot CorporationCompanion robot for personal interaction
US8077963Jul 13, 2004Dec 13, 2011Yulun WangMobile robot with a head-based movement mapping scheme
US8116910Aug 23, 2007Feb 14, 2012Intouch Technologies, Inc.Telepresence robot with a printer
US8170241Apr 17, 2008May 1, 2012Intouch Technologies, Inc.Mobile tele-presence system with a microphone system
US8179418May 15, 2012Intouch Technologies, Inc.Robotic based health care system
US8195333Jun 5, 2012Irobot CorporationCompanion robot for personal interaction
US8209051Sep 27, 2006Jun 26, 2012Intouch Technologies, Inc.Medical tele-robotic system
US8340819Sep 16, 2009Dec 25, 2012Intouch Technologies, Inc.Mobile videoconferencing robot system with network adaptive driving
US8359122 *Jan 22, 2013Vision Robotics CorporationAutonomous personal service robot
US8376803 *Feb 19, 2013Nec CorporationChild-care robot and a method of controlling the robot
US8384755Feb 26, 2013Intouch Technologies, Inc.Portable remote presence robot
US8401275Mar 19, 2013Intouch Technologies, Inc.Mobile robot with a head-based movement mapping scheme
US8463435Jan 6, 2009Jun 11, 2013Intouch Technologies, Inc.Server connectivity control for tele-presence robot
US8583282Sep 29, 2006Nov 12, 2013Irobot CorporationCompanion robot for personal interaction
US8670017Mar 4, 2010Mar 11, 2014Intouch Technologies, Inc.Remote presence system including a cart that supports a robot face and an overhead camera
US8718837Jan 27, 2012May 6, 2014Intouch TechnologiesInterfacing with a mobile telepresence robot
US8836751Nov 8, 2011Sep 16, 2014Intouch Technologies, Inc.Tele-presence system with a user interface that displays different communication links
US8849679Nov 25, 2008Sep 30, 2014Intouch Technologies, Inc.Remote controlled robot system that provides medical images
US8849680Jan 29, 2009Sep 30, 2014Intouch Technologies, Inc.Documentation through a remote presence robot
US8892260Sep 30, 2013Nov 18, 2014Irobot CorporationMobile robot for telecommunication
US8897920Apr 17, 2009Nov 25, 2014Intouch Technologies, Inc.Tele-presence robot system with software modularity, projector and laser pointer
US8902278Jul 25, 2012Dec 2, 2014Intouch Technologies, Inc.Systems and methods for visualizing and managing telepresence devices in healthcare networks
US8930019Sep 23, 2011Jan 6, 2015Irobot CorporationMobile human interface robot
US8935005Feb 22, 2011Jan 13, 2015Irobot CorporationOperating a mobile robot
US8935006Sep 29, 2006Jan 13, 2015Irobot CorporationCompanion robot for personal interaction
US8965579Jan 27, 2012Feb 24, 2015Intouch TechnologiesInterfacing with a mobile telepresence robot
US8983174Feb 19, 2013Mar 17, 2015Intouch Technologies, Inc.Mobile robot with a head-based movement mapping scheme
US8996165Oct 21, 2008Mar 31, 2015Intouch Technologies, Inc.Telepresence robot with a camera boom
US9014848Feb 22, 2011Apr 21, 2015Irobot CorporationMobile robot system
US9089972Jan 16, 2014Jul 28, 2015Intouch Technologies, Inc.Remote presence system including a cart that supports a robot face and an overhead camera
US9098611Mar 14, 2013Aug 4, 2015Intouch Technologies, Inc.Enhanced video interaction for a user interface of a telepresence network
US9138891Nov 25, 2008Sep 22, 2015Intouch Technologies, Inc.Server connectivity control for tele-presence robot
US9160783 *May 9, 2007Oct 13, 2015Intouch Technologies, Inc.Robot system that operates through a network firewall
US9174342Nov 21, 2014Nov 3, 2015Intouch Technologies, Inc.Social behavior rules for a medical telepresence robot
US9193065Jul 10, 2008Nov 24, 2015Intouch Technologies, Inc.Docking system for a tele-presence robot
US9198728Sep 30, 2005Dec 1, 2015Intouch Technologies, Inc.Multi-camera mobile teleconferencing platform
US9251313Apr 11, 2012Feb 2, 2016Intouch Technologies, Inc.Systems and methods for visualizing and managing telepresence devices in healthcare networks
US9264664Dec 3, 2010Feb 16, 2016Intouch Technologies, Inc.Systems and methods for dynamic bandwidth allocation
US9296107May 10, 2012Mar 29, 2016Intouch Technologies, Inc.Protocol for a remotely controlled videoconferencing robot
US9296109Oct 13, 2014Mar 29, 2016Irobot CorporationMobile robot for telecommunication
US9323250Aug 2, 2013Apr 26, 2016Intouch Technologies, Inc.Time-dependent navigation of telepresence robots
US9361021Nov 21, 2014Jun 7, 2016Irobot CorporationGraphical user interfaces including touchpad driving interfaces for telemedicine devices
US9375843Jun 18, 2010Jun 28, 2016Intouch Technologies, Inc.Protocol for a remotely controlled videoconferencing robot
US9429934Oct 15, 2013Aug 30, 2016Intouch Technologies, Inc.Mobile videoconferencing robot system with network adaptive driving
US20050021187 *Aug 6, 2004Jan 27, 2005Yulun WangMedical tele-robotic system
US20050027400 *Aug 6, 2004Feb 3, 2005Yulun WangMedical tele-robotic system
US20050215171 *Mar 25, 2005Sep 29, 2005Shinichi OonakaChild-care robot and a method of controlling the robot
US20060082642 *Oct 15, 2004Apr 20, 2006Yulun WangTele-robotic videoconferencing in a corporate environment
US20060161303 *Jan 18, 2005Jul 20, 2006Yulun WangMobile videoconferencing platform with automatic shut-off features
US20060259193 *May 12, 2005Nov 16, 2006Yulun WangTelerobotic system with a dual application screen presentation
US20070198129 *Feb 15, 2007Aug 23, 2007Harvey KoselkaAutonomous personal service robot
US20070198130 *Feb 22, 2006Aug 23, 2007Yulun WangGraphical interface for a remote presence system
US20070199108 *Sep 29, 2006Aug 23, 2007Colin AngleCompanion robot for personal interaction
US20070291109 *Oct 2, 2006Dec 20, 2007Yulun WangRemote controlled mobile robot with auxillary input ports
US20080082211 *Oct 3, 2006Apr 3, 2008Yulun WangRemote presence display through remotely controlled robot
US20090055023 *Aug 23, 2007Feb 26, 2009Derek WaltersTelepresence robot with a printer
US20090105882 *Dec 29, 2008Apr 23, 2009Intouch Technologies, Inc.Medical Tele-Robotic System
US20090177323 *Aug 27, 2008Jul 9, 2009Andrew ZieglerCompanion robot for personal interaction
US20100010673 *Jul 11, 2008Jan 14, 2010Yulun WangTele-presence robot system with multi-cast features
US20100019715 *Apr 17, 2008Jan 28, 2010David Bjorn RoeMobile tele-presence system with a microphone system
US20110172822 *Jul 23, 2010Jul 14, 2011Andrew ZieglerCompanion Robot for Personal Interaction
US20140114475 *Jun 17, 2013Apr 24, 2014Electronics And Telecommunications Research InstituteApparatus and method for sharing device resources between robot software components
US20150100461 *Oct 4, 2013Apr 9, 2015Dan BaryakarRobotic System Controlled by Multi Participants
USRE45870 *Jul 6, 2012Jan 26, 2016Intouch Technologies, Inc.Apparatus and method for patient rounding with a remote controlled robot
EP2281668A1 *Sep 29, 2006Feb 9, 2011iRobot CorporationCompanion robot for personal interaction
WO2005098729A2 *Mar 26, 2005Oct 20, 2005Harvey KoselkaAutonomous personal service robot
WO2005098729A3 *Mar 26, 2005Dec 21, 2006David GollaherAutonomous personal service robot
WO2016083870A1 *Nov 26, 2014Jun 2, 2016Husqvarna AbRemote interaction with a robotic vehicle
Classifications
U.S. Classification700/245
International ClassificationG06F19/00
Cooperative ClassificationG06F19/3418, B25J9/1697, G06F19/3406, B25J19/023, B25J9/1689, G05D1/0022, G05D2201/0206, Y10S901/47, Y10S901/01
European ClassificationB25J9/16T4, B25J19/02B4, G06F19/34C, G06F19/34A
Legal Events
DateCodeEventDescription
Feb 20, 2004ASAssignment
Owner name: INTOUCH-HEALTH, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WANG, YULUN;JORDAN, CHARLES S.;LABY, KEITH PHILLIP;AND OTHERS;REEL/FRAME:015014/0666;SIGNING DATES FROM 20040209 TO 20040213
Jun 15, 2005ASAssignment
Owner name: INTOUCH TECHNOLOGIES, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTOUCH HEALTH, INC.;REEL/FRAME:016686/0356
Effective date: 20050531