US 8,401,275 B2Grant

Mobile robot with a head-based movement mapping scheme

Issue Date:2013-03-19

•23 Claims

•9 Drawing Sheets

Abstract

A robotic system that includes a mobile robot and a remote input device. The input device may be a joystick that is used to move a camera and a mobile platform of the robot. The system may operate in a mode where the mobile platform moves in a camera reference coordinate system. The camera reference coordinate system is fixed to a viewing image provided by the camera so that movement of the robot corresponds to a direction viewed on a screen. This prevents disorientation during movement of the robot if the camera is panned across a viewing area.

Metadata

Assignee

InTouch Technologies, Inc.

Inventors

Yulun Wang
Charles S. Jordan
Keith P. Laby
Jonathan Southard
Marco Pinter
Brian Miller

Application Information

Application Number:US 12/413,038

Filing Date:2009-03-27

Priority Date:2004-07-13

Art Unit:2665

Classifications

IPC:

G06K9/00

Patent Drawings (9 sheets)

Description

Cross Reference to Related Applications

[0001] This application is a divisional application of claiming priority to U.S. application Ser. No. 10/890,891, filed Jul. 13, 2004, pending.

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.

[0006] The assignee of this invention(s), InTouch-Health, Inc. markets a remote controlled mobile robot under the trademark COMPANION that can be used by medical personnel to remotely “visit” patients. The COMPANION system includes a mobile robot with a camera, monitor, microphone, speakers, and other equipment that allow for two-way audio/visual communication between the patient and someone operating the system from a remotely located computer.

[0007] The COMPANION system includes a joystick that can be manipulated to move a mobile platform of the robot. A forward pivot of the joystick causes a corresponding forward movement of the mobile platform. The joystick button can be depressed to move the camera and allow the user to pan a room. Unfortunately, panning the camera may cause the forward viewing direction depicted by the screen to be different than the forward vector of the mobile platform. A forward pivot of the joystick will cause an angular movement of the robot relative to the field of view provided by the robot camera. This can cause disorientation and in general complicates movement of the robot.

Brief Summary of the Invention

[0008] A mobile robot system that is controlled through an input device. The system includes a robot that has a camera located in a camera reference coordinate system, and a mobile platform. The input device causes movement of the camera, and movement of the mobile platform within the camera reference coordinate system.

Brief Description of the Drawings

[0009] FIG. 1 is an illustration of a robotic system;

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

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

[0012] FIG. 4 is side view of the robot;

[0013] FIG. 5 is an illustration of a mapping scheme for a joystick of the system;

[0014] FIG. 6 is a top perspective view of a holonomic platform of the robot;

[0015] FIG. 7 is a side perspective view of a roller assembly of the holonomic platform;

[0016] FIG. 8 is a bottom perspective view showing a pedestal assembly of the robot;

[0017] FIG. 9 is a sectional view showing an actuator of the pedestal assembly.

Detailed Description

[0018] Disclosed is a robotic system that includes a mobile robot and a remote input device. The input device may be a joystick that is used to move a camera and a mobile platform of the robot. The system may operate in a mode where the mobile platform moves in a camera reference coordinate system. The camera reference coordinate system is fixed to a viewing image provided by the camera so that movement of the robot corresponds to a direction viewed on a screen. This prevents disorientation during movement of the robot if the camera is panned across a viewing area.

[0019] 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.

[0020] 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 joystick 32 may have a toggle button 33 that allows the system to operate in two different modes. In one mode the robot moves in a platform reference coordinate system. In another mode the robot moves in a camera reference coordinate system.

[0021] The control station 16 is typically located in a place that is remote from the robot 12. Although only one robot 12 and one station 16 are shown, it is to be understood that the system 10 may have a plurality of robots 12 and/or a plurality of remote stations that communicate through the broadband network. In general any number of robots 12 may be controlled by any number of remote stations 16. 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 mobile 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.

[0023] 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.

[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 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.

[0026] 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.

[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. 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 16. 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 104 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 provides three degrees of freedom to allow the robot 12 to move in any direction.

[0031] The robot 12 may have a 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.

[0032] The platform 110 is located within a platform reference coordinate system that may have axes X_p, Y_pand Z_p. By way of example, the y-axis Y_pmay extend from a nose of the platform 110. The camera 38 is fixed to a camera reference coordinate system that may have axes X_c, Y_cand Z_c. The y-axis Y_cmay extend perpendicular from the camera lens. When the robot is initialized, the y-axis Y_cof the camera coordinate system may be aligned with the y-axis Y_pof the platform coordinate system. A forward pivoting of the joystick 32 (shown in FIG. 1) may cause a corresponding movement of the platform 110 in the direction of the y-axis Y_pin the platform coordinate system.

[0033] The robot may have a drive vector that may have axes X_d, Y_d, and Z_dthat is mapped to the camera coordinate system, the platform coordinate system or some other system. By way of example, the y-axis Y_pmay extend in the direction of forward motion. Mapping includes the process of transforming an input command into a directional movement relative to one or more coordinate systems. The robot controller may perform certain algorithms to translate input commands to platform movement in accordance with a specified mapping scheme. For example, when the drive vector is mapped to the camera coordinate system the controller computes the drive vector of the input command relative to the camera coordinate system. In a platform mapping scheme the input drive vector is computed relative to the platform coordinate system. In yet another scheme the drive vector can be computed relative to another coordinate system, such as a world coordinate system (eg. coordinate system relative to the ground) that is independent of the camera or platform coordinate systems. Mapping the drive vector to the camera coordinate system may be desirable because all movement would be relative to the image viewed by the user, providing a system that is intuitive to use.

[0034] A twisting of the joystick 32 may cause the camera 38 to swivel as indicated by arrows 4. For example, if the joystick 32 is twisted +45 degrees the camera 38 will pivot +45 degrees. Swiveling the camera 38 also moves the y-axis Y_cof the camera coordinate system, because the y-axis Y_cis fixed to the camera. This may be different than the drive direction. The remote station computer may operate a program to generate a command that will automatically rotate the platform 110 to realign the y-axis Y_pof the platform coordinate system with the y-axis Y_cof the camera coordinate system. For the above example, the platform 110 is rotated +45 degrees. This approach keeps the platform 110 aligned with the camera 38, so that any subsequent movement of the robot will be intuitive relative to the image provided by the camera. For example, a forward pivot of the joystick will induce a forward movement of the robot as viewed through the monitor of the remote station. In this driving scheme, the platform may not be aligned with the head. The computer may generate trajectory planning for the platform coordinate system to move into alignment with the head coordinate system over a period of time or distance traveled, with or without an initial delay in time or some distance.

[0035] The system may be configured so that pivotal movement of the joystick 32 may be mapped to a corresponding directional movement of the robot as shown in FIG. 5. For example, pivoting, the joystick along the +45 degree line shown in FIG. 5 may cause the robot to move in a +45 degree direction relative to the y-axis Y_cof the camera coordinate frame. Alternatively, the camera may pan +45 degrees and the platform 110 may rotate +45 degrees before forward movement by the robot. The automatic panning and platform rotation causes the robot to move in a forward direction as depicted by the image provided by the camera. The robot may have a mode wherein the user can twist the joystick to pan the camera during robot movement such that the movement is not in the direction the camera is pointing. This allows the user to visually pan while moving the robot. The joystick may have a spring return that automatically returns the position of the stick when released by the user. This causes the camera to be aligned with the direction of movement.

[0036] In general the robot may have a number of different mapping schemes and relative, dependent or independent, movement between the camera, the platform and drive direction. Relative movement between the camera and platform may occur in a camera based mapping scheme, a platform based mapping scheme, or some other scheme.

[0037] Although, the automatic platform rotation commands have been described as be generated by the remote station computer, it is to be understood that the robot may determine the commands and signals necessary to re-orient the platform 110 and/or the camera 38. The robot 12 may include a potentiometer (not shown) that tracks the position of the camera and provides feedback to the low level controller 80. The low level controller 80 may automatically rotate the platform to align the y-axes Y_cand Y_por otherwise compensate for camera movement. The mode button 33 may allow the operator to place the system in either a tracking mode or a normal mode. In the tracking mode the robot moves relative to the camera coordinate system so that movement is intuitive relative to the screen even when the camera is panned. In normal mode the robot moves within the platform coordinate system.

[0038] FIG. 6 shows an embodiment of a 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.

[0039] 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.

[0040] 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 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.

[0041] 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.

[0042] 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 in a direction orthogonal to the drive direction when one of the other roller assemblies 120 is driving and moving the robot 12.

[0043] As shown in FIG. 8, 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.

[0044] As shown in FIG. 9, 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.

[0045] 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).

[0046] The robot 12 can be maneuvered through the home or facility by manipulating the input device 32 at a remote station 16. 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.

[0047] 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 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.

[0048] 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.

[0049] 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.

[0050] 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 I and II, show how the mechanisms resolve access request from the various users.

[0051]

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]

	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

[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] The robot 12 and remote station 16 transmit commands through the broadband network 18. The commands can be generated by the user in a variety of ways. For example, commands to move the robot may be generated by moving the joystick 32 (see FIG. 1). The commands are preferably assembled into packets in accordance with TCP/IP protocol. Table III provides a list of control commands that are generated at the remote station and transmitted to the robot through the network.

[0055]

TABLE III

Control Commands
Command	Example	Description

drive	drive 10.0 0.0 5.0	The drive command directs the robot to move
		at the specified velocity (in cm/sec) in the
		(x, y) plane, and turn its facing at the
		specified rate (degrees/sec).
goodbye	goodbye	The goodbye command terminates a user
		session and relinquishes control of the
		robot
gotoHomePosition	gotoHomePosition 1	The gotoHomePosition command moves the head
		to a fixed “home” position (pan and tilt),
		and restores zoom to default value. The
		index value can be 0, 1, or 2. The exact
		pan/tilt values for each index are specified
		in robot configuration files.
head	head vel pan 5.0 tilt	The head command controls the head motion.
	10.0	It can send commands in two modes,
		identified by keyword: either positional
		(“pos”) or velocity (“vol”). In velocity
		mode, the pan and tilt values are desired
		velocities of the head on the pan and tilt
		axes, in degree/sec. A single command can
		include just the pan section, or just the
		tilt section, or both.
keepalive	keepalive	The keepalive command causes no action, but
		keeps the communication (socket) link open
		so that a session can continue. In scripts,
		it can be used to introduce delay time into
		the action.
