US 7,142,945 B2Grant
Medical tele-robotic system
Issue Date:2006-11-28
•7 Claims
•12 Drawing Sheets
Abstract
A robotic system that includes a remote controlled robot. The robot may include a camera, a monitor and a holonomic platform all attached to a robot housing. The robot may be controlled by a remote control station that also has a camera and a monitor. The remote control station may be linked to a base station that is wirelessly coupled to the robot. The cameras and monitors allow a care giver at the remote location to monitor and care for a patient through the robot. The holonomic platform allows the robot to move about a home or facility to locate and/or follow a patient.
Metadata
Assignee
- InTouch Technologies, Inc.
Inventors
- Yulun Wang
- Keith Phillip Laby
- Charles S. Jordan
- Steven Edward Butner
- Jonathan Southard
Application Information
Application Number:US 10/913,650
Filing Date:2004-08-06
Priority Date:2002-07-25
Art Unit:3661
Classifications
IPC:
G06F19/00
Patent Drawings (12 sheets)
Description
Cross Reference to Related Applications
[0001] This application is a divisional application claiming priority to U.S. patent application Ser. No. 10/206,457, filed Jul. 25, 2002, now U.S. Pat. No. 6,925,357.
Background of the Invention
[0002] 1. Field of the Invention
[0003] The subject matter disclosed generally relates to the field of robotics used in the medical field.
[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. There have also been developed “toy” robots for home use. Such robots typically have a relatively simple movement platform and some type of speech synthesis for generating words and sounds. It would be desirable to provide a robotic system that would allow for remote patient monitoring and assistance.
Brief Summary of the Invention
[0007] A robot that may include a camera and a monitor that are attached to a housing. The robot may also have a platform that is attached to the housing and coupled to a controller. The controller may be coupled to a broadband interface.
Brief Description of the Drawings
[0008] FIG. 1 is an illustration of a robotic system;
[0009] FIG. 2 is a schematic of an electrical system of a robot;
[0010] FIG. 3 is a further schematic of the electrical system of the robot;
[0011] FIG. 4 is an illustration of a robot with an arm in an upward position;
[0012] FIG. 5 is an illustration of the robot with the arm in a lower position;
[0013] FIG. 6 is an illustration of a holonomic platform of the robot;
[0014] FIG. 7 is an illustration of a roller assembly of the holonomic platform;
[0015] FIG. 8 is an illustration of an arm assembly of the robot;
[0016] FIG. 9 is an illustration of a gripper assembly of the arm;
[0017] FIG. 10 is a schematic of a battery recharger for the robot;
[0018] FIG. 11 is a vector diagram that may be used to compute movement of the robot.
Detailed Description
[0019] Disclosed is a robotic system that includes a remote controlled robot. The robot may include a camera, a monitor and a holonomic platform all attached to a robot housing. The robot may be controlled by a remote control station that also has a camera and a monitor. The remote control station may be linked to a base station that is wirelessly coupled to the robot. The cameras and monitors allow a care giver at the remote location to monitor and care for a patient through the robot. The holonomic platform allows the robot to move about a home or facility to locate and/or follow a patient.
[0020] 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 remote control station 16. The 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.
[0021] The 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. The control station 16 is typically located in a place that is remote from the robot 12. Although only one remote control station 16 is shown, the system 10 may include a plurality of remote stations. Additionally, 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.
[0022] 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 antennae 44 that is wirelessly coupled to an antennae 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.
[0023] The 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.
[0024] 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.
[0025] 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 44 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.11a.
[0026] The controller 54 may operate with a LINUX OS operating system. The controller 54 may also operate X 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.
[0027] 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.
[0028] 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, or to actuate an arm of the robot. 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.
[0029] 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 may be replaced or the robot 12 may be coupled to a wall power outlet by an electrical cord (not shown).
[0030] 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 allows the robot 12 to move in any direction. Although not shown the robot housing 112 may include bumpers.
[0031] The robot 12 may have an arm 114 that supports the camera 38 and monitor 40. The arm 114 may have two degrees of freedom so that the camera 26 and monitor 24 can be moved from an upper position shown in FIG. 4 to a lower position shown in FIG. 5 . The arm 114 may have an end effector 116 such as a gripper that can grasp objects.
[0032] The robot 12 may include a drawer 118 that can automatically move between a closed position and an open position. The drawer 118 can be used to dispense drugs to a patient. For example, the drawer 118 may include a drug(s) that must be taken at a certain time. The robot 12 may be programmed so that the drawer 118 is opened at the desired time. A nurse or other health care provider may periodically “load” the drawer 118. The robot may also have a battery recharger port 119. Although drugs are described, it is to be understood that the drawer 118 could hold any item.
[0033] As shown in FIG. 6 the holonomic platform 110 may include three roller assemblies 120 that are mounted to a base plate 122. The roller assemblies 120 are typically equally spaced about the platform 110 and allow for movement in any direction.
[0034] FIG. 7 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 includes a retainer ring 128 and a plurality of bushings 130 that allow the ball 124 to rotate in an x and y direction but prevents movement in a z direction.
[0035] 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 attached to drive pins 142 that are attached to a transmission bracket 144. The transmission rollers 126 are attached to a transmission bracket 144 by a roller pin 146. The transmission brackets 144 each have a pin 143 that is supported by a part of the housing.
[0036] 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 drive balls 126 are out of phase so that one of the balls 126 is always in contact with ball 124. The roller pin 146 and bracket 144 allow the transmission rollers 126 to freely spin and allow orthoganal directional passive movement when one of the other roller assemblies 120 is driving and moving the robot 12.
[0037] FIGS. 8 and 9 show an embodiment of the arm 114. The arm 114 may include a first linkage 150 that is pivotally mounted to a fixed plate 152 of the robot housing 12. The arm 114 may also include a second linkage 154 that is pivotally connected to the first linkage 150 and a third linkage 156 that is pivotally connected to the second linkage 154.
[0038] The first linkage 150 may be coupled to a first motor 158 and motor encoder 160 by a gear assembly 162. Rotation of the motor 158 will cause a corresponding pivotal movement of the linkage 150 and arm 114. The linkage 150 may be coupled to the fixed plate 152 by a bearing 164.
[0039] The second linkage 154 may be coupled to a second motor 166 and encoder 168 by a gear assembly 170 and a pulley assembly 172. The pulley assembly 172 may be connected to the gear assembly 170 by a pin 174 that extends through the gear assembly 162 of the first motor 158. The second linkage 154 may be attached to a pin 176 that can spin relative to the first linkage 150. The pulley assembly 172 may have a belt 178 that couples a pair of pulleys 180 and 182 that are attached to pins 174 and 176, respectively. Pin 176 may be coupled to the first linkage 150 by bearings 182. The arm 114 is configured to allow wires 183 to be internally routed through the linkages 150, 154 and 156.
[0040] The third linkage 156 may be connected to a pin 184 that can spin relative to the second linkage 154. The pin 184 may be coupled to the second linkage 154 by a bearing assembly 186. The third linkage 156 may be structurally coupled to the first linkage 150 by a pair of pulley assemblies 188. The pulley assembly 188 insures a horizontal position of the third linkage 156 no matter what position the first 150 and second 154 linkages are in. As shown in FIGS. 4 and 5 the third linkage 156 is always in a horizontal position. This insures that the camera 26 is always in the same orientation, thus reducing the possibility of disorientation at the remote control station when viewing the patient.
[0041] The gripper 116 is attached to the third linkage 156. The gripper 116 may include a pair of fingers 190 that are pivotally attached to a base plate 192. The fingers 190 are coupled to a motor 194 and encoder 196 by a gear assembly 198. The base plate 192 is coupled to the third linkage 156 by a bearing assembly 200. The motor 194 can spin the base plate 192 and fingers 192 relative to the third linkage 156.
[0042] The gripper 116 may further have a push rod 202 that can engage cam surfaces 204 of the fingers 190 to move the gripper fingers 190 between open and closed positions. The push rod 202 may be coupled to a motor 206 and encoder (not shown) by a linkage assembly 208. Actuation of the motor 206 will translate the push rod 202 and move the fingers 190. The motor 206 may have a force sensor that provides force feedback back to the remote control station. The input device of the remote control station may have a force feedback mechanism so that the user feels the force being exerted onto the gripper fingers 190.
[0043] 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 station allow for teleconferencing between the patient and the person at the remote station.
[0044] The robot 12 can be maneuvered through the home or facility by manipulating the input device 32 at the remote station 16. The robot 12 may also have autonomous movement. For example, the robot 12 may be programmed to automatically move to a patients room at a certain time to dispense drugs in the drawer 118 without input from the remote station 16. The robot 12 can be programmed to monitor and/or assist a patient 24 hours a day, 7 days a week. Such a monitoring capability is enhanced by the autonomous recharging function of the robot.
[0045] The robot 10 may be controlled by a number of different users. To accommodate for this the robot may have an arbitration system. The arbitration system may be integrated into the operating system of the robot 12. For example, the arbitration technique may be embedded into the operating system of the high-level controller 50.
[0046] By way of example, 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 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 tele-conference with the patient.
[0051] The arbitration scheme 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.
[0052]
| 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 |
[0053]
| TABLE II | |||||
|---|---|---|---|---|---|
| Requesting User | |||||
| Local | Caregiver | Doctor | Family | Service | |
| Current | |||||
| User | |||||
| Local | Not Allowed | Warn current user of | Warn current user of | Warn current user of | Warn current user of |
| pending user | pending user | pending user | pending user | ||
| Notifying requesting | Notifying requesting user | Notifying requesting user | Notifying 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 | ||
| 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 | that system is in use | Queue or callback | user that system is in | |
| in use | in 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 | pending user | pending user | pending user | |
| Notify requesting | in 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 | request | pending user | ||
| Notify requesting | in 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 | |||
[0054] 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.
[0055] FIG. 10 shows an embodiment of a battery recharger. The robot port 119 may include a secondary winding 250 that is magnetically coupled to a primary winding 252 of the battery recharger station 106. The primary winding 252 is coupled to an electrical outlet plug 254 by a relay circuit 256, a fuse 258 and a switch 260. The relay 256 is controlled by a recharger controller 262.
[0056] The recharger controller 262 is connected to a recharger infrared (IR) transceiver 264. The recharger IR transceiver 264 is coupled to a robot IR transceiver 266. The robot IR transceiver 266 is connected to the low level controller 52. The robot 10 may also have an alignment sensor 268 that can sense a target 270 on the station 106. By way of example, the sensor 268 may include an optical emitter and receiver that detects a light beam reflected from the target 270. The controller 52 may also sense a current flow into the battery 104 to determine whether the robot 12 is aligned with the docking station 106.
[0057] The secondary windings 250 are connected to the battery 104 by a charger circuit 272. The secondary 250 and primary 252 windings may each have wires 274 wrapped about a magnetic core 276. The station 106 may also have an oscillator/chopper circuit (not shown) to increase the voltage magnetically transferred to the secondary winding 250.
[0058] In operation, the robot 10 is moved to the battery recharger station 106 either autonomously, or by user control. The robot 10 is moved until the sensor 268 is aligned with the target 270. The low level controller 52 then sends a command to the recharger controller 262 through the transceivers 264 and 266. The recharger controller 262 then closes the relay 256 wherein power is transferred to the battery 104 through the windings 250 and 252. When the battery 104 is recharged, or the battery recharging process is interrupted by the user, the low level controller 52 transmits a command to the recharger controller 262 to open the relay 256. The robot 10 then moves away from the recharging station 106.
[0059] FIG. 11 shows a vector diagram that can be used to compute movement of the robot with the following equations:
[0060]
[0061] where,
[0062] w1=is the drive angular velocity of a first ball 124.
[0063] w2=is the drive angular velocity of a second ball 124.
[0064] w3=is the drive angular velocity of a third ball 124.
[0065] V=is the input linear velocity for the robot. V has components Vx and Vy, where; Vx=|V|cos θ and Vy=|V|sin θ.
[0066] ψ=is the input angular velocity for the robot.
[0067] Let the angular velocity vector w=[w1, w2, w3]T. (4)
[0068]
[0069] and the velocity vector:
V=[vx, vy, ψ]T (6)
W=A·V (7)
V=[vx, vy, ψ]T (6)
W=A·V (7)
[0070] The angular velocity vector w is calculated from equation (7) and compared with the actual w valves measured by the motor encoder. An algorithm performs an error correction routine to compensate for differences in the actual and desired valves.
[0071] 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.
Claims
Post-issuance certificates present
The text shown below may not reflect later post-issuance changes.
What is claimed is:
1. A method that allows a person to remotely visit a patient located in a healthcare facility, comprising:
accessing a robot from a remote station;
capturing video and audio of the patient by the robot;
transmitting the video and audio of the patient to the remote station;
displaying the video of the patient at the remote station;
generating the audio of the patient at the remote station;
capturing video and audio of the person at the remote station
transmitting the video and audio of the person to the robot;
displaying the video of the person on a monitor of the robot;
generating the audio of the person at the robot;
transmitting a command from the remote station to move the robot; and,
moving the robot across a surface of the healthcare facility in response to the transmitted command.
2. The method of claim 1, wherein the command, and the audio and video of the patient and the person are transmitted through a broadband network.
3. The method of claim 1, wherein the robot is located in a hospital.
4. The method of claim 1, wherein the robot is located in a residential care facility.
5. The method of claim 1, further comprising logging onto the remote station with a password.
6. The method of claim 1, wherein the transmitted video and audio are encrypted.
7. The method of claim 1, further comprising a family priority assignment that is transmitted to the robot.
Patent Citations (82)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3821995(A) | 1974-07-01 | Aghnides | Applicant |
| US4413693(A) | 1983-11-01 | Derby | Applicant |
| US4471354(A) | 1984-09-01 | Smith | Applicant |
| US4519466(A) | 1985-05-01 | Shiraishi | Applicant |
| US4638445(A) | 1987-01-01 | Mattaboni | Applicant |
| US4733737(A) | 1988-03-01 | Falamak | Applicant |
| US4875172(A) | 1989-10-01 | Kanayama | Applicant |
| US5073749(A) | 1991-12-01 | Kanayama | Applicant |
| US5186270(A) | 1993-02-01 | West | Applicant |
| US5341854(A) | 1994-08-01 | Zezulka et al. | Applicant |
| US5374879(A) | 1994-12-01 | Pin et al. | Applicant |
| US5419008(A) | 1995-05-01 | West | Applicant |
| US5544649(A) | 1996-08-01 | David et al. | Examiner |
| US5630566(A) | 1997-05-01 | Case | Applicant |
| US5636218(A) | 1997-06-01 | Ishikawa et al. | Applicant |
| US5762458(A) | 1998-06-01 | Wang et al. | Applicant |
| US5802494(A) | 1998-09-01 | Kuno | Examiner |
| US5838575(A) | 1998-11-01 | Lion | Applicant |
| US5857534(A) | 1999-01-01 | DeValult et al. | Applicant |
| US5959423(A) | 1999-09-01 | Nakanishi et al. | Applicant |
| US5966130(A) | 1999-10-01 | Benman, Jr. | Applicant |
| US6006946(A) | 1999-12-01 | Williams et al. | Applicant |
| US6036812(A) | 2000-03-01 | Williams et al. | Applicant |
| US6135228(A) | 2000-10-01 | Asada et al. | Applicant |
| US6232735(B1) | 2001-05-01 | Baba et al. | Applicant |
| US6259806(B1) | 2001-07-01 | Green | Applicant |
| US6292713(B1) | 2001-09-01 | Jouppi et al. | Applicant |
| US6304050(B1) | 2001-10-01 | Skaar et al. | Applicant |
| US6346950(B1) | 2002-02-01 | Jouppi | Applicant |
| US6369847(B1) | 2002-04-01 | James et al. | Applicant |
| US6430471(B1) | 2002-08-01 | Kintou et al. | Applicant |
| US6438457(B1) | 2002-08-01 | Yokoo et al. | Applicant |
| US6463361(B1) | 2002-10-01 | Wang et al. | Applicant |
| US6474434(B1) | 2002-11-01 | Bech | Applicant |
| US6491701(B1) | 2002-12-01 | Tierney et al. | Applicant |
| US6496099(B1) | 2002-12-01 | Wang et al. | Applicant |
| US6522906(B1) | 2003-02-01 | Salisbury et al. | Applicant |
| US6535793(B1) | 2003-03-01 | Allard | Applicant |
| US6549215(B1) | 2003-04-01 | Jouppi | Applicant |
| US6587750(B1) | 2003-07-01 | Gerbi et al. | Applicant |
| US6594552(B1) | 2003-07-01 | Nowlin et al. | Applicant |
| US6684129(B1) | 2004-01-01 | Salisbury et al. | Applicant |
| US6799065(B1) | 2004-09-01 | Niemeyer | Applicant |
| US6804656(B1) | 2004-10-01 | Rosenfeld et al. | Applicant |
| US6839612(B1) | 2005-01-01 | Sanchez et al. | Applicant |
| US6852107(B1) | 2005-02-01 | Wang et al. | Applicant |
| US6879879(B1) | 2005-04-01 | Jouppi et al. | Applicant |
| US2001/0037163(A1) | 2001-11-01 | Allard | Applicant |
| US2001/0054071(A1) | 2001-12-01 | Loeb | Applicant |
| US2002/0027597(A1) | 2002-03-01 | Sachau | Applicant |
| US2002/0057279(A1) | 2002-05-01 | Jouppi | Applicant |
| US2002/0058929(A1) | 2002-05-01 | Green | Applicant |
| US2002/0063726(A1) | 2002-05-01 | Jouppi | Applicant |
| US2002/0120362(A1) | 2002-08-01 | Lathan et al. | Applicant |
| US2002/0130950(A1) | 2002-09-01 | James et al. | Applicant |
| US2002/0141595(A1) | 2002-10-01 | Jouppi | Applicant |
| US2002/0183894(A1) | 2002-12-01 | Wang et al. | Applicant |
| US2003/0050733(A1) | 2003-03-01 | Wang et al. | Applicant |
| US2003/0100892(A1) | 2003-05-01 | Morley et al. | Applicant |
| US2003/0114962(A1) | 2003-06-01 | Niemeyer | Applicant |
| US2003/0135203(A1) | 2003-07-01 | Wang et al. | Applicant |
| US2003/0144649(A1) | 2003-07-01 | Ghodoussi et al. | Applicant |
| US2003/0151658(A1) | 2003-08-01 | Smith | Applicant |
| US2003/0220541(A1) | 2003-11-01 | Salisbury et al. | Applicant |
| US2004/0019406(A1) | 2004-01-01 | Wang et al. | Examiner |
| US2004/0117065(A1) | 2004-06-01 | Wang et al. | Examiner |
| US2004/0143421(A1) | 2004-07-01 | Wang et al. | Examiner |
| US2004/0162637(A1) | 2004-08-01 | Wang et al. | Examiner |
| US2004/0167666(A1) | 2004-08-01 | Wang et al. | Examiner |
| US2004/0167668(A1) | 2004-08-01 | Wang et al. | Examiner |
| US2004/0174129(A1) | 2004-09-01 | Wang et al. | Examiner |
| US2005/0021182(A1) | 2005-01-01 | Wang et al. | Examiner |
| US2005/0021183(A1) | 2005-01-01 | Wang et al. | Examiner |
| US2005/0021187(A1) | 2005-01-01 | Wang et al. | Examiner |
| US2005/0028221(A1) | 2005-02-01 | Liu et al. | Applicant |
| US2005/0035862(A1) | 2005-02-01 | Wildman et al. | Examiner |
| US2006/0047365(A1) | 2006-03-01 | Ghodoussi et al. | Examiner |
| CA2289697(A1) | 1998-11-01 | Applicant | |
| EP981905(B1) | 2002-01-01 | Applicant | |
| JP7257422(A) | 1995-10-01 | Applicant | |
| JP2002-046088 | 2002-02-01 | Applicant | |
| JP2002305743(A) | 2002-10-01 | Applicant |
Non-Patent Literature (34)
- Tzafestas et al., VR-based teleoperation of a mobile robotic assistant: Progress report, 2000, Internet, p. 1-23.Examiner
- McCardle et al., The challenge of utilising new technology in design education, 2000, Internet, p. 122-127.Examiner
- Trum et al., Probabilistic algorithms and the interactive museum tour-guide robot Minerva, 2000, Internet, p. 1-35.Examiner
- Ojha et al., An application of virtual reality in rehabilitation, 1994, IEEE, p., 4-6.Examiner
- Stephenson, Dr. robot tested at Hopkins, 2003, Internet, p. 1.Examiner
- Elhajj et al., Supermedia in Internet-based telerobotic operations, 2001, Internet, p., 1-14.Examiner
- Bauer, Jeffrey C., “Service Robots in Health Care: The Evolution of Mechanical Solutions to Human Resource Problems”, Jun. 2003.Applicant
- Breslow, Michael J., MD et al., “Effect of a multiple-site intensive care unit telemedicine program on clinical and economic outcome: An alternative paradigm for intensivist staffing”, Critical Care Med, Jan. 2004, vol. 32, No. 1, pp. 31-38.Applicant
- Celi et al., “The elCU: It's not just telemedicine”, Critical Care Medicine, vol. 29, No. 8 (Supplement), Aug. 2001.Applicant
- CNN.com/Technology, Paging R.Robot: Machine helps doctors with patients, Sep. 30, 2003, Internet, 1-3.Applicant
- Davies, “Robotics in Minimally Invasive Surgery”, 1995, Internet, pp. 5/1-5/2.Applicant
- Goldman, Lea, “Machine Dreams”, Entrepreneurs, Forbes, May 27, 2002.Applicant
- Harmo et al., “Moving Eye—Interactive Telepresence Over Internet With a Ball Shaped Mobile Robot”, 2000.Applicant
- Hees, William P., “Communications Design for a Remote Presence Robot”, Jan. 14, 2002.Applicant
- Jouppi, et al., :Mutually-Immersive Audio Telepresence, Audio Engineering Society Convention Paper, presented at 113th Convention Oct. 2002.Applicant
- Jouppi, Norman P., “First Steps Towards Mutually-Immersive Mobile Telepresence”, 2002.Applicant
- Kanehiro, Fumio et al., Virtual Humanoid Robot Platform to Develop Controllers of Real Humanoid Robots without Porting, 2001,IEEE, pp. 3217-3276.Applicant
- Lim, Hun-ok et al., Control to Realize Human-like Walking of a Biped Humanoid Robot, IEE 2000, pp. 3271-3276.Applicant
- Loeb, Gerald, “Virtual Visit: Improving Communication for Those Who Need It Most”, 2001.Applicant
- Mack, “Minimally invasive and robotic surgery”, 2001, IEEE, pp. 568-572.Applicant
- Magne Charge—Smart Power for Electric Vehicles, Internet, Jun. 27, 2002.Applicant
- Martin, Anya, “Days Ahead”, Assisted Living Today, vol. 9, Nov./Dec. 2002, pp. 19-22.Applicant
- McCardle et al., “The challenge of utilizing new technology in design education”, 2000 Internet, pp. 122-127.Applicant
- Paulos et al., “A World Wide Web Telerobotic Remote Environment Browser”, http://vive.cs.berkeley.edu/capek, 1995.Applicant
- Paulos, Eric John, “Personal Tele-Embodiment”, 2001.Applicant
- Paulos, et al. , “Ubiquitous Tele-embodiment: Applications and Implications”, International Journal of Human Computer Studies, Jun. 1997, vol. 46, No. 6, pp. 861-877.Applicant
- Paulos, et al., “Designing Personal Tele-Embodiment”, Presented at the IEEE International Conference on Robotics and Animation, Leuven, Belgium, May 20, 1998.Applicant
- Pin et al., “A New Family of Omnidirectional and Holonomic Wheeled Platforms for Mobile Robots”, IEEE, vol. 10, No. 4, Aug. 1994.Applicant
- Roland PIQUEPAILLE's Technology Trends, How new technologies are modifying your way of life, 2003, Internet, pp. 1-2.Applicant
- Roy et al., “Towards Personal Service Robots for the Elderly”, Internet, Mar. 7, 2002.Applicant
- Stoianovici et al., “Robotic Tools for Minimally Invasive Urologic Surgery”, Dec. 2002, Internet, 1-17.Applicant
- Tendick et al., “Human-Machine Interfaces for Minimally Invasive Surgery”, 1997, IEEE, pp. 1-6.Applicant
- Urquhart, Kim, “InTouch's robotic Companion ‘beams up’ healthcare experts”, Medical Device Daily, vol. 7, No. 39, Feb. 27, 2003, p. 1, 4.Applicant
- Zorn, Benjamin G., “Ubiquitous Telepresence”, http://www.cs.colorado.edu/-zorn/ut/vision/vision.html, Mar. 5, 1996.Applicant