With the improvement of mobile computing devices, users are able to use their devices for a variety of different purposes. Not only can a user operate a smartphone for making phone calls and for browsing the internet, for example, but a user can use his or her smartphone to perform a variety of different tasks.
The disclosure herein is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements, and in which:
Embodiments described herein provide for a computing device that can detect one or more rounded objects (e.g., a ball, a self-propelled device having a spherical housing) in an image and track the detected rounded object(s). The computing device can utilize the detected rounded objects as input for performing one or more operations or processes on the computing device.
According to some embodiments, one or more images, including frames of real-time video, can be received from an image capturing device of the computing device. The computing device can operate one or more applications or operate in one or more modes that use the components of the image capturing device in order to receive visual input. The visual input can be of a scene and/or objects in the scene in which the lens of the image capturing device is focused on or pointed towards. For example, the scene can include an object of interest that is in motion and has a rounded shape.
Embodiments provide for the computing device to receive a plurality of images in order to detect one or more rounded objects (corresponding to one or more objects of interest) in one or more of the images. A rounded object that is depicted in an image, for example, can correspond to an object of interest having at least a housing or structure with a rounded shape or a partial rounded shape, such as an ellipse, oval, disc, sphere, etc. The object of interest can correspond to, for example, a ball, a circular object, a cylindrical object, or a self-propelled device having a spherical housing, etc., that is included within the scene (e.g., visual input detected by the image capturing device). In some examples, a self-propelled device can be modified (e.g., post assembly) to include a rounded or spherical aspect (e.g., attach a rounded object to the self-propelled device or drop a ping pong ball in a truck bed of a remote controlled truck). The computing device can process and utilize the detected objects in the images as input for performing one or more operations or processes on the computing device.
In some embodiments, each of the received images can be individually processed in order to detect one or more rounded objects. The computing device can use one or more detection techniques, together or individually, in order to detect the rounded object(s). According to one or more embodiments, the detection techniques can include using an image filter and a detection algorithm based on the size of the rounded object. In addition, the detection techniques can be used to determine the position information of one or more rounded objects based on a relative position of the one or more rounded objects in the one or more images. Detecting rounded object(s) in images can enable the computing device to track the movement of the rounded object(s), as well as the velocity and/or acceleration of the motion.
Upon detecting one or more rounded objects in the received images, the computing device can utilize the detected one or more rounded objects and the respective position information as input for performing additional operations or processes. In one embodiment, the computing device can adjust the images that include a detected rounded object, and present the adjusted images on a display device. In other embodiments, the computing device can use the detected rounded object as input for controlling the detected object (e.g., as a remote device).
According to one or more embodiments, the image capturing device can be distinct and separate from the computing device that detects the one or more rounded objects in the one or more images. The image capturing device and the computing device can wirelessly communicate with each other in order to enable the computing device to receive the one or more images from the image capturing device. A recording device, such as a video capturing device, can also be separate from and wirelessly communicate with the computing device. In other embodiments, the devices can be a part of or be incorporated together as one device.
Embodiments described herein also provide for the operations and/or processes that are performed by the recording device and/or the image capturing device and/or the computing device to be performed at different times and different orders (e.g., shifted temporally).
One or more embodiments described herein provide that methods, techniques, and actions performed by a computing device are performed programmatically, or as a computer-implemented method. Programmatically, as used herein, means through the use of code or computer-executable instructions. These instructions can be stored in one or more memory resources of the computing device. A programmatically performed step may or may not be automatic.
One or more embodiments described herein can be implemented using programmatic modules or components of a system. A programmatic module or component can include a program, a sub-routine, a portion of a program, or a software component or a hardware component capable of performing one or more stated tasks or functions. As used herein, a module or component can exist on a hardware component independently of other modules or components. Alternatively, a module or component can be a shared element or process of other modules, programs or machines.
Some embodiments described herein can generally require the use of computing devices, including processing and memory resources. For example, one or more embodiments described herein may be implemented, in whole or in part, on computing devices such as digital cameras, digital camcorders, desktop computers, cellular or smart phones, personal digital assistants (PDAs), laptop computers, printers, digital picture frames, and tablet devices. Memory, processing, and network resources may all be used in connection with the establishment, use, or performance of any embodiment described herein (including with the performance of any method or with the implementation of any system).
Furthermore, one or more embodiments described herein may be implemented through the use of instructions that are executable by one or more processors. These instructions may be carried on a computer-readable medium. Machines shown or described with figures below provide examples of processing resources and computer-readable mediums on which instructions for implementing embodiments of the invention can be carried and/or executed. In particular, the numerous machines shown with embodiments of the invention include processor(s) and various forms of memory for holding data and instructions. Examples of computer-readable mediums include permanent memory storage devices, such as hard drives on personal computers or servers. Other examples of computer storage mediums include portable storage units, such as CD or DVD units, flash memory (such as carried on smart phones, multifunctional devices or tablets), and magnetic memory. Computers, terminals, network enabled devices (e.g., mobile devices, such as cell phones) are all examples of machines and devices that utilize processors, memory, and instructions stored on computer-readable mediums. Additionally, embodiments may be implemented in the form of computer-programs, or a computer usable carrier medium capable of carrying such a program.
System Description
In an example of
Still further, system 100 can perform dimensional analysis of a plurality of images depicting a scene that includes an object of interest. Specifically, system 100 can perform dimensional analysis in order to determine the distance of the object of interest from the image capturing device and/or the computing device. For that purpose, in one example, rounded objects can be detected and processed in images efficiently by components of system 100.
In one embodiment, system 100 includes object detect 110, image adjust 130, user interface (UI) component 140, device control 150 and wireless communication (WCOM) 160. The components of system 100 combine to receive a plurality of images from an image capturing device and to automatically process the images to detect one or more rounded objects depicted in the images. Each image can be processed using one or more detection techniques so that the detected objects can be processed as input for performing one or more operations on the computing device.
According to an embodiment, the object detect 110 can also include sub-components, such as image filter 112, gradient detect 120, and image mark 122. These components can combine to enable the object detect 110 to detect and track one or more objects depicted in a plurality of images.
The computing device can operate one or more applications and/or operate in one or more different modes. In one embodiment, system 100 can be operated in response to a user executing or launching an application or program that uses visual input detected by an image capturing device to perform one or more processes (e.g., a game application or a device calibration settings program). The object detect 110 can receive a visual input 114, such as image input, from the image capturing device in order to detect one or more rounded objects in one or more images. For example, an image capturing device (e.g., an integrated camera) can receive and capture a scene (e.g., from whatever view and/or object(s) the lens is pointing at). The visual input 114 can be in the form of a sequence of images, or through video input (e.g., a plurality of images that are captured continuously at 30-60 frames per second).
In some embodiments, a preview of the images that are being received by the computing device can be provided on a display device of the computing device. For example, the visual input 114 can also be provided to the UI component 140 so that the UI component 140 generates the preview image of the received visual input 114 (as well as one or more features that can be presented with the preview image, e.g., zoom in or zoom out features, capture image feature). The display device (e.g., a touch-sensitive display device) can present a dynamically changing, real-time image of a scene in which the image capturing device is currently pointing at. This image can include one or more objects of interest in the scene, having a rounded characteristic (e.g., having a rounded housing or portion of the housing). A user can also capture and store one or more images of the scene by pressing down on a capture button or trigger, or by using another user interface feature (e.g., tap a “capture image” graphic feature provided on a touch-sensitive display).
According to some embodiments, the object detect 110 can individually process individual images to detect objects of interest. In particular, the objects of interest can be designated to match a particular shape, such as semi-sphere, or sphere (or other spherical portion). For each received image via the visual input 114, the object detect 110 can operate an image recognition software, and/or other image processing methods in order to detect the rounded, designated characteristic of the object of interest. For example, the object detect 110 can scan the pixels of the individually captured images to detect rounded objects corresponding to spheres, semi-spheres or other variations (depending on the designated rounded characteristics).
The object detect 110 can use different detection techniques, together or individually, in order to detect one or more rounded objects in individual images. In one embodiment, the image filter 112 of the object detect 110 can receive one or more images and apply a filter, such as a grayscale filter, to each of the received images. Applying a grayscale filter to the image can convert each pixel of the image to a shade of gray (e.g., based on intensity information). The image filter 112 can provide a grayscale image 116 of each received image to the gradient detect 120 and the image mark 122. Once in grayscale, a trained object detector can scan the grayscale pixels for rounded objects that potentially correspond to the object of interest. The use of the grayscale filter promotes fast image object detection to enable real-time detection of an object of interest when that object is in motion.
In some embodiments, the objects of interest can include additional characteristics to facilitate their respective tracking. For example, the rounded characteristic of the object of interest can further be combined with additional features, such as other structural visual landmarks, brightness in color (e.g., white, silver, yellow, etc.), illuminations, or surface patterns. By way of example, the object of interest can be brightly colored (e.g., white), and the use of a grayscale filter on the processed input images can yield objects which can have a lighter shade of gray than other pixels for other portions of the same scene. In one embodiment, the grayscale images 116 can be provided to the gradient detect 120 and the image mark 122, which use one or more image processing methods (e.g., apply one or more algorithms), to detect the rounded object(s) in each grayscale image 116.
Still further, in variations, known (or pre-determined) information about the objects of interest can be used in performing object detection. For example, a user can provide inputs 126 that correspond to visual markers for the object of interest. Such inputs 126 can include, for example, the estimated size (e.g., a radius or diameter) of the rounded object(s) as well as the color(s) of the object(s) via an input mechanism (e.g., using one or more buttons, or a touch-sensitive display screen). In another variation, the user can provide input 126 corresponding to a circular gesture on the touch-sensitive display in order to indicate an approximate size of the object as presented on the display. In other examples, information about the one or more rounded objects can be stored in a memory of the computing device. The gradient detect 120 can use known information in order to detect the rounded object(s) in each of the images.
In one embodiment, the gradient detect 120 can process individual pixels (or some pixels) of the grayscale images 116 in order to determine a respective gradient for the individual pixels. The gradient for particular pixel can be based on surrounding pixels, including immediately adjacent pixels. A gradient corresponds to a vector having a direction in which the brightness level of pixels in that direction increases. For example, the brightness level of a pixel is lower or less bright than the brightness level of other pixels in the direction of the gradient. The image mark 122 implements logic that marks, for the determined gradient of each pixel, a point in the direction of the gradient that is within the distance equal to a radii (e.g., actual radius, radius of curvature) of the rounded object(s). For example, the user can indicate (via a user input 126) that the rounded object to be detected has a radius of a certain size or approximate pixel length. For example, the approximated pixel length can be set to twenty pixels. In other examples, the approximated pixel length can be assumed or predetermined based on previously stored information about the size of the rounded object in the image. Using the determined gradient, for each pixel, the image mark 122 can mark a point within the twenty pixel length of that particular pixel in the direction of the gradient that has the highest brightness level. This can represent a center or middle of the rounded object. Based on the plurality of markings (e.g., a marking for each pixel of the grayscale image 116), the object detect 110 can assume that a region of the image having a plurality of markings corresponds to the center of the rounded object and can determine the location or position of the rounded object(s) in each grayscale image 116 (if any exists). The determined position information of the rounded object can be relative to the image.
The gradient detect 120 can also access parameters (that can be stored in a database or list in a memory resource of the computing device) in determining the gradient for each pixel in the grayscale image 116. A parameter, for example, can include a brightness threshold and a gradient threshold. The brightness threshold can instruct the gradient detect 120 to ignore computing a gradient for a particular pixel if adjacent pixels (pixels in a direction moving away from the particular pixel within a radius distance of that particular pixel), do not show a pattern of increasing in brightness. In another example, a gradient threshold can instruct the gradient detect 120 to ignore computing a gradient for a particular pixel if adjacent pixels do not show a strong enough change in brightness levels in a direction moving away from the particular pixel. For pixels where gradients are not computed, no markings would be provided by the image mark 122.
In another embodiment, the object detect 110 can apply different radii of a rounded object in order to detect the rounded object in the grayscale images 116. Because the gradient detect 120 and the image mark 122 can process each individual pixel in a grayscale image 116, the object detect 110 assumes that the radii used to detect the rounded object can vary from one region of the image to another, for each grayscale image 116. Due to the angle, the orientation, the distance, and the positioning of the image capturing device in relation to the rounded object(s), a rounded object(s) can vary in size depending on how close it is to the user. The object detect 110 can receive information about the orientation and the positioning of the image capturing device (e.g., where the lens of the image capturing device is pointed at or focused on) to determine whether a given pixel in an image represents the ground or floor that is closer to the user or user's feet, or whether the pixel represents a point that is further away from the user (e.g., closer to the horizon). The object detect 110 further assumes that if a particular point in the image represents a region that is closer to the user, then the rounded object at or near that point would typically be larger in the image than if the rounded object was further away from the user. As a result, for a point that represents a region closer to the user, the image mark 122 can apply a larger radius when marking a region in the direction of the gradient of that point (as the rounded ball to be detected is assumed to be larger in the image).
For a point that represents a region that is further away from the user, the rounded object at or near that point would typically appear to be smaller in the image. As a result, after determining that the given point represents a region further away from the user, the image mark 122 can apply a smaller radius when marking a region in the direction of the gradient for that point (e.g., ten pixel lengths instead of twenty pixel lengths). In this manner, the object detect 110 can also determine whether the rounded object is moving in one or more directions, as the rounded object can become larger in size from one image to another in a sequence of images (e.g., if it is moving closer to the user) or become smaller in size from one image to another (e.g., if it is moving further away from the user).
For example, based on the accelerometer and/or other sensing mechanisms of the computing device, the computing device can detect its position relative to the ground. In addition, the computing device can determine the ground plane and horizon of the image(s) being provided by the image capturing device. Based on the determined information, if the user is holding the computing device in a way so that the lens of the image capturing device is pointing to an area that is closer to her, for example, the computing device can increase the radius (e.g., size) of rounded objects that are being detected. On the other hand, if the user is holding the computing in a way so that the lens of the image capturing device is pointing to an area that is further away from the user (e.g., a further distance away proximity), the radius of rounded objects that are being detected can be decreased.
As discussed, for each determined gradient (for each pixel), the image mark 122 can mark a point (e.g., a location in or with the image) in the direction of the gradient that is within the distance equal to the radius of the rounded object(s). In this manner, instead of the user indicating that the rounded object to be detected has a certain radius, the image mark 122 can mark a point within a varying radius in the direction of the gradient that has the highest brightness level. The radius can be varied depending on whether the lens of the image capturing device of the computing device is pointing to an area that is closer to or further from the user.
In some embodiments, the estimated size of the one or more rounded objects can be automatically configured and/or stored in a memory resource of the computing device. For example, a rounded object can be a self-propelled device having a rounded housing (e.g., a spherical housing) that is paired or wirelessly connected with the user's computing device. Information about the user's self-propelled device can be stored in the memory resource of the computing device.
The object detect 110 can also apply different types of filters depending on the user input 126. In some embodiments, the image filter 112 can apply other types of filters depending on the color(s) of the rounded object(s) of interest that is being detected by the object detect 110. If the rounded object of interest is dark in color, for example, the user can provide an input 126 that indicates the color of the ball.
The object detect 110 can detect one or more rounded objects in one or more images and also provide information corresponding to the detected objects. Information about the detected objects can include the color of the object, the size, the shape (e.g., ellipse or sphere), the position of the object relative to the image, etc. In one embodiment, the information about the detected rounded object(s) can be stored in a memory resource of the computing device.
According to one or more embodiments, system 100 utilizes the detected one or more objects from the image(s) (including the position information of the one or more objects) as input for performing one or more operations or processes on the computing device. In the example system of
In some embodiments, system 100 can determine that a rounded object of interest is moving based on the object detected images 124. For example, two or more images corresponding to different instances in time (e.g., in sequence) can include a rounded object corresponding to the object of interest in the scene. In the first image of two or more images, the rounded object can be detected at a first position relative to that image. In the next image in the sequence, the rounded object can be detected at a second position relative to that image. As a result of the change in position of the detected rounded object in different images, the device control 150 and/or the image adjust 130 can determine that the rounded object is in motion (or has moved). In other examples, the rounded object of interest can be in a stationary position, but be rotating in place. The rotating rounded object can be detected in the image(s).
Still further, the rounded object detected from image input can be translated into a coordinate data for a given reference frame relevant to the image depiction. This coordinate reference frame can be translated into a real-world coordinate system in order to observe and/or predict position related information about the object of interest. The position of the object of interest can thus be mapped from an image depiction of the object, given that the depth of the object from the image capturing device can be determined from dimensional analysis of the object's depiction. In addition to position information, the velocity of the object of interest can be determined from the reference frame of the image depiction of the object, as mapped to the determined reference frame of the real-world object of interest.
In another example, the object of interest having a rounded characteristic can be placed on top of an object with a known height instead of on the ground or floor (e.g., on top of a coffee table or on top of a remote controlled toy truck). Using the known (or pre-determined) information about the object of interest and the known height, the object detect 110 can determine a more accurate position of the object in the image(s). In addition, based on the information (such as the known information and height) and the reference frames, the image adjust 130 can provide images that are to be rendered on a display device that are dimensionally accurate (with respect to the actual location of the object of interest and the position of the image capturing device).
For example, the image adjust 130 can process the object detected images 124 in order to dynamically adjust at least a portion of an image. The image adjust 130 can also access a set of rules for mapping the coordinate reference frame and the real-world coordinate system so that the rendered adjusted images can be dimensionally accurate with respect to the real-world scene. The rules can correspond to real world parameters. In some example, the real world parameters can be altered, e.g., by user input, if a dimensionally accurate rendition is not desired.
The image adjust 130 can also store the adjusted image 132 in a memory resource of the computing device. This enables a user to access the memory resource in order to view any of the stored adjusted images 132 at a later time. In other embodiments, system 100 can enable additional processing of the images for performing other operations. The image adjust 130, for example, can access the previously processed images and perform additional adjustments to the images. In some variations, the processes performed by the object detect 110 and/or image adjust 130 can be performed on images that are stored, rather than “live” or in real-time. Thus, for example, the processes described with the object detect 110 and the image adjust 130 can optionally be temporally shifted with respect to when the images are captured and/or stored.
In other examples, the image adjust 130 can dynamically overlay or replace the detected rounded object in the image with a graphic image (e.g., a character, an animal, some other object other than a ball) or after the image of the detected rounded object itself (e.g., change the color of the rounded object, or distort the rounded object) in real-time. The adjusted image 132 can be provided to the UI component 140 so that the user of the computing device can see on a display device, rendered content that includes the adjusted detected object. The UI component 140 can also generate one or more features that can be presented on the display device of the computing device. As described, in some examples, the adjusted content that is rendered can be dimensionally accurate with respect to the position of the actually object of interest and the position of the image capturing device.
For example, the user can watch a live sporting event (e.g., kids playing soccer at a park) and point the lens of her computing device at the field. The visual input 114 received can include a plurality of frames of images detected by the image capturing device. The object detect 110 can detect the rounded object (corresponding to the object of interest, e.g., the soccer ball) in each of the sequence of images (e.g., the position of the ball can be different in each image because the ball is in motion). The image adjust 130 can process the detected object (e.g., the detected soccer ball) by highlighting the ball or providing a ring around the ball and providing the images to the UI component 140. The user is then able to see the adjusted images 132 (with any additional features) on the display device of the computing device.
In other embodiments, the device control 150 can process the object detected images 124 in order to provide one or more controls for a remote device. For example, the detected rounded object can be a self-propelled device that is paired or wirelessly connected with the user's computing device. The user can see the representations of the received visual input 114 that includes the detected rounded object (e.g., the user's self-propelled device) on the display device of the computing device. The user can then interact with the displayed representation of the self-propelled device on the touch-sensitive display screen by providing user input 152 (e.g., touch input on the touch-sensitive display screen) to the device control 150.
The device control 150 receives object detected images 124 and the user input 152 to determine what types of control information to generate 154. Based on the received information corresponding to the detected rounded object via object detected images 124, the control information 154 can be determined by detecting the user input 152 on a particular location of the display screen, for example, and determining that the location corresponds to the detected rounded object on the image. For example, the user can tap on the displayed representation of the self-propelled device to cause it to spin, for example, or tap and drag his or her finger in a direction to cause the self-propelled device to move accordingly. The control information 154 is provided on the WCOM 160 so that the information can be provided to a remote device.
For example, the device control 150 determines the position of the detected rounded object in the object detected image(s) 124 (e.g., the position of the detected rounded object relative to the image). When the user provides an input or performs a gesture on the representation of the self-propelled device (e.g., drags the representation to the right on the touch-sensitive display), the device control 150 can determine the path of the gesture, relative to a reference (e.g., the original position of the displayed representation of the self-propelled device), and translate the gesture to control signals for moving the self-propelled device in a similar manner. The control signals can be provided to the self-propelled device to cause the self-propelled device to move accordingly.
The WCOM 160 serves to exchange data between system 100 and other external devices (e.g., such as a remote device or the user's self-propelled device). In one embodiment, WCOM 160 can implement a variety of different protocols, such as a BLUETOOTH communications protocol, a Wi-Fi communications protocol, infrared communications protocol, etc. The control information 154 can be wireless communicated to the remote device (e.g., the self-propelled device, for example) to cause the self-propelled device to perform a designated action corresponding to the user command.
In some embodiments, the device control 150 can provide control information 154 for calibrating one or more components of the remote device (or for calibrating one or more components of the computing device). For example, the rounded object of interest (e.g., the user's self-propelled device) can have one or more gyroscopes. Over time, the gyroscope may need recalibration due to gyroscope drift. By using the object detected images 124, the device control 150 can detect whether the self-propelled device is moving, for example, or whether it is stationary, and provide control information 154 (that includes calibration information) to be transmitted to the self-propelled device via WCOM 160. Based on detecting the line of movement of the self-propelled device and the object detected images 124, the device control 150 can calibrate the gyroscope of the self-propelled device. In one embodiment, the device control 150 can also receive device information 162 from the self-propelled device that includes current information about the components of the self-propelled device (including real-time information about the gyroscope). The device control 150 can use this information for calibrating the gyroscope of the self-propelled device. In this manner, system 100 can be used to eliminate gyroscope drift.
Similarly, the one or more gyroscopes of the computing device can also be calibrated using the detected rounded object. For example, when the rounded object is determined to be still or stationary, the device control 150 can calibrate the gyroscope of the computing device by using the detected rounded object as a reference point.
The object detect 110 can also provide object detected images 118 to other components or systems of the computing device and/or to remote devices (not shown in
According to one or more embodiments, the visual input 114 received by system 100 can also be provided from an image capturing device that is remote from the computing device. For example, the image capturing device can be separate from the computing device. The image capturing device can detect and/or capture scenes and transmit the visual input 114 to the computing device (e.g., using a wire or wirelessly). System 100 can receive the visual input 114 via the WCOM 160, for example, when the visual input 114 is received wirelessly from the image capturing device. System 100 can then detect one or more rounded objects from the images received from the remote image capturing device and perform additional operations based on the processed detected objects.
In another embodiment, system 100 can receive the images (e.g., frames from real-time video) and then process the images (e.g., detect one or more rounded objects and/or adjust the images) after a duration of time. For example, the visual input 114 provided by the image capturing device can first be stored in a memory resource of the computing device before the object detect 110 retrieves or receives the visual input 114 for processing. The object detect 110 can perform the processing in response to a user input 126 (thereby causing the visual input 114 to be retrieved or received by the object detect 110 from the memory resource). In other embodiments, system 100 can perform additional processing even after the images are dynamically processed. For example, after the image adjust 130 processes the object detected images 124 the first time, at a later time, the image adjust 130 can perform additional processing to provide different adjusted images 132 to the UI component 140. In this manner, a user can view different adjusted images 132 (e.g., an adjusted image with different graphic image overlays) at different times.
In some embodiments, some of the components that are described in system 100 can be provided as being individual components or as being part of the same component. For example, the object detect 110 and the image adjust 130 can be provided as part of the same component. In another example, the object detect 110 and the device control 150 can be provided as part of the same component. In other embodiments, the components that are described in system 100 can be provided as part of the device operating system or as part of one of more applications (e.g., as part of a camera application, a remote device controlling application, or a gaming application). Logic can be implemented with a camera application (e.g., software) and/or with hardware of the image capturing device.
In some examples, the object of interest can alternatively have other predefined shapes that can be subject to dimensional and image analysis in order to detect objects in one or more images. For example, system 100 can utilize other object detection and/or image processing techniques to detect objects having shapes other than a rounded shape, such as a classifier that is trained for detecting an object with a particular two-dimensional shape (e.g., having a rectangular shape or triangular shape). The object detect 110 can detect other predefined shapes to translate dimensional information about an image of that object into spatial and/or positional information in the real-world.
As an addition or alternative, examples described herein can also be used for adjacent object analysis. In adjacent object analysis, position information about an object that is adjacent to the object of interest can be determined based on its known spatial relationship with the object of interest. For example, the object of interest can be a tank vehicle, where the position of the tank vehicle can be determined in the image(s). The gun that the tank vehicle is equipped with can also be tracked using adjacent object analysis.
Still further, multiple objects of interest (e.g., having a rounded or spherical shape) can be simultaneously tracked in one or more images of a given scene. The objects of interest can be in motion or be stationary. The object detect 110 can detect multiple objects of interest along with the position information for each tracked object. The position of each tracked object relative to other tracked objects can be used to determine other objects or points of interest that may be intermediate to the objects of interest. For example, multiple spherical objects can be detected and tracked in images to determine a point cloud for purpose of determining the position of other objects that may be near one or more of the tracked objects.
Methodology
The computing device can receive a plurality of images from its image capturing device (step 200). The plurality of images can correspond to visual input of a scene that the lens of the image capturing device is pointing at or focused on. In some embodiments, the image input can correspond to real-time video that is provided by the image capturing device (sub-step 202). Real-time video can include a number of frames (where each frame can be an image) that are detected and/or captured per second (e.g., 30 frames per second).
Each of the images can be individually processed to detect one or more rounded objects in the images (step 210). The computing device can operate an image recognition software and/or other image processing methods in order to detect the rounded object(s) in each image. A rounded object in an image can correspond to an object of interest that is present in the scene and having a rounded housing characteristic. In one embodiment, the rounded object(s) can be detected by applying known information for determining object(s) of interest (sub-step 212). The known information can be provided by a user or can be preconfigured and/or stored in a memory resource of the computing device.
According to one or more embodiments, the known information can include the size of the rounded object(s) of interest (sub-step 214). The size of the rounded object(s) can correspond to the radius (or radii for ellipses, for example) of the object or the diameter of the object, or in some cases, the relative size as compared to the screen size of the display device. The one or more rounded objects can be detected in each of the images by using size information about the rounded object(s), such as a radius or diameter of a rounded object (e.g., in pixel lengths). In addition, known information can include information corresponding to the positioning of the computing device with respect to the ground plane (sub-step 216). Based on the orientation, direction, and position in which the user is pointing the lens of the computing device, the rounded object(s) can be determined as being smaller in size (relative to the screen size) or larger in size. In such cases, the radius or diameter of the rounded object can dynamically vary in size. A rounded object can be detected in each image, for example, by applying a grayscale filter, such as discussed in
By detecting one or more rounded objects in the images, the computing device can utilize the detected object(s) and the position information of the detected object(s) as input for performing one or more operations or processes on the computing device (step 220). For example, the computing device can adjust the images, for display on a display device, by generating an overlay or by replacing the detected rounded object(s) in the image with a graphic feature that mimics the movement of the rounded object(s) in the images (sub-step 222). Such graphical adjustments can be useful for gaming applications that use real world scenarios as part of the game.
In one embodiment, the overlay can also be a graphic feature having three-dimensional characteristics. The graphic feature can be rendered as part of the displayed images so that it is consistent with the three-dimensionality and movement of the detected rounded object. For example, if the rounded object rotates in 180 degrees, the overlaid graphic feature can also rotate in a similar feature.
The computing device can also process the detected object(s) as input for wirelessly controlling the detected rounded object(s) (e.g., the self-propelled device) (sub-step 224). For example, the user can manipulate the image containing the representation of the self-propelled device on the display device in order to control the actual self-propelled device (e.g., the object of interest) to move in a certain direction with a certain speed. The user can also tap a target location on the touch-sensitive display screen in order to cause the self-propelled device to move to the target location. In another embodiment, the detected rounded object(s) can be used as input for projecting or displaying images based on real life objects in the vicinity of the user and the real life rounded object (sub-step 226). The detected rounded object(s) can also be used for calibrating one or more components of the detected rounded object (sub-step 228).
Other applications of processing the detected object(s) as input may include tracking balls in ball sports, or using balls and/or circular discs as being markers or fixed reference points (e.g., fiducial markers). The discs, for example, can be used as a reference point or measurement point for placing other objects in the image(s). In addition, other applications include using the detected object(s) for spatial mapping or navigation. Points, object positions, navigation way-points, etc. can all be given virtual locations which correspond with concrete locations over a long period of time. The computing device can provide information about the location and position of the detected rounded object to the rounded object so that the rounded object (e.g., self-propelled device) can measure its own progress toward target locations and navigate itself to locations. In other applications, based on the detected rounded object(s), absolute positions of objects of known height can be calculated by selecting (e.g., tapping on the display screen) the objects' locations from the image(s).
After the computing device detects the rounded object and the location or position of the rounded object in the plurality of images, the detected rounded object can be utilized as input for performing one or more additional operations. In one embodiment, the image(s) can be adjusted by visually altering the detected rounded object. For example, the user can operate the computing device in order to play a game (e.g., operate a gaming application). In
Each of the images can be processed to detect the spherical object, and the detected spherical object can be processed as input so that, on the display device of the computing device, the displayed dragon also moves accordingly. In some variations, the images being rendered can be dynamically adjusted. For example, the graphic image of the dragon can be dynamically changed to a graphic image of a lizard in response to a trigger, such as a user input or the object of interest being moved to a particular location or next to another object of interest.
As an addition or alternative, a computing device, such as a device that implements system 100 of
For example, multiple users can engage with one another in a gaming environment, where a first user controls the movement of the object of interest using a first computing device, while a second user and a third user track the object of interest and render content on their respective computing devices. A fourth user can use a fourth computing device to control what content is being displayed on the second and third users' devices (e.g., dynamically adjust what graphic image is displayed in place of the detected object). For example, in one implementation, the second user can track the object of interest and view rendered content that is different than content that is rendered on a computing device of the third user (e.g., based on the fourth user controlling what content is to be displayed to individual users). The computing devices can communicate with each other via a wireless communication protocol, such as Bluetooth or Wi-Fi.
In another usage example, multiple users with respective computing devices can detect and track ten objects of interest, including one or more self-propelled devices. Control over one or more objects of interest can be passed between the users.
Hardware Diagram
The processing resources 410 are configured with software and/or other logic to perform one or more processes, steps and other functions described with embodiments, such as described by
The processing resources 410 can execute instructions for operating the object detect and for receiving images (via visual input 462) that have been captured by the lens and/or other components 460 of the image capturing device. After detecting one or more rounded objects in the one or more images, the processing resources 410 can execute instructions for causing adjusted images 412 to be presented on the display device 430. The processing resources 410 can also execute instructions to provide device controls 414 for a remote device via the communication sub-systems 440.
In some embodiments, the processing resources 410 can execute and operate a variety of different applications and/or functionalities, such as, for example, a home page or start screen, an application launcher page, messaging applications (e.g., SMS messaging application, e-mail application, IM application), a phone application, game applications, calendar application, document application, web browser application, clock application, camera application, media viewing application (e.g., for videos, images, audio), social media applications, financial applications, and device settings.
Interactive Augmented Reality
In many embodiments, the method further includes interfacing with a second computing device that provides a virtual environment in order to cause the second computing device to render a virtual entity upon the virtual environment (504). The virtual entity may correspond to the self-propelled device moving in the real-world environment. In many embodiments, the interfacing may be performed by the mobile computing device. For example, a user of the mobile computing device may launch an application that causes the mobile computing device to interface with the second computing device. Alternatively or as an addition, the second computing device may perform the function of interfacing with the mobile computing device. For example, a user of the second computing device may provide an input that causes the second computing device to interface with the mobile computing device. The second computing device may include a controller, whereby the user may operate the controller to interact with the virtual environment. Using the controller, the user may then prompt the second computing device to interface with the mobile computing device.
In many embodiments, once the mobile computing device and the second computing device have interfaced, some or all of the virtual environment may then be displayed on the mobile computing device via the second computing device (506). A virtual entity corresponding to the self-propelled device can also also be rendered in the virtual environment (508). For example, a character in the virtual environment may represent the self-propelled device in the real-world environment. In these and related embodiments, a user of the mobile computing device may simultaneously control the self-propelled in the real-world environment and the virtual entity in the virtual environment. In related embodiments, the virtual environment may be provided as augmented reality, and the virtual entity corresponding to the self-propelled device may interact in the augmented reality.
In many embodiments, the method further includes detecting an event relating to the self-propelled device in the real-world environment, then generating a virtual event based on the detected event (510). For example, the detected event may relate to a particular movement or interaction of the self-propelled device in the real-world environment. The event may be detected by either the mobile computing device or the second computing device via the interface. The mobile computing device may then incorporate the virtual event into the virtual environment. In doing so, the mobile computing device may translate that particular movement or interaction as a virtual event, such as a control or command in the virtual environment. As an addition or alternative, the real-world event may relate to the self-propelled device impacting a surface. Such an impact may correspond to a virtual event in which the virtual entity performs a function. The function may be configured by the user, or may be preprogrammed in a game or application.
Referring to
The virtual environment 612, provided by the second computing device may be displayed on the mobile computing device 604. The virtual environment 612 may be an environment developed for user interaction through the second computing device 602. For example, the virtual environment 612 may be a three-dimensional map provided through an online computer program. Alternatively, the virtual environment 612 may be a mediated, or an augmented reality map of the real world with any number or variety of customizations. As an addition or alternative, the virtual environment 612 may be provided by a gaming console as part of, for example, a mobile game, mini game, an emergent game, etc.
Additionally, the mobile computing device 604 can be further configured to access saved data associated with the virtual environment 612 stored on the second computing device 602. The saved data may, for example, correspond to previous interactions by the user within the virtual environment 612. Similarly, the second computing device 602 can be further configured to convey the saved data to the mobile computing device 604, and congruently link the previous interactions within the virtual environment 612 to the mobile computing device 604. Thus, for example, a user playing a game having a virtual environment 612 on the second computing device 602, may save data associated with that game, and subsequently access the saved data using the mobile computing device 604, and utilize the self-propelled device 608 as a virtual character 610 (as shown in
Referring to
Thus, in practice, the user may play a character anywhere in the real world by operating the self-propelled device 608 in a real world environment. A parallel augmented reality world may be displayed on the mobile computing device 608 with the virtual entity 610 in the virtual environment 612 corresponding to the self-propelled device 608. Using the controls 614 for the self-propelled device 608, the user can operate the self-propelled device 608 and arrange it to interact with the augmented reality environment 612 via the virtual entity 610.
It is contemplated for embodiments described herein to extend to individual elements and concepts described herein, independently of other concepts, ideas or system, as well as for embodiments to include combinations of elements recited anywhere in this application. Although embodiments are described in detail herein with reference to the accompanying drawings, it is to be understood that the invention is not limited to those precise embodiments. As such, many modifications and variations will be apparent to practitioners skilled in this art. Accordingly, it is intended that the scope of the invention be defined by the following claims and their equivalents. Furthermore, it is contemplated that a particular feature described either individually or as part of an embodiment can be combined with other individually described features, or parts of other embodiments, even if the other features and embodiments make no mentioned of the particular feature. Thus, the absence of describing combinations should not preclude the inventor from claiming rights to such combinations.
One or more embodiments described herein provide that methods, techniques and actions performed by a computing device are performed programmatically, or as a computer-implemented method. Programmatically means through the use of code, or computer-executable instructions. A programmatically performed step may or may not be automatic.
One or more embodiments described herein may be implemented using programmatic modules or components. A programmatic module or component may include a program, a subroutine, a portion of a program, or a software component or a hardware component capable of performing one or more stated tasks or functions. As used herein, a module or component can exist on a hardware component independently of other modules or components. Alternatively, a module or component can be a shared element or process of other modules, programs or machines.
Furthermore, one or more embodiments described herein may be implemented through the use of instructions that are executable by one or more processors. These instructions may be carried on a computer-readable medium. Machines shown or described with FIGS. below provide examples of processing resources and computer-readable mediums on which instructions for implementing embodiments of the invention can be carried and/or executed. In particular, the numerous machines shown with embodiments of the invention include processor(s) and various forms of memory for holding data and instructions. Examples of computer-readable mediums include permanent memory storage devices, such as hard drives on personal computers or servers. Other examples of computer storage mediums include portable storage units (such as CD or DVD units), flash memory (such as carried on many cell phones and tablets)), and magnetic memory. Computers, terminals, network enabled devices (e.g., mobile devices such as cell phones) are all examples of machines and devices that utilize processors, memory and instructions stored on computer-readable mediums. Additionally, embodiments may be implemented in the form of computer-programs, or a computer usable carrier medium capable of carrying such a program.
Although illustrative embodiments have been described in detail herein with reference to the accompanying drawings, variations to specific embodiments and details are encompassed by this disclosure. It is intended that the scope of the invention is defined by the following claims and their equivalents. Furthermore, it is contemplated that a particular feature described, either individually or as part of an embodiment, can be combined with other individually described features, or parts of other embodiments. Thus, absence of describing combinations should not preclude the inventor(s) from claiming rights to such combinations.
While certain embodiments of the inventions have been described above, it will be understood that the embodiments described are by way of example only. Accordingly, the inventions should not be limited based on the described embodiments. Rather, the scope of the inventions described herein should only be limited in light of the claims that follow when taken in conjunction with the above description and accompanying drawings.
This application is a continuation-in-part of U.S. application Ser. No. 13/894,247 (now U.S. Pat. No. 9,280,717), filed May 14, 2013, entitled “OPERATING A COMPUTING DEVICE BY DETECTING ROUNDED OBJECTS IN AN IMAGE”, which claims priority to U.S. Provisional Patent Application Ser. No. 61/646,716, filed May 14, 2012, entitled “OPERATING A COMPUTING DEVICE BY DETECTING ROUNDED OBJECTS IN AN IMAGE”, the disclosures of which are hereby incorporated by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
90546 | Huntington | May 1869 | A |
933623 | Cecil | Sep 1909 | A |
1263262 | McFaul | Apr 1918 | A |
2796601 | Hagopian | Nov 1956 | A |
2949696 | Easterling | Aug 1960 | A |
2977714 | Gibson | Apr 1961 | A |
3313365 | Jackson | Apr 1967 | A |
3667156 | Tomiyama | Jun 1972 | A |
3683216 | Post | Aug 1972 | A |
3821995 | Aghnides | Jul 1974 | A |
4310987 | Chieffo | Jan 1982 | A |
4519466 | Shiraishi | May 1985 | A |
4541814 | Martin | Sep 1985 | A |
4601675 | Robinson | Jul 1986 | A |
4733737 | Falamak | Mar 1988 | A |
4897070 | Wagstaff | Jan 1990 | A |
4996468 | Field et al. | Feb 1991 | A |
5087000 | Suto | Feb 1992 | A |
5213176 | Oroku et al. | May 1993 | A |
5297981 | Maxim et al. | Mar 1994 | A |
5342051 | Rankin et al. | Aug 1994 | A |
5413345 | Nauck | May 1995 | A |
5439408 | Wilkinson | Aug 1995 | A |
5489099 | Rankin et al. | Feb 1996 | A |
5513854 | Daver | May 1996 | A |
5595121 | Elliot | Jan 1997 | A |
5628232 | Bakholdin et al. | May 1997 | A |
5644139 | Allen et al. | Jul 1997 | A |
5676582 | Lin | Oct 1997 | A |
5739657 | Takayama et al. | Apr 1998 | A |
5759083 | Polumbaum et al. | Jun 1998 | A |
5780826 | Hareyama et al. | Jul 1998 | A |
5793142 | Richard | Sep 1998 | A |
5871386 | Bart et al. | Feb 1999 | A |
5952796 | Colgate et al. | Sep 1999 | A |
5953056 | Tucker | Sep 1999 | A |
6144128 | Rosen | Nov 2000 | A |
6227933 | Michaud et al. | May 2001 | B1 |
6246927 | Dratman | Jun 2001 | B1 |
6315667 | Steinhart | Nov 2001 | B1 |
6320352 | Terazoe | Nov 2001 | B2 |
6390213 | Bleicher | May 2002 | B1 |
6439956 | Ho | Jul 2002 | B1 |
6449010 | Tucker | Sep 2002 | B1 |
6456938 | Barnard | Sep 2002 | B1 |
6458008 | Hyneman | Oct 2002 | B1 |
6459955 | Bartsch et al. | Oct 2002 | B1 |
6502657 | Kerrebrock et al. | Jan 2003 | B2 |
6535793 | Allard | Mar 2003 | B2 |
6573883 | Bartlett | Jun 2003 | B1 |
6584376 | Van Kammer | Jun 2003 | B1 |
6615109 | Matsuoka et al. | Sep 2003 | B1 |
6764373 | Osawa et al. | Jul 2004 | B1 |
6785590 | Kasuga et al. | Aug 2004 | B2 |
6786795 | Mullaney et al. | Sep 2004 | B1 |
6789768 | Kalisch | Sep 2004 | B1 |
6856696 | Ajioka | Feb 2005 | B1 |
6901110 | Tsougarakis et al. | May 2005 | B1 |
6902464 | Lee | Jun 2005 | B1 |
6945843 | Motosko | Sep 2005 | B1 |
6980956 | Takagi et al. | Dec 2005 | B1 |
7058205 | Jepson et al. | Jun 2006 | B2 |
7069113 | Matsuoka et al. | Jun 2006 | B2 |
7130741 | Bodin et al. | Oct 2006 | B2 |
7170047 | Pal | Jan 2007 | B2 |
7173604 | Marvit et al. | Feb 2007 | B2 |
7258591 | Xu et al. | Aug 2007 | B2 |
7283647 | McNitt | Oct 2007 | B2 |
7292711 | Kiraly et al. | Nov 2007 | B2 |
7298869 | Abernathy | Nov 2007 | B1 |
7324663 | Kiraly | Jan 2008 | B2 |
7328671 | Kates | Feb 2008 | B2 |
7340077 | Gokturk et al. | Mar 2008 | B2 |
7340344 | Chappell | Mar 2008 | B2 |
7344430 | Hasty et al. | Mar 2008 | B2 |
7409924 | Kates | Aug 2008 | B2 |
7424867 | Kates | Sep 2008 | B2 |
7432718 | Ishihara et al. | Oct 2008 | B2 |
7463001 | Tsurukawa | Dec 2008 | B2 |
7501780 | Yamamoto | Mar 2009 | B2 |
7526362 | Kim et al. | Apr 2009 | B2 |
7542597 | Rahn et al. | Jun 2009 | B2 |
7639874 | Bushell et al. | Dec 2009 | B2 |
7699683 | Caspi | Apr 2010 | B2 |
7702131 | Chinen et al. | Apr 2010 | B2 |
7714880 | Johnson | May 2010 | B2 |
7714895 | Pretlove | May 2010 | B2 |
7726422 | Sun et al. | Jun 2010 | B2 |
7755660 | Nejikovsky et al. | Jul 2010 | B2 |
7822507 | Ishihara et al. | Oct 2010 | B2 |
7847504 | Hollis | Dec 2010 | B2 |
7853357 | Sawada et al. | Dec 2010 | B2 |
7899226 | Pescatore et al. | Mar 2011 | B2 |
7957837 | Ziegler et al. | Jun 2011 | B2 |
7979162 | Niemela et al. | Jul 2011 | B2 |
8025551 | Torres et al. | Sep 2011 | B2 |
8038504 | Wong | Oct 2011 | B1 |
8077981 | Elangovan et al. | Dec 2011 | B2 |
8099189 | Kaznov et al. | Jan 2012 | B2 |
8128450 | Imai | Mar 2012 | B2 |
8128500 | Borst et al. | Mar 2012 | B1 |
8142287 | Podoloff | Mar 2012 | B2 |
8144118 | Hildreth | Mar 2012 | B2 |
8180436 | Boyden et al. | May 2012 | B2 |
8190295 | Garretson | May 2012 | B1 |
8195333 | Ziegler et al. | Jun 2012 | B2 |
8197298 | Willett | Jun 2012 | B2 |
8210289 | Lu et al. | Jul 2012 | B1 |
8258917 | Cai et al. | Sep 2012 | B2 |
8269447 | Smoot et al. | Sep 2012 | B2 |
8274406 | Karlsson et al. | Sep 2012 | B2 |
8275544 | Wells et al. | Sep 2012 | B1 |
8326469 | Phillips et al. | Dec 2012 | B2 |
8330639 | Wong et al. | Dec 2012 | B2 |
8352643 | Bimbaum et al. | Jan 2013 | B2 |
8355818 | Nielsen et al. | Jan 2013 | B2 |
8364136 | Hoffberg et al. | Jan 2013 | B2 |
8376756 | Robb | Feb 2013 | B2 |
8392065 | Tolstedt et al. | Mar 2013 | B2 |
8396611 | Phillips et al. | Mar 2013 | B2 |
8400619 | Bachrach et al. | Mar 2013 | B1 |
8417384 | Togawa et al. | Apr 2013 | B2 |
8430192 | Gillett | Apr 2013 | B2 |
8442661 | Blackwell et al. | May 2013 | B1 |
8456298 | Valtonen | Jun 2013 | B2 |
8459383 | Burget | Jun 2013 | B1 |
8522902 | Gomi et al. | Sep 2013 | B2 |
8540038 | Ullman | Sep 2013 | B1 |
8571781 | Bernstein et al. | Oct 2013 | B2 |
8577595 | Zhao et al. | Nov 2013 | B2 |
8600600 | Jung | Dec 2013 | B2 |
8670889 | Kaznov | Mar 2014 | B2 |
8672062 | Schroll et al. | Mar 2014 | B2 |
8751063 | Bernstein et al. | Jun 2014 | B2 |
8766983 | Marks et al. | Jul 2014 | B2 |
8788130 | Tran et al. | Jul 2014 | B1 |
8805947 | Kuzkin | Aug 2014 | B1 |
8838273 | Hvass et al. | Sep 2014 | B2 |
8862301 | Araki et al. | Oct 2014 | B2 |
8882559 | Fessenmaier | Nov 2014 | B2 |
8885882 | Yin et al. | Nov 2014 | B1 |
9011197 | Smoot et al. | Apr 2015 | B2 |
9014848 | Farlow et al. | Apr 2015 | B2 |
9041622 | McCulloch | May 2015 | B2 |
9090214 | Bernstein et al. | Jul 2015 | B2 |
9114838 | Bernstein et al. | Aug 2015 | B2 |
9150263 | Bernstein et al. | Oct 2015 | B2 |
9193404 | Bernstein et al. | Nov 2015 | B2 |
9211920 | Bernstein et al. | Dec 2015 | B1 |
9218316 | Bernstein et al. | Dec 2015 | B2 |
9280717 | Polo et al. | Mar 2016 | B2 |
9290220 | Bernstein et al. | Mar 2016 | B2 |
9292758 | Polo et al. | Mar 2016 | B2 |
9389612 | Bernstein et al. | Jul 2016 | B2 |
9394016 | Bernstein et al. | Jul 2016 | B2 |
9395725 | Berstein et al. | Jul 2016 | B2 |
9429940 | Bernstein et al. | Aug 2016 | B2 |
9457730 | Berstein et al. | Oct 2016 | B2 |
9481410 | Bernstein et al. | Nov 2016 | B2 |
9483876 | Polo et al. | Nov 2016 | B2 |
9558612 | Lyons | Jan 2017 | B2 |
20020011368 | Berg | Jan 2002 | A1 |
20020036104 | Kerrebrock et al. | Mar 2002 | A1 |
20020142701 | Rosenberg | Oct 2002 | A1 |
20030093182 | Yokoyama | May 2003 | A1 |
20030118217 | Kondo et al. | Jun 2003 | A1 |
20030179176 | Waterston | Sep 2003 | A1 |
20030216834 | Allard | Nov 2003 | A1 |
20030216835 | Wakui | Nov 2003 | A1 |
20040002843 | Robarts et al. | Jan 2004 | A1 |
20040015266 | Skoog | Jan 2004 | A1 |
20040168837 | Michaud et al. | Sep 2004 | A1 |
20040182614 | Wakui | Sep 2004 | A1 |
20040186623 | Dooley et al. | Sep 2004 | A1 |
20040192163 | Siegel | Sep 2004 | A1 |
20040198159 | Xu et al. | Oct 2004 | A1 |
20050004723 | Duggan et al. | Jan 2005 | A1 |
20050186884 | Evans | Aug 2005 | A1 |
20050216186 | Dorfman | Sep 2005 | A1 |
20050226192 | Red et al. | Oct 2005 | A1 |
20050264472 | Rast | Dec 2005 | A1 |
20060080802 | Tani | Apr 2006 | A1 |
20060095158 | Lee et al. | May 2006 | A1 |
20060101465 | Kato et al. | May 2006 | A1 |
20060132318 | Shimizu | Jun 2006 | A1 |
20060164261 | Stiffler | Jul 2006 | A1 |
20060241812 | Juang | Oct 2006 | A1 |
20060271251 | Hopkins | Nov 2006 | A1 |
20070034734 | Yoeli | Feb 2007 | A1 |
20070085706 | Feyereisen et al. | Apr 2007 | A1 |
20070112462 | Kim et al. | May 2007 | A1 |
20070150103 | Im | Jun 2007 | A1 |
20070162862 | Ogasawara | Jul 2007 | A1 |
20070192910 | Vu | Aug 2007 | A1 |
20070249422 | Podoloff | Oct 2007 | A1 |
20070259592 | Imai et al. | Nov 2007 | A1 |
20070282484 | Chung et al. | Dec 2007 | A1 |
20080009965 | Bruemmer et al. | Jan 2008 | A1 |
20080012518 | Yamamoto | Jan 2008 | A1 |
20080033641 | Medalia | Feb 2008 | A1 |
20080077284 | Swope | Mar 2008 | A1 |
20080082208 | Hong | Apr 2008 | A1 |
20080086241 | Phillips et al. | Apr 2008 | A1 |
20080121097 | Rudakevych et al. | May 2008 | A1 |
20080174268 | Koo et al. | Jul 2008 | A1 |
20080174448 | Hudson | Jul 2008 | A1 |
20080182479 | Elliott et al. | Jul 2008 | A1 |
20080240507 | Niwa et al. | Oct 2008 | A1 |
20080263628 | Norman et al. | Oct 2008 | A1 |
20080267450 | Sugimoto et al. | Oct 2008 | A1 |
20080269949 | Norman et al. | Oct 2008 | A1 |
20090018712 | Duncan | Jan 2009 | A1 |
20090028439 | Elangovan et al. | Jan 2009 | A1 |
20090033623 | Lin | Feb 2009 | A1 |
20090055019 | Stiehl et al. | Feb 2009 | A1 |
20090057238 | Garti | Mar 2009 | A1 |
20090069084 | Reece | Mar 2009 | A1 |
20090073034 | Linsky et al. | Mar 2009 | A1 |
20090078484 | Kocijan | Mar 2009 | A1 |
20090081923 | Dooley et al. | Mar 2009 | A1 |
20090133467 | Mori et al. | May 2009 | A1 |
20090138232 | Fuwa | May 2009 | A1 |
20090153349 | Lin | Jun 2009 | A1 |
20090157221 | Sip | Jun 2009 | A1 |
20090161983 | Ciurea | Jun 2009 | A1 |
20090164638 | Jang | Jun 2009 | A1 |
20090171516 | Reich | Jul 2009 | A1 |
20090187299 | Fregene | Jul 2009 | A1 |
20090198371 | Emanuel et al. | Aug 2009 | A1 |
20090204261 | Strand et al. | Aug 2009 | A1 |
20090222148 | Knotts et al. | Sep 2009 | A1 |
20090226035 | Iihoshi et al. | Sep 2009 | A1 |
20090245656 | Hu | Oct 2009 | A1 |
20090256822 | Amireh et al. | Oct 2009 | A1 |
20090262074 | Nasiri et al. | Oct 2009 | A1 |
20090265671 | Sachs et al. | Oct 2009 | A1 |
20090278932 | Yi | Nov 2009 | A1 |
20090284553 | Seydoux | Nov 2009 | A1 |
20090316012 | Matos | Dec 2009 | A1 |
20100002909 | Lefevre et al. | Jan 2010 | A1 |
20100004798 | Bodin et al. | Jan 2010 | A1 |
20100010669 | Lee et al. | Jan 2010 | A1 |
20100010672 | Wang et al. | Jan 2010 | A1 |
20100032224 | Liu | Feb 2010 | A1 |
20100063652 | Anderson | Mar 2010 | A1 |
20100066676 | Kramer et al. | Mar 2010 | A1 |
20100084513 | Gariepy et al. | Apr 2010 | A1 |
20100090661 | Chen et al. | Apr 2010 | A1 |
20100106344 | Edwards et al. | Apr 2010 | A1 |
20100145236 | Greenberg et al. | Jun 2010 | A1 |
20100169098 | Patch | Jul 2010 | A1 |
20100172287 | Krieter | Jul 2010 | A1 |
20100178982 | Ehrman | Jul 2010 | A1 |
20100183195 | Sharma | Jul 2010 | A1 |
20100234993 | Seelinger et al. | Sep 2010 | A1 |
20100241289 | Sandberg | Sep 2010 | A1 |
20100261526 | Anderson et al. | Oct 2010 | A1 |
20100264756 | Lee et al. | Oct 2010 | A1 |
20100283988 | Mosier et al. | Nov 2010 | A1 |
20100302247 | Perez et al. | Dec 2010 | A1 |
20100302359 | Adams | Dec 2010 | A1 |
20100305778 | Dorneich et al. | Dec 2010 | A1 |
20100305781 | Felix | Dec 2010 | A1 |
20100312917 | Allport | Dec 2010 | A1 |
20100324753 | Okumatsu | Dec 2010 | A1 |
20110003640 | Ehrman | Jan 2011 | A9 |
20110018731 | Linsky et al. | Jan 2011 | A1 |
20110018794 | Linsky et al. | Jan 2011 | A1 |
20110022196 | Linsky et al. | Jan 2011 | A1 |
20110035054 | Gal et al. | Feb 2011 | A1 |
20110050940 | Lanz et al. | Mar 2011 | A1 |
20110060492 | Kaznov | Mar 2011 | A1 |
20110065488 | Okamura et al. | Mar 2011 | A1 |
20110071652 | Brown et al. | Mar 2011 | A1 |
20110071702 | Wang et al. | Mar 2011 | A1 |
20110082566 | Herr et al. | Apr 2011 | A1 |
20110087371 | Sandberg et al. | Apr 2011 | A1 |
20110138416 | Kang et al. | Jun 2011 | A1 |
20110153885 | Mak et al. | Jun 2011 | A1 |
20110156943 | Wong et al. | Jun 2011 | A1 |
20110174565 | Rochat | Jul 2011 | A1 |
20110183732 | Block et al. | Jul 2011 | A1 |
20110184590 | Duggan et al. | Jul 2011 | A1 |
20110201362 | Bregman-Amitai et al. | Aug 2011 | A1 |
20110132671 | Lee et al. | Sep 2011 | A1 |
20110213278 | Horak et al. | Sep 2011 | A1 |
20110231013 | Smoot et al. | Sep 2011 | A1 |
20110234488 | Ge et al. | Sep 2011 | A1 |
20110237324 | Clavin et al. | Sep 2011 | A1 |
20110246904 | Pinto | Oct 2011 | A1 |
20110249074 | Cranfill | Oct 2011 | A1 |
20110250967 | Kulas | Oct 2011 | A1 |
20110273379 | Chen et al. | Nov 2011 | A1 |
20110283223 | Vaittinen et al. | Nov 2011 | A1 |
20110285349 | Widmer et al. | Nov 2011 | A1 |
20110286631 | Wagner et al. | Nov 2011 | A1 |
20110291926 | Gokturk et al. | Dec 2011 | A1 |
20110304633 | Beardsley | Dec 2011 | A1 |
20110308873 | Kim et al. | Dec 2011 | A1 |
20110313568 | Blackwell et al. | Dec 2011 | A1 |
20110320830 | Ito | Dec 2011 | A1 |
20120009845 | Schmelzer | Jan 2012 | A1 |
20120035799 | Ehrmann | Feb 2012 | A1 |
20120043149 | Kim et al. | Feb 2012 | A1 |
20120043172 | Ichikawa | Feb 2012 | A1 |
20120059520 | Kossett | Mar 2012 | A1 |
20120065747 | Brown et al. | Mar 2012 | A1 |
20120072023 | Ota | Mar 2012 | A1 |
20120083945 | Oakley et al. | Apr 2012 | A1 |
20120083962 | Sato et al. | Apr 2012 | A1 |
20120099756 | Sherman et al. | Apr 2012 | A1 |
20120100915 | Margalit et al. | Apr 2012 | A1 |
20120106783 | Chang et al. | May 2012 | A1 |
20120112553 | Stoner | May 2012 | A1 |
20120129605 | Livet | May 2012 | A1 |
20120143482 | Goossen et al. | Jun 2012 | A1 |
20120146775 | Kudo et al. | Jun 2012 | A1 |
20120149359 | Huang | Jun 2012 | A1 |
20120167014 | Joo et al. | Jun 2012 | A1 |
20120168240 | Wilson | Jul 2012 | A1 |
20120168241 | Bernstein et al. | Jul 2012 | A1 |
20120173018 | Allen et al. | Jul 2012 | A1 |
20120173047 | Bernstein et al. | Jul 2012 | A1 |
20120173049 | Bernstein et al. | Jul 2012 | A1 |
20120173050 | Berstein et al. | Jul 2012 | A1 |
20120185115 | Dean | Jul 2012 | A1 |
20120193154 | Wellborn et al. | Aug 2012 | A1 |
20120197439 | Wang et al. | Aug 2012 | A1 |
20120200380 | Kocijan | Aug 2012 | A1 |
20120215355 | Bewley et al. | Aug 2012 | A1 |
20120229647 | Calman et al. | Sep 2012 | A1 |
20120232977 | Calman et al. | Sep 2012 | A1 |
20120233015 | Calman et al. | Sep 2012 | A1 |
20120240077 | Vaittinen et al. | Sep 2012 | A1 |
20120244969 | Binder | Sep 2012 | A1 |
20120258645 | Cheng | Oct 2012 | A1 |
20120262002 | Widmer et al. | Oct 2012 | A1 |
20120263154 | Blanchflower et al. | Oct 2012 | A1 |
20120291926 | Misra et al. | Nov 2012 | A1 |
20120293548 | Perez et al. | Nov 2012 | A1 |
20120298049 | Cook et al. | Nov 2012 | A1 |
20120298430 | Schroll et al. | Nov 2012 | A1 |
20120302129 | Persaud | Nov 2012 | A1 |
20120306850 | Balan et al. | Dec 2012 | A1 |
20120307001 | Osako et al. | Dec 2012 | A1 |
20120309261 | Boman | Dec 2012 | A1 |
20120311810 | Gilbert et al. | Dec 2012 | A1 |
20130022274 | Lawrence Ashok Inigo | Jan 2013 | A1 |
20130040533 | Miller | Feb 2013 | A1 |
20130050069 | Ota | Feb 2013 | A1 |
20130065482 | Trickett | Mar 2013 | A1 |
20130105239 | Fung | May 2013 | A1 |
20130109272 | Rindlishbacher | May 2013 | A1 |
20130113307 | Kim et al. | May 2013 | A1 |
20130143482 | Regier | Jun 2013 | A1 |
20130173089 | Bernstein et al. | Jul 2013 | A1 |
20130200207 | Pongratz | Aug 2013 | A1 |
20130265225 | Nasiri et al. | Oct 2013 | A1 |
20130293584 | Anderson | Nov 2013 | A1 |
20130307875 | Anderson | Nov 2013 | A1 |
20140008496 | Ye | Jan 2014 | A1 |
20140015493 | Wirz et al. | Jan 2014 | A1 |
20140120887 | Huang | May 2014 | A1 |
20140207280 | Duffley | Jul 2014 | A1 |
20140238762 | Berberian et al. | Aug 2014 | A1 |
20140249697 | Fredriksson | Sep 2014 | A1 |
20140371954 | Lee et al. | Dec 2014 | A1 |
20150091697 | Takayasu | Apr 2015 | A1 |
20150175202 | MacGregor | Jun 2015 | A1 |
20150209664 | Haseltine | Jul 2015 | A1 |
20150268666 | Wang et al. | Sep 2015 | A1 |
20160033967 | Bernstein et al. | Feb 2016 | A1 |
20160054734 | Bernstein et al. | Feb 2016 | A1 |
20160090133 | Bernstein et al. | Mar 2016 | A1 |
20160148367 | Polo et al. | May 2016 | A1 |
20160202696 | Bernstein et al. | Jul 2016 | A1 |
20160246299 | Berberian et al. | Aug 2016 | A1 |
20160282871 | Berstein et al. | Sep 2016 | A1 |
20160291591 | Bernstein et al. | Oct 2016 | A1 |
20160291595 | Halloran | Oct 2016 | A1 |
20160349748 | Bernstein et al. | Dec 2016 | A1 |
20170080352 | Bernstein et al. | Mar 2017 | A1 |
20170092009 | Polo et al. | Mar 2017 | A1 |
Number | Date | Country |
---|---|---|
1302717 | Jul 2001 | CN |
1765595 | May 2006 | CN |
101154110 | Apr 2008 | CN |
201147642 | Nov 2008 | CN |
201220111 | Apr 2009 | CN |
101426664 | May 2009 | CN |
102060060 | May 2011 | CN |
102421629 | Apr 2012 | CN |
19809168 | Sep 1999 | DE |
101 46 862 | May 2002 | DE |
102011108689 | Apr 2012 | DE |
1944573 | Jul 2008 | EP |
102010042395 | Apr 2012 | EP |
2309650 | Aug 1997 | GB |
2319756 | Jun 1998 | GB |
03182290 | Aug 1991 | JP |
H07-308462 | Nov 1995 | JP |
09254838 | Sep 1997 | JP |
2000218578 | Aug 2000 | JP |
2001153650 | Jun 2001 | JP |
2002345706 | Dec 2002 | JP |
2004042246 | Feb 2004 | JP |
2004148439 | May 2004 | JP |
2004260917 | Sep 2004 | JP |
2007072802 | Mar 2007 | JP |
2007213353 | Aug 2007 | JP |
2008-040725 | Feb 2008 | JP |
2011530756 | Dec 2011 | JP |
2012022457 | Feb 2012 | JP |
4893862 | Mar 2012 | JP |
10-2008-040725 | Aug 2008 | KR |
10-2008-0073626 | Aug 2008 | KR |
10-2008-0092595 | Oct 2008 | KR |
10-2009-0000013 | Jan 2009 | KR |
20100001408 | Jan 2010 | KR |
10-0969873 | Jul 2010 | KR |
20105393 | Apr 2010 | TW |
WO-9725239 | Jul 1997 | WO |
WO-2006049559 | May 2006 | WO |
WO-2012094349 | Jul 2012 | WO |
2012103525 | Aug 2012 | WO |
Entry |
---|
US 9,342,073, 05/2016, Berstein et al. (withdrawn) |
Hashimoto et al., Nov. 2011, “TouchMe: An Augmented Reality Based Remote Robot Manipulation” (pp. 61-66). |
Arioui et al., 2011 AACC Publication, “Force Feedback Stabilization for Remote Control of an Assistive Mobile Robot” (pp. 4898-4903). |
Osorio et al., 2010 IDMME Publication, “Mobile Robots Design and Implementation: From Virtual Simulation to Real Robots” (pp. 1-6). |
Simsarian et al, 1996 Publication, “Achieving virtual presence with a semi-autonomous robot through a multi-reality and speech control interface”. (pp. 50-63). |
Diolaiti et al., 2002 IEEE Publication, “Tele-operation of a Mobile Robot Through Haptic Feedback” (pp. 1-6). |
U.S. Appl. No. 61/362,005, filed Jul. 7, 2010, Schmelzer, Richard. |
Liu, Dalian et al., “Motion Control of a Spherical Mobile Robot by Feedback Linearization,” 7th WC on IC&A, Jun. 27, 2008, Chongqing, China, pp. 965-970. 6 pages. |
Shu, Guanghui et al., “Motion Control of Spherical Robot Based on Conservation of Angular Momentum,” IEEE Intl Conf on Mechatronics & Automation, Aug. 12, Changchun, China, pp. 599-604. 6 pages. |
Joshi, Vrunda et al., “Design, modeling and controllability of a spherical mobile robot”, 13th Natl Conf on Mechanisms & Machines (NaCoMM07) IISc, Bangalore, India, Dec. 13, 2007, pp. 1-6. |
Harmo, Panu et al., “Moving Eye—Interactive Telepresence over Internet with a Ball Shaped Mobile Robot,” Automation Tech Lab, Finland, Oct. 2, 2001. 6 pages. http://automation.tkk.fi/files/tervetaas/MovingEye4.pdf. |
Halme, Aarne, et al., “Motion Control of a Spherical Mobile Robot”, Helsinki, IEEE AMC '1996, pp. 259-264. 6 pages. |
Non-Final Office Action mailed Apr. 29, 2013, for related U.S. Appl. No. 13/342,874, filed Jan. 3, 2012, 47 pages. |
Final Office Action mailed Jun. 6, 2014, for related U.S. Appl. No. 13/342,908, filed Jan. 3, 2012, 32 pages. |
U.S. Appl. No. 61/362,005, Schmelzer, filed Jul. 7, 2010, 10 pages. |
European Search Report and European Search Opinion mailed Nov. 6, 2014, for related EP Application No. 12731945.7 filed Jul. 26, 2013. 7 pages. |
Non-Final Office Action mailed Dec. 20, 2013, for related U.S. Appl. No. 13/342,908, filed Jan. 3, 2012, 28 pages. |
International Search Report and the Written Opinion mailed Dec. 17, 2014, for Application No. PCT/US2014/059973 filed Sep. 10, 2014, 13 pages. |
Non-Final Office Action mailed Oct. 16, 2012, for related U.S. Appl. No. 13/342,853, filed Feb. 19, 2013, 10 pages. |
Non-Final Office Action mailed Apr. 9, 2013, for related U.S. Appl. No. 13/342,892, filed Jan. 3, 2013, 19 pages. |
Notification of Transmittal of International Search Report and the Written Opinion of the International Searching Authority mailed Dec. 3, 2012, for related PCT Application No. PCT/US2012/020115 filed Jan. 3, 2012, 11 pages. |
Non-Final Office Action mailed Apr. 16, 2013, for related U.S. Appl. No. 13/342,884, filed Jan. 3, 2013, 20 pages. |
Notice of Allowance mailed Apr. 19, 2013, for related U.S. Appl. No. 13/342,853, filed Feb. 19, 2013, 11 pages. |
Non-Final Office Action mailed May 13, 2013, for related U.S. Appl. No. 13/342,874, filed Jan. 3, 2012, 17 pages. |
Non-Final Office Action mailed Jun. 3, 2013, for related U.S. Appl. No. 13/342,914, filed Jan. 3, 2012, 32 pages. |
Koshiyama et al., Machine Translation for JP 2000-218578, Aug. 8, 2000, 11 Pages. |
Non-Final Office Action mailed Jun. 13, 2013, for related U.S. Appl. No. 13/342,908, filed Jan. 3, 2012, 36 pages. |
GearBox Ball Prototype Jun. 29, 2010, Pictures from Video [online]. Orbotix, Inc., Jun. 30, 2010, 91 pages. Retrieved from the internet:<URL: http://www.youtube.com/watch?v=qRBM7bAaXpU>. |
Notification of Transmittal of International Search Report and the Written Opinion of the International Searching Authority mailed Aug. 28, 2013, for related PCT Application No. PCT/US2013/041023 filed May 14, 2013, 11 pages. |
Notification of Transmittal of International Search Report and the Written Opinion of the International Searching Authority mailed Oct. 15, 2013, for related PCT Application No. PCT/US2013/050327 filed Jul. 12, 2013, 13 pages. |
Final Office Action mailed Nov. 15, 2013, for related U.S. Appl. No. 13/342,892, filed Jan. 3, 2013, 21 pages. |
Final Office Action mailed Nov. 18, 2013, for related U.S. Appl. No. 13/342,884, filed Jan. 3, 2013, 19 pages. |
Final Office Action mailed Nov. 18, 2013, for related U.S. Appl. No. 13/342,874, filed Jan. 3, 2012, 21 pages. |
Final Office Action mailed Nov. 13, 2013, for related U.S. Appl. No. 13/342,914, filed Jan. 3, 2012, 30 pages. |
U.S. Appl. No. 13/894,247, Amendment and Response dated Aug. 13, 2015, 9 pages. |
U.S. Appl. No. 13/894,247, Notice of Allowance dated Oct. 29, 2015, 7 pages. |
U.S. Appl. No. 13/894,247, Office Action dated Jun. 12, 2015, 14 pages. |
U.S. Appl. No. 14/035,841 Amendment and Response dated Sep. 14, 2015, 12 pages. |
U.S. Appl. No. 14/035,841, Notice of Allowance dated Sep. 25, 2015, 5 pages. |
U.S. Appl. No. 14/035,841, Notice of Allowance dated Oct. 7, 2015, 2 pages. |
U.S. Appl. No. 14/035,841, Notice of Allowance dated Oct. 16, 2015, 2 pages. |
U.S. Appl. No. 14/035,841, Office Action dated May 13, 2015, 12 pages. |
U.S. Appl. No. 14/137,954, Amendment and Response dated Aug. 3, 2015, 14 pages. |
U.S. Appl. No. 14/137,954, Amendment and Response dated Feb. 5, 2016, 11 pages. |
U.S. Appl. No. 14/137,954, Amendment and Response dated Jun. 6, 2016, 12 pages. |
U.S. Appl. No. 14/137,954, Notice of Allowance dated Sep. 26, 2016, 8 pages. |
U.S. Appl. No. 14/137,954, Office Action dated May 4, 2015, 26 pages. |
U.S. Appl. No. 14/137,954, Office Action dated Nov. 5, 2015, 31 pages. |
U.S. Appl. No. 14/137,954, Office Action dated Apr. 12, 2016, 27 pages. |
U.S. Appl. No. 14/148,541, Amendment and Response dated Sep. 4, 2015, 14 pages. |
U.S. Appl. No. 14/148,541, Office Action dated Jun. 4, 2015, 18 pages. |
U.S. Appl. No. 14/148,541, Notice of Allowance dated Nov. 18, 2015, 11 pages. |
U.S. Appl. No. 14/261,288, Amendment and Response dated Nov. 5, 2015, 12 pages. |
U.S. Appl. No. 14/261,288, Notice of Allowance dated Nov. 23, 2015, 10 pages. |
U.S. Appl. No. 14/261,288, Office Action dated Jul. 7, 2015, 13 pages. |
U.S. Appl. No. 14/271,203, Advisory Action dated Mar. 2, 2016, 3 pages. |
U.S. Appl. No. 14/271,203, Amendment and Response dated Oct. 26, 2015, 10 pages. |
U.S. Appl. No. 14/271,203, Amendment and Response dated Feb 23, 2016, 9 pages. |
U.S. Appl. No. 14/271,203, Amendment and Response dated Mar. 11, 2016, 9 pages. |
U.S. Appl. No. 14/271,203, Amendment and Response dated Jun. 6, 2016, 9 pages. |
U.S. Appl. No. 14/271,203, Office Action dated Jul. 27, 2015, 11 pages. |
U.S. Appl. No. 14/271,203, Office Action dated Dec. 21, 2015, 10 pages. |
U.S. Appl. No. 14/271,203, Office Action dated Apr. 4, 2016, 10 pages. |
U.S. Appl. No. 14/271,203, Office Action dated Aug. 1, 2016, 17 pages. |
U.S. Appl. No. 14/459,235, Notice of Allowance dated Mar. 6, 2015, 9 pages. |
U.S. Appl. No. 14/459,235, Notice of Allowance dated Jun. 25, 2015, 7 pages. |
U.S. Appl. No. 14/663,446, Notice of Allowance dated Sep. 25, 2015, 9 pages. |
U.S. Appl. No. 14/691,349, Amendment and Response dated Aug. 28, 2015, 11 pages. |
U.S. Appl. No. 14/691,349, Amendment and Response dated Jan. 26, 2016, 6 pages. |
U.S. Appl. No. 14/691,349, Notice of Allowance dated Mar. 4, 2016, 5 pages. |
U.S. Appl. No. 14/691,349, Notice of Allowance dated Jun. 6, 2016, 5 pages. |
U.S. Appl. No. 14/691,349, Office Action dated Jul. 17, 2015, 9 pages. |
U.S. Appl. No. 14/832,801, Amendment and Response dated Feb. 5, 2016, 10 pages. |
U.S. Appl. No. 14/832,801, Amendment and Response dated Feb. 12, 2016, 8 pages. |
U.S. Appl. No. 14/832,801, Notice of Allowance dated Mar. 22, 2016, 10 pages. |
U.S. Appl. No. 14/832,801, Notice of Allowance dated May 11, 2016, 5 pages. |
U.S. Appl. No. 14/832,801, Office Action dated Nov. 6, 2015, 6 pages. |
U.S. Appl. No. 14/839,610, Amendment and Response dated Feb. 18, 2016, 11 pages. |
U.S. Appl. No. 14/839,610, Notice of Allowance dated Mar. 23, 2016, 16 pages. |
U.S. Appl. No. 14/839,610, Office Action dated Nov. 18, 2015, 7 pages. |
U.S. Appl. No. 14/850,910, Amendment and Response dated Feb. 18, 2016, 7 pages. |
U.S. Appl. No. 14/850,910, Notice of Allowance dated Mar. 17, 2016, 11 pages. |
U.S. Appl. No. 14/850,910, Office Action dated Nov. 25, 2015, 8 pages. |
U.S. Appl. No. 14/968,594, Amendment and Response dated Apr. 5, 2016, 7 pages. |
U.S. Appl. No. 14/968,594, Notice of Allowance dated Jul. 19, 2016, 6 pages. |
U.S. Appl. No. 14/968,594, Office Action dated Feb. 3, 2016, 5 pages. |
U.S. Appl. No. 14/975,510, Amendment and Response dated May 12, 2016, 8 pages. |
U.S. Appl. No. 14/975,510, Notice of Allowance dated Jul. 7, 2016, 5 pages. |
U.S. Appl. No. 14/975,510, Office Action dated Feb. 12, 2016, 6 pages. |
U.S. Appl. No. 15/017,211, Notice of Allowance dated Jul. 5, 2016, 10 pages. |
U.S. Appl. No. 15/017,211, Notice of Allowance dated Aug. 8, 2016, 4 pages. |
U.S. Appl. No. 15/232,490, Office Action dated Sep. 23, 2016, 5 pages. |
European Search Report in Application 13790911.5, dated Oct. 14, 2016, 10 pages. |
Loy et al., “Fast Radial Symmetry for Detecing Points of Interest”, IEEE Transactions on Pattern Analysis and Machine Intelligence, IEEE Computer Society, USA, vol. 25, No. 8, Aug. 1, 2003, 15 pages. |
European Search Report in Application 14795148.7, dated Dec. 7, 2016, 7 pages. |
Korean Office Action in Application 10-2014-7034020, dated Dec. 23, 2016, 11 pages. |
U.S. Appl. No. 13/342,914, Decision on Appeal dated Feb. 1, 2017, 8 pages. |
U.S. Appl. No. 14/884,632, Office Action dated Jan. 25, 2017, 7 pages. |
U.S. Appl. No. 14/271,203, Amendment and Response dated Feb. 1, 2017, 12 pages. |
“Roll, Pitch, and Yaw, How Things Fly”, How Things Fly website, https://howthingsfly.si.edu/flight-dynamics/roll-pitch-and-yaw. |
Chinese Office Action in Application 201380036857.2, dated Jun. 29, 2016, 10 pages. |
Chinese Office Action in Application 201620300686, dated Sep. 9, 2016, 3 pages. |
European Search Report in Application 13817382.2, dated Mar. 11, 2016, 8 pages. |
Korean Office Action in Application 10-2015-7003642, dated Nov. 28, 2016, 13 pages. |
PCT International Search Report in PCT/US2014/037013, dated Aug. 26, 2014, 8 pages. |
PCT International Search Report in PCT/US2014/068606, dated Mar. 2, 2015, 7 pages. |
PCT International Search Report in PCT/US2015/030877, dated Aug. 13, 2015, 5 pages. |
PCT International Search Report in PCT/US2015/044885, dated Oct. 29, 2015, 7 pages. |
U.S. Appl. No. 13/342,853, Amendment and Response dated Feb. 19, 2013, 7 pages. |
U.S. Appl. No. 13/342,853, Notice of Allowance dated Jun. 20, 2013, 6 pages. |
U.S. Appl. No. 13/342,874, Amendment and Response dated Sep. 13, 2013, 21 pages. |
U.S. Appl. No. 13/342,874, Amendment and Response dated Jan. 21, 2014, 13 pages. |
U.S. Appl. No. 13/342,874, Amendment and Response dated Jul. 14, 2014, 13 pages. |
U.S. Appl. No. 13/342,874, Amendment and Response dated Mar. 5, 2015, 11 pages. |
U.S. Appl. No. 13/342,874, Amendment and Response dated Jul. 7, 2015, 9 pages. |
U.S. Appl. No. 13/342,874, Notice of Allowance dated Jul. 24, 2015, 18 pages. |
U.S. Appl. No. 13/342,874, Notice of Allowance dated Aug. 11, 2015, 3 pages. |
U.S. Appl. No. 13/342,874, Office Action dated Sep. 4, 2014, 16 pages. |
U.S. Appl. No. 13/342,874, Office Action dated Apr. 7, 2015, 8 pages. |
U.S. Appl. No. 13/342,884, Amendment and Response dated Sep. 16, 2013, 32 pages. |
U.S. Appl. No. 13/342,884, Amendment and Response dated Jan. 21, 2014, 11 pages. |
U.S. Appl. No. 13/342,884, Notice of Allowance dated Feb. 19, 2014, 14 pages. |
U.S. Appl. No. 13/342,892, Amendment and Response dated Sep. 9, 2013, 27 pages. |
U.S. Appl. No. 13/342,892, Amendment and Response dated Feb. 18, 2014, 12 pages. |
U.S. Appl. No. 13/342,892, Appeal Brief dated Jul. 17, 2014, 30 pages. |
U.S. Appl. No. 13/342,892, Office Action dated Nov. 15, 2013, 18 pages. |
U.S. Appl. No. 13/342,892, Response to Appeal Brief dated Aug. 6, 2014, 16 pages. |
U.S. Appl. No. 13/342,908, Advisory Action dated Aug. 11, 2014, 3 pages. |
U.S. Appl. No. 13/342,908, Advisory Action dated Sep. 18, 2014, 4 pages. |
U.S. Appl. No. 13/342,908, Amendment and Response dated Oct. 15, 2013, 32 pages. |
U.S. Appl. No. 13/342,908, Amendment and Response dated Mar. 20, 2014, 21 pages. |
U.S. Appl. No. 13/342,908, Amendment and Response dated Aug. 8, 2014, 13 pages. |
U.S. Appl. No. 13/342,908, Amendment and Response dated Sep. 5, 2014, 18 pages. |
U.S. Appl. No. 13/342,908, Amendment and Response dated Apr. 6, 2015, 12 pages. |
U.S. Appl. No. 13/342,908, Notice of Allowance dated Apr. 29, 2015, 12 pages. |
U.S. Appl. No. 13/342,908, Supplemental Amendment and Response dated Apr. 17, 2015, 10 pages. |
U.S. Appl. No. 13/342,914, Advisory Action dated Feb. 13, 2014, 3 pages. |
U.S. Appl. No. 13/342,914, Amendment and Response dated Sep. 3, 2013, 24 pages. |
U.S. Appl. No. 13/342,914, Amendment and Response dated Feb. 3, 2014, 12 pages. |
U.S. Appl. No. 13/342,914, Appeal Brief dated Jul. 3, 2014, 27 pages. |
U.S. Appl. No. 13/342,914, Response to Appeal Brief dated Jul. 29, 2014, 10 pages. |
U.S. Appl. No. 13/549,097, Amendment and Response dated Mar. 24, 2015, 14 pages. |
U.S. Appl. No. 13/549,097, Amendment and Response dated Jan. 22, 2016, 16 pages. |
U.S. Appl. No. 13/549,097, Office Action dated Dec. 26, 2014, 20 pages. |
U.S. Appl. No. 13/549,097, Office Action dated Oct. 22, 2015, 20 pages. |
U.S. Appl. No. 13/549,097, Office Action dated Oct. 4, 2016, 22 pages. |
U.S. Appl. No. 13/766,455, Amendment and Response dated Jul. 15, 2015, 11 pages. |
U.S. Appl. No. 13/766,455, Notice of Allowance dated Aug. 20, 2015, 15 pages. |
U.S. Appl. No. 13/766,455, Office Action dated Apr. 15, 2015, 9 pages. |
Airplane Flying Handbook (FAA-H-8083-3B) Chapter 10, Figure, 10-2, https://www.faa.gov/regulations—policies/handbooks—manuals/aviation/airplane—handbook/media/12—afh—ch10.pdf, 10 pages, 2004, 10 pages. |
Chinese Office Action in Application 201380036857.2, dated Mar. 22, 2017, 11 pages. |
Chinese Office Action in Application 201620300686.0, dated Feb. 3, 2016, 5 pages. |
Chinese Office Action in Application 201702030180700, dated Feb. 7, 2017, 8 pages. |
Curriculum of Dr. Jason Janet cited in IPR2017-01272, filed Apr. 20, 2017, 6 pages. |
Declaration of Dr. Jason Janet cited in IPR2017-01272, filed Apr. 20, 2017, 79 pages. |
European Extended Search Report in Application 14795148.7, dated Apr. 5, 2017, 12 pages. |
Gene F. Franklin, J. David Powell, Abbas Emami-Naeini, Feedback Control of Dynamic Systems, Fourth Edition, Prentice Hall, 2002, 28 pages. |
Hashem Ghariblu and Hadi Mohammadi, Structure and Dynamic Modeling of a Spherical Robot, 8th International Symposium on Mechatronics and its Applications, 2012, 5 pages. |
Hiroyuki Fujita, A Decade of MEMS and its Future, Proceedings IEEE the Tenth Annual International Workshop on Micro Electra Mechanical Systems, 1997, 8 pages. |
How a Small Robotics Startup Helped Disney Bring BB-8 to Life, US Chamber of Commerce (https://www.uschamber.com/above-thefold/how-small-robotics-startup-helped-disney-bring-bb-8-life), Retrieved on Mar. 31, 2017, 6 pages. |
Japanese Office Action in Application 2015-512768, dated Dec. 6, 2016, 9 pages. |
Japanese Office Action in Application 2015-521853, dated Feb. 14, 2017, 6 pages. |
Martyn Williams, Sony unwraps high-tech 'healing' ball, CNN.com, published Mar. 28, 2002, http://edition.cnn.com/2002/TECH/ptech/03/28/robodex.healing.ball.idg/?related, retreived on Apr. 4, 2017, 1 page. |
Masato Ishikawa, Ryohei Kitayoshi, and Toshiharu Sugie, Dynamic rolling locomotion by spherical mobile robots considering its generalized momentum, Proceedings of SICE Annual Conference 2010 2311 (2010), 6 pages. |
Meet BB-8: The New Droid in the Lives of Star Wars Buffs, Wharton School of the University of Pennsylvania (Nov. 13, 2015) (http://knowledge.wharton.upenn.edu/article/meet-bb-8-the-newdroid-in-the-lives-of-star-wars-buffs/), Retrieved on Mar. 31, 2017, 3 pages. |
PCT International Preliminary Report on Patentability in PCT/US2015/030877, dated Feb. 23, 2017, 5 pages. |
PCT International Preliminary Report on Patentability in PCT/US2015/044885, dated Feb. 23, 2017, 5 pages. |
Qiang Zhan, Yao Cai, and Caixia Yan, Design, Analysis and Experiments of an Omni-Directional Spherical Robot, IEEE International Conference on Robotics and Automation 4921, 2011, 6 pages. |
Randall Munroe, New Pet, http://xkcd.com/413/, Retrieved from Internet Archive (http://web.archive.org/ web/20080701080435/http://xkcd.com/413/) (2008), Retrieved on Apr. 13, 2017, 3 pages. |
U.S. Appl. No. 13/549,097, Amendment and Response dated Mar. 14, 2017, 13 pages. |
U.S. Appl. No. 14/137,954, Notice of Allowance dated Mar. 8, 2017, 8 pages. |
U.S. Appl. No. 14/271,203, Office Action dated Feb. 21, 2017, 12 pages. |
U.S. Appl. No. 14/884,632, Amendment and Response dated Apr. 19, 2017, 3 pages. |
U.S. Appl. No. 14/933,827, Office Action dated Apr. 21, 2017, 7 pages. |
U.S. Appl. No. 15/040,331, Office Action dated Apr. 13, 2017, 10 pages. |
U.S. Appl. No. 15/232,490, Amendment and Response dated Feb. 22, 2017, 3 pages. |
U.S. Appl. No. 15/232,490, Office Action dated Mar. 17, 2017, 4 pages. |
Kialing Lv and Minglu Zhang, Robot Control Based on Voice Command, IEEE International Conference on Automation and Logistics 2490, 2008, 5 pages. |
Chinese Office Action in Application 201620300686, dated May 2, 2017, 2 pages. (No English Translation). |
U.S. Appl. No. 15/281,478, Office Action dated May 5, 2017, 5 pages. |
U.S. Appl. No. 14/884,632, Notice of Allowance dated May 15, 2017, 8 pages. |
U.S. Appl. No. 15/146,631, Office Action dated May 16, 2017, 11 pages. |
U.S. Appl. No. 13/342,892, Board Decision dated May 5, 2017, 8 pages. |
European Office Action in Application 13817383.8, dated Apr. 20, 2017, 6 pages. |
Chinese Office Action in Application 201480029695.4, dated May 27, 2017, 22 pages. |
Chinese Office Action in Application 201510463007.1, dated May 31, 2017, 8 pages. |
European Extended Search Report in Application 14853882.0, dated Jun. 22, 2017, 6 pages. |
Korean Office Action in Application 10-2014-7034020, dated Jun. 30, 2017, 11 pages. |
U.S. Appl. No. 15/232,490, Amendment and Response dated Jul. 10, 2017, 3 pages. |
U.S. Appl. No. 15/040,331, Amendment and Response dated Jul. 10, 2017, 10 pages. |
U.S. Appl. No. 14/884,632, Supplemental Notice of Allowance dated Jun. 1, 2017, 2 pages. |
U.S. Appl. No. 14/137,954, Notice of Allowance dated Jun. 29, 2017, 8 pages. |
U.S. Appl. No. 13/342,892, Notice of Allowance dated Jun. 7, 2017, 7 pages. |
U.S. Appl. No. 13/342,892, Supplemental Notice of Allowance dated Jun. 29, 2017, 2 pages. |
U.S. Appl. No. 13/549,097, Office Action dated Jun. 26, 2017, 30 pages. |
Chinese Notice of Allowance in Application 201380036857.2, dated Aug. 1, 2017, 4 pages. |
Chinese Office Action in Application 201510463336.6, dated Jul. 17, 2017, 5 pages. (No English Translation). |
Korean Notice of Allowance in Application 10-2015-7003642, dated Jul. 25, 2017, 4 pages. |
U.S. Appl. No. 13/549,097, Advisory Action dated Sep. 22, 2017, 2 pages. |
U.S. Appl. No. 15/146,631, Office Action dated Sep. 21, 2017, 14 pages. |
U.S. Appl. No. 15/232,490, Notice of Allowance dated Sep. 21, 2017, 7 pages. |
U.S. Appl. No. 13/342,892, Supplemental Notice of Allowance dated Jul. 26, 2017, 2 pages. |
U.S. Appl. No. 13/549,097, Amendment and Response dated Aug. 25, 2017, 11 pages. |
U.S. Appl. No. 14/137,954, Supplemental Notice of Allowance dated Jul. 27, 2017, 2 pages. |
U.S. Appl. No. 14/271,203, Amendment and Response dated Aug. 18, 2017, 11 pages. |
U.S. Appl. No. 14/884,632, Supplemental Notice of Allowance dated Jul. 28, 2017, 2 pages. |
U.S. Appl. No. 15/040,331, Notice of Allowance dated Aug. 1, 2017, 9 pages. |
U.S. Appl. No. 15/146,631, Amendment and Response dated Aug. 18, 2017, 10 pages. |
U.S. Appl. No. 15/177,809, Office Action dated Aug. 16, 2017, 6 pages. |
U.S. Appl. No. 15/180,485, Office Action dated Aug. 17, 2017, 9 pages. |
U.S. Appl. No. 15/232,490, Notice of Allowance dated Aug. 10, 2017, 5 pages. |
U.S. Appl. No. 15/281,478, Amendment and Response dated Sep. 5, 2017, 8 pages. |
Wright's Brothers Propulsion System, Smithsonian national Air and Museum, retrieved , retreived Aug. 17, 2017, https://airandspace.si.edu/exhibitions/wright-brothers/online/fly/1903/propulsion.cfm, 5 pages. |
Number | Date | Country | |
---|---|---|---|
20140051513 A1 | Feb 2014 | US |
Number | Date | Country | |
---|---|---|---|
61646716 | May 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13894247 | May 2013 | US |
Child | 14054636 | US |