odometry	odometry 5	The odometry command enables the flow of
		odometry messages from the robot. The
		argument is the number of times odometry is
		to be reported each second. A value of 0
		turns odometry off.
reboot	reboot	The reboot command causes the robot computer
		to reboot immediately. The ongoing session
		is immediately broken off.
restoreHeadPosition	restoreHeadPosition	The restoreHeadPosition functions like the
		gotoHomePosition command, but it homes the
		head to a position previously saved with
		gotoHomePosition.
saveHeadPosition	saveHeadPosition	The saveHeadPosition command causes the
		robot to save the current head position (pan
		and tilt) in a scratch location in temporary
		storage so that this position can be
		restored. Subsequent calls to
		“restoreHeadPosition” will restore this
		saved position. Each call to
		saveHeadPosition overwrites any previously
		saved position.
setCameraFocus	setCameraFocus 100.0	The setCameraFocus command controls focus
		for the camera on the robot side. The value
		sent is passed “raw” to the video
		application running on the robot, which
		interprets it according to its own
		specification.
setCameraZoom	setCameraZoom 100.0	The setCameraZoom command controls zoom for
		the camera on the robot side. The value
		sent is passed “raw” to the video
		application running on the robot, which
		interprets it according to its own
		specification.
shutdown	Shutdown	The shutdown command shuts down the robot
		and powers down its computer.
stop	stop	The stop command directs the robot to stop
		moving immediately. It is assumed this will
		be as sudden a stop as the mechanism can
		safely accommodate.
timing	Timing 3245629 500	The timing message is used to estimate
		message latency. It holds the UCT value
		(seconds + milliseconds) of the time the
		message was sent, as recorded on the sending
		machine. To do a valid test, you must
		compare results in each direction (i.e.,
		sending from machine A to machine B, then
		from machine B to machine A) in order to
		account for differences in the clocks
		between the two machines. The robot records
		data internally to estimate average and
		maximum latency over the course of a
		session, which it prints to log files.
userTask	userTask “Jane Doe”	The userTask command notifies the robot of
	“Remote Visit”	the current user and task. It typically is
		sent once at the start of the session,
		although it can be sent during a session if
		the user and/or task change. The robot uses
		this information for record-keeping.

[0056] Table IV provides a list of reporting commands that are generated by the robot and transmitted to the remote station through the network.

[0057]

TABLE IV

Reporting Commands
Command	Example	Description

abnormalExit	abnormalExit	This message informs the user that the robot
		software has crashed or otherwise exited
		abnormally. Te robot software catches top-
		level exceptions and generates this message
		if any such exceptions occur.
bodyType	bodyType 3	The bodyType message informs the station
		which type body (using the numbering of the
		mechanical team) the current robot has.
		This allows the robot to be drawn correctly
		in the station user interface, and allows
		for any other necessary body-specific
		adjustments.
driveEnabled	driveEnabled true	This message is sent at the start of a
		session to indicate whether the drive system
		is operational.
emergencyShutdown	emergencyShutdown	This message informs the station that the
		robot software has detected a possible
		“runaway” condition (an failure causing the
		robot to move out of control) and is
		shutting the entire system down to prevent
		hazardous motion.
odometry	odometry 10 20 340	The odometry command reports the current
		(x, y) position (cm) and body orientation
		(degrees) of the robot, in the original
		coordinate space of the robot at the start
		of the session.
sensorGroup	group_data	Sensors on the robot are arranged into
		groups, each group of a single type (bumps,
		range sensors, charge meter, etc.) The
		sensorGroup message is sent once per group
		at the start of each session. It contains
		the number, type, locations, and any other
		relevant data for the sensors in that group.
		The station assumes nothing about the
		equipment carried on the robot; everything
		it knows about the sensors comes from the
		sensorGroup messages.
sensorState	groupName state data	The sensorState command reports the current
		state values for a specified group of
		sensor. The syntax and interpretation for
		the state data is specific to each group.
		This message is sent once for each group at
		each sensor evaluation (normally several
		times per second).
systemError	systemError	This message informs the station user of a
	driveController	failure in one of the robot's subsystems.
		The error_type argument indicates which
		subsystem failed, including driveController,
		sensorController, headHome.
systemInfo	systemInfo wireless 45	This message allows regular reporting of
		information that falls outside the sensor
		system such as wireless signal strength.
text	text “This is some	The text string sends a text string from the
	text”	robot to the station, where the string is
		displayed to the user. This message is used
		mainly for debugging.
version	version 1.6	This message identifies the software version
		currently running on the robot. It is sent
		once at the start of the session to allow
		the station to do any necessary backward
		compatibility adjustments.

[0058] 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

What is claimed is:

1. A mobile robot system that is controlled through an input device, comprising:

a robot that has a camera with a camera reference coordinate system having at least a first axis fixed to said camera and a mobile platform with a platform reference coordinate system having at least a first axis fixed to said mobile platform; and,

an input device that causes movement of both said camera and said mobile platfoiin within the camera reference coordinate system such that the first axes of the camera and platform reference coordinate systems become aligned from a state wherein the first axes of the camera and platform reference coordinate systems were not in alignment.

2. The system of claim 1, wherein said input device is a joystick.

3. The system of claim 1, wherein said mobile platform rotates to align an axis of a platform reference coordinate system fixed to said mobile platform with an axis of the camera reference coordinate system.

4. The system of claim 1, wherein movement of said mobile platform is accompanied by a movement of said camera.

5. The system of claim 2, wherein twisting said joystick causes rotation of said camera and pivoting said joystick causes said mobile platform to move.

6. The system of claim 1, further comprising a computer coupled to said input device and said robot.

7. The system of claim 1, further comprising a wireless base station coupled to said robot and said input device.

8. The system of claim 7, further comprising a broadband network that is coupled to said wireless base station and said input device.

9. The system of claim 1, wherein said robot includes a monitor.

10. A mobile robot system that is controlled through an input device, comprising:

a robot that has a camera with a camera reference coordinate system with at least a first axis fixed to said camera, and a mobile platform with a platform reference coordinate system with at least a first axis fixed to said mobile platform; and,

input means for moving both said camera and said mobile platform within the camera reference coordinate system such that the first axes of the camera and platform reference coordinate systems become aligned from a state wherein the first axes of the camera and platform reference coordinate systems were not in alignment.

11. The system of claim 10, wherein said input means includes a joystick.

12. The system of claim 10, wherein movement of said mobile platform is accompanied by a movement of said camera.

13. The system of claim 11, wherein twisting said joystick causes rotation of said camera and pivoting said joystick causes said mobile platform to move.

14. The system of claim 10, wherein said input means includes a computer.

15. The system of claim 10, further comprising a wireless base station coupled to said robot and said input means.

16. The system of claim 15, further comprising a broadband network that is coupled to said wireless base station and said input means.

17. The system of claim 1, wherein said robot includes a monitor.

18. A method for controlling a robot, comprising:

moving both a camera of a robot with a camera reference coordinate system with at least a first axis that is fixed to the camera and a mobile platform with a platform reference coordinate system with at least a first axis fixed to the mobile platform, such that the first axes of the camera and platform reference coordinate systems become aligned from a state wherein the first axes of the camera and platform reference coordinate systems were not in alignment.

19. The method of claim 18, wherein the robot is in a mode where the robot moves within a platform reference coordinate system.

20. The method of claim 18, wherein the robot has a mobile platform with a platform reference coordinate system, and the mobile platform is rotated so that an axis of a platform reference coordinate system is aligned with an axis of the camera reference coordinate system.

21. The method of claim 18, wherein the robot receives commands from a wireless base station.

22. The method of claim 21, wherein the command is transmitted through a broadband network.

23. The method of claim 18, wherein the camera and robot are moved through manipulation of a joystick.

Patent Citations (595)

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
US4572594(A)	1986-02-01	Schwartz	Applicant
US4625274(A)	1986-11-01	Schroeder	Applicant
US4638445(A)	1987-01-01	Mattaboni	Applicant
US4652204(A)	1987-03-01	Arnett	Applicant
US4669168(A)	1987-06-01	Tamura et al.	Applicant
US4697472(A)	1987-10-01	Hiyane	Applicant
US4709265(A)	1987-11-01	Silverman et al.	Applicant
US4733737(A)	1988-03-01	Falamak	Applicant
US4751658(A)	1988-06-01	Kadonoff et al.	Applicant
US4766581(A)	1988-08-01	Korn et al.	Applicant
US4777416(A)	1988-10-01	George, II et al.	Applicant
US4797557(A)	1989-01-01	Ohman	Applicant
US4803625(A)	1989-02-01	Fu et al.	Applicant
US4847764(A)	1989-07-01	Halvorson	Applicant
US4875172(A)	1989-10-01	Kanayama	Applicant
US4942512(A)	1990-07-01	Kohno	Applicant
US4942538(A)	1990-07-01	Yuan et al.	Applicant
US4953159(A)	1990-08-01	Hayden et al.	Applicant
US4974607(A)	1990-12-01	Miwa	Applicant
US4977971(A)	1990-12-01	Crane, III et al.	Applicant
US5006988(A)	1991-04-01	Borenstein et al.	Applicant
US5040116(A)	1991-08-01	Evans et al.	Applicant
US5051906(A)	1991-09-01	Evans et al.	Applicant
US5073749(A)	1991-12-01	Kanayama	Applicant
US5084828(A)	1992-01-01	Kaufman et al.	Applicant
US5130794(A)	1992-07-01	Ritchey	Applicant
US5148591(A)	1992-09-01	Pryor	Applicant
US5153833(A)	1992-10-01	Gordon et al.	Applicant
US5155684(A)	1992-10-01	Burke et al.	Applicant
US5157491(A)	1992-10-01	Kassatly	Applicant
US5182641(A)	1993-01-01	Diner et al.	Applicant
US5186270(A)	1993-02-01	West	Applicant
US5193143(A)	1993-03-01	Kaemmerer et al.	Applicant
US5217453(A)	1993-06-01	Wilk	Applicant
US5224157(A)	1993-06-01	Yamada et al.	Applicant
US5231693(A)	1993-07-01	Backes et al.	Applicant
US5236432(A)	1993-08-01	Matsen, II et al.	Applicant
US5413693(A)	1993-11-01	Derby	Applicant
US5305427(A)	1994-04-01	Nagata	Applicant
US5315287(A)	1994-05-01	Sol	Applicant
US5319611(A)	1994-06-01	Korba	Applicant
US5341242(A)	1994-08-01	Gilboa et al.	Applicant
US5341459(A)	1994-08-01	Backes	Applicant
US5341854(A)	1994-08-01	Zezulka et al.	Applicant
US5347457(A)	1994-09-01	Tanaka et al.	Applicant
US5350033(A)	1994-09-01	Kraft	Applicant
US5366896(A)	1994-11-01	Margrey et al.	Applicant
US5374879(A)	1994-12-01	Pin et al.	Applicant
US5417210(A)	1995-05-01	Funda et al.	Applicant
US5419008(A)	1995-05-01	West	Applicant
US5436542(A)	1995-07-01	Petelin et al.	Applicant
US5441042(A)	1995-08-01	Putman	Applicant
US5441047(A)	1995-08-01	David et al.	Applicant
US5442728(A)	1995-08-01	Kaufman et al.	Applicant
US5462051(A)	1995-10-01	Oka et al.	Applicant
US5486853(A)	1996-01-01	Baxter et al.	Applicant
US5510832(A)	1996-04-01	Garcia	Applicant
US5528289(A)	1996-06-01	Cortjens et al.	Applicant
US5539741(A)	1996-07-01	Barraclough et al.	Applicant
US5544649(A)	1996-08-01	David et al.	Applicant
US5550577(A)	1996-08-01	Verbiest et al.	Applicant
US5553609(A)	1996-09-01	Chen et al.	Applicant
US5572229(A)	1996-11-01	Fisher	Applicant
US5572999(A)	1996-11-01	Funda et al.	Applicant
US5594859(A)	1997-01-01	Palmer et al.	Applicant
US5600573(A)	1997-02-01	Hendricks et al.	Applicant
US5630566(A)	1997-05-01	Case	Applicant
US5636218(A)	1997-06-01	Ishikawa	Applicant
US5652849(A)	1997-07-01	Conway et al.	Applicant
US5657246(A)	1997-08-01	Hogan et al.	Applicant
US5659779(A)	1997-08-01	Laird et al.	Applicant
US5682199(A)	1997-10-01	Lankford	Applicant
US5684695(A)	1997-11-01	Bauer	Applicant
US5701904(A)	1997-12-01	Simmons et al.	Applicant
US5739657(A)	1998-04-01	Takayama et al.	Applicant
US5749058(A)	1998-05-01	Hashimoto	Applicant
US5749362(A)	1998-05-01	Funda et al.	Applicant
US5762458(A)	1998-06-01	Wang et al.	Applicant
US5764731(A)	1998-06-01	Yablon	Applicant
US5767897(A)	1998-06-01	Howell	Applicant
US5786846(A)	1998-07-01	Hiroaki	Applicant
US5802494(A)	1998-09-01	Kuno	Applicant
US5836872(A)	1998-11-01	Kenet et al.	Applicant
US5838575(A)	1998-11-01	Lion	Applicant
US5857534(A)	1999-01-01	DeVault et al.	Applicant
US5867653(A)	1999-02-01	Aras et al.	Applicant
US5871451(A)	1999-02-01	Unger et al.	Applicant
US5876325(A)	1999-03-01	Mizuno et al.	Applicant
US5911036(A)	1999-06-01	Wright et al.	Applicant
US5917958(A)	1999-06-01	Nunally et al.	Applicant
US5927423(A)	1999-07-01	Wada et al.	Applicant
US5949758(A)	1999-09-01	Kober	Applicant
US5954692(A)	1999-09-01	Smith et al.	Applicant
US5959423(A)	1999-09-01	Nakanishi et al.	Applicant
US5966130(A)	1999-10-01	Benman, Jr.	Applicant
US5973724(A)	1999-10-01	Riddle	Applicant
US5974446(A)	1999-10-01	Sonnenreich et al.	Applicant
US5995884(A)	1999-11-01	Allen et al.	Applicant
US5999977(A)	1999-12-01	Riddle	Applicant
US6006946(A)	1999-12-01	Williams et al.	Applicant
US6036812(A)	2000-03-01	Williams et al.	Applicant
US6133944(A)	2000-10-01	Braun et al.	Applicant
US6135228(A)	2000-10-01	Asada et al.	Applicant
US6148100(A)	2000-11-01	Anderson et al.	Applicant
US6170929(B1)	2001-01-01	Wilson et al.	Applicant
US6175779(B1)	2001-01-01	Barrett	Applicant
US6201984(B1)	2001-03-01	Funda et al.	Applicant
US6211903(B1)	2001-04-01	Bullister	Applicant
US6219587(B1)	2001-04-01	Ahlin et al.	Applicant
US6232735(B1)	2001-05-01	Baba et al.	Applicant
US6233504(B1)	2001-05-01	Das et al.	Applicant
US6256556(B1)	2001-07-01	Zenke	Applicant
US6259806(B1)	2001-07-01	Green	Applicant
US6259956(B1)	2001-07-01	Myers et al.	Applicant
US6266162(B1)	2001-07-01	Okamura et al.	Applicant
US6266577(B1)	2001-07-01	Popp et al.	Applicant
US6289263(B1)	2001-09-01	Mukherjee	Applicant
US6292713(B1)	2001-09-01	Jouppi et al.	Applicant
US6304050(B1)	2001-10-01	Skaar et al.	Applicant
US6321137(B1)	2001-11-01	De Smet	Applicant
US6325756(B1)	2001-12-01	Webb et al.	Applicant
US6327516(B1)	2001-12-01	Zenke	Applicant
US6330486(B1)	2001-12-01	Padula	Applicant
US6330493(B1)	2001-12-01	Takahashi et al.	Applicant
US6346950(B1)	2002-02-01	Jouppi	Applicant
US6346962(B1)	2002-02-01	Goodridge	Applicant
US6369847(B1)	2002-04-01	James et al.	Applicant
US6381515(B1)	2002-04-01	Inoue et al.	Applicant
US6408230(B2)	2002-06-01	Wada	Applicant
US6430471(B1)	2002-08-01	Kintou et al.	Applicant
US6430475(B2)	2002-08-01	Okamoto et al.	Applicant
US6438457(B1)	2002-08-01	Yokoo et al.	Applicant
US6452915(B1)	2002-09-01	Jorgensen	Applicant
US6457043(B1)	2002-09-01	Kwak et al.	Applicant
US6459955(B1)	2002-10-01	Bartsch et al.	Applicant
US6463352(B1)	2002-10-01	Tadokoro et al.	Applicant
US6463361(B1)	2002-10-01	Wang et al.	Applicant
US6466844(B1)	2002-10-01	Ikeda et al.	Applicant
US6468265(B1)	2002-10-01	Evans et al.	Applicant
US6474434(B1)	2002-11-01	Bech	Applicant
US6480762(B1)	2002-11-01	Uchikubo et al.	Applicant
US6491701(B2)	2002-12-01	Tierney et al.	Applicant
US6496099(B2)	2002-12-01	Wang et al.	Applicant
US6496755(B2)	2002-12-01	Wallach et al.	Applicant
US6501740(B1)	2002-12-01	Sun et al.	Applicant
US6507773(B2)	2003-01-01	Parker et al.	Applicant
US6522906(B1)	2003-02-01	Salisbury et al.	Applicant
US6523629(B1)	2003-02-01	Buttz et al.	Applicant
US6526332(B2)	2003-02-01	Sakamoto et al.	Applicant
US6529765(B1)	2003-03-01	Franck et al.	Applicant
US6529802(B1)	2003-03-01	Kawakita et al.	Applicant
US6532404(B2)	2003-03-01	Colens	Applicant
US6535182(B2)	2003-03-01	Stanton	Applicant
US6535793(B2)	2003-03-01	Allard	Examiner
US6540039(B1)	2003-04-01	Yu et al.	Applicant
US6543899(B2)	2003-04-01	Covannon et al.	Applicant
US6549215(B2)	2003-04-01	Jouppi	Applicant
US6563533(B1)	2003-05-01	Colby	Applicant
US6580246(B2)	2003-06-01	Jacobs	Applicant
US6581798(B2)	2003-06-01	Liff et al.	Applicant
US6584376(B1)	2003-06-01	Van Kommer	Applicant
US6587750(B2)	2003-07-01	Gerbi et al.	Applicant
US6594269(B1)	2003-07-01	Polcyn	Applicant
US6594552(B1)	2003-07-01	Nowlin et al.	Applicant
US6602469(B1)	2003-08-01	Maus et al.	Applicant
US6604019(B2)	2003-08-01	Ahlin et al.	Applicant
US6604021(B2)	2003-08-01	Imai et al.	Applicant
US6611120(B2)	2003-08-01	Song et al.	Applicant
US6646677(B2)	2003-11-01	Noro et al.	Applicant
US6650748(B1)	2003-11-01	Edwards et al.	Applicant
US6666374(B1)	2003-12-01	Green et al.	Applicant
US6684129(B2)	2004-01-01	Salisbury et al.	Applicant
US6691000(B2)	2004-02-01	Nagai et al.	Applicant
US6710797(B1)	2004-03-01	McNelley et al.	Applicant
US6728599(B2)	2004-04-01	Wang et al.	Applicant
US6763282(B2)	2004-07-01	Glenn et al.	Applicant
US6764373(B1)	2004-07-01	Osawa et al.	Applicant
US6769771(B2)	2004-08-01	Trumbull	Applicant
US6781606(B2)	2004-08-01	Jouppi	Applicant
US6784916(B2)	2004-08-01	Smith	Applicant
US6785589(B2)	2004-08-01	Eggenberger et al.	Applicant
US6791550(B2)	2004-09-01	Goldhor et al.	Applicant
US6798753(B1)	2004-09-01	Doganata et al.	Applicant
US6799065(B1)	2004-09-01	Niemeyer	Applicant
US6799088(B2)	2004-09-01	Wang et al.	Applicant
US6804580(B1)	2004-10-01	Stoddard et al.	Applicant
US6804656(B1)	2004-10-01	Rosenfeld et al.	Applicant
US6810411(B1)	2004-10-01	Coughlin et al.	Applicant
US6836703(B2)	2004-12-01	Wang et al.	Applicant
US6839612(B2)	2005-01-01	Sanchez et al.	Applicant
US6840904(B2)	2005-01-01	Goldberg	Applicant
US6845297(B2)	2005-01-01	Allard	Examiner
US6852107(B2)	2005-02-01	Wang et al.	Applicant
US6853878(B2)	2005-02-01	Hirayama et al.	Applicant
US6853880(B2)	2005-02-01	Sakagami et al.	Applicant
US6871117(B2)	2005-03-01	Wang et al.	Applicant
US6879879(B2)	2005-04-01	Jouppi et al.	Applicant
US6888333(B2)	2005-05-01	Laby	Applicant
US6892112(B2)	2005-05-01	Wang et al.	Applicant
US6895305(B2)	2005-05-01	Lathan et al.	Applicant
US6898484(B2)	2005-05-01	Lemelson et al.	Applicant
US6914622(B1)	2005-07-01	Smith et al.	Applicant
US6925357(B2)	2005-08-01	Wang et al.	Applicant
US6951535(B2)	2005-10-01	Ghodoussi et al.	Applicant
US6952470(B1)	2005-10-01	Tioe et al.	Applicant
US6958706(B2)	2005-10-01	Chaco et al.	Applicant
US6965394(B2)	2005-11-01	Gutta et al.	Applicant
US6995664(B1)	2006-02-01	Darling	Applicant
US7030757(B2)	2006-04-01	Matsuhira et al.	Applicant
US7058689(B2)	2006-06-01	Parker et al.	Applicant
US7092001(B2)	2006-08-01	Schulz	Applicant
US7096090(B1)	2006-08-01	Zweig	Applicant
US7115102(B2)	2006-10-01	Abbruscato	Applicant
US7117067(B2)	2006-10-01	McLurkin et al.	Applicant
US7123285(B2)	2006-10-01	Smith et al.	Applicant
US7123974(B1)	2006-10-01	Hamilton	Applicant
US7123991(B2)	2006-10-01	Graf et al.	Applicant
US7127325(B2)	2006-10-01	Nagata et al.	Applicant
US7129970(B2)	2006-10-01	James et al.	Applicant
US7133062(B2)	2006-11-01	Castles	Applicant
US7142945(B2)	2006-11-01	Wang et al.	Applicant
US7142947(B2)	2006-11-01	Wang et al.	Applicant
US7151982(B2)	2006-12-01	Liff	Applicant
US7154526(B2)	2006-12-01	Foote et al.	Applicant
US7155306(B2)	2006-12-01	Haitin et al.	Applicant
US7156809(B2)	2007-01-01	Quy	Applicant
US7158859(B2)	2007-01-01	Wang et al.	Applicant
US7158860(B2)	2007-01-01	Wang et al.	Applicant
US7161322(B2)	2007-01-01	Wang et al.	Applicant
US7162338(B2)	2007-01-01	Goncalves et al.	Applicant
US7164969(B2)	2007-01-01	Wang et al.	Applicant
US7171286(B2)	2007-01-01	Wang et al.	Applicant
US7174238(B1)	2007-02-01	Zweig	Applicant
US7184559(B2)	2007-02-01	Jouppi	Applicant
US7188000(B2)	2007-03-01	Chiappetta et al.	Applicant
US7199790(B2)	2007-04-01	Rosenberg et al.	Applicant
US7202851(B2)	2007-04-01	Cunningham et al.	Applicant
US7206627(B2)	2007-04-01	Abovitz et al.	Applicant
US7215786(B2)	2007-05-01	Nakadai et al.	Applicant
US7227334(B2)	2007-06-01	Yang et al.	Applicant
US7256708(B2)	2007-08-01	Rosenfeld et al.	Applicant
US7262573(B2)	2007-08-01	Wang et al.	Examiner
US7289883(B2)	2007-10-01	Wang et al.	Applicant
US7292912(B2)	2007-11-01	Wang et al.	Applicant
US7321807(B2)	2008-01-01	Laski	Applicant
US7346429(B2)	2008-03-01	Goldenberg et al.	Applicant
US7382399(B1)	2008-06-01	McCall	Applicant
US7386730(B2)	2008-06-01	Uchikubo	Applicant
US7432949(B2)	2008-10-01	Remy et al.	Applicant
US7441953(B2)	2008-10-01	Banks	Applicant
US7525281(B2)	2009-04-01	Koyanagi et al.	Applicant
US7535486(B2)	2009-05-01	Motomura et al.	Applicant
US7593030(B2)	2009-09-01	Wang et al.	Applicant
US7624166(B2)	2009-11-01	Foote et al.	Applicant
US7719229(B2)	2010-05-01	Kaneko et al.	Applicant
US7761185(B2)	2010-07-01	Wang et al.	Applicant
US7769492(B2)	2010-08-01	Wang et al.	Applicant
US7813836(B2)	2010-10-01	Wang et al.	Applicant
US7831575(B2)	2010-11-01	Trossell et al.	Applicant
US7835775(B2)	2010-11-01	Sawayama et al.	Applicant
USRE42288(E)	2011-04-01	Degioanni	Applicant
US7924323(B2)	2011-04-01	Walker et al.	Applicant
US7982763(B2)	2011-07-01	King	Applicant
US8077963(B2)	2011-12-01	Wang et al.	Applicant
US8116910(B2)	2012-02-01	Walters et al.	Applicant
US8170241(B2)	2012-05-01	Roe et al.	Applicant
US8179418(B2)	2012-05-01	Wright et al.	Applicant
US8209051(B2)	2012-06-01	Wang et al.	Applicant
US2001/0002448(A1)	2001-05-01	Wilson et al.	Applicant
US2001/0010053(A1)	2001-07-01	Ben-Shachar et al.	Applicant
US2001/0034475(A1)	2001-10-01	Flach et al.	Applicant
US2001/0034544(A1)	2001-10-01	Mo	Applicant
US2001/0037163(A1)	2001-11-01	Allard	Applicant
US2001/0051881(A1)	2001-12-01	Filler	Applicant
US2001/0054071(A1)	2001-12-01	Loeb	Applicant
US2001/0055373(A1)	2001-12-01	Yamashita	Applicant
US2002/0015296(A1)	2002-02-01	Howell	Applicant
US2002/0027597(A1)	2002-03-01	Sachau	Applicant
US2002/0049517(A1)	2002-04-01	Ruffner	Applicant
US2002/0055917(A1)	2002-05-01	Muraca	Applicant
US2002/0057279(A1)	2002-05-01	Jouppi	Examiner
US2002/0058929(A1)	2002-05-01	Green	Applicant
US2002/0059587(A1)	2002-05-01	Cofano et al.	Applicant
US2002/0063726(A1)	2002-05-01	Jouppi	Applicant
US2002/0073429(A1)	2002-06-01	Beane et al.	Applicant
US2002/0082498(A1)	2002-06-01	Wendt et al.	Applicant
US2002/0095238(A1)	2002-07-01	Ahlin et al.	Applicant
US2002/0098879(A1)	2002-07-01	Rheey	Applicant
US2002/0104094(A1)	2002-08-01	Alexander et al.	Applicant
US2002/0111988(A1)	2002-08-01	Sato	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/0143923(A1)	2002-10-01	Alexander	Applicant
US2002/0177925(A1)	2002-11-01	Onishi et al.	Applicant
US2002/0183894(A1)	2002-12-01	Wang et al.	Applicant
US2002/0184674(A1)	2002-12-01	Xi et al.	Applicant
US2002/0186243(A1)	2002-12-01	Ellis et al.	Applicant
US2003/0030397(A1)	2003-02-01	Simmons	Applicant
US2003/0048481(A1)	2003-03-01	Kobayashi et al.	Applicant
US2003/0050733(A1)	2003-03-01	Wang et al.	Applicant
US2003/0060808(A1)	2003-03-01	Wilk	Applicant
US2003/0063600(A1)	2003-04-01	Noma et al.	Applicant
US2003/0069752(A1)	2003-04-01	Ledain et al.	Applicant
US2003/0100892(A1)	2003-05-01	Morley et al.	Applicant
US2003/0104806(A1)	2003-06-01	Ruef et al.	Applicant
US2003/0114962(A1)	2003-06-01	Niemeyer	Applicant
US2003/0126361(A1)	2003-07-01	Slater et al.	Applicant
US2003/0135203(A1)	2003-07-01	Wang et al.	Applicant
US2003/0144579(A1)	2003-07-01	Buss	Applicant
US2003/0144649(A1)	2003-07-01	Ghodoussi et al.	Applicant
US2003/0151658(A1)	2003-08-01	Smith	Applicant
US2003/0171710(A1)	2003-09-01	Bassuk et al.	Applicant
US2003/0174285(A1)	2003-09-01	Trumbull	Applicant
US2003/0180697(A1)	2003-09-01	Kim et al.	Applicant
US2003/0199000(A1)	2003-10-01	Valkirs et al.	Applicant
US2003/0206242(A1)	2003-11-01	Choi	Applicant
US2003/0216834(A1)	2003-11-01	Allard	Applicant
US2003/0220541(A1)	2003-11-01	Salisbury, Jr. et al.	Applicant
US2003/0220715(A1)	2003-11-01	Kneifel et al.	Applicant
US2003/0231244(A1)	2003-12-01	Bonilla et al.	Applicant
US2003/0232649(A1)	2003-12-01	Gizis et al.	Applicant
US2004/0010344(A1)	2004-01-01	Hiratsuka et al.	Applicant
US2004/0012362(A1)	2004-01-01	Tsurumi	Applicant
US2004/0013295(A1)	2004-01-01	Sabe et al.	Applicant
US2004/0019406(A1)	2004-01-01	Wang et al.	Applicant
US2004/0024490(A1)	2004-02-01	McLurkin et al.	Applicant
US2004/0041904(A1)	2004-03-01	Lapalme et al.	Applicant
US2004/0065073(A1)	2004-04-01	Nash	Applicant
US2004/0068657(A1)	2004-04-01	Alexander et al.	Applicant
US2004/0078219(A1)	2004-04-01	Kaylor et al.	Applicant
US2004/0080610(A1)	2004-04-01	James et al.	Applicant
US2004/0088077(A1)	2004-05-01	Jouppi et al.	Applicant
US2004/0093409(A1)	2004-05-01	Thompson et al.	Applicant
US2004/0098167(A1)	2004-05-01	Yi et al.	Applicant
US2004/0102167(A1)	2004-05-01	Shim et al.	Applicant
US2004/0117065(A1)	2004-06-01	Wang et al.	Applicant
US2004/0138547(A1)	2004-07-01	Wang et al.	Applicant
US2004/0143421(A1)	2004-07-01	Wang et al.	Applicant
US2004/0148638(A1)	2004-07-01	Weisman et al.	Applicant
US2004/0153211(A1)	2004-08-01	Kamoto et al.	Applicant
US2004/0157612(A1)	2004-08-01	Kim	Applicant
US2004/0162637(A1)	2004-08-01	Wang et al.	Applicant
US2004/0167666(A1)	2004-08-01	Wang et al.	Applicant
US2004/0167668(A1)	2004-08-01	Wang et al.	Applicant
US2004/0170300(A1)	2004-09-01	Jouppi	Applicant
US2004/0172301(A1)	2004-09-01	Mihai et al.	Applicant
US2004/0174129(A1)	2004-09-01	Wang et al.	Applicant
US2004/0175684(A1)	2004-09-01	Kaasa et al.	Applicant
US2004/0179714(A1)	2004-09-01	Jouppi et al.	Applicant
US2004/0189700(A1)	2004-09-01	Mandavilli et al.	Applicant
US2004/0201602(A1)	2004-10-01	Mody et al.	Applicant
US2004/0215490(A1)	2004-10-01	Duchon et al.	Applicant
US2004/0224676(A1)	2004-11-01	Iseki	Applicant
US2004/0230340(A1)	2004-11-01	Fukuchi et al.	Applicant
US2004/0240981(A1)	2004-12-01	Dothan et al.	Applicant
US2005/0003330(A1)	2005-01-01	Asgarinejad	Applicant
US2005/0007445(A1)	2005-01-01	Foote et al.	Applicant
US2005/0013149(A1)	2005-01-01	Trossell	Applicant
US2005/0021182(A1)	2005-01-01	Wang	Applicant
US2005/0021183(A1)	2005-01-01	Wang et al.	Applicant
US2005/0021187(A1)	2005-01-01	Wang et al.	Applicant
US2005/0021309(A1)	2005-01-01	Alexander et al.	Applicant
US2005/0024485(A1)	2005-02-01	Castles et al.	Applicant
US2005/0027567(A1)	2005-02-01	Taha	Applicant
US2005/0027794(A1)	2005-02-01	Decker	Applicant
US2005/0028221(A1)	2005-02-01	Liu et al.	Applicant
US2005/0035862(A1)	2005-02-01	Wildman et al.	Applicant
US2005/0038416(A1)	2005-02-01	Wang et al.	Applicant
US2005/0038564(A1)	2005-02-01	Burick	Applicant
US2005/0049898(A1)	2005-03-01	Hirakawa	Applicant
US2005/0052527(A1)	2005-03-01	Remy et al.	Applicant
US2005/0065435(A1)	2005-03-01	Rauch et al.	Applicant
US2005/0065438(A1)	2005-03-01	Miller	Applicant
US2005/0065659(A1)	2005-03-01	Tanaka et al.	Applicant
US2005/0065813(A1)	2005-03-01	Mishelevich et al.	Applicant
US2005/0071046(A1)	2005-03-01	Miyazaki et al.	Applicant
US2005/0083011(A1)	2005-04-01	Yang et al.	Applicant
US2005/0099493(A1)	2005-05-01	Chew	Applicant
US2005/0104964(A1)	2005-05-01	Bovyrin et al.	Applicant
US2005/0110867(A1)	2005-05-01	Schulz	Applicant
US2005/0122390(A1)	2005-06-01	Wang et al.	Applicant
US2005/0154265(A1)	2005-07-01	Miro et al.	Applicant
US2005/0182322(A1)	2005-08-01	Grispo	Applicant
US2005/0192721(A1)	2005-09-01	Jouppi	Applicant
US2005/0204438(A1)	2005-09-01	Wang et al.	Applicant
US2005/0212478(A1)	2005-09-01	Takenaka	Applicant
US2005/0219356(A1)	2005-10-01	Smith et al.	Applicant
US2005/0225634(A1)	2005-10-01	Brunetti et al.	Applicant
US2005/0231156(A1)	2005-10-01	Yan	Applicant
US2005/0232647(A1)	2005-10-01	Takenaka	Applicant
US2005/0267826(A1)	2005-12-01	Levy et al.	Applicant
US2005/0283414(A1)	2005-12-01	Fernandes et al.	Applicant
US2006/0007943(A1)	2006-01-01	Fellman	Applicant
US2006/0013263(A1)	2006-01-01	Fellman	Applicant
US2006/0013469(A1)	2006-01-01	Wang et al.	Applicant
US2006/0013488(A1)	2006-01-01	Inoue	Applicant
US2006/0029065(A1)	2006-02-01	Fellman	Applicant
US2006/0047365(A1)	2006-03-01	Ghodoussi et al.	Applicant
US2006/0048286(A1)	2006-03-01	Donato	Applicant
US2006/0052676(A1)	2006-03-01	Wang et al.	Applicant
US2006/0052684(A1)	2006-03-01	Takahashi et al.	Applicant
US2006/0064212(A1)	2006-03-01	Thorne	Applicant
US2006/0074525(A1)	2006-04-01	Close et al.	Applicant
US2006/0082642(A1)	2006-04-01	Wang et al.	Applicant
US2006/0087746(A1)	2006-04-01	Lipow	Applicant
US2006/0095158(A1)	2006-05-01	Lee et al.	Applicant
US2006/0095170(A1)	2006-05-01	Yang et al.	Applicant
US2006/0098573(A1)	2006-05-01	Beer et al.	Applicant
US2006/0103659(A1)	2006-05-01	Karandikar et al.	Applicant
US2006/0104279(A1)	2006-05-01	Fellman et al.	Applicant
US2006/0106493(A1)	2006-05-01	Niemeyer et al.	Applicant
US2006/0122482(A1)	2006-06-01	Mariotti et al.	Applicant
US2006/0142983(A1)	2006-06-01	Sorensen	Applicant
US2006/0161303(A1)	2006-07-01	Wang et al.	Applicant
US2006/0164546(A1)	2006-07-01	Adachi	Applicant
US2006/0173712(A1)	2006-08-01	Joubert	Applicant
US2006/0178776(A1)	2006-08-01	Feingold et al.	Applicant
US2006/0189393(A1)	2006-08-01	Edery	Applicant
US2006/0195569(A1)	2006-08-01	Barker	Applicant
US2006/0259193(A1)	2006-11-01	Wang et al.	Applicant
US2006/0293788(A1)	2006-12-01	Pogodin	Applicant
US2007/0021871(A1)	2007-01-01	Wang et al.	Applicant
US2007/0046237(A1)	2007-03-01	Lakshmanan et al.	Applicant
US2007/0050937(A1)	2007-03-01	Song et al.	Applicant
US2007/0064092(A1)	2007-03-01	Sandbeg et al.	Applicant
US2007/0078566(A1)	2007-04-01	Wang et al.	Applicant
US2007/0112700(A1)	2007-05-01	Den et al.	Applicant
US2007/0117516(A1)	2007-05-01	Saidi et al.	Applicant
US2007/0120965(A1)	2007-05-01	Sandberg et al.	Applicant
US2007/0122783(A1)	2007-05-01	Habashi	Applicant
US2007/0135967(A1)	2007-06-01	Jung et al.	Applicant
US2007/0142964(A1)	2007-06-01	Abramson	Applicant
US2007/0176060(A1)	2007-08-01	White et al.	Applicant
US2007/0192910(A1)	2007-08-01	Vu et al.	Applicant
US2007/0197896(A1)	2007-08-01	Moll et al.	Applicant
US2007/0198128(A1)	2007-08-01	Ziegler et al.	Applicant
US2007/0199108(A1)	2007-08-01	Angle et al.	Applicant
US2007/0216347(A1)	2007-09-01	Kaneko et al.	Applicant
US2007/0250212(A1)	2007-10-01	Halloran et al.	Applicant
US2007/0262884(A1)	2007-11-01	Goncalves et al.	Applicant
US2007/0273751(A1)	2007-11-01	Sachau	Applicant
US2007/0291109(A1)	2007-12-01	Wang et al.	Applicant
US2007/0291128(A1)	2007-12-01	Wang et al.	Applicant
US2008/0011904(A1)	2008-01-01	Cepollina et al.	Applicant
US2008/0065268(A1)	2008-03-01	Wang et al.	Applicant
US2008/0082211(A1)	2008-04-01	Wang et al.	Applicant
US2008/0133052(A1)	2008-06-01	Jones et al.	Applicant
US2008/0201017(A1)	2008-08-01	Wang et al.	Applicant
US2008/0215987(A1)	2008-09-01	Alexander et al.	Applicant
US2008/0229531(A1)	2008-09-01	Takida	Applicant
US2008/0255703(A1)	2008-10-01	Wang et al.	Applicant
US2008/0263451(A1)	2008-10-01	Portele et al.	Applicant
US2008/0269949(A1)	2008-10-01	Norman et al.	Applicant
US2008/0281467(A1)	2008-11-01	Pinter	Applicant
US2009/0030552(A1)	2009-01-01	Nakadai et al.	Applicant
US2009/0055023(A1)	2009-02-01	Walters et al.	Applicant
US2009/0105882(A1)	2009-04-01	Wang et al.	Applicant
US2009/0125147(A1)	2009-05-01	Wang et al.	Examiner
US2009/0237317(A1)	2009-09-01	Rofougaran	Applicant
US2009/0240371(A1)	2009-09-01	Wang et al.	Applicant
US2009/0259339(A1)	2009-10-01	Wright et al.	Applicant
US2010/0010672(A1)	2010-01-01	Wang et al.	Applicant
US2010/0010673(A1)	2010-01-01	Wang et al.	Applicant
US2010/0019715(A1)	2010-01-01	Roe et al.	Applicant
US2010/0070079(A1)	2010-03-01	Mangaser et al.	Applicant
US2010/0073490(A1)	2010-03-01	Wang et al.	Applicant
US2010/0076600(A1)	2010-03-01	Cross et al.	Applicant
US2010/0115418(A1)	2010-05-01	Wang et al.	Applicant
US2010/0116566(A1)	2010-05-01	Ohm et al.	Applicant
US2010/0131103(A1)	2010-05-01	Herzog et al.	Applicant
US2010/0191375(A1)	2010-07-01	Wright et al.	Applicant
US2010/0268383(A1)	2010-10-01	Wang et al.	Applicant
US2010/0323783(A1)	2010-12-01	Nonaka et al.	Applicant
US2011/0050841(A1)	2011-03-01	Wang et al.	Applicant
US2011/0071702(A1)	2011-03-01	Wang et al.	Applicant
US2011/0172822(A1)	2011-07-01	Ziegler et al.	Applicant
US2011/0187875(A1)	2011-08-01	Sanchez et al.	Applicant
US2011/0190930(A1)	2011-08-01	Hanrahan et al.	Applicant
US2011/0218674(A1)	2011-09-01	Stuart et al.	Applicant
US2011/0245973(A1)	2011-10-01	Wang et al.	Applicant
US2011/0292193(A1)	2011-12-01	Wang et al.	Applicant
US2011/0301759(A1)	2011-12-01	Wang et al.	Applicant
US2012/0023506(A1)	2012-01-01	Maeckel et al.	Applicant
US2012/0072023(A1)	2012-03-01	Ota	Applicant
US2012/0092157(A1)	2012-04-01	Tran	Applicant
CA2289697(A1)	1998-11-01		Applicant
CN1554193(A)	2004-12-01		Applicant
CN1554985(A)	2004-12-01		Applicant
CN101106939(A)	2008-01-01		Applicant
CN101390098(A)	2009-03-01		Applicant
CN101507260(A)	2009-08-01		Applicant
CN101730894(A)	2010-06-01		Applicant
CN101866396(A)	2010-10-01		Applicant
CN101978365(A)	2011-02-01		Applicant
CN102203759(A)	2011-09-01		Applicant
CN101106939(B)	2011-11-01		Applicant
EP466492(A2)	1992-01-01		Applicant
EP94/488673(A2)	1992-06-01		Applicant
EP981905(B1)	2002-01-01		Applicant
EP1262142(A2)	2002-12-01		Applicant
EP1536660(B2)	2004-09-01		Applicant
EP1536660(A2)	2005-06-01		Applicant
EP2005/1573406(A2)	2005-09-01		Applicant
EP2005/1594660(A2)	2005-11-01		Applicant
EP2007/179464(A2)	2007-06-01		Applicant
EP2007/1800476(A2)	2007-06-01		Applicant
EP2007/1856644(A2)	2007-11-01		Applicant
EP2008/1928310(A2)	2008-06-01		Applicant
EP2009/2027716(A2)	2009-02-01		Applicant
EP2010/2145274(A1)	2010-01-01		Applicant
EP2010/2214111(A2)	2010-08-01		Applicant
EP2010/2263158(A2)	2010-12-01		Applicant
EP2011/2300930(A2)	2011-03-01		Applicant
EP2011/2342651(A2)	2011-07-01		Applicant
JO2007/081646(A)	2007-03-01		Applicant
JP2007-213753(A)	1995-08-01		Applicant
JP2007-248823(A)	1995-08-01		Applicant
JP7-257422(A)	1995-10-01		Applicant
JP8-084328(A)	1996-03-01		Applicant
JP96/8320727(A)	1996-12-01		Applicant
JP9-267276(A)	1997-10-01		Applicant
JP10079097(A)	1998-03-01		Applicant
JP10288689(A)	1998-10-01		Applicant
JP2000-032319(A)	2000-01-01		Applicant
JP2000/049800(A)	2000-02-01		Applicant
JP2000/079587(A)	2000-03-01		Applicant
JP2000/196876(A)	2000-07-01		Applicant
JP2000-235423(A)	2000-08-01		Applicant
JP2001/125641(A)	2001-05-01		Applicant
JP2001-147718(A)	2001-05-01		Applicant
JP2001/179663(A)	2001-07-01		Applicant
JP2001-198865(A)	2001-07-01		Applicant
JP2001-198868(A)	2001-07-01		Applicant
JP2001-199356(A)	2001-07-01		Applicant
JP2000-188124	2002-01-01		Applicant
JP2002-000574(A)	2002-01-01		Applicant
JP2002-046088(A)	2002-02-01		Applicant
JP2002/1129670(A)	2002-04-01		Applicant
JP2002/101333(A)	2002-05-01		Applicant
JP2002-305743(A)	2002-10-01		Applicant
JP2002-355779(A)	2002-12-01		Applicant
JP2004/524824(T)	2004-08-01		Applicant
JP2004/261941(A)	2004-09-01		Applicant
JP2004/289379(A)	2004-10-01		Applicant
JP2005/028066(A)	2005-02-01		Applicant
JP2005/059170(A)	2005-03-01		Applicant
JP2006/508806(A)	2006-03-01		Applicant
JP2006/109094(A)	2006-04-01		Applicant
JP2006/224294(A)	2006-08-01		Applicant
JP2006/246438(A)	2006-09-01		Applicant
JP2010/064154(A)	2010-03-01		Applicant
JP2010/0532109(A)	2010-09-01		Applicant
JP2010/246954(A)	2010-11-01		Applicant
KR2006/0037979(A)	2006-05-01		Applicant
KR2009/0012542(A)	2009-02-01		Applicant
KR2010/0019479(A)	2010-02-01		Applicant
KR2010/0139037(A)	2010-12-01		Applicant
WO93/06690(A1)	1993-04-01		Applicant
WO98/51078(A)	1998-11-01		Applicant
WO99/67067(A1)	1999-12-01		Applicant
WO/33726(A3)	2000-06-01		Applicant
WO3/077745(A)	2003-09-01		Applicant
WO2004/008738(A1)	2004-01-01		Applicant
WO2004/012018(A2)	2004-02-01		Applicant
WO2004/075456(A2)	2004-09-01		Applicant
WO2006/012797(A1)	2006-02-01		Applicant
WO2006/078611(A1)	2006-04-01		Applicant
WO2006044847(A2)	2006-04-01		Applicant
WO2007/041295(A1)	2007-04-01		Applicant
WO2007/041295(A2)	2007-04-01		Applicant
WO2007/041038(A1)	2007-06-01		Applicant
WO2008/100272(A2)	2008-08-01		Applicant
WO2008/100272(A3)	2008-10-01		Applicant
WO2009/117274(A2)	2009-09-01		Applicant
WO2009/128997(A1)	2009-10-01		Applicant
WO2009/145958(A2)	2009-12-01		Applicant
WO2010/006205(A1)	2010-01-01		Applicant
WO2010/006211(A1)	2010-01-01		Applicant
WO2010/033666(A1)	2010-03-01		Applicant
WO2010/047881(A1)	2010-04-01		Applicant
WO2010/062798(A1)	2010-06-01		Applicant
WO2010/065257(A1)	2010-06-01		Applicant
WO2010/120407(A1)	2010-10-01		Applicant
WO2011/028589(A2)	2011-03-01		Applicant
WO2011/028589(A3)	2011-04-01		Applicant
WO2011/097130(A2)	2011-08-01		Applicant
WO2011/097132(A2)	2011-08-01		Applicant
WO2011/109336(A2)	2011-09-01		Applicant
WO2011/097132(A3)	2011-12-01		Applicant
WO2011/149902(A2)	2011-12-01		Applicant

Non-Patent Literature (144)

Knight et al, “Active Visual Alignment of a Mobile Stereo Camera Platform,” Apr. 24-28, 2000, Proceedings of the IEEE International Conference on Robotics and Automation, San Francisco, pp. 3202-3208.Examiner
Al-Kassab, “A Review of Telemedicine”, Journal of Telemedicine and Telecare, 1999, vol. 5, Supplement 1.Applicant
F. Ando et al., “A Multimedia Self-service Terminal with Conferencing Functions”, 1995, IEEE, pp. 357-362.Applicant
Android Amusement Corp., “What Marketing Secret . . . Renting Robots from Android Amusement Corp!”, (Advertisement) 1982.Applicant
Applebome, “Planning Domesticated Robots for Tomorrow's Household”, New York Times, Mar. 4, 1982, pp. 21 and 23, http://www.theoldrobots.com/images17/dc17.JPG.Applicant
Baltus et al., “Towards Personal Service Robots for the Elderly, Proceedings for the Elderly Workshop on Interactive Robots and Entertainment”, 2000, Computer Science and Robotics, http://www.cs.cmu.edu/thrun/papers/thrun.nursebot-early.pdfApplicant
Bar-Cohen et al., Virtual reality robotic telesurgery simulations using MEMICA haptic system, Mar. 5, 2001, Internet, pp. 1-7.Applicant
Bartholomew, “An Apothecary's Pharmacy”, 1230-1240 http://classes.bnf.fr/ema/grands/034.htm.Applicant
Bauer, Jeffrey C., “Service Robots in Health Care: The Evolution of Mechanical Solutions to Human Resource Problems”, Jun. 2003.Applicant
Bauer, John et al., “Remote telesurgical mentoring: feasibility and efficacy”, 2000, IEEE, pp. 1-9.Applicant
Bischoff, “Design Concept and Realization of the Humanoid Service Robot HERMES”, Field and Service Robotics, Springer, London, 1998, pp. 485-492.Applicant
Blackwell, Gerry, “Video: A Wireless LAN Killer App?”, Apr. 16, 2002, Internet pp. 1-3.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
Brooks, Rodney, Abstracts from Flesh & Machines, How Robots Will Change Us, “Remote Presence”, p. 131-147, Feb. 2002.Applicant
Celi et al., “The eICU: It's not just telemedicine”, Critical Care Medicine, vol. 29, No. 8 (Supplement), Aug. 2001.Applicant
Cheetham, Anastasia et al., “Interface Development for a Child's Video Conferencing Robot”, 2000, pp. 1-4.Applicant
Cleary et al., “State of the art in surgical robotics: Clinical applications and technology challenges”, Feb. 24, 2002 Internet, pp. 1-26.Applicant
CNN, “Floating ‘droids’ to roam space corridors of the future”, Jan. 12, 2000, Internet, pp. 1-4.Applicant
CNN.com/Technology,“ Paging R.Robot: Machine helps doctors with patients”, Sep. 30, 2003, Internet, 1-3.Applicant
Crowley, “Hello to Our Future”, AARP Bulletin, Jan. 2000 http://www.cs.cmu.ed/-nursebot/web/press/aarp—99—14/millennium.html.Applicant
Dalton, “Techniques for Web Telerobotics”, PhD Thesis, University of Western Australia, 2001, pp. 27-62, 149-191; http://telerobot.mech.uwa.edu.au/information.html, http://catalogue.library.uwa.edu.au/search.Applicant
Davies, “Robotics in Minimally Invasive Surgery”, 1995, Internet, pp. 5/1-5/2.Applicant
Discovery Channel Canada, “Inventing the Future: 2000 Years of Discovery”, Jan. 2, 2000 (Video/Transcript).Applicant
Elhajj et al., “Supermedia in Internet-based telerobotic operations”, 2001, Internet, pp. 1-14.Applicant
Elhajj et al., “Synchronization and Control of Supermedia Transmission Via the Internet”, Proceedings of 2001 International Symposium on Intelligent Multimedia, Video and Speech Processing, May 2-4, 2001, Hong Kong.Applicant
Ellison et al., “Telerounding and Patient Satisfaction Following Surgery”.Applicant
Fels, “Developing a Video-Mediated Communication System for Hospitalized Children”, Telemedicine Journal, vol. 5, No. 2, 1999.Applicant
Fetterman, “Videoconferencing over the Internet”, 2001, Internet, pp. 1-8.Applicant
Fiorini, “Health Care Robotics: A Progress Report”, IEEE International Conference on Robotics and Automation, pp. 1271-1276, Apr. 1997.Applicant
Ghiasi, “A Generic Web-based Teleoperations Architecture: Details and Experience”, SPIE Conference on Telemanipulator and Telepresence Technologies VI, Sep. 1999.Applicant
Goldberg et al., “Collaborative Teleoperation via the Internet”, IEEE International Conference on Robotics and Automation, Apr. 2000, San Francisco, California.Applicant
Goldberg, “Desktop Teleoperation via the World Wide Web, Proceedings of the IEEE International Conference on Robotics and Automation”, 1995, pp. 654-659 http://citeseer.ist.psu.edu/cache/papers/cs/5/ftp:zSzzSzusc.eduzSzpubzSziriszSzraiders.pdf/gol.Applicant
Goldberg, “More Online Robots, Robots that Manipulate”, Internet, Updated Aug. 2001 http://ford.ieor.berkeley.edu/ir/robots—a2.html.Applicant
Goldenberg, et al., “Telemedicine in Otolaryngology”, American Journal of Otolaryngology, vol. 23, No. 1, 2002, pp. 35-43.Applicant
Goldman, Lea, “Machine Dreams”, Entrepreneurs, Forbes, May 27, 2002.Applicant
Gump, Michael D., “Robot Technology Improves VA Pharmacies”, 2001, Internet, pp. 1-3.Applicant
Han, et al., “Construction of an Omnidirectional Mobile Robot Platform Based on Active Dual-Wheel Caster Mechanisms and Development of a Control Simulator”, 2000, Kluwer Acedemic Publishers, vol. 29, pp. 257-275.Applicant
Handley, “RFC 2327—SDP: Session Description Protocol”, Apr. 1998 http://www.faqs.org/rfcs/rfc2327.html.Applicant
Hanebeck, “ROMAN: a mobile Robotic Assistant for Indoor Service Applications”, Proceedings of the 1997 IEEE/RSJ International Conference on Intelligent Robots and Systems, 1997.Applicant
Harmo et al., “Moving Eye—Interactive Telepresence Over Internet With a Ball Shaped Mobile Robot”, 2000.Applicant
Haule et al., “Control Scheme for Delayed Teleoperation Tasks”, May 17, 1995, Proceedings of the Pacific Rim Conference on Communications, Computer and Signal Processing.Applicant
Hees, William P., “Communications Design for a Remote Presence Robot”, Jan. 14, 2002.Applicant
Holmberg, “Development of a Holonomic Mobile Robot for Mobile Manipulation Tasks”, International Conference on Field and Service Robotics, Pittsburgh, PA, Aug. 1999.Applicant
Ishiguro, “Integrating a Perceptual Information Infrastructure with Robotic Avatars: A Framework for Tele-Existence” Proceeding of IEEE Conference on Intelligent Robots and Systems, http://www.ai.soc.i.kyoto-u.ac.jp/services/publications/99/99conf/07.pdf.Applicant
Ishihara, Ken et al., “Intelligent Microrobot DDS (Drug Delivery System) Measured and Controlled by Ultrasonics”, Nov. 3-5, 1991, IEEE/RSJ, pp. 1145-1150, vol. 2.Applicant
ITU, “ITU-T H.323 Packet-based multimedia communications”, ITU, Feb. 1998, http://www.itu.int/rec./T-REC-H.323-199802-S/en.Applicant
Ivanova, Natali, “Master's thesis: Internet Based Interface for Control of a Mobile Robot”, Department of Numerical Analysis and Computer Science.Applicant
Jenkins, “Telehealth Advancing Nursing Practice”, Nursing Outlook, Mar./Apr. 2001, vol. 49, No. 2.Applicant
Johanson, “Supporting video-mediated communication over the Internet”, Chalmers University of Technology, Dept of Computer Engineering, Gothenburg, Sweden, 2003.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”, CSCW '02, Nov. 16-20, 2002, New Orleans LA.Applicant
Kanehiro, Fumio et al., “Virtual Humanoid Robot Platform to Develop Controllers of Real Humanoid Robots without Porting”, 2001, IEEE, pp. 3217-3276.Applicant
Kaplan et al., “An Internet Accessible Telepresence”.Applicant
Keller et al., “Raven Interface Project”, Fall 2001 http://upclose.lrdc.pittedu/people/louw—assets/Raven—Slides.pps.Applicant
Khatib, “Robots in Human Environments”, Proc. International Conference on Control, Automation, Robotics, and Vision, ICRACV2000, Dec. 2000, Singapore, pp. 454-457.Applicant
Kuzuoka et al., “Can the GestureCam Be a Surrogate?”.Applicant
Lane, “Automated Aides”, Newsday, Oct. 17, 2000, http://www.cs.cum.edu/-nursebot/web/press/nd4380.htm.Applicant
Lee et al., “A novel method of surgical instruction: International telementoring”, 1998, Internet pp. 1-4.Applicant
Lim, Hun-ok et al., “Control to Realize Human-like Walking of a Biped Humanoid Robot”, IEEE 2000, pp. 3271-3276.Applicant
Linebarger, John M. et al., “Concurrency Control Mechanisms for Closely Coupled Collaboration in Multithreaded Virtual Environments”, Presence, Special Issue on Advances in Collaborative VEs (2004).Applicant
Loeb, Gerald, “Virtual Visit: Improving Communication for Those Who Need It Most”, 2001.Applicant
Long, “HelpMate Robotics, Inc. (Formerly Transitions Research Corporation) Robot Navigation Technology”, NIST Special Publication 950-1, Mar. 1999, http://www.atp.nist.gov/eao/sp950-1/helpmate.htm.Applicant
Luna, Nancy, “Robot a new face on geriatric care”, OC Register, Aug. 6, 2003.Applicant
Mack, “Minimally invasive and robotic surgery”, 2001, Internet IEEE, pp. 568-572.Applicant
Mair, “Telepresence—The Technology and Its Economic and Social Implications”, IEEE Technology and Society, 1997.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
Meng et al., “E-Service Robot in Home Healthcare”, Proceedings of the 2000 IEEE/RSJ, International Conference on Intelligent Robots and Systems, 2000, pp. 832-837.Applicant
Michaud, “Introducing ‘Nursebot’”, The Boston Globe, Sep. 11, 2001, pp. 1-5, http://www.cs.cmu.edu/nursebot/web/press/globe—3—01/index.html.Applicant
Mobile Robotics Research Group, “Mobile Robotics Research Group”, 2000 Internet, pp. 1-2, Edinburgh.Applicant
Montemerlo, “Telepresence: Experiments in Next Generation Internet”, CMU Robotics Institute, Oct. 20, 1998, http://www.ri.cmu.edu/creative/archives.htm (Video/Transcript).Applicant
Murphy, “Introduction to A1 Robotics”, 2000.Applicant
Nakajima et al., “A Multimedia Teleteaching System sing an Electronic Whiteboard for Two-Way Communication of Motion Videos and Chalkboards”, 1993, IEEE, pp. 436-441.Applicant
“National Energy Research Scientific Computing Center, Berkeley Lab's RAGE Telepresence Robot Captures R&D100 Award”, Jul. 2, 2002, http://www.nersc.gov/news/newsroom/RAGE070202.php.Applicant
Nomadic Technologies, Inc., “Nomad XR4000 Hardware Manual”, Mar. 1999.Applicant
Ogata et al., “Emotional Communication Robot: WAMOEBA-2R—Emotion Model and Evaluation Experiments”, 1999, Internet, pp. 1-16.Applicant
Ogata et al., “Development of Emotional Communication Robot: WAMOEBA-2r—Experimental evaluation . . . ”, 2000 IEEE, pp. 175-180.Applicant
Oh et al., “Autonomous Battery Recharging for Indoor Mobile Robots”, Proceedings of Australian Conference on Robotics and Automation, 2000, http://users.rsise.anu.edu.au/rsl/rsl—papers/ACRA2000/Auto—Recharge—Paper.pdf.Applicant
Ojha, Anad, “An application of Virtual Reality in Rehabilitation”, Jan. 1994, IEEE, pp. 4-6.Applicant
Paulos et al., “A World Wide Web Telerobotic Remote Environment Browser”, http://vive.cs.berkeley.edu/capek, 1995.Applicant
Paulos, “Designing Personal Tele-embodiment”, IEEE International Conference on Robotics and Automation, 1998, http://www.prop.org/papers/icra98.pdf.Applicant
Paulos, Eric John, “Personal Tele-Embodiment”, UC Berkeley, Fall 2001.Applicant
Paulos, “PRoP: Personal Roving Presence”, ACM:CHI Proceedings of CHI '98, http://www.prop.org/papers/chi98.pdf.Applicant
Paulos, Video of PRoP 2 at Richmond Field Station, www.prop.org.May 2001, Printout of Home Page of Website and two-page Transcript of the audio portion of said PRoP Video.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
Pin.et al., “A New Family of Omnidirectional and Holonomic Wheeled Platforms for Mobile Robots”, IEEE, vol. 10, No. 4, Aug. 1994.Applicant
Rovetta et al., “A New Telerobotic Application: Remote Laparoscopic Surgery Using Satellites and Optical Fiber Networks for Data Exchange”, Jun. 1, 1996, International Journal of Robotics Research, pp. 267-279.Applicant
Roy et al., “Towards Personal Service Robots for the Elderly”, Internet, Mar. 7, 2002.Applicant
Sandt, Frederic et al., “Perceptions for a Transport Robot in Public Environments”, 1997, IROS '97.Applicant
Schaeffer, “Care-O-bot: A System for Assisting Elderly or Disabled Persons in Home Environments”, Proceedings of AAATE-99, 1999, http://morpha.de/download/publications/IPA—Systems—For—AssistingElderly—or—DisabledPersons—AAATE1999.pdf.Applicant
Schulz, “Web Interfaces for Mobile Robots in Public Places”, Robotics & Automation Magazine, IEEE, vol. 7, Issue 1, Mar. 2000.Applicant
Shimoga et al., Touch and force reflection for telepresence surgery, 1994, IEEE, pp. 1049-1050.Applicant
Siegwart, “Interacting Mobile Robots on the Web”, Proceedings of the 1999 IEEE International Conference on Robotics and Automation, May 1999.Applicant
Simmons, “Xavier: An Autonomous Mobile Robot on the Web”, IEEE Robotics and Automation Magazine, 1999, pp. 43-48.Applicant
Spawar Systems Center, “Robart”, 1998, San Diego, CA, http://web.archive.org/web/*/http://www.nosc.mil/robots/land/robart/robart.html http://web.archive.org/web/19981202205636/http://www.nosc.mil/robots/land/robart/robart.html.Applicant
Stephenson, Gary, “Dr. Robot Tested at Hopkins”, Aug. 5, 2003, Internet, pp. 1-2.Applicant
Stoianovici et al., “Robotic Tools for Minimally Invasive Urologic Surgery”, Dec. 2002, Internet, 1-17.Applicant
Suplee, “Mastering the Robot”, The Washington Post, p. A01, Sep. 17, 2000 http://www.cs.cmu.edu-nursebot/web/press/wash/index.html.Applicant
Tahboub, Karim A. et al., “Dynamics Analysis and Control of a Holonomic Vehicle With Continously Variable Transmission”, Mar. 2002, Journal of Dynamic Systems, Measurement, and Control, ASME vol. 124, pp. 118-126.Applicant
Tendick et al., “Human-Machine Interfaces for Minimally Invasive Surgery”, 1997, IEEE, pp. 2771-2776.Applicant
Thrun et al, “Probabilistic Algorithms and the Interactive Museum Tour-Guide Robot Minerva”, 2000, Internet pp. 1-35.Applicant
Tzafestas, et al., “VR-based Teleoperation of a Mobile Robotic Assistant: Progress Report”, Nov. 2000, Internet, pp. 1-23.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
Weiss et al., Telework and video-mediated communication: Importance of real-time, interactive communication for workers with disabilities, pp. 1-4, California State University Northridge, http://www.csun.edu/cod/conf/1999/proceedings/session0238.html.Applicant
West et al., “Design of Ball Wheel Mechanisms for Omnidirectional Vehicles with Full Mobility and Invariant Kinematics”, Journal of Mechanical Design, vol. 119, pp. 153-161, Jun. 1997.Applicant
Yamasaki et al., Applying Personal Robots and Active Interface to Video Conference Systems, 1995, Internet, pp. 243-248.Applicant
Yamauchi et al., PackBot: A Versatile Platform for Military Robotics, 2004, Internet, pp. 1-10.Applicant
Yong et al., “Robot task execution with telepresence using virtual reality technology”, 1998, Internet, pp. 1-9.Applicant
Zamrazil, Kristie, “Telemedicine in Texas: Public Policy Concerns”, House Research Organization Focus Report, Texas House of Representatives, No. 76-22, May 5, 2000 http://www.hro.house.state.tx.us/focus/telemed.pdf.Applicant
Zipperer, Lorri, “Robotic dispensing system”, 1999, Internet, pp. 1-2.Applicant
Zorn, Benjamin G., “Ubiquitous Telepresence”, http://www.cs.colorado.edu/˜zorn/ut/vision/vision.html, Mar. 5, 1996.Applicant
Linebarger, et al., “Concurrency Control Mechanisms for Closely Coupled Collaboration in Multithreaded Virtual Environments”, Presence, Special Issue on Advances in Collaborative VEs, 2004.Applicant
Yamauchi, “PackBot: A Versatile Platform for Military Robotics”, Internet, 2004, pp. 1-10.Applicant
Yong, et al., “Robot task execution with telepresence using virtual reality technology”, Internet, 1998, pp. 1-8.Applicant
Zamrazil, “Telemedicine in Texas: Public Policy Concerns”, House Research Organization Focus Report, Texas House of Representatives, http://www.hro.house.state.tx.us/focus/telemed.pdf, May 5, 2000, pp. 76-22.Applicant
Zipperer, “Robotic dispensing system”, ISMP Medication Safety Alert! vol. 4, Issue 17, Aug. 25, 1999, pp. 1-2.Applicant
Zorn, “Ubiquitous Telepresence”, http://www.cs.colorado.edu/-zorn/utlvision/vision.html, Mar. 3, 1996.Applicant
Barrett, “Video Conferencing Business Soars as Companies Cut Travel; Some Travel Cuts Are Permanent”, http://www.ivci.com/international—videoconferencing—news—videoconferencing—news—19.html, Mar. 13, 2002.Applicant
Brooks, “A Robust Layered Control System for a Mobile Robot,” IEEE Journal of Robotics and Automation, 2 (1), Mar. 1986, 10 pgs.Applicant
Candelas, et al., “Flexible virtual and remote laboratory for teaching Robotics”, FORMATEX 2006; Proc. Advance in Control Education Madrid, Spain, Jun. 2006, pp. 21-23.Applicant
Davis, “Meet iRobot, The Smartest Webcam on Wheels,” Wired Magazine, 8.09, http://www.wired.com/wired/archive/8.09/irobot—pr.html, Sep. 2000, 2 pgs.Applicant
Dean, et al., “1992 AAAI Robot Exhibition and Competition,” AI Magazine, Spring 1993, 10 pgs.Applicant
“Defendant VGo Communications, Inc.'s Invalidity Contentions Pursuant to the Feb. 27, 2012 Civil Minute Order”, May 2, 2012.Applicant
“Defendant-Counterclaimant VGo Communications, Inc.'s Supplemental Invalidity Contentions Pursuant to the Feb. 27, 2012 Civil Minute Order”, May 14, 2012.Applicant
DiGiorgio, “Is Your Emergency Department of the Leading Edge?”, Internet, 2005, pp. 1-4.Applicant
Dudenhoeffer, et al., “Command and Control Architectures for Autonomous Micro-Robotic Forces”, http://www.inl.gov/technicalpublications/Documents/3157051.pdf, Apr. 2001.Applicant
Elhajj, “Real-Time Haptic Feedback in Internet-Based Telerobotic Operation”, IEEE International Conference on Electro/Information Technology, http://www.egr.msu.edu/˜ralab-web/cgi—bin/internet-teleoperation.php, Jun. 2000.Applicant
Fong, “Collaborative Control: A Robot-Centric Model for Vehicle Teleoperation”, The Robotics Institute Carnegie Mellon University, http://web.archive.org/web/20030504040803/www.ricmu.edu/cgi-bin/tech—reports.cgi?year=2001&text=0, Nov. 2001.Applicant
Grow, “Office Coworker Robot,” Time Magazine, http://www.time.com/time/specials/packages/article/0,28804,1936165—1936255—1936640,00.html, Nov. 19, 2001, 2 pgs.Applicant
ITU, “ITU-T H.281 A Far End Camera Control Protocol for Videoconferences using H.224”, http://www.itu.int/rec/T-RECHch.281-199411-l/en, Nov. 1994.Applicant
ITU, “ITU-T H.450.11 Call Intrusion Supplementary Service for H.323”, http://www.itu.int/rec/T-RECH.450.11-200103-I/en, Mar. 2001.Applicant
ITU, “ITU-T H.450.9 Call Completion Supplementary Services for H.323”, http://www.itu.int/rec/T-RECH.450.9-200011-I/en, Nov. 2000.Applicant
Keller, et al., “Raven Interface Project”, Fall 2001, http://upclose.lrdc.pitt.edu/people/louw—assets/Raven—Slides.pps , Fall 2001.Applicant
Knight, et al., “Active Visual Alignment of a Mobile Stereo Camera Platform”, Proceedings of the IEEE, International Conference on Robotics and Automation, San Francisco, Apr. 24-28, 2000, pp. 3202-3208.Applicant
Metz, “HP Labs”, PCMAG.com, http://www.pcmag.com/article2/0,2817,1130820,00.asp, Jul. 1, 2003.Applicant
Picturetel, “PictureTel Live200 for Windows NT Product Guide”, http://support.polycom.com/global/documents/support/user/products/video/live200—live2OONT—product—guide.pdf, Nov. 1994.Applicant
“PictureTel Adds New Features and Functionality to Its Award-Winning Live200 Desktop Videoconferencing System”, PR Newswire Association, LLC, Gale, Cengage Learning, http://www.thefreelibrary.com/PictureTel+Adds+New+Features+And+Functionality+To+Its+Award-Winning...-a019512804, Jun. 13, 1997.Applicant
Roach, “Automatic Call Back Service in SIP”, http://tools.ietf.org/pdf/draftroach-sip-acb-00.pdf, Mar. 2000.Applicant
Salemi, et al., “MILO: Personal robot platform”, Internet, 2005, pp. 1-6.Applicant
Summers, “Microsoft NetMeeting 3 Features excerpt from Official Microsoft NetMeeting 3.0 Book”, http://technet.microsoft.com/en-us/library/cc723477.aspx#XSLTsection121121120120, excerpt from Microsoft Press http://www.computerbooksonline.com/abook.asp?i=0735605823, Mar. 1999.Applicant
U.S. Appl. No. 10/783,760, filed Feb. 20, 2004, Wang, et al., 48 pgs.Applicant
U.S. Appl. No. 60/449,762, filed Feb. 24, 2003, Wang, et al., 28 pgs.Applicant
Weiss, et al., “PEBBLES: A Personal Technology for Meeting Education, Social and Emotional Needs of Hospitalised Children”, Personal and Ubiquitous Computing 5, Springer-Verlag London Ltd., 2001, pp. 157-168.Applicant
Zambroski, “CMU, Pitt Developing ‘nursebor’”, http://www.cs.cmu.edu/˜nursebot/web/press/tribunereview.html, Oct. 27, 2000.Applicant