A variety of augmented and virtual reality devices exist which are usable for generating and viewing interactive virtual imagery. Such virtual imagery may include information displays, content windows, user interfaces, artificially intelligent virtual entities, 3D models, and other virtual objects. Virtual imagery may be world-locked so as to make it appear that virtual objects remain in a fixed location in the real world.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure.
One or more sensors of a virtual reality device track a pose of the virtual reality device. The virtual reality device requests a virtual image having a perspective corresponding to a future pose from a remote computer. After receiving the requested virtual image, the virtual reality device adjusts the virtual image to an adjusted virtual image having an updated perspective corresponding to an updated tracked pose of the virtual reality device. Then, a virtual reality display displays the adjusted virtual image.
When using a virtual reality device, it may sometimes be desirable to outsource some or all rendering of virtual images to a remote computer. In such cases, a virtual reality device may send to a remote computer a request for a virtual image. The remote computer may then render the virtual image, and send it to the virtual reality device for display. Remote rendering of virtual images may present several advantages over local rendering, as will be explained in more detail below. However, remote rendering may also introduce delay between when a virtual image is requested and when the virtual image is actually displayed, potentially resulting in a less satisfactory user experience. Virtual images displayed by a virtual reality device may be substantially “world-locked,” such that the virtual images appear to occupy specific positions in physical space which do not change as the perspective of the virtual reality device changes. In order to maintain this effect, rendered virtual imagery must appear to update substantially simultaneously as a user moves. For example, as a user moves to the left, a rendered virtual image may need to simultaneously shift a proportional distance to the right, so as to appear not to move relative to the real world. Delays in image rendering introduced by remote rendering can compromise this effect, resulting in “jittery” or “swimmy” images. As discussed below, these effects can be lessened by recognizing the time necessary to request and receive a remotely-rendered virtual image, and requesting the virtual image for a corresponding time in the future.
Remote rendering of virtual images may be useful in any number of potential scenarios. For example, the virtual images to be rendered may be complex, and require substantial computer resources for rendering and/or manipulation. In such cases, rendering of virtual images may be outsourced to a remote computer with greater image rendering and/or general processing capabilities than the virtual reality device.
In another example, remote rendering may be useful for reducing iteration time and/or testing code changes during software development. An application developer may use a remote computer to write a software application executable by a virtual reality device. During application development, the developer may test aspects of the software application by executing it on a remote computer configured to send rendered imagery to a virtual reality device. The remote computer may have one or more tools/features useful for application development which are not available/easily accessible on the virtual reality device. The developer may use the virtual reality device during this process, evaluating and/or interacting with the rendered virtual imagery. This may allow the application developer to test software changes substantially in real time, eliminating the need to compile and install new software builds on the virtual reality device before testing can occur. In some embodiments, the developer may be able to make changes to the software application by interacting with one or more virtual elements via the virtual reality device, thereby affecting the software running on the remote computer.
At 106, one or more sensors track a pose of the virtual reality device. A pose may be defined as a set of variables establishing the virtual reality device's position and/or orientation at a specific moment in time. Such variables may include the device's current three-dimensional coordinates (e.g., X, Y, and Z coordinates), comprising three degrees of freedom (3DOF). Further, the one or more sensors may track the virtual reality device's current pitch, roll, and yaw, providing an additional three degrees of freedom (3DOF), for a combined six degrees of freedom (6DOF). In some embodiments, the one or more sensors are configured to detect a motion of the virtual reality device in one or more dimensions. For example, if a user of a wearable virtual reality device walks forward, moves his head, leans backward, and/or moves in any other way, the one or more sensors may detect the motion and continuously update the tracked pose. The one or more sensors may comprise one or more gyroscopes, accelerometers, proximity sensors, optical sensors, infrared sensors, ultrasonic sensors, microphones, global positioning system (GPS) receivers, cameras, thermometers, barometers, and/or any other suitable sensors.
At 108, a pose prediction machine of virtual reality device 100 predicts a future pose of the virtual reality device at a future time. The future time may be any suitable time in the future, and may be established according to one or more criteria, as described in further detail below. In particular, the future time may be separated from the current time by a buffer period, and the size of the buffer period may depend upon one or more factors. The future pose is the pose prediction machine's prediction of what the pose of virtual reality device 100 will be at or near the future time, according to the device's current pose, movement, and/or other factors, as will be explained below.
In order to predict the future pose, the pose prediction machine may make use of the virtual reality device's current pose and movement, as tracked by the one or more sensors. Then, the pose prediction machine may extrapolate the detected motion forward from the current time to the future time, thus generating a reasonable approximation of the position and/or orientation the virtual reality device 100 is likely to have at or near the future time. For example, if the one or more sensors determine that, at a current time, virtual reality device 100 is moving slowly to the left, then the pose prediction machine may predict a future pose of the virtual reality device by extrapolating the device's leftward motion until the future time.
In some embodiments, other factors may be considered when predicting the future pose of virtual reality device 100. For example, when virtual reality device 100 is worn by a user, the future pose may be predicted by extrapolating the detected motion forward with biomechanical constraints. This may include determining that a detected motion is consistent with a predictable human movement such as nodding, head turning, bending at the waist, jumping, etc., and using this information to more accurately predict the future motion and resulting pose. For example, the pose prediction machine may determine that a detected motion is consistent with a user turning his head. Based on the duration and speed of the detected head turn, the pose prediction machine may determine a likely future pose extrapolated from the current pose and detected head-turning motion.
Further, the pose prediction machine may predict the future pose by extrapolating the detected motion forward with environmental constraints. This may include identifying one or more real-world/virtual objects, features, elements, and/or other points of interest that a user is likely to focus on. For example, if the pose prediction machine determines that a user is turning his head to look at a nearby television set, the pose prediction machine may predict that the user will focus on the television set, and therefore predict the future pose according to an assumption that the detected motion will stop once the television set is in the center of the user's field of view. Similar predictions can be made for virtual objects. For example, the pose prediction machine may determine that a user is tilting his head upward toward a world-locked virtual monitor, and predict the future pose accordingly. Alternatively, the pose prediction machine may determine that there are no notable points of interest in the path of the detected motion, and use this information when predicting the future pose.
In the illustrated example, the pose prediction machine is shown as being part of the virtual reality device. However, in some embodiments, the pose prediction machine may be part of the remote computer. For example, the virtual reality device may send to the remote computer data from the one or more sensors, and the pose prediction machine of the remote computer may predict the future pose of the virtual reality device based on the sensor data, as described above.
At 110, a communications machine of the virtual reality device sends to the remote computer a request for a virtual image. Specifically, the virtual reality device requests a virtual image having a perspective corresponding to the future pose of the virtual reality device. In other words, after the pose prediction machine predicts the future pose, the communications machine requests that the remote computer render one or more virtual images from the predicted perspective of the virtual reality device.
In some embodiments, the request may specify one or more virtual images consistent with one or more points of view. For example, the virtual reality device may request two virtual images with slightly different perspectives, one to be displayed for a user's left eye, and one to be displayed for a user's right eye. Additional perspectives may also be requested, for example from the point of view of one or more cameras attached to the virtual reality device and/or present in the real-world environment. Further, the request may specify that rendered virtual images have a certain resolution and/or size. This resolution may match a resolution of a display device by which the virtual image will be displayed, or the requested resolution may be different from (e.g., greater or less than) the resolution of the display device, as will be explained in further detail below with respect to
Virtual reality device 100 sends the request to remote computer 102 over network 104. As described above, network 104 may be virtually any suitable computer network including, for example, the Internet and/or a local area network (LAN). As such, when communicating over the computer network, each of the virtual reality device and the remote computer occupy a different network node. The virtual reality device and the remote computer may be separated by virtually any physical distance, provided they are able to communicate over the computer network.
At 112, a remote communications machine of the remote computer receives from a virtual reality device a request for a virtual image. As described above, the request is for one or more virtual images having a perspective corresponding to a predicted future pose of the virtual reality device.
At 114, a virtual image renderer of the remote computer renders the virtual image for the virtual reality device as specified by the request.
At 116, the remote communications machine of the remote computer sends to the virtual reality device the rendered virtual image. In some embodiments, the virtual image may be compressed and/or otherwise modified prior to sending. This may be done, for example, responsive to a transmission speed and/or maximum bandwidth of the computer network.
In some embodiments, information pertaining to the predicted future pose may be attached to the rendered virtual image before it is sent to the virtual reality device. This may permit a virtual reality device to determine which rendered virtual images correspond to which predicted future poses. Further, in the case where the pose prediction machine is located at the remote computer, sending pose information with the rendered virtual image may allow the virtual reality device to determine the future pose for which the virtual image was rendered. This information may be linked to the rendered virtual images in any suitable way. For example, the pose information may simply be appended to each network packet including rendered virtual imagery. Alternately, pose information may be encoded within each network packet as pixel data associated with the rendered virtual imagery. Pixels including pose information may be cleared to black once decoded by the virtual reality device. Further, pose information may be indexed according to integer identifiers and tracked by one or more computer devices via, for example, a send and lookup method.
At 118, the communications machine of the virtual reality device 100 receives from the remote computer the virtual image. Upon receipt of the virtual image, the virtual reality device may perform one or more processing/analysis steps in order to, for example, decompress the received virtual image and/or otherwise modify it before additional operations are performed.
At 120, after the rendered virtual image has been received, the communications machine of the virtual reality device 100 determines a communications latency of the computer network by measuring an elapsed time between the request being sent and the virtual image being received. This communications latency may be used in future decisions regarding how virtual images should be rendered. For example, as described above, the pose prediction machine predicts the future pose of the virtual reality device at a future time, and this future time is separated from the current time by a buffer period. In some embodiments, the pose prediction machine may be configured to dynamically adjust the buffer period by dynamically increasing the buffer period with increasing communications latency and dynamically decreasing the buffer period with decreasing communications latency. A high communications latency may indicate relatively slow communication between the virtual reality device and the remote computer over the computer network. As such, the pose prediction machine may need to predict the future pose for a future time which is relatively far in the future, in order to account for the time it will take before a requested virtual image has been remotely rendered and received. However, when the communications latency is low, the pose prediction machine may be able to predict the future pose for a future time which is relatively closer to the current time, thereby increasing the accuracy of the prediction. Further, the current framerate for display of virtual images may be adjusted based on communications latency, and the communications latency may be taken into account when establishing a resolution of virtual images. For example, in cases of high communications latency, framerate and virtual image resolution may be dynamically reduced, in order to minimize network congestion related latency/delays.
At 122, a late stage reprojection machine of the virtual reality device 100 adjusts the virtual image before it is displayed. Such late stage reprojection can lessen any noticeable effects resulting from the pose prediction engine predicting the wrong pose. Specifically, the rendered virtual image, which has a perspective corresponding to the predicted future pose, may be adjusted to have an updated perspective corresponding to an updated tracked pose of the virtual reality device. For example, before a virtual image is requested, the one or more sensors may determine that the virtual reality device is moving to the left, and the pose prediction machine may use this information to predict a future pose where the virtual reality device has moved somewhat to the left relative to the current pose. Then, a virtual image having this perspective may be requested. However, after requesting the virtual image, the one or more sensors may determine that the leftward motion has stopped sooner than expected, and as a result, the rendered virtual image will not match the actual pose of the device at the future time. As such, if the rendered virtual image was displayed to a user unmodified, virtual objects within the virtual image may appear to suddenly move away from their world-locked positions. To solve this problem, the late stage reprojection machine may adjust the image by shifting the virtual image by an amount that is proportional to a difference between the predicted future pose and the updated tracked pose. Given the above example, the late stage reprojection machine may slightly shift the virtual image in order to compensate for the change in the virtual reality device's motion, ensuring that, from the user's perspective, world-locked virtual objects remain in their designated positions.
In some embodiments, the updated tracked pose used by the late stage reprojection machine will be the last possible pose which can be used before the virtual image is displayed, so as to ensure that the virtual image is adjusted according to the most recent possible information. The updated tracked pose used to adjust the rendered virtual image may represent the virtual reality device's position and/or orientation at a time either before the virtual image has been received, or after the virtual image has been received and before it is displayed. In some embodiments, the pose prediction machine may begin continuously comparing the most recent updated tracked pose to the predicted future pose as soon as the virtual image is requested, dynamically determining which adjustments need to be made to the rendered virtual image before it is displayed.
At 124, a virtual reality display of the virtual reality device 100 displays the adjusted virtual image at or near the future time. Once the rendered virtual image has been received and adjusted by the late stage reprojection machine, it is displayed at or near the future time using the virtual reality display. Virtual reality device 100 may incorporate virtually any type of display usable for displaying rendered virtual imagery.
Once the adjusted virtual image is displayed, the process described above repeats. The pose prediction machine uses the new current pose to predict a new future pose, and the communications machine requests a new rendered image for the new future pose. In some embodiments, the process described above is continuously repeating, such that at any given moment in time, multiple steps of the process are being carried out simultaneously. For example, at the same time a virtual image is being displayed by the virtual reality display, new future poses are being predicted, and new virtual images are being requested, rendered, and adjusted.
At 204, the pose prediction machine uses current pose 201 and the detected movement indicated by arrow 202 to predict a future pose of the virtual reality device. Such a prediction may be made as described above with respect to
Next, at 206,
At 208, a virtual image is rendered at a remote computing device according to predicted future pose 207. Virtual image rendering may occur at the remote computing device according to the process described above with respect to
Next, at 210,
Advancing in time from 200, at 212,
At 214, after the future pose has been predicted and updated tracked pose 213 has been determined, the late stage reprojection machine compares the predicted future pose to the updated tracked pose. In this case, the late stage reprojection machine will identify differences in position and/or orientation between predicted future pose 207 and updated tracked pose 213. As described above, in some embodiments, once the rendered virtual image has been requested, the late stage reprojection machine may continuously compare the updated tracked pose to the predicted future pose, in order to determine which if any adjustments should be made to the received virtual image before it is displayed.
Next, at 216, the late stage reprojection machine uses the results of the comparison performed at 214 to adjust the rendered virtual image to have an updated perspective corresponding to the updated tracked pose 213 of the virtual reality device. Such adjustment may comprise shifting the virtual image by an amount that is proportional to a difference between the predicted future pose and the updated tracked pose. In the illustrated example, the late stage reprojection machine may shift the rendered virtual image in order to account for the differences in position and/or orientation of the virtual reality device between the predicted future pose 207 and the updated tracked pose 213.
Finally, at 218,
Also shown at 218 is a non-adjusted position 219 of the world-locked virtual object, shown as a dashed box. The virtual reality device does not display the world-locked virtual object at position 219 in the adjusted virtual image. Rather, it is included in
In some embodiments, an environment of a virtual reality device may include virtual objects which are too large to fit within a field of view (FOV) of the virtual reality device, or are located entirely outside of the current FOV. For example, a user of a virtual reality device may play a game requiring the user to interact with a large virtual dragon. The dragon may be too large to fit entirely within the FOV of the virtual reality device, meaning a virtual image rendered for a given pose of the virtual reality device may not include the entire dragon, and instead only include the portions of the dragon which are currently visible in the FOV. Similarly, a user may interact with a virtual object, anchoring it to a particular location in the physical world, then move such that the virtual object is no longer visible within the virtual reality device's current FOV. As such, a virtual image rendered for a given pose of the virtual reality device may only include the virtual object when it is within the device's current FOV.
During remote rendering, virtual images may be rendered based on which virtual objects would be visible to a virtual reality device occupying a predicted future pose at a future time. For example, at a predicted future pose, an FOV of a virtual reality device may include only the head of a virtual dragon. As a result, a virtual image rendered for the predicted future pose may include only the dragon's head. However, this may pose a problem if, at an updated tracked pose, the FOV of the virtual reality device includes an area which should be occupied by a neck/body of the virtual dragon. The late stage reprojection machine could adjust the rendered virtual image in order to compensate for any differences between the predicted future pose and the updated tracked pose. However, this may not be possible if the rendered virtual image only includes the dragon's head, for example. Adjusting the virtual image may move the head of the dragon to a position consistent with the updated tracked pose, though leave blank space where the dragon's neck and body should be.
In order to address this problem, a virtual image may be rendered which is oversized relative to a set resolution of a virtual reality display, then cropped to match the set resolution before the virtual image is displayed.
At 302, the virtual reality device requests a rendered virtual image. The rendered virtual image may be oversized relative to the set resolution of the virtual reality display. In some embodiments, virtual images may be automatically oversized at least to a degree, in order to ensure that adjustments can be made in the event that the predicted future pose does not match the updated tracked pose. Alternately, images may only be oversized when a threshold motion is detected by the one or more sensors. Further, an amount of oversizing may be proportional to a speed of the detected motion, the current framerate, and/or an average variation in network latency.
At 304,
The oversized virtual image includes virtual wizards 305. Each virtual wizard is fully rendered by the remote computer, despite the fact that only part of each virtual wizard may be visible in the virtual reality device's FOV. Further, the virtual image is shown as being oversized in two dimensions—a horizontal dimension and a vertical dimension. However, in some embodiments, a degree of oversizing may be different in different dimension. For example, an amount of oversizing in a first dimension of the virtual image may be proportional to a speed of the detected motion in the first dimension, and an amount of oversizing in a second dimension of the virtual image may be independently proportional to a speed of the detected motion in the second dimension. For example, if a virtual reality device is moving rapidly in a horizontal direction, and slowly in a vertical dimension, a rendered virtual image may be greatly oversized in a horizontal dimension, and only slightly oversized in a vertical dimension. Dynamically setting the amount of oversizing according to detected motion may allow a virtual reality device to shift virtual images as necessary for proper display, without wasting resources by rendering unnecessarily large virtual images.
At 306, the virtual reality device adjusts the rendered virtual image before it is displayed. In this case, adjusting the virtual image comprises cropping the virtual image to the set resolution of the virtual reality display. At this time, the late stage reprojection machine may perform any other adjustment operations before the virtual image is displayed. For example, the late stage reprojection machine may shift the virtual image in order to account for differences between the predicted future pose and the updated tracked pose.
Next,
Alternatively, a virtual image may be rendered which is undersized relative to a set resolution of a virtual reality display. Such images may be rendered and displayed in a similar manner to the oversized virtual images described above. For example, an undersized virtual image may be rendered which has a resolution which is less than the set resolution of the virtual reality display, and then stretched to fit the size of the virtual reality display. This may help maintain a constant framerate during periods of network congestion and high communications latency. An amount of undersizing may be proportional to a speed of the detected motion, the current framerate, and/or an average variation in network latency.
In some embodiments, a rendered virtual image may be oversized relative to a size of a virtual reality display, though use the same resolution as the virtual reality display. In such a scenario, each pixel of the oversized virtual image will cover a larger area than a pixel from a rendered virtual image which is the same size as the virtual reality display. In some embodiments, such blurring may be desirable. For example, in the event that a virtual reality device is moving, a blurred virtual image may be rendered, simulating a motion blur effect. In some embodiments, additional operations may be performed in order to perform smoothing of a blurred virtual image before it is displayed.
In some embodiments, the virtual image is a three-dimensional image, and includes a number of virtual objects, each rendered to appear at a different distance away from the virtual reality device. The rendered virtual image may include color and depth information (an RGBD image). For example, in addition to one or more color values used to illuminate the display (e.g., RGB values), each pixel may also include underlying depth information (e.g., D value) which is not displayed, but which can be used to position the individual virtual objects on the display if the predicted pose differs from an updated tracked pose.
One or more virtual objects optionally may be locally rendered on the virtual reality device while other virtual objects are remotely rendered on the remote computer. In such embodiments, the virtual reality device may include a local virtual image renderer configured to locally render one or more virtual objects. Further, in such embodiments, the virtual reality display may be configured to display the one or more virtual objects rendered by the local virtual image renderer with the adjusted virtual image. This may be done for a variety of reasons. For example, relatively simple virtual objects may be rendered by a virtual reality device, while more complicated objects may be rendered remotely. Further, virtual objects with relatively low latency tolerance including, for example, cursors, may be rendered locally, where rendering can be done without network associated communications latency. For example,
In some embodiments, the remote computer may render a three-dimensional image and transmit it to the virtual reality device for adjustment and display. However, in the event of low network bandwidth/other network delays, or if the remote computer is unable to render virtual images at a framerate defined by the virtual reality device, the remote computer may render a two-dimensional RGB virtual image and send this virtual image to the virtual reality device along with an associated depth map. The late stage reprojection machine may then adjust the received virtual image according to differences between the predicted future pose and the updated tracked pose, and further according to information included in the received depth map. Adjusting the two-dimensional virtual image to include information from the depth map may be done through any suitable technique including, for example, rendering the image on a tessellated plane as a heightmap, or building a voxel representation of the virtual environment. Further, virtual images may be rendered and/or modified by the virtual reality device via ray tracing, constructed as a virtual mesh, or via virtually any other suitable techniques. Further, the virtual reality device may locally render a depth map, and use this locally rendered depth map to occlude portions of a received virtual image, thereby reducing the latency of any occlusion operations. The techniques described above may allow virtual image rendering and display to be performed efficiently, independent of network transmission speed and/or remote computer rendering speed.
In some embodiments, a rendered virtual image may include additional content provided by the remote computer. For example, a remote computer may be connected to one or more local/remote content sources which provide audio and/or visual content. Further, content provided by the remote computer may include information pertaining to one or more hardware components/software operations of the remote computer. The additional content may be included in the virtual image in any suitable manner. For example, the virtual image may include visual content from a remote/local video service. This visual content may be included in the virtual image as a floating virtual monitor, or presented to the user in any other suitable manner. Additionally, when an application developer is using remote rendering to test changes in a software application, as described above, additional content provided to the virtual reality device may include, for example, debug information, and/or any other suitable information related to the virtual reality device and/or the remote computer.
The method starts at 600, where one or more sensors track a pose of the virtual reality device. Next, at 602, a pose prediction machine predicts a future pose of the virtual reality device at a future time.
At 604, the method determines if remote rendering is currently active. If remote rendering is not active (NO at 604), then the method proceeds to 606, where a local image renderer of the virtual reality device renders a virtual image for the predicted future pose. However, if remote rendering is active (YES at 604), then the method proceeds to 614.
From 606, the method proceeds to 608, where a late stage reprojection machine of the virtual reality device determines whether there are any differences between the future pose predicted at 602, and an updated tracked pose determined by the one or more sensors. If differences exist (YES at 608), then the method proceeds to 610. If no differences exist (NO at 608), then the method proceeds to 612.
At 610, the late stage reprojection machine adjusts the virtual image to an adjusted virtual image having an updated perspective corresponding to an updated tracked pose of the virtual reality device. Once the virtual image has been adjusted, the method proceeds to 612, where a virtual reality display of the virtual reality device displays the adjusted virtual image at or near the future time.
At 614, a communications machine of the virtual reality device sends to a remote computer a request for a virtual image having a perspective corresponding to the future pose of the virtual reality device. At 616, a remote communications machine of the remote computer receives the request from the virtual reality device.
Next, at 618, a virtual image renderer of the remote computer renders the virtual image for the virtual reality device as specified by the request received by the remote communications machine. Once the image has been rendered, the method proceeds to 620, at which point the remote communications machine sends to the virtual reality device the rendered virtual image.
At 622, the communications machine of the virtual reality device receives from the remote computer the virtual image, and the method proceeds to 608. The method of
HMD 700 includes separate right and left display panels, 704R and 704L, which may be wholly or partly transparent from the perspective of the wearer, to give the wearer a clear view of his or her surroundings. For example, the appearance of the physical environment may be augmented by graphical content (e.g., one or more pixels each having a respective color and brightness) that is presented via the display panels to create an augmented reality environment.
Each display panel includes a backlight and a liquid-crystal display (LCD) type microdisplay. The backlight may include an ensemble of light-emitting diodes (LEDs)—e.g., white LEDs or a distribution of red, green, and blue LEDs. The backlight may be configured to direct its emission through the LCD microdisplay, which forms a display image based on control signals from compute system 706. The LCD microdisplay may include numerous, individually addressable pixels arranged on a rectangular grid or other geometry. In some embodiments, pixels transmitting red light may be juxtaposed to pixels transmitting green and blue light, so that the LCD microdisplay forms a color image. In other embodiments, a reflective liquid-crystal-on-silicon (LCOS) microdisplay or a digital micromirror array may be used in lieu of the LCD microdisplay. Alternatively, an active LED, holographic, or scanned-beam microdisplay may be used to form right and left display images. Although the drawings show separate right and left display panels, a single display panel extending over both eyes may be used instead.
Compute system 706 is operatively coupled to the display panels and to other display-system componentry. The compute system may include a logic machine and a storage machine, as discussed in more detail below with respect to
HMD device 700 may also include a head tracking system that utilizes one or more motion sensors, such as sensors 708 on HMD device 700, to capture pose data and thereby enable position tracking, direction and orientation sensing, and/or motion detection of the user's head and/or HMD device 700.
The head tracking system may also support other suitable positioning techniques, such as GPS or other global navigation systems. Further, while specific examples of position sensor systems have been described, it will be appreciated that any other suitable position sensor systems may be used. For example, pose and/or movement data may be determined based on sensor information from any combination of sensors mounted on the wearer and/or external to the wearer including, but not limited to, any number of gyroscopes, accelerometers, inertial measurement units (IMUs), GPS devices, barometers, magnetometers, cameras (e.g., visible light cameras, infrared light cameras, time-of-flight depth cameras, structured light depth cameras, etc.), communication devices (e.g., WIFI antennas/interfaces), etc.
In some examples the HMD device 700 may also include an optical sensor system that utilizes one or more outward facing sensors, such as color camera 712 or depth camera 714 on HMD device 700, to capture image data. The outward facing sensor(s) may detect movements within its field of view, such as gesture-based inputs or other movements performed by a user or by a person or physical object within the field of view. The outward facing sensor(s) may also capture 2D image information and depth information from the physical environment and physical objects within the environment.
The optical sensor system may include a depth tracking system that generates depth tracking data via one or more depth cameras. In one example, each depth camera may include left and right cameras of a stereoscopic vision system. Time-resolved images from one or more of these depth cameras may be registered to each other and/or to images from another optical sensor such as a visible spectrum camera, and may be combined to yield depth-resolved video.
In other examples a structured light depth camera may be configured to project a structured infrared illumination, and to image the illumination reflected from a scene onto which the illumination is projected. A depth map of the scene may be constructed based on spacings between adjacent features in the various regions of an imaged scene. In still other examples, a depth camera may take the form of a time-of-flight depth camera configured to project a pulsed infrared illumination onto a scene and detect the illumination reflected from the scene. For example, modulated illumination may be provided by an infrared light source, and a phase difference between projected and reflected illumination may be used to calculate the time between projecting and detecting the light. It will be appreciated that any other suitable depth camera may be used within the scope of the present disclosure.
The outward facing sensor(s) may capture images of the physical environment in which a user is situated. With respect to the HMD device 700, in one example a mixed reality display program may include a 3D modeling system that uses such captured images to generate a virtual environment that models the physical environment surrounding the user.
In one example, the HMD 700 may include a gaze tracking system configured to detect a direction of gaze of each eye of a user. The gaze detection subsystem may be configured to determine gaze directions of each of a user's eyes in any suitable manner. For example, the gaze detection subsystem may comprise one or more light sources, such as infrared light sources, configured to cause a glint of light to reflect from the cornea of each eye of a user. One or more image sensors may then be configured to capture an image of the user's eyes.
Images of the glints and of the pupils as determined from image data gathered from the image sensors may be used to determine an optical axis of each eye. Using this information, the gaze tracking system may then determine a direction the user is gazing. The gaze tracking system may additionally or alternatively determine at what physical or virtual object the user is gazing. Such gaze tracking data may then be provided to the HMD device 700.
It will also be understood that the gaze tracking system may have any suitable number and arrangement of light sources and image sensors. For example, the gaze tracking system of the HMD device 700 may utilize at least one inward facing sensor.
The HMD device 700 may also include a microphone system that includes one or more microphones that capture audio data. In other examples, audio may be presented to the user via one or more speakers, such as speakers 710 on the HMD device 700.
In some embodiments, the methods and processes described herein may be tied to one or more computing systems of one or more computing devices. In particular, such methods and processes may be implemented as a computer-application program or service, an application-programming interface (API), a library, and/or other computer-program product.
Local computer 800 includes a logic machine 802 and a storage machine 804. Local computer 800 may optionally include a display subsystem 810, input subsystem 812, communications machine 814, and/or other components not shown in
Logic machines 802 and 818 include one or more physical devices configured to execute instructions. For example, the logic machines may be configured to execute instructions that are part of one or more applications, services, programs, routines, libraries, objects, components, data structures, or other logical constructs. Such instructions may be implemented to perform a task, implement a data type, transform the state of one or more components, achieve a technical effect, or otherwise arrive at a desired result.
The logic machines may include one or more processors configured to execute software instructions. Additionally or alternatively, the logic machines may include one or more hardware or firmware logic machines configured to execute hardware or firmware instructions. Processors of the logic machines may be single-core or multi-core, and the instructions executed thereon may be configured for sequential, parallel, and/or distributed processing. Individual components of the logic machines optionally may be distributed among two or more separate devices, which may be remotely located and/or configured for coordinated processing. Aspects of the logic machines may be virtualized and executed by remotely accessible, networked computing devices configured in a cloud-computing configuration.
Storage machines 804 and 820 include one or more physical devices configured to hold instructions executable by the logic machines to implement the methods and processes described herein. When such methods and processes are implemented, the state of storage machines 804 and 820 may be transformed—e.g., to hold different data.
Storage machines 804 and 820 may include removable and/or built-in devices. Storage machines 804 and 820 may include optical memory (e.g., CD, DVD, HD-DVD, Blu-Ray Disc, etc.), semiconductor memory (e.g., RAM, EPROM, EEPROM, etc.), and/or magnetic memory (e.g., hard-disk drive, floppy-disk drive, tape drive, MRAM, etc.), among others. Storage machines 804 and 820 may include volatile, nonvolatile, dynamic, static, read/write, read-only, random-access, sequential-access, location-addressable, file-addressable, and/or content-addressable devices.
It will be appreciated that storage machines 804 and 820 include one or more physical devices. However, aspects of the instructions described herein alternatively may be propagated by a communication medium (e.g., an electromagnetic signal, an optical signal, etc.) that is not held by a physical device for a finite duration.
Aspects of logic machines 802 and 818, and storage machines 804 and 820, may be integrated together into one or more hardware-logic components. Such hardware-logic components may include field-programmable gate arrays (FPGAs), program- and application-specific integrated circuits (PASIC/ASICs), program- and application-specific standard products (PSSP/ASSPs), system-on-a-chip (SOC), and complex programmable logic devices (CPLDs), for example.
The pose prediction machine 806 and the late stage reprojection machine 808 may be implemented via logic machine 802 and storage machine 804 and/or any other suitable devices. Further, the virtual image renderer 822 may be implemented via logic machine 818 and storage machine 820 and/or any other suitable devices. In some embodiments, the local computer 800 may include a local image renderer, as described above, which may additionally be implemented via logic machine 802 and storage machine 804. Further, the remote computer may include a pose prediction machine, as described above, which may be implemented via logic machine 818 and storage machine 820.
The terms “module,” “program,” and “engine” may be used to describe an aspect of computing system 800 implemented to perform a particular function. In some cases, a module, program, or engine may be instantiated via logic machines 802 and/or 818 executing instructions held by storage machines 804 and/or 820. It will be understood that different modules, programs, and/or engines may be instantiated from the same application, service, code block, object, library, routine, API, function, etc. Likewise, the same module, program, and/or engine may be instantiated by different applications, services, code blocks, objects, routines, APIs, functions, etc. The terms “module,” “program,” and “engine” may encompass individual or groups of executable files, data files, libraries, drivers, scripts, database records, etc.
It will be appreciated that a “service”, as used herein, is an application program executable across multiple user sessions. A service may be available to one or more system components, programs, and/or other services. In some implementations, a service may run on one or more server-computing devices.
When included, display subsystems 810 and/or 824 may be used to present a visual representation of data held by storage machines 804 and/or 820. This visual representation may take the form of a graphical user interface (GUI). As the herein described methods and processes change the data held by the storage machines, and thus transform the state of the storage machines, the state of display subsystems 810 and 824 may likewise be transformed to visually represent changes in the underlying data. Display subsystems 810 and 824 may include one or more display devices utilizing virtually any type of technology. Such display devices may be combined with logic machines 802 and 818 and/or storage machines 804 and 820 in a shared enclosure, or such display devices may be peripheral display devices. In particular, display subsystem 810 may in some embodiments be implemented as a virtual reality display.
When included, input subsystems 812 and 826 may comprise or interface with one or more user-input devices such as a keyboard, mouse, touch screen, or game controller. In some embodiments, the input subsystems may comprise or interface with selected natural user input (NUI) componentry. Such componentry may be integrated or peripheral, and the transduction and/or processing of input actions may be handled on- or off-board. Example NUI componentry may include a microphone for speech and/or voice recognition; an infrared, color, stereoscopic, and/or depth camera for machine vision and/or gesture recognition; a head tracker, eye tracker, accelerometer, and/or gyroscope for motion detection and/or intent recognition; as well as electric-field sensing componentry for assessing brain activity. In particular, the one or more sensors described above may in some embodiments be implemented as input subsystems 812 and/or 826.
When included, communications machine 814 and remote communications machine 828 may be configured to communicatively couple local computer 800 to remote computer 816 via network 830, and may be further configured to allow the local computer and/or the remote computer to communicate with one or more other computer systems. Communications machine 814 and remote communications machine 828 may include wired and/or wireless communication devices compatible with one or more different communication protocols. As non-limiting examples, the communications machines may be configured for communication via a wireless telephone network, or a wired or wireless local- or wide-area network. In some embodiments, the communications machines may allow local computer 800 and remote computer 816 to send and/or receive messages to and/or from other devices via a network such as the Internet.
In an example, a virtual reality device comprises: one or more sensors configured to track a pose of the virtual reality device; a pose prediction machine configured to predict a future pose of the virtual reality device at a future time; a communications machine configured to send to a remote computer a request for a virtual image having a perspective corresponding to the future pose of the virtual reality device and to receive from the remote computer the virtual image; a late stage reprojection machine configured to adjust the virtual image to an adjusted virtual image having an updated perspective corresponding to an updated tracked pose of the virtual reality device; and a virtual reality display configured to display the adjusted virtual image. In this example or any other example, the communications machine is further configured to determine a communications latency by measuring an elapsed time between the request being sent and the virtual image being received. In this example or any other example, the pose prediction machine is configured to dynamically adjust a buffer period between a current time and the future time for which the future pose is predicted, the buffer period dynamically increased with increasing communications latency and dynamically decreased with decreasing communications latency. In this example or any other example, the one or more sensors are configured to detect a motion of the virtual reality device in one or more dimensions. In this example or any other example, the pose prediction machine is configured to predict the future pose by extrapolating the detected motion forward from a current time to the future time. In this example or any other example, extrapolating the detected motion comprises extrapolating the detected motion forward with biomechanical constraints. In this example or any other example, extrapolating the detected motion comprises extrapolating the detected motion forward with environmental constraints. In this example or any other example, the virtual reality device is configured to display an image having a set resolution, and the virtual image is oversized relative to the set resolution. In this example or any other example, an amount of oversizing is proportional to a speed of the detected motion. In this example or any other example, an amount of oversizing in a first dimension of the virtual image is proportional to a speed of the detected motion in the first dimension, and an amount of oversizing in a second dimension of the virtual image is independently proportional to a speed of the detected motion in the second dimension. In this example or any other example, adjusting the virtual image comprises cropping the virtual image to the set resolution. In this example or any other example, adjusting the virtual image comprises shifting the virtual image by an amount that is proportional to a difference between the predicted future pose and the updated tracked pose. In this example or any other example, the virtual image is a three-dimensional image, adjusting the virtual image comprises independently shifting different aspects of the three-dimensional virtual image by an amount that is proportional to a difference between the predicted future pose and the updated tracked pose, and further comprises independently shifting each particular aspect of the three-dimensional virtual image by an amount that is inversely proportional to a virtual depth of the particular aspect. In this example or any other example, the virtual reality device further comprises a local virtual image renderer configured to locally render one or more virtual objects, and the virtual reality display is configured to display the one or more virtual objects rendered by the local virtual image renderer with the adjusted virtual image. In this example or any other example, the virtual reality device and the remote computer communicate over a computer network, and each of the virtual reality device and the remote computer occupy a different network node. In this example or any other example, the virtual image received from the remote computer includes additional content provided by the remote computer.
In an example, a computing device comprises: a remote communications machine configured to receive from a virtual reality device a request for a virtual image having a perspective corresponding to a predicted future pose of the virtual reality device, and send to the virtual reality device a rendered virtual image; and a virtual image renderer configured to render the virtual image for the virtual reality device as specified by the request received by the remote communications machine.
In an example, a virtual reality device comprises: one or more sensors configured to track a pose of the virtual reality device; a communications machine configured to send to a remote computer a request for a virtual image having a perspective corresponding to a future pose of the virtual reality device and to receive from the remote computer the virtual image; a late stage reprojection machine configured to adjust the virtual image to an adjusted virtual image having an updated perspective corresponding to an updated tracked pose of the virtual reality device; and a virtual reality display configured to display the adjusted virtual image. In this example or any other example, a future time of the future pose is dynamically predicted based on communication latency. In this example or any other example, the future pose is predicted by extrapolating detected motion forward from a current time to the future time.
It will be understood that the configurations and/or approaches described herein are exemplary in nature, and that these specific embodiments or examples are not to be considered in a limiting sense, because numerous variations are possible. The specific routines or methods described herein may represent one or more of any number of processing strategies. As such, various acts illustrated and/or described may be performed in the sequence illustrated and/or described, in other sequences, in parallel, or omitted. Likewise, the order of the above-described processes may be changed.
The subject matter of the present disclosure includes all novel and nonobvious combinations and subcombinations of the various processes, systems and configurations, and other features, functions, acts, and/or properties disclosed herein, as well as any and all equivalents thereof.
Number | Name | Date | Kind |
---|---|---|---|
5742264 | Inagaki | Apr 1998 | A |
5787333 | Rasinski | Jul 1998 | A |
5959597 | Yamada | Sep 1999 | A |
6092058 | Smyth | Jul 2000 | A |
6133867 | Eberwine | Oct 2000 | A |
6215780 | Peters | Apr 2001 | B1 |
6234983 | Storey | May 2001 | B1 |
6359603 | Zwern | Mar 2002 | B1 |
6415317 | Yelon | Jul 2002 | B1 |
7117157 | Taylor | Oct 2006 | B1 |
7804507 | Yang et al. | Sep 2010 | B2 |
8050881 | Yeung | Nov 2011 | B1 |
8098290 | Mittal | Jan 2012 | B2 |
8403757 | Mizrachi | Mar 2013 | B2 |
8487838 | Lewis et al. | Jul 2013 | B2 |
8620069 | Pinkus | Dec 2013 | B1 |
8633946 | Cohen | Jan 2014 | B2 |
8813028 | Farooqi | Aug 2014 | B2 |
8826344 | Gavade | Sep 2014 | B1 |
8886715 | Zhu | Nov 2014 | B1 |
8988509 | Macmillan | Mar 2015 | B1 |
8990011 | Zhao | Mar 2015 | B2 |
9063330 | LaValle | Jun 2015 | B2 |
9164588 | Johnson | Oct 2015 | B1 |
9176582 | Johnson | Nov 2015 | B1 |
9199176 | Iwamoto | Dec 2015 | B2 |
9229540 | Mandella | Jan 2016 | B2 |
9240069 | Li | Jan 2016 | B1 |
9269239 | Jensen | Feb 2016 | B1 |
9279983 | Davis | Mar 2016 | B1 |
9329682 | Keane | May 2016 | B2 |
9360671 | Zhou | Jun 2016 | B1 |
9374676 | Banin | Jun 2016 | B1 |
9389088 | Kalai | Jul 2016 | B2 |
9396588 | Li | Jul 2016 | B1 |
9451051 | Ray | Sep 2016 | B1 |
9459454 | The | Oct 2016 | B1 |
9479567 | Koorapati | Oct 2016 | B1 |
9514551 | Dewan | Dec 2016 | B2 |
9569812 | Kopf | Feb 2017 | B1 |
9595083 | Smith | Mar 2017 | B1 |
9652893 | Michail | May 2017 | B2 |
9652897 | Osborn | May 2017 | B2 |
9672660 | Mullins | Jun 2017 | B2 |
9767613 | Bedikian | Sep 2017 | B1 |
9779540 | Katz | Oct 2017 | B2 |
9779554 | Stafford | Oct 2017 | B2 |
9823473 | Kobayashi | Nov 2017 | B2 |
9858637 | Quach | Jan 2018 | B1 |
9897805 | Stafford | Feb 2018 | B2 |
9904969 | Westerhoff | Feb 2018 | B1 |
9927870 | Li | Mar 2018 | B2 |
9928655 | Alston | Mar 2018 | B1 |
9984441 | Kritt | May 2018 | B2 |
9984499 | Jurgenson | May 2018 | B1 |
9992449 | Ashkenazi | Jun 2018 | B1 |
9992628 | Lopez-Uricoechea | Jun 2018 | B2 |
9996149 | Martin | Jun 2018 | B1 |
10026233 | Li | Jul 2018 | B2 |
10083538 | Li | Sep 2018 | B2 |
10089790 | Lawson | Oct 2018 | B2 |
10127725 | Kohler | Nov 2018 | B2 |
10194259 | Martin | Jan 2019 | B1 |
10217058 | Gamon | Feb 2019 | B2 |
10255658 | Kono | Apr 2019 | B2 |
10304199 | Menozzi | May 2019 | B2 |
10313661 | Kass | Jun 2019 | B2 |
10317680 | Richards | Jun 2019 | B1 |
10321258 | Arteaga | Jun 2019 | B2 |
10338392 | Kohler | Jul 2019 | B2 |
10410349 | Haraden | Sep 2019 | B2 |
10417739 | Bastani | Sep 2019 | B2 |
10460455 | Giurgica-Tiron | Oct 2019 | B2 |
10481679 | Sevostianov | Nov 2019 | B2 |
10520739 | Vlachos | Dec 2019 | B1 |
10528132 | Hassani | Jan 2020 | B1 |
10565964 | Hicks | Feb 2020 | B2 |
10585472 | Tokubo | Mar 2020 | B2 |
10599919 | Freedman | Mar 2020 | B2 |
10629107 | Yamamoto | Apr 2020 | B2 |
10644397 | Pallister | May 2020 | B2 |
10698218 | Geng | Jun 2020 | B1 |
10699472 | Yeoh | Jun 2020 | B2 |
10712817 | Ronngren | Jul 2020 | B1 |
10732707 | Lavalle | Aug 2020 | B2 |
10802287 | Selan | Oct 2020 | B2 |
20010022558 | Karr, Jr. | Sep 2001 | A1 |
20030025651 | Susnjara | Feb 2003 | A1 |
20030025652 | Susnfara | Feb 2003 | A1 |
20040036717 | Kjeldsen | Feb 2004 | A1 |
20040039938 | Katz | Feb 2004 | A1 |
20040051680 | Azuma | Mar 2004 | A1 |
20040240708 | Hu | Dec 2004 | A1 |
20050165886 | Tuer | Jul 2005 | A1 |
20050196015 | Luo | Sep 2005 | A1 |
20060187850 | Ward | Aug 2006 | A1 |
20060188080 | Terpstra | Aug 2006 | A1 |
20070035562 | Azuma | Feb 2007 | A1 |
20070238529 | Iwamoto | Oct 2007 | A1 |
20070276590 | Leonard | Nov 2007 | A1 |
20070294030 | Jones | Dec 2007 | A1 |
20080141127 | Yamamoto | Jun 2008 | A1 |
20090281718 | Gibran | Nov 2009 | A1 |
20100009747 | Reville | Jan 2010 | A1 |
20100026714 | Utagawa | Feb 2010 | A1 |
20100091096 | Oikawa | Apr 2010 | A1 |
20100195517 | Kihara | Aug 2010 | A1 |
20100226360 | Li | Sep 2010 | A1 |
20110050568 | Hu | Mar 2011 | A1 |
20110102469 | Kami | May 2011 | A1 |
20110157196 | Nave | Jun 2011 | A1 |
20110169625 | James | Jul 2011 | A1 |
20110234584 | Endo | Sep 2011 | A1 |
20110248987 | Mitchell | Oct 2011 | A1 |
20110254860 | Lontrop et al. | Oct 2011 | A1 |
20120056887 | Kim | Mar 2012 | A1 |
20120105473 | Bar-Zeev | May 2012 | A1 |
20120113223 | Hilliges | May 2012 | A1 |
20120133748 | Chung | May 2012 | A1 |
20120154390 | Narita | Jun 2012 | A1 |
20120188256 | Lee et al. | Jul 2012 | A1 |
20120281906 | Appia | Nov 2012 | A1 |
20120299911 | Tytgat | Nov 2012 | A1 |
20120306850 | Balan et al. | Dec 2012 | A1 |
20120308140 | Ambrus | Dec 2012 | A1 |
20120309532 | Ambrus | Dec 2012 | A1 |
20120320224 | Miyoshi | Dec 2012 | A1 |
20120330659 | Nakadai | Dec 2012 | A1 |
20130003864 | Sullivan | Jan 2013 | A1 |
20130041590 | Burich | Feb 2013 | A1 |
20130079039 | Heikkilae | Mar 2013 | A1 |
20130128364 | Wheeler | May 2013 | A1 |
20130147838 | Small et al. | Jun 2013 | A1 |
20130151651 | Chhaochharia | Jun 2013 | A1 |
20130169682 | Novak et al. | Jul 2013 | A1 |
20130185022 | Maehata | Jul 2013 | A1 |
20130307847 | Dey | Nov 2013 | A1 |
20130308016 | Ishii | Nov 2013 | A1 |
20130326364 | Latta | Dec 2013 | A1 |
20130328927 | Mount | Dec 2013 | A1 |
20130335405 | Scavezze | Dec 2013 | A1 |
20140002491 | Lamb et al. | Jan 2014 | A1 |
20140125554 | Pan | May 2014 | A1 |
20140145079 | Omino | May 2014 | A1 |
20140146394 | Tout | May 2014 | A1 |
20140168261 | Margolis | Jun 2014 | A1 |
20140176591 | Klein | Jun 2014 | A1 |
20140186049 | Oshima | Jul 2014 | A1 |
20140240313 | Varga | Aug 2014 | A1 |
20140240351 | Scavezze | Aug 2014 | A1 |
20140267420 | Schowengerdt et al. | Sep 2014 | A1 |
20140310595 | Acharya | Oct 2014 | A1 |
20140324249 | Lacaze | Oct 2014 | A1 |
20140354515 | LaValle | Dec 2014 | A1 |
20140361956 | Mikhailov | Dec 2014 | A1 |
20140361977 | Stafford | Dec 2014 | A1 |
20140368534 | Salter et al. | Dec 2014 | A1 |
20140368535 | Salter | Dec 2014 | A1 |
20140372957 | Keane | Dec 2014 | A1 |
20140375634 | Hillesland | Dec 2014 | A1 |
20150002542 | Chan | Jan 2015 | A1 |
20150029218 | Williams | Jan 2015 | A1 |
20150046296 | Hart | Feb 2015 | A1 |
20150049004 | Deering | Feb 2015 | A1 |
20150117757 | Drazic | Apr 2015 | A1 |
20150123973 | Larsen | May 2015 | A1 |
20150134723 | Kansal | May 2015 | A1 |
20150145889 | Hanai | May 2015 | A1 |
20150188984 | Mullins | Jul 2015 | A1 |
20150193949 | Katz | Jul 2015 | A1 |
20150206317 | Baek | Jul 2015 | A1 |
20150228118 | Eade | Aug 2015 | A1 |
20150234189 | Lyons | Aug 2015 | A1 |
20150234455 | LaValle | Aug 2015 | A1 |
20150310665 | Michail | Oct 2015 | A1 |
20150317833 | Ebstyne | Nov 2015 | A1 |
20150323988 | Kuehne | Nov 2015 | A1 |
20150339468 | Son | Nov 2015 | A1 |
20150355332 | Jeong | Dec 2015 | A1 |
20150356774 | Gal | Dec 2015 | A1 |
20150373153 | Jenkins | Dec 2015 | A1 |
20160012855 | Krishnan | Jan 2016 | A1 |
20160025971 | Crow | Jan 2016 | A1 |
20160027141 | Patel | Jan 2016 | A1 |
20160034823 | Farkas | Feb 2016 | A1 |
20160035139 | Fuchs | Feb 2016 | A1 |
20160042566 | Mao | Feb 2016 | A1 |
20160055640 | Menozzi | Feb 2016 | A1 |
20160070551 | Miller | Mar 2016 | A1 |
20160077166 | Morozov | Mar 2016 | A1 |
20160085310 | Shotton | Mar 2016 | A1 |
20160087868 | Polychronis | Mar 2016 | A1 |
20160093105 | Rimon | Mar 2016 | A1 |
20160131902 | Ambrus | May 2016 | A1 |
20160155260 | Jenkins | Jun 2016 | A1 |
20160163112 | Mullins | Jun 2016 | A1 |
20160179336 | Ambrus | Jun 2016 | A1 |
20160189429 | Mallinson | Jun 2016 | A1 |
20160205174 | Pitio | Jul 2016 | A1 |
20160209916 | Sendai | Jul 2016 | A1 |
20160210780 | Paulovich | Jul 2016 | A1 |
20160216760 | Trutna | Jul 2016 | A1 |
20160217760 | Chu | Jul 2016 | A1 |
20160219267 | Chu | Jul 2016 | A1 |
20160219272 | Fujimaki | Jul 2016 | A1 |
20160219325 | Chu | Jul 2016 | A1 |
20160227098 | Yasuhara | Aug 2016 | A1 |
20160238852 | Ellsworth | Aug 2016 | A1 |
20160252955 | Yamamoto | Sep 2016 | A1 |
20160253842 | Shapira | Sep 2016 | A1 |
20160259403 | Wang | Sep 2016 | A1 |
20160260251 | Stafford | Sep 2016 | A1 |
20160260261 | Hsu | Sep 2016 | A1 |
20160261300 | Fei | Sep 2016 | A1 |
20160262608 | Krueger | Sep 2016 | A1 |
20160267720 | Mandella | Sep 2016 | A1 |
20160282619 | Oto | Sep 2016 | A1 |
20160284126 | Leppanen | Sep 2016 | A1 |
20160321548 | Ziskind | Nov 2016 | A1 |
20160350973 | Shapira | Dec 2016 | A1 |
20160358299 | Toth | Dec 2016 | A1 |
20160360466 | Barak | Dec 2016 | A1 |
20170003750 | Li | Jan 2017 | A1 |
20170003764 | Li | Jan 2017 | A1 |
20170004648 | Li | Jan 2017 | A1 |
20170010692 | Getz | Jan 2017 | A1 |
20170017831 | Rollend | Jan 2017 | A1 |
20170018086 | Zhang | Jan 2017 | A1 |
20170018121 | Lawson | Jan 2017 | A1 |
20170024624 | Bieg | Jan 2017 | A1 |
20170034037 | Gilad | Feb 2017 | A1 |
20170038837 | Faaborg | Feb 2017 | A1 |
20170053450 | Rodriguez | Feb 2017 | A1 |
20170060264 | Gasselin de Richebourg | Mar 2017 | A1 |
20170060286 | Gasselin de Richebourg | Mar 2017 | A1 |
20170060645 | Gasselin de Richebourg | Mar 2017 | A1 |
20170103457 | Acuna-Rohter | Apr 2017 | A1 |
20170115488 | Ambrus | Apr 2017 | A1 |
20170124170 | Koorapati | May 2017 | A1 |
20170124713 | Jurgenson | May 2017 | A1 |
20170148206 | Donner | May 2017 | A1 |
20170154464 | Lanier | Jun 2017 | A1 |
20170155885 | Selstad | Jun 2017 | A1 |
20170160518 | Lanman | Jun 2017 | A1 |
20170160795 | Hu | Jun 2017 | A1 |
20170160798 | Lanman | Jun 2017 | A1 |
20170161951 | Fix | Jun 2017 | A1 |
20170177082 | Michail | Jun 2017 | A1 |
20170180721 | Parker | Jun 2017 | A1 |
20170185144 | Li | Jun 2017 | A1 |
20170186231 | Petrov | Jun 2017 | A1 |
20170200304 | Li | Jul 2017 | A1 |
20170208416 | Petrov | Jul 2017 | A1 |
20170213388 | Margolis | Jul 2017 | A1 |
20170249745 | Fiala | Aug 2017 | A1 |
20170254664 | Parekh | Sep 2017 | A1 |
20170262054 | Lanman | Sep 2017 | A1 |
20170287409 | Richards | Oct 2017 | A1 |
20170289219 | Khalid | Oct 2017 | A1 |
20170289530 | Smithwick | Oct 2017 | A1 |
20170291704 | Alegria | Oct 2017 | A1 |
20170294989 | Chen | Oct 2017 | A1 |
20170295446 | Thagadur Shivappa | Oct 2017 | A1 |
20170302918 | Mammou | Oct 2017 | A1 |
20170316607 | Khalid | Nov 2017 | A1 |
20170347084 | Boyce | Nov 2017 | A1 |
20170347236 | Frusina | Nov 2017 | A1 |
20170353812 | Schaefer | Dec 2017 | A1 |
20170358136 | Gollier | Dec 2017 | A1 |
20170372494 | Zhu | Dec 2017 | A1 |
20170373890 | Fertonani | Dec 2017 | A1 |
20170374343 | Boulton | Dec 2017 | A1 |
20170374344 | Boulton | Dec 2017 | A1 |
20180008141 | Krueger | Jan 2018 | A1 |
20180017659 | Irie | Jan 2018 | A1 |
20180018783 | Menozzi | Jan 2018 | A1 |
20180025478 | Lee | Jan 2018 | A1 |
20180039083 | Miller | Feb 2018 | A1 |
20180040162 | Donnelly | Feb 2018 | A1 |
20180041849 | Farmani | Feb 2018 | A1 |
20180049023 | Stuber | Feb 2018 | A1 |
20180059779 | Sisbot | Mar 2018 | A1 |
20180075653 | Schillings | Mar 2018 | A1 |
20180078034 | Savall | Mar 2018 | A1 |
20180081171 | Park | Mar 2018 | A1 |
20180081178 | Shpunt | Mar 2018 | A1 |
20180091791 | Jiang | Mar 2018 | A1 |
20180091924 | Hammerschmidt | Mar 2018 | A1 |
20180108179 | Tomlin | Apr 2018 | A1 |
20180161682 | Myhill | Jun 2018 | A1 |
20180167132 | Balk | Jun 2018 | A1 |
20180175926 | Rudrapatna | Jun 2018 | A1 |
20180188384 | Ramanandan | Jul 2018 | A1 |
20180189661 | Tatourian | Jul 2018 | A1 |
20180190037 | Sou | Jul 2018 | A1 |
20180190091 | Yuan | Jul 2018 | A1 |
20180192058 | Chen | Jul 2018 | A1 |
20180196509 | Trail | Jul 2018 | A1 |
20180203505 | Trail | Jul 2018 | A1 |
20180204078 | Seng | Jul 2018 | A1 |
20180205943 | Trail | Jul 2018 | A1 |
20180206134 | Kudo | Jul 2018 | A1 |
20180220119 | Horvitz | Aug 2018 | A1 |
20180232928 | Grant | Aug 2018 | A1 |
20180239145 | Lanman | Aug 2018 | A1 |
20180261012 | Mullins | Sep 2018 | A1 |
20180262847 | Pedersen | Sep 2018 | A1 |
20180262849 | Farmani | Sep 2018 | A1 |
20180268589 | Grant | Sep 2018 | A1 |
20180275748 | Haraden | Sep 2018 | A1 |
20180276824 | Haraden | Sep 2018 | A1 |
20180277164 | Wang | Sep 2018 | A1 |
20180284872 | Schluessler | Oct 2018 | A1 |
20180284876 | Ray | Oct 2018 | A1 |
20180286105 | Surti | Oct 2018 | A1 |
20180288423 | Vembar | Oct 2018 | A1 |
20180292895 | Schluessler | Oct 2018 | A1 |
20180300098 | Vembar | Oct 2018 | A1 |
20180300897 | Woods | Oct 2018 | A1 |
20180301110 | Feng | Oct 2018 | A1 |
20180302590 | Kuzyakov | Oct 2018 | A1 |
20180307306 | Johnston | Oct 2018 | A1 |
20180308451 | Saur | Oct 2018 | A1 |
20180308455 | Hicks | Oct 2018 | A1 |
20180309927 | Tanner | Oct 2018 | A1 |
20180341323 | Mate | Nov 2018 | A1 |
20180356882 | Kaneko | Dec 2018 | A1 |
20180374192 | Kunkel | Dec 2018 | A1 |
20190006754 | Pallister | Jan 2019 | A1 |
20190026864 | Chen | Jan 2019 | A1 |
20190026904 | Chen | Jan 2019 | A1 |
20190035363 | Schluessler | Jan 2019 | A1 |
20190037203 | Ishiguchi | Jan 2019 | A1 |
20190037462 | Chowdhury | Jan 2019 | A1 |
20190041976 | Veeramani | Feb 2019 | A1 |
20190057542 | Bronder | Feb 2019 | A1 |
20190058853 | Brudnak | Feb 2019 | A1 |
20190058863 | Sameer | Feb 2019 | A1 |
20190072367 | Balk | Mar 2019 | A1 |
20190147221 | Grabner | May 2019 | A1 |
20190155372 | Cuervo | May 2019 | A1 |
20190158731 | Demarty | May 2019 | A1 |
20190200902 | El Kouby-Benichou | Jul 2019 | A1 |
20190206115 | Tytgat | Jul 2019 | A1 |
20190209005 | Barraza-Bernal | Jul 2019 | A1 |
20190212158 | Gordon | Jul 2019 | A1 |
20190228215 | Najafirad | Jul 2019 | A1 |
20190235624 | Goldberg | Aug 2019 | A1 |
20190236344 | Chen | Aug 2019 | A1 |
20190243472 | Stafford | Aug 2019 | A1 |
20190244436 | Stansell | Aug 2019 | A1 |
20190250702 | Cristani | Aug 2019 | A1 |
20190251892 | Stoll | Aug 2019 | A1 |
20190279603 | Hada | Sep 2019 | A1 |
20190286231 | Burns | Sep 2019 | A1 |
20190320142 | Cutler | Oct 2019 | A1 |
20190354174 | Young | Nov 2019 | A1 |
20190356894 | Oh | Nov 2019 | A1 |
20190373391 | Han et al. | Dec 2019 | A1 |
20190379893 | Krishnan | Dec 2019 | A1 |
20190384378 | Ebert | Dec 2019 | A1 |
20190392212 | Sawhney | Dec 2019 | A1 |
20200005486 | Sinha | Jan 2020 | A1 |
20200035203 | Kosik | Jan 2020 | A1 |
20200043223 | Leiby | Feb 2020 | A1 |
20200045285 | Varerkar | Feb 2020 | A1 |
20200051320 | Laffont | Feb 2020 | A1 |
20200090403 | Ishida | Mar 2020 | A1 |
20200092488 | Bhuruth | Mar 2020 | A1 |
20200094141 | Fersch | Mar 2020 | A1 |
20200111195 | Vlachos | Apr 2020 | A1 |
20200124940 | Shimada | Apr 2020 | A1 |
20200125066 | Abe | Apr 2020 | A1 |
20200132996 | Yokota | Apr 2020 | A1 |
20200133000 | Amati | Apr 2020 | A1 |
20200135150 | Sugihara | Apr 2020 | A1 |
20200167712 | Stracquatanio | May 2020 | A1 |
20200195828 | Reyserhove | Jun 2020 | A1 |
20200195875 | Berkovich | Jun 2020 | A1 |
20200221243 | Schaefer | Jul 2020 | A1 |
20200225473 | Selan | Jul 2020 | A1 |
20200226357 | Protter | Jul 2020 | A1 |
20200228788 | Selan | Jul 2020 | A1 |
20200254876 | Cordell | Aug 2020 | A1 |
20200288164 | Lin | Sep 2020 | A1 |
20200322748 | Han | Oct 2020 | A1 |
Number | Date | Country |
---|---|---|
101080691 | Nov 2007 | CN |
102591449 | Jul 2012 | CN |
3070680 | Sep 2016 | EP |
2014144526 | Sep 2014 | WO |
2015098292 | Jul 2015 | WO |
Entry |
---|
Welch et al., SCAAT: Incremental Tracking with Incomplete Information, 1997 (Year: 1997). |
Szalavari, Z. et al., “‘Studierstube’ An Environment for Collaboration in Augmented Reality,” CVE '96 Workshop Proceedings, Sep. 19, 1996, 15 pages. |
Ohshima, T. et al., “AR2Hockey: A Case Study of Collaborative Augmented Reality,” IEEE 1998 Virtual Reality Annual International Symposium, Mar. 14, 1998, 8 pages. |
Billinghurst, M. et al., “A Wearable Spatial Conferencing Space,” 2nd IEEE International Symposium on Wearable computers (ISWC '98), Oct. 19, 1998, 8 pages. |
Billinghurst, M. et al., “Collaborative Mixed Reality,” International Symposium on Mixed Reality (MR '99), Mar. 19, 1999, 14 pages. |
Raskar, R. et al., “Table-Top Spatially-Augmented Reality: Bringing Physical Models to Life with Projected Imagery,” Second IEEE and Acm International Workshop on Augmented Reality (IWAR '99), Oct. 20, 1999, 8 pages. |
Ando, T. et al., “Head Mounted Display for Mixed Reality using Holographic Optical Elements,” Memoirs of the Faculty of Engineering, Osaka City University, Dec. 1999, 6 pages. |
Kato, H. et al., “Virtual Object Manipulation on a Table-Top AR Environment,” International Symposium on Augmented Reality (ISAR 2000), Oct. 2000, 9 pages. |
Benko, H. et al., “Collaborative Mixed Reality Visualization of an Archaeological Excavation,” Third IEEE and ACM International Symposium on Mixed and Augmented Reality (ISMAR '04), Nov. 2, 2004, 9 pages. |
Piekarski, W. et al., “Augmented Reality Working Planes: A Foundation for Action and Construction at a Distance,” Third IEEE and ACM International Symposium on Mixed and Augmented Reality (ISMAR '04), Nov. 2, 2004, 10 pages. |
Cosco, F. et al., “Visuo-Haptic Mixed Reality with Unobstructed Tool-Hand Integration,” IEEE Transactions on Visualization and Computer Graphics, vol. 19, No. 1, Apr. 17, 2012, 14 pages. |
“Canon Launches New MR (Mixed Reality) System, Contributing to Shorter Development Times During Product Design,” Canon Global News Releases Website, Available Online at http://www.canon.com/news/2012/jun18e.html, Jun. 18, 2012, 3 pages. |
“Unity Remote Coming to Google Cardboard SDK”, Retrieved on: Jul. 14, 2015 Available at: http://www.ebuzzword.com/unity-remote-coming-to-google-cardboard-sdk. |
Flynn, Scott, “Announcing Support for Microsoft Hololens”, Published on: Apr. 29, 2015 Available at: http://blogs.unity3d.com/2015/04/29/announcing-support-for-microsoft-hololens/. |
“Testing apps on the Gear2 Remotely”, Published on: Apr. 22, 2014 Available at: http://developer.samsung.com/what-is-new/blog/2014/Testing-apps-on-the-Gear2-Remotely. |
“About Remote Test Lab”, Published on: Oct. 24, 2012 Available at: http://developer.samsung.com/remotetestlab/rtlAboutRTL.action. |
“Creating and Running a Wearable App”, Published on: Mar. 16, 2015 Available at: https://developer.android.com/training/wearables/apps/creating.html. |
Helppi, Ville-Veikko, “App Development and Testing on Wearables”, Published on: Mar. 31, 2015 Available at: http://testdroid.com/news/app-development-and-testing-on-wearables. |
Lins, et al., “Development of Interactive Applications for Google Glass”, In Proceedings of Trends and Techniques in Virtual and Augmented Reality, vol. 4, May, 2014, pp. 167-188. |
Southard, Don, “Xcode 6: Live Rendering, Visual View Debugging, and Swift”, Published on: Sep. 18, 2014 Available at: http://www.macstories.net/mac/xcode-6-live-rendering-visual-view-debugging-and-swift/. |
“The Challenges of Creating a VR Application”, Retrieved on: Jul. 14, 2015 Available at: http://www.middlevr.com/resources/the-challenges-of-creating-a-vr-application/. |
“Hierarchy Viewer Walkthrough”, Retrieved on: Jul. 14, 2015 Available at: https://developer.android.com/tools/performance/hierarchy-viewer/index.html. |
“Develop for Google Glass—10 Steps for a Quick Start”, Published on: May 12, 2013 Available at: http://glass-apps.org/glass-developer. |
ISA European Patent Office, International Search Report and Written Opinion Issued in PCT Application No. PCT/US2016/013127, dated Apr. 1, 2016, WIPO, 14 pages. |
IPEA European Patent Office, Second Written Opinion Issued in PCT Application No. PCT/US2016/013127, dated Dec. 12, 2016, Wipo, 10 pages. |
ISA European Patent Office, International Search Report and Written Opinion Issued in PCT Application No. PCT/US2016/057565, dated Jan. 30, 2017, WIPO, 13 pages. |
Gamez, et al., “Wireless Network Delay Estimation for Time-Sensitive Application”, Retrieved From: <<https://web.archive.org/web/20160528074506/https://people-esaii.upc.edu/people/pmarti/nde_06.pdf>, Jul. 27, 2006, 13 Pages. |
Ananda, et al., “Estimation of Round Trip Time in Distributed Real Time System Architectures”, In Proceedings of the Australasian Telecommunication Networks and Applications Conference (ATNAC), Nov. 20, 2013, pp. 57-62. |
“Second Written Opinion Issued in PCT Application No. PCT/US2016/057565”, dated Sep. 5, 2017, 9 Pages. |
“International Preliminary Report on Patentability Issued in PCT Application No. PCT/US2016/057565”, dated Jan. 31, 2018, 10 Pages. |
“Office Action Issued in European Patent Application No. 16790809.4”, dated Apr. 18, 2019, 7 Pages. |
“Summon to Attend Oral Proceedings Issued in European Patent Application No. 16790809.4”, Mailed Date: Mar. 13, 2020, 14 Pages. |
“First Office Action and Search Report Issued in Chinese Patent Application No. 201680062861.X”, dated Aug. 3, 2020, 20 Pages. |
Number | Date | Country | |
---|---|---|---|
20170115488 A1 | Apr 2017 | US |