Patent Grant
8606401
1. Technical Field
This invention relates to robots, and more particularly to autonomous coverage robots and associated navigation systems.
2. Background
Autonomous robots are robots which can perform desired tasks in unstructured environments without continuous human guidance. Many kinds of robots are autonomous to some degree. Different robots can be autonomous in different ways. An autonomous coverage robot traverses a work surface without continuous human guidance to perform one or more tasks. In the field of home, office and/or consumer-oriented robotics, mobile robots that perform household functions such as vacuum cleaning, floor washing, patrolling, lawn cutting and other such tasks have been widely adopted.
In one aspect, an autonomous coverage robot includes a chassis defining a forward drive direction, a controller carried by the chassis, omni-directional receiver carried by the chassis, and a directional receiver disposed on a forward portion of the chassis and responsive to an emission incident on the forward portion of the chassis from the drive direction. The directional receiver includes a mounting receptacle defining first and second apertures substantially aligned with the drive direction, and first and second component receivers housed in the receptacle and positioned to be responsive to the emission received through the first and second apertures, respectively. The component receivers are each configured to generate a respective signal in response to the emission. The controller is configured to determine a direction of the emission in relation to the drive direction based on the signals generated by the component receivers.
The directional receiver is installed onto a front portion of the chassis and housed within the mounting receptacle. The mounting structure stabilizes and supports the directional receiver which is used for docking and navigation throughout a room. The directional receiver includes two detectors which are highly directional in the sense that they are able to detect peaks of an overlapping signal from far away and servo in on the source of the beam using those peaks. In one example, the first and second component receivers of the directional receiver are positioned to form an angle of between about 1 and 15 degrees there between. In addition, the first and second component receivers may be collimated to focus at a point between about 3 and 5 meters from the robot or on any point within each bounded area.
The controller maneuvers the robot to detect an emission with the omni-directional receiver, and in response to the detection, orients the chassis to align the robot drive direction with the determined emission direction based on the signals generated by the component receivers of the directional receiver. The controller, in response to a detected emission with the directional receiver, orients the chassis to align the robot drive direction with the determined emission direction based on the signals generated by the component receivers of the directional receiver. The receivers may be configured to receive transmissions of infrared light.
In one implementation, the omni-directional receiver includes a housing having an upper portion and defining an inner cavity, a conical, and an emission receiver. The upper portion allows a transmission of an emission into the inner cavity. The conical reflector is disposed on an upper surface of the cavity to reflect emissions incident on the upper portion of the housing down into the cavity. The emission receiver is disposed in the cavity below the conical reflector.
In one example, the robot includes a floor cleaning assembly carried by the chassis, a cleaning bin carried by the chassis and arranged to collect debris removed from a floor by the cleaning assembly, and a bin sensor. The bin sensor is configured to generate a signal indicative of the cleaning bin reaching a threshold filling that causes the controller to initiate a docking sequence.
In another aspect, an autonomous mobile robot system for bounded areas includes a navigation beacon and an autonomous coverage robot. The navigation beacon has a gateway beacon emitter arranged to transmit a gateway marking emission with the navigation beacon disposed within a gateway between the first bounded area and an adjacent second bounded area. The autonomous coverage robot includes a beacon emission sensor responsive to the beacon emission, and a drive system configured to maneuver the robot about the first bounded area in a cleaning mode in which the robot is redirected in response to detecting the gateway marking emission. The drive system is also configured to maneuver the robot through the gateway into the second bounded area in a migration mode.
The beacon may be configured to emit an infrared signal for the gateway marking emission, or any other type of signal, which is readily stopped by a wall so as not to “bleed over” into adjacent rooms and uniquely identify the current room or locality in which the robot is located.
In one implementation, the robot remains in the first bounded area upon the robot redirection in response to detecting the gateway marking emission in the cleaning mode. The gateway marking emission may be infrared light and the beacon emission sensor is configured to detect transmissions of infrared light.
In another implementation, the drive system is configured to maneuver the robot about the first bounded area in the cleaning mode for a preset time interval, and to automatically initiate the migration mode at expiration of the time interval. The drive system is configured to maneuver the robot across the gateway emission in the migration mode.
In yet another implementation, the drive system is configured to maneuver the robot about the first bounded area in the cleaning mode until a preset number of encounters of the gateway marking emission have been detected, and then to automatically initiate the migration mode. The coverage robot's dwell time in one room or selective rooms can also be set by a timer or schedule, a number of collisions or interactions with a proximity beam of a particular beacon, a character or number of dirt or debris detections, remaining battery life, and maintenance or remote control overrides.
In one example, the robot includes a floor cleaning system that removes debris from the floor as the robot is maneuvered.
In some examples, the robot includes a transmitter that signals the beacon to disrupt transmission of the gateway emission in the migration mode.
In another example, the navigation beacon includes a vectoring beacon emitter arranged to transmit a directed vectoring emission into the first bounded area with the beacon disposed within the gateway. The robot drive system is configured to direct the robot toward the beacon upon encountering the vectoring emission in the migration mode. The navigation beacon transmits the directed vectoring emission, which may be infrared light, at an angle adjacent the cross-gateway direction of between about 45 and 90 degrees. The robot, while in the migration mode, discerns a position of the navigation beacon in response to detection of the directed vectoring emission and aligns a drive direction defined by the robot in relation to an emission path defined by the directed vectoring emission. The robot advances along the emission path to reach and traverse the gateway. The navigation beacon may also transmit a proximity emission laterally about the beacon, where the robot avoids cleaning and migration within the proximity emission.
In some examples, the robot wirelessly communicates with the navigation beacon to deactivate the directed vectoring emission while in the cleaning mode and activate the directed vectoring emission while in the migration mode. In other examples, the robot remotely activates the directed vectoring emission of the navigation beacon and deactivates the gateway emission upon initiating the migration mode. Furthermore, the robot remotely deactivates the directed vectoring emission of the navigation beacon and activates the gateway emission upon terminating the migration mode. The robot remotely activates and deactivates the emissions of the navigation beacon with a radiofrequency communication. The navigation beacon may also be configured to communicate schedule information with the robot.
The system may also include a base station located in one of the bounded areas. The base station includes a base defining a docking direction from which the robot may properly dock, and a robot charger housed in the base. An omni-directional beam emitter may be mounted on the base and configured to project a proximity beam laterally around the docking station. Two navigational field emitters are housed in the base and arranged to emit respective, laterally bounded and overlapping fields of emissions of signal beams, respectively. One of the emitted fields defines a lateral field edge aligned with the docking direction and overlapped by the other of the fields. The two navigational field emitters of the base station are positioned to form an angle therebetween of between about 45 and 90 degrees. The fields of emissions of the two navigational field emitters of the base station may be infrared light.
In another aspect, a method of navigating an autonomous coverage robot between bounded areas includes positioning a navigation beacon in a gateway between adjoining first and second bounded areas. The beacon configured to transmit a gateway marking emission across the gateway. In some example, the navigation beacon may also transmit a proximity emission laterally about the beacon, where the robot avoids cleaning and migration within the proximity emission. The method also includes placing the coverage robot within the first bounded area. The robot autonomously traverses the first bounded area in a cleaning mode and upon encountering the gateway marking emission in the gateway, the robot remains in the first bounded area, thereby avoiding the robot migration into the second area. Upon termination of the cleaning mode in the first area, the robot autonomously initiates a migration mode to move through the gateway, past the beacon, into the second bounded area.
In some examples, the robot remotely deactivates the gateway marking emission of the navigation beacon upon initiating the migration mode and activates the gateway marking emission upon terminating the migration mode. The gateway marking emission may be infrared light. In other examples, the robot is non-responsive to the gateway emission while in the migration mode.
In one example, upon termination of the migration mode in the second area, the robot autonomously initiates the cleaning mode in the second bounded area.
In one example, the navigation beacon is configured to transmit a directed vectoring emission into the first bounded area with the beacon disposed within the gateway. The robot drives toward the beacon upon detecting the vectoring emission in the migration mode. Detecting the directed vectoring emission in the migration mode includes the robot sensing the directed vectoring emission with a directional receiver on the robot, where the directional receiver is aligned with a robot drive direction, and the robot aligning the robot drive direction with a path defined by the directed vectoring emission. The robot may also sense the directed vectoring emission with an omni-directional receiver on the robot before maneuvering to detect the directed vectoring emission by the directional receiver on the robot. The robot moves past the beacon by moving towards the beacon along the emission path, sensing a beacon perimeter emitted by the beacon, and moving along the beam perimeter through the gateway and into the second area.
In another aspect, a method of navigating an autonomous coverage robot between bounded areas includes positioning a navigation beacon in a gateway between adjoining first and second bounded areas. The beacon is configured to transmit a directed emission into the first bounded area and a gateway emission in a cross-gateway direction. The method also includes placing the coverage robot within the first bounded area. The robot autonomously traverses the first bounded area in a cleaning mode and upon encountering the gateway emission, the robot remains in the first bounded area, thereby avoiding the robot migration into the second area. Upon termination of the cleaning mode in the first area, the robot autonomously initiates a migration mode to move through the gateway into the second bounded area by detecting the directed emission and, in response to the directed emission, moves past the beacon through the gateway and into the second area.
The navigation beacon includes a base positionable in the gateway, the base defining a cross-gateway direction. A gateway beam emitter is housed in the base and arranged to emit a beam in the cross-gateway direction. First and second directional beam emitters are housed in the base and arranged to emit respective focused beams into each of the adjoining areas when the base is positioned in the gateway. An omni-directional beam emitter is disposed on the base and configured to project a proximity beam laterally around the beacon. The first and second directional focused beams form angles adjacent the cross-gateway direction of between about 45 and 90 degrees.
Another example of the navigation beacon includes a beam emitter emitting a beam along the line of a “virtual wall” and a circular proximity beam (and/or RF zone) to prevent the robot collisions when detected by the robot. A first beam emitter may be positioned in the gateway to emit a beam across the gateway. A second beam emitter may be positioned in the gateway to emit a beam angled into a first room and modulated to signify the first room. A third beam emitter may be positioned in the gateway to emit a beam angled into a second adjoining room and modulated to signify the second room.
The navigation beacon can also act as a virtual temporary confinement wall or gateway, where the robot stays within the virtual gateway(s) for, e.g., a predetermined number of virtual gateway interactions or time span, then crosses the virtual gateway and resets its time or incident counter to dwell in the next “room” which could be partially or wholly defined by virtual gateways.
Multiple beacons may be employed to define the boundaries of each bounded area. The directed vectoring and gateway emissions may be infrared light. Each transmitted emission is differentiated by time division multiplexing with a fixed period random offset. Each beacon is encoded differently (e.g. left and right beams) and can be set by a DIP switch or other such device located on the beacon. The beacon encoding can be set or changed by the robot (e.g. via RF commands issued by the robot) as the robot encounters successive beacons or two beacons with the same encoding. The beacon may be set to be virtual walls or threshold markers (or both). As the robot encounters each beacon, the robot counts the beacons and identifies them by their modulation. The first one encountered is number one, and is believed to be nearest a base. The second one is number two, farther yet. The third one is number three, farther yet. The left and right side beams or directed beams of the beacons are encoded differently. As a result, the robot can record which side is thought to be nearer to the base. When the robot is ready to return to the base (e.g. timed out, low battery remaining, bin full, schedule finished, maintenance needed, general event triggered, or under any other circumstances), the robot looks for the lowest numbered beacon with an away-side beam and heads in that direction. The directionality of the beam also allows the robot to maneuver past the beacon appropriately. For example, on the way out from the base station, the robot passes directed beam A and directed beam B, sequentially, of a beacon, either one or both on the left side of the robot. To return to the base station the robot should wait/hunt/clean until it detects directed beam B of the beacon. The robot then approaches the beacon by following beam B until it detects a proximity beam of the beacon. The robot turns left and proceeds in a curved path along an edge of the proximity beam while hunting/cleaning until the robot detects beam A. The robot follows beam A out away from the beacon and then hunts/cleans for the base station. This is merely one example of how to navigate using the directionality of the room-identifying left and right beacons.
In some examples, upon termination of the migration mode in the second area, the robot autonomously initiates a docking mode to maneuver towards a base station in the second area and docking with the station. The base station includes a base defining a docking direction from which the robot may properly dock, a robot charger housed in the base, an omni-directional beam emitter mounted on the base and configured to project a proximity beam latently around the base station, and two navigational field emitters housed in the base and arranged to emit respective, laterally bounded and overlapping fields of emissions of signal beams, respectively. One of the emitted fields defines a lateral field edge aligned with the docking direction and overlapped by the other of the fields. The robot maneuvers towards the base station by detecting and advancing along the lateral field edge of the overlapping fields aligned with the docking direction until docked with the station. The two navigational field emitters, which may be infrared emitters, are positioned to form an angle therebetween of between about 45 and 90 degrees. The robot detects the emissions of the base station with an omni-directional receiver on the robot and maneuvers to detect an outer lateral field edge of at least one field emission. The robot advances along the outer lateral field edge of the one field emission to the aligned lateral field edge of the overlapping fields. Upon detecting the aligned lateral field edge, the robot advances along the aligned lateral field edge until docked with the station.
Like reference symbols in the various drawings indicate like elements.
Like reference symbols in the various drawings indicate like elements.
Omni directional sensors 104 may be used to sense when the robot 100 is in close proximity to a navigation beacon. For example, the omni-directional sensor 104 may relay a signal to a control system that indicates the strength of an emission, where a stronger signal indicates closer proximity to a navigation beacon.
Proximity sensors 1072 may be used to detect when an obstacle is nearby. The proximity sensors 1072 may, for example, be infrared or ultrasonic sensors that provide a signal when an object is within a given range of the robot 100.
Contact or bump sensors 1074 may be used to detect if the robot 100 physically encounters an obstacle. Such sensors 1074 may use a physical property such as capacitance or physical displacement within the robot 100 to determine when it has encountered an obstacle.
Cliff sensors 1076 may be used to sense when the robot 100 has encountered the edge of the floor, such as when it encounters a set of stairs. The robot 100 may have behaviors that cause it to take an action, such as changing its direction of travel, when an edge is detected.
In some implementations, cliff sensors 1074 may be installed within a mounting apparatus that stabilizes and protects the sensor and which positions the sensor to point towards the window installed onto the bottom of the mounting apparatus. Together the sensor, the mounting apparatus and the window comprise a cliff sensor unit. There may, for instance, be four cliff sensor units installed within the bumper.
Reliability of a cliff sensor may be increased by reducing dust buildup.
In some implementations, a window may be installed on the bottom of the mounting apparatus which includes a shield mounted within a slanted molding composed of a material which prevents dust build up, such as an antistatic material. The shield component and the molding may be welded together. To further facilitate the reduction in dust and dirt buildup, the shield may be mounted on a slant to allow dirt to more easily slide off.
In some implementations, a secondary cliff sensor may be present behind existing cliff sensors to detect floor edges in the event that a wheel drop sensor on the caster wheel fail.
Controller 103 may be configured to propel the robot 100 according to a heading setting and a speed setting. Signals received from proximity and contact sensors may be used by the control system to issue commands that deal with obstacles. Signals from the proximity and contact sensors may cause the control system to change the commanded speed or heading of the robot 100. For instance, a signal from a proximity sensor due to a nearby wall may result in the control system issuing a command to slow down. In another instance, a collision signal from the contact sensors due to an encounter with a chair may cause the control system to issue a command to change heading. In other instances, the speed setting of the mobile the robot may not be reduced in response to the contact sensor; and/or the heading setting of the mobile the robot may not be altered in response to the proximity sensor, but instead the two sensors may operate independently.
Controller 103 may include a first independent behavioral routine configured to adjust the speed setting of the mobile the robot; and a second independent behavioral routine configured to alter the heading setting of the mobile the robot, in which the first and second independent behavioral routines are configured to execute concurrently and mutually independently. The first independent behavioral routine may be configured to poll the proximity sensor, and the second independent behavioral routine may be configured to poll the kinetic bump sensor.
The component receivers 114, 116 are positioned relative to the apertures 110, 112 such that emissions which originate along the driving direction and fall on the directional receiver 104 may pass through the apertures 110, 112 and onto their respective component receivers 114, 116. Emissions falling on the component receivers 114, 116 result in a corresponding signals being generated which may be used by controller 103 to determine the direction of the emission relative to the robot's drive direction. A cover 117 attached to the top of the mounting receptacle 108 to prevent emissions that do not originate along the driving direction from falling on the component receivers 114, 116. In some implementations, locking tabs 119 or some other fastening method may be used to secure the cover 117 to the mounting receptacle 108.
In some implementations, the component receivers 114, 116 of the directional receiver 104 can detect a homing beam with an overlap of substantially between 10% and 30%. In one example, the first and second component receivers 114, 116 may be positioned such that emissions falling squarely on each would form an angle in the range of 1 to 15 degrees. In another example, the first and second component receivers 114, 116 may be aligned so emissions aligned with them cross at a point 3 to 5 meters in front of the robot. In one example, each component receiver 114, 116 receives emissions within a sweep angle of between about 28 to 33 degrees with a center of the sweep at about 14 degrees from a direction normal to the directional receiver 104 and a sweep overlap of about 10 degrees with the other component receiver 114, 116.
In some cases, the controller 103 may maneuver the robot 100 to detect an emission with the omni-directional receiver 104. The direction of the emission may be determined using the component receivers 114, 116. In response to the detection, the controller 103 may orient the chassis 102 to align the robot drive direction with the determined emission direction.
In other cases, controller 103 may orient the chassis 102 to align the robot drive direction with the determined emission direction based on the signals generated by the component receivers 114, 116 in response to emissions detected with the directional receiver 106.
In some implementations, the receivers 114, 116, and 122 may be configured to receive transmissions of infrared light (IR). In such cases, a guide 128 (e.g. a light pipe) may guide emissions reflected off the conical reflector 120 and channels them to emission receiver 122.
The robot 100 may have a floor cleaning system that removes dirt and debris from the floor as it maneuvers about. The floor cleaning system may include a floor cleaning assembly 140, a cleaning bin 142 and a bin sensor (not shown). The floor cleaning assemblies 140 and 146 and cleaning bin 142 may be carried by the chassis 102. Cleaning bin 142 may be arranged to collect debris removed from a floor being cleaned by cleaning assembly 140. The bin sensor may be configured to generate a signal that indicates whether the cleaning bin has been filled to a threshold. When the threshold has been reached, controller 103 may initiate a docking sequence with a base station (described below). Cleaning bin 142 may be accessed to empty its contents either manually or, in some implementations, the robot 100 may automatically empty cleaning, bin 142 when docked.
In addition to providing a framework for the other elements that make up the robot 100, the chassis 102 may have a ridge on its front which is higher than all other points on the chassis 102. Such a ridge may be stop the robot 100 if it encounters an overhead obstacle, such as a couch, and prevent it from becoming wedged underneath. To enable the robot 100 to more easily free itself in the event it becomes wedged, controller 103 may normally command the drive system 130 to operate at less than maximum torque, for instance at 50% of capacity. If the robot 100 becomes wedged, for instance, sensed by increased current flowing to the drive motors, controller 103 may command increased torque to free the robot 100.
Another example of an anti-wedging system includes a spring loaded wheel system having a potentiometer to measure how much the robot 100 is pushed down by a potential wedging obstacle. Another example includes an infrared sensor disposed on a lower surface of the robot 100, where the infrared sensor is used to measure a distance that the robot 100 is pushed down.
Navigation beacon 150 has a beacon emitter assembly 152, which includes a gateway beacon emitter 154 and an omni-directional emitter 160. Gateway beacon emitter 154 may be arranged to transmit a gateway marking emission. For instance, beacon 150 may be located within a gateway that separates a first and second adjacent areas and emit the gateway marking emission to form a boundary. Omni-directional receiver 104 and directional receiver 106 on the robot 100 may detect the gateway marking emissions and thereby function as beacon emission sensors. For example, beacon 150 and the robot 100 may use infrared light (IR) emitters and sensors to create and detect the gateway marking emissions.
In one example, the robot 100 controls the state of the navigation beams through commands transmitted over a packet radio network. The address that the beacons respond to on this network is a combination of a robot address and a node address. After installing batteries in the beacon 150, the beacon 150 periodically tries to contact any robot to see if it should wake up and operate its emitters. A robot 100 may respond by transmitting a radio packet containing an invitation to join its network and a temporary address to use. While operating with a temporary address, the beacon 150 transmits an infrared code in a fence beam from emitter 154 and force field beam from omni-directional emitter 160 indicating that it is not bound, i.e. its radio address is temporary. When a robot 100 sees a beam with the bound code, it iteratively transmits a radio packet to every recently assigned temporary address to send a new code in its beam called a wink. If the robot 100 sees a wink code, it transmits a radio packet containing a new node address to be used from now on as well as a time indicating the number of hours the address is valid for use. Having bound to a robot 100 successfully, the beacon 150 will henceforth only wake up in the presence of that robot 100. The technique of confirming radio communications using infrared light signals is designed to prevent a robot 100 that is not on the same floor as the beacon 150 from controlling it permanently.
Drive system 130 may be configured to maneuver the robot 100 about the first area while in a cleaning mode. In the cleaning mode, the robot 100 may be redirected in response to detecting the gateway marking emission. In addition, the drive system 130 may also be configured to maneuver the robot 100 through the gateway into the second bounded area while in a migration mode.
While in the cleaning mode, the robot 100 may remain in the first bounded area by changing its drive direction when it detects the gateway marking emission. The gateway marking emission thus acts as a virtual barrier which may prevent the robot 100 from leaving the first bounded area.
In some instances, the drive system 130 may be configured to maneuver the robot 100 about the first bounded area in the cleaning mode for a preset time interval. When the preset time interval elapses, the drive system 130 may be automatically put in migration mode. While in migration mode, drive system 130 may be configured to maneuver the robot 100 across the gateway emission. In other instances, the drive system may configured to maneuver the robot about the first bounded area in the cleaning mode until it encounters of the gateway marking emission a preset number of times. Once the gateway marking emission has been encountered the preset number of times, the migration mode may be automatically initiated.
The robot 100 may include a transmitter for communicating with beacon 150. The transmitter may be used to signals beacon 150 to halt or pause transmission of the gateway emission in the migration mode. By signaling beacon 150 to turn on its various emitters only when needed, the system may implement a power-saving function. Such a function may serve to extend battery life in beacon 150.
While in migration mode, drive system 130 may be configured to direct the robot 100 toward beacon 150 when it encounters the directed vectoring emission emanating from vectoring beacon emitter 156. The robot 100 may then determine the position of the beacon 150 based on the detected direction of the directed vectoring emission relative to directional receiver 106. Once position is determined, the robot 100 may align itself in a drive direction relative to the directed vectoring emission. For example, the robot 100 may advance forward along the path of the directed vectoring emission to reach and traverse the gateway in which beacon 150 is located.
The robot 100 may be able to remotely activate and deactivate the beacon emissions. For example, the robot 100 may use wireless communication, such as radiofrequency (RF) communication, to pass activation and deactivation signals. The robot 100 may remotely activate the directed vectoring emission of the beacon 150 and deactivate the gateway emission upon initiating the migration mode. The robot 100 may remotely deactivate the directed vectoring emission of beacon 150 and activate the gateway emission upon terminating the migration mode.
In some instances, the beacon 150 may be configured to communicate schedule information with the robot 100. For example, beacon 150 may be able to transmit times for which the robot 100 should enter cleaning mode, when it should enter migration mode, etc. Schedule information may include details such as starting or ending times and dates.
Navigation beacon 150 may also transmit a proximity emission laterally about itself. The robot 100 may avoid cleaning and migration within the proximity emission by executing a pre-configured behavior such as changing its course when the proximity emission is detected. The proximity emission may be thought of as a “force field” through which the robot 100 is not permitted to pass.
Navigation beacon 150 may have a switch to select between a confinement mode, a navigation mode, and an off mode. Navigation beacon 150 may have a range select switch like a virtual wall. There may be a light to indicate when the navigation beacon is operating. The navigation beacon 150 may turn on an operational indicator light it is enabled or only when commanded to do so by the robot 100. There may also be a low battery warning, and there may be a separate low battery light.
In order to reduce power consumption and thus increase battery life, different operational modes may exist for the navigation beacon. When the robot 100 is not operating, navigation beacon 150 may be in a low power mode in which emitters are off and the navigation beacon periodically monitors the communication link to determine if a wakeup is necessary. When the robot 100 is operating, it may send a signal to a single or multiple navigation beacons to turn on their respective emitters. There may be different commands to turn on the various emitters. In addition, the navigation beacon may return to low power mode after an elapsed time.
In the event multiple navigation beacon are used with the robot 100, each navigation beacon may have a unique identifier, such as a 16-bit (or larger) identification number contained in memory. This identifier may be generated in the factory or by the navigation beacon itself. If the identifier is generated in the factory it may be stored in non-volatile memory in the beacon. The robot 100 may use the unique identifier to generate an internal map which may be used to navigate from one bounded region to another by navigating from one navigation beacon to another. In some implementations, the identifier for navigation beacon 150 may be used to generate signals encoded in its emissions that may be detected by the robot 100. In the event that navigation beacon 150 is unable to transmit the entire identification number, a unique code maybe generated as a derivation of the ID or by negotiation between the navigation beacons that are present and/or the robot 100.
The robot and navigation beacons may communicate via point to point or via broadcast transmissions. In the point to point scheme, the robot would have to learn the identifiers of all of the navigation beacons. Then it could send transmissions with a data field indicating the destination navigation beacon. That navigation beacon and only that navigation beacon would respond accordingly. This has the advantage that only specific navigation beacons would respond, keeping other navigation beacons off and thus increasing their battery life. User interaction may be used to train the robot to know the navigation beacons.
An alternate concept is for the robot to broadcast to all navigation beacons a command to enable them. This scheme works without user interaction. In order to mitigate this effect of increased battery consumption and reduced battery life on these navigation beacons, an alleviating technique is to reduce the power of the robot transmission.
The robot charger 184 may begins operating when triggered by a detection circuit after the robot 100 is docked to base 182. Battery conditions may be used to govern whether a deeply discharge mode, a pre-charge trickle mode, or a post charge trickle mode is used to charge the battery.
The omni-directional emitter 190 may be mounted on housing 188 and be configured to project a proximity beam laterally around the docking station through the use of an upper housing 196. Upper housing 196 may be configured such that emissions from omni-directional emitter 190 form a desired pattern outside base 182, such as a circle.
Navigational field emitters 192 and 194 may be attached to lower housing 188 and arranged to emit respective, laterally bounded and overlapping fields of emissions of signal beams. One of the emitted fields may define a lateral field edge aligned with the docking direction and be overlapped by the other emitted fields. The two navigational field emitters of the base station may be positioned such that their angle of overlap may be about 6 degrees and each emitter's aperture angle may be 20-30 degrees. A projection 198 on lower housing 188 may be used to shape the emissions from emitters 192, 194 to achieve the above pattern. In one example, the navigational field emitters 192 projects a beam at about 12 degrees from a direction normal to the emitter assembly 186, where the beam sweeps about 40 degrees starting from about −5 degrees to about 35. The other navigational field emitters 194, with the L-shaped baffle or mask 198 terminating near the middle of the LED, projects a beam at about 12 degrees from a direction normal to the emitter assembly 186, where the beam sweeps from straight out to about −35 degrees. In some implementations, the emission fields may consist of infrared light (IR). In such cases, field emitters 190, 192, and 194 may consist of infrared light emitting diodes (LEDs).
Accordingly, because the manner and methods by which the robot handles sequences of goals and navigation are relatively independent of the actual physical form of the infrastructure, for discussions involving such manner and methods, “navigation beacon” includes active and passive landmarks of other physical kinds (e.g., bar codes, retro-reflective tags, illuminated or IR spots projected on the ceiling or walls, directional RF or visible light, and other features identifiable in the environment), and “beam” includes directed vectors of other physical kinds (including inferred directional vectors calculated or kept in memory that may be followed, as well as line-of-sight directions to distant observed objects). In the example shown, walls 201, a first navigation beacon 202 and a second navigation beacon 203 (also discussed herein as “lighthouses”) define a first bounded area 204, a second bounded area 206, and a third bounded area 207 (which are typically rooms of a home). Navigation beacon 202 may be configured to transmit a gateway marking emission 208 (also noted herein as a “virtual gateway” or “gateway beam”) across a gateway 210 (typically a doorway, but openings of a few feet to 10 or 12 feet are possible, as well as arbitrary segmenting of a room without any particular openings). The gateway marking emission 208 may be an IR signal, for example, which can be sensed by a coverage robot 212.
The robot 212 may be placed within a bounded area 204. The robot 212 may autonomously traverse the bounded area 204 in a cleaning mode. If the robot 212 encounters gateway marking emission 208 in gateway 210, the robot 212 remains in the bounded area 204 without moving into an adjacent bounded area 206. Upon termination of the cleaning or coverage mode in the first area, the robot 212 may autonomously (i.e., in response to an internal trigger condition as discussed herein, e.g., time expired, distance covered, percent covered) enter a migration mode in which the robot continues cleaning but monitors for the gateway 210, locates a gateway 210, moves to and through gateway 210, (past beacon 202), into the adjacent bounded area 206.
In some implementations, the robot 212 may autonomously enter the cleaning mode after the migration to bounded area 206 has been completed. While in the migration mode, the robot 202 may be non-responsive to gateway emission 208 (although the robot may record having crossed the gateway emission 208). In some cases, the robot 212 may remotely (i.e., by direct or relayed RF communications or line-of-sight or reflected optical signaling) deactivate gateway marking emission 208 upon entering migration mode. The robot 212 may also activate gateway marking emission 208 after exiting the migration mode.
Furthermore, navigation beacon 202 may transmit a proximity emission or field 214 laterally around (surrounding) itself, establishing an exclusion zone or “force field”. The robot 212 may detect this proximity field and use the detection to attempt to avoid maneuvering within the exclusion zone around a beacon 202 while in the cleaning or migrating modes. The primary purpose of the exclusion zone is to prevent the robot 202 from striking the beacon 202 itself and moving it.
Navigation beacon 202 may be configured to transmit a first directed vectoring emission 216 (also discussed herein as a “directed emission,” “directed beam,” “launch beam” or “tractor beam”) into bounded area 204 and a second directed vectoring emission 217 into bounded area 206, with beacon 202 positioned within gateway 210. For example, the robot 212 may drive toward beacon 202 upon detecting directed emission 216 while in the migration mode.
While in the migration mode, the robot 212 may detect the directed emission 216 by sensing the directed emission 216 with a directional receiver 218 (also discussed herein as a “binocular sensor,” e.g., including twin detectors in collimated tubes) located on the front of the robot 212 (i.e. the side of the robot 212 that is aligned with the forward the robot drive direction). Alternatively, the robot 212 may sense the directed emission 216 with an omni-directional receiver 222 prior to detection by directional receiver 218. The term “omni-directional receiver” as discussed herein includes non-directional and multi-directional receivers, e.g., receivers including two or more sensors (at compass points, etc.) directed about the periphery of the robot. The robot 212 may use the signal detected by omni-directional receiver 222 to then maneuver (turn in place or turn going in forward or reverse directions) to sense directed emission 216 with directional receiver 218. The robot 212 may align its direction of travel with a path defined by an edge 220 of directed emission 216. Directional and omni-directional receivers 218 and 222 may have construction and function similar to that described above.
In some cases, the robot 212 may move towards the beacon 202 along the emission path (i.e., servoing using the two beam detectors 114 and 116 of the binocular sensor 106) until it senses a beacon perimeter 224 (i.e. the edge of proximity field emission 214). The robot 212 may move along beam perimeter 224 through the gateway 210 and into bounded area 206. The angle between the gateway emission 208 and directed emission 216 may, in some instances, be between about 45 and 90 degrees, and optionally is about 60 degrees. The gateway emission 208 is sized according to the robot diameter, and diverges to be approximately the width of the robot at the proximity field edge or range of detection (e.g., to prevent the robot crossing at that point). This may be a span of 10 degrees or more, but is determined by the robot diameter. The angle between the center of the gateway emission 208 and the center of each directed emission 216 is, in two different examples, about 45 degrees or about 60 degrees, and each directed emission 216 beam is a diverging beam made diffuse by the slot mask near the emitter, and is, in two different examples, about 20-30 degrees (e.g., 25 degrees) or about 30-50 degrees (e.g., 40 degrees). In some instances, the directed emissions 216 and 217 may consist of infrared light.
The robot 212 may remotely activate and/or deactivate emissions coming from beacon 202, such as directed emission 216 or gateway emission 208. Various methods may be used to transmit signals between the robot 212 and the navigation beacons 202 and 203.
In particular, it is effective to use the same inexpensive, common IR-LED emitters for each of the emitters of each of the beacons 202, 203, and in addition for a recharging or other dock 240 for the robot 212. The same sensors on the robot 212 can detect all of the emitters; and different sensors on the robot 212 (e.g., the multi-directional as well as the collimated directional sensors) can detect the same emitters for different purposes (as discussed herein, e.g., following, homing, stopping). In order to differentiate between the different emitters, each emitter may be encoded (e.g., modulated with a different serial code). This also helps avoid confusion with household and other remote controls as well as IR components of sunlight and other ambient sources. However, as shown in
In this situation, especially when using optical multi-directional receivers or a common optical omni-directional receiver (but also in other instances, e.g., RF) the sensor or software structure is configured to be capable of discerning one emitter from another when several signals are simultaneously received. If different frequencies are available, then these may be employed. One strategy is for the emitters to take turns, being synchronized by their communications with the robot or each other. However, this is complex and introduces a failure mode when synchronization breaks down. It is advantageous for each beacon 202, 203 and dock 240 to self-control, and stagger their own signals in time, with intervals between each emission. For instance, each transmitted emission may be differentiated by time division multiplexing (i.e., multiplexing as the beam origins are taken together as a system, including within a beacon having more than one beam or among several beacons) with a fixed period random offset (e.g., which may be different for each beam source). The interval or random offset may be changed from time to time (e.g., at random intervals) or by communication with the robot (e.g., by RF communication when the robot detects an interference condition). At manufacture, or upon changing offset, e.g., the offset may be selected from a set of offsets unlikely to harmonically interfere, or that do not share common factors. In this manner, the robot may encounter several emission paths at once yet discern the identity of each. In other instances, each transmitted emission may be differentiated by different wavelengths of light, infrared modulations, and wavelength filters/windows on the emitters and receivers.
The robot 212 may use RF communication to signal to beacon 202 to remotely activate directed emission 216 and deactivate gateway emission 208 upon initiating the migration mode. In another example, the robot 212 may remotely deactivate the directed vectoring emission 216 and activate gateway emission 208 upon exiting the migration mode.
In some instances, the robot 212 may activate a gateway emission 226 separating bounded areas 206 and 207 and initiate the cleaning mode. Similarly to that described above, the robot 212 may be prevented from leaving bounded area 206 when it encounters gateway emissions 208 and 226. When finished cleaning in bounded area 206, the robot 212 may initiate the migration mode and navigate through gateway 228 by following directed emission 230 to a perimeter 234 of a proximity emission 232 and enter bounded area 207. Once in bounded area 207, the robot 212 may re-enter the cleaning or working mode. After, for instance, a set time period or preset number of encounters with gateway emission 208, the robot 212 may migrate from bounded area 204 to bounded area 206.
Alternatively, a virtual wall emitter (gateway) may be set to independently deactivate itself on a schedule to permit the robot to cross the gateway, e.g., acting as a virtual wall for a first interval (to confine in a first or current room), then deactivating temporarily or intermittently, then acting as a virtual wall for a second interval (to confine in a second or successive room). This technique may also be interactive, e.g., the robot may use RF communication with one or more beacons to deactivate a virtual wall or bypass/cross a virtual wall.
It should be noted that in all instances herein, the robot's behavior system is arranged such that obstacle events, including cliff detection events, have a higher priority than any room-to-room navigation or cleaning. Accordingly, for example, when the robot encounters a cliff detection in the middle of a navigation or other set of sequenced behaviors, the robot may nonetheless avoid the cliff (aborting the current part of the sequence and resetting the state of the sequence).
The base station 240 may include a base, a robot charger, an omni-directional beam emitter and two navigational field emitters and be similar to the base station 180 described above. The robot 212 may maneuver towards base station 240 by detecting and advancing along one of the lateral field edges 242 or 244 of the overlapping fields 246, 248 aligned with the docking direction until docked with the station 240.
The robot 212 may detect the emissions of base station 240 with omni-directional receiver 222 on the robot and maneuver to detect an outer lateral field edge (e.g. 247) of at least one field emission 246 or 248. The robot 212 may then advance along outer lateral field edge 247 or 249 to the aligned lateral field edge 242 or 244 of the overlapping fields. Upon detecting the aligned lateral field edge 242 or 244, the robot 212 advances along the aligned lateral field edge 242 or 244 until docked with base station 240.
While embodiments of the robot discussed herein may use behavioral based control only in part or not at all, behavior based control is effective at controlling the robot to be robust (i.e. not getting stuck or failing) as well as safe. Accordingly,
In the reactive yet sequenced behaviors, the implied success of a related behavior in a sequence is an enabling condition (among others) for each behavior beyond the initiating behavior in the sequence (some sequences may have more than one initiating behavior or branches). The implied success is kept as a state signifying an enabling condition of a successive behavior, in the form of a flag, state machine, or the like. The state may be set or changed by a behavior itself upon completion, by an arbiter process, or by a planning process.
Referring to
The reactive behaviors have, as their enabling conditions or triggers, various sensors and detections of phenomena, but, in general, not (arbitrary) states of a sequence. As shown in
Actual physical sensors may be represented in the architecture by “virtual” sensors synthesized from the conditioning and drivers. Additional “virtual” sensors that are synthesized from detectable or interpreted physical properties, proprioceptive or interpreted upon the robot 302, such as over-current of a motor, stasis or stuck condition of the robot 302 (by monitoring a lack of odometry reading from a wheel encoder or counter), battery charge state via coulometry, and other virtual sensors “virtual N.”
In addition, reactive behaviors can act according to enabling conditions that represent detected phenomena to be sought or followed. A beam or wireless (RF, acoustic) signal can be detected without direction; or in some cases with direction. A remote beam or marker (bar code, retro-reflective, distinctive, fiducial, or natural recognized by vision landmark) giving a direction can permit homing or relative movement; without direction the robot 302 can nonetheless move to servo on the presence, absence, and/or relative strength of a detected signal. The reflection of a beam from the robot 302, edge, or line can be similarly detected, and following behaviors (such as obstacle following by the robot 302) conducted by servoing on such signal. A debris or artifact signal can be collected by monitoring debris or objects collected by or traversed by the robot, and that signal can be an enabling condition for a reactive behavior controlling a spot coverage pattern. A general class of “seek/servo N” signals are thus also reactive behavior enabling conditions or triggers.
The robot 302 maintains concurrent processes, “parallel” processes that are not generally considered reactive behaviors. A scheduler 292d may be necessary to allocate processor time to most other processes, e.g., including the arbiter and behaviors, in a co-operative or other multitasking manner. If more threading is available, less processes may be managed by the scheduler 292d. As noted, filters and conditioning 292c and drivers 292b, can interpret and translate raw signals. These processes are not considered reactive behaviors, and exercise no direct control over the motor drives or other actuators. In addition, in the present embodiment, brush motor controller(s) 292a control the main and side brushes, although these may alternatively be controlled by dedicated brush behaviors and a brush control arbiter.
With reference to
While maintaining state is recognized to potentially reduce the robustness of competent reactive control architecture, sequences of intended actions may require the maintenance of some state. As discussed herein, if sequenced reactive behaviors are controlled to execute using request states which may be robustly reset or erased without primary function failure, the reduction in robustness can be reduced.
One exemplary sequenced reactive behavior set is employed by the robot 302 to transition between rooms or navigate to a distal room. As depicted in
After the homing beam homing behavior 294b has completed, the sequence is in a state where an assumption is made regarding the state that the robot is located appropriately to align with the field to permit begin field following about a beacon to transition to a new chamber. A (new) align start enabling condition (e.g., field align state or request) may be set by the completing sequenced reactive behavior or by the planner, via condition flag or state machine. In order to accommodate the possibility that the field may be the first detectable signal encountered upon initiation of the homing request, the detection of the proximity field by the multi-directional receiver is an equivalent (OR) condition to the field align request, if the homing request is active when the field is encountered, this combination also should initiate field align behavior 294c. If there are no abort conditions, the field align behavior 294c executes. After the field align behavior 294c has completed, the sequence (of sequenced reactive behaviors) is in a state where a next assumption is made regarding the state—that the robot is oriented appropriately to begin field following. A (new) follow start enabling condition (e.g., field follow state or request) may be set by the completing sequenced reactive behavior or by the planner, via condition flag or state machine. Similarly, the launch behavior 294e may have as a primary enabling condition a state-based request rather than a sensor detection. Each of these behaviors 294a, 294b, 294c, 294d, 294e is detailed herein below.
In two of these cases, optionally, a state to enter the entire sequence (homing request) is maintained and an additional state to begin a next part of the sequence (field follow request; launch request) is set and both conditions are necessary to start the next sequenced reactive behavior. This would permit restarting the sequence immediately after an abort (by maintaining the entire sequence request state). Alternatively, the entire sequence entry request is reset and the only the next sequenced reactive behavior entry condition is set (field align request or field follow request). This would cause the entire sequence to be otherwise restarted (e.g., by a new or continued occurrence of conditions that would cause the planner to set the sequence request) after an abort, which could improve general robustness (although not necessarily goal-specific robustness) by erasing essentially all states.
In two cases, no sensor-based condition is an enabling condition for the next sequenced reactive behavior in the sequence, but an enabling condition is a sequence-based or a state-based request—e.g., field follow request, launch request. Accordingly, a sequence may include sequenced reactive behaviors that include only sequence states or progress as enabling conditions for the next sequenced reactive behavior (such as the field follow behavior, or launch behavior), as well as sequenced reactive behaviors that include both sensor-based conditions and sequence states, progress or requests as enabling conditions (such as the beam align or tractor homing behaviors).
In one case, a state to enter the entire sequence (homing request) is maintained and either a sensor-based condition or a sequence-based request is an enabling condition for a next sequenced reactive behavior (field align) in the sequence—e.g., a homing request AND (field align request OR field detection) is interpreted by the arbiter to permit field aligning if no reactive behaviors have higher priority. Accordingly, a sequence may include sequenced reactive behaviors that include either a combination of sequence state/requests, or both sensor-based conditions and sequence request/states, as enabling conditions for a next sequenced reactive behavior.
It should be noted that entry and mid-sequence branching is possible by enabling different behaviors depending on different combinations of sensor-based conditions and sequence states. For example, just as two possible entry points into the sequence are permitted by detecting different sensor events (multi-directional or directional) at the same time as a common entry point enabling condition (homing request), branches in the sequence to different next sequenced reactive behaviors are permitted by detecting different sensor events at the same time as a common mid-sequence enabling condition (e.g., candidate behaviors each enabled by a unique combination of sensor event and sequence state). Optionally, if different sequences each are maintained with different states, different mid-sequence state combinations permit nesting of sequences (candidate behaviors each enabled by a unique combination).
Sequence planner 253 optionally maintains a navigation mode state switch or finite state machine 243a, and/or such states or requests are maintained separately (e.g., follow start, follow done).
As shown in
The sequenced behaviors are “reactive” despite being dependent upon sequence state at least because they may be subject to the same arbiter 252 as the reactive behaviors, and/or react to sequence states as enabling conditions in the same manner as reactive behaviors react to real-time sensor events, and/or are prioritized lower than at least escape and avoidance behaviors. In addition, the states may be wholly reset to restart a reactive process. Even when a sequence or next sequenced reactive behavior's enabling conditions are satisfied, a reactive behavior that also has enabling conditions satisfied and preserves continuous autonomous operation will be executed instead. Reactive docking behaviors, which generally permit the robot to return and recharge for continued autonomous operation, may be prioritized higher than, in particular, navigation-related sequenced reactive behaviors. Reactive coverage behaviors may be prioritized below navigation sequenced reactive behaviors, in particular. Some portions of the docking behaviors noted herein are alternatively arranged as sequenced reactive behaviors; or other sequences are possible. Beacon-based navigation as discussed herein is an example of one implementation of combining sequenced reactive behaviors with non-sequenced reactive behaviors.
As shown in
As shown in
One candidate routine maintained/executed by the planner 253 is shown in
After the robot 302 has detected a specified cleaning period has elapsed or the robot 302 has detected a specified number of bumps or the robot has detected a specified condition requiring a set of sequenced behaviors, the sequence planner 253 executing on the controller 250 will decide to exit the cleaning mode and enter the migration mode. The robot may also enter the migration mode right from the dock, in order to proceed to a distal or remote room in order to begin cleaning there. The migration mode executes the task of moving from one room to an adjacent room. As discussed above, the migration mode is advantageously not a monolithic process, but is a succession of sequenced reactive behaviors started by an initial behavior—that has an enabling condition of a migration mode request (also discussed herein as a “homing request”). The planner 253 will raise a “new room”/homing request enabling condition, state, or flag. The remaining enabling condition is a sensor detection of a guiding tractor beam (optionally, limited to one beam identified according to the location state 253b as originating with the lighthouse/beacon to be homed upon), which, when the beam is detected (substantially immediately if the robot is in the beam, or after the robot encounters the beam as it continues the coverage behaviors having satisfied enabling conditions), triggers the homing beam-align behavior 294a to be selected by the arbiter 252 for execution. The robot 302 performs the task of migrating from one bounded area to an adjacent bounded area by executing the homing beam-align behavior 294a while at the same time possibly executing the cliff avoiding 256 (on any occasion when any cliff detector fails to see the floor—i.e., the enabling condition of the higher priority & reactive avoidance behavior is also satisfied) and drive 266 behaviors (e.g., if an abort condition resets the sequence). When multiple behaviors are trigged by sensor inputs or the planner 253, the arbiter 252 will arbitrate the behaviors in order of priority. That is, the arbiter may also arbitrate among different sequences of reactive behaviors, or the planner may only start one sequence. The beacon crossing sequence 262 has five sequenced reactive behaviors, beginning with the homing beam-align behavior 294a, which are executed or sequentially based on controller inputs as discussed herein. If the robot 302 experiences a signal input (such as a bump sensor input) that requires execution of a behavior having a higher priority, the robot 302 will execute the behavior of higher priority and afterwards, upon the presence of the necessary enabling conditions, may reinitiate a previous sequence of reactive sequenced behaviors.
The beacon crossing sequence 262 commences by entering the beam homing 294b or beam aligning behaviors 294a, depending on a robot position within the first bounded area in relation to the beacon 304. Generally, the robot 302 will initiate a maneuver to detect with its omni-directional receiver 104 the first directed beam 306 from the navigational beacon 304 into a first area (e.g. turning 360 degrees or driving in a circle).
After the robot 302 has aligned the drive direction with the directed emission 306 of the beacon 304 by using the directional receiver 106, the robot may commence the beam homing behavior 294b.
The behavioral sequence, as discussed, permits the robot 302, after initiating the beacon crossing sequence 262, to skip the beam aligning behavior 294a if the directional receiver 318 already detects the directed beam emission 306 and is already aligned with the directed beam emission 306. Abort conditions may prevent these and permit later restarts. As discussed herein, a combination of reactive behavior based control and sequenced reactive behavior control is advantageous. However, some embodiments discussed herein do not necessarily exclude other reactive or non reactive techniques. While executing the beam homing behavior 294b, the robot 302 moves towards the navigational beacon 304 while maintaining its alignment with (e.g., servoing upon) the directed beam 306 in response to the signals of the directional receiver 318.
As an alternative behavior that would be suitable as part of the sequenced reactive behaviors, if the directional receiver 318 is selected to be more sensitive (e.g., by collimation and confinement) at remote distances than the omni-directional receiver 322, the directional receiver 318 may receive the force field emission 310 even though the omni-directional sensor 322 does not. In this case, the directional sensor 318 may be used to alternatively home on the force field emission 310. In this case, an alternative behavior is provided in the sequence, identical to the tractor homing behavior 294b except that the sensor-based enabling condition is that the force field 310 is seen in the directional sensor 318; and the homing is on this emission 310. As an example of behavioral robustness, this behavior may be arbitrarily added to the sequence of reactive behaviors without changing any other behavior or disrupting any other process, with a priority above or below the existing tractor homing behavior 294a depending on empirical evidence that one or the other tended to be more reliable.
Upon detecting the proximity field 310, the robot 302 executes the field aligning behavior 294c.
Accordingly, as shown in
The robot 302 may encounter the proximity field 310 before encountering the directed beam 306. In this case, the robot 302 does not execute the beam aligning or beam homing behavior, 294a and 294b, respectively. Instead, the robot 302 recognizes the encoding of the proximity field 310 and executes the field aligning behavior 294d.
When the robot 302 no longer detects the proximity field beam 310 with the directional receiver 218, the robot 302 executes the field following behavior 294c.
As shown in
That is, as shown in
While migrating, the robot 302 stores in memory the beam encodings of the first and second directed beams 306 and 314, respectively, at each navigational beacon 304 encountered while away from a base station 340. To return to the base station 340, the robot 302 conducts coverage behaviors while the homing request is on, resulting in discovering the appropriate directed beams 306 and 314, respectively, and corresponding encodings, to follow a sequence of encountered beams back to the base station 340. In one example, the robot 302 can wirelessly communicate (e.g. radiofrequency) with the navigational beacons 304 to independently activate each previously encountered beam 306, 314, and 316 one at a time to find (traversing a room using random bounce and/or obstacle following to place itself in a beam path) and follow each beam back to the base station 340.
In another example (not shown), navigation beacons may emit at least one, two, or three beam signals: fence/gate beam (referred to herein as “yellow”, but in reality having a first modulation of a first frequency in the IR band), right-hand navigation beam (referred to as “red”, but in reality having either or both of different modulation or a different frequency in the IR band from the “yellow” beam), and left-hand navigation beam (referred to as “green”, but in reality having either or both of a different modulation or a different frequency in the IR band from the “yellow” and “red” beams).
If multiple navigation beacons are provided, each would have different modulation of its beams, but the emitters of the fence/gate beam, right hand beam, or left hand beam would preferably be consistent among the navigation beacons.
Regardless of its assignment as fence, gate, or trail marker, as one example, a navigation beacon also may emit a geometrically determined force field (“blue”, again in actuality either or both of a different modulation or frequency in the IR band, although a force field could also be radio frequency RF rather than visible or IR light) in a circular region around their base. This may identify its presence to a robot, and allow a robot to follow a path around the Navigation beacon (through a gate or past a trail marker), for example.
An IR-based beacon system can be designed to use a geometric solution, similar in certain respects to a non-limiting example such as a shaded floor lamp which lights up only a small area around itself, in order to provide a well-defined force field via IR, for example.
A fence navigation beacon may emit a yellow beam directly out the front of the navigation beacon (0 degrees) and a single navigation beam (red or green) at about a 60-degree angle to the right or left of the yellow beam, for example. A gate navigation beacon may emit a yellow beam to the front, a red beam at −60 degrees, and a green beam at about +60 degrees, as another non-limiting example; also, for example, a trail marker Navigation beacon may emit a red beam at about −60 degrees and a green beam at about +60 degrees.
Navigation beacon “beams” in some non-limiting examples may not be narrowly focused (thus not requiring a special lens); they may fan out to light as much of the room as may be practicable without mutual interference. As an alternative, for example, a standard home base LED not requiring other optics may also be used.
Referring to
The default docking behavior, docking lobe following 296a, as shown in
The robot 302 keeps track of the signals detected by the omni-directional receiver 322 over a window of 30 seconds. When the robot 302 detects that the frequency and variance of line crossing events (crossing the normal (zero degree) edge 362) is above about 1 Hz and below a variance of about 2.5 seconds it determines that the robot 302 is following the normal (zero degree) edge 362 and will simply drive straight by executing a smooth homing behavior, instead of continuing to follow the edge 362 (with the inevitable right-left oscillation) under the lobe following behavior 296a.
Referring to
Referring to
Referring to
Referring to
Another possible implementation of bump follow 264c includes the robot 302 keeping track of the projected location of the dock 340 and turning preferentially toward the estimated dock location during bump follow 264c. Each time the robot 302 crosses the normal (zero degree) edge 362 while facing the dock 340 and detecting the dock 340 by its directional receiver 318, the robot 302 uses odometry to project the location of the dock 340 about 5 feet out along a direction of travel. The robot 302 can use odometry throughout the docking maneuver to estimate the orientation of itself to the projected location of the dock 340.
The combination of short bouts of bump following and normal docking methods allow the robot 302 to dock in the face of a large variety of obstacles including but not limited to walls, chairs, and boxes, as well as reflections of the IR docking beams.
“ROBOT OBSTACLE DETECTION SYSTEM”, U.S. Pat. No. 6,594,844, disclosing proximity sensors such as cliff sensors and wall following sensors; “AUTONOMOUS FLOOR-CLEANING ROBOT”, U.S. Pat. No. 6,883,201, disclosing a general structure of an iRobot Roomba coverage/cleaning robot and main and edge cleaning heads in detail; “METHOD AND SYSTEM FOR MULTI-MODE COVERAGE FOR AN AUTONOMOUS ROBOT”, U.S. Pat. No. 6,809,490, disclosing motion control and coverage behaviors, including escape behaviors, selected by an arbiter according to the principles of behavior based robotics; and “METHOD AND SYSTEM FOR ROBOT LOCALIZATION AND CONFINEMENT”, U.S. Pat. No. 6,781,338, disclosing virtual walls, i.e., robot confinement using wall-simulating directed beams, are each incorporated by reference herein in their entireties.
Other robot details and features combinable with those described herein may be found in the following U.S. patent applications, entitled “COVERAGE ROBOT MOBILITY” having assigned Ser. No. 11/633,885; “MODULAR ROBOT” having assigned Ser. No. 11/633,886; and “ROBOT SYSTEM” having assigned Ser. No. 11/633,883 the entire contents of the aforementioned applications are hereby incorporated by reference.
A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the following claims. Accordingly, other implementations are within the scope of the following claims.
This application for U.S. Patent is a continuation of U.S. patent application Ser. No. 11/633,869 filed Dec. 4, 2006, which claims the benefit of U.S. Provisional Application No. 60/741,442 filed Dec. 2, 2005, the contents of both of which are expressly incorporated by reference herein in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 1755054 | Darst | Apr 1930 | A |
| 1780221 | Buchmann | Nov 1930 | A |
| 1970302 | Gerhardt | Aug 1934 | A |
| 2302111 | Dow et al. | Nov 1942 | A |
| 3166138 | Dunn | Jan 1965 | A |
| 3457575 | Bienek | Jul 1969 | A |
| 3550714 | Bellinger | Dec 1970 | A |
| 3569727 | Aggarwal | Mar 1971 | A |
| 3674316 | De Brey | Jul 1972 | A |
| 3696727 | Yokozato | Oct 1972 | A |
| 3756667 | Bombardier | Sep 1973 | A |
| 3809004 | Leonheart | May 1974 | A |
| 3821028 | Ziener | Jun 1974 | A |
| 3845831 | James | Nov 1974 | A |
| 3863285 | Hukuba | Feb 1975 | A |
| 3888181 | Kups | Jun 1975 | A |
| 3937174 | Haaga | Feb 1976 | A |
| 4099284 | Shinozaki et al. | Jul 1978 | A |
| 4119900 | Kremnitz | Oct 1978 | A |
| D258901 | Keyworth | Apr 1981 | S |
| 4306329 | Yokoi | Dec 1981 | A |
| 4328545 | Halsall et al. | May 1982 | A |
| 4369543 | Chen et al. | Jan 1983 | A |
| 4477998 | You | Oct 1984 | A |
| 4492058 | Goldfarb | Jan 1985 | A |
| 4513469 | Godfrey et al. | Apr 1985 | A |
| D278732 | Ohkado | May 1985 | S |
| 4556313 | Miller, Jr. et al. | Dec 1985 | A |
| PP46740 | Tyler | Oct 1986 | |
| 4618213 | Chen | Oct 1986 | A |
| 4620285 | Perdue | Oct 1986 | A |
| 4626995 | Lofgren et al. | Dec 1986 | A |
| 4662854 | Fang | May 1987 | A |
| 4674048 | Okumura | Jun 1987 | A |
| 4679152 | Perdue | Jul 1987 | A |
| 4696074 | Cavalli et al. | Sep 1987 | A |
| D292223 | Trumbull | Oct 1987 | S |
| 4700301 | Dyke | Oct 1987 | A |
| 4700427 | Knepper | Oct 1987 | A |
| 4710020 | Maddox et al. | Dec 1987 | A |
| 4716621 | Zoni | Jan 1988 | A |
| 4733430 | Westergren | Mar 1988 | A |
| 4733431 | Martin | Mar 1988 | A |
| 4756049 | Uehara | Jul 1988 | A |
| 4777416 | George, II et al. | Oct 1988 | A |
| D298766 | Tanno | Nov 1988 | S |
| 4782550 | Jacobs | Nov 1988 | A |
| 4811228 | Hyyppa | Mar 1989 | A |
| 4813906 | Matsuyama | Mar 1989 | A |
| 4815157 | Tsuchiya | Mar 1989 | A |
| 4829442 | Kadonoff et al. | May 1989 | A |
| 4829626 | Harkonen | May 1989 | A |
| 4832098 | Palinkas | May 1989 | A |
| 4851661 | Everett, Jr. | Jul 1989 | A |
| 4854000 | Takimoto | Aug 1989 | A |
| 4884506 | Guerreri | Dec 1989 | A |
| 4887415 | Martin | Dec 1989 | A |
| 4893025 | Lee | Jan 1990 | A |
| 4901394 | Nakamura et al. | Feb 1990 | A |
| 4912643 | Beirne | Mar 1990 | A |
| 4918441 | Bohman | Apr 1990 | A |
| 4919224 | Shyu et al. | Apr 1990 | A |
| 4919489 | Kopsco | Apr 1990 | A |
| 4920605 | Takashima | May 1990 | A |
| 4933864 | Evans et al. | Jun 1990 | A |
| 4956891 | Wulff | Sep 1990 | A |
| 4962453 | Pong et al. | Oct 1990 | A |
| 4967862 | Pong et al. | Nov 1990 | A |
| 4971591 | Raviv | Nov 1990 | A |
| 4974283 | Holsten et al. | Dec 1990 | A |
| 4977639 | Takahashi et al. | Dec 1990 | A |
| 5001635 | Yasutomi et al. | Mar 1991 | A |
| 5002145 | Waqkaumi et al. | Mar 1991 | A |
| 5022812 | Coughlan et al. | Jun 1991 | A |
| D318500 | Malewicki | Jul 1991 | S |
| 5032775 | Mizuno et al. | Jul 1991 | A |
| 5033291 | Podoloff et al. | Jul 1991 | A |
| 5049802 | Mintus | Sep 1991 | A |
| 5062819 | Mallory | Nov 1991 | A |
| 5070567 | Holland | Dec 1991 | A |
| 5086535 | Grossmeyer et al. | Feb 1992 | A |
| 5090321 | Abouav | Feb 1992 | A |
| 5093955 | Blehert et al. | Mar 1992 | A |
| 5094311 | Akeel | Mar 1992 | A |
| 5105502 | Takashima | Apr 1992 | A |
| 5109566 | Kobayashi et al. | May 1992 | A |
| 5115538 | Cochran et al. | May 1992 | A |
| 5136750 | Takashima et al. | Aug 1992 | A |
| 5142985 | Stearns | Sep 1992 | A |
| 5144715 | Matsuyo et al. | Sep 1992 | A |
| 5152028 | Hirano | Oct 1992 | A |
| 5163202 | Kawakami et al. | Nov 1992 | A |
| 5165064 | Mattaboni | Nov 1992 | A |
| 5173881 | Sindle | Dec 1992 | A |
| 5182833 | Yamaguchi et al. | Feb 1993 | A |
| 5204814 | Noonan et al. | Apr 1993 | A |
| 5208521 | Aoyama | May 1993 | A |
| 5216777 | Moro et al. | Jun 1993 | A |
| 5233682 | Abe et al. | Aug 1993 | A |
| 5239720 | Wood et al. | Aug 1993 | A |
| 5251358 | Moro et al. | Oct 1993 | A |
| 5261139 | Lewis | Nov 1993 | A |
| 5276618 | Everett, Jr. | Jan 1994 | A |
| 5277064 | Knigga et al. | Jan 1994 | A |
| 5279672 | Belker, Jr. et al. | Jan 1994 | A |
| 5284522 | Kobayashi et al. | Feb 1994 | A |
| 5293955 | Lee | Mar 1994 | A |
| 5303448 | Hennessey et al. | Apr 1994 | A |
| 5309592 | Hiratsuka | May 1994 | A |
| 5310379 | Hippely | May 1994 | A |
| 5319828 | Waldhauser et al. | Jun 1994 | A |
| 5321614 | Ashworth | Jun 1994 | A |
| 5324948 | Dudar et al. | Jun 1994 | A |
| 5341540 | Soupert et al. | Aug 1994 | A |
| 5353224 | Lee et al. | Oct 1994 | A |
| 5363935 | Schempf | Nov 1994 | A |
| 5369347 | Yoo | Nov 1994 | A |
| 5369838 | Wood et al. | Dec 1994 | A |
| 5400244 | Watanabe et al. | Mar 1995 | A |
| 5410479 | Coker | Apr 1995 | A |
| 5435405 | Schempf | Jul 1995 | A |
| 5440216 | Kim | Aug 1995 | A |
| 5442358 | Keeler | Aug 1995 | A |
| 5444965 | Colens | Aug 1995 | A |
| 5446356 | Kim | Aug 1995 | A |
| 5451135 | Schempf | Sep 1995 | A |
| 5454129 | Kell | Oct 1995 | A |
| 5455982 | Armstrong et al. | Oct 1995 | A |
| 5465525 | Mifune et al. | Nov 1995 | A |
| 5467273 | Faibish et al. | Nov 1995 | A |
| 5471560 | Allard | Nov 1995 | A |
| 5491670 | Weber | Feb 1996 | A |
| 5497529 | Boesi | Mar 1996 | A |
| 5498948 | Bruni | Mar 1996 | A |
| 5502638 | Takenaka | Mar 1996 | A |
| 5505072 | Oreper | Apr 1996 | A |
| 5507067 | Hoekstra et al. | Apr 1996 | A |
| 5511147 | Abdel-Malek | Apr 1996 | A |
| 5515572 | Hoekstra et al. | May 1996 | A |
| 5534762 | Kim | Jul 1996 | A |
| 5537017 | Feiten et al. | Jul 1996 | A |
| 5539953 | Kurz | Jul 1996 | A |
| 5542146 | Hoekstra et al. | Aug 1996 | A |
| 5548511 | Bancroft | Aug 1996 | A |
| 5551525 | Pack et al. | Sep 1996 | A |
| 5553349 | Kilstrom et al. | Sep 1996 | A |
| 5555587 | Guha | Sep 1996 | A |
| 5560077 | Crotchett | Oct 1996 | A |
| 5563366 | La Mura | Oct 1996 | A |
| 5568589 | Hwang | Oct 1996 | A |
| D375592 | Ljunggren | Nov 1996 | S |
| 5611106 | Wulff | Mar 1997 | A |
| 5611108 | Knowlton et al. | Mar 1997 | A |
| 5613261 | Kawakami et al. | Mar 1997 | A |
| 5621291 | Lee | Apr 1997 | A |
| 5622236 | Azumi et al. | Apr 1997 | A |
| 5634237 | Paranjpe | Jun 1997 | A |
| 5634239 | Tuvin et al. | Jun 1997 | A |
| 5636402 | Kubo et al. | Jun 1997 | A |
| 5647554 | Ikegami et al. | Jul 1997 | A |
| 5650702 | Azumi | Jul 1997 | A |
| 5652489 | Kawakami | Jul 1997 | A |
| 5682313 | Edlund et al. | Oct 1997 | A |
| 5682839 | Grimsley et al. | Nov 1997 | A |
| 5696675 | Nakamura et al. | Dec 1997 | A |
| 5709007 | Chiang | Jan 1998 | A |
| 5714119 | Kawagoe et al. | Feb 1998 | A |
| 5717169 | Liang et al. | Feb 1998 | A |
| 5717484 | Hamaguchi et al. | Feb 1998 | A |
| 5720077 | Nakamura et al. | Feb 1998 | A |
| 5735959 | Kubo et al. | Apr 1998 | A |
| 5752871 | Tsuzuki | May 1998 | A |
| 5756904 | Oreper | May 1998 | A |
| 5761762 | Kubo et al. | Jun 1998 | A |
| 5764888 | Bolan | Jun 1998 | A |
| 5767437 | Rogers | Jun 1998 | A |
| 5777596 | Herbert | Jul 1998 | A |
| 5781960 | Kilstrom et al. | Jul 1998 | A |
| 5787545 | Colens | Aug 1998 | A |
| 5794297 | Muta | Aug 1998 | A |
| 5812267 | Everett, Jr. et al. | Sep 1998 | A |
| 5815880 | Nakanishi | Oct 1998 | A |
| 5819008 | Asama et al. | Oct 1998 | A |
| 5820821 | Kawagoe et al. | Oct 1998 | A |
| 5825981 | Matsuda | Oct 1998 | A |
| 5831597 | West et al. | Nov 1998 | A |
| 5839156 | Park et al. | Nov 1998 | A |
| 5839532 | Yoshiji | Nov 1998 | A |
| 5841259 | Kim et al. | Nov 1998 | A |
| 5867800 | Leif | Feb 1999 | A |
| 5869910 | Colens | Feb 1999 | A |
| 5894621 | Kubo | Apr 1999 | A |
| 5903124 | Kawakami | May 1999 | A |
| 5905209 | Oreper | May 1999 | A |
| 5911260 | Suzuki | Jun 1999 | A |
| 5916008 | Wong | Jun 1999 | A |
| 5926909 | McGee | Jul 1999 | A |
| 5933102 | Miller | Aug 1999 | A |
| 5933913 | Wright et al. | Aug 1999 | A |
| 5935179 | Kleiner et al. | Aug 1999 | A |
| 5940346 | Sadowsky et al. | Aug 1999 | A |
| 5940927 | Haegermarck et al. | Aug 1999 | A |
| 5940930 | Oh et al. | Aug 1999 | A |
| 5942869 | Katou | Aug 1999 | A |
| 5943730 | Boomgaarden | Aug 1999 | A |
| 5943733 | Tagliaferri | Aug 1999 | A |
| 5947225 | Kawakami et al. | Sep 1999 | A |
| 5959423 | Nakanishi et al. | Sep 1999 | A |
| 5968281 | Wright et al. | Oct 1999 | A |
| 5974348 | Rocks | Oct 1999 | A |
| 5983448 | Wright et al. | Nov 1999 | A |
| 5984880 | Lander | Nov 1999 | A |
| 5989700 | Krivopal | Nov 1999 | A |
| 5991951 | Kubo | Nov 1999 | A |
| 5995884 | Allen et al. | Nov 1999 | A |
| 5998953 | Nakamura et al. | Dec 1999 | A |
| 6000088 | Wright et al. | Dec 1999 | A |
| 6023813 | Thatcher et al. | Feb 2000 | A |
| 6023814 | Imamura | Feb 2000 | A |
| 6025687 | Himeda et al. | Feb 2000 | A |
| 6030464 | Azevedo | Feb 2000 | A |
| 6032542 | Warnick | Mar 2000 | A |
| 6036572 | Sze | Mar 2000 | A |
| 6038501 | Kawakami | Mar 2000 | A |
| 6041471 | Charky et al. | Mar 2000 | A |
| 6049620 | Dickinson et al. | Apr 2000 | A |
| 6055702 | Imamura | May 2000 | A |
| 6065182 | Wright et al. | May 2000 | A |
| 6070290 | Schwarze et al. | Jun 2000 | A |
| 6076025 | Ueno et al. | Jun 2000 | A |
| 6076226 | Reed | Jun 2000 | A |
| 6088020 | Mor | Jul 2000 | A |
| 6099091 | Campbell | Aug 2000 | A |
| 6101671 | Wright et al. | Aug 2000 | A |
| 6108031 | King | Aug 2000 | A |
| 6108076 | Hanseder | Aug 2000 | A |
| 6108269 | Kabel | Aug 2000 | A |
| 6112143 | Allen et al. | Aug 2000 | A |
| 6112996 | Matsuo | Sep 2000 | A |
| 6119057 | Kawagoe | Sep 2000 | A |
| 6124694 | Bancroft et al. | Sep 2000 | A |
| 6125498 | Roberts et al. | Oct 2000 | A |
| 6138063 | Himeda | Oct 2000 | A |
| 6142252 | Kinto et al. | Nov 2000 | A |
| 6154694 | Aoki | Nov 2000 | A |
| 6167587 | Kasper et al. | Jan 2001 | B1 |
| 6173651 | Pathe et al. | Jan 2001 | B1 |
| 6192548 | Huffman | Feb 2001 | B1 |
| 6226830 | Hendriks et al. | May 2001 | B1 |
| 6230362 | Kasper et al. | May 2001 | B1 |
| 6240342 | Fiegert et al. | May 2001 | B1 |
| 6243913 | Frank et al. | Jun 2001 | B1 |
| 6255793 | Peless et al. | Jul 2001 | B1 |
| 6259979 | Holmquist | Jul 2001 | B1 |
| 6263539 | Baig | Jul 2001 | B1 |
| 6272936 | Oreper | Aug 2001 | B1 |
| 6283034 | Miles, Jr. | Sep 2001 | B1 |
| 6285930 | Dickson et al. | Sep 2001 | B1 |
| 6300737 | Begvall et al. | Oct 2001 | B1 |
| 6321515 | Colens | Nov 2001 | B1 |
| 6327741 | Reed | Dec 2001 | B1 |
| 6332400 | Meyer | Dec 2001 | B1 |
| 6339735 | Peless et al. | Jan 2002 | B1 |
| 6370453 | Sommer | Apr 2002 | B2 |
| 6374155 | Wallach et al. | Apr 2002 | B1 |
| 6385515 | Dickson et al. | May 2002 | B1 |
| 6389329 | Colens | May 2002 | B1 |
| 6400048 | Nishimura | Jun 2002 | B1 |
| 6401294 | Kasper | Jun 2002 | B2 |
| 6408226 | Byrne et al. | Jun 2002 | B1 |
| 6412141 | Kasper et al. | Jul 2002 | B2 |
| 6430471 | Kintou et al. | Aug 2002 | B1 |
| 6437227 | Theimer | Aug 2002 | B1 |
| 6437465 | Nishimura | Aug 2002 | B1 |
| 6438456 | Feddema et al. | Aug 2002 | B1 |
| 6442476 | Poropat | Aug 2002 | B1 |
| 6443509 | Levin et al. | Sep 2002 | B1 |
| 6444003 | Sutcliffe | Sep 2002 | B1 |
| 6463368 | Feiten et al. | Oct 2002 | B1 |
| 6465982 | Bergvall et al. | Oct 2002 | B1 |
| 6480762 | Uchikubo et al. | Nov 2002 | B1 |
| 6481515 | Kirkpatrick et al. | Nov 2002 | B1 |
| 6490977 | Bossarte et al. | Dec 2002 | B1 |
| 6493612 | Bisset | Dec 2002 | B1 |
| 6493613 | Peless et al. | Dec 2002 | B2 |
| 6496754 | Song et al. | Dec 2002 | B2 |
| 6496755 | Wallach et al. | Dec 2002 | B2 |
| 6504610 | Bauer et al. | Jan 2003 | B1 |
| 6507773 | Parker et al. | Jan 2003 | B2 |
| 6525509 | Petersson et al. | Feb 2003 | B1 |
| 6530102 | Pierce et al. | Mar 2003 | B1 |
| 6532404 | Colens | Mar 2003 | B2 |
| 6535793 | Allard | Mar 2003 | B2 |
| 6540607 | Mokris et al. | Apr 2003 | B2 |
| 6548982 | Papanikolopoulos et al. | Apr 2003 | B1 |
| 6557104 | Vu | Apr 2003 | B2 |
| D474312 | Stephens | May 2003 | S |
| 6571415 | Gerber et al. | Jun 2003 | B2 |
| 6571422 | Gordon | Jun 2003 | B1 |
| 6574536 | Kawagoe et al. | Jun 2003 | B1 |
| 6580246 | Jacobs | Jun 2003 | B2 |
| 6584376 | Kommer | Jun 2003 | B1 |
| 6586908 | Petersson et al. | Jul 2003 | B2 |
| 6594551 | McKinney, Jr. | Jul 2003 | B2 |
| 6594844 | Jones | Jul 2003 | B2 |
| D478884 | Slipy et al. | Aug 2003 | S |
| 6601265 | Burlington | Aug 2003 | B1 |
| 6604022 | Parker et al. | Aug 2003 | B2 |
| 6605156 | Clark et al. | Aug 2003 | B1 |
| 6611120 | Song et al. | Aug 2003 | B2 |
| 6611734 | Parker et al. | Aug 2003 | B2 |
| 6611738 | Ruffner | Aug 2003 | B2 |
| 6615108 | Peless et al. | Sep 2003 | B1 |
| 6624744 | Wilson | Sep 2003 | B1 |
| 6625843 | Kim et al. | Sep 2003 | B2 |
| 6629028 | Paromtchik et al. | Sep 2003 | B2 |
| 6633150 | Wallach et al. | Oct 2003 | B1 |
| 6637546 | Wang | Oct 2003 | B1 |
| 6658325 | Zweig | Dec 2003 | B2 |
| 6658693 | Reed, Jr. | Dec 2003 | B1 |
| 6661239 | Ozik | Dec 2003 | B1 |
| 6671592 | Bisset et al. | Dec 2003 | B1 |
| 6687571 | Byrne et al. | Feb 2004 | B1 |
| 6690134 | Jones et al. | Feb 2004 | B1 |
| 6741054 | Koselka et al. | May 2004 | B2 |
| 6741364 | Lange et al. | May 2004 | B2 |
| 6748297 | Song et al. | Jun 2004 | B2 |
| 6756703 | Chang | Jun 2004 | B2 |
| 6764373 | Osawa et al. | Jul 2004 | B1 |
| 6774596 | Bisset | Aug 2004 | B1 |
| 6781338 | Jones et al. | Aug 2004 | B2 |
| 6809490 | Jones et al. | Oct 2004 | B2 |
| 6830120 | Yashima et al. | Dec 2004 | B1 |
| 6836701 | McKee | Dec 2004 | B2 |
| 6841963 | Song et al. | Jan 2005 | B2 |
| 6845297 | Allard | Jan 2005 | B2 |
| 6856811 | Burdue | Feb 2005 | B2 |
| 6859010 | Jeon et al. | Feb 2005 | B2 |
| 6859682 | Naka et al. | Feb 2005 | B2 |
| 6860206 | Rudakevych et al. | Mar 2005 | B1 |
| 6865447 | Lau et al. | Mar 2005 | B2 |
| 6870792 | Chiappetta | Mar 2005 | B2 |
| 6871115 | Huang et al. | Mar 2005 | B2 |
| 6883201 | Jones et al. | Apr 2005 | B2 |
| 6886651 | Slocum | May 2005 | B1 |
| 6888333 | Laby | May 2005 | B2 |
| 6901624 | Mori et al. | Jun 2005 | B2 |
| 6925357 | Wang et al. | Aug 2005 | B2 |
| 6925679 | Wallach et al. | Aug 2005 | B2 |
| 6929548 | Wang | Aug 2005 | B2 |
| D510066 | Hickey et al. | Sep 2005 | S |
| 6938298 | Aasen | Sep 2005 | B2 |
| 6940291 | Ozik | Sep 2005 | B1 |
| 6956348 | Landry et al. | Oct 2005 | B2 |
| 6957712 | Song et al. | Oct 2005 | B2 |
| 6965209 | Jones et al. | Nov 2005 | B2 |
| 6971140 | Kim | Dec 2005 | B2 |
| 6985556 | Shanmugavel | Jan 2006 | B2 |
| 6993954 | George | Feb 2006 | B1 |
| 6999850 | McDonald | Feb 2006 | B2 |
| 7024278 | Chiappetta et al. | Apr 2006 | B2 |
| 7024280 | Parker et al. | Apr 2006 | B2 |
| 7030768 | Wanie | Apr 2006 | B2 |
| 7031805 | Lee et al. | Apr 2006 | B2 |
| 7053578 | Diehl et al. | May 2006 | B2 |
| 7054716 | McKee | May 2006 | B2 |
| 7055210 | Keppler et al. | Jun 2006 | B2 |
| 7057120 | Ma et al. | Jun 2006 | B2 |
| 7057643 | Iida | Jun 2006 | B2 |
| 7059012 | Song et al. | Jun 2006 | B2 |
| 7065430 | Naka et al. | Jun 2006 | B2 |
| 7066291 | Martins et al. | Jun 2006 | B2 |
| 7069124 | Whittaker et al. | Jun 2006 | B1 |
| 7079923 | Abramson et al. | Jul 2006 | B2 |
| 7085624 | Aldred et al. | Aug 2006 | B2 |
| 7113847 | Chmura et al. | Sep 2006 | B2 |
| 7133746 | Abramson et al. | Nov 2006 | B2 |
| 7155308 | Jones | Dec 2006 | B2 |
| 7167775 | Abramson et al. | Jan 2007 | B2 |
| 7171285 | Kim et al. | Jan 2007 | B2 |
| 7188000 | Chiappetta et al. | Mar 2007 | B2 |
| 7196487 | Jones | Mar 2007 | B2 |
| 7201786 | Wegelin et al. | Apr 2007 | B2 |
| 7206677 | Hulden | Apr 2007 | B2 |
| 7211980 | Bruemmer et al. | May 2007 | B1 |
| 7225500 | Diehl et al. | Jun 2007 | B2 |
| 7246405 | Yan | Jul 2007 | B2 |
| 7248951 | Hulden | Jul 2007 | B2 |
| 7275280 | Haegermarck et al. | Oct 2007 | B2 |
| 7288912 | Landry et al. | Oct 2007 | B2 |
| 7318248 | Yan | Jan 2008 | B1 |
| 7324870 | Lee | Jan 2008 | B2 |
| 7328196 | Peters, II | Feb 2008 | B2 |
| 7332890 | Cohen et al. | Feb 2008 | B2 |
| 7346428 | Huffman et al. | Mar 2008 | B1 |
| 7352153 | Yan | Apr 2008 | B2 |
| 7359766 | Jeon et al. | Apr 2008 | B2 |
| 7360277 | Moshenrose et al. | Apr 2008 | B2 |
| 7389156 | Ziegler et al. | Jun 2008 | B2 |
| 7389166 | Harwig et al. | Jun 2008 | B2 |
| 7408157 | Yan | Aug 2008 | B2 |
| 7418762 | Arai et al. | Sep 2008 | B2 |
| 7430462 | Chiu et al. | Sep 2008 | B2 |
| 7441298 | Svendsen et al. | Oct 2008 | B2 |
| 7444206 | Abramson et al. | Oct 2008 | B2 |
| 7459871 | Landry et al. | Dec 2008 | B2 |
| 7467026 | Sakagami et al. | Dec 2008 | B2 |
| 7474941 | Kim et al. | Jan 2009 | B2 |
| 7503096 | Lin | Mar 2009 | B2 |
| 7515991 | Egawa et al. | Apr 2009 | B2 |
| 7555363 | Augenbraun et al. | Jun 2009 | B2 |
| 7557703 | Yamada et al. | Jul 2009 | B2 |
| 7568259 | Yan | Aug 2009 | B2 |
| 7578020 | Jaworski et al. | Aug 2009 | B2 |
| 7600521 | Woo | Oct 2009 | B2 |
| 7603744 | Reindle | Oct 2009 | B2 |
| 7617557 | Reindle | Nov 2009 | B2 |
| 7647144 | Haegermarck | Jan 2010 | B2 |
| 7650666 | Jang | Jan 2010 | B2 |
| 7660650 | Kawagoe et al. | Feb 2010 | B2 |
| 7663333 | Jones et al. | Feb 2010 | B2 |
| 7693605 | Park | Apr 2010 | B2 |
| 7706917 | Chiappetta et al. | Apr 2010 | B1 |
| 7720554 | DiBernardo et al. | May 2010 | B2 |
| 7765635 | Park | Aug 2010 | B2 |
| 7801645 | Taylor et al. | Sep 2010 | B2 |
| 7805220 | Taylor et al. | Sep 2010 | B2 |
| 7849555 | Hahm et al. | Dec 2010 | B2 |
| 7853645 | Brown et al. | Dec 2010 | B2 |
| 7920941 | Park et al. | Apr 2011 | B2 |
| 7937800 | Yan | May 2011 | B2 |
| 7957836 | Myeong et al. | Jun 2011 | B2 |
| 20010020200 | Das et al. | Sep 2001 | A1 |
| 20010025183 | Shahidi | Sep 2001 | A1 |
| 20010043509 | Green | Nov 2001 | A1 |
| 20010045883 | Holdaway | Nov 2001 | A1 |
| 20010047231 | Peless et al. | Nov 2001 | A1 |
| 20020011813 | Koselka et al. | Jan 2002 | A1 |
| 20020016649 | Jones | Feb 2002 | A1 |
| 20020081937 | Yamada et al. | Jun 2002 | A1 |
| 20020095239 | Wallach et al. | Jul 2002 | A1 |
| 20020108209 | Peterson | Aug 2002 | A1 |
| 20020120364 | Colens | Aug 2002 | A1 |
| 20020156556 | Ruffner | Oct 2002 | A1 |
| 20020173877 | Zweig | Nov 2002 | A1 |
| 20030009259 | Hattori et al. | Jan 2003 | A1 |
| 20030019071 | Field et al. | Jan 2003 | A1 |
| 20030023356 | Keable | Jan 2003 | A1 |
| 20030025472 | Jones et al. | Feb 2003 | A1 |
| 20030028286 | Glenn | Feb 2003 | A1 |
| 20030030399 | Jacobs | Feb 2003 | A1 |
| 20030060928 | Abramson et al. | Mar 2003 | A1 |
| 20030067451 | Tagg | Apr 2003 | A1 |
| 20030120389 | Abramson et al. | Jun 2003 | A1 |
| 20030137268 | Papanikolopoulos et al. | Jul 2003 | A1 |
| 20030192144 | Song et al. | Oct 2003 | A1 |
| 20030216834 | Allard | Nov 2003 | A1 |
| 20030229421 | Chmura et al. | Dec 2003 | A1 |
| 20030233177 | Johnson et al. | Dec 2003 | A1 |
| 20040020000 | Jones | Feb 2004 | A1 |
| 20040030448 | Solomon | Feb 2004 | A1 |
| 20040030449 | Solomon | Feb 2004 | A1 |
| 20040030450 | Solomon | Feb 2004 | A1 |
| 20040030451 | Solomon | Feb 2004 | A1 |
| 20040030571 | Solomon | Feb 2004 | A1 |
| 20040031113 | Wosewick et al. | Feb 2004 | A1 |
| 20040049877 | Jones et al. | Mar 2004 | A1 |
| 20040068351 | Solomon | Apr 2004 | A1 |
| 20040068415 | Solomon | Apr 2004 | A1 |
| 20040068416 | Solomon | Apr 2004 | A1 |
| 20040074038 | Im et al. | Apr 2004 | A1 |
| 20040074044 | Diehl et al. | Apr 2004 | A1 |
| 20040076324 | Burl et al. | Apr 2004 | A1 |
| 20040083570 | Song et al. | May 2004 | A1 |
| 20040085037 | Jones et al. | May 2004 | A1 |
| 20040088079 | Lavarec et al. | May 2004 | A1 |
| 20040093122 | Galibraith | May 2004 | A1 |
| 20040098167 | Yi et al. | May 2004 | A1 |
| 20040111184 | Chiappetta et al. | Jun 2004 | A1 |
| 20040117064 | McDonald | Jun 2004 | A1 |
| 20040117846 | Karaoguz et al. | Jun 2004 | A1 |
| 20040128028 | Miyamoto et al. | Jul 2004 | A1 |
| 20040133316 | Dean | Jul 2004 | A1 |
| 20040134336 | Solomon | Jul 2004 | A1 |
| 20040134337 | Solomon | Jul 2004 | A1 |
| 20040143919 | Wilder | Jul 2004 | A1 |
| 20040148419 | Chen et al. | Jul 2004 | A1 |
| 20040148731 | Damman et al. | Aug 2004 | A1 |
| 20040153212 | Profio et al. | Aug 2004 | A1 |
| 20040156541 | Jeon et al. | Aug 2004 | A1 |
| 20040158357 | Lee et al. | Aug 2004 | A1 |
| 20040181706 | Chen et al. | Sep 2004 | A1 |
| 20040187249 | Jones et al. | Sep 2004 | A1 |
| 20040187457 | Colens | Sep 2004 | A1 |
| 20040200505 | Taylor et al. | Oct 2004 | A1 |
| 20040204792 | Taylor et al. | Oct 2004 | A1 |
| 20040210345 | Noda et al. | Oct 2004 | A1 |
| 20040211444 | Taylor et al. | Oct 2004 | A1 |
| 20040236468 | Taylor et al. | Nov 2004 | A1 |
| 20040244138 | Taylor et al. | Dec 2004 | A1 |
| 20040255425 | Arai et al. | Dec 2004 | A1 |
| 20050000543 | Taylor et al. | Jan 2005 | A1 |
| 20050010330 | Abramson et al. | Jan 2005 | A1 |
| 20050010331 | Taylor et al. | Jan 2005 | A1 |
| 20050021181 | Kim et al. | Jan 2005 | A1 |
| 20050028316 | Thomas et al. | Feb 2005 | A1 |
| 20050067994 | Jones et al. | Mar 2005 | A1 |
| 20050137749 | Jeon et al. | Jun 2005 | A1 |
| 20050150519 | Keppler et al. | Jul 2005 | A1 |
| 20050154795 | Kuz et al. | Jul 2005 | A1 |
| 20050156562 | Cohen et al. | Jul 2005 | A1 |
| 20050165508 | Kanda et al. | Jul 2005 | A1 |
| 20050166354 | Uehigashi | Aug 2005 | A1 |
| 20050166355 | Tani | Aug 2005 | A1 |
| 20050172445 | Diehl et al. | Aug 2005 | A1 |
| 20050183230 | Uehigashi | Aug 2005 | A1 |
| 20050187678 | Myeong et al. | Aug 2005 | A1 |
| 20050192707 | Park et al. | Sep 2005 | A1 |
| 20050204717 | Colens | Sep 2005 | A1 |
| 20050209736 | Kawagoe | Sep 2005 | A1 |
| 20050213082 | DiBernardo et al. | Sep 2005 | A1 |
| 20050217042 | Reindle | Oct 2005 | A1 |
| 20050218852 | Landry et al. | Oct 2005 | A1 |
| 20050222933 | Wesby | Oct 2005 | A1 |
| 20050235451 | Yan | Oct 2005 | A1 |
| 20050251292 | Casey et al. | Nov 2005 | A1 |
| 20050258154 | Blankenship et al. | Nov 2005 | A1 |
| 20050273967 | Taylor et al. | Dec 2005 | A1 |
| 20050288819 | De Guzman | Dec 2005 | A1 |
| 20060010638 | Shimizu et al. | Jan 2006 | A1 |
| 20060020369 | Taylor et al. | Jan 2006 | A1 |
| 20060020370 | Abramson | Jan 2006 | A1 |
| 20060021168 | Nishikawa | Feb 2006 | A1 |
| 20060025134 | Cho et al. | Feb 2006 | A1 |
| 20060037170 | Shimizu | Feb 2006 | A1 |
| 20060042042 | Mertes et al. | Mar 2006 | A1 |
| 20060060216 | Woo | Mar 2006 | A1 |
| 20060061657 | Rew et al. | Mar 2006 | A1 |
| 20060087273 | Ko et al. | Apr 2006 | A1 |
| 20060089765 | Pack et al. | Apr 2006 | A1 |
| 20060100741 | Jung | May 2006 | A1 |
| 20060119839 | Bertin et al. | Jun 2006 | A1 |
| 20060143295 | Costa-Requena et al. | Jun 2006 | A1 |
| 20060146776 | Kim | Jul 2006 | A1 |
| 20060150361 | Aldred et al. | Jul 2006 | A1 |
| 20060190133 | Konandreas et al. | Aug 2006 | A1 |
| 20060196003 | Song et al. | Sep 2006 | A1 |
| 20060259194 | Chiu | Nov 2006 | A1 |
| 20060288519 | Jaworski et al. | Dec 2006 | A1 |
| 20060293787 | Kanda et al. | Dec 2006 | A1 |
| 20070006404 | Cheng et al. | Jan 2007 | A1 |
| 20070017061 | Yan | Jan 2007 | A1 |
| 20070028574 | Yan | Feb 2007 | A1 |
| 20070032904 | Kawagoe et al. | Feb 2007 | A1 |
| 20070042716 | Goodall et al. | Feb 2007 | A1 |
| 20070061041 | Zweig | Mar 2007 | A1 |
| 20070114975 | Cohen et al. | May 2007 | A1 |
| 20070142964 | Abramson | Jun 2007 | A1 |
| 20070150096 | Yeh et al. | Jun 2007 | A1 |
| 20070157420 | Lee et al. | Jul 2007 | A1 |
| 20070213892 | Jones et al. | Sep 2007 | A1 |
| 20070234492 | Svendsen et al. | Oct 2007 | A1 |
| 20070244610 | Ozick et al. | Oct 2007 | A1 |
| 20070250212 | Halloran et al. | Oct 2007 | A1 |
| 20070266508 | Jones et al. | Nov 2007 | A1 |
| 20080007203 | Cohen et al. | Jan 2008 | A1 |
| 20080015738 | Casey et al. | Jan 2008 | A1 |
| 20080052846 | Kapoor et al. | Mar 2008 | A1 |
| 20080058987 | Ozick et al. | Mar 2008 | A1 |
| 20080091304 | Ozick et al. | Apr 2008 | A1 |
| 20080091305 | Svendsen et al. | Apr 2008 | A1 |
| 20080184518 | Taylor et al. | Aug 2008 | A1 |
| 20080281470 | Gilbert et al. | Nov 2008 | A1 |
| 20080282494 | Won et al. | Nov 2008 | A1 |
| 20080302586 | Yan | Dec 2008 | A1 |
| 20090007366 | Svendsen et al. | Jan 2009 | A1 |
| 20090038089 | Landry et al. | Feb 2009 | A1 |
| 20090049640 | Lee et al. | Feb 2009 | A1 |
| 20090055022 | Casey et al. | Feb 2009 | A1 |
| 20090228165 | Ozick et al. | Sep 2009 | A1 |
| 20100037418 | Hussey et al. | Feb 2010 | A1 |
| 20100049365 | Jones et al. | Feb 2010 | A1 |
| 20100063628 | Landry et al. | Mar 2010 | A1 |
| 20100268384 | Jones et al. | Oct 2010 | A1 |
| 20100312429 | Jones et al. | Dec 2010 | A1 |
| 20110077802 | Halloran et al. | Mar 2011 | A1 |
| Number | Date | Country |
|---|---|---|
| 2003-275566 | Jun 2004 | AU |
| 3536907 | Apr 1986 | DE |
| 9311014 | Oct 1993 | DE |
| 4338841 | May 1995 | DE |
| 4414683 | Oct 1995 | DE |
| 19849978 | Feb 2001 | DE |
| 10242257 | Apr 2003 | DE |
| 10357636 | Jul 2005 | DE |
| 102004041021 | Aug 2005 | DE |
| 102005046813 | Apr 2007 | DE |
| 102005046813 | Apr 2007 | DE |
| 338988 | Dec 1988 | DK |
| 265542 | May 1988 | EP |
| 281085 | Sep 1988 | EP |
| 286328 | Oct 1988 | EP |
| 294101 | Dec 1988 | EP |
| 307381 | Mar 1989 | EP |
| 352045 | Jan 1990 | EP |
| 358628 | Mar 1990 | EP |
| 389459 | Sep 1990 | EP |
| 433697 | Jun 1991 | EP |
| 479273 | Apr 1992 | EP |
| 554978 | Aug 1993 | EP |
| 615719 | Sep 1994 | EP |
| 845237 | Jun 1998 | EP |
| 1018315 | Jul 2000 | EP |
| 1172719 | Jan 2002 | EP |
| 1380245 | Jan 2004 | EP |
| 1380246 | Jan 2004 | EP |
| 1557730 | Jul 2005 | EP |
| 1331537 | Aug 2005 | EP |
| 1642522 | Apr 2006 | EP |
| 1672455 | Jun 2006 | EP |
| 2238196AA | Aug 2005 | ES |
| 722755 | Mar 1932 | FR |
| 2601443 | Jan 1988 | FR |
| 2213047 | Aug 1989 | GB |
| 2225221 | May 1990 | GB |
| 2267360 | Dec 1993 | GB |
| 2284957 | Jun 1995 | GB |
| 2300082 | Oct 1996 | GB |
| 2344747 | Jun 2000 | GB |
| 53110257 | Sep 1978 | JP |
| 57014726 | Jan 1982 | JP |
| 57064217 | Apr 1982 | JP |
| 59033511 | Feb 1984 | JP |
| 59094005 | May 1984 | JP |
| 59099308 | Jun 1984 | JP |
| 59112311 | Jun 1984 | JP |
| 59131668 | Jul 1984 | JP |
| 59164973 | Sep 1984 | JP |
| 59184917 | Oct 1984 | JP |
| 2283343 | Nov 1984 | JP |
| 59212924 | Dec 1984 | JP |
| 59226909 | Dec 1984 | JP |
| 60089213 | May 1985 | JP |
| 60089213 | May 1985 | JP |
| 60211510 | Oct 1985 | JP |
| 61023221 | Jan 1986 | JP |
| 61097712 | Jun 1986 | JP |
| 61160366 | Jul 1986 | JP |
| 62070709 | May 1987 | JP |
| 62189057 | Aug 1987 | JP |
| 62263507 | Nov 1987 | JP |
| 63203483 | Aug 1988 | JP |
| 1162454 | Jun 1989 | JP |
| 2006312 | Jan 1990 | JP |
| 11-102220 | Apr 1990 | JP |
| 3051023 | Mar 1991 | JP |
| 3197758 | Aug 1991 | JP |
| 3201903 | Sep 1991 | JP |
| 4019586 | Jan 1992 | JP |
| 4074285 | Mar 1992 | JP |
| 4084921 | Mar 1992 | JP |
| 5023269 | Feb 1993 | JP |
| 5040519 | Feb 1993 | JP |
| 5042076 | Feb 1993 | JP |
| 5046246 | Feb 1993 | JP |
| 5054620 | Mar 1993 | JP |
| 5060049 | Mar 1993 | JP |
| 5091604 | Apr 1993 | JP |
| 5150827 | Jun 1993 | JP |
| 5150829 | Jun 1993 | JP |
| 5-54620 | Jul 1993 | JP |
| 5257527 | Oct 1993 | JP |
| 5285861 | Nov 1993 | JP |
| 6003251 | Jan 1994 | JP |
| 6026312 | Feb 1994 | JP |
| 6105781 | Apr 1994 | JP |
| 6137828 | May 1994 | JP |
| 6293095 | Oct 1994 | JP |
| 7059702 | Mar 1995 | JP |
| 7222705 | Aug 1995 | JP |
| 07-281752 | Oct 1995 | JP |
| 7270518 | Oct 1995 | JP |
| 7281742 | Oct 1995 | JP |
| 7281752 | Oct 1995 | JP |
| 7295636 | Nov 1995 | JP |
| 7311041 | Nov 1995 | JP |
| 07-313417 | Dec 1995 | JP |
| 07-319542 | Dec 1995 | JP |
| 7313417 | Dec 1995 | JP |
| 7319542 | Dec 1995 | JP |
| 08-016241 | Jan 1996 | JP |
| 8000393 | Jan 1996 | JP |
| 8016241 | Jan 1996 | JP |
| 8016776 | Feb 1996 | JP |
| 08-063229 | Mar 1996 | JP |
| 8063229 | Mar 1996 | JP |
| 8083125 | Mar 1996 | JP |
| 8089449 | Apr 1996 | JP |
| 08-123548 | May 1996 | JP |
| 2520732 | May 1996 | JP |
| 8123548 | May 1996 | JP |
| 8152916 | Jun 1996 | JP |
| 08-256960 | Oct 1996 | JP |
| 08-263137 | Oct 1996 | JP |
| 8256960 | Oct 1996 | JP |
| 8263137 | Oct 1996 | JP |
| 08-286741 | Nov 1996 | JP |
| 08-286744 | Nov 1996 | JP |
| 08-286745 | Nov 1996 | JP |
| 08-286747 | Nov 1996 | JP |
| 8286741 | Nov 1996 | JP |
| 8286744 | Nov 1996 | JP |
| 8286745 | Nov 1996 | JP |
| 8286747 | Nov 1996 | JP |
| 08-322774 | Dec 1996 | JP |
| 08-335112 | Dec 1996 | JP |
| 8322774 | Dec 1996 | JP |
| 8335112 | Dec 1996 | JP |
| 8339297 | Dec 1996 | JP |
| 09-047413 | Feb 1997 | JP |
| 9043901 | Feb 1997 | JP |
| 9044240 | Feb 1997 | JP |
| 9047413 | Feb 1997 | JP |
| 09-066855 | Mar 1997 | JP |
| 9066855 | Mar 1997 | JP |
| 9145309 | Jun 1997 | JP |
| 9160644 | Jun 1997 | JP |
| 9179625 | Jul 1997 | JP |
| 9179685 | Jul 1997 | JP |
| 9192069 | Jul 1997 | JP |
| 09-204223 | Aug 1997 | JP |
| 09-204224 | Aug 1997 | JP |
| 9204223 | Aug 1997 | JP |
| 9204224 | Aug 1997 | JP |
| 9206258 | Aug 1997 | JP |
| 9233712 | Sep 1997 | JP |
| 09251318 | Sep 1997 | JP |
| 9251318 | Sep 1997 | JP |
| 09-265319 | Oct 1997 | JP |
| 09-269807 | Oct 1997 | JP |
| 09-269810 | Oct 1997 | JP |
| 09-269824 | Oct 1997 | JP |
| 9265319 | Oct 1997 | JP |
| 9269807 | Oct 1997 | JP |
| 9269810 | Oct 1997 | JP |
| 9269824 | Oct 1997 | JP |
| 09-319431 | Dec 1997 | JP |
| 09-319432 | Dec 1997 | JP |
| 09-319434 | Dec 1997 | JP |
| 09-325812 | Dec 1997 | JP |
| 9319431 | Dec 1997 | JP |
| 9319432 | Dec 1997 | JP |
| 9319434 | Dec 1997 | JP |
| 9325812 | Dec 1997 | JP |
| 10-027020 | Jan 1998 | JP |
| 10-055215 | Feb 1998 | JP |
| 10-105233 | Apr 1998 | JP |
| 10-117973 | May 1998 | JP |
| 10-118963 | May 1998 | JP |
| 10117973 | May 1998 | JP |
| 10177414 | Jun 1998 | JP |
| 10214114 | Aug 1998 | JP |
| 10228316 | Aug 1998 | JP |
| 10-240342 | Sep 1998 | JP |
| 10-240343 | Sep 1998 | JP |
| 10-260727 | Sep 1998 | JP |
| 10240342 | Sep 1998 | JP |
| 10260727 | Sep 1998 | JP |
| 10-295595 | Nov 1998 | JP |
| 11-065655 | Mar 1999 | JP |
| 11-065657 | Mar 1999 | JP |
| 11065655 | Mar 1999 | JP |
| 11085269 | Mar 1999 | JP |
| 11-102219 | Apr 1999 | JP |
| 11102219 | Apr 1999 | JP |
| 11-174145 | Jul 1999 | JP |
| 11-175149 | Jul 1999 | JP |
| 5054620 | Jul 1999 | JP |
| 11-213157 | Aug 1999 | JP |
| 11212642 | Aug 1999 | JP |
| 11248806 | Sep 1999 | JP |
| 11-295412 | Oct 1999 | JP |
| 11282533 | Oct 1999 | JP |
| 11346964 | Dec 1999 | JP |
| 2000-056006 | Feb 2000 | JP |
| 2000-056831 | Feb 2000 | JP |
| 2000047728 | Feb 2000 | JP |
| 2000-066722 | Mar 2000 | JP |
| 2000-075925 | Mar 2000 | JP |
| 10240343 | May 2000 | JP |
| 2000275321 | Oct 2000 | JP |
| 2000353014 | Dec 2000 | JP |
| 2001022443 | Jan 2001 | JP |
| 2001-022443 | Feb 2001 | JP |
| 2001067588 | Mar 2001 | JP |
| 2001087182 | Apr 2001 | JP |
| 2001121455 | May 2001 | JP |
| 2001125641 | May 2001 | JP |
| 2001-508572 | Jun 2001 | JP |
| 2001-197008 | Jul 2001 | JP |
| 2001197008 | Jul 2001 | JP |
| 2001216482 | Aug 2001 | JP |
| 2001-265437 | Sep 2001 | JP |
| 2001289939 | Oct 2001 | JP |
| 2001306170 | Nov 2001 | JP |
| 2001320781 | Nov 2001 | JP |
| 2002-073170 | Mar 2002 | JP |
| 2002073170 | Mar 2002 | JP |
| 2002078650 | Mar 2002 | JP |
| 2002204769 | Jul 2002 | JP |
| 2002247510 | Aug 2002 | JP |
| 2002-333920 | Nov 2002 | JP |
| 2002366227 | Dec 2002 | JP |
| 2002369778 | Dec 2002 | JP |
| 2003-010088 | Jan 2003 | JP |
| 2003-015740 | Jan 2003 | JP |
| 2003038401 | Feb 2003 | JP |
| 2003038402 | Feb 2003 | JP |
| 2003061882 | Mar 2003 | JP |
| 2003084994 | Mar 2003 | JP |
| 2003-167628 | Jun 2003 | JP |
| 2003180586 | Jul 2003 | JP |
| 2003180587 | Jul 2003 | JP |
| 2003186539 | Jul 2003 | JP |
| 2003190064 | Jul 2003 | JP |
| 2003-228421 | Aug 2003 | JP |
| 2003228421 | Aug 2003 | JP |
| 2003241836 | Aug 2003 | JP |
| 2003262520 | Sep 2003 | JP |
| 2003304992 | Oct 2003 | JP |
| 2003285288 | Oct 2003 | JP |
| 2003310509 | Nov 2003 | JP |
| 2003330543 | Nov 2003 | JP |
| 2004-123040 | Apr 2004 | JP |
| 2004148021 | May 2004 | JP |
| 2004-160102 | Jun 2004 | JP |
| 2004-174228 | Jun 2004 | JP |
| 2004198330 | Jul 2004 | JP |
| 2004-267236 | Sep 2004 | JP |
| 2004351234 | Dec 2004 | JP |
| 2005-135400 | May 2005 | JP |
| 2005118354 | May 2005 | JP |
| 2005-245916 | Sep 2005 | JP |
| 2005230032 | Sep 2005 | JP |
| 2005352707 | Oct 2005 | JP |
| 2005296511 | Oct 2005 | JP |
| 2005-346700 | Dec 2005 | JP |
| 2005346700 | Dec 2005 | JP |
| 2006043071 | Feb 2006 | JP |
| 2006-079145 | Mar 2006 | JP |
| 2006-079157 | Mar 2006 | JP |
| 2006155274 | Jun 2006 | JP |
| 2006227673 | Aug 2006 | JP |
| 2006-247467 | Sep 2006 | JP |
| 2006-260161 | Sep 2006 | JP |
| 2006-293662 | Oct 2006 | JP |
| 2006-296697 | Nov 2006 | JP |
| 2007034866 | Feb 2007 | JP |
| 2007-213180 | Aug 2007 | JP |
| 2009-015611 | Jan 2009 | JP |
| 2010-198552 | Sep 2010 | JP |
| WO9526512 | Oct 1995 | WO |
| WO9530887 | Nov 1995 | WO |
| WO9617258 | Jun 1996 | WO |
| WO9715224 | May 1997 | WO |
| WO9740734 | Nov 1997 | WO |
| WO9741451 | Nov 1997 | WO |
| WO9853456 | Nov 1998 | WO |
| WO9905580 | Feb 1999 | WO |
| WO9916078 | Apr 1999 | WO |
| WO9928800 | Jun 1999 | WO |
| WO9938056 | Jul 1999 | WO |
| WO9938237 | Jul 1999 | WO |
| WO9943250 | Sep 1999 | WO |
| WO9959042 | Nov 1999 | WO |
| WO0004430 | Jan 2000 | WO |
| 0038028 | Jun 2000 | WO |
| WO0036962 | Jun 2000 | WO |
| WO0038026 | Jun 2000 | WO |
| WO0038028 | Jun 2000 | WO |
| WO0038029 | Jun 2000 | WO |
| WO0078410 | Dec 2000 | WO |
| WO0106904 | Feb 2001 | WO |
| WO0106905 | Feb 2001 | WO |
| WO0180703 | Nov 2001 | WO |
| WO0191623 | Dec 2001 | WO |
| WO0224292 | Mar 2002 | WO |
| WO0239864 | May 2002 | WO |
| WO0239868 | May 2002 | WO |
| 02069775 | Sep 2002 | WO |
| 02071175 | Sep 2002 | WO |
| WO02067752 | Sep 2002 | WO |
| WO02069774 | Sep 2002 | WO |
| WO02069775 | Sep 2002 | WO |
| WO02074150 | Sep 2002 | WO |
| WO02075350 | Sep 2002 | WO |
| WO02081074 | Oct 2002 | WO |
| WO2004004534 | Jan 2004 | WO |
| WO2004006134 | Jan 2004 | WO |
| 2004043215 | May 2004 | WO |
| 2004058028 | Jul 2004 | WO |
| 2004059409 | Jul 2004 | WO |
| WO2004058028 | Jul 2004 | WO |
| 2005006935 | Jan 2005 | WO |
| 2005036292 | Apr 2005 | WO |
| 2005055795 | Jun 2005 | WO |
| 2005055796 | Jun 2005 | WO |
| WO2005076545 | Aug 2005 | WO |
| WO2005077243 | Aug 2005 | WO |
| 2005081074 | Sep 2005 | WO |
| 2005082223 | Sep 2005 | WO |
| WO2005082223 | Sep 2005 | WO |
| WO2005083541 | Sep 2005 | WO |
| WO2005098475 | Oct 2005 | WO |
| WO2005098476 | Oct 2005 | WO |
| WO2006046400 | May 2006 | WO |
| 2006061133 | Jun 2006 | WO |
| 2006068403 | Jun 2006 | WO |
| 2006073248 | Jul 2006 | WO |
| 2007036490 | Apr 2007 | WO |
| WO2007065033 | Jun 2007 | WO |
| Entry |
|---|
| Foreign Office Action in corresponding JP 2008-543546, dispatch date of Nov. 2, 2011, and English language translation thereof. |
| Prassler et al., “A Short History of Cleaning Robots,” Autonomous Robots, vol. 9, pp. 211-226 (2000). |
| Jarosiewicz, Eugenio, “EEL 5666 Intelligent Machine Design Laboratory”, University of Florida, Department of Electrical and Computer Engineering, Aug. 4, 1999, 50 pages. |
| Japan Office Action in JP 2008-543546, dated Aug. 1, 2012, along with an English language translation thereof. |
| Office Action in U.S. Appl. No. 11/633,869, dated Apr. 26, 2012. |
| Office Action in U.S. Appl. No. 11/633,869, dated Oct. 6, 2011. |
| Andersen et al., “Landmark based navigation strategies”, SPIE Conference on Mobile Robots XIII, SPIE vol. 3525, pp. 170-181, Jan. 8, 1999. |
| Ascii, Mar. 25, 2002, http://ascii.jp/elem/000/000/330/330024/ accessed Nov. 1, 2011. |
| U.S. Appl. No. 60/605,066 as provided to WIPO in PCT/US2005/030422, corresponding to U.S. Appl. No. 11/574,290, U.S. publication 2008/0184518, filed Aug. 27, 2004. |
| U.S. Appl. No. 60/605,181 as provided to WIPO in PCT/US2005/030422, corresponding to U.S. Appl. No. 11/574,290, U.S. publication 2008/0184518, filed Aug. 27, 2004. |
| Derek Kurth, “Range-Only Robot Localization and SLAM with Radio”, http://www.ri.cmu.edu/pub—files/pub4/kurth—derek—2004—1/kurth—derek—2004—1.pdf. 60 pages, May, 2004, accessed Jul. 27, 2012. |
| Electrolux Trilobite, Jan. 12, 2001, http://www.electrolux-ui.com:8080/2002%5C822%5C833102EN.pdf, accessed Jul. 2, 2012 10 pages. |
| Florbot GE Plastics, 1989-1990, 2 pages, available at http://www.fuseid.com/, accessed Sep. 27, 2012 |
| Gregg et al., “Autonomous Lawn Care Applications,” 2006 Florida Conference on Recent Advances in Robotics, Miami, Florida, May 25-26, 2006, Florida International University, 5 pages. |
| Hitachi ‘Feature’, http://kadenfan.hitachi.co.jp/robot/feature/feature.html, 1 page, Nov. 19, 2008. |
| Hitachi, http://www.hitachi.co.jp/New/cnews/hi—030529—hi—030529.pdf , 8 pages, May 29, 2003. |
| Home Robot—UBOT; Microbotusa.com, retrieved from the WWW at www.microrobotusa.com, accessed Dec. 2, 2008. |
| King and Weiman, “Helpmate™ Autonomous Mobile Robots Navigation Systems,” SPIE vol. 1388 Mobile Robots, pp. 190-198 (1990). |
| Li et al. “Robust Statistical Methods for Securing Wireless Localization in Sensor Networks,” Information Procesing in Sensor Networks, 2005, Fourth International Symposium on, pp. 91-98, Apr. 2005. |
| Martishevcky, “The Accuracy of point light target coordinate determination by dissectoral tracking system”, SPIE vol. 2591, pp. 25-30, Oct. 23, 2005. |
| Maschinemarkt Würzburg 105, Nr. 27, pp. 3, 30, Jul. 5, 1999. |
| Miwako Doi “Using the symbiosis of human and robots from approaching Research and Development Center,” Toshiba Corporation, 16 pages, available at http://warp.ndl.go.jp/info:ndljp/pid/258151/www.soumu.go.jp/joho—tsusin/policyreports/chousa/netrobot/pdf/030214—1—33—a.pdf, Feb. 26, 2003. |
| Paromtchik “Toward Optical Guidance of Mobile Robots,” Proceedings of the Fourth World Multiconference on Systemics, Cybermetics and Informatics, Orlando, FL, USA, Jul. 23, 2000, vol. IX, pp. 44-49, available at http://emotion.inrialpes.fr/˜paromt/infos/papers/paromtchik:asama:sci:2000.ps.gz, accessed Jul. 3, 2012. |
| Roboking—not just a vacuum cleaner, a robot!, Jan. 21, 2004, infocom.uz/2004/01/21/robokingne-prosto-pyilesos-a-robot/, accessed Oct. 10, 2011, 7 pages. |
| Sebastian Thrun, “Learning Occupancy Grid Maps With Forward Sensor Models,” Autonomous Robots 15, 111-127, Sep. 1, 2003. |
| SVET Computers—New Technologies—Robot Vacuum Cleaner, Oct. 1999, available at http://www.sk.rs/1999/10/sknt01.html, accessed Nov. 1, 2011. |
| Written Opinion of the International Searching Authority, PCT/US2004/001504, Aug. 20, 2012, 9 pages. |
| Facts on the Trilobite http://www.frc.ri.cmu.edu/˜hpm/talks/Extras/trilobite.desc.html 2 pages accessed Nov. 1, 2011. |
| Florbot GE Plastics, 1989-1990, 2 pages, available at http://www.fuseid.com/, accessed Sep. 27, 2012. |
| Fuentes, et al. “Mobile Robotics 1994”, University of Rochester. Computer Science Department, TR 588, 44 pages, Dec. 7, 1994.. |
| Grumet “Robots Clean House”, Popular Mechanics, Nov. 2003. |
| Robovacc1999. |
| LG RoboKing V-R4000, http://www.popco.net/zboard/view.php?id=tr—review&no=40, Aug. 5, 2005, 15 pages, copyright date 1999-2011. |
| Dyson's Robot Vacuum Cleaner —the DC06, http://www.gizmag.com/go/1282/ 3 pages, dated May 2, 2004. |
| Electrolux Trilobite ZA1, http://www.electrolux-ui.com:8080/2002%5C822%5C833102EN.pdf 10 pages, dated Jan. 12, 2001. |
| Electrolux Trilobite, http://www.robocon.co.kr/trilobite/Presentation—Trilobite—Kor—030104.ppt 19 pages, undated. |
| Electrolux web site Sep. 2002, http://www.frc.ri.cmu.edu/˜hpm/talks/Extras/trilobite.desc.html 2 pages, dated Sep. 2002. |
| Euroflex Intellegente Monster manual, English language excerpt, cover and pp. 17-30, undated. |
| Euroflex Monster, http://www.euroflex.tv/novita—dett.php?id=15 1 page, dated Jan. 1, 2006. |
| Floorbotics VR-8 Floor Cleaning Robot, http://www.consensus.com.au/SoftwareAwards/CSAarchive/CSA2004/CSAart04/FloorBot/FX1%20Product%20Description%2020%20January%202004.pdf, (2004), 11 pages. |
| Friendly Robotics RV Manual, http://www.robotsandrelax.com/PDFs/RV400Manual.pdf pp. 1-18. dated 2004. |
| Hitachi Robot Cleaner, It's eye, www.hitachi.co.jp/rd/pdf/topics/hitac2003—10.pdf, Oct. 2003, 2 pages, copyright date 2003. |
| Hitachi Robot Cleaner, http://www.hitachi.co.jp/New/cnews/hl—030529—hl—030529.pdf, 8 pages, dated May 29, 2003. |
| LG Announces the First Robotic Vacuum Cleaner of Korea, Robot Buying Guide, http://robotbg.com/news/2003/04/22/lg—announces—the—first—robotic—vacuum—cleaner—of—korea, 1 page, Apr. 21, 2003. |
| Roboking-Not Just a Vacuum Cleaner, a Robot!, http;//infocom.uz/2004/01/21/robokingne-prosto-pyilesos-a-robot/, Jan. 21, 2004, foreign language version, 7 pages. |
| Roboking-Not Just a Vacuum Cleaner, a Robot!, http;//infocom.uz/2004/01/21/robokingne-prosto-pyilesos-a-robot/, Jan. 21, 2004, English version, 5 pages. |
| Clean Mate 365 Intelligent Automatic Vacuum Cleaner Model QQ-1 User Manual, www.metapo.com/support/user—manual.pdf 3 pages, undated. |
| Microrobot UBot MR-UB01K, http://us.aving.net/news/view.php?articleld=23031 5 pages, dated Aug. 25, 2006. |
| Robotic Vacuum by Matsushita about to undergo Field Testing, http://www.taipeitimes.com/News/worldbiz/archives/2002/03/26/0000129338 2 pages, dated Mar. 26, 2002, copyright date 1999-2011. |
| Matsushita robotic cleaner, http://techon.nikkeibp.co.jp/members/01db/200203/1006501/ 3 pages, dated Mar. 25, 2002, copyright date 1995-2011. |
| Matsushita robotic cleaner, http://ascii.jp/elem/000/000/330/330024/ 9 pages, dated Mar. 25, 2002. |
| Sanyo Robot Cleaner http://www.itmedia.co.jp/news/0111/16/robofesta—m.html, 4 pages, dated Nov. 16, 2001. |
| Sanyo Robot Cleaner http://www.itmedia.co.jp/news/0111/16/robofesta—m2.html, 3 pages, dated Nov. 16, 2001. |
| Yujin Robotics, An Intelligent Cleaning Robot “Iclebo Q”, http://us.aving.net/news/view.php?articleld=7257 8 pages, dated Sep. 2, 2005. |
| Vacuum Cleaner Robot Operated in Conjunction with 3G Cellular Phone, http://www.toshiba.co.jp/tech/review/2004/09/59—09pdf/a13.pdf pp. 53-55, dated 2004. |
| Toshiba prototype, http://warp.ndl.go.jp/info:ndljp/pid/258151/www.soumu.go.jp/joho—tsusin/policyreports/chousa/netrobot/pdf/030214—1—33—a.pdf, pp. 1-16, dated 2003. |
| SVET Kompujutera Robot usisivac http://www.sk.rs/1999/10/sknt01.html, foreign language version, 1 page, dated Oct. 1999, copyright date 1984-2011. |
| SVET Kompjutera Robot Vacuum Cleaner, SK Web 2:54, English version, dated Oct. 1999, 1 page, copyright date 1984-2011. |
| Robo Vac, Arbeitet ohne Aufsicht, Maschinemarkt, Wurzburg 105 (1999) 27, 3 pages, dated Jul. 5, 1999. |
| U.S. Appl. No. 60/605,066, filed on Aug. 27, 2004. |
| U.S. Appl. No. 60/605,181, filed on Aug. 27, 2004. |
| Hitachi, “Feature,” http://kadenfan.hitachi.co.jp/robot/feature/feature.html, 1 pages, accessed Nov. 19, 2008, dated May 29, 2003. |
| Microrobot, “Home Robot—UBOT,” http://www.microrobotusa.com/product—1—1—.html, 2 pages, accessed Dec. 2, 2008, copyright date 2007. |
| lnMach, “Intelligent Machines,” http://www.inmach.de/inside.html, 1 page, accessed Nov. 19, 2008. |
| Hammacher Schlemmer, “Electrolux Trilobite Robotic Vacuum at Hammacher Schlemmer,” www.hammacher.com/publish/71579.asp?promo=xsells, 3 pages, accessed Mar. 18, 2005, copyright date 2004. |
| TotalVac.com, “Karcher RC3000 RoboCleaner Robot Vacuum at TotalVac,” www.totalvac.com/robot—vacuum.htm, 3 pages, accessed Mar. 18, 2005, copyright date 2004. |
| MobileMag, Samsung unveils high-tech robot vacuum cleaner, http://www.mobilemag.com/content/100/102/C2261/, 4 pages, accessed Mar. 18, 2005, dated Nov. 25, 2003, copyright date 2002-2004. |
| Iirobotics.com, Samsung unveils its multifunction robot vacuum,Samsung Robot Vacuum (VC-RP30W), http://www.iirobotics.com/webpages/hotstuff.php?ubre=111, 3 pages, accessed Mar. 18, 2005, dated Aug. 31, 2004. |
| OnRobo, Samsung unveils it multifunction robot vacuum, http://www.onrobo.com/enews/0210/samsung—vacuum.shtml, 3 pages, accessed Mar. 18, 2005, copyright date 2004. |
| Gregg, M. et al., “Autonomous Lawn Care Applications”, 2006 Florida Conference on Recent Advances in Robotics, FCRAR May 25-26, 2006, pp. 1-5. |
| UAMA (Asia) Industrial Co. Ltd., “Robot Family,” 1 page, indicates available in 2005. |
| Matsutek Enterprises Co. Ltd., “Automatic Rechargeable Vacuum Cleaner,” http://matsutek.manufacturer.globalsources.com/si/6008801427181/pdtl/Home-vacuum/10, 3 pages, accessed Apr. 23, 2007, copyright date 2007. |
| LG, RoboKing, 4 pages. Undated. |
| Collection of pictures of robotic cleaners, devices AA-BF, 50 pages. Undated. |
| Braunstingl et al., “Fuzzy Logic Wall Following of a Mobile Robot Based on the Concept of General Perception,” Sep. 1995, ICAR '95, 7th Int'l Conference on Advanced Robotics, Sant Feliu De Guixols, Spain, pp. 367-376. |
| Yata et al., “Wall Following Using Angle Information Measured by a Single Ultrasonic Transducer,” Proceedings of the 1998 IEEE, International Conference on Robotics & Automation, Leuven, Belgium, pp. 1590-1596, May, 1998. |
| Tse et al., “Design of a Navigation System for a Household Mobile Robot Using Neural Networks” Dept. of Manufacturing Engg. & Engg. Management, City University of Hong Kong, pp. 2151-2156, 1998. |
| Wolf, J. et al., “Robust Vision-Based Localization by Combining an Image-Retrieval System with Monte Carlo Localization”, IEEE Transactions on Robotics, vol. 21, No. 2 pp. 208-216, Apr. 2005. |
| Eren et al., “Accuracy in Position Estimation of Mobile Robots Based on Coded Infrared Signal Transmission,” Proceedings: Integrating Intelligent Instrumentation and Control, Instrumentation and Measurement Technology Conference, IMTC/95, pp. 548-551, 1995. |
| Karlsson, N. et al. “Core Technologies for Service Robotics”, Proceedings of 2004 IEEE/RSJ International Conference on Intelligent Robots and Systems, Sep. 28-Oct. 2, 2004, Sendai Japan, pp. 2979-2984. |
| Leonard et al., “Mobile Robot Localization by Tracking Geometric Beacons,” IEEE Transactions on Robotics and Automation, vol. 7, No. 3, pp. 376-382, Jun. 1991. |
| Paromtchik, “Toward Optical Guidance of Mobile Robots.” Proceedings of the Fourth World Multiconference on Systemics, Cybernetics and Informatics, Orlando, FL, USA, Jul. 23-26, 2000, vol. IX, six pages. |
| Wong, EIED Online>>Robot Business, Ed Online ID# 13114, 17 pages, Jul. 26, 2006, copyright date 2006. |
| Facchinetti et al., “Using and Learning Vision-Based Self-Positioning for Autonomous Robot Navigation,” ICARCV '94, The Third International Conference on Automation, Robotics and Computer Vision, Singapore, vol. 3 pp. 1694-1698, Nov. 1994. |
| Facchinetti et al., “Self-Positioning Robot Navigation Using Ceiling Images Sequences,” ACCV'95, pp. 1-5, Dec. 5-8, 1995. |
| King et al., “Heplmate-TM- Autonomous Mobile Robot Navigation System,” SPIE, vol. 1388, Mobile Robots V, pp. 190-198, 1990. |
| Fairfield et al., “Mobile Robot Localization with Sparse Landmarks,” Proceedings of SPIE, vol. 4573, pp. 148-155, 2002. |
| Benayad-Cherif et al., “Mobile Robot Navigation Sensors,” SPIE, vol. 1831, Mobile Robots VII pp. 378-387, 1992. |
| The Sharper Image, e-Vac Robotic Vacuum, SI727 Instructions, www.sharperimage.com , 18 pages, copyright 2004. |
| Ebay, Roomba Timer -> Timed Cleaning- Floorvac Robotic Vacuum, Cgi.ebay.com/ws/eBay|SAP|.d11?viewitem&category=43526&item=4375198387&rd=1, 5 pages, Apr. 20, 2005. |
| Friendly Robotics , “Friendly Robotics- Friendly Vac, Robotic Vacuum Cleaner,” http://www.friendlyrobotics.com/vac.htm, 4 pages, accessed Apr. 20, 2005. |
| Ebay, Zoombot Remote Controlled Vacuum- RV-500 New Roomba 2, Cgi.ebay.com/ws/ebay|SAP|.dll?viewitem&category?43526&item=4373497618&Rd=1, 7 pages, Apr. 20, 2005. |
| The Sharper Image, E Vac Robotic Vacuum, http://www.sharperimage.com/us/en/templates/products/pipmorework1printable.jhtml, 1 page, accessed Mar. 18, 2005. |
| Office Action from U.S. Appl. No. 11/671,305, dated Aug. 22, 2007. |
| Number | Date | Country | |
|---|---|---|---|
| 20110004339 A1 | Jan 2011 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60741442 | Dec 2005 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11633869 | Dec 2006 | US |
| Child | 12828525 | US |